Title 49

PART 395 APPENDIX A



Appendix A to Subpart B of Part 395 - Functional Specifications for All Electronic Logging Devices (ELDs)

49:5.1.1.2.38.2.17.11.17 : Appendix A

Appendix A to Subpart B of Part 395 - Functional Specifications for All Electronic Logging Devices (ELDs) Table of Contents 1. Scope and Description Scope 1.1. ELD Function 1.2. System Users 1.3. System Architecture 1.4. System Design 1.5. Sections of Appendix 2. Abbreviations 3. Definitions; Notations 3.1. Definitions 3.1.1. Databus 3.1.2. ELD Event 3.1.3. Exempt Driver 3.1.4. Geo-Location 3.1.5. Ignition Power Cycle, Ignition Power On Cycle, Ignition Power Off Cycle 3.1.6. Unidentified Driver 3.2. Notations 4. Functional Requirements 4.1. ELD User Accounts 4.1.1. Account Types 4.1.2. Account Creation 4.1.3. Account Security 4.1.4. Account Management 4.1.5. Non-Authenticated Operation 4.2. ELD-Vehicle Interface 4.3. ELD Inputs 4.3.1. ELD Sensing 4.3.1.1. Engine Power Status 4.3.1.2. Vehicle Motion Status 4.3.1.3. Vehicle Miles 4.3.1.4. Engine Hours 4.3.1.5. Date and Time 4.3.1.6. CMV Position 4.3.1.7. CMV VIN 4.3.2. Driver's Manual Entries 4.3.2.1. Driver's Entry of Required Event Data Fields 4.3.2.2. Driver's Status Inputs 4.3.2.2.1. Driver's Indication of Duty Status 4.3.2.2.2. Driver's Indication of Situations Impacting Driving Time Recording 4.3.2.3. Driver's Certification of Records 4.3.2.4. Driver's Data Transfer Initiation Input 4.3.2.5. Driver's Entry of an Output File Comment 4.3.2.6. Driver's Annotation of Records 4.3.2.7. Driver's Entry of Location Information 4.3.2.8. Driver's Record Entry/Edit 4.3.2.8.1 Mechanism for Driver Edits and Annotations 4.3.2.8.2 Driver Edit Limitations 4.3.3. Motor Carrier's Manual Entries 4.3.3.1. ELD Configuration 4.3.3.1.1. Configuration of Available Categories Impacting Driving Time Recording 4.3.3.1.2. Configuration of Using ELDs 4.3.3.1.3. Motor Carrier's Post-Review Electronic Edit Request 4.4. ELD Processing and Calculations 4.4.1. Conditions for Automatic Setting of Duty Status 4.4.1.1. Automatic Setting of Duty Status to Driving 4.4.1.2. Automatic Setting of Duty Status to On-Duty Not Driving 4.4.1.3. Other Automatic Duty-Status Setting Actions Prohibited 4.4.2. Geo-Location Conversions 4.4.3. Date and Time Conversions 4.4.4. Setting of Event Parameters in Records, Edits, and Entries 4.4.4.1. Event Sequence Identifier (ID) Number 4.4.4.2. Event Record Status, Event Record Origin, Event Type Setting 4.4.4.2.1. Records Automatically Logged by ELD 4.4.4.2.2. Driver Edits 4.4.4.2.3. Driver Entries 4.4.4.2.4. Driver's Assumption of Unidentified Driver Logs 4.4.4.2.5. Motor Carrier Edit Suggestions 4.4.4.2.6. Driver's Actions Over Motor Carrier Edit Suggestions 4.4.5. Data Integrity Check Functions 4.4.5.1. Event Data Check 4.4.5.1.1. Event Checksum Calculation 4.4.5.1.2. Event Data Check Calculation 4.4.5.2. Line Data Check 4.4.5.2.1. Line Checksum Calculation 4.4.5.2.2. Line Data Check Calculation 4.4.5.2.3. Line Data Check Value Inclusion in Output File 4.4.5.3. File Data Check 4.4.5.3.1. File Checksum Calculation 4.4.5.3.2. File Data Check Value Calculation 4.4.5.3.3. File Data Check Value Inclusion in Output File. 4.5. ELD Recording 4.5.1. Events and Data To Record 4.5.1.1. Event: Change in Driver's Duty Status 4.5.1.2. Event: Intermediate Logs 4.5.1.3. Event: Change in Driver's Indication of Allowed Conditions that Impact Driving Time Recording 4.5.1.4. Event: Driver's Certification of Own Records 4.5.1.5. Event: Driver's Login/Logout Activity 4.5.1.6. Event: CMV's Engine Power Up and Shut Down Activity 4.5.1.7. Event: ELD Malfunction and Data Diagnostics Occurrence 4.6. ELD's Self-Monitoring of Required Functions 4.6.1. Compliance Self-Monitoring, Malfunctions and Data Diagnostic Events 4.6.1.1. Power Compliance Monitoring 4.6.1.2. Engine Synchronization Compliance Monitoring 4.6.1.3. Timing Compliance Monitoring 4.6.1.4. Positioning Compliance Monitoring 4.6.1.5. Data Recording Compliance Monitoring 4.6.1.6. Monitoring Records Logged under the Unidentified Driver Profile 4.6.1.7. Data Transfer Compliance Monitoring 4.6.1.8. Other Technology-Specific Operational Health Monitoring 4.6.2. ELD Malfunction Status Indicator 4.6.2.1. Visual Malfunction Indicator 4.6.3. ELD Data Diagnostic Status Indicator 4.6.3.1. Visual Data Diagnostics Indicator 4.7. Special Purpose ELD Functions 4.7.1. Driver's ELD Volume Control 4.7.2. Driver's Access To Own ELD Records 4.7.3. Privacy Preserving Provision for Use During Personal Uses of a CMV 4.8. ELD Outputs 4.8.1. Printout or Display 4.8.1.1. Print Paper Requirements 4.8.1.2. Display Requirements 4.8.1.3. Information To Be Shown on the Printout and Display at Roadside 4.8.2. ELD Data File 4.8.2.1. ELD Output File Standard 4.8.2.1.1. Header Segment 4.8.2.1.2. User List 4.8.2.1.3. CMV List 4.8.2.1.4. ELD Event List for Driver's Record of Duty Status 4.8.2.1.5. Event Annotations, Comments, and Driver's Location Description 4.8.2.1.6. ELD Event List for Driver's Certification of Own Records 4.8.2.1.7. Malfunction and Diagnostic Event Records 4.8.2.1.8. ELD Login/Logout Report 4.8.2.1.9. CMV's Engine Power-Up and Shut Down Activity 4.8.2.1.10. ELD Event Log List for the Unidentified Driver Profile 4.8.2.1.11. File Data Check Value 4.8.2.2. ELD Output File Name Standard 4.9. Data Transfer Capability Requirements 4.9.1. Data Transfer During Roadside Safety Inspections 4.9.2. Motor Carrier Data Reporting 4.10. Communications Standards for the Transmittal of Data Files From ELDs 4.10.1. Data Transfer Mechanisms 4.10.1.1. Wireless Data Transfer via Web Services 4.10.1.2. Wireless Data Transfer Through E-Mail 4.10.1.3. Data Transfer via USB 2.0 4.10.1.4 Wireless Data Transfer via Bluetooth® 4.10.2. Motor Carrier Data Transmission 5. ELD Registration and Certification 5.1. ELD Provider's Registration 5.1.1. Registering Online 5.1.2. Keeping Information Current 5.1.3. Authentication Information Distribution 5.2. Certification of Conformity With FMCSA Standards 5.2.1. Online Certification 5.2.2. Procedure To Validate an ELD's Authenticity 5.3. Publicly Available Information 5.4. Removal of Listed Certification 5.4.1. Removal Process 5.4.2. Notice 5.4.3. Response 5.4.4. Agency Action 5.4.5. Administrative Review 6. References 7. Data Elements Dictionary 7.1. 24-Hour Period Starting Time 7.2. Carrier Name 7.3. Carrier's USDOT Number 7.4. CMV Power Unit Number 7.5. CMV VIN 7.6. Comment/Annotation 7.7. Data Diagnostic Event Indicator Status 7.8. Date 7.9. Distance Since Last Valid Coordinates 7.10. Driver's License Issuing State 7.11. Driver's License Number 7.12. Driver's Location Description 7.13. ELD Account Type 7.14. ELD Authentication Value 7.15. ELD Identifier 7.16. ELD Provider 7.17. ELD Registration ID 7.18. ELD Username 7.19. Engine Hours 7.20. Event Code 7.21. Event Data Check Value 7.22. Event Record Origin 7.23. Event Record Status 7.24. Event Sequence ID Number 7.25. Event Type 7.26. Exempt Driver Configuration 7.27. File Data Check Value 7.28. First Name 7.29. Geo-Location 7.30. Last Name 7.31. Latitude 7.32. Line Data Check Value 7.33. Longitude 7.34. Malfunction/Diagnostic Code 7.35. Malfunction Indicator Status 7.36. Multiday Basis Used 7.37. Order Number 7.38. Output File Comment 7.39. Shipping Document Number 7.40. Time 7.41. Time Zone Offset from UTC 7.42. Trailer Number(s) 7.43. Vehicle Miles 1. Scope and Description

