The manager sees not just the task fulfillment but the fact that maintenance works are about to start or already being executed. Consider the example:
Let's compare the process with something familiar.
- Let's say, we have the "Oil change" Service scheduled for December 14.
- We set up Fleet Run in such a way that on December 12, Service is assigned to the specified unit and gets to the "Due" Services so we could have enough time to plan it out.
- When the fleet manager sees a new Service, they understand that the vehicle will undergo the oil change in two days. They need to call the service station, sign up the vehicle, and let the driver know.
- December 14 is the oil change day. Having made sure the right vehicle is at the service station, the manager changes the Service status to "In progress."
- The driver calls the fleet manager to inform them everything is done. The manager changes the status to "Closed." The "Oil change" Service which costs $50 gets into the archive to be displayed later in reports and statistics.
assignment in the Fleet Run is like the registration of works in the fleet manager's register. The manager doesn't breathe down the mechanic's neck, they just call to make sure: the vehicle is at the service station, the mechanic follows the work plan, and uses the right spare parts. In the end, the manager gets to know the result: the mechanic examines the vehicle and either gets the job done and issues an invoice or says the repair is not needed, in other words – rejects the Service
. One more important option:
you can attach a file to the Service
. For example, if a mechanic or driver sends you a picture from the service station or document scans, you attach them to the Service
for this vehicle and can view them at any time.
You can create the Service
manually or set up an automated activation with the help of Intervals