Control Resource Overtime Through a Routing Plan

Overtime is calculated differently by each organization. Therefore, the Oracle Field Service Routing module does not calculate overtime as an absolute dollar value, but instead calculates it as time beyond a resource’s assigned work schedule that might be required to fulfill an activity.

Using the Resource overtime options within the routing plan enables you to determine how activities that might extend past the end of the resource’s shift are handled.

The following figure shows the Resource overtime settings:

Choose from the following options:

• Assign activities even if the assignment causes overtime: This option provides the best chance of getting many activities assigned, though some may extend past the end of a shift.

  For best results, do not use this setting if you have significantly more work than resources can complete in a regular workday. If you run routing, results will include a large amount of overtime. This setting is most useful for certain types of work where you are willing to incur the additional cost, for example VIP work.

• Do not assign overtime activities and leave them in the bucket: This means that any jobs that have service windows and/or predicted durations that could push a resource into overtime are left in the bucket.

• Do not assign activities with more than _____ minutes overtime: This enables you to control the amount of overtime allowed, essentially extending a shift in order to accommodate more work assignments.

• Do not assign activities unlikely to be finished in ____ minutes before end of resource’s day: This also limits the possibility of overtime, but with the consideration of whether a resource needs additional time (return to depot, drive home, etc.) before the end of their shift.

  Note: If you use restrictive overtime settings, fewer good matches might be found and more activities could be left in the bucket to be routed manually.