The following abbreviations are used for duty statuses throughout the application, including the graph grid:
The following abbreviations are used to distinguish among various special activities while in off duty status. These activities all display as OFF (Line 1) on the graph grid, but with a corresponding annotation in the remarks section of the log:
This indicates that the driver is waiting at a natural gas or oil well site. Per United States HOS regulations, specially trained drivers of commercial motor vehicles that are specially constructed to service oil wells may record such time as off duty.
This indicates that the driver is resting in other sleeping accommodations (other than the vehicle's sleeper berth) at a natural gas or oil well location. Per United States HOS regulations, a specially trained driver who operates a CMV specially constructed to service natural gas or oil wells may record such time as off duty.
For ELD compliant devices, the following abbreviations are used for special driving conditions throughout the application:
This indicates that the driver is relieved from work and all responsibility for performing work and is operating the vehicle strictly for personal use. When used from an ELD compliant device, the vehicle can be moved without triggering driving periods. This event should always start at the same time as (or be contained within) an off duty event.
This indicates that the vehicle can be moved about the yard without triggering driving periods. This event should always start at the same time as (or be contained within) an On-Duty, Not Driving (ON) event.
This indicates that the previous PC or YM event has ended and the special driving condition has cleared.
A rule set is a way of identifying which HOS rules apply to a driver based on the locality in which the driver operates, the type of freight carried or vehicle driven, and the cycle within which the driver operates. When a driver operates a commercial vehicle but is not subject to hours of service regulations and not required to use an ELD to record RODS (i.e., is ELD EXEMPT), the rule set also identifies ELD EXEMPT settings (e.g., enabling the Rest Break option on the mobile to indicate OFF and ON status changes when taking breaks (e.g., lunch break)).
For example, a rule set of "US 7-day property-carrying" describes a set of rules for drivers operating in US interstate commerce, transporting non-hazardous freight, for a motor carrier that does not operate vehicles every day of the week. "US 8-day passenger-carrying" describes a set of rules for drivers operating in US interstate commerce, operating a bus or motorcoach, for a motor carrier that operates vehicles every day of the week.
Drivers operating under Canada South of 60 jurisdiction have the option to defer up to 2 hours of their required daily off duty time to the next day. Deferring off duty time allows drivers to decrease the total required daily off duty time for the initial day (Day 1), and add that amount to the off duty time that must be taken on the following day (Day 2). Day 1 and Day 2 deferral events can be edited or deleted by the driver on the mobile device and driver portal.
A driver may only indicate deferral while logged into the mobile logging device. The driver is responsible for any HOS violations incurred during the deferral process. Other conditions for indicating deferral include:
An exception is an exceptional circumstance in which a driver is permitted per HOS regulations to extend the maximum driving time.
The driver must attest that all conditions for claiming this exception have been met. This exception may not be combined with the Adverse Conditions exception.
The adverse conditions must have been unknown at the time the trip was started, and the trip must have been possible to complete within the driver's regular work shift under normal driving conditions. This exception may not be combined with the 16 Hour exception.
It must have been possible for the driver to complete the trip in accordance with applicable hours of service limits if there had not been an emergency.
The driver must not drive after the 14th hour after coming on duty on 5 days of any period of 7 consecutive days, and must not drive after the 16th hour after coming on duty on 2 days of any period of 7 consecutive days.
The driver must attest that all conditions for claiming this exception have been met. Use the annotation to document the specific reason that the driver is exempt from the rest break requirement.
An annotation is a comment or note related to a record, update, or edit. Annotations provide a means for the driver or other authorized support personnel to offer an explanation for the record, edit, or entry. They may also be added automatically in some circumstances to document system events.
Under ELD rules, drivers are required to certify that their record of duty status is true and correct before submitting their log. A driver may use the host driver portal application or the mobile device to review and certify.
The software update to support Canadian ELD requirements includes additional enhancements and usability features that can only be enabled for an organization once all mobile devices have been updated. Documentation will refer to features included with Canadian ELD as "the Canadian ELD suite of functionality".
CMV Power Unit (vehicle) details are typically added by the mobile application whenever a driver signs in to a logging device. If the driver is authenticated, the CMV Power Unit Number specified during the provisioning process will be added to the list of resources used by the driver on that day.
If a driver remains signed in to a mobile logging device over midnight, the CMV Power Unit Number will be added to the list of vehicles for that driver for the following day.
Co-driver information is typically recorded by the mobile application whenever two or more drivers are signed in to the same mobile logging device at the same time.
For example, suppose Driver A signs in to a mobile logging device. If Driver B signs in to that same device before Driver A signs out, Driver A will be added as a co-driver on the current day's log for Driver B, and Driver B will be added as a co-driver for Driver A for that day.
If two or more drivers remain signed in to the same mobile logging device over midnight, their names will be added as co-drivers for each other for the following day.
Trailer and shipment information is typically recorded by the mobile application whenever a driver adds to the list of current resources. Once a trailer or shipment is added, the information for that resource will be added to the list of trailers or shipments hauled by the driver for that day. This logic also extends to other drivers who are signed in to the same mobile logging device.
For example, suppose Driver A signs in to a device. If Driver B signs in to that same device and adds a trailer or shipment before Driver A signs out, that resource will be added to the current day's log for both Driver A and Driver B. Likewise, if Driver C signs in to that same device before that trailer or shipment is dropped, that resource will be added to the current day's log for Driver C as well.
If the last driver to sign out of the mobile application does so without removing all current resources, the next driver to sign in to that same device will be asked whether to keep the trailers and/or shipments as current resources. If the driver answers Yes, the current resources will be kept and added to the list of trailers or shipments hauled by the driver. If a driver remains signed in to a mobile logging device over midnight, any current resources will be added to the list of trailers or shipment hauled by that driver for the following day.
Duty status changes are typically recorded by the mobile application whenever a driver elects to record a status change or when the mobile application detects that the vehicle has started or stopped moving.
If the vehicle is moving and the primary driver is in Driving (D) status over midnight, a new Driving status change (starting at 12:00 AM) will be added for the following day.
In the case that a driver has forgotten to sign in or out of the mobile logging device, first return to the device and sign out before correcting their status. If the driver operated a vehicle without an ELD, needs to transcribe logs recorded for another carrier, or was otherwise unable to use the HOS application to record duty statuses, use the Status Change page to add duty status changes to the log.
In the case that duty status changes were recorded for the Unidentified Driver, use the Unidentified Driver Resolution page to reassign each status change to the correct driver. Drivers will also be prompted to review these events and can accept them on the device as applicable.
A driver may record time as Personal Conveyance by selecting the OFF PC status in the mobile application. This status is only available for drivers that have been configured to Allow Authorized Personal Use of CMV (PC) on ELD.
Time recorded in Personal Conveyance is shown as OFF (Line 1) on the graph grid and as OFF with a corresponding "Authorized Personal Use of CMV" event wherever log events are listed.
A driver may record time as Off Duty, Waiting at Well Site by selecting the OFF Wait at Well button in the mobile application. This button is enabled only if the driver is configured with an "oil field special" rule set.
Time recorded as Off Duty, Waiting at Well Site is shown as OFF (Line 1) on the graph grid and as OFF with a corresponding annotation of "Waiting or standby at oil or natural gas well site" wherever log events are listed.
A driver may record time as Off Duty, Sleeping at Well Site by selecting the OFF Sleep at Well button in the mobile application. This button is enabled only if the driver is configured with an "oil field special" rule set.
Time recorded as Off Duty, Sleeping at Well Site is shown as OFF (Line 1) on the graph grid and as OFF with a corresponding annotation of "Sleeping in other accommodation at oil or natural gas well site" wherever log events are listed.
Driver logs are stored for six months by default. US and Canadian regulations require that all driver logs and associated data be retained for 6 months. Log data older than 6 months is purged daily. When a driver log is purged, any violations, device failures or log edits for that date are also purged.
If the carrier or driver wishes to retain copies of data older than these limits, this can be done at their own risk by printing the logs before they are purged from the host at 6 months. Any driver logs available are subject to inspection during an audit.
Yes. Deleting a driver merely hides the driver's records from view; it does not delete the driver's records from the web server database.
So long as the driver's logs have not yet been purged, you may retrieve them by restoring the deleted driver. For more information on deleting and restoring, see Drivers.
The HOS application analyzes all of the driver's available electronic driver logs, including any exceptions that the driver has claimed, to calculate the time remaining for each HOS rule that applies to the driver's assigned rule set. The lowest of the values calculated for each applicable HOS rule is expressed as the driver's "driving time left". If a driver operates a commercial motor vehicle with no driving time left, a violation of one or more rules will be reported.
The goal of hours of service regulations is to ensure that drivers of commercial motor vehicles are adequately rested so that they may operate their vehicles safely. A driver operating in the United States who has used all available driving time may remain on duty so long as the driver does not operate a commercial motor vehicle until additional driving time is gained. Therefore, violations are reported for drivers operating in the United States only if a Driving (D) status is recorded while the driver has zero driving time left.
Drivers operating in Canada are subject to the Daily Off Duty rule. Because this rule establishes a daily minimum requirement for off duty time, violations of this rule will be reported for drivers who fail to meet the requirement, even if they do not operate a commercial motor vehicle later that same day.
A conflict is an indication of some omission or inconsistency in a driver's log. Conflicts should be resolved as soon as possible because they affect the quality of information provided by the HOS application.
Resolving a conflict typically requires one or more edits to a driver's log.
As a general rule, it is better to edit a log event than to delete a log event.
Keep in mind that a reason is required for each change to a log event and all changes are tracked. Editing an existing event therefore requires fewer steps and results in fewer actions displayed in the log history than deleting an event and adding a new event in its place.
You can change the start time of a duty status, but you cannot change the end time. The HOS application calculates the end date and time automatically.
The end date and time of a duty status is equal to the start date and time of the next subsequent duty status. If no subsequent duty status has been recorded yet, an end time will not be shown.
You cannot undo a change after it has been saved or accepted and made Active. You can make a subsequent edit to correct any information that you entered incorrectly. An edit that is still Inactive - Requested may be deleted and replaced by a new requested change, or the driver can reject the requested change.
Keep in mind that any change made to current log events will result in one or more actions being displayed in the log history. You should therefore plan all changes you need to make before making any of them, and review all details carefully before saving.
The Reason For Change explains why it was necessary to edit the information originally recorded by the driver or log recording software. This text is included as an annotation to the affected event(s) and is required to be entered per US and Canadian ELD requirements.
ELD rules prohibit motor carrier personnel from requesting corrective edits until the driver's record of duty status has been certified and submitted through the ELD. Authorized motor carrier personnel may suggest historical entries where no electronic record of duty status exists (such as when records for the previous 7 days are entered for a newly hired driver). Edits requested by anyone other than the driver will require the driver's approval or rejection.
Automatically recorded driving time can only be modified using the mobile application. If a driver's current status is Driving (D), the driver must change to another status using a mobile logging device before subsequent edits can be made. Verify device connectivity before editing the driver's log.
The HOS application tracks all changes to a driver's log according to ELD rules.
Log events have a Status field indicating the status of each event.
The HOS Application requires a Reason for Change to be entered for any change to a driver's log events. The Reason for Change is shown as an annotation to the event.
When a driver makes a change to the log, the change becomes effective immediately. For example, when a driver deletes an event, the event is immediately given a record status of Inactive - Changed.
When a user who is not the driver makes a change to the log, the change is marked Inactive - Requested until reviewed by the driver. The driver must either accept or reject a requested change.
Changing a log event can sometimes result in two actions being recorded. For example, changing the start time of a duty status may create one request to delete the status change that was originally recorded, and a second request to add a status change at the new time. For maximum transparency in case of an Hours of Service audit, the log history shows both requests as separate actions taken by the same application user at the same time.
When the Unidentified Driver's duty status is set to Driving (D), and the CMV has not been in-motion for 6 consecutive minutes following the driving event, the ELD must automatically switch the duty status to On-Duty, Not Driving (ON). Therefore, when a driver accepts an unidentified driving event, a subsequent ON event is added, to mark the end of driving. If the driver was in some other status (SB or OFF) when driving ended, further edits may be made until the driver's log reflects the actual sequence of duty status changes.
ELD rules require that an ELD monitor its compliance with the ELD technical requirements and detect malfunctions and data inconsistencies related to power, engine synchronization, missing data, timing, positioning, data recording, data transfer, and unidentified driver records requirements. The ELD output identifies these data diagnostic and malfunction events and their status as either "detected" or "cleared". Typically, according to guidance from the FMCSA, a driver can follow the ELD provider's and the motor carrier's recommendations to resolve the data inconsistencies that generate an ELD data diagnostic event, while a motor carrier must correct a malfunction.
Power Data Diagnostic Events occur when an ELD is not powered and fully functional within one minute of the vehicle's engine receiving power and does not remain powered for as long as the vehicle's engine stays powered.
Power Compliance Malfunctions occur when an ELD is not powered for an aggregated in-motion driving time of 30 minutes or more over a 24-hour period across all driver profiles.
Engine Synchronization Data Diagnostic Events occur when an ELD loses ECM connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) and can no longer acquire updated values for the required ELD parameters within five seconds of the need.
Engine Synchronization Compliance Malfunctions occur when ECM connectivity to any of the required data sources (engine power status, vehicle motion status, miles driven, and engine hours) is lost for more than 30 minutes during a 24-hour period aggregated across all drivers operating the ELD.
When an ELD is not sufficiently synchronized with Coordinated Universal Time (UTC) that is, the ELD's internal clock is off by 10 or more minutes, a Timing Compliance Malfunction occurs.
When an ELD fails to acquire a valid position measurement within 5 miles of the commercial motor vehicle moving and 60 minutes has passed, a Position Compliance Malfunction is recorded.
A Data Recording Compliance Malfunction occurs when an ELD can no longer record or retain required events or retrieve recorded logs that are not kept remotely by the motor carrier.
A Missing Required Data Elements Data Diagnostic Event occurs when any required data field is missing at the time of its recording.
A Data Transfer Data Diagnostic Event occurs when the operation of the data transfer mechanism(s) is not confirmed.
A Data Transfer Compliance Malfunction occurs when the ELD has had three consecutive unconfirmed data transfer attempts.
An Unidentified Driving Records Data Diagnostic Event occurs when more than 30 minutes of driving time for an unidentified driver is recorded within a 24-hour period.