which must be convertible to the local time at the location where it is
recorded.
    (ii) If a driver has fewer than 10 supporting documents containing
the four data elements under paragraph (c)(2)(i) of this section for a
24-hour period, a document containing the data elements under
(c)(2)(i)(A)-(C) of this section is considered a supporting document
for purposes of paragraph (d) of this section.
    (d) Maximum number of supporting documents. (1) Subject to
paragraphs (d)(3) and (4) of this section, a motor carrier need not
maintain more than 10 supporting documents for an individual driver's
24-hour period under paragraph (c) of this section.
    (2) In applying the limit on the number of documents required under
paragraph (d)(1) of this section, each electronic mobile communication
record applicable to an individual driver's 24-hour period shall be
counted as a single document.
    (3) If a driver submitted more than 10 supporting documents for a
24-hour period, a motor carrier must retain the supporting documents
containing earliest and latest time indication among the 10 supporting
documents maintained.
    (4) In addition to other supporting documents required under this
section, and notwithstanding the maximum number of documents under
paragraph (d)(1) of this section, a motor carrier that requires a
driver to complete a paper record of duty status under Sec.
395.8(a)(1)(iii) must maintain toll receipts for any period when the
driver kept paper records of duty status.
    (e) Link to driver's record of duty status. A motor carrier must
maintain supporting documents in such a manner that they may be
effectively matched to the corresponding driver's record of duty
status.
    (f) Prohibition of destruction. No motor carrier or driver may
obscure, deface, destroy, mutilate, or alter existing information
contained in a supporting document.
    (g)(1) On request during a roadside inspection, a driver must make
available to an authorized Federal, State, or local official for the
official's review any supporting document in the driver's possession.
    (2) A driver need not produce a supporting document under paragraph
(g)(1) of this section in a format other than the format in which the
driver possesses it.
    (h) Self-compliance systems. (1) FMCSA may authorize on a case-by-
case basis motor carrier self-compliance systems.
    (2) Requests for use of a supporting document self-compliance
system may be submitted to FMCSA under the procedures described in 49
CFR part 381, subpart C (Procedures for Applying for Exemptions).
    (3) FMCSA will consider requests concerning types of supporting
documents maintained by a motor carrier under Sec.  395.8(k)(1) and the
method by which a driver retains and maintains a copy of the record of
duty

status for the previous 7 days and makes it available for inspection
while on duty in accordance with Sec.  395.8.
0
17. Amend Sec.  395.15 by revising paragraph (a) to read as follows:

Sec.  395.15  Automatic on-board recording devices.

    (a) Authority to use. (1) A motor carrier that installs and
requires a driver to use an automatic on-board recording device in
accordance with this section before [DATE TWO YEARS AFTER THE EFFECTIVE
DATE OF THE FINAL RULE] may continue to use the compliant automatic on-
board recording device no later than [DATE FOUR YEARS AFTER THE
EFFECTIVE DATE OF THE FINAL RULE]. Otherwise, the authority to use
automatic on-board recording devices (AOBRDs) under this section ends
on [DATE TWO YEARS AFTER THE EFFECTIVE DATE OF THE FINAL RULE].
    (2) A motor carrier may require a driver to use an automatic on-
board recording device to record the driver's hours of service.
    (3) Every driver required by a motor carrier to use an automatic
on-board recording device shall use such device to record the driver's
hours of service.
* * * * *

Sec. Sec.  395.16-395.19  [Reserved]

0
18. Add and reserve Sec. Sec.  395.16 through 395.19.
0
19. Amend part 395 by adding a new subpart B, consisting of Sec. Sec.
395.20 through 395.38, and Appendix to Subpart B of Part 395, to read
as follows:

Subpart B--Electronic Logging Devices (ELDs)

Sec.  395.20 ELD applicability and scope.
Sec.  395.22 Motor carrier responsibilities--In general.
Sec.  395.24 Driver responsibilities--In general.
Sec.  395.26 ELD data automatically recorded.
Sec.  395.28 Special driving categories; other driving statuses.
Sec.  395.30 ELD record submissions, edits, annotations, and data
retention.
Sec.  395.32 Non-authenticated driver logs.
Sec.  395.34 ELD malfunctions and data diagnostic events.
Sec.  395.36 Driver access to records.
Sec.  395.38 Incorporation by reference.
Appendix to Subpart B of Part 395--Functional Specifications for All
Electronic Logging Devices (ELDS)

Subpart B--Electronic Logging Devices (ELDs)

Sec.  395.20  ELD applicability and scope.

    (a) Scope. This subpart applies to ELDs used to record a driver's
hours of service under Sec.  395.8(a).
    (b) Applicability. An ELD used after [DATE TWO YEARS AFTER THE
EFFECTIVE DATE OF FINAL RULE] must meet the requirements of this
subpart.
    (c) ELD system. Throughout this subpart, a reference to an ELD
includes, to the extent applicable, an ELD support system.

Sec.  395.22  Motor carrier responsibilities--In general.

    (a) Registered ELD required. A motor carrier required to use an ELD
must use only an ELD that is listed on the Federal Motor Carrier Safety
Administration's registered ELDs list, accessible through the Agency's
Web site.
    (b) User rights management. (1) This paragraph (b) of this section
applies to a motor carrier whose drivers use ELDs and to the motor
carrier's support personnel who have been authorized by the motor
carrier to access ELD records and make or suggest authorized edits.
    (2) A motor carrier must:
    (i) Actively manage ELD accounts, including creating, deactivating,
and updating accounts, and ensure that properly authenticated
individuals have ELD accounts with appropriate rights;
    (ii) Assign a unique ELD username to each user account with the
required user identification data;
    (iii) Ensure that a driver's license used in the creation of an ELD
driver account is valid and corresponds to the intended driver; and
    (iv) Ensure that information entered to create a new account is
accurate.
    (c) Driver identification data. (1) The ELD user account assigned
by the motor carrier to a driver requires the following data elements:
    (i) A driver's first and last name, as reflected on the driver's
license;
    (ii) A unique ELD username selected by the motor carrier;
    (iii) The driver's valid driver's license number; and
    (iv) The State or jurisdiction that issued the driver's license.
    (2) The driver's license number or Social Security number must not
be used as, or as part of, the username for the account created on an
ELD.
    (d) Motor carrier support personnel identification data. The ELD
user account assigned by a motor carrier to support personnel requires
the following data elements:
    (1) The individual's first and last name, as reflected on a
government issued identification; and
    (2) A unique ELD username selected by the motor carrier.
    (e) Proper log-in required. The motor carrier must require that its
drivers and support personnel log into the ELD system using their
proper identification data.
    (f) Calibration. A motor carrier must ensure that an ELD is
calibrated and maintained in accordance with the provider's
specifications.
    (g) Portable ELDs. If a driver uses a portable ELD, the motor
carrier shall ensure that the ELD is mounted in a fixed position during
the operation of the commercial motor vehicle and visible to the driver
when the driver is seated in the normal driving position.
    (h) In-vehicle information. A motor carrier must ensure that its
drivers possess onboard a commercial motor vehicle an ELD information
packet containing the following items:
    (1) A user's manual for the driver describing how to operate the
ELD;
    (2) An instruction sheet for the driver describing the data
transfer mechanisms supported by the ELD and step-by-step instructions
for the driver to produce and transfer the driver's hours-of-service
records to an authorized safety official;
    (3) An instruction sheet for the driver describing ELD malfunction
reporting requirements and recordkeeping procedures during ELD
malfunctions; and
    (4) A supply of blank driver's records of duty status graph-grids
sufficient to record the driver's duty status and other related
information for a minimum of 8 days.
    (i) Record backup and security. (1) A motor carrier must maintain
for 6 months a back-up copy of the ELD records on a device separate
from that on which the original data are stored.
    (2) A motor carrier must maintain a driver's ELD records so as to
protect a driver's privacy in a manner consistent with sound business
practices.
    (j) Record production. When requested by an authorized safety
official, a motor carrier must produce ELD records in an electronic
format either on request or, if the motor carrier has multiple offices
or terminals, within the time permitted under Sec.  390.29.

Sec.  395.24  Driver responsibilities--In general.

    (a) In general. A driver must provide the information the ELD
requires as prompted by the ELD and required by the motor carrier.
    (b) Driver's duty status. A driver must input the driver's duty
status by selecting among the following categories available on the
ELD:
    (1) ``Off duty'' or ``OFF'' or ``1'';
    (2) ``Sleeper berth'' or ``SB'' or ``2'', to be used only if
sleeper berth is used;
    (3) ``Driving'' or ``D'' or ``3''; or
    (4) ``On-duty not driving'' or ``ON'' or ``4''.
    (c) Miscellaneous data. (1) A driver must manually input the
following information in the ELD:

    (i) Annotations, when applicable;
    (ii) Driver's location description, when prompted by the ELD; and
    (iii) Output file comment, when directed by an authorized safety
officer.
    (2) A driver must manually input or verify the following
information on the ELD:
    (i) Commercial motor vehicle power unit number;
    (ii) Trailer number(s), if applicable; and
    (iii) Shipping document number, if applicable.
    (d) Driver use of ELD. On request by an authorized safety official,
a driver must produce and transfer from an ELD the driver's hours-of-
service records in accordance with the instruction sheet provided by
the motor carrier.

Sec.  395.26  ELD data automatically recorded.

    (a) In general. An ELD provides the following functions and
automatically records the data elements listed in this section in
accordance with the requirements contained in the appendix to subpart B
of part 395.
    (b) Data automatically recorded. The ELD automatically records the
following data elements:
    (1) Date;
    (2) Time;
    (3) CMV geographic location information;
    (4) Engine hours;
    (5) Vehicle miles;
    (6) Driver or authenticated user identification data;
    (7) Vehicle identification data; and
    (8) Motor carrier identification data.
    (c) Change of duty status. When a driver indicates a change of duty
status under Sec.  395.24(b), the ELD records the data elements in
paragraphs (b)(1) through (8) of this section.
    (d) Intermediate recording. (1) When a commercial motor vehicle is
in motion and there has not been a duty status change or another
intermediate recording in the previous 1 hour, the ELD automatically
records an intermediate recording that includes the data elements in
paragraphs (b)(1) through (8) of this section.
    (2) If the intermediate recording is created during a period when
the driver indicates authorized personal use of a commercial motor
vehicle, the data elements in paragraphs (b)(4) and (b)(5) of this
section (engine hours and vehicle miles) will be left blank and
paragraph (b)(3) of this section (location) will be recorded with a
single decimal point resolution (approximately within a 10-mile
radius).
    (e) Change in special driving category. If a driver indicates a
change in status under Sec.  395.28(a)(2), the ELD records the data
elements in paragraphs (b)(1) through (8) of this section.
    (f) Certification of the driver's daily record. The ELD provides a
function for recording the driver's certification of the driver's
records for every 24-hour period. When a driver certifies or
recertifies the driver's records for a given 24-hour period under Sec.
395.30(b)(2), the ELD records the date, time and driver identification
data elements in paragraphs (b)(1), (2), and (6) of this section.
    (g) Log in/log out. When an authorized user logs into or out of an
ELD, the ELD records the data elements in paragraphs (b)(1) and (2) and
(b)(4) through (8) of this section.
    (h) Engine power up/shut down. When a commercial motor vehicle's
engine is powered up or powered down, the ELD records the data elements
in paragraphs (b)(1) through (8) of this section.
    (i) Authorized personal use. If the record is created during a
period when the driver has indicated authorized personal use of a
commercial motor vehicle, the data element in paragraph (a)(3) of this
section is logged with a single decimal point resolution (approximately
within a 10-mile radius).
    (j) Malfunction and data diagnostic event. When an ELD detects or
clears a malfunction or data diagnostic event, the ELD records the data
elements in paragraphs (b)(1) and (2) and (b)(4) through (8) of this
section.

Sec.  395.28.  Special driving categories; other driving statuses.

    (a) Special driving categories. (1) Motor carrier options. A motor
carrier may configure an ELD to authorize a driver to indicate that the
driver is operating a commercial motor vehicle under any of the
following special driving categories:
    (i) Authorized personal use; and
    (ii) Yard moves.
    (2) Driver's responsibilities. A driver operating a commercial
