Creating and managing systems engineering models > System Navigator > System Navigator with Teamcenter Integration commands

System Navigator with Teamcenter Integration commands

This is the master reference for the Teamcenter synchronization mechanics exposed through the System Navigator in Mechatronics Concept Designer when running in Teamcenter Integration for Designcenter NX mode. It covers save/refresh at the whole-model level, per-folder open/refresh, cross-model tracelinks (requirement↔function↔logical), and folder-level commands for pushing systems engineering objects down into mechanical, electrical, software, and behavioral (physics) objects.

Main panel commands (whole-session sync)

Right-click in the main panel of the System Navigator:

Command	Description
Save to Teamcenter	Saves the function and logical model to Teamcenter Integration.
Refresh from Teamcenter	Rereads the function and the logical model from Teamcenter Integration.
Properties	Opens the System Navigator Properties dialog box and lets you select which columns are displayed.

Note: these two commands are explicitly scoped to function and logical models (not requirements — requirement sync has its own folder-level Open/Refresh commands below).

Node-level commands (when a node is selected):

Ctrl+C — Copies the node and its children.
Ctrl+V — Pastes a copied node and its children to the selected location in the hierarchy.

Requirements folder commands

Command	Description
Open Requirement Model	In Teamcenter Integration mode, opens a requirement structure from the database.
Refresh Requirement Model	Rereads the requirement model from Teamcenter Integration.

For a child requirement:

Show Requirement Details — Displays the selected requirement's details located in Teamcenter Integration.

For a child requirement (extended set — combines the two shown in source):

Add Existing Requirement — Lets you add an existing requirement from Teamcenter Integration below the selected requirement.
Derive Function — Lets you create a new function which is linked to the selected function/requirement (cross-model derivation).
Show Requirement Details — Displays the selected requirement's details located in Teamcenter Integration.
Start Tracelink — Starts a tracelink on the selected requirement.

Function folder commands

Command	Description
Open Function Model	Opens a function structure from the database.
Refresh Function Model	Rereads the function model from Teamcenter Integration.

For a root function:

Add Existing Function — Lets you add an existing function from Teamcenter Integration below the selected function.
Derive Logical — Lets you create a new logical which is linked to the selected function.
Start Tracelink — Lets you create a new logical which is linked to the selected function (tracelink-initiated derivation).
End Tracelink — Designates the selected function as the target of a tracelink.

Logical folder commands

Command	Description
Open Logical Model	In Teamcenter Integration mode, opens a logical structure from the database. The item type is Logical Block.
Refresh Logical Model	Rereads the logical model from Teamcenter Integration.

For a logical root node:

Add Existing Logical — Lets you add an existing logical from Teamcenter Integration below the selected logical.
End Tracelink — Designates the selected logical as the target of a tracelink.

Cross-model dependent-object commands (Details panel)

These commands create tracelinks between systems engineering object types and are available on child requirement/function/logical nodes:

Folder context	Command	Effect
Available when a child function or logical is selected	Add Dependent Requirement (implied context)	Creates a tracelink between the selected object and a requirement.
Function folder — available when a child function or logical is selected	Add Dependent Function	Creates a tracelink between the selected object and a function.
Logical folder — available when a child requirement or function is selected	Add Dependent Logical	Creates a tracelink between the selected object and a logical.

This trio of "Add Dependent X" commands is the direct mechanism for building the requirement↔function↔logical traceability chain from either side of the relationship (e.g., starting from a function and adding a dependent requirement, or starting from a requirement and adding a dependent logical).

Mechanical folder commands

Command	Availability	Description
Add Component	Only when a logical is selected	Opens the Add Component dialog box; lets you add a loaded component or open an unloaded component to add to the assembly.
Create New Component	—	Opens the New Component File dialog box; creates a new empty component, added to the current assembly and to the Mechanical folder.

Electrical folder commands

Command	Availability	Description
Add New Electrical Part	Only when a logical with Aspect = Product is selected	Opens the Electrical Part dialog box; lets you type in the name of an electrical part. The created part exposes a Place Electrical Part shortcut, which can search the Reuse Library or — when running in Teamcenter Integration mode — browse Teamcenter Integration directly for the part.

Software folder commands

Command	Availability	Description
Add New Operation	Only when a function or logical is selected	Opens the Operation dialog box; creates a new operation.
Add Existing Operation	—	Opens the Add Existing Operation dialog box; lets you select an operation from the graphics window to add to the Software folder.

Behavioral folder commands

Command	Availability	Description
Select Physics	Only when a logical is selected	Lets you select physics objects from the Physics Navigator or graphics window.
Edit	—	Opens the respective dialog box.

Synthesis: the Teamcenter sync model in one picture

Whole-model sync happens at two granularities: Save to Teamcenter / Refresh from Teamcenter (function+logical, main panel) and Open/Refresh Requirement|Function|Logical Model (per-folder, per-model-type).
Item type: logical structures round-trip through Teamcenter as the Logical Block item type — a concrete detail useful for anyone inspecting or scripting against the underlying Teamcenter data model.
No merge/conflict UI is exposed here — the commands are strictly one-directional pulls (Open/Refresh/Add Existing) or one-directional pushes (Save to Teamcenter). There is no separate "resolve conflicts" dialog described for the systems engineering models; conflict handling for concept-vs-detailed geometry replacement is instead covered by the Replacement Assistant (see "Transferring physics definitions from a concept to a detailed model").
Cross-model links (requirement↔function↔logical) are only meaningful/available in Teamcenter Integration mode, using Derive Function, Derive Logical, Start Tracelink/End Tracelink, and the three Add Dependent X commands.
Downstream links (logical→mechanical/electrical/software/behavioral) are populated via the Mechanical/Electrical/Software/Behavioral folder commands shown here, which overlap with (and are the native-command counterpart to) the Dependency-panel-driven tracelink tasks described in "Create a tracelink between a logical and a mechanical part" and "...and a physics object."