4Configure a Routing Plan

Overview of Routing Plan Configuration

Routing plans provide the rules to use when deciding how to route activities to resources. After you add or clone a routing plan, you must configure it. This includes defining the run schedule and creating filters that prioritize activities based on a variety of conditions and situational factors. When you configure a routing plan, your choices can have a significant influence on the routing process.

Note: It is not recommended to have more than 100 routing plans or buckets running routing plans simultaneously, for example: 1 routing plan for 100 buckets and 10 routing plans for 10 buckets. If the number of routing plans or buckets exceed this limit, it causes routing executions to be queued for processing. If your current configuration exceeds this value, you must review and adjust your routing configurations to get an efficient routing execution.

Configure the Routing Plan Section of a Routing Plan

You must provide general details about the routing plan including the profile on which it is based, the routing method and the number of minutes and seconds it will run.

To configure the routing plan section:

  1. Click Routing to open the Routing screen.

  2. Select Routing Plans to display the routing plans and routing profiles available for the selected bucket or resource.

  3. Click the Modify link to open the Edit routing plan screen.

  4. Click Routing Plan to expand that section.


    Image shows the Routing plan name, routing profile assigned to it and status whether it is active
  5. Identify the routing name and profile and provide other basic details.

    • Routing plan name: Enter a name that makes this plan easy to identify.

    • Routing profile: Identify the profile to which this routing plan belongs.

    • Active: Select the check box to make this plan available for routing. You can deactivate a routing plan to avoid running it accidentally. For example, if you have routing plans that you run during certain seasons or other busy times of the year, you can make them inactive until you are ready to use them.

    • Description: Enter a description for the routing plan. This is an optional field.

  6. Click Add.

    Tip: If you find that routing is regularly running until the time limit, consider increasing the time limit and monitor the results to see if they are more efficient.
    If the Time Limit shows any value between 5 seconds and 20 minutes, the routing plan runs over and over again until it either finds the best match or the time limit expires, whichever comes first.

Configure the Run Schedule for the Routing Plan

The run schedule identifies when you want the plan to run, how often you want to run it, and whether you want to run it over multiple days. You can also specify the day’s activities to run the plan against. The run schedule that you choose has an effect on the information you can share with your customers through notifications. For example, if you want to launch a notification the afternoon before an activity, but you don’t run routing until the evening, your notification will not include the time slot.

To configure the run schedule for the Routing Plan:

  1. Navigate to the Routing Profiles screen and locate the routing plan that you want to configure.

  2. In the Actions column, click Modify.

    The Edit Routing Plan screen appears.
  3. Expand Run Schedule.

  4. Configure one of the following routing plans:

    1. Create a plan to start routing manually:

      1. Select Manually from the Run routing drop-down list.

      2. Enter a number in the Apply to activities within day interval field. The activities selected for this routing plan are executed within the number of days selected in this field, starting the selected day.

      3. Select the duration for which the plan must run in the Time limit field.

      This figure shows an example of a manual routing plan:

      Image shows a manual routing plan.

    2. Create a recurring routing plan:

      1. Select Recurrent from the Run routing drop-down list.

      2. Enter a number in the Apply to activities within day interval field. The activities selected for this routing plan are executed within the number of days selected in this field, starting the selected day.

      3. Select the start and end time at which the routing plan must run, in the Start time and End time fields.

      4. Enter the interval between each run in the Interval between runs in minutes field.

      5. Check the boxes corresponding to the days on which the routing plan must run recurrently, in the Activity days field.

      6. Select the duration for which the plan must run in the Time limit field. This time denotes the maximum number of minutes and seconds that the routing plan will run before producing a result. When the application launches a routing plan, it runs the plan over and over again until it either finds the best match or the time limit expires, whichever comes first. Three minutes is usually sufficient. The maximum time limit possible is 20 minutes.

    3. Create a plan that runs once a day:

      1. Select once a day from the Run routing drop-down list.

      2. The activities selected for this routing plan are executed within the number of days selected in the Apply to activities within day interval field, starting the selected day. The default value is 1.

      3. The Start day for activity processing field is used in the Once a Day and Recurrently plans. New values for Start day for activity processing allow to run routing starting at 2, 3 or 4 weeks in future.

        Select one of these values from the drop-down list:

        • yesterday

        • today

        • tomorrow

        • +2 days

        • +3 days

        • +4 days

        • +5 days

        • +6 days

        • +7 days

        • +8 days

        • +2 weeks

        • +3 weeks

        • +4 weeks

      4. Enter the time at which the routing plan must run, in the Time of run field.

      5. The Activity days field specifies the days on which activities are scheduled.

      6. Select the duration for which the plan must run in the Time limit field. This time denotes the maximum number of minutes and seconds that the routing plan will run before producing a result. When the application launches a routing plan, it runs the plan over and over again until it either finds the best match or the time limit expires, whichever comes first. Three minutes is usually sufficient. The maximum time limit possible is 20 minutes.

      This figure shows an example of a plan that runs once a day:

      Image shows a routing plan that runs once a day

    4. Create a plan that runs immediately:

      1. Select Immediately from the Run routing drop-down list.

      2. Select one of the following options:

        • for Urgent Activities: Activities are assigned and scheduled the same day, regardless of whether this assignment disrupts other scheduled activities. In this case, the SLA is not honored for the activity.

        • activities that correspond with filter: Only those activities that correspond to the selected filter are assigned immediately. Such activities can also be bundled with other activities that are scheduled for the same location and bucket in the near future.

          The figure shows the Run routing field in the Add Routing Plan screen:


          Image shows the Run routing field with immediately option selected.
      3. Use the Assignment and Bundling within __ day interval starting fields to configure bundling activities.

    5. Create a plan that runs sequentially after another plan:

      1. Select Sequentially from the Run routing drop-down list.

      2. Select the plan that must run before the current plan, from the after the completion of drop-down list.

      3. Select the duration for which the plan must run in the Time limit field. This time denotes the maximum number of minutes and seconds that the routing plan will run before producing a result. When the application launches a routing plan, it runs the plan over and over again until it either finds the best match or the time limit expires, whichever comes first. Three minutes is usually sufficient. The maximum time limit possible is 20 minutes.

  5. Use Street Level Routing (SLR) to obtain travel data in your routing plan:

    This feature can be used with routing runs that run Manually, Once a Day, Recurrently and Sequentially; it is not available for Immediate routing runs. To improve the quality of the routing run with SLR, configure the plan with adequate time to gather enough SLR data. We recommend that you allocate a minimum of five (5) minutes for Once a day and Manual routing plans. This time will vary based on your business and the amount of activities to be optimized. You may increase the time if needed.

    The Run schedule section shows the Use SLR to obtain travel data check box. This indicates that the time limit includes extra time for SLR data.

    1. Select the Use SLR to obtain travel data check box.

    2. Select the duration in the Time limit field to adjust the time limit accordingly.

      The routing run time includes both gathering SLR data and using that data to run Routing.

      In some situations when there are a large number of pending activities, every point to point travel combination cannot be obtained in the allotted time period. When this occurs, routing will use SLR data and learning travel data to optimize the routes. This ensures routes are optimized quickly with the optimal combination of travel data.

      The figure shows the Run schedule section in the Add Routing Plan screen:


      Image shows the Run schedule section in the Add Routing Plan screen.
      Note: SLR in Routing requires a subscription to Oracle Field Service Enterprise and Oracle Field Service Standard Map Service with Google Maps or Oracle Field Service Standard Map Service with Baidu Maps.
  6. Click Add to save your changes.

    Note: In some cases, when routing's evaluation has to terminate due to time limit, it consumes slightly more time than configured. This is because termination cannot occur at the arbitrary point; it occurs only after the completion of the current block of computations.

Restriction of Activities Routed Through Immediate Routing Plan

You can now restrict activities routed through a particular Immediate Routing plan. This is useful to avoid any confusion in technicians’ routes or in case if the you want to bulk route all the activities created in late hours through a nightly routing plan.

To restrict activities routing through a particular Immediate routing plan, enter values in the Start time and End time fields as needed and save the Immediate routing plan.

After Start time and/or End time fields are filled, no activities will be routed before Start time and after End time.

  • If both Start time and End time fields do not show any values in the Immediate routing plan by default, there are no restrictions; activities are routed through Immediate routing plan 24 x 7.

  • If onlyStart time field is populated, End time is considered to be equal to midnight (or time set by Overnight settings section in the Business rules screen).

  • If only End time field is populated, Start time is considered to be equal to midnight (or time set by Overnight settings section in the Business rules screen).

    Note: Scheduled Immediate routing plan routes those activities that were created after End time and before Start time and not routed during this period by another routing plan, after the Start time.

Segmentable Activities Assignment Using Bulk Routing

You can now route segmentable activities using Bulk Routing. Whether you route the segmentable activity from the bucket using Immediate Routing or Bulk Routing, the assignment rules are the same; the routing plan (Immediate or Bulk Routing) either assigns the whole activity to a single resource or leaves it in the bucket.

Note: Earlier, you could assign segmentable activities to a resource either using manual move or through Immediate Routing.

Both Immediate and Bulk Routing observe these rules for segmentable activities:

  • Work zones—the resource's work zone must match the work zone of the activity

  • Work skills—the resource's work skills must match the work skills required by the activity

  • Resource preference—routing should assign the activity to preferred resources or only to required resources, if specified

  • Service window—routing should observe the activity service window for all the segments

  • Access hours – routing should observe the activity access hours for all the segments

  • SLA start—the SLA start of the activity observed for the first segment

  • SLA end—the SLA end of the activity observed for the last segment

  • Minimum segment duration for a single day <> minutes – indicates that those segments having lesser than minimal duration are not created

  • Maximum segment duration for a single day <> minutes – indicates that the total daily amount of segments cannot exceed the configured value. (with the exception for the days containing the last segment of activity, which can exceed the configured amount but the remainder cannot be more than the minimum segment duration)

