Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
This is the 13th blog of this series, before this I have created a blog from module 3 on the topic “Implement the Schedule Assistant” which you can check here: MB2-877 MICROSOFT DYNAMICS 365 FOR FIELD SERVICE MODULE 3 TOPIC – IMPLEMENT THE SCHEDULE ASSISTANT
In this blog we are starting with the topic – Optimize resource scheduling from module 3 “Scheduling and dispatch work orders”:
⦿ Requires a valid production instance of Field Service
⦿ Licensed per resource you want to optimize
I would really suggest you to go through the brief article here : RSO Configuration as I will not be able to perform these steps to show you how its done. It requires a valid field service license. So we will need to just understand the concept!
Maximize total working hours: The version of the engine results (iteration) with the total highest aggregate work time will win this objective.
Minimize total travel time: The version of the engine results (iteration) with the total lowest aggregate travel time will win this objective.
Locked Booking: The engine will try and schedule the iteration/scenario that successfully creates/assigns the most “Locked” schedules to appropriate resources.
High priority Requirement: The fitness function will evaluate this objective, and will give priority to the solutions with the highest score for priority.
Schedule Within Working Hours: Verifies that the task is not scheduled out side of the resource’s working hours.
Meets Required Characteristics: Verifies the resource meets all the required skills needed to complete the work.
Locked to Resource: If marked, Resource Scheduling Optimization will not change any locked resources in the booking requirement.
Scheduling Windows: If marked, Resource Scheduling Optimization will not change any locked scheduling windows in the booking requirement.
Restricted Resources: If marked, Resource Scheduling Optimization will check resource preference to see if it’s “restricted”. If the requirement has a restricted resource in which there is no expiration, or expiration in the past, Resource Scheduling Optimization will not schedule this resource for this booking requirement.
We could not do much handson on this topic due to the limitation of having a paid field service trial but will try/focus on as much as handson on other topics. see you in the next blog!
Business Applications communities