Moreover, the method assumes component failures are independent. In reality, common-cause failures (e.g., a flood drowning all generators in the same basement) can ruin the math. Modern extensions (the "common-cause beta factor model") were developed by Billinton’s students to address this. Roy Billinton’s solution is no longer confined to high-voltage circuit breakers. Every time your smartphone switches seamlessly between 5G and Wi-Fi, an embedded Billinton-style reliability model decides when to hand off. When an autonomous car brakes for a phantom obstacle, its fault tree analysis (a Billinton tool) decides whether the sensor failed or the object is real.
Billinton’s revolutionary insight was simple yet profound: The Billinton Framework: Deconstructing Failure In his feature solution—codified in the Billinton & Allan textbooks—reliability evaluation breaks into two fundamental questions: 1. Can the system do its job right now ? (Adequacy) Do you have enough capacity this instant ? For a power plant: Are there enough working generators to meet current demand? For a data center: Is there enough UPS battery to ride through a 5-second voltage sag? 2. Can the system stay doing its job? (Security) This is the dynamic question. If a single component fails, will the rest cascade into collapse? The 2003 Northeast Blackout (50 million people) was not an adequacy failure—there was enough generation. It was a security failure: one line’s outage overloaded its neighbor, which tripped, which overloaded the next, in a domino effect. Roy Billinton’s solution is no longer confined to
The feature that defines Billinton’s work is this: which overloaded the next