Appendix A to Part 395 Appendix A to Part 395—Electronic On-Board Recorder Performance Specifications

1. Data Elements Dictionary for Electronic On-Board Recorders (EOBRs)

1.1To facilitate the electronic transfer of records to roadside inspection personnel and compliance review personnel, and provide the ability of various third-party and proprietary EOBR devices to be interoperable, a consistent electronic file format and record layout for the electronic RODS data to be recorded are necessary. This EOBR data elements dictionary provides a standardized and consistent format for EOBR output data.

EOBR Data File Format

1.2Regardless of the particular electronic file type (such as ASCII or XML) ultimately used for recording the electronic RODS produced by an EOBR, RODS data must be recorded according to a “flat file” database model format. A flat file is a simple database in which all information is stored in a plain text format with one database “record” per line. Each of these data records is divided into “fields” using delimiters (as in a comma-separate-values data file) or based on fixed column positions. Table 1 below presents the general concept of a flat data file consisting of data “fields” (columns) and data “records” (rows).

[Figure or graphic omitted. See the official source.]

1.3The data elements dictionary describes the data fields component of the above framework. Individual data records must be generated and recorded whenever there is a change in driver duty status, an EOBR diagnostic event (such as power-on/off, self test, etc.), or when one or more data fields of an existing data record are later amended. In the last case, the corrected record must be recorded and noted as “current” in the “Event Status Code” data field, with the original record maintained in its unedited form and noted as “historical” in the “Event Status Code” data field. The EOBR Data Elements Dictionary is described in Table 2. The event codes are listed in Table 3.

2. Communications Standards for the Transmittal of Data Files From Electronic On-Board Recorders (EOBRs)

2.1EOBRs must produce and store RODS in accordance with the file format specified in this appendix and must be capable of a one-way transfer of these records through wired and wireless methods to authorized safety officials upon request.

2.2Wired. EOBRs must be capable of transferring RODS using the “Universal Serial Bus Specification (Revision 2.0)” (incorporated by reference, see § 395.18). Each EOBR device must implement a single USB compliant interface featuring a Type A connector. The USB interface must implement the Mass Storage class (08h) for driverless operation.

2.3Wireless. EOBRs must be capable of transferring RODS using one of the following wireless standards:

2.3.1802.11g-2003 standard as defined in the 802.11-2007 base standard for wireless communication “IEEE Standard for Information Technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements: Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications” (IEEE Std. 802.11-2007) (incorporated by reference, see § 395.18).

2.3.2Commercial Mobile Radio Services (e.g., cellular).

3. Certification of EOBRs To Assess Conformity With FMCSA Standards

3.1The following outcome-based performance requirements must be included in the self-certification testing conducted by EOBR manufacturers:

3.1.1Location

3.1.1.1The location description for the duty status change must be sufficiently precise to enable enforcement personnel to quickly determine the vehicle's geographic location at each change of duty status on a standard map or road atlas.

3.1.1.2When the CMV is in motion, location and time must be recorded at intervals of no greater than 60 minutes. This recorded information must be available for an audit of EOBR data, but is not required to be displayed on the EOBR's visual output device.

3.1.1.3Location codes derived from satellite or terrestrial sources, or a combination thereof must be used. The location codes must correspond, at minimum, to the GNIS maintained by the United States Geological Survey.

3.1.2Distance traveled

3.1.2.1Distance traveled may use units of miles or kilometers driving during each on-duty driving period and total for each 24-hour period for each driver operating the CMV.

3.1.2.2If the EOBR records units of distance in kilometers, it must provide a means to display the equivalent distance in English units.

3.1.2.3If the EOBR obtains distance-traveled information from a source internal to the CMV, the information must be accurate to the CMV's odometer.

3.1.3Date and time

3.1.3.1The date and time must be reported on the EOBR output record and display for each change of duty status and at such additional entries as specified under “Location.”

3.1.3.2The date and time must be obtained, transmitted, and recorded in such a way that it cannot be altered by a motor carrier or driver.

3.1.3.3The time must be coordinated to the Universal Time Clock (UTC) and must not drift more than 60 seconds per month.

3.1.4File format and communication protocols: The EOBR must produce and transfer a RODS file in the format and communication methods specified in sections 1.0 and 2.0 of this Appendix.

3.1.5Environment

3.1.5.1 [Reserved]

3.1.5.2Vibration and shock—The EOBR must meet industry standards for vibration stability and for preventing electrical shocks to device operators.

3.2The EOBR and EOBR support systems must be certified by the manufacturer as evidence that their design has been sufficiently tested to meet the requirements of § 395.16 under the conditions in which they would be used.

3.3The exterior faceplate of EOBRs must be marked by the manufacturer with the text 'USDOT-EOBR' as evidence that the device has been tested and certified as meeting the performance requirements of § 395.16.

[75 FR 17248, Apr. 5, 2010, as amended at 75 FR 55491, Sept. 13, 2010]