Failure Mode and Effects Analysis (FMEA) represents a systematic, proactive approach to identifying potential failures in products, processes, and systems before they occur. System FMEA specifically focuses on analyzing failures at the system level, examining how different subsystems and components interact and where these interactions might lead to problems. This comprehensive guide will walk you through the process of conducting a System FMEA, providing you with practical knowledge to improve reliability and reduce risk in your organization.
Understanding System FMEA
System FMEA differs from other types of FMEA by examining failures at the highest level of product or system architecture. While Design FMEA focuses on component-level failures and Process FMEA examines manufacturing processes, System FMEA evaluates how subsystems interact within the complete system. This holistic perspective helps identify failure modes that might not be apparent when examining individual components in isolation. You might also enjoy reading about How to Create an Effective To-Be Process: A Complete Guide to Process Optimization.
The primary objective of System FMEA is to identify potential system-level failures, assess their impact on overall system performance, and implement corrective actions to prevent these failures from reaching customers. This methodology proves particularly valuable in complex systems where multiple subsystems must work together seamlessly, such as automotive systems, medical devices, aerospace equipment, and industrial machinery. You might also enjoy reading about How to Master Inferential Statistics: A Complete Guide for Data-Driven Decision Making.
When to Conduct System FMEA
System FMEA should be initiated early in the design phase, ideally during the conceptual design stage when changes are less costly to implement. The analysis remains a living document throughout the product lifecycle, requiring updates when design changes occur, new failure modes are discovered, or operating conditions change. Organizations typically conduct System FMEA before proceeding to Design FMEA, ensuring that system-level interactions are properly understood and addressed.
Step-by-Step Process for Conducting System FMEA
Step 1: Assemble Your Cross-Functional Team
Begin by gathering a diverse team with expertise across different areas of your system. Your team should include design engineers, quality engineers, reliability experts, customer service representatives, and subject matter experts familiar with system operations. A typical team consists of five to eight members who can contribute unique perspectives on potential failure modes.
Step 2: Define the System and Its Boundaries
Clearly establish what constitutes your system and where its boundaries lie. Create a block diagram showing all major subsystems and their interfaces. For example, if analyzing an automotive braking system, your subsystems might include the brake pedal assembly, hydraulic system, anti-lock braking system (ABS), brake calipers, and electronic control unit. Document all inputs, outputs, and interactions between subsystems.
Step 3: Identify System Functions
List all functions that your system must perform to meet customer requirements. Be specific and measurable. Using our braking system example, functions might include:
- Reduce vehicle speed from 60 mph to 0 mph within 150 feet
- Maintain directional stability during emergency braking
- Prevent wheel lock-up on slippery surfaces
- Provide consistent pedal feel across temperature ranges
- Alert driver to system malfunctions
Step 4: Identify Potential Failure Modes
For each system function, brainstorm all possible ways the system could fail to perform that function. A failure mode describes how the system could potentially fail. Consider complete failures, partial failures, intermittent failures, and performance degradation. In our braking system example, potential failure modes might include:
- Inadequate braking force generated
- Delayed brake response time
- Uneven braking between wheels
- ABS system fails to activate
- Brake pedal feels spongy or unresponsive
Step 5: Determine Potential Effects of Failure
Analyze what happens when each failure mode occurs. Effects should be described from the customer perspective and in terms of system performance. Consider both immediate and downstream effects. For inadequate braking force, effects might include increased stopping distance, potential collision with obstacles, customer injury, property damage, and regulatory non-compliance.
Step 6: Assign Severity Ratings
Evaluate the seriousness of each failure effect using a severity scale from 1 to 10, where 10 represents the most severe consequence. This rating reflects the impact on the customer and system performance.
Sample severity scale:
- 9-10: Hazardous, may endanger operator or violate regulations
- 7-8: High severity, system inoperable with significant performance loss
- 5-6: Moderate severity, reduced performance but system remains functional
- 3-4: Low severity, minor impact on performance
- 1-2: Minimal severity, customer may not notice
For inadequate braking force leading to potential collision, you would assign a severity rating of 10.
Step 7: Identify Potential Causes
Determine the root causes that could lead to each failure mode. Be specific and trace back to fundamental design weaknesses or system vulnerabilities. For inadequate braking force, potential causes might include hydraulic fluid leak, worn brake pads, air in hydraulic lines, master cylinder failure, or electronic control unit malfunction.
Step 8: Assign Occurrence Ratings
Estimate the likelihood of each cause occurring using a scale from 1 to 10, where 10 represents very high probability. Base these ratings on historical data, test results, warranty claims, or engineering judgment when data is unavailable.
Sample occurrence scale:
- 9-10: Very high, failure almost certain (more than 1 in 10)
- 7-8: High, repeated failures likely (1 in 20 to 1 in 100)
- 5-6: Moderate, occasional failures (1 in 100 to 1 in 1,000)
- 3-4: Low, relatively few failures (1 in 10,000 to 1 in 100,000)
- 1-2: Remote, failure unlikely (less than 1 in 1,000,000)
Step 9: Identify Current Controls
Document existing design features, tests, inspections, or procedures that either prevent the failure cause from occurring or detect the failure before it reaches the customer. For hydraulic fluid leaks, current controls might include seal integrity testing, pressure drop monitoring, fluid level sensors, and visual inspection protocols.
Step 10: Assign Detection Ratings
Rate the effectiveness of current controls in detecting the failure cause or mode before the system reaches the customer. Use a scale from 1 to 10, where 10 indicates detection is nearly impossible.
Sample detection scale:
- 9-10: Detection almost impossible, no known controls
- 7-8: Poor detection capability, controls unreliable
- 5-6: Moderate detection capability, controls may detect failure
- 3-4: Good detection capability, high likelihood of detection
- 1-2: Excellent detection, failure will almost certainly be detected
Step 11: Calculate Risk Priority Number (RPN)
Multiply Severity × Occurrence × Detection to calculate the RPN for each failure mode. This number ranges from 1 to 1,000 and helps prioritize which failure modes require immediate attention.
Example calculation:
Failure Mode: Inadequate braking force
Severity: 10 (potential collision, injury)
Occurrence: 3 (low probability with current design)
Detection: 4 (good detection through testing)
RPN: 10 × 3 × 4 = 120
Step 12: Develop and Implement Action Plans
For high-RPN items (typically RPN greater than 100) or any failure with severity rating of 9 or 10, develop specific action plans to reduce risk. Actions might include design changes, additional testing, enhanced inspection procedures, or improved detection methods. Assign responsibility and target completion dates for each action.
Step 13: Recalculate RPN After Actions
After implementing corrective actions, reassess the severity, occurrence, and detection ratings. Calculate new RPN values to verify that risk has been adequately reduced. Continue this improvement cycle until acceptable risk levels are achieved.
Sample System FMEA Data Set
Consider a simplified example for an automotive climate control system:
Function: Maintain cabin temperature between 68-72°F
Failure Mode: Insufficient cooling capacity
Effect: Cabin temperature exceeds 72°F, customer discomfort, potential safety issue in extreme heat
Severity: 7
Cause: Refrigerant leak in AC system
Occurrence: 5
Current Controls: Pressure testing during assembly, refrigerant level sensors
Detection: 3
RPN: 7 × 5 × 3 = 105
Recommended Action: Implement enhanced leak testing using helium detection, add redundant pressure monitoring, improve seal design
Responsibility: Design Engineering Team
Target Date: Prior to production validation testing
Best Practices for System FMEA Success
To maximize the effectiveness of your System FMEA efforts, schedule regular team meetings to maintain momentum and ensure consistent participation. Use historical data from warranty claims, field failures, and customer complaints to inform your ratings and validate assumptions. Focus on preventing high-severity failures first, even if their RPN is not the highest, as customer safety should always take priority over statistical rankings.
Maintain your FMEA as a living document, updating it whenever design changes occur, new information becomes available, or actual field performance differs from predictions. Integrate System FMEA findings into your overall quality planning process, using insights to inform testing strategies, validation plans, and quality control procedures.
Common Pitfalls to Avoid
Many organizations fall into the trap of treating FMEA as a one-time exercise or compliance checkbox rather than a continuous improvement tool. Avoid using generic ratings without supporting data or rationale. Do not allow the process to become overly bureaucratic; focus on meaningful analysis rather than documentation for its own sake. Ensure that recommended actions are specific, measurable, and actually implemented rather than simply documented and forgotten.
Enhance Your Skills Through Professional Training
Mastering System FMEA requires both theoretical knowledge and practical application. While this guide provides a solid foundation, becoming proficient in FMEA and related quality methodologies requires hands-on practice and expert guidance. Lean Six Sigma training programs offer comprehensive instruction in System FMEA alongside other powerful quality tools and techniques that can transform your organization’s approach to quality and reliability.
Through structured Lean Six Sigma training, you will gain deeper insights into statistical analysis, root cause investigation, process improvement, and risk management. You will learn how to integrate System FMEA with other quality planning tools such as Quality Function Deployment (QFD), Control Plans, and Design of Experiments (DOE). Professional certification demonstrates your commitment to quality excellence and significantly enhances your career prospects in quality management, engineering, and operations roles.
The investment in Lean Six Sigma training pays dividends throughout your career, providing you with a structured methodology for solving complex problems, reducing defects, and improving customer satisfaction. You will join a global community of quality professionals who share best practices and support each other’s continuous improvement journey.
Enrol in Lean Six Sigma Training Today and take the next step in your professional development. Whether you are just beginning your quality journey or seeking to formalize and expand your existing knowledge, Lean Six Sigma certification provides the credentials, skills, and confidence you need to drive meaningful improvements in your organization. Start your transformation today and become the quality leader your organization needs to compete in an increasingly demanding marketplace.