However, during the initial activity assignment, Immediate Routing optimizes only start/finish time of the segmentable activity. Bulk routing also tries to optimize travel time to and from each activity segment and overtime, overdue and other parameters of the segment the same way as they are optimized for single-day activities.

Link a Segmentable Activity With Another Segmentable Activity

You can link a segmentable activity with another segmentable activity using the same link types that you use to link a regular activity with a segmentable activity.

Follow these steps to route a linked segmentable activity.

  1. Run the multiday routing plan where the segmentable activities fit to the filters.

  2. Set a Bulk routing plan running for a scheduled time to cover all the linked segmentable activities that you want to route.

    Note: Only Bulk routing supports routing linked segmentable activities. Immediate routing ignores all segmentable activities that have links.

Supported Link Types and Constraints

Here are the link types and constraints supported for links between segmentable activities:

  • Simultaneous (Segmentable and Segmentable activities): no constraints available
  • Segmentable activity Finish to Segmentable activity Start:
    • Same Day: earliest (as of calendar means) segment of a latter activity should start the same day as the latest (as of calendar means) segment of former activity finishes
    • Same Provider: all segments of latter activity should be done by the same resource(s) participated in doing of any segment of former one
    • Different Providers: all segments of latter activity should be done by the different resource(s) then participated in doing of any segment of former one
  • Segmentable activity Start to Segmentable activity Start:
    • Different Providers: all segments of latter activity should be done by the different resource(s) then participated in doing of any segment of former one
    • If you try to add unsupported activity link type and/or constraint, a warning is displayed and no link is added.
  • For Segmentable Activity Finish linked to Segmentable Activity Start:
    • Same Day: earliest (as of calendar means) segment of a latter activity should start the same day as the latest (as of calendar means) segment of former activity finishes
    • Same Provider: all segments of latter activity should be done by the same resource(s) participated in doing of any segment of former one
    • Different Day: An activity that needs technical break between - first segment of a latter activity should start at least a day after the last segment of the former activity finishes
    • Different Providers: all segments of latter activity should be done by the different resource(s) then participated in doing of any segment of former one
  • For Segmentable Activity Start linked to Regular Activity Start (or vice versa):
    • Different Providers: all segments of latter activity should be done by the different resource(s) then participated in doing of any segment of former one

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:


Image shows Resource overtime actions available for a routing engine

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.

Control Travel Time Through the Routing Plan

Routing has been improved by better utilizing point-to-point SLR travel distances and timings along with travel statistics. Subscribers of Oracle Field Service Enterprise Cloud Service have the option to limit the travel time for a resource to reach an activity.

You can control travel time through the Routing Plan. With improved Travel time section of the routing plan settings, you can add the option to choose the optimization type and set distance limits.

To control Travel time

  1. Open the Routing Plan. Scroll down to display the Travel time settings.

  2. Choose either time or distance depending the routing plan settings as follows:

    • Prefer fastest routes, even if it means the increase of a total travel distance—Indicates that activities might require lengthy travel but the total travel time for the entire bucket is optimal. This option is the default option and results in the most optimized routes.
    • Prefer shortest routes, even if it means the increase of a total travel time— Indicates that activities might require a longer travel time but the total distance travelled will be optimal.

    You can minimize summary travel if some specific activities are getting long travel or some activities are left unassigned and summary travel may be increased. This enables you to limit the amount of travel time or distance a resource can spend travelling for any one activity. This results in fewer assigned activities and less optimal routes, but eliminates any travel that is beyond the specified amount of time or distance.

  3. Check the following fields and enter the time limit in minutes and the distance limit in miles:

    • Avoid travel longer than __ minutes
    • Avoid travel longer than __ miles
    Note: If no value is set in the in the Individual travel limit, minutes field, it will use a default value, 240 minutes. Similarly if no value is set in the in the Individual travel limit, kilometers field, it will use a default value, 200 kms.

Set the SLR Time Limit

You can now choose separate time limits for Routing and SLR.

Use these steps to choose the time limit for SLR.
  1. Scroll down to the Travel Time section.

  2. Enable the Use SLR check box and select a value from the SLR time limit drop-down list.

    Do not choose SLR Time Limit to be more than or equal to the Routing time limit for the following reasons:

    • Routing time limit defines the time frame within which the whole routing plan should finish.

    • SLR time limit defines which part of this time can be used for SLR-related tasks, allowing you to fine tune routing performance.

    Note: If you use SLR functionality in Routing, you should subscribe to the corresponding SKU.
  3. For those plans having Use SLR check box enabled, SLR time limit field is populated based on the value in the Routing time limit field during migration using these rules:

    • 5 seconds 5 seconds
    • 10 seconds 5 seconds
    • 15 seconds 10 seconds
    • 30 seconds 15 seconds
    • 1 minute 30 seconds
    • 2 minutes 1 minute
    • 3 minutes 2 minutes
    • 5 minutes 3 minutes
    • 10 minutes 5 minutes
    • 15 minutes 10 minutes
    • 20 minutes 15 minutes
    • 40 minutes 20 minutes
    • 60 minutes 40 minutes
  4. Here are some examples:

    • If you choose the Total routing time limit to be 5 minutes and SLR time limit as 3 minutes, you should expect the overall routing result in about 5 minutes, the SLR module uses up to 3 minutes and routing engine uses the remaining time.
    • If you choose the Total routing time limit to be 60 minutes and SLR time limit as 40 minutes, you should expect the overall result after an hour, from which time the SLR module uses up to 40 minutes.
To obtain better quality of routing run with SLR, you must allow adequate time for SLR time limit depending on the number of activities to be routed. We recommend that you allocate a minimum of five (5) minutes for Once a day and Manual routing plans.

Compatibility Parameters

You can view displays those parameters that are not deprecated but not recommended to use in the Compatibility Parameters section.

These parameters are not recommended to use:

  • Try to schedule activities to service window start parameter is not recommended for use.

    Alternatively, you can select the Override default service window reservation check box under the Compatibility Parameters section and set the Service window reservation, % value as 100%.

  • Use Dynamic Routing parameter is not recommended for use.

    You can achieve similar results by just limiting the number of visible activities in the route for Technicians.

    However, if you must set this parameter, you can enable the relevant check box under the Compatibility Parameters.

Sequential Routing Run

Oracle Field Service Routing allows you to configure the Routing plans that run automatically in a strict finish-to-start sequence. Such sequential assignment may be quite important in certain business environments where some activities must be assigned only after a different category of activities has been assigned.

Configuring several Routing plans to run at specified times so that the routing plans follow each other may be a solution. However, this solution is not too reliable. Depending on the number of activities in the bucket, a Routing run may take longer or shorter than estimated which may either create unproductive gaps in the Routing operation or even ruin the sequence. Sequential Routing run has become the optimal solution for this challenge. Two or more Routing plans are configured to start one after the other. The sequence is automatic, thus, any unusually long or short Routing runs will not affect it.

The Routing plan configuration window now has an additional Run Routing option – sequentially. When it is selected, the Routing Run window changes to include the field where the preceding Routing plan is to be chosen. For sequential Routing plans, the selection of a predecessor is mandatory; so, at least one Routing plan has to be created priorly.

Sequential Routing Plan Configuration

The configuration of a sequential Routing run always includes selection of a predecessor Routing plan, that is, the one to be completed before the current one starts. Any Routing plan, regardless of its schedule, can be selected as predecessor. However, any Routing plan can have only one successor, therefore, whenever a sequence has already been created, the predecessor Routing plan of such sequence can no longer be selected for other sequences. Its name is disabled in the list.

The following figure shows the settings for a sequential routing plan:


This figure shows the list of predecessor routing plans.
Sequential Routing plans can be used as predecessors creating longer sequences, if the business needs so require. Other routing plan settings depend on the company specifics and are not influenced by the sequential nature of the Routing plan.
Note: Routing plan sequences can only be created within one routing profile. Sequences of Routing plans between different Routing profiles are not supported. The Routing plan summary shown in the Routing plan header contains its schedule – Sequentially after [predecessor_Routing_plan_name].

A Routing plan belonging to a sequence cannot be deleted unless detached from the sequence. On an attempt to delete such Routing plan, the action is rejected with the [Routing_plan_name] is already in use and cannot be deleted error message. To detach a Routing plan, change the schedule from sequentially to any other, starting from the last plan in the sequence. This restriction applies to all plans in a sequence regardless of their position. The system prevents creation of Routing plan chains forming closed loops in which the first plan is to be started after the completion of the last one. If the first Routing plan in the sequence is changed to the sequential schedule to start after the completion of the last plan in the same sequence, the modification is rejected with the Routing plan {plan_name} cannot be processed error message.

Sequential Routing Plan Execution

A sequence of Routing plans is started with the start of the first Routing plan. The first plan is started according to its schedule settings – automatically (timed), manually or immediately after a certain activity appears in the bucket. After its completion the second Routing plan starts automatically followed by the subsequent Routing plans, if any.

