VDOT Hampton Roads TOC

Status:

Existing

Definition:

The VDOT Hampton Roads TOC is a nerve center of an integrated system of advanced technologies including computer software, traffic cameras,ramp meters. From the Hampton Roads TOC, VDOT monitors and manages traffic, recognizes and responds to incidents, and instantly delivers information to motorists. VDOT Eastern Operations area Traffic Center is responsible for monitoring and managing traffic in Eastern Operations area which includes Hampton Roads and a part of Fredicksburg district area.

Stakeholder:

VDOT ERO Region

Systems Interconnected
with the VDOT Hampton Roads TOC


Architecture Flow Diagrams
which include VDOT Hampton Roads TOC:

Architecture Flows
to/from the VDOT Hampton Roads TOC:

VDOT Hampton Roads TOC flows into icon APM-Maersk Terminals Operations Center VDOT Hampton Roads TOC flows into icon Chesapeake Bay Bridge-Tunnel TOC VDOT Hampton Roads TOC flows into icon City of Chesapeake TMC VDOT Hampton Roads TOC flows into icon City of Hampton TMC VDOT Hampton Roads TOC flows into icon City of Newport News TMC VDOT Hampton Roads TOC flows into icon City of Norfolk STC VDOT Hampton Roads TOC flows into icon City of Suffolk TOC VDOT Hampton Roads TOC flows into icon City of Virginia Beach TMC VDOT Hampton Roads TOC flows into icon George P. Coleman Bridge Toll Plaza Field Equipment VDOT Hampton Roads TOC flows into icon Hampton Roads Local Public Safety Centers VDOT Hampton Roads TOC flows into icon Hampton Roads Local Public Safety Mobile Centers VDOT Hampton Roads TOC flows into icon Hampton Roads MPO VDOT Hampton Roads TOC flows into icon HRT Operations Centers VDOT Hampton Roads TOC flows into icon James River Drawbridge Field Equipment VDOT Hampton Roads TOC flows into icon Media Outlets VDOT Hampton Roads TOC flows into icon Newport News/ Williamsburg International Airport (NNWIA) VDOT Hampton Roads TOC flows into icon Norfolk International Airport VDOT Hampton Roads TOC flows into icon Private Sector ISP Centers VDOT Hampton Roads TOC flows into icon Research and Data Collection Center VDOT Hampton Roads TOC flows into icon Special Event Promoters VDOT Hampton Roads TOC flows into icon Tourism and Travel Service Information Sources VDOT Hampton Roads TOC flows into icon VDOT ADMS VDOT Hampton Roads TOC flows into icon VDOT Asset Management System VDOT Hampton Roads TOC flows into icon VDOT Critical Infrastructure Security System VDOT Hampton Roads TOC flows into icon VDOT Hampton Roads Bridge-Tunnel (HRBT) TOC VDOT Hampton Roads TOC flows into icon VDOT Hampton Roads District Maintenance and Construction Residencies VDOT Hampton Roads TOC flows into icon VDOT Hampton Roads SSP Vehicles VDOT Hampton Roads TOC flows into icon VDOT Hampton Roads TOC Field Equipment VDOT Hampton Roads TOC flows into icon VDOT Joint Berkley Bridge- Downtown Elizabeth River Tunnel TOC VDOT Hampton Roads TOC flows into icon VDOT Midtown Elizabeth River Tunnel TOC VDOT Hampton Roads TOC flows into icon VDOT Monitor-Merrimac Memorial Bridge-Tunnel (MMMBT) TOC VDOT Hampton Roads TOC flows into icon VDOT Public Affairs VDOT Hampton Roads TOC flows into icon VDOT Remote Workstations VDOT Hampton Roads TOC flows into icon VDOT Richmond TOC VDOT Hampton Roads TOC flows into icon VDOT RTIMIS VDOT Hampton Roads TOC flows into icon VDOT TEOC VDOT Hampton Roads TOC flows into icon VDOT VaTraffic VDOT Hampton Roads TOC flows into icon VDOT Video Clearinghouses VDOT Hampton Roads TOC flows into icon VPA Terminals Operations Center VDOT Hampton Roads TOC flows into icon VSP Center VDOT Hampton Roads TOC flows into icon VSP Mobile Unified Command Center VDOT Hampton Roads TOC flows into icon VSP Vehicles VDOT Hampton Roads TOC flows into icon WAT Operations Center APM-Maersk Terminals Operations Centerflows into iconVDOT Hampton Roads TOC Chesapeake Bay Bridge-Tunnel TOCflows into iconVDOT Hampton Roads TOC City of Chesapeake TMCflows into iconVDOT Hampton Roads TOC City of Hampton TMCflows into iconVDOT Hampton Roads TOC City of Newport News TMCflows into iconVDOT Hampton Roads TOC City of Norfolk STCflows into iconVDOT Hampton Roads TOC City of Suffolk TOCflows into iconVDOT Hampton Roads TOC City of Virginia Beach TMCflows into iconVDOT Hampton Roads TOC George P. Coleman Bridge Toll Plazaflows into iconVDOT Hampton Roads TOC George P. Coleman Bridge Toll Plaza Field Equipmentflows into iconVDOT Hampton Roads TOC Hampton Roads Local Public Safety Centersflows into iconVDOT Hampton Roads TOC Hampton Roads Local Public Safety Mobile Centersflows into iconVDOT Hampton Roads TOC High Rise Drawbridgeflows into iconVDOT Hampton Roads TOC HRT Operations Centersflows into iconVDOT Hampton Roads TOC James River Drawbridgeflows into iconVDOT Hampton Roads TOC James River Drawbridge Field Equipmentflows into iconVDOT Hampton Roads TOC Jordan Drawbridgeflows into iconVDOT Hampton Roads TOC Media Outletsflows into iconVDOT Hampton Roads TOC Newport News/ Williamsburg International Airport (NNWIA)flows into iconVDOT Hampton Roads TOC Norfolk International Airportflows into iconVDOT Hampton Roads TOC Private Sector ISP Centersflows into iconVDOT Hampton Roads TOC Research and Data Collection Centerflows into iconVDOT Hampton Roads TOC Special Event Promotersflows into iconVDOT Hampton Roads TOC VDOT ADMSflows into iconVDOT Hampton Roads TOC VDOT Asset Management Systemflows into iconVDOT Hampton Roads TOC VDOT Critical Infrastructure Security Systemflows into iconVDOT Hampton Roads TOC VDOT ESS Weather Platformflows into iconVDOT Hampton Roads TOC VDOT Hampton Roads Bridge-Tunnel (HRBT) TOCflows into iconVDOT Hampton Roads TOC VDOT Hampton Roads District Maintenance and Construction Residenciesflows into iconVDOT Hampton Roads TOC VDOT Hampton Roads SSP Vehiclesflows into iconVDOT Hampton Roads TOC VDOT Hampton Roads TOC Field Equipmentflows into iconVDOT Hampton Roads TOC VDOT Joint Berkley Bridge- Downtown Elizabeth River Tunnel TOCflows into iconVDOT Hampton Roads TOC VDOT Midtown Elizabeth River Tunnel TOCflows into iconVDOT Hampton Roads TOC VDOT Monitor-Merrimac Memorial Bridge-Tunnel (MMMBT) TOCflows into iconVDOT Hampton Roads TOC VDOT Public Affairsflows into iconVDOT Hampton Roads TOC VDOT Remote Workstationsflows into iconVDOT Hampton Roads TOC VDOT Richmond TOCflows into iconVDOT Hampton Roads TOC VDOT RTIMISflows into iconVDOT Hampton Roads TOC VDOT TEOCflows into iconVDOT Hampton Roads TOC VDOT VaTrafficflows into iconVDOT Hampton Roads TOC VDOT Video Clearinghousesflows into iconVDOT Hampton Roads TOC VPA Terminals Operations Centerflows into iconVDOT Hampton Roads TOC VSP Centerflows into iconVDOT Hampton Roads TOC VSP Mobile Unified Command Centerflows into iconVDOT Hampton Roads TOC VSP Vehiclesflows into iconVDOT Hampton Roads TOC WAT Operations Centerflows into iconVDOT Hampton Roads TOC

National ITS Architecture Subsystems
mapped to the VDOT Hampton Roads TOC:

National ITS Architecture Services
associated with VDOT Hampton Roads TOC:

National ITS Architecture Functional Requirements
associated with VDOT Hampton Roads TOC:

ITS Data Repository
  1. The center shall collect data to be archived from one or more data sources.
  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 the archived data in a focused repository that is suited to a particular set of ITS data users.
  4. The center shall include capabilities for performing quality checks on the incoming archived data.
  5. The center shall include capabilities for error notification on the incoming archived data.
  6. The center shall include capabilities for archive to archive coordination.
  7. The center shall support a broad range of archived data management implementations, ranging from simple data marts that collect a focused set of data and serve a particular user community to large-scale data warehouses that collect, integrate, and summarize transportation data from multiple sources and serve a broad array of users within a region.
  8. The center shall perform quality checks on received data.
  9. The center shall provide the capability to execute methods on the incoming data such as cleansing, summarizations, aggregations, or transformations applied to the data before it is stored in the archive.
  10. The center shall respond to requests from the administrator interface function to maintain the archive data.
  11. When data or a catalog of data is received from the archive, the center shall generate the requested data product for the users systems.
Center 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.
ISP Traveler Data Collection
  1. The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes.
  2. The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities.
  3. The center shall collect, process, and store current and forecast road conditions and surface weather conditions.
  4. The center shall collect, process, and store event information.
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 monitor, analyze, and store multimodal crossing and high occupancy vehicle (HOV) lane sensor data under remote control of the center.
  4. The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.
  5. The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution.
  6. 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.
  7. The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for traffic data.
