|
|
| Home>>
Products>>SCR-QMS>>
ISO/TS 16949>>FMEA
|
| HISTORY |
The FMEA process was originally developed by the US military in 1949 to classify failures
"according to their impact on mission success and personnel/equipment safety". FMEA has
since been used on the 1960s Apollo space missions. In the 1980s it was used by Ford to
reduce risks after one model of car, the Pinto, suffered a fault in several vehicles causing
the fuel tank to rupture and subsequently burst into flames after crashes
|
| Failure Mode Effects Analysis (FMEA) |
Failure mode and effects analysis(FMEA) is a method (first developed for systems engineering) that examines potential failures in products or processes.
It may be used to evaluate risk management priorities for mitigating known threat-vulnerabilities
FMEA helps select remedial actions that reduce cumulative impacts of life-cycle
consequences(risks) from a systems failure (fault).
By adapting hazard tree analysis to facilitate visual learning, this method illustrates
connections between multiple contributing causes and cumulative (life-cycle) consequences
The basic process is to take a description of the parts of a system, and list the
consequences if each part fails. In most formal systems, the consequences are then
evaluated by three criteria and associated risk indices
|
| SCREEN SHOTS |
|
Click for FMEA |
Click for Process Flow Diagram |
Click for PFD Chart |
|
|
| APPLICATIONS |
- FMEA is most commonly applied but not limited to design
(Design FMEA) and manufacturing processes (Process FMEA)
- Design failure modes effects analysis (DFMEA) identifies potential failures of
a design before they occur. DFMEA then goes on to establish the potential effects of the
failures, their cause, how
often and when they might occur and their potential seriousness
- Process failure modes effects analysis (PFMEA) is
a systemized group of activities intended to
- Recognize and evaluate the potential failure of a product/process and its effect,
- Identify actions which could eliminate or
reduce the occurrence, or improve detectability,
- Document the process, and
- Track changes to process-incorporated to avoid potential failures
|
|
