Regional Architecture Logo
 

Send Your Comments

E-Mail

Roadway Equipment Coordination Equipment Package

Architecture Geographic Scope

Description:

Field elements that control and send data to other field elements (such as environmental sensors that send data to a DMS or coordination between traffic controllers on adjacent intersections), without center control.

 

Included in:

Angelina Neches River Authority Flood Detectors
City of Livingston ITS Field Equipment
City of Lufkin ITS Field Equipment
City of Nacogdoches ITS Field Equipment
County Road and Bridge Field Equipment
Lower Neches Valley Flood Detectors
Municipal ITS Field Equipment
Sabine River Authority Flood Warning Devices
Trinity River Authority Flood Detectors
TxDOT Lufkin District CCTV
TxDOT Lufkin District DMS
TxDOT Lufkin District Field Sensors
TxDOT Lufkin District HAR
TxDOT Lufkin District Traffic Signals
TxDOT Lufkin District Work Zone Equipment

Functional Requirements:

1The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that provide data and status information to other field element devices (such as dynamic message signs, ramp meters, traffic signals, work zone intrusion alert systems), without center control.
2The field element shall include sensors (such as traffic, environmental, and work zone intrusion detection sensors) that receive control information from other field element devices, without center control.
3The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems, barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that provide data and status information to other field element devices (such as dynamic message signs, traffic controllers on adjacent intersections), without center control.
4The field element shall include devices (such as arterial or freeway controllers, roadway automated treatment systems, barrier and safeguard systems, emissions or pollution systems, and work zone intrusion alert systems) that receive control information from other field element devices, without center control.
  

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.
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.
  
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.