Hi @Steve Hupp /All -

We have use case where 

1.Technicians are travelling by air within USA and working on appointments in other corner from his/her home location(assuming they are secondary resources on multiple territories) and 

2.Additionally - these same technicians can work on local appointments(in Primary territories and can travel by Car) whenever it's needed.

3.Point to mention is - Mostly Appointments are multi-day.

Now -

1. Whenever they are travelling locally - gantt is showing Travel time correctly (Start and End ) - Working as designed.

2.In case Air travel we don't want gantt to show and Scheduler Engine to block resource time - As we know - for air time we cant predict travel details and its not even supported in Product.

e.g. here by using resource address and Appointment address, resource are getting blocked for entire week using default travel calculation and dispatcher /optimization will not able to use that travel time period to book other appointment(except if we forcibly book using drag-drop with rule violation).

3.In reality resources are travelling by air and we are planning to show resources air travel(to and from air travel dates-entire day and  these dates are with SA start and End date- we can easily figure out total duration and travel duration - this is also working good with some customization) on gantt by using Resource Absence with new value in Picklist type - Travel/xyz.

3.In order to Prevent automatic travel calculation - I am thinking to remove address from SA if resource is planning to travel by air.- In this case Scheduling will not calculate to and fro travel time and resource will be available for other Appointments during that period.

Could you please suggest if you any better/alternate solution for this work in order to ignore travel time calculation for long distance/air travel appointments.

CC: @Leigh-Anne Nugent

#SFS #FSLOfficeHours #FSL #Multi-day #AirTravelling #Fsl Scheduling #TravelTime