Objectives

The new learning objectives of this exercise are to update names and part structures from the SysML model to the PLM repository.

Preparation

This exercise assumes the student has

Cameo System Modeler 18.0 - 19.0 (or MagicDraw with SysML plug-in) installed correctly on his or her machine with a valid license for use, and
Syndeia 3.4 installed as a plugin for Cameo/MagicDraw with a valid license for use
Syndeia Teamcenter interface, correctly installed with a valid license for user.
A Teamcenter repository network connection in the Syndeia Repository Manager
Completed Exercise 11.1 to create a UAV PLM part structure in Teamcenter

The user can use any Teamcenter repository network connection they have available. It is generally advisable to carry out these exercises in a non-production repository, a "sandbox", set up for training and practice purposes.

Exercise

In this exercise, we will continue with the models from Exercise 11.1, adding an additional block to the SysML model, Payload, and using it as a part of UAV. The resulting SysML model BDD looks like Figure 1.

Figure 1 Modified UAV SysML model
In the Syndeia Settings tab, scroll down to Teamcenter settings and check Revise items when updating. This affects the designation of Teamcenter items after revision.
Refresh the Syndeia dashboard Connection Manager by right-clicking the Teamcenter_Tutorial Part 1 package on the left side and choosing Refresh. It will appear similar to Figure 2

Figure 2 Syndeia dashboard, Connection Manager tab, after modifying SysML model, before updating PLM repository
The corresponding Connection Browser tab appears as in Figure 3. For this screenshot, we (1) right-clicked on the Teamcenter_Tutorial Part 1 package (top row) and selected Refresh, then Expand All, and (2) filtered the Key column by clicking on the downward arrow icon in the column header, selecting (Custom…), and choosing "is not empty" criterion. This reduces the number of empty rows displayed.

Figure 3 Syndeia dashboard, Connection Browser tab, after modifying SysML model, before updating PLM repository. The red highlight shows the filter options arrow for the Key column.
Use the Comparison Manager to display the current differences between the two models. Right-click on the Teamcenter_Tutorial Part 1 package and choose Compare Source & Target, as shown in Figure 4.

Figure 4 Launching comparison
The Comparison Result tab will be displayed, as in Figure 5. Note that the row shown in red represents the new part property of UAV that has no corresponding element on the PLM side. Note that the new block, Payload, does not appear as a separate element in the table, because it does not have an existing connection to a PLM object to compare against.

Figure 5 Syndeia dashboard, Comparison result tab, after modifying SysML model, before updating PLM repository
To update the PLM model from the revised SysML model, right-click on the Teamcenter_Tutorial Part 1 package and select Sync Source → Target. The results of this operation are shown for the Connection Manager (Figure 6), Connection Search (Figure 7), and Comparison Result (Figure 8) tabs after syncing. It may be necessary to refresh each display. For the Comparison Result, you will need to perform Compare Source and Target again to check that everything is in-sync, as shown in Figure 8.

Figure 6 Connection Manager after syncing
Note that the version of the UAV part in Teamcenter has changed from A.1 to B.1 (since a new part occurrence has been added and the Settings in Step 2 were set to Revise item when updating), as shown in Figure 6. The connection between the UAV block in SysML and the UAV part in Teamcenter, DZSB01-R122, is now in version 2, as shown in Figure 7, and points to this new revision (B.1).
Figure 7 Connection Search after syncing
Note also that a new Teamcenter item, 002305-Payload, has been created, but it was not created inside the Demo 1 folder. It was created in the Home folder and would need to be moved manually into the Demo 1 folder if that was desired for housekeeping purposes.
Figure 8 Comparison Result after syncing
The same updating result would have been achieved if we had synced the UAV block across connection DZSB01-R122 (Figure 3). By syncing across the Teamcenter_Tutorial Part 1 package, we synced simultaneously across all 3 connections held by blocks in that package. If we had updated in the opposite direction, PLM to SysML, the result would have been different. The part property pyld would have been deleted from the UAV block, although the Payload block would not have been affected.