Announcements
No record found.
Hi,
I am a Project Analyst and the Business I work in is currently implementing D365 Field Service. I was expecting Travel Time Calculations when using RSO:
It does not appear to be the case. We have Short SLA's to meet. Has anyone else had a similar experience with Short SLA's and essentially no real time traffic updates when calculating travel distance. What impact did/does it have on your scheduling?
As I understand it, there may be more beneficial feturers coming down the track and potentially a Real Time API can be used. Discussing that with the Team performing the implementation for us.
Appreciate any assistance or feedback.
Regards
Pete
Hi Pete, thank you so much for your feedback regarding travel time predictions on RSO! We greatly appreciate suggestions to our implementations in order to improve the RSO experience for all our users. To clarify, our current RSO implementation does utilize historical travel data (using Bing Maps as the provider) to predict travel time between bookings. This historical data is includes historic traffic congestion trends (such as peak hour traffic). Does this address your concern regarding Historical Time of Day Travel?
Also, with the above in mind, could I please seek some clarification on your idea? Specifically, what do you refer to as “Real Time” in the implementation, as well as possibly some examples of the scenarios that your proposed solution seeks to address. Thank you!
Sincerely,
Ryan (FS Program Manager)
Hi Ryan,
Thank you for the below.
We have our implementation partner advising that Historical Travel based on time of day (Rush Hour) is not included when predicting the travel time between bookings. Thank you for confirming that it does.
We have short SLA Work Orders. IE – 90minutes to 4 hours. We would have though that “Real Time/Live” Travel updates would be more appropriate than just historical. Similar to what you can see on Map view, but having it auto update the travel time estimate on the booking.
Example. Historical Rush Hour Traffic (8am) advises it takes 40 minutes to travel from “A” to “B”. However there is an unexpected Road closure or Traffic Incident, and the Travel will take 75 minutes. I would suggest having the Travel Time on the Booking Auto Update to 75 minutes would be the right way to go about it. Given the Resource is actually driving they can’t really do the update themselves (if in fact they are aware of what the additional travel time would be). RSO would then run every 15-30 minutes and re arrange future bookings accordingly.
Kind Regards
what waste gates? if they are k03 or k04 you may need a helper spring to smooth things out. adding more preload is going to make your issues works, I fought the issue for a while, I backed the preload off and it got better and now I'll be adding a helper spring to up the cracking pressure without losing travel. alternatively you could get adjustable wastgates.
saveyourpound.uk/.../
Hi Ryan. Wondering if you had reviewed my example below. We are looking to connect to Google maps to get real time traffic updates, however it is going to be costly.
*************
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our community stars!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Daniyal Khaleel 60 Most Valuable Professional
11manish 14 Super User 2026 Season 2
Hamza H 8 Super User 2026 Season 2