The Routing widget on the Activities screen shows the first Routing plan in the sequence with an icon appropriate to its schedule. The subsequent Routing plans are marked with the 'chain' icon meaning that the plan is part of a sequence. When the first Routing plan in the sequence is started, the user if offered two options – to run only the current Routing plan or the entire sequence. If the user chooses to run only the current Routing plan, it will be executed as any other Routing plan. If the user chooses to run the whole sequence, the completion of the first Routing plan will automatically trigger the second plan, and so on. Sequential Routing plan runs are identified on the Routing screen by the 'chain' icon in the Initiated column and the runs after [predecessor_Routing_plan_name] note in the Routing Plan column.

Any Routing plan belonging to a sequence can be rolled back without influencing other plans in the same sequence. Activities assigned or not assigned as the result of other plans in the sequence will remain in their places. A deactivated Routing plan is skipped in the sequential Routing run. Other plans in the sequence start according to their settings.

This video describes how to create a sequential routing plan.

Immediate Activity Assignment

The Routing module can now prioritize activities and assign urgent ones to technicians immediately, even if it is at the cost of other activities. If the priority of the new activity is high enough, Routing can rearrange technicians' routes and insert urgent activities in front of other activities. This rearrangement happens even when the technician is already on the way to an activity or in the middle of an activity.

Oracle Field Service Routing automatically assigns activities created in the bucket to resources matching the requirements of such activities. Depending on your company requirements, you can select a routing schedule that is the most suitable for a particular bucket. Routing can be started manually or once a day or recurrently with the specified interval. These options covered most of the operational patterns used by different companies. If the company preferred to distribute the workload the day before and provide its technicians with complete routes at the beginning of their working day, then once-a-day Routing is the best option. If the company has to respond quickly to new tasks received during the day, then recurrent Routing running several times a day is the solution.

The demand for a solution designed to handle urgent activities has called for a further enhancement of the Routing schedule options. The Routing module is now able to assign activities meeting certain criteria immediately after they are created in or moved to the bucket. This way, the time between the activity creation and its assignment is minimal. Routing now has one more schedule option, immediate. Depending on the schedule settings, Routing either assigns urgent activities identified by the activity priority or assigns certain activities from the bucket keeping the time till assignment to the minimum.

Urgent and immediate activities with SLA end that have a preferred resource are assigned to preferred resources. If a preferred resource has the work day start after SLA end time and other resources are available to execute this activity, then the activity is assigned to the other resource. Further, if a preferred resource is not available for an urgent activity assignment, the activity will be assigned to another resource with the matching work skills (and work zone based on the routing plan configuration).

Urgent routing doesn't assign activities to those technicians who just have on-call working calendars but their route is not activated. Urgent routing assigns activities to those technicians who have on-call working calendars and their route is activated.

Basic Principles of Immediate Activity Assignment

Immediate-assignment functionality is aimed at assigning certain activities immediately following their creation in or moving to the bucket. It serves the following purposes:
  • Assignment of activities with the minimum ETA possible. The activities to be assigned are determined by the Activity Priority settings.

  • Assignment of activities within the configured interval. The activities to be assigned are determined by applying a filter.

  • Support segmentable activity assignment when the Activity Type = segmentable activity flag is set.

    Note: Segmentable activities are not supported by urgent routing plans.
  • Segmentable activities are available for Immediate Routing when you create them and when you move them to the bucket.

  • Immediate routing of segmentable activities will use the required work skill ratio and not the preferred work skill ratio. This is different from regular activities.

Immediate Routing may not route those activities that are linked with hard constraints if they are assigned to the Bucket and linked before Immediate Routing triggers and starts the processing of such new Activities. Activities linked with other constraints will be routed via Immediate routing without any issues.

Start-start and finish-finish are considered hard constraints as one linked activity is assigned to a resource while another linked activity is in the bucket; this violates the constraint for an assigned activity.

Immediate Routing may still assign one of the linked activities (say activity A) in case if:
  • Activities linked to A are assigned to the field resource

  • Activity A is assigned in such a way that its links will not be violated (apart from other Routing's conditions) .

    Note: Assigning simultaneous links is not supported via Immediate Routing; such activities are skipped and left unassigned.

Resource Filters in Immediate and Urgent Routing

Immediate and urgent routing plans contain resource filters similar to Bulk Routing plans. The Filters section is similar to the Bulk Routing with the following exceptions.

To set resource filters:

  1. Navigate to the Routing screen.

  2. In the row for the Immediate or urgent routing plan, click the Properties icon and select Modify.

  3. In the Edit Routing Plan screen for Urgent and Immediate routing plan, expand the Filters section, set the filters as needed. The Filters section is similar to the Bulk Routing with the following exceptions:

    • Only one predefined filter is available for non-scheduled activities in the routing bucket

    • You cannot add other filters or delete existing filters

    • You cannot add/modify/delete activity filters

Activity Priority

Activity priority used by Routing to assign urgent activities is defined for the whole company as one of the Business Rules settings.

By setting the activity priority the company defines the activity property and its values which will make the activity urgent. For example, the company must always perform repairs as soon as possible to reduce service disruptions to the minimum. In this case the company may select Activity Type as the property and Repair as its value to consider an activity urgent. Only one activity property can be used to identify urgent activities. Several values of the same property can be used as criteria of activity urgency. In this case the values must be separated by commas or carriage returns (new lines) in the Urgent activities have the following values of the property field. Values in the Normal activities have the following values of the property field define the values for the Activity Type field, to consider an activity as normal.

The following figure shows the Activity priority section of the Business Rules screen:


Image shows Activity priority used by Routing with property values and priority level
Note: The order of property values defines the priority level. The value listed first will have the highest priority, with other values following in the descending order.

Priority activity ETA does not include SLA, it includes the service window. This may result in SLA violation. In priority activities, such SLA violations are considered to be expected behavior. However, SLA is included for all rest activities.

SLA Policies Available at Filter Level

In Routing, four additional SLA policies are available to be set up on a filter level. With Default policy, you may prefer to ignore SLA, reduce SLA aging, place activity as late as possible within SLA window or prefer to not route activities out of SLA window. To support more SLA policies, four additional Non Assignment Costs for activity is added and maximum Center Zone cost may now be up to 999 999.

SLA Policy

We recommend that you define the needed SLA policy based on activity's properties. You may create a new SLA policy or use the existing policies. To utilize this feature, make sure that you have activity filters available for use in routing, and clearly differentiate the activities having different SLA treatment policies.

These choices are available for selection in the SLA Policy drop-down list on the Activity Filter parameters window:

  • Default - Execution after SLA End is penalized with prolonged aging period
  • Ignore SLA - SLA is less important than other constraints
  • Reduced Aging - Execution after SLA End is penalized with shortened aging period
  • As Late As Possible - SLA is penalized, but late execution within SLA window is preferred
  • Do Not Allow SLA Overstep - Prevent routing activities out of SLA window

This section discusses these SLA policies in detail.

Default

This is the default policy used for all migrated plans and for newly created plans and filters. This policy provides good balance between SLA and other constraints. while it is possible for routing to assign an activity outside of SLA window, such an assignment is penalized and the penalty is increased day to day, which urges routing to assign an activity either within the SLA window or at least not too far away from SLA End.

Ignore SLA

You must use this policy when SLA is less important than other constraints, for example pure internal SLAs. In this case, routing may prefer another activity to an activity with outdated SLA (which is to be ignored) to the activity being within non-ignorable SLA but having e.g. less travel or higher non-assignment cost. However, when routing is to choose between two activities and for both SLA is to be ignored, routing will prefer one with the most outdated SLA.

Reduced Aging

You must use this policy when your SLA is important but the penalty for breaking the SLA window is either fixed or daily penalty is negligible (at least after the first 7 days). In this case routing will try to assign an activity within SLA window. If it's not possible due to resource restrictions or other constraints, routing will put an activity to a most suitable date instead of trying to do it as soon as possible at all the costs.

As Late As Possible

You must use this policy when your contractual SLA window for repeating work (for example regular maintenance) is calculated based on the date of previous work. While it is important to start (and finish) the work within SLA window, the user may prefer to pull the work closer to SLA End so that no extra work is done. However, this may be altered by other ways of route optimization, for example bundling - if a Technician is already on site for the urgent work and the date of maintenance is approaching, the same Technician may do maintenance as well).

NOTE: For Routing to effectively assign the activity having SLA policy As Late As Possible, you should allow routing plan decent view period in days in advance. It is recommended to route such activities with the plans having Apply to activities within day interval set to two weeks or more.

Do Not Allow SLA Overstep

You must use this policy when your SLAs are dictated by law or government rather than being contractual and overstepping the SLA window may imply serious consequences. If this policy is chosen, routing will either place an activity within SLA window, or reject the assignment with corresponding error message (either 6019 - Unacceptable SLA overdue or more detailed message, providing insights why activity is impossible to be done within SLA window).

Non-Assignment Costs

If there is a chance that an activity that meets the conditions of a given filter might not be assigned, then the application selects a setting that it will weigh against other considerations to determine who will be assigned which jobs – and which might remain in the bucket. In essence, this helps the application prioritize certain types of activities.

This table helps you to decide which non-assignment cost to choose for a particular activity. Note that the higher the non-assignment costs, the lesser the chances of this activity to be left in the bucket or being moved from resource's route to the bucket.

Name Comment
Minimal non-assignment is acceptable
Low assign if it costs almost nothing
Normal assign if it is not expensive
High assign if there is good match between a technician and an activity
Highest assign if there is an acceptable match between a technician and an activity
Extreme assign even if there is poor match between a technician and an activity
Topmost do the best to assign activity
Ultimate activity should be assigned in almost any case
At All Costs non-assignment is unacceptable

For a higher non-assignment cost, use a bigger value for the Center point home zone radius overstep weight value to restrict routing from assignment of important activities outside of this area.

