NX/Structure Manager Linkup

Teamcenter Integration enables you to use NX assemblies and the Teamcenter Structure Manager together, to edit a single product structure database.
Teamcenter Integration does this by keeping the NX internal data structures synchronized with the Teamcenter database. The Teamcenter product
structure data is considered to be the master.
You can edit this single product structure from either NX or Teamcenter Structure Manager.

Benefits
The benefits of using this facility include:

Access to the Where Used function for NX assemblies.

Availability of bill of materials information within the database without having to use NX to view or edit it, so reports or interfaces to other systems (for
example, MRP) can be built.

Note Be careful when editing in both NX and Structure Manager simultaneously. We recommend that you edit from one application, save and close,
then edit from the other application as normal practice. This avoids possible confusion about which edits have been saved and propagated into
current sessions of the other tool.

The NX data structures, which can be kept synchronized with the database, are the components (instances) and the Parts List entries in part files. By
default, components in the Structure Manager bill, which have quantity 1 and no Default Unit Of Measure (UOM), appear as components in the NX
assembly and others appear only in Parts Lists.

Note This is only done for master part files since Teamcenter does not maintain this data for non-master part files.

The NX/Teamcenter Linkup figure (later in this topic) illustrates the linkup between Teamcenter components, NX components and the NX Parts List.
Refer to it when reading the sections discussing how these three behave in conjunction with each other.

Defaults and Preferences

There are three NX customer defaults that affect the action of the functions described in this topic:

Structure Update On Load

Structure Update On Save
Callout Management

There is also an Teamcenter preference for the selective load function that may be placed in your user, group or site preference file:

IMAN_show_open_in_ug_button
When viewing items in Structure Manager, the following Teamcenter preference assigns the same Find No. to an item that has the same ID as one that
already exists in the BOMView. If the ID is diffferent, the item is given a new Find No.

PS_new_seqno_mode=existing

The synchronization actions are carried out at various points in the NX session as follows:

NX Session Action
During the load The NX part file data structures are updated to reflect edits made to the Teamcenter product
structure since it was last loaded by NX.
During the save The Teamcenter product structure is updated to reflect product structure and attribute edits made
in the part file during the current session.
While editing the Parts List and attributes The Teamcenter product structure is examined and if updates made are likely not to be
compatible with the database, warning messages are given.
Positioning new components New components that are noted as having been added in the Teamcenter product structure, are
marked as having been positioned.

The actions in the first three situations are described further in this topic.

Terminology
There are a number of terms that are used in different ways in Teamcenter and NX. The following is a list of potentially confusing terms and a short
description of each of their meanings within this topic:

Component - a single-level usage of one part within another. (In NX this is called a component and in Teamcenter an occurrence.)
Packed - display option to allow multiple components to be shown as one line in the Structure Manager BOM.
Aggregate - a component in Structure Manager that has non-unit quantity or whose child part has units of measure.
BomView Revision - the single level bill of materials for an item revision in Teamcenter.

NX and Teamcenter Component Properties

There are a number of properties of NX components that appear also as properties of Teamcenter components. These are:

Reference Set - This can be set by the user in NX as normal. If the note type UG REF SET is defined in the Teamcenter database, then it is filled
when saved with the current reference set name for each component. If this is edited in Teamcenter, then the reference set changes for the NX
component as part of the update next time the part is loaded. If the new value of the note does not match any reference set, the reference set does
not change and a warning is displayed. The check is case-independent.
Transform - Each component has a transform that may be a result of evaluating a mating condition. This is written to the transform field on the
corresponding Teamcenter component. This cannot be edited from Teamcenter Structure Manager.
Component Name - The NX component name is synchronized with Teamcenter Structure Manager and can be edited with either one.

1 од 2
 The component name in NX is identified in the Component Properties dialog box. The name is defined in the Name box on the General tab
and is snychronized to the Structure Manager. After changing the name in the Name box, click Apply Name to All Occurrences in the Actions
group to apply the name to the NX instance.
The component name in Structure Manager is a note whose type is UG NAME (case-independent match) as there is no component name
concept supported directly by Structure Manager. If this is defined in the Teamcenter database, it is used; otherwise, no synchronization takes
place.

© 2017 Siemens Product Lifecycle Management Software Inc.

2 од 2