Overview The DFMEA Risksheet implements a three-level item hierarchy—characteristic (Item) → failure mode → cause—with integrated upstream and downstream risk traceability. The risksheet automatically calculates Risk Priority Numbers (RPN) using severity, occurrence, and detection ratings, applies color-coded visual indicators, and guides engineers through a structured seven-step mitigation workflow via progressive views.
Key characteristics:
17 columns organized into 4 logical header groups9 workflow views implementing a guided DFMEA methodologyAutomatic RPN calculation with 3-tier color coding (green/yellow/red)Upstream risk linking to System FMEA failure modes via the causes roleMitigation task management with linked risk controls, requirements, and verificationSC/CC classification badges for safety-critical and critical characteristics
Column Structure The DFMEA Risksheet contains 17 data columns organized into 4 header groups:
Group 1: Component Characteristics (Item level) Column Type Purpose Notes itemText (control column) Characteristic identifier and title Links to characteristic work item type. SC/CC classification badge rendered via cellRenderer. Zoom column for detail navigation. SC/CC ClassificationBadge (text) Safety-critical or critical characteristic designation Displays “SC” (orange) or “CC” (red) pill-format badge. Both client-side JavaScript and server-side Velocity rendering for print/export compatibility.
Group 2: Potential Failure (Failure mode and cause levels) Column Type Purpose Notes failureModeText (control column) Description of how the characteristic could fail Zoom column for failure mode detail. Item-level nesting: all failure modes for a characteristic roll up to that characteristic row. failureEffectsText The consequence of the failure mode on system or customer What happens if this failure mode occurs? Links to downstream system effects. potentialCausesText Root causes contributing to the failure mode Engineering analysis of why the failure mode could happen. upstreamRisksmultiItemLink with causes role Links to System FMEA failure modes causing this characteristic failure Enables vertical traceability from system to component level. Displays linked item title + parent module name (e.g., “Power Loss → System SFMEA: FCC-SFMEA”).
Group 3: Set Ranking (Pre-mitigation RPN) Column Type Purpose Default Notes severityEnum (1–5) Failure mode severity rating — 1 = No Effect, 5 = Catastrophic. Per ARP 4761 / DO-254 classification scales. occurrenceEnum (1–5) Likelihood of failure mode happening — 1 = Extremely Remote, 5 = Extremely Probable. detectionEnum (1–5) Ability to detect the failure before reaching customer — 1 = Certain to Detect, 5 = Certain Not to Detect. commonRpnFormula Pre-mitigation Risk Priority Number severity × occurrence × detectionCalculated value (no user input). Range 1–125. Color-coded cell decorator applied.
Group 4: Mitigations (Task management level) Column Type Purpose Notes riskControlIdText Identifier of the risk control (mitigation task) Linked to riskControl work item type. Multiple controls can address the same failure mode. riskControlTitleText Title/description of the mitigation action Displays linked risk control title for human reference. riskControlStatusEnum Workflow status of the mitigation task Values: Open, In Progress, Review, Closed, Deferred. linkedRequirementsserverRender (Velocity) Requirements allocated by this risk control Server-side rendering traverses task’s back-links to sysReq and desReq. Rendered as bulleted list. requirementVerificationserverRender (Velocity) Test cases verifying the linked requirements Server-side rendering traverses from requirements to linked testCase work items. Shows verification status.
Group 5: Final Ranking (Post-mitigation RPN) Column Type Purpose Default Notes occurrenceNewEnum (1–5) Post-mitigation occurrence rating — Applied after risk controls implemented. Typically lower than pre-mitigation occurrence. detectionNewEnum (1–5) Post-mitigation detection rating — Applied after design changes or additional controls. commonRpnNewFormula Post-mitigation Risk Priority Number severity × occurrenceNew × detectionNewCalculated value. Color-coded cell decorator applied (same 3-tier scale as pre-mitigation). Row header colored by post-mitigation RPN.
RPN Auto-Calculation (Pre-mitigation) commonRpn = severity × occurrence × detection
Cell Decorator: 3-tier color coding:
Green (≤10): Low risk, acceptable without mitigationYellow (11–30): Medium risk, mitigation requiredRed (>30): High risk, immediate action required
Also renders numeric value with text label below: “Low”, “Medium”, or “High”.
RPN Auto-Calculation (Post-mitigation) commonRpnNew = severity × occurrenceNew × detectionNew
Same 3-tier color coding as commonRpn. Used for row header background color via rowHeaderRpnNew renderer.
Auto-Generated Risk Description riskDescription = 'ON CHARACTERISTICS: ' + item_title + ' FAILURE MODE: ' + failureMode + ' CAUSE: ' + potentialCauses
Background cell styling: whitesmoke. Used in reports and risk summaries for narrative context.
Views (Workflow Guidance) The DFMEA Risksheet provides 9 progressive views guiding the seven-step DFMEA methodology:
View Name Purpose Visible Columns Use Case Default Overview and navigation item, failureMode, severity, occurrence, detection, commonRpn, riskControlTitle, riskControlStatus General browsing and status review No Up/Down Risks Simplified view excluding traceability All except upstreamRisks When component-level analysis is independent 1. Identify Failure Modes Discover potential failure modes item, failureMode, failureEffects, potentialCauses Initial FMEA brainstorming phase 2. Initial Risk Ranking Assign pre-mitigation RPN item, failureMode, severity, occurrence, detection, commonRpn Risk assessment phase 3. Link Upstream SFMEA Connect to system-level failure modes item, failureMode, upstreamRisks, commonRpn Establish traceability chain 4. Define Mitigations Create risk control tasks item, failureMode, riskControlId, riskControlTitle, riskControlStatus Mitigation planning 5. Verify Controls Check requirements and test coverage riskControlId, linkedRequirements, requirementVerification Verification planning 6. Final Risk Evaluation Assign post-mitigation RPN failureMode, occurrenceNew, detectionNew, commonRpnNew Residual risk assessment 7. Risk Summary High-level overview of risk posture item, failureMode, commonRpn, commonRpnNew, riskControlStatus Executive reporting Full View All columns (@all) Every column Complete analysis review
Cell Decorators and Styling RPN Cell Decorator Applied to both commonRpn and commonRpnNew columns. Renders:
Numeric RPN value
Colored background: green (≤10), yellow (11–30), or red (>30)
Text label below value: “Low”, “Medium”, or “High”
CSS classes: rpn1 (low), rpn2 (medium), rpn3 (high)
Example output: SC/CC Classification Badge Applied to SC/CC Classification column at Item (characteristic) level. Renders:
Pill-format badge with rounded corners
Orange background + white text for “SC” (Safety-Critical)
Red background + white text for “CC” (Critical Characteristic)
Both JavaScript (DOM) and Velocity (server) rendering for print/export
Example outputs: [SC] (orange pill) or [CC] (red pill)
The row header (leftmost column) is colored by post-mitigation RPN value using rowHeaderRpnNew renderer:
Green row header: post-mitigation RPN ≤10
Yellow row header: post-mitigation RPN 11–30
Red row header: post-mitigation RPN >30
Provides instant visual scan of risk status across all failure modes in the sheet.
Item Hierarchy and Nesting The DFMEA Risksheet implements a 3-level hierarchy for organized risk analysis:
Navigation:
Control Column (item and failureMode): Click to expand/collapse hierarchy levelsZoom Column : Click to navigate to linked work item detail pageUpstream Risks : Click to navigate to parent-level SFMEA failure mode
Example Structure Upstream Risk Linking The upstreamRisks column implements vertical traceability from System FMEA to Design FMEA:
Property Value Column Type multiItemLinkLink Role causes (forward direction)Target Type failureMode (from System FMEA)Rendering Item title + parent module name User Interaction Click to navigate to upstream failure mode in System FMEA risksheet
Example data:
System FMEA : “Power Bus Lost”
↓ causesDesign FMEA : “Voltage Below Minimum”
Displayed as: “Power Bus Lost (System SFMEA: FCC-SFMEA)”
The link cardinality and whether multiple upstream risks are supported per failure mode should be verified in the live Aerospace Safety Solution risksheet interface.
Mitigation Task Management Risk Control Linking The mitigation section (riskControlId, riskControlTitle, riskControlStatus) links Design FMEA entries to risk control tasks:
Property Value Notes Link Type Implicit via task ID Risk control is a separate riskControl work item type Cardinality Multiple A failure mode can have multiple mitigations Status Tracking Workflow enum Open → In Progress → Review → Closed (or Deferred) Requirement Allocation Back-links to sysReq / desReq Risk control task allocates requirements to implement the mitigation Verification Linked test cases Requirements linked to risk control are verified by test cases
Mitigation Chain (Velocity Traversal) The linkedRequirements and requirementVerification columns use server-side Velocity templates to automatically traverse the mitigation chain:
Risk Control Task
↓ back-link (allocatesTo)
System/Design Requirement
↓ forward-link (verifiedBy)
Test Case
Example traversal: Data Model Integration Work Item Type Relationships Work Item Type Role in DFMEA Link Role Cardinality characteristicItem (row) — 1 per row failureModePotential failure — 1..* per characteristic riskControlMitigation task (implicit) 1..* per failure mode sysReq / desReqRequirement allocated by risk control allocatesTo (back-link)1..* per risk control testCaseVerification of requirement verifiedBy1..* per requirement failureMode (System FMEA)Upstream risk via traceability causes1..* per DFMEA failure mode
Custom Fields The DFMEA document itself contains minimal custom fields:
Field Type Purpose Example Value systemElementIdReference Links risksheet to specific component ”ADCI” (Air Data Computer Interface) (Other fields) — Inherited from Document type status, version, owner, team
The complete set of document-level custom fields should be verified in the Aerospace Safety Solution project configuration.
Instance vs. Template The DFMEA Risksheet uses a template-instance pattern :
Template: modules/RiskTemplates/DFMEATemplate/attachments/risksheet.json
Serves as the master configuration for all Design FMEA risksheets
Located in the RiskTemplates folder (not part of any project space)
Registered in context.properties for template discovery
Instances: modules/Risks/DFMEA-<COMPONENT>/attachments/risksheet.json
Created per component (e.g., DFMEA-CMP-PSU for Power Supply Unit)
Byte-identical copies of the template at creation timeNot inherited or linked — changes to template do NOT auto-propagate to instances
Can be customized independently after creation
If the DFMEA template configuration is updated, existing instances must be manually updated to incorporate changes. There is no automatic propagation mechanism. Use version control or change notifications to track template updates across instances.
Configuration Files The DFMEA Risksheet configuration is stored in a single JSON file:
For instances:
File format: JSON with the following root-level sections:
columns[] — Column definitions (17 items)headerGroups[] — Logical grouping for column headers (4 groups)views[] — Workflow views (9 items)formulas{} — Formula definitions (3 formulas)cellDecorators[] — Visual rendering rules (2 decorators)rowHeader.renderer — Row header styling rule (1 renderer)
See reference/risksheet-sfmea.md for the System FMEA risksheet configuration reference. See reference/risksheet-fha.md for the Functional Hazard Assessment risksheet reference. For complete risksheet.json schema documentation, consult the Nextedy Risksheet product documentation. Key Workflow Patterns Pattern 1: Finding Upstream Risks When analyzing a Design FMEA failure mode:
Check the upstreamRisks column for linked System FMEA failure modes
Click the upstream link to view the parent failure mode in the System SFMEA risksheet
Review the upstream risk’s severity and occurrence to inform component-level strategy
Pattern 2: Planning Mitigations When defining risk controls for a failure mode:
Create or link a riskControl work item
Populate riskControlId, riskControlTitle, and riskControlStatus
The risk control task should allocate design requirements to implement the fix
The system automatically traverses to linked test cases for verification planning
Pattern 3: Post-Mitigation Evaluation After risk controls are implemented:
Update occurrenceNew and detectionNew based on design changes and new testing
commonRpnNew recalculates automaticallyIf post-mitigation RPN remains high, escalate or loop back to step 2
Row header turns green when residual risk is acceptable (≤10)
Code: modules/RiskTemplates/DFMEATemplate/attachments/risksheet.json (0.70) · modules/Risks/DFMEA-CMP-PSU/attachments/risksheet.json (0.66) · datasets/sol-aero-ui-walkthrough/summary.md, navigation.md, dashboards/home-dashboard.md, dashboards/role-dashboards.md, dashboards/standards-compliance.md, risksheet-views/risksheet-views.md, work-item-types/data-model.md (0.63) · modules/RiskTemplates/SubSystem-FMEATemplate/attachments/risksheet.json (0.62) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.60) · modules/RiskTemplates/DFMEATemplate/attachments/risksheetTopPanel.vm, SubSystem-FMEATemplate/attachments/risksheetTopPanel.vm, System-FMEATemplate/attachments/risksheetTopPanel.vm, PFMEATemplate/attachments/risksheetTopPanel.vm, HazardTrackingTemplate/attachments/risksheetTopPanel.vm, DFMEATemplate/attachments/risksheetPdfExport.vm, SubSystem-FMEATemplate/attachments/risksheetPdfExport.vm, System-FMEATemplate/attachments/risksheetPdfExport.vm, PFMEATemplate/attachments/risksheetPdfExport.vm (0.59) · modules/RiskTemplates/DFMEATemplate/module.xml, modules/Risks/DFMEA-CMP-PSU/module.xml, modules/_default/WholeRTMSheet/module.xml, modules/Requirements/CUSTOMER-REQS/module.xml (representative of ~50 module.xml files across all spaces and templates) (0.58) · modules/Risks/COMPLIANCE-001/module.xml, modules/Risks/MIL-STD-882E-HTS-001/module.xml, modules/Risks/SEC-THREAT-001/module.xml, modules/Risks/SFMEA-SUB-001/module.xml, modules/Risks/SFMEA-SUB-002/module.xml, modules/Risks/SFMEA-SUB-003/module.xml (0.58) · modules/RiskTemplates/System-FMEATemplate/attachments/risksheet.json (0.58) · modules/RiskTemplates/PSSATemplate/attachments/risksheet.json (0.58)
