View the Routing Report

The routing report analyzes the quality of routes and measures the performance of the routing group over time. The routing report provides route statistics, such as travel time, work time, and number of completed jobs, and is used to measure both productivity and drive time.

To view the Routing report:

1. Select the Navigation button.
2. Select the Routing report from the navigation pane.
3. Review the routing report. It presents a summary of each route, planned or actual, in terms of minutes of travel, work, job fit %, overtime and idle time. It presents the current view at the time it is run as follows:

   • If run before the start of the day, the report represents the planned route

   • If run after the end of the day (or days later), the report represents what actually happened

   • If run mid-day, the report will be part actual and part planned

4. Select a resource bucket or organization in the Resource Tree to run the routing report .

   A single total line is provided for all the resources included in the report. Some buckets contain resources while others govern a hierarchy of buckets or organizations. The report will be broken down either by individual resource or by bucket or organization, depending on the hierarchy.

5. Review the following information in the report:

   • Aggregator—Either a bucket or an organization

   • Mobile Worker– Name of the selected resource

   • Date–The date of Route in day/month/year format

   • Jobs–The number of jobs on route for that day, filtered by status and work type conditions. Status can be any of the following:

     • Pending

     • Started

     • Complete

     • Suspended

     The total number of jobs includes jobs that meet the status and work type conditions above, including jobs that were on the resource’s route within the specified day and jobs with no service window (all day jobs).
   • Travel, minutes–The number of minutes used for travel. If the route has not yet been completed, this will show the estimated travel time.

     Note: Travel time represents total travel time from and to known locations. If an activity (such as lunch) is not a known location, Oracle Field Service will not represent that time in travel time. Similarly, time spent on activities (meetings or lunch) is not represented in the routing report.

   • Work, minutes–The total minutes of work-duration time in a mobile worker's route for a specified day in the defined date range. If the route has not been started or completed yet, this will show the estimated work time.

   • Job Fit % – The average skill level for jobs on a route. This metric is based on the Oracle Field Service work skill %. If a mobile worker does not have a corresponding work skill for an activity (or doesn't have any work skills), then the work skill for the activity is considered to be 0.

   • Overtime, minutes–The number of overtime minutes for the day. Overtime is calculated as [End of the last job performed] - [Schedule shift end time]. If a resource has no overtime, the report will display a "0" value.

     Note: Oracle Field Service considers overtime to be any time outside the resources’s shift for that day. This does not influence the Oracle Field Service overtime calculation. if the mobile worker has a 10 hour day scheduled or has worked 35 hours earlier in the week, Oracle Field Service just looks at time within or outside the shift represented in that day’s working calendar.

   • Idle Time, minutes–The time within a route when a mobile worker is waiting to begin traveling to the customer's location in order not to arrive before the service window starts. In other words, it is the time that is not filled with travel time, work time, or an activity.