By default, SLA penalty is increasing every day of SLA overstep, so if you have a lot of outdated activities, you should either consider using custom SLA policies (Ignore SLA, Reduced Aging) or use higher non-assignment costs for important activities (while using lower non-assignment costs for not so important activities having outdated SLA).

Follow these steps to configure the SLA policy:
  1. Create a new routing plan or select an existing routing plan to Modify.
  2. Create or choose an activity filter for a given plan and click Settings.

    This image shows the Filter parameters dialog box.

    Image shows Filter parameters dialog box showing SLA policies

  3. In the Filter parameters dialog box, choose the needed value for SLA policy and save the changes.
To configure the Cost of not assigning an activity:
  1. Create a new routing plan or select an existing routing plan to Modify.
  2. Create or choose an activity filter for a given plan and click Settings.

    This image shows the Filter parameters dialog box.

    Image shows Filter parameters dialog box showing SLA policies

  3. In the Filter parameters dialog box, choose the needed value for Cost of not assigning an activity and save the changes.

Constraints and Limits

As of now, only bulk routing supports the SLA Policy and only at the routing plan level. You must make sure that assignment of routing plan having non-default SLA Policy setting is not rewritten by other routing plans with non-default settings and/or manually.

Routing Plan Settings

To assign urgent activities, you must create a special Routing plan.

ETA calculation for priority and normal activities include:

  1. On applying of routing output application moves activities to corresponding resources in accordance with order which is returned in the output.

  2. Priority activity ETA calculation takes into account service window (as it is the time agreed with final customer), but not SLA. This can result in SLA violation. In case of priority activities such SLA violation is expected behavior. At the same time, SLA is taken into account for the rest activities.

The Run schedule field now has the immediately option, which is used to assign the activities meeting the defined criteria as they appear in the bucket.

Once immediately is selected, two options of activity selection appear. Here the user has to choose the group of activities to be assigned immediately. The following options are available:
  • for Urgent Activities (Routing will assign the activities matching the 'property+value' combination defined in the Activity Priority field)

  • for activities that correspond with {filter_name} filter (Routing will assign the activities matching the selected activity filter)

Image shows Run schedule pane with Urgent Activities drop-down list values: manually, once a day, recurrent, immediately, and sequentially

The option assigning activities matching a filter can be useful when certain categories of activities have to be assigned as soon as possible, so that the time between the customer's order and the assignment confirmation is reduced to a minimum. Also, it may be necessary to quickly estimate the remaining available time in a bucket. The main goal is to assign all activities, even if such assignment results in sub-optimal routes. Routes can be reoptimized in subsequent Routing runs. All activities not matching the defined criteria will remain in the bucket until the next Routing run is scheduled according to a different Routing plan.

Urgent activities must be assigned as soon as possible, therefore, other factors, such as resource overtime, cost of assignment or non-assignment, route optimization and reoptimization, etc. are ignored. When immediately is selected as the Routing mode, sections containing other settings (Assignment Parameters, Filters, Reoptmization, Resource Overtime, and Travel Time) are hidden as irrelevant.

Note: Only one routing plan intended to assign Urgent Activities can be created per Routing profile. Multiple Routing plans intended to assign urgent activities may interfere with each other. As soon as one Routing plan is created, the for Urgent Activities option becomes inactive for subsequent Routing plans. For the same reason, the Clone option is not available for a Routing plan configured for assignment of urgent activities.

Assignment of Urgent Activities

When the routing plan is set to Urgent activities, Routing refers to the Business Rules settings defining the urgent activity properties.

If an activity created in or moved to the bucket matches the urgent activity parameters Routing will assign it immediately to the most appropriate resource, even if such assignment violates SLA's of other activities in the resource's route. Urgent activity assignment observes the following constraints:
  • Work zone—the resource's work zone must match that of the activity.

  • Work skills—the resource's work skills must match the work skills required by the activity.

  • Resource preference—the activity may be assigned only to those resources that meet the required or preferred resource preferences, if specified.

  • Service window—the activity service window must be observed.

  • SLA end—the SLA end of the activity must be observed. Activities with expired SLA will not be routed using Immediate Routing.

  • Working Calendar: the resource must have a working calendar to be considered for assignment.

Selection of Resource for Urgent Activity Assignment
Since the principal objective of urgent activity assignment is to reduce its ETA to the minimum, it is important to assign it to the resource, which is the closest to the activity site, so that the travel time is the shortest. Depending on their priority (the priority property value) urgent activities can be placed at different points in the route:
  • At the beginning of the route

  • After a started or completed activity

  • After a pending activity

The position in route which the urgent activity is to take defines the method of determining the resource location. The following cases are possible:
  • The urgent activity is to be placed at the beginning of the route:

    • If the resource has GPS coordinates newer than 20 minutes ago, the GPS coordinates are used.

    • If no GPS coordinates are available or if GPS coordinates are older than 20 minutes, the resource's Start Location is used.

    • If no GPS coordinates are available or if GPS coordinates are older than 20 minutes and no Start Location is assigned to the resource able to ensure the minimum ETA from among those matching the activity requirements, the resource's location is undefined, thus such a position is not suitable for urgent activity assignment.

  • The urgent activity is to be placed after a started or completed activity:

    • If the resource's GPS coordinates are newer than the address of the started or completed activity, the GPS coordinates are used.

    • If no GPS coordinates are available or if GPS coordinates are older than the address of the started or completed activity, the address of the started or completed activity is used.

  • The urgent activity is to be placed after a pending activity:

    • The address of the pending activity is used.

Urgent activities may be assigned to a resource already traveling to a different activity or even in the process of performing a different activity. In this case the urgent activity still has priority, and the resource either has to change direction or interrupt another activity. Any activities for which a different property value is set are not considered urgent and will be assigned in the usual manner.

Assignment of Non-Urgent Activities

When choosing the for activities that correspond with {filter} option, you must select that filter based on which Routing will identify activities to assign immediately.

The drop-down list contains all activity filters applicable for routing which have been created on the Filters screen. When you create an activity matching the selected filter in the bucket, Routing immediately assigns it to an appropriate resource. However, unlike urgent activities, Routing assigns a non-urgent activity to an available time slot (no constraints of other activities will be violated) and only when it causes no overtime to the resource. A Routing profile may contain several routing plans designed to assign non-urgent activities immediately. Such plans may be based on different activity filters, so that activities meeting the criteria of several filters are assigned immediately after creation.

If the All option is selected from the filter list, all activities appearing in the bucket will be assigned immediately.

Non-urgent activity assignment observes the following constraints:
  • Work zone—the resource's work zone must match that of the activity.

  • Work skills—the resource's work skills must match the work skills required by the activity.

  • Resource preference—the activity may be assigned only to required or preferred resources, if specified.

  • Service window—the activity service window should be observed. Note that schedule date is not observed thus, activity may be scheduled to any date up to 14 days from now.

  • SLA start—the SLA start of the activity should be observed.

  • SLA end—the SLA end of the activity should be observed.

  • Required inventory - the activity may be assigned only to those resources that have enough inventory to handle the activity, if specified.

Note: Immediate routing supports segmentable activities only if they are non-urgent activities.

When Routing is set to assign non-urgent activities, it does not perform route optimization. The goal is to assign all activities as soon as possible. The next scheduled routing run may reoptimize the routes created as the result of immediate assignment according to its settings.

Bundling of Activities

You can bundle activities (in immediate or bulk routing) with other activities that are scheduled for the same location and bucket in the near future.

Bundling of Activities in Immediate Routing

Immediate activity assignment may result in certain additional costs related to the violation of other activity SLA or the resource's travel to a different location. To compensate for such additional costs, sometimes it is reasonable to combine the urgent activity with other activities that are located in the same place. Another situation is when the urgent activity requires admission to a restricted area. In this case, the company may assign other activities in the same facility to the same resource and request access only once. Such assignment type is called bundling.

Routing determines which activities may be bundled together by the same criteria that are used in creation of visits. For example, if activity asset (which, depends on activity type, may be translated to activity address or equipment id or area code) is used as a visit bundling key then the activity asset will also be considered in the assignment of urgent activities, and, should any activities be found on the same asset as the urgent one, such activities will be bundled that is, assigned together to the same resource, same day and one immediately after the other.

Bundling of Activities in Bulk Routing

Bulk routing also uses visits bundling key and address (i.e. address, city, state, zip/post code and country) to determine which activities can be performed as a bundle. This provides improved optimization due to time saved on travel and other operations.

To define activities that (are already scheduled in the future and) are eligible to be moved to form a bundle, select these options:
  • Enable moving activities between providers to bundle activities from different routes

  • Enable moving activities from one day to another during routing plan period to bundle activities scheduled to different days.

Bundling in Bulk Routing is a soft rule enforced with each routing run. If a lesser cost-fit method is available or if it is more optimal to perform two or more activities by two or more resources, you can assign multiple resources instead of creating a bundle; the Enable moving activities between resources routes check box is enabled.

Bundling Conditions

The application uses these conditions to determine the activities which activities can be bundled together:

  • activities must be in the Pending status

  • activities must have the same bundling key (for Immediate Routing)

  • activities must have the same bundling key or the same address (for Bulk Routing)

  • activities must be within the defined interval of dates (for Immediate Routing, see below)

  • non-scheduled activities must have an empty SLA start value or a SLA start value within the defined interval of dates (for Immediate Routing, see below)

