Objectives

The new learning objectives of this exercise are to generate a product structure in a Teamcenter repository from a block structure in a Rhapsody SysML model, using the default mapping in Syndeia.

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.zip (Get it here - SysML Models, Profiles and Mappings.). 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.
Caution: Rhapsody has, by default, restrictions on the naming of SysML elements, which can create problems when Syndeia tries to create Rhapsody model elements that violate these restriction, e.g. beginning a SysML block name with a number. We recommend modifying any Rhapsody models you create to relax these restrictions. Modify the properties of the top-level package of the model under General::Model::NamesRegExp with the following string and save.

^(([a-zA-Z0-9_][a-zA-Z0-9_ ():-]*)|(operator.+))$

Exercise

1. Create an empty folder in a Teamcenter repository to which you have access. In this example, it will be Demo 2 in the repository Teamcenter 11.2 AWS @ Intercax Office.
   
   

2. Open the Rhapsody model Syndeia_Tutorial_Testbed.rpy (Get it here - SysML Models, Profiles and Mappings.). Right-click on package Teamcenter_Tutorial Part 1, launch the Syndeia dashboard, and select a Syndeia project if necessary.
   
   

3. Go to the Settings tab. Make sure that the Use mapping checkbox is unchecked. We will work with custom mappings for SysML-to-Teamcenter in later exercises.
   
   

4. Go to the Connection Manager tab. Open the SysML model in the left column and your Teamcenter repository on the right.
   
   

   Open

   

   Figure 1 Syndeia Dashboard, Connection Manager tab
   
   

5. To generate the UAV part structure in the empty folder Demo 2, choose Model Transform as Connection Type in the center column, then drag-and-drop the UAV block from the left panel onto the Demo 2 folder in the right panel. A window will appear as in Figure 2. Click Yes.
   
   

   Open

   

   Figure 2  Syndeia Dashboard, Connection Manager tab
   
   

6. A series of messages will scroll in the bottom section of the dashboard. As shown in Figure 3, the Demo 1 folder on the PLM side now reflects the product structure imported from the SysML model.
   
   

   Figure 3  Syndeia Dashboard, Connection Manager tab, after generation of part structure in the PLM repository
   
   

7. To view the persistent connection that has been created between the UAV block in the SysML model and the UAV part under the Demo 2 PLM folder, click on the Connection Browser tab of the Syndeia Dashboard and expand the UAV block on the left (Figure 4).
   
   

   Figure 4  Syndeia Dashboard, Connection Browser tab, showing the connection between UAV in the two domains
   
   

8. To view all the connections within the Syndeia Cloud project (if Syndeia Cloud is used) or the SysML model (if connection data is stored there), click on the Connection Search tab (Figure 5) of the Syndeia dashboard and click the Get All button. Note that

   1. connections were created between each of the blocks that are used as parts of UAV, e.g. Body, and the corresponding parts created in the PLM product, and
      
      

   2. the connection label assigned by Syndeia and/or the UAV version number may be different in your case.
      
      
      

      Figure 5 Syndeia Dashboard, Connection Search tab, showing all the connections within the Syndeia Cloud project Dirk Sandbox 04