(a) This appendix specifies the minimal requirements for an electronic logging device (ELD) necessary for an ELD provider to build and certify that its technology is compliant with this appendix.

1.1. ELD Function

The ELD discussed in this appendix is an electronic module capable of recording the electronic records of duty status for CMV drivers using the unit in a driving environment within a CMV and meets the compliance requirements in this appendix.

1.2. System Users

Users of ELDs are:

(a) CMV drivers employed by a motor carrier; and

(b) Support personnel who have been authorized by the motor carrier to:

(1) Create, remove, and manage user accounts;

(2) Configure allowed ELD parameters; and

(3) Access, review, and manage drivers' ELD records on behalf of the motor carrier.

1.3. System Architecture

An ELD may be implemented as a stand-alone technology or within another electronic module. It may be installed in a CMV or may be implemented on a handheld unit that may be moved from vehicle to vehicle. The functional requirements are the same for all types of system architecture that may be used in implementing the ELD functionality.

1.4. System Design

(a) An ELD is integrally synchronized with the engine of the CMV such that driving time can be automatically recorded for the driver operating the CMV and using the ELD.

(b) An ELD allows for manual inputs from the driver and the motor carrier support personnel and automatically captures date and time, vehicle position, and vehicle operational parameters.

(c) An ELD records a driver's electronic RODS and other supporting events with the required data elements specified in this appendix and retains data to support the performance requirements specified in this appendix.

