Worked examples — Redundancy — cold standby, hot standby, active redundancy
This page drills the redundancy formulas from the parent topic until every case is muscle memory. We will not introduce new theory — we will stress-test the reliability tools on every kind of input a problem can throw at you: normal numbers, zero time, infinite time, degenerate switches, word problems, and one exam twist.
Before we start, one reminder of the symbols we already earned in the parent note (nothing new here):
Recall The symbols we already built
- ::: the failure rate — how many failures per hour a single unit averages. Bigger = fails sooner.
- ::: reliability at time — the probability a unit is still alive at time . Starts at (alive for sure), decays toward .
- ::: the survival curve of one unit — why exponential? Because a constant failure rate means the chance of surviving the next hour is the same every hour, and multiplying that constant survival over many hours gives an exponential. It is the only curve with "no memory".
- ::: mean time to failure — the area under the survival curve. Wider area = lives longer on average.
The scenario matrix
Every redundancy problem you will meet falls into one of these case classes. The worked examples below are labelled with the cell they cover, and together they hit every cell.
| Cell | Case class | What makes it tricky |
|---|---|---|
| A | Normal cold vs hot MTTF | plug numbers, compare vs |
| B | Reliability at a specific finite time | evaluate , don't confuse with MTTF |
| C | Zero-time input () | degenerate: every system reads |
| D | Infinite-time limit () | degenerate: every |
| E | TMR (active, 2-of-3) crossover | TMR is worse than single for large |
| F | Imperfect switch (single point of failure) | switch reliability multiplies in |
| G | Power-budget word problem | reliability gain vs watts cost |
| H | Exam twist — "when does TMR beat single?" | solve inequality for |
Example A — Cold vs hot standby MTTF (normal numbers)
Forecast: Guess the ordering before reading on. Which redundancy scheme should give the longest average life?
-
Single unit. h. Why this step? This is our baseline — everything else is measured against it.
-
Hot standby. From the parent, h. Why this step? Both units age together, so the backup burns half its life just sitting warm — we gain only half a lifetime.
-
Cold standby. h. Why this step? The cold backup's clock only starts at switchover, so we gain a full second lifetime.
Verify: Ratio . Cold wins on paper — matching the parent's key comparison . Units are hours throughout. ✓ (This cell is A.)
Example B — Reliability at a finite mission time
Forecast: MTTF said cold was best. At a specific short time, will cold still look better, and by how much?
-
Single unit. , so . Why this step? We need the single-unit survival first because both redundant formulas are built from it.
-
Hot standby. . Why this step? Hot standby fails only when both fail; this formula is .
-
Cold standby. . Why this step? Cold uses the first two Poisson terms because it survives until the second failure, and the backup didn't age while waiting.
Verify: Order at this time is — cold is best here too, consistent with Example A. All are probabilities in . ✓
The figure below plots all three survival curves. Notice they all launch from at the left edge (Example C), the grey single-unit curve sags fastest, and at the red dashed line h the three coloured dots sit exactly at the numbers we just computed — blue (cold) highest, orange (hot) just below, grey (single) far lower.

Example C — The zero-time degenerate case
Forecast: Before computing — what's the probability anything has failed the instant you turn it on?
- Single: .
- Hot: .
- Cold: . Why these steps? At nothing has had time to fail. A correct reliability curve must start at (certain survival). Any formula that gave anything else at would be wrong.
Verify: All three equal . This is the sanity check every reliability formula must pass — if yours doesn't start at , you copied it wrong. ✓ (Cell C.)
Example D — The infinite-time limit
Forecast: Given infinite time, does any redundancy scheme survive forever?
-
Single: . Why this step? We start with the simplest curve because the other three are all built from — if it dies, they inherit that death.
-
Hot: . Why this step? Both terms contain a decaying exponential, so each term is dragged to zero independently — a sum of zeros is zero.
-
Cold: (exponential beats the linear ). Why this step? This is the one term that could fool you — the factor grows, but shrinks faster than any polynomial grows, so the product still dies. We must check the fastest-growing factor to be sure.
-
TMR: with gives . Why this step? TMR's reliability is a polynomial in with no constant term, so once the underlying unit reliability the whole voter output collapses to zero too.
Verify: Every system tends to . Redundancy buys time, never immortality — it slows the decay, it cannot stop it. The area under the slower-decaying curve is exactly the MTTF gain we computed in Example A. ✓ (Cell D.)
Example E — TMR and its crossover point
Forecast: TMR always beats a single unit... or does it? Guess what happens when each unit is already unreliable ().
-
High-quality units, . . Why this step? When units are good, "2-of-3" masks the rare single failure — TMR () beats single ().
-
Poor units, . . Why this step? When units are bad, needing two to work simultaneously is harder than needing one — TMR () is worse than single ()!
Verify: The crossover is exactly (see Example H). Above it TMR helps; below it TMR hurts. So helps, hurts — matches. ✓
The figure below draws the grey diagonal (single unit, output = input) against the green TMR curve. Where the green curve sits above the diagonal (shaded green, ) TMR helps; where it dips below (shaded red, ) TMR hurts. The blue dot at lands in the green zone, the orange dot at lands in the red zone, and the two curves cross exactly at the red dot .

Example F — Imperfect switch (single point of failure)
Forecast: The parent warned the switch is itself a single point of failure. Guess: does a switch wipe out the redundancy benefit?
-
Ideal redundant pair. . Why this step? This is the "two computers, perfect switch" fantasy — the number people quote.
-
Multiply by the switch. The whole chain only works if the switch also works, so multiply: . Why this step? The switch is in series with the redundant block — one series weak link caps the whole system (this is a reliability block diagram with a series element).
-
Sanity vs single unit. Single unit . So real redundancy — still a gain, but far short of the fantasy.
Verify: : redundancy still helps but the switch throws away most of the gain. This is why real spacecraft use fault detection and isolation plus cross-strapping to make the switch itself reliable. ✓ (Cell F.)
Example G — Power-budget word problem
Forecast: Reliability says cold has higher MTTF anyway. Does the power budget agree or conflict?
-
Check the hot-standby power draw. Extra load W. Available margin W. Since , hot standby violates the power budget. Why this step? A design that busts the power budget is infeasible regardless of reliability — power is a hard constraint.
-
Check the cold-standby power draw. Extra load W (backup OFF). : fits. Why this step? Cold's zero standby power is its headline advantage on a battery-tight spacecraft.
-
Check the timing requirement. Cold's s switchover tolerable s gap: acceptable. Why this step? Cold's only downside (delay) is inside the allowed limit here.
Verify: Power ( ✓), timing ( ✓), and cold already had the higher MTTF from Example A. Every constraint points to cold standby — a rare case with no tradeoff. ✓ (Cell G.)
Example H — Exam twist: solve for the TMR crossover
Forecast: Example E hinted the crossover is . Prove it and find the other roots.
-
Set up the equation. . Why this step? "TMR beats single" ⇔ ; the boundary is equality.
-
Bring to one side and factor. . Why this step? Factoring turns a cubic into three simple roots — no formula needed.
-
Read off the roots. , , . Why this step? A product equals zero only when one of its factors is zero, so we set each of the three factors , , to zero in turn — that is the whole point of factoring, it hands us the roots directly.
-
Decide the winning region. Test (Example E): TMR ✓. Test : TMR ✓. So TMR beats single exactly when . Why this step? Roots only mark where the two curves cross; to learn which side wins we must sample one point in each interval between roots — the sign of the difference there settles the whole interval.
Verify: Roots satisfy the cubic; the sign tests confirm TMR helps above and hurts below. Consistent with Example E. ✓ (Cell H.)
Recall Quick self-test
At , does TMR beat a single unit? ::: No — they are exactly equal; is the crossover. Why does cold standby have higher MTTF than hot? ::: The cold backup doesn't age while OFF, so you gain a full second lifetime instead of only half. A "redundant" system with a fragile switch — where does the switch sit in the reliability block diagram? ::: In series with the redundant block, so it caps total reliability.
Where each idea connects
See also: Failure Modes and Effects Analysis (FMEA) to find which failures need covering, Single Event Upset (SEU) for the radiation bit-flips that trigger switchovers, and Byzantine Fault Tolerance for when a faulty unit lies to the voter.