The Mantua Group

Simple Black and White Asset Management, Reliability Expertise, and Maintenance Execution Perfection.

RBDs and Fault Trees: Two Lenses, One System

RBD use Left to Right Success Logic - Fault Trees use Bottom to Top propagation of Failure Logic

Here is something that surprises many engineers the first time they see it: a Reliability Block Diagram and a Fault Tree are mathematically equivalent. Same system, same Boolean probability logic, two directions of reading. An RBD reads left to right and asks what has to work for the system to succeed. A fault tree reads top to bottom and asks what has to fail for the system to fail.

The translation between them is exact:

  • Series blocks in an RBD correspond to an OR gate in a fault tree. If any one of the series items fails, the system fails.
  • Parallel blocks in an RBD correspond to an AND gate in a fault tree. All redundant paths must fail before the system fails.
  • Minimal cut sets are the meeting point. The unique combinations of basic events that cause the top event in a fault tree are exactly the minimal failure combinations that break every success path in the equivalent RBD. Our page on Fault Tree Analysis services explains cut sets, gates and top events in detail, and our white paper on the MOCUS algorithm derives the classic method for extracting them from first principles, with a working Python implementation.

Why Two Representations Survive

Because different stakeholders think in different directions. Operations people naturally reason in success paths: the pump feeds the exchanger, the exchanger feeds the column. Safety and risk people naturally reason in failure paths: loss of cooling AND loss of trip function. If your modelling environment forces everyone through one lens, you lose half the room in every review.

The two lenses also earn their keep on different questions. RBDs excel at availability and production problems: throughput logic, buffers, standby arrangements, and the system-level consequences of maintenance strategy, which is where availability simulation takes over. Fault trees excel at safety and rare-event problems: minimal cut sets, importance measures, common cause failure, and the quantified arguments that regulators demand. Once common cause enters the picture, redundancy is never as good as the naive arithmetic suggests; our white paper on the Beta Factor CCF model gives the first-principles derivation with worked examples.

How the Tools Help You Discover the Benefit

Reliability Workbench and Availability Workbench are built on a shared framework, so the two representations are not rival products but sibling views. RWB provides the dedicated Reliability Block Diagram module and the Fault Tree Analysis module, with automatic minimal cut set extraction, failure frequency and unavailability calculated at every gate, and importance measures that rank which paths matter. Shared failure models, consequence structures and parts libraries mean the RBD your maintenance team builds and the fault tree your safety team builds speak the same underlying language. One model of the truth, understood by everyone who needs it.

If you have only ever worked in one representation, learning the other will sharpen your thinking about both. Our Fault Tree Analysis and RAMS training courses deliberately teach them side by side, and the podcast episode You Gotta Think digs into why choosing the right tool for the right job matters more than mastering any single one.

Go Deeper

How can we help? Talk to us at contact@mantua.group.