Skip to main content

​
Before You Begin

Navigate to the relevant FMEA risksheet document (SFMEA or DFMEA). For component-level analysis, open the appropriate DFMEA document (e.g., Air Data Computer Interface (ADCI) - Component DFMEA). Switch to the Define Mitigations view — step 4 of the 9-view workflow.

​
Steps

​
1. Open the Define Mitigations View

In your DFMEA risksheet, click the view selector and choose Define Mitigations (step 4 of 7 in the visible progression). The risksheet displays five columns in the Mitigations group:
ColumnContent
Task IDRisk control identifier (e.g., RC-001)
TitleControl description
StatusImplementation lifecycle state
RequirementsAuto-populated from linked design/system requirements
VerificationAuto-populated test cases linked through requirements

​
2. Add a Risk Control to a Failure Mode

In the Task column for the target failure mode row, click the task picker to create or link a risk control work item. Fill in the required fields:
  • Title — describe the specific control action (e.g., “Implement watchdog timer for sensor timeout detection”)
  • Status — set the initial lifecycle state
Use a description that connects the control to its failure mode cause. This makes requirements traversal readable when the Requirements column renders linked items automatically.

​
3. Set the Implementation Status

Each risk control tracks a four-state lifecycle: Not Started → In Progress → Implemented → Verified Set the status to Not Started when first creating the control. Update it as implementation progresses.
The FMEA Summary Report aggregates controls by status. Controls left at Not Started at time of certification review are flagged as open actions. Update status promptly as work progresses.
The Requirements column renders automatically — it traverses back-links from the risk control to any linked sysReq or desReq work items. To establish this link, open the risk control work item and add links to the relevant system or design requirements using the standard Polarion link role.
The exact UI steps for linking requirements to risk controls from within the risksheet picker may vary. If the Requirements column shows empty after linking, open the risk control item directly and verify the requirement link is saved.

​
5. Verify Test Coverage Appears

Once requirements are linked to the risk control, the Verification column auto-populates with any test cases linked to those requirements. This creates the full traceability chain: diagram No manual entry is needed for the Requirements or Verification columns — they reflect the linked data automatically.

​
6. Score Post-Mitigation RPN

After adding controls, move to Step 5: Verify Controls and then Step 6: Final Risk Evaluation to enter post-mitigation Occurrence and Detection scores. The post-mitigation RPN (commonRpnNew) is calculated automatically:
RPN RangeColorRisk Level
≤ 10GreenLow
11–30YellowMedium
> 30RedHigh
All failure modes should reach a post-mitigation RPN of ≤ 10 (green) before the DFMEA document is submitted for review. Red rows in the Final Risk Evaluation view are flagged automatically.

​
7. Check Cascading to Subsystem SFMEA

For system-level SFMEA documents, risk controls assigned at the subsystem level are linked via the causes back-link role to parent failure modes. Verify the cascade is intact by opening the parent SFMEA and confirming child subsystem rows show populated control status.
The risksheet configuration for each DFMEA instance (e.g., PSU, BITE, NVM) is independent of the template. If you need to add a new column or modify column behavior, each instance document must be updated separately — changes to the template do not propagate automatically.

​
Verification

You should now see the Status column updated on your risk control, the Requirements column showing linked requirement IDs, and the Verification column displaying associated test cases. The post-mitigation RPN cell in the Final Risk Evaluation view should recalculate with the updated color band.

​
See Also

Code: 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.50) · modules/RiskTemplates/DFMEATemplate/attachments/risksheet.json (0.50) · 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.49) · modules/Risks/DFMEA-CMP-PSU/attachments/risksheet.json (0.43) · .polarion/pages/spaces/Requirements/Home/page.xml, Design/Home/page.xml, Risks/Home/page.xml, Testing/Home/page.xml, Risks/FMEA Reports/page.xml, Documentation/Home/page.xml, Documentation/Powersheet Help Redirect/page.xml, RiskTemplates/Home/page.xml (0.42) · .polarion/tracker/fields/severity-enum.xml, status-enum.xml, priority-enum.xml, implementationStatus-enum.xml, riskSpecification-document-status-enum.xml (0.42) · modules/RiskTemplates/CCATemplate/attachments/risksheet.json (0.41) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.41) · modules/RiskTemplates/System-FMEATemplate/attachments/risksheet.json (0.41) · modules/RiskTemplates/SubSystem-FMEATemplate/attachments/risksheet.json (0.40)