Driver Activity | Hours of Service

There are several upcoming requirements from established Fleet Management companies , who are to comply by Driver safety rules

Hi Pach,
Thanks for reverting...
As far as the available solution concern there are various companies providing this kind of solution.

But the main problem is if we do not want to get tied up with specific hardware devices or any ELD solutions we cannot achieve custom Hours of Service using Wialon at all.

I suggest if Gurtam can add flexibility to have/ configure desired rules for HoS which includes only a few basic fields into the Wialon application, same as what we do in Eco-Driving where we have the flexibility to define our own parameters, so this will help in all the way and save lots of hardware cost.

Please find attached image for fields which will be required:

Please reconsider my point.

Thank you.

We have to have greater flexibility in setting the parameters for driver hours logging and reporting as using the current standard in Wialon is not suitable for our market so it is a wasted function for us. Giving us greater control over how the hours are captured, reported and alerted is a must. Many of the lower end system have this capability already.

One size does not fit all in this situation.

Hi all,

that's an interesting topic that you have raised here and quite a debatable one.

Taking into account that regulations on the driver activity are mostly region-specific, I envision manual setting of these regulations by users themselves to be a more rounded solution than trying to embrace all possible regions in terms of what regulations each of them has and hardcode them in the system.

However, such a customization has another side and it lies in its complexity in terms of development and further maintenance. So we want to be very careful with adding an ability to set up the rules of driver activity to the product and make sure that it brings benefits.

In the nearest time we do not have plans to make any enhancements to this functionality, but I have noted down this request to our collection of all partners request. Let's stay tuned.

Hello

I have been asking this for very log time. I think it would be better for the first time to know how A+A Security is doing it. I found their reports very interesting.
https://gurtam.com/en/blog/wialon-lafargeholcim-az

Hello mars, how are you?
Yesterday we visited a prospect that have the same needs of others we meet before: controlling the working hours based on the law.
Here in Brazil it is based on Lei Nº 13.103, 03/02/2015.

Problem:
So as other partners and I said before, the problem is to calculate properly the working hours, extra hours, meal time, parkings, loads, unloads...

Solution:
What I purpose: Creating a new app only for this case or report inside Wialon, where the we could set lot of filters to control every situation.
Note: This solution would be useful for many partners and not just for us, since everyone could use a single source of information!!!
The problem could be simple solved using geofences/group of geofences or sensors, trip detection and two types of reports.

Calculation:
The start of the working day would be set with the first trip;
The end ot the working day would be set with the end of the last trip;
The duration of working hours would be calculated with the desired formula, for example here in Brazil: Start - End - (Lunch Time - Parkings - Load/Unload/Oversight Time) During the interval
Extra hours would be calculated by exceeding the maximum working day hours;
The meal time would be calculated by the parking time inside Meal geofences/sensor;
The Load/Unload time would be calculated by the time inside Load/Unload/Oversight geofences/sensor;
The duration of rest would be calculated with the desired formula, for example here in Brazil: Interval - working hours - Load/Unload/Oversight Time
Rest between days would be calculated as the difference between the next day start working day and previously day working day end.

Filters:
Working hours: min and max;
Extra hours: day max and week max;
Meal: min and max, intervals - hh:mm to hh:mm;
Night hours: hh:mm to hh:mm;
Continuous driving without stop: max time of driving, min time of stop;
Time between working days: min.

Lunch and Load/Unload Detection:
Selecting the Meal method: geofences/group or digital sensor;
Selecting the Load/Unload/Oversight method: geofences/group or digital sensor.

Notifications/Events:
Min and Max meal duration exceeded;
Extra hours when drivers do;
Exceeding extra hours by day/week;
Min rest duration exceeded;
Min rest between days exceeded;
Continuous driving without stop;
Min stop time not done, when driver have worked for 5 hours without a stop of at least 30 minutes.

Reports:
01) One would basecally bring all these informations of durations:
driver    /start*    /end*    /Durat. - Working Hours    /extra    /night    /meal*    /load-oversight    /rest    /btwn day
*Would have the locations too.

02) The other would bring the events, for example:
driver    /    time        /    event
John    /    20:55    /    Extra hours
Crys    /    14:00    /    Meal %min duration%
Fer    /    15:05    /    Continuous driving without stop

Load/Unload/Oversight Time is called "wait time" here, and its paid differently.
Why Geofences? I believe that using geofences is the best way to automatizate without using any sensors. E.g.: if the vehicle is in this place, is because the driver is having a lunch. The manager create the geofences, group them by function: meal or "wait time", and the platform knows what to consider.

---

Today we already have this feature in the other platform we use, but the calculation is done by an mobile app with macros, I'm sending some screenshots. It actually doesn't work very well because depends on the driver using the app properly, but when used it works very well.

We already have many clients and prospects that asked us for this type of management, so I really think this would have great potential for Wialon, for every partner.

Probably there are some points that I've missed, different points of view, so I hope that other partners share their opinions.

Thank you!!!

Hello mars, thank you for the answer, I'll be happy to help wherever I can!!! And actually, I do believe too that creating an app/module would be the right thing to do.