Product structure elements

The following elements may be included in a product structure that you manage in Structure Manager.

Note The terms component, line, and occurrence are used commonly. All these terms refer to the single-level link between an assembly and a component. Information typically associated with the link includes find numbers and notes for assembly (such as torque setting and lubrication notes). Data used for configuration may also be stored on an occurrence (for example, variant condition). Element Purpose Aggregate occurrence A single occurrence representing multiple usages of the same component item by setting the quantity attribute. Use an aggregate occurrence where separate occurrences are not required to distinguish individual usages (for example, rivets). Assembly A single-level assembly with no hierarchy, as distinct from a multilevel product structure. Assembly data is stored in a BOM view revision. BOM view revision A workspace object that stores the single-level assembly structure of an item revision, that is, occurrences. Access may be controlled on the structure (BOM view revision) independently of other data. BOM view revisions are only meaningful in the context of the item revisions for which they are created. Component A node in a structure—a child in a single-level parent-child relationship. When you add components, you create an occurrence for each component added. Contrast with instance—a child in a multilevel parent-child relationship.

Note Do not confuse a component in Teamcenter with a component in NX. In Teamcenter, a component is a single-level assembly-child relationship (a relative occurrence). Configuration rule A rule that configures the structure. There are two kinds of configuration rules: revision rules and variant rules. Custom note Provides additional information about an item or item revision. A custom note contains unique information about the part or document. Compare with standard note. DirectModel dataset A dataset containing a JT (visualization) file. Files of this format can be generated by NX and other applications. Default view type Teamcenter applies a default global view type where possible, for example, when opening an item revision. Use of a default view type avoids the need for a user to choose between multiple views. The default view type is set by the PSE_default_view_type preference. Design The CAD design solution that implements a business part. Each part may be implemented by one or more CAD designs. Likewise, a CAD design may implement more than one part. Certain parts do not require a design solution, for example, paint and glue. Find number A number that identifies individual occurrences (or groups of occurrences) within a single-level assembly. Components are ordered by find number within an assembly.

Note By default, occurrences are populated with numeric find numbers. However, they may contain any text string. Teamcenter ignores nonnumeric values when ordering components in the assembly. Line A line in the product structure and all the attributes associated with it. A line represents a single occurrence in the structure. When you click a line, you select all the properties associated with the line, including both occurrence and item properties.

Note In Structure Manager, you can edit appropriate properties of the selected line, for example, the item revision or note.

Note (occurrence note) Assembly related textual data that is associated with an occurrence. Contrast with standard note and custom note.

Note type (occurrence note) The system administrator creates different occurrence note types. Users can then specify values for the different note types where required. Occurrence (Sometimes called relative occurrence.) A hierarchical structure relationship between the immediate parent assembly and its child component item (in an imprecise assembly) or item revision (in a precise assembly). You can use a find number to identify an occurrence, but this number may not be unique. Data can be stored on the occurrence, including occurrence notes and transforms. Part A business object that is represented by an item in the product structure. Each part may have one or more CAD designs associated with it. The part is managed by the company's part releasing system; it is typically revised and releases separately from the associated design. Piece part A part with no structure (no associated BOM view revision). This is sometimes referred to as a detail part. Product structure The whole multilevel product structure, as distinct from a single-level assembly (which is sometimes referred to as a BOM view revision or BVR). Standard note Provides additional information about an item or item revision. A standard note typically contains information provided by a standards organization and can be attached to multiple parts or documents. Compare with custom note. Substitute A particular occurrence may have substitute components that are interchangeable for that specific occurrence. One is the preferred substitute, and Teamcenter shows it in the structure. If these substitute parts are intended as manufacturing substitutes, you can manufacture an assembly using any of the substitutes. View type An attribute of a BOM view revision that specifies its intended usage, for example, design or manufacture. The administrator may define any number of view types. A chain of BOM view revisions of the same type are anchored by a BOM view of the corresponding view type. An item revision may contain only one BOM view revision for each view type. The view type distinguishes one BOM view revision from another BOM view revision of the same item revision.