Regional Architecture Logo
 

Send Your Comments

E-Mail

Roadway Incident Detection Equipment Package

Architecture Geographic Scope

Description:

Field elements that provide video images of traffic conditions, including advanced CCTV cameras with built-in incident detection algorithms.

 

Included in:

Angelina Neches River Authority Flood Detectors
Lower Neches Valley Flood Detectors
Sabine River Authority Flood Warning Devices
Trinity River Authority Flood Detectors

Functional Requirements:

1The field element shall collect, process, and send traffic images to the center for further analysis and distribution.
2The field element shall remotely process video data and provide an indication of potential incidents to the traffic management center.
3The field element's video devices shall be remotely controlled by a traffic management center.
4The field element shall provide operational status and fault data for the incident detection devices to the traffic management center.
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
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.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.7.1.2The Incident Identification function shall include the capability to identify existing (both planned and unplanned) incidents.
1.7.1.2.2The Incident Identification function shall determine and continuously monitor at least the following characteristics of each existing incident:
1.7.1.2.2(a)Type (including Terrain Hazards).
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.
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.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.2WZMS shall support the management of data about work zones.
8.1.3.2.4WZMS shall provide information on work zone activities to other agencies, including but not limited to:
8.1.3.2.4(e)Traffic management systems
  
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.