(d) An ELD generates a standard data file output and transfers it to an authorized safety official upon request.

(e) This appendix specifies minimally required data elements that must be part of an event record such that a standard ELD output file can be produced by all compliant ELDs.

(f) Figure 1 provides a visual layout of how this appendix is generally organized to further explain the required sub-functions of an ELD.

1.5. Sections of Appendix

(a) Section 2 lists the abbreviations used throughout this appendix.

(b) Section 3 provides definitions for terms and notations used in this document.

(c) Section 4 lists functional requirements for an ELD. More specifically, section 4.1 describes the security requirements for account management within an ELD system and introduces the term “Unidentified Driver” account. Section 4.2 explains internal engine synchronization requirements and its applicability when used in recording a driver's record of duty status in CMVs. Section 4.3 describes the inputs of an ELD which includes automatically measured signals by the ELD as covered in section 4.3.1, and manual entries by the authenticated driver as covered in section 4.3.2 and by the motor carrier as covered in section 4.3.3. The ELD requirements for internal processing and tracking of information flow are described in section 4.4, which includes conditions for and prohibitions against automatic setting of duty-status in section 4.4.1, required geo-location and date and time conversion functions in sections 4.4.2 and 4.4.3, respectively, use of event attributes for tracking of edit and entry history in section 4.4.4, and the use of data check functions in the recording of ELD logs in section 4.4.5 as standard security measures for all ELDs. Section 4.5 describes the events an ELD must record and the data elements each type of event must include. Section 4.6 introduces device self-monitoring requirements and standardizes the minimal set of malfunctions and data diagnostic events an ELD must be able to detect. Section 4.7 introduces technical functions that are intended to guard a driver against harassment and introduces a privacy preserving provision when a driver operates a CMV for personal purposes. Section 4.8 explains ELD outputs, which are the information displayed to a user and the standard data output file an ELD must produce. Sections 4.9 and 4.10, respectively, describe the data reporting requirements and the communications protocols.

(d) Section 5 describes the ELD certification and registration process.

(e) Section 6 lists the cited references throughout this appendix.

(f) Section 7 provides a data elements dictionary referencing each data element identified in this appendix.

