By and large you got the point. We would like to separate intervalls in the existing reports (trips, engine hours, geofences and perhaps others) when the drivers and/or the trailers changed.
Actually we are focusing on construction machines, tractors and other agro machines, so transportation is not in the spot at our side.
Mainly we are using codepads (see attached picture) for driver/trailer identification (but of course there are other versions such as iButtons, RFID tags).
"cargo transportation during which there are 2 drivers in the car throughout the whole time and they change at short stops, then it is logical to display one common interval of the trip and two drivers" So even, we are not in cargo bussiness..., but I'm pretty sure that endusers would like to know not only the "common" mileages and times but the separate ones, too. (Performance monitoring)
In our focus the most important thing would be the geofences report.
Our projects bigger picture: the units (tractors, construction machines, agro machines) are working on 50+ zones/areas (let's call them geofences). When they have to then they are working continously 7/24. The units doesn't stop (no ignition change, no other digital sign change) exept: there is a new driver or a new trailer. Some times the new driver/trailer comes inside a geofence sometimes the change is outside.
Sure there are some LEGO methods, as you wrote: "recommend you to use filtering by driver with extraction intervals. In this case, you need to create several tables, but your case will be covered"In an avarege account (20units, 50+ geofences, 50+ drivers, 50+trailers) building the reports what you have mentioned..well, it is possible, but not realistic (even we have to do it..unfortunately).
Also we are "hacking" the engine hours/trips riports this way:We are making some extra (digital) sensors:"Driver change" & "Trailer change".
With the "Expressions" function we are checking if there is a change in the driver(trailer) parameters.
driver_param - #driver_param //if it is zero then it was no change, if it is not zero, the there was a change.
It is calibrated the following way: if there was no change then the sensor's value will be "1" and "0" if there was a change. (so it is invers)
And there is only one step forward: we have to validate the igniton sensor with multiplying this "Driver change sensor". (If there was a change then it is multiplyed with "0") Voilá there are new lines in engine hours and trips reports when the driver(trailer) changed...
Unfortunately this doesn't work for the geofences reports. It's so sad.
I write this down to show that we are quite creative to solve the situations...but WHY on earth is this hacking needed..
In a global view adding two checkbox to the reports' "Intervals Filtration" section could solve all our needs:
☑Generate new line when driver change
☑Generate new line when trailer change
And making these codes for each reports won't be a too big project. Due the checkbox the users could use the reports both the old and the new way.
But the "new" would be better
Let me know if you have any questions! And thank you for your interest in our needs!!!
Eflotta Vehicle Tracking Ltd, Hungarywww.eflotta.com