Production capacity utilisation: % of capacity used
Production utilization shows the share of available capacity actually used over a period. It is an indicator of the balance of demand, schedules, setup, and execution discipline; it differs from OEE, which measures the efficiency and quality of equipment operation.
What the Metric Measures
How busy lines/shops are relative to their available (planned) capacity. It helps identify bottlenecks, adjust schedules, and make decisions on outsourcing/investments and TPM.
Calculation
- By time: Utilization, % = Productive time worked / Available time × 100
- By volume: Utilization, % = Actual output / Available output capacity × 100
- Available time = shift calendar × hours × days × equipment − planned downtime (maintenance, training, audits)
- For a multi-product mix, use standard hours or equivalent units
- Difference from OEE: utilization ≠ efficiency/quality; OEE = Availability × Performance × Quality
Calculation example
A line can produce 10,000 units a month and actually produced 7,800. Utilisation = 7,800 / 10,000 × 100 = 78%. Or in machine hours: 600 hours available, 468 in operation — the same 78%. A 22% reserve allows extra orders without investment.
Data Sources
MES/SCADA/PLC (states, cycles), ERP/1C (plan/actual, routings, standard time), APS (capacity calendars), CMMS (maintenance), shift timesheets, setup/changeover logs.
Interpretation
- 70–90% — a balanced mode with a "cushion" for variations and repairs
- >95% — risk of queues/WIP, defects, emergency downtime; relieve bottlenecks
- <60% — underloading; review the demand plan, batch sizes, shift patterns, setup time
- Monitor bottlenecks separately — the average can mask the problem
Useful Breakdowns
- Lines / shops / equipment; shifts / days of the week
- SKUs / product groups; processing vs setup / inspection
- Planned maintenance vs actual; in-house production vs outsourcing
Dashboard Visualizations
- Utilization trend by line/shop
- Heatmap by hour/shift
- Capacity vs Load: available capacity versus demand
- Gantt of schedules and waterfall of time losses (setup, minor stoppages, repairs)
- WIP/queues at the bottleneck, threshold breach alerts
How to Set Goals
Set target utilization by resource, taking into account demand volatility, SLA, and TPM; define a capacity cushion, alert thresholds, and rules for consolidating batches/rescheduling work, and introduce SMED to reduce setup.
Common Mistakes
- Calculating from a "theoretical" 24/7 without planned maintenance
- Confusion with OEE and double-counting setup
- Different shift calendars in the comparison base
- Ignoring the bottleneck (averaging masks overloading)
- Incorrect units (hours vs output), no standard time
- Uncleaned downtime due to lack of raw materials/documents
Questions for Discussion
- What effect would −30% setup at the bottleneck have?
- Is an additional shift or outsourcing partnership needed for demand peaks?
- What capacity cushion is optimal for your portfolio?
- How will a change in the SKU mix affect utilization and OTD?