Regional Architecture Logo
 

Send Your Comments

 E-Mail

Roadway Equipment Coordination Equipment Package

 Architecture Geographic Scope

Description:

 This equipment package coordinates field equipment that is distributed along the roadway by supporting communications directly between the field equipment. This includes coordination between remote sensors and field devices (e.g., Dynamic Message Signs) and coordination between the field devices themselves (e.g., coordination between traffic controllers that are controlling adjacent intersections.).

 

Included in:

 Brownsville MPO Field Equipment
Cameron County International Bridge Field Equipment
City of Brownsville Field Equipment
City of Harlingen Field Equipment
City of McAllen Field Equipment
City of Pharr Field Equipment
Hidalgo/Reynosa Bridge Field Equipment
Pharr/Reynosa Bridge Field Equipment
Private International Bridge Field Equipment
TxDOT Pharr District DMS
TxDOT Pharr District Flood Monitoring System
TxDOT Pharr District HAR
TxDOT Pharr District Lane Control Signals
TxDOT Pharr District Traffic Signals

Processes:
1.1.1.5Provide Sensor Interface to Other Roadway Devices
1.2.7.8Provide Device Interface to Other Roadway Devices
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.2EN-ROUTE DRIVER INFORMATION
1.2.3DI shall provide an In-vehicle Signing capability.
1.2.3.2The DI In-vehicle Signing function shall include a long term capability to serve more of the traveler's needs.
1.2.3.2.3The In-vehicle Signing function shall provide the capability to utilize data from roadside environmental sensors as inputs to warning messages.
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.0ITS shall include a Traffic Control (TC) function. Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions are provided, which are, (1) Traffic Flow Optimization, (2) Traffic Surveillance, (3) Control, and (4) Provide Information. This will also include control of network signal systems with eventual integration of freeway control.
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.3.3Device Control shall include the capability to control freeway ramp metering.
1.6.3.4Device Control shall communicate control data to the following devices.
1.6.3.4(b)Ramp meters.
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.7.1.1.1(b)Environmental sensors.
1.7.1.1.1(g)Sponsors of special events.
1.7.1.2The Incident Identification function shall include the capability to identify existing (both planned and unplanned) incidents.
1.7.1.2.1The Incident Identification function shall use information from the following types of sources, where available, to identify existing incidents:
1.7.1.2.1(b)Environmental sensors.
1.8.2TDM shall include a processing function.
1.8.2.1The processing function shall provide the capability to generate management and control strategies that facilitate the implementation of policies and regulations designed to address the following:
1.8.2.1(e)Air pollution/emission information and detection.
  
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 07-16-2003 using Ronald C. Ice and Associates Web Spinner Technology.