Skip to main content
Use the System Structure Navigator to understand your system’s hierarchical structure, verify completeness of system element definitions, validate that all elements have corresponding functions and characteristics, and drill down into detailed analyses (FMEA, risk controls) for any system component.

Overview

The System Structure Navigator provides a hierarchical tree view of all system elements organized by decomposition level:
SYSTEM: Top-level system (e.g., AEB System)
├── SUBSYSTEM: Intermediate decomposition level
│   ├── COMPONENT: Leaf-level design elements
│   └── COMPONENT: Leaf-level design elements
└── SUBSYSTEM: Additional subsystems
    ├── COMPONENT: Design element
    └── COMPONENT: Design element
This structure mirrors the multi-level FMEA hierarchy required by ISO 26262 and AIAG-VDA standards: System FMEA (SFMEA) analyzes system-level failure modes, Subsystem FMEA (SFMEA) analyzes subsystem level, and Design FMEA (DFMEA) analyzes component design elements.

Report Structure

PropertyDescription
Report TypeInteractive hierarchical reference report (Velocity dashboard)
Primary SpaceDesign space
Data SourcesystemElement work items with parent-child relationships (type=system, subsystem, component)
Navigation TargetLinks to design requirements, functions, characteristics, and FMEA modules per element
Standards ReferenceISO 26262 Part 4 (System Design): system element hierarchy; ISO 26262 Part 5 (Hardware Design): hardware architecture
AudienceSystem architects, design engineers, safety engineers validating system completeness

System Element Hierarchy Levels

The System Structure Navigator recognizes three hierarchy levels defined by the elementType enumeration field on systemElement work items:
LevelTypePurposeTypical Count
SystemsystemTop-level system entity; scope boundary for SFMEA1 per project (e.g., “AEB System”)
SubsystemsubsystemIntermediate architectural decomposition; each has SFMEA3–6 typical (e.g., “Sensor Housing Subsystem”)
ComponentcomponentLeaf-level design element; each has DFMEA8–15 typical (e.g., “Camera Module”)
The navigator queries the RTM domain model’s parent-child relationships to construct the tree. Each systemElement links to zero or more child elements via the children[] relationship (typically modeled as a back-link constraint).

Column Structure

The System Structure Navigator displays the following columns:
ColumnTypeDescriptionLinks To
Element NametextFull name of system element (e.g., “Sensor Housing Assembly”)systemElement work item
Element TypeenumHierarchy level (System / Subsystem / Component)
Function CountintegerReal-time count of function work items assigned to this element via allocatedTo link role
Characteristic CountintegerReal-time count of characteristic work items assigned to this element via allocatedTo link role
Failure Mode CountintegerCount of failureMode work items linked to this element’s DFMEA moduleDFMEA modules
Risk Control CountintegerCount of riskControl work items linked to failure modes for this elementRisk controls
Design Requirement CountintegerCount of design requirements allocated to this elementDesign requirements
DFMEA Document LinkhyperlinkDeep link to the Design FMEA (DFMEA) Risksheet for this component (component level only)DFMEA Risksheet
Characteristics Sheet LinkhyperlinkDeep link to the Characteristics PowerSheet for this elementCharacteristics PowerSheet
FMEA Coverage Statustraffic lightVisual indicator (🟢 green ≥90% FM coverage, 🟡 yellow 70–89%, 🔴 red <70%, ⚪ gray no FMEAs)

Report Layout

System-Level Summary Card

At the top of the report:
SectionContent
System Element TreeHierarchical view of system/subsystem/component structure
Element PropertiesSelected element’s fields, status, and attributes
Linked ItemsRelated requirements, failure modes, test cases
Coverage SummaryTraceability completeness per element
Quick NavigationJump to related Risksheet, PowerSheet, or report

Hierarchical Tree Section

