16 4 AOBRDs v. ELDs AOBRDs v. ELDs – Highlighting Some Differences DEVICE FUNCTIONALITY AOBRDs ELDs “Integral Synchronization” with Vehicle Required but term is not defined in FMCSA rules Integral synchronization required. ELD must interface with CMV engine control module to automatically capture engine power status, vehicle motion, miles driven, engine hours. (CMVs older than MY 2000 exempted) Recording CMV Location Required at each change of duty status. Manual or automated Automated entry required at each change of duty status, at 60-minute intervals while CMV in motion, at engine on and off, and at beginning and end of personal use and yard moves Graph Grid Display Not required. Only time and sequence of duty status changes must be shown, including starting time of each day Required. Must be able to show a graph grid of driver’s day either on display or on a printout HOS Advisory or Warning Messages Not required or addressed Not required. “Unassigned driving time/miles” warning must be provided upon login “Default” Duty Status Not required or addressed On-duty not driving status, when CMV has not been in-mo - tion for 5 consecutive minutes, and driver has not respond - ed to required ELD prompt within one minute. No other non-driver initiated status change is allowed Communication/ Data Transfer Methods to Law Enforcement Not addressed – some interface between AOBRD support system and printer Required. Two Options: 1. Telematics-must transfer data via both wireless web services and wireless email 2. Local Transfer-must transfer data via both USB 2.0 and Bluetooth. Both types of ELDs must be capable of displaying standardized ELD data set to authorized safety officials via display or printout Resistance to Tampering AOBRD and support systems must be tamperproof to maximum extent practical Must not permit alteration or erasure of original information collected concerning driver’s record, or alteration of the source data streams used to provide that information. ELD must support data integrity check functions Sensor Failures and Edited Data Must identify sensor failures and edited data Must have capability to monitor its compliance (engine connectivity, timing, location, etc) for detectable malfunctions and data inconsistencies. ELD must record these occurrences. Information originally compiled by Scopelitis Transportation Consulting, LLC