When the application finds the acceptable destination route, it checks these assignment constraints for all activities in the bundle:
  • work zones—the resource's work zone must match that of the activity

  • work skills—the resource's work skills must match the work skills required by the activity

  • Resource preference—the activity may be assigned only to required or preferred resources, if specified

  • Service window—the activity service window should be observed

  • Access hours – the activity access hours should be observed

  • SLA start—the SLA start of the activity should be observed

  • SLA end—the SLA end of the activity should be observed

  • Maximum duration if a single bundle— 8 hours

Order of Activities in Bundles

When a bundle is formed, the sequence of activities within is determined according to thes constraints:

  1. activity link constraints

  2. activity priority

  3. service window end

  4. service window start

  5. SLA end

  6. SLA start

  7. activity ID

All bundled activities are analyzed for constraints in the order stated previously. If no activities belong to any links, the activity priority, if any, determines the sequence. If no priorities are set for the bundled activities, the activities with the earliest service window end will be placed first, and so on.

Bundling Urgent Activities

When activities are bundled to an urgent activity (the one with the priority defined in the Business Rules screen), the urgent activity is assigned first. When the destination route has been found for the urgent activity, other activities are analyzed to find whether the route can be joined with the urgent activity. While creating a Routing plan for immediate activity assignment, the user can define the period within which Routing has to search for activities to bundle with the urgent one. For that purpose, the Run schedule settings include the Bundling within [ ] day interval field.

The Bundling within [ ] day interval field defines the period within which Routing has to search for activities to bundle with the urgent one. The interval can be set in the range between 1 and 99 days. If no activities matching the bundling criteria are found within the bundling range, no bundles are created.

Bundling Non-urgent Activities

When non-urgent activities are to be assigned immediately, the system checks if any activities in the already existing routes have the same bundling keys. Upon finding such routes, the system checks other assignment constraints and assigns a non-urgent activity only if all assignment constraints are satisfied. A non-urgent activity will be assigned to the route containing the largest number of activities with the same bundling key or to the route with the earliest date. If no such route has been found, the non-urgent activity is assigned to the first acceptable route with no bundling. The bundling date range is defined as part of the Routing plan settings.

The following assignment and bundling settings can be made:

Assignment and Bundling within [ ] day interval starting [ ] – the start and duration of the period within which the application has to assign scheduled activities and create bundles with the already assigned ones. The bundling interval can be set in the range between 1 and 99 days. Assignment and bundling of activities will start on the selected day and continue for the defined duration of the interval. For example, if the following settings have been made: Assignment and Bundling within 10 day interval starting Today +2, the application searches for activities matching the visit bundling keys two days from today and continue for 10 days. Non-urgent activities will be assigned to form bundles with the found activities within the same period. If no bundles can be formed, non-urgent activities will be assigned to routes within the same period

Immediate Routing Plan Execution

Immediate Routing Plan is triggered by the creation of an urgent activity or an activity matching the filter in the bucket. If activity is not routed immediately after it is placed in the bucket (due to lack of resources or not matching the filter), Immediate Routing Plan may be re-triggered periodically and also by any activity property change. Immediate Routing plans can never be started manually and, therefore, have no Run link in the list of Routing plans for a bucket.

The results of an immediate Routing run include the following data:
  • If the plan was set to assign Urgent Activities:

    • Assigned activities – the number of successfully assigned urgent activities

    • Bundled activities – the number of other activities joint with the urgent ones

  • If the plan was set to assign non-urgent activities matching the selected filter:

    • Assigned activities – the number of activities assigned without creating bundles

    • Assigned with bundling activities – the number of activities matching the selected filter assigned in bundles

    • Bundled activities – the number of activities from the bucket or non-scheduled pool joined with the filtered activities to create bundles

Assignment and Fallback Options for Activity Broadcasting

The Assignment and Fallback section is displayed when you create a routing profile with the option, immediately from the Run routing drop-down list.

Note: You must enable the Collaboration service to view the Assignment and Fallback section. View the About screen to verify whether the service is enabled.
The Assignment and Fallback section is used to configure the following settings:
  • To trigger activity broadcasting to multiple users, use one of the following options:

    • Automatic: Assigns activity directly to matching resources in the bucket.

    • via Collaboration: Triggers activity broadcasting to users in collaboration.

    Note: The Bundling option is not available when you assign activities using the via collaboration option.
  • Enter the time in minutes in the Activity should be assigned in _ minutes field to set the time out period for broadcasting. If no user accepts the activity within the defined period, broadcasting is timed out. Limit is set to 99 minutes.

  • Fallback option: Select the configured message scenario for the Fallback option that must run when the activity fails or when the system times out. The configured message scenario sends the failure message to the user.

Automate Required Inventory Pickup Creation Using Bulk Routing

Bulk routing may auto-create inventory pickup activities to obtain required inventory pieces from the nearest warehouse and handle the changes during intra-day routing re-optimization runs. This increases the autorouted percentage value and improves routing quality as the same technician completes more activities.

This feature includes these options:

  • Bulk routing auto-creates activities to pickup inventory from the nearest warehouse if such an inventory pickup allows more optimal routes creation according to chosen optimization goal
  • New settings are available in the routing plan to support automated creation of required inventory pickup
  • New activity type group and new pre-defined activity type are available for Warehouse visits
  • Viewing the amount of inventory booked via the automated required inventory pickups creation by bulk routing is available on the warehouse inventory page
  • Calendars and locations may now be added to resources of all roles excluding Organization Units but including Buckets and Tools

You will learn how to automate required inventory pick-up using bulk routing in this section.

Follow these steps to utilize inventory pickup functionality:

  1. Review Warehouse Visit activity type and modify if necessary or create a new activity type.

  2. Add a warehouse resource type

  3. Create and configure a warehouse resource.

  4. Fill the Warehouse inventory.

  5. Update the inventory identifier screen configuration.

  6. Add resource filter for use in routing plans.

  7. Configure a routing plan.

  8. Plan for recurrent optimization.

This section discusses the above steps in detail:

Review Warehouse Visit Activity Type

The 20D version of OFS automatically includes a Warehouse Visits activity type group, and the default Warehouse Visit activity type is included for your convenience. If the default activity type meets your organization’s needs, you don’t have to do anything else regarding this step.

If it doesn’t meet your needs, you can edit it by defining the default duration, selecting time slots, and disabling any of the selected features (except for “Support of Inventory” and “Support of not-ordered activities,” which are enabled by default). Notice that pending Warehouse Visit activities use purple color-coding to help identify them on the Manage view and Dispatch Console.

If you want to create a new warehouse activity, you must select Warehouse Visits for the activity group. The Warehouse Visits activity group automatically limits the available features for any activity type created within that group. For example, “Support of inventory” is selected by default. Other constraints include the inability to select the activity to be mass or repeating activities, to move or reschedule activities of this type, and to support work skills or work zones. Additional limitations exist, and the Features list is specifically configured to enable only the allowable features for activity types in this activity group.

Add a Warehouse Resource Type

Add a warehouse resource type that uses the Bucket resource role. Be sure that it’s active. The “Routing can assign activities” and “Used for quota management” features can be enabled at your discretion.

Create and Configure a Warehouse Resource

Decide whether the warehouse routing resource should be a child of the bucket that contains the activities to be routed. Another option is to locate it outside the routing bucket’s hierarchy. If you choose this option, the following conditions must be met before Routing can create an automatic pickup activity for required inventory:
  • The warehouse resource must have at least one of the same work zones as the routing bucket.
  • The Filters section of the routing plan must have “Use resources outside the routing bucket” enabled.
  • The activity’s work zone must match the warehouse’s work zone.

Now, you’ll create a warehouse resource. For Resource Type, select the one you just created. And for Org Unit/Bucket, select either the routing bucket or the entity where you want to warehouse to reside in the resource tree.

You must add a Start location for the warehouse resource, which is simply its address, and that you set that Start location for each day of the week the warehouse is open. You must also ensure that the warehouse resource’s calendar is set for the days of the week and hours of the day when field resources can pick up required inventory. Routing can create Warehouse Visit activities only if the warehouse resource has both location and calendar information specified.

Fill Warehouse Resource with Inventory

You can create inventory for the warehouse resource via API (see the Integration section under Additional Information), or you can do so manually by selecting Resource Inventory on the Resource Info screen for the warehouse resource, selecting Add to Resource, and adding inventory items.

Update the Inventory Identifier Screen Configuration

This step updates the “Identify equipment by” identifier screen configuration to display the Booked Quantity value for each inventory item. The regular Quantity value does not change when the Warehouse Visit activity is created, although OFS does note that the required inventory is booked. And OFS knows that the remaining available inventory is the total quantity minus the booked quantity. Adding this step simply lets you see what’s been booked.

To do this, under the Collaboration and Identifiers section of the user type screen configuration, open the “Identify equipment by” screen context and add the Booked Quantity property. If no required inventory has been booked, this value will not appear in the equipment list.

Add Resource Filter for Use in Routing Plans

Routing needs to be able to identify warehouse resources, so the next step is to create a resource filter that uses the condition “Resource Type (ptype) In Warehouse.” (Creating a custom property to distinguish a warehouse resource type from other resource types is also an option.)

Configure Routing Plan

You can configure the automatic creation of Warehouse Visits to pick up required inventory for any type of routing plan.

The first thing you need to do is modify the Assignment Parameters section by selecting Enable Routing by Inventory. Then select Enable Inventory Pickup and select the Warehouse Visit activity type from the “Inventory pickup activity type” drop-down menu.

Next, you’ll make some changes to the Filters section of the routing plan. Select one of the activity filters, select Resources, and then select the Warehouse resource and set its priority to “Treat as warehouse.” (This step needs to be done for only one filter within the routing plan, regardless of the total number of filters being used.)

