Creating and managing systems engineering models > Creating a logical model

Creating a logical model

After you define the design requirements and functions, the next step is to create logical models. You can create those in Teamcenter Integration or directly in Mechatronics Concept Designer. In either case it is recommended that you follow a consistent approach to define the logical blocks.

Structure of a logical model

Logical models are organized as a hierarchy:

Broad logical group — defines a general idea of how tasks are completed.
Logical subgroups — have increased specificity on how to accomplish the broad tasks.
Logical units — consist of specific ideas on how to complete a task.

The basic elements of these models are called logical blocks. Logical blocks:

Contain data from multiple disciplines.
Provide a dedicated interface.
Contain sensors and actuators that change and measure physical values.
Include a letter code to indicate the unit's purpose.

Note: The letter codes used in the logical model are based on the IEC 81346 standard.

Example decomposition

Using a simplified factory/robotic-arm example, a logical block decomposition satisfies the following upstream models:

Requirement model — e.g., "Acceptable parts must be packaged together"
Functional model — e.g., "Sort parts"

Example hierarchy shown in the documentation:

Logical
└── Robotic Arm
    ├── Base
    │   ├── Short Arm
    │   │   └── Physical Dimensions
    │   └── Arm Motor
    ├── Long Arm
    │   └── Physical Dimension
    └── Mechatronics
        ├── Base Motor
        ├── Sensors
        └── Power Source

Linking logicals

Logicals can be linked to requirements or to each other, either in Teamcenter Integration or directly in Mechatronics Concept Designer. Refer to the Requirements Manager Guide section of the Teamcenter Help documentation for details on cross-linking logicals to requirements.

Creating a logical model

Structure of a logical model

Example decomposition

Linking logicals

Related documentation