---

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC

Status:

Existing

Definition:

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC provides traffic control, surveillance, incident detection, and traffic information dissemination. It also has a centralized traffic management center which has interface with VDOT ERO TOC.

Stakeholder:

VDOT ERO Region

Architecture Flow Diagrams
which include VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC:

• VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT Critical Infrastructure Security System
• VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT ERO TOC/ATMS
• VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC Field Equipment
• VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT Hampton Roads District Maintenance and Construction Residencies
• VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT VaTraffic
• VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VSP Center

Architecture Flows
to/from the VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC:

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT Critical Infrastructure Security System

• alert status


• threat information


• traffic images

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT ERO TOC/ATMS

• device control request


• device data


• device status


• emergency traffic control request


• emergency traffic coordination


• evacuation information


• incident information


• incident response coordination


• resource deployment status


• resource request


• traffic images


• transportation system status

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC Field Equipment

• barrier system control


• environmental sensors control


• roadway dynamic signage data


• traffic detector control


• traffic metering control


• video surveillance control

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT Hampton Roads District Maintenance and Construction Residencies

• equipment maintenance request

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT VaTraffic

• incident information


• incident response coordination


• incident response status


• transportation system status

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VSP Center

• incident information


• incident response coordination


• resource coordination

VDOT Critical Infrastructure Security SystemVDOT Hampton Roads Bridge-Tunnel (HRBT) TOC

• alert notification


• threat information


• traffic images


• transportation system status

VDOT ERO TOC/ATMSVDOT Hampton Roads Bridge-Tunnel (HRBT) TOC

• emergency traffic control request


• emergency traffic coordination


• evacuation information


• incident information


• maint and constr work plans


• resource deployment status


• road network conditions


• traffic images


• transportation system status

VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC Field EquipmentVDOT Hampton Roads Bridge-Tunnel (HRBT) TOC

• barrier system status


• environmental sensor data


• field equipment status


• roadway dynamic signage status


• traffic detector data


• traffic images


• traffic metering status

VDOT Hampton Roads District Maintenance and Construction ResidenciesVDOT Hampton Roads Bridge-Tunnel (HRBT) TOC

• equipment maintenance status

VDOT VaTrafficVDOT Hampton Roads Bridge-Tunnel (HRBT) TOC

• incident information


• incident response coordination


• incident response status


• transportation system status

VSP CenterVDOT Hampton Roads Bridge-Tunnel (HRBT) TOC

• alert notification coordination


• emergency plan coordination


• evacuation coordination


• incident response coordination


• resource coordination

National ITS Architecture Subsystems
mapped to the VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC:

• Archived Data System Subsystem
• Archived Data User System Terminator
• Data Distribution System Subsystem
• Emergency Management Center Subsystem
• Maint and Constr Management Center Subsystem
• Traffic Management Center Subsystem
• Transit Vehicle OBE Subsystem
• Transportation Information Center Subsystem

National ITS Architecture Services
associated with VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC:

• MC05 - Roadway Maintenance and Construction - Virginia ER Region -- (Graphic)
• TM01 - Infrastructure-Based Traffic Surveillance - VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC -- (Graphic)
• TM05 - Freeway Control - VDOT Hampton Roads Bridge - Tunnel (HRBT) TOC -- (Graphic)
• TM19 - Roadway Closure Management - Virginia ER Region -- (Graphic)
• TM24 - Tunnel Management (Tunnel Guide Lights for Speed Management) -- (Graphic)

National ITS Architecture Functional Requirements
associated with VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC:

Emergency Secure Area Surveillance

1. The center shall monitor maintenance status of the security sensor field equipment.
2. The center shall respond to control data from center personnel regarding security surveillance data collection, processing, threat detection, and image matching.
3. The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).
4. The center shall identify potential security threats based on collected security surveillance data.
5. The center shall exchange surveillance data with other emergency centers.
6. The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways). The data may be raw or pre-processed in the field.

TMC Incident Detection

1. The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.
2. The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.
3. The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.
4. The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters and traveler information service providers.
5. The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
6. The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.

TMC Reversible Lane Management

