Based on the Field Service Guide, our understanding is that if a Resource Absence is created without an address, it will calculate drive time for surrounding Service Appointments using the address on the Service Territory Member for the Service Resource.
"If an absence doesn’t have an address, optimization uses the resource’s home base to calculate travel time to the next service appointment. For a more precise travel estimate, add an address to the absence, such as the location of the previous appointment or an address for the break."
We have been seeing examples where this is not the case. Below are screenshots showing the drive time for an Absence without an address versus the drive time when it's been updated with the Service Resource's home base.
Absence without an address:
Absence with the Service Resource's home address:
Updating the Absence with the address of the previous Service Appointment does not change drive time. Confirming that, without an address, the drive time for the Service Appointment following the Absence is being calculated using the address of the Service Appointment before the Absence.
Curious if there is something we are missing or if our understanding is incorrect.
Thanks!
@Steve Hupp The SA was originally added with optimization but my testing was on platform by dragging and dropping.
I see that mention of optimization now. So it sounds like it could be that when optimizing it considers the drive time from the home base but for on platform scheduling and displaying drive times in the Gantt it will calculate from the previous SA. I will set up some tests to confirm that theory.
Thanks for the help, Steve.
