FMEA: Identifying and preventing risks early

Von David Leimann
Teile diesen Beitrag
Miniature figures examining a bar chart with error bars comparing product risk factors

FMEA (Failure Mode and Effects Analysis) is a proven method for systematically identifying potential failures in product development, processes, and systems before they occur. In product development, quality management, and complex engineering projects, FMEA helps assess risks precisely and define targeted countermeasures. For start-ups and mid-sized companies developing innovative products, FMEA provides a structured foundation to minimize development risks, reduce costs, and accelerate time to market.

What is FMEA?

The abbreviation FMEA stands for Failure Mode and Effects Analysis, known in German as Fehlermöglichkeits- und Einflussanalyse. It is a systematic risk analysis method designed to identify potential sources of failure at an early stage, evaluate their effects, and derive preventive actions.

The core idea behind FMEA is simple. Instead of fixing problems only after they occur, failures are anticipated during development or planning. This saves time, reduces costs, and sustainably improves product quality.

FMEA answers three fundamental questions:

  1. What can go wrong? Identification of potential failures
  2. Why can it go wrong? Analysis of root causes
  3. What will we do about it? Definition of prevention and detection actions

This structured approach makes FMEA an essential tool in modern product development, especially for technically demanding systems where failures can have serious consequences.

Why is FMEA important in product development?

 

As innovative technical products evolve, complexity continues to increase. Components, materials, manufacturing processes, and system integration must work together seamlessly. At the same time, requirements for safety, quality, and reliability are rising.

FMEA supports development teams in navigating this complexity systematically. It forces a precise examination of potential failure sources and creates transparency around risks that might otherwise be overlooked.

Concrete benefits of FMEA:

  • Early failure prevention: Issues are identified before they arise in production or at the customer.
  • Cost reduction: Rework, recalls, and warranty cases are minimized.
  • Higher product quality: Weak points are identified and corrected in a targeted way.
  • Improved documentation: FMEA creates a traceable knowledge base for future projects.
  • Compliance with standards: Many industries, such as automotive, medical technology, and aerospace, require FMEA as part of quality management.

For start-ups and SMEs working with limited resources, FMEA is an effective instrument to manage development risks in a controlled way and reach product maturity efficiently.

Failure Mode and Effects Analysis: The core principles

Team analyzing charts and figures in a business report spread across the table

Failure Mode and Effects Analysis is based on a structured procedure that is divided into several steps. The goal is to systematically capture potential failures, analyze their effects and causes, and prioritize actions.

The three key evaluation criteria in FMEA:

  1. Severity (S): How serious is the effect of the failure for the customer or the system?
  2. Occurrence (O): How likely is it that the failure will occur?
  3. Detection (D): How likely is it that the failure will be detected before delivery?

Each criterion is rated on a scale from 1 to 10. Multiplying them yields the Risk Priority Number (RPN):

RPN = S × O × D

The higher the RPN, the more urgent the need for action. Typically, actions are defined and implemented for all failures with an RPN above a specified threshold, such as 100 or 125.

FMEA is not a one-time activity, but a living process. It is continuously updated when designs change, new insights emerge, or actions have been implemented.

Types of FMEA: Which variants exist?

Depending on the application area and development phase, FMEA is divided into different types. Each variant has a specific focus and is suited to different questions.

System FMEA

System FMEA looks at the overall system and analyzes interactions between components, subsystems, and interfaces. It is often used in early development phases to identify system-wide risks before detailed design or manufacturing decisions are made.

Typical applications: Vehicle systems, powertrains, complex machinery, electronic systems.

Design FMEA

Design FMEA focuses on the product itself and investigates potential failures in design, material selection, geometry, or functional behavior. It is carried out by development engineers to ensure the product meets required specifications and remains robust under load.

Typical applications: Component development, prototyping, CAD design, material selection.

Process FMEA

Process FMEA analyzes manufacturing and assembly processes. The goal is to identify failures that can occur during production, such as incorrect assembly, tool wear, tolerance deviations, or insufficient inspection methods.

Typical applications: Series production, assembly lines, quality control, supply chain management.

Additional variants

Depending on the industry and application, there are specialized FMEA variants, such as FMEA-MSR (Monitoring and System Response) for safety-critical systems or Software FMEA for software development.

Process FMEA: Preventing failures in manufacturing

Process FMEA is particularly relevant for companies that manufacture products in series or must manage complex assembly processes. While Design FMEA examines the product itself, Process FMEA analyzes the steps required to produce the product.

Typical failure sources in Process FMEA:

  • Incorrect tool selection or tool wear
  • Insufficient training of assembly personnel
  • Faulty material feeding or storage conditions
  • Inadequate inspection methods or missing inspection points
  • Process variability, such as temperature, pressure, or cycle time

