SEQUENCING: planSequence versus planBasicTours

This forum deals with any kind of trip optimization whether it is automatic planning or manual dispatching, refering to transport orders or service planning.
Post Reply
User avatar
Bernd Welter
Site Admin
Posts: 2564
Joined: Mon Apr 14, 2014 10:28 am
Contact:

SEQUENCING: planSequence versus planBasicTours

Post by Bernd Welter »

Hi there,

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
So what I experienced several times in the past is
  • 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"
I helped many players with this approach and therefore I'd like to recommend this on a generic base.
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
Bernd Welter
Technical Partner Manager Developer Components
PTV Logistics - Germany

Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning... :twisted:
Post Reply