Reading the Routing Run Summary

The Routing Run Summary shows the list of available resource plans and resource profiles that are active. This Summary section has been updated to display the Priority time left and Priority time spent. This allows Oracle Field Service Professional and Enterprise users to visually see how much of the daily High Priority queued time xxx remains allowing for improved routing plan configurations.

The Routing Run Summary displays the aggregated data of the statuses of the routing plans assigned to the selected bucket. The following statuses are available:

• Scheduled: Indicates routing plans to be run according to the schedule

• Completed: Indicates finished routing plans

• Running: routing plans run currently in progress

  Note: The Rollback option is not available in the Execution Summary block for new activity broadcasting.

Launched column contains information about users who ran the routing plan for Manual and Recurrent plans and special icons for Once a day, Sequential and Immediate plans.

When you select the Immediate routing via Collaboration option, the Report tab in the Automatic Routing window is updated with the following details:

• Destination Resource: Displays the user to which the activity is assigned.

• Average Mileage: Displays the Average Mileage per route for travel-enabled activities (either Average Mileage or Average Kilometer, depending of the units chosen)

• Error/Comments: Displays the Activity Status, namely, error messages or success messages.

When you select another bucket from the resource tree, the Routing Run Summary refreshes to display only those resource profiles and resource plans that are available for the selected resource. The Routing Run Summary shows 0 of 0 for Assigned activities, when activities are reassigned between resources or assigned back to the bucket during re-optimization. Only activities assigned from the bucket to a resource during optimization are added in Assigned activities.

You can now plan your routing runs in such a way that the routing runs at the expected time without waiting for any pending runs.

Daily queue would start at 00:00 UTC (aligns with new API limits for the new SKUs). For the initial release, all routing plans will run at high priority until it exceeds the limit after which all plans will run at low priority until the next day. For routing plans that take less than 1 second to execute, Routing considers 1 second as the runtime precision is 1 second.

The Routing Run Summary section shows the current state of the priority time limits for routing.

In the Routing screen, click Routing Run Summary to display the priority time left for routing and the overall time spent in routing at the bucket (or group of buckets) level.

This image displays the Routing Run Summary.

Priorities for routing include:

• Highest - Contains all routing runs for companies that are not yet exceeded their daily limits.
• Lowest - Contains all routing runs for companies which daily limits is spent.

You can switch to the Lowest priority option in case routing runs have exceeded the daily limit set for high-priority.

Routing limits are as follows:

• Professional:
  • TEST instances:
    • Priority Queueing = 1 hr/day
    • After priority is exceeded everything is low
  • PROD:
    • Priority Queueing = 2 hrs/day
    • After priority is exceeded everything is low
• Enterprise:
• TEST instances:
  • Priority Queueing = 4 hrs/day
  • After priority is exceeded everything is low
• PROD:
  • Priority Queueing = 10 hrs/day (due to SLR if based on routing plan run time)
  • After priority is exceeded everything is low

In the Routing screen, click the Routing Summary tab.

The Routing Run Summary shows the current state of the priority time limits for routing. It displays the high priority time left and the overall high priority time spent in routing across the buckets.