{ "schema_version": 2, "run_id": "2026-08-24_841bdbd", "commit": "841bdbd1c138d0a2223255bf2b93b9fd9dd26158", "commit_short": "841bdbd", "timestamp_utc": "2026-08-24T22:53:12Z", "cases": [ { "case_id": "ELD-1.1:1", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.1-1", "step": 1, "pdf_page": 177, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_account_structure_separates_drivers_and_support" ], "requirement": "An ELD must support a user account structure\nthat separates drivers and motor carrier\u2019s support personnel\n(i.e. Non-drivers)." }, { "case_id": "ELD-1.1:2", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.2-1", "step": 2, "pdf_page": 178, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_every_eld_user_has_unique_identifier" ], "requirement": "Each user of the ELD must have a valid active\naccount on the ELD with a unique identifier assigned by the\nmotor carrier." }, { "case_id": "ELD-1.1:3", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.2-2", "step": 3, "pdf_page": 179, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_account_creation_captures_license_number_and_state" ], "requirement": "Each driver account must require the entry of\nthe driver\u2019s license number and the State or jurisdiction that\nissued the driver\u2019s license into the ELD during the account\ncreation process." }, { "case_id": "ELD-1.1:4", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.2-3", "step": 4, "pdf_page": 180, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_license_securely_stored_and_session_bound" ], "requirement": "The driver account must securely store the\ndriver\u2019s license number and the State or jurisdiction on the\nELD" }, { "case_id": "ELD-1.1:5", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.2-4", "step": 5, "pdf_page": 181, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_no_second_account_for_the_same_license" ], "requirement": "An ELD must not allow creation of more than\none driver account associated with a driver\u2019s license for a\ngiven motor carrier." }, { "case_id": "ELD-1.1:6", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.2-5", "step": 6, "pdf_page": 181, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_driver_account_cannot_create_accounts" ], "requirement": "A driver account must not have administrative\nrights to create new accounts on the ELD." }, { "case_id": "ELD-1.1:7", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.2-6", "step": 7, "pdf_page": 182, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_support_account_cannot_record_eld_data" ], "requirement": "A support personnel account must not allow\nrecording of ELD data for its account holder." }, { "case_id": "ELD-1.1:8", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.2-7", "step": 8, "pdf_page": 182, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_duty_review.py::test_streams_partition_owner_vs_unidentified" ], "requirement": "An ELD must reserve a unique driver account\nfor recording events during non-authenticated operation of\na CMV." }, { "case_id": "ELD-1.1:9", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.3-1", "step": 9, "pdf_page": 183, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_logs.py::test_flag_on_requires_auth", "tests/test_eld_logs.py::test_pipeline_fixture_day_hand_computed" ], "requirement": "An ELD must provide secure access to data\nrecorded and stored on the system by requiring user\nauthentication during system login." }, { "case_id": "ELD-1.1:10", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.3-2", "step": 10, "pdf_page": 183, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_driver_accounts_access_only_their_own_data" ], "requirement": "Driver accounts must only have access to data\nassociated with that driver, protecting the authenticity and\nconfidentiality of the collected information." }, { "case_id": "ELD-1.1:11", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.4-1", "step": 11, "pdf_page": 184, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_co_drivers.py::test_attribution_round_trip_and_partition" ], "requirement": "An ELD must be capable of separately\nrecording and retaining ELD data for each individual driver\nusing the ELD." }, { "case_id": "ELD-1.1:12", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.4-2", "step": 12, "pdf_page": 185, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_team.py::test_login_act_walk_eld_1_1_12" ], "requirement": "An ELD must provide for and require\nconcurrent authentication for team drivers." }, { "case_id": "ELD-1.1:13", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.4-3", "step": 13, "pdf_page": 186, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_most_recent_unit_produces_the_complete_report" ], "requirement": "If more than one ELD unit is used to record a\ndriver\u2019s electronic records within a motor carrier\u2019s\noperation, the ELD in the vehicle the driver is operating most\nrecently must be able to produce a complete ELD report for\nthat driver" }, { "case_id": "ELD-1.1:14", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.4-4", "step": 14, "pdf_page": 187, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w1_accounts.py::test_complete_report_spans_current_day_plus_seven" ], "requirement": "The complete ELD report for that driver must\nconsist of the current 24-hour period and the previous 7\nconsecutive days." }, { "case_id": "ELD-1.1:15", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.5-1", "step": 15, "pdf_page": 188, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_duty_review.py::test_no_session_pipeline_attributes_to_the_unidentified_profile" ], "requirement": "An ELD must associate all non-authenticated\noperation of a CMV with a single ELD account labeled\nunidentified driver." }, { "case_id": "ELD-1.1:16", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.5-2", "step": 16, "pdf_page": 189, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "If a driver does not log onto the ELD, as soon\nas the vehicle is in motion, the ELD must provide a visual or\nvisual and audible warning reminding the driver to stop and\nlogin to the ELD" }, { "case_id": "ELD-1.1:17", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.5-3", "step": 17, "pdf_page": 190, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "If a driver does not log onto the ELD, as soon\nas the vehicle is in motion, the ELD must record accumulated\ndriving and on-duty, not-driving, time in accordance with\nthe ELD defaults described in Appendix B, section 4.4.1\nunder the unidentified driver profile" }, { "case_id": "ELD-1.1:18", "procedure": "ELD-1.1", "functional_area": "ELD \u2013 Accounts", "requirement_no": "ELD-FUNC-4.1.5-4", "step": 18, "pdf_page": 191, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "If a driver does not log onto the ELD, as soon\nas the vehicle is in motion, the ELD must not allow entry of\nany information into the ELD other than a response to the\nlogin prompt" }, { "case_id": "ELD-1.2:1", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.1-1", "step": 1, "pdf_page": 193, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "An ELD must be powered and become fully functional\nwithin 1 minute of the vehicle\u2019s engine receiving power and must\nremain powered for as long as the vehicle\u2019s engine stays powered." }, { "case_id": "ELD-1.2:2", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.2-1", "step": 2, "pdf_page": 194, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_duty_detector.py::TestThresholdTrio::test_4_9_mph_is_not_motion", "tests/eld/test_duty_detector.py::TestThresholdTrio::test_5_0_mph_exactly_at_threshold_begins_driving", "tests/eld/test_duty_detector.py::TestThresholdTrio::test_5_1_mph_begins_driving", "tests/eld/test_duty_detector_pipeline_e2e.py::test_pipeline_clean_short_haul_frames_to_clocks" ], "requirement": "An ELD must automatically determine whether a CMV is in motion or\nstopped by comparing the vehicle speed information with respect to a\nset speed threshold. (See Appendix B, section 4.3.1.2 for more details)" }, { "case_id": "ELD-1.2:3", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.2-2", "step": 3, "pdf_page": 195, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "If an ELD is required to have a link to the vehicle\u2019s\nengine ECM, vehicle speed information must be acquired from the\nengine ECM. Otherwise, vehicle speed information must be acquired\nusing an independent source. (See Appendix B, section 4.3.1.2 for\nmore details)." }, { "case_id": "ELD-1.2:4", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.3-1", "step": 4, "pdf_page": 196, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_vehicle_miles_monitored_and_whole_mile_units" ], "requirement": "An ELD must monitor vehicle miles as accumulated by a\nCMV over the course of an ignition power on cycle (accumulated\nvehicle miles) and over the course of CMV\u2019s operation (total vehicle\nmiles). Vehicle miles information must use or must be converted to\nunits of whole miles." }, { "case_id": "ELD-1.2:5", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.4-1", "step": 5, "pdf_page": 197, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_engine_hours_monitored_and_tenth_hour_units" ], "requirement": "An ELD must monitor engine hours of the CMV over the\ncourse of an ignition power on cycle (elapsed engine hours) and over\nthe course of the CMV\u2019s operation total engine hours. Engine hours\nmust use or must be converted to hours in intervals of a tenth of an\nhour." }, { "case_id": "ELD-1.2:6", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.5-1", "step": 6, "pdf_page": 197, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_date_time_automatic_without_external_input" ], "requirement": "The ELD must obtain and record the date and time\ninformation automatically without allowing any external input or\ninterference from a motor carrier, driver, or any other person." }, { "case_id": "ELD-1.2:7", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.5-2", "step": 7, "pdf_page": 198, "state": "operational", "finding": null, "owner": "deployment-ntp", "nodes": [], "requirement": "The ELD time must be synchronized to Coordinated\nUniversal Time (UTC) and the absolute deviation from UTC must not\nexceed 10 minutes at any point in time." }, { "case_id": "ELD-1.2:8", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.6-1", "step": 8, "pdf_page": 198, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "An ELD must have the capability to automatically\ndetermine the position of the CMV in standard latitude/longitude\ncoordinates with the accuracy and availability requirements of this\nsection." }, { "case_id": "ELD-1.2:9", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.6-2", "step": 9, "pdf_page": 199, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_position_recorded_without_external_input" ], "requirement": "ELD must obtain and record this information without\nallowing any external input or interference from a motor carrier,\ndriver, or any other person." }, { "case_id": "ELD-1.2:10", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.6-3", "step": 10, "pdf_page": 199, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "CMV position measurement must be accurate to\n\u00b10.5 mile of absolute position of the CMV when an ELD measures a\nvalid latitude/longitude coordinate value." }, { "case_id": "ELD-1.2:11", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.6-4", "step": 11, "pdf_page": 200, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestFileStructure::test_exact_header_lines_for_known_inputs", "tests/eld/test_erods_generator.py::TestEventList::test_yard_move_keeps_conventional_precision_and_fields" ], "requirement": "Position information must be obtained in or converted\ninto standard signed latitude and longitude values and must be\nexpressed as decimal degrees to hundreds of a degree precision (i.e., a\ndecimal point and two decimal places)." }, { "case_id": "ELD-1.2:12", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.6-5", "step": 12, "pdf_page": 201, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "Measurement accuracy combined with the reporting\nprecision requirement implies that position reporting accuracy will be\nin the order of \u00b11mile of absolute position of the CMV during the\ncourse of a CMV\u2019s commercial operation." }, { "case_id": "ELD-1.2:13", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.6-6", "step": 13, "pdf_page": 202, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_personal_use_blanks_miles_and_hours_even_when_facts_supply_them" ], "requirement": "During periods of a driver\u2019s indication of personal use of\nthe CMV, measurement reporting precision requirement is further\nreduced to be expressed as decimal degrees to tenths of a degree (i.e.\na decimal point and single decimal place) as further specified in\nAppendix B, section 4.7.3." }, { "case_id": "ELD-1.2:14", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.6-7", "step": 14, "pdf_page": 203, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "An ELD must be able to acquire a valid position\nmeasurement at least once every 5 miles of driving; however, CMV\nlocation information is only recorded during ELD events as specified in\nAppendix B, section 4.5.1" }, { "case_id": "ELD-1.2:15", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.1.7-1", "step": 15, "pdf_page": 204, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "The vehicle identification number (VIN) for the power\nunit of a CMV must be automatically obtained from the engine ECM\nand recorded if it is available on the vehicle data bus." }, { "case_id": "ELD-1.2:16", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2-1", "step": 16, "pdf_page": 205, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_in_motion_refuses_every_manual_act", "tests/test_eld_acts.py::test_in_motion_clears_when_auto_driving_ends" ], "requirement": "An ELD must prompt the driver to input information\ninto the ELD only when the CMV is stationary and driver\u2019s duty status\nis not on-duty driving, except for the condition specified in Appendix\nB, section 4.4.1.2." }, { "case_id": "ELD-1.2:17", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2-2", "step": 17, "pdf_page": 206, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_only_the_operating_driver_changes_their_status" ], "requirement": "If the driver\u2019s duty status is driving, an ELD must only\nallow the driver who is operating the CMV to change the driver\u2019s duty\nstatus to another duty status." }, { "case_id": "ELD-1.2:18", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2-3", "step": 18, "pdf_page": 206, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "A stopped vehicle must maintain zero (0) miles per hour\nspeed to be considered stationary for purposes of information entry\ninto an ELD." }, { "case_id": "ELD-1.2:19", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2-4", "step": 19, "pdf_page": 207, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_team.py::test_co_driver_entries_while_vehicle_in_motion_eld_1_2_19" ], "requirement": "An ELD must allow an authenticated co-driver who is\nnot driving, but who has logged into the ELD prior to the vehicle being\nin motion to make entries over his or her own records when the\nvehicle is in motion." }, { "case_id": "ELD-1.2:20", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2-5", "step": 20, "pdf_page": 208, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_team.py::test_role_change_refused_in_motion_eld_1_2_20", "tests/test_eld_team.py::test_swap_refusal_lanes" ], "requirement": "The ELD must not allow co-drivers to switch driving\nroles when the vehicle is in motion." }, { "case_id": "ELD-1.2:21", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.1-1", "step": 21, "pdf_page": 208, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_driver_enters_power_unit_trailer_shipping_records" ], "requirement": "An ELD must provide a means for a driver to manually\nenter information pertaining to driver\u2019s ELD records such as CMV\npower unit number, as specified in section 7.4 of this appendix; trailer\nnumber(s), as specified in section 7.42; and shipping document\nnumber, as specified in section 7.39." }, { "case_id": "ELD-1.2:22", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.1-2", "step": 22, "pdf_page": 209, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_auto_populated_record_fields_reviewable_and_correctable" ], "requirement": "If the motor carrier populates these fields\nautomatically, the ELD must provide means for the driver to review\nsuch information and make corrections as necessary." }, { "case_id": "ELD-1.2:23", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.1-1", "step": 23, "pdf_page": 209, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_switch_produces_exact_kernel_event" ], "requirement": "An ELD must provide a means for the authenticated\ndriver to select a driver\u2019s duty status." }, { "case_id": "ELD-1.2:24", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.1-2", "step": 24, "pdf_page": 210, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_logs_copy.py::test_status_terms_match_the_registry_mandate" ], "requirement": "The ELD must use the ELD duty status categories listed\nin Table 1. (See Table 1 in Appendix B, section 4.3.2.2.1 for details)" }, { "case_id": "ELD-1.2:25", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-1", "step": 25, "pdf_page": 210, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_end_category_is_the_next_switch", "tests/test_logs_copy.py::test_category_terms_match_the_registry_mandate" ], "requirement": "An ELD must provide means for a driver to indicate the\nbeginning and end of a period when the driver may use the CMV for\nauthorized personal use, or for performing yard moves." }, { "case_id": "ELD-1.2:26", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-2", "step": 26, "pdf_page": 211, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_table_6_type_3_codes_for_pc_and_ym" ], "requirement": "The ELD must acquire this status (authorized personal\nuse) in a standard format from the category list in Table 2. (See Table\n2 in Appendix B, section 4.3.2.2.2 for details)" }, { "case_id": "ELD-1.2:27", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-3", "step": 27, "pdf_page": 211, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_only_carrier_enabled_categories_selectable" ], "requirement": "An ELD must allow a driver to only select categories that\na motor carrier enables by configuration for that driver, as described\nin Appendix B, section 4.3.3.1.1." }, { "case_id": "ELD-1.2:28", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-4", "step": 28, "pdf_page": 211, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_one_category_at_a_time_latest_selection_wins" ], "requirement": "An ELD must only allow one category to be selected at\nany given time and use the latest selection by the driver." }, { "case_id": "ELD-1.2:29", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-5", "step": 29, "pdf_page": 212, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_category_start_records_driving_with_category" ], "requirement": "The ELD must prompt the driver to enter an annotation\nupon selection of a category from Table 2 in Appendix B and record\ndriver\u2019s entry." }, { "case_id": "ELD-1.2:30", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-6", "step": 30, "pdf_page": 212, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "A driver\u2019s indication of special driving situation must\nreset to none if the ELD or CMV\u2019s engine goes through a power off\ncycle (ELD or CMV\u2019s engine turns off and then on)" }, { "case_id": "ELD-1.2:31", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-7", "step": 31, "pdf_page": 213, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "The driver's indication will reset to none except if the\ndriver has indicated authorized personal use of CMV, in which case,\nthe ELD must require confirmation of continuation of the authorized\npersonal use of CMV condition by the driver." }, { "case_id": "ELD-1.2:32", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.2.2-8", "step": 32, "pdf_page": 214, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "If the driver's indication is not confirmed by the driver\nand the vehicle is in motion, the ELD must default to none." }, { "case_id": "ELD-1.2:33", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.3-1", "step": 33, "pdf_page": 215, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_certifications.py::test_first_certification_round_trip", "tests/test_logs_copy.py::test_certify_terms_match_the_registry_mandate" ], "requirement": "An ELD must include a function whereby a driver can\ncertify the driver\u2019s records at the end of a 24-hour period. This\nfunction, when selected, must display a statement that reads \u201cI\nhereby certify that my data entries and my record of duty status for\nthis 24-hour period are true and correct.\u201d Driver must be prompted to\nselect \u201cAgree\u201d or \u201cNot ready.\u201d Driver\u2019s affirmative selection of\n\u201cAgree\u201d must be recorded as an event." }, { "case_id": "ELD-1.2:34", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.3-2", "step": 34, "pdf_page": 216, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_only_the_authenticated_driver_certifies_their_records" ], "requirement": "An ELD must only allow the authenticated driver to\ncertify records associated with that driver." }, { "case_id": "ELD-1.2:35", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.3-3", "step": 35, "pdf_page": 217, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_certifications.py::test_dirty_in_face_flags_needs_recert_and_recert_appends", "tests/test_eld_certifications.py::test_dirty_out_face_supersede_moving_moment_away", "tests/test_eld_certifications.py::test_clean_day_recertify_refuses_409" ], "requirement": "If any edits are necessary after the driver certifies the\nrecords for a given 24-hour period, the ELD must require and prompt\nthe driver to re-certify the updated records." }, { "case_id": "ELD-1.2:36", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.3-4", "step": 36, "pdf_page": 218, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_login_and_logout_prompt_uncertified_past_days" ], "requirement": "If there are any past records on the ELD (excluding the\ncurrent 24-hour period) that requires certification or re-certification\nby the driver, the ELD must indicate the required driver action on the\nELD\u2019s display and prompt the driver to take the necessary action\nduring the login and logout processes." }, { "case_id": "ELD-1.2:37", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.4-1", "step": 37, "pdf_page": 219, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_inspection.py::test_transfer_seam_routes_method_and_threads_comment" ], "requirement": "An ELD must provide a standardized single-step driver\ninterface for compilation of driver\u2019s ELD records and initiation of the\ndata transfer to authorized safety officials when requested during a\nroadside inspection." }, { "case_id": "ELD-1.2:38", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.4-2", "step": 38, "pdf_page": 219, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_transfer_request_flow_options_and_comment_prompt" ], "requirement": "The ELD must input the data transfer request from the\ndriver, require confirmation, present and request selection of the\nsupported data transfer options by the ELD, and prompt for entry of\nthe output file comment as specified in Appendix B, section 4.3.2.5." }, { "case_id": "ELD-1.2:39", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.4-3", "step": 39, "pdf_page": 220, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_output_file_generated_and_transfer_performed_on_the_live_test_lane" ], "requirement": "Upon confirmation of the output file request, the ELD\nmust generate the compliant output file and perform the data\ntransfer." }, { "case_id": "ELD-1.2:40", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.4-4", "step": 40, "pdf_page": 220, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "The supported single-step data transfer initiation\nmechanism (such as a switch or an icon on a touch-screen display)\nmust be clearly marked and visible to the driver when the vehicle is\nstopped." }, { "case_id": "ELD-1.2:41", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.5-1", "step": 41, "pdf_page": 221, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestHeaderValidation::test_dictionary_windows_are_enforced", "tests/test_eld_inspection.py::test_erods_file_comment_window", "tests/test_eld_inspection.py::test_transfer_comment_window_on_wire_shape" ], "requirement": "An ELD must accommodate the entry of an output file\ncomment up to 60 characters long." }, { "case_id": "ELD-1.2:42", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.5-2", "step": 42, "pdf_page": 222, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_officer_key_phrase_embeds_in_the_output_dataset" ], "requirement": "If an authorized safety official provides a key phrase or\ncode during an inspection to be included in the output file comment, it\nmust be entered and embedded into the electronic ELD records in the\nexchanged dataset as specified in Appendix B, section 4.8.2.1.1." }, { "case_id": "ELD-1.2:43", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.5-3", "step": 43, "pdf_page": 223, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_output_file_comment_defaults_blank" ], "requirement": "The default value for the output file comment must be\nblank." }, { "case_id": "ELD-1.2:44", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.5-4", "step": 44, "pdf_page": 223, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_output_file_comment_scoped_to_its_own_file" ], "requirement": "This output file comment must be used only for the\ncreation of the related data files for the intended time, place, and ELD\nuser." }, { "case_id": "ELD-1.2:45", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.6-1", "step": 45, "pdf_page": 224, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_duty_ledger.py::test_annotate_via_supersede_keeps_the_moment" ], "requirement": "An ELD must allow for a driver to add annotations in\ntext format to recorded, entered, or edited ELD events." }, { "case_id": "ELD-1.2:46", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.6-2", "step": 46, "pdf_page": 224, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_category_note_floors" ], "requirement": "The ELD must require annotations to be 4 characters or\nlonger, including embedded spaces if driver annotation is required and\ndriver is prompted by the ELD." }, { "case_id": "ELD-1.2:47", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.7-1", "step": 47, "pdf_page": 225, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_manual_location_entry_in_text_format" ], "requirement": "An ELD must allow manual entry of a CMV\u2019s location by\nthe driver in text format in support of the driver edit requirements\ndescribed in Appendix B, section 4.3.2.8." }, { "case_id": "ELD-1.2:48", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.7-2", "step": 48, "pdf_page": 225, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_manual_location_only_when_prompted" ], "requirement": "Driver\u2019s manual location entry must be available as an\noption to a driver only when prompted by the ELD under allowed\nconditions as described in Appendix B, section 4.6.1.4." }, { "case_id": "ELD-1.2:49", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.7-3", "step": 49, "pdf_page": 225, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_manual_location_shows_m_in_latlon_fields" ], "requirement": "A manual location entry must show \u201cM\u201d in the\nlatitude/longitude coordinates fields in ELD records." }, { "case_id": "ELD-1.2:50", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8-1", "step": 50, "pdf_page": 226, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_correction_supersedes_and_audits", "tests/test_eld_acts.py::test_manual_entry_lands_retroactively_in_order", "tests/test_eld_logs.py::test_superseded_rows_excluded_through_endpoint" ], "requirement": "An ELD must provide a mechanism for a driver to\nreview, edit, and annotate the driver\u2019s ELD records when a notation of\nerrors or omissions is necessary or enter the driver\u2019s missing ELD\nrecords subject to the requirements specified in this section." }, { "case_id": "ELD-1.2:51", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8-2", "step": 51, "pdf_page": 226, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_duty_ledger.py::test_orm_update_raises", "tests/test_duty_ledger.py::test_orm_delete_raises" ], "requirement": "An ELD must not permit alteration or erasure of the\noriginal information collected concerning the driver\u2019s ELD records or\nalteration of the source data streams used to provide that\ninformation." }, { "case_id": "ELD-1.2:52", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8.1-1", "step": 52, "pdf_page": 227, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_duty_ledger.py::test_supersede_stages_audit_row_and_flips_effective_stream" ], "requirement": "If a driver edits or annotates an ELD record or enters\nmissing information the act must not overwrite the original record." }, { "case_id": "ELD-1.2:53", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8.1-2", "step": 53, "pdf_page": 227, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_duty_ledger.py::test_supersede_chain_resolves_to_the_tip" ], "requirement": "The ELD must use the process outlined in Appendix B,\nsection 4.4.4.2 to configure required event attributes to track the edit\nhistory of records." }, { "case_id": "ELD-1.2:54", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8.1-3", "step": 54, "pdf_page": 228, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_correction_note_required" ], "requirement": "Driver edits must be accompanied by an annotation.\nThe ELD must prompt the driver to annotate edits." }, { "case_id": "ELD-1.2:55", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8.2-1", "step": 55, "pdf_page": 228, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_non_editable_event_types_have_no_edit_lane" ], "requirement": "An ELD must not allow or require the editing or manual\nentry of records with the following event types, as described in\nAppendix C, section 7.1.24 (See Appendix B, section 4.3.2.8.2 for\ndetails)" }, { "case_id": "ELD-1.2:56", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8.2-2", "step": 56, "pdf_page": 229, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_shorten_faces_all_refuse", "tests/test_eld_acts.py::test_shorten_legal_lanes_pass" ], "requirement": "An ELD must not allow automatically recorded driving\ntime to be shortened." }, { "case_id": "ELD-1.2:57", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.2.8.2-3", "step": 57, "pdf_page": 230, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_team.py::test_reassign_dual_accept_full_walk_eld_1_2_57", "tests/test_eld_team.py::test_correction_inherits_co_driver_attribution", "tests/test_duty_review.py::test_claim_constructs_assumed_row_and_original_is_immortal", "tests/test_duty_review.py::test_claim_endpoint_round_trip" ], "requirement": "An ELD must not allow the ELD username associated with an\nELD record to be edited or reassigned, except under the following\ncircumstances (See Appendix B, section 4.3.2.8.2 for details)" }, { "case_id": "ELD-1.2:58", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.1-1", "step": 58, "pdf_page": 231, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_carrier_configures_category_availability" ], "requirement": "An ELD must allow a motor carrier to unilaterally\nconfigure the availability of each of the three categories listed on\nTable 2 in Appendix B that the motor carrier chooses to authorize for\neach of its drivers." }, { "case_id": "ELD-1.2:59", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.1-2", "step": 59, "pdf_page": 232, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_new_account_defaults_no_categories" ], "requirement": "By default, none of these categories listed on Table 2 in\nAppendix B must be available to a new driver account without the\nmotor carrier proactively configuring their availability." }, { "case_id": "ELD-1.2:60", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.1-3", "step": 60, "pdf_page": 232, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_carrier_changes_category_configuration" ], "requirement": "A motor carrier may change the configuration for the\navailability of each category for each of its drivers." }, { "case_id": "ELD-1.2:61", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.1-4", "step": 61, "pdf_page": 233, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_category_config_changes_recorded_and_communicated_at_login" ], "requirement": "Changes to the configuration setting must be recorded\non the ELD and communicated to the applicable authenticated driver\nduring the ELD login process." }, { "case_id": "ELD-1.2:62", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.2-1", "step": 62, "pdf_page": 234, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_carrier_configures_exempt_driver" ], "requirement": "An ELD must provide the motor carrier an ability to\nconfigure a driver account exempt from use of an ELD." }, { "case_id": "ELD-1.2:63", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.2-2", "step": 63, "pdf_page": 234, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_new_account_defaults_no_exemption" ], "requirement": "The ELD must default the setting of this configuration\noption for each new driver account created on an ELD to no\nexemption." }, { "case_id": "ELD-1.2:64", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.2-3", "step": 64, "pdf_page": 235, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_exemption_proactively_configured" ], "requirement": "An exemption for the new driver account must be\nproactively configured for an applicable driver account by the motor\ncarrier." }, { "case_id": "ELD-1.2:65", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.2-4", "step": 65, "pdf_page": 236, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_exemption_requires_annotation" ], "requirement": "The ELD must prompt the motor carrier to annotate the\nrecord and provide an explanation for the configuration of exemption." }, { "case_id": "ELD-1.2:66", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.2-5", "step": 66, "pdf_page": 237, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_exempt_indication_at_login_and_logout" ], "requirement": "If a motor carrier configures a driver account to be\nexempt, the ELD must present the configured indication that is in\neffect for that driver during the ELD login and logout processes." }, { "case_id": "ELD-1.2:67", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.2-6", "step": 67, "pdf_page": 238, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_exempt_records_driving_suspends_diagnostics" ], "requirement": "If a motor carrier configures a driver account as exempt\nthe ELD must continue to record ELD driving time but suspend\ndetection of missing data elements data diagnostic event for the\ndriver described in Appendix B, section 4.6.1.5 and data transfer\ncompliance monitoring function described in Appendix B, section\n4.6.1.7 when such driver is authenticated on the ELD." }, { "case_id": "ELD-1.2:68", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.3-1", "step": 68, "pdf_page": 239, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_carrier_screens_corrective_edits" ], "requirement": "An ELD may allow the motor carrier (via a monitoring\nalgorithm or support personnel) to screen corrective edits to the\ndriver\u2019s certified (as described in Appendix B, section 4.3.2.3)" }, { "case_id": "ELD-1.2:69", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.3-2", "step": 69, "pdf_page": 239, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_carrier_reviews_corrective_edits" ], "requirement": "An ELD may allow the motor carrier (via a monitoring\nalgorithm or support personnel) to review corrective edits to the\ndriver\u2019s certified (as described in Appendix B, section 4.3.2.3)" }, { "case_id": "ELD-1.2:70", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.3-3", "step": 70, "pdf_page": 240, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_carrier_requests_corrective_edits" ], "requirement": "An ELD may allow the motor carrier (via a monitoring\nalgorithm or support personnel) to request corrective edits to the\ndriver\u2019s certified (as described in Appendix B, section 4.3.2.3)" }, { "case_id": "ELD-1.2:71", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.3-4", "step": 71, "pdf_page": 240, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_carrier_submits_records_electronically" ], "requirement": "An ELD may allow the motor carrier to submit records\nthrough the ELD system electronically." }, { "case_id": "ELD-1.2:72", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.3-5", "step": 72, "pdf_page": 241, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_driver_sees_and_reviews_requested_edits" ], "requirement": "If submitting records through the ELD system\nelectronically is implemented by the ELD, the ELD must also support\nfunctions for the driver to see and review the requested edits." }, { "case_id": "ELD-1.2:73", "procedure": "ELD-1.2", "functional_area": "ELD \u2013 Inputs", "requirement_no": "ELD-FUNC-4.3.3.1.3-6", "step": 73, "pdf_page": 242, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w2_engine_sync_power.py::test_non_driver_edits_require_driver_confirmation" ], "requirement": "Edits requested by anyone or any system other than the\ndriver must require the driver\u2019s electronic confirmation or rejection." }, { "case_id": "ELD-1.3:1", "procedure": "ELD-1.3", "functional_area": "ELD \u2013 Vehicle Interface", "requirement_no": "ELD-FUNC-4.2-1", "step": 1, "pdf_page": 244, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "An ELD must be integrally synchronized with\nthe engine of the CMV. (See Appendix B, section 4.2 for\nmore details)" }, { "case_id": "ELD-2.1:1", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.1.1-1", "step": 1, "pdf_page": 252, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_duty_ledger.py::test_pipeline_clean_short_haul_through_the_database" ], "requirement": "An ELD must automatically record driving\ntime when the vehicle is in motion by setting duty\nstatus to driving for the driver." }, { "case_id": "ELD-2.1:2", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.1.1-2", "step": 2, "pdf_page": 253, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_personal_use_status_holds_through_motion" ], "requirement": "If the driver sets the duty status to off-\nduty and indicates personal use of CMV, duty status\nmust remain off-duty until the driver\u2019s indication of the\ndriving condition ends." }, { "case_id": "ELD-2.1:3", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.1.1-3", "step": 3, "pdf_page": 254, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_yard_move_status_holds_through_motion" ], "requirement": "If the duty status is set to on-duty not\ndriving and indicates yard moves, the duty status must\nremain on-duty not driving until driver\u2019s indication of\nthe driving condition ends." }, { "case_id": "ELD-2.1:4", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.1.2-1", "step": 4, "pdf_page": 255, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_prompt_after_five_stationary_minutes" ], "requirement": "When the duty status is set to driving,\nand the CMV has not been in-motion for 5 consecutive\nminutes, the ELD must prompt the driver to confirm\ncontinued driving status or enter the proper duty\nstatus." }, { "case_id": "ELD-2.1:5", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.1.2-2", "step": 5, "pdf_page": 256, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_unanswered_prompt_defaults_odnd_in_one_minute" ], "requirement": "If the driver does not respond to the ELD\nprompt within 1-minute after receiving the prompt, the\nELD must automatically switch the duty status to on-\nduty not driving. The time thresholds for purposes of\nthis section must not be configurable." }, { "case_id": "ELD-2.1:6", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.2-1", "step": 6, "pdf_page": 257, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_duty_changes_convert_position_to_geolocation_text" ], "requirement": "For each change in duty status, the ELD\nmust convert automatically captured vehicle position in\nlatitude/longitude coordinates into geo-location\ninformation, indicating approximate distance and\ndirection to an identifiable location corresponding to\nthe name of a nearby city, town, or village, with a State\nabbreviation.\nPrecondition:\n\u2022 Set up test environment to capture geo-location\ninformation" }, { "case_id": "ELD-2.1:7", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.2-3", "step": 7, "pdf_page": 258, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_viewable_outputs_feature_place_name_text" ], "requirement": "An ELD\u2019s viewable outputs (such as\nprintouts or displays) must feature geo-location\ninformation as place names in text format." }, { "case_id": "ELD-2.1:8", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.3-1", "step": 8, "pdf_page": 259, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_utc_converts_to_home_terminal_with_dst" ], "requirement": "An ELD must have the capability to\nconvert and track date and time captured in UTC\nstandard to the time standard in effect at driver\u2019s home\nterminal, taking the daylight savings time changes into\naccount by using the parameter \u201cTime Zone Offset from\nUTC\u201d as specified in section 7.41.\nPreconditions:\n\u2022 The ELD must be able to manage and convert\ntime in UTC standard to the driver\u2019s home\nterminal time" }, { "case_id": "ELD-2.1:9", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.3-2", "step": 9, "pdf_page": 260, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_rods_recorded_in_home_terminal_24_hour_period" ], "requirement": "An ELD must record the driver\u2019s record of\nduty status using the time standard in effect at the\ndriver\u2019s home terminal for a 24-hour period beginning\nwith the time specified by the motor carrier for that\ndriver\u2019s home terminal." }, { "case_id": "ELD-2.1:10", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.3-3", "step": 10, "pdf_page": 261, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_certification_events_carry_the_timezone_offset" ], "requirement": "The data element \u201cTime Zone Offset from\nUTC\u201d must be included in the \u201cDriver\u2019s Certification of\nOwn Records\u201d events as specified in section 4.5.1.4." }, { "case_id": "ELD-2.1:11", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.1-2", "step": 11, "pdf_page": 262, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_sequence_ids_continuous_across_all_users" ], "requirement": "The event sequence ID number for each\nELD must use continuous numbering across all users of\nthat ELD.\nPrecondition:\n\u2022 Multiple driver user accounts are needed for this\nrequirement with event records" }, { "case_id": "ELD-2.1:12", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.1-3", "step": 12, "pdf_page": 263, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_sequence_ids_continuous_across_engines" ], "requirement": "The event sequence ID number for each\nELD must use continuous numbering across all engines.\nPrecondition:\n\u2022 Multiple vehicles are needed for this requirement" }, { "case_id": "ELD-2.1:13", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.1-4", "step": 13, "pdf_page": 264, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_sequence_ids_continuous_across_power_cycles" ], "requirement": "The event sequence ID number for each\nELD must use continuous numbering across all ELD\npower on and off cycles." }, { "case_id": "ELD-2.1:14", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.1-5", "step": 14, "pdf_page": 265, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_new_event_takes_the_next_sequence_id" ], "requirement": "An ELD must use the next available event\nsequence ID number (incremented by one) each time a\nnew event log is recorded." }, { "case_id": "ELD-2.1:15", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.1-6", "step": 15, "pdf_page": 265, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_sequence_id_wraps_after_ffff" ], "requirement": "Event sequence ID number must track at\nleast the last 65,536 unique events recorded on the ELD." }, { "case_id": "ELD-2.1:16", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.1-7", "step": 16, "pdf_page": 266, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_sequence_ids_are_unpadded_hex_in_chronological_order" ], "requirement": "The continuous event sequence ID\nnumbering structure used by the ELD must be mapped\ninto a continuous hexadecimal number between 0000\n(Decimal 0) and FFFF (Decimal 65535)." }, { "case_id": "ELD-2.1:17", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2-1", "step": 17, "pdf_page": 267, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_originals_retained_through_edits" ], "requirement": "An ELD must retain the original records\neven when allowed edits and entries are made over a\ndriver\u2019s ELD records.\nPrecondition:\n\u2022 Retrieve the original record from the ELD\ndatabase" }, { "case_id": "ELD-2.1:18", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2-2", "step": 18, "pdf_page": 268, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_record_status_produced_in_standard_categories" ], "requirement": "An ELD must keep track of all event\nrecord history, and the process used by the ELD must\nproduce the event record status for the ELD records in\nthe standard categories specified in sections 7.23, 7.22\nand 7.25.\nPrecondition:\n\u2022 Ensure active and inactive events are supported" }, { "case_id": "ELD-2.1:19", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2-3", "step": 19, "pdf_page": 269, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_table_7_origin_codes_for_all_four_sources" ], "requirement": "An ELD must keep track of all event\nrecord history, and the process used by the ELD must\nproduce the event record origin for the ELD records in\nthe standard categories specified in sections 7.23, 7.22\nand 7.25.\nPrecondition:\n\u2022 Ensure active and inactive events are supported" }, { "case_id": "ELD-2.1:20", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2-4", "step": 20, "pdf_page": 270, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_event_types_produced_in_standard_categories" ], "requirement": "An ELD must keep track of all event\nrecord history, and the process used by the ELD must\nproduce the event type for the ELD records in the\nstandard categories specified in sections 7.23, 7.22 and\n7.25\nPrecondition:\n\u2022 Ensure active and inactive events are supported" }, { "case_id": "ELD-2.1:21", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.1-1", "step": 21, "pdf_page": 271, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_auto_created_record_status_is_active" ], "requirement": "At the instance an ELD creates a record\nautomatically, the ELD must set the \u201cEvent Record\nStatus\u201d to \u201c1\u201d (active)" }, { "case_id": "ELD-2.1:22", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.1-2", "step": 22, "pdf_page": 271, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_auto_created_record_origin_is_one" ], "requirement": "At the instance an ELD creates a record\nautomatically, the ELD must set the \u201cEvent Record\nOrigin\u201d to \u201c1\u201d (automatically recorded by ELD)" }, { "case_id": "ELD-2.1:23", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.2-1", "step": 23, "pdf_page": 272, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_acts.py::test_correction_of_corrected_refuses" ], "requirement": "At the instance of a driver editing existing\nrecord(s), the ELD must identify the ELD record(s) being\nmodified for which the \u201cEvent Record Status\u201d is\ncurrently set to \u201c1\u201d (active)" }, { "case_id": "ELD-2.1:24", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.2-2", "step": 24, "pdf_page": 272, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_editing_acquires_driver_input" ], "requirement": "At the instance of a driver editing existing\nrecord(s), the ELD must acquire driver input for the\nintended edit." }, { "case_id": "ELD-2.1:25", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.2-3", "step": 25, "pdf_page": 273, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_editing_constructs_the_replacement_record" ], "requirement": "At the instance of a driver editing existing\nrecord(s), the ELD must construct the ELD record(s) that\nwill replace the record(s) identified in (1) above." }, { "case_id": "ELD-2.1:26", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.2-4", "step": 26, "pdf_page": 273, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_edited_original_set_inactive_changed" ], "requirement": "At the instance of a driver editing existing\nrecord(s), the ELD must set the \u201cEvent Record Status\u201d of\nthe ELD record(s) identified in (1) above, which is being\nmodified, to \u201c2\u201d (inactive-changed)." }, { "case_id": "ELD-2.1:27", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.2-5", "step": 27, "pdf_page": 274, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_edit_replacement_status_is_active" ], "requirement": "At the instance of a driver editing existing\nrecord(s), the ELD must set the \u201cEvent Record Status\u201d of\nthe ELD record(s) constructed in (2) above to \u201c1\u201d\n(active)." }, { "case_id": "ELD-2.1:28", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.2-6", "step": 28, "pdf_page": 275, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_edit_replacement_origin_is_driver" ], "requirement": "At the instance of a driver editing existing\nrecord(s), the ELD must set the \u201cEvent Record Origin\u201d of\nthe ELD record(s) constructed in (2) above to \u201c2\u201d (edited\nor entered by the driver)." }, { "case_id": "ELD-2.1:29", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.3-1", "step": 29, "pdf_page": 276, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_missing_entry_requires_the_reason" ], "requirement": "When a driver enters missing record(s),\nthe ELD must acquire driver input for the missing\nentries being implemented.\nPrecondition:\n\u2022 An event record entry needs to be missing for this\ntest" }, { "case_id": "ELD-2.1:30", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.3-2", "step": 30, "pdf_page": 277, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_missing_entry_constructs_the_new_record" ], "requirement": "When a driver enters missing record(s),\nthe ELD must construct the new ELD record(s) that will\nrepresent the driver entries.\nPrecondition:\n\u2022 An event record entry needs to be missing for this\ntest" }, { "case_id": "ELD-2.1:31", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.3-3", "step": 31, "pdf_page": 278, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_missing_entry_status_is_active" ], "requirement": "When a driver enters missing record(s),\nthe ELD must set the \u201cevent record status\u201d of the ELD\nrecord(s) constructed in (1) above to \u201c1\u201d (active).\nPrecondition:\n\u2022 An event record entry needs to be missing for this\ntest" }, { "case_id": "ELD-2.1:32", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.3-4", "step": 32, "pdf_page": 279, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_missing_entry_origin_is_driver" ], "requirement": "When a driver enters missing record(s),\nthe ELD must set the \u201cevent record origin\u201d of the ELD\nrecord(s) constructed in (1) above to \u201c2\u201d (edited or\nentered by the driver).\nPrecondition:\n\u2022 An event record entry needs to be missing for this\ntest" }, { "case_id": "ELD-2.1:33", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.4-1", "step": 33, "pdf_page": 280, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_unidentified_records_identified_and_assigned" ], "requirement": "When a driver reviews ELD record(s)\nlogged under the unidentified driver profile, the ELD\nmust identify the ELD record(s) logged under the\nunidentified driver profile that will be reassigned to the\ndriver.\nPrecondition:\n\u2022 Unidentified driver profile records need to be on\nthe ELD for this test" }, { "case_id": "ELD-2.1:34", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.4-2", "step": 34, "pdf_page": 281, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_assume_uses_original_elements_and_acquires_input" ], "requirement": "When a driver reviews and assumes ELD\nrecord(s) logged under the unidentified driver profile,\nthe ELD must use elements of the unidentified driver\nlog(s) from (1) above and acquire driver input to\npopulate missing elements of the log originally recorded\nunder the unidentified driver profile.\nPrecondition:\n\u2022 An unidentified driver event is recorded on the\nELD" }, { "case_id": "ELD-2.1:35", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.4-3", "step": 35, "pdf_page": 282, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_assume_constructs_the_new_event_for_the_driver" ], "requirement": "When a driver reviews and assumes ELD\nrecord(s) logged under the unidentified driver profile,\nthe ELD must construct the new event record(s) for the\ndriver.\nPrecondition:\n\u2022 An unidentified driver event is recorded on the\nELD" }, { "case_id": "ELD-2.1:36", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.4-4", "step": 36, "pdf_page": 283, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_assumed_original_set_inactive_changed" ], "requirement": "When a driver reviews and assumes ELD\nrecord(s) logged under the unidentified driver profile,\nthe ELD must set the event record status of the ELD\nrecord(s) identified in (1) above, which is being\nmodified, to \u201c2\u201d (inactive\u2013changed).\nPrecondition:\n\u2022 An unidentified driver event is recorded on the\nELD" }, { "case_id": "ELD-2.1:37", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.4-5", "step": 37, "pdf_page": 284, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_assumed_record_status_is_active" ], "requirement": "When a driver reviews and assumes ELD\nrecord(s) logged under the unidentified driver profile,\nthe ELD must set the event record status of the ELD\nrecord(s) constructed in (2) above to \u201c1\u201d (active).\nPrecondition:\n\u2022 An unidentified driver event is recorded on the\nELD" }, { "case_id": "ELD-2.1:38", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.4-6", "step": 38, "pdf_page": 285, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_assumed_record_origin_is_four" ], "requirement": "When a driver reviews and assumes ELD\nrecord(s) logged under the unidentified driver profile,\nthe ELD must set the event record origin of the ELD\nrecord(s) constructed in (2) above to \u201c4\u201d (assumed from\nunidentified driver profile).\nPrecondition:\n\u2022 An unidentified driver event is recorded on the\nELD" }, { "case_id": "ELD-2.1:39", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.5-1", "step": 39, "pdf_page": 286, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_carrier_edit_request_identifies_active_targets" ], "requirement": "If a motor carrier requests an edit on a\ndriver\u2019s records electronically, the ELD must identify the\nELD record(s) being requested to be modified for which\nthe \u201cevent record status\u201d is currently set to \u201c1\u201d (active).\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:40", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.5-2", "step": 40, "pdf_page": 287, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_carrier_edit_request_acquires_carrier_input" ], "requirement": "If a motor carrier requests an edit on a\ndriver\u2019s records electronically, the ELD must acquire\nmotor carrier input for the intended edit.\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:41", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.5-3", "step": 41, "pdf_page": 288, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_approved_carrier_edit_constructs_the_replacement" ], "requirement": "If a motor carrier requests an edit on a\ndriver\u2019s records electronically, the ELD must construct\nthe ELD record(s) that will replace the record identified\nin (1) above \u2013if approved by the driver.\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:42", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.5-4", "step": 42, "pdf_page": 289, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_requested_edit_sets_status_three" ], "requirement": "If a motor carrier requests an edit on a\ndriver\u2019s records electronically, the ELD must set the\nevent record status of the ELD record(s) in (2) above to\n\u201c3\u201d (inactive\u2013change requested).\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:43", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.5-5", "step": 43, "pdf_page": 290, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_carrier_constructed_record_origin_is_three" ], "requirement": "If a motor carrier requests an edit on a\ndriver\u2019s records electronically, the ELD must set the\nevent record origin of the ELD record constructed in (2)\nabove to \u201c3\u201d (edit requested by an authenticated user\nother than the driver).\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:44", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.6-1", "step": 44, "pdf_page": 291, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_driver_functions_to_review_requested_edits" ], "requirement": "If edits are requested by the motor\ncarrier to the driver over a driver\u2019s records\nelectronically, the ELD must implement functions for\nthe driver to review the requested edits.\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:45", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.6-2", "step": 45, "pdf_page": 292, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_driver_functions_to_confirm_or_reject" ], "requirement": "If edits are requested by the motor\ncarrier to the driver over a driver\u2019s records\nelectronically, the ELD must implement functions for\nthe driver to indicate on the ELD whether the driver\nconfirms or rejects the requested edit(s).\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:46", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.6-3", "step": 46, "pdf_page": 293, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_approval_sets_original_inactive_changed" ], "requirement": "If the driver approves the motor carrier\u2019s\nedit suggestion the ELD must set the event record status\nof the ELD record(s) to \u201c2\u201d (inactive\u2013changed).\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:47", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.6-4", "step": 47, "pdf_page": 294, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_approval_sets_replacement_active" ], "requirement": "If the driver approves the motor carrier\u2019s\nedit suggestion the ELD must set the \u201cevent record\nstatus\u201d of the ELD record(s) to \u201c1\u201d (active).\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:48", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.4.2.6-5", "step": 48, "pdf_page": 295, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_rejection_sets_status_four" ], "requirement": "If the driver disapproves the motor\ncarrier\u2019s edit(s) suggestion, the ELD must set the \u201cevent\nrecord status\u201d of the ELD record(s) to \u201c4\u201d (inactive\u2013\nchange rejected).\nPrecondition:\n\u2022 The motor carrier has requested an edit on a\ndriver\u2019s record electronically" }, { "case_id": "ELD-2.1:49", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5-1", "step": 49, "pdf_page": 296, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_check_values_recorded_per_event_line_and_file" ], "requirement": "An ELD must support standard security\nmeasures that require the calculation and recording of\nstandard data check values for each ELD event\nrecorded, for each line of the output file, and for the\nentire data file to be generated for transmission to an\nauthorized safety official or the motor carrier." }, { "case_id": "ELD-2.1:50", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5-2", "step": 50, "pdf_page": 296, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_auto_event_check_value_accompanies_the_record" ], "requirement": "An event data check value must be\ncalculated at the time of the following instances and\nmust accompany that event record thereafter: When an\nevent record is automatically created by the ELD" }, { "case_id": "ELD-2.1:51", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5-3", "step": 51, "pdf_page": 297, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_driver_edit_gets_its_own_check_value" ], "requirement": "An event data check value must be\ncalculated at the time of the following instances: When\nan authorized edit is performed by the driver on the ELD\nPrecondition:\n\u2022 An edit has been requested on a driver\u2019s record\nelectronically" }, { "case_id": "ELD-2.1:52", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5-4", "step": 52, "pdf_page": 298, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_carrier_edit_proposal_gets_a_check_value" ], "requirement": "An event data check value must be\ncalculated at the time of the following instances and\nmust accompany that event record thereafter: When an\nelectronic edit proposal is created by the motor carrier\nthrough the ELD system." }, { "case_id": "ELD-2.1:53", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.1.1-2", "step": 53, "pdf_page": 298, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_event_checksum_calculated_for_each_created_event" ], "requirement": "The ELD must calculate an event\nchecksum value associated with each ELD event at the\ninstance of the event record being created." }, { "case_id": "ELD-2.1:54", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.1.1-3", "step": 54, "pdf_page": 299, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_check_values.py::TestEventDataCheckValue::test_all_ten_elements_participate" ], "requirement": "The event record elements that must be\nincluded in the checksum calculation are the following." }, { "case_id": "ELD-2.1:55", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.2-1", "step": 55, "pdf_page": 300, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_line_check_values_calculated_at_generation" ], "requirement": "A line data check value must be\ncalculated at the time of the generation of the ELD\noutput file." }, { "case_id": "ELD-2.1:56", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.2-2", "step": 56, "pdf_page": 300, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_line_data_check_values_ride_the_live_officials_transfer" ], "requirement": "A line data check value must be\ncalculated when transferring data to authorized safety\nofficials." }, { "case_id": "ELD-2.1:57", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.2-3", "step": 57, "pdf_page": 301, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_erods_composition.py::test_line_check_values_on_catalogued_export" ], "requirement": "A line data check value must be\ncalculated when cataloguing drivers\u2019 ELD records at a\nmotor carrier\u2019s facility." }, { "case_id": "ELD-2.1:58", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.2.1-1", "step": 58, "pdf_page": 301, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestFileStructure::test_every_data_line_ends_with_its_own_line_data_check_value" ], "requirement": "The ELD must calculate a line checksum\nvalue associated with each line of ELD output file at the\ninstance when an ELD output file is generated." }, { "case_id": "ELD-2.1:59", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.2.3-1", "step": 59, "pdf_page": 302, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w3_duty_recording.py::test_line_check_value_is_the_last_item_of_each_line" ], "requirement": "The calculated line data check value must\nbe appended as the last line item of each of the\nindividual line items of the ELD output file." }, { "case_id": "ELD-2.1:60", "procedure": "ELD-2.1", "functional_area": "ELD \u2013 Processing", "requirement_no": "ELD-FUNC-4.4.5.3-1", "step": 60, "pdf_page": 302, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestFileStructure::test_file_data_check_value_recomputes_over_all_line_values" ], "requirement": "A file data check value must also be\ncalculated at the time of the creation of an ELD output\nfile." }, { "case_id": "ELD-2.2:1", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6-1", "step": 1, "pdf_page": 305, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_table4_malfunctions_monitored_and_recorded" ], "requirement": "An ELD must have the capability to\nmonitor its compliance with the technical\nrequirements of this section for detectable\nmalfunctions listed in Table 4 of Appendix B and must\nkeep records of its malfunction. (See Appendix B,\nsection 4.6 for details)." }, { "case_id": "ELD-2.2:2", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6-2", "step": 2, "pdf_page": 306, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_table4_diagnostics_monitored_and_recorded" ], "requirement": "An ELD must have the capability to\nmonitor its compliance with the technical\nrequirements of this section for data inconsistencies\nlisted in Table 4 of Appendix B and must keep records\nof its data diagnostic event detection. (See Appendix\nB, section 4.6 for details)." }, { "case_id": "ELD-2.2:3", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.1-1", "step": 3, "pdf_page": 307, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_power_monitoring_records_diagnostic_events" ], "requirement": "An ELD must monitor data it receives from the\nengine ECM or alternative sources as allowed in Appendix B,\nsections 4.3.1.1- 4.3.1.4, its onboard sensors, and data record\nhistory to identify instances when it may not have complied with\nthe power requirements specified in Appendix B, section 4.3.1.1,\nin which case, the ELD must record a power data diagnostics\nevent for the corresponding driver(s), or under the unidentified\ndriver profile if no drivers were authenticated at the time of\ndetection.\nPrecondition:\n\u2022\nData event records are recorded from engine ECM or\nother alternative sources\n\u2022\nA power data diagnostic malfunction is recorded" }, { "case_id": "ELD-2.2:4", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.1-2", "step": 4, "pdf_page": 308, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_p_sets_at_exactly_thirty_inclusive", "tests/eld/test_malfunction_evaluator.py::test_p_rolling_window_aggregates_and_expires" ], "requirement": "An ELD must set a power compliance\nmalfunction if the power data diagnostics event\ndescribed above indicate an aggregated in-motion\ndriving time understatement of 30 minutes or more\non the ELD over a 24-hour period across all driver\nprofiles, including the unidentified driver profile.\nPrecondition:\n\u2022 There has been an aggregated in-motion driving\ntime understatement of 30 minutes or more on\nthe ELD over a 24-hour period across all driver\nprofiles\n\u2022 A power data diagnostic malfunction is\nrecorded" }, { "case_id": "ELD-2.2:5", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-1", "step": 5, "pdf_page": 309, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_ecm_source_monitoring_previously_tested_reference" ], "requirement": "An ELD must monitor the data it\nreceives from the engine ECM or alternative sources\nas allowed in Appendix B, sections 4.3.1.1-4.3.1.4." }, { "case_id": "ELD-2.2:6", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-2", "step": 6, "pdf_page": 309, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_sync_sensor_instances_become_diagnostic_records" ], "requirement": "An ELD must monitor the data it\nreceives from its onboard sensors to identify instances\nof its non-compliance with the ELD engine\nsynchronization requirement specified in Appendix B,\nsection 4.2.\nPrecondition:\n\u2022 Instances of non-compliance with the ELD\nengine synchronization requirement exist" }, { "case_id": "ELD-2.2:7", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-3", "step": 7, "pdf_page": 310, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_sync_history_instances_become_diagnostic_records" ], "requirement": "An ELD must monitor the data it\nreceives from its onboard data record history to\nidentify instances of its non-compliance with the ELD\nengine synchronization requirement specified in\nAppendix B, section 4.2.\nPrecondition:\n\u2022 Instances of non-compliance with the ELD\nengine synchronization requirement exist" }, { "case_id": "ELD-2.2:8", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-4", "step": 8, "pdf_page": 311, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_sync_sensor_durations_become_diagnostic_records" ], "requirement": "An ELD must monitor the data it\nreceives from its onboard sensors to identify\ndurations of its non-compliance with the ELD engine\nsynchronization requirement specified in Appendix B,\nsection 4.2.\nPrecondition:\n\u2022 Instances of non-compliance with the ELD\nengine synchronization requirement exist" }, { "case_id": "ELD-2.2:9", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-5", "step": 9, "pdf_page": 312, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_sync_history_durations_become_diagnostic_records" ], "requirement": "An ELD must monitor the data it\nreceives from its data record history to identify\ndurations of its non-compliance with the ELD engine\nsynchronization requirement specified in Appendix B,\nsection 4.2.\nPrecondition:\n\u2022 Instances of non-compliance with the ELD\nengine synchronization requirement exist" }, { "case_id": "ELD-2.2:10", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-6", "step": 10, "pdf_page": 313, "state": "hardware-owned", "finding": null, "owner": "H3b", "nodes": [], "requirement": "An ELD required to establish a link to\nthe engine ECM, as described in Appendix B, section\n4.2, must monitor its connectivity to the engine ECM.\nPrecondition:\n\u2022 The ELD has established a link to the engine\nECM" }, { "case_id": "ELD-2.2:11", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-7", "step": 11, "pdf_page": 314, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_sub_five_second_loss_is_no_event", "tests/eld/test_malfunction_evaluator.py::test_loss_beyond_five_seconds_sets_at_the_acquisition_boundary" ], "requirement": "An ELD required to establish a link to\nthe engine ECM as described in Appendix B, section\n4.2 must record an engine-synchronization data\ndiagnostics event when it no longer can acquire\nupdated values for the ELD parameters required for\nrecords within 5 seconds of the need.\nPrecondition:\n\u2022 The ELD has established a link to the engine\nECM\n\u2022 ELD is unable to capture updated values for ELD\nparameters within engine synchronization data" }, { "case_id": "ELD-2.2:12", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.2-8", "step": 12, "pdf_page": 315, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_exactly_thirty_minutes_sets_p_and_not_e", "tests/eld/test_malfunction_evaluator.py::test_one_second_past_thirty_sets_e_at_the_crossing_instant" ], "requirement": "An ELD must set an engine\nsynchronization compliance malfunction if\nconnectivity to any of the required data sources\nspecified in Appendix B, section 4.3.1 is lost for more\nthan 30 minutes during a 24-hour period aggregated\nacross all driver profiles, including the unidentified\ndriver profile.\nPrecondition:\n\u2022 There must be a connectivity failure to engine\npower status, vehicle motion status, vehicle\nmiles, engine hours, date and time, CMV\nposition, and/or CMV VIN" }, { "case_id": "ELD-2.2:13", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.3-1", "step": 13, "pdf_page": 316, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_periodic_utc_cross_check_exists" ], "requirement": "The ELD must periodically cross-check\nits compliance with the requirement specified in\nAppendix B, section 4.3.1.5 with respect to an\naccurate external UTC source." }, { "case_id": "ELD-2.2:14", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.3-2", "step": 14, "pdf_page": 317, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_timing_boundary_600_is_compliant_601_is_not" ], "requirement": "The ELD must record a timing\ncompliance malfunction when it can no longer meet\nthe underlying compliance requirement.\nPrecondition:\n\u2022 Timing compliance malfunction created" }, { "case_id": "ELD-2.2:15", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.4-3", "step": 15, "pdf_page": 318, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_location_records_use_last_valid_position_and_distance" ], "requirement": "ELD records requiring location\ninformation must use the last valid position\nmeasurement and include the latitude/longitude\ncoordinates and distance traveled, in miles, since the\nlast valid position measurement." }, { "case_id": "ELD-2.2:16", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.4-4", "step": 16, "pdf_page": 319, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_no_fix_elapsed_time_is_monitored" ], "requirement": "An ELD must monitor elapsed time\nduring periods when the ELD fails to acquire a valid\nposition measurement within the past 5 miles of\nCMV\u2019s movement.\nPrecondition:\n\u2022 ELD failure to acquire a valid position\nmeasurement within 5 miles of CMV\u2019s\nmovement should exist" }, { "case_id": "ELD-2.2:17", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.4-5", "step": 17, "pdf_page": 320, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_l_cumulative_crossing_mid_span", "tests/eld/test_malfunction_evaluator.py::test_l_exactly_sixty_never_sets" ], "requirement": "When such elapsed time exceeds a\ncumulative 60 minutes over a 24 hour period, the ELD\nmust set and record a positioning compliance\nmalfunction." }, { "case_id": "ELD-2.2:18", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.4-6", "step": 18, "pdf_page": 321, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_absent_position_renders_the_x_code_and_distance_cap" ], "requirement": "If a new ELD event must be recorded at an\ninstance when ELD had failed to acquire a valid position\nmeasurement within the most recent elapsed 5 miles of\ndriving, but the ELD has not yet set a positioning\ncompliance malfunction, the ELD must record the character\n\u201cX\u201d in both the latitude and longitude fields.\nPrecondition:\n\u2022\nELD failure to acquire a valid position measurement\nwithin 5 miles of CMV\u2019s movement should exist" }, { "case_id": "ELD-2.2:19", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.4-7", "step": 19, "pdf_page": 322, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_duty_change_prompts_manual_location_logged_as_m" ], "requirement": "If the location is entered manually by the\ndriver, it must log the character \u201cM\u201d instead. Under the\ncircumstances listed in this paragraph, if the ELD event is\ndue to a change in duty status for the driver, the ELD must\nprompt the driver to enter location manually in accordance\nwith Appendix B, section 4.3.2.7.\nPrecondition:\n\u2022\nELD failure to acquire a valid position measurement\nwithin 5 miles of CMV\u2019s movement should exist" }, { "case_id": "ELD-2.2:20", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.4-8", "step": 20, "pdf_page": 323, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_missing_location_in_motion_records_diagnostic_three" ], "requirement": "If the location information is not\nentered by the driver and the vehicle is in motion, the\nELD must record a missing required data elements\ndata diagnostic event for the driver." }, { "case_id": "ELD-2.2:21", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.4-9", "step": 21, "pdf_page": 324, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_positioning_malfunction_forces_e_in_location_fields" ], "requirement": "If a new ELD event must be recorded at\nan instance when the ELD has set a positioning\ncompliance malfunction, the ELD must record the\ncharacter \u201cE\u201d in both the latitude and longitude fields\nregardless of whether the driver is prompted and\nmanually enters location information.\nPrecondition:\n\u2022 The ELD has a positioning compliance\nmalfunction" }, { "case_id": "ELD-2.2:22", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.5-1", "step": 22, "pdf_page": 325, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_storage_capacity_and_integrity_are_monitored" ], "requirement": "An ELD must monitor its storage\ncapacity and integrity." }, { "case_id": "ELD-2.2:23", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.5-2", "step": 23, "pdf_page": 326, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_recording_failure_sets_and_clears_on_restoration" ], "requirement": "An ELD must detect a data recording\ncompliance malfunction if it can no longer record or\nretain required events or retrieve recorded logs that\nare not otherwise catalogued remotely by the motor\ncarrier.\nPrecondition:\n\u2022 A data recording compliance malfunction is\npresent" }, { "case_id": "ELD-2.2:24", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.5-3", "step": 24, "pdf_page": 327, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_event_record_completeness_is_monitored" ], "requirement": "An ELD must monitor the completeness\nof the ELD event record information in relation to the\nrequired data elements for each event type." }, { "case_id": "ELD-2.2:25", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.5-4", "step": 25, "pdf_page": 328, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_missing_data_probe_sets_once_and_clears_affirmatively" ], "requirement": "An ELD must record a missing data\nelements data diagnostics event for the driver if any\nrequired field is missing at the time of recording.\nPrecondition:\n\u2022 Required field are missing from a driving record" }, { "case_id": "ELD-2.2:26", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.6-1", "step": 26, "pdf_page": 329, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_session_start_warns_of_new_unassigned_driving_time" ], "requirement": "When there are ELD records involving\ndriving time logged on an ELD under the unidentified\ndriver profile, the ELD must prompt the driver(s)\nlogging into that ELD with a warning indicating the\nexistence of new unassigned driving time.\nPrecondition:\n\u2022 The ELD must contain records of driving time\nlogged under the unidentified driver profile" }, { "case_id": "ELD-2.2:27", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.6-2", "step": 27, "pdf_page": 330, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_driver_can_review_then_acknowledge_or_reject" ], "requirement": "The ELD must provide a mechanism for\nthe driver to review and either acknowledge the\nassignment of one or more of the unidentified driver\nrecords attributable to the driver under the\nauthenticated driver\u2019s profile as described in\nAppendix B, section 4.3.2.8.2(1) or indicate that these\nrecords are not attributable to the driver." }, { "case_id": "ELD-2.2:28", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.6-3", "step": 28, "pdf_page": 331, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_thirty_minute_unidentified_detection_is_wired" ], "requirement": "If more than 30 minutes of driving in a\n24-hour period show an unidentified driver on the\nELD, the ELD must detect an unidentified driving\nrecords data diagnostic event." }, { "case_id": "ELD-2.2:29", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.6-4", "step": 29, "pdf_page": 331, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_unidentified_diagnostic_recorded_beyond_thirty_minutes" ], "requirement": "If more than 30 minutes of driving in a\n24-hour period show an unidentified driver on the\nELD, the ELD must record an unidentified driving\nrecords data diagnostic event." }, { "case_id": "ELD-2.2:30", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.6-5", "step": 30, "pdf_page": 332, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_unidentified_indicator_on_for_every_driver_of_this_eld" ], "requirement": "If more than 30 minutes of driving in a\n24-hour period show an unidentified driver on the\nELD, the data diagnostic indicator must be turned on\nfor all drivers logged in to that ELD for the current 24-\nhour period." }, { "case_id": "ELD-2.2:31", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.6-6", "step": 31, "pdf_page": 333, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_unidentified_indicator_persists_the_following_seven_days" ], "requirement": "If more than 30 minutes of driving in a\n24-hour period show an unidentified driver on the\nELD, the data diagnostic indicator must be turned on\nfor all drivers logged in to that ELD for the following 7\ndays." }, { "case_id": "ELD-2.2:32", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.6-7", "step": 32, "pdf_page": 334, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_unidentified_diagnostic_clears_when_claims_drain_to_fifteen" ], "requirement": "An unidentified driving records data diagnostic\nevent can be cleared by the ELD when driving time logged under\nthe unidentified driver profile for the current 24-hour period and\nthe previous 7 consecutive days drops to 15 minutes or less." }, { "case_id": "ELD-2.2:33", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.7-1", "step": 33, "pdf_page": 335, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_sweep_monitors_in_service_and_records" ], "requirement": "An ELD must implement in-service\nmonitoring functions to verify that the data transfer\nmechanism(s) described in Appendix B, section 4.9.1\nare continuing to function properly." }, { "case_id": "ELD-2.2:34", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.7-2", "step": 34, "pdf_page": 336, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_weekly_cadence_across_three_consecutive_windows" ], "requirement": "An ELD must verify the in-service\nmonitoring functionality at least once every 7 days." }, { "case_id": "ELD-2.2:35", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.7-3", "step": 35, "pdf_page": 337, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_monitoring_is_automatic_zero_driver_steps" ], "requirement": "The in-service monitoring functions\nmay be automatic or may involve manual steps for a\ndriver." }, { "case_id": "ELD-2.2:36", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.7-4", "step": 36, "pdf_page": 338, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_failed_check_sets_diagnostic_four" ], "requirement": "An ELD must record a data transfer data\ndiagnostic event.\nPrecondition:\n\u2022 Data diagnostic events are present on the ELD" }, { "case_id": "ELD-2.2:37", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.7-5", "step": 37, "pdf_page": 339, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_frequency_increases_to_daily_after_the_diagnostic" ], "requirement": "After an ELD records a data transfer\ndata diagnostic event, the ELD must increase the\nfrequency of the monitoring function to check at least\nonce every 24-hour period.\nPrecondition:\n\u2022 Data diagnostic events are present on the ELD" }, { "case_id": "ELD-2.2:38", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.1.7-6", "step": 38, "pdf_page": 340, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_malfunction_evaluator.py::test_ladder_three_consecutive_failures_after_the_diagnostic_set_s", "tests/eld/test_malfunction_evaluator.py::test_confirmed_check_breaks_the_ladder_and_clears" ], "requirement": "If the ELD stays in the unconfirmed data\ntransfer mode following the next three consecutive\nmonitoring checks, the ELD must detect a data\ntransfer compliance malfunction.\nPrecondition:\n\u2022 In-service monitoring mechanism in a failed\noperation state" }, { "case_id": "ELD-2.2:39", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.2-1", "step": 39, "pdf_page": 341, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_active_malfunction_indicated_to_all_drivers" ], "requirement": "ELD malfunctions affect integrity of the\ndevice and its compliance; therefore, active\nmalfunctions must be indicated to all drivers who may\nuse that ELD.\nPrecondition:\n\u2022 A malfunction on the ELD is present and visible" }, { "case_id": "ELD-2.2:40", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.2-2", "step": 40, "pdf_page": 342, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "An ELD must provide a recognizable\nvisual indicator, and may provide an audible signal, to\nthe operator as to its malfunction status.\nPrecondition:\n\u2022 A malfunction on the ELD has been created" }, { "case_id": "ELD-2.2:41", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.2.1-1", "step": 41, "pdf_page": 343, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_single_malfunction_indicator_channel_persists_across_users" ], "requirement": "An ELD must display a single visual\nmalfunction indicator for all drivers using the ELD on\nthe ELD\u2019s display or on a stand-alone indicator.\nPrecondition:\n\u2022 A malfunction on the ELD is generated" }, { "case_id": "ELD-2.2:42", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.2.1-2", "step": 42, "pdf_page": 344, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "The visual signal for the malfunction\nindicator must be visible to the driver when the driver\nis seated in the normal driving position.\nPrecondition:\n\u2022 A malfunction on the ELD is generated" }, { "case_id": "ELD-2.2:43", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.2.1-3", "step": 43, "pdf_page": 345, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "The ELD malfunction indicator must be\nclearly illuminated when there is an active\nmalfunction on the ELD.\nPrecondition\n\u2022 A malfunction on the ELD is generated" }, { "case_id": "ELD-2.2:44", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.2.1-4", "step": 44, "pdf_page": 346, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "The malfunction status must be\ncontinuously communicated to the driver when the\nELD is powered.\nPrecondition:\n\u2022 A malfunction on the ELD is present and visible" }, { "case_id": "ELD-2.2:45", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.3-1", "step": 45, "pdf_page": 347, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_diagnostic_status_scopes_to_the_authenticated_driver" ], "requirement": "ELD data diagnostic status affects only\nthe authenticated user; therefore, an ELD must only\nindicate the active data diagnostics status applicable\nto the driver logged into the ELD.\nPrecondition:\n\u2022 Multiple accounts with different data diagnostic\nstatuses are loaded on the ELD device" }, { "case_id": "ELD-2.2:46", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.3-2", "step": 46, "pdf_page": 348, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "An ELD must provide a recognizable\nvisual indicator, and may provide an audible signal, to\nthe driver as to its data diagnostics status.\nPrecondition:\n\u2022 Data diagnostic events are present on the ELD" }, { "case_id": "ELD-2.2:47", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.3.1-1", "step": 47, "pdf_page": 349, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w4_monitoring.py::test_diagnostic_indicator_apart_from_malfunction_indicator" ], "requirement": "An ELD must display a single visual data\ndiagnostics indicator, apart from the visual\nmalfunction indicator described in Appendix B,\nsection 4.6.2.1, to visually communicate existence of\nactive data diagnostics events for the applicable\ndriver.\nPrecondition:\n\u2022 Data diagnostic events are present on the ELD\n\u2022 Malfunction events are present on the ELD" }, { "case_id": "ELD-2.2:48", "procedure": "ELD-2.2", "functional_area": "ELD \u2013 Monitoring", "requirement_no": "ELD-FUNC-4.6.3.1-2", "step": 48, "pdf_page": 350, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "The visual signal must be visible to the\ndriver when the driver is seated in the normal driving\nposition.\nPrecondition:\n\u2022 Data diagnostic events are present on the ELD\n\u2022 Malfunction events are present on the ELD" }, { "case_id": "ELD-2.3:1", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.1-1", "step": 1, "pdf_page": 353, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_duty_status_change_recorded_and_associated_to_the_driver" ], "requirement": "When a driver\u2019s duty status changes, the\nELD must associate the record with the driver." }, { "case_id": "ELD-2.3:2", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.1-2", "step": 2, "pdf_page": 353, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_duty_status_record_associates_the_record_originator" ], "requirement": "When a driver\u2019s duty status changes, the\nELD must associate the record with the record originator\n(if created during an edit or entry)." }, { "case_id": "ELD-2.3:3", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.1-3", "step": 3, "pdf_page": 354, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_duty_status_record_associates_the_vehicle" ], "requirement": "When a driver\u2019s duty status changes, the\nELD must associate the record with the vehicle." }, { "case_id": "ELD-2.3:4", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.1-4", "step": 4, "pdf_page": 354, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_duty_status_record_associates_the_motor_carrier" ], "requirement": "When a driver\u2019s duty status changes, the\nELD must associate the record with the motor carrier." }, { "case_id": "ELD-2.3:5", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.1-5", "step": 5, "pdf_page": 355, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_duty_status_record_associates_the_shipping_document" ], "requirement": "When a driver\u2019s duty status changes, the\nELD must associate the record with the shipping\ndocument number." }, { "case_id": "ELD-2.3:6", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.1-6", "step": 6, "pdf_page": 356, "state": "xfail", "finding": "FLIP-FINDING-W5-EVENT-ELEMENTS-1", "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_duty_status_record_includes_the_45111_data_elements" ], "requirement": "When a driver\u2019s duty status changes, the ELD\nmust include the following data elements (See Appendix B,\nsection 4.5.1.1 for details)." }, { "case_id": "ELD-2.3:7", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.2-1", "step": 7, "pdf_page": 357, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_intermediate_log_event_recorded_after_an_hour_in_motion" ], "requirement": "When a CMV is in motion, as described in\nAppendix B, section 4.3.1.2, and there has not been a\nduty status change event or another intermediate log\nevent recorded in the previous 1-hour period, the ELD\nmust record a new intermediate log event." }, { "case_id": "ELD-2.3:8", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.2-2", "step": 8, "pdf_page": 358, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_intermediate_record_associates_the_driver" ], "requirement": "The ELD must associate the record to the\ndriver." }, { "case_id": "ELD-2.3:9", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.2-3", "step": 9, "pdf_page": 358, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_intermediate_record_associates_the_vehicle" ], "requirement": "The ELD must associate the record with\nthe vehicle." }, { "case_id": "ELD-2.3:10", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.2-4", "step": 10, "pdf_page": 359, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_intermediate_record_associates_the_motor_carrier" ], "requirement": "The ELD must associate the record with\nthe motor carrier." }, { "case_id": "ELD-2.3:11", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.2-5", "step": 11, "pdf_page": 359, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_intermediate_record_associates_the_shipping_document" ], "requirement": "The ELD must associate the record with\nthe shipping document number." }, { "case_id": "ELD-2.3:12", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.2-6", "step": 12, "pdf_page": 360, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_intermediate_record_includes_the_45111_elements" ], "requirement": "The ELD must include the following data\nelements outlined in Appendix B, section 4.5.1.1." }, { "case_id": "ELD-2.3:13", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.3-1", "step": 13, "pdf_page": 361, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_pcym_indication_change_records_new_events" ], "requirement": "At each instance when the status of a\ndriver\u2019s indication of personal use of CMV or yard moves\nchanges, the ELD must record a new event." }, { "case_id": "ELD-2.3:14", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.3-2", "step": 14, "pdf_page": 361, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_pcym_record_associates_the_driver" ], "requirement": "The ELD must associate the record to the\ndriver." }, { "case_id": "ELD-2.3:15", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.3-3", "step": 15, "pdf_page": 362, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_pcym_record_associates_the_vehicle" ], "requirement": "The ELD must associate the record with\nthe vehicle." }, { "case_id": "ELD-2.3:16", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.3-4", "step": 16, "pdf_page": 362, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_pcym_record_associates_the_motor_carrier" ], "requirement": "The ELD must associate the record with\nthe motor carrier." }, { "case_id": "ELD-2.3:17", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.3-5", "step": 17, "pdf_page": 363, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_pcym_record_associates_the_shipping_document" ], "requirement": "The ELD must associate the record with\nthe shipping document number" }, { "case_id": "ELD-2.3:18", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.3-6", "step": 18, "pdf_page": 364, "state": "xfail", "finding": "FLIP-FINDING-W5-EVENT-ELEMENTS-2", "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_pcym_record_includes_the_45111_data_elements" ], "requirement": "The ELD must include the following data\nelements outlined in Appendix B, section 4.5.1.1." }, { "case_id": "ELD-2.3:19", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.4-1", "step": 19, "pdf_page": 365, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_certify_and_recertify_both_record_events" ], "requirement": "At each instance when a driver certifies or\nre-certifies that driver\u2019s records for a given 24-hour\nperiod are true and correct, the ELD must record the\nevent." }, { "case_id": "ELD-2.3:20", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.4-2", "step": 20, "pdf_page": 366, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_certification_record_associates_the_driver" ], "requirement": "The ELD must associate the record to the\ndriver." }, { "case_id": "ELD-2.3:21", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.4-3", "step": 21, "pdf_page": 366, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_certification_record_associates_the_vehicle" ], "requirement": "The ELD must associate the record with\nthe vehicle." }, { "case_id": "ELD-2.3:22", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.4-4", "step": 22, "pdf_page": 367, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_certification_record_associates_the_motor_carrier" ], "requirement": "The ELD must associate the record with\nthe motor carrier." }, { "case_id": "ELD-2.3:23", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.4-5", "step": 23, "pdf_page": 367, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_certification_record_associates_the_shipping_document" ], "requirement": "The ELD must associate the record with\nthe shipping document number." }, { "case_id": "ELD-2.3:24", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.4-6", "step": 24, "pdf_page": 368, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_certification_record_carries_the_4514_data_elements" ], "requirement": "The ELD must include the following data\nelements (see Appendix B, section 4.5.1.4 for details)." }, { "case_id": "ELD-2.3:25", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.5-1", "step": 25, "pdf_page": 369, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_login_logout_events_are_recorded" ], "requirement": "At each instance when an authorized user\nlogs in and out of the ELD, the ELD must record the\nevent." }, { "case_id": "ELD-2.3:26", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.5-2", "step": 26, "pdf_page": 369, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_login_record_associates_the_driver" ], "requirement": "The ELD must associate the record to the\ndriver." }, { "case_id": "ELD-2.3:27", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.5-3", "step": 27, "pdf_page": 370, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_login_record_associates_the_vehicle" ], "requirement": "The ELD must associate the record with\nthe vehicle." }, { "case_id": "ELD-2.3:28", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.5-4", "step": 28, "pdf_page": 370, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_login_record_associates_the_motor_carrier" ], "requirement": "The ELD must associate the record with\nthe motor carrier." }, { "case_id": "ELD-2.3:29", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.5-5", "step": 29, "pdf_page": 371, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_login_record_associates_the_shipping_document" ], "requirement": "The ELD must associate the record with\nthe shipping document number." }, { "case_id": "ELD-2.3:30", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.5-6", "step": 30, "pdf_page": 372, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_login_record_includes_the_4515_elements" ], "requirement": "The ELD must include the following data\nelements (see Appendix B, section 4.5.1.5 for details)." }, { "case_id": "ELD-2.3:31", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-1", "step": 31, "pdf_page": 373, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_engine_power_events_recorded_within_one_minute" ], "requirement": "When a CMV\u2019s engine is powered up or\nshut down, an ELD must record the event within 1\nminute of occurrence." }, { "case_id": "ELD-2.3:32", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-2", "step": 32, "pdf_page": 374, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_earliest_shutdown_retained_when_cmv_has_not_moved" ], "requirement": "When a CMV\u2019s engine is powered up or\nshut down, an ELD must retain the earliest shut down\nevent if CMV has not moved since the last ignition power\non cycle." }, { "case_id": "ELD-2.3:33", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-3", "step": 33, "pdf_page": 374, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_latest_power_up_retained_when_cmv_has_not_moved" ], "requirement": "When a CMV\u2019s engine is powered up or\nshut down, an ELD must retain the latest power-up event\nif CMV has not moved since the last ignition power on\ncycle." }, { "case_id": "ELD-2.3:34", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-4", "step": 34, "pdf_page": 375, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_power_record_associates_the_driver_or_unidentified_profile" ], "requirement": "The ELD must associate the record to the\ndriver or the unidentified driver profile." }, { "case_id": "ELD-2.3:35", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-5", "step": 35, "pdf_page": 375, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_power_record_associates_the_vehicle" ], "requirement": "The ELD must associate the record with\nthe vehicle." }, { "case_id": "ELD-2.3:36", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-6", "step": 36, "pdf_page": 376, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_power_record_associates_the_motor_carrier" ], "requirement": "The ELD must associate the record with\nthe motor carrier." }, { "case_id": "ELD-2.3:37", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-7", "step": 37, "pdf_page": 376, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_power_record_associates_the_shipping_document" ], "requirement": "The ELD must associate the record with\nthe shipping document number." }, { "case_id": "ELD-2.3:38", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.6-8", "step": 38, "pdf_page": 377, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_power_record_includes_the_4516_elements" ], "requirement": "The ELD must include the following data\nelements (see Appendix B, section 4.5.1.6 for details)." }, { "case_id": "ELD-2.3:39", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-1", "step": 39, "pdf_page": 378, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_malfunction_set_is_recorded" ], "requirement": "At each instance when an ELD malfunction\nis detected by the ELD, the ELD must record the event." }, { "case_id": "ELD-2.3:40", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-2", "step": 40, "pdf_page": 378, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_malfunction_clear_is_recorded" ], "requirement": "At each instance when an ELD malfunction\nis cleared by the ELD, the ELD must record the event." }, { "case_id": "ELD-2.3:41", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-3", "step": 41, "pdf_page": 379, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_data_diagnostic_set_is_recorded" ], "requirement": "At each instance when an ELD data\ndiagnostic event is detected by the ELD, the ELD must\nrecord the event." }, { "case_id": "ELD-2.3:42", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-4", "step": 42, "pdf_page": 379, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_data_diagnostic_clear_is_recorded" ], "requirement": "At each instance when an ELD data\ndiagnostic event is cleared by the ELD, the ELD must\nrecord the event." }, { "case_id": "ELD-2.3:43", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-5", "step": 43, "pdf_page": 380, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_malfunction_ledger.py::test_reader_orders_and_scopes_to_the_user" ], "requirement": "The ELD must associate the record to the\ndriver." }, { "case_id": "ELD-2.3:44", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-6", "step": 44, "pdf_page": 380, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_malfunction_ledger.py::test_vehicle_attaches_when_known" ], "requirement": "The ELD must associate the record with\nthe vehicle." }, { "case_id": "ELD-2.3:45", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-7", "step": 45, "pdf_page": 381, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_malfunction_record_associates_the_motor_carrier" ], "requirement": "The ELD must associate the record with\nthe motor carrier." }, { "case_id": "ELD-2.3:46", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-8", "step": 46, "pdf_page": 381, "state": "xfail", "finding": "FLIP-FINDING-W5-EVENT-SHIPPING-4", "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_malfunction_record_shipping_capture", "tests/eld/flip/test_flip_w5_recording.py::test_malfunction_record_associates_the_shipping_document" ], "requirement": "The ELD must associate the record with\nthe shipping document number." }, { "case_id": "ELD-2.3:47", "procedure": "ELD-2.3", "functional_area": "ELD \u2013 Recording", "requirement_no": "ELD-FUNC-4.5.1.7-9", "step": 47, "pdf_page": 382, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w5_recording.py::test_malfunction_record_includes_the_4517_elements" ], "requirement": "The ELD must include the following data\nelements (see Appendix B, section 4.5.1.7 for details)." }, { "case_id": "ELD-3.1:1", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.1.1-1", "step": 1, "pdf_page": 388, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "Print paper must be able to accommodate the graph\ngrid specifications as listed in section 4.8.1.3 of Appendix B." }, { "case_id": "ELD-3.1:2", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.1.2-1", "step": 2, "pdf_page": 388, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "If an ELD does not produce a printout, the ELD must\nbe designed so that its display may be reasonably viewed by an\nauthorized safety official without entering the commercial motor\nvehicle." }, { "case_id": "ELD-3.1:3", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.1.3-1", "step": 3, "pdf_page": 389, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/test_eld_inspection.py::test_unidentified_profile_renders_separately" ], "requirement": "The printout and display must show reports for the\ninspected driver\u2019s profile and the unidentified driver profile\nseparately." }, { "case_id": "ELD-3.1:4", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.1.3-2", "step": 4, "pdf_page": 390, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_display_carries_the_o1_identity_elements", "tests/eld/flip/test_flip_w6_eld_outputs.py::test_display_carries_a_shipping_id", "tests/eld/flip/test_flip_w6_eld_outputs.py::test_display_carries_a_current_location" ], "requirement": "The printout and display must show the following information for\nthe current 24-hour period and each of the previous 7 consecutive days (See\n4.8.1.3 for more details)." }, { "case_id": "ELD-3.1:5", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.1.3-3", "step": 5, "pdf_page": 391, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "The printout must show each change of duty status on a\ngraph-grid and must be at least 6 inches by 1.5 inches in size." }, { "case_id": "ELD-3.1:6", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.1.3-4", "step": 6, "pdf_page": 391, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_grid_overlays_pc_and_ym_on_their_effective_rows" ], "requirement": "The graph-grid must overlay periods of driver\u2019s\nindications of authorized personal use of CMV and yard moves\nusing a different style line (such as dashed or dotted line) or\nshading." }, { "case_id": "ELD-3.1:7", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1-1", "step": 7, "pdf_page": 392, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_standard_output_file_produced_for_transfer_on_the_live_test_lane" ], "requirement": "The ELD must produce a standard ELD data output file\nfor transfer purposes, which must be generated according to the\nstandard specified in this section." }, { "case_id": "ELD-3.1:8", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1-2", "step": 8, "pdf_page": 393, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestFileStructure::test_all_eleven_segment_titles_in_order_even_with_no_events", "tests/eld/test_erods_generator.py::TestFileStructure::test_file_is_ascii_and_cr_terminated" ], "requirement": "Data output must be provided in a single comma-\ndelimited file outlined in this section using American National\nStandard Code for Information Exchange (ASCII) character sets\nmeeting the standards of ANSI INCITS 4-1986 (R2012) (incorporated\nby reference, see \u00a7 395.38), reference (3)(b) in section 6 of\nAppendix C. It must include: (1) a header segment, which specifies\ncurrent or non-varying elements of an ELD file; and (2) variable\nlength comma-delimited segments for the drivers, vehicles, ELD\nevents, ELD malfunction and data diagnostics records, ELD login and\nlogout activity, and unidentified driver records." }, { "case_id": "ELD-3.1:9", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.2-1", "step": 9, "pdf_page": 394, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_user_list_derives_from_driving_records_and_support_edits" ], "requirement": "The User List must list all drivers and co-drivers with\ndriving time records on the most recent CMV operated by the\ninspected driver and motor carrier\u2019s support personnel who\nrequested edits within the time period for which this file is\ngenerated.\nPrecondition:\n\u2022 User must acquire the most recent CMV that has been\noperated by the inspected driver or motor carrier\u2019s support\npersonnel who requested edits within the time period for\nwhich the file is generated" }, { "case_id": "ELD-3.1:10", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.2-2", "step": 10, "pdf_page": 395, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_user_list_orders_most_recent_first_including_the_profile" ], "requirement": "The user list must be in chronological order with most\nrecent user of the ELD on top, including the driver being inspected,\nthe co-driver, and the unidentified driver profile." }, { "case_id": "ELD-3.1:11", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.2-3", "step": 11, "pdf_page": 396, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_user_list_rows_are_activity_gated" ], "requirement": "The User List has a variable number of rows\ndepending on the number of profiles with activity over the time\nperiod for which this file is generated. (See Appendix B, section\n4.8.2.1.2 for details)\nPrecondition:\n\u2022 Various number of profiles with activity should exist over time\nperiod for which the file is generated" }, { "case_id": "ELD-3.1:12", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.3-1", "step": 12, "pdf_page": 397, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_cmv_list_lists_each_cmv_operated_in_the_period" ], "requirement": "The CMV List must list each CMV that the current\ndriver operated and that has been recorded on the driver\u2019s ELD\nrecords within the time period for which this file is generated.\nPrecondition:\n\u2022 The current driver must have operated at least one CMV\nwithin the time period for which the file is generated\n\u2022 At least one CMV should be recorded on the driver\u2019s ELD\nrecords within the time period for which the file is generated" }, { "case_id": "ELD-3.1:13", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.3-2", "step": 13, "pdf_page": 398, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_cmv_list_ranks_most_recent_operation_first" ], "requirement": "The list must be rank ordered in accordance with the\ntime of CMV operation with the most recent CMV being on top.\nPrecondition:\n\u2022 The current driver must have operated at least one CMV\nwithin the time period for which the file is generated\n\u2022 At least one CMV should be recorded on the driver\u2019s ELD\nrecords within the time period for which the file is generated" }, { "case_id": "ELD-3.1:14", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.3-3", "step": 14, "pdf_page": 399, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_cmv_list_row_count_tracks_the_cmvs_operated" ], "requirement": "This segment has a variable number of rows\ndepending on the number of CMVs operated by the driver over the\ntime period for which this file is generated (See Appendix B, section\n4.8.2.1.3 for details).\nPrecondition:\n\u2022 The driver must have operated at least one CMV within the\ntime period for which the file is generated" }, { "case_id": "ELD-3.1:15", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.4-1", "step": 15, "pdf_page": 400, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_table_6_type_1_codes_for_all_four_statuses" ], "requirement": "The ELD Event List for Driver\u2019s RODS must list ELD\nevent records tagged with event type 1 (a change in duty status as\ndescribed in Appendix B, section 4.5.1.1).\nPrecondition:\n\u2022 A change in duty status must exist within the records" }, { "case_id": "ELD-3.1:16", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.4-2", "step": 16, "pdf_page": 400, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_event_list_carries_type_2_intermediate_rows" ], "requirement": "This segment must list ELD event records tagged with\nevent type 2 (an intermediate log as described in Appendix B,\nsection 4.5.1.2)" }, { "case_id": "ELD-3.1:17", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.4-3", "step": 17, "pdf_page": 401, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_type_3_rows_project_pc_and_ym_through_the_ledger" ], "requirement": "This segment must list ELD event records tagged with\nevent type 3 (a change in driver\u2019s indication of conditions impacting\ndriving time recording as described in Appendix B, section 4.5.1.3)" }, { "case_id": "ELD-3.1:18", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.4-4", "step": 18, "pdf_page": 402, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_superseded_rows_surface_with_record_status_2" ], "requirement": "The ELD Event List for Driver\u2019s RODS must list all\nevent record status types and of all event record origins for the\ndriver, rank ordered with the most current log on top in accordance\nwith the date and time fields of the record.\nPrecondition:\n\u2022 Event records must exist within the ELD" }, { "case_id": "ELD-3.1:19", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.4-5", "step": 19, "pdf_page": 403, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_event_list_row_count_tracks_the_recorded_events" ], "requirement": "ELD Event List for Driver\u2019s RODS has a variable\nnumber of rows depending on the number of ELD events recorded\nfor the driver over the time period for which this file is generated.\n(See Appendix B, section 4.8.2.1.4 for details)\nPrecondition:\n\u2022 Event records must exist within the ELD" }, { "case_id": "ELD-3.1:20", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.5-1", "step": 20, "pdf_page": 404, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_events_without_annotation_or_location_do_not_reach_the_segment" ], "requirement": "This segment must list only the elements of the ELD\nevent list created in Appendix B, section 4.8.2.1.4 above that have\nan annotation, comment, or a manual entry of location description\nby the driver." }, { "case_id": "ELD-3.1:21", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.5-2", "step": 21, "pdf_page": 405, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestEventList::test_annotation_rows_carry_username_date_time_and_location" ], "requirement": "This segment has a variable number of rows\ndepending on the number of ELD events under Appendix B, section\n4.8.2.1.4 that feature a comment, annotation, or manual location\nentry by the driver. (See Appendix B, section 4.8.2.1.5 for details)" }, { "case_id": "ELD-3.1:22", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.6-1", "step": 22, "pdf_page": 406, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestCertificationSegment::test_row_shape_is_the_transcribed_line_template", "tests/eld/test_erods_generator.py::TestCertificationSegment::test_segment_renders_most_current_on_top" ], "requirement": "The ELD Event List for Driver\u2019s Certification of Own\nRecords must list ELD event records with event type 4 (driver\u2019s\ncertification of own records as described in Appendix B, section\n4.5.1.4) for the inspected driver for time period for which this file is\ngenerated, It must be rank ordered with the most current record on\ntop." }, { "case_id": "ELD-3.1:23", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.6-2", "step": 23, "pdf_page": 407, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestCertificationSegment::test_empty_input_emits_title_with_zero_rows_and_no_flag", "tests/eld/test_erods_generator.py::TestCertificationSegment::test_event_code_caps_at_nine_per_table_6" ], "requirement": "This segment has a variable number of rows\ndepending on the number of certification and re-certification\nactions the authenticated driver may have executed on the ELD\nover the time period for which this file is generated. (See Appendix\nB, section 4.8.2.1.6 for details)" }, { "case_id": "ELD-3.1:24", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.7-1", "step": 24, "pdf_page": 408, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_malfunction_segment_lists_stored_malfunctions" ], "requirement": "The Malfunction and Diagnostic Event Records must\nlist all ELD malfunctions that have occurred on this ELD during the\ntime period for which this file is generated.\nPrecondition:\n\u2022 ELD malfunctions much have occurred on this ELD during the\ntime period for which the file is generated" }, { "case_id": "ELD-3.1:25", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.7-2", "step": 25, "pdf_page": 409, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_diagnostic_rows_relate_to_the_inspected_driver" ], "requirement": "The Malfunction and Diagnostic Event Records must\nlist diagnostic event records related to the driver being inspected,\nrank ordered with the most current record on top.\nPrecondition:\n\u2022 Diagnostic event records related to the driver must exist\nwithin the ELD" }, { "case_id": "ELD-3.1:26", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.7-3", "step": 26, "pdf_page": 410, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_malfunction_segment_row_count_tracks_the_records" ], "requirement": "This segment has a variable number of rows\ndepending on the number of ELD malfunctions and ELD diagnostic\nevent records recorded and relevant to the inspected driver over\nthe time period for which this file is generated. (See Appendix B,\nsection 4.8.2.1.7 for details)\nPrecondition:\n\u2022 There should be at least one ELD malfunction and diagnostic\nevent recorded within the ELD" }, { "case_id": "ELD-3.1:27", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.8-1", "step": 27, "pdf_page": 411, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_login_logout_report_lists_type_5_events" ], "requirement": "The ELD Login/Logout Report must list the login and\nlogout activity on the ELD (ELD events with event type 5 (A driver\u2019s\nlogin/logout activity)) for the inspected driver for the time period\nfor which this file is generated.\nPrecondition:\n\u2022 Login and logout activity must exist within the ELD" }, { "case_id": "ELD-3.1:28", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.8-2", "step": 28, "pdf_page": 411, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_login_logout_report_ranks_most_recent_first" ], "requirement": "The login/logout activity logs must be rank ordered\nwith the most recent activity on top. (See Appendix B, section\n4.8.2.1.8 for details)" }, { "case_id": "ELD-3.1:29", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.9-1", "step": 29, "pdf_page": 412, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_engine_power_segment_lists_type_6_events" ], "requirement": "CMV\u2019s Engine Power Up and Shut Down Activity must\nlist the logs created when CMV\u2019s engine is powered up and shut\ndown (ELD events with event type 6 (CMV\u2019s engine power up/shut\ndown)) for the time period for which this file is generated.\nPrecondition:\n\u2022 CMV engine power up/shut down activity logs must exist\nwithin the ELD" }, { "case_id": "ELD-3.1:30", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.9-2", "step": 30, "pdf_page": 412, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_engine_power_segment_ranks_latest_first" ], "requirement": "The power up/shutdown logs must be rank ordered\nwith the latest activity on top. (See Appendix B, section 4.8.2.1.9\nfor details)" }, { "case_id": "ELD-3.1:31", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.10-1", "step": 31, "pdf_page": 413, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_unidentified_segment_lists_the_profile_stream" ], "requirement": "The ELD Event Log List for the Unidentified Driver\nProfile must list the ELD event records for the Unidentified Driver\nprofile, rank ordered with most current log on top in accordance\nwith the date and time fields of the logs.\nPrecondition:\n\u2022 Unidentified driver records must exist within the ELD" }, { "case_id": "ELD-3.1:32", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.1.10-2", "step": 32, "pdf_page": 414, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_unidentified_segment_row_count_tracks_the_profile" ], "requirement": "This segment has a variable number of rows\ndepending on the number of Unidentified Driver ELD records\nrecorded over the time period for which this file is generated. (See\nAppendix B, section 4.8.2.1.10 for details)\nPrecondition:\n\u2022 Unidentified driver records must exist within the ELD" }, { "case_id": "ELD-3.1:33", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.8.2.2-1", "step": 33, "pdf_page": 415, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/test_erods_generator.py::TestOutputFileName::test_spec_example_short_last_name_underscore_padded", "tests/eld/test_erods_generator.py::TestOutputFileName::test_spec_example_digit_sum_113_uses_last_two_digits", "tests/eld/test_erods_generator.py::TestOutputFileName::test_spec_example_digit_sum_below_ten_zero_padded", "tests/eld/test_erods_generator.py::TestOutputFileName::test_spec_example_date_form", "tests/eld/test_erods_generator.py::TestOutputFileName::test_suffix_is_validated", "tests/eld/test_erods_generator.py::TestOutputFileName::test_generator_stamps_the_home_terminal_creation_date" ], "requirement": "If the ELD output is saved in a file for transfer or maintenance purposes, it\nmust follow the twenty-five character-long filename standard below: (See Appendix B,\nsection 4.8.2.2 for details)" }, { "case_id": "ELD-3.1:34", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.1-1", "step": 34, "pdf_page": 416, "state": "hardware-owned", "finding": null, "owner": "bench", "nodes": [], "requirement": "If a driver selects the sleeper-berth state for the\ndriver\u2019s record of duty status, and no co-driver has logged into the\nELD as on-duty driving, and if the ELD outputs audible signals, the\nELD must allow the driver to mute the ELD\u2019s volume or turn off the\nELD\u2019s audible output or automatically mute the ELD\u2019s volume or\nturn off the ELD\u2019s audible output.\nPrecondition:\n\u2022 No co-driver may be logged into the ELD as on-duty driving\n\u2022 The ELD must output audible signals" }, { "case_id": "ELD-3.1:35", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.2-1", "step": 35, "pdf_page": 417, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_driver_obtains_own_copy_on_demand_at_the_driver_venue" ], "requirement": "An ELD must provide a mechanism for a driver to\nobtain a copy of the driver\u2019s own ELD records on demand, in either\nan electronic or printout format compliant with inspection\nstandards outlined in Appendix B, section 4.8.2.1." }, { "case_id": "ELD-3.1:36", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.2-2", "step": 36, "pdf_page": 418, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_the_copy_does_not_go_through_the_motor_carrier" ], "requirement": "The process must not require a driver to go through\nthe motor carrier to obtain copies of the driver\u2019s own ELD records if\ndriver\u2019s records reside on or are accessible directly by the ELD unit\nused by the driver." }, { "case_id": "ELD-3.1:37", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.2-3", "step": 37, "pdf_page": 419, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_driver_displays_the_copied_data_on_a_computer_under_the_ruling" ], "requirement": "If an ELD meets the requirements of this section by\nmaking data files available to the driver, it must also provide a\nutility function for the driver to display the data on a computer, at a\nminimum, as specified in \u00a7 395.8(g).\nPrecondition:\n\u2022 Before starting the test, verify the 4.7.2-1 and 4.7.2-2\nrequirements were completed first" }, { "case_id": "ELD-3.1:38", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.3-2", "step": 38, "pdf_page": 420, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_personal_use_omits_meters_and_reduces_precision" ], "requirement": "When a driver indicates that the driver is temporarily\nusing the CMV for an authorized personal purpose, a subset of the\nrecorded elements must either be omitted in the records or\nrecorded at a lower precision level, as described in further detail\nbelow. The driver indicates this intent by setting driver\u2019s duty status\nto off-duty as described in Appendix B, section 4.3.2.2.1 and\nindicating authorized personal use of CMV as described in Appendix\nB, section 4.3.2.2.2." }, { "case_id": "ELD-3.1:39", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.3-3", "step": 39, "pdf_page": 421, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_personal_use_position_renders_single_decimal" ], "requirement": "During a period when a driver indicates authorized\npersonal use of CMV, the ELD must record all new ELD events with\nlatitude/longitude coordinates information rounded to a single\ndecimal place resolution" }, { "case_id": "ELD-3.1:40", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.3-4", "step": 40, "pdf_page": 422, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_pc_blanking_spares_engine_power_events" ], "requirement": "During a period when a driver indicates authorized\npersonal use of CMV, the ELD must omit recording vehicle miles and\nengine hours fields in new ELD logs by leaving them blank, except\nfor events corresponding to a CMV\u2019s engine power-up and shut-\ndown activity as described in Appendix B, section 4.5.1.6." }, { "case_id": "ELD-3.1:41", "procedure": "ELD-3.1", "functional_area": "ELD-Outputs", "requirement_no": "ELD-FUNC-4.7.3-5", "step": 41, "pdf_page": 423, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w6_eld_outputs.py::test_personal_use_prompts_for_continuation_at_ignition_on" ], "requirement": "A driver\u2019s indication that the CMV is being operated\nfor authorized personal purposes may span more than one CMV\nignition on cycle if the driver proactively confirms continuation of\nthe personal use condition prior to placing the vehicle in motion\nwhen the ELD prompts the driver at the beginning of the new\nignition power on cycle.\nPrecondition:\n\u2022 Vehicle interface is needed for this requirement" }, { "case_id": "ELD-3.2:1", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.1-1", "step": 1, "pdf_page": 425, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_eight_day_window_produced_and_shown_at_the_driver_venue" ], "requirement": "On demand during a roadside safety inspection,\nan ELD must produce a driver\u2019s record of duty status for the\ncurrent 24-hour period and the previous 7 consecutive days in\nelectronic format, in the standard data format described in\nAppendix B, section 4.8.2.1.\nPrecondition:\n\u2022 ELD has to have 7 consecutive days of duty status records" }, { "case_id": "ELD-3.2:2", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.1-2", "step": 2, "pdf_page": 426, "state": "operational", "finding": null, "owner": "O1", "nodes": [], "requirement": "When a driver uses the single-step driver\ninterface, as described in Appendix B, section 4.3.2.4, to\nindicate for the ELD to compile and transfer driver\u2019s ELD\nrecords to authorized safety officials, the ELD must transfer the\ngenerated ELD data output to the computing environment used\nby authorized safety officials via the standards referenced in\nthis section.\nPrecondition:\n\u2022 The supported single-step data transfer initiation\nmechanism (such as a switch or an icon on a touch-\nscreen display) must be clearly marked and visible to the\ndriver when the vehicle is stopped." }, { "case_id": "ELD-3.2:3", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.1-3", "step": 3, "pdf_page": 427, "state": "operational", "finding": null, "owner": "O1", "nodes": [], "requirement": "An ELD must support one of the two options for\nroadside data transfer in paragraph (b) of this section, and\nmust certify proper operation of each element under that\noption. (See Appendix B, section 4.9.1 for details)" }, { "case_id": "ELD-3.2:4", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.2-1", "step": 4, "pdf_page": 428, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_records_retained_and_producible_past_six_months" ], "requirement": "An ELD must be capable of maintaining and\nretaining copies of electronic ELD records for a period of at\nleast 6 months from the date of receipt.\nPrecondition:\n\u2022 ELD records should exist for a period of at least 6 months\nfrom the day of receipt" }, { "case_id": "ELD-3.2:5", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.2-2", "step": 5, "pdf_page": 428, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_produces_files_for_a_subset_of_drivers" ], "requirement": "An ELD must produce, on demand, a data file or\na series of data files of ELD records for a subset of its drivers." }, { "case_id": "ELD-3.2:6", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.2-3", "step": 6, "pdf_page": 429, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_produces_files_for_a_subset_of_vehicles" ], "requirement": "An ELD must produce, on demand, a data file or\na series of data files of ELD records for a subset of its vehicles." }, { "case_id": "ELD-3.2:7", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.2-4", "step": 7, "pdf_page": 430, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_produces_files_for_an_official_specified_period" ], "requirement": "An ELD must produce, on demand, a data file or\na series of data files of ELD records for subset of the 6-month\nrecord retention period, to be specified by an authorized safety\nofficial, in an electronic format standard described in Appendix\nB, section 4.8.2.1 or, if the motor carrier has multiple offices or\nterminals, within the time permitted under \u00a7 390.29." }, { "case_id": "ELD-3.2:8", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.9.2-5", "step": 8, "pdf_page": 431, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_elected_transfer_pair_operational_on_the_live_test_lanes" ], "requirement": "At a minimum, an ELD must be able to transfer\nthe ELD records electronically by one of the following transfer\nmechanisms: Web Services as specified in section 4.10.1.1 of\nthis appendix (but not necessarily wirelessly), E-mail as\nspecified 4.10.1.2 (but not necessarily wirelessly) or USB 2.0 as\nspecified in section 4.10.1.3 of this appendix and Bluetooth, as\nspecified in section 4.10.1.4" }, { "case_id": "ELD-3.2:9", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.1-2", "step": 9, "pdf_page": 432, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_transfer_follows_the_committed_wsdl_1_1" ], "requirement": "Transfer of ELD data to FMCSA via Web Services\nmust follow the following standards: Web Services Description\nLanguage (WSDL) (See Appendix B, section 4.10.1.1 for details)\n1.1 (incorporated by reference, see \u00a7395.38), reference (1)(a) in\nsection 6 Appendix C." }, { "case_id": "ELD-3.2:10", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.1-3", "step": 10, "pdf_page": 432, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_transfer_speaks_soap_1_2" ], "requirement": "Transfer of ELD data to FMCSA via Web Services\nmust follow the following standards: Simple Object Access\nProtocol (SOAP) (See Appendix B, section 4.10.1.1 for details)\n1.2 (incorporated by reference, see \u00a7395.38),reference (1)(b) in\nsection 6 of Appendix C" }, { "case_id": "ELD-3.2:11", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.1-4", "step": 11, "pdf_page": 433, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_transfer_payload_is_well_formed_xml_1_0" ], "requirement": "Transfer of ELD data to FMCSA via Web Services\nmust follow the following standards: Extensible Markup\nLanguage (XML) (See Appendix B, section 4.10.1.1 for details)\n1.0 5th Edition (incorporated by reference, see \u00a7395.38),\nreference (1)(c) in section 6 of Appendix C." }, { "case_id": "ELD-3.2:12", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.1-5", "step": 12, "pdf_page": 433, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_transmission_privacy_tls_on_the_support_system_pipe" ], "requirement": "ELD data transmission from the ELD to the ELD\nsupport system must be accomplished in a way that protects\nthe privacy of the driver(s)." }, { "case_id": "ELD-3.2:13", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.1-6", "step": 13, "pdf_page": 434, "state": "operational", "finding": null, "owner": "O1", "nodes": [], "requirement": "At roadside if both the vehicle operator and law\nenforcement have an available data connection, the vehicle\noperator will initiate the transfer of ELD data to an authorized\nsafety official. (See Appendix B, section 4.10.1.1 for details)\nPrecondition:\n\u2022 At roadside, both the vehicle operator and the law\nenforcement should have an available data connection" }, { "case_id": "ELD-3.2:14", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.2-1", "step": 14, "pdf_page": 435, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_email_file_attached_and_sent_via_smtp_on_the_live_test_lane" ], "requirement": "ELD must attach a file to an e-mail message to be\nsent using RFC 5321 Simple Mail Transfer Protocol (SMTP)\n(incorporated by reference, see \u00a7 395.38), reference (7) (b) in\nsection 6 of Appendix C, to a specific e-mail address, which will\nbe shared with the ELD providers during the technology\nregistration process." }, { "case_id": "ELD-3.2:15", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.2-2", "step": 15, "pdf_page": 436, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_emailed_file_smime_encrypted_and_parsed_on_the_live_test_lane" ], "requirement": "The file must have the format described in\nsection 4.8.2.1 of this appendix and must be encrypted using\nthe Secure/Multipurpose Internet Mail Extensions as described\nin RFC 5751 (incorporated by reference, see \u00a7 395.38), and the\nRSA algorithm as described in RFC 4056 (incorporated by\nreference, see \u00a7 395.38), with the FMCSA public key compliant\nwith NIST SP 800-32 (incorporated by reference, see \u00a7 395.38)\nto be provided to the ELD provider at the time of registration.\nThe content must be encrypted using AES in FIPS Publication\n197 (incorporated by reference, see \u00a7 395.38), and RFC 3565\n(incorporated by reference, see \u00a7 395.38)." }, { "case_id": "ELD-3.2:16", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.2-3", "step": 16, "pdf_page": 437, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_email_receipt_confirmation_loop_closed_on_the_live_test_lane" ], "requirement": "The e-mail must be formatted using the RFC 5322\nInternet Message Format (incorporated by reference, see \u00a7\n395.38), reference (7)(c) in section 6 Appendix C, as follows:\n(See Appendix B, section 4.10.1.3 for details). A message\nconfirming receipt of the ELD file will be sent to the address\nspecified in the e-mail. The filename must follow the\nconvention specified in Appendix B, section 4.8.2.2." }, { "case_id": "ELD-3.2:17", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.3-1", "step": 17, "pdf_page": 438, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "ELDs certified for USB data transfer mechanism\nmust be capable of transferring ELD records using the Universal\nSerial Bus Specification (Revision 2.0)(incorporated by\nreference, see \u00a7 395.38), reference (2)(a) in section 6 of\nAppendix C.\nPrecondition:\n\u2022 Driver must have had opportunity to enter a comment\nwithin the file" }, { "case_id": "ELD-3.2:18", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.3-2", "step": 18, "pdf_page": 439, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "Each ELD technology must implement a single\nUSB-compliant interface with the necessary adaptors for a Type\nA connector. The USB interface must implement the Mass\nStorage class (08h) for driverless operation, to comply with IEEE\nstandard 1667-2009, (incorporated by reference, see \u00a7 395.38),\nreference (4)(a) in section 6 of Appendix C." }, { "case_id": "ELD-3.2:19", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.3-3", "step": 19, "pdf_page": 439, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "ELD must be capable of providing power to a\nstandard USB-compatible drive." }, { "case_id": "ELD-3.2:20", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.3-4", "step": 20, "pdf_page": 440, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "An ELD must re-authenticate the driver prior to\nsaving the driver\u2019s ELD file to an external device." }, { "case_id": "ELD-3.2:21", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.3-5", "step": 21, "pdf_page": 441, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "On initiation by an authenticated driver, an ELD\nmust be capable of saving ELD file(s) to USB-compatible drives\n(AES, in FIPS Publication 197, incorporated by reference, see \u00a7\n395.38) that are provided by authorized safety officials during\nan inspection.\nPrecondition:\n\u2022 USB compatible drives should be provided by authorized\nsafety officials\n\u2022 An ELD provider developing an ELD technology must\nregister online at a secure FMCSA website" }, { "case_id": "ELD-3.2:22", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.3-6", "step": 22, "pdf_page": 442, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "Prior to initiating this action, ELDs must be\ncapable of reading a text file from an authorized safety\nofficials\u2019 drive and verifying it against a file provided to ELD\nproviders who have registered their technologies as described\nin section 5.1." }, { "case_id": "ELD-3.2:23", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.4-1", "step": 23, "pdf_page": 442, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "Bluetooth SIG Specification of the Bluetooth\nSystem covering core package version 2.1 + EDR or higher\n(incorporated by reference, see \u00a7 395.38), reference (8) (a) in\nsection 6 of Appendix C, must be followed. ELDs using this\nstandard must be capable of displaying a Personal\nIdentification Number generated by the Bluetooth application\nprofile for bonding with other devices.\nPrecondition:\n\u2022 ELD must use Bluetooth SIG specification standard of the\nBluetooth system" }, { "case_id": "ELD-3.2:24", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.4-2", "step": 24, "pdf_page": 443, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "Upon request of an authorized official, the ELD\nmust become discoverable by the authorized safety officials\u2019\nBluetooth-enabled computing platform, and generate a\nrandom code, which the driver must share with the official." }, { "case_id": "ELD-3.2:25", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.1.4-3", "step": 25, "pdf_page": 443, "state": "n-a-by-election", "finding": null, "owner": "election \u2014 \u00a74.9.1 Option-1 telematics", "nodes": [], "requirement": "The ELD must connect to the roadside authorized\nsafety officials\u2019 technology via wireless personal area network\nand transmit the required data via Web Services as described in\nAppendix B, section 4.10.1.1." }, { "case_id": "ELD-3.2:26", "procedure": "ELD-3.2", "functional_area": "ELD-Data Transfer", "requirement_no": "ELD-FUNC-4.10.2-1", "step": 26, "pdf_page": 444, "state": "pass", "finding": null, "owner": null, "nodes": [ "tests/eld/flip/test_flip_w8_data_transfer.py::test_enforcement_specified_historical_subset_transmitted" ], "requirement": "Regardless of the roadside transmission option\nsupported by an ELD, ELD records are maintained and retained\nmust be able to transmit enforcement-specified historical data\nfor their drivers using one of the methods specified under\nsection Appendix B, section 4.9.2." } ] }