GoTacho shows the whole fleet at once: whether driver cards and tachograph data are downloaded on time, when the calibration expires, who drove the vehicle and whether there are any driving and rest time violations. Everything is read from the tachograph files themselves.
Tachograph data has to be downloaded regularly: the driver card - at least once every 28 days, the device memory - once every 90 days. The operator is responsible for this, and a failure usually comes to light on the road.
We built GoTacho. It shows where things stand in advance and for the whole fleet at once, and opens in Wialon from the Apps menu - nothing needs to be installed.
Vehicle numbers, VINs, driver names and card numbers are fictional, any resemblance is coincidental.
One row is one vehicle. When the card and the device data were last downloaded, how often that has to be done, the next calibration date and the nearest deadline. Green, yellow and red show where everything is fine, where a deadline is approaching and where it has already passed.
Above the table one line says the main thing: how many vehicles need attention and what exactly is missing.
The worst part is what the file dates do not show. If a download breaks off, a fresh file lands in storage every time, but with old data inside.
During a check we found two vehicles where the file was dated yesterday and the data inside was three months old.
Formally the download was running. In fact there had been none for three months.
The application compares the date of the file with the date of the data inside and marks such vehicles separately.
The failed attempts themselves are visible too: a tachograph file noticeably smaller than the others on that vehicle is marked «incomplete». One such file is chance. If there are two or more, the vehicle appears in the «Need attention» line: downloads are breaking off regularly.
The next calibration date is written by the workshop into the tachograph memory. The application reads it from there, so it does not depend on what was entered into the records by hand and when.
At the very first comparison, in a fleet of thirteen vehicles three had a recorded date that differed from the one stored in the device.
These records are not on the driver card - the device keeps them itself. A common story: the vehicle was moved, the card was not inserted, off it went. The owner is responsible for such cases and is usually the last to learn about them.
Next to the number of cases you see the dates of the latest ones, the duration of each and the top speed. Duration matters more than the count here: three minutes without a card most likely means the vehicle was moved around the yard, thirty-five means a trip.
The device keeps other records as well: power interruptions, sensor errors, card authentication failures. The application names them in words rather than codes. But the name says what the device recorded, not why: the same code comes from a faulty card and from workshop work alike. It is a reason to check, not a conclusion.
The tachograph records every card insertion and withdrawal: the driver's name, the time and the odometer reading. This builds up the history of the vehicle - who worked on it and when, how many kilometres each driver covered.
The device memory holds about three months of such records, after which older ones are overwritten. But every downloaded file is a snapshot of that memory on the day of the download, and older files still hold what the device has already forgotten. The application reads several files downloaded at different times and assembles a history going back a year and more.
If the driver never takes the card out of the slot, and on long hauls that is what happens, the stint has no end - the application shows «card still in the slot» and takes the distance from the daily odometer readings.
From the card data the application checks daily and continuous driving, daily rest, the weekly fifty-six and ninety hours and weekly rest. A shift is counted between rest periods rather than by calendar days - otherwise six hours before midnight and six after would look like two quiet days.
Crew work is handled separately: a crew has its own limits, and a lawful schedule is not marked as a violation.
Each week is shown as a picture: seven days one under another, with colour showing what the driver was doing at each hour. Under the week are its own violations, with the date, the time and a description.
Any day can be expanded into a detailed strip.
We count cautiously. If there is a gap in the data, the application will not claim that a violation took place: it may hide a violation, but it will not show one that did not happen.
Only the enforcement authority gives a binding assessment of compliance, and its conclusions may differ from ours.
By vehicle: device, calibration, driving without a card and speed exceedances. By driver: what period the data covers, how many hours behind the wheel and how many violations of each kind.
The «Manual» button on the top bar. It also says what the application does not do and what should not be relied on without checking. The application and the manual are translated into Estonian, Russian, English and Finnish.
We have opened a demonstration page with a fictional fleet. Everything is clickable except the files themselves: they are not there, the fleet is invented from start to finish.
The application reads files that are downloaded from the tachograph remotely. So the vehicle needs equipment that can download them, and not every device can.
If remote downloading is already set up for you, nothing needs to be done on the vehicles: we connect it on our side.
If it is not set up, we will look at what is installed on the vehicles. Some devices can be fitted with a module, some need replacing - it depends on the model and the year.
If you are not our customer yet, we start the same way: send us the list of vehicles and devices and we will tell you where the application will work on the existing equipment and where a replacement is needed.
Write to info@gogps.ee or call +372 56 888 112.