Explanation of how driver work/rest times are calculated in both modules and what could cause data differences.

Information needed in order to perform the task (plus who needs to provide it)

link all the apps needed in order to perform the task

Here is an example of how data could look when there are some issues with driver detection. Open the Driving times module and generate the Driver's working time report for the requested driver:

And here is the reasoning - for driver card removal:

DRIVING activity is the last one found when generating a report, this is why there is no time point at which we should stop calculating driving hours. So, in the report, the last driving activity was calculated to be finished at midnight. When the driver's assignation is removed before the driver finished his DRIVING activity.

The report is sensitive to driver card removals, and driver id loss issues.

For such cases we have a note in the report for a reason: The following data was calculated using only K-Line data because the .ddd file was not available. For this reason, the data may be inaccurate

When driver cards are removed such cases could occur often. The recommendation would be to generate a report while the driver card file is already downloaded.

Despite losing the driver id, when the driver state changes in the driving times module it is understood as state changes for the last driver, thus the difference between the two results.

*Accurate data is dedicated to drivers with TACHO data and Tacho states. When data is calculated from K-line data, there you can see some inaccuracies until the driver card is downloaded.