The navigator renders a collapsible tree table showing each system element indented by hierarchy level:
SYSTEM: AEB System
├─ Subsystem: Sensor Housing Subsystem
│  ├─ Component: Sensor Housing Assembly      [18 FM] [16 RC]
│  ├─ Component: Camera Module                [24 FM] [19 RC]
│  └─ Component: Radar Module                 [18 FM] [15 RC]
├─ Subsystem: ECU Processing Subsystem
│  ├─ Component: System-on-Chip (SoC)         [22 FM] [18 RC]
│  ├─ Component: Safety Co-Processor          [7 FM]  [6 RC]
│  ├─ Component: Memory (Flash/RAM)           [12 FM] [10 RC]
│  └─ Component: Power Management IC          [11 FM] [9 RC]
└─ Subsystem: Vehicle Interface Subsystem
   └─ Component: CAN Transceivers             [19 FM] [15 RC]
Each row is clickable: clicking an element name navigates to the systemElement work item detail page. Clicking a function/characteristic/FM count drills down to a filtered PowerSheet or Risksheet for that element.

Gap Analysis Sections

Below the tree, the navigator displays three gap sections:

Components Without DFMEA

Lists all component-level system elements that do not yet have a linked Design FMEA module (DFMEA document in Design space). Example:
  • Memory (Flash/RAM) — No DFMEA module assigned → [Create DFMEA]

Components Missing Functions

Lists components with zero allocated functions (allocation gap). Example:
  • CAN Transceivers — 0 functions allocated → [Allocate Functions]

Components Missing Characteristics

Lists components with zero allocated characteristics (design parameter definition gap). Example:
  • (none)

Unfinished FMEA Analyses

Lists components with DFMEA modules where >10% of failure modes lack post-mitigation assessment (incomplete risk mitigation):
  • Memory (Flash/RAM) — 87% FMEA coverage (7/8 failure modes assessed) → [View Incomplete FMs]

Technical Implementation

Data Sources

The System Structure Navigator aggregates data from multiple work item types and link roles:
SourceQueryPurpose
systemElementtype:system OR type:subsystem OR type:componentRetrieve all elements
Parent-child relationshipslinkedWorkItems:(parent, children) or backlinkedWorkItems:(parent, children)Build hierarchy tree
FunctionslinkedWorkItems:allocatedTo with target type=functionCount functions per element
CharacteristicslinkedWorkItems:allocatedTo with target type=characteristicCount characteristics per element
Design FMEA modulesmoduleFolder=Design AND moduleName contains element nameFind DFMEA documents
Failure modestype:failureMode AND linkedWorkItems:module=<DFMEA>Count FMs per element
Risk controlstype:riskControl AND backlinkedWorkItems:mitigates=<FM>Count controls per FM

Velocity Macros Used

The report uses the following Nextedy Velocity macros:
#import('nextedy_solutions.vm')
#nxInit()

## Macro: nxSystemElementTree(systemElement, indent)
## Recursively renders system element hierarchy with children
#macro(nxSystemElementTree $element $indent)
  #set($children = $element.linkedWorkItems().forward('children', 'systemElement'))
  <tr style="background-color: #{'#ffffff' if $indent % 2 == 0 else '#f5f5f5'};">
    <td style="padding-left: ${indent * 20}px;">
      <strong>$element.title</strong>
    </td>
    <td>#nxStatCount("type:function AND linkedWorkItems:allocatedTo.back()=$element.id")</td>
    <td>#nxStatCount("type:characteristic AND linkedWorkItems:allocatedTo.back()=$element.id")</td>
    <td>#nxLinkCoverage($element, "failureMode", "assesses", "forward")</td>
    <td>
      #if($element.fields().elementType().text() == 'component')
        #set($dfmea = $element.linkedWorkItems().forward('hasDfmea', 'module'))
        #if($dfmea)
          <a href="/automotive/polarion/#/project/$projectId/wiki/$dfmea.name">View DFMEA</a>
        #else
          <span style="color: red;">⚠ No DFMEA</span>
        #end
      #end
    </td>
  </tr>
  #foreach($child in $children)
    #nxSystemElementTree($child, $indent + 1)
  #end
#end

Coverage Calculations

