What Is Downtime?

Downtime is any period when an asset or system is unavailable for use - because it has failed, because it is being serviced, or because something outside it (power, parts, people) is missing. It is the mirror image of asset uptime: every hour an asset was supposed to be working but was not. The word covers both a factory line standing still and a cordless drill sitting in a repair shop; the scale differs, the logic does not.

Planned vs unplanned downtime

The most useful split is not what caused the downtime but whether anyone chose it. Planned downtime is scheduled - servicing, inspections, upgrades, cleaning - and the timing is picked to hurt least. Unplanned downtime is the asset deciding for you, usually mid-use, which is why an hour of it costs several times an hour of the planned kind: the work in progress stops, someone scrambles to diagnose, parts get ordered at speed, and commitments slip. The relationship between the two is the core trade of maintenance, covered in more depth under planned vs unplanned maintenance: accepting small, scheduled unavailability to avoid large, random unavailability.

Where the real cost hides

The visible cost of downtime is the repair invoice. The larger costs are usually around it:

• Idle labour - the crew that cannot work because the machine, van, or appliance they need is out.
• Substitution - hire charges for a replacement, or the quiet damage of doing the job with the wrong tool.
• Knock-on delay - missed slots, rescheduled customers, overtime to catch up.
• Reputation - the customer who experienced the delay remembers it longer than you do.

This is why two identical breakdowns can have wildly different costs depending on when they happen and what was waiting on the asset.

Measuring downtime

Small teams do not need an availability dashboard to start - they need a record of when each asset went out of service and when it came back. From that you get the basics: total hours down per asset per period, and downtime split by cause (failure, servicing, waiting for parts, waiting for a decision). The split is the insight. “Waiting for parts” dominating the total points to stocking critical spares; “waiting for a decision” points to a process problem, not an equipment problem. Repeat offenders surface fast once the history is per-asset rather than per-memory.

Reducing downtime

The levers, roughly in order of cheapness: do the inspections that catch failures early; keep service history per asset so the repeat offenders are visible and can be fixed properly or retired; convert unplanned work to planned by servicing on schedule rather than on failure; keep a worked-down maintenance backlog so small faults do not queue until they become big ones; and for genuinely critical kit, hold a spare. None of these is glamorous, which is why they are routinely skipped.

Downtime in practice

The habit that makes everything else possible is marking the status change: the moment an asset goes out of service, its record says so, with a reason. In AMPthilly, setting an asset’s status to in repair and raising a service desk ticket gives the team a live view of what is down and why, and leaves a permanent repair history on the asset - which is how you later spot the machine that has quietly been down five times this year.

Related terms

• Asset Uptime - the availability percentage downtime subtracts from
• Planned vs Unplanned Maintenance - the trade-off that determines which kind of downtime you get
• Maintenance Backlog - the queue of outstanding work that feeds future downtime
• CMMS - the software category focused on scheduling work to minimise downtime
• Service Level Agreement - the formal availability commitment downtime is measured against