Plan for Recurrent Optimization

Throughout the day, if activities get added, canceled, or deleted, it may affect the booked and available quantities of inventory at the warehouse.

Here’s what happens in those circumstances:
  • If the activity requiring inventory is deleted or canceled before inventory pickup, the inventory in the Warehouse Visit activity is not changed, but a warning appears to let the technician know that inventory needs have been changed. It is possible that the Warehouse Visit is for picking up inventory for multiple jobs, the Warehouse Visit activity is not deleted automatically.
  • In these additional situations, no changes are made to the Warehouse Visit activity:
    • If the activity requiring inventory is suspended or changed to non-ordered
    • If the activity is moved (manually or via API) to another day and/or resource

It is recommended that you follow the best practice of running recurrent optimization plans on the bucket. This practice can add, modify, or remove Warehouse Visit activities and update the warehouse inventory list. This is true even if multiple Warehouse Visit activities were scheduled for a single customer activity.

You may want to set up a recurring daily Warehouse Visit activity to maintain a placeholder for that activity in every route to account for a resource’s time. Then, when a day-before or intraday optimization plan is run, if no missing required inventory is identified, Routing will automatically remove the Warehouse Visit activity from the route.

Additional Information

Moving Automatically Created Warehouse Visit Activities

Although you can manually edit Warehouse Visit activities that were created automatically, we recommend against it to avoid jeopardizing other activities in the route. If manual editing makes changes that do jeopardize other activities or the Warehouse Visit activity, a warning message appears.

Working with Both Regular and Automatically Created Warehouse Visits

Although Routing will automatically create Warehouse Visit activities when needed for activities with required inventory, it’s possible that you also have “regular” warehouse visit activities that were created either manually or via API for example to replenish trunk stock. Both of these types of warehouse activities can appear in the same route. And you may want to continue to manage the regular activities manually. However, it may be possible that the inventory needed by regular visits is available at the same warehouse as the automatically created visit, it makes sense to pick up all inventory at the same time.

One way to accomplish that is through two different activity types for warehouse visits: one created in the Internal activity group for manually managed warehouse activities, and the other created in the Warehouse Visits activity type group. When you do that, Routing will create, update, and delete required inventory pickups automatically, and it will bundle regular visits with the automatically created visits if they both have the same address – the warehouse resource’s Start location.

Another way to accomplish that is to create regular Warehouse Visit activities as placeholders in every route. You can even use the same activity type in the Warehouse Visits group for both manually and automatically created Warehouse Visit activities. Then, any required inventory that needs to be picked up is automatically added to the pre-created activity, and if no required inventory is needed, the activity is removed. If you want to ensure that Warehouse Visit activities remain on future days’ routes, you can set your optimization plan to remove only today’s warehouse activities if no required inventory needs to be picked up.

Working with Multiple Warehouse Visit Types

By default only one predefined Warehouse Visit activity type is available to automatically create a visit activity to pick up required inventory. You can, however, create additional types for use in different routing plans. For example, you might want to differentiate Warehouse Visits for in-house workers and contractors. You can set up one activity type with a default activity duration for the contractor Warehouse Visit, while setting up another that uses learned statistics to estimate pickup duration for in-house resources.

Working With Visits Created by Order Parts Plug-in V.2

If you created an order pickup plug-in based on the sample code of plug-in-order-parts-collection_v2.zip placed at https://www.oracle.com/downloads/samplecode/ofsc-samplecode-downloads.html with the option to create follow-up activity turned on, and you would like to use plug-in and the feature under the same routing bucket, make sure that these options are available:

  • The inventory items ordered via Order parts plug-in are not the same inventory items the warehouse is filled with
  • Moving activities between providers and reordering is prohibited for activities being created by Order Parts plug-in.

Integration

To fill the inventory list of the warehouse, use REST API the same way as filling the field resource inventory: Use the standard API requests, and refer to:
  • https://docs.oracle.com/en/cloud/saas/field-service/20c/cxfsc/op-rest-ofsccore-v1-resources-resourceid-inventories-post.html for individual requests
  • https://docs.oracle.com/en/cloud/saas/field-service/20c/cxfsc/op-rest-ofsccore-v1-resources-custom-actions-bulkupdateinventories-post.html for bulk requests
The Events API can be used to track the initial activity booking by filtering the events for the creation of Warehouse Visit activity types. You can also track changes made to inventory booking through routing optimization by filtering the events of inventory creation/deletion for the activity type. These are the events produced when Routing automatically creates required inventory pickup activities:
  • activityCreated – Routing creates warehouse visit activity.
  • activityMoved – Initiated when rollback occurs and a Warehouse Visit is deleted. An Undo Rollback action is available because Routing does not actually delete the Warehouse Visit activity but instead moves it to a hidden queue of the same resource for the same day. Then, if no Undo Rollback occurs, Routing deletes those hidden visits in the next routing run.
  • customerInventoryCreated, customerInventoryUpdated, customerInventoryDeleted – Routing performs adjustment of inventory reservation. The created inventory items belong to the customer pool and has references to both the Warehouse Visit activity and warehouse bucket. A reference to the warehouse bucket can be used to distinguish the reserved inventory from the regular customer inventory. Also, although the reserved inventory can be serialized, it doesn’t have serial number values.

Capacity/Quota

Routes that have multiple Warehouse Visits can affect capacity and quota because these activities require time to pick up inventory from warehouse. To compensate for this, you can reserve quota by setting the threshold lower than 100% of capacity for activities in capacity categories that might be affected by inventory pickup.

Limitations

Routing by inventory functionality does not support segmentable activities. It does not create required inventory pickups for such activities.

Warning Messages/Troubleshooting

If the warehouse resource cannot be used, you will see one of the following messages. This table provides the steps to correct the problem:

Warning How to fix
Field resource cannot be used as a warehouse Fix the filter used for "Treat as warehouse" to exclude field resources. Do note that buckets are recommended to be used for warehouses.
A resource sharing inventory in teamwork cannot be used as a warehouse Disable ability to share resources in teamwork for a given resource type.
A resource without Start Location cannot be used as a warehouse Make sure that Start Locations are assigned for warehouse resources for all the days covered by routing plan
A resource without working calendar cannot be used as a warehouse Make sure that Working Schedules are assigned for warehouse resources for all the days covered by routing plan
A resource without inventory cannot be used as a warehouse Make sure that warehouse could have an inventory. Make sure that inventory was assigned to a warehouse.

Bulk Routing (High Uniformity) Routing Profile

The routing plan in the Bulk Routing (High Uniformity) routing profile distributes activities evenly across the entire workforce while still minimizing travel and work costs where possible.

The following table describes the values you must set in the Routing plan section:

Setting Value Explanation
Routing Plan Name Uniform – Bulk Routing N/A
Routing Profile Bulk Routing (High Uniformity) N/A
Active Checked The routing plan must be active before the application can use it to run routing.
Time Limit 3 minutes The amount of time that the plan runs. Three minutes is usually sufficient. In some cases, running the plan longer might produce a result that better matches your objectives.

The following table describes the values you must set in the Routing schedule section:

Setting Value Explanation
Run routing N/A N/A

You can use any run schedule with this goal. Most companies that use bulk routing run the plan once a day in the evening or early morning.

The following table describes the values you must set in the Filters section:

Setting Value Explanation
Resources link Activities *Bulk Routing does not use filters. You can add filters to prioritize certain types of activities or certain resources over others.
Scheduled Assignment Cost Normal

The following table describes the values you must set in the Filter parameters section:

Setting Value
Assigning Activities which are about to be late Do not assign "overdue" activities and leave them in the bucket
Cost of not assigning an activity Normal - default setting
Late arrival penalty Normal - late arrival may result in rescheduling if the customer is no longer at home

The following table describes the values you must set in the Assignment parameters section:

Setting Value Explanation
Enable routing by inventory Check box is cleared
  • Routing takes into account required inventories for all activities that are sent to routing. Activities which have no inventory requirements are not affected by this setting.

  • They will be routed in the same way as before. Activities which have inventory requirements can only be assigned to resources which meet all inventory requirements.

  • Activities will be left unassigned if there are no resources which meet their inventory requirements.

Enable Inventory Pickup Check box is selected Bulk routing may auto-create an inventory pickup activities to obtain required inventory pieces from the nearest warehouse and handle the changes during intra-day routing re-optimization runs. This increases the autorouted percentage value and improves routing quality as the same technician completes more activities.
Dynamic Routing Check box is cleared Dynamic routing enables you to control the number of activities or the amount of time that should be filled on the resources’ schedules. Routing plans that use dynamic routing are typically run recurrently throughout the day.
Limit work by points Check box is cleared
  • This option is necessary only if you use points to estimate activities.

  • This option limits the number of activities assigned to a resource based on the maximum points allowed within the shift.

  • The point value for each activity must be sent through the API.

Try to schedule activities to service window start Check box is selected This option schedules activities as close to the start of service windows as possible. As a result, the activities are divided evenly across all of the resources in the bucket. Activities are typically more evenly distributed, but routes may be less efficient.
Center point home zone support and Home zone radius 4 An optional setting that permits you to specify a radius spans a technician’s starting location. Penalties are assessed for assigning activities outside the circle of the defined radius. The further away the activity is, the higher the penalty.
Home zone radius overstep weight 4 This option defines the penalty to be applied if the resource leaves the home area to complete the activity. This option is displayed when Center point home zone support is selected.
Automatic Ordering Check box is selected This option places activities without service windows on the route in the most efficient order. Checking this option makes routes more efficient, but reduces the resources’ freedom to exercise judgement in completing activities.

