After studying this material, you should be able to:
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
| Segment | What Happens | Who Handles It | Time Scale |
|---|---|---|---|
| First Mile | Factory → Regional Distribution Center | Single truck | Hours/1 day |
| Middle Mile | Hub → Hub across regions/countries | Multiple trucks, multiple handoffs | Days/week |
| Last Mile | Local Hub → Consumer | Single delivery vehicle | Hours/1 day |
First and last mile = one shipment, one vehicle Middle mile = one shipment, MANY vehicles
Groningen (NL) → Utrecht Hub → Antwerp Hub → Paris Hub → Versailles
[First Mile] [-------- Middle Mile --------] [Last Mile]
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?"
Imagine your shipment arriving at a hub. It must:
If it MISSES the connection:
Shipment waits → Significant delay → Customer unhappy
This is called a synchronization problem — timing dependencies cascade across the entire network.
| Feature | Standard VRP | Middle-Mile |
|---|---|---|
| Mathematical model | Vehicle routing/sequencing | Multi-commodity flow on space-time graph |
| Time horizon | Single day | Multi-day |
| Vehicle assignments | One vehicle per shipment | Multiple vehicles per shipment |
| Schedules | Flexible routing | Fixed vehicle schedules |
| Constraints | Few, often relaxable | Many, non-relaxable |
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
Because of these dependencies, existing VRP solvers cannot be applied to middle-mile problems. The problem structure is fundamentally different.
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:
Research Attention:
First Mile ████████████ (well studied)
Last Mile ████████████ (well studied)
Middle Mile ██ (significantly understudied)
Yet Middle Mile = largest portion of logistics COST
MilleMiglia is an open-source C++ instance generator that creates realistic, synthetic middle-mile logistics benchmarks — without exposing any real company 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.
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 │
└─────────────────────────────────────┘
| Domain | Benchmark Library | Purpose |
|---|---|---|
| Capacitated VRP | CVRPLIB | Standardized test instances |
| Middle-Mile | MilleMiglia | Standardized test instances |
MilleMiglia aims to do for middle-mile research what CVRPLIB did for VRP research — create a common language and testing ground.
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
Better Benchmarks
↓
Better Algorithms
↓
Better Middle-Mile Optimization
↓
Lower Logistics Costs + Faster Delivery
↓
Your poffert arrives FRESH 🥞
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