1. The center shall monitor the use of reversible lanes and detect wrong-way vehicles in reversible lanes using sensor and surveillance information, and the current lane control status (which direction the lane is currently operating).
2. The center shall provide the capability for center personnel to control access and management of reversible lane facilities, including the direction of traffic flow changes during the day, especially between the peak hours and dedication of more lanes to the congestion direction during special events.
3. The center shall remotely control automated reversible lane equipment and driver information systems (such as lane control signals) that control traffic in reversible lanes on surface streets.
4. The center shall remotely control devices to detect traffic in reversible lanes, including wrong-way vehicles.
5. The center shall collect fault data for the reversible lane field equipment and send to the maintenance center for repair.
6. The center shall collect operational status for the reversible lane field equipment.
7. The center shall remotely control automated reversible lane equipment and driver information systems (such as lane control signals) that control traffic in reversible lanes on freeways.

TMC Traffic Metering

1. The center shall collect fault data from ramp meters, interchange meters, and mainline meters.
2. The center shall implement control strategies, under control of center personnel, on some or all of the freeway network devices (e.g. ramp meters, interchange meters, and mainline meters), based on data from sensors monitoring traffic conditions upstream, downstream, and queue data on the approaches to the meters.
3. The center shall collect operational status from ramp meters, interchange meters, and mainline meters and compare against the control information sent by the center.
4. The center shall remotely control systems to manage use of the freeways, including ramp, interchange, and mainline metering.

TMC Traffic Information Dissemination

1. The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
2. The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management centers, parking facilities, and traveler information providers.
3. The center shall retrieve locally stored traffic information, including current and forecasted traffic information, road and weather conditions, traffic incident information, information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements), and the definition of the road network itself.
4. The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.

TMC Basic Surveillance

1. The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.
2. The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each).
3. The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
4. The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.

TMC Incident Dispatch Coordination

1. The center shall receive inputs from emergency management and transit management centers to develop an overall status of the transportation system including emergency transit schedules in effect and current status and condition of the transportation infrastructure.
2. The center shall coordinate information and controls with other traffic management centers.
3. The center shall exchange road network status assessment information with emergency management and maintenance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
4. The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
5. The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, border crossings, and rail operations centers.
6. The center shall share resources with allied agency centers to implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination with maintenance centers.
7. The center shall exchange incident information with emergency management centers, maintenance and construction centers, transit centers, information service providers, and the media including description, location, traffic impact, status, expected duration, and response information.
8. The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
9. The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.

Archive Data Repository

1. The center shall collect data from centers.
2. The center shall collect data catalogs from one or more data sources. A catalog describes the data contained in the collection of archived data and may include descriptions of the schema or structure of the data, a description of the contents of the data; e.g., time range of entries, number of entries; or a sample of the data (e. g. a thumbnail).
3. The center shall store collected data in an information repository.
4. The center shall perform quality checks on collected data.
5. The center shall notify the system operator of errors related to data collection, analysis and archival.
6. The center shall include capabilities for archive to archive coordination.

TMC Barrier System Management

1. The center shall collect barrier system fault data and send to the maintenance center for repair.
2. The center shall collect barrier system operational status.
3. The center shall accept requests for barrier system activation from other centers and from center personnel to support emergency response and detours.
4. The center shall remotely control barrier systems for transportation facilities and infrastructure. Barrier systems include automated or remotely controlled gates, barriers and other systems that manage entry to roadways.

Emergency Secure Area Alarm Support

1. The center shall collect silent and audible alarms received from travelers in secure areas (such as transit stops, rest areas, park and ride lots, modal interchange facilities).
2. After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.
3. After the alarm message becomes a verified incident, the center shall determine the appropriate response.
4. The center shall determine whether the alarm message indicates an emergency that requires the attention of public safety agencies, and forward alarm message data to the appropriate agency as necessary.
5. The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as directed by the personnel.

Emergency Secure Area Sensor Management

1. The center shall request activation of barriers and safeguards on request from center personnel.
2. The center shall maintain the status of the security sensor field equipment.
3. The center shall identify potential security threats based on collected security sensor data.
4. The center shall remotely monitor and control security sensor data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways). The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), infrastructure condition and integrity, intrusion and motion, and object detection sensors. The data may be raw or pre-processed in the field.
5. The center shall exchange security sensor data with other emergency centers.
6. The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations, and other emergency management centers.