What does downtime really cost?

When a road is blocked and a mining operation cannot ship its production, the internal conversation almost always starts with logistics: how long it will last, which alternative route exists, whom to call. It rarely starts with the question that truly matters: how much each hour of stopped operation costs, and who in the organization has that figure at hand when they need it.

The Boyacá strike put a concrete number on the table: COP 6 billion per day in economic impact for the affected operations, according to El Tiempo. It is not a figure for technical unavailability. It is direct economic exposure, measurable and recurring every time an external condition stops the operation.

The executive question is not “how do we prevent the next strike?”; that is not in the operation’s hands. The question is: how much does an hour of unavailability of our critical assets really cost, and does that figure live in a report someone puts together after the fact, or is it available in real time to whoever has to decide while it is happening?

Most industrial operations can answer “how much do we produce” precisely. Very few can answer “how much does not producing cost us” with the same speed. That asymmetry is the real problem: it is not that information on the economic impact of unavailability is missing. It is that the information arrives late, fragmented, or only when someone decides to build the report.

This is not a problem solved with more sensors. It is a question of whether the organization can connect an operational signal with its economic cost at the moment when the decision can still change the outcome.

How much did the last hour of unavailability cost your operation, and how much time passed between when it happened and when someone could put a number on it?

Source

El Tiempo, Economía section: losses of about COP 6 billion per day from the Boyacá strikes.