Automate the Process of Reporting Re-engineered ELD's to FMCSA through SafeSpect
| Entry Date | May 22, 2026 |
|---|---|
| Issue Number | 26-075-INFO |
| Name | Abe Dunivin |
| Agency | Oregon Dept of Transportation |
| Address | 455 Airport Rd Bldg ASalem, OR, 97302United StatesMap It (opens in a new tab) |
| Phone | 5412072847 |
| [email protected] | |
| Committee | Information Systems Committee |
| Status | Open |
| Summary of Issue | Reporting re-engineered ELD's to FMCSA. When a re-engineered ELD 395.8(e)(2) has been discovered FMCSA Tech support wants the inspector to report the device. With all the things an inspector must do roadside, there are times the inspector forgets to send the information. |
| Justification or Need | Re-engineered ELD's are a huge problem nationwide and need to be reported. Oregon caught 283 of these between April 1st and May 17. According to FMCSA only a fraction of them were reported and this is not just an Oregon problem but a nationwide problem. Every refresh class and almost every email I am reminding our inspectors the need to report these devices. |
| Request for Action | During the inspection process the inspector has to log into eRODS to view the ROD's. It is my understanding that my request to automatically save the ROD's was approved. This request is to automate the process. When the inspector selects a 395.8(e)(2) violation, a window would automatically pop up with the ELD file attached along with all evidence the inspector has already uploaded into SafeSpect. The inspector would quickly review the information for accuracy and then click the send button. This would streamline the process, shorten inspection time, and eliminate the excuse that the inspector forgot to send the information. FMCSA would receive the information promptly to investigate the ELD. By identifying and revoking non-compliant ELDs, this process would help improve roadway safety and ultimately save lives. |