Skip to main content

​
Prerequisites

​
How Mitigation Tasks Work in DFMEA

In the DFMEA risksheet, mitigation actions are implemented as task links to task work items connected via the mitigates link role. These tasks represent the corrective or preventive actions taken to reduce the failure mode’s occurrence or improve its detection. diagram In the DFMEA risksheet, locate the mitigation task columns:
ColumnFieldPurpose
Task IDtask.$item (taskLink)Links to the mitigation task work item
Task Titletask.titleDisplays the task name
Task Statustask.statusShows the task implementation status
To create a new mitigation task:
  1. Click the Task ID cell for the target failure mode row
  2. Select Create new to create a new task work item
  3. Enter a descriptive title for the mitigation action
  4. Save — the task is created and linked via the mitigates role
To link an existing task:
  1. Click the Task ID cell
  2. Search for the existing task or risk control
  3. Select it to establish the link
DFMEA mitigation tasks are generic task work items linked through the mitigates role. This differs from HARA, which links specifically to riskControl items in the Risk Control Plan document. You can link either type depending on your workflow.

​
Step 2: Document the Mitigation Action

After creating the task, ensure the following fields are complete:
  1. Title: A clear, actionable description of the mitigation measure
  2. Status: Track implementation progress through the task workflow
Example mitigation actions:
Failure ModeMitigation ActionType
Delivers incorrect dosage volumeAdd redundant flow sensor with cross-check algorithmDesign change
Fails to detect occlusionImplement pressure threshold alarm with 200ms responseProtective measure
Displays inaccurate flow rateAdd IFU warning about calibration requirementsInformation for safety

​
Step 3: Assign Multiple Actions (If Needed)

A single failure mode may require multiple mitigation actions. To add additional tasks:
  1. Click the task column on the same failure mode row
  2. Create or link another task
  3. Each task appears as a separate entry
Consider whether the mitigation addresses occurrence (preventing the failure), detection (catching the failure earlier), or both. Effective DFMEA mitigation typically targets the highest-impact factor.

​
Step 4: Verify Requirements Traceability

The risksheet automatically populates two server-rendered traceability columns:

​
Requirements Column

Shows system requirements (sysReq) and design requirements (desReq) linked to the mitigation task:
  • The column traverses task > back-links > sysReq/desReq work items
  • Requirements appear automatically when they are linked to the task in Polarion

​
Requirement Verification Column

Shows test cases verifying the linked requirements:
  • Performs a two-hop traversal: task > requirements > test cases
  • Displays verification test cases with their parent requirement reference
  • Provides end-to-end traceability from failure mode through to verification evidence
These columns are server-rendered using Velocity templates. They update automatically as requirements and test cases are linked in Polarion — no manual entry in the risksheet is needed.

​
Step 5: Track Mitigation Status

Monitor the Task Status column to track implementation:
  1. New tasks start in the default workflow state
  2. As the team implements the mitigation, update the task status through the Polarion workflow
  3. The risksheet reflects the current status in real time

​
What Happens Next

After mitigation actions are defined and implemented:
  1. Re-score occurrence and detection with the mitigations in place — see Evaluate Post-Mitigation RPN
  2. Verify requirements coverage through the PowerSheet RTM views to ensure all controls have implementing requirements
  3. Check HARA alignment — if the failure mode is linked to HARA risk records, verify that the HARA risk controls are consistent with the DFMEA mitigations
DFMEA risksheet configuration (DFMEATemplate/risksheet.json), failure mode custom fields (failureMode-custom-fields.xml), Risk Control Plan configuration (RiskControlPlanTemplate/risksheet.json), UI walkthrough (risksheet-views.md).