925 Techies
← All case studies Logistics & Supply Chain

100 million fewer miles a year through route optimization

How carriers, 3PLs and shippers use AI for routing, forecasting, document automation and exception handling.

100MMiles saved per year, projected by UPS
10M galFuel saved per year
55,000US routes covered at full rollout

Figures: UPS, 2013–2016. Source and caveats below.

01 The problem

Logistics margins are thin and decided by small inefficiencies repeated many times: an extra mile per route, an empty backhaul, a truck waiting at a dock. Dispatchers and planners make these decisions under time pressure with incomplete information.

The back office is equally manual. Bills of lading, customs forms, rate confirmations and proof-of-delivery documents arrive as PDFs and photos and are keyed in by hand, and customers call to ask where their shipment is.

02 Where AI fits

A

Route and load optimization

Algorithms that sequence stops and build loads against delivery windows, driver hours, traffic and vehicle capacity.

B

Demand and capacity forecasting

Lane-level volume forecasts to position equipment and labor ahead of demand.

C

Document automation

Extraction from bills of lading, invoices and customs paperwork straight into the TMS, with exceptions flagged.

D

Exception management agents

Agents that watch for delays, notify the customer, propose a recovery plan and rebook with approval.

E

Predictive maintenance

Telematics data used to schedule service before a breakdown takes a vehicle off the road.

03 Reference architecture

The layers we put in place for a typical logistics & supply chain deployment, from your systems of record up to the people who review the output.

  1. L1TMS, WMS, ERP and telematics
  2. L2Document capture and extraction
  3. L3Forecasting and optimization engines
  4. L4Exception-handling agents
  5. L5Dispatcher and planner console
  6. L6Customer tracking and notifications

04 Real-world implementation

Public deploymentUPS2013–2016

UPS developed ORION (On-Road Integrated Optimization and Navigation) to compute delivery routes for its drivers. UPS projected that at full deployment across 55,000 US routes, ORION would cut about 100 million miles driven and 10 million gallons of fuel a year, with a corresponding reduction of roughly 100,000 metric tons of CO2. UPS has noted that saving one mile per driver per day is worth up to $50 million a year to the company.

100MMiles saved per year, projected by UPS
10M galFuel saved per year
55,000US routes covered at full rollout

Source: BSR case study on ORION adoption at UPS; UPS company statements. UPS is not a 925 Techies client.

What to keep in mind: These are UPS's own projections from the rollout period, and ORION took about a decade to develop. Mid-sized fleets now reach the same class of optimization with off-the-shelf solvers and current models in months.

05 Business impact

Cost per mile

Fewer miles and better-filled trucks reduce fuel, maintenance and driver hours directly.

Asset utilization

Better forecasts mean fewer empty miles and less idle equipment.

Back-office cost

Automated document entry speeds up billing and shortens days sales outstanding.

Service level

Proactive exception handling improves on-time performance and cuts "where is my freight" calls.

KPIs we baseline and track
Cost per mileEmpty milesOn-time deliveryDocuments processed without touchDays sales outstanding

06 Implementation roadmap

  1. Weeks 1–3

    Assess

    Baseline cost per mile, empty miles and document handling time. Pick one terminal, lane or document type.

  2. Weeks 4–9

    Prove

    Run the optimizer or extraction model alongside current operations and compare outcomes on the same days.

  3. Weeks 10–22

    Build

    Integrate with the TMS and driver apps. Train dispatchers and gather their overrides as feedback.

  4. Ongoing

    Operate

    Track adherence and savings by terminal, tune constraints, extend across the network.

07 Guardrails

  • Dispatchers can override any recommendation
  • Hours-of-service and safety rules are hard constraints
  • Low-confidence document fields go to a person
  • Savings measured against a baseline, by terminal

08 Services involved

Start here

Exploring AI in logistics & supply chain?

We can run a proof of concept on your own data in about four weeks, measured against the KPIs above.