as you may know: we invented a "score" property for a VisitOrder in the xCluster2.planVisits method in version 2.20. Here's just two results that show the impact of the score on a planning.
- Without considering the customers score the total score of the scheduled visits is 550.
- By considering the visits score the planning output increases the score to 627 which is about 15% higher than without the feature!
Attention:
- Of course the score makes sense if WorkloadOptions are applied. Otherwise there's no need to prioritize
- Both WorkloadOptions and OvernightOptions rely on GUROBI!
Bernd
PS:
Both results are based on
- 2 weeks planning cycle
- maximum workload of 40 hours/week, daily workload set to target=8,maximum=10 hours
- overnight options: up to 4 overnights/week
- 300 input visits - (one visit per cycle per location)
-
- The scores I provided range between 8 and 14. Most of the visits have a score of 9.
- planvisits.scores.PNG (5.69 KiB) Viewed 8068 times
