Currently, our drivers are switching their rulesets between "No Ruleset (8 days)" and "USA Property 70-hour/8-day" rulesets. This switching is meant to account for when drivers are operating non-regulated vehicles (under 10,001 lbs) versus regulated vehicles. However, even when they switch between these rulesets, only on duty and drive time is still recorded under the "No Ruleset" category, which creates issues with the accurate recording of regulated driving time for Hours of Service (HOS) compliance.
Just to clarify, drive time does not need to be recorded for non-regulated vehicles (those under 10,001 lbs), but on-duty/off-duty times must still be tracked. For example, if a driver is in an F-250 (a non-regulated vehicle) without a trailer attached, logged into Geotab, their driving time is still recorded even though it doesn't need to be. When the driver hooks up a trailer and switches to the "70-hour/8-day" ruleset, their drive time should begin recording correctly, but the software is combining the non-regulated vehicle drive time with the regulated one, leading to inaccurate data. This discrepancy could result in potential violations if the driver is stopped by a regulatory authority, as it might show an incorrect total driving time that could trigger penalties or cause the driver to be put out of service.
The only other solution we've considered is for drivers not to log into Geotab when driving unregulated vehicles. However, we'd like to avoid this because we want to maintain full visibility over who is driving which vehicle, track dangerous driving behaviors, monitor total drive time across the company, and integrate with other third-party systems that rely on this driver data.
I was hoping to find a solution that might look at a vehicles group (which our non-regulated vehicles are all in a separate group from our regulated vehicles) and use this to determine or keep drive time from hitting a driver's logs. This would also change if a trailer was attached to a vehicle, and could maybe switch a driver automatically to the proper ruleset based on predetermined settings. I may be talking about something that has to be an integration on our part, so I am curious something like this may be possible through the geotab api or creating a rule in geotab itself?