Allow travel time outside of working hours with Resource Scheduling Optimization

By default, the Resource Scheduling Optimization add-in for Dynamics 365 Field Service considers travel time part of a technician's work hours. However, this default setting doesn't match every organization's business needs. For example, a technician's work hours begin at 8 AM. By default, the optimization algorithm schedules the technician to start to travel to the customer's site at 8 AM. Therefore, the technician won't start to work at the site until some time after 8 AM.

Administrators can change the settings of an optimization goal to allow travel time outside of working hours. The system can then schedule a technician to begin their workday a little earlier. In this way, they can start to travel before the beginning of working hours and arrive at the work location when their work hours begin.

Resource utilization might improve if travel time isn't considered part of a technician's work hours.

Edit the constraints of an optimization goal

To remove the default constraint from an optimization goal, follow these steps.

  1. Open the optimization goal for which you want to allow travel time outside of working hours.
  2. Remove the Schedule Within Working Hours constraint.

Screenshot of an optimization goal that has the Schedule Within Working Hours constraint.

Enable a resource for scheduling outside of working hours

To define which resources are considered for travel outside of working hours, follow these steps.

  1. In Resource Scheduling Optimization, go to Scheduling > Resources.
  2. Open a bookable resource.
  3. On the Scheduling tab, for the Schedule Outside Work Hours field, select Allow Travel Before Work Hours, Allow Travel After Work Hours, or both.
  4. For the Travel Limit (in minutes) field, specify how much extra time, in minutes, the Resource Scheduling Optimization algorithm can allocate for travel. The travel limit that you define applies to both travel before working hours and travel after working hours. You can't define a separate travel limit for each option.

Screenshot showing the scheduling rules for a bookable resource.