2009
Table Of Contents
- Contents
- Tubes and Pipes
- 1 Getting Started with Tube & Pipe
- 2 Route Basics
- 3 Setting Styles
- 4 Creating Rigid Routes and Runs
- General Workflow for Rigid Routes
- Creating Auto Route Regions
- Manually Creating Parametric Regions
- Automatically Dimension Route Sketches
- Create Segments With Precise Values
- Define Parallel and Perpendicular Segments
- Snap Route Points to Existing Geometry
- Place Constraints On Route Sketches
- Create Bends Between Existing Pipe Segments
- Create Pipe Routes With Custom Bends
- Create Bent Tube Routes
- Realign 3D Orthogonal Route Tool
- Control Dimension Visibility
- Populated Routes
- 5 Creating and Editing Flexible Hose Routes
- 6 Editing Rigid Routes and Runs
- 7 Using Content Center Libraries
- 8 Authoring and Publishing
- 9 Documenting Routes and Runs
- Cable and Harness
- 10 Getting Started with Cable and Harness
- 11 Working With Harness Assemblies
- 12 Using the Cable and Harness Library
- 13 Working with Wires and Cables
- About Wires and Cables
- Setting Modeling and Curvature Behavior
- Inserting Wires and Cables Manually
- Moving Wires and Cables
- Deleting Wires and Cables
- Replacing Wires
- Assigning Virtual Parts
- Importing Harness Data
- Adding Shape to Wires and Cable Wires
- Setting Occurrence Properties
- Changing Wire and Cable Displays
- 14 Working with Segments
- 15 Routing Wires and Cables
- 16 Working with Splices
- 17 Working with Ribbon Cables
- 18 Generating Reports
- 19 Working Nailboards and Drawings
- IDF Translator
- Index
Set iPart Family Key Columns
An iPart can have up to 9 keys used to define criteria for AutoDrop and filtering
out the iPart for tube and pipe styles.
Pipe iParts typically have 3 family key columns: nominal size, schedule number,
and pipe length. For the sample pipe iPart:
■ On the Other tab, NPS is primary key {1} and SCH is secondary key {2}.
■ On the Parameters tab, PL is tertiary key {3}.
Fitting iParts typically have 1 family key column: nominal size. For the sample
elbow iParts, on the Other tab, NPS is primary key {1}.
The following image illustrates the relationship between iPart family key
columns and part family thumbnail page in the Content Center.
Family key columns play an important role in the file naming schema for part
families in the Content Center. After authoring and publishing, the sequential
combination of hierarchical keys form the value of the pre-defined property
{DESIGNATION} in the Content Center. In this case, {DESIGNATION} is pipe
{NS} {SN} {PL}, in which pipe indicates the conduit part type.
Prepare iParts | 163