Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
what are the step by step instructions to execute and utilize displaying technique in CATIA V5.
NicoleKristen
Member Posts: 4
in Dynamics GP
we will discuss that in CATIA V5 elements in the specification tree should be renamed according to function and how much easier the edition process will be with proper naming of elements.
Avoid cryptic specification trees
a part with an organized specification tree (left side) versus a part with mixed modelling specification tree (right side). Both files present the same end geometry, considering the initial parameters specified for the design.
Let us make a comparison between their respective specification trees; notice that the organized part was named and all features in the PartBody were renamed as well. All elements inside the Skeleton geometrical set were also renamed but were not presented in the image.
Renaming may not seem important at first glance and for many designers is not considered a priority at all. We cannot emphasize enough how important this step is, particularly if the model is prone to edition at a later stage. Complex models become particularly hard to interpret, even for the part creator, given enough time.
Renaming should be done considering the function and not necessarily the tool name that was used to create the element. This rule is universal for all created design elements and modelling elements, we specifically state the created elements because imported input elements should keep their name, given in the source file where they were copied from. Notice also that the elements are numbered according to a specific coding method that we will discuss in a future article. This coding will help us group the used feature tools by function and increase model robustness.
Design and modelling stage organization
When we start inserting elements in a part, we should respect the Hierarchy Rule. This rule stratifies elements in different levels:
Imported reference geometry
Reference geometry and additional axis systems
Sketches
Imported solid geometry
Solid geometry features
This means a higher hierarchy element, such as reference geometry, cannot depend on elements belonging to lower levels of the hierarchy, such as faces created by solid geometry features. If we create the elements in sequence, it will help us guarantee that the hierarchy is respected. If we do not create them in sequence then we should be careful with the dependencies created.
There is a major difference between specification trees presented in figure 1; the organized specification tree (on the left) has two containers while the mixed modelling version only has the PartBody, thus one container only.
The organized tree version has a geometrical set called Skeleton and the PartBody. This clearly highlights the fact that the designer broke the creative process in two stages; all the design elements were inserted inside the Skeleton while all the modelling elements where created and stored inside the PartBody.
The mixed modelling version only has the PartBody because the sketch elements and reference geometry were created when needed and not according to the Hierarchy Rule. This makes the edition process that much harder because the sketch elements depend on existing modelled geometry (and they shouldn’t), this method increases the size of the dependency ladder and lends the model its unpredictable behaviour when edited.
Avoid cryptic specification trees
a part with an organized specification tree (left side) versus a part with mixed modelling specification tree (right side). Both files present the same end geometry, considering the initial parameters specified for the design.
Let us make a comparison between their respective specification trees; notice that the organized part was named and all features in the PartBody were renamed as well. All elements inside the Skeleton geometrical set were also renamed but were not presented in the image.
Renaming may not seem important at first glance and for many designers is not considered a priority at all. We cannot emphasize enough how important this step is, particularly if the model is prone to edition at a later stage. Complex models become particularly hard to interpret, even for the part creator, given enough time.
Renaming should be done considering the function and not necessarily the tool name that was used to create the element. This rule is universal for all created design elements and modelling elements, we specifically state the created elements because imported input elements should keep their name, given in the source file where they were copied from. Notice also that the elements are numbered according to a specific coding method that we will discuss in a future article. This coding will help us group the used feature tools by function and increase model robustness.
Design and modelling stage organization
When we start inserting elements in a part, we should respect the Hierarchy Rule. This rule stratifies elements in different levels:
Imported reference geometry
Reference geometry and additional axis systems
Sketches
Imported solid geometry
Solid geometry features
This means a higher hierarchy element, such as reference geometry, cannot depend on elements belonging to lower levels of the hierarchy, such as faces created by solid geometry features. If we create the elements in sequence, it will help us guarantee that the hierarchy is respected. If we do not create them in sequence then we should be careful with the dependencies created.
There is a major difference between specification trees presented in figure 1; the organized specification tree (on the left) has two containers while the mixed modelling version only has the PartBody, thus one container only.
The organized tree version has a geometrical set called Skeleton and the PartBody. This clearly highlights the fact that the designer broke the creative process in two stages; all the design elements were inserted inside the Skeleton while all the modelling elements where created and stored inside the PartBody.
The mixed modelling version only has the PartBody because the sketch elements and reference geometry were created when needed and not according to the Hierarchy Rule. This makes the edition process that much harder because the sketch elements depend on existing modelled geometry (and they shouldn’t), this method increases the size of the dependency ladder and lends the model its unpredictable behaviour when edited.
0