Regional Architecture Logo
 

Send Your Comments

E-Mail

On-board Cargo Monitoring Equipment Package

Architecture Geographic Scope

Description:

This Equipment package provides the Commercial Vehicle Subsystem the capability to monitor both interstate and intrastate cargo safety such that enforcement and HAZMAT response teams can be provided with timely and accurate information. This includes only the equipment on board the cargo container such as a communication device, possibly the addition of a cell-based radio, and equipment for the processing and storage of cargo material. This can also include optional sensors for temperature, pressure, load leveling, or acceleration depending upon the items monitored. It is already expected that the cargo location devices such as GPS equipment and an integration processor already exist. These items are presented as part of the On-board Trip Monitoring Equipment package.

 

Included in:

Commercial Vehicles
Rail Operators Rail Cars

Processes:

2.4.2Collect On-board Commercial Vehicle Sensor Data
2.4.3Analyze Commercial Vehicle On-board Data
2.4.5Communicate Commercial Vehicle On-board Data to Vehicle Manager
2.4.6Provide Commercial Vehicle On-board Data Store Interface
  

User Service Requirements (fully or partially addressed):

4.0COMMERCIAL VEHICLE OPERATIONS
4.1COMMERCIAL VEHICLE ELECTRONIC CLEARANCE
4.1.1CVEC 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.6When 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.2CVEC shall include a Vehicle System capability
4.1.2.1Vehicle System shall provide the capability to accommodate both interstate and intrastate carriers.
4.1.2.3Vehicle System shall provide the capability for each individual vehicle's or carrier's participation in the process to be on a voluntary basis.
4.2AUTOMATED ROADSIDE SAFETY INSPECTION
4.2.2The ARSI capability shall include a Vehicle System (VS) function.
4.2.2.1VS shall provide a processing capability that automates the roadside inspection tasks.
4.2.2.2The VS architecture shall provide the capability to be developed and integrated as a phased implementation.
4.2.2.3The VS shall include sensors to efficiently check vehicle systems and driver condition.
4.2.2.4The VS shall include the capability for continuous updates to vehicle safety records or an "electronic decal/record" on the vehicle.
4.2.2.5The VS shall include an on-board safety status monitoring system that is accessible from the roadside.
4.2.2.6The VS shall provide an initial automated inspection capability that will expedite and supplement the existing visual and manual inspection processes.
4.3ON-BOARD SAFETY MONITORING
4.3.1OBSM shall include a Fixed Facility (FF) capability for the analysis and control of safety information.
4.3.1.2The FF shall provide the capability to provide warnings of any safety problem that has been identified.
4.3.2OBSM shall include a Vehicle System (VS) that is a part of each vehicle.
4.3.2.1The 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.2The VS shall provide the capability to alert the vehicle driver whenever there is a critical safety problem or potential emergency.
4.4.3.2IBEC 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.5HAZARDOUS MATERIAL INCIDENT RESPONSE
4.5.0ITS shall include a Hazardous Materials (HAZMAT) Incident Response (HIR) service.
4.5.1HIR shall include a HAZMAT Incident Notification (HIN) function.
4.5.1.1HIN 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.2HIN 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.
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 09-26-2004 using Ronald C. Ice and Associates Web Spinner Technology.