Throughput Calculator measures completed and good-unit output per hour from a real production period. Compare your observed rate with a demand target and an optional ideal cycle, while keeping scheduled time, downtime, quality, and performance definitions clear. Results appear after you calculate.
Enter observed production
Throughput Calculator formulas
The main Throughput Calculator rate includes unplanned stops in its denominator and is therefore a delivered-output measure for the scheduled production window. The run rate excludes those stops and describes pace while operating. Neither is a count of items started, in process, or reworked later. Use the same counting boundary for all inputs.
How to use this Throughput Calculator
Select a completed period, such as one shift. Enter the minutes scheduled for production after removing time when output was not planned. Enter unplanned downtime within that scheduled period. Count total completed pieces at the process or line output and first-pass rejects among them. The good count equals total minus rejects. Use this Throughput Calculator for the same time and count boundary. The calculator requires at least one good unit so the seconds-per-good-unit measure is defined; periods with zero good output should be recorded separately as zero throughput.
Optionally enter a good-unit target per planned hour. This target uses the same denominator as the main throughput measure, so the period target equals hourly target multiplied by planned production hours. Optionally enter ideal cycle time for the process constraint. That comparison reports an ideal running rate and OEE-style performance ratio, which can exceed 100% if the chosen ideal cycle is slower than your observed average. Check the ideal cycle definition and count data if this happens.
Worked throughput example
For a Throughput Calculator example, a line has 480 planned production minutes, including 30 unplanned downtime minutes. It completes 900 units, including 45 first-pass rejects. Good output is 855 units and operating time is 450 minutes. Its delivered good-unit throughput is 855 ÷ 8 = 106.88 good units per planned hour. While operating, it makes 855 ÷ 7.5 = 114 good units per operating hour.
| Measure | Calculation | Result |
|---|---|---|
| First-pass yield | 855 ÷ 900 | 95% |
| Availability | 450 ÷ 480 | 93.75% |
| Effective planned seconds per good unit | 480 × 60 ÷ 855 | 33.68 s |
| Target good units | 110 × 8 planned hours | 880 units |
| Gap to target | 855 − 880 | −25 units |
| Performance at 25-second ideal cycle | 25 × 900 ÷ (450 × 60) | 83.33% |
The Throughput Calculator shows a target shortfall of 25 good units in this period. At the measured good-unit run rate, that represents about 13.16 additional operating minutes, assuming the same yield and running pace. Do not automatically treat this as a scheduling solution: the root cause might be downtime, rejects, or a speed constraint.
Throughput versus cycle time, takt, and OEE
Throughput is the number of units crossing a defined process boundary per time period. Cycle time gives the interval between completed units while operating. Takt is the customer-demand interval based on planned production time. OEE combines availability, performance, and quality against an ideal cycle. These metrics answer related but different questions, so label your denominator whenever sharing a rate.
Use the Cycle Time Calculator for measured cycles and stop-inclusive pace. Use the Takt Time Calculator to set demand rhythm. Use the OEE Calculator to separate downtime, speed, and quality losses, or the Production Capacity Calculator for a forward-looking multi-line plan. This Throughput Calculator reports measured output rather than forecasting future output.
Assumptions and measurement limits
The Throughput Calculator assumes one consistent production window, one output counting point, and comparable units. It treats rejects as first-pass rejects and does not model rework later recovered, work in progress, mixed products with different ideal cycles, shifts with different schedules, bottlenecks elsewhere in a network, or statistical variation. If output is batched, count completed pieces as they cross the selected boundary, not intermediate transfers. If multiple products have different ideal cycles, calculate separate runs or use an appropriately weighted method before comparing performance.
OEE.com’s implementation guide recommends collecting good count at the process constraint and defining ideal cycle as the true theoretical minimum. Its cycle-time discussion distinguishes run pace from effective measures that include stop time. Those definitions inform this calculator’s separately labeled planned-time throughput, operating-time rate, and ideal-cycle comparison.
Frequently asked questions
Does the Throughput Calculator include downtime?
The headline good-unit throughput uses planned production time, including unplanned downtime. The separate operating rate excludes downtime. Both are displayed so the denominator is explicit.
Should I count rejected units?
Enter them separately from total completed units. The main result uses first-pass good units. The total-unit rate includes rejects, while yield shows their effect.
What happens when the ideal cycle is unknown?
Enter 0 for ideal cycle. The calculator still reports measured throughput, yield, availability, and target gap, and labels ideal-rate metrics as not provided.
Why can performance exceed 100%?
The supplied ideal cycle may be slower than actual average running cycle, or counts and time may use different boundaries. Recheck the ideal value and production records.
Is this Throughput Calculator the same as production capacity?
No. Throughput here is observed completed output in a measured period. Capacity is an estimate of possible output under stated future operating assumptions.
How do the downloads work?
In this Throughput Calculator, after calculation, Download PDF opens the browser print dialog for Save as PDF, and Download Excel provides an Excel-compatible CSV with the entered data and results.
Related production calculators