A readout to a client's leadership team
Case study

FedEx improved package volume forecast accuracy by 20%

FedEx had petabytes of shipment event data on Azure but no reliable way to turn it into production forecasts and delay alerts.

FedEx

FedEx · Operations · L2

20%more accurate package volume forecasts

The workflow before

FedEx moves more than 15 million shipments a day and records billions of tracking events a year. Data science teams worked in silos with different tools, and experimental models rarely reached production. Forecasts leaned on manual processes, and customers heard about delays after they happened. When COVID-19 hit, demand swung faster than the planning process could follow.

What we built

Working with Oliver Wyman, we built a machine learning environment on Azure Data Lake and Databricks over 44 weeks, from data foundation through production deployment.

We put four model families into production: package volume forecasts by lane and service, delivery time predictions, real-time delay prediction that triggers proactive customer notices, and shipping pattern analysis for segmentation and anomaly detection.

We added COVID-19 trigger conditions and scenario models so planners could test network stress and reallocate capacity as demand moved.

Before and after

MeasureBeforeAfter
Package volume forecast accuracyBaseline20% better
Peak period forecast errorBaseline15% lower
Missed delivery windowsBaseline25% fewer
Customer calls about delaysBaseline25% fewer

What's next

With forecasting and delay models in production, the next step is Level 3, Workflow Agents: acting on a predicted delay end to end, rerouting and rebooking with a person reviewing exceptions.

ShareLinkedInEmail

Operational event data flows through Azure Event Hubs into Azure Data Lake Storage Gen2, secured with Azure Active Directory. Databricks with Delta Lake handles engineering and feature generation, and a feature store keeps reusable features for all models.

Models (time-series forecasting and gradient boosting) are tracked and versioned in MLflow, deployed through GitHub Actions CI/CD with A/B testing, and monitored for drift and performance. Infrastructure is defined in Terraform.

Predictions are written back into FedEx operational systems so delay scores drive customer notifications in real time.

Next step

Let's build the case study we tell next.