Blog / Performance
Performance · Guide

Speed Losses in OEE: Definition, Formula, Example

OL By OEE Lab Editorial |Updated 1 November 2026 |7 min read
Short answer

Speed loss is the production time lost because a machine runs below its ideal rate while it is running. The formula is speed loss = runtime minus (units made divided by ideal rate), shown as a share of scheduled time. In OEE it is what pulls the performance factor below 100%: performance = theoretical time / runtime.

What is speed loss?

A machine can be running and still lose time. It runs, but slower than it should.

That lost time is speed loss. It sits in the performance part of OEE.

Nakajima's six big losses split it in two: reduced speed (running slower than the design rate) and idling and minor stoppages (short stops). Both show up as units that were never made.

Speed loss is not downtime. The machine never stopped long enough to log. It just made fewer units than the clock allowed.

The formula

You need three numbers: runtime, units made and the ideal rate. The ideal rate is the best rate the machine is accredited for, for that product.

Theoretical time = units made / ideal rate
Speed loss (min) = runtime - theoretical time
Speed loss (%) = speed loss (min) / scheduled time
Performance = theoretical time / runtime
Speed loss and performance (Hansen method)

This follows the method in Overall Equipment Effectiveness (R. C. Hansen, 2001): all units made, whether good or bad, count here. Bad units are a quality loss, not a speed loss.

Worked example

Example: a filling line has an ideal rate of 60 units per minute. The shift is 480 minutes. Logged stops add up to 60 minutes, so runtime is 420 minutes.

The line made 22,050 units in that time. Of those, 21,600 were good.

StepResult
Theoretical time for 22,050 units22,050 / 60 = 367.5 min
Speed loss420 - 367.5 = 52.5 min
Speed loss as share of scheduled time52.5 / 480 = 10.9%
Performance367.5 / 420 = 87.5%
Availability420 / 480 = 87.5%
Quality21,600 / 22,050 = 98.0%
OEE87.5% x 87.5% x 98.0% = 75.0%

Check it the simple way: 21,600 good units / 60 = 360 minutes of perfect running. 360 / 480 = 75.0%. Both routes agree.

Scheduled time100%
Stops (60 min)12.5%
Speed loss (52.5 min)10.9%
Waste (7.5 min)1.6%
Good output (360 min)75.0%
Where the 480 minutes went in the example. Stops 12.5%, speed loss 10.9%, waste 1.6%, good output 75.0%. They add up to 100%.

Speed loss is the second biggest slice here. Many teams chase the stops and never look at it.

Two kinds of speed loss in one number

The 52.5 minutes hide two different problems. You fix them in different ways.

  • Slow running. The machine runs all the time, but at a lower speed than ideal.
  • Short stops nobody logged. The machine halts for seconds, many times an hour. See micro-stops.

Example: a counter on the line shows 40 short stops of 30 seconds that never reached the log. That is 20 minutes. The other 32.5 minutes is slow running.

Split the two before you plan any fix. Slow running points to settings, materials and wear.

Short stops point to jams, sensors and feeding. The fix list is in how to reduce micro-stops.

Read speed loss by product

One shift average can hide the problem. Break it down by product.

Example: the same line ran two products in a week, each with its own ideal rate.

ProductIdeal rateRuntimeUnitsPerformance
Bottle A60 / min1,000 min57,00095.0%
Bottle B40 / min500 min15,00075.0%

Check: Bottle A is 57,000 / (1,000 x 60) = 95.0%. Bottle B is 15,000 / (500 x 40) = 75.0%.

The weighted performance for the week is the theoretical time over the runtime: (950 + 375) / 1,500 = 88.3%. Bottle B loses 125 minutes, against 50 for Bottle A, in half the runtime.

Now the team knows where to look first: the setting, the material or the wear on Bottle B.

Common causes of reduced speed

  • Operators run below the ideal rate to keep a poor material running.
  • Worn parts make the machine unstable at full speed.
  • A new or difficult product is run slower than the family rate.
  • The machine ramps up slowly after a restart. See startup losses.
  • Upstream or downstream equipment cannot keep up, so the machine is throttled.

Overall Equipment Effectiveness (R. C. Hansen, 2001) gives one plain example: running at half speed because of a raw-material problem is a speed loss.

How to measure it on the floor

  1. 1Fix the ideal rate. Use the best accredited rate for each product family. Do not use the speed you usually run.
  2. 2Count all units. Take the total units made in the run, good and bad, from a counter.
  3. 3Measure runtime. Scheduled time minus every logged stop.
  4. 4Compute theoretical time. Units divided by ideal rate. The gap to runtime is the speed loss.
  5. 5Look at it by product and by hour. A flat average hides the slow hours and the slow products.
Five steps to see speed loss on your own line

If you do not know the ideal rate, Overall Equipment Effectiveness (R. C. Hansen, 2001) suggests the rate from the best 4 hours of the last 400. It is a starting point, not a final answer.

For the other two factors, see how to calculate OEE. The full model is in the six big losses.

Common mistakes

  • Ideal rate set too low. If the ideal equals today's speed, performance reads 100% and the loss vanishes.
  • Performance above 100%. This means the ideal rate is wrong. Re-check it, or cap the value at 100% and note it.
  • Mixing products. One ideal rate for a fast and a slow product gives a false picture. Use a rate per product family.
  • Counting stops twice. Stop time is already out of runtime. Do not subtract it again.

Should you just run faster?

Not always. Overall Equipment Effectiveness (R. C. Hansen, 2001) warns that in a reactive area running below 70% OEE, a 10% speed-up usually gives only 3 to 6% more product. It can also hide a quality disaster.

His advice is to raise OEE first: going from 65% to 72% OEE gives the same 10% more output. Then speed up in a planned way, and re-accredit the new ideal rate once quality is proven.

Use the free OEE calculator to test your own numbers.

See it live in Fabrico

Speed loss only shows up when counts and stops are measured against an ideal rate. Fabrico takes stops, speed and counts live from PLCs or IoT sensors (external sensors on older machines), with add-on AI cameras counting output where a machine has no usable signal, then shows OEE per line and shift. See how Fabrico reads machine speed and counts.

Book a Fabrico demo

What people ask next

What is the difference between speed loss and micro-stops?

Speed loss is a slow run, while micro-stops are short halts. Both lower the performance factor, and both sit in the same bucket if the short stops are not logged. See micro-stops for how to find them.

Can performance be above 100%?

Only if the ideal rate is set too low. Treat it as a signal to re-check the rate for that product. For non-bottleneck machines you can cap performance at 100% and note the overspeed.

Is speed loss part of availability?

No. Availability counts logged stops. Speed loss is the time lost while the machine is running, so it belongs to performance.

How do I find speed loss without a data system?

Read a unit counter at the start and end of a run and note the clock time. Divide units by minutes and compare with the ideal rate. A simple log sheet next to it covers the stops.

What is a good performance figure?

There is no single number that fits every process. Compare each product with its own ideal rate and watch the trend. The way the three OEE factors combine is in how to calculate OEE.

Related guides: How to Calculate Downtime Percentage: Formula · Performance Over 100 Percent in OEE: Fix Guide · Causes of Reduced Speed on a Production Line · Speed Loss Calculation in OEE: Step by Step · Ideal Run Rate in OEE: How to Calculate It

← More OEE Lab guides · Open the OEE Calculator →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES