vWork optimization has some advanced features.
This article includes
1. Selecting minimum workers or infinite workers
Infinite workers - This allows you to create an optimisation without knowing how many workers you need. You will be able to assign runs to workers once the optimization is complete (as shown below).
Minimum workers - This allows you to fill up your workers within the time given, so the optimization can be completed by the least about of runs / workers, However the runs will maximize the time window given.
2. Selecting worker and job capacity.
The capacity of a worker can be used as a volume or speed measure. This capacity relates to the optional capacity that you can set in a job.
We have more detail and examples of capacity on this page here.
3. Adding extra jobs to your completed optimization:
When you have completed an optimization, you can add additional jobs if needed. Just click the below button.
then select your additional jobs with the polygon selection tool-
4. Selecting different map view options:
You can enable or disable any of the below view options from the view settings on the bottom left of the page:
5. Viewing the duration and distance for your optimization:
When using the 'View' button to review your previously run optimizations, we list the total time for the route and total distance for the route as shown in the screenshot below.
6. Using optimization order and grouping for the same location:
There are two optional properties for assets that let you control the order that jobs are done in when jobs are at the same location. (for example deliveries to a large mall).
These properties can be added and are editable in the asset form, or through asset import.
The properties are "Optimization order" and "Optimization grouping".
The idea behind these two properties is jobs within the same "Optimization Grouping" will be ordered together according to their "Optimization Order".
I.e., if there are 3 jobs that should be done one after the other, you would give the same "Optimization Grouping" to the 3 jobs, and then values for the "Optimization Order" in the order they should be done.
For example, any time you have assets that are a multilevel building (say a big mall in Albany), I'd recommend you use it this way:
- Give all assets on level 1 the Optimization Order:
1 and Grouping:
- Give all assets on level 2 the Optimization Order:
2 and Grouping:
- Give all assets on level 3 the Optimization Order:
3 and Grouping:
All jobs generated for assets on level 1 should then all appear before jobs on level 2, and so on.
If you have two big malls they need to service in the same optimization, the different Groupings will keep them separate from each other.