Thomas Bray • Senior Editor, Transportation Management • J. J. Keller & Associates, Inc. Elise Chianelli • Product Manager Safety & Compliance • PeopleNet Fred Fakkema • Vice President, Compliance • Zonar Supplemental Notice of Proposed Rulemaking published to Federal Register on 3/28/2014 Rule addresses: ◦ ELD Use ◦ ELD Technical Standards ◦ Retention of Supporting Documents Carrier is responsible for ensuring ELD has been registered with FMCSA AOBRD valid 4 years after effective date All vehicles required to adopt ELD within 2 years of final rule Only exceptions are 100 and 150 air-mile drivers that had to complete a log 8 days (or less) out of last 30 days No exceptions for: ◦ Leased or rented vehicles ◦ Driveaway/towaway drivers ◦ “Non-trucking” motor carriers ◦ Older or non-CDL vehicles Data elements include: ◦ Date and time ◦ Location 1 mile while on duty 10 miles during personal use ◦ ◦ ◦ ◦ Driver logged in Engine hours and vehicle mileage Vehicle identification Authorized carrier identification Engine, Speed & Distance must be captured by vehicle Must capture data elements ◦ ◦ ◦ ◦ At startup and shutdown At each change of duty status Once per hour when vehicle is operating At start and end of “personal use” or “yard time” FMCSA is requesting info on how to handle older vehicles rather than requiring an alternate connection Same as Current Requirements and: ◦ Driver’s First and Last Name ◦ ELD username ◦ Total Engine Hours ◦ Show Miles for each Driving period ◦ ELD Malfunction Status ◦ Data Diagnostic Status Indicator for the Authenticated Driver All Drivers and Support Personnel must have unique user name and password associated with their account Driver account must include driver’s license information to provide unique ID Driver must not have Administrative rights ELD must include “unassigned driver” account All unassigned driving time must be assigned or accounted for Could create a problem for carriers that use a leasing company that moves units around for them Driver must “certify” log within 24 hours Back office support edits must all be approved by driver ◦ Cannot submit until last activity for the day is complete All annotations, comments, and changes must be retained, along with original Driver direct access to 6 months logs Driving time automatically calculated Driver must have ability to add/update Driver entries to be made when vehicle is stopped Driver must notify carrier within 24 hours of system failure Portable ELDs must be fixed mounted during operation ◦ ◦ ◦ ◦ ◦ Annotations CMV number Trailer numbers Shipment Information Output Comment, as requested by enforcement ELD prompts Driver to Login if vehicle moves with no driver Device requires alert if vehicle stops moving for 5 minutes ◦ Defaults to On Duty if no driver entry within 1 min ◦ Other automatic duty status settings are prohibited Driver must add Location if no position fix at duty change Driver does NOT have to be prompted when approaching hours limit System must have “mute” to be used when driver is in the sleeper Must be capable of producing Graph Grid at Roadside or Print One step process for Data Transfer Authorized Official selects method of transfer At least One Primary Method: ◦ Web Services ◦ Bluetooth ◦ Email Two Backup Methods ◦ USB (all devices must support) Scannable QR Code Transjet Transfer Standardized data output format ◦ System can use any type of data, but output must be standard ◦ May provide a “value-add” option for vehicle providers Carrier provide data to Auditors and Drivers upon request Carrier to maintain a “backup copy” Five Categories: ◦ ◦ ◦ ◦ ◦ Origin & Destination (BOLs) Dispatch & Trip Sheets Expense Receipts Mobile Communication Payroll Required Data Elements: ◦ ◦ ◦ ◦ Driver Name Date Time Location Max of 10 records in 24 Hour Period Drivers must submit to Carrier within 8 days Drivers must produce at Roadside