Speed Loss and Micro-Stoppage Calculator
Performance is the least understood part of OEE. It hides two different problems: the machine running slower than its ideal cycle, and the many short stops nobody logs. This calculator separates them, so the team knows whether to chase tooling and parameters or jams and starvation.
Your numbers
Average time per part when the machine is actually cycling.
Time the machine was scheduled and not in a recorded stop.
Stops too short to be logged as downtime, typically under 5 minutes.
Your results
Performance is capped at 100 percent in practice. A value above that means the ideal cycle time is set too slow and should be revalidated.
Performance rate vs actual cycle time
Sweeps Average actual cycle time while running from 12 to 18, holding your other inputs fixed.
Capture minor stops without extra keying
Optional: we can discuss how to bring counter and stop data into reporting your supervisors already use.
Optional. The tool and every export work without this. No spam.
How to use it
Take a shift or a day. Enter the ideal cycle time, the average cycle time while running, and the run time after recorded downtime. Then count minor stops, those too short to appear in your downtime log, and their average duration. The calculator splits the performance loss into a stop component and a speed component, shows the performance rate and counts the parts lost against the ideal. Count stops from machine counters or video for a few shifts rather than relying on memory.
- Use a validated ideal cycle time, not a guess
- Sample at least three shifts to find the average stop duration
- Record minor stops with a reason code where possible
Formula and logic
Performance equals parts produced times ideal cycle time, divided by run time. When stops remove time from cycling, parts equal cycling time divided by actual cycle time. That expands to: one minus the stop share, minus the cycling share times one minus ideal over actual. So performance equals 100 minus stop loss minus speed loss, and each loss is shown separately. This is the standard treatment of reduced speed and minor stops, two of the six big losses. Keep the definitions consistent over time, otherwise trends mislead.
Worked example
A 7 hour run with a 12 second ideal and 14.5 second actual cycle, plus 35 stops averaging 40 seconds. Stops cost 1,400 seconds, about 5.6 percent. The machine cycles for 23,800 seconds, making roughly 1,641 parts instead of an ideal 2,100. Speed loss is about 16.3 percent, so performance is 78.2 percent and 459 parts are lost. Here the slow cycle is the larger lever: check feeds, speeds, and conservative operator settings before chasing stops.
Common mistakes
Setting the ideal cycle time to what the machine currently achieves hides speed loss completely and makes OEE look healthy. Another is logging stops only above five minutes, which pushes dozens of small stops into performance without any evidence. Operators also slow machines down on purpose to avoid stops, so compare speed and stop losses together before declaring a fix.
- Do not set ideal equal to current average
- Do not ignore stops under five minutes
- Watch for speed being lowered to hide stops
Frequently Asked Questions
What counts as a micro-stoppage?
A short interruption, usually under about five minutes, that the operator clears without a maintenance call: a jam, sensor trip, or starved feeder. They rarely get logged as downtime, so they land in performance loss.
Why is my performance over 100 percent?
The ideal cycle time is set too slow, or counts are wrong. Revalidate the ideal against design capacity or best demonstrated rate and fix the reference before using OEE for decisions.
How do I get the average actual cycle time?
Divide cycling time by parts produced, where cycling time is run time minus the time lost to minor stops. Machine counters and timestamps give this reliably; a stopwatch gives a rough check.
Which loss should I attack first?
Start with whichever is larger in your result, and with the cheapest cause. Speed loss often responds to parameter and tooling changes; minor stops usually respond to cleaning, standards and sensor fixes.
If machine counters or PLC signals already exist, we can help bring cycle and stop data into a read-only view alongside your ERP production reporting.
Related Tools
OEE Improvement Payback Calculator
Convert a planned OEE improvement into extra units, margin, payback and ROI so the project can be funded on numbers.
Costing & FinanceImprove OEE vs Buy a New Machine Calculator
Compare the annual cost per extra unit from an OEE improvement project against buying more capacity.
Industry TemplatesOEE Improvement A3 Charter Template
A fill-in A3 style project charter that captures baseline OEE, the biggest loss, countermeasures and follow-up on one document.
Discrete ManufacturingOEE Calculator (Overall Equipment Effectiveness)
Break your Overall Equipment Effectiveness into availability, performance, and quality, and see how far you sit from the 85% world-class benchmark.
Field Service & QualityMTTR Improvement Value Calculator
See what each hour of mean-time-to-repair reduction is worth per year in avoided downtime and labor, based on your incident volume and downtime cost.
More MES & Shop Floor tools
See all- Line Balancing Worksheet
- SMED Changeover Reduction Worksheet
- Finite Capacity Scheduling Worksheet
- Production Schedule Template
- Bottleneck Analysis Calculator
- Drum Buffer Rope Buffer Sizing Calculator
- Production Schedule Adherence Calculator
- Production Schedule Release Checklist
- Daily Production Schedule Board Worksheet