Section 4.8 explains ELD outputs, which are the information displayed to a user and the standard data output file an ELD must produce.
#FMCSA PERSONAL CONVEYANCE LAWS DRIVER#
Section 4.7 introduces technical functions that are intended to guard a driver against harassment and introduces a privacy preserving provision when a driver operates a CMV for personal purposes. Section 4.6 introduces device self-monitoring requirements and standardizes the minimal set of malfunctions and data diagnostic events an ELD must be able to detect. Section 4.5 describes the events an ELD must record and the data elements each type of event must include. The ELD requirements for internal processing and tracking of information flow are described in section 4.4, which includes conditions for and prohibitions against automatic setting of duty-status in section 4.4.1, required geo-location and date and time conversion functions in sections 4.4.2 and 4.4.3, respectively, use of event attributes for tracking of edit and entry history in section 4.4.4, and the use of data check functions in the recording of ELD logs in section 4.4.5 as standard security measures for all ELDs.
#FMCSA PERSONAL CONVEYANCE LAWS MANUAL#
Section 4.3 describes the inputs of an ELD which includes automatically measured signals by the ELD as covered in section 4.3.1, and manual entries by the authenticated driver as covered in section 4.3.2 and by the motor carrier as covered in section 4.3.3. Section 4.2 explains internal engine synchronization requirements and its applicability when used in recording a driver's record of duty status in CMVs. More specifically, section 4.1 describes the security requirements for account management within an ELD system and introduces the term “Unidentified Driver” account. (c) Section 4 lists functional requirements for an ELD. (b) Section 3 provides definitions for terms and notations used in this document. (a) Section 2 lists the abbreviations used throughout this appendix.
(f) Figure 1 provides a visual layout of how this appendix is generally organized to further explain the required sub-functions of an ELD. (e) This appendix specifies minimally required data elements that must be part of an event record such that a standard ELD output file can be produced by all compliant ELDs. (d) An ELD generates a standard data file output and transfers it to an authorized safety official upon request. (c) An ELD records a driver's electronic RODS and other supporting events with the required data elements specified in this appendix and retains data to support the performance requirements specified in this appendix. (b) An ELD allows for manual inputs from the driver and the motor carrier support personnel and automatically captures date and time, vehicle position, and vehicle operational parameters. (a) An ELD is integrally synchronized with the engine of the CMV such that driving time can be automatically recorded for the driver operating the CMV and using the ELD.
0 kommentar(er)
