User Tools

Site Tools


This is an old revision of the document!

Work on following article or section is in progress

Defining and Working with Partial Systems

KBLFRM-682 Fig. ##: ComponentNodeTypes

Sometimes there is the situation that concrete target components are unknown (or not yet defined) or different (topic specific) parts of a system schematic are developed independently as partial systems (e.g. vehicle infrastructure like power, ground or bus systems). In these cases more than one schematic plan exists like the “blue” and the “red” one, which are shown in the example in figure ##.

For theses situations the enumeration ComponentNodeType contains the specific value “OpenLink” (figure ##).
In the diagram in figure ## you can see the corresponding model to the “blue” system schematic from the plan. Each component is represented by a ComponentNode with it's slots and pins underneath which are represented by the ComponentConnector and the ComponentPort class. In addition to that the component M.31 is also shown in the diagram even though it is not existing on the blue plan.

Fig. ##: System Schematic

As you can see the ComponentNode is marked with the node type “OpenLink” to clarify that this component is NOT part of the system schematic but components from the plan DO HAVE a connection to it. In the example below the pin A1 from the component E1.1 is connected to M.31 → A1. This is also the reason why there is a Connection with its ConnectionEnds shown in the diagram.

Caution: When merging the definition of these partial systems together into one vehicle system, it is mandatory to resolve these open links and replace them by determined ComponentNode elements. It is also possible to reference the concerning ComponentPort by a Connection/ConnectionEnd even though it is not part of the same DocumentVersion

Fig. ##: System Schematic Diagram

tutorials/vec/working_with_partial_systems.1558344146.txt.gz · Last modified: 2019/05/20 11:22 by 4soft.fehlmann