Overview
Hours of service is a way to track the hours that a driver is working and inform/alert the driver, dispatchers, and compliance responsible individuals when those hours are nearing or violating configured thresholds. These thresholds are flexible and can be based on ELD mandates, union contracts, state laws, etc.
HOS Data Source
HOS calculations can be based on either ELD (Electronic Logging Device) or Time Clock data. The rules evaluation is identical and irrelevant of the source of the data. The mapping from ELD is direct and the relevant times are On Duty, Off Duty, and Driving . For Time Clock, the times that are relevant are Clock In, Clock Out, Break Start, and Break End. Additionally, Time Clock has no differentiation between driving and not driving, so driving based rules and violations do not apply to Time Clock sourced data and will not be shown on the UI.
Data Source Differences
- The displayed name for some of the HOS statuses are different (Timeclock vs ELD)
- Clocked In vs On Duty
- Clocked Out vs Off Duty
- On Break vs N/A
- Time Clock doesn’t have the concept of driving so all driving related violations are removed as options.
- On Break is unique to Time Clock and can be configured as being either On Duty or Off Duty
HOS Profile
The HOS profile allows you to define the violations, how to evaluate them and who they apply to. They can be configured in the settings page.
Settings --> Client Management --> HOS Profiles
Note: Profiles cannot be deleted while there are still users assigned to the profile.
Profile to User Association
If User Classes are enabled (Business Entity configuration) then there is an option of associating an HOS profile to a User Class and therefore all users in that class. This association can be overwritten for a specific user. The association can also be configured from either the HOS Profile edit modal or the User edit modal in user settings.
If there are no User Classes then the mapping from HOS profile to user is user specific and must be set individually, there is no client-wide default.
Violations Daily Limits and Cycle Limits
There are two types of windows or periods of violation rule evaluation, Daily and Cycle. Both work in the same basic way, which is that a user is allowed a certain amount of work within a window and must be off duty/not working in order to reset the window. Resetting the window means that all accumulated working hours are effectively set back down to zero and a new window starting with no accumulated time can begin.
Daily Limits
A daily window in general terms means a single day of work. A simple configuration for a daily window might be that a user is allowed to work up to 12 hours and to get to the next day must be off duty for at least 8 consecutive hours. This is not a calendar day because a user’s day may cross the midnight threshold. For example, if a driver is working an overnight pour, they can’t work 24 hours straight from noon to noon just because they worked past midnight, they’re still bound by a 12 hour work day.
Breaks: For an ELD Data Source profile, On Duty Not Driving, Off Duty and Sleeper Berth are all considered break types for the daily window. For a Time Clock Data Source profile, Break time can be selected as off duty.
Cycle Limits
A cycle window is generally considered a work week (although it’s not necessarily 7 days). A typical configuration might be that a user could work up to 60 hours in a cycle and must take a 36 consecutive hour break to reset the window.
Violation Rules
Below are the possible violation types. For every violation type, the HOS profile can be configured with a hours violation and warning, to trigger notifications when exceeding and nearing the violation.
Daily Violations
- Driving Time (ELD only, ELD differentiates between On Duty Driving and On Duty Not Driving)
- With the ability to extend based on small breaks (refer to "On Duty And Driving Time Extensions” for details)
- On Duty
- Consecutive Drive Time (ELD only)
- With minimum break time to split consecutive driving time (5 minutes of on duty not driving between two 6 hour driving times generally counts as 12:05 of driving time, but a 30 minute not driving time allows the split to two separate 6 hour driving times that are permitted). The Min Break Duration is configurable for Consecutive Drive Time.
Cycle Violation
- Cycle On Duty
HOS Evaluation Changes
The HOS logic does support the idea of making changes to the historical record. For an ELD data source, you can either make a change to an existing record or add a new one, there is no delete. For a Time Clock data source, you can also delete.
In either case, the system will look back at the HOS cycle at the time and adjust the entries based on the change. This also means that cycle periods, daily periods, and violations will get adjusted. This can result in:
- new violations being created - making it possible to get notified of a violation happening several days ago
- existing violations to have their severity changed or even resolved - resolved violations will still be displayed.
Notifications
HOS Warnings & Violations
Settings --> Alerts --> Select HOS Warnings & Violations for Type
- This alert must be associated to 1 or more HOS profiles to trigger.
- The alert can be configured to notify at the warning and/or violation level or any of the violation types.
- Driver notifications, realtime notifications, and scheduled notifications are also available.
User Experience
DigiTrack
An "HOS" button will be available on the drivers Menu and will provide the driver with their HOS data
WebApp
There are two main pages for HOS on the webapp, current cycle summary with the ability to drill down to a user specific cycle summary and details.
Cycle Summary
Warning And Violation Stats provides a full summary of all users that have an HOS profile. The filters do not apply. Each chart shows the percentage/number of users that are either in Good Standing, Approaching Limit (crossed the warning hours setting), or In Violation for each possible type of violation. Clicking on any of the links, or anywhere on each chart, will explicitly set the violation based filters. They will not affect filters currently selected for non violation based filters.
Users provides a list of all users and they’re current summary. This list is directly affected by the page filters. The violation columns are {accumulated hours}/{violation hours} and will show an appropriate icon if a violation/warning is currently applicable.
Driver Detail
Current Cycle Stats will have one chart per violation. When in good standing or approaching limit the darker color is the accumulated time and it will keep increasing until crossing over into a violation. However, once a violation has occurred the darker color is the accumulated time past violation. In the screen capture below, Daily Driving is in red (violation).
Current Cycle Stats off duty charts are a little different. The darker color is how much time is remaining until the window break period is reached and will effectively be counting down. These charts will also never be red, they will change from yellow for not having reached the break limit to green after reaching it.
Login Based Cycle Counts are one row per daily window in the current cycle. Off Duty/Reset is the amount of off duty time accumulated until the next window, or in the case of the current daily window the currently accumulated off duty time.
Clicking into details for the daily window will display a Duty Status graph, list of tickets worked during that daily window, ELD header information, and a list of ELD records for that daily window.
WebApp Map
When a driver has HOS enabled and is logged into a truck, their HOS details will be displayed in the Truck slide-out and Truck status slide-out.
Comments
0 comments
Article is closed for comments.