5
Hey everyone,
I’m trying to implement Resource Scheduling Optimization in CRM, and I need to require that Bookings be scheduled with a specific Resource. I’ve tried using the Resource Preferences, but they’re not followed 100% of the time. Does anyone here have any experience with solving for something like this? I’m at a loss, and I haven’t been able to find anything online that solves for it. Thanks!
If you upgrade to the latest version of URS (FS 8.8.3.533) you will find a new resource preference type on the WO/RR called "Must choose from". List your preferred resources and RSO will not assign to anybody else. Make sure to activate the constraint "Meets Resource Preferences". Seems we released this feature just for you! :-)
Watch out for a blog post from the program manager in the coming days.
My suggestion above is still worth a try. Generate a dummy booking, assign it to the preferred resource and lock the booking to the resource. Specify the promised window from 7am to midnight. "Early in the day" is not possible today, high-priority jobs are preferably booked, but not ASAP. This is on the roadmap as a new optimization goal. Only downside - if you don't have enough capacity, the booking will most likely remain at the original time, but at least it does not get removed.
1 - WOs MUST be booked with a specific Resource on a specific Date
2 - WOs can start as early as 7am and as late as midnight (though they rarely do - we're still working to better understand our duration estimates)
3 - We will have priority WOs that need to be addressed early in the day at the expense of drive time if necessary.
4 - We need the Resource's daily route to be optimized for minimal "windshield time."
I would also have proposed lock options (option set on booking). I think if you set it to Resoure, than RSO would optimize the date & time only, but not shift it to another Resource anymore.
The main focus is route optimization. Right now we're in two systems (legacy field service system - old and busted; CRM FS - new hotness), and the legacy system is still handling scheduling, so I've got everything configured so that we can specify the specific date a WO should be executed along with the Resource that should be used to execute the WO. I'm using Characteristics (I have one specific to each Resource) to require that the Resource be used. Its not ideal, but its working.
I don't know your overall scenario, but one workaround could be to create a dummy booking for your RR and the desired resource, then set the lock option to Resource. This way RSO cannot delete the booking nor can it assign it to someone else. After the RSO run, check for bookings that have not been moved and treat them manually.
So for those curious, I think what I'm going to end up doing is creating a Characteristic for each Resource and then adding the Characteristic to the Resource Requirement to force RSO to schedule with the correct Resource.
#1
André Arnaud de Cal...
291,431
Super User 2024 Season 2
#2
Martin Dráb
230,503
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
