Production downtime vs speed loss: which gap are you measuring?

The difference between downtime and speed loss

A physical short stop may be classified as a performance loss rather than an availability loss. Vorne’s six-loss framework allows a locally defined threshold for tracked stops. Document that threshold and use it consistently. Do not count the same interruption in both categories.

Set the time boundary before calculating

Planned production time is the period in which production is intended to occur. In the OEE framework, time with no production intention, such as an excluded lunch break, is schedule loss. A changeover within planned production time is an availability loss.

The word “planned” alone does not tell you which denominator to use. A shift-shortfall calculation may start with clock time remaining and subtract every future zero-output interval. An OEE calculation starts with its defined planned production time. Keep those boundaries explicit.

Use different formulas for availability and performance

The OEE calculation guide gives these relationships:

Use compatible time units. The ideal rate is the benchmark for diagnosing speed loss; it is different from an observed rate used to estimate upcoming production. An inaccurate benchmark can hide a performance gap. Vorne’s practical OEE guide discusses that measurement problem.

Worked example: stops and slow running each cost output

This is an illustrative 60-minute production window for one product. The ideal gross rate is 120 units/hour, or 2 units/minute. A tracked stop lasts 10 minutes. During the remaining 50 minutes, the line produces 80 total units, of which 76 pass first time.

The tracked stop accounts for 10 × 2 = 20 gross units of ideal-rate opportunity. The run-time performance gap is 100 − 80 = another 20 gross units. Four produced units do not pass first time.

Against the 120-unit ideal opportunity for the full window, the final good-output gap is 20 + 20 + 4 = 44 units. This arithmetic explains the measurement, not the cause of each loss or the feasibility of eliminating it.

Express performance loss as equivalent minutes carefully

For the same example, making 80 units at 2 units/minute would take 40 ideal minutes. Measured run time was 50 minutes, so the performance gap is 10 ideal-rate-equivalent minutes.

This is a derived quantity: run time − total units ÷ ideal units per minute. It is not evidence that a single 10-minute stop occurred. The gap could reflect slow cycles, repeated minor stops or a mix. Retain event and cycle evidence when investigating the cause.

Avoid counting the same loss twice

• Use one stop-classification policy. If a minor stop remains in run time and lowers performance, do not also subtract it from run time for availability.
• Compare the same product and window. A combined rate across products with different ideal cycle times can conceal which process slowed.
• Keep gross and good counts separate. Performance uses total output; quality captures what did not pass first time.
• Keep counts and minutes separate. Convert units explicitly before comparing opportunity loss across categories.
• Do not infer the cause from a percentage alone. Pair the measured gap with a time window, product, stop reason or cycle evidence.

Choose the next question from the evidence

For a tracked stop, examine its timestamps and recorded reason. For a performance gap, examine the product’s cycle timing and the benchmark used. For quality loss, examine the rejected count and defect evidence. Then establish an owner and a specific follow-up rather than assuming every shortfall has the same remedy.

To explore the remaining shift, use the shift-shortfall calculator with an observed gross running rate and future stops. It calculates a scenario; it does not calculate OEE or identify the loss cause. Read how to calculate production shortfall for the full method, or explore MagicWand production monitoring for the product view.