The Make Adaptive command applies to both the tube and pipe reuse workflow and assembly configuration workflow. The following table compares the differences in various aspects between the two workflows.
|
Reuse Workflow |
Configuration Workflow |
|
|
Edit environment |
Normal tube and pipe assembly |
Tube and pipe iAssembly factory |
|
Target components |
Secondary occurrences of the tube and pipe runs assembly, runs, routes, and hose assemblies. |
Non-adaptive primary runs assembly automatically created by configurations. |
|
External assembly constraints |
Assembly constraints can be placed to position a tube and pipe secondary occurrence as a rigid body. After the Make Adaptive command is applied, all such constraints are suppressed. |
When an external assembly constraint is created, edited, or deleted in an iAssembly factory, it is captured only in the active configuration member. |
|
File naming |
Once tube and pipe secondary occurrences are made adaptive, they follow the standard tube and pipe file naming convention and browser naming convention by default. File naming can be customized to meet your design needs. |
When a non-adaptive primary runs assembly is transitioned into the tube and pipe interchangeability set, the new adaptive primary runs assembly containing routes and runs is created in the appropriate configuration folder. By default, file names are prefixed with the configuration name. File naming can be customized to meet your design needs. |
|
File location |
You can designate a location to store the tube and pipe components if you are working with a secondary occurrence of primary runs assembly. |
File location for tube and pipe components are system-defined. Each configuration is affiliated to a specific folder. |
|
How to |
Transition a non-adaptive primary runs assembly into tube and pipe interchangeability set |