Generating a SysML Product Structure from Windchill

The object of this tutorial is to generate a block structure in a Rhapsody SysML model from a product structure in Windchill. In this exercise, we will continue from the work created in the previous tutorial.
The package Tutorial_2_03 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, set the Connection Type to Model Transform and drag the UAV (A.4) part from the repository side onto the empty SysML package on the left Click Yes on the dialog box window that appears to confirm.
After the part generation is complete, the Syndeia dashboard should appear.
Confirm that Rhapsody displays the same new part structure in the previously empty package Tutorial_2_03. Save the revised SysML model.
Syncing Windchill Changes to SysML
In general, updating the SysML model from the PLM part structure is the simple inverse of the procedure described in Section 2.2.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.
In Rhapsody, delete the Payload block and add two new blocks, Fuselage and Wings, and use them as parts of the Body block. 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.
Using the Syndeia dashboard, delete the existing connection between the Payload part in Windchill and the Payload block (now deleted) in the SysML Tutorial_2_03 package. 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.
After these changes, the Connection Manager tab in the Syndeia dashboard should look like the figure below. If we right-click on Tutorial_2_03 in the Connection Browser and select Compare SysML & Target, the Comparison Result tab will looks as below. The differences are (connection and revision IDs may differ in your exercise)
1. Under C1, the Latest Target has a part pyld:Payload (A.1) that does not appear in SysML.
2. Under C2, 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_03 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 C1 row beneath it, right-click and select Sync Target → SysML.
Do a new comparison across all connections. The Comparison Result tab should look like below. Note that the mismatch across C1 has been resolved, but the mismatch across C2 has not. The original changes to the SysML have not been pushed over to the PLM side.
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 C2 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.
1. On the Syndeia dashboard, go to the Connection Summary tab.
2. Multiple select all the connections between the elements in the Tutorial_2_03 packages (see the Source column) and PLM repository elements.
3. Right-click and select Delete Connection(s). If the connections are not deleted, they will appear in future Connection Summaries, which may be confusing.

Browser not supported