The Job Monitor runs automatically, tracking the real-time workings of field staff and comparing it to your scheduled jobs in order to track the status of those jobs. The Job Monitor deduces when your drivers arrive at and when they complete jobs based on the known movements of the vehicles to which your drivers are assigned.
The Job Monitor does not support location processing of vehicles shared using Verizon Connect Share.
If Driver Initiated Status is enabled in the Verizon Connect® WorkPlan™ mobile application, the Job Monitor will not automatically set job statuses. It will instead expect job status to be set manually by the user of the mobile device.
This topic describes, in detail, how the Job Monitor determines when job-related events occur.
Some of the inferences made by the Job Monitor can be influenced by options you select in the Settings dialog box.
A driver is considered to arrive at a job when the vehicle moves within the radius of the job site within the scheduled arrival time window (the earliest and latest arrival times for the job) plus or minus a threshold. The threshold on either side of the time window is specified by setting the Job Arrival Allowance on the Job Settings page. This threshold allows jobs to be detected as early or late.
A vehicle is not considered to have arrived at a job site unless one of the following occurs:
- The ignition was turned off while the vehicle was stopped at the job site.
- The vehicle did not depart the job until the planned time on site had elapsed.
- The vehicle spent at least 10 minutes idling at the job site.
Time on Site
At its simplest, the time on site is the time from when a vehicle arrives at the job site until the vehicle departs the job site. This might be difficult to determine, however, when there are overlapping jobs (multiple job sites in close proximity to each other such that a vehicle might be within the radius of more than one job site at the same time). To enforce the rule that a vehicle is only on-site at one job at a time, time spent in overlapping jobs is redistributed when a route is completed, based on the relative sizes of each job's actual time on site. In general, jobs are ordered by actual arrival time, and in the case of "ties", by planned arrival time.
The previous job is the last job that the driver completed. The current job is the first incomplete job in the scheduled route after the previous job. Any job that is completed before a job scheduled for earlier in the route will be considered to have been completed in the wrong order. For example, if a driver skips a job and then returns to it later in the day and completes it, that job will be marked “Wrong Order” (because the order the driver is completing the jobs in went backwards at some stage). It is assumed that the driver will continue on the route from the current job forward, and that any skipped jobs will be left incomplete.
There are a number of places in the Verizon Connect® Response™ UI where an estimated time of arrival is shown for a job. These estimates are only calculated for jobs where the driver has an assigned vehicle.
In the Dispatch Job dialog box, this estimate is based on the assumption that the driver departs the current job at the planned time or, if there is no current job, that the driver departs for the new job immediately. This does not take into account any other jobs already scheduled on the driver's route, which might precede the job being assigned. As a result, the ETA that appears once the job has been dispatched might differ from the value shown when you dispatch the job.
The ETA is always calculated assuming that the driver follows the scheduled route, in order, from the current job onward. This means that if a job has been skipped, the estimates for arrival at the rest of the jobs on the route assume that the driver will not go back to complete the skipped job.
Route Start and Completion
Typically, a route is considered to start when a vehicle leaves the initial depot (base location). If there are not reports indicating the vehicle has departed a depot, the route is considered to start when the vehicle arrives at the first job.
A route is considered to be "In Progress" when an arrival at any job site on the route is detected.
A route is considered complete when the last job (return to depot) is completed, the planned time for the entire route has elapsed, and one of the following holds true:
- The vehicle has stopped at the depot (ignition off).
- The vehicle has idled longer than the planned time on site.
When a route is completed, it is no longer monitored. Any jobs with a status are marked as complete and any jobs with a status of en-route are marked as assigned.
If a vehicle starts a new route (arrives at a job of the new route), without arriving at the last job of the current route, or if the scheduled time for the route plus a threshold amount has elapsed, the current route gets a status of Not Complete, and the new route becomes the current route.