SysML Block Structure → Teamcenter
Generating a Teamcenter Product Structure from SysML
...
Figure 33 Syndeia Dashboard, Connection Summary tab, showing all the connections owned by the Tutorial_2_04 SysML package.
Syncing SysML Changes to Teamcenter
...
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 34.
Figure 34 Modified UAV SysML model
...
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 37.
...
Figure 38 Syndeia dashboard, Comparison result tab, after modifying SysML model, before updating PLM repository.
...
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 39), Connection Browser (Figure 40), and Comparison Result (Figure 41) 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 41.
Note that the version of the UAV part in Teamcenter has changed from A;1to B;1 (since 2 new part occurrences have been added), as shown in Figure 39. 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 40.
The same updating result would have been achieved if we had synced the UAV block across connection C12 (Figure 36). By syncing across the Tutorial_2_04 package, we synced simultaneously across all 3 connections held by blocks in that package.
If we had updated in the opposite direction, PLM to SysML, the result would have been different. The part property pyld would have been deleted from the UAV block, although the Payload block would not have been affected.
...
Figure 39 Connection Manager after syncing
Figure 40 Connection Browser after syncing
Figure 41 Comparison Result after syncing
SysML Requirements Structure → Teamcenter
Syndeia allows requirements to be generated, compared and synchronized bidirectionally between MagicDraw and Teamcenter. Exchange is complicated by the different approaches to requirements hierarchies in the two tools.
Generating Teamcenter Requirements from SysML
...
- In the MagicDraw menu bar, select Option→Project and choose General Project Options.
- Scroll down to the Numbering section and uncheck Use Element Auto-numbering.
- MagicDraw requires that this setting be made for each individual project. It cannot be set as default for all projects.
- Without this setting, MagicDraw will tend to renumber the Teamcenter requirements whenever the two models are connected, which may not be desirable for the user.
...
Syncing Requirements from SysML to Teamcenter
Syndeia is able to compare and sync requirements across existing connections.
Figure 99 Compare Requirements
...
Dependencies from SysML to Teamcenter
Syndeia is able to generate, compare and sync dependencies between SysML and Teamcenter. In SysML, dependencies include <<satisfy>>, <<trace>>, <<verify>>, <<allocate>> and other relationships that are dependencies with additional stereotypes attached. In Teamcenter, dependencies take the form of Trace Links, which do not differentiate between different types of SysML dependencies.
...
Figure 101 SysML Requirements diagram showing dependencies
...
Teamcenter Product Structure → SysML
Generating a SysML Product Structure from Teamcenter
...
The object of this tutorial is to generate a block structure in a MagicDraw 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 here.
...
Figure 43 Confirmation window
...
Confirm that MagicDraw displays the same new part structure in the previously empty package Tutorial_2_05. Save the revised SysML model.
Syncing Teamcenter 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.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 45 MagicDraw model has been revised by adding two parts to Body block.
...
- In the Connection Browser tab, on the UAV block row or on the connection C14 row beneath it, right-click and select Sync Target -> SysML.
...
Figure 48 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 SysML -> Target across C16 or across all connections.
Teamcenter Requirements Structure → SysML
The reverse process from Section 2.11, generating requirements in MagicDraw from the Teamcenter repository, is very similar, including the features of comparing and synching. Exchange is complicated by the different approaches to requirements hierarchies in the two tools.
Generating SysML Requirements from Teamcenter
...
Teamcenter, unlike SysML, allows a requirement to be owned by more than one other requirement or requirement specification. Therefore, a Teamcenter requirement can exist as both an independent requirement and as an "owned" requirement. No corresponding structure is available in SysML, so the "owned" Teamcenter requirement is represented by a SysML requirement that is a <<copy>> of an independent requirement. In Figure 108, this relationship appears three times, for Engine Specification, Max Power, and Efficiency.
Figure 108 SysML model showing transferred requirements structureThis tutorial lists the sysML - Teamcenter capabilities
| Page Tree | ||
|---|---|---|
|