MilleMiglia: Modeling the Hidden Middle Mile

Image for MilleMiglia: A realistic instance generator for middle-mile logistics

After studying this material, you should be able to:

  1. Define the three segments of logistics (first, middle, last mile) and distinguish their operational characteristics
  2. Explain why middle-mile logistics is mathematically more complex than standard Vehicle Routing Problems
  3. Identify the key constraints unique to middle-mile logistics
  4. Understand what MilleMiglia is, why it was created, and how it works
  5. Recognize the broader significance of standardized benchmarking in logistics research

Step-by-Step Study Material

Step 1: The Logistics Journey — Three Miles Explained

Think of a shipment traveling from a factory to your doorstep as a relay race with three distinct legs:

FACTORY → [FIRST MILE] → Regional Hub → [MIDDLE MILE] → Distant Hub → [LAST MILE] → YOUR DOOR
SegmentWhat HappensWho Handles ItTime Scale
First MileFactory → Regional Distribution CenterSingle truckHours/1 day
Middle MileHub → Hub across regions/countriesMultiple trucks, multiple handoffsDays/week
Last MileLocal Hub → ConsumerSingle delivery vehicleHours/1 day

Key Insight

First and last mile = one shipment, one vehicle Middle mile = one shipment, MANY vehicles

Real Example (From the Article)

Groningen (NL) → Utrecht Hub → Antwerp Hub → Paris Hub → Versailles
     [First Mile]      [-------- Middle Mile --------]    [Last Mile]

Step 2: Why Middle Mile Is Fundamentally Different

The Relay Race Problem

In first/last mile logistics, optimization is relatively straightforward:

Standard VRP Question:
"Which vehicle visits which stops, in what order?"

In middle-mile logistics, the question becomes far more complex:

Middle Mile Question:
"Which shipment travels on which sequence of vehicles,
 across which hubs, timed to catch which connections?"

The Synchronization Challenge

Imagine your shipment arriving at a hub. It must:

  1. ✅ Arrive within a specific time window
  2. ✅ Be unloaded and sorted
  3. ✅ Be consolidated with other freight
  4. Catch the next scheduled truck to its destination
If it MISSES the connection:
Shipment waits → Significant delay → Customer unhappy

This is called a synchronization problem — timing dependencies cascade across the entire network.


Step 3: The Mathematical Structure — Why Existing Solvers Fail

Standard VRP vs. Middle-Mile Model

FeatureStandard VRPMiddle-Mile
Mathematical modelVehicle routing/sequencingMulti-commodity flow on space-time graph
Time horizonSingle dayMulti-day
Vehicle assignmentsOne vehicle per shipmentMultiple vehicles per shipment
SchedulesFlexible routingFixed vehicle schedules
ConstraintsFew, often relaxableMany, non-relaxable

Key Constraints Unique to Middle Mile

Think of these as hard rules that cannot be bent without breaking the real-world model:

1. FIXED SCHEDULES
   Trucks depart at set times — you cannot reschedule them

2. THROUGHPUT LIMITS
   Distribution centers can only process X shipments per hour

3. CONNECTION TIMING
   Shipment must arrive before truck departs — no exceptions

4. MULTI-DAY HORIZON
   Planning spans days, not hours

Why This Matters

Because of these dependencies, existing VRP solvers cannot be applied to middle-mile problems. The problem structure is fundamentally different.


Step 4: The Research Gap — Why MilleMiglia Was Needed

The Problem with Existing Research

Academic Research Progress requires:
    → Standardized benchmark data
    → Publicly available test instances
    → Reproducible experiments

Middle-Mile Research had:
    → No public datasets
    → Proprietary company data (trade secrets)
    → No standardized benchmarks

This created a chicken-and-egg problem:

  • Researchers couldn't develop solvers without data
  • Companies wouldn't share data without proven solvers

Historical Research Imbalance

Research Attention:
First Mile  ████████████  (well studied)
Last Mile   ████████████  (well studied)
Middle Mile ██            (significantly understudied)

Yet Middle Mile = largest portion of logistics COST

Step 5: What MilleMiglia Is and How It Works

Definition

MilleMiglia is an open-source C++ instance generator that creates realistic, synthetic middle-mile logistics benchmarks — without exposing any real company data.

How It Generates Realistic Data

The key innovation is using statistical distributions calibrated against real-world data:

Real Industrial Data (private)
         +
Public Information from Industry
         ↓
Statistical Distributions
         ↓
Synthetic Instances that LOOK real
but CONTAIN no proprietary information

This is similar to how a map simulator can generate realistic-looking cities without copying any actual city.

Technical Architecture

MilleMiglia Components:
┌─────────────────────────────────────┐
│  C++ Generator Core                 │
│  ↓                                  │
│  Protocol Buffers (data format)     │  ← Single compact file per instance
│  ↓                                  │
│  Generated Instance includes:       │
│    • Fixed vehicle schedules        │
│    • Hub throughput limits          │
│    • Synchronization requirements   │
│    • Demand volumes                 │
│    • Network topology               │
└─────────────────────────────────────┘

Why Protocol Buffers?

  • Language-agnostic (solvers in Python, Java, C++ can all read it)
  • Compact file size
  • All constraints embedded in one file

Step 6: The Broader Significance

Analogy to Existing Research Infrastructure

DomainBenchmark LibraryPurpose
Capacitated VRPCVRPLIBStandardized test instances
Middle-MileMilleMigliaStandardized test instances

MilleMiglia aims to do for middle-mile research what CVRPLIB did for VRP research — create a common language and testing ground.

Applications Enabled

MilleMiglia instances can be used for:

1. ALGORITHM DEVELOPMENT
   → Test new optimization solvers

2. MACHINE LEARNING
   → Generate massive datasets to train ML models

3. BENCHMARKING
   → Compare solver performance fairly

4. ACADEMIC RESEARCH
   → Publish reproducible results

Real-World Impact Chain

Better Benchmarks
      ↓
Better Algorithms
      ↓
Better Middle-Mile Optimization
      ↓
Lower Logistics Costs + Faster Delivery
      ↓
Your poffert arrives FRESH 🥞

Summary: Concept Map

LOGISTICS NETWORK
├── First Mile (VRP) → well-studied
├── Middle Mile → UNDERSTUDIED
│   ├── Characteristics
│   │   ├── Multi-vehicle per shipment
│   │   ├── Fixed schedules
│   │   ├── Hub synchronization
│   │   └── Multi-day horizon
│   ├── Math Model: Multi-commodity flow on space-time graph
│   ├── Problem: No public benchmark data
│   └── Solution: MilleMiglia
│       ├── Synthetic but realistic instances
│       ├── Statistical distributions
│       ├── Open-source C++
│       └── Protocol Buffer format
└── Last Mile (VRP) → well-studied

Self-Check Questions

  1. What makes middle-mile logistics a relay race rather than a simple delivery?
  2. Why can't standard VRP solvers handle middle-mile problems?
  3. What happens if a shipment misses its connection at a distribution center?
  4. How does MilleMiglia generate realistic data without revealing private information?
  5. What is the analogy between CVRPLIB and MilleMiglia?
  6. Name three constraints unique to middle-mile logistics that cannot be relaxed.

More to study