Time-to-output loss pathDemand boundary shown after the protected stage
Business
Production Line Capacity Calculator
Build a capacity promise from scheduled days and shifts rather than a nameplate rate. The model removes planned changeovers and maintenance, then applies operating uptime, first-pass yield, and a protection buffer before comparing saleable capacity with demand.
Protected good-unit capacity-
Expected good capacity-
Nameplate starts-
Net planned run hours-
Demand coverage-
Protected surplus / shortfall-
Capacity lost to planned stops-
Schedule status-
Protected capacity relative to entered demand
Capacity conversion path
Convert calendar minutes into a defensible customer promise
Retained capacityLoss or protection reserve
| Capacity layer | Calculation basis | Output | Units lost | Planning use |
|---|
Capacity planning sequence
How to build a protected production commitment
- Define the monthly calendar in days, shifts, and hours.
- Remove planned changeover and maintenance minutes once—before applying uptime.
- Use the constraint cycle for the complete line, not an unconstrained machine speed.
- Apply measured uptime and first-pass yield to the remaining run time.
- Reserve a protection buffer only after expected good output is known, then compare with demand.
Constraint logic
Why nameplate, expected, and protected capacity answer different questions
Nameplate capacity is a physical ceiling. Expected good capacity reflects the entered operating losses. Protected capacity is the volume a planner is willing to promise while retaining a defined reserve. Demand coverage should therefore use protected—not nameplate—capacity.
Detailed calculation process
Capacity formulas, units, and loss order
S = days × shifts × hours × 60R = max(0, S − changeovers × minutes/changeover − maintenance hours × 60)N = R × 60 ÷ cycle secondsG = N × uptime × yieldC = G × (1 − protection buffer)Default schedule reconciliation
From 352 calendar hours to a customer-facing capacity
- 22 × 2 × 8 = 352 hours, or 21,120 scheduled minutes.
- 44 × 28 = 1,232 changeover minutes; maintenance removes another 1,080 minutes.
- Net planned run = 18,808 minutes; at 36 seconds/unit this supports 31,347 starts.
- 91% uptime and 96% yield produce about 27,386 first-pass good units.
- An 8% protection buffer leaves about 25,195 committed units to compare with demand.
Planning decisions
Use the loss path to select a lever
- Reduce SKU changeovers only when sequencing and inventory tradeoffs are acceptable.
- Improve uptime with evidence from stop codes and mean-time measures.
- Improve yield without hiding rework labor or downstream inspection.
Scope limits
What this line-level model excludes
- Parallel-machine routing and product-mix cycle distributions
- Labor availability, material shortages, and warehouse constraints
- Random failure distributions and queueing between stations
- Seasonal daily demand and overtime premiums
Production capacity FAQ
Questions behind a capacity promise
Why not multiply nameplate capacity by one combined efficiency?
Separating planned stops, uptime, yield, and protection shows which loss can actually be changed.
Can the buffer be zero?
Yes, but the result becomes an expected point estimate rather than a protected commitment.
What should happen when planned stops exceed the schedule?
The model floors run time at zero and reports an infeasible schedule instead of producing negative capacity.
Practical examples
Production Line Capacity Calculator in real planning situations
- Size monthly output after a multi-SKU changeover plan.
- Find the demand shortfall created by maintenance and quality losses.
- Compare nameplate starts with protected customer-commit capacity.
Important note
Before relying on this result
Calculated from the entered values using the displayed accounting method. Reconcile material decisions with source records and applicable accounting policy.
Additional Production Line Capacity Calculator questions
Why is the buffer applied after yield?
The buffer protects the final saleable capacity promise, not raw machine starts.
Should planned maintenance also reduce uptime?
No. If maintenance is removed explicitly from scheduled time, uptime should measure losses inside the remaining planned run time.
What if changeovers exceed scheduled time?
The calculator stops at zero run time and flags the schedule as infeasible.
Does this model include parallel machines?
Use the line-level ideal cycle for the combined constraint or model each bottleneck separately.