Regional Architecture Logo
 

Send Your Comments

E-Mail

On-board CV Electronic Data Equipment Package

Architecture Geographic Scope

Description:

This Equipment package provides the Commercial Vehicle Subsystem the capability for two-way data exchange between the vehicle and the roadside facility with the transmission of information such as status of driver, vehicle, and carrier IDs and cargo information. The driver, vehicle and carrier are identified via the tag so that actual weight from roadside mainline weigh-in-motion may be checked. This includes only the equipment on the commercial vehicle including a processor/tag for identification, especially a HAZMAT identification. The actual reading and processing required for the credential checking and weigh-in-motion will be performed by the roadside.

 

Included in:

Commercial Vehicles

Processes:

2.2.3Provide CV Driver Electronic Credential and Tax Filing Interface
2.3.7Produce Commercial Vehicle Driver Message on Vehicle
2.4.2Collect On-board Commercial Vehicle Sensor Data
2.4.3Analyze Commercial Vehicle On-board Data
2.4.4Provide Commercial Vehicle Driver Interface
2.4.6Provide Commercial Vehicle On-board Data Store Interface
2.6.2Transmit Commercial Vehicle Tag Data
2.6.3Provide Commercial Driver Tag Data Interface
2.6.4Provide Lock Tag Data Interface
2.6.5Manage Commercial Vehicle Tag Data Store
  

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.4Fixed Facility shall include processing to issue pull-in for safety inspection signals of the following type:
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(b)Vehicle Credentials.
4.1.1.6(c)Driver Credentials/Status.
4.1.1.6(d)Vehicle Weight Information.
4.1.1.6(e)Tax Payment Account.
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.2Vehicle System shall provide the capability for each vehicle to establish two-way communications with fixed facilities.
4.2AUTOMATED ROADSIDE SAFETY INSPECTION
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.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.1.7The FF shall provide the capability to have two-way data exchange between the Roadside facility and each vehicle.
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.4COMMERCIAL VEHICLE ADMINISTRATIVE PROCESSES
4.4.1CVAP shall include an Electronic Purchase Of Credentials (EPC) function with capabilities that include but are not limited to the following:
4.4.2CVAP shall include an Automated Mileage and Fuel Reporting and Auditing (AMFRA) function that includes but is not limited to the following:
4.4.3CVAP shall include an International Border Electronic Clearance (IBEC) function.
4.4.3.1IBEC 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.1(a)Driver Clearance.
4.4.3.1(b)Cargo Clearance.
4.4.3.1(c)Vehicle.
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(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.4.3.2(f)Verify Duties Paid.
4.4.3.2(g)Verify Vehicle Identity.
4.4.3.2(h)Verify Vehicle Weight.
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.
4.6COMMERCIAL FLEET MANAGEMENT
4.6.1CFM 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 01-11-2003 using Ronald C. Ice and Associates Web Spinner Technology.