You are here

ELD Manufacturers

What do I need to know?

Manufacturers are responsible for registering their ELDs and certifying that they meet the technical specifications set forth in the ELD rule.

Manufacturers can begin registering and certifying ELDs 60 days following the final publication date of the ELD Rule (i.e., on February 16, 2016).

ELDs vs. AOBRDs

An electronic logging device (ELD) is not the same as an automatic onboard recording device. The technical specifications are different.

Manufacturers will be able to notify owners of existing AOBRDs if their devices are capable of being updated to meet ELD requirement through software updates. These updated devices must be certified and registered by the manufacturers on the FMCSA ELD registration page.

ELD Compliance Requirements

To be included on FMCSA’s list of compliant ELDs, each ELD must:

An ELD can include portable ELDs and mobile devices – so long as it fully meets the technical specifications, and is certified and registered.

If FMCSA finds that an ELD listed on its website does not comply with the technical specifications, FMCSA may initiate removal of an ELD model or version from its list by providing written notice to the ELD provider stating:

  • The reasons that FMCSA proposes to remove the model or version from the FMCSA list; and
  • Any corrective action that the provider must take for the ELD model or version to remain on the list.

If an ELD is removed from the list, FMCSA will alert industry through announcements on its website and other communications.

What do I need to do?

Certify and Register Your ELDs

FMCSA’s registration page provides specific instructions and an interactive form to register ELDs.

A compliance test procedure is available with step-by-step instructions to verify that a system meets the technical specifications in the ELD rule.

Registration is at the model level of the ELD, not the individual device level.

If a combination of technology or sub-components is needed to meet the technical specifications, the manufacturer must register all of the components together as an ELD device. For example, if ELD capabilities are provided through an app running on a specific smart phone, the provider must register the multiple devices or components. A sample statement might be: We certify that our model XXX, used in conjunction with an (phone or device type/model) conforms to the ELD specifications).

The ELD registration process allows providers to update and maintain their device information to accommodate software version revisions.

When manufacturers update device information and software revisions on the registration site, they must certify that the updated device(s) continue to meet the regulation's technical specifications.

Required Registration Information

To register ELDs, manufacturers must register for a company account on the registration site, providing:

  • Company name of the technology provider/manufacturer.
  • Company address.
  • Name of an individual authorized by the provider to verify that the ELD is compliant and to certify it (primary POC); and one or more alternate contacts.
  • Telephone number and email address for the primary contact and each alternate contact.

To register and certify the ELD, providers must provide the following information:

  • Name of ELD product.
  • Model number of product.
  • Software version.
  • ELD identifier (a six-character alphanumeric identifier assigned by the provider to uniquely identify the certified model and version of the ELD; this must match the ELD identifier that is included in the data output from the ELD.
  • Picture and/or screenshot of the product.
  • User's manual describing how to operate the ELD.
  • Description of the supported and certified data transfer mechanisms and step-by-step instructions for a driver to transfer ELD records to an authorized safety official.
  • Summary description of ELD malfunctions.
  • ELD authentication value, alphanumeric value that will be used to verify the authenticity of the ELD (per section 7.14 of the final rule).

Certification also requires authentication using the authentication value; and a “certifying statement” describing how the product was tested to comply with FMCSA regulations.

Resources

Updated: Wednesday, December 21, 2016
Submit Feedback >