Failure Mode and Effects Analysis (FMEA)

Definition

Failure Mode and Effects Analysis (FMEA) is a structured risk analysis method used to identify potential failure modes in a product, process, or system, assess the effects and causes of those failures, and prioritize preventive or corrective action based on risk severity.

What is Failure Mode and Effects Analysis (FMEA)?

FMEA examines what could go wrong, how serious the consequence would be, how likely the cause is to occur, and how likely current controls are to detect the issue before it reaches the customer or next process step. That makes it both a design review tool and a process control tool.

The method works through cross functional review. Teams define the item or process being analyzed, list possible failure modes, identify effects and causes, assess current controls, assign ratings, and prioritize action. The result is a documented risk picture that guides process redesign, control strengthening, and supplier quality planning.

FMEA is used in manufacturing, product development, automotive, aerospace, medical devices, industrial equipment, and supplier quality management where prevention is cheaper and safer than reacting after failure occurs.

How FMEA Is Calculated

Traditional FMEA often uses a Risk Priority Number, or RPN, calculated as Severity × Occurrence × Detection. Each factor is usually rated on a numeric scale, often from 1 to 10, where higher numbers indicate greater severity, higher frequency, or poorer detectability. The higher the RPN, the more urgent the need for action.

Many organizations now place stronger emphasis on severity and action priority rather than relying on RPN alone, because two failure modes can share the same product score while presenting very different business or safety implications.

Types of FMEA

Design FMEA evaluates how a product design could fail to meet intended function before the design is frozen or released. Process FMEA examines how a manufacturing or operational process could introduce defects, variability, or safety issues during execution.

Some organizations also use system FMEA for broader functional interactions and service FMEA for transaction or service delivery processes, particularly where failures affect compliance, patient safety, or customer outcomes.

Key Elements of an FMEA

An FMEA entry normally includes the process step or function, the potential failure mode, the effect of failure, the cause, current preventive and detection controls, numeric ratings, recommended actions, ownership, and target dates. Without ownership and follow up, the document becomes an archive rather than a risk control tool.

The quality of the analysis depends heavily on accurate process knowledge. If the team lacks design, manufacturing, maintenance, supplier, or field failure insight, important failure modes may never be identified.

FMEA in Supplier and Procurement Management

Procurement and supplier quality teams use FMEA when assessing new suppliers, approving process changes, reviewing manufacturing readiness, and controlling high risk components. A supplier’s process FMEA can reveal where defects may occur and whether the existing controls are adequate for the intended application.

It is especially relevant where sourced components have critical safety, performance, or regulatory requirements and where a failure could cause recalls, downtime, or severe warranty exposure.

Limits of FMEA

FMEA is only as strong as the team’s knowledge, assumptions, and discipline. It may miss rare or systemic failures, and ratings can become subjective if criteria are not calibrated. It also requires updating when designs, materials, tooling, suppliers, or operating conditions change.

For that reason, FMEA should be linked to real failure data, control plans, change management, and lessons learned rather than being treated as a one time compliance document.

Frequently Asked Questions about Failure Mode and Effects Analysis (FMEA)

What is a failure mode in FMEA?

A failure mode is the specific way in which a product, process, or system might fail to perform its intended function. Examples include a seal leaking, software logic producing an incorrect output, a fastener loosening, or a process step using the wrong torque setting. FMEA requires the team to define those failure modes clearly because vague wording makes effects, causes, and controls hard to assess correctly.

Why is FMEA valuable before production launch?

It allows teams to identify preventable weaknesses before failures reach the customer, the plant, or the field. During launch, process controls, supplier capability, tooling behavior, and design assumptions are still being validated. FMEA provides a structured way to ask where failure could occur, what the impact would be, and which preventive controls should be improved before volume risk and warranty exposure increase.

Is the highest RPN always the highest priority?

Not necessarily. A very severe failure with lower occurrence can still require urgent action even if its overall RPN is not the largest number on the page. Many organizations therefore use action priority logic or escalation rules that give special weight to severity, safety, or regulatory effect. Numeric scoring supports discussion, but sound engineering judgment must still guide prioritization.

How often should an FMEA be updated?

It should be updated whenever there is a meaningful change in design, process flow, material, tooling, supplier, operating environment, customer complaint pattern, or control method. It should also be revisited when field failures or internal defects reveal that earlier assumptions were incomplete. An outdated FMEA may create a false sense of control because the documented risks no longer match actual operating conditions.