2. Abbreviations 3pDP Third-Party Developers' Partnership ASCII American Standard Code for Information Interchange CAN Control Area Network CMV Commercial Motor Vehicle ECM Electronic Control Module ELD Electronic Logging Device FMCSA Federal Motor Carrier Safety Administration HOS Hours of Service HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure ICD Interface Control Document SAFER Safety and Fitness Electronic Records RFC Request for Comments RODS Records of Duty Status TLS Transport Layer Security UCT Coordinated Universal Time USB Universal Serial Bus WSDL Web Services Definition Language XML Extensible Markup Language XOR Exclusive Or {bitwise binary operation} 3. Definitions; Notations 3.1. Definitions 3.1.1. Databus

A vehicle databus refers to an internal communications network that interconnects components inside a vehicle and facilitates exchange of data between subsystems typically using serial or control area network protocols.

3.1.2. ELD Event

An ELD event refers to a discrete instance in time when the ELD records data with the data elements specified in this appendix. The discrete ELD events relate to the driver's duty status and ELD's operational integrity. They are either triggered by input from the driver (driver's duty status changes, driver's login/logout activity, etc.) or triggered by the ELD's internal monitoring functions (ELD malfunction detection, data diagnostics detection, intermediate logs, etc.). ELD events and required data elements for each type of ELD event are described in detail in section 4.5.1 of this appendix.

3.1.3. Exempt Driver

As specified in further detail in section 4.3.3.1.2 of this appendix, an ELD must allow a motor carrier to configure an ELD for a driver who may be exempt from the use of the ELD. An example of an exempt driver would be a driver operating under the short-haul exemption in § 395.1(e) of this part (100 air-mile radius driver and non-CDL 150-air mile radius driver). Even though exempt drivers do not have to use an ELD, in operations when an ELD equipped CMV may be shared between exempt and non-exempt drivers, motor carriers can use this allowed configuration to avoid issues with unidentified driver data diagnostics errors.

3.1.4. Geo-Location

Geo-location is the conversion of a position measurement in latitude/longitude coordinates into a description of the distance and direction to a recognizable nearby location name. Geo-location information is used on an ELD's display or printout.

3.1.5. Ignition Power Cycle, Ignition Power On Cycle, Ignition Power Off Cycle

(a) An ignition power cycle refers to the engine's power status changing from “on to off” or “off to on”, typically with the driver controlling engine power status by switching the ignition key positions.

(b) An ignition power on cycle refers to the engine power sequence changing from “off to on and then off”. This refers to a continuous period when a CMV's engine is powered.

(c) An ignition power off cycle refers to the engine power sequence changing from “on to off and then on”. This refers to a continuous period when a CMV's engine is not powered.

3.1.6. Unidentified Driver

“Unidentified Driver” refers to the operation of a CMV featuring an ELD without an authenticated driver logging in the system. Functional specifications in this appendix require an ELD to automatically capture driving time under such conditions and attribute such records to the unique “Unidentified Driver account,” as specified in section 4.1.5 of this appendix, until the motor carrier and the driver review the records and they are assigned to the true and correct owner, as described in § 395.32 of this part.

3.2. Notations

Throughout this appendix the following notations are used when data elements are referenced.

(a) < . > indicates a parameter an ELD must track. For example refers to the unique <ELD username> or identifier specified during the creation of an ELD account with the requirements set forth in section 7.18 of this appendix.

(b) { .} indicates which of multiple values of a parameter is being referenced. For example <ELD username {for the co-driver}> refers specifically to the ELD username for the co-driver.

(c) <CR> indicates a carriage return or new line or end of the current line. This notation is used in section 4.8.2 of this appendix, which describes the standard ELD output file.

4. Functional Requirements 4.1. ELD User Accounts 4.1.1. Account Types

An ELD must support a user account structure that separates drivers and motor carrier's support personnel (i.e. non-drivers).

4.1.2. Account Creation

(a) Each user of the ELD must have a valid active account on the ELD with a unique identifier assigned by the motor carrier.

(b) Each driver account must require the entry of the driver's license number and the State or jurisdiction that issued the driver's license into the ELD during the account creation process. The driver account must securely store this information on the ELD.

(c) An ELD must not allow creation of more than one driver account associated with a driver's license for a given motor carrier.

(d) A driver account must not have administrative rights to create new accounts on the ELD.

(e) A support personnel account must not allow recording of ELD data for its account holder.