motor vehicle under one of the authorized categories listed in
paragraph (a)(1) of this section:
    (i) Must select on the ELD the applicable special driving category
before the start of the status and deselect when the indicated status
ends; and
    (ii) When prompted by the ELD, annotate the driver's ELD record
describing the driver's activity.
    (b) Drivers exempt from ELD use. A motor carrier may configure an
ELD to designate a driver as exempt from ELD use.
    (c) Other driving statuses. A driver operating a commercial motor
vehicle under any exception under Sec.  390.3(f) or Sec.  395.1 who is
not covered under paragraph (a) or (b) of this section must annotate
the driver's ELD record explaining the applicable exemption.

Sec.  395.30  ELD record submissions, edits, annotations, and data
retention.

    (a) True and correct record keeping. A driver and the motor carrier
must ensure that the driver's ELD records are accurate.
    (b) Review of records and certification by driver. (1) A driver
must review the driver's ELD records, edit and correct inaccurate
records, enter any missing information, and certify the accuracy of the
information.
    (2) Using the certification function of the ELD, the driver must
certify the driver's records by affirmatively selecting ``Agree''
immediately following 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.'' The driver must certify the record immediately
after the final required entry has been made or corrected for the 24-
hour period.
    (3) The driver must submit the driver's certified ELD records to
the motor carrier in accordance with Sec.  395.8(a)(2).
    (4) If any edits are necessary after the driver submits the records
to the motor carrier, the driver must recertify the record after the
edits are made.
    (c) Edits, entries, and annotations. (1) Subject to the edit
limitations of an ELD, a driver may edit, enter missing information,
and annotate ELD recorded events. When edits, additions, or annotations
are necessary, a driver must use the ELD and respond to the ELD's
prompts.
    (2) The driver or support personnel must annotate each change or
addition to a record.
    (3) In the case of team drivers, if there was a mistake resulting
in the wrong driver being assigned driving-time hours by the ELD, and
if the team drivers were both indicated in each other's records for
that period as co-drivers, driving time may be edited and reassigned
between the team drivers following the procedure supported by the ELD.
    (d) Motor carrier-proposed edits. (1) On review of a driver's
submitted records, the motor carrier may request edits to a driver's
records of duty status to ensure accuracy. A driver must confirm or
reject any proposed change, implement the appropriate edits on the
driver's record of duty status, and recertify and resubmit the records
in order for any motor carrier-proposed changes to take effect.
    (2) A motor carrier may not request edits to the driver's
electronic records

before the records have been submitted by the driver.
    (3) Edits requested by any system or by any person other than the
driver must require the driver's electronic confirmation or rejection.
    (e) Coercion prohibited. A motor carrier may not coerce a driver to
make a false certification of the driver's data entries or record of
duty status.
    (f) Motor carrier data retention requirements. A motor carrier must
not alter or erase, or permit or require alteration or erasure of, the
original information collected concerning the driver's hours of
service, the source data streams used to provide that information, or
information contained in any ELD support system that uses the original
information and source data streams.

Sec.  395.32  Non-authenticated driver logs.

    (a) Tracking non-authenticated operation. The ELD must associate
the non-authenticated operation of a commercial motor vehicle with a
single account labeled ``Unidentified Driver'' as soon as the vehicle
is in motion, if no driver has logged into the ELD.
    (b) Driver. When a driver logs into an ELD, the driver must review
any unassigned driving time when prompted by the ELD and must:
    (1) Assume any records that belong to the driver under the driver's
account; or
    (2) Indicate that the records are not attributable to the driver.
    (c) Motor carrier. (1) A motor carrier must ensure that records of
unidentified driving are reviewed and must:
    (i) Annotate the record, explaining why the time is unassigned; or
    (ii) Assign the record to the appropriate driver to correctly
reflect the driver's hours of service.
    (2) A motor carrier must retain unidentified driving records for
each ELD for a minimum of 6 months from the date of receipt.
    (3) During a safety inspection, audit or investigation by an
authorized safety official, a motor carrier must make available
unidentified driving records from the ELD corresponding to the time
period for which ELD records are required.

Sec.  395.34  ELD malfunctions and data diagnostic events.

    (a) Recordkeeping during ELD malfunctions. In case of an ELD
malfunction, a driver must do the following:
    (1) Note the malfunction of the ELD and provide written notice of
the malfunction to the motor carrier within 24 hours;
    (2) Reconstruct the record of duty status for the current 24-hour
period and the previous 7 consecutive days, and record the records of
duty status on graph-grid paper logs that comply with Sec.  395.8,
unless the driver already possesses the records or the records are
retrievable from the ELD; and
    (3) Continue to manually prepare a record of duty status until the
ELD is serviced and brought back into compliance with this subpart.
    (b) Inspections during malfunctions. When a driver is inspected for
hours of service compliance during an ELD malfunction, the driver must
provide the authorized safety official the driver's records of duty
status manually maintained as specified under paragraphs (a)(2) and (3)
of this section.
    (c) Driver requirements during ELD data diagnostic events. If an
ELD indicates that there is a data inconsistency that generates a data
diagnostic event, the driver must follow the motor carrier's and ELD
provider's recommendations in resolving the data inconsistency.
    (d) Motor carrier requirements for repair, replacement, or service.
(1) If a motor carrier receives or discovers information concerning the
malfunction of an ELD, the motor carrier must take corrective actions
to correct the malfunction of the ELD within 8 days of discovery of the
condition or a driver's notification to the motor carrier, whichever
occurs first.
    (2) A motor carrier seeking to extend the period of time permitted
for repair, replacement, or service of one or more ELDs shall notify
the FMCSA Division Administrator for the State of the motor carrier's
principal place of business within 5 days after a driver notifies the
motor carrier under paragraph (a)(1) of this section. Each request for
an extension under this section must be signed by the motor carrier and
must contain:
    (i) The name, address, and telephone number of the motor carrier
representative who files the request;
    (ii) The make, model, and serial number of each ELD;
    (iii) The date and location of each ELD malfunction as reported by
the driver to the carrier; and
    (iv) A concise statement describing actions taken by the motor
carrier to make a good faith effort to repair, replace, or service the
ELD units, including why the carrier needs additional time beyond the 8
days provided by this section.
    (3) If FMCSA determines that the motor carrier is continuing to
make a good faith effort to ensure repair, replacement, or service to
address the malfunction of each ELD, FMCSA may allow an additional
period.
    (4) FMCSA will provide written notice to the motor carrier of its
determination. The determination may include any conditions that FMCSA
considers necessary to ensure hours-of-service compliance. The
determination shall constitute a final agency action.
    (5) A carrier providing a request for extension that meets the
requirements of paragraph (d)(2) of this section is deemed in
compliance with Sec.  395.8(a)(1)(i) and (a)(2) until FMCSA makes an
extension determination under this section, provided the motor carrier
and driver continue to comply with the other requirements of this
section.

Sec.  395.36  Driver access to records.

    (a) Records on ELD. Drivers must be able to access their own ELD
records. A motor carrier must not introduce a process that would
require a driver to go through the motor carrier to obtain copies of
the driver's own ELD records if such records exist on or are
automatically retrievable through the ELD operated by the driver.
    (b) Records in motor carrier's possession. On request, a motor
carrier must provide a driver with access to and copies of the driver's
own ELD records unavailable under paragraph (a) of this section during
the period a motor carrier is required to retain the records under
Sec.  395.8(k).

Sec.  395.38  Incorporation by reference.

    (a) Incorporation by reference. Certain materials are incorporated
by reference in part 395, with the approval of the Director of the
Office of the Federal Register under 5 U.S.C. 552(a), and 1 CFR part
51. To enforce any edition other than that specified in this section,
the Federal Motor Carrier Safety Administration must publish notice of
change in the Federal Register, and the material must be available to
the public. All approved material is available for inspection at the
Federal Motor Carrier Safety Administration, Office of Bus and Truck
Standards and Operations (MC-PS),<PHONE_NUMBER>, and is available from
the sources listed below. It is also available for inspection at the
National Archives and Records Administration (NARA). For information on
the availability of this material at NARA, call<PHONE_NUMBER> or go to
http://www.archives.gov/federal_register/code_of_federal_regulations/ibr_locations.html.
    (b) Institute of Electrical and Electronic Engineers (IEEE)
Standards Association. 445 Hoes Lane, Piscataway, NJ 08854-4141. Web
page is http://standards.ieee.org/index.html. Telephone is (732) 981-
0060.

    (1) ``Standard for Authentication in Host Attachments of Transient
Storage Devices,'' IEEE Standards Association: 2009 (IEEE Std. 1667-
2009). Incorporation by reference approved for appendix to subpart B of
part 395, paragraph <IP_ADDRESS>.
    (2) [Reserved]
    (c) Universal Serial Bus Implementers Forum (USBIF). 3855 SW. 153rd
Drive, Beaverton, Oregon 97006. Web page is http://www.usb.org.
Telephone is<PHONE_NUMBER>.
    (1) ``Universal Serial Bus Specification,'' Compaq, Hewlett-
Packard, Intel, Lucent, Microsoft, NEC, Philips; April 27, 2000
(Revision 2.0). Incorporation by reference approved for appendix to
subpart B of part 395, paragraphs 4.9.1, Table 5, 4.9.2, <IP_ADDRESS>, and
4.10.3.
    (2) [Reserved]
    (d) American National Standards Institute (ANSI). 11 West 42nd
Street, New York, New York 10036. Web page is http://webstore.ansi.org.
Telephone is<PHONE_NUMBER>.
    (1) ``ANSI INCITS 446-2008, American National Standard for
