You’re offline. This is a read only version of the page.
Announcements
Hi,
I am setting up my field service works orders etc. When scheduling resources to a work order, the "estimated travel time" seems to only account for travel from the resource origin (resource address) to the field service location. It does not calculate or display the travel time for the resource to return to their origin once the job is done. This seems crazy to me, am I missing something? My expectation would be for the actual work booking to have travel time at either end. Further, if there are multiple locations in a day, how is travel time determined between job locations?
Thanks
Al Iggs : Hello Alexander and Emmanuel,
We are struggling with the same issue regarding calculating travel time for FSE to go back to start location (Home) and add this to the last booking of the day. Can you please advise on the solution that you have put in place or can be used finally? We are not using RSO for information. Many thanks for you help.
Best regards.
I would create a 1-minute booking (not necessarily a WO) at the end of the working hours (must be within the hours) with the home location of the resource. If you then create a new WO booking during the day, the system will calculate travel to the WO job plus travel from the WO job to the home location. If you utilize RSO, don't forget to lock the dummy booking to time and resource.
Hello Alexander,
what would you suggest if the return time needs to be present on the schedule board?
We thought on the solution of creating a wo with the address of the ressource that as bookings created automatically everytime the ressource has missions, and create bookings accordingly. But i don't find this solution very sexy.
Thanks for your answer.
Ok, Thank You!
It depends on how you schedule. Using drag&drop no travel is calculated, but that's on the roadmap and will improve soon. If you run Schedule Assistant, it will take travel into consideration. When it's the first job of the day, it will calculate travel from resource start location (home/office), otherwise it will use the location from the previous job. Schedule Assistant will also leave time for returning to the resource's end location, but the ultimate decision about the booking remains with the dispatcher.
When using RSO, traveling from start/previous job and returning after work is calculated automatically. The travel time from the last job to the end location is currently not shown on the Gantt chart, there is already an idea filed on the ideas portal (experience.dynamics.com/ideas ), if you want to give a thumbs up. There are also suggested ideas for scenarios in which you do NOT want to consider travel time for the first or after the last job, which is often required in urban scenarios where resources are responsible for their travel.
#1
André Arnaud de Cal...
291,359
Super User 2024 Season 2
#2
Martin Dráb
230,370
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