(f) An ELD must reserve a unique driver account for recording events during non-authenticated operation of a CMV. This appendix will refer to this account as the “unidentified driver account.”

4.1.3. Account Security

(a) An ELD must provide secure access to data recorded and stored on the system by requiring user authentication during system login.

(b) Driver accounts must only have access to data associated with that driver, protecting the authenticity and confidentiality of the collected information.

4.1.4. Account Management

(a) An ELD must be capable of separately recording and retaining ELD data for each individual driver using the ELD.

(b) An ELD must provide for and require concurrent authentication for team drivers.

(c) If more than one ELD unit is used to record a driver's electronic records within a motor carrier's operation, the ELD in the vehicle the driver is operating most recently must be able to produce a complete ELD report for that driver, on demand, for the current 24-hour period and the previous 7 consecutive days.

4.1.5. Non-Authenticated Operation

(a) An ELD must associate all non-authenticated operation of a CMV with a single ELD account labeled unidentified driver.

(b) If a driver does not log onto the ELD, as soon as the vehicle is in motion, the ELD must:

(1) Provide a visual or visual and audible warning reminding the driver to stop and log in to the ELD;

(2) Record accumulated driving and on-duty, not-driving, time in accordance with the ELD defaults described in section 4.4.1 of this appendix under the unidentified driver profile; and

(3) Not allow entry of any information into the ELD other than a response to the login prompt.

4.2. ELD-Vehicle Interface

(a) An ELD must be integrally synchronized with the engine of the CMV. Engine synchronization for purposes of ELD compliance means the monitoring of the vehicle's engine operation to automatically capture the engine's power status, vehicle's motion status, miles driven value, and engine hours value when the CMV's engine is powered.

(b) An ELD used while operating a CMV that is a model year 2000 or later model year, as indicated by the vehicle identification number (VIN), that has an engine electronic control module (ECM) must establish a link to the engine ECM when the CMV's engine is powered and receive automatically the engine's power status, vehicle's motion status, miles driven value, and engine hours value through the serial or Control Area Network communication protocols supported by the engine ECM or the vehicle's databus. If the vehicle does not have an ECM, an ELD may use alternative sources to obtain or estimate these vehicle parameters with the listed accuracy requirements under section 4.3.1 of this appendix.

4.3. ELD Inputs 4.3.1. ELD Sensing 4.3.1.1. Engine Power Status

An ELD must be powered and become fully functional within 1 minute of the vehicle's engine receiving power and must remain powered for as long as the vehicle's engine stays powered.

4.3.1.2. Vehicle Motion Status

(a) An ELD must automatically determine whether a CMV is in motion or stopped by comparing the vehicle speed information with respect to a set speed threshold as follows:

(1) Once the vehicle speed exceeds the set speed threshold, it must be considered in motion.

(2) Once in motion, the vehicle must be considered in motion until its speed falls to 0 miles per hour and stays at 0 miles per hour for 3 consecutive seconds. Then, the vehicle will be considered stopped.

(3) An ELD's set speed threshold for determination of the in-motion state for the purpose of this section must not be configurable to greater than 5 miles per hour.

(b) If an ELD is required to have a link to the vehicle's engine ECM, vehicle speed information must be acquired from the engine ECM or the vehicle's databus. Otherwise, vehicle speed information must be acquired using an independent source apart from the positioning services described under section 4.3.1.6 of this appendix and must be accurate within ±3 miles per hour of the CMV's true ground speed for purposes of determining the in-motion state for the CMV.

4.3.1.3. Vehicle Miles

(a) An ELD must monitor vehicle miles as accumulated by a CMV over the course of an ignition power on cycle (accumulated vehicle miles) and over the course of CMV's operation (total vehicle miles). Vehicle miles information must use or must be converted to units of whole miles.

(b) If the ELD is required to have a link to the vehicle's engine ECM as specified in section 4.2 of this appendix:

(1) The ELD must monitor the odometer message broadcast on the engine ECM or the vehicle's databus and use it to log total vehicle miles information; and

(2) The ELD must use the odometer message to determine accumulated vehicle miles since engine's last power on instance.

(c) If the ELD is not required to have a link to the vehicle's engine ECM as specified in section 4.2 of this appendix, the accumulated vehicle miles indication must be obtained or estimated from a source that is accurate to within ±10% of miles accumulated by the CMV over a 24-hour period as indicated on the vehicle's odometer display.

