New Jersey Statewide and Regional ITS Architectures
Menu
Region Home
Stakeholders
Inventory by Stakeholder
Inventory by Entity
Sausage Diagram
Market Packages by Functional Area
Market Packages by Stakeholder
Market Package Descriptions
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

Equipment Package: Roadside Electronic Screening

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: DRJTBC Facility Commercial Vehicle Check
NJSP Commercial Carrier/Safety Inspection Unit
Other Facility (Toll) Commercial Vehicle Check
PANYNJ Port Commerce Terminal Access Equipment
Processes: 2.3.1 - Produce Commercial Vehicle Driver Message at Roadside
2.3.2.1 - Administer Commercial Vehicle Roadside Credentials Database
2.3.2.2 - Process Screening Transactions
2.3.3.4 - Carry-out Commercial Vehicle Roadside Safety Screening
2.3.4 - Detect and Classify Commercial Vehicles and Freight Equipment
2.3.5 - Provide Commercial Vehicle Roadside Operator Interface
2.3.6 - Provide Commercial Vehicle Reports
User Service Requirements: 4.0 - COMMERCIAL VEHICLE OPERATIONS
4.1 - COMMERCIAL VEHICLE ELECTRONIC CLEARANCE
4.1.0 - ITS shall include a Commercial Vehicle Electronic Clearance (CVEC) capability.
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.1 - Fixed Facility shall provide the capability for state participation in the CVEC program to be voluntary.
4.1.1.2 - Fixed Facility shall provide the capability to support the enrollment of vehicles/carriers in the CVEC program.
4.1.1.3 - Fixed Facility shall provide the capability to accommodate both interstate and intrastate vehicles/carriers.
4.1.1.4 - Fixed 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.5 - Fixed Facility shall provide the facility operator the capability to manually override the issuance of automatically and randomly generated Pull-In requests.
4.1.1.6 - When making the "Pass/Need To Stop" determination the Fixed Facility shall perform checks on the following:
4.1.1.7 - Fixed Facility shall provide the capability to establish two-way communications with each vehicle approaching the facility.
4.1.1.8 - Fixed Facility shall include the capability to access and quickly update information on vehicle problems that are detected.
4.1.2 - CVEC shall include a Vehicle System capability
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.0 - ITS shall include an Automated Roadside Safety Inspection (ARSI) capability.
4.2.1 - The 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.1 - RF shall provide a processing capability that automates the roadside inspection tasks.
4.2.1.2 - RF shall include the capability to perform brake inspections at the roadside.
4.2.1.3 - RF 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.4 - RF shall collect, store, maintain and provide real-time on-line interactive access to historical safety data at the roadside facility.
4.2.1.6 - RF 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.2 - The ARSI capability shall include a Vehicle System (VS) function.
4.2.2.2 - The VS architecture shall provide the capability to be developed and integrated as a phased implementation.
4.2.2.5 - The VS shall include an on-board safety status monitoring system that is accessible from the roadside.
4.3 - ON-BOARD SAFETY AND SECURITY MONITORING
4.3.0 - ITS shall include an On-Board Safety and Security Monitoring (OBSSM) function, that provides monitoring and warnings of safety and security problems. For safety related issues, the 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. For security related issues, the commercial vehicle driver and authorized freight data users are informed of any problems related to freight container, trailer or commercial vehicle integrity. For commercial vehicle driver/commercial vehicle/freight container or trailer assignment mismatches, authorized freight data users are informed of a potential problem. Requirements for On-Board Safety and Security Monitoring are given below:
4.3.1 - OBSSM shall include a Fixed Facility (FF) capability for the analysis and control of safety information.
4.3.1.1 - The 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.2 - The FF shall provide the capability to provide warnings of any safety problem that has been identified.
4.3.1.3 - The 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.4 - The 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.5 - The 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.7 - The FF shall provide the capability to have two-way data exchange between the Roadside facility and each vehicle.
4.3.3 - OBSSM shall include a Freight Security Management (FSM) function
4.3.3.1 - FSM shall include a Freight container or trailer Integrity (FI) function
4.3.3.1.3 - FI shall support the transmission of freight integrity data to freight data users.
4.4 - COMMERCIAL VEHICLE ADMINISTRATIVE PROCESSES
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.2(b) - Electronic Vehicle Log.
4.5 - HAZARDOUS MATERIAL SECURITY AND INCIDENT RESPONSE
4.5.4 - HSIR shall include a HAZMAT Security (HS) function.
4.5.4.2 - HS shall provide a roadside security sensitive HAZMAT security (RHS) function.
4.5.4.2.1 - RHS shall include the capability for detection of security sensitive HAZMAT shipments.
4.5.4.2.2 - RHS shall include the capability for classification of security sensitive HAZMAT shipments.
4.5.4.2.3 - RHS shall provide the capability to correlate a security sensitive HAZMAT vehicle detection with its authorized activity.
4.5.4.2.4 - RHS shall include the capability to notify public safety agencies, including those having jurisdiction over the location, when unauthorized security sensitive HAZMAT activity has been detected and verified.
4.5.4.2.5 - RHS shall include the capability to notify traffic management agencies when unauthorized security sensitive HAZMAT activity has been detected and verified.

Last updated: 02-08-05