4.3 On-board Safety And Security Monitoring (User Service*)

The On-board Safety and Security Monitoring user service non-intrusively monitors the driver, vehicle, and cargo and notifies the driver, carrier, and, possibly, enforcement personnel if an unsafe situation arises during operation of the vehicle. Such an unsafe situation might involve the status of driver fatigue, vehicle systems, or cargo shift. This user service also assures freight container, trailer, and commercial vehicle integrity by monitoring on-board sensors for a breach or tamper event and monitoring assignment integrity between the vehicle, the driver or custodian, and the freight container.

User Service Requirements*:
4.3.0 ITS shall include an On-Board Safety and Security Monitoring (OBSSM) function, that provides monitoring and warnings of safety and security problems. For safety related issues, the primary importance is to inform the driver, as soon as possible, of any problem that has been detected. Of secondary importance is notifying the carrier of detected safety problems. Last in importance is the notification of appropriate enforcement agencies. For security related issues, the commercial vehicle driver and authorized freight data users are informed of any problems related to freight container, trailer or commercial vehicle integrity. For commercial vehicle driver/commercial vehicle/freight container or trailer assignment mismatches, authorized freight data users are informed of a potential problem. Requirements for On-Board Safety and Security Monitoring are given below:
PSpecs*: 2.1.1.1 , 2.1.1.7 , 2.1.2 , 2.1.3 , 2.1.5 , 2.1.6 , 2.1.7 , 2.2.3 , 2.3.1 , 2.3.3.1 , 2.3.3.4 , 2.3.4 , 2.3.5 , 2.3.6 , 2.3.7 , 2.4.1 , 2.4.2 , 2.4.3 , 2.4.4 , 2.4.5 , 2.4.6 , 2.4.7 , 2.4.9 , 2.7.1 , 2.7.3 , 2.7.5 , 2.7.6 , 2.7.7 , 5.1.1.2
4.3.1 OBSSM shall include a Roadside Capability for the analysis and control of safety information.
PSpecs*: 2.3.1 , 2.3.3.1 , 2.3.3.4 , 2.3.4 , 2.3.5 , 2.3.6 , 2.3.7 , 2.4.1 , 2.4.2 , 2.4.7
4.3.1.1 The Roadside Capability shall provide the capability to analyze data received from each vehicle approaching and determine the identification of:
PSpecs*: 2.3.3.1 , 2.3.3.4
4.3.1.1(a) Vehicle.
PSpecs*: 2.3.3.4
4.3.1.1(b) Driver.
PSpecs*: 2.3.3.4
4.3.1.2 The Roadside Capability shall provide the capability to provide warnings of any safety problem that has been identified.
PSpecs*: 2.3.1 , 2.3.7 , 2.4.2 , 2.4.7
4.3.1.3 The Roadside Capability shall provide capability to log the passing of each vehicle and the associated results from the decision of whether to request the vehicle to pull in or continue without stopping.
PSpecs*: 2.3.3.1 , 2.3.3.4 , 2.3.6
4.3.1.4 The Roadside Capability shall provide the capability to automatically make a decision as to whether to allow each vehicle to pass or require them to stop for a check.
PSpecs*: 2.3.3.1 , 2.3.3.4
4.3.1.5 The Roadside Capability shall provide the capability for enforcement officials to manually override the automatically generated decision for vehicles to pull-in for safety inspection.
PSpecs*: 2.3.5
4.3.1.6 The Roadside Capability shall provide the capability to perform pre-trip and post-trip inspections of each vehicle.
PSpecs*: 2.3.3.1 , 2.4.1
4.3.1.7 The Roadside Capability shall provide the capability to have two-way data exchange between the Roadside facility and each vehicle.
PSpecs*: 2.3.1 , 2.3.3.1 , 2.3.4 , 2.3.7
4.3.2 OBSSM shall include a Vehicle System (VS) that is a part of each vehicle.
PSpecs*: 2.1.2 , 2.1.3 , 2.1.6 , 2.1.7 , 2.2.3 , 2.4.1 , 2.4.2 , 2.4.3 , 2.4.4 , 2.4.5 , 2.4.6 , 2.4.7
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:
PSpecs*: 2.2.3 , 2.4.2 , 2.4.3 , 2.4.4 , 2.4.5 , 2.4.6 , 2.4.7
4.3.2.1(a) Vehicle safety status.
PSpecs*: 2.4.3
4.3.2.1(b) Cargo safety status.
PSpecs*: 2.4.3
4.3.2.1(c) Driver safety status.
PSpecs*: 2.4.3
4.3.2.1(d) Vehicle Identification.
PSpecs*: 2.4.3
4.3.2.1(e) Driver Identification.
PSpecs*: 2.4.3
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.
PSpecs*: 2.4.3 , 2.4.5 , 2.4.6
4.3.2.3 The VS shall provide the capability to have two-way data exchange between each Roadside facility encountered and the vehicle.
PSpecs*: 2.4.1
4.3.2.4 The VS shall include a Vehicle Integrity (VI) function.
PSpecs*: 2.1.2 , 2.1.6 , 2.4.2 , 2.4.3 , 2.4.4 , 2.4.7
4.3.2.4.1 The VI shall monitor on-board sensors to detect a breach or tamper event.
PSpecs*: 2.4.3
4.3.2.4.2 The VI shall provide the capability to collect and process vehicle integrity information.
PSpecs*: 2.4.2 , 2.4.3 , 2.4.7
4.3.2.4.3 The VI shall provide integrity event information to the driver and carrier's dispatch function.
PSpecs*: 2.1.2 , 2.1.6 , 2.4.4
4.3.2.5 The VS shall include a Vehicle Asset Management (VAM) function.
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.1 VAM shall provide the capability to monitor and track the location and movement of commercial vehicles by authorized users.
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.2 VAM shall be capable of collecting and storing information on the operating conditions of the commercial vehicle to support fleet maintenance planning, including but not limited to:
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.2(a) System status (e.g. status of brake system, oil pressure, etc.)
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.2(b) Engine temperature
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.2(c) Mileage
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.2(d) Tire wear
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.2(e) Brake wear
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.2.5.2(f) Belt wear
PSpecs*: 2.1.2 , 2.1.3 , 2.1.7
4.3.3 OBSSM shall include a Freight Security Management (FSM) function
PSpecs*: 2.1.1.1 , 2.1.1.7 , 2.1.5 , 2.1.6 , 2.3.4 , 2.4.2 , 2.4.7 , 2.4.9 , 2.7.1 , 2.7.3 , 2.7.5 , 2.7.6 , 2.7.7 , 5.1.1.2
4.3.3.1 FSM shall include a Freight container or trailer Integrity (FI) function
PSpecs*: 2.3.4 , 2.7.1 , 2.7.5 , 2.7.6
4.3.3.1.1 FI shall monitor freight container or trailer data to detect a breach or tamper event.
PSpecs*: 2.7.1
4.3.3.1.2 FI shall provide the capability to process freight container or trailer integrity data.
PSpecs*: 2.7.5
4.3.3.1.3 FI shall support the transmission of freight integrity data to freight data users.
PSpecs*: 2.3.4 , 2.7.1 , 2.7.6
4.3.3.2 FSM shall include a commercial vehicle driver/commercial vehicle/freight container or trailer Assignment Integrity (AI) function.
PSpecs*: 2.1.1.1 , 2.1.1.7 , 2.1.5 , 2.1.6 , 2.4.2 , 2.4.7 , 2.4.9 , 2.7.3 , 2.7.7 , 5.1.1.2
4.3.3.2.1 AI shall provide the capability to plan a driver/commercial vehicle/freight container or trailer assignment for a specific trip.
PSpecs*: 2.1.1.1 , 2.1.5 , 2.7.3 , 2.7.7
4.3.3.2.2 AI shall include the capability to store the driver/commercial vehicle/freight container or trailer assignment information.
PSpecs*: 2.1.1.7
4.3.3.2.3 AI shall include the capability to monitor the identity of the driver.
PSpecs*: 2.4.9
4.3.3.2.4 AI shall include the capability to monitor the identity of the commercial vehicle.
PSpecs*: 2.4.2 , 2.4.7
4.3.3.2.5 AI shall include the capability to monitor the identity of the freight container or trailer.
PSpecs*: 2.4.2 , 2.4.7
4.3.3.2.6 AI shall provide the capability to correlate the identity of the driver, commercial vehicle and freight container or trailer with the planned assignment.
PSpecs*: 2.1.1.7
4.3.3.2.7 AI shall alert authorized freight data users when a driver/commercial vehicle/freight container or trailer mismatch has been detected and verified.
PSpecs*: 2.1.1.7 , 2.1.6 , 5.1.1.2