Definition
FMEA breaks a product or process into functions, potential failure modes, effects, and causes. The team assesses risks and prioritizes actions before a failure occurs or recurs in operation.
Key facts
- FMEA is proactive and performed by a cross-functional team.
- It starts with functions and requirements, not only known failures.
- Ratings support prioritization but do not replace engineering judgment.
- The document must be updated when designs, processes, or knowledge change.
What does FMEA (Failure Mode and Effects Analysis) reveal about failures?
For each function, the team describes failure mode, effect, cause, and current prevention or detection controls. These inputs lead to prioritized improvements.
How do teams use FMEA (Failure Mode and Effects Analysis) in failure analysis?
Operating experience contributes real failure modes and detection opportunities. In return, FMEA helps target maintenance tasks at critical mechanisms and effective checks.
What can make FMEA (Failure Mode and Effects Analysis) misleading?
An FMEA loses value when archived at the end of a project. Changes, new events, and the effectiveness of completed actions should continually feed back into it.