| Data Transfer Methods | How to send Roadside Inspection ODTMobile supports data transfer via Email or Web Services. 1. When a Roadside Inspection occurs, the driver should press the "Roadside Inspection" button on the phone/tablet screen, then hand the device to the Safety Officer. 2. The Safety Officer can use the phone/tablet menu options to view the Driver Log Header, Driver Event Log, Driver Log Chart, or Unidentified Driver Records Log. 3. To receive a copy of the Driver Log report, the Safety Officer can pick "Transfer Via Email" or "Transfer Via Web Services". Transfer via Email: a. The Safety Officer should then enter his/her Email address, by pressing the "To" field. A "soft" keyboard will appear on the screen, allowing the officer to enter an Email address. b. The officer may optionally enter a Comment to be included in the report, by pressing the "Comment" field. c. The officer should then press "Done" to remove the soft keyboard. d. The officer can then press "Send" to send the Email, or Cancel to cancel the operation. Transfer via Web Services: a. The officer may optionally enter a Comment or Key Phrase to be included in the report, by pressing the "Comment" field. A "soft" keyboard will appear on the screen. b. The officer should then press "Done" to remove the soft keyboard. c. The officer can then press "Send" to send the report, or Cancel to cancel the operation. |
| Malfunction Notes | Summary of ODTMobile A1 Malfunction Types Power compliance malfunction (P) Accumulate 30 minutes of missed Driving time over 24 hours (4.6.1.1(b)) Engine synchronization compliance malfunction Accumulate 30 minutes of Engine Sync Diagnostics over 24 hours (4.6.1.2(c)) Timing compliance malfunction (E) Check against time reference > 10 minutes (4.6.1.3&4.3.1.5) Positioning compliance malfunction (T) Accumulate 60 minutes time where last good GPS was > 5 miles away (4.6.1.4(c)) Data recording compliance malfunction (R) Fail at saving new records (or other data) Data transfer compliance malfunction (S) When in "unconfirmed data transfer mode" test ELD Output File Transfer every 24 hours. After 4 fails, declare Malfunction (4.6.1.7(c)) ODTMobile malfunction (O) A "catch-all" malfunction, for ODTMobile-specific errors. |
| Certifying Statement | ODTMobile A1 was tested, based on the Requirements Traceability Matrix from FMCSA's "Electronic Logging Device (ELD) Test Plan and Procedures 10/17/2016 Version 2.0". Most of the test steps were taken directly from the example procedures in Chapters 1, 2, and 3 from that document. Some modifications were made, appropriate to the particular architecture of ODTMobile, but we believe the functional objectives were met in each case. As specified in the Test Plan doc, tests related to the Web Services portal at FMCSA or to Email encryption were not performed. |
