Fabrikam Logistics: Territory Restrictions, Crew Scheduling, and Emergency Priority
Fabrikam Logistics provides on-site maintenance for 80 technicians across six territories. The company uses Dynamics 365 Field Service with the Schedule Board and Resource Scheduling Optimization running nightly. Three crews handle heavy lifts; each crew has a lead and two helpers. The operations manager reports that RSO books technicians outside their assigned territory, travel time is excessive (estimated 30 minutes but actual 45), and crew bookings are often split across multiple work orders. Emergency work orders are not prioritized and sometimes wait 24 hours. The company wants to reduce travel time, keep crews together, and ensure emergency work orders are scheduled within four hours. They also want to use RSO more effectively without increasing the number of technicians.
1. Why is RSO assigning technicians outside their territory, and what would you change in the RSO configuration to enforce territory boundaries?
Read the worked answer
Check three layers. First, confirm each bookable resource has the correct territory populated and that the work order requirement also has a territory. If either side is blank, RSO cannot match them. Second, review the RSO scope and goal. Territory must be a hard resource restriction, not a soft preference, and the goal should include match territory rather than only minimizing travel. Third, check Booking Setup fulfillment preferences and the Schedule Board filters, because a permissive fulfillment setting can let RSO fall back to any resource when no territory match is found. Also verify that organizational units and business units are not unintentionally widening the candidate pool. If RSO still crosses boundaries, inspect the travel time and distance settings because an unrealistically low travel estimate can make a distant technician look cheaper than a nearby one. Fix by setting the resource territory, adding the territory requirement to the work order, configuring the RSO goal with an exact territory match as a constraint, and setting the fulfillment preference to restrict to territory. Then run RSO in simulation mode and review the bookings before enabling it.
2. How would you configure Field Service so that crews are scheduled as a single unit and never split? Explain the booking setup and RSO settings.
Read the worked answer
Model each crew as a crew bookable resource with the lead and helpers as crew members. Do not schedule the individual members as separate resources for crew work. On the requirement, set the resource type to crew and target the specific crew or a pool of crews. In RSO, add a resource restriction that requires a crew and set the match to crew. In Booking Setup, set the fulfillment preference to crew and disallow partial crew bookings. Remove individual crew members from the RSO scope for work that requires a crew so the optimizer cannot satisfy the requirement by booking one person. If a crew can handle multiple work orders in a day, use the crew resource for the whole day and create bookings against the crew rather than the individuals. Review the Schedule Board crew view and test with a heavy-lift work order to confirm the booking creates one crew booking with all members attached. Use booking alerts to catch any booking that assigns an individual member to a crew-only requirement.
3. How would you prioritize emergency work orders in RSO so they are scheduled within four hours, and what fallback would you configure for manual dispatch?
Read the worked answer
Set a priority value on the work order and carry it to the requirement. In RSO, create a goal that treats priority 1 as a hard constraint, applies a four-hour time window, and minimizes travel. Limit the RSO scope for the frequent run to emergency work orders only, and run it every 15 to 30 minutes. Keep the nightly run for routine work. On the Schedule Board, configure auto-fill and sorting so dispatchers see emergency work first. For fallback, use booking alerts and a Power Automate flow that checks for unbooked priority 1 work orders older than one hour and notifies the dispatcher with the work order number, territory, and required characteristics. Give dispatchers a manual scheduling view that shows the four-hour time window and the certification and crew requirements so they can override without breaking constraints. Measure results by tracking the percentage of emergency work orders booked within four hours and the average travel time per booking.