Information Technology--Identifying Attributes for Named Physical and
Cultural Geographic Features (Except Roads and Highways) of the United
States, Its Territories, Outlying Areas, and Freely Associated Areas
and the Waters of the Same to the Limit of the Twelve-Mile Statutory
Zone (10/28/2008),'' (ANSI INCITS 446-2008). Incorporation by reference
approved for appendix to subpart B of part 395, paragraph 4.4.2. (For
further information, see also the Geographic Names Information System
(GNIS) at http://geonames.usgs.gov/domestic/index.html.)
    (2) ``Information Systems--Coded Character Sets--7-Bit American
National Standard Code for Information Interchange (7-Bit ASCII),''
ANSI INCITS 4-1986 (R2007). Incorporation by reference approved for
appendix to subpart B of part 395, Table 3 and paragraph <IP_ADDRESS>.
    (e) International Standards Organization (ISO). 1, ch. de la Voie-
Creuse, CP 56--CH-1211, Geneva 20, Switzerland. Web page is http://www.iso.org. Telephone is 41 22 749 03 46.
    (1) ``ISO/IEC 18004:2006 Information technology--Automatic
identification and data capture techniques--QR Code 2005 bar code
symbology specification.'' Incorporation by reference approved for
appendix to subpart B of part 395, paragraph <IP_ADDRESS>.
    (2) ``ISO/IEC 17568 Information technology--Telecommunications and
information exchange between systems--Close proximity electric
induction wireless communications.'' Incorporation by reference
approved for appendix to subpart B of part 395, paragraph <IP_ADDRESS>.
    (f) Internet Engineering Task Force (IETF). C/o Association
Management Solutions, LLC (AMS) 48377 Freemont Blvd., Suite 117,
Freemont, CA 94538. Telephone is<PHONE_NUMBER>.
    (1) Request for Comment (RFC) 5246-``The Transport Layer Security
(TLS) Protocol Version 1.2,'' August 2008. Incorporation by reference
approved for appendix to subpart B of part 395, paragraph <IP_ADDRESS>.
    (2) RFC 5321--``Simple Mail Transfer Protocol,'' October 2008.
Incorporation by reference approved for appendix to subpart B of part
395, paragraph <IP_ADDRESS>.
    (3) RFC 5322--``Internet Message Format,'' October 2008.
Incorporation by reference approved for appendix to subpart B of part
395, paragraph <IP_ADDRESS>.
    (g) U.S. Department of Commerce, National Institute of Standards
and Technology (NIST). 100 Bureau Drive, Stop 1070, Gaithersburg, MD
20899-1070. Web page is http://www.nist.gov. Telephone is (301) 975-
6478.
    (1) ``Federal Information Processing Standards (FIPS) Publication
197, November 26, 2001, Announcing the ADVANCED ENCRYPTION STANDARD
(AES).'' Incorporation by reference approved for appendix to subpart B
of part 395, paragraphs <IP_ADDRESS> and <IP_ADDRESS>.
    (2) ``Special Publication (SP) 800-32, February 26, 2001,
Introduction to Public Key Technology and the Federal PKI
Infrastructure.'' Incorporation by reference approved for appendix to
subpart B of part 395, paragraphs <IP_ADDRESS> and <IP_ADDRESS>.
    (h) World Wide Web Consortium (W3C). 32 Vassar Street, Building 32-
G514, Cambridge, MA 02139. Web page is http://www.w3.org. Telephone is
(617) 253-2613.
    (1) ``Web Services Description Language (WSDL) 1.1, W3C Note 15,
March 2001,'' Ariba, IBM Research, Microsoft. Incorporation by
reference approved for appendix to subpart B of part 395, paragraph
<IP_ADDRESS>(1).
    (2) ``Simple Object Access Protocol (SOAP) Version 1.2 Part 1:
Messaging Framework (Second Edition), W3C Recommendation 27 April
2007,'' W3C[supreg] (MIT, ERCIM, Keio). Incorporation by reference
approved for appendix to subpart B of part 395, paragraph <IP_ADDRESS>(2).
    (3) ``Extensible Markup Language (XML) 1.0 (Fifth Edition), W3C
Recommendation 26 November 2008,'' W3C[supreg] (MIT, ERCIM, Keio).
Incorporation by reference approved for appendix to subpart B of part
395, paragraph <IP_ADDRESS>(3).
    (4) RFC 2616 ``Hypertext Transfer Protocol--HTTP/1.1''
Incorporation by reference approved for appendix to subpart B of part
395, paragraph <IP_ADDRESS>.
    (i) Bluetooth SIG, Inc., 5209 Lake Washington Blvd. NE., Suite 350,
Kirkland, WA 98033. Web page is https://www.bluetooth.org/Technical/Specifications/adopted.htm. Telephone is<PHONE_NUMBER>.
    (1) ``Specification of the Bluetooth System: Wireless Connections
Made Easy,'' Bluetooth SIG Version, Covered Core Package version 2.1 +
EDR or a higher version. Incorporation by reference approved for
appendix to subpart B of part 395, paragraph <IP_ADDRESS>.
    (2) [Reserved]

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

Table of Contents

1. SCOPE AND DESCRIPTION
    1.1. ELD Function
    1.2. System User
    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
    <IP_ADDRESS>. Engine Power Status
    <IP_ADDRESS>. Vehicle Motion Status
    <IP_ADDRESS>. Vehicle Miles
    <IP_ADDRESS>. Engine Hours
    <IP_ADDRESS>. Date and Time
    <IP_ADDRESS>. CMV Position
    <IP_ADDRESS>. CMV VIN
    4.3.2. Driver's Manual Entries
    <IP_ADDRESS>. Driver's Entry of Required Event Data Fields
    <IP_ADDRESS>. Driver's Status Inputs
    <IP_ADDRESS>.1. Driver's Indication of Duty Status
    <IP_ADDRESS>.2. Driver's Indication of Situations Impacting Driving
Time Recording
    <IP_ADDRESS>. Driver's Certification of Records
    <IP_ADDRESS>. Driver's Data Transfer Initiation Input

    <IP_ADDRESS>. Driver's Entry of an Output File Comment
    <IP_ADDRESS>. Driver's Annotation of Records
    <IP_ADDRESS>. Driver's Entry of Location Information
    <IP_ADDRESS>. Driver's Record Entry/Edit
    4.3.3. Motor Carrier's Manual Entries
    <IP_ADDRESS>. ELD Configuration
    <IP_ADDRESS>.1. Configuration of Available Categories Impacting
Driving Time Recording
    <IP_ADDRESS>.2. Configuration of Using ELDs
    4.4. ELD Processing and Calculations
    4.4.1. Conditions for Automatic Setting of Duty Status
    <IP_ADDRESS>. Automatic Setting of Duty Status to Driving
    <IP_ADDRESS>. Automatic Setting of Duty Status to On-Duty Not Driving
    <IP_ADDRESS>. 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
    <IP_ADDRESS>. Event Sequence Identifier (ID) number
    <IP_ADDRESS>. Event Record Status, Event Record Origin, Event Type
Setting
    <IP_ADDRESS>.1. Records Automatically Logged by ELD
    <IP_ADDRESS>.2. Driver Edits
    <IP_ADDRESS>.3. Driver entries
    <IP_ADDRESS>.4. Driver's Assumption of Unidentified Driver Logs
    <IP_ADDRESS>.5. Motor Carrier Edit Suggestions
    <IP_ADDRESS>.6. Driver's Actions Over Motor Carrier Edit Suggestions
    4.4.5. Data Integrity Check Functions
    <IP_ADDRESS>. Event Data Check
    <IP_ADDRESS>.1. Event Checksum Calculation
    <IP_ADDRESS>.2. Event Data Check Calculation
    <IP_ADDRESS>. Line Data Check
    <IP_ADDRESS>.1. Line Checksum Calculation
    <IP_ADDRESS>.2. Line Data Check Calculation
    <IP_ADDRESS>.3. Line Data Check Value Inclusion in Output File
    <IP_ADDRESS>. File Data Check
    <IP_ADDRESS>.1. File Checksum Calculation
    <IP_ADDRESS>.2. File Data Check Value Calculation
    <IP_ADDRESS>.3. File Data Check Value Inclusion in Output File
    4.5. ELD Recording
    4.5.1. Events and Data to Record
    <IP_ADDRESS>. Event: Change in Driver's Duty Status
    <IP_ADDRESS>. Event: Intermediate Logs
    <IP_ADDRESS>. Event: Change in Driver's Indication of Allowed
Conditions that Impact Driving Time Recording
    <IP_ADDRESS>. Event: Driver's Certification of Own Records
    <IP_ADDRESS>. Event: Driver's Login/Logout Activity
    <IP_ADDRESS>. Event: CMV's Engine Power Up and Shut Down Activity
    <IP_ADDRESS>. 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
    <IP_ADDRESS>. Power Compliance Monitoring
    <IP_ADDRESS>. Engine Synchronization Compliance Monitoring
    <IP_ADDRESS>. Timing Compliance Monitoring
    <IP_ADDRESS>. Positioning Compliance Monitoring
    <IP_ADDRESS>. Data Recording Compliance Monitoring
    <IP_ADDRESS>. Monitoring Records Logged under the Unidentified Driver
Profile
    <IP_ADDRESS>. Data Transfer Compliance Monitoring
    <IP_ADDRESS>. Other Technology-Specific Operational Health Monitoring
    4.6.2. ELD Malfunction Status Indicator
    <IP_ADDRESS>. Visual Malfunction Indicator
    4.6.3. ELD Data Diagnostic Status Indicator
    <IP_ADDRESS>. 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. Information To Be Displayed by an ELD
    4.8.2. ELD Data File
    <IP_ADDRESS>. ELD Output File Standard
    <IP_ADDRESS>.1. Header Segment
    <IP_ADDRESS>.2. User List
    <IP_ADDRESS>.3. CMV List
    <IP_ADDRESS>.4. ELD Event List for Driver's Record of Duty Status
    <IP_ADDRESS>.5. Event Annotations, Comments, and Driver's Location
Description
    <IP_ADDRESS>.6. ELD Event List for Driver's Certification of Own
Records
    <IP_ADDRESS>.7. Malfunction and Diagnostic Event Records
    <IP_ADDRESS>.8. ELD Login/Logout Report
    <IP_ADDRESS>.9. CMV's Engine Power-Up and Shut Down Activity
    <IP_ADDRESS>.10. ELD Event Log List for the Unidentified Driver
Profile
    <IP_ADDRESS>.11. File Data Check Value
    <IP_ADDRESS>. ELD Output File Name Standard
    4.9. Data Transfer Capability Requirements
    4.9.1. Data Reporting 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. Primary Wireless Data Transfer Mechanisms
    <IP_ADDRESS>. Wireless Data Transfer via Web Services
    <IP_ADDRESS>. Wireless Data Transfer via Bluetooth[supreg]
    <IP_ADDRESS>. Wireless Data Transfer Through E-Mail
    4.10.2. Backup Wired and Proximity Data Transfer Mechanisms
    <IP_ADDRESS>. USB 2.0
    <IP_ADDRESS>. Data Transfer via Scannable QR Codes
    <IP_ADDRESS>. Data Transfer via TransferJetTM
    <IP_ADDRESS>. Printout
    4.10.3. Motor Carrier Support System Data Transmission.
5. ELD-CERTIFICATION--REGISTRATION
    5.1. Certification of Conformity with FMCSA Standards
    5.1.1. Registering Online
    5.1.2. Keeping Information Current
    5.1.3. Authentication Information Distribution
    5.2. ELD Provider's Registration.
    5.2.1. Online Certification
    5.2.2. Procedure to Validate an ELD's Authenticity
    5.3. Publicly Available Information
6. REFERENCES
7. DATA ELEMENTS DICTIONARY
    7.1.1. 24-Hour Period Starting Time
    7.1.2. Carrier Name
    7.1.3. Carrier's USDOT Number
    7.1.4. CMV Power Unit Number
    7.1.5. CMV VIN
    7.1.6. Comment/Annotation
    7.1.7. Data Diagnostic Event Indicator Status
    7.1.8. Date
    7.1.9. Distance Since Last Valid Coordinates
    7.1.10. Driver's License Issuing State
    7.1.11. Driver's License Number
    7.1.12. Driver's Location Description
    7.1.13. ELD Account Type
    7.1.14. ELD Authentication Value
    7.1.15. ELD Identifier
    7.1.16. ELD Registration ID
    7.1.17. ELD Username
    7.1.18. Engine Hours
    7.1.19. Event Code
    7.1.20. Event Data Check Value
    7.1.21. Event Record Origin
    7.1.22. Event Record Status
    7.1.23. Event Sequence ID Number
    7.1.24. Event Type
    7.1.25. Exempt Driver Configuration
    7.1.26. File Data Check Value
    7.1.27. First Name
    7.1.28. Geo-Location
    7.1.29. Last Name
    7.1.30. Latitude
    7.1.31. Line Data Check Value
    7.1.32. Longitude
    7.1.33. Malfunction/Diagnostic Code
    7.1.34. Malfunction Indicator Status
    7.1.35. Multiday Basis Used
    7.1.36. Order Number
    7.1.37. Output File Comment
    7.1.38. Shipping Document Number
    7.1.39. Time
    7.1.40. Time Zone Offset from UTC
    7.1.41. Trailer Number(s)
    7.1.42. Vehicle Miles

1. Scope and Description

    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.
    Throughout this appendix, a reference to an ELD includes, to the
extent applicable, an ELD support system.

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:
    (1) CMV drivers employed by a motor carrier; and
    (2) Support personnel who have been authorized by the motor
carrier to:
    (a) Create, remove and manage user accounts;
    (b) Configure allowed ELD parameters; and
    (c) 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

    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.
    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.
    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
    An ELD generates a standard data file output and transfers it to
an authorized safety official upon request.
    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.
    Figure 1 provides a visual layout of how this appendix is
generally organized to further explain the required sub-functions of
an ELD.
BILLING CODE 4910-EX-P
[GRAPHIC] [TIFF OMITTED] TP28MR14.000

BILLING CODE 4910-EX-C

1.5. Sections of Appendix

    Section 2 lists the abbreviations used throughout this appendix.
    Section 3 provides definitions for terms and notations used in
this document.
    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 built before
and after a threshold model year. 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 element each type of an event must include. Section 4.6
introduces device self-monitoring requirements and standardizes the
minimal set of malfunctions and data diagnostic events an ELM 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.
    Section 5 describes the ELD certification and registration
process.
    Section 6 lists the cited references throughout this appendix.
    Section 7 provides a data elements dictionary for each data
element referenced 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
QR Quick Response
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{time}

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 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 events are described in detail in section 4.5.1.

3.1.3. Exempt Driver

    As specified in further detail in section <IP_ADDRESS>.2, an ELD must
allow a motor carrier to configure an ELD for a driver who may be
exempt from the use of ELD. Examples of an exempt driver would be a
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 in ELD's displayable outputs such as on a
screen.

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

    An ignition power cycle refers to the engine's power status
changing from ``on to off'' or ``off to on'', typically with driver
controlling ignition power by switching the ignition key positions.
    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.
    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 with the unique ``Unidentified Driver''
account, as specified in section 4.1.5, until they are reviewed and
assigned to the true and correct owner of these records.

3.2. Notations

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

<.> indicates a parameter an ELD must track. For example ELD
username refers to the unique  or identifier specified
during the creation of an ELD account with the requirements set
forth in section 7.1.17.
{.{time}  indicates which of multiple values of a parameter is being
referenced. For example ELD username {for the co-driver{time}
refers specifically the ELD username for the co-driver.
 indicates a carriage return or new line or end of current line.
This notation is used in section 4.8.2 which describes the standard
ELD output file and in section <IP_ADDRESS> which describes a standard
printout report.

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

    Each user of the ELD must have a valid active account on the ELD
with a unique identifier assigned by the motor carrier.
    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.
    An ELD must not allow creation of more than one driver account
associated with a driver's license for a given motor carrier.
    A driver account must not have administrative rights to create
new accounts on the ELD.
    A support personnel account must not allow recording of ELD data
for its account holder.
    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 unidentified driver account.

4.1.3. Account Security

    An ELD must provide secure access to data recorded and stored on
the system by requiring user authentication during system login.
    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

    An ELD must be capable of separately recording and retaining ELD
data for each individual driver using the ELD.
    An ELD must provide for and require concurrent authentication
for team drivers.
    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

    An ELD must associate all non-authenticated operation of a CMV
with a single ELD account labeled unidentified driver.
    If a driver does not log onto the ELD, as soon as the vehicle is
in motion, the ELD must:
    (a) Provide a visual or visual and audible warning reminding the
driver to stop and login to the ELD;
    (b) Record accumulated driving and on-duty, not-driving, time in
accordance with the ELD defaults described in section 4.4.1 under
the unidentified driver profile; and
    (c) Not allow entry of any information into the ELD other than a
response to the login prompt.

4.2. ELD-Vehicle Interface

    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 engine's power status, vehicle's motion status, miles driven
value, and engine hours value. Furthermore, an ELD used while
operating a CMV that is a model year 2000 or later model year, as
indicated by the vehicle identification number, that has engine
electronic control module (ECM), must establish a link to the engine
ECM and receive this information automatically through the serial or
Control Area Network communication (CAN) protocols supported by the
vehicle's engine ECM. Otherwise, an ELD may use alternative sources
to obtain or

estimate these vehicle parameters with the listed accuracy
requirements under section 4.3.1.

4.3. ELD Inputs

4.3.1. ELD Sensing

<IP_ADDRESS>. Engine Power Status

    An ELD must be powered within 15 seconds of the vehicle's engine
receiving power and must remain powered for as long as the vehicle's
engine stays powered.

<IP_ADDRESS>. Vehicle Motion Status

    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.
    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.
Otherwise, vehicle speed information must be acquired using an
independent source apart from the positioning services described
under section <IP_ADDRESS> 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.

<IP_ADDRESS>. Vehicle Miles

    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.
    If the ELD is required to have a link to the vehicle's engine
ECM as specified in section 4.2:
    (1) The ELD must monitor the engine ECM's odometer message
broadcast 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.
    Otherwise, 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.

<IP_ADDRESS>. Engine Hours

    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 CMV's operation total engine hours. Engine hours must
use or must be converted to hours in intervals of a tenth of an
hour.
    If an ELD is required to have a link to the vehicle's engine
ECM, the ELD must monitor engine ECM's total engine hours message
broadcast 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.

<IP_ADDRESS>. Date and Time

    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.
    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.

<IP_ADDRESS>. CMV Position

    An ELD must have the capability to automatically determine the
position of the CMV in standard latitude/longitude coordinates with
the accuracy and availability requirements of this section.
    ELD must obtain and record this information without allowing any
external input or interference from a motor carrier, driver, or any
other person.
    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.
    Position information must be obtained in or converted into
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).
    Measurement accuracy combined with the reporting precision
requirement implies that position reporting accuracy will be in the
order of 1mile of absolute position of the CMV during
the course of a CMV's commercial operation.
    During periods of a driver's indication of personal use of the
CMV, measurement reporting precision requirement is further reduced
to be expressed as decimal degrees to tenths of a degree (i.e. a
decimal point and single decimal place) as further specified in
section 4.7.3.
    An ELD must be able to acquire a valid position measurement at
least once every 5 miles of driving; however, CMV location
information is only recorded during ELD events as specified in
section 4.5.1.

<IP_ADDRESS>. CMV VIN

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

4.3.2. Driver's Manual Entries

    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 <IP_ADDRESS>.
    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.
    A stopped vehicle must maintain zero (0) miles per hour speed to
be considered stationary for purposes of information entry into an
ELD.
    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.

<IP_ADDRESS>. Driver's Entry of Required Event Data Fields

    An ELD must provide a means for a driver to manually enter
information pertaining to driver's ELD records such as CMV power
unit number as specified in section 7.1.4, trailer number(s) as
specified in section 7.1.41 and shipping document number as
specified in 7.1.38.
    If these fields are populated automatically by motor carrier's
ELD system, the ELD must provide means for the driver to review such
information and make corrections as necessary.

<IP_ADDRESS>. Driver's Status Inputs

<IP_ADDRESS>.1. Driver's Indication of Duty Status

    An ELD must provide a means for the authenticated driver to
select a driver's duty status. The ELD must use the ELD duty status
categories listed in Table 1.

                     Table 1--Duty Status Categories
------------------------------------------------------------------------
          Duty status                Abbreviation          Data coding
------------------------------------------------------------------------
Off Duty......................  OFF...................                 1
Sleeper Berth.................  SB....................                 2
Driving.......................  D.....................                 3
On-duty Not Driving...........  ON....................                 4
------------------------------------------------------------------------

<IP_ADDRESS>.2. Driver's Indication of Situations Impacting Driving Time
Recording

    An ELD must provide 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.
This list must be supported independent of the duty status
categories described in section <IP_ADDRESS>.1.

   Table 2--Categories for Driver's Indication of Situations Impacting
                         Driving Time Recording
------------------------------------------------------------------------
           Category                  Abbreviation          Data coding
------------------------------------------------------------------------
Authorized Personal Use of CMV  PC....................                 1
Yard Moves....................  YM....................                 2
Default: None.................  ......................                 0
------------------------------------------------------------------------

    An ELD must allow a driver to only select categories that a
motor carrier enables by configuration for that driver, as described
in section <IP_ADDRESS>.1.
    An ELD must only allow one category to be selected at any given
time and use the latest selection by the driver.
    The ELD must prompt the driver to enter an annotation upon
selection of a category from Table 2 and record driver's entry.
    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, in which case, 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.

<IP_ADDRESS>. Driver's Certification of Records

    An ELD must include a function whereby a driver can certify the
driver's records at the end of a 24-hour period. 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.'' Driver must be prompted to select
``Agree'' or ``Not ready.'' Driver's affirmative selection of
``Agree'' must be recorded as an event.
    An ELD must only allow the authenticated driver to certify
records associated with that driver.
    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.
    If there are any past records on the ELD (excluding the current
24-hour period) that requires 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.

<IP_ADDRESS>. Driver's Data Transfer Initiation Input

    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.
    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 <IP_ADDRESS>. Upon confirmation, the
ELD must generate the compliant output file and perform the data
transfer.
    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.

<IP_ADDRESS>. 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 into the electronic
ELD records in the exchanged dataset as specified in section
<IP_ADDRESS>.1. 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.

<IP_ADDRESS>. Driver's Annotation of Records

    An ELD must allow for a driver to add annotations in text format
to recorded, entered, or edited ELD events.
    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.

<IP_ADDRESS>. Driver's Entry of Location Information

    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 <IP_ADDRESS>.
    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 <IP_ADDRESS>.
    A manual location entry must show ``M'' in the latitude/
longitude coordinates fields in ELD records.

<IP_ADDRESS>. Driver's Record Entry/Edit

    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.
    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.

<IP_ADDRESS>.1. Mechanism for Driver Edits and Annotations

    If a driver edits or annotates an ELD record or enters missing
information the act must not overwrite the original record.
    The ELD must use the process outlined in section <IP_ADDRESS> to
configure required event attributes to track the edit history of
records.
    Driver edits must be accompanied by an annotation. The ELD must
prompt the driver to annotate edits.

<IP_ADDRESS>.2. Driver Edit Limitations

    An ELD must not allow or require the editing or manual entry of
records with the following event types, as described in section
7.1.24:

------------------------------------------------------------------------
             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.
------------------------------------------------------------------------

    An ELD must not allow automatically recorded driving time to be
shortened. An ELD must not allow the ELD username associated with an
ELD record to be edited or reassigned, except under the following
circumstances:
    (1) Assignment of Unidentified Driver records. ELD events
recorded under the ``Unidentified Driver'' profile may be edited and
assigned to the driver associated with the record; and
    (2) Correction of errors with team drivers. In the case of team
drivers, the driver account associated with the driving time records
may be edited and reassigned between the team drivers if there was a
mistake resulting in a mismatch between the actual driver and the
driver recorded by the ELD and if the team drivers were both
indicated in each other's records as a co-driver. The ELD must
require each co-driver to confirm the change for the corrective
action to take effect.

4.3.3. Motor Carrier's Manual Entries

    An ELD must restrict availability of motor carrier entries
outlined in this subsection only to authenticated ``support
personnel'' account holders.

<IP_ADDRESS>. ELD Configuration

    If an ELD or a technology that includes an ELD function offers
configuration options to the motor carrier or the driver that are
not otherwise addressed or prohibited in this appendix, the
configuration options must not

affect the ELD's compliance with the requirements of this rule for
each configuration setting of the ELD.

<IP_ADDRESS>.1. Configuration of Available Categories Impacting Driving Time
Recording

    An ELD must allow a motor carrier to unilaterally configure the
availability of each of the three categories listed on Table 2 that
the motor carrier chooses to authorize for each of its drivers. By
default, none of these categories must be available to a new driver
account without the motor carrier proactively configuring their
availability.
    A motor carrier may change the configuration for the
availability of each category for each of its drivers. Changes to
the configuration setting must be recorded on the ELD and
communicated to the applicable authenticated driver during the ELD
login process.

<IP_ADDRESS>.2. Configuration of Using ELDs

    An ELD must provide the motor carrier an ability to configure a
driver account exempt from use of an ELD.
    The ELD must default the setting of this configuration option
for each new driver account created on an ELD to no exemption. An
exemption must be proactively configured for an applicable driver
account by the motor carrier. The ELD must prompt the motor carrier
to annotate the record and provide an explanation for the
configuration of exemption.
    If a motor carrier configures a driver account to be exempt, the
ELD must present the configured indication that is in effect for
that driver during the ELD login and logout processes.
    If a motor carrier configures a driver account as exempt the ELD
must continue to record ELD driving time but suspend detection of
missing data elements data diagnostic event for the driver described
in section <IP_ADDRESS> and data transfer compliance monitoring function
described in section <IP_ADDRESS> when such driver is authenticated on
the ELD.

<IP_ADDRESS>. Motor Carrier's Post-Review Electronic Edit Requests

    An ELD may allow the motor carrier (via a monitoring algorithm
or support personnel) to screen, review, and request corrective
edits to the driver's certified (as described in section <IP_ADDRESS>)
and submitted records through the ELD system electronically. If this
function is implemented by the ELD, the ELD must also support
functions for the driver to see and review the requested edits.
    Edits requested by anyone or any system other than the driver
must require the driver's electronic confirmation or rejection.

4.4. ELD Processing and Calculations

4.4.1. Conditions for Automatic Setting of Duty Status

<IP_ADDRESS>. Automatic Setting of Duty Status to Driving

    An ELD must automatically record driving time when the vehicle
is in motion by setting duty status to driving for the driver
unless, before the vehicle is in motion, the driver:
    (1) Sets the duty status to off-duty and indicates personal use
of CMV, in which case duty status must remain off-duty until
driver's indication of the driving condition ends; or
    (2) Sets the duty status to on-duty not driving and indicates
yard moves, in which case duty status must remain on-duty not
driving until driver's indication of the driving condition ends.

<IP_ADDRESS>. Automatic Setting of Duty Status to On-Duty Not Driving

    When the duty status is set to driving, and the CMV has not been
in-motion for 5 consecutive minutes, the ELD must prompt the driver
to confirm continued driving status or enter the proper duty status.
If the driver does not respond to the ELD prompt within 1-minute
after receiving the prompt, the ELD must automatically switch the
duty status to on-duty not driving. The time thresholds for purposes
of this section must not be configurable.

<IP_ADDRESS>. Other Automatic Duty-Status Setting Actions Prohibited

    An ELD must not feature any other automatic records of duty
setting mechanism than those described in sections <IP_ADDRESS> and
<IP_ADDRESS>. Duty status changes that are not initiated by the driver,
including duty status alteration recommendations by motor carrier
support personnel or a software algorithm, are subject to motor
carrier edit requirements in section <IP_ADDRESS>.

4.4.2. Geo-Location Conversions

    For each change in duty status, the ELD must convert
automatically captured vehicle position in latitude/longitude
coordinates into geo-location information, indicating approximate
distance and direction to an identifiable location corresponding to
the name of a nearby city, town, or village, with a State
abbreviation.
    Geo-location information must be derived from a database that
contains all cities, towns, and villages with a population of 5,000
or greater and listed in ANSI INCITS 446-2008 (incorporated by
reference, see Sec.  395.38), reference (3)(a) in section 6 of this
appendix.
    An ELD's viewable outputs (such as printouts or displays) must
feature geo-location information as place names in text format.

4.4.3. Date and Time Conversions

    An ELD must have the capability to convert and track date and
time captured in UTC standard to the time standard in effect at
driver's home terminal, taking the daylight savings time changes
into account by using the parameter ``Time Zone Offset from UTC'' as
specified in section 7.1.40.
    An ELD must record the driver's record of duty status using the
time standard in effect at the driver's home terminal for a 24-hour
period beginning with the time specified by the motor carrier for
that driver's home terminal.
    The data element ``Time Zone Offset from UTC'' must be included
in the ``Driver's certification of Own Records'' events as specified
in section <IP_ADDRESS>.

4.4.4. Setting of Event Parameters in Records, Edits, and Entries

    This section describes the security measures for configuring and
tracking event attributes for ELD records, edits, and entries in a
standardized manner.
    <IP_ADDRESS>. Event Sequence Identifier (ID) Number
    Each ELD event must feature an event sequence ID Number.
    The event sequence ID number for each ELD must use continuous
numbering across all users of that ELD and across engine and ELD
power on and off cycles.
    An ELD must use the next available event sequence ID number
(incremented by one) each time a new event log is recorded.
    Event sequence ID number must track at least the last 65,536
unique events recorded on the ELD.
    The continuous event sequence ID numbering structure used by the
ELD must be mapped into a continuous hexadecimal number between 0000
(Decimal 0) and FFFF (Decimal 65535).

<IP_ADDRESS>. Event Record Status, Event Record Origin, Event Type Setting

    An ELD must retain the original records even when allowed edits
and entries are made over a driver's ELD records.
    An ELD must keep track of all event record history, and the
process used by the ELD must produce the event record status, event
record origin, and event type for the ELD records in the standard
categories specified in sections 7.1.22, 7.1.21 and 7.1.24,
respectively for each record as a standard security measure. For
example, an ELD may use the process outlined in sections <IP_ADDRESS>.1-
<IP_ADDRESS>.6 to meet the requirements of this section.

<IP_ADDRESS>.1. Records Automatically Logged by ELD

    At the instance an ELD creates a record automatically, the ELD
must:
    (1) Set the ``Event Record Status'' to ``1'' (active); and
    (2) Set the ``Event Record Origin'' to ``1'' (automatically
recorded by ELD).

<IP_ADDRESS>.2. Driver Edits

    At the instance of a driver editing existing record(s), the ELD
must:
    (1) Identify the ELD record(s) being modified for which the
``Event Record Status'' is currently set to ``1'' (active);
    (2) Acquire driver input for the intended edit and construct the
ELD record(s) that will replace the record(s) identified in (1)
above;
    (3) Set the ``Event Record Status'' of the ELD record(s)
identified in (1) above, which is being modified, to ``2''
(inactive-changed);
    (4) Set the ``Event Record Status'' of the ELD record(s)
constructed in (2) above to ``1'' (active); and
    (5) Set the ``Event Record Origin'' of the ELD record(s)
constructed in (2) above to ``2'' (edited or entered by the driver).

<IP_ADDRESS>.3. Driver Entries

    When a driver enters missing record(s), the ELD must:
    (1) Acquire driver input for the missing entries being
implemented and construct the new ELD record(s) that will represent
the driver entries;
    (2) Set the ``event record status'' of the ELD record(s)
constructed in (1) above to ``1'' (active); and

    (3) Set the ``event record origin'' of the ELD record(s)
constructed in (1) above to ``2'' (edited or entered by the driver).

<IP_ADDRESS>.4. Driver's Assumption of Unidentified Driver Logs

    When a driver reviews and assumes ELD record(s) logged under the
unidentified driver profile, the ELD must:
    (1) Identify the ELD record(s) logged under the unidentified
driver profile that will be reassigned to the driver;
    (2) Use elements of the unidentified driver log(s) from (1)
above and acquire driver input to populate missing elements of the
log originally recorded under the unidentified driver profile, and
construct the new event record(s) for the driver;
    (3) Set the event record status of the ELD record(s) identified
in (1) above, which is being modified, to ``2'' (inactive-changed);
    (4) Set the event record status of the ELD record(s) constructed
in (2) above to ``1'' (active); and
    (5) Set the event record origin of the ELD record(s) constructed
in (2) above to ``4'' (assumed from unidentified driver profile).

<IP_ADDRESS>.5. Motor Carrier Edit Suggestions

    If a motor carrier requests an edit on a driver's records
electronically, the ELD must:
    (1) Identify the ELD record(s) being requested to be modified
for which the ``event record status'' is currently set to ``1''
(active);
    (2) Acquire motor carrier input for the intended edit and
construct the ELD record(s) that will replace the record identified
in (1) above --if approved by the driver;
    (3) Set the event record status of the ELD record(s) in (2)
above to ``3'' (inactive-change requested); and
    (4) Set the event record origin of the ELD record constructed in
(2) above to ``3'' (edit requested by an authenticated user other
than the driver).

<IP_ADDRESS>.6. Driver's Actions Over Motor Carrier Edit Suggestions

    (1) If edits are requested by the motor carrier to the driver
over a driver's records electronically, the ELD must implement
functions for the driver to review the requested edits, see their
effects and indicate on the ELD whether the driver confirms or
rejects the requested edit(s).
    (2) If the driver approves the motor carrier's edit suggestion
the ELD must:
    (a) Set the event record status of the ELD record(s) identified
under section <IP_ADDRESS>.5(1) being modified, to ``2'' (inactive-
changed); and
    (b) Set the ``event record status'' of the ELD record(s)
constructed in <IP_ADDRESS>.5(2) to ``1'' (active).
    (3) If the driver disapproves the motor carrier's edit(s)
suggestion, the ELD must set the ``event record status'' of the ELD
record(s) identified in <IP_ADDRESS>.5(2) to ``4'' (inactive-change
rejected).

4.4.5. Data Integrity Check Functions

    An ELD must support standard security measures which require the
calculation and recording of standard data check values for each ELD
event recorded, for each line of the output file, and for the entire
data file to be generated for transmission to an authorized safety
official or the motor carrier.
    For purposes of implementing data check calculations, the
alphanumeric-to-numeric mapping provided in Table 3 must be used.
    Each ELD event record type specified in sections <IP_ADDRESS> and
<IP_ADDRESS> must include an event data check value, which must be
calculated as specified in section <IP_ADDRESS>. An event data check
value must be calculated at the time of the following instances and
must accompany that event record thereafter:
    (1) When an event record is automatically created by the ELD;
    (2) When an authorized edit is performed by the driver on the
ELD or on its support systems; and
    (3) When an electronic edit proposal is created by the motor
carrier through the ELD system.
    Each line of the ELD output file must include a line data check
value, which must be calculated as specified in section <IP_ADDRESS>.
    Each ELD report must also include a file data check value, which
must be calculated as specified in section <IP_ADDRESS>.

<IP_ADDRESS>. Event Data Check

    The event data check value must be calculated as follows.

<IP_ADDRESS>.1. Event Checksum Calculation

    A checksum calculation includes the summation of numeric values
or mappings of a specified group of alphanumeric data elements. The
ELD must calculate an event checksum value associated with each ELD
event at the instance of the event record being created.
    The event record elements that must be included in the checksum
calculation are the following:
    (1) ,
    (2) ,
    (3) ,
    (4) ,
    (5) ,
    (6) ,
    (7) ,
    (8) ,
    (9) , and
    (10) < ELD username>.
    The ELD must sum the numeric values of all individual characters
making up the listed data elements using the character to decimal
value coding specified in Table 3, and use the 8-bit lower byte of
the hexadecimal representation of the summed total as the event
checksum value for that event.

<IP_ADDRESS>.2. Event Data Check Calculation

    The event data check value must be the hexadecimal
representation of the output 8-bit byte, after the below bitwise
operations are performed on the binary representation of the event
checksum value, as set forth below:
    (1) Three consecutive circular shift left (rotate no carry -
left) operations; and
    (2) A bitwise exclusive OR (XOR) operation with the hexadecimal
value C3 (decimal 195; binary 11000011).

<IP_ADDRESS>. Line Data Check

    A line data check value must be calculated at the time of the
generation of the ELD output file, to transfer data to authorized
safety officials or to catalogue drivers' ELD records at a motor
carrier's facility. A line data check value must be calculated as
follows.

<IP_ADDRESS>.1. Line Checksum Calculation

    The ELD must calculate a line checksum value associated with
each line of ELD output file at the instance when an ELD output file
is generated.
    The data elements that must be included in the line checksum
calculation vary as per the output data file specified in section
<IP_ADDRESS>.
    The ELD must convert each character featured in a line of output
using the character to decimal value coding specified on Table 3 and
sum the converted numeric values of each character listed on a given
ELD output line item (excluding the line data check value being
calculated), and use the 8-bit lower byte value of the hexadecimal
representation of the summed total as the line checksum value for
that line of output.

<IP_ADDRESS>.2. Line Data Check Calculation

    The line data check value must be calculated by performing the
following operations on the binary representation of the line
checksum value as follows:
    (1) Three consecutive circular shift left (rotate no carry-left)
operations on the line checksum value; and
    (2) A bitwise XOR operation with the hexadecimal value 96
(decimal 150; binary 10010110).

<IP_ADDRESS>.3. Line Data Check Value Inclusion in Output File

    The calculated line data check value must be appended as the
last line item of each of the individual line items of the ELD
output file as specified in the output file format in section
<IP_ADDRESS>.

<IP_ADDRESS>. File Data Check

    A file data check value must also be calculated at the time of
the creation of an ELD output file. A file data check value must be
calculated as follows.

<IP_ADDRESS>.1. File Checksum Calculation

    The ELD must calculate a single 16-bit file checksum value
associated with an ELD output file at the instance when an ELD
output file is generated.
    The file data check value calculation must include all
individual line data check values contained in that file.
    The ELD must sum all individual line data check values contained
in a data file output created, and use the lower two 8-bit byte
values of the hexadecimal representation of the summed total as the
``file checksum'' value.

<IP_ADDRESS>.2. File Data Check Value Calculation

    The file data check value must be calculated by performing the
following operations on the binary representation of the file
checksum value:
    (1) Three consecutive circular shift left (aka rotate no carry -
left) operations on each 8-bit bytes of the value; and
    (2) A bitwise XOR operation with the hexadecimal value 969C
(decimal 38556; binary<PHONE_NUMBER>011100).
    The file data check value must be the 16-bit output obtained
from the above process.

<IP_ADDRESS>.3. File Data Check Value Inclusion in Output File

    The calculated 16-bit file data check value must be converted to
hexadecimal 8-bit bytes and must be appended as the last line item
of the ELD output file as specified in the output file format in
section <IP_ADDRESS>.11.
BILLING CODE 4190-EX-P
[GRAPHIC] [TIFF OMITTED] TP28MR14.001

BILLING CODE 4190-EX-C

4.5. ELD Recording

4.5.1. Events and Data to Record

    An ELD must record data at the following discrete events:

<IP_ADDRESS>. Event: Change in Driver's Duty Status

    When a driver's duty status changes, the ELD must associate the
record with the driver, the record originator--if created during an
edit or entry--the vehicle, the motor carrier, and the shipping
document number and must include the following data elements:
    (1)  as described in section 7.1.23;
    (2)  as described in section 7.1.22;
    (3)  as described in section 7.1.21;
    (4)  as described in section 7.1.24;
    (5)  as described in section 7.1.19;
    (6) <{Event{time}  Date> as described in section 7.1.8;
    (7) <{Event{time}  Time> as described in section 7.1.39;
    (8) <{Accumulated{time}  Vehicle Miles> as described in section
7.1.42;
    (9) <{Elapsed{time}  Engine Hours> as described in section
7.1.18;
    (10) <{Event{time}  Latitude> as described in section 7.1.30;
    (11) <{Event{time}  Longitude> as described in section 7.1.32;
    (12)  as described in
section 7.1.9;
    (13)  as described
in section 7.1.34;
    (14)
as described in section 7.1.7;
    (15) <{Event{time}  Comment/Annotation> as described in section
7.1.6;
    (16)  as described in section
7.1.12; and
    (17)  as described in section 7.1.20.

<IP_ADDRESS>. Event: Intermediate Logs

    When a CMV is in motion, as described in section <IP_ADDRESS>, and
there has not been a duty status change event or another
intermediate log event recorded in the previous 1-hour period, the
ELD must record a new intermediate log event.
    The ELD must associate the record to the driver, the vehicle,
the motor carrier, and the shipping document number, and must
include the same data elements outlined in section <IP_ADDRESS> except
for item (16).

<IP_ADDRESS>. Event: Change in Driver's Indication of Allowed Conditions
That Impact Driving Time Recording

    At each instance when the status of a driver's indication of
personal use of CMV or yard moves changes, the ELD must record a new
event. The ELD must associate the record with the driver, the
vehicle, the motor carrier, and the shipping document number, and
must include the same data elements outlined in section <IP_ADDRESS>.

<IP_ADDRESS>. Event: Driver's Certification of Own Records

    At each instance when a driver certifies or re-certifies that
driver's records for a given 24-hour period are true and correct,
the ELD must record the event. The ELD must associate the record
with the driver, the vehicle, the motor carrier, and the shipping
document number and must include the following data elements:
    (1)  as described in section 7.1.23;
    (2)  as described in section 7.1.24;
    (3)  as described in section 7.1.19;
    (4)  as described in section 7.1.40.
    (5) <{Event{time}  Date>and  as described in section 7.1.8; and
    (6) <{Event{time}  Time> as described in section 7.1.39.

<IP_ADDRESS>. Event: Driver's Login/Logout Activity

    At each instance when an authorized user logs in and out of the
ELD, the ELD must record the event. The ELD must associate the
record with the driver, the vehicle, the motor carrier, and the
shipping document number, and must include the following data
elements:
    (1)  as described in section 7.1.23;
    (2)  as described in section 7.1.24;
    (3)  as described in section 7.1.19;
    (4) <{Event{time}  Date> as described in section 7.1.8;
    (5) <{Event{time}  Time> as described in section 7.1.39;
    (6) <{Total{time}  Vehicle Miles> as described in section
7.1.42; and
    (7) <{Total{time}  Engine Hours> as described in section 7.1.18.

<IP_ADDRESS>. Event: CMV's Engine Power Up and Shut Down Activity

    When a CMV's engine is powered up or shut down, an ELD must
record the event within 1 minute of occurrence and retain the
earliest shut down and latest power-up event if CMV has not moved
since the last ignition power on cycle. The ELD must associate the
record with the driver or the unidentified driver profile, the
vehicle, the motor carrier, and the shipping document number, and
must include the following data elements:
    (1)  as described in section 7.1.23;
    (2)  as described in section 7.1.24;
    (3)  as described in section 7.1.19;
    (4) <{Event{time}  Date> as described in section 7.1.8;
    (5) <{Event{time}  Time> as described in section 7.1.39;
    (6) <{Total{time}  Vehicle Miles> as described in section
7.1.42;
    (7) <{Total{time}  Engine Hours> as described in section 7.1.18;
    (8) <{Event{time}  Latitude> as described in section 7.1.30;
    (9) <{Event{time}  Longitude> as described in section 7.1.32;
and
    (10)  as described in
section 7.1.9.

<IP_ADDRESS>. Event: ELD Malfunction and Data Diagnostics Occurrence

    At each instance when an ELD malfunction or data diagnostic
event is detected or cleared by the ELD, the ELD must record the
event. The ELD must associate the record with the driver, the
vehicle, the motor carrier, and the shipping document number, and
must include the following data elements:
    (1)  as described in section 7.1.23;
    (2)  as described in section 7.1.24;
    (3)  as described in section 7.1.19;
    (4)  as described in section
7.1.33;
    (5) <{Event{time}  Date> as described in section 7.1.8;
    (6) <{Event{time}  Time> as described in section 7.1.39;
    (7) <{Total{time}  Vehicle Miles> as described in section
7.1.42; and
    (8) <{Total{time}  Engine Hours> as described in section 7.1.18.

4.6. ELD's Self-Monitoring of Required Functions

    An ELD must have the capability to monitor its compliance with
the technical requirements of this section for detectable
malfunctions and data inconsistencies listed in Table 4 and must
keep records of its malfunction and data diagnostic event detection.

  Table 4--Standard Coding for Required Compliance Malfunction and Data
                       Diagnostic Event Detection
------------------------------------------------------------------------
      Malfunction/diagnostic code            Malfunction description
------------------------------------------------------------------------
P.....................................  ``Power Compliance''
                                         Malfunction.
E.....................................  ``Engine synchronization
                                         compliance'' malfunction.
T.....................................  ``Timing compliance''
                                         malfunction.
L.....................................  ``Positioning compliance''
                                         malfunction.
R.....................................  ``Data recording compliance''
                                         malfunction.
S.....................................  ``Data transfer compliance''
                                         malfunction.

O.....................................  ``Other'' ELD detected
                                         malfunction.
------------------------------------------------------------------------
      Malfunction/diagnostic code             Data diagnostic event
------------------------------------------------------------------------
1.....................................  ``Power data diagnostic'' event.
2.....................................  ``Engine synchronization data
                                         diagnostic'' event.
3.....................................  ``Missing required data elements
                                         data diagnostic'' event.
4.....................................  ``Data transfer data
                                         diagnostic'' event.
5.....................................  ``Unidentified driving records
                                         data diagnostic'' event.
6.....................................  ``Other'' ELD identified
                                         diagnostic event.
------------------------------------------------------------------------

4.6.1. Compliance Self-Monitoring, Malfunctions and Data Diagnostic
Events

<IP_ADDRESS>. Power Compliance Monitoring

    An ELD must monitor data it receives from the engine ECM or
alternative sources as allowed in sections <IP_ADDRESS>- <IP_ADDRESS>, its
onboard sensors, and data record history to identify instances when
it may not have complied with the power requirements specified in
section <IP_ADDRESS>, in which case, the ELD must record a power data
diagnostics event for the corresponding driver(s), or under the
unidentified diver profile if no drivers were authenticated at the
time of detection.
    An ELD must set a power compliance malfunction if the power data
diagnostics event described above indicate an aggregated in-motion
driving time understatement of 30 minutes or more on the ELD over a
24-hour period across all driver profiles, including the
unidentified driver profile.

<IP_ADDRESS>. Engine Synchronization Compliance Monitoring

    An ELD must monitor the data it receives from the engine ECM or
alternative sources as allowed in sections <IP_ADDRESS>-<IP_ADDRESS>, its
onboard sensors and data record history to identify instances and
durations of its non-compliance with the ELD engine synchronization
requirement specified in section 4.2.
    An ELD required to establish a link to the engine ECM as
described in section 4.2 of this section must monitor its
connectivity to the engine ECM and its ability to retrieve the
vehicle parameters described under section 4.3.1 and must record an
engine-synchronization data diagnostics event when it no longer can
acquire updated values for the ELD parameters required for records
within 5 seconds of the need.
    An ELD must set an engine synchronization compliance malfunction
if connectivity to any of the required data sources specified in
section 4.3.1 is lost for more than 30 minutes during a 24-hour
period aggregated across all driver profiles, including the
unidentified driver profile.

<IP_ADDRESS>. Timing Compliance Monitoring

    The ELD must periodically cross-check its compliance with the
requirement specified in section <IP_ADDRESS> with respect to an accurate
external UTC source and must record a timing compliance malfunction
when it can no longer meet the underlying compliance requirement.

<IP_ADDRESS>. Positioning Compliance Monitoring

    An ELD must continually monitor the availability of valid
position measurements meeting the listed accuracy requirements in
section <IP_ADDRESS> and must track the distance and elapsed time from
the last valid measurement point.
    An ELD records requiring location information must use the last
valid position measurement and include the latitude/longitude
coordinates and distance traveled, in miles, since the last valid
position measurement.
    An ELD must monitor elapsed time during periods when the ELD
fails to acquire a valid position measurement within the past 5
miles of CMV's movement. When such elapsed time exceeds a cumulative
60 minutes over a 24 hour period, the ELD must set and record a
positioning compliance malfunction.
    If a new ELD event must be recorded at an instance when ELD had
failed to acquire a valid position measurement within the most
recent elapsed 5 miles of driving, but the ELD has not yet set a
positioning compliance malfunction, the ELD must record the
character ``X'' in both the latitude and longitude fields, unless
location is entered manually by the driver, in which case it must
log the character ``M'' instead. Under the circumstances listed in
this paragraph, if the ELD event is due to a change in duty status
for the driver, the ELD must prompt the driver to enter location
manually in accordance with section <IP_ADDRESS>. If the location
information is not entered by the driver and the vehicle is in
motion, the ELD must record a missing required data elements data
diagnostic event for the driver.
    If a new ELD event must be recorded at an instance when the ELD
has set a positioning compliance malfunction, the ELD must record
the character ``E'' in both the latitude and longitude fields
regardless of whether the driver is prompted and manually enters
location information.

<IP_ADDRESS>. Data Recording Compliance Monitoring

    An ELD must monitor its storage capacity and integrity and must
detect a data recording compliance malfunction if it can no longer
record or retain required events or retrieve recorded logs that are
not otherwise catalogued remotely by the motor carrier.
    An ELD must monitor the completeness of the ELD event record
information in relation to the required data elements for each event
type and must record a missing data elements data diagnostics event
for the driver if any required field is missing at the time of
recording.

<IP_ADDRESS>. Monitoring Records Logged Under the Unidentified Driver
Profile

    When there are ELD records involving driving time logged on an
ELD under the unidentified driver profile, the ELD must prompt the
driver(s) logging into that ELD with a warning indicating the
existence of new unassigned driving time. The ELD must provide a
mechanism for the driver to review and either acknowledge the
assignment of one or more of the unidentified driver records
attributable to the driver under the authenticated driver's profile
as described in section <IP_ADDRESS>.2(1) or indicate that these records
are not attributable to the driver.
    If more than 30 minutes of driving in a 24-hour period show
unidentified driver on the ELD, the ELD must detect and record an
unidentified driving records data diagnostic event and data
diagnostic indicator must be turned on for all drivers logged in to
that ELD for the current 24-hour period and the following 7 days.
    An unidentified driving records data diagnostic event can be
cleared by the ELD when driving time logged under the unidentified
driver profile for the current 24-hour period and the previous 7
consecutive days drops to 15 minutes or less.

<IP_ADDRESS>. Data Transfer Compliance Monitoring

    An ELD must implement in-service monitoring functions to verify
that certified primary roadside transfer mechanism(s) described in
section 4.9.1 are continuing to function properly. An ELD must
verify this functionality at least once every 7 days. These
monitoring functions may be automatic or may involve manual steps
for a driver.
    An ELD must record a data transfer data diagnostic event and
enter an unconfirmed data transfer mode if the monitoring mechanism
fails to confirm proper in-service operation of certified primary
roadside transfer mechanism(s).

    After an ELD records a data transfer data diagnostic event, the
ELD must increase the frequency of the monitoring function to check
at least once every 24-hour period. If the ELD stays in the
unconfirmed data transfer mode following the next three consecutive
monitoring checks, the ELD must detect a data transfer compliance
malfunction.

<IP_ADDRESS>. Other Technology-Specific Operational Health Monitoring

    In addition to the required monitoring schemes described in
sections <IP_ADDRESS>-<IP_ADDRESS>, the ELD provider may implement additional,
technology-specific malfunction and data diagnostic detection
schemes and may use the ELD's malfunction status indicator and data
diagnostic status indicator (described in sections <IP_ADDRESS> and
<IP_ADDRESS>) to communicate ELD's malfunction or non-compliant state to
the operator(s) of the ELD.

4.6.2. ELD Malfunction Status Indicator

    ELD malfunctions affect integrity of the device and its
compliance; therefore, active malfunctions must be indicated to all
drivers who may use that ELD. An ELD must provide a recognizable
visual indicator, and may provide an audible signal, to the operator
as to its malfunction status.

<IP_ADDRESS>. Visual Malfunction Indicator

    An ELD must display a single visual malfunction indicator for
all drivers using the ELD on the ELD's display or on a stand-alone
indicator. The visual signal must be visible to the driver when the
driver is seated in the normal driving position.
    The ELD malfunction indicator must be clearly illuminated when
there is an active malfunction on the ELD.
    The malfunction status must be continuously communicated to the
driver when the ELD is powered.

4.6.3. ELD Data Diagnostic Status Indicator

    ELD data diagnostic status affects only the authenticated user;
therefore, an ELD must only indicate the active data diagnostics
status applicable to the driver logged into the ELD. An ELD must
provide a recognizable visual indicator, and may provide an audible
signal, to the driver as to its data diagnostics status.

<IP_ADDRESS>. Visual Data Diagnostics Indicator

    An ELD must display a single visual data diagnostics indicator,
apart from the visual malfunction indicator described in section
<IP_ADDRESS>, to visually communicate existence of active data
diagnostics events for the applicable driver. The visual signal must
be visible to the driver when the driver is seated in the normal
driving position.
    The data diagnostic indicator must be clearly illuminated when
there is a detected data inconsistency for the authenticated driver.
    The data diagnostics status must be continuously communicated to
the applicable driver when the ELD is powered.

4.7. Special Purpose ELD Functions

4.7.1. Driver's ELD Volume Control

    If a driver selects the sleeper-berth state for the driver's
record of duty status, and no co-driver has logged into the ELD as
on-duty driving, and if the ELD outputs audible signals, the ELD
must either:
    (1) Allow the driver to mute the ELD's volume or turn off the
ELD's audible output, or
    (2) Automatically mute the ELD's volume or turn off the ELD's
audible output.
    For purposes of this section, if an ELD operates in combination
with another device or other hardware or software technology that is
not separate from the ELD, the volume controls required herein apply
to the combined device or technology.

4.7.2. Driver's Access to Own ELD Records

    An ELD must provide a mechanism for a driver to obtain a copy of
the driver's own hours-of-service records on demand, in either an
electronic or printout format compliant with inspection standards
outlined in section <IP_ADDRESS>.
    The process must not require a driver to go through the motor
carrier to obtain copies of the driver's own hours-of-service
records if driver's records reside on or are accessible directly by
the ELD unit used by the driver.
    If an ELD meets the requirements of this section by making data
files available to the driver, it must also provide a utility
function for the driver to display the data on a computer, at a
minimum, as specified in Sec.  395.8(g).

4.7.3. Privacy Preserving Provision for Use During Personal Uses of a
CMV

    While an ELD must record the events listed in section 4.5.1
under all circumstances, a subset of the recorded elements must
either be omitted in the records or recorded at a lower precision
level, as described in further detail below, when a driver indicates
that the driver is temporarily using the CMV for an authorized
personal purpose. The driver indicates this intent by setting
driver's duty status to off-duty as described in section <IP_ADDRESS>.1
and indicating authorized personal use of CMV as described in
section <IP_ADDRESS>.2.
    During a period when a driver indicates authorized personal use
of CMV, the ELD must:
    (1) Record all new ELD events with latitude/longitude
coordinates information rounded to a single decimal place
resolution; and
    (2) Omit recording vehicle miles and engine hours fields in new
ELD logs by leaving them blank, except for events corresponding to a
CMV's engine power-up and shut-down activity as described in section
<IP_ADDRESS>.
    A driver's indication that the CMV is being operated for
authorized personal purposes may span more than one CMV ignition on
cycle if the driver proactively confirms continuation of the
personal use condition prior to placing the vehicle in motion when
the ELD prompts the driver at the beginning of the new ignition
power on cycle.

4.8. ELD Outputs

4.8.1. Information To Be Displayed by an ELD

    An ELD must support the capability to present the following
information to a user of the ELD via its user-interface:
    (1) Authenticated driver's last name, first name and ELD
username.
    (2) Total miles driven and total engine hours information used
in logs.
    (3) ELD malfunction status indicator.
    (4) ELD data diagnostic status indicator for the authenticated
driver.
    (5) ELD records associated with the authenticated driver, and
records in which the driver serves as a co-driver including the
following information:
    (i) Each change of duty status for the current 24-hour period
and the previous 7 consecutive days and the time of day and location
for each change;
    (ii) Total miles of driving during each driving period and the
current duty day; and
    (iii) The sequence of driver's indication pertaining to
authorized personal use of the CMV and yard moves (as specified in
section <IP_ADDRESS>.2) and the accompanying driver annotations for the
current 24-hour period and the previous 7 consecutive days.
    (6) A summary of ELD records associated with the driver,
reflecting total hours on duty and driving time for the current 24-
hour period and the previous 7 consecutive days.
    (7) A graph-grid view of driver's daily duty status changes for
the current 24-hour period and each of the previous 7 consecutive
days either on a display unit or on a printout report as specified
in section <IP_ADDRESS>.
    (8) The ELD records associated with the unidentified driver
profile recorded on that ELD as follows:
    (i) The sequence of driving and non-driving time logged for the
current 24-hour period and the previous 7 consecutive days.
    (ii) Total miles of driving during each driving period and the
current duty day.
    (9) A summary of ELD records associated with the unidentified
driver profile, reflecting the total hours on duty and driving time
for the current 24-hour period and the previous 7 consecutive days.

4.8.2. ELD Data File

    An ELD must have the capability to generate a consistent
electronic file output compliant with the format described herein to
facilitate the transfer, processing and standardized display of ELD
data sets on the authorized safety officials' computing
environments.

<IP_ADDRESS>. ELD Output File Standard

    Regardless of the particular database architecture used for
recording the ELD events in electronic format, the ELD must produce
a standard ELD data output file for transfer purposes, which must be
generated according to the standard specified in this section.
    Data output must be provided in a single comma-delimited file
outlined in this section using American National Standard Code for
Information Exchange (ASCII) character sets meeting the standards of
ANSI INCITS 4-1986 (R2007) (incorporated by reference, see Sec.
395.38), reference (3)(b) in section 6 of this appendix. It must
include: (1) A header segment, which specifies current or non-
varying elements of an ELD file; and (2) variable length comma-
delimited segments for the drivers, vehicles, ELD events, ELD
malfunction and data diagnostics records, ELD login and logout
activity, and unidentified driver records.

<IP_ADDRESS>.1. Header Segment

    This segment must include the following data elements and
format:
[GRAPHIC] [TIFF OMITTED] TP28MR14.002

[GRAPHIC] [TIFF OMITTED] TP28MR14.003

<IP_ADDRESS>.2. User List

    This segment must list all drivers and co-drivers with driving
time records on the most recent CMV operated by the inspected driver
or motor carrier's support personnel who requested edits within the
time period for which this file is generated. The list must be in
chronological order with most recent user of the ELD on top,
including the driver being inspected, the co-driver, and the
unidentified driver profile. This segment has a variable number of
rows depending on the number of profiles with activity over the time
period for which this file is generated. This section must start
with the following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.004

    Each subsequent row must have the following data elements:
    [GRAPHIC] [TIFF OMITTED] TP28MR14.005

<IP_ADDRESS>.3. CMV List

    This segment must list each CMV that the current driver operated
and that has been recorded on the driver's ELD records within the
time period for which this file is generated. The list must be rank
ordered in accordance with the time of CMV operation with the most
recent CMV being on top. This segment has a variable number of rows
depending on the number of CMVs operated by the driver over the time
period for which this file is generated. This section must start
with the following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.006

    Each subsequent row must have the following data elements:
    [GRAPHIC] [TIFF OMITTED] TP28MR14.007

<IP_ADDRESS>.4. ELD Event List for Driver's Record of Duty Status

    This segment must list ELD event records tagged with event types
1 (a change in duty status as described in section <IP_ADDRESS>), 2 (an
intermediate log as described in section <IP_ADDRESS>), and 3 (a change
in driver's indication of conditions impacting driving time
recording as described in section <IP_ADDRESS>). The segment must list
all event record status types and of all event record origins for
the driver, rank ordered with the most current log on top in
accordance with the date and time fields of the record. This segment
has a variable number of rows depending on the number of ELD events
recorded for the driver over the time period for which this file is
generated. This section must start with the following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.008

    Each subsequent row must have the following data elements:

[GRAPHIC] [TIFF OMITTED] TP28MR14.009

<IP_ADDRESS>.5. Event Annotations, Comments, and Driver's Location
Description

    This segment must list only the elements of the ELD event list
created in <IP_ADDRESS>.4 above that have an annotation, comment, or a
manual entry of location description by the driver. This segment has
a variable number of rows depending on the number of ELD events
under section <IP_ADDRESS>.4 that feature a comment, annotation, or
manual location entry by the driver. This section must start with
the following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.010

    Each subsequent row must have the following data elements:
    [GRAPHIC] [TIFF OMITTED] TP28MR14.011

<IP_ADDRESS>.6. ELD Event List for Driver's Certification of Own Records

    This segment must list ELD event records with event type 4
(driver's certification of own records as described in section
<IP_ADDRESS>) for the inspected driver for time period for which this
file is generated. It must be rank ordered with the most current
record on top. This segment has a variable number of rows depending
on the number of certification and re-certification actions the
authenticated driver may have executed on the ELD over the time
period for which this file is generated. This section must start
with the following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.012

    Each subsequent row must have the following data elements:

[GRAPHIC] [TIFF OMITTED] TP28MR14.013

<IP_ADDRESS>.7. Malfunction and Diagnostic Event Records

    This segment must list all ELD malfunctions that have occurred
on this ELD during the time period for which this file is generated.
It must list diagnostic event records related to the driver being
inspected, rank ordered with the most current record on top. This
segment has a variable number of rows depending on the number of ELD
malfunctions and ELD diagnostic event records recorded and relevant
to the inspected driver over the time period for which this file is
generated. This section must start with the following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.014

    Each subsequent row must have the following data elements:
    [GRAPHIC] [TIFF OMITTED] TP28MR14.015

<IP_ADDRESS>.8. ELD Login/Logout Report

    This segment must list the login and logout activity on the ELD
(ELD events with event type 5 (A driver's login/logout activity))
for the inspected driver for the time period for which this file is
generated. It must be rank ordered with the most recent activity on
top. This section must start with the following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.016

    Each subsequent row must have the following data elements:
    [GRAPHIC] [TIFF OMITTED] TP28MR14.017

<IP_ADDRESS>.9. CMV's Engine Power-Up and Shut Down Activity

    This segment must list the logs created when CMV's engine is
powered up and shut down (ELD events with event type 6 (CMV's engine
power up/shut down)) for the time period for which this file is
generated. It must be rank ordered with the latest activity on top.
This section must start with the following title:

[GRAPHIC] [TIFF OMITTED] TP28MR14.018

    Each subsequent row must have the following data elements:
    [GRAPHIC] [TIFF OMITTED] TP28MR14.019

<IP_ADDRESS>.10. ELD Event Log List for the Unidentified Driver Profile

    This segment must list the ELD event records for the
Unidentified Driver profile, rank ordered with most current log on
top in accordance with the date and time fields of the logs. This
segment has a variable number of rows depending on the number of
Unidentified Driver ELD records recorded over the time period for
which this file is generated. This section must start with the
following title:
[GRAPHIC] [TIFF OMITTED] TP28MR14.020

    Each subsequent row must have the following data elements:
    [GRAPHIC] [TIFF OMITTED] TP28MR14.021

<IP_ADDRESS>.11. File Data Check Value

    This segment lists the file data check value as specified in
section <IP_ADDRESS> of this appendix. This part includes a single line
as follows:
[GRAPHIC] [TIFF OMITTED] TP28MR14.022

<IP_ADDRESS>. ELD Output File Name Standard

    If the ELD output is saved in a file for transfer or maintenance
purposes, it must follow the twenty-five character-long filename
standard below:
    (1) The first five position characters of the filename must
correspond to the first five letters of the last name of the driver
for whom the file is compiled. If the last name of the driver is
shorter than 5 characters, remaining positions must use the
character

``--'' [underscore] as a substitute character. For example, if the
last name of the driver is ``Lee'', the first five characters of the
output file must feature ``Lee----''.
    (2) The sixth and seventh position characters of the filename
must correspond to the last two digits of the driver's license
number for the driver for whom the file is compiled.
    (3) The eighth and ninth position characters of the filename
must correspond to the sum of all individual numeric digits in the
driver's license number for the driver for whom the file is
compiled. The result must be represented in two-digit format. If the
sum value exceeds 99, use the last two digits of the result. For
example, if the result equals ``113'', use ``13''. If the result is
less than 10, use 0 as the first digit. For example, if the result
equals ``5'', use ``05''.
    (4) The tenth through fifteenth position characters of the
filename must correspond to the date the file is created. The result
must be represented in six digit format ``MMDDYY'' where ``MM''
represent the month, ``''DD'' represent the day and ``YY'' represent
the last two digits of the year. For example, February 5, 2013 must
be represented as ``020513''.
    (5) The sixteenth position character of the filename must be a
hyphen ``-''.
    (6) The seventeenth through twenty-fifth position characters of
the filename must, by default, be ``000000000'' but each of these
nine digits can be freely configured by the motor carrier or the ELD
provider to be a number between 0 and 9 or a character between A and
Z to be able to produce distinct files--if or when necessary--that
may otherwise be identical in filename as per the convention
proposed in this section. ELD providers or motor carriers do not
need to disclose details of conventions they may use for configuring
the seventeenth through twenty-fifth digits of the filename.

4.9. Data Transfer Capability Requirements

    An ELD must be able to present the captured ELD records of a
driver in the standard electronic format as described below, and
transfer the data file to an authorized safety official, on demand,
for inspection purposes.

4.9.1. Data Reporting During Roadside Safety Inspections

    On demand during a roadside safety inspection, an ELD must
produce a driver's record of duty status for the current 24-hour
period and the previous 7 consecutive days in electronic format, in
the standard data format described in section <IP_ADDRESS>.
    When a driver uses the single-step driver interface, as
described in section <IP_ADDRESS>, to indicate for the ELD to compile and
transfer driver's ELD records to authorized safety officials, the
ELD must transfer the generated ELD data output to the computing
environment used by authorized safety officials via the standards
referenced in this section. To meet roadside data reporting
requirements, an ELD must do at least one of the following:
    (1) Generate a printout of the record of duty status report for
the current 24-hour period and the previous 7 consecutive days in
the printout format described in section <IP_ADDRESS> that can be handed
to an enforcement officer. Upon request, the ELD must also generate
a printout including a scannable QR code (Quick Response) or a
series of QR codes that embed the ELD data used for the printout as
specified in section <IP_ADDRESS>; or
    (2) Support the one primary and the two backup data transfer
mechanisms in accordance with the transfer standards outlined in
section 4.10.
    (a) The primary transfer mechanisms options are as follows: Web
Services as specified in section <IP_ADDRESS>, or Bluetooth as specified
in section <IP_ADDRESS>, or email as specified in section <IP_ADDRESS>.
    (b) The backup transfer mechanisms are as follows:
    USB 2.0 (incorporated by reference, see Sec.  395.38), reference
(2)(a) in section 6 of this appendix, and as specified in section
<IP_ADDRESS>, and
    (i) Scannable QR codes as specified in section <IP_ADDRESS>; or
    (ii) TransferJet as specified in section <IP_ADDRESS>.
    An ELD must support one of the 7 options for roadside data
transfer in Table 5 and must certify proper operation of each
element under that option. An authorized safety official will
specify which transfer mechanism the official will use within the
certified transfer mechanisms of an ELD.

Table 5--Required Combination of Roadside Data Transfer Capabilities for
                                 an ELD
------------------------------------------------------------------------
            Option                Certified data transfer capabilities
------------------------------------------------------------------------
Option 1:.....................  Printout Report + QR Code printout.
Option 2:.....................  Wireless Web Services + USB 2.0 + QR
                                 Codes.
Option 3:.....................  Wireless Web Services + USB 2.0 +
                                 TransferJet.
Option 4:.....................  Bluetooth + USB 2.0 + QR Codes.
Option 5:.....................  Bluetooth + USB 2.0 + TransferJet.
Option 6:.....................  Wireless Email + USB 2.0 + QR Codes.
Option 7:.....................  Wireless Email + USB 2.0 + TransferJet.
------------------------------------------------------------------------

4.9.2. Motor Carrier Data Reporting

    An ELD or a support system used in conjunction with ELDs must be
capable of maintaining and retaining copies of electronic ELD
records for a period of at least 6 months from the date of receipt.
    An ELD or a support system used in conjunction with an ELD must
produce, on demand, a data file or a series of data files of ELD
records for a subset of its drivers, a subset of its vehicles, and
for a subset of the 6-month record retention period, to be specified
by an authorized safety official, in an electronic format standard
described in section <IP_ADDRESS> or, if the motor carrier has multiple
offices or terminals, within the time permitted under Sec.  390.29.
    At a minimum, an ELD or a support system used in conjunction
with an ELD must be able to transfer the ELD data file or files
electronically by one of the following three transfer mechanisms:
    (1) Web Services as specified in section <IP_ADDRESS> (but not
necessarily wirelessly); or
    (2) USB 2.0, reference (2)(a) in section 6 of this appendix, and
as specified in section <IP_ADDRESS>; or
    (3) Email as specified <IP_ADDRESS> (but not necessarily
wirelessly).

4.10. Communications Standards for the Transmittal of Data Files
From ELDs

    ELDs must transmit ELD records electronically in accordance with
the file format specified in section <IP_ADDRESS> and must be capable of
a one-way transfer of these records through wired and/or wireless
methods to authorized safety officials upon request as specified in
section 4.9.

4.10.1. Primary Wireless Data Transfer Mechanisms

    For each type of wireless transfer mechanisms, an ELD, when
used, must follow the underlying specifications in this section.

<IP_ADDRESS>. Wireless Data Transfer via Web Services

    Transfer of ELD data to FMCSA via Web Services must follow the
following standards:
    (1) Web Services Description Language (WSDL) 1.1 (incorporated
by reference, see Sec.  395.38), reference (1)(a) in section 6 of
this appendix
    (2) Simple Object Access Protocol (SOAP) 1.2 (incorporated by
reference, see Sec.  395.38), reference (1)(b) in section 6 of this
appendix
    (3) Extensible Markup Language (XML) 1.0 5th Edition
(incorporated by reference, see Sec.  395.38), reference (1)(c) in
section 6 of this appendix
    (4) FMCSA's Third-Party Developers' Partnership (3pDP) (see
https://3pdp.fmcsa.dot.gov/)
    If an ELD provider plans to use Web Services, upon ELD provider
registration as described in section 5.1 of this appendix, FMCSA
will provide formatting files necessary to convert the ELD file into
an XML format and upload the data to the

FMCSA servers. These files include the FMCSA's Rules of Behavior,
XML Schema, WSDL file, Interface Control Document (ICD), and the ELD
Web Services Development Handbook. Additionally, ELD Providers must
obtain a Public/Private Key pair compliant with the NIST SP 800-32,
Introduction to Public Key Technology and the Federal PKI
Infrastructure, (incorporated by reference, see Sec.  395.38),
reference (5)(b) in section 6 of this appendix, and submit the
public key with their registration. ELD Providers will be required
to complete a test procedure to ensure their data is properly
formatted before they can begin submitting driver's ELD data to the
FMCSA server.
    ELD data transmission from the ELD to the ELD support system
must be accomplished in a way that protects the privacy of the
driver(s).
    At roadside if both the vehicle operator and law enforcement
have an available data connection, the vehicle operator will
initiate the transfer of ELD data to FMCSA. The ELD support system
will convert the ELD file to XML using an FMCSA provided schema and
upload it using information provided in the WSDL file using SOAP via
Hypertext Transfer Protocol Secure (HTTPS) using HTTP and RFC 5246,
Transport Layer Security (TLS) Protocol Version 1.2 (incorporated by
reference, see Sec.  395.38), references (1)(a), (b), (c), (d) and
(7)(a) in section 6 of this appendix.

<IP_ADDRESS>. Wireless Data Transfer via Bluetooth[supreg]

    Bluetooth SIG Specification of the Bluetooth System covering
core package version 2.1 + EDR or higher (incorporated by reference,
see Sec.  395.38), reference (8)(a) in section 6 of this appendix,
must be followed. ELDs using this standard must be capable of
displaying a Personal Identification Number generated by the
Bluetooth application profile for bonding with other devices. Upon
request of an authorized official, the ELD must become discoverable
by the authorized safety officials' Bluetooth-enabled computing
platform, and generate a random code, which the driver must share
with the official. The ELD must connect to the roadside authorized
safety officials' technology via wireless personal area network and
transmit the required data via Web Services as described in section
<IP_ADDRESS> of this appendix.

<IP_ADDRESS>. Wireless Data Transfer Through EMail

    ELD must attach a file to an email message to be sent using RFC
5321 Simple Mail Transfer Protocol (SMTP) (incorporated by
reference, see Sec.  395.38), reference (7)(b) in section 6 of this
appendix, to a specific email address, which will be shared with the
ELD providers during the technology registration process.
    The file must have the format as described in section <IP_ADDRESS>
and must be encrypted using AES-256 in FIPS Publication 197
(incorporated by reference, see Sec.  395.38), reference (5)(a) in
section 6 of this appendix, with the FMCSA public key compliant with
NIST SP 800-32, reference (5)(b) in section 6 of this appendix, to
be provided to the ELD provider at the time of registration.
    The email must be formatted using the RFC 5322 Internet Message
Format (incorporated by reference, see Sec.  395.38), reference
(7)(c) in section 6 of this appendix, as follows:
[GRAPHIC] [TIFF OMITTED] TP28MR14.023

    A message confirming receipt of the ELD file will be sent to the
address specified in the email. The filename must follow the
convention specified in section <IP_ADDRESS>.

4.10.2. Backup Wired and Proximity Data Transfer Mechanisms

    For each type of close proximity data transfer mechanisms used,
an ELD must follow the specifications in this section.

<IP_ADDRESS>. USB 2.0

    ELDs certified for USB data transfer mechanism must be capable
of transferring ELD records using the Universal Serial Bus
Specification (Revision 2.0) (incorporated by reference, see Sec.
395.38), reference (2)(a) in section 6 of this appendix.
    Each ELD technology must implement a single USB-compliant
interface with the necessary adaptors for a Type A connector. The
USB interface must implement the Mass Storage class (08h) for
driverless operation, to comply with IEEE standard 1667-2009,
(incorporated by reference, see Sec.  395.38), reference (4)(a) in
section 6 of this appendix.
    ELD must be capable of providing power to a standard USB-
compatible drive.
    An ELD must re-authenticate the driver prior to saving the
driver's ELD file to an external device.
    On initiation by an authenticated driver, an ELD must be capable
of saving ELD file(s) to USB-compatible drives (AES-256 hardware
encrypted, reference (5)(a) in section 0 of this appendix) that are
provided by authorized safety officials during an inspection. Prior