When you optimize a route in ServiceCore, the locations, appointment times, service durations, and distance information are calculated together automatically to return a new version of the route stops in optimal order.
Most times this goes off without a hitch. When route optimizations go wrong, we'll let you know by displaying an on-screen message telling you what part of the route is causing the issue so you can take steps to resolve the problem.
In this article you'll see a glossary of the error messages you may see when route optimization fails. We've also included steps to resolve each issue.
Before You Start
Here are a few things to keep in mind before you optimize a route:
- Route optimization requires there to be three or more stops on the route which can include any combination of destinations and jobs
- All locations on the route must have valid Latitude and Longitude
- For information on how to create jobs and destinations with valid Latitude and Longitude, please review these help articles:
- When using any of the schedule views to optimize a route (Week, Day, List, Map, Directions) you will need to click on "Refresh Schedule" in order to see the newly optimized order of stops
What constraints are used during route optimization?
Route optimization takes into account the follow pieces of information every time you click "Optimize Day" for a route from the Schedule:
- Departure Time
- Departure Location
- Travel time between each stop
- Service duration of each job and destination
- Appointment times (access hours) of each job
- End location
- Traffic (based on the average traffic for that day and area for the past two years)
Why is this so special?
Here are a couple scenarios to describe how route optimization works smarter and harder for you, and when optimization will work or fail:
When Route Optimization Will Work | When Route Optimization Will Fail |
---|---|
The new route optimization will put stops in an optimal order. For example, if you have a combination of jobs and destinations like this:
|
Also, the new route optimization will let you know when you won't make it to a job on the route in time. For example:
|
FAQs
When creating a job, if the "Time Window" is 8AM - 9AM, and the duration is set to 3 hours, what will happen?
In this case, routing will fail. That's because a 3 hour job cannot be started and finished in a 1 hour time window. Optimization will fail when the service duration is greater than the time window.
To prevent route optimization from failing, edit the job to only set a “Start” time of 8AM for the “Time Window” and leave the “End” time empty. Then, route optimization will work because it will route the driver to the job site by 9AM to do a 3 hour job.
If a pick-up job has a time window of 1:00PM - 2:00PM and the job takes 15 minutes to compete, what will happen?
In this case, route optimization will work. That's because the time window is greater than the job duration.
Glossary of Route Optimization Error Messages
In the examples below:
- "S123" is an example name of a Site
- "Springfield Landfill" is an example name of a Destination
- "J123" is an example Job Number
- "John S." is an example User Name
Error Message | Definition and Steps to Resolve |
---|---|
Could not parse a latitude/longitude from site S123 | One of the job site locations on the route has invalid Latitude or Longitude GPS coordinates. To fix this, follow these steps:
|
Could not parse a latitude/longitude from destination Springfield Landfill | One of the destinations on the route has invalid Latitude or Longitude GPS coordinates. To fix this, follow these steps:
|
Optimization failed. You must provide at least 3 destinations | Your route only has one or two stops. Three or more stops are required to optimize a route. To fix this, follow these steps:
|
Optimization failed for John S. on Jan 1, 2022. The route contains an invalid combination of times and durations for J123, Springfield Landfill. | Route optimization may have failed for the following reasons:
Important Notes:
|
Other Error Messages Not Listed Above | If you encounter an error that isn't listed above, please submit a support request for ServiceCore to assist you. |