Page Comparison

Generating a SysML Product Structure from Teamcenter

1. The object of this tutorial is to generate a block structure in a Rhapsody SysML model from a product structure in Teamcenter. In this exercise, we will continue from the work created in the previous tutorial. An identical tutorial for a Windchill repository is provided in Section 2.3.
2. The package Tutorial_2_05 in the SysML model is empty. Launch the Syndeia dashboard from this package (close it first if it is still open from the previous exercise). Using the Connection Manager on the Syndeia dashboard, as shown in Figure 41 , set the Connection Type to Model Transform and drag the UAV (B;1) item version from the repository side onto the empty SysML package on the left. Click Yes on the dialog box window that appears to confirm (Figure 42).
   

   

   Figure 41 Syndeia dashboard with empty package New_Satellite and Satellite_User PLM part Structure in Teamcenter
   

   Figure 42 Confirmation window

    
3. After the part generation is complete, the Syndeia dashboard should appear as in Figure 43below.
   
    
   Figure 43 Syndeia Dashboard after generation of SysML part structure in Tutorial_2_05
   
   
4. Confirm that Rhapsody displays the same new part structure in the previously empty package Tutorial_2_05. Save the revised SysML model.

...

In general, updating the SysML model from the PLM part structure is the simple inverse of the procedure described in Section 2.4.2: Right-click on the connection or connections to be updated and select Synch Target -> SysML. However, we will consider a more complex scenario where both models have been changed individually and we want to combine the changes. 

Figure 44Rhapsody model has been revised by adding two parts to Body block.
 

1. In Rhapsody, delete the Payload block and add two new blocks, Fuselage and Wings, and use them as parts of the Body block. Figure 44 The figure shows the revised structure. Note that the diagram had to be created by the Rhapsody user; it is not created automatically by either Rhapsody or Syndeia.
2. Using the Syndeia dashboard, delete the existing connection between the Payload item in Teamcenter and the Payload block (now deleted) in the SysML Tutorial_2_05 package. Currently, Syndeia does not automatically remove connections when an element at either end of the connection is deleted, so this must b done manually. Leaving the "orphaned" connector in the model will create problems later during synch.
3. After these changes, the Connection Manager tab in the Syndeia dashboard should look like Figure 45figure below. If we right-click on Tutorial_2_05 in the Connection Browser and select Compare SysML & Target, the Comparison Result tab will look similar to Figure 46the figure below. The differences are (connection and revision IDs may differ in your exercise)
   1. Under C14, the Latest Target has a part pyld:Payload (A;1) that does not appear in SysML.
   2. Under C16, the Body block in SysML has two new parts, fsl:Fuselage and wng:Wings.In this exercise, we wish to update the PLM model changes to the SysML side without overwriting the changes made to the SysML model. If we chose to update from PLM to SysML across all the connections simultaneously (i.e. at the Tutorial_2_05 package level), the result would be to delete the new part properties fsl:Fuselage and wng:Wings on the SysML side, because these parts do not exist on the PLM side. Instead, we will update the SysML model across individual connections.\
      
      

      

      Figure 45 Syndeia dashboard after changes to both SysML and PLM part structures

      

      Figure 46 Syndeia dashboard, Comparison Result tab, after changes to both SysML and PLM part structures

      
      

4. In the Connection Browser tab, on the UAV block row or on the connection C1 row beneath it, right-click and select Sync Target -> SysML.
5. Do a new comparison across all connections. The Comparison Result tab should look like Figure 47the figure below. Note that the mismatch across C1 has been resolved, but the mismatch across C3 has not. The original changes to the SysML have not been pushed over to the PLM side.
   
   

   Figure 47 Syndeia dashboard, Comparison Result tab, after changes to both SysML and PLM part structures
    
   
   

6. To fully harmonize the two models, it would be necessary to push the SysML changes in Body over to the PLM side, syncing SysML -> Target across C3 or across all connections.

...