Route Optimization by roundtime, capacities, balance,

API
1

We use RouteXL to optimize our nine daily driver routes for a hot meal delivery service. The drivers are divided into 4 areas:

  • Area 1 has 2 drivers

  • Area 2 has 3 drivers

  • Area 3 has 3 drivers

  • Area 4 has 1 driver

All drivers should ideally be on the road for approximately the same amount of time and/or handle a comparable number of stops.

At the moment, we are getting poor results in Area 2:

  • Route 1 has 18 stops

  • Route 2 has 17 stops

  • Route 3 has 3 stops

These are currently our parameters:
strResponse = RufeRouteXLAn(“locations=” & UrlEncode(strJSON) & _
“&parameters[rounds]=” & intAnzahl & _
“&parameters[balance]=10” & _
“&parameters[roundtime]=” & intRoundtime & _
“&parameters[capacities]=” & intCapacity, _
strURL, strUser, strPassword)
After introducing capacities into our API requests, we initially achieved good results. Since today, however, this no longer seems to work. It appears as if capacities no longer has any effect on the optimization results.

Has anything changed in the API regarding this behavior?

2

The API has not changed in any way that impacts this behaviour. However we’d advise against using a low balance settings if you want equal rounds in time. You may want to try with high balance e.g. 90.

We can check in more detail, but we’d need the exact request you’re sending and the result you receive. If you don’t want to share that here, feel free to use email to info@routexl.com

3

Thank you for your instant reply.You are right. To be honest, I thougt balance=10 is the maximum value for equal tours. Now I know, its up to 100. I tried a value of 80 and everything works like expected.

1 Like