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
| Property | Description |
|---|
| Report Type | Interactive hierarchical reference report (Velocity dashboard) |
| Primary Space | Design space |
| Data Source | systemElement work items with parent-child relationships (type=system, subsystem, component) |
| Navigation Target | Links to design requirements, functions, characteristics, and FMEA modules per element |
| Standards Reference | ISO 26262 Part 4 (System Design): system element hierarchy; ISO 26262 Part 5 (Hardware Design): hardware architecture |
| Audience | System 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:
| Level | Type | Purpose | Typical Count |
|---|
| System | system | Top-level system entity; scope boundary for SFMEA | 1 per project (e.g., “AEB System”) |
| Subsystem | subsystem | Intermediate architectural decomposition; each has SFMEA | 3–6 typical (e.g., “Sensor Housing Subsystem”) |
| Component | component | Leaf-level design element; each has DFMEA | 8–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:
| Column | Type | Description | Links To |
|---|
| Element Name | text | Full name of system element (e.g., “Sensor Housing Assembly”) | systemElement work item |
| Element Type | enum | Hierarchy level (System / Subsystem / Component) | — |
| Function Count | integer | Real-time count of function work items assigned to this element via allocatedTo link role | — |
| Characteristic Count | integer | Real-time count of characteristic work items assigned to this element via allocatedTo link role | — |
| Failure Mode Count | integer | Count of failureMode work items linked to this element’s DFMEA module | DFMEA modules |
| Risk Control Count | integer | Count of riskControl work items linked to failure modes for this element | Risk controls |
| Design Requirement Count | integer | Count of design requirements allocated to this element | Design requirements |
| DFMEA Document Link | hyperlink | Deep link to the Design FMEA (DFMEA) Risksheet for this component (component level only) | DFMEA Risksheet |
| Characteristics Sheet Link | hyperlink | Deep link to the Characteristics PowerSheet for this element | Characteristics PowerSheet |
| FMEA Coverage Status | traffic light | Visual 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:
| Section | Content |
|---|
| System Element Tree | Hierarchical view of system/subsystem/component structure |
| Element Properties | Selected element’s fields, status, and attributes |
| Linked Items | Related requirements, failure modes, test cases |
| Coverage Summary | Traceability completeness per element |
| Quick Navigation | Jump 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:
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:
| Source | Query | Purpose |
|---|
| systemElement | type:system OR type:subsystem OR type:component | Retrieve all elements |
| Parent-child relationships | linkedWorkItems:(parent, children) or backlinkedWorkItems:(parent, children) | Build hierarchy tree |
| Functions | linkedWorkItems:allocatedTo with target type=function | Count functions per element |
| Characteristics | linkedWorkItems:allocatedTo with target type=characteristic | Count characteristics per element |
| Design FMEA modules | moduleFolder=Design AND moduleName contains element name | Find DFMEA documents |
| Failure modes | type:failureMode AND linkedWorkItems:module=<DFMEA> | Count FMs per element |
| Risk controls | type: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
Navigation and Integration
The System Structure Navigator provides quick-access links to related reference pages:
| Target | Link | Purpose |
|---|
| RTM Domain Model | systemElement entity definition, parent-child relationships | Understand data structure |
| System Element Reference | systemElement work item type definition, fields, usage | Work with elements |
| Function Reference | function work item type, allocation semantics | Allocate functions |
| Characteristic Reference | characteristic work item type, SC/CC classification | Define characteristics |
| Design FMEA Report | Executive-level DFMEA coverage by component | View FMEA summary |
| Design Verification Sheet | PowerSheet showing design requirements and characteristics per element | Verify design completeness |
| Whole RTM Sheet | Complete traceability matrix across all levels | Validate 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:
| Standard | Compliance Point | How Navigator Helps |
|---|
| ISO 26262 Part 4 | System element hierarchy defined (4.3.2) | Visualizes hierarchy structure and completeness |
| ISO 26262 Part 5 | Hardware architecture decomposed to components (5.1.1) | Shows component-level elements and DFMEA coverage |
| ISO 26262 Part 4–6 | All safety-critical functions and characteristics identified (cross-part) | Flags missing function/characteristic allocations |
| AIAG-VDA FMEA | Multi-level FMEA per product hierarchy (System → Subsystem → Component) | Validates DFMEA module assignment to each component |
| IATF 16949 | All special characteristics tracked per component (APQP requirement 4.5) | Shows characteristic counts and allocation status |
Common Tasks
Validate System Completeness
- Open System Structure Navigator
- Review system-level summary card: confirm 100% function and characteristic allocation
- Scroll through tree; look for ⚪ gray status (missing DFMEA modules)
- Click red-status components; examine gaps in “Components Missing Functions” section
- Create missing FMEAs or allocate missing design parameters as needed
Prepare for Design Freeze
- Filter to components with 🟡 yellow status
- Complete all FMEA post-mitigation assessments per Track Post-Mitigation Ratings
- Verify all risk controls have linked test cases per Link Tests to Requirements
- Confirm all components show 🟢 green (≥90% coverage)
Generate Audit Report
- Take screenshot of System Structure Navigator
- Export system-level summary card to PDF
- Document any red/yellow status components as open items
- Cross-reference with Safety Readiness Scorecard for standards-specific readiness metrics