What is the meaning of AvoidEarlyRecreations in TourOpt.INI?

This forum deals with any kind of trip optimization whether it is automatic planning or manual dispatching, refering to transport orders or service planning.

What is the meaning of AvoidEarlyRecreations in TourOpt.INI?

Postby Bernd Welter » Tue Nov 21, 2017 12:34 pm

Hi there,

for those who use Driver Settings in the tour optimization the following TourOpt.INI switch could be helpful:
AvoidEarlyRecreations

  • The default value of „AvoidEarlyRecreations” is FALSE.
  • If set to FALSE the algorithms evaluates whether it is helpful to create breaks right at the beginning of tours which could be meaningful to avoid waiting periods right in front of a service at a customer. (bit it doesn’t have to insert them at the beginning, it is just an option)
  • If set to TRUE “breaks, daily rests and weekly rests” will not be inserted at the beginning. So a break is therefore inserted after 4.5 hours and so on.
  • Attention: the name of the parameter shows “AVOID” and not “FORBID”, so an early break could still appear. If a waiting period of 45mins (or more) cannot be avoided the time is used for a break anyway. But a 40min waiting period will not be exceeded to 45min.

Alex wrote:
• Recreations are the general term for breaks, daily rests and weekly rests.
• A recreation is early if it is scheduled before it is due. For instance, a break is early if it is scheduled before 4.5h of driving.
• An early recreation may be beneficial if the driver would have to wait otherwise. For instance, if a waiting time of 35 minutes is inevitable, the driver may take a 45 minute break on arrival at the customer and perform service there 10 minutes after the opening interval has opened.
• It may happen that an early break is scheduled only after a driving period of one hour or less.
• As said, the algorithm does so only if it is beneficial, that is, if it leads to an earlier tour end.
• It is possible to switch this feature off completely by setting AvoidEarlyRecreationsto FALSE.
• Then the algorithm will never consider early recreations.
• You may only encounter an early break if a waiting time of 45 minutes or more is inevitable because this waiting time counts as break.


best regards,
Bernd
Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

https://www.youtube.com/channel/UCgkUli9yGf0gwTDdxbMZ-Kg
User avatar
Bernd Welter
Site Admin
 
Posts: 932
Joined: Mon Apr 14, 2014 10:28 am

Re: What is the meaning of AvoidEarlyRecreations in TourOpt.

Postby Joost » Tue Nov 21, 2017 1:03 pm

Also, since the 1.24.0.3 release this parameter is available in the interface on the planningparams so you do not have to adjust your server side configuration. See also:

https://xserver.ptvgroup.com/fileadmin/ ... ningParams
Joost Claessen
Senior Technical Consultant
PTV Benelux
Joost
 
Posts: 173
Joined: Fri Apr 25, 2014 1:46 pm

Re: What is the meaning of AvoidEarlyRecreations in TourOpt.

Postby Bernd Welter » Tue Nov 21, 2017 1:11 pm

avoidEarlyRecreations.PNG
invented in 1.24.0.3
avoidEarlyRecreations.PNG (10.59 KiB) Viewed 206 times


There you go...
I missed one single sprint ;-) Thanks for the amendment, Joost!

Best regards,
Bernd
Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

https://www.youtube.com/channel/UCgkUli9yGf0gwTDdxbMZ-Kg
User avatar
Bernd Welter
Site Admin
 
Posts: 932
Joined: Mon Apr 14, 2014 10:28 am


Return to PTV xTourServer

cron