Throughput Calculator
Calculate process throughput, identify the bottleneck station limiting output, and see how much capacity is lost to the constraint.
📈 Operations📐 Throughput = 1 / bottleneck cycle time; limited by the slowest station💼 Business
Station 1 cycle time (minutes)
Station 2 cycle time
Station 3 cycle time
Station 4 cycle time
Available hours per day
Yield rate (%)
Please enter valid values.
Formula & Reference
| Variable | Symbol | Formula | Units |
|---|---|---|---|
| Throughput Calculator | — | Throughput = 1 / bottleneck cycle time; limited by the slowest station | units per hour |
Step-by-Step Examples
Example 1
Unbalanced Line
Stations at 1.2, 2.4, 1.8, 1.5 minutes, 7.5 hours available, 96% yield.
- Bottleneck = Station 2 at 2.4 minutes
- Throughput = 60 / 2.4 = 25.0 units/hour
- Good units = 25.0 × 0.96 = 24.0/hour
- Daily = 180 good units
- Perfectly balanced at 1.725 min would give 34.8/hr — 39% higher
✓ 25.0/hr — Station 2 is the constraint
Example 2
Well Balanced
Stations at 1.9, 2.0, 1.95, 1.85 minutes.
- Bottleneck = Station 2 at 2.0 minutes
- Throughput = 30.0 units/hour
- All stations run 93 to 100% of bottleneck pace
- Little to gain from rebalancing
✓ 30.0/hr — well balanced
Example 3
Severe Constraint
Stations at 0.8, 0.9, 4.2, 1.0 minutes.
- Bottleneck = Station 3 at 4.2 minutes
- Throughput = 14.3 units/hour
- Other stations idle most of the time
- Balanced would give 34.3/hr — 140% higher
✓ 14.3/hr — severe bottleneck
Real-World Applications
Constraint Identification
Throughput is set entirely by the slowest station, so improving anything else changes nothing.
Line Balancing
Comparing actual throughput against a perfectly balanced line quantifies the opportunity from rebalancing.
Investment Targeting
Capital spend should go to the bottleneck. Upgrading a non-constraint station adds cost without adding output.
Capacity Planning
Throughput multiplied by available hours gives realistic daily capacity for order promising.
Common Mistakes to Avoid
⚠️
Improving non-bottleneck stations
Speeding up a station that is not the constraint produces no additional output, only more work-in-progress inventory piling up before the bottleneck.
⚠️
Ignoring yield
Gross throughput overstates usable output. Only good units count toward meeting demand.
⚠️
Assuming the bottleneck is fixed
Once the constraint is improved, a different station becomes the bottleneck. Improvement is iterative rather than one-off.
Frequently Asked Questions
What is throughput? ▾
The rate at which a process produces completed units, determined entirely by the slowest station in the sequence.
How do I find the bottleneck? ▾
It is the station with the longest cycle time. Work-in-progress inventory typically accumulates immediately before it.
Why does improving other stations not help? ▾
Because output is limited by the constraint. Faster upstream stations just build inventory in front of the bottleneck; faster downstream stations sit idle.
What is line balancing? ▾
Redistributing work so station cycle times are roughly equal, which raises throughput toward the theoretical maximum for the total work content.
Does the bottleneck move? ▾
Yes. After improving the current constraint, another station becomes the limiting factor, which is why throughput improvement is a continuous cycle.