Function Allocation Coverage:
Covered = COUNT(function WHERE linkedWorkItems.allocatedTo.back = element)
Total = COUNT(function WHERE linkedWorkItems.allocatedTo.back IN (element OR siblings))
Coverage % = Covered / Total * 100
FMEA Coverage per Element:
Covered = COUNT(failureMode WHERE module = element.dfmeaModule AND postmitigationAP IS NOT NULL)
Total = COUNT(failureMode WHERE module = element.dfmeaModule)
Coverage % = Covered / Total * 100
Risk Control Effectiveness:
Covered = COUNT(riskControl WHERE backlinkedWorkItems.mitigates.back.postmitigationAP < 'H')
Total = COUNT(failureMode WHERE module = element.dfmeaModule AND postmitigationAP = 'H')
Effectiveness % = Covered / Total * 100
The System Structure Navigator provides quick-access links to related reference pages:
TargetLinkPurpose
RTM Domain ModelsystemElement entity definition, parent-child relationshipsUnderstand data structure
System Element ReferencesystemElement work item type definition, fields, usageWork with elements
Function Referencefunction work item type, allocation semanticsAllocate functions
Characteristic Referencecharacteristic work item type, SC/CC classificationDefine characteristics
Design FMEA ReportExecutive-level DFMEA coverage by componentView FMEA summary
Design Verification SheetPowerSheet showing design requirements and characteristics per elementVerify design completeness
Whole RTM SheetComplete traceability matrix across all levelsValidate traceability

Drill-Down Actions

Clicking any count or status indicator in the System Structure Navigator executes a filtered query:
  • Function count → Opens Subsystem Functions Sheet filtered to this element
  • Characteristic count → Opens Characteristics PowerSheet filtered to this element
  • Failure mode count → Opens the Design FMEA Risksheet for this component (design space)
  • Risk control count → Executes Lucene query: type:riskControl AND backlinkedWorkItems:mitigates:falureMode.module=<DFMEA>
  • Coverage status (🔴 red) → Opens FMEA module with filter showing incomplete failure modes

Interpretation Guide

Green Status (🟢 ≥90% Coverage)

  • All functions allocated and characteristics defined
  • ≥90% of failure modes have post-mitigation assessment
  • Risk controls assigned to all high-priority failure modes
  • Action: Monitor for new requirements; conduct periodic reviews per Risk Control Effectiveness Report

Yellow Status (🟡 70–89% Coverage)

  • Some functions/characteristics missing OR some failure modes lack post-mitigation assessment
  • Action: Complete FMEA assessment per FMEA Workflow; allocate missing design parameters per Characteristics How-To

Red Status (🔴 <70% Coverage)

  • Significant gaps in function allocation, characteristic definition, or FMEA completion
  • Action: Prioritize element completion; escalate to design team; see Traceability Gap Resolution

Gray Status (⚪ No DFMEA Module)

  • Component lacks an assigned Design FMEA Risksheet module
  • Action: Create new DFMEA document per Create DFMEA Document

Standards Compliance

The System Structure Navigator supports compliance validation for:
StandardCompliance PointHow Navigator Helps
ISO 26262 Part 4System element hierarchy defined (4.3.2)Visualizes hierarchy structure and completeness
ISO 26262 Part 5Hardware architecture decomposed to components (5.1.1)Shows component-level elements and DFMEA coverage
ISO 26262 Part 4–6All safety-critical functions and characteristics identified (cross-part)Flags missing function/characteristic allocations
AIAG-VDA FMEAMulti-level FMEA per product hierarchy (System → Subsystem → Component)Validates DFMEA module assignment to each component
IATF 16949All special characteristics tracked per component (APQP requirement 4.5)Shows characteristic counts and allocation status

Common Tasks

Validate System Completeness

  1. Open System Structure Navigator
  2. Review system-level summary card: confirm 100% function and characteristic allocation
  3. Scroll through tree; look for ⚪ gray status (missing DFMEA modules)
  4. Click red-status components; examine gaps in “Components Missing Functions” section
  5. Create missing FMEAs or allocate missing design parameters as needed

Prepare for Design Freeze

  1. Filter to components with 🟡 yellow status
  2. Complete all FMEA post-mitigation assessments per Track Post-Mitigation Ratings
  3. Verify all risk controls have linked test cases per Link Tests to Requirements
  4. Confirm all components show 🟢 green (≥90% coverage)

Generate Audit Report

  1. Take screenshot of System Structure Navigator
  2. Export system-level summary card to PDF
  3. Document any red/yellow status components as open items
  4. Cross-reference with Safety Readiness Scorecard for standards-specific readiness metrics