Regional Architecture Logo
 

Send Your Comments

E-Mail

On-board Cargo Monitoring Equipment Package

Architecture Geographic Scope

Description:

On-board systems monitoring the location and status of the commercial vehicle and its cargo. Sends the data on to appropriate centers and roadside facilities, including emergency management in the case of HAZMAT incidents.

 

Included in:

Commercial Vehicles
Rail Operators Rail Cars

Functional Requirements:

1The commercial vehicle shall compute the location of the commercial vehicle and its freight equipment based on inputs from a vehicle location determination function.
2The commercial vehicle shall monitor on-board systems and record measures such as weight, vehicle security status, vehicle safety status, vehicle identity, driver status, driver safety status, distance traveled, and brake condition.
3The commercial vehicle shall monitor information concerning the freight equipment including cargo type, HAZMAT designation (if any) for the cargo, cargo weight, the type of container in which the cargo is held, safety condition of the cargo, etc.
4The commercial vehicle shall forward information concerning the freight equipment on to its fleet and freight management center as well as the roadside check facility.
5The commercial vehicle shall send notification of a hazmat spill to appropriate emergency management center in case of an incident including the information from cargo sensors, vehicle location, and the carrier identification.
  

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 AND SECURITY MONITORING
4.3.1OBSSM 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.2OBSSM 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.3.2.4The VS shall include a Vehicle Integrity (VI) function.
4.3.2.4.1The VI shall monitor on-board sensors to detect a breach or tamper event.
4.3.2.4.2The VI shall provide the capability to collect and process vehicle integrity information.
4.3.3OBSSM shall include a Freight Security Management (FSM) function
4.3.3.2FSM shall include a commercial vehicle driver/commercial vehicle/freight container or trailer Assignment Integrity (AI) function.
4.3.3.2.4AI shall include the capability to monitor the identity of the commercial vehicle.
4.3.3.2.5AI shall include the capability to monitor the identity of the freight container or trailer.
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 SECURITY AND INCIDENT RESPONSE
4.5.0ITS shall include a Hazardous Materials (HAZMAT) Security and Incident Response (HSIR) service.
4.5.1HSIR 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.
4.5.4HSIR shall include a HAZMAT Security (HS) function.
4.5.4.3HS shall include a Driver Authentication function (DA)
4.5.4.3.3DA shall include the capability to notify the vehicles dispatch function if an unauthorized driver attempts to operate the vehicle.
4.5.4.3.4DA shall include the capability to safely disable a vehicle if an unauthorized driver attempts to operate the vehicle.
4.5.4.3.5DA shall include the capability to allow a vehicles dispatch function to safely disable the vehicle.
4.5.4.3.6DA shall include the capability to notify public safety if an unauthorized driver attempts to operate the vehicle.
4.5.4.3.7DA shall include the capability to notify traffic management if an unauthorized driver attempts to operate the vehicle.
  
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 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.