Speed loss in minutes = run time - (total units ÷ ideal rate). Divide it by scheduled time to get the OEE points it costs. Example: 412 minutes of run time, 42,000 units and an ideal rate of 120 per minute give 412 - 350 = 62 minutes, or 13.8 points of a 450-minute shift.
Speed loss calculator
Enter one shift. The defaults are the carton line worked through below. Updates as you type.
Split: minor stops or reduced speed
Minor stops and slow running both land in performance, but the fixes differ.
The working
Total units are used for speed loss, so bad units still count here. They come off later, in quality.
The four numbers you need
You can do this sum on a phone at the line. Get these from the shift record before you start, and if the words are new, what speed losses are covers the meaning.
| Input | Where it comes from | Example: a carton line |
|---|---|---|
| Scheduled time | The shift plan, minus excluded time | 450 min |
| Logged stops | The stop log | 38 min |
| Total units, good and bad | A counter at the machine output | 42,000 |
| Ideal rate | The accredited rate for this format | 120 / min |
No agreed rate yet? Work it out first with how to calculate ideal run rate, because every result below depends on it.
Calculate it in four steps
Step 2 is the idea to hold on to. It asks how long those 42,000 cartons should have taken at full speed.
The line was up for 412 minutes and needed only 350, so 62 minutes went somewhere. Nobody logged those minutes as stops, and that is why this loss is easy to miss.
The same loss, said four ways
People quote speed loss in different units, and then argue because the numbers do not match. All four below describe the same 62 minutes.
| Unit | Calculation | Result | Good for |
|---|---|---|---|
| Minutes | 412 - 350 | 62 min | Comparing with stops |
| Units not made | 62 x 120 | 7,440 | Talking to planners |
| Share of run time | 62 / 412 | 15.0% | 100% minus performance |
| Share of scheduled time | 62 / 450 | 13.8% | OEE points lost |
The last two rows cause the most confusion. Performance here is 350 ÷ 412 = 85.0%, but raising it to 100% adds 13.8 OEE points, not 15, before quality.
That is because performance only applies to the time the line ran. To turn it into OEE points, multiply by availability: (412 ÷ 450) x (62 ÷ 412) = 62 ÷ 450 = 13.8%.
Check it against the whole shift
Say 41,160 of the cartons were good, so 840 were bad. Those 840 are worth 840 ÷ 120 = 7 minutes at the ideal rate.
Add the parts: 38 + 62 + 7 + 343 = 450. If your own numbers do not close like this, a count or a time is wrong.
The three factors agree: 91.6% x 85.0% x 98.0% = 76.2%. So does the short route, 343 ÷ 450 = 76.2%.
Split it: reduced speed or minor stops?
The 62 minutes hold two problems with different fixes. You need one more number to separate them: how long the short stops added up to.
Example: the machine's stop signal or a run counter shows 48 short stops of about 25 seconds, none of them in the log. That is 48 x 25 ÷ 60 = 20 minutes.
Take out the short stops and the line truly ran for 412 - 20 = 392 minutes. Its speed while moving was 42,000 ÷ 392 = 107.1 per minute, against the ideal 120.
This matches the classic TPM split of performance into two rates, covered in net operating time. Here that is 392 ÷ 412 = 95.1% and 350 ÷ 392 = 89.3%, and together they make 350 ÷ 412 = 85.0%.
If you have no stop signal, watch the machine with a stopwatch for 30 minutes and scale up with care. Then use the lists in causes of reduced speed and what micro-stops are.
Do it hour by hour
A shift total tells you how much, and hourly numbers tell you when. Run the same sum for each hour.
| Hour | Run min | Units | Units / 120 | Speed loss |
|---|---|---|---|---|
| 1 | 60 | 6,000 | 50.0 | 10.0 min |
| 2 | 60 | 6,600 | 55.0 | 5.0 min |
| 3 | 45 | 4,200 | 35.0 | 10.0 min |
| 4 | 60 | 5,400 | 45.0 | 15.0 min |
Hour 4 loses the most, so ask what changed. A new pallet of blanks, a crew change or a warm machine is often easier to spot this way than in a shift total.
With more than one product
Add up the theoretical time per product, and take the total from run time. Do not use an average rate.
Example: in 400 minutes of run time, a machine makes 18,000 of product A at 120 per minute and 10,500 of product B at 70 per minute. That is 150 + 150 = 300 theoretical minutes, so speed loss is 100 minutes.
What it is worth
Only count money if you can sell the extra units, or stop paying for overtime. Example: at a hypothetical margin of 0.10 per carton, 7,440 cartons are worth 744 per shift.
The hidden factory calculator does this over a year. If the line has no demand for more, the same minutes are still worth having as fewer shifts.
Mistakes that change the answer
- Using good units in the formula. That counts bad units twice, as speed loss and as quality loss.
- Using planned time in place of run time. Stops then get counted as speed loss too.
- Moving the stop threshold and calling it a gain. A longer threshold moves minutes from availability to speed loss, and the stop threshold page shows that the total stays the same.
- A negative answer. Speed loss below zero means performance is over 100%, so check the rate and the counter.
The split above is hard because short stops leave no record. Fabrico reads every stop from the PLC or IoT sensors and shows it as minutes of OEE lost per line and shift, and where cameras are fitted, the video of any stop can be streamed on request next to its machine data. See how Fabrico uses cameras for OEE.
What people ask next
What is the formula for speed loss in OEE?
Speed loss in minutes = run time - (total units ÷ ideal rate). As a share of the shift, divide by scheduled time. The factor it lowers is explained in how to calculate OEE performance.
Is speed loss the same as 100% minus performance?
That is the speed loss as a share of run time. As a share of scheduled time, it is smaller, because you multiply by availability. Use the scheduled-time figure when you add losses up to 100%.
Do minor stops count as speed loss?
In the three-factor sum, unlogged short stops land in performance along with slow running, so yes. Separate the two with a counter or stop signal, since the fixes differ, as minor stops vs breakdowns explains.
Can I calculate speed loss with no stop log?
Not on its own, since you need run time to separate it from stops. You can still get stops and speed loss together: scheduled time minus total units ÷ ideal rate. An hour meter or a stack light signal gives you run time cheaply.
What if my speed loss is negative?
Then the line made more than the ideal rate allows, which should not happen. The ideal rate is too low or the counter counts wrong, and performance over 100% shows how to fix it.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.