FMEA-MSR

FMEA-MSR (Monitoring and System Response) analyzes how safety-critical systems detect failures and respond to them. It extends the standard FMEA approach with ratings for monitoring capability and system response adequacy.

When to Use FMEA-MSR

Use FMEA-MSR when your system has:

• Active monitoring — Sensors, diagnostics, or software that detect failures in real time
• Automated responses — Systems that take action when a failure is detected (e.g., emergency braking, failsafe modes)
• Safety-critical functions — Where undetected failures could lead to harm

Common applications:

• Autonomous vehicle sensor systems
• Medical device monitoring (patient alarms, drug delivery oversight)
• Industrial safety interlocks
• Aerospace flight control diagnostics
• ADAS (Advanced Driver Assistance Systems)

AIAG-VDA Supplement

FMEA-MSR was introduced as a supplement to the AIAG & VDA FMEA Handbook specifically for systems where diagnostic monitoring and response are safety-critical.

Key Differences from Standard FMEA

FMEA-MSR replaces two of the three standard ratings:

Standard FMEA	FMEA-MSR	Focus
Severity (S)	Severity (S)	Same — impact of the failure (unchanged)
Occurrence (O)	Frequency (F)	How frequently the failure scenario occurs
Detection (D)	Monitoring (M)	How effectively the system monitors for and responds to the failure

Frequency (F) Rating

Replaces Occurrence. Rates how often the failure condition is expected to arise during system operation:

Rating	Frequency
10	Continuous or near-continuous
7-9	Frequent during operation
4-6	Occasional during operation
2-3	Rare during operation
1	Extremely unlikely during operation

Monitoring (M) Rating

Replaces Detection. Rates how well the system monitors for the failure and how effective its response is:

Rating	Monitoring Capability
10	No monitoring capability
7-9	Monitoring exists but response is inadequate or too slow
4-6	Monitoring detects the failure; response partially mitigates
2-3	Reliable monitoring with effective automated response
1	Continuous monitoring with immediate, fully effective response

Creating an FMEA-MSR Analysis

1. Navigate to FMEA Workspace → Advanced Mode
2. Click "New Analysis"
3. Select "FMEA-MSR" as the type
4. Fill in:
   • Component Name — The system being monitored (e.g., "Collision Detection System")
   • Monitoring Methods — How the system detects failures (e.g., "Radar, camera, ultrasonic")
   • System Response — What the system does when a failure is detected (e.g., "Emergency braking, driver alert")

MSR Worksheet

The FMEA-MSR has its own Worksheet sub-tab with MSR-specific columns:

Column	Description
Structure Element	System component
Function	What it should do
Failure Mode	How it can fail
Effect	Impact of failure
S	Severity (1-10)
Cause	Root cause
Monitoring Method	How the failure is detected
F	Frequency (1-10)
System Response	How the system reacts
M	Monitoring effectiveness (1-10)
AP	Action Priority

Action Priority for FMEA-MSR uses the same High/Medium/Low rules but substitutes F for O and M for D.

MSR XML Exchange

For interoperability with other FMEA tools, NirmIQ supports the VDA MSR 2.1.2 XML exchange format.

Import

1. Open the FMEA-MSR analysis
2. Click "Import" → "MSR XML"
3. Upload a .xml file conforming to VDA MSR 2.1.2
4. Review the parsed data
5. Confirm to import failure modes into the analysis

Export

1. Open the FMEA-MSR analysis
2. Click "Export" → "MSR XML"
3. The .xml file downloads in VDA MSR 2.1.2 format

This enables data exchange with tools like APIS IQ-FMEA, Plato SCIO, and other MSR-compatible software.

Example: Autonomous Emergency Braking

Component: Forward Collision Warning System
Monitoring: Front radar (77GHz) + stereo camera

Failure Mode: System fails to detect stationary vehicle ahead
Effect: Collision at full speed, potential fatality
Severity: 10

Cause: Radar return obscured by road spray
Frequency: 4 (occurs in heavy rain conditions)

Monitoring Method: Camera cross-validates radar, system self-test every 100ms
System Response: Driver alert at T-3s, pre-fill brakes at T-2s, emergency braking at T-1s
Monitoring: 3 (reliable monitoring with effective response)

Action Priority: HIGH (S=10)

Best Practices

1. Focus on monitoring gaps — The most critical items are those where Monitoring (M) is high (poor monitoring) and Severity is high
2. Document response times — Include specific timing in system response descriptions (e.g., "braking within 200ms")
3. Consider degraded modes — What happens when the primary monitoring fails? Document the backup response
4. Test monitoring paths — Verify that the monitoring method actually detects the failure in real-world conditions
5. Link to DFMEA — FMEA-MSR complements DFMEA; the design analysis identifies failures, MSR analyzes how they're detected and managed

What's Next?

• Advanced FMEA — Compare DFMEA, PFMEA, and FMEA-MSR
• FMEA Worksheet — Edit MSR failure modes in grid view
• Visual Diagrams — Process Flow and Failure Net visualizations
• Import & Export — Excel import/export options