Verizon Connect® Dispatch™ is used in two ways: firstly to fine tune routes generated by Verizon Connect® Scenarios™ based on recurring job, shift, shift pattern, vehicle configuration, and other values specified in the enterprise fleet maintenance platform; and secondly to create jobs and routes itself for the next week and then fine tune these jobs and routes. Typically, this fine tuning takes place only days before routes are scheduled. Scenarios calculates the most efficient routes and estimated arrival times for each stop that drivers need to make days, weeks or even months in advance and at a very high level, often for entire regions or cities encompassing many depots and customers.
Routes generated well in advance for any given day by Scenarios are created using the best information available at the time, but will often need to be refined to account for changes to local conditions. This 'next day' planning model is helpful when dealing with unpredictable events, such as:
- Road closures, construction or natural disasters that can impact traffic flow.
- Unavailable drivers - sickness, holiday, leave, over maximum shift length, and so on.
- Unavailable vehicles - mechanical breakdowns, maintenance, accidents, theft, compliance requirements, and so on.
- Changed customer orders - for example, last-minute changes to quantities, time windows.
- Emergency or one-off deliveries.
- Follow-up deliveries - jobs that couldn't be completed previously for any reason.
- Short or incomplete deliveries from previous shifts - jobs missed from the day before, for example.
To adjust for constantly shifting conditions, depot managers and route planners will typically use Dispatch to:
- Review routes and jobs for a given day.
- Edit route details, including drivers, shifts and vehicles.
- Assign and re-assign jobs to routes, or move jobs between routes.
- Add new jobs and remove jobs that are no longer required.
In this help guide you can find detailed descriptions of the core tasks you can perform with Dispatch, such as managing routes and jobs, assigning jobs to driven routes, modifying the number or order of jobs in a route, and copying jobs directly from one route to another. These tasks are organized into logical groups for each feature.