4.0 | COMMERCIAL VEHICLE OPERATIONS |
4.1 | COMMERCIAL VEHICLE ELECTRONIC CLEARANCE |
4.1.1 | CVEC shall include a Fixed Facility consisting of those structures and equipment to include Ports Of Entry, Inspection Stations, Weigh Stations and Toll Booths. |
4.1.1.6 | When making the "Pass/Need To Stop" determination the Fixed Facility shall perform checks on the following: |
4.1.1.6(a) | Vehicle/Carrier Safety Information. |
4.1.1.6(c) | Driver Credentials/Status. |
4.1.2 | CVEC shall include a Vehicle System capability |
4.1.2.1 | Vehicle System shall provide the capability to accommodate both interstate and intrastate carriers. |
4.1.2.3 | Vehicle System shall provide the capability for each individual vehicle's or carrier's participation in the process to be on a voluntary basis. |
4.2 | AUTOMATED ROADSIDE SAFETY INSPECTION |
4.2.2 | The ARSI capability shall include a Vehicle System (VS) function. |
4.2.2.1 | VS shall provide a processing capability that automates the roadside inspection tasks. |
4.2.2.2 | The VS architecture shall provide the capability to be developed and integrated as a phased implementation. |
4.2.2.3 | The VS shall include sensors to efficiently check vehicle systems and driver condition. |
4.2.2.4 | The VS shall include the capability for continuous updates to vehicle safety records or an "electronic decal/record" on the vehicle. |
4.2.2.5 | The VS shall include an on-board safety status monitoring system that is accessible from the roadside. |
4.2.2.6 | The VS shall provide an initial automated inspection capability that will expedite and supplement the existing visual and manual inspection processes. |
4.3 | ON-BOARD SAFETY AND SECURITY MONITORING |
4.3.1 | OBSSM shall include a Fixed Facility (FF) capability for the analysis and control of safety information. |
4.3.1.2 | The FF shall provide the capability to provide warnings of any safety problem that has been identified. |
4.3.2 | OBSSM shall include a Vehicle System (VS) that is a part of each vehicle. |
4.3.2.1 | The VS shall provide the capability to collect and process information to supply those roadside facilities being encountered at mainline speeds with each vehicle's safety status to include the following: |
4.3.2.1(a) | Vehicle safety status. |
4.3.2.1(b) | Cargo safety status. |
4.3.2.1(c) | Driver safety status. |
4.3.2.1(d) | Vehicle Identification. |
4.3.2.1(e) | Driver Identification. |
4.3.2.2 | The VS shall provide the capability to alert the vehicle driver whenever there is a critical safety problem or potential emergency. |
4.3.2.4 | The VS shall include a Vehicle Integrity (VI) function. |
4.3.2.4.1 | The VI shall monitor on-board sensors to detect a breach or tamper event. |
4.3.2.4.2 | The VI shall provide the capability to collect and process vehicle integrity information. |
4.3.3 | OBSSM shall include a Freight Security Management (FSM) function |
4.3.3.2 | FSM shall include a commercial vehicle driver/commercial vehicle/freight container or trailer Assignment Integrity (AI) function. |
4.3.3.2.4 | AI shall include the capability to monitor the identity of the commercial vehicle. |
4.3.3.2.5 | AI shall include the capability to monitor the identity of the freight container or trailer. |
4.4.3.2 | IBEC shall have an Electronic Records function that enables certification of border crossing shipment with the verification capabilities to include but not be limited to the following: |
4.4.3.2(a) | Verify driver identity. |
4.4.3.2(c) | Verify Nature of cargo. |
4.5 | HAZARDOUS MATERIAL SECURITY AND INCIDENT RESPONSE |
4.5.0 | ITS shall include a Hazardous Materials (HAZMAT) Security and Incident Response (HSIR) service. |
4.5.1 | HSIR shall include a HAZMAT Incident Notification (HIN) function. |
4.5.1.1 | HIN shall include the capability to provide enforcement and HAZMAT response teams with timely and accurate information on cargo contents when the vehicle is involved in an incident. |
4.5.1.2 | HIN shall be capable of providing the following Information : |
4.5.1.2(a) | Time of incident. |
4.5.1.2(b) | Location of the incident. |
4.5.1.2(c) | The material(s) involved. |
4.5.4 | HSIR shall include a HAZMAT Security (HS) function. |
4.5.4.3 | HS shall include a Driver Authentication function (DA) |
4.5.4.3.3 | DA shall include the capability to notify the vehicles dispatch function if an unauthorized driver attempts to operate the vehicle. |
4.5.4.3.4 | DA shall include the capability to safely disable a vehicle if an unauthorized driver attempts to operate the vehicle. |
4.5.4.3.5 | DA shall include the capability to allow a vehicles dispatch function to safely disable the vehicle. |
4.5.4.3.6 | DA shall include the capability to notify public safety if an unauthorized driver attempts to operate the vehicle. |
4.5.4.3.7 | DA shall include the capability to notify traffic management if an unauthorized driver attempts to operate the vehicle. |
| |