Generated by GPT-5-mini| FMEA | |
|---|---|
| Name | Failure Modes and Effects Analysis |
| Othernames | FMEA |
| Type | Risk analysis technique |
| Developed | 1940s–1960s |
| Origin | United States |
| Disciplines | Industrial engineering, Reliability engineering |
FMEA is a systematic, structured technique for identifying potential failure modes, their causes, and effects on system performance across design, process, and service contexts. Used to prioritize risks and guide mitigation, it combines analytical, collaborative, and quantitative elements to reduce harm and improve reliability in complex systems. Practitioners apply it in engineering projects, manufacturing lines, healthcare settings, and software deployments to align safety, quality, and regulatory objectives.
FMEA originated as a proactive tool to forecast failures in products and processes, informing decision-makers in Ford Motor Company, General Motors, Boeing, NASA, and U.S. Department of Defense. It interfaces with complementary methods such as Fault tree analysis, Hazard and Operability Study, Root cause analysis, Six Sigma, and Total Quality Management. Variants include design- and process-centered forms, and it is taught in curricula at institutions like Massachusetts Institute of Technology, Stanford University, University of Michigan, and Georgia Institute of Technology.
The method’s antecedents trace to reliability engineering programs in the United States during World War II and the early Cold War, particularly within U.S. Air Force procurement and aerospace programs led by entities like North American Aviation and Lockheed. Systematic codification progressed with automotive quality control initiatives at Ford Motor Company and General Motors in the 1940s–1960s and later diffusion through standards bodies including Society of Automotive Engineers and International Organization for Standardization. High-profile implementations in projects at Boeing 747 development and Apollo program operations helped standardize templates and cross-functional team practices. Regulatory and industry adoption by Food and Drug Administration, European Medicines Agency, and International Electrotechnical Commission further institutionalized FMEA variants.
Core steps include function identification, failure mode enumeration, cause analysis, effect assessment, detection evaluation, and prioritization via scoring matrices. Common types are Design FMEA (DFMEA), Process FMEA (PFMEA), System FMEA, and Software FMEA, often integrated with Reliability-centered maintenance and Failure reporting, analysis, and corrective action system. Tools and notations derive from MIL-STD-1629A, AIAG manuals, and industry handbooks used by firms such as Toyota, Siemens, Honeywell, and General Electric. Multidisciplinary teams frequently include members from engineering groups at Tesla, Inc., Airbus, Raytheon Technologies, and IBM.
FMEA is applied across sectors: automotive supply chains in Toyota Production System implementations, aerospace certification for aircraft like the Airbus A320, medical device design overseen by Johnson & Johnson and Medtronic, pharmaceutical manufacturing regulated by FDA, and energy infrastructure managed by ExxonMobil and Siemens Energy. Healthcare systems employ FMEA in hospitals such as Mayo Clinic and Cleveland Clinic to evaluate clinical workflows, while software organizations including Google and Microsoft adapt FMEA concepts into reliability frameworks. Public-sector projects at NASA and U.S. Department of Transportation use FMEA alongside Probabilistic risk assessment for mission assurance and safety compliance.
Traditional FMEA uses ordinal scoring for Severity, Occurrence, and Detection, multiplied to yield a Risk Priority Number (RPN), a practice codified in guidance from AIAG and used by corporations like Ford Motor Company and General Motors. Alternative metrics include Criticality Index, Priority Risk Number, and Risk Coverage Gap analyses employed by Lockheed Martin and Boeing. Statistical integration with Weibull analysis, Monte Carlo simulation, and Bayesian methods enables probabilistic estimation in programs at NASA Jet Propulsion Laboratory and research at MIT. Some standards recommend thresholding, Pareto analysis, and linking scores to cost–benefit frameworks used in portfolio decisions at Procter & Gamble and 3M.
Effective implementation favors cross-functional teams with representation from design, manufacturing, quality, and service groups, following templates from Society of Automotive Engineers, AIAG, and ISO 9001 procedures. Best practices include defining system boundaries, maintaining traceable assumptions as in MIL-STD programs, using controlled vocabularies from company libraries at Toyota or Siemens, and integrating FMEA outputs with corrective action systems like Corrective and Preventive Action processes at Pfizer and Roche. Digital tools for execution range from spreadsheets to PLM systems by Siemens PLM and Dassault Systèmes, and collaboration platforms used at Amazon and Apple.
Critiques note subjectivity in scoring, inconsistent RPN interpretation, and potential for checklist-driven compliance rather than substantive risk reduction—issues raised in debates involving National Academy of Sciences reports and industry audits at Boeing and General Motors. RPN multiplication can mask trade-offs; reforms propose ranked-priority tables, fuzzy logic, and probabilistic risk metrics favored in studies at Stanford University and Carnegie Mellon University. Other limitations include resource intensity for large systems (observed in projects at NASA and Lockheed Martin), cultural resistance within organizations like General Electric historic case studies, and challenges integrating human factors emphasized by World Health Organization guidance for healthcare safety.
Category:Risk management