Reduced speed loss and minor stops are the two Six Big Losses that both cut into the Performance factor of OEE, but they are different problems that demand different fixes. Reduced speed loss is time the machine keeps running below its rated cycle rate, while minor stops (also called idling and minor stoppages) are brief, self-cleared interruptions of a few seconds to a couple of minutes. Both silently erode throughput, and because they land inside the same OEE factor, teams often lump them together and chase the wrong root cause. Separating them is the first move toward recovering hidden capacity.
Overall Equipment Effectiveness multiplies three factors: Availability, Performance, and Quality. Availability captures long downtime events. Quality captures defects and rework. Performance captures everything that makes the machine produce slower than its theoretical maximum while it is scheduled and running. That is exactly where both reduced speed and minor stops live.
The Performance factor is calculated as (Ideal Cycle Time multiplied by Total Count) divided by Run Time. Because it only compares actual output to ideal output over the run window, it cannot tell you why the gap exists. A machine drifting 8 percent slow and a machine that jams for 10 seconds every few minutes can post the identical Performance number. The math blends them. Your job is to unblend them before you spend a single euro on a fix.
Reduced speed loss occurs when equipment runs slower than its ideal or nameplate cycle rate. The machine is producing good parts, it just is not producing them fast enough. This loss is continuous rather than episodic, which is what makes it easy to normalize and forget.
Reduced speed is often a maintenance and standards problem. It responds well to condition-based maintenance, disciplined autonomous maintenance routines, and a documented ideal cycle time that everyone agrees is real.
Minor stops are short interruptions, usually under two minutes, that the operator clears without a maintenance call. They are so brief that most manual logs never capture them, yet in aggregate they can outweigh a couple of major breakdowns. The classic signature is high frequency, low individual duration.
Because minor stops recur in patterns, they are ideal candidates for Pareto analysis and structured root-cause work such as 8D problem solving or an A3. A failure mode and effects analysis on the top three stop locations often pays for itself in a week.
Consider a filling line with an ideal cycle time of 1.0 second per unit and a Run Time of 8 hours (28,800 seconds) in a shift.
Both lines report 87 percent Performance and roughly 25,000 units. Yet Line A needs a maintenance and setpoint review to close a chronic speed gap, while Line B needs an engineering fix at the jam points. Send the wrong crew and you burn the week. This is why splitting the loss, not just measuring the factor, is the real skill.
Manual clipboards almost never catch minor stops, so the split has to come from the machine signal itself. Capture a high-resolution stream of cycle events and apply a simple rule: any pause longer than a threshold (often 2 to 5 minutes, and always below your Availability downtime cutoff) counts as a minor stop, and any sustained cadence slower than ideal counts as reduced speed.
Once split, the losses route to different playbooks. Reduced speed connects to reliability metrics like MTBF and MTTR and to a shift away from reactive toward proactive maintenance. Minor stops connect to the constraint itself, so theory of constraints thinking helps you prioritize the stops on the bottleneck machine first.
You cannot split a loss you cannot see, and minor stops in particular are invisible to manual logging. Fabrico is the real-time data foundation for exactly this problem. It captures real-time OEE and production monitoring directly from the machine, including computer vision on equipment that has no PLC, so short stoppages and slow cadence are both recorded automatically instead of being missed on a clipboard. Every cycle and stop is timestamped, which lets you separate reduced speed loss from minor stops in your Performance factor and see the true frequency and location of each.
From there, Fabrico works as a field-ready CMMS: recurring stop reasons and speed-related degradation become work orders, assets carry their history, preventive schedules keep the fixes in place, and spare parts are tracked against the jobs. Fabrico is EU-built with EU data residency, so the data behind these decisions stays on European infrastructure. You can explore the pieces through the OEE monitoring overview and the CMMS overview.
Reduced speed loss is continuous: the machine keeps running but below its ideal cycle rate, producing good parts too slowly. Minor stops are episodic: brief interruptions of seconds to a couple of minutes that the operator clears without a maintenance call. Both reduce the Performance factor, but one is a cadence problem and the other is an interruption-frequency problem, so they need different countermeasures.
Minor stops are too short and too frequent for people to log by hand, so they never reach the record at all. Reduced speed is the opposite: it is visible but gets normalized, because a line running a little slow every day starts to feel like the standard rate. Automated cycle-level capture solves both by recording the true cadence and every short stop without relying on memory.
Split the two, then quantify the lost units from each using your own cycle data, and prioritize the larger number on your bottleneck machine. Minor stops often win on frequency and are quick to attack at specific jam points, while reduced speed usually needs a maintenance and setpoint review. A short Pareto pass on the data almost always makes the sequence obvious.
Ready to see reduced speed loss and minor stops split automatically from live machine data? Book a Fabrico demo and watch your Performance losses separate into problems you can actually fix.
Login
Blog