6Routing Visualization

Introduction to Routing Visualization

The Routing screen gives a graphic, visual, and transparent display of what is actually happening in the Routing module.

Looking at the Routing screen, you can see the summary of the Routing Plans assigned to the selected bucket, the autorouting efficiency ratio, the resource utilization ratio and the actual savings achieved as the result of Routing.

To open the Routing screen, click the Navigation button and click Routing.

The Routing screen consists of the resource tree and the Summary Bar. The resource tree in the left part of the screen allows selecting buckets for which data is to be displayed. The resource tree has a hierarchical structure, that is, when a parent bucket is selected, the screen shows aggregated data of its child buckets.

The resource tree on the Routing screen now contains only those resources that are of resource type Bucket with the Routing can assign activities check boxes enabled. For each resource that you select in the resource tree, the Routing screen displays the number of activities for that resource. The calendar widget in the top part of the screen is used to select the date for which Routing data is to be displayed.

    Reading the Summary Bar

    The summary bar shows the Routing results for the selected bucket. In each case, the data shown in the summary bar is the aggregated data of all individual resources' routes created as the result of routing runs.

      Reading the Routing Plans Block

      The Routing Plans block shows the number of scheduled routing plans.

      The number next to the puzzle icon is the number of routing plans assigned to the selected bucket or its child buckets, if any.

      You can click the Routing Plans block to open the list of profiles assigned to a current bucket and its child buckets (if any).
      • If there are no child buckets, only the profile of the current bucket with the list plans will be displayed.

      • If no routing profile is assigned to the bucket, it is possible assign routing plans using the Assign link.

        Reading the Execution Summary Block

        The Execution Summary block shows the list of available resource plans and resource profiles that are active.

        The Execution Summary block 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.
        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 Execution Summary block refreshes to display only those resource profiles and resource plans that are available for the selected resource. The Execution Summary View 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.

          Reading the Autorouting Block

          The Autorouting block shows the efficiency of automatic Routing in percent. The Autorouting block includes both scheduled activities for the date selected and non-scheduled activities that were routed but not necessarily by the date selected.

          The Autorouting efficiency is calculated as the ratio of the number of autorouted activities to the total number of routed activities (both automatically and manually). This statistics takes into account the number of operations resulting in 'meaningful' changes to the activity routing, that is, changes to the date of the route or the resource to whose route the activity has been assigned. Operations bringing no changes to the activity date or resource to which the activity is assigned, are ignored. Similarly, reverse operations resulting in no change to the initial activity assignment are ignored, as well.

          The figures shown in the Autorouting block are aggregated results of all resources in the selected bucket and its child buckets, if any. If no activities were routed manually, the Autorouting efficiency is 100%. The Autorouting drop-down menu contains the following data:

          • Manually processed: Displays the number of manually routed activities

          • By Dispatcher / By Resource: Allows viewing the number of manual operations performed by the dispatcher or by the resource. This section contains the breakdown of manual operations in the following types:

            • Assigned: Activities moved from the bucket to resources' routes

            • Reassigned: Activities moved between resources

            • Unassigned: Activities moved from resources' routes to the bucket

            • Reordered: Activities moved to a different position in the route. The Reordered category is not available in manually processed By Resource column

          • Total amount of manually processed activities {number} (of {number})

            Reading the Resource Utilization Block

            The Resource Utilization block shows the efficiency of resources working time use in percent.

            The resource utilization ratio is calculated as the ratio of the actual resource useful time to the useful time defined by the baseline settings. The resource utilization block displays the aggregated result of all routes created as the result of Routing in the selected bucket.

            The Useful Time section consists of Working Time (the time spent by the resources for actual activities performance), Overtime and Travel Time. The window also includes the Idle Time section, which is the waiting time between activities.

              Reading the Savings Block

              The Savings block shows the value of savings achieved by the Routing runs in the selected bucket. It is possible to view the cost savings, that is, the money which the company can save by applying the Routing results, or the time savings, that is, the working time which can be gained or travel time and overtime which can be reduced by applying the Routing results. The savings amount is calculated on the basis of the Baseline Settings defined in the same window.

              Both the Cost savings and the Time savings options show the total savings and their breakdown as follows:

              Image shows Savings block screen with Cost savings and Time savings options

              • Work time increase: Increase of the time spent on actual activities performance which can be represented as actual time in hours and minutes (Time savings) or converted to money according to the Baseline Settings (Cost savings)

              • Travel time reduction: Reduction of the time spent on travel between activities which can be represented as actual time in hours and minutes (Time savings) or converted to money according to the Baseline Settings (Cost savings)

              • Overtime reduction: Reduction of the overtime created for the resources as the result of Routing run which can be represented as actual time in hours and minutes (Time savings) or converted to money according to the Baseline Settings (Cost savings)

                The value in the Savings block is the sum of the three values mentioned earlier.

                In some cases savings values may be negative when some technicians in the bucket were not assigned enough activities to earn their daily salary. However, such negative result may be compensated by other optimizations and the overall routing result may be positive.

                Configure Routing

                The Routing functionality shows the savings achieved for the selected bucket as the result of Routing runs. This requires setting the average company parameters based on the existing statistics of the company business. In Oracle Field Service Cloud these parameters are called Baseline Settings.

                To configure routing parameters:

                1. Click Baseline Settings to open the list of parameters that need to be configured.

                2. Set the following parameters:

                  • Fully-loaded resource hourly cost: Cost of 1 hour of the resource’s work based on the resource's salary, benefits, training, overhead costs, equipment costs or depreciation in US dollars. When the Time savings view is selected, this setting is disabled as it has no influence on time savings

                  • Cost per mile: Cost of one mile of the resource's travel in US dollars (or cost of one kilometer of the resource’s travel in your local currency). When the Time savings view is selected, this setting is disabled as it has no influence on time savings

                  • Overtime increase: Resource's hourly cost increase in case of overtime in per cent

                  • Average resource daily work time: Average time the resource spends on activities performance in a day in hours

                  • Average resource daily travel time: Average time the resource spends on travel between activities in a day in hours

                  • Average resource overtime: Average acceptable overtime per resource in hours

                  • Travel speed: Average speed with which resources travel in miles per hour

                Routing Tabs Displayed on Mobile Devices

                Routing screen tabs have been improved to allow smooth functionality on all the devices such as mobile phones and all screen sizes.

                You can create, modify and start routing plans, set baselines, and review the routing results from any device supported by Oracle Field Service Cloud. The Routing screens are now easy to use on all the devices supported by Oracle Field Service Cloud, compatible with different screen sizes including mobile phones.

                The following figure shows how the tabs align vertically when the Routing screen is accessed from a mobile device:


                Image shows Routing screen in a mobile device.

                The following sections discuss how Routing screen tabs appear on devices with different display sizes.

                Routing Tabs Displayed in Web Browsers:

                The following figure shows the Routing Plans Tab of the Routing screen:


                Image shows Routing Plans Tab in a web browser.

                The following figure shows the Routing Execution Tab of the Routing screen:


                Image shows Routing Execution Tab in a web browser.

                The following figure shows the Results Tab of the Routing screen:


                Image shows Results Tab in a web browser.

                The following figure shows the Savings Tab of the Routing screen:


                Image shows Savings Tab in a web browser.

                Routing Tabs Displayed in Devices with Smaller Display Size:

                The following figure shows the Routing Plans Tab of the Routing screen:


                Image shows Routing Plans Tab in a device with medium display size.

                The following figure shows the Routing Execution Tab of the Routing screen:


                Image shows Routing Execution Tab in a device with medium display size.

                The following figure shows the Results Tab of the Routing screen:


                Image shows Results Tab in a device with medium display size.

                The following figure shows the Savings Tab of the Routing screen:


                Image shows Savings Tab in a device with medium display size

                Routing Tabs Displayed in Mobile Devices:

                The following figure shows the Routing Plans Tab of the Routing screen:


                Image shows Routing Plans Tab in a mobile device.

                The following figure shows the Routing Execution Tab of the Routing screen:


                Image shows Routing Execution Tab in a mobile device.

                The following figure shows the Results Tab of the Routing screen:


                Image shows Results Tab in a mobile device.

                The following figure shows the Savings Tab of the Routing screen:


                Image shows Savings Tab in a mobile device.

                Manual and Automatic Routing Run

                Routing Plans scheduled to run according to the Run schedule settings are run automatically at the scheduled time. However, each Routing Plan assigned to the selected bucket can be started manually when necessary.

                  Run a Routing Plan Manually

                  You can run a routing plan that is assigned to a bucket either manually or automatically. This procedure describes how to run a routing plan manually.

                  The puzzle icon that is used to run a routing plan manually is controlled by the Routing visibility. When the visibility is disabled for a user, the puzzle icon is hidden and the user cannot start routing plans manually.

                  To run a routing plan manually:

                  1. Navigate to the Activities screen (Time View, List View and Map View).

                  2. Select a bucket in the resource tree and click the puzzle icon.

                    The list of all routing plans assigned to the bucket is displayed. The list also shows the number of non-assigned activities in the bucket and the number of available resources, as shown in the following figure:
                    This figure shows drop-down menu with the list of routing plans.
                    Note: When a resource other than bucket is selected, the puzzle icon is hidden.
                  3. Click Run.

                    A confirmation dialog appears prompting you to confirm that you want to manually start the selected plan.
                  4. Click OK.

                    The Manual routing window with processing icon is displayed. The title of the window displays the Routing Plan name and the ID. When the routing plan is running, the window shows a shuffling puzzle representing the progress of the routing run. The right pane shows the Routing run statistics.

                    This image displays the Summary tab in the routing results window:


                    This figure shows the Summary tab on the routing results window.
                  5. Review the following fields on the Results window

                    Field Description
                    Resources used Indicates the total number of resources to which activities have been assigned.
                    Routed activities Indicates total number of activities assigned by Routing. This section also includes the percentage of the assigned activities in the total number of activities in the bucket and the percentage of activities assigned with SLA overdue.
                    Non-Routed activities Indicates the total number of activities not assigned by Routing in the current run with their breakdown by non-routing reasons.
                    Rejected activities Specifies the number of activities which could never be assigned in the current conditions and the reasons for their non-assignment. For example, if some activities cannot be assigned as no resource in the selected bucket meets all their requirements, such activities will be rejected. The number of rejected activities is included in the total number of non-routed activities.
                    Average working time Indicates the average time resources spend on performing activities in a working day and its ratio against the baseline figure.
                    Average overtime Indicates the average overtime created as the result of the Routing run and its ratio against the baseline figure.
                    Average travel time Specifies the average travel to be performed by resources as the result of the Routing run and its ratio against the baseline figure.
                    Average down time Indicates the average idle time created as the result of the Routing run and its ratio against the baseline figure.
                    Average Mileage Specifies the average mileage per route for travel-enabled activities (in Average Mileage or Average Kilometer based on the units chosen).
                    Resource utilization Specifies the efficiency of resources working time use in per cent.
                    Routing run time Indicates the time in which the Routing run was completed.
                    Days Indicates the total number of days in the period for which segmentable activities routing run is planned for.
                    Resources Indicates the total number of resources in the bucket.
                    Activities Indicates the total number of activities in the bucket
                    Savings Specifies the financial savings achieved by the Routing run broken down into:
                    • Working time optimization savings: Savings achieved as the result of resources' working time increase

                    • Overtime optimization savings: Savings achieved as the result of overtime reduction

                    • Travel time optimization savings: Savings achieved as the result of travel time reduction

                    Total savings Indicates the sum of Working time optimization savings, Overtime optimization savings, and Travel time optimization savings.

                    When the routing run completes, its results are immediately applied, that is, the activities are placed in the resources' routes. To reject the routing run results, you can click Rollback (the activities will be returned to the bucket).

                    Automatic Routing Run

                    Automatic Routing runs require no user actions to start. When a Routing Plan is run automatically, no pop-up windows appear. The Routing plans that are currently running are shown in the Running status under the Execution Summary block. Click the line of a running Routing Plan to open the Automatic Routing window that has the behavior and functionality similar to that of the Manual Routing window described previously.

                      Unlimited Queued Routing

                      Oracle Field Service Professional and Enterprise Cloud subscribers will have access to unlimited queued routing. Routing runs will be prioritized into High Priority and Standard Priority runs with High Priority runs being processed prior to Standard Priority routing runs. Each subscription and Instance type will have a number of high priority hours allocated per day where the hours will reset daily at 00:00UTC.

                      Subscription Type Oracle Field Service Professional Oracle Field Service Professional Oracle Field Service Enterprise Oracle Field Service Enterprise
                      Instance Type TEST PROD TEST PROD
                      High Priority (hours/day) 1 2 4 10
                      Standard Priority (hours/day) Unlimited Unlimited Unlimited Unlimited

                      Users can manage the routing run time using the Time Limit parameter in the Run Schedule section of the Routing Plan. The actual run time used is displayed on the Execution Summary page for each individual routing plan that has been executed. Any routing plan that take less then 1 second to execute with consume 1 second in the calculation.

                      Beginning daily at 00:00 UTC, any configured and executed ‘manually’, ‘once a day’, ‘recurrently’ and ‘sequentially’ routing run will be automatically assigned a High Priority status. Each executed routing run will reduce the number of High Priority hours available that day. After the allotted number of High Priority hours is consumed for an instance, all subsequent routing runs will default to the Standard Priority where they will be processed based on their priority.

                      Example Scenario

                      Following is an example scenario:
                      • Subscription Type = Oracle Field Service Professional
                      • Instance Type = TEST
                        • High Priority (hours/day) = 1 hour
                        • Standard Priority (hours/day) = Unlimited
                      • Routing setup:
                        • Routing Plan = Bulk
                          • Routing Run = Once a Day
                          • Run Time = 07:00
                          • Time Limit = 15 minutes
                        • Routing Plan = Daily
                          • Routing Run = Recurrently
                          • Run Time = 08:30-18:30
                          • Interval = 60 minutes
                          • Time Limit = 10 minutes
                      • Outcome:
                        • Bulk routing runs in 5 buckets with each bucket’s routing run takes 4 minutes to execute.
                        • Daily routing runs in 5 buckets with each bucket’s daily run takes 1 minute to execute.

                        Type Time Total Minutes Used Priority Notes
                        Bulk 07:00 20 High
                        • 5 Buckets * 4 minutes = 20 minutes
                        • High Priority since this is the first run after 00:00 UTC
                        Daily 08:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 25 minutes
                        Daily 09:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 30 minutes
                        Daily 10:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 35 minutes
                        Daily 11:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 40 minutes
                        Daily 12:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 45 minutes
                        Daily 13:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 50 minutes
                        Daily 14:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 55 minutes
                        Daily 15:30 5 High
                        • 5 Buckets * 1 minute = 5 minutes
                        • High Priority since total time used is 60 minutes
                        Daily 16:30 5 Standard
                        • 5 Buckets * 1 minute = 5 minutes
                        • Standard Priority since Priority Time is used
                        Daily 17:30 5 Standard
                        • 5 Buckets * 1 minute = 5 minutes
                        • Standard Priority since High Priority Time was consumed
                        Daily 18:30 5 Standard
                        • 5 Buckets * 1 minute = 5 minutes
                        • Standard Priority since High Priority Time was consumed

                      Receive Routing Advice from Oracle

                      Oracle provides services to assist you in assessing your routing needs, developing a routing strategy, and implementing that strategy in Oracle Field Service Cloud. Oracle representatives can also assess your current routing strategy and assist you in improving the results. For details about these services, contact Oracle support.