What is Performance (speed loss)?
Performance (speed loss) captures the difference between the ideal technical run rate of a line and the actual rate achieved during operating time. It highlights efficiency erosion caused by micro-stops and slow cycles, directly affecting throughput, marginal cost structure, and the financial productivity of fixed manufacturing assets.
Formula
Core definitions:
- Operating time (Run time) = Planned production time − Unplanned downtime
- Ideal run rate = 3600 ÷ Ideal cycle time (sec / unit)
- Actual run rate = Total units produced ÷ (Operating time ÷ 60)
Performance percentage:
Speed loss percentage:
Lost units from speed loss:
Lost time from slowdowns:
Ideal output at runtime:
Example
A line runs with:
- Planned production time: 480 min
- Unplanned downtime: 60 min
- Ideal cycle time: 45 sec/unit
- Total units produced: 540 units
- Operating time = 480 − 60 = 420 min
- Ideal output at runtime = 420 × 60 ÷ 45 = 560 units
- Performance approx 96.4%
- Speed loss = 3.6%
- Lost units = 560 − 540 = 20 units
- Lost time approx 15 min
The line is running at 96.4% of ideal speed, losing 3.6% performance — equal to 20 units of unrealized throughput, directly influencing cost per unit and asset-level financial returns.
How to Use the Performance (Speed Loss) Calculator
Use this calculator to compare how fast your line actually ran versus its ideal speed. Enter your shift time, downtime, ideal cycle time, and total units, then review the performance and speed loss numbers to see how much output you’re leaving on the table.
Set your planned production time
- In Planned production time (min), enter the total scheduled time for the line or machine (e.g., an 8-hour shift = 480 minutes).
Enter unplanned downtime
- In Unplanned downtime (min), add all unplanned stops (breakdowns, jams, waiting on materials, etc.). The calculator uses this to get your true Operating time:
Add your ideal cycle time per unit
- In Ideal cycle time per unit (seconds), enter the theoretical best-case time to produce one unit. The calculator converts this into an Ideal run rate (units/hour) and ideal output at runtime:
Enter the total units actually produced
- In Total units produced, input all units made during the operating time (good + scrap if you’re focusing purely on speed). The calculator compares this to the ideal output to compute performance and speed loss:
Review results and interpretation
- Check Performance and Speed loss at the top of the Results table, then look at supporting metrics: Lost units (vs ideal), Lost time from slowdowns, Ideal vs actual run rate, and Speed loss level. Use the bottom summary sentence to quickly communicate the impact (e.g., “Lost ~20 units (~15 min) across 420 min of runtime”) in meetings or reports.
Frequently Asked Questions
What does the performance % and speed loss % actually tell me about my line?
Performance shows how fast you really ran versus the theoretical max speed. Speed loss is simply the gap to 100% performance – it’s the percentage of output you left on the table because of slow cycles, micro-stops, or running below design speed.
Is a 3–5% speed loss acceptable, or should I be worried?
Single-digit speed loss (≈95–100% performance) usually indicates a well-tuned line with only minor slowdowns. Once speed loss consistently climbs above 10–15%, you’re likely losing significant output per shift and should treat it as a priority improvement area.
Can I use this calculator if I don’t track every micro-stop or minor slowdown?
Yes. As long as you know planned production time, unplanned downtime, ideal cycle time per unit, and total units produced, the calculator infers all speed losses (micro-stops, slow cycles, running intentionally slower) from the gap between ideal and actual output.
How does this performance/speed loss result connect to my OEE?
In OEE, performance is one of the three factors (Availability × Performance × Quality). The performance % from this calculator can plug straight into your OEE calculation, and speed loss is simply the part of OEE lost due to running below ideal speed rather than due to downtime or scrap.
Sources & Methodology