SEQUENCING: planSequence versus planBasicTours
Posted: Mon Jul 17, 2017 2:49 pm
Hi there,
today I discussed the following reoccuring topic with our global consultants:
A customer describes his usecase as a sequencing topic
Under the roof planSequence is using the same component as planBasicTours.
But while you can override the steps via planBasicTours this is not possible with planSequence: the methods used in planSequence are not available through the API.
Check this:
http://xserver.ptvgroup.com/forum/viewt ... uence#p494
Feedback is welcome!
Best regards,
Bernd
today I discussed the following reoccuring topic with our global consultants:
A customer describes his usecase as a sequencing topic
- He wants to optimize a single resource
- He approaches this with planSequence
- He wants to know how to parametrize this scenario
- a customer starts implementation with planSequence
- he complains about poor quality of planing results ("my dispatcher finds a better solution")
- we analyse his scenario
- we find a better solution but with changes in the touropt.ini (using different planning algorithms)
- we tell him to use planBasicTours instead because it is more flexible (I prefer "approaching the methods by API" over "approach methods by TOUROPT.ini") but...
- ...we would limit his license file to xtour.maxVehicleCount=1 and xtour.planBasicToursAllowed=true
- he complains about "I already spent so much time in planSequence"
Under the roof planSequence is using the same component as planBasicTours.
But while you can override the steps via planBasicTours this is not possible with planSequence: the methods used in planSequence are not available through the API.
Check this:
http://xserver.ptvgroup.com/forum/viewt ... uence#p494
Feedback is welcome!
Best regards,
Bernd