When the onboard computer or unit in the asset loses communication, because of say for instance poor communication as a result of lost signal, the last status a driver was in will be set to the assumed duty status until the unit communicates with the system again. The system thus assumes a duty status until the unit comes into range again.
Say for instance a driver was driving in a area with poor communication signal and the unit stopped sending information for a period of 4 hours. The system will assume that the driver is still driving for those 4 hours and display it as such in MiX Fleet Manager with a blue line on the HOS timeline. As soon as the driver comes back into an area that allows the unit to send the correct information, the correct HOS data will be displayed in the system. This means that if the driver drove for only 2 hours, stopped for an hour and drove another hour the correct information will now be indicated on the HOS and driver timelines and automatically updated as soon as the unit is communicating again.
The assumed data will be displayed on the timeline as follows:
You can choose if the system must make use of assumed data when triggering violations and notifications by setting the available hours calculation settings in database administration.