The following table describes the values you must set in the Optimization Strategy section:

Setting Explanation
Optimization Goal Select the goal from the drop-down list: Reduce overdue, optimize routes, or assign high priority activities.
Filters Filters compare routing results with the activities in the bucket and reassign activities based on the priorities set in the new filters.

ClickAdd filters to add activities which can be optimized.

Under Activities, select the filter that you want to run against the activities in the bucket. Under Destination for unassigned activities, select the status that you want to assign to activities that are not assigned to routes and are, instead, returned to the bucket.

This table describes the values you must set in the Resource overtime section:

Setting Value
Assign activities even if the assignment causes overtime Check box is cleared
Do not assign "overtime" activities and leave them in the bucket
Note: When you select this option, resources do not receive activities that will extend their workday past their scheduled working hours.
Check box is selected
Do not assign activities with more than __ min. overtime Check box is cleared
Do not assign activities that unlikely to be finished in __ min. before end of resource's day Check box is cleared
This table describes the values you must set in the Travel time section:

Setting Value
Minimize summary travel even if some activities require long travel times.
Note: This option produces routes with optimized travel times for the entire organization, but not necessarily for each individual resource. As a result, a few activities might require long travel times, but the amount of travel for the whole group is optimized.
Check box is selected
Avoid travel longer than __ minutes, even though some activities might not be assigned and summary travel might increase. Check box is cleared

Dynamic Routing Profile

The routing plan in the Dynamic Routing (2 Activity/120 min) routes activities frequently. This routing plan is useful when activities are booked shortly before the activity time or when you do not know in advance which resources will be available to accept the activities. Routing results are not as optimal as using bulk routing, but activities are routed closer to their actual activity time.

The following table describes the values you must set in the Add routing profile screen to create a dynamic routing profile:

Setting Value Explanation
Routing Plan Name 2hr in advance - Dynamic Routing N/A
Routing Profile Dynamic Routing (2 Activity / 120 min) N/A
Active Check box is selected The routing plan must be active before the application can use it to run routing.
The following table describes the values you must set in the Run schedule screen to create a dynamic routing profile:

Setting Value
Run routing Recurrent
Apply to activities within 1 day interval ( Range of 1 and 99 days)
starting Today
Start time 6:00
End time 20:00
Interval between runs 30 minutes
Activity days Mon, Tue, Wed, Thu, Fri
Time limit 5 minutes
Three minutes is usually sufficient. In some cases, running the plan longer might produce a result that better matches your objectives. When activities are added to the system throughout the day and require a quick turn around, you must run routing plans frequently. Choose the recurrent option and run the plan to Today’s activities. Set the interval between runs to a short interval, typically 30-60 minutes is optimal. The following table describes the values you must set in the Assignment parameters section to create a dynamic routing profile:

Setting Value Explanation
Home zone radius overstep weight 4 This option defines the penalty to be applied if the resource leaves the home area to complete the activity. This option displays only when Center point home zone support is checked. The default value is 4.
Try to schedule activities to service window start Check box is selected This option schedules activities as close to the start of service windows as possible. As a result, the activities are divided evenly across all of the resources in the bucket. Activities are typically more evenly distributed, but routes might be less efficient.
Automatic Ordering Check box is selected This option places activities without service windows on the route in the most efficient order. Checking this option makes routes more efficient, but reduces the resources’ freedom to complete activities when they want to.
Center point home zone support and Home zone radius An optional setting that enables you to specify a radius that spans a technician’s starting location. During the routing process penalties are assessed for assigning activities beyond this radius. The further away the activity is, the higher the penalty.
Limit work by points Check box is cleared This option is only necessary if you use points to estimate activities. This option limits the number of activities assigned to a resource based on the maximum points allowed within a resource’s shift. You must send the point value for each activity through the API. This option displays only when Center point home zone support is checked.
The following table describes the values you must set in the Filter parameters screen to create a dynamic routing profile:

Setting Value Explanation
Load Resources for 120 minutes

2 activities

Dynamic routing enables you to control the number of activities that should be placed on the resources’ schedules, or the amount of time that should be filled on the resources’ schedules. 120 minutes means that the routing plan fills the resource’s next 120 minutes with activities and 2 activities means that the routing plan assigns, at most, two activities to the resource.
Stop loading when any limit is exceeded Check box is cleared When checked, this option instructs the routing plan to stop adding activities to the resource’s schedule when either the activity limit or the time limit is reached.
Stop loading when both limits are exceeded Check box is selected When checked, this option instructs the routing plan to stop adding activities to the resource’s schedule when both the activity limit and the time limit is reached.
Assign activities even if the assignment causes overtime Check box is selected When you select Assign activities even if the assignment cause overtime, routes are optimized for travel time and work, but resources might need to work past their scheduled working hours.
Do not assign "overtime" activities and leave them in the bucket Check box is cleared When checked, this option instructs the routing plan to stop adding activities to the resource’s schedule when both the activity limit and the time limit are reached.
The following table describes the values you must set in the Resource overtime screen to create a dynamic routing profile:

Setting Value
Do not assign activities with more than __ min. overtime Check box is cleared
Do not assign activities that are unlikely to be finished in __ min. before end of resource's day Check box is cleared
Note: When you select Assign activities even if the assignment cause overtime, routes are optimized for travel time and work, but resources might need to work past their scheduled working hours.
The typical selection for this setting is Minimize summary travel even if some specific activities have long travel. This option produces routes with optimized travel times for the entire organization, but not necessarily for each individual resource. As a result, a few activities might require long travel times, but the amount of travel for the whole group is optimized.

Change the Optimization Goal

You can now select optimization goals for the routing plan and set routing plan parameters in an optimal way. When you select an Optimization Goal, routing tweaks the variable parameters (costs) and suggests changes to the routing plan parameter:

Migration

During the migration process, re-optimization goals are migrated to optimizations.

This table provides the re-optimization goals and new optimizations goals:

Legacy Re-optimization Goal

New Optimization Goal

Optimize routes

Default

Assign high priority activities

Maximized assigned activities number

Reduce overdue

Reduce activities overdue

To set optimization goal for a routing plan:

  1. Navigate to the Routing screen.

  2. Select the routing plan that you want to modify in the list.

  3. Click the Modify link to display the Modify routing plan dialog box.

  4. Expand the Optimization Strategy section and select an Optimization goal from the drop-down list:

    This figure shows the Modify routing plan dialog box with the Optimization goal options:

    Image shows the parameters under Optimization goal drop-down list

  5. When you select an Optimization Goal, routing tweaks the variable parameters (costs) and suggests changes to the routing plan parameter.

    • Default—Ensures that there are no changes in the general routing behavior in comparison with previous versions. This is the default value.
    • Maximize assigned activities number—Slightly pushes the routing optimization behavior so that more activities are taken to the routes in total even if it requires more travel. If moving the activities between resource routes is ON, the routing plan will start only if there are non-assigned activities with high or highest non-assignment cost and the results are applied only if at least one such activity is assigned. The suggestions listed also help in setting up a routing plan to assign activities more aggressively.
    • Minimize total travel—Slightly pushes the routing optimization behavior such a way that less travel is involved even at the cost of lesser total activities number. The suggestions listed also helps to set up a routing plan to minimize travel more aggressively.
    • Maximize activities per resource ratio—Slightly pushes the routing optimization behavior in accordance to real travel time or distance in such a way that activities are assigning to less number of resources, leaving some of them completely free if possible. This option is recommended if there more personnel in the bucket that are needed for today and user would like to transfer resources to another bucket for some time. The suggestions listed also helps to set up a routing plan to minimize number of assigned resources.
    • Reduce activities overdue—If moving the activities between resource routes is ON, the routing plan will only start if there are activities to be processed with high or highest overdue penalty and actually assigned with overdue and the results are applied only if the resulting overdue was decreased by given percentage. The suggestions listed helps to set up a routing plan to minimize number of activities having overdue and total overdue value
  6. Based on the selected option, internal routing optimization strategy is tweaked for better achieving the goal (with the except of default Balanced mode, which leaves costs untouched)

  7. If there are other parameters that are set to sub optimal values according to the selected goal, the suggestions for their values will also be displayed in this section.

  8. Click Update to save your changes.

Optimize Travels Within a Single Route

Routing allows you to optimize travels within a single route. Routing reorders activities within the same route and to reassign them to another resource to achieve better travel results.

To set travel optimization within a single route, follow these steps.

  1. Navigate to the Routing screen.

  2. Find the row for the routing plan that you want to modify.

  3. Click the Modify link to display the Modify routing plan dialog box.

  4. Expand the Optimization Strategy section and select an Optimization goal from the drop-down list.

    • Choose Do not move activities between routes and do not reorder activities if you want routing plan to add activities to existing routes without moving existing preassigned activities either between resources or within the same route.

    • Choose Reorder activities within resource route for the routing plan to reorder activities within the same route but not moving them between different providers routes.

    • Choose Move activities between resources routes only for the routing plan to reassign activities but keep the order of activities in the same route unchanged.

    • Choose Move activities between resources routes and reorder within the same route so that the routing plan can both reassign and reorder activities.

  5. Based on the selected option, internal routing optimization strategy is tweaked for better achieving the goal.

  6. To manage chances activities being moved within different routes, set the value Moving activities penalty value.

    If you set this value to 0, activities are moved whenever there are better routes according to selected optimization goal and routing plan settings.

    The higher this value is, the bigger gain such a reassignment should bring for being applied, otherwise routes remains unchanged.

  7. If the route reordering is applied, it allows routing improvement according to selected optimization goal and routing plan settings.

  8. Click Update to save your changes.

