Route optimisation can get complex when you consider all of the variables passed across to the optimisation servers -
- Individual worker hours vs the job time windows allowed.
- Utilization of the worker (ie if they already have jobs booked)
- Length of the jobs vs hours in the day for the worker (or the workers shift hours).
- Geographic location of the jobs and travel time.
- Capacity setting of the worker vs capacity required for the jobs.
- Previously assigned jobs outside of the optimisation job selection that still have to be completed in the optimisation timeframe (so we need to allow for these).
- Having to respect some jobs with a planned start time (if you forget to set to ignore these).
Don't worry, we will be building smart error messages soon, so we can tell you the problem.
Below are the recommended things to check when you have a failed optimisation, if these still provide no help, please email firstname.lastname@example.org.
1. Check workers' hours vs the time windows on the job/jobs. Also check your company working hours vs time windows. Or the specific worker's shift hours, if their shift ends we may not be able to assign all jobs as the time required to complete these may go beyond the end of the worker's shift.
2. Check the jobs are not in any current open or pending optimisation. Jobs will not show on the optimisation map if they are already in use in another optimisation.
3. Check the jobs have only one geocoded step, this is a current limitation of our optimisation. (more than one geo address per job).
4. Check the worker has the capacity (they do not have other jobs booked for this time)
5. Check the worker does not have other jobs in the timeframe that you cannot see, we will have to optimize around these, sometimes making the route look strange or non-optimal.
6. Check the duration of the jobs does not exceed the available hours in the run (ie 9 x 1 hour jobs will fail if allocated to an 8 hour worker shift)
7. If it takes 5 hours to drive between 2 jobs in an optimisation, yet the driver is only allocated 4 hours in the time window, or is on a short shift on that day, the optimization will fail.
What if my route does not make sense (sends the driver all across town)?
- Check the Start times for the jobs in the Optimisation. If some jobs have set start times set, and you don't select the "ignore planned start times" setting, the optimisation will include these start times and do its best to route all the other jobs around these static start time jobs.
- Check the driver does not have one or 2 jobs already assigned in the time frame, vWork will still send the driver to these other jobs, yet you cannot see these 'outside jobs' as they are not in your optimisation job selection.
- Check the Time Windows set for the Jobs in the Optimisation against the Duration of the Jobs. vWork will not assign more jobs to a Time Window than can be completed in that time window.