4.3.1.4. Engine Hours

(a) An ELD must monitor engine hours of the CMV over the course of an ignition power on cycle (elapsed engine hours) and over the course of the total engine hours of the CMV's operation. Engine hours must use or must be converted to hours in intervals of a tenth of an hour.

(b) If an ELD is required to have a link to the vehicle's engine ECM, the ELD must monitor the total engine hours message broadcast on the engine ECM or the vehicle's databus and use it to log total engine hours information. Otherwise, engine hours must be obtained or estimated from a source that monitors the ignition power of the CMV and must be accurate within ±0.1 hour of the engine's total operation within a given ignition power on cycle.

4.3.1.5. Date and Time

(a) The ELD must obtain and record the date and time information automatically without allowing any external input or interference from a motor carrier, driver, or any other person.

(b) The ELD time must be synchronized to Coordinated Universal Time (UCT) and the absolute deviation from UCT must not exceed 10 minutes at any point in time.

4.3.1.6. CMV Position

(a) An ELD must determine automatically the position of the CMV in standard latitude/longitude coordinates with the accuracy and availability requirements of this section.

(b) The ELD must obtain and record this information without allowing any external input or interference from a motor carrier, driver, or any other person.

(c) CMV position measurement must be accurate to ±0.5 mile of absolute position of the CMV when an ELD measures a valid latitude/longitude coordinate value.

(d) Position information must be obtained in or converted to standard signed latitude and longitude values and must be expressed as decimal degrees to hundreds of a degree precision (i.e., a decimal point and two decimal places).

(e) Measurement accuracy combined with the reporting precision requirement implies that position reporting accuracy will be on the order of ±1mile of absolute position of the CMV during the course of a CMV's commercial operation.

(f) During periods of a driver's indication of personal use of the CMV, the measurement reporting precision requirement is reduced to tenths of a degree (i.e., a decimal point and single decimal place) as further specified in section 4.7.3 of this appendix.

(g) An ELD must be able to acquire a valid position measurement at least once every 5 miles of driving; however, the ELD records CMV location information only during ELD events as specified in section 4.5.1 of this appendix.

4.3.1.7. CMV VIN

The vehicle identification number (VIN) for the power unit of a CMV must be automatically obtained and recorded if it is available on the vehicle databus.

4.3.2. Driver's Manual Entries

(a) An ELD must prompt the driver to input information into the ELD only when the CMV is stationary and driver's duty status is not on-duty driving, except for the condition specified in section 4.4.1.2 of this appendix.

(b) If the driver's duty status is driving, an ELD must only allow the driver who is operating the CMV to change the driver's duty status to another duty status.

(c) A stopped vehicle must maintain zero (0) miles per hour speed to be considered stationary for purposes of information entry into an ELD.

(d) An ELD must allow an authenticated co-driver who is not driving, but who has logged into the ELD prior to the vehicle being in motion, to make entries over his or her own records when the vehicle is in motion. The ELD must not allow co-drivers to switch driving roles when the vehicle is in motion.

4.3.2.1. Driver's Entry of Required Event Data Fields

(a) An ELD must provide a means for a driver to enter information pertaining to the driver's ELD records manually, e.g., CMV power unit number, as specified in section 7.4 of this appendix; trailer number(s), as specified in section 7.42; and shipping document number, as specified in section 7.39.

(b) If the motor carrier populates these fields automatically, the ELD must provide means for the driver to review such information and make corrections as necessary.

4.3.2.2. Driver's Status Inputs 4.3.2.2.1. Driver's Indication of Duty Status

(a) An ELD must provide a means for the authenticated driver to select a driver's duty status.

(b) The ELD must use the ELD duty status categories listed in Table 1 of this appendix.

4.3.2.2.2. Driver's Indication of Situations Impacting Driving Time Recording

(a) An ELD must provide the means for a driver to indicate the beginning and end of a period when the driver may use the CMV for authorized personal use or for performing yard moves. The ELD must acquire this status in a standard format from the category list in Table 2 of this appendix. This list must be supported independent of the duty status categories described in section 4.3.2.2.1 of this appendix.

(b) An ELD must allow a driver to select only categories that a motor carrier enables by configuration for that driver, as described in section 4.3.3.1.1 of this appendix.

(c) An ELD must only allow one category to be selected at any given time and use the latest selection by the driver.

