Reduced Speed Loss

Reduced speed loss is production lost when a machine runs, but runs slower than its ideal cycle time. It is one of the six big losses, and it sits under the Performance factor of OEE. Because the line is still moving, it makes no noise and no event, which is why it is the loss most plants never see.

Everyone talks about breakdowns. A stopped line is loud, visible, and logged to the minute. Meanwhile a line running 10% under rate all shift, every shift, quietly loses more output than the breakdown anyone remembers, and nobody writes it down, because from across the floor the machine looks fine. This guide covers what reduced speed loss is, why it hides, what it actually costs, what causes it, and how to find and fix it.

What is reduced speed loss?

Reduced speed loss, also called speed loss or slow cycles, is the output a machine gives up by running below its ideal cycle time during the time it is running. The ideal cycle time is the fastest the process can sustainably run one unit; run slower than that and the difference is reduced speed loss. It is one of the six big losses and it lowers the OEE Performance factor.

Performance in OEE is defined as (ideal cycle time × total count) ÷ run time. Reduced speed drives total count down without changing run time, the machine is up and running the whole while, just producing fewer units than it should. That is what separates it from a breakdown: a breakdown steals run time and shows up in machine downtime; reduced speed steals output while the run-time clock says everything is fine.

Why is reduced speed the most underreported of the six big losses?

Because it does not generate an event. The five other losses all leave a mark someone notices: a breakdown stops the line, a changeover has a start and end, a minor stop trips a sensor, a defect fills a reject bin. Reduced speed produces nothing to react to. The machine is running, the operator is present, the counter is climbing, it just climbs slower than it should, and slow does not sound an alarm.

So it falls through every net built to catch downtime. A plant can have a disciplined downtime log, a tidy changeover procedure, and a full scrap-tracking system, and still be blind to reduced speed, because none of those systems are watching rate against the ideal. Among the six big losses reduced speed and minor stops together are usually the largest slice of OEE loss in any plant that has already fixed its big breakdowns, and reduced speed is the half of that pair nobody can point to.

How much does a slow line actually cost?

More than the breakdown everyone remembers. Here is the arithmetic with hypothetical numbers. A line has an ideal rate of 60 units per minute and runs an eight-hour shift, 480 minutes. At ideal it would make 28,800 units. Running 10% under rate, at 54 units per minute, it makes 25,920, a loss of 2,880 units per shift.

Now compare that to the breakdown the whole plant talks about. A 30-minute breakdown at 60 units per minute costs 1,800 units. The invisible 10% speed loss costs 2,880-60% more than the breakdown, and it happens every single shift, while the breakdown is a bad day. Put another way, a 10% speed loss is the equivalent of a 48-minute breakdown that no one logs, every shift:

A steady 10% speed loss burns roughly 200 hours of production a year on a single line, the equivalent of shutting the line down for five full 40-hour weeks, and it never appears in a downtime report. That is why chasing the last visible breakdown while ignoring rate is a losing trade.

What causes reduced speed loss?

Reduced speed usually traces to equipment condition, materials, environment, or people running the process below its capability. The common causes:

• Dirty or worn equipment. Worn bearings, belts, and cutting tools raise resistance and drag the effective rate down long before they fail outright.
• Poor lubrication. Under-lubricated moving parts run hot and slow, and operators back the speed off to keep them from binding.
• Substandard or variable materials. Off-spec stock, moisture, or inconsistent feed forces the line to run gently to avoid jams and defects.
• Poor environmental conditions. Heat, humidity, and dust change how a process behaves and often push the sustainable rate below the nameplate.
• Operator inexperience or caution. A crew that has been burned by jams or scrap will run below rate on purpose, and a newer operator may not know the line can go faster.
• Startup and shutdown. The ramp before a process reaches steady state runs slow by nature, and frequent restarts multiply that drag.

Notice how many of these are quiet, gradual, and easy to normalize. A line that has crept down to 90% of rate over two years feels normal to the people who run it every day. That is the trap: reduced speed becomes the new baseline, and the loss disappears into the definition of "normal." It is closely tied to equipment condition, which is why plants that run total productive maintenance a discipline the American Society for Quality describes as keeping equipment at its ideal operating condition to prevent breakdowns and slowdowns, recover speed loss as a side effect of the maintenance work itself.

How is reduced speed different from minor stops?

Both are Performance losses, but they lose output in different shapes. Reduced speed is a continuous shortfall, the line runs the whole time, just slow. Minor stops, also called idling and minor stoppages, are brief interruptions of a few seconds to a couple of minutes, a jam cleared by hand, a sensor false-trip, a quick adjustment, too short to count as downtime but frequent enough to add up. One is a steady drip; the other is a stutter.

They matter together because Performance is where they both land, and Performance is typically the largest single source of OEE loss once the major breakdowns are handled. Telling them apart matters for the fix: minor stops are a reliability and mistake-proofing problem, while reduced speed is a condition, materials, or standards problem. Lump them into one "performance" number and you cannot tell which lever to pull.

How do you find and fix reduced speed loss?

You cannot fix a loss you cannot see, so finding it comes first, and finding it means comparing actual rate to a real ideal, minute by minute. A dependable sequence:

1. Set an honest ideal cycle time. Not the sales-brochure number and not the current average, but the fastest the process has reliably sustained. Everything downstream compares to this, so a soft ideal hides the loss.
2. Measure actual rate continuously, not per shift. A shift total averages the loss away. You need rate over time to see when and where the line runs slow, which points at the cause.
3. Split Performance into minor stops and reduced speed. Time the short stops so what remains is true slow-running. Now you know which of the two problems you have.
4. Trace the slow-running to its cause. Walk the line while it runs under rate and check the usual suspects, tooling wear, lubrication, material feed, temperature, and whether the crew is holding speed back on purpose.
5. Restore condition and standard. Fix the worn or dirty component, correct the material or environment, and set a written standard rate the crew can run to with confidence. Autonomous and preventive maintenance keep it there.
6. Put actual-versus-ideal rate on a live board. Reduced speed only stays fixed when the gap is visible in the moment. Post rate against target where the crew sees it and it stops drifting back down.

How does reduced speed loss connect to OEE and the plant?

Reduced speed is the quietest term in the OEE equation and often the most valuable to recover, because it needs no capital, the machine is already there, already running, just leaving output on the floor. Recovering it lifts throughput with no new equipment, which is why it belongs on the manufacturing KPI board next to availability, not buried inside a single OEE percentage.

The catch, again, is visibility. Reduced speed loss stays hidden precisely because it produces no event to capture, and a plant running on paper only sees rate when someone works out the shift total the next morning, long after the slow-running is over. Capturing rate continuously at the point of work, the way Harmony logs production activity live and feeds real-time boards and automatic production reporting off one record (see the platform), is what turns reduced speed from an invisible tax into a number you can watch and drive down. That is also the argument for pairing a live board with the shift report, see real-time vs shift reporting and the shift CLS made from paper logs to real-time capture is worked through in the CLS case study.