Chesapeake Bay Bridge-Tunnel TOC

Status:

Existing

Definition:

The Chesapeake Bay Bridge-Tunnel (CBBT) TOC represents both of the operations center( one on North and the other on the south). These two operations centers are the failover systems meaning one can takeover the other incase of the other one's failure. These systems currently collects wind and roadway data from bridges comprising the facility. The CBBT TOC shares incident information with VDOT and communicates with Virginia Beach’s EMS for medical assistance during incidents. Additionally, CBBT TOC relies on the Virginia State Police for incident response as back-up to its own police and fire crews.

Stakeholder:

Chesapeake Bay Bridge and Tunnel Commission

Systems Interconnected
with the Chesapeake Bay Bridge-Tunnel TOC


Architecture Flow Diagrams
which include Chesapeake Bay Bridge-Tunnel TOC:

Architecture Flows
to/from the Chesapeake Bay Bridge-Tunnel TOC:

Chesapeake Bay Bridge-Tunnel TOC flows into icon Chesapeake Bay Bridge-Tunnel Field Equipment Chesapeake Bay Bridge-Tunnel TOC flows into icon Chesapeake Bay Bridge-Tunnel Public Safety Vehicles Chesapeake Bay Bridge-Tunnel TOC flows into icon Chesapeake Bay Bridge-Tunnel Toll Collection Field Equipment Chesapeake Bay Bridge-Tunnel TOC flows into icon VDOT Hampton Roads TOC Chesapeake Bay Bridge-Tunnel TOC flows into icon VSP Center Chesapeake Bay Bridge-Tunnel TOC flows into icon VSP Mobile Unified Command Center Chesapeake Bay Bridge-Tunnel Field Equipmentflows into iconChesapeake Bay Bridge-Tunnel TOC Chesapeake Bay Bridge-Tunnel Public Safety Vehiclesflows into iconChesapeake Bay Bridge-Tunnel TOC Chesapeake Bay Bridge-Tunnel Toll Collection Field Equipmentflows into iconChesapeake Bay Bridge-Tunnel TOC VDOT Hampton Roads TOCflows into iconChesapeake Bay Bridge-Tunnel TOC VSP Centerflows into iconChesapeake Bay Bridge-Tunnel TOC VSP Mobile Unified Command Centerflows into iconChesapeake Bay Bridge-Tunnel TOC Weather Service Providersflows into iconChesapeake Bay Bridge-Tunnel TOC

National ITS Architecture Subsystems
mapped to the Chesapeake Bay Bridge-Tunnel TOC:

National ITS Architecture Services
associated with Chesapeake Bay Bridge-Tunnel TOC:

National ITS Architecture Functional Requirements
associated with Chesapeake Bay Bridge-Tunnel TOC:

Center Secure Area Surveillance
  1. 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.
  2. The center shall exchange surveillance data with other emergency centers.
  3. The center shall identify potential security threats based on collected security surveillance data.
  4. 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).
  5. The center shall remotely control security surveillance devices on-board transit vehicles.
  6. The center shall match traveler video images against a database from the Alerting and Advisory Systems of known images that may represent criminals and terrorists.
  7. The center shall exchange traveler images with other emergency management centers to support traveler image matching.
  8. The center shall respond to control data from center personnel regarding security surveillance data collection, processing, threat detection, and image matching.
  9. The center shall monitor maintenance status of the security sensor field equipment.
Center Secure Area Sensor Management
  1. 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.
  2. The center shall exchange security sensor data with other emergency centers.
  3. The center shall identify potential security threats based on collected security sensor data.
  4. The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat analysis processing.
  5. The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations, and other emergency management centers.
  6. The center shall request activation of barriers and safeguards on request from center personnel.
  7. The center shall monitor maintenance status of the security sensor field equipment.
Toll Administration
  1. The center shall manage toll transactions, including maintaining a log of all transactions and toll pricing structure information.
  2. The center shall dynamically price tolls based on current traffic condition information.
  3. For electronic toll payments requiring financial payment, the center shall process the financial information from toll plazas and manage an interface to a Financial Institution.
  4. The center shall manage a local billing database for toll customers.
  5. The center shall manage the details of toll payment violations based on vehicle information from the toll plaza, registration information from the Department of Motor Vehicles, invalid payment information from a Financial Institution, and previous violation information stored locally, and report such violations to appropriate law enforcement agencies.
  6. The center shall calculate traffic flow based on timestamped toll transactions for vehicle travel between successive toll plazas and send to other agencies.
  7. The center shall respond to changes in toll prices from the Toll Administrator.
  8. The center shall support requests for advanced toll payment and provide this information to its toll plazas.
  9. The center shall support wide-area alerts from emergency centers by passing on the information to its toll plazas and the Toll Administrator.
  10. The center shall support toll transactions by commercial fleet operators.
Toll Data Collection
  1. The center shall collect toll operational data and pricing data.
  2. The center shall assign quality control metrics and meta-data to be stored along with the data. Meta-data may include attributes that describe the source and quality of the data and the conditions surrounding the collection of the data.
  3. The center shall receive and respond to requests from ITS Archives for either a catalog of the toll data or for the data itself.
  4. The center shall be able to produce sample products of the data available.
Collect Traffic Surveillance
  1. The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
  2. The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
  3. The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.
  4. The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution.
  5. The center shall maintain a database of surveillance and sensors and the freeways, surface street and rural roadways, e.g. where they are located, to which part(s) of the network their data applies, the type of data, and the ownership of each link (that is, the agency or entity responsible for collecting and storing surveillance of the link) in the network.