Table of Contents
Detection ratings in Failure Mode and Effects Analysis (FMEA) represent a critical component of risk assessment that helps organizations identify potential failures before they impact customers. Understanding how to accurately calculate and apply detection ratings is essential for building robust quality management systems and ensuring product reliability across industries.
What Are Detection Ratings in FMEA?
Detection ratings are ranking numbers associated with the best control from the list of detection-type controls, based on criteria from the detection scale. These ratings form one of three key components used to assess risk in FMEA, alongside severity and occurrence ratings.
The detection ranking considers the likelihood of detection of the failure mode or cause, according to defined criteria. Detection is a relative ranking within the scope of the specific FMEA and is determined without regard to the severity or likelihood of occurrence. This independence ensures that each dimension of risk receives appropriate attention during the analysis process.
The Detection Rating Scale
The detection scale ranges from 1 (always detected) to 10 (never detected) for each occurrence. This inverse relationship means that lower numbers indicate better detection capability, while higher numbers signal poor or nonexistent detection methods.
A low detection rating of 1-3 means the control system is highly effective and will almost identify the issue before it escapes. Conversely, a high detection rating of 8-10 means the failure is unable to be detected and it will detect when it reaches the customer.
Suggested ratings on a scale of 1 to 5 (or 10) include: 5 (9 or 10) zero probability of detecting the potential failure cause, 4 (7 or 8) close to zero probability of detecting potential failure cause, 3 (4, 5 or 6) not likely to detect potential failure cause, 2 (2 or 3) good chance of detecting potential failure cause, and 1 (1) almost certain to identify potential failure cause.
Detection in Design FMEA vs Process FMEA
Detection ratings apply differently depending on whether you’re conducting a Design FMEA (DFMEA) or Process FMEA (PFMEA). For Design FMEAs, detection is the ranking number corresponding to the likelihood that the current detection-type Design Controls will detect the failure mode or cause, typically in a timeframe before the product design is released for production.
For Process FMEAs, detection is the ranking number corresponding to the likelihood that the current detection-type Process Controls will detect the failure mode or cause, typically in a timeframe before the part or assembly leaves the manufacturing or assembly plant.
DFMEA detection focuses on design verification and validation methods which includes simulations, assembly tests and physical prototype/part testing. PFMEA detection focuses on process controls like inspection, error-proofing, process validation tests, in-process testing, and end-of-line checks.
The Role of Detection in Risk Priority Number Calculation
Severity, Occurrence, and Detection indexes are derived from the failure mode and effects analysis: Risk Priority Number = Severity x Occurrence x Detection. The RPN provides a numerical value that helps teams prioritize which failure modes require immediate attention and corrective action.
However, relying solely on RPN has limitations. The RPN should not be the only index used to evaluate the risk of each failure mode. The team should also use Severity, Occurrence, and Detection to prioritize risks. This multi-dimensional approach ensures that high-severity issues receive appropriate attention even when occurrence or detection ratings might result in a moderate RPN.
Understanding Action Priority (AP)
FMEA AP, or Action Priority, is a rating method introduced in the AIAG & VDA Failure Mode and Effects Analysis – FMEA Handbook that provides a priority level based on Severity, Occurrence, and Detection values. While the RPN is a risk assessment value based on Severity x Occurrence x Detection, AP was developed in order to give more emphasis to Severity first, then Occurrence, and then Detection.
Together with Severity and Occurrence, detection helps to arrange risks using the Action Priority. This approach addresses some of the mathematical limitations inherent in the RPN calculation method.
How to Calculate Detection Ratings: A Step-by-Step Process
Calculating detection ratings requires systematic evaluation of existing controls and their effectiveness at identifying potential failures. The process involves careful analysis of current detection methods and honest assessment of their capabilities.
Step 1: Identify Current Detection Controls
For each cause, the FMEA team assesses the detection ranking, which is the likelihood that the current detection-type controls will be able to detect the cause of the failure mode. Begin by documenting all existing detection methods, including inspection procedures, testing protocols, monitoring systems, and validation activities.
Detection controls can include various methods such as visual inspections, automated testing equipment, statistical process control, error-proofing devices (poka-yoke), prototype testing, simulation analysis, and end-of-line functional tests. Each control should be evaluated for its ability to detect the specific failure mode or cause under consideration.
Step 2: Evaluate Control Effectiveness
A suggested approach is assuming the failure has occurred and then assessing the capability of the detection-type design or process control to detect the failure mode or cause. This thought experiment helps teams realistically evaluate whether their controls would actually catch the problem.
Consider factors such as the timing of detection (in-station vs. downstream), the reliability of the detection method, whether detection is automated or manual, the frequency of inspection or testing, and whether the control can detect all instances of the failure or only a sample.
Step 3: Assign the Detection Rating
According to the AIAG-VDA standard, Detection rating is the number associated to the controls, and how effective the existing controls are in identifying a potential failure cause or mode. Use your organization’s detection rating table to assign the appropriate numerical value based on the control effectiveness assessment.
Downstream detection (Rating 4) means the failure is caught later, in-station detection (Rating 3) catches it at the operation where it occurs, poka-yoke (Rating 2) actively prevents or stops the error, and Rating 1 implies the failure cannot happen due to built-in design/process safeguards.
Step 4: Document the Rationale
Recording the reasoning behind each detection rating is essential for consistency and future reference. Documentation should include the specific controls evaluated, why a particular rating was assigned, any assumptions made during the assessment, and references to testing data or historical performance that supports the rating.
This documentation becomes invaluable when the FMEA is reviewed or updated, when team members change, or when explaining decisions to stakeholders and auditors.
Practical Examples of Detection Rating Assignment
Understanding how to apply detection ratings in real-world scenarios helps teams develop consistency and accuracy in their FMEA work.
Design FMEA Example
For a failure mode where a connector does not lock properly due to weak latch design, with current detection control of prototype testing with limited number of samples and latch force test done only at room temperature, since the test may not detect all weak latch cases, Detection rating is assigned 6 (moderate).
If later a 100% endurance test or simulation with field correlation is added, then Detection rating could be improved to 3. This example demonstrates how enhanced testing protocols can significantly improve detection capability.
Process FMEA Example
For an assembly process for automotive brake caliper with failure mode of piston not fully pressed (incomplete seating) caused by pressing force not sufficient or misalignment during pressing, with current detection control of in-station pressure test that detects leak immediately after pressing, the test is performed immediately after the operation with automatic in-station machine-based detection that detects the failure mode.
Detection rating is assigned 3 (High). The immediate, automated nature of this detection method provides strong capability to catch failures before they proceed to subsequent operations.
Common Challenges in Detection Rating Assignment
Teams frequently encounter difficulties when assigning detection ratings. Understanding these challenges helps organizations develop more effective FMEA processes.
Subjectivity and Inconsistency
One of the primary challenges is the subjective nature of detection rating tables. Different team members may interpret the same control effectiveness differently, leading to inconsistent ratings across similar situations. Organizations can address this by developing detailed, customized detection rating criteria specific to their processes and products, providing examples and case studies for reference, conducting calibration exercises where teams rate the same scenarios and discuss differences, and ensuring cross-functional representation on FMEA teams to bring diverse perspectives.
Overestimating Detection Capability
Teams sometimes assign overly optimistic detection ratings, assuming controls will work better than they actually do in practice. This can occur when relying on theoretical control capabilities rather than actual performance data, failing to account for human factors in manual inspection processes, not considering the impact of production volume on inspection effectiveness, or overlooking the possibility of multiple failures occurring simultaneously.
If there is no detection-type control for a given failure mode or cause, the detection ranking should be set to the highest level. This conservative approach ensures that the absence of controls is appropriately reflected in risk assessment.
Confusion Between Detection Types
Organizations must clearly distinguish between different types of detection. Detection before release to production or customer differs from detection during customer use, and detection of the failure mode versus detection of the root cause requires different approaches. Additionally, prevention controls versus detection controls serve fundamentally different purposes in risk management.
Strategies for Improving Detection Effectiveness
Reducing detection ratings requires implementing stronger controls that increase the likelihood of identifying failures before they escape to customers.
Implement Error-Proofing (Poka-Yoke)
Improving detection requires automation, error-proofing, and robust validation methods. Error-proofing devices prevent defects from occurring or make defects immediately obvious when they do occur. These mechanisms can include physical design features that prevent incorrect assembly, sensors that detect missing components or incorrect positioning, automated systems that stop production when parameters fall outside acceptable ranges, and visual management systems that make abnormalities immediately apparent.
Enhance Testing and Inspection Methods
Upgrading testing and inspection capabilities can significantly improve detection ratings. Consider implementing 100% automated inspection rather than sampling, using advanced measurement technologies such as vision systems or coordinate measuring machines, conducting testing under conditions that replicate actual use environments, and implementing statistical process control to detect trends before defects occur.
Moving from downstream detection to in-station detection provides faster feedback and prevents defective parts from proceeding through subsequent operations. This approach reduces waste and improves overall process efficiency.
Increase Inspection Frequency and Coverage
More frequent inspection or testing increases the likelihood of detecting failures. However, this approach must be balanced against cost and cycle time considerations. Strategies include implementing first-piece inspection for setup-related causes, conducting periodic audits of automated detection systems to ensure they remain effective, using layered process audits to verify that controls are functioning as intended, and establishing clear escalation procedures when detection systems identify potential issues.
Leverage Advanced Technologies
Modern technologies offer new opportunities for improving detection capability. Artificial intelligence and machine learning can identify patterns that indicate potential failures, Internet of Things (IoT) sensors provide real-time monitoring of critical parameters, predictive analytics can forecast when failures are likely to occur, and digital twins enable virtual testing and validation before physical production begins.
The Relationship Between Detection and Other FMEA Elements
Understanding how detection interacts with severity and occurrence helps teams make better risk management decisions.
Detection Cannot Reduce Severity
A key principle of FMEA is that severity cannot be reduced through detection or occurrence controls. The only way to reduce severity is to remove the risk through design changes. Detection only affects whether the failure is caught before reaching the customer; it doesn’t change the impact if the failure does occur.
This principle is crucial for prioritizing improvement efforts. High-severity failure modes should ideally be eliminated through design changes rather than relying solely on detection to prevent customer impact.
Detection is Independent of Occurrence
According to FMEA standards, Severity, Occurrence, and Detection are determined separately, without regard to one another. A failure mode might have low occurrence (happens rarely) but also have poor detection (difficult to catch when it does happen). Conversely, a common failure might have excellent detection capability.
This independence ensures that each dimension of risk receives appropriate consideration. Teams should not assume that rare failures don’t need good detection, or that common failures automatically have good detection.
Balancing Prevention and Detection
While detection is important, prevention is generally preferable. The hierarchy of controls in risk management prioritizes elimination of hazards, followed by substitution, engineering controls, administrative controls, and finally personal protective equipment or detection as the last line of defense.
In FMEA terms, this means that reducing occurrence through prevention controls is often more effective than relying solely on detection. However, detection remains essential as a backup when prevention controls fail or when elimination of the failure mode is not feasible.
Detection Rating in the AIAG-VDA FMEA Methodology
In the AIAG-VDA FMEA methodology, Detection plays an important role in the Risk Analysis step. The AIAG-VDA approach represents the harmonization of American and German FMEA standards, providing a globally recognized framework.
Step 5: Risk Analysis
Detection is assigned in Step 5 – Risk Analysis of the AIAG-VDA 7-Step approach, where first we identify the Current detection controls then we assign detection rating based on how strong our detection is. This step involves systematic evaluation of all existing controls and their effectiveness.
Step 6: Optimization
Detection is also assigned in Step 6 – Optimization of the AIAG-VDA 7-Step approach, where if existing detection is weak and there is a high action priority, the aim is to reduce that risk, and detection is one factor used to reduce risk.
If strong detection controls are added in optimization then the rating could go down and risk may decrease. This iterative process of assessment and improvement is fundamental to effective FMEA practice.
Best Practices for Detection Rating Management
Implementing these best practices helps organizations maximize the value of detection ratings in their FMEA processes.
Develop Clear, Customized Rating Criteria
While industry-standard detection rating tables provide a starting point, organizations benefit from developing criteria tailored to their specific processes and products. Customized criteria should reflect the types of controls actually used in your operations, account for industry-specific requirements and regulations, provide clear distinctions between rating levels, and include examples relevant to your products and processes.
Use Cross-Functional Teams
Effective detection rating requires input from multiple perspectives. Quality engineers understand inspection and testing methods, manufacturing engineers know the capabilities and limitations of production equipment, design engineers can explain intended functionality and potential failure modes, and operators provide practical insights into how controls work in daily practice.
This diverse input helps ensure that detection ratings reflect reality rather than assumptions.
Validate Ratings with Data
Whenever possible, support detection ratings with objective data. Historical defect detection rates show how often controls have actually caught failures in the past, capability studies demonstrate the measurement system’s ability to distinguish good from bad parts, and audit results reveal whether controls are consistently applied as intended.
Data-driven detection ratings are more credible and defensible than purely subjective assessments.
Review and Update Regularly
Detection ratings should not be static. Regular review ensures they remain accurate as processes change, new technologies become available, or historical performance data reveals gaps in detection capability. Establish a schedule for periodic FMEA review, trigger updates when process changes occur, incorporate lessons learned from escaped defects, and benchmark against industry best practices.
Train Team Members Consistently
Consistent application of detection ratings requires that all team members understand the methodology. Training should cover the purpose and principles of FMEA, how to interpret detection rating criteria, examples of rating assignment for common scenarios, and common pitfalls to avoid.
Regular refresher training helps maintain consistency as team membership changes over time.
Advanced Considerations for Detection Rating
As organizations mature in their FMEA practice, they may encounter more complex scenarios that require sophisticated approaches to detection rating.
Multiple Detection Controls
When multiple detection controls exist for a single failure mode, the team must decide how to assign the detection rating. The standard approach is to rate based on the best (most effective) control, assuming it will be the one that catches the failure. However, some organizations consider the combined effectiveness of multiple controls, recognizing that redundant detection provides additional assurance.
The key is to apply a consistent methodology across all failure modes in the FMEA.
Detection Timing Considerations
The timing of detection significantly impacts its effectiveness. In-station detection catches failures immediately at the operation where they occur, preventing defective parts from proceeding to subsequent operations. End-of-line detection catches failures before shipment but after significant value has been added. Post-delivery detection relies on customer feedback or warranty claims, representing the worst-case scenario.
Detection rating criteria should account for these timing differences, with earlier detection receiving better (lower) ratings.
Detection in Service
Some industries need to consider detection of failures after the product is in customer hands. This is particularly relevant for products with long service lives, safety-critical applications, or situations where in-service monitoring is feasible. In-service detection might include diagnostic systems that alert users to problems, scheduled maintenance inspections, or monitoring systems that predict failures before they occur.
Organizations using in-service detection should clearly define whether their detection ratings assess pre-delivery or post-delivery detection capability.
Common Mistakes to Avoid
Understanding common errors helps teams avoid pitfalls that undermine FMEA effectiveness.
Confusing Prevention with Detection
Prevention controls reduce the likelihood that a failure will occur (affecting occurrence rating), while detection controls identify failures that have occurred. Mixing these concepts leads to inaccurate ratings. For example, a robust design that prevents a failure mode is not a detection control—it’s a prevention control that should reduce occurrence rating instead.
Rating Based on Intended Rather Than Actual Performance
Detection ratings should reflect how controls actually perform, not how they’re supposed to perform in theory. If inspection procedures are defined but not consistently followed, if automated systems have high false-positive rates that lead operators to ignore alarms, or if measurement systems lack adequate resolution to detect the failure, then the detection rating should reflect these realities.
Ignoring Human Factors
Manual inspection and testing are subject to human limitations. Factors such as fatigue, distraction, training level, and workload affect detection capability. Detection ratings for manual controls should account for these factors rather than assuming perfect human performance.
Failing to Consider Failure Mode Characteristics
Some failure modes are inherently easier to detect than others. Catastrophic failures that cause complete loss of function are typically easier to detect than gradual degradation. Visible defects are easier to detect than internal defects. Detection ratings should reflect these inherent characteristics of the failure mode.
Integrating Detection Ratings with Continuous Improvement
Detection ratings provide valuable input for continuous improvement initiatives beyond the immediate FMEA process.
Identifying Improvement Opportunities
High detection ratings (poor detection capability) highlight opportunities for improvement. Prioritize improvement efforts based on the combination of severity, occurrence, and detection. High-severity failure modes with poor detection deserve immediate attention, even if occurrence is low.
Measuring Improvement Effectiveness
When improvements are implemented to enhance detection, the revised detection rating provides a measure of effectiveness. Track detection ratings over time to demonstrate continuous improvement, compare actual defect escape rates to predicted rates based on detection ratings, and use detection rating trends as a key performance indicator for quality management.
Sharing Best Practices
Effective detection controls identified in one FMEA may be applicable to other processes or products. Organizations should establish mechanisms to share successful detection methods across teams, document lessons learned from detection failures, and create a library of proven detection controls for common failure modes.
Software Tools for Detection Rating Management
Modern FMEA software provides capabilities that enhance detection rating accuracy and consistency. These tools offer standardized rating tables that ensure consistency across teams, automated calculation of RPN and Action Priority, tracking of detection rating changes over time, and links between detection controls and other quality system documents.
While software doesn’t replace the need for expert judgment in assigning detection ratings, it does provide structure and documentation that support effective FMEA practice.
Industry-Specific Detection Considerations
Different industries face unique challenges in detection rating that require tailored approaches.
Automotive Industry
The automotive industry has well-established FMEA practices with detailed detection rating criteria. Automotive FMEAs typically emphasize in-station detection and error-proofing, use specific rating criteria for different types of gauging and inspection, and require consideration of both manufacturing and assembly detection controls.
Medical Device Industry
Medical device manufacturers face stringent regulatory requirements that affect detection approaches. Detection controls must be validated and documented to regulatory standards, risk management must integrate with ISO 14971 requirements, and detection of failures that could affect patient safety receives highest priority.
Aerospace Industry
Aerospace applications involve complex systems with critical safety requirements. Detection often involves multiple layers of inspection and testing, non-destructive testing methods play a significant role, and traceability of detection activities is essential for certification.
Software Development
Software FMEAs require different detection approaches than hardware. Detection controls include code reviews, automated testing, static analysis tools, and beta testing programs. The challenge lies in detecting logic errors and edge cases that may not be apparent through normal testing.
The Future of Detection in FMEA
Emerging technologies and methodologies are changing how organizations approach detection in FMEA.
Artificial Intelligence and Machine Learning
AI and machine learning enable detection capabilities that were previously impossible. These technologies can identify subtle patterns that indicate impending failures, learn from historical data to improve detection accuracy over time, and adapt to changing conditions without manual reprogramming.
As these technologies mature, detection rating criteria will need to evolve to account for their unique capabilities and limitations.
Internet of Things and Real-Time Monitoring
IoT sensors enable continuous monitoring of products and processes, providing detection capabilities that extend beyond traditional inspection points. Real-time data allows for immediate detection of anomalies, predictive algorithms can forecast failures before they occur, and remote monitoring enables detection of in-service failures.
Digital Twins and Virtual Testing
Digital twin technology creates virtual replicas of physical products and processes, enabling detection of potential failures through simulation before physical production begins. This approach can significantly improve detection ratings for design FMEAs by identifying issues that would be difficult or expensive to detect through physical testing alone.
Conclusion: Building a Culture of Effective Detection
Accurate detection ratings are essential for effective FMEA and robust quality management. By understanding the principles of detection rating, implementing systematic calculation processes, avoiding common pitfalls, and continuously improving detection capabilities, organizations can significantly reduce the risk of failures reaching customers.
Success requires more than just following procedures—it demands a culture that values honest assessment of detection capabilities, invests in effective controls, and continuously seeks improvement. When detection ratings accurately reflect reality and drive meaningful improvements, FMEA becomes a powerful tool for enhancing product quality, customer satisfaction, and organizational success.
Organizations should view detection ratings not as a compliance exercise but as a strategic tool for understanding and managing risk. The insights gained from thorough detection analysis inform decisions about where to invest in quality controls, how to prioritize improvement efforts, and how to build more robust processes and products.
For additional resources on FMEA methodology and quality management, consider exploring the American Society for Quality and the Automotive Industry Action Group, which provide standards, training, and best practices for FMEA implementation. The U.S. Food and Drug Administration offers guidance on risk management for medical devices, while ISO standards provide internationally recognized frameworks for quality and risk management across industries.