File naming

Files names and location of the master runs assembly , runs, and routes can be determined upon creation, but cannot be later modified. By default, multiple routes and runs are incrementally numbered based on file naming convention.

Display names of tube and pipe documents in the Model browser differ from file names in your project workspace. You can use the Design Assistant to rename display names in the Model browser.

Tip: The top assembly file name is not the project name suffixed with .ipj. It might be confusing if the top assembly file name is the same with the project name.

• To verify the project name, click ManageProjects. The Projects pane displays the currently active project name, as well as all existing project names.
• To verify the top assembly file name, check the top .iam in the Model browser.

Display names in the Model browser

By default, tube and pipe files use the following naming convention to display the container structure in the Model browser.

• Master runs assembly: Tube and Pipe Runs
• Runs: Pipe Run <n>
• Routes: Route<n>
• Flexible hose assemblies: Flexible Hose <n>. Each hose assembly contains only one hose route.
• Hose routes: Hose<n>.ipt

  , where <n> is the index number that automatically increments to indicate a unique file name.

Note: If the master assembly, runs, or routes are a result of using Make Adaptive on secondary occurrences, their display names in the Model browser may vary.

File names in your project workspace

By default, tube and pipe files use the following naming convention to store in your project workspace.

• Tube and pipe runs assembly: <top_assembly>.Tube and Pipe Runs.iam
• Runs: <top_assembly>.Run<n>.iam
• Routes: <top_assembly>.Route<n>.ipt
• Flexible hose assemblies: <top_assembly>.Hose<n>.iam
• Hose routes: <top_assembly>.Hose<n>.ipt

  The <top_assembly> is the top assembly underneath your project workspace as top_assembly in top_assembly.iam, and <n> is the index number that automatically increments to indicate a unique file name by default.

Secondary occurrences in the reuse and configuration workflows

In the copy and reuse workflow, for either display names in the Model browser or file names in your project workspace, secondary occurrences of exclusive tube and pipe components are suffixed with an occurrence number. When applying the Make Adaptive command, file names for the new documents can be customized but must be unique.

For the default display names in the Model browser:

• When a secondary occurrence becomes a primary occurrence , the new primary occurrence follows the standard tube and pipe browser naming convention.
• Secondary occurrences contained in a parent secondary occurrence remain non-adaptive. They cannot be made adaptive in a nested way. Display names in the Model browser inherit from the secondary occurrence with a suffix of occurrence number.

In the assembly configuration workflow, the master runs assembly keeps the same file name in the corresponding configuration folders in your project workspace.