Process FMEA helps identify these risks and define actions that ensure production remains stable, repeatable, and free of defects. It is closely linked to methods such as SPC (Statistical Process Control) and Poka-Yoke (error prevention through design).

For start-ups moving from prototyping to series production, Process FMEA is an important tool for validating manufacturing readiness and preventing quality issues early.

FMEA workflow: The most important steps

Conducting an FMEA follows a structured workflow that ensures all relevant failure sources are captured and evaluated. The process is typically carried out by an interdisciplinary team to incorporate different perspectives.

Step 1: Preparation and team formation

First, all necessary documents are collected, such as CAD models, specifications, process descriptions, standards, and experience from previous projects. An interdisciplinary team from development, manufacturing, quality assurance, and, where applicable, external experts is formed.

Step 2: System analysis and structuring

The system, product, or process is broken down into its elements and described functionally. Which functions does each component fulfill, and which requirements apply? This structure forms the basis for later failure analysis.

Step 3: Identification of potential failures

For each function or process step, possible failures are identified. The key question is what can go wrong. Examples include a component cracking, a weld seam leaking, or a valve not closing fully.

Step 4: Root cause analysis

For each identified failure, the possible causes are determined. The key question is why the failure can occur. Examples include material defects, incorrect sizing, or insufficient testing.

Step 5: Rating according to S, O, D

Each failure is rated in terms of severity, occurrence, and detection. This yields the Risk Priority Number (RPN).

Step 6: Defining actions

For failures with a high RPN, actions are defined, such as design changes, additional inspections, process adjustments, or training. Responsibilities and deadlines are assigned.

Step 7: Implementation and re-evaluation

After actions are implemented, the FMEA is updated and the RPN is recalculated. The goal is to continuously reduce risk.

Step 8: Documentation and continuous maintenance

The FMEA is documented and serves as a knowledge base for future projects. It is continuously updated when changes occur or new insights become available.

FMEA example: Practical application in product development

To make FMEA more tangible, consider a practical example from the development of a flow-carrying component, such as a valve for a hydrogen combustion system (H2ICE).

Starting situation:

An engineering company develops a novel valve for a hydrogen combustion system (H2ICE). The valve must withstand high pressures, open and close precisely, and remain leak-tight over the long term.

FMEA execution (excerpt):

Component or Function Potential Failure Effect of Failure Severity (S) Cause of Failure Occurrence (O) Detection (D) RPN Action
Valve seat Leakage Hydrogen escape, safety risk 10 Material defect, incorrect surface finish 5 4 200 CFD analysis of pressure distribution, material inspection, surface optimization
Valve spring Spring fracture Valve does not close, engine failure 9 Overload, material fatigue 3 6 162 FEM analysis, durability testing, material change
Seal Wear Leakage, performance loss 8 High temperatures, chemical reaction with H2 6 5 240 Material selection (H2 resistant), temperature analysis, prototype testing

Actions:

  1. CFD simulation: Flow and pressure distribution in the valve are analyzed virtually to identify critical areas.
  2. FEM analysis: Mechanical loads on the valve spring are calculated to evaluate oversizing or a material change.
  3. Material selection: Seal materials are tested for hydrogen resistance and temperature durability.
  4. Prototype testing: Functional prototypes are validated on a test bench to verify the actions.

After implementing the actions, the RPN drops significantly, and the valve achieves the required reliability.

This example shows how FMEA systematically identifies risks and derives targeted engineering actions. Especially when combined with simulation methods such as CFD and FEM and with prototype testing, FMEA becomes a powerful tool in product development.

FMEA combined with modern engineering methods

Classic FMEA is increasingly combined with digital methods and AI-supported approaches to assess risks even more precisely and derive actions more efficiently.

Simulation and FMEA:

Modern simulation tools such as CFD (Computational Fluid Dynamics) or FEM (Finite Element Method) make it possible to investigate potential failure sources virtually at an early stage. Instead of relying on experience and estimates, engineers can generate precise data on loads, flows, temperatures, or pressure distributions. These insights flow directly into the FMEA and increase the accuracy of the assessment.

Example: A CFD simulation shows that flow separation in the valve leads to increased wear. This finding is documented in the FMEA, severity is rated higher, and geometry optimization is defined as an action.

AI and machine learning:

Data-driven methods such as machine learning can analyze historical FMEA data, detect patterns, and make predictions about failure likelihoods. Surrogate models trained on simulation data enable rapid evaluation of design variants and support risk analysis.

Prototyping and validation:

FMEA identifies critical areas that must be validated specifically during the prototyping phase. Through rapid prototyping, 3D printing, and functional testing, actions can be verified quickly and the FMEA can be improved iteratively.

This combination of FMEA, simulation, AI, and prototyping accelerates product development, reduces costs, and sustainably increases product quality.

