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: 20 customers
  1. Kassel-Wilhelmshöhe (45 vol.)
  2. Düsseldorf Hbf (80 vol.)
  3. Frankfurt Hbf (85 vol.)
  4. Aachen Hbf (40 vol.)
  5. Stuttgart Hbf (90 vol.)
  6. Dresden Hbf (65 vol.)
  7. München Hbf (100 vol.)
  8. Bremen Hbf (85 vol.)
  9. Leipzig Hbf (40 vol.)
  10. Dortmund Hbf (40 vol.)
  11. Nürnberg Hbf (35 vol.)
  12. Karlsruhe Hbf (50 vol.)
  13. Köln Hbf (80 vol.)
  14. Mannheim Hbf (55 vol.)
  15. Kiel Hbf (80 vol.)
  16. Mainz Hbf (100 vol.)
  17. Würzburg Hbf (85 vol.)
  18. Saarbrücken Hbf (50 vol.)
  19. Osnabrück Hbf (100 vol.)
  20. Freiburg Hbf (90 vol.)
Result
OVERALL | #TOURS: 5 | COST: 7174.169 km | LOAD: 1395 vol. | VCAP: 300 vol.
Tour 1
COST: 1211.245 km
LOAD: 270 vol.

  1. Mainz Hbf | 100 vol.
  2. Frankfurt Hbf | 85 vol.
  3. Würzburg Hbf | 85 vol.

Tour 2
COST: 1712.783 km
LOAD: 290 vol.

  1. München Hbf | 100 vol.
  2. Karlsruhe Hbf | 50 vol.
  3. Nürnberg Hbf | 35 vol.
  4. Leipzig Hbf | 40 vol.
  5. Dresden Hbf | 65 vol.

Tour 3
COST: 1354.834 km
LOAD: 285 vol.

  1. Köln Hbf | 80 vol.
  2. Aachen Hbf | 40 vol.
  3. Düsseldorf Hbf | 80 vol.
  4. Dortmund Hbf | 40 vol.
  5. Kassel-Wilhelmshöhe | 45 vol.

Tour 4
COST: 1095.698 km
LOAD: 265 vol.

  1. Osnabrück Hbf | 100 vol.
  2. Bremen Hbf | 85 vol.
  3. Kiel Hbf | 80 vol.

Tour 5
COST: 1799.609 km
LOAD: 285 vol.

  1. Mannheim Hbf | 55 vol.
  2. Saarbrücken Hbf | 50 vol.
  3. Freiburg Hbf | 90 vol.
  4. Stuttgart Hbf | 90 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: 1395 vol. | Vehicle capacity: 300 vol.
Loads: [45, 0, 80, 85, 0, 40, 90, 65, 0, 100, 85, 40, 40, 35, 50, 0, 80, 55, 80, 100, 85, 50, 100, 90]

ITERATION
Generation: #1
Best cost: 7442.637 | Path: [1, 0, 12, 2, 16, 5, 1, 7, 11, 13, 20, 17, 1, 18, 10, 22, 1, 19, 3, 14, 21, 1, 6, 23, 9, 1]
Best cost: 7325.743 | Path: [1, 3, 19, 17, 14, 1, 11, 7, 13, 20, 0, 1, 18, 10, 22, 1, 12, 2, 16, 5, 21, 1, 9, 6, 23, 1]
Best cost: 7310.785 | Path: [1, 21, 17, 14, 6, 13, 1, 11, 7, 20, 3, 1, 18, 10, 22, 1, 0, 12, 2, 16, 5, 1, 19, 23, 9, 1]
Best cost: 7309.205 | Path: [1, 21, 17, 14, 6, 13, 1, 11, 7, 19, 3, 1, 18, 10, 22, 1, 0, 12, 2, 16, 5, 1, 20, 23, 9, 1]
Best cost: 7214.706 | Path: [1, 20, 3, 19, 1, 7, 11, 13, 6, 14, 1, 18, 10, 22, 1, 0, 12, 2, 16, 5, 1, 17, 21, 23, 9, 1]
Generation: #4
Best cost: 7208.509 | Path: [1, 20, 3, 19, 1, 7, 11, 13, 9, 14, 1, 0, 12, 2, 16, 5, 1, 18, 10, 22, 1, 17, 21, 23, 6, 1]

OPTIMIZING each tour...
Current: [[1, 20, 3, 19, 1], [1, 7, 11, 13, 9, 14, 1], [1, 0, 12, 2, 16, 5, 1], [1, 18, 10, 22, 1], [1, 17, 21, 23, 6, 1]]
[1] Cost: 1215.072 to 1211.245 | Optimized: [1, 19, 3, 20, 1]
[2] Cost: 1719.910 to 1712.783 | Optimized: [1, 9, 14, 13, 11, 7, 1]
[3] Cost: 1372.044 to 1354.834 | Optimized: [1, 16, 5, 2, 12, 0, 1]
[4] Cost: 1101.874 to 1095.698 | Optimized: [1, 22, 10, 18, 1]

ACO RESULTS
[1/270 vol./1211.245 km] Berlin Hbf -> Mainz Hbf -> Frankfurt Hbf -> Würzburg Hbf --> Berlin Hbf
[2/290 vol./1712.783 km] Berlin Hbf -> München Hbf -> Karlsruhe Hbf -> Nürnberg Hbf -> Leipzig Hbf -> Dresden Hbf --> Berlin Hbf
[3/285 vol./1354.834 km] Berlin Hbf -> Köln Hbf -> Aachen Hbf -> Düsseldorf Hbf -> Dortmund Hbf -> Kassel-Wilhelmshöhe --> Berlin Hbf
[4/265 vol./1095.698 km] Berlin Hbf -> Osnabrück Hbf -> Bremen Hbf -> Kiel Hbf --> Berlin Hbf
[5/285 vol./1799.609 km] Berlin Hbf -> Mannheim Hbf -> Saarbrücken Hbf -> Freiburg Hbf -> Stuttgart Hbf --> Berlin Hbf
OPTIMIZATION RESULT: 5 tours | 7174.169 km.