Why Downtime Is Really a Knowledge Problem

When a line stops, the cost clock starts. Industry surveys put the cost of unplanned downtime in the tens of thousands of dollars an hour for many plants. Siemens' 2024 research, for example, puts it at around US$36,000 an hour in the lowest-cost sector it studied, food and consumer goods, and far higher in automotive. Most of the conversation is about preventing the stoppage. A lot of the cost, though, comes from what happens after it starts.

Where the time actually goes

Think about a typical stoppage and break it into stages:

1. Notice and call it in. Usually quick.
2. Diagnose. What is actually wrong? This is often the longest stage.
3. Find the information. Which manual, which page, which drawing, has this happened before?
4. Get parts and people. Sometimes outside your control.
5. Do the repair. Often the shortest stage, once you know what you're doing.
6. Restart and check.

Stages 2 and 3 are knowledge. They depend on whether the person on shift has, or can quickly get to, what the best engineer on site would know.

The same fault, different outcomes

Take a recurring fault. With the experienced engineer on shift, it's fixed in twenty minutes. On nights, with a newer engineer, it takes three hours: they search the manual, ring a colleague, try something that doesn't work, and ring again. The machine, the fault and the repair are identical. The difference is knowledge.

Why prevention isn't the whole answer

Predictive maintenance and sensors have their place. They need data, installation and time, and they won't prevent every stoppage. When a machine does stop, the quality of the next hour depends on what your people know and how fast they can get to it.

What you can do about it

• Measure it. For your ten most frequent faults, record how long it takes to find the right information as well as how long the repair takes.
• Capture fixes where they happen. Film them, note them, and attach them to the machine.
• Make it one place. Manuals, SOPs, past fixes and notes should be somewhere an engineer can search in plain language.
• Close the shift gap. Whatever the day shift knows should be available at 2am.

Putting a number on it

Our calculator lets you try your own figures: stoppages per month, repair time and cost of downtime. It also shows what an illustrative improvement in repair time would be worth. It's a scenario rather than a promise, and the best way to find your real number is a trial on your own documents.