Objectives
The new learning objectives of this exercise are to update a block structure in a Rhapsody SysML model and a product structure in Teamcenter. We execute a more complex scenario than Exercise 11.2, where changes to both models must be preserved.
Preparation
This exercise assumes the student has
IBM Rational Rhapsody 8.2 installed correctly on his or her machine with a valid license for use, and
Syndeia 3.3 installed as a plugin for Rhapsody 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
We will use the provided Rhapsody project Syndeia_Tutorial_Testbed.rpy. The specific instructions call for a Teamcenter network connection named Teamcenter 11.2 AWS @ Intercax Office, but 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 the Rhapsody model, delete the Payload block and the part property pyld:Payload in the Teamcenter_Tutorial Part 2 package and add two new blocks, Fuselage and Wings, use them as part properties of the Body block. Figure 1 shows the revised structure. Note that this diagram had to be created by the Rhapsody user; it is not created automatically by either Rhapsody or Syndeia.
Figure 1 Rhapsody model has been revised by adding two parts to Body block.
Using the Connection Search tab, delete the existing connection between the Payload part in Windchill and the Payload block (now deleted) in the SysML Teamcenter_Tutorial Part 2 package (Figure 2). Syndeia does not automatically remove connections when an element at either end of the connection is deleted, so this must be done manually. Leaving the "orphaned" connector in the model will create problems later during sync.
Figure 2 Deleting connection from Payload block in MagicDraw Teamcenter_Tutorial Part 2 package
After these changes, refresh the Teamcenter_Tutorial Part 2 package in the Connection Manager tab and it should look like Figure 3.
Figure 3 Syndeia dashboard after changes to both SysML and PLM part structures
Right-click on Teamcenter_Tutorial Part 2 in the Connection Browser and select Compare Source and Target. The Comparison Result tab will look similar to Figure 4. The differences are (revision IDs may differ in your exercise)
the Latest Target has a part pyld:Payload (A.1) that does not appear in SysML.
the Body block in SysML has two new parts, fsl:Fuselage and wng:Wings.
Figure 4 Syndeia dashboard, Comparison Result tab, after changes to SysML & PLM part structures
In this exercise, we wish to preserve the PLM model change made in Exercise 11.2 (the Payload item) and push it back to the SysML side, without overwriting the changes made to the SysML model (the Wing and Fuselage blocks). If we chose to update from PLM to SysML across all the connections simultaneously (i.e. at the Teamcenter_Tutorial Part 2 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 PLM model selectively across the individual Body connection, then update the SysML model from Teamcenter using the UAV connection.
Under the Connection Browser tab, right-click the Body block row or the connection beneath it and select Sync Source -> Target.
Do a new comparison across all connections (i.e. on the Teamcenter_Tutorial Part 2 package row in the Connection Browser). The Comparison Result tab should look like Figure 5. Note that the differences between the Body blocks has been resolved and Wings and Fuselage now appear in the Teamcenter model, but the difference in UAV parts has not.
Figure 5 Syndeia dashboard, Comparison Result tab, after updates to PLM part structure
Under the Connection Browser tab, right-click the UAV block row or the connection beneath it and select Sync Target -> Source.
Do a new comparison across all connections (i.e. on the Teamcenter_Tutorial Part 2 package row in the Connection Browser). The Comparison Result tab should look like Figure 6. The Payload block and part property (of UAV) have been restored and the SysML and PLM models are reconciled.
Figure 6 Syndeia dashboard, Comparison Result tab, after update to SysML part structure
Close the Syndeia dashboard.