Currently, Syndeia supports updating of names and part structures from the SysML model to the PLM repository (and in reverse). Additional capabilities will be added in the future. In this exercise, we will continue with the models from the last section, adding an additional block to the SysML model, Payload, and using it as a part of the UAV.
Refresh the Syndeia dashboard by right-clicking the Tutorial_2_02 package on the left side and choosing Refresh.

The corresponding Connection Browser tab appears. For this screenshot, we (1) right-clicked on the Tutorial_2_02 package (top row) and selected Expand All, and (2) filtered the Connection 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.
Use the Comparison Manager to display the current differences between the two models. Right-click on the Tutorial_2_02 package and choose Compare SysML & Target.
The Comparison Result tab will be displayed. 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 in the table, because it does not have an existing connection to a PLM object to compare against.
To update the PLM model from the revised SysML model, right-click on the Tutorial_2_02 package and select Sync SysML → Target. The results of this operation are shown for the Connection Manager, Connection Browser, and Comparison Result tabs after syncing. It may be necessary to refresh each display. For the Comparison Result, you will need to perform the comparison again to check that everything is in-sync, as shown.

Note that the version of the UAV part in Windchill has changed from A.3 to A.4 (since 1 new part occurrence has been added). The connection between the UAV block in SysML and the UAV part in Windchill has been updated to point to this new revision (A.4), as shown.

The same updating result would have been achieved if we had synced the UAV block across connection C16. By syncing across the Tutorial_2_02 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.
Before we proceed to the next section, we will practice deleting connections between the PLM and SysML models. This is not necessary when we complete an exercise, but can be a useful way to prevent obsolete or unneeded connections from littering up the model.

1. On the Syndeia dashboard, go to the Connection Summary tab.
2. Multiple select all the connections between the elements in the Tutorial_2_02 packages (see the Source column) and PLM repository elements.
3. Right-click and select Delete Connection(s). If the connections are not deleted, they will appear in future Connection Summaries, which may be confusing.

Browser not supported