(d) The ELD must prompt the driver to enter an annotation upon selection of a category from Table 2 of this appendix and record the driver's entry.

(e) A driver's indication of special driving situation must reset to none if the ELD or CMV's engine goes through a power off cycle (ELD or CMV's engine turns off and then on) except if the driver has indicated authorized personal use of CMV. If the driver has indicated authorized personal use of the CMV, the ELD must require confirmation of continuation of the authorized personal use of CMV condition by the driver. If not confirmed by the driver and the vehicle is in motion, the ELD must default to none.

4.3.2.3. Driver's Certification of Records

(a) An ELD must include a function whereby a driver can certify the driver's records at the end of a 24-hour period.

(1) This function, when selected, must display a statement that reads “I hereby certify that my data entries and my record of duty status for this 24-hour period are true and correct.”

(2) An ELD must prompt the driver to select “Agree” or “Not ready.” An ELD must record the driver's affirmative selection of “Agree” as an event.

(b) An ELD must only allow the authenticated driver to certify records associated with that driver.

(c) If any edits are necessary after the driver certifies the records for a given 24-hour period, the ELD must require and prompt the driver to re-certify the updated records.

(d) If there are any past records on the ELD (excluding the current 24-hour period) that require certification or re-certification by the driver, the ELD must indicate the required driver action on the ELD's display and prompt the driver to take the necessary action during the login and logout processes.

4.3.2.4. Driver's Data Transfer Initiation Input

(a) An ELD must provide a standardized single-step driver interface for compilation of driver's ELD records and initiation of the data transfer to authorized safety officials when requested during a roadside inspection.

(b) The ELD must input the data transfer request from the driver, require confirmation, present and request selection of the supported data transfer options by the ELD, and prompt for entry of the output file comment as specified in section 4.3.2.5 of this appendix. Upon confirmation, the ELD must generate the compliant output file and perform the data transfer.

(c) The supported single-step data transfer initiation mechanism (such as a switch or an icon on a touch-screen display) must be clearly marked and visible to the driver when the vehicle is stopped.

4.3.2.5. Driver's Entry of an Output File Comment

An ELD must accommodate the entry of an output file comment up to 60 characters long. If an authorized safety official provides a key phrase or code during an inspection to be included in the output file comment, it must be entered and embedded in the electronic ELD records in the exchanged dataset as specified in section 4.8.2.1.1 of this appendix. The default value for the output file comment must be blank. This output file comment must be used only for the creation of the related data files for the intended time, place, and ELD user.

4.3.2.6. Driver's Annotation of Records

(a) An ELD must allow a driver to add annotations in text format to recorded, entered, or edited ELD events.

(b) The ELD must require annotations to be 4 characters or longer, including embedded spaces if driver annotation is required and driver is prompted by the ELD.

4.3.2.7. Driver's Entry of Location Information

(a) An ELD must allow manual entry of a CMV's location by the driver in text format in support of the driver edit requirements described in section 4.3.2.8 of this appendix.

(b) The driver's manual location entry must be available as an option to a driver only when prompted by the ELD under allowed conditions as described in section 4.6.1.4 of this appendix.

(c) A manual location entry must show “M” in the latitude/longitude coordinates fields in ELD records.

4.3.2.8. Driver's Record Entry/Edit

(a) An ELD must provide a mechanism for a driver to review, edit, and annotate the driver's ELD records when a notation of errors or omissions is necessary or enter the driver's missing ELD records subject to the requirements specified in this section.

(b) An ELD must not permit alteration or erasure of the original information collected concerning the driver's ELD records or alteration of the source data streams used to provide that information.

4.3.2.8.1. Mechanism for Driver Edits and Annotations

(a) If a driver edits or annotates an ELD record or enters missing information, the act must not overwrite the original record.

(b) The ELD must use the process outlined in section 4.4.4.2 of this appendix to configure required event attributes to track the edit history of records.

(c) Driver edits must be accompanied by an annotation. The ELD must prompt the driver to annotate edits.

4.3.2.8.2. Driver Edit Limitations

(a) An ELD must not allow or require the editing or manual entry of records with the following event types, as described in section 7.25 of this appendix:

Event type Description
2 An intermediate log,
5 A driver's login/logout activity,
6 CMV's engine power up/shut down, or
7 ELD malfunctions and data diagnostic events.