• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

5.1.3: Communicate Emergency Status

This process shall receive the emergency service response plans and the status of their implementation for dissemination to other ITS functions. That dissemination shall be subject to sanitization according to prearranged rules, implemented in this process. The process shall also read data about emergency responses from the emergency services action log. All data shall be communicated by the process in standard formats to travelers, drivers, and other ITS functions. In the case of in-vehicle, personal traveler, and transit emergencies, after each emergency becomes a verified incident, the data shall be sent as soon as new status or plan data is received. Dissemination shall be controlled according to rules determined in this process to limit the information transmitted to that information useful to the receiver. Emergency information that is received from the emergency telephone system or E911 operators, shall be disseminated only when the response plan data is first received. That has the effect of only disseminating data on incidents that have been verified, since only verified incidents will have response plans. The process shall also extract data from the emergency service action log on request from processes in other ITS functions, and from the emergency services operator. Communication to in-vehicle processes may include requests for additional information or a set of commands to the vehicle security system. This process shall provide communication to the public by maintaining interfaces with Transit, Driver and Traveler Services, Maintenance and Construction, and Traffic functions as well as the media, rail operations, and the emergency telecommunications system. This latter interface shall support the use of Reverse 911 to accomplish the notification of an emergency situation to residents and business owners in a particular area during an emergency. This process shall support the identification of locations, such as neighborhoods or businesses, impacted by an emergency based on information received by this process. Such information may include the incident location, the severity of the incident, the impacted area, and the nature and schedule of the recovery efforts.

This process is associated with the Emergency Management Center physical object.

This process is associated with the following application objects:

• Emergency Call-Taking
• Emergency Evacuation Support
• Emergency Incident Command
• Emergency Notification Support
• Emergency Response Management

This process is associated with the following data flows:

• deactivate_traveler_information_restrictions_for_traffic - Out
• deactivate_traveler_information_restrictions_for_transit - Out
• deactivate_traveler_information_restrictions_for_travelers - Out
• detailed_emergency_status - In
• emergency_data_for_transit - Out
• emergency_response_data_for_communications - In
• emergency_service_action_log - In
• emergency_service_log_for_archive - Out
• emergency_service_log_output - Out
• emergency_service_log_output_request - In
• emergency_services_corridor_operational_strategies - In
• evacuation_data - Out
• evacuation_data_for_communications - In
• incident_details - Out
• incident_info_from_emerg - Out
• incident_information - Out
• roadway_closure_from_emergency - Out
• tets-incident_acknowledge - Out
• tets-incident_information_dissemination - Out
• tm-emergency_information - Out
• transit_incident_coordination_data - Out
• traveler_information_restrictions_for_traffic - Out
• traveler_information_restrictions_for_transit - Out
• traveler_information_restrictions_for_travelers - Out
• tro-incident_information - Out