Syncing SysML Changes to Teamcenter.


  1. 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, Payload, to the SysML model and using it as a part of the UAV. The resulting SysML model BDD looks like Figure 33.
  2. Refresh the Syndeia dashboard by right-clicking the Tutorial_2_04 package on the left side and choosing Refresh. It will appear similar to Figure 14.

    The corresponding Connection Browser tab appears as in Figure 35. For this screenshot, we (1) right-clicked on the Tutorial_2_04 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.

  3. Use the Comparison Manager to display the current differences between the two models. Right-click on the Tutorial_2_04 package and choose Compare SysML & Target, as shown in Figure 36. 

  4. The Comparison Result tab will be displayed, as in Figure 37. 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.

  5. To update the PLM model from the revised SysML model, right-click on the Tutorial_2_04 package and select Sync SysML → Target. The results of this operation are shown for the Connection Manager (Figure 38), Connection Browser (Figure 39), and Comparison Result (Figure 40) 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 in Figure 40.

     




Note that the version of the UAV part in Teamcenter has changed from A;1 to B;1 (since 2 new part occurrences have been added). The connection between the UAV block in SysML and the UAV part in Teamcenter has been updated to point to this new revision (B;1).

The same updating result would have been achieved if we had synced the UAV block across connection C2. By syncing across the Tutorial_2_04 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.

Delete all connections and close the Syndeia dashboard when the exercise is completed. If the connections are not deleted, they will appear in future Connection Summaries, which may be confusing.