Challenges and common mistakes in FMEA

Laptop displaying a 3D pie chart presentation projected on a screen in the background

Despite its advantages, FMEA is not always implemented optimally in practice. Common challenges include:

Insufficient team composition:

FMEA relies on interdisciplinary expertise. If important perspectives, such as manufacturing or quality assurance, are not included, failure sources remain undiscovered.

Superficial analysis:

If FMEA is treated as a purely formal checkbox exercise, potential failures are not analyzed thoroughly enough. Ratings are set arbitrarily or too optimistically.

Lack of updates:

FMEA is a living process. If design or process changes are not incorporated, the FMEA loses its value.

Unclear responsibility for actions:

Actions without clear owners and deadlines are often not implemented. The FMEA then remains ineffective.

Excessive complexity:

For very complex systems, the FMEA can become difficult to manage. A clear structure helps, and in some cases splitting the work into multiple FMEAs, such as system, design, and process, is beneficial.

When is FMEA worth it for start-ups and SMEs?

Start-ups and small to mid-sized companies often ask whether the effort required for an FMEA is justified. The answer depends on several factors.

FMEA is especially worthwhile when:

  • The product is safety-critical, such as in automotive, medical technology, or aerospace.
  • Quality requirements are high and failures are expensive.
  • Complex systems or processes are being developed.
  • Standards or customers explicitly require FMEA.
  • The company is transitioning from prototypes to series production.

Even when there is no formal requirement, a lean FMEA can provide valuable insights and minimize development risks. Especially when combined with modern simulation methods and prototyping, FMEA becomes an efficient tool that saves costs and accelerates market readiness.

Conclusion: FMEA as a strategic tool for safe product development

FMEA is far more than a formal quality tool. It is a systematic method for identifying risks early, evaluating them precisely, and reducing them effectively. In modern product development, where complexity, safety requirements, and time to market continue to increase, FMEA provides a structured foundation for steering development processes and preventing failures before they occur.

For start-ups and SMEs operating with limited resources, FMEA is a powerful instrument for managing development risks in a controlled way. Combined with simulation, prototyping, and data-driven methods, FMEA becomes a strategic tool that not only improves product quality but also reduces costs and accelerates product launch.

Would you like to apply FMEA in your development project, or do you need support with risk analysis, simulation, or prototype development? Felsaris supports you from concept phase through to series readiness. Schedule a non-binding consultation and find out how we can make your product development safer, faster, and more efficient.

Frequently asked questions about FMEA

What does FMEA mean and what does the abbreviation stand for?

FMEA stands for Failure Mode and Effects Analysis, known in German as Fehlermöglichkeits- und Einflussanalyse. It is a systematic risk analysis method that identifies potential failures in products, processes, or systems early, evaluates them, and derives actions to prevent them.

What types of FMEA are there?

The main types of FMEA are System FMEA (analysis of the overall system), Design FMEA (analysis of product design), and Process FMEA (analysis of manufacturing and assembly processes). Depending on the application, there are additional specialized variants such as Software FMEA or FMEA-MSR.

How is the Risk Priority Number (RPN) calculated?

The RPN is calculated by multiplying the three rating criteria: RPN = Severity (S) × Occurrence (O) × Detection (D). Each criterion is rated on a scale from 1 to 10. The higher the RPN, the more urgent the need for action.

When should an FMEA be carried out?

FMEA should be carried out as early as possible in the development phase, ideally already during the concept stage. It is updated continuously when designs change, new insights emerge, or actions are implemented. FMEA is also useful when processes change or new manufacturing methods are introduced.

How do Design FMEA and Process FMEA differ?

Design FMEA analyzes the product itself and investigates failures in design, material selection, or functional behavior. Process FMEA, in contrast, looks at manufacturing and assembly processes and identifies failure sources that can occur during production, such as incorrect assembly or insufficient inspection methods.

What benefits does FMEA offer in product development?

FMEA enables early failure prevention, reduces costs through fewer rework loops and recalls, increases product quality, improves documentation, and supports compliance with standards and customer requirements. It creates transparency around risks and supports well-founded development decisions.

Can FMEA be combined with simulation methods?

Yes, combining FMEA with simulation methods such as CFD (Computational Fluid Dynamics) or FEM (Finite Element Method) significantly improves the accuracy of risk assessment. Simulations provide precise data on loads, flows, or temperatures that can be incorporated directly into the FMEA and improve the rating of severity and occurrence.

How much effort does it take to conduct an FMEA?

The effort depends on the complexity of the product or process. For simple components, a lean FMEA can be completed in a few hours, while complex systems require several workshops and detailed analyses. In most cases, the benefit clearly outweighs the effort, especially when failures are avoided early.

Link copied ✅