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.

Results:

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.
Note: Despite the policy chosen, bulk routing is always observing SLA start and will not allow activity assignment before SLA start with the only exception of activities assigned manually before routing run with such a violation.