Where FMEA Fits Among Risk Methods

Failure mode and effects analysis (FMEA) is one of several structured methods for finding risk before it becomes harm. An advanced practitioner must know what it does well, what it does badly, and when another method should be used instead or alongside it. Choosing the wrong method is a common reason a study produces many pages and little protection.

Bottom-up and top-down

FMEA is a bottom-up (inductive) method. It starts with each element of a design or each step of a process and asks: how can this fail, and what follows? It is thorough for single failures, because it forces the team to visit every element in turn.

Fault tree analysis (FTA) is top-down (deductive). It starts with one undesired top event, such as "loss of braking", and works downward through logic gates to the combinations of causes that produce it. It handles combinations of failures well, which FMEA does not.

Worked example: a brake actuator

A team designing an electric brake actuator runs a design FMEA. It finds that the motor winding can short, the position sensor can drift, and the gear can strip. Each failure mode gets an effect, a cause and controls. But the most serious hazard is "brake applies with no driver demand", which needs the sensor to drift and the software plausibility check to fail at the same time. The FMEA lists both, on separate rows, each with a modest rating. Only a fault tree on the top event shows that together they form a two-failure path with a shared cause: a common supply voltage. The two methods are complementary, not competing.

Worked example: a chemical dosing skid

A process plant team wanted to run a process FMEA on a dosing skid. The real risks were deviations in flow, pressure and temperature during operation, not errors in how the skid was built. A HAZOP was the better tool. FMEA was then used on the skid's control instruments, where component failure modes mattered.