Creating and managing systems engineering models > Systems engineering models overview > Systems engineering models workflow

Systems engineering models workflow

The systems engineering models workflow spans multiple engineering disciplines and documents the relationships involved in requirements management, functional design, logical modeling, and traceability for a machine concept. Several roles concurrently work together to develop the models.

Note: this file focuses on the logical modeling portion of the workflow and how it hands off into MCD's physical/concept model; requirement- and function-specific workflow detail is covered separately.

The workflow steps

1. Develop requirements

Gather and structure the main design and system requirements.
Add subrequirements based on the main requirements.
Add more details to the requirements using embedded tools like Microsoft Word.

2. Develop a functional model

Define basic functions of the system.
Create a hierarchy based on a functional decomposition.
Create and maintain alternatives for the functional design.
Reuse functional units.
Define the output parameters of the functions and associate them with requirements.

3. Develop a logical model

Create the basic logical model to define how functional blocks are accomplished.
Create a hierarchy based on a logical decomposition.
Reuse logical blocks.
Define the parameters of the logical blocks and associate them with functions.

4. Create tracelinks

Create tracelinks to show the dependencies between functional units and the logical blocks. To create tracelinks:

Select a root systems engineering object.
Link sub-objects to root objects to connect the driving factors of the root object.

Where the systems engineering models go next

Once developed, the systems engineering models are imported to MCD and used to design the physical model. This is the single-sentence summary of the entire requirement/function/logical → concept model pipeline: the SE models (whether authored in Teamcenter or natively) feed forward into the physical/concept design phase of Mechatronics Concept Designer, which is where logical-to-mechanical/electrical/behavioral tracelinks (see "Mapping logical blocks to physical/concept model objects") take over.