Overview
The Subsystem Functions Sheet implements a two-section RTM (Requirements Traceability Matrix) expansion pattern that displays:
- Left section: Subsystem Function entities with safety classification indicators (SC/CC badges)
- Right section: Failure Mode entities linked to each function through the RTM model relationship
This denormalized grid view enables safety engineers to simultaneously review function definitions and their associated failure modes, supporting progressive FMEA/FMECA workflows where design functions must be traced to failure analysis artifacts.
RTM Model Configuration
| Property | Type | Default | Description |
|---|
| sourceQuery | String | type:function AND moduleFolder:current() | Lucene query that selects Function entities from the currently viewed Polarion document; scopes PowerSheet to document context for embedded sheets |
| entityFactory | String | function | RTM model entity type identifier for Function work items; resolves to Function type in .polarion/nextedy/models/domain-model.yaml |
| expansionPaths | Array | ["failureModes"] | RTM relationship traversal path starting from Function entities; expands through failureModes link role to retrieve linked FailureMode entities; supports multi-hop paths using dot notation |
| expandedEntityType | String | failureMode | Target entity type (FailureMode) reached through expansion; determines which columns and formatters are available in the right-side section |
| currentDocument | Boolean | true | When true, limits Function entities to those in the currently open document; essential for embedded PowerSheet scenarios where scoping prevents cross-document function mixing |
The Subsystem Functions Sheet applies current document constraint to ensure that only functions defined in the active LiveDoc are displayed. This prevents accidental mixing of functions from different subsystems or analysis documents. For cross-document functional analysis, use the Whole RTM PowerSheet. Column Groups and Layout
Function Properties Column Group
The left section groups all Function metadata columns with dark green header styling. Columns collapse to the Description field, optimizing screen space for progressive disclosure workflows.
| Property | Type | Default | Description |
|---|
| name | String | Function Properties | Display label for the column group header; appears in green (#1b5e20 background) |
| collapseTo | String | description | Column that remains visible when user minimizes the group; description field serves as anchor for function summary |
| color | String | darkgreen | Background color theme for all columns in this group; applies to header and cell backgrounds for visual cohesion |
| description | String | Function metadata fields (read-only) | Inline help text explaining the section’s purpose |
| Column | Formatter | Width | Read-Only | Purpose |
|---|
objectId | standard | 100px | Yes | Function work item ID (e.g., F-001); serves as stable identifier for traceability |
title | boldTitle | 250px | Yes | Function name/title; rendered bold for visual emphasis; focus column for keyboard navigation |
description | standard | 350px | Yes | Detailed function description including operational context; collapse target for group |
classification | standard | 100px | Yes | Safety classification value (SC or CC); used by SC/CC badge renderer |
actionPriority | colorPriority | 80px | Yes | Final Action Priority (H/M/L) derived from highest-priority failure mode in this function |
Failure Modes Column Group
The right section expands through the RTM model relationship to display all linked FailureMode entities with dark red header styling. Multiple failure modes per function create multiple rows in the PowerSheet.
| Property | Type | Default | Description |
|---|
| name | String | Failure Modes | Display label for the column group header; appears in dark red (#b71c1c background) |
| collapseTo | String | description | Column that remains visible when minimized; failure mode description provides quick reference |
| color | String | darkred | Background color theme for all columns in this group; visually distinguishes failure data from function data |
| editable | Boolean | true | Unlike function columns, failure mode columns permit inline editing for corrective action entry and severity reassessment |
| Column | Formatter | Width | Read-Only | Purpose |
|---|
objectId | standard | 100px | Yes | Failure mode work item ID (e.g., FM-1234); links to detailed FMEA analysis in Risks space |
description | standard | 350px | No | Failure mode description text; editable for refinement as FMEA analysis progresses |
severity | standard | 80px | No | FMEA Severity rating (1-10 scale); editable to reflect updated risk assessment |
occurrence | standard | 80px | No | FMEA Occurrence rating (0-10 scale per ISO 26262 / AIAG-VDA methodology) |
detection | standard | 80px | No | FMEA Detection rating (0-10 scale); editable to reflect effectiveness of detection methods |
actionPriority | colorPriority | 80px | No | Action Priority (H/M/L) computed from pre-mitigation S×O×D; green/orange/red background indicates severity tier |
Safety Classification Renderer (SC/CC Badge)
Custom JavaScript formatter that displays safety classification values as uppercase badges with conditional background color:
// Configuration in subsystem-functions.yaml
classificationRenderer:
type: "safetyClassificationBadge"
properties:
scColor: "#FF9800" // Orange for Safety-Critical (SC)
ccColor: "#F44336" // Red for Critical Component (CC)
textColor: "#FFFFFF" // White text for contrast
textTransform: "uppercase" // Display "SC" and "CC" in capitals
- Displays the classification value (e.g., “SC”, “CC”, “NORM”) as a badge
- SC values render with orange background per ISO 26262 visual convention
- CC values render with red background to indicate component criticality
- Non-critical functions render with neutral gray background
- Badge width auto-fits text; provides quick visual scan of safety-critical functions
The SC/CC classification determines which design requirements and characteristics require failure mode analysis per ISO 26262 and AIAG-VDA methodology. Functions marked as SC or CC must have complete failure mode coverage in Design FMEA. Use this visual indicator to verify coverage completeness.
Action Priority Color-Coding Renderer
Conditional formatting that applies three-tier traffic-light styling to Action Priority values:
# Configuration example
actionPriorityRenderer:
type: "trafficLight"
conditions:
- value: "H"
backgroundColor: "#F44336" # Red for High priority
textColor: "#FFFFFF"
- value: "M"
backgroundColor: "#FF9800" # Orange for Medium priority
textColor: "#000000"
- value: "L"
backgroundColor: "#4CAF50" # Green for Low priority
textColor: "#FFFFFF"
| Action Priority | Background Color | Use Case |
|---|
| H (High) | Red | Failure modes requiring immediate risk control implementation; blocks design release until mitigated |
| M (Medium) | Orange | Failures requiring close monitoring and control plan implementation; acceptable with control evidence |
| L (Low) | Green | Low-risk failures with existing detection methods; acceptable for production; still requires control plan documentation |
The Subsystem Functions Sheet displays final Action Priority (H/M/L) computed from post-mitigation FMEA ratings. This prioritization reflects the effectiveness of risk controls applied to each failure mode and drives the Control Plan workflow in manufacturing.
Predefined Views
Default View (Complete)
Displays all Function and Failure Mode columns for comprehensive FMEA analysis and design verification planning.
Use case: Safety engineers conducting design FMEA analysis; design engineers linking design requirements to failure modes for failure control; configuration managers verifying FMEA completeness.
Configuration:
views:
- name: "default"
hiddenColumns: [] # All columns visible
sortBy: "title"
sortAscending: true
Without Failure Modes View
Hides all Failure Mode columns; displays only Function Properties section. Supports progressive workflow where functions are defined first, then failure modes are linked in a subsequent analysis phase.
Use case: Early design phase when functions are being defined but FMEA analysis has not yet commenced; system engineers reviewing function allocation without safety analysis details.
Configuration:
views:
- name: "withoutFailureModes"
hiddenColumns:
- "failureModes.*" # Collapse entire failure modes group
sortBy: "title"
sortAscending: true
Summary View
Displays only Function ID, Title, SC/CC Classification, and final Action Priority. Hides detailed descriptions for high-level executive reporting or quick compliance scan.
Use case: Program manager reviewing safety-critical function coverage; compliance auditor verifying SC/CC function identification; executive safety readiness scorecard.
Configuration:
views:
- name: "summary"
visibleColumns:
- "functionProperties.objectId"
- "functionProperties.title"
- "functionProperties.classification"
- "failureModes.actionPriority"
sortBy: "classification"
sortAscending: false # SC functions appear first
Default Sorting
Rows are sorted in ascending order by Function title, ensuring consistent, alphabetically-ordered function listing across analysis cycles. Users can override this sort interactively via PowerSheet UI controls (click column header to re-sort).
| Sort Property | Order | Rationale |
|---|
| title | Ascending (A→Z) | Alphabetical ordering provides predictable navigation for safety engineers; enables consistent cross-document function referencing |
| objectId | (secondary) | When function titles are identical, falls back to ID ordering for deterministic stability |
- Function — Represents subsystem-level functional capabilities; contains SC/CC classification and description; parent for failure analysis
- Failure Mode — Represents potential failure scenarios for functions; contains FMEA severity, occurrence, detection ratings and Action Priority
- Characteristic — Physical design parameters linked to functions; traces characteristics to failure modes via Design FMEA analysis
- System Element — System decomposition hierarchy; functions are allocated to system elements for architectural traceability
Workflow Integration
Typical Usage Sequence
- Function Definition Phase: Subsystem architects use the Design Verification Sheet to create Function entities and allocate them to System Elements
- Function Review: Switch to Without Failure Modes view to review function definitions with design team before FMEA analysis begins
- FMEA Analysis Phase: Safety engineers analyze each function in the default view, creating FailureMode entities for each identified failure scenario
- Severity Assessment: Rate failure modes using FMEA Severity, Occurrence, and Detection scales; Action Priority auto-computes based on S×O×D formula
- Risk Control Planning: Implement design controls (design changes, additional verification, component selection) and update post-mitigation Action Priority values
- Executive Review: Switch to Summary view to verify SC/CC function coverage and final Action Priority distribution for safety readiness scorecard
The Subsystem Functions Sheet is closely related to the Design Verification Sheet, which shows the same functions but with linked Design Requirements instead of Failure Modes. Use both sheets in tandem to maintain bidirectional traceability between function definitions and design FMEA analysis. Configuration Reference
Complete PowerSheet YAML configuration path:
.polarion/nextedy/sheet-configurations/subsystem-functions.yaml
Key Configuration Properties
sourceQuery: "type:function AND moduleFolder:current()"
entityFactory: "function"
expansionPaths:
- "failureModes"
expandedEntityType: "failureMode"
currentDocument: true
columnGroups:
- name: "Function Properties"
color: "darkgreen"
collapseTo: "description"
columns:
- name: "objectId"
formatter: "standard"
readOnly: true
width: "100px"
- name: "title"
formatter: "boldTitle"
readOnly: true
width: "250px"
hasFocus: true
- name: "description"
formatter: "standard"
readOnly: true
width: "350px"
- name: "classification"
formatter: "safetyClassificationBadge"
readOnly: true
width: "100px"
- name: "actionPriority"
formatter: "trafficLight"
readOnly: true
width: "80px"
- name: "Failure Modes"
color: "darkred"
collapseTo: "description"
editable: true
columns:
- name: "objectId"
formatter: "standard"
readOnly: true
width: "100px"
- name: "description"
formatter: "standard"
readOnly: false
width: "350px"
- name: "severity"
formatter: "numeric"
readOnly: false
width: "80px"
- name: "occurrence"
formatter: "numeric"
readOnly: false
width: "80px"
- name: "detection"
formatter: "numeric"
readOnly: false
width: "80px"
- name: "actionPriority"
formatter: "trafficLight"
readOnly: false
width: "80px"
sortBy: "title"
sortAscending: true
views:
- name: "default"
visibleColumns: "*"
- name: "withoutFailureModes"
hiddenColumns:
- "failureModes.*"
- name: "summary"
visibleColumns:
- "functionProperties.objectId"
- "functionProperties.title"
- "functionProperties.classification"
- "failureModes.actionPriority"
| Sheet | Purpose | Left Section | Right Section | Use Case |
|---|
| Subsystem Functions | Function-to-Failure analysis | Functions (SC/CC badge) | Failure Modes (FMEA ratings) | Design FMEA; safety classification verification |
| Design Verification | Function-to-Requirement traceability | Functions | Design Requirements | Verification planning; requirements allocation |
| Characteristics | Characteristic-to-Failure analysis | Characteristics (design parameters) | Failure Modes | Tolerance & target value management |
| Component Characteristics | Component-level design analysis | Characteristics (per component) | Failure Modes | Component DFMEA execution |
| Whole RTM | Cross-document traceability | Customer/System Requirements | Design Requirements / Functions | End-to-end V-model verification |
See Also
