General scope
IEC 60812 describes failure modes and effects analysis, known by the acronym FMEA, and its extension that adds criticality. It offers guidance for planning the study, carrying it out, documenting it and maintaining it. It does not set universal acceptance values: it provides a methodological framework that each organization adapts to its product or process.
What the standard gives guidance on
- When and why to apply the analysis: as a design, verification and improvement tool throughout the life cycle.
- How to define the scope: the system, its functions, boundaries and operating conditions.
- How to identify failure modes, causes and effects at different levels of the system.
- How to assess severity, occurrence and detection to prioritize actions.
- How to document the analysis with worksheets and keep it up to date.
Analysis approaches
The method can be applied from the components up to the system, considering each failure mode of the parts, or from the functions, studying how each function can cease to be fulfilled. The functional approach is useful in the early design stages, when not all components are defined yet.
What an engineer sees in practice
The standard does not replace the team’s technical knowledge: the quality of the analysis depends on the participation of people who know the design and its operation. Severity and probability scales are usually defined within the organization, and what matters is to use them consistently.
When it is not enough
The analysis normally studies failures one at a time. For combinations of failures, human errors or dependencies between components, it is complemented with other methods, such as the fault tree.
How to use this information
This guide describes the general scope only. The specific requirements, definitions and recommendations must be consulted in the current edition of the document, purchased through official channels, because standards are revised and their contents may change.