Production worked example
Throughput at 63% uptime: a worked example
Here is what the math looks like when conditions slip. We hold every other input steady and drop uptime to 63%, then walk the calculation through step by step. Estimate hourly, shift, and daily output from cycle time, uptime, and yield.
The inputs for this scenario
- Cycle time: 36 sec / unit (held at the documented default)
- Uptime: 63 % (the input this scenario stresses; the baseline uses 88)
- Shift length: 8 hr (held at the documented default)
- Shifts per day: 2 shifts (held at the documented default)
- Good yield: 97 % (held at the documented default)
Working through the calculation
- The calculation starts from the formula this tool documents: Gross rate = 3,600 รท cycle time.
- Good throughput works out to 61.11 units / hr at these inputs, and this is the headline figure for the scenario.
- Gross rate works out to 100 units / hr at these inputs.
- Units per shift works out to 489 units at these inputs.
- Units per day works out to 978 units at these inputs.
How this compares with the baseline
- Against the tool's baseline example, where uptime sits at 88% and the headline result is 85.36 units / hr, this scenario comes in 28.41% below the baseline at 61.11 units / hr.
- The practical read: the gap between this scenario and the baseline is entirely attributable to uptime, so recovering it is worth quantifying in dollars before considering equipment or staffing changes. It assumes one cycle time, one uptime, and one yield for the whole run; mixed parts, ramp-up, or a true bottleneck upstream will make the daily figure optimistic.
Results at a glance
- Good throughput: 61.11 units / hr (headline result)
- Gross rate: 100 units / hr
- Units per shift: 489 units
- Units per day: 978 units
Run it with your numbers
- To rerun this with your own numbers, open the live Throughput calculator, set uptime to your actual value, and adjust the remaining inputs to match your operation.
Last reviewed 2026-05-12.