Add an Activity Filter to a Routing Plan

You can use filters to prioritize certain types of activities or resources over others during the routing process. Filters are an alternative to using another routing plan for prioritization.

You must create the filter, set the conditions, and make the filter available for routing first. See Creating a Filter for more information.

To configure routing parameters:

  1. Navigate to the Routing Profiles screen and find the routing plan that you want to add the filter to.

  2. Click the Modify link.

  3. Expand the Filters section of the Edit Routing Plan screen.

  4. Click the Add activity filter button.

    The Set of activities to be assigned dialog box is displayed.

  5. Select the filter that you want to add to the routing plan from the Activities drop-down list.

    A drop-down list is displayed.
  6. Select the type of activities to which the filter should be applied from the second drop-down list (if any).

    • Non-scheduled activities in the routing bucket. These activities are not currently on any route. They are not assigned to time slots or resources. Routing will attempt to route them during the next run.

    • Activities in the routing bucket. These activities are not currently on any route. They are assigned to time slots, but are not assigned to resources. Routing will attempt to route them during the next run.

    • Preassigned non-scheduled activities. These activities are already assigned to resources, but they are not assigned to time slots. You can use reoptimization to automatically move these activities during the routing process.

    You can add the filter for Activities in existing routes by clicking the Add activity filter link. These activities are already assigned to resources and time slots. You can use reoptimization to automatically move these activities during the routing process.

  7. Optional: Under Assignment Cost, assign a cost to this filter.

    In general, the higher the cost, the less desirable the assignment. If you select Do not assign, activities of that type can never be assigned to a resource that meets this filter condition.
    This figure shows the Set of activities to be assigned dialog box with activity priority levels for the selected activity:
    This figure shows the Set of activities to be assigned dialog box with activity priority levels for the selected activity.
  8. Repeat these steps to add additional filters to the routing plan. Arrange the filters in the order that you want them to be applied using drag and drop. The filters are applied in chronological order starting at the top of the list. The * (Other) filter is always applied last.

  9. Click OK.

Assignment Cost for Multiple Activity Filters

In this example, the routing strategy includes these steps:
  • Do not assign work to contractors.

  • Assign activities to In-house resources before all others.

The Contractors filter has the assignment cost Do not assign so that activities are never assigned to contractors.

The In-House filter has a lower assignment cost than the * (Other) filter so that in-house personnel receive activities before all other resources.

Configure an Activity Filter for Routing

Once you have added a filter to a plan, you can adjust some additional settings that affect how the Oracle Field Service Routing module processes the filtered activities.

Note: Evaluate these settings carefully before changing them. They add constraints to the routing process that can significantly restrict the number of activities that are assigned to routes.

To configure an activity filter:

  1. Navigate to the Routing Profiles screen and find the routing plan that you want to add the filter to.

  2. Click Actions and select Modify to open the Edit Routing Plan screen.

  3. Expand the Filters section of the Edit Routing Plan screen.

  4. Find the filter that you want to configure and click Settings.

    The following figure shows the Filter Parameters screen:


    Image shows the Filter Parameters screen for a selected routing plan.
  5. Select options for this filter based on your business goals and click Submit:

    • Late arrival penalty: The weighting options regarding lateness penalties range from “minimal” to “highest." Examples are provided to assist in selecting the best option. The application uses this information to weigh activity assignment decisions when there’s a chance that a resource will arrive late to an activity.

    • Assigning activities which are about to be late: You can set a “lateness tolerance” that the application will accommodate when assigning new activities to resources.

      Note: For preassigned activities, use the Do not assign activities with more than X minutes overdue option with a high X (for example 1000) value. Do not use Assign activities even if resource is unlikely to arrive inside time slot option.
    • Cost of not assigning an activity: If there is a chance that an activity that meets the conditions of this filter might not be assigned, then this option provides the application with a setting that it will weigh against other considerations to determine who will be assigned which jobs – and which might remain in the bucket. In essence, this helps the application prioritize certain types of activities.
      Tip: The normal setting sometimes leaves too many activities unassigned. When this happens, test your results with the high setting or the highest setting.
    • Allow rescheduling of activities from one day to another within routing plan period: Use this option to reschedule activities in a segmentable activities routing plan. When this option is selected, only the activities for which the option is selected are rescheduled within the period that the routing plan runs. For example, if you have a segmentable activities routing plan that spans for five days, and you want to reschedule an activity that was supposed to be started on the second day, the activity will be rescheduled either for the third, fourth, or the fifth day. If an activity cannot be rescheduled, an appropriate message is displayed. Remember, the results of running a segmentable activities routing run without rescheduling is the same as running single-day runs for the same number of days.

Alter Automatic Ordering for a Routing Plan

The Not Ordered Activity Behavior option in the Add or Edit Routing Plan dialog box places the activities that are without service windows on the route in the most efficient order. If you set it to Do not order, the application places these activities on the route, but does not assign a time slot. In this case, resources decide when to do the work. If you set the option to Order, it helps you complete more activities through the day, but it also reduces the resource's ability to use their own judgment in completing activities.

You can alter automatic ordering for the routing plan at a filter level.

Follow these steps:

  1. In the Add/Edit Routing Plan, navigate to the Not Ordered Activity Behavior section before the Filters section:

  2. In the Not Ordered Activity Behavior field, select the Order by filter option and click Update.

  3. Alternatively, you can set this option in the Filter Parameters dialog box:

    This image shows the Filter parameters dialog box with Not ordered activity behavior field.

    The image shows the Filter parameters dialog box with Not ordered activity behavior field.

  4. For each filter, select one of these options in the Not Ordered Activity Behavior field and click Update:

    • Do not order—Select this option if you do not want to change the activity ordering status – status of all activities will be as Ordered after the routing.
    • Order—Select this option if you want to make all of the activities as automatically ordered during the routing plan. This is a default value for new routing plans.
    • Order by—Select this option if you want to make all eligible activities as automatically ordered or unordered during the routing plan.
    By default, when you choose the Order by filter option for Not Ordered Activity Behavior on routing plan level, all activity filters will have their Not Ordered Activity Behavior set to Order. The same setting is default for newly added filters.
    Note: When creating, routing plans will have Not Ordered Activity Behavior on routing plan level set up to Order. You must manually set this option.

Migration from Oracle Field Service versions prior to 19D

Routing plans having Automatic ordering option set to ON after migration will have Not Ordered Activity Behavior on routing plan level set up to Order. Routing plans having Automatic ordering option set to OFF after migration will have Not Ordered Activity Behavior on routing plan level set up to Do not order, so the behavior of migrated routing plans remains unchanged after the migration.

Assign Activities to Temporary Resources

Normally routing considers activities from a given bucket and routes it down through the children in the hierarchical tree. However, there could be a situation where a resource must be temporarily assigned to work in an area, which is not part of the parent resource hierarchy. To handle such situations, routing can be configured to use resources from different parts of the resource tree.

To enable the feature, follow this process:
  1. Select the Work zone support check box on the Business Rules screen.

  2. Assign one (or more) work zones common with the routing bucket to the resource on the Resource work zones screen. You must assign the Work Zone to the resource, and not to the parent organization unit. Work Zones assigned to the parent Organization Unit (bucket or organization) will not be used for this purpose.

  3. On the routing plan editor, open the Filters section and check the Use resources outside the routing bucket check box.

After you have followed the steps mentioned earlier, resources that are permanently located in the bucket and the resources that are temporarily assigned are treated equally while assigning activities. This is available for manual, once a day, recurrent or sequential routing plans. The Routing screen shows the number of resources available for the given bucket and routing plan. As with other routing plans, Routing takes into account the work skill levels, work zone ratios, work schedules, locations and all other parameters while routing activities for temporary resources.
Note: The assign activities to temporary resources feature is not available for immediate or urgent routing plans.

Suppose that you have enabled the Organizations option and you have more than one organization defined. In this case, the activities are routed to the temporary resource only if the resource's organization matches with either the bucket's organization or the organization of any bucket or organization unit down the hierarchical tree. Suppose that you run a routing plan simultaneously on two (or more) buckets, which could be at different levels, but share the same resources that are either temporarily assigned or present in the tree hierarchy. The subsequent plans are paused until the previous plans finish running. This might lead to a delay in displaying the routing run results.

Enable or Disable Activation of the Route for a User Type

You can now enable or disable activation or reactivation of the route for a particular user type:

To enable or disable activation or reactivation of the route for a user type, use these steps.
  1. Click the Navigation button and select Configuration.

  2. In the User Types configuration page, select the desired user type.

  3. Click the Enable GPS Telemetry check box under the Permissions section.

  4. To enable route activation, clear the Disable route activation if geolocation is not enabled on device check box

  5. To disable route activation, click the Disable route activation if geolocation is not enabled on device check box

    This indicates that the route is not activated. Location services are turned off on the device.
When you log into Oracle Field Service and try activating the route, you will see a warning message to enable location services first. Warning messages are as follows:
  • Browser:

    • Error Message:

      Route Activation requires your location.

    • Action:

      Enable location sharing on your device. Once enabled, refresh the browser page and “allow" location access when requested.

  • iOS app:

    • Error Message:

      Route Activation requires your location.

    • Action:

      Enable location access in your iOS settings.

      To enable location services, navigate to Device Settings, Privacy, Location Services

  • Android app:

    • Error Message:

      Route Activation requires your location.

    • Action:

      Click the Enable Now button to turn on location services.