Kauai Regional ITS Architecture

Element Expanded Functional Requirements: HDOT-AIR-K Security Dispatch Center


Functional Area: Emergency Dispatch
  1. The center shall dispatch emergency vehicles to respond to verified emergencies under center personnel control.
  2. The center shall store the current status of all emergency vehicles available for dispatch and those that have been dispatched.
  3. The center shall relay location and incident details to the responding vehicles.
  4. The center shall track the location and status of emergency vehicles responding to an emergency based on information from the emergency vehicle.
  5. The center shall store and maintain the emergency service responses in an action log.
  6. The center shall provide the capability for digitized map data to act as the background to the information presented to the emergency system operator.
  7. The center shall receive traffic images to support dispatch of emergency vehicles.
  8. The center shall provide the capability to request remote control of traffic surveillance devices.
  9. The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate resources are dispatched and utilized.
  10. The center shall receive CCTV images from emergency vehicles.
  11. The center shall track the location of emergency personnel in the field.
  12. The center shall provide the capability to request remote control of traffic surveillance devices.
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.
 

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.