Regional Architecture Logo
 

Send Your Comments

E-Mail

Roadside Electronic Screening Equipment Package

Architecture Geographic Scope

Description:

This Equipment package provides the Commercial Vehicle Check Subsystem the capabilities for two-way communication with approaching properly equipped commercial vehicles at mainline speeds, reading tags for automated vehicle identification and credential checking. There will be a capability to appropriately screen all vehicles, not just those that are equipped. This Equipment package shall be able to process the data from the commercial vehicles along with accessed database information to determine whether a pull-in message is needed or to generate random pull-in messages with provisions for facility operators and enforcement officials to have manual override capabilities. Support shall be provided to both interstate and intrastate carriers.

 

Included in:

DPS Electronic Screening Stations
US BCBP Electronic Clearance System

Processes:

2.3.1Produce Commercial Vehicle Driver Message at Roadside
2.3.2.1Administer Commercial Vehicle Roadside Credentials Database
2.3.2.2Process Screening Transactions
2.3.3.4Carry-out Commercial Vehicle Roadside Safety Screening
2.3.4Detect Commercial Vehicle
2.3.5Provide Commercial Vehicle Roadside Operator Interface
2.3.6Provide Commercial Vehicle Reports
  

User Service Requirements (fully or partially addressed):

4.0COMMERCIAL VEHICLE OPERATIONS
4.1COMMERCIAL VEHICLE ELECTRONIC CLEARANCE
4.1.0ITS shall include a Commercial Vehicle Electronic Clearance (CVEC) capability.
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.1Fixed Facility shall provide the capability for state participation in the CVEC program to be voluntary.
4.1.1.2Fixed Facility shall provide the capability to support the enrollment of vehicles/carriers in the CVEC program.
4.1.1.3Fixed Facility shall provide the capability to accommodate both interstate and intrastate vehicles/carriers.
4.1.1.4Fixed Facility shall include processing to issue pull-in for safety inspection signals of the following type:
4.1.1.4(a)Automatically generated from Pass/Need To Stop tests.
4.1.1.4(b)Randomly generated.
4.1.1.4(c)Manually generated.
4.1.1.5Fixed Facility shall provide the facility operator the capability to manually override the issuance of automatically and randomly generated Pull-In requests.
4.1.1.6When making the "Pass/Need To Stop" determination the Fixed Facility shall perform checks on the following:
4.1.1.7Fixed Facility shall provide the capability to establish two-way communications with each vehicle approaching the facility.
4.1.1.8Fixed Facility shall include the capability to access and quickly update information on vehicle problems that are detected.
4.1.2CVEC shall include a Vehicle System capability
4.1.2.2Vehicle System shall provide the capability for each vehicle to establish two-way communications with fixed facilities.
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.0ITS shall include an Automated Roadside Safety Inspection (ARSI) capability.
4.2.1The ARSI capability shall include a Roadside Facility (RF) function that improves the ability to perform safety inspection through the use of automation.
4.2.1.1RF shall provide a processing capability that automates the roadside inspection tasks.
4.2.1.2RF shall include the capability to perform brake inspections at the roadside.
4.2.1.3RF shall include the capability for operators to use hand held devices to rapidly inspect vehicle and driver components that produce the following:
4.2.1.3(a)Pass/Fail results.
4.2.1.3(b)Data on actual condition.
4.2.1.3(c)Data on expected life projections.
4.2.1.4RF shall collect, store, maintain and provide real-time on-line interactive access to historical safety data at the roadside facility.
4.2.1.6RF shall provide the capability to automatically identify to the enforcement personnel approaching vehicles that have been flagged as potentially needing maintenance or put out of service.
4.2.2The ARSI capability shall include a Vehicle System (VS) function.
4.2.2.2The VS architecture shall provide the capability to be developed and integrated as a phased implementation.
4.2.2.5The VS shall include an on-board safety status monitoring system that is accessible from the roadside.
4.3ON-BOARD SAFETY MONITORING
4.3.0ITS shall include an On-Board Safety Monitoring (OBSM) function, that provides monitoring and warnings of safety problems. Of 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. Requirements for On-Board Safety Monitoring are given below:
4.3.1OBSM shall include a Fixed Facility (FF) capability for the analysis and control of safety information.
4.3.1.1The FF shall provide the capability to analyze data received from each vehicle approaching and determine the identification of:
4.3.1.1(a)Vehicle.
4.3.1.1(b)Driver.
4.3.1.2The FF shall provide the capability to provide warnings of any safety problem that has been identified.
4.3.1.3The FF 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.
4.3.1.4The FF 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.
4.3.1.5The FF shall provide the capability for enforcement officials to manually override the automatically generated decision for vehicles to pull-in for safety inspection.
4.3.1.7The FF shall provide the capability to have two-way data exchange between the Roadside facility and each vehicle.
4.4COMMERCIAL VEHICLE ADMINISTRATIVE PROCESSES
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.2(b)Electronic Vehicle Log.
  
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-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.