TMC Freeway Management
  1. The center shall remotely control systems to manage use of the freeways, including ramp meters, mainline metering, and lane controls.
  2. The center shall collect operational status from ramp meters, mainline metering, and lane controls and compare against the control information sent by the center.
  3. The center shall collect fault data from ramp meters, mainline metering, and lane controls.
  4. The center shall implement control strategies, under control of center personnel, on some or all of the freeway network devices (e.g. ramp meters, mainline metering, and lane controls), based on data from sensors monitoring traffic conditions upstream, downstream, and queue data on the ramps themselves.
TMC HOV Lane Management
  1. The center shall remotely control sensors to detect high-occupancy vehicle (HOV) lane usage.
  2. The center shall remotely control driver information systems to notify users of lane status for lanes that become HOV or High Occupancy Toll (HOT) lanes during certain times of the day on freeways.
  3. The center shall remotely control freeway control devices, such as ramp signals and mainline metering and other systems associated with freeway operations that control use of HOV lanes.
  4. The center shall collect traffic flow measures and information regarding vehicle occupancy (i.e., lane usage) in HOV lanes.
  5. The center shall collect operational status for the freeway control devices associated with HOV lane control.
  6. The center shall collect fault data for the freeway control devices associated with HOV lane control for repair.
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 remotely control driver information systems that communicate directly from a center to the vehicle radio (such as Highway Advisory Radios) for dissemination of traffic and other information to drivers.
  3. The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).
  4. The center shall collect fault data for the driver information systems equipment (DMS, HAR, etc.) for repair.
  5. 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.
  6. The center shall distribute traffic data to maintenance and construction centers, transit centers, emergency management centers, and traveler information providers.
  7. The center shall distribute traffic data to the media; the capability to provide the information in both data stream and graphical display shall be supported.
  8. The center shall provide the capability for center personnel to control the nature of the data that is available to non-traffic operations centers and the media.
TMC Regional Traffic Management
  1. The center shall exchange traffic information with other traffic management centers including incident information, congestion data, traffic data, signal timing plans, and real-time signal control information.
  2. The center shall exchange traffic control information with other traffic management centers to support remote monitoring and control of traffic management devices (e.g. signs, sensors, signals, cameras, etc.).
TMC Incident Detection
  1. 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.
  2. The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.
  3. The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, border crossings, and intermodal freight depots.
  4. 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.
  5. The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.
  6. The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.
TMC Incident Dispatch Coordination/Communication
  1. 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.
  2. The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
  3. 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.
  4. 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.
  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 provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
  7. 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.
  8. The center shall coordinate information and controls with other traffic management centers.
  9. The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for traffic incident management.
TMC Evacuation Support
  1. The center shall coordinate planning for evacuation with emergency management centers - including pre-planning activities such as establishing routes, areas to be evacuated, timing, etc.
  2. The center shall support requests from emergency management centers to preempt the current traffic control strategy, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems to support evacuation traffic control plans.
  3. The center shall coordinate information and controls with other traffic management centers.
  4. The center shall coordinate execution of evacuation strategies with emergency management centers - including activities such as setting closures and detours, establishing routes, updating areas to be evacuated, timing the process, etc.
TMC Reversible Lane Management
  1. The center shall remotely control devices to detect traffic in reversible lanes, including wrong-way vehicles.
  2. 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).
  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 freeways.
  4. The center shall collect operational status for the reversible lane field equipment.
  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 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.
Barrier System Management
  1. 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.
  2. The center shall collect barrier system operational status.
  3. The center shall collect barrier system fault data and send to the maintenance center for repair.
  4. The center shall accept requests for barrier system activation from other centers and from center personnel to support emergency response and detours.
Traffic Data Collection
  1. The center shall collect traffic management data such as operational data, event logs, etc.
  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 traffic data or for the data itself.
  4. The center shall be able to produce sample products of the data available.
TMC Transportation Operations Data Collection
  1. The center shall collect real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, special event and incident information.