If you’ve been struggling to stay on top of the heated EOBR mandate debate—not to mention the constantly shifting timeline—you’re not alone. The road to the final rule has been a bumpy one.
So, if you need help wrapping your brain around EOBR technical requirements or up-to-date insights into the mandate timeline, you’ve come to the right place.
Here’s what you need to know…
EOBR, ELD, and AOBRD – What’s the difference?
Not a whole heckuva lot, to be quite honest.
If you step back for a big picture view, you’ll see that an EOBR (or ELD, or AOBRD) is simply a system that syncs to your vehicle’s engine and electronically tracks your Record of Duty Status, or RODS.
- An Automatic On-Board Recording Device, or AOBRD, is any logging device that complies with the FMCSA’s 395.15 standards—including a direct connection to the vehicle engine.
- Meanwhile, there’s technically no such thing as an Electronic On-Board Recording Device, or EOBR. Such devices would have been defined by 395.16, but that rule was vacated over concerns about driver harassment. Still, with “EOBR” at the heart of the heated debate, it’s the name that stuck.
- Dictated by MAP-21, the FMCSA is preparing to issue a new rule that attempts to address driver harassment concerns, while still mandating electronic logging of RODS. Devices that comply with the new rule will be formally referred to as Electronic Logging Devices, or ELDs.
While EOBRs (or, ELDs) must log a driver’s duty status to be considered a compliant device, some on the market do much, much more. So, as you do your comparison shopping, consider the value these kinds of reporting could bring to your business:
- Electronic Driver Vehicle Inspection Reports (DVIR)
- IFTA fuel tax reporting automation
- Driver behavior reporting on speeding, idling and hard braking
- Mapping and routing solutions integration
- And more
Your EOBR mandate compliance timeline.
Still running on paper logs and wondering when the EOBR mandate will be enforced?
As of February 4, 2014, here’s what you’re looking at:
- The rulemaking is currently under review by the Office of Management and Budget (OMB).
- After the rulemaking is cleared, the FMCSA will review the rule—a process that typically takes two weeks—and publish the Supplemental Notice of Proposed Rulemaking.
- A public comment period, expected to be at least 60 days, will follow.
- Three to nine months following the close of the public comment period, the FMCSA will publish its final rule, following a thorough review of public comments and rule revisions.
- Two years after the final rule is published, drivers and carriers who are required to file a RODS must comply with the EOBR mandate. The enforcement date is expected between the summer of 2016 and early winter 2017.
When it comes to EOBR technology, what makes a solution compliant?
Regulatory requirements for EOBRs (well, AOBRDs to be technically correct) have been established by the FMCSA’s rule 395.15.
To comply with the EOBR mandate, your device must synchronize with your vehicle’s engine (many mobile EOBRs don’t do that) and record:
- The name of the driver and any co-drivers, as well as their corresponding driver identification information, such as user IDs and passwords. (The name of the driver and any co-drivers are not required to be transmitted as part of the downloaded file during a roadside inspection.)
- Driver duty statuses: “Off duty”, “Sleeper berth”, “Driving,” and “On-duty Not Driving.”
- Dates and times.
- Vehicle location at each duty status change.
- The distance traveled.
- The name and USDOT Number of the driver’s motor carrier, as well as the carrier’s main office address.
- The 24-hour period starting time (midnight, 9 AM, noon, or 3 PM, for example).
- The multi-day rule set the motor carrier uses to calculate cumulative duty hours and driving time (seven or eight days).
- The number of hours for each duty status in a 24-hour period, as well as the total number of hours.
- The truck and trailer number.
- Shipping document numbers or the name of the shipper and the commodity being transported.
Compliant EOBR devices must also:
- Give drivers a helping hand where Hours of Service is concerned, with audible or visual alerts that prompt them to look for safe parking at least 30 minutes before they reach their daily or weekly driving and on-duty time limits.
- Allow drivers to provide HOS information for the previous 7 days, plus the current day, when requested of them by law enforcement.
It’s crucial to note that only drivers may make entries to their driver logs, and that all hard copies of the RODS must be signed by the driver.
Make HOS compliance simple.
We can help with easy-to-use electronic driver logs.Learn more
Improve your CSA scores.
It’s simple with robust reporting and real-time alerts.Learn more
What EOBR is right for you?
Learn why mobile solutions are a smart move.Learn more