Route Optimization FAQ
Route Optimization was introduced in X Dispatch 17.
Please read through and review this information before providing approval for the Technical Support department to enable Route Optimization on your system.
Common Questions
What is Route Optimization?
Route Optimization is a feature in X Dispatch that optimizes a route, or sequence of orders. In addition, Route Optimization provides ETAs for when the optimized work should be expected for completion by the driver. Currently the ETA is only visible to X Dispatch users only.
How much does it cost?
Currently, Route Optimization is offered as a free service. This may change with additional functionality and Route Optimization will have a different pricing structure. We will inform you before we begin billing.
What is the structure of Route Optimization and Re-Optimization execution?
There is no maximum amount of times Route Optimization can run.
First auto-optimization of each route will run 3 hours before the route's earliest stop. This is done so that the RO service does not become overloaded. Manual optimizations can be executed at any time.
Manual: From the Dispatch Board in X Dispatch right click on the driver or route you would like to optimize. Select "Optimize Sequence", then press the Optimize button.
Automated: To access the Route Optimization global settings found in Tools > Route Optimization. Here you can edit settings for automatic re-optimization for drivers (assigned orders) and posted orders.
What are the significant changes which queue automatic re-optimization?
For On Demand orders:
- Orders Added/Dispatched to driver
- Orders removed from driver (either by removing the driver, redispatching the order, or the order being canceled)
- Either Pickup or Destination address change (different lat lon for either address should trigger this as well)
- Change in any of the 4 time windows on an order
- Order Completed Early
- Order Completed Late
For assigned Routes:
- Stops Added or Removed from Manifest
- Moving a route stop from one route to another
- Address Change (different lat lon should trigger this as well)
- Change to the StopMin or StopMax time window
- Stop Completed Early
- Stop Completed Late
For X Dispatch 19.0 or newer, auto-optimization for routes will happen at stop completion or POD.
What to watch out for...
Please be aware of the following items.
Route Optimization:
- Route Optimization requires an active license for Geocoding
- Each stop/order must be geocoded. Stops/orders which are not geocoded will prevent a successful optimization result
- Does not currently take traffic into account
- If multiple "Start" or "End" stops are present on the route, the earliest "Start" and latest "End" stops are used (cannot optimize routes with more than one "Start" or "End" stop type)
- Frequency of the automatic re-optimization cannot be modified
- Cannot be paused or stopped for a period of time (the only way to stop Route Optimization from automatically running for specific drivers or routes is from the global options)
- Works best for distribution work in phase 1
- Drivers must have the option to "Sort by Itinerary" in Nextstop (other sort methods do not observe the sequence of the stops)
What's coming in the future...
We are actively expanding Route Optimization features. We will provide updates on our progress with each release of X Dispatch. On the agenda:
- Can support Routes with multiple "Start" or "End" Stops - these stops are moved to the top, or bottom of the route (respectively)
- Suggesting the best top 3 active drivers for an order
- Suggesting the best unassigned order for a driver
- Suggesting the best route (on same postdate) for a route stop
- Automatically selecting the top suggested driver for an order, and assigning the work to that driver
- Take all unassigned route stops, and determine if they can be placed on existing routes and still meet all time window criteria
- Determining the fewest number of routes that are required to complete all work within the time windows
- Suggesting route stops that could be moved from one route to another to increase efficiency
More Information
General rules or guidelines for how routes are optimized
Stops with an exact time have priority over stops that do not
The min/max times are always a large consideration when optimization occurs.
- A Load Stop will always be before stops that are dependent on that stop
- A Return Stop (not a return leg of an order) will be after stops that are dependent on that stop
- An order's pickup will NEVER be after the related order's delivery
- Route chaining is observed when optimizing routes (any stop that chains parcels from another stop will not be out of order in the chain)
- Any stop marked as Start will be prioritized over any other stop type
- Any stop marked as End will be prioritized lower than any other stop type
- IMPORTANT - The driver's current location should be used as the origin location when optimizing their stops. We do not want to begin a route on the east side of town if the driver is currently on the west side of town
- If there is no "Start" on a route, we use the driver's location to determine the starting point. The driver's location is always used when optimizing orders
Can I control who has access to Route Optimization?
Yes, there is a user permission.
Can I see the status of the last run of Route Optimization?
Yes. From the Dispatch Board in X Dispatch right click the driver or route, then select "Optimization Status".
Is this Route Optimization compatible with MapPoint?
Yes. Routes that are re-sequenced will display the new optimized sequence in MapPoint.
Can I temporarily override the Route Optimization global settings for a route?
Yes. From the Dispatch Board in X Dispatch right click on the driver or route and select "Optimize Sequence". Then select "Edit" and "Override global settings.
Where can I find out how to use Route Optimization?
Learn more:
CXT Support Site Route Optimization
CXT Technical Support: (602) 265-0195 opt 3 or create a support ticket.
What do I need to get started?
Contact CXT support or your account manager to obtain a Route Optimization Service URL.