RTM Model Configuration
| Property | Type | Default | Description |
|---|
| sourceQuery | string | entity.type = 'Characteristic' | Queries Characteristic work items from the RTM domain model |
| expansionPath | string | Characteristic.failureModes | Expands from each characteristic to its linked failure mode entities via the failureModes relationship |
| expansionMode | string | denormalized | Displays expansion results in denormalized grid format with failure mode columns appended to characteristic rows |
| sortBy | string | objectId ASC | Default sort order by characteristic identifier in ascending sequence for reproducible view ordering |
Column Groups Configuration
The sheet organizes columns into two visually distinct semantic sections with color-coded headers:
| Group | Header Color | Purpose | Collapse Target |
|---|
| Characteristic Properties | Dark Green (#2d5016) | Displays characteristic ID, title, SC/CC classification, target value, and tolerance specification | title |
| Failure Modes | Dark Red (#5d1f1a) | Shows linked failure mode descriptions, severity/occurrence/detection ratings, and action priority from FMEA analysis | description |
Characteristic Properties Group
| Column Name | Field Binding | Type | Editable | Width | Description |
|---|
| Characteristic ID | objectId | text | false | 120px | Unique identifier for the characteristic (e.g., CH-001), managed by Polarion |
| Title | title | text | true | 250px | Characteristic name or parameter description (e.g., “Camera Lens Focal Length”) |
| SC/CC Classification | classification | enum | true | 100px | Safety-Critical (SC) or Critical Component (CC) designation with custom rendering |
| Target Value | targetValue | text | true | 150px | Design requirement specification for measurable characteristic parameters (e.g., “50mm ± 0.5mm”) |
| Tolerance | tolerance | text | true | 150px | Tolerance range or environmental constraint notes for characteristic variability bounds |
Failure Modes Group
| Column Name | Field Binding | Type | Editable | Width | Description |
|---|
| Failure Mode Description | FailureMode.description | text | false | 300px | Read-only scenario detail from linked failure mode (e.g., “Lens contamination causing object detection failure”) |
| FMEA Severity | FailureMode.severity | enum | false | 80px | Pre-mitigation severity rating (1-10) from DFMEA analysis; read-only for traceability audit trail |
| FMEA Occurrence | FailureMode.occurrence | enum | false | 80px | Pre-mitigation occurrence frequency (0-10) from DFMEA analysis |
| FMEA Detection | FailureMode.detection | enum | false | 80px | Pre-mitigation detection capability (0-10) from DFMEA analysis; indicates how easily failure is detected |
| Action Priority | FailureMode.postmitigationAP | enum | false | 80px | Traffic-light formatted action priority (H=High/orange, M=Medium/yellow, L=Low/green) from post-mitigation FMEA ratings |
SC/CC Classification Rendering
The SC/CC classification field uses a custom formatter to render uppercase labels with conditional color coding:
- SC (Safety-Critical): Component whose failure directly impacts ISO 26262 functional safety; requires ASIL decomposition and safety goal allocation
- CC (Critical Component): Component required for product quality per IATF 16949; does not directly impact functional safety but affects customer satisfaction and reliability
Rendering Rules
Renderer: SCCCRenderer
Input: 'SC' or 'CC' enum value
Output Format:
SC: uppercase label 'SC' with orange background (#FFA500)
CC: uppercase label 'CC' with red background (#FF0000)
Display: Bold font, white text for contrast
Rationale: Visual severity hierarchy — orange (SC) < red (CC) distinguishes safety-critical components from quality-critical components
Color Mapping Rationale:
- Orange for SC indicates safety-critical requirement with ISO 26262 compliance obligation
- Red for CC indicates highest-priority manufacturing control requirement with IATF traceability
- Colors match traffic-light conventions (yellow/red for warning/critical states)
The final action priority field displays color-coded indicators derived from post-mitigation FMEA calculations:
| Action Priority | Color | Meaning | Response Required |
|---|
| H (High) | Red (#FF0000) | Severity × Occurrence × Detection ≥ 125 post-mitigation | Immediate corrective action required; cannot proceed to production |
| M (Medium) | Orange/Yellow (#FFA500) | Severity × Occurrence × Detection 50-124 post-mitigation | Mitigation review required; may proceed with controls in place |
| L (Low) | Green (#00AA00) | Severity × Occurrence × Detection < 50 post-mitigation | Routine monitoring; acceptable for production release |
Action Priority is computed from post-mitigation SFMEA/DFMEA ratings. If source FMEA is not linked or ratings are not updated, AP value will be outdated. Always refresh FMEA document before reviewing characteristics sheet.
Predefined Views
The sheet provides multiple progressive workflow views for different phases of design verification:
Full Detail View (Default)
Configuration:
View: 'default'
Columns: All characteristic properties + all failure mode columns
Sort: By objectId ascending
Purpose: Complete design-to-FMEA traceability review
Audience: Design engineers during DVP&R planning, FMEA engineers linking failure modes
Use Case: When creating design verification plans, engineers need to see all failure modes and their FMEA ratings simultaneously to assess test coverage requirements.
Without Failure Modes View
Configuration:
View: 'WithoutFailureModes'
Columns: Characteristic ID, Title, SC/CC Classification, Target Value, Tolerance (failure modes hidden)
Sort: By objectId ascending
Purpose: Focused editing of design parameters without FMEA distraction
Audience: Design engineers during characteristic definition phase (left side of V-model)
Use Case: During initial design phase (V-model concept/system design stages), characteristics are defined before FMEA analysis. This view eliminates visual clutter from empty failure mode columns.
Summary View
Configuration:
View: 'Summary'
Columns: Characteristic ID, Title, SC/CC Classification (failure modes hidden, detail columns collapsed)
Sort: By objectId ascending
Purpose: Executive-level review and quick characteristic triage
Audience: Program managers, safety engineers, design reviews and compliance audits
Use Case: When presenting design characteristics in safety review meetings or audit preparations, abbreviated view fits typical presentation screen real estate while preserving key traceability information.
RTM Expansion Pattern
Component Design Document
│
├─ Characteristic: "Camera Lens Focal Length"
│ ├─ SC/CC: SC (safety-critical for object detection)
│ ├─ Target Value: "50mm ± 0.5mm"
│ └─ failureModes link → [traversed by PowerSheet expansion]
│ ├─ Failure Mode: "Lens contamination → blurred image"
│ │ └─ DFMEA Post-AP: H (Red)
│ ├─ Failure Mode: "Optical coating degradation → reduced light transmission"
│ │ └─ DFMEA Post-AP: M (Orange)
│ └─ Failure Mode: "Mechanical misalignment → off-axis focus"
│ └─ DFMEA Post-AP: L (Green)
│
└─ Characteristic: "Sensor Housing Temperature Range"
├─ CC: Critical Component
├─ Target Value: "-40°C to +85°C"
└─ failureModes link → [0 failure modes; no linked FMEA scenarios]
Expansion Mechanics:
- PowerSheet queries all Characteristic entities from RTM domain model
- For each characteristic, RTM expansion traverses
failureModes link role
- Each linked failure mode renders in a new sub-row beneath parent characteristic
- Characteristic fields (ID, title, SC/CC) repeat across sub-rows for context
- Failure mode fields (description, severity, AP) populate in dedicated columns
- Collapse/expand toggle available per characteristic row to hide/show failure modes
Entity Factory Configuration
Inline creation of linked failure modes directly from the sheet:
| Property | Value | Purpose |
|---|
| entityType | FailureMode | Create new failure mode work items |
| targetModule | Design/ComponentDFMEA | Place new failure modes in Design FMEA specification document |
| autoLinkRole | failureModes | Automatically create bidirectional link from characteristic to new failure mode |
| defaultFields | category='Design' | Pre-populate category enum to distinguish from system/process FMEA failure modes |
Workflow Benefit: Design engineer can identify new failure scenario while reviewing characteristics, create failure mode with single click, and automatically maintain characteristic-to-FMEA traceability without manual linking.
Default Sorting Behavior
Primary Sort: objectId (ascending)
Characteristic rows sort by internal identifier (e.g., CH-001, CH-002, CH-003) rather than alphabetical title. This ordering strategy provides:
- Reproducibility: Same sort order across all sessions and user views, enabling cross-team reference by characteristic ID
- Document Correlation: Mirrors LiveDoc outline numbering, allowing alignment with printed Design Specification document
- Predictability: Design engineer can confidently reference “Characteristic CH-045” knowing it will appear in same sequence in colleague’s sheet
User Override: Click any column header to re-sort by that field (e.g., sort by Action Priority to identify high-risk characteristics first).
Design Verification Integration
The Component Characteristics Sheet bridges design specification and test planning:
| V-Model Phase | Work Item Types | PowerSheet Config |
|---|
| Design Phase | Design Requirements, Functions | design-verification.yaml |
| Implementation Phase | Components, Characteristics | component-characteristics.yaml |
| Verification Phase | Test Cases, Test Results | subsystem-verification.yaml |
Design engineers use this sheet to ensure every characteristic with SC/CC classification has:
- Linked failure modes in DFMEA (traceability to risk analysis)
- Verification test cases in DVP plan (traceability to validation evidence)
- Action priority status (risk control effectiveness)
After using Component Characteristics Sheet to identify high-priority characteristics (filter by Action Priority = H), navigate to Design Verification Sheet to create corresponding test cases. Use characteristic ID as test case reference for traceability audit trail.
Configuration Example
# .polarion/nextedy/sheet-configurations/component-characteristics.yaml
name: "Component Characteristics Sheet"
description: "Design characteristics with FMEA failure mode traceability"
rtmModelConfiguration:
sourceQuery: "entity.type = 'Characteristic'"
expansionPath: "Characteristic.failureModes"
sortBy: "objectId ASC"
columnGroups:
- name: "Characteristic Properties"
collapseTo: "title"
headerColor: "#2d5016"
columns:
- field: "objectId"
label: "ID"
editable: false
width: "120px"
- field: "title"
label: "Characteristic"
editable: true
width: "250px"
- field: "classification"
label: "SC/CC"
renderer: "SCCCRenderer"
editable: true
width: "100px"
- field: "targetValue"
label: "Target Value"
editable: true
width: "150px"
- field: "tolerance"
label: "Tolerance"
editable: true
width: "150px"
- name: "Failure Modes"
collapseTo: "description"
headerColor: "#5d1f1a"
columns:
- field: "FailureMode.description"
label: "Failure Scenario"
editable: false
width: "300px"
- field: "FailureMode.severity"
label: "Severity"
editable: false
width: "80px"
- field: "FailureMode.occurrence"
label: "Occurrence"
editable: false
width: "80px"
- field: "FailureMode.detection"
label: "Detection"
editable: false
width: "80px"
- field: "FailureMode.postmitigationAP"
label: "Action Priority"
renderer: "TrafficLightRenderer"
editable: false
width: "80px"
entityFactory:
type: "FailureMode"
targetModule: "Design/ComponentDFMEA"
autoLinkRole: "failureModes"
views:
- name: "default"
label: "Full Detail"
visibleColumnGroups: ["Characteristic Properties", "Failure Modes"]
- name: "WithoutFailureModes"
label: "Without Failure Modes"
hiddenColumns: ["Failure Modes"]
- name: "Summary"
label: "Summary"
visibleColumns: ["objectId", "title", "classification"]