Skip to main content

​
Prerequisites

Before creating the hierarchy, you should have:
  • At least one top-level System Element defined (see Define System Elements)
  • A clear understanding of your product architecture from system to component level
  • ASIL targets determined from HARA safety goals (if applicable)

​
Steps

​
1. Navigate to System Elements Module

From the sidebar, navigate to Documentation → System Structure Navigator or directly to the Design space, then locate the System Elements document in the inventory tree.

​
2. Create Parent-Child Relationships

For each System Element:
  1. Open the work item form
  2. Scroll to the Linked Work Items section
  3. In the parent link role field, select the immediate parent element
  4. Save the work item
Instead of opening each work item individually, use the System Structure Navigator PowerSheet view to batch-assign parent relationships directly in the grid.

​
3. Verify Hierarchy Structure

Open the System Structure Navigator report to visualize the complete tree: 
System: AEB System
├── Subsystem: Sensor & Housing Subsystem
│   ├── Component: Sensor Housing Assembly
│   ├── Component: Camera Module
│   └── Component: Radar Module
├── Subsystem: ECU & Processing Subsystem
│   ├── Component: System-on-Chip (SoC)
│   ├── Component: Safety Co-Processor
│   ├── Component: Memory (Flash & RAM)
│   └── Component: Power Management IC (PMIC)
└── Subsystem: Vehicle Interface Subsystem
    └── Component: CAN Transceivers
The navigator uses elementType values to determine hierarchy depth and applies color-coded icons:
Element TypeIcon ColorTypical Level
SystemDark Purple (#4527a0)Top level
SubsystemMedium Purple (#5e35b1)Middle tier
Assembly, SubassemblyLight Purple (#7e57c2)Lower tier
Component, EquipmentLightest PurpleLeaf nodes

​
4. Configure Outline Numbering

Enable automatic outline numbering to maintain hierarchy clarity:
  1. From the Documentation space, select the System Elements module
  2. Click ⚙️ Module Settings
  3. Enable Auto Outline Numbering
  4. Set numbering format to 1.1.1 style
This produces identifiers like:
  • 1 System: AEB System
  • 1.1 Subsystem: Sensor & Housing Subsystem
  • 1.1.1 Component: Camera Module
  • 1.1.2 Component: Radar Module
Once the hierarchy is established, allocate functions to elements using the allocatedTo link role:
  1. Open a Function work item (e.g., “Detect Obstacle in Path”)
  2. In Linked Work Items → allocatedTo, select one or more System Elements
  3. Save
This creates the traceability required for AIAG-VDA FMEA structure columns (System Element → Function → Failure Mode → Characteristic).

​
Common Issues

Avoid setting Element A as parent of Element B while Element B is parent of Element A. The System Structure Navigator will display an error or infinite loop. Always verify the hierarchy flows from System → Subsystem → Component in one direction.
Don’t mix elementType values at the same hierarchy depth (e.g., one child as “Assembly” and another as “Component” under the same parent). This breaks visual consistency in reports and FMEA structure columns. Standardize element types by level:
  • Level 1: System
  • Level 2: Subsystem
  • Level 3: Assembly or Component
  • Level 4: Subassembly or Equipment
If you’re documenting multiple similar products (e.g., AEB System v1, v2, v3), export the System Elements module as a template and reuse it for new projects. This ensures consistent hierarchy patterns and reduces data entry errors.

​
ASCII-Art Hierarchy Visualization

diagram

​
Verification

You should now see:
  • A complete hierarchy tree in the System Structure Navigator report
  • Outline-numbered System Element IDs (e.g., 1.1.1, 1.1.2)
  • Color-coded icons matching elementType values in all dashboard views
  • Functions linked to System Elements via allocatedTo relationship
Test the hierarchy by:
  1. Opening the System Structure Navigator report
  2. Clicking on any System Element row
  3. Verifying the Allocated Functions column shows related functions
  4. Checking that FMEA Risksheet documents filter to the correct System Element scope

​
See Also