Maui Regional ITS Architecture

Element Expanded Functional Requirements: HDOT-HWY-M Traffic Operations Center


Functional Area: 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 equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each )
  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.
Functional Area: 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 and traveler information service providers.
  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 support requests from emergency management centers and border inspection systems to remotely control sensor and surveillance equipment located in the field.
  6. The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.
  7. The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.
Functional Area: 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 support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption.
  4. 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.
  5. 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.
  6. 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.
  7. The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
  8. The center shall monitor incident response performance and calculate incident response and clearance times.
  9. 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.
  10. The center shall coordinate information and controls with other traffic management centers.
  11. 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.
  12. 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.
  13. The center shall respond to requests from border agencies to implement special traffic control measures (e.g. lane assignments by vehicle type) on the approaches to a border crossing.
Functional Area: TMC Multimodal Coordination
  1. The center shall respond to requests from transit management centers for signal priority at one or more intersections along a particular transit route.
  2. The center shall exchange information with transit management centers including details current transit routes, the level of service on each route, and the progress of individual vehicles along their routes.
Functional Area: 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.).
Functional Area: TMC Signal Control
  1. The center shall remotely control traffic signal controllers.
  2. The center shall accept notifications of pedestrian calls.
  3. The center shall collect traffic signal controller operational status and compare against the control information sent by the center.
  4. The center shall collect traffic signal controller fault data from the field.
  5. The center shall manage (define, store and modify) control plans to coordinate signalized intersections, to be engaged at the direction of center personnel or according to a daily schedule.
  6. The center shall implement control plans to coordinate signalized intersections based on data from sensors.
  7. The center shall manage boundaries of the control sections used within the signal system.
  8. The center shall maintain traffic signal coordination including synchronizing clocks throughout the system.
Functional Area: 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.
Functional Area: 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.
Functional Area: 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 remotely monitor video images and audio surveillance data collected in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers). The data may be raw or pre-processed in the field.
  3. The center shall remotely monitor video images and audio surveillance data collected on-board transit vehicles. The data may be raw or pre-processed in the field.
  4. The center shall exchange surveillance data with other emergency centers.
  5. The center shall identify potential security threats based on collected security surveillance data.
  6. The center shall verify potential security threats by correlating security surveillance data from multiple sources.
  7. 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).
  8. The center shall remotely control security surveillance devices in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers).
  9. The center shall remotely control security surveillance devices on-board transit vehicles.
  10. 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.
  11. The center shall exchange traveler images with other emergency management centers to support traveler image matching.
  12. The center shall respond to control data from center personnel regarding security surveillance data collection, processing, threat detection, and image matching.
  13. The center shall monitor maintenance status of the security sensor field equipment.
  14. The center shall remotely monitor video images and audio surveillance data collected in secure areas including facilities and transportation infrastructure. The data may be raw or pre-processed in the field.
Functional Area: 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.
Functional Area: 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. The center shall collect silent and audible alarms received from transit vehicles, originated by the traveler or the transit vehicle operator.
  3. After the alarm message has been received, the center shall generate an alarm acknowledgment to the sender.
  4. After the alarm message becomes a verified incident, the center shall determine the appropriate response.
  5. 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.
  6. The center shall forward the alarm message to center personnel and respond to the traveler or transit vehicle operator as directed by the personnel.
 

The Hawaiian language uses two diacritical markings. The 'okina is a glottal stop; and the kahako is a macron. The State of Hawaii strongly encourages the use of Hawaiian diacritical markings. The National ITS Architecture tool, Turbo Architecture, does not allow for the Hawaiian diacritical markings to be input and as such, customized service package diagrams, operational concepts and other outputs from Turbo are unable to reflect the diacritical markings. To ensure consistency in this ITS Architecture website, no Hawaiian diacritical markings will be used.