Exercise 4.4 - Syncing Windchill to SysML.
Objectives
The new learning objectives of this exercise are to update a block structure in a Rhapsody SysML model from a product structure in Windchill. We execute a more complex scenario than Exercise 4.2, where both models have been changed individually and we want to combine the changes.
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 Windchill interface, correctly installed with a valid license for user.
A Windchill repository network connection in the Syndeia Repository Manager
The specific instructions in this example use a Windchill repository connection named Windchill 11.1 @ Intercax, but the user can use any Windchill repository 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 this exercise, we will continue from the work created in Exercise 4.3.
In Rhapsody, delete the Payload block and the pyld.Payload part property of UAV and add two new blocks, Fuselage and Wings, and use them as parts of the Body block. Figure 1 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.
Figure 1Â SysML model, revised by adding two parts to Body block, removing pyld.Payload part.
Using the Syndeia dashboard, delete the existing connection between the Payload part in Windchill and the Payload block (now deleted) in the SysML Windchill_Tutorial Part 2 package. In the Connection Search tab (Figure 2, refresh the list by clicking Get All, right-click the row for the connection to be deleted, select Delete and confirm deletion. Currently, 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 synch.
Figure 2 Deleting the Payload block – Payload part connection
After these changes, the Connection Manager tab in the Syndeia dashboard should look like Figure 3. If we right-click on Windchill_Tutorial Part 2 in the Connection Browser and select Compare Source & Target, the Comparison Result tab will look similar to Figure 4. The differences are (connection and revision IDs may differ in your exercise)
Under DZSB04-R94, the Latest Target has a part pyld:Payload (A.1) that does not appear in SysML.
Under DZSB04-R95, the Body block in SysML has two new parts, fsl:Fuselage and wng:Wings.
Figure 3Â Syndeia dashboard after changes to both SysML and PLM part structures
Figure 4Â Syndeia dashboard, Comparison Result tab, after changes to SysML & PLM part structures
In this exercise, we wish to update the PLM model content, specifically the Payload part, 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 Windchill_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 SysML model across individual connections.
In the Connection Browser tab, on the UAV block row or on the connection DZSB04-R94 row beneath it, right-click and select Sync Target -> Source.
Do a new comparison across all connections. The Comparison Result tab should look like Figure 5. Note that the mismatch across DZSB04-R94 has been resolved, but the mismatch across DZSB04-R95 has not. The original changes to the SysML have not been pushed over to the PLM side.
Figure 5Â Syndeia dashboard, Comparison Result tab, after changes to both SysML and PLM part structures
To fully harmonize the two models, it would be necessary to push the SysML changes in Body over to the PLM side, syncing Source -> Target across DZSB04-R95 or across all connections.
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.
On the Syndeia dashboard, go to the Connection Search tab. Click Get All to see all the Syndeia connections in the current project.
Multiple-select all the connections between the elements in the Windchill_Tutorial Part 1 and Windchill_Tutorial Part 2 packages (see the Source column) and PLM repository elements.
Right-click and select Delete Connection(s).
Â