Downtime

Executives need a clean unit of measurement before they can price disruption, and downtime is that unit: the time a service or process is unavailable. The term exists to separate duration from damage; how long we were down is a fact, what it cost is an analysis. Without this separation, discussions drift into anecdotes and IT jargon. With it, the board can compare incidents, trends and investments on one scale.

Downtime is recorded by operations or IT from incident logs, and the BIA translates it into money and obligations: cost per hour, contractual penalties, regulatory deadlines. It appears in service reports, in the cost-of-downtime line of the BIA, and on board dashboards as hours per quarter. For example, if order intake generates USD 40,000 an hour, an 8-hour outage is a USD 320,000 conversation, a number a CFO can weigh against the cost of redundancy. Recovery targets such as RTO are, in essence, promises about maximum acceptable downtime.

The trap is worshipping availability percentages: 99.9% uptime still allows nearly 9 hours of downtime a year and says nothing about when they fall. Eight of those hours on salary payment day can hurt more than eighty overnight. The right lens is downtime weighted by business impact, not raw totals. In the ERGP programme, a chapter of Module 3 on impact analysis shows how downtime becomes cost and tolerance figures.