Dynamics 365 Resource Scheduling Optimization v3.0 Released
Microsoft has confirmed the release of Resource Scheduling Optimization (RSO) v3.0 for Dynamics 365 for Field Service.
The new capabilities and feature improvements include:
Best Matching Skill Level Resource Objective
Subject to setting an optimisation goal, RSO will assess the proficiency rating of each resource when matching job requirements to resources who possess these characteristics.
This is designed to help schedulers book the best qualified people, subject to other constraints, but reduce the likelihood of highly qualified resources being assigned to lower grade jobs for which they are overqualified.
If resources don't possess the required skills / characteristics for a specific requirement, or they are less proficient in these areas they won't be eligible for the booking.
The highest proficiency score will be awarded to resources who possess the exact skill level, i.e. those who are best matching
Overqualified resources will be eligible but will receive a lower score compared to individuals who precisely match the required competency.
Microsoft's launch post references a scenario whereby competency is ranked 1-10 with 10 being most skilled. In this scenario, if a job requires a rating of 4 for a specific competency, a resource who is rated 10 will be scored lower by RSO. Instead, this will prioritise better matching resources with those rated at 4 scoring highest and others rated between 9 and 5 being scored on an ascending scale, albeit less than the best matching resource who rank 4.
If the overall RSO goal is not configured for 'best matching skill level', less qualified resources could be booked as well as those overqualified. One aspect that doesn't change in this scenario is that more overqualified a resource is, the lower score the score they will get.
Maximise Preferred Resource
RSO will take into account any preferred resources that are listed on a resource requirement.
As such, the Optimiser will prioritise booking for preferred resources, subject to availability and other constraints.
This capability is also driven by an RSO goal with a supporting setting for 'Maximise Preferred Resources'.
On each resource requirement record, one or more preferred resources can then be added.
RSO will consider the list of preferred resources noted on related requirements. The optimizer will try to assign bookings to preferred resources first while meeting other constraints and objectives. This is achieved by adding the 'Maximize Preferred Resources' objective in your RSO goal and adding preferred resources on the requirement that will be optimized.
Change Objective Order in Optimisation Goals
As the above examples demonstrate, configuring RSO Optimisation Goals is crucial to helping schedulers book the best available resource.
In RSO v3, users can easily adjust order of existing objectives by moving the priority of individual items up or down.
In addition to including 'Maximise Preferred Resource' and 'Best Matching Skill Level', other factors can include 'Minimise Travel Time' and 'Maximise Total Working Hours'.
Other RSO Improvements:
- Allow empty time values on requirements - this enables scenarios where only a start or finish time is selected.
- Improved logic to resolve booking conflicts
Read the Microsoft post to find out more about what's new in RSO v3.