Send Your Comments

On-board CV Electronic Data Equipment Package

Description:

On-board systems exchanging information between the vehicle and the roadside facility with the information such as status of driver, vehicle, carrier IDs and cargo information identified via an electronic tag. Actual weight from roadside mainline weigh-in-motion may be checked.

Included in:

Commercial Vehicles

Functional Requirements:

1	The commercial vehicle shall receive pass/pull-in messages from the roadside check facilities and present them to the driver in either audible or visual forms.
2	The commercial vehicle shall respond to requests to provide data accumulated on-board the vehicle to roadside check facilities for inspection including driver logs, electronic identifiers, credentials, border clearance data, and other screening data such as cargo status, hazmat identifiers, out of service status, vehicle axle weight, vehicle weight, and time.
3	The commercial vehicle shall respond to requests to provide the identity, status and other information from the electronic cargo lock tag, if so equipped, to roadside check facilities, inlcuding border crossings.
4	The commercial vehicle shall support an interface to a commercial vehicle driver that is also acting in the role of a commercial vehicle fleet manager to set up routes, pay necessary taxes, obtain proper credentials, and write the identifiers to the electronic tag for the driver, vehicle, and carrier.

User Service Requirements (fully or partially addressed):

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.4	Fixed Facility shall include processing to issue pull-in for safety inspection signals of the following type:
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.2	Vehicle System shall provide the capability for each vehicle to establish two-way communications with fixed facilities.
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.7	The VS shall provide a two-way Communications capability that facilitates the roadside inspection tasks.
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.1.6	The FF shall provide the capability to perform pre-trip and post-trip inspections of each vehicle.
4.3.1.7	The FF shall provide the capability to have two-way data exchange between the Roadside facility and each vehicle.
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.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.3	The VS shall provide the capability to have two-way data exchange between each Roadside facility encountered and the vehicle.
4.4	COMMERCIAL VEHICLE ADMINISTRATIVE PROCESSES
4.4.1	CVAP shall include an Electronic Purchase Of Credentials (EPC) function with capabilities that include but are not limited to the following:
4.4.2	CVAP shall include an Automated Mileage and Fuel Reporting and Auditing (AMFRA) function that includes but is not limited to the following:
4.4.3	CVAP shall include an International Border Electronic Clearance (IBEC) function.
4.4.3.1	IBEC provides the capability to electronically clear vehicles crossing international borders with those countries adjacent to the United States. IBEC shall provide the capability to clear the following:
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(b)	Verify shipper.
4.4.3.2(c)	Verify Nature of cargo.
4.4.3.2(d)	Verify Carrier safety.
4.4.3.2(e)	Verify credential records.
4.6	FREIGHT MOBILITY
4.6.1	FM shall include a Commercial Vehicle Fleet Management (CVFM) function.
4.6.1.1	CVFM shall include the capability for users to provide commercial drivers and dispatchers with real-time routing information in response to congestion or incidents.

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-12-2005 using Ronald C. Ice and Associates Web Spinner Technology.