The most common capacity planning mistake is designing a system to run at 100% of its rated throughput. Queueing theory shows why this fails: throughput does not degrade linearly as utilization approaches 100%. It collapses.
This applies to every resource in a warehouse, including sorters, dock doors, AMR fleets, AS/RS cranes, and pack stations. The math is the same in each case.
Why Throughput Collapses Before 100%
The M/M/1 queueing model (single server, random arrivals, random service times) gives the expected wait time at any utilization level:
Average wait time = (utilization / (1 - utilization)) × average service time| Utilization | Wait multiplier | Interpretation |
|---|---|---|
| 50% | 1.0x | Wait = 1 service time |
| 70% | 2.3x | Wait = 2.3 service times |
| 80% | 4.0x | Wait = 4 service times |
| 90% | 9.0x | Wait = 9 service times |
| 95% | 19.0x | Wait = 19 service times |
What this means in practice: A sorter designed for 10,000 items/hour running at 90% utilization does not deliver 9,000 items/hour. It delivers significantly less, because demand variability creates queues that can’t clear fast enough. The stated throughput is the theoretical maximum under perfectly uniform arrival conditions, which never exist.
The 80% Design Rule
Design every major throughput resource to no more than 80% utilization at design-day peak volume.
- Sorter: design throughput / 0.80 = rated sorter capacity to specify
- Dock doors: (peak trailers × dwell time) / (shift hours × 0.80) = doors required
- AMR fleet: size to 70% utilization at peak (see AMR Fleet Sizing for the queueing derivation)
- AS/RS cranes: design throughput / 0.80 = required crane count
- Pack stations: peak orders/hr / 0.80 = stations to staff
The 20% headroom absorbs: arrival variability, service time variability, minor equipment faults, and the natural unevenness of real operations.
Where This Rule Gets Violated
In automation business cases: Vendors present system throughput at 85-95% utilization to minimize the equipment count and reduce the quoted capital cost. The system ships, goes live, and immediately has throughput problems. The shortfall is not a defect, it was in the specification.
Require vendors to state throughput at 80% utilization in the RFP response. If a vendor only provides nameplate throughput without stating the utilization assumption, ask.
In labor planning: The same math applies to pick stations. A pack zone designed for 12 packers at “100% efficiency” will queue the moment one station has a problem, a supply shortage, or an unusually complex order. Design for 10 packers at 80% efficiency; the 12th and 13th packer are surge capacity.
In building design: Dock doors are often sized to current-year trailer volumes at 90%+ utilization. At 90%, any above-average day creates spillover onto the yard. Dock scheduling software helps, but the right answer is 80% utilization at design-day peak.
The Storage Utilization Version
The same principle applies to storage capacity, for different reasons.
At 85%+ rack utilization, WMS putaway logic runs out of optimal locations and starts placing product in suboptimal slots. Double-handling increases. Replenishment cycles break down. Inventory accuracy problems appear.
Operating ceiling: 85% storage utilization during normal operations. Design to 85% at the expected peak inventory level, not the average. See Facility Layout Design for space program sizing methodology.
The Diagnostic
If an operation is running with chronic throughput complaints and the utilization data shows consistent 85%+ on any major resource, that resource is not undersized. It is undersized relative to what it was designed for. The fix is either additional capacity, demand smoothing (staggered release windows, dock scheduling), or a design review to confirm the utilization ceiling was applied at specification.