top of page

Common-Cause Failures and Single Points of Failure: Lessons from the End of the Line

Writer: JD Solomon
JD Solomon
13 minutes ago
5 min read
Many engineers and operators blur the difference between common-cause failures and single points of failure.
Many engineers and operators blur the difference between common-cause failures and single points of failure.

The previous article in this series covered reliability and redundancy. Redundancy works only when redundant assets fail independently, and many engineers and operators blur the difference between common-cause failures and single points of failure. The distinction matters because each calls for a different mitigation strategy. A common-cause failure defeats multiple assets at the same time. A single point of failure ends the mission even when every major asset remains fully functional.

 

Common-Cause Failure: When Four Rods Are Not Four Rods

Redundancy exists so that another asset can perform the required function when one fails. However, redundant assets are not necessarily independent assets.

 

Three pumps from the same manufacturer, installed at the same time, operated under the same conditions, and maintained with the same procedures may appear redundant. A design flaw, software issue, or operating practice can take them all down at once. The real question is whether the assets fail independently.

 

From the Beach

Someone casually asked me whether the four surf rods on my fishing cart could all fail the same way. The fish were not biting, and the guy turned out to be an engineer who worked for one of my clients, so the question got more of my attention than it otherwise would have.

 

My first answer was about the reels. As the previous piece noted, three of my four heavy reels are Penn Fierce, which is a real common-cause exposure. However, they are different sizes and generations purchased in different years, and that diversity softens the risk. Years of service without a fleet-wide problem support the conclusion. However, operating history alone is weak evidence because common-cause failures are rare and often stay hidden until the day they appear.

 

My second answer was better. The real common-cause exposure on my cart sits downstream of the reels, and I manage most of it without overanalyzing it.

 

  • Line comes from different spools. I usually put one spool on this class of reels and use the extra on a lighter class.

  • Rigs come from three or four packs at a time, and I mix plain mono, beaded, and metal rigs in different strengths.

  • Spare hooks come from different manufacturers.

  • I tie every knot myself, and I use the standard fisherman's knot every time.


The Human Factor is Not Diversified

The remaining common cause is me. The knot works great, and years of results support it. However, one person tying one knot is a shared mechanism across every rod, and a bad day at the knot shows up on all four lines. Salt spray and sand are the other shared exposures, followed by the same rinse-and-lube routine for every rod. The tackle is diverse. The human factor is not.

 

Single Points of Failure: Follow the Line to the Hook

A single point of failure does not require multiple assets. It requires only one vulnerable component that can end the mission.

 

I treat the rod and reel as a single functional asset, no different from a pump-and-motor assembly or an actuator-and-valve pair. Individual components exist, but they work together to perform one operational function. With that asset definition established, follow the mission path from the reel handle to the hook.

 

The rod-and-reel asset is reliable. Failures are uncommon and maintenance requirements are modest. The terminal tackle is another story. Hooks become dull and bend. Swivels wear, rig components corrode, and pre-tied knots degrade. Entire rigs are lost to snags, abrasion, bluefish, or simple wear and tear.

 

The rod and reel keep working while a failed swivel or knot ends the cast. A bent hook does not end it, but it cuts the rig's coverage in half, which is why the first article in this series called the second hook coverage and not redundancy. The asset survives. The mission does not.

 

Raise the Level of Analysis

A bent hook on one rod is not a single point of failure for the morning. The second rod is still fishing, and a baited rod on hot standby takes its place in seconds. The N+2 redundancy described in the previous piece absorbs a single tackle failure, which is why I carry four heavy rods.

 

The true single points of failure sit at the system level. Run out of bait and every rod is idle. The bag is the other one. It holds the spare-rig box along with the tools, including knives, needle-nose pliers, and tape measures. Without it, a lost rig or a deep hook ends the session for that rod, and the bag's absence affects every rod at once. That makes the bag both a single point of failure and a common cause.

 

Looking at the Risk to Fleet

I treat that risk differently depending on the fleet. With the lighter classes of rods and reels, I sometimes leave the bag at home. With the heavy fleet and in heavy conditions, I never do. That is a risk-based decision about critical spares, matched to the consequence of failure, and it is the same decision a utility makes when it chooses which spares to keep on site and which to keep in the warehouse.

 

That is the connection practitioners often miss. The small consumables that fail most often are also the components most likely to share a common cause, and both problems depend on a spares strategy that rarely gets the attention the primary asset does.

 

Why Organizations Miss the End of the Line

Reliability programs focus on large, visible assets that are easier to inventory, secure capital funding for, and include in management reports. Smaller supporting components receive less scrutiny even when they drive more mission failures. The same pattern appears across many industries.

 

  • A treatment process is constrained by instrumentation rather than pumps.

  • A facility suffers outages because of electrical connections rather than major equipment.

  • A communications network is disrupted by an overlooked dependency rather than a primary server.

  • A bank of identical analyzers drifts together because every unit is calibrated against the same standard.

 

Many of these small components are bought in batches, stocked from a single supplier, and maintained by the same technician. They are frequent failures and common-cause carriers at the same time, which is why analysis that stops at the asset boundary misses them.

 

Different Problems Require Different Mitigations

Common-cause failures and single points of failure answer different questions. The common-cause question asks whether one underlying mechanism can defeat multiple assets. The single-point-of-failure question asks which individual failure can end the mission. The mitigation strategies follow from those questions.

 

Diversity and separation are the primary defenses against common-cause failure. Mix suppliers and production lots, stagger installation and replacement, and avoid having one crew or procedure touch every redundant unit at the same time.

 

On my fishing cart, most of that diversity comes from habit. I do not overanalyze it, and practical diversity often works that way. The human factor is harder to diversify, so the defense shifts to a proven method, a consistent check, and retying the connection whenever there is doubt.

 

Redundancy, wear-rate inspection frequency, and critical spares are defenses against single points of failure. Consumables like hooks and swivels need a stocking strategy. On the beach, that means checking hooks often and bringing the bag whenever the conditions make a lost rig costly. In a utility, it means treating instrumentation and connectors as critical spares even though each one costs very little.

 

The Lesson at the End of the Line

Effective reliability analysis distinguishes common-cause from single points of failure and then follows the entire mission path beyond the primary asset. The biggest risks often lie in small, inexpensive components that fail most often and share the most common causes. The rod and reel rarely end the fishing. What happens at the end of the line does.



JD Solomon is the founder of JD Solomon, Inc., the creator of the FINESSE Fishbone Diagram®, and the co-creator of the SOAP criticality method©. He is the author of Communicating Reliability, Risk & Resiliency to Decision Makers: How to Get Your Boss’s Boss to Understand and Facilitating with FINESSE: A Guide to Successful Business Solutions.

Comments


bottom of page