| Data Transfer Methods | ERODS TRANSFER WEB SERVICES and EMAIL Instructions on Driver CARD in Manual also 1. From the HOS Log screen, select the 3-dot menu, located in the top-right corner of the screen. 2. Select ERODS File Transfer. The ERODS File Transfer screen appears. 3. Select a Transfer Method, either Web Services or Email. Enter Comment if requested, Select Send. 4. The message ERODS File is Being Processed by Omnitracs appears. If the transfer fails, the HOS Log screen display is considered a compliant secondary record. |
| Malfunction Notes | MALFUNCTIONS AND DIAGNOSTICS If you receive any of the following errors or malfunctions on your ELD you are required to keep paper logs until the malfunction has been corrected. • Power - An ELD must be powered and function within one minute of the vehicle’s engine receiving power and remain powered for as long as the vehicle’s engine stays powered. • Engine Synchronization - An ELD is required to establish a link to the engine ECM and monitor its connectivity to the engine ECM and its ability to retrieve the vehicle parameters. • Timing - The ELD must cross-check its compliance with the external UTC source and must record any timing compliance malfunction. • Positioning - An ELD must monitor the availability of position measurements meeting the listed accuracy requirements and track the distance and time from the last valid measured point. Data Recording - 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. • Data Transfer - An ELD must implement inservice monitoring functions to verify that the data transfer mechanism(s) are continuing to function properly. • Other - Any other ELD-detected malfunction such as Bluetooth, relay, etc. |
| Certifying Statement | Omnitracs XRS (XRSAN1) FMCSA Certifying Statement on Product Testing for ELD Regulation Compliance Omnitracs has distributed and supported AOBRDs in the marketplace since 1989 and has developed testing processes that would assess all areas of the compliance requirements for 49CFR 395.8 and 49CFR 395.15. We have a quality assurance process that follows the creation of story cards for each section of the ELD Mandate specifications. This QA process has been standard operating procedure for Omnitracs and has increased with the ELD mandate requirements. We have used the ELD Testing document issued by FMCSA as a reference to ensure that our testing parallels or exceeds the requirements. Additionally, tests have been created that evaluate fringe cases that are not included in the FMCSA document. Omnitracs employs automated script testing processes for testing of individual elements to ensure consistent and repeatable testing as well the ability to add fringe case scenarios to ensure that in each section of the ELD Mandate, compliance is achieved. We have modified our product through variance changes in the vehicle ECM, changes by OEM and SAE standards, and maintained compliance to ensure that we are continually able to supply information from the ECM. This has ensured that we comply with all the data capture and motion detection requirements specified in the ELD Mandate for the engine ECM. Our testing process includes testing in actual CMV class 6- 8 vehicles as well as using vehicle ECM simulators in testing labs. We additionally use GPS simulators to validate recovery and diagnostics for various situations that can occur in vehicles or environments when GPS may be compromised. With this and other testing processes we are able to test each requirement for diagnostics and malfunctions as required by the ELD Mandate specifications. Additionally, we have provided to Volpe an eRODS test file requested by FMCSA and that file has been accepted. We understand that the actual eRODS transfer process has not been finalized and it will require additional testing and some modifications once all information is available from FMCSA. Omnitracs information security program is based on NIST 800-53 Revision 4. We have ensured that the specified additional security requirements referenced in the regulation for PKI, FIPS, and other NIST specifications have been achieved for compliance to support eRODS transfer. |
