What Is Downtime Tracking?
Also known as: machine downtime tracking, downtime reason codes, stoppage tracking
Definition
Downtime tracking is the systematic recording of when a machine or line stops, for how long and for what reason, so that planned and unplanned stoppages can be measured, categorized and reduced.
Downtime Tracking Explained
A stop is recorded with a start time, end time, machine and a reason code. Machine signals (run, idle, fault) give accurate timestamps. Operators or technicians add the reason, such as no material, changeover, tool break, mechanical failure or waiting on quality. A short, well-designed list of reason codes is critical: dozens of codes produce an unused list, and the code Other becomes the biggest bucket.
Downtime is the availability component of OEE. Analyzing it with a Pareto chart shows the few causes responsible for most lost hours. It also splits planned stops (changeovers, scheduled maintenance, breaks) from unplanned ones, which need different responses: SMED for changeovers, maintenance strategy for breakdowns, material staging for starvation.
ERP-based data collection can capture indirect labor or machine down transactions, but dense machine data usually comes from an MES, a machine monitoring system using MTConnect or OPC UA, or PLC counters. The data is also used by maintenance modules to compute MTBF and MTTR and trigger work orders.
Why It Matters
- You cannot reduce losses you do not measure, and manual estimates usually understate them.
- Reason-coded stops direct improvement effort to the biggest cause rather than the loudest complaint.
- It supplies the availability figure for OEE and the failure data for MTBF and MTTR.
- It supports capacity decisions: spare hours may be hiding in downtime, avoiding premature machine purchases.
In Practice
A machining cell reports 62 percent availability. Reason-coded data over four weeks shows 35 percent of lost time is waiting for material, 30 percent is changeover, 20 percent is tool breakage and the rest is a mix. The team stages material at the cell and standardizes tool presets, raising availability toward the high 70s without any new equipment purchase.
Frequently Asked Questions
What are common downtime reason codes?
Changeover, no material, no operator, tooling, mechanical or electrical breakdown, waiting for quality, planned maintenance and break. Keep the list short and review it regularly.
Can downtime be tracked without sensors?
Yes, with operator entries on a terminal, but accuracy depends on discipline. Machine signals give precise timing; operators add the reason.
How does it relate to OEE?
Downtime determines availability, one of the three OEE factors alongside performance and quality.
Related Terms
OEE (Overall Equipment Effectiveness)
OEE (Overall Equipment Effectiveness) is a manufacturing metric that multiplies Availability, Performance, and Quality into a single percentage showing how much of scheduled production time an asset spends making good parts at its rated speed.
MTBF (Mean Time Between Failures)
MTBF (Mean Time Between Failures) is the average operating time a repairable asset runs between consecutive failures, calculated as total operating time divided by the number of failures in that period. It measures reliability, not expected lifetime.
MTTR (Mean Time To Repair)
MTTR (Mean Time To Repair) is the average time required to restore a failed asset to full operating condition, calculated as total repair time divided by the number of repairs. It measures maintainability rather than reliability.
SMED (Single-Minute Exchange of Die)
SMED (Single-Minute Exchange of Die) is a structured method developed by Shigeo Shingo for reducing equipment changeover time to under ten minutes, primarily by converting setup steps that require the machine stopped into steps performed while it still runs.
TPM (Total Productive Maintenance)
TPM (Total Productive Maintenance) is a company-wide approach to equipment reliability that shifts routine care to operators, builds structured planned maintenance, and targets the elimination of breakdowns, speed loss, and defects caused by equipment condition.
Working with Downtime Tracking in a live environment? Our engineers do this every day - and our AI agents automate most of it.