To calculate downtime in production, divide total downtime minutes by total planned production time, then multiply by 100 to get a downtime percentage: Downtime % = (Total Downtime ÷ Planned Production Time) x 100.
For example, a machine scheduled to run 480 minutes in a shift that loses 60 minutes to stoppages has a downtime rate of 12.5%. Most manufacturers track this by machine, shift, and reason code rather than as a single plant-wide number, since that's what actually points to where the time is being lost.
The basic formula is straightforward:
To use it, two numbers need to be accurate:
Example: A machine is scheduled for an 8-hour shift (480 minutes). It experiences a 25-minute jam, a 20-minute changeover overrun, and a 15-minute unplanned repair, totaling 60 minutes of downtime.
Downtime % = (60 ÷ 480) x 100 = 12.5%
Not all downtime should be counted the same way, since planned and unplanned downtime point to different problems.
Mixing the two into a single downtime figure hides the real problem. A plant with a lot of planned maintenance but very little unplanned downtime is in a fundamentally different position than one with the opposite mix, even if the total downtime hours look similar.
Downtime feeds directly into the availability component of OEE (Overall Equipment Effectiveness), one of the three factors, along with performance and quality, used to calculate the metric.
Using the earlier example: Availability = (480 − 60) ÷ 480 = 87.5%.
That availability score then multiplies with performance and quality to produce overall OEE. This is why downtime tracking and OEE tracking are usually built into the same system rather than calculated separately, since they rely on the same underlying data.
Manual downtime tracking uses paper logs or spreadsheets, with an operator noting start and stop times along with a reason. It's workable at small scale but tends to break down for a few reasons:
Automated downtime tracking solves this by detecting machine state changes directly from the equipment, timestamping each event to the second, and prompting for (or automatically assigning) a reason code. Platforms like Caddis's downtime tracking report stoppages within five seconds of occurrence, which is precise enough to catch short stops that manual logs consistently miss.
Calculating a downtime percentage is only useful if it leads to action. A few ways plants use the number:
Divide total downtime minutes by planned production time in minutes, then multiply by 100. A machine scheduled for 480 minutes that loses 60 minutes to stoppages has a downtime rate of 12.5%.
There's no universal benchmark, since it depends heavily on the industry and equipment type, but many discrete manufacturers target unplanned downtime under 10%. What matters most is tracking the trend over time and identifying the specific causes driving it.
Planned maintenance is typically excluded from the planned production time used in downtime and OEE calculations, since that time was never expected to be productive. It should still be tracked separately for maintenance planning purposes.
Downtime is the raw time lost to stoppages. Availability is the percentage of planned production time that remained after subtracting downtime, and it's one of the three components used to calculate OEE.
Reducing unplanned downtime starts with accurate reason code data to identify the biggest contributors, followed by targeted fixes, whether that's a maintenance schedule change, a changeover process improvement, or predictive maintenance based on machine condition data.
Calculating downtime by hand works for a single machine on a single shift. It stops working the moment a plant runs multiple machines, multiple shifts, or wants to catch the short stops that manual logs miss. Automated downtime tracking handles the calculation in real time and shows exactly where the time is going.
To see automated downtime tracking on your own machines, book a free demo with Caddis Systems.