Availability Math and the Downtime Budget

Turning availability figures into an annual downtime budget shows exactly how much redundancy a mission-critical installation must carry.

From availability to hours

Availability A relates to annual downtime by (1 − A) × 8,766 hours. Working the burner and Tier III numbers gives a concrete downtime budget that drives the redundancy design.

Reading the budget

• Tier III 0.99982 → about 1.6 hours of downtime per year.
• Burner 0.995 → about 44 hours per year.
• Burner 0.86 → about 1,227 hours per year (~51 days).

How redundancy closes it

If a mission needs Tier-III-class continuity from sources that individually deliver 0.86–0.995, the system must carry parallel capacity and fast-switching storage so that one unit's downtime is invisible to the load. Two independent units, each at 0.995, combined so either can carry the load, give a combined unavailability far below a single unit — approaching the Tier III target as units and storage are added.

The point of the math is not to claim the burner reaches Tier III. It is to size the redundancy honestly. The downtime budget is the design input; the redundancy architecture is the response. No monetary values enter this calculation — it is purely time and reliability.

From budget to architecture

The downtime budget is what converts an abstract availability figure into concrete redundancy: how many parallel units, how much storage, and how fast a spare must pick up load. Two independent units near 0.995 combine to an unavailability far below either alone, approaching the Tier III target as units are added. The math is purely reliability and time, with no economic content.