MBSE Reference · Tools, Abstraction & the Digital Thread

A Map of the Engineering Landscape

People mislabel MBSE tools — calling Cameo a “requirements management tool,” for example — because they blur three separate questions into one. Keep the questions apart and the confusion dissolves.

1
What level of abstraction?
Requirements → Functional → Logical → Physical
2
What engineering domain?
System · Electrical · Software · Fluid · Mechanical
3
Who is the system of record?
One record — Teamcenter (Requirements + PLM as one)

▸A tool is a region of this map — not a discipline. Each one is a where you author; Teamcenter is the single where it’s governed.

Abstraction ↓  ×  Domain →
System of record — Teamcenter SysML authoring — Cameo + Electrical — Capital Fluid & Mechanical — NX Software — ALM
Teamcenter One system of record · Requirements + PLM
R

Requirements · managed record · all domains

Teamcenter Requirements

The requirements system of record — IDs, baselines, attributes, verification method (T/A/I/D) and coverage across every domain. Textual + parametric (L1–L8).

IDsBaselinesVerificationCoverage
F
Functional
What it does

Functional layer · all domains

SysML Authoring

Multi-domain functions, functional flows and requirement allocation. Traces up to requirements, down to logical. Aligns to system-engineering standards (e.g. ARP4754A).

Tools: Cameo · IBM Rhapsody · Sparx EA · Papyrus

LEVEL vs DOMAIN ↓
SystemMulti-domain
ElectricalE / E
SoftwareSW
FluidHyd / Pneu / Fuel
MechanicalMCAD
L
Logical
How it’s organized

SysML Authoring

System logical

Logical blocks, ports, signals, interfaces; functional→logical allocation.

Capital Systems Architect

E/E architecture

Electrical, electronic & software domain enrichment.

ALM

SW architecture

Software components & interface definition.

NX Diagramming

Fluid architecture

Hydraulic / pneumatic / fuel schematic diagrams.

NX

Mechanical logical

Packaging, spatial & mechanical structure.

P
Physical
The realized design

Integrated

In Teamcenter

System-level physical = the governed product structure.

Capital

Detailed E/E

Schematics, wiring, harness, formboard, maintenance.

Code · Build

Implementation

Source, build & software configuration.

NX

Detailed fluid

3D layout & detailed diagrams.

NX

3D detailed design

Parts, assemblies & drawings.

Increasing fidelity down the ladder
PLM

System of record · digital thread · every artifact above

Teamcenter PLM

Governs identity, versioning, configuration & change management, and end-to-end traceability for everything in the frame. The tools author; Teamcenter governs.

VersioningChange controlConfig mgmtTraceability

Layer 2 · The boxes, defined

What each box means — and who owns the truth

Every capability says three things: what it is, what it owns, and whether it’s the system of record (the governed truth) or an authoring home (where the work is done, then released into the record). Each card’s accent color reads back to its place on the map above.

RRequirements managementTeamcenter Requirements
Is
The managed record for requirements — every requirement a controlled item, not a line in a document.
Owns
Requirement identity & text, parameters, attributes (verification method, safety level, status), baselines, versions, coverage & impact.
Record
System of record for requirements. Every other tool references or allocates to these — none of them governs them.
F–LSysML authoringCameo, Rhapsody, Sparx…
Is
The MBSE model where the system is formalized in SysML — functions, flows, logical blocks, ports, signals.
Owns
The functional architecture, the system-level logical architecture, and the allocation web tying requirement → function → logical.
Record
Authored, not governed. Consumes requirements from Teamcenter; hands domain detail to Capital & NX. It can hold requirements — but it owns the relationships, not the requirements. That is why it is not an RM tool.
L→PElectrical architectureCapital Systems Architect
Is
Where the multi-domain logical becomes a real E/E architecture — networks, devices and signals mapped toward wires.
Owns
The E/E logical & architecture (Capital Systems Architect); then detailed schematics, wiring, harness & formboard (Capital detailed tools).
Record
Authored here; released through Teamcenter. Traces up to the SysML logical; the controlled design is governed by the PLM backbone.
L→PFluid & mechanicalNX
Is
The mechanical environment — NX Diagramming for fluid / hydraulic / pneumatic schematics, and NX for 3D mechanical design.
Owns
Fluid schematic architecture (NX Diagramming), mechanical packaging & structure, and the 3D detailed design — parts, assemblies, drawings.
Record
Authored here; released through Teamcenter. Geometry and schematics become controlled items in the PLM backbone.
L→PSoftwareALM
Is
The application-lifecycle environment for software architecture and implementation.
Owns
Software component architecture & interfaces, then source, build and software configuration.
Record
Authored here, governed through Teamcenter (or a linked ALM record). Interfaces trace back to the system logical.
ALLSystem of record · digital threadTeamcenter (PLM)
Is
The backbone that governs everything the authoring tools produce — the frame around the whole map.
Owns
Identity, versioning, baselines, configuration & change management, and end-to-end traceability across every domain and level.
Record
The system of record for every artifact. The tools build; Teamcenter is where each artifact becomes the controlled truth — and where the digital thread stays unbroken.

Author ≠ Record

Where you build an artifact is not where it’s governed. Cameo, Capital and NX are authoring homes. Teamcenter is the system of record — the frame around everything — owning identity, versioning, baselines and change control. Confusing these two roles is why people mislabel tools.

Why Cameo isn’t your RM tool

Cameo can hold requirements and trace them to functions and verification — genuinely valuable. But it manages the relationships to requirements, not the governed lifecycle of each one. The managed record — IDs, baselines, audit, coverage at scale — lives in Teamcenter Requirements. Containing a requirement ≠ managing it.