If you select a Teamcenter repository in the Repository Tree Panel (LHS), you can see the contents of that repository in the Repository Content Panel (RHS). This content information is lazily loaded—every time you expand a node, a request is made to the Teamcenter server for information, and the results are displayed. Users can view a wide range of product information in Teamcenter, as also shown below.

The top-level node displayed for a Teamcenter repository in the Syndeia Dashboard is the Home Folder If there is any content in the repository that is not in the home folder, users are requested to create a link to it in the home folder (via search-copy-paste) in the Teamcenter rich client (or web client), and then it will be visible in the home folder in the Syndeia Dashboard (after refresh). Creating a link does not copy the item but only creates a reference to it in Teamcenter. of the user. Under the home folder, users can see sub-folders, and other major types of Teamcenter objects in any folder, such as: Items (and Item Revisions), Parts (and Part Revisions), Requirement Specs (and Requirement Spec Revisions), Requirements (and Requirement Revisions), Paragraphs (and Paragraph Revisions), and Trace Links (both direct and indirect). Since Item is the parent type for most Teamcenter model objects, users can see all those objects and their revisions.

For any Item, including special types such as Part, Requirement, Requirement Spec, and Paragraph, users can see all the Item Revisions (and their equivalent sub-types), as shown for the Unmanned Aerial Vehicle item (id 000464) in its revisions A.1, B.1, and C.2. For a given Item Revision and its sub-types (such as Requirement Spec Revision and Requirement Revision), users can see its structure, also known as the bill-of-materials (BOM). This includes both Precise and Imprecise BOMs. For example, the BOM for Item Revision 000464-Unmanned Aerial Vehicle version C.2 is shown in the figure and includes multiple BOM lines, such as aircraft, gps, and autopilot. The BOM lines are shown using in the refdes: Item Revision format. Similarly, the structure of requirement spec revision 001230-Fire UAV Specification version A.3 is also shown in the figure.

In addition to the structure, the Syndeia Dashboard also shows both Direct and Indirect Trace Links starting or ending on a given item revision (or its subtypes). For example, the item revision Unmanned Aerial Vehicle item (id 000464) revision C.2 has a trace link to the requirement specification Fire UAV Specification.

Viewing NX models managed in Teamcenter
When an item is expanded, you can view all the item revisions for that item. For a given item revision, you can also view all the associated datasets. For a given dataset, you can see all the files (ImanFile objects). If the dataset is of type UGMASTER—datasets for storing CAD model files—and contains NX prt file, you can expand the prt file object in the Syndeia Dashboard and view the part model. For example, the toycar_assy/A;1 item revision contains the toycar_assy-A dataset which contains the toycar_assy_A.prt file (NX CAD file). When the prt file is expanded, Syndeia initializes a NX session, if it not already initialized, and connects that NX session to Teamcenter and loads the NX part model in the session. This can take some time (few seconds to a minute) depending on speed on initializing NX session on your machine and connecting it to Teamcenter.

When a NX file (.prt) is expanded, Syndeia initializes a NX session and starts communicating with the NX part model in the .prt file. The first element seen under the NX part file (.prt) is the NX part object if the part is a piece part, or the root component of the part assembly if the part is an assembly. In the latter case, if the root component is expanded, you can see sub-components which can be expanded further. The first element seen under the NX part file (.prt) is the NX part object if the part is a piece part, or the root component of the part assembly if the part is an assembly. In the latter case, if the root component is expanded, you can see sub-components which can be expanded further.

Browser not supported