Solving CVRP with ACO

Minimizing Travel Cost for Complex Delivery Problems

Start With The Story

This scenario involves the Capacitated Vehicle Routing Problem, solved using the meta-heuristics algorithm Ant Colony Optimization. Basically, VRP is a network consisting of a number of nodes (sometimes called cities) and arcs connecting one to all others along with the corresponding costs. Mostly, the aim is to minimize the cost in visiting each customer once and only once. The term "capacitated" is added due to some capacity constraints on the vehicles (vcap).

Enter the problem. Some company wants to deliver loads to a number of customers. In this case, we have 24 nodes based on the location of Germany's train stations (don't ask why). The delivery always starts from and ends at the depot, visiting a list of customers in other cities. And then a number of questions arise:

  • How do we minimize the travel cost in terms of distance?
  • How many trucks are required?
  • Which cities are visited by the truck #1, #2. etc.?
Such questions are addressed by employing the ants.

How to use this page?
Two parameters can be adjusted:
  • depot: [0..23], def = 0
  • vcap: [200..400], def = 400
Calling this page without parameter will get the defaults. Otherwise, just try something like this

There is a way to set all the demands, but I don't think you are ready for that. 😉
Map
DEPOT: Berlin Hbf
VCAP: 300 vol.
ACTIVE: 14 customers
  1. Düsseldorf Hbf (55 vol.)
  2. Hannover Hbf (80 vol.)
  3. Stuttgart Hbf (70 vol.)
  4. Dresden Hbf (85 vol.)
  5. München Hbf (75 vol.)
  6. Leipzig Hbf (75 vol.)
  7. Dortmund Hbf (50 vol.)
  8. Nürnberg Hbf (45 vol.)
  9. Ulm Hbf (100 vol.)
  10. Köln Hbf (20 vol.)
  11. Kiel Hbf (95 vol.)
  12. Mainz Hbf (55 vol.)
  13. Würzburg Hbf (85 vol.)
  14. Freiburg Hbf (45 vol.)
Result
OVERALL | #TOURS: 4 | COST: 5072.13 km | LOAD: 935 vol. | VCAP: 300 vol.
Tour 1
COST: 1827.547 km
LOAD: 290 vol.

  1. München Hbf | 75 vol.
  2. Ulm Hbf | 100 vol.
  3. Stuttgart Hbf | 70 vol.
  4. Freiburg Hbf | 45 vol.

Tour 2
COST: 1187.501 km
LOAD: 290 vol.

  1. Würzburg Hbf | 85 vol.
  2. Nürnberg Hbf | 45 vol.
  3. Leipzig Hbf | 75 vol.
  4. Dresden Hbf | 85 vol.

Tour 3
COST: 1355.139 km
LOAD: 260 vol.

  1. Mainz Hbf | 55 vol.
  2. Köln Hbf | 20 vol.
  3. Düsseldorf Hbf | 55 vol.
  4. Dortmund Hbf | 50 vol.
  5. Hannover Hbf | 80 vol.

Tour 4
COST: 701.943 km
LOAD: 95 vol.

  1. Kiel Hbf | 95 vol.

ANTS
#generations: 10 for global, 5 for local
#ants: 5 times #active_customers

ACO
Rel. importance of pheromones α = 1.0
Rel. importance of visibility β = 10.0
Trail persistance ρ = 0.5
Pheromone intensity Q = 10

See this wikipedia page to learn more.

What kind of cost?
Directed driving distance, obtained through Google API. The visualization does not display that since the idea is VRP. Adding such feature is very easy, but not a priority for this case.
Can we use any address?
Yes, absolutely. What we need is the geo-coordinates of the addresses, and the distance matrix, which is not a problem. See my oldie master thesis here, implemented using PHP/MySQL for a delivery case in Darmstadt city, Germany.
Travel time as the cost?
Just replace the distance matrix with a duration matrix, then it is done. Please keep in mind, this feature is not intended for realtime use. But regarding the idea, not an issue.
Up to how many nodes?
There is no definitive answer for that. However, if a large number of nodes involved, a good strategy is required. Actually, for this one, a suitable technique is already implemented instead of a "plain" ACO. 

NETWORK
Depo: [1] Berlin Hbf | Number of cities: 24 | Total loads: 935 vol. | Vehicle capacity: 300 vol.
Loads: [0, 0, 55, 0, 80, 0, 70, 85, 0, 75, 0, 75, 50, 45, 0, 100, 20, 0, 95, 55, 85, 0, 0, 45]

ITERATION
Generation: #1
Best cost: 6349.352 | Path: [1, 2, 16, 12, 4, 11, 1, 7, 19, 20, 13, 1, 18, 6, 15, 1, 9, 23, 1]
Best cost: 6037.695 | Path: [1, 4, 12, 2, 16, 19, 1, 11, 7, 13, 20, 1, 18, 23, 6, 9, 1, 15, 1]
Best cost: 5787.739 | Path: [1, 6, 15, 9, 13, 1, 7, 11, 4, 12, 1, 19, 20, 16, 2, 23, 1, 18, 1]
Best cost: 5681.129 | Path: [1, 18, 4, 12, 2, 16, 1, 11, 7, 13, 20, 1, 9, 15, 6, 23, 1, 19, 1]
Best cost: 5122.058 | Path: [1, 23, 6, 15, 9, 1, 11, 7, 20, 13, 1, 4, 12, 2, 16, 19, 1, 18, 1]
Best cost: 5090.182 | Path: [1, 23, 6, 15, 9, 1, 7, 11, 13, 20, 1, 4, 12, 2, 16, 19, 1, 18, 1]
Best cost: 5086.196 | Path: [1, 23, 6, 15, 9, 1, 7, 11, 20, 13, 1, 4, 12, 2, 16, 19, 1, 18, 1]
Generation: #2
Best cost: 5074.872 | Path: [1, 9, 15, 6, 23, 1, 7, 11, 13, 20, 1, 4, 12, 2, 16, 19, 1, 18, 1]

OPTIMIZING each tour...
Current: [[1, 9, 15, 6, 23, 1], [1, 7, 11, 13, 20, 1], [1, 4, 12, 2, 16, 19, 1], [1, 18, 1]]
[2] Cost: 1190.097 to 1187.501 | Optimized: [1, 20, 13, 11, 7, 1]
[3] Cost: 1355.285 to 1355.139 | Optimized: [1, 19, 16, 2, 12, 4, 1]

ACO RESULTS
[1/290 vol./1827.547 km] Berlin Hbf -> München Hbf -> Ulm Hbf -> Stuttgart Hbf -> Freiburg Hbf --> Berlin Hbf
[2/290 vol./1187.501 km] Berlin Hbf -> Würzburg Hbf -> Nürnberg Hbf -> Leipzig Hbf -> Dresden Hbf --> Berlin Hbf
[3/260 vol./1355.139 km] Berlin Hbf -> Mainz Hbf -> Köln Hbf -> Düsseldorf Hbf -> Dortmund Hbf -> Hannover Hbf --> Berlin Hbf
[4/ 95 vol./ 701.943 km] Berlin Hbf -> Kiel Hbf --> Berlin Hbf
OPTIMIZATION RESULT: 4 tours | 5072.130 km.