UPS 2013 Christmas delivery capacity meltdown
UPS failed to deliver a large number of packages in time for Christmas 2013, disappointing customers of major e-commerce retailers including Amazon.
The damage was public. The root cause was preventable.
UPS failed to deliver a large number of packages in time for Christmas 2013, disappointing customers of major e-commerce retailers including Amazon.
What the software actually got wrong
UPS's shipment-volume forecasting and capacity-planning systems significantly underestimated how much last-minute e-commerce volume the network would need to absorb that holiday season, especially given increasingly aggressive guaranteed-delivery promises from retailers, leaving the network without enough capacity to handle the actual surge.
UPS's shipment-volume forecasting and capacity-planning systems significantly underestimated how...
UPS's shipment-volume forecasting and capacity-planning systems significantly underestimated how much last-minute e-commerce volume the network would need to absorb that holiday season, especially given increasingly aggressive guaranteed-delivery promises from retailers, leaving the network without enough capacity to handle the actual surge.
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.