The Connection Manager tab in the Syndeia Dashboard provides an easy-to-use, drag-n-drop interface for creating connections between SysML model elements and repository elements, and generating SysML models from repository models, and vice versa.

The Connection Manager tab has four elements -

The System Model Panel, which displays the SysML element from which the Syndeia Dashboard was launched, and its sub-elements. To select a different element, such as a different package, right click on any SysML element in the System Model Panel and select Go to.
The Connection Type Panel, which displays the available connection types.
The Repository Panel, which displays the repository to which connections can be made. The repository shown can be changed by clicking on the panel title bar.
The Message Panel at the bottom, which displays status and error messages during operation.

The normal operation of the Connection Manager involves the following main steps:

Select a type of connection in the Connection Panel (middle)
Drag and drop a SysML element to a repository element, or vice versa, to create a connection, or generate a model (which also creates connections).

The four main types of connection supported by this version of Syndeia are as follows:

Reference Connection – This is the most basic type of connection between a SysML model element and a repository element. It establishes a traceability link between the two elements.
Function Wrap Connection – This type of connection is used to wrap an external executable model (or code) with a SysML model element, such that when the SysML model element is executed, Syndeia can invoke the external model and bring back execution results to the SysML model for verification. For example, connections between SysML constraint blocks and external MATAB or Mathematica scripts and functions fall into this category.
Data Map Connection – This type of connection is used to map the attributes/properties of a SysML model element with those of a repository element such that Syndeia can compare and bi-directionally sync the property values on-demand. For example, the connection between the value properties of a SysML block and the cells (or entries) in an Excel table row (or MySQL table row) are of this type.
Model Transform Connection – This type of connection is used to map the structure of a SysML model element with that of a repository element such that Syndeia can compare and bi-directionally sync the structure on-demand. For example, the connection between a SysML block to a Windchill / Teamcenter part is an example of this type. The compare operation can show the differences in the structures by comparing the part properties of the SysML block with part BOM in Windchill / Teamcenter, and the bi-directional sync operations can be used to update the part properties of the SysML block or part BOM in Windchill / Teamcenter.

Each connection type has a specific purpose. Syndeia users must decide the purpose of connecting / integrating the SysML model elements with the repository elements, and then pick up a connection type that serves their needs. For guidance, refer to the tutorials in the Tutorials document. Not all types of connections are supported for all types of SysML model elements and repository elements. The tables in sections 4.5.1- 4.5.6 show the specific connection types that are supported for elements in each repository and the drag-n-drop operations to achieve the same. The Syndeia Tutorials provide step-by-step guide for these operations.

Additional Notes for Rhapsody

Rhapsody: Rhapsody 8.0.x does not allow SysML elements with spaces in names by default. Users should modify a property in their project to allow spaces in names on model elements. See the following link from the IBM website on how to do this: http://goo.gl/cvhBSk (short link). Users are requested to change this setting since it may cause issues in generating SysML model elements from other repositories (such as Windchill, Teamcenter, and MySQL) that allow for spaces in model element names.

Browser not supported