Regional Architecture Logo
 

Send Your Comments

E-Mail

Roadway Speed Monitoring Equipment Package

Architecture Geographic Scope

Description:

Vehicle speed sensors that detect excessive vehicle speeds, informing drivers, centers and/or enforcement agencies of speed violations.

 

Included in:

TxDOT Lufkin District Field Sensors

Functional Requirements:

1The field element shall include sensors to detect vehicle speeds, under traffic or maintenance center control.
2The field element shall include sensors to detect vehicle speeds, under enforcement agency control.
3If the speed detected by vehicle speed sensors is determined to be excessive, the field element shall provide a safe speed advisory to passing drivers via a driver information system (such as portable messages signs, etc.).
4The field element shall base speed advisories to passing drivers on environmental conditions.
5The field element shall monitor notify an enforcement agency when a speed violation is detected.
6The field element shall return operational status for the vehicle speed sensors to the controlling traffic or maintenance center; including measured speeds, warning messages displayed, and violation records.
7The field element shall return operational status for the vehicle speed sensors to the enforcement agency.
8The field element shall return fault data for the vehicle speed sensors to the controlling center for repair.
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.5TRAVELER SERVICES INFORMATION
1.5.2TSI shall include an Information Access function that allows travelers to access the available information.
1.5.2.5Information Access shall provide the capability for travelers to access the TSI information via any of, but not limited to, the following methods:
1.5.2.5(a)Highway advisory radio.
1.6TRAFFIC CONTROL
1.6.2TC shall include a Traffic Surveillance function.
1.6.2.1Traffic Surveillance shall include a vehicle detection function with the capability of accurately detecting vehicles in a real-time fashion.
1.6.2.1.1Vehicle detection shall include the capability to determine those vehicles that are HOVs.
1.6.2.2Traffic Surveillance shall include a data collect function to provide the capability to collect data for determining traffic flow and prediction.
1.6.2.2.1The data collect function shall provide the capability to quickly feedback traffic data to the control processes.
1.6.2.3Traffic Surveillance shall include a wide-area surveillance capability to include several jurisdictions.
1.6.2.3.1The wide-area surveillance shall gather speed and flow information.
1.6.2.4TC shall provide the capability to acquire detailed traffic measurements at specific locations.
1.6.3TC shall include a Device Control function.
1.6.3.3The Device Control function shall provide the capability to exercise control over those devices utilized for traffic control.
1.6.3.3.2Device Control shall include the capability to dynamically control traffic signing.
1.6.3.4Device Control shall communicate control data to the following devices.
1.6.3.4(c)Information signs.
1.7INCIDENT MANAGEMENT
1.7.1Incident Management shall provide an Incident Identification function to identify incidents.
1.7.1.1The Incident Identification function shall include the capability to identify predicted incidents.
1.7.1.1.1The Incident Identification function shall use information from the following types of sources, where available, to identify predicted incidents:
1.7.1.1.1(a)Traffic flow sensors.
1.8TRAVEL DEMAND MANAGEMENT
1.8.0ITS shall include a Travel Demand Management (TDM) function. Travel Demand Management will generate and communicate management and control strategies that will support and facilitate the implementation of TDM programs, policies and regulations. It consists of two major functions, which are, (1) Increase Efficiency of Transportation System and (2) Provide Wide Variety of Mobility Options.
1.8.3TDM shall include a sensors/control function.
1.8.3.1The sensors/control function shall provide the capability to gather information needed for the generation of management and control strategies to include, but not be limited to the, following:
1.8.3.1(b)Usage levels.
5.0EMERGENCY MANAGEMENT
5.1EMERGENCY NOTIFICATION AND PERSONAL SECURITY
5.1.3ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas.
5.1.3.5RSEM shall include a Physical Security System (PSS) function.
5.1.3.5.4PSS shall warn travelers of impending security system deployment via local information systems.
5.1.5ENPS shall include a Protect Sensitive Traveler Information (PSTI) function to inhibit distribution of traveler information that is deemed to be sensitive.
5.1.5.1PSTI shall notify transportation operators and information providers when access to information from ITS surveillance and sensor systems must be restricted.
5.1.5.2The PSTI notification shall identify the geographic area, time, specific devices, and/or other information necessary to determine the traveler information that must be protected.
5.1.5.3PSTI shall restrict access to traveler information for the affected area until access restrictions are removed.
5.1.5.4PSTI shall notify transportation operators and information providers when traveler information access restrictions are removed.
8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.3Maintenance and Construction Operations shall provide a Work Zone Management and Safety (WZMS) function, which provides support for the effectiveness, safety, and efficiency of roadway operations during all work zone activities. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Public Safety Organizations, Information Service Providers, and Travelers.
8.1.3.1WZMS shall monitor, control, and direct activity in the vicinity of work zones.
8.1.3.1.1WZMS shall provide information about work zones, including but not limited to:
8.1.3.1.1(a)Anticipated delays
8.1.3.1.1(b)Alternate routes
8.1.3.1.1(c)Suggested speed limit
8.1.3.1.2WZMS shall provide support for automated speed enforcement around work zones.
8.1.3.1.3WZMS shall be able to divert vehicles around work zones via automated lane changing techniques.
8.1.3.1.3.1WZMS shall collect information used to support automated lane changing, including but not limited to:
8.1.3.1.3.1(a)Volume
8.1.3.1.3.1(b)Occupancy
8.1.3.1.3.1(c)Speed
8.1.3.1.3.1(d)Headways
8.1.3.1.3.1(e)Vehicle characteristics
8.1.3.1.3.1(f)Merging distance
8.1.3.3WZMS shall provide systems that communicate reliable, accurate, and timely traveler information, including but not limited to:
8.1.3.3(a)Location, including lane closure information
8.1.3.3(b)Alternate route / detour
8.1.3.3(c)Work zone speed limit
8.1.3.3(d)Delay
  
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-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.