...

1. The object of this tutorial is to generate a product structure in a Teamcenter repository from a block structure in a Rhapsody SysML model. We will use the sample model Syndeia Tutorial Testbed. An identical tutorial for a Windchill repository is provided in Section 2.2in SysML Block Structure → Windchill.
    
2. Create an empty product in a Teamcenter repository to which you have access. In this example, it will be UAV-Demo in the repository Tc-newuav. (It is outside the scope of this tutorial to describe how to use the PLM tools, but in Teamcenter, it is necessary to open an interface to your Teamcenter repository and go to File→New→Folder. Appendix 1 provides a more detailed description of working directly in Teamcenter repositories.)
    

3. Open the Rhapsody model Syndeia Tutorial Testbed. Right-click on package Tutorial_2_04, launch the Syndeia dashboard, and click on the Connection Manager tab. Click on Repository at the top of the right panel and select the Tc-newuav repository. The dashboard should appear as in Figure 8. The left panel shows the SysML model element. The right panel shows the contents of the Teamcenter repository Tc-newuav.
   
   

    

4. To generate the UAV part structure in the empty product UAV_Demo, choose Model Tranform as Connection Type in the center of the dashboard, then drag-and-drop the UAV block from the left panel onto the UAV_Demo product in the right panel. A window will appear as in Figure 9. Click Yes.
   
   
   

   Figure 29Syndeia Dashboard, Connection Manager tab

    

5. A series of messages will scroll in the bottom section of the dashboard. As shown in Figure 10, the UAV_Demo product on the PLM side now reflects the product structure imported from the SysML model.
   
   
   
   

6. To view the persistent connection that has been created between the UAV block in the SysML model and the UAV part under the UAV_Demo PLM product, click on the Connection Browser tab of the Syndeia Dashboard and expand the UAV block on the left. Note the connection in Figure 11 below; the connection label (C2) assigned by Syndeia and/or the UAV version number (A;1) may be different in your case.
   
   
   

   Figure 31Syndeia Dashboard, Connection Browser tab, showing the connection between SatelliteSystem inthe two domains

    

7. To view all the connections to elements in the Tutorial_2_04 SysML model, click on the Connection Summary tab (Figure 12) of the Syndeia Dashboard and click the Refresh button on the upper right. Note that connections were created between all of the blocks that are used as parts of UAV, e.g. Body, and the corresponding parts created in the PLM product.

...

Syncing SysML Changes to Teamcenter

Figure 33 Modified UAV SysML model

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.
   
   
   

   Figure 34Syndeia dashboard, Connection Manager tab, after modifying SysML model, before updating PLM repository

   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.

   Figure 35Syndeia dashboard, Connection Browser tab, after modifying SysML model, before updating PLM repository. Filter function is highlighted in red.

    

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. 
   
   
   

   Figure 36 Launching comparison

   
   

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.
   
   

   Figure 37Syndeia dashboard, Comparison result tab, after modifying SysML model, before updating PLM repository.

    

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.
   
    
   

   Figure 38 Connection Manager after syncing

   
   
   

    Figure 39 Connection Browser after syncing
   
   

   

   Figure 40 Comparison Result after syncing

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), as shown in Figure 38. 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), as shown in Figure 39.

The same updating result would have been achieved if we had synced the UAV block across connection C2 (Figure 35). By syncing across the Tutorial_2_04 package, we synced simultaneously across all 3 connections held by blocks in that package.

...