Provides history and detail of Hos Logs which have been sent to the FMCSA in Standard Output format

Overview

Enforcement Request History provides the detail for each time ELD Hos Logs were sent to FMCSA using Standard Output Format.
DriverTech provides the ability to generate a Standard Output File of specific ELD Hos Logs in the following ways:

• Roadside Enforcement from the ELD
• Export Hos Log from the Portal. This is not the preferred option as it does not allow immediate review of the Logs before exporting.
• Hos Log Details Admin Tab from the Portal. This is the recommend option as it allows you to easily review the Logs before exporting.

Full detail of what is included in the Standard Output File, modes of sending to FMCSA, and Response Status codes can be found in the ELD_ICD_Development_Handbook.pdf

Details

Use the selector to choose a specific [Driver], [Driver Group], or [ALL] and a [DateRange] OR use the default values selected THEN select [Get Results] to obtain a list of records.

Requested On, Requested By

The date on which the Standard Output was generated and sent to FMCSA and the Individual which Executed the request

Driver, StartDate and EndDate

The Driver and Date Range of ELD Hos Logs which were included in the request 

File Comment

The Standard Output File Comment as provided by Enforcement Officer.
This value can be 'made up' as desired if performing [... as Test], see Log Details or Export Log

FMCSA Response

Response provided by FMCSA upon receipt and validation of the Standard Output File; You may Click on the value to view the result. 

FMCSA Provides the following to quantify the overall Validation Result of the submission and indicates the highest level of severity for any individual message:

• VALID
  No errors encountered when validating the format of ELD output file and that all Required and Optional field values were included. 
  A "VALID" response provides no indication of the Driver being in or out of violation.
• ERROR
  An issue was discovered during the validation process which will result in the inspector being unable to open or trust the contents of the ELD Output File.
  Any Submissions with ERROR response will need to be investigated and corrected before re-submitting by a company Manager or Safety Official. 
  Most Common items which we have seen result in an ERROR are: 
  • Missing or Invalid USDOT# - To correct, ensure that a DOT is configured on the Company, Terminal Authority, or Ad-Hoc Authority Groups depending upon your configuration strategy. Please contact Support if you're not sure which to use.
  • Missing or Invalid Drivers License detail - To correct, ensure that the License information is accurate and complete on the Driver Administration page.
• WARNING
  An issue was discovered which makes the file out of compliance with the rule, but the file can still be loaded and viewed by the inspector so the decision of whether to accept or reject the contents lies with them.
• INFORMATION
  Indicates a situation that is being flagged for informational purposes. These messages will be passed to the inspector for review, but do not necessarily indicate any issue with the data file. Example: An informational message would be passed indicating that the file contains malfunction events to aid the inspector in reviewing the file.
  Most Common items which we have seen result in an INFORMATION status are: 
  • Missing VIN - To investigate, confirm the JBUS is providing a VIN or use the Vehicle Administration page to configure a 'manual vin' for the vehicle
• NOTVALIDATED
  This status may occur depending upon FMCSA validation system availability and/or when FMCSA Web Service cannot be contacted and DriverTech system falls back to sending the Standard Output File to FMCSA via Email

Issue Count

Number of 'issues' FMCSA identified when validating the Standard Output File which was submitted

Standard Output File of Included ELD Logs

This is the actual Standard Output File which was submitted to FMCSA. This file will include ONLY ELD Hos Logs if the selected Date Range includes both AOBR and ELD Logs.

Clicking on the Icon will display the file content in a new window.

NOTE: If you want to re-submit this same file, you should right-click and 'save link as' in order to preserve line endings because when displayed in a browser the line endings will be converted to CRLF automatically by your browser, but FMCSA will only accept line endings of CR. We have stored the document in the format accepted by FMCSA and 'save link as' will obtain the Standard Output File in the original format, bypassing any browser manipulation of the text.

PDF of Included Logs

PDF Representation of the Log Data for all logs (AOBR and ELD) in the selected Date Range. The PDF Export complies with §395.34(a)(2)

Sent to Enforcement

Indicates if the Submission was sent as a "Test" or passed along to Enforcement after validation