Send Your Comments

Roadside WIM Equipment Package

Description:

Roadside check facility equipment to detect and measure the weight commercial vehicles at high speed. Can include an interface to the credential checking or it can be a stand alone package with display.

Included in:

TxDOT Paris District Weigh-In-Motion Station

Functional Requirements:

1	The roadside check facility equipment shall detect the presence of commercial vehicles and freight equipment approaching a facility. Sensors can differentiate between different types of vehicles and determine the number of axles, gross vehicle weight, weight per axle, and the identification of the vehicle and its cargo.
2	The roadside check facility equipment shall request and input electronic screening data from the commercial vehicle's electronic tag data.
3	The roadside check facility equipment shall send a pass/pull-in notification to the commercial vehicle and its driver based on the information received from the vehicle and the measurements taken. The message may be sent to the on-board equipment in the commercial vehicle or transmitted to the driver using equipment such as dynamic message signs, red-green lights, flashing signs, etc.

User Service Requirements (fully or partially addressed):

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.4	Fixed Facility shall include processing to issue pull-in for safety inspection signals of the following type:
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.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.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.2	The FF shall provide the capability to provide warnings of any safety problem that has been identified.
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.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.

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.