Emergency Management (Subsystem*)

The Emergency Management (EM) Subsystem represents public safety, emergency management, and other allied agency systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. The subsystem includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This subsystem also represents other allied systems including centers associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers.

The subsystem manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). The subsystem provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system.

This subsystem monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It interfaces with other Emergency Management Subsystems to support coordinated emergency response involving multiple agencies. The subsystem stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. As the response progresses, situation information including damage assessments, response status, evacuation information, and resource information are shared to keep all allied agencies appraised of the response. Interface with the Transit Management Subsystem allows coordinated use of transit vehicles to facilitate response to major emergencies and to support evacuation efforts. The Emergency Management Subsystem also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted.

The subsystem tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other center subsystems to aide in selecting the emergency vehicle(s) and routes that will provide the most timely response. Interface with the Traffic Management Subsystem allows strategic coordination in tailoring traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.

Functionality
Inputs/Outputs
Security
Subsystem Interfaces Diagram
Terminator Interfaces Diagram

Subsystem Interfaces Diagram

This is a context diagram for the entity Emergency Management Subsystem that shows the interfaces to subsystems and every architecture flow that this entity sends or receives, as defined in the National ITS Architecture. A complete list of all architecture flows shown on this diagram, is available under the Inputs/Outputs section on this page.

Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.

Terminator Interfaces Diagram

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Security Considerations:

The Emergency Management Subsystem provides critical functions that directly impact public safety. It handles sensitive information, must "operate through" and be available in distressed environments, and is subject to numerous threats including both physical and cyber attacks. The Emergency Management Subsystem represents an extremely broad group of call-taking, dispatch, command post, and operations centers. In addition to these public safety and emergency management centers, the Emergency Management Subsystem also represents private sector telematics service providers, service patrol dispatch systems, and security monitoring systems. Each of these systems has unique security vulnerabilities that must be considered in defining appropriate security services. Systems represented by the Emergency Management Subsystem operate in environments ranging from tightly controlled, secure command centers through open field environments when command posts are established in the vicinity of a major incident or disaster. The command post environment, with its reliance on wireless communications and relative lack of physical and environmental protection, has different vulnerabilities than systems operating in a fixed center. The availability requirements for an individual center must be assessed in the context of the concept of operations for the region. For example, the availability requirements for a service patrol dispatch system may not be high because the dispatch operation may be moved to an emergency operations center in times of crisis. The emergency operations center would have much more stringent availability requirements in this scenario. Similarly, the sensitivity and value of the information handled by each specific system must be evaluated to determine appropriate security safeguards for integrity and confidentiality. While it is good practice for all systems, a rigorous evaluation of security objectives, threats, vulnerabilities, and countermeasures is particularly important for each system represented by the Emergency Management Subsystem.

Functionality: Equipment Packages* and PSpecs*

Center Secure Area Alarm Support (Equipment Package*)
PSpecs:
- 5.1.1.4.6-Provide Operator Interface for Security
- 5.1.7.4-Manage Alarms
Center Secure Area Sensor Management (Equipment Package*)
PSpecs:
- 5.1.1.4.1-Manage Secure Area Sensors
- 5.1.1.4.3-Analyze Threats
- 5.1.1.4.4-Disseminate Threat Info
- 5.1.1.4.6-Provide Operator Interface for Security
- 5.1.4-Manage Emergency Response
- 5.2-Provide Operator Interface for Emergency Data
Center Secure Area Surveillance (Equipment Package*)
PSpecs:
- 5.1.1.4.2-Manage Secure Area Surveillance
- 5.1.1.4.5-Analyze Traveler Image
- 5.1.1.4.6-Provide Operator Interface for Security
- 5.1.2-Determine Coordinated Response Plan
- 5.2-Provide Operator Interface for Emergency Data
Emergency Call-Taking (Equipment Package*)
PSpecs:
- 5.1.1.1-Coordinate Emergency Inputs
- 5.1.1.3-Collect Incident And Event Data
- 5.1.2-Determine Coordinated Response Plan
- 5.1.3-Communicate Emergency Status
- 5.1.4-Manage Emergency Response
- 5.2-Provide Operator Interface for Emergency Data
- 5.5-Update Emergency Display Map Data
Emergency Commercial Vehicle Response (Equipment Package*)
PSpecs:
- 5.1.1.1-Coordinate Emergency Inputs
- 5.1.1.2-Identify Commercial Vehicle Emergencies
- 5.1.2-Determine Coordinated Response Plan
- 5.1.4-Manage Emergency Response
- 5.2-Provide Operator Interface for Emergency Data
Emergency Data Collection (Equipment Package*)
PSpecs:
- 5.6-Manage Emergency Services Data
Emergency Dispatch (Equipment Package*)
PSpecs:
- 5.1.2-Determine Coordinated Response Plan
- 5.1.4-Manage Emergency Response
- 5.2-Provide Operator Interface for Emergency Data
- 5.3.2-Dispatch Vehicle
- 5.3.6-Maintain Vehicle Status
- 5.5-Update Emergency Display Map Data
Emergency Early Warning System (Equipment Package*)
PSpecs:
- 5.1.1.3-Collect Incident And Event Data
- 5.1.2-Determine Coordinated Response Plan
- 5.1.3-Communicate Emergency Status
- 5.1.8-Manage Wide Area Alerts and Advisories
Emergency Environmental Monitoring (Equipment Package*)
PSpecs:
- 5.1.4-Manage Emergency Response
Emergency Evacuation Support (Equipment Package*)
PSpecs:
- 5.1.3-Communicate Emergency Status
- 5.1.4-Manage Emergency Response
- 5.2-Provide Operator Interface for Emergency Data
- 5.7.4-Provide Evacuation Coordination
- 5.7.5-Manage Evacuation
Emergency Response Management (Equipment Package*)
PSpecs:
- 5.1.1.3-Collect Incident And Event Data
- 5.1.2-Determine Coordinated Response Plan
- 5.1.3-Communicate Emergency Status
- 5.1.4-Manage Emergency Response
- 5.1.5-Manage Emergency Service Allocation Store
- 5.2-Provide Operator Interface for Emergency Data
- 5.3.1-Select Response Mode
- 5.5-Update Emergency Display Map Data
- 5.7.1-Assess System Status For Disasters
- 5.7.2-Provide Disaster Response Coordination
- 5.7.3-Assess System Status For Evacuation
Emergency Routing (Equipment Package*)
PSpecs:
- 5.2-Provide Operator Interface for Emergency Data
- 5.3.6-Maintain Vehicle Status
- 5.3.7-Provide Emergency Vehicle Route
Emergency Transportation Operations Data Collection (Equipment Package*)
PSpecs:
- 5.1.4-Manage Emergency Response
- 5.2-Provide Operator Interface for Emergency Data
- 5.3.7-Provide Emergency Vehicle Route
- 5.7.1-Assess System Status For Disasters
- 5.7.3-Assess System Status For Evacuation
Incident Command (Equipment Package*)
PSpecs:
- 5.1.1.3-Collect Incident And Event Data
- 5.1.3-Communicate Emergency Status
- 5.1.4-Manage Emergency Response
- 5.3.4-Assess Response Status
Mayday Support (Equipment Package*)
PSpecs:
- 5.1.2-Determine Coordinated Response Plan
- 5.1.3-Communicate Emergency Status
- 5.1.6-Process Mayday Messages
- 5.2-Provide Operator Interface for Emergency Data
Service Patrol Management (Equipment Package*)
PSpecs:
- 5.1.3-Communicate Emergency Status
- 5.2-Provide Operator Interface for Emergency Data
- 5.3.2-Dispatch Vehicle
- 5.3.4-Assess Response Status
- 5.3.6-Maintain Vehicle Status

Inputs/Outputs: Architecture Flows* and Data Flows*

Alerting and Advisory Systems Emergency Management

alerts and advisories (Architecture Flow*) - Assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), and alerts (information on imminent or in-progress emergencies). This flow also provides supporting descriptive detail on incidents, threats, and vulnerabilities to increase preparedness and support effective response to threats against the surface transportation system.
Data Flows*:
- faas-alerts_and_advisories_for_threat_analysis
- faas-wide_area_alert_notifications_and_advisories
threat support data (Architecture Flow*) - Information provided to help receiving agency identify possible threats, including biometric image processing support data.
Data Flows*:

Archived Data Management Emergency Management

archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*:
- em_archive_request
archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
- em_archive_status

Border Inspection Systems Emergency Management

border incident information (Architecture Flow*) - Notification of existence of incident in the vicinity of the border. Information would include expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided.
Data Flows*:
- fbis-border_incident_information

Care Facility Emergency Management

care facility status (Architecture Flow*) - Information regarding facility type and capabilities, facility status, and its ability to admit new patients.
Data Flows*:
- fcf-care_facility_status_response
- fcf-care_facility_status_response_for_disaster

Commercial Vehicle Emergency Management

hazmat spill notification (Architecture Flow*) - Information provided to emergency response organizations when cargo sensors detect a release of hazardous material. This information will include sensor information, vehicle location and identification, and carrier identification.
Data Flows*:
- cvo_hazmat_spill_data

Commercial Vehicle Check Emergency Management

alarm (Architecture Flow*) - Information about a Commercial Vehicle or Freight Equipment breach, non-permitted security sensitive hazmat detected at the roadside, route deviation, or Commercial Vehicle Driver / Commercial Vehicle / Freight Equipment assignment mismatches which includes the location of the Commercial Vehicle and appropriate identities.
Data Flows*:
- cv_hazmat_alarm

Emergency Management Alerting and Advisory Systems

threat data for analysis (Architecture Flow*) - Data from surveillance or sensor equipment in secure areas provided for further analysis.
Data Flows*:
threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
Data Flows*:
- taas-threat_info

Emergency Management Archived Data Management

emergency archive data (Architecture Flow*) - Logged emergency information including information that characterizes identified incidents (routine highway incidents through disasters), corresponding incident response information, evacuation information, surveillance data, threat data, and resource information. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
- em_archive_data

Emergency Management Border Inspection Systems

border incident response status (Architecture Flow*) - Status of the current incident response at a border crossing, including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
Data Flows*:
- tbis-border_incident_information

Emergency Management Care Facility

care facility status request (Architecture Flow*) - Request for information regarding care facility availability and status.
Data Flows*:

Emergency Management Emergency Personnel

incident command information presentation (Architecture Flow*) - Presentation of information to emergency personnel in the field that supports local tactical decision-making within an incident command system structure.
Data Flows*:
- tep-incident_command_information_presentation

Emergency Management Emergency System Operator

emergency operations status (Architecture Flow*) - Presentation of information to the operator including emergency operations data, supporting a range of emergency operating positions including call taker, dispatch, emergency operations, security monitoring, and various other operations and communications center operator positions.
Data Flows*:

Emergency Management Emergency Telecommunications System

incident information for public (Architecture Flow*) - Report of current desensitized incident information prepared for public dissemination through the telecommunications system.
Data Flows*:
- tets-incident_information_dissemination
incident notification response (Architecture Flow*) - Interactive acknowledgement and verification of the incident information received, requests for additional information, and general information on incident response status.
Data Flows*:
- tets-incident_acknowledge

Emergency Management Emergency Vehicle

decision support information (Architecture Flow*) - Information provided to support effective and safe incident response, including local traffic, road, and weather conditions, hazardous material information, and the current status of resources that have been allocated to an incident.
Data Flows*:
- local_decision_support
emergency dispatch requests (Architecture Flow*) - Emergency vehicle dispatch instructions including incident location and available information concerning the incident.
Data Flows*:
- emergency_vehicle_dispatch_request
suggested route (Architecture Flow*) - Suggested route for a dispatched emergency or maintenance vehicle that may reflect current network conditions and the additional routing options available to en route emergency or maintenance vehicles that are not available to the general public.
Data Flows*:
- emergency_vehicle_suggested_route

Emergency Management Event Promoters

event confirmation (Architecture Flow*) - Confirmation that special event details have been received and processed.
Data Flows*:
- tevp-planned_event_confirmation

Emergency Management Fleet and Freight Management

disable commercial vehicle (Architecture Flow*) - A request that a specific commercial vehicle should be safely disabled.
Data Flows*:
- disable_commercial_vehicle
hazmat information request (Architecture Flow*) - Request for information about a particular hazmat load.
Data Flows*:
- cf_hazmat_request

Emergency Management Information Service Provider

alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies 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 flow may also identify specific information that should not be released to the public.
Data Flows*:
evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*:
- evacuation_data_for_isp
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
- incident_information
transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
- disaster_transportation_system_status_for_isp
- evacuation_transportation_system_status_for_isp

Emergency Management Maintenance and Construction Management

alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies 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 flow may also identify specific information that should not be released to the public.
Data Flows*:
- wide_area_alert_notification_for_maint
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- disaster_response_plan_coordination_to_m_and_c
- evacuation_plan_coordination_to_m_and_c
evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*:
- evacuation_information_for_m_and_c
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
- incident_info_from_emerg
incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
Data Flows*:
- incident_response_status_from_emerg
maint and constr resource request (Architecture Flow*) - Request for road maintenance and construction resources that can be used in the diversion of traffic (cones, portable signs), clearance of a road hazard, repair of ancillary damage, or any other incident response. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of resources.
Data Flows*:
security field equipment status (Architecture Flow*) - Identification of security sensors and surveillance equipment requiring repair and known information about the associated faults.
Data Flows*:
- security_sensor_equip_status_for_m_and_c
- security_surveillance_equip_status_for_m_and_c
threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
Data Flows*:
- threat_info_for_maint
transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
work plan feedback (Architecture Flow*) - Comments and suggested changes to proposed construction and maintenance work schedules and activities. This information influences work plan schedules so that they minimize impact to other system operations and the overall transportation system.
Data Flows*:
- m_and_c_plan_feedback_from_emerg

Emergency Management Map Update Provider

map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
Data Flows*:
- tmup-emergency_route_map_request
- tmup-request_emergency_display_update

Emergency Management Media

incident information for media (Architecture Flow*) - Report of current desensitized incident information prepared for public dissemination through the media.
Data Flows*:
- tm-emergency_information

Emergency Management Other Emergency Management

alert notification coordination (Architecture Flow*) - Coordination of emergency alerts to be distributed to the public. This includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public and status of the public notification.
Data Flows*:
- toem-alert_notification_status
- toem-wide_area_alert_notification
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- toem-disaster_response_plan_coordination
- toem-evacuation_plan_coordination
evacuation coordination (Architecture Flow*) - Coordination of information regarding a pending or in-process evacuation. Includes evacuation zones, evacuation times, evacuation routes, forecast network conditions, and reentry times.
Data Flows*:
- toem-evacuation_information_for_other_em
- toem-evacuation_status
incident command information coordination (Architecture Flow*) - Information that supports local management of an incident. It includes resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response.
Data Flows*:
- toem-incident_command_information_coordination
incident report (Architecture Flow*) - Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate incident response.
Data Flows*:
- toem-incident_details
- toem-mayday_emergency_data
incident response coordination (Architecture Flow*) - Incident response procedures and current incident response status that are shared between allied response agencies to support a coordinated response to incidents. This flow provides current situation information, including a summary of incident status and its impact on the transportation system and other infrastructure, and current and planned response activities. This flow also coordinates a positive hand off of responsibility for all or part of an incident response between agencies.
Data Flows*:
resource coordination (Architecture Flow*) - Coordination of resource inventory information, specific resource status information, resource prioritization and reallocation between jurisdictions, and specific requests for resources and responses that service those requests.
Data Flows*:
threat information coordination (Architecture Flow*) - Sensor, surveillance, and threat data including raw and processed data that is collected by sensor and surveillance equipment located in secure areas.
Data Flows*:
transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
- toem-transportation_system_status_for_disaster
- toem-transportation_system_status_for_evacuation

Emergency Management Payment Administration

alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies 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 flow may also identify specific information that should not be released to the public.
Data Flows*:
- wide_area_alert_notification_for_tolls
toll service change request (Architecture Flow*) - Request to change pricing, modify restrictions, or modify operations of a toll road facility
Data Flows*:
- evacuation_toll_change_request

Emergency Management Personal Information Access

emergency acknowledge (Architecture Flow*) - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
Data Flows*:
- emergency_request_personal_traveler_acknowledge

Emergency Management Public Health System

public health request (Architecture Flow*) - Request for specific information or recommended response concerning an emergency involving biological or other medically related emergency.
Data Flows*:
- tphs-public_health_evacuation_request
- tphs-public_health_request

Emergency Management Rail Operations

emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- tro-disaster_response_plan_coordination
- tro-evacuation_plan_coordination
evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*:
- tro-evacuation_information_for_rail
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
- tro-incident_information
incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
Data Flows*:
- tro-incident_response_status
threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
Data Flows*:
- tro-threat_info
transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
- tro-transportation_system_status_for_disaster
- tro-transportation_system_status_for_evacuation

Emergency Management Remote Traveler Support

alarm acknowledge (Architecture Flow*) - Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information.
Data Flows*:
- secure_area_traveler_alarm_response
- traveler_alarm_acknowledge
secure area sensor control (Architecture Flow*) - Information used to configure and control threat sensors (e.g., thermal, acoustic, radiological, chemical), object, motion and intrusion detection sensors. The provided information controls sensor data collection, aggregation, filtering, and other local processing.
Data Flows*:
secure area surveillance control (Architecture Flow*) - Information used to configure and control audio and video surveillance systems used for transportation infrastructure security in secure areas. The provided information controls surveillance data collection, aggregation, filtering, and other local processing.
Data Flows*:
- traveler_secure_area_surveillance_control
- traveler_surveillance_field_proc_parameters

Emergency Management Security Monitoring

infrastructure monitoring sensor control (Architecture Flow*) - Data used to configure and control infrastructure monitoring sensors.
Data Flows*:
- infrastructure_integrity_sensor_control
secure area sensor control (Architecture Flow*) - Information used to configure and control threat sensors (e.g., thermal, acoustic, radiological, chemical), object, motion and intrusion detection sensors. The provided information controls sensor data collection, aggregation, filtering, and other local processing.
Data Flows*:
secure area surveillance control (Architecture Flow*) - Information used to configure and control audio and video surveillance systems used for transportation infrastructure security in secure areas. The provided information controls surveillance data collection, aggregation, filtering, and other local processing.
Data Flows*:
- secure_area_surveillance_control
- secure_area_surveillance_field_proc_parameters

Emergency Management Shelter Providers

evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*:
- tsp-shelter_evacuation_information
- tsp-shelter_information_request

Emergency Management Surface Transportation Weather Service

transportation weather information request (Architecture Flow*) - A request for transportation weather information that may specify the area of interest (a geographic region, particular routes within a region, specific road segments), the type of information that is required, the desired spatial resolution of the information, and time horizon.
Data Flows*:
- tstws-trans_weather_info_request

Emergency Management Traffic Management

alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies 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 flow may also identify specific information that should not be released to the public.
Data Flows*:
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- disaster_response_plan_coordination_to_traffic
- evacuation_plan_coordination_to_traffic
emergency route request (Architecture Flow*) - Request for access routes for emergency response vehicles and equipment. This may be a request for ingress or egress routes or other emergency routes.
Data Flows*:
- emergency_route_request
emergency traffic control request (Architecture Flow*) - Special request to preempt the current traffic control strategy in effect at one or more signalized intersections or highway segments, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems. For example, this flow can request all signals to red-flash, request a progression of traffic control preemptions along an emergency vehicle route, request a specific evacuation traffic control plan, request activation of a road closure barrier system, or place a public safety or emergency-related message on a dynamic message sign.
Data Flows*:
evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*:
- evacuation_information_for_traffic_management
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
- incident_details
incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
Data Flows*:
- incident_response_status
remote surveillance control (Architecture Flow*) - The control commands used to remotely operate another center's sensors or surveillance equipment so that roadside surveillance assets can be shared by more than one agency.
Data Flows*:
- remote_video_image_control
resource deployment status (Architecture Flow*) - Status of resource deployment identifying the resources (vehicles, equipment, materials, and personnel) available and their current status. General resource inventory information and specific status of deployed resources may be included.
Data Flows*:
- em_resource_response_to_traffic
resource request (Architecture Flow*) - A request for resources to implement special traffic control measures, assist in clean up, verify an incident, etc. The request may poll for resource availability or request pre-staging, staging, or immediate deployment of resources. Resources may be explicitly requested or a service may be requested and the specific resource deployment may be determined by the responding agency.
Data Flows*:
- resource_request
- traffic_evacuation_resource_request
road closure notification (Architecture Flow*) - Notification that agency personnel have closed a road due to adverse weather, major incident, or other reason.
Data Flows*:
- roadway_closure_from_emergency
threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
Data Flows*:
- threat_info_for_traffic
transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:

Emergency Management Transit Management

alert notification (Architecture Flow*) - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies 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 flow may also identify specific information that should not be released to the public.
Data Flows*:
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- disaster_response_plan_coordination_to_transit
- evacuation_plan_coordination_to_transit
emergency transit service request (Architecture Flow*) - Request to modify transit service and fare schedules to address emergencies, including requests for transit services to evacuate people from and/or deploy response agency personnel to an emergency scene. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of transit resources.
Data Flows*:
- request_for_emergency_transit_support
- transit_evacuation_resource_request
evacuation information (Architecture Flow*) - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
Data Flows*:
- evacuation_information_for_transit_management
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
- emergency_data_for_transit
incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
Data Flows*:
- incident_response_status_to_transit
- transit_incident_coordination_data
threat information (Architecture Flow*) - Threats regarding transportation infrastructure, facilities, or systems detected by a variety of methods (sensors, surveillance, threat analysis of advisories from outside agencies, etc.
Data Flows*:
- threat_info_for_transit
transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:

Emergency Management Transit Vehicle

alarm acknowledge (Architecture Flow*) - Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information.
Data Flows*:
- on_board_traveler_alarm_response
- secure_transit_vehicle_alarm_acknowledge
secure area sensor control (Architecture Flow*) - Information used to configure and control threat sensors (e.g., thermal, acoustic, radiological, chemical), object, motion and intrusion detection sensors. The provided information controls sensor data collection, aggregation, filtering, and other local processing.
Data Flows*:
secure area surveillance control (Architecture Flow*) - Information used to configure and control audio and video surveillance systems used for transportation infrastructure security in secure areas. The provided information controls surveillance data collection, aggregation, filtering, and other local processing.
Data Flows*:
- vehicle_secure_area_surveillance_control
- vehicle_secure_area_surveillance_field_proc_parameters

Emergency Management Vehicle

emergency acknowledge (Architecture Flow*) - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
Data Flows*:
- emergency_request_driver_acknowledge
- emergency_request_vehicle_acknowledge
emergency data request (Architecture Flow*) - A request for additional information or a control command issued by the emergency response agency in response to an emergency request for assistance from a traveler.
Data Flows*:
- emergency_data_request
- vehicle_security_system_commands

Emergency Personnel Emergency Management

incident command inputs (Architecture Flow*) - User input from emergency personnel including incident command status, incident information and resource coordination.
Data Flows*:
- fep-incident_command_inputs

Emergency System Operator Emergency Management

emergency operations inputs (Architecture Flow*) - Emergency operator inputs supporting call taking, dispatch, emergency operations, security monitoring, and other operations and communications center operator functions.
Data Flows*:

Emergency Telecommunications System Emergency Management

incident notification (Architecture Flow*) - The notification of an incident including its nature, severity, and location.
Data Flows*:
- fets-caller_information
- fets-incident_information

Emergency Vehicle Emergency Management

emergency dispatch response (Architecture Flow*) - Request for additional emergency dispatch information and provision of en route status.
Data Flows*:
- emergency_vehicle_dispatch_response
emergency vehicle tracking data (Architecture Flow*) - The current location and operating status of the emergency vehicle.
Data Flows*:
- emergency_vehicle_tracking_data
incident status (Architecture Flow*) - Information gathered at the incident site that more completely characterizes the incident and provides current incident response status.
Data Flows*:
- incident_status_update

Event Promoters Emergency Management

event plans (Architecture Flow*) - Plans for major events possibly impacting traffic.
Data Flows*:
- fevp-planned_event_data

Fleet and Freight Management Emergency Management

alarm (Architecture Flow*) - Information about a Commercial Vehicle or Freight Equipment breach, non-permitted security sensitive hazmat detected at the roadside, route deviation, or Commercial Vehicle Driver / Commercial Vehicle / Freight Equipment assignment mismatches which includes the location of the Commercial Vehicle and appropriate identities.
Data Flows*:
- cvo_alarm
- freight_alarm
hazmat information (Architecture Flow*) - Information about a particular hazmat load including nature of the load and unloading instructions. May also include hazmat vehicle route and route update information.
Data Flows*:
- cf_hazmat_route_information
- cf_hazmat_vehicle_information

Information Service Provider Emergency Management

alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*:
- alert_notification_status_from_travelers
transportation information for operations (Architecture Flow*) - Information on the state of transportation system operations including traffic and road conditions, advisories, incidents, transit service information, weather information, parking information, and other related data.
Data Flows*:

Maintenance and Construction Management Emergency Management

alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*:
- alert_notification_status_from_maint
current asset restrictions (Architecture Flow*) - Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction.
Data Flows*:
- asset_restrictions_for_em_response
- asset_restrictions_for_emerg
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- disaster_response_plan_coordination_from_m_and_c
- evacuation_plan_coordination_from_m_and_c
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
- incident_info_for_emerg
maint and constr resource response (Architecture Flow*) - Current status of maintenance and construction resources including availability and deployment status. General resource inventory information covering vehicles, equipment, materials, and people and specific resource deployment status may be included.
Data Flows*:
- m_and_c_evacuation_resource_response
- m_and_c_resource_response_to_emerg
maint and constr work plans (Architecture Flow*) - Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations.
Data Flows*:
- m_and_c_work_plans_for_emerg
road network status assessment (Architecture Flow*) - 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.
Data Flows*:
- m_and_c_status_assessment_for_disaster
- m_and_c_status_assessment_for_evacuation
road weather information (Architecture Flow*) - Road conditions and weather information that are made available by road maintenance operations to other transportation system operators.
Data Flows*:
- road_weather_info_for_emergency
roadway maintenance status (Architecture Flow*) - Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status).
Data Flows*:
- roadway_maint_status_for_emerg
security equipment maintenance status (Architecture Flow*) - Current status of security surveillance and sensor field equipment maintenance actions.
Data Flows*:
- security_sensor_equip_maint_status
- security_surveillance_equip_maint_status
work zone information (Architecture Flow*) - Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts.
Data Flows*:
- work_zone_info_for_emergency

Map Update Provider Emergency Management

map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:
- fmup-emergency_display_update
- fmup-emergency_route_map_update

Other Emergency Management Emergency Management

alert notification coordination (Architecture Flow*) - Coordination of emergency alerts to be distributed to the public. This includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public and status of the public notification.
Data Flows*:
- foem-alert_notification_status
- foem-wide_area_alert_notification
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- foem-disaster_response_plan_coordination
- foem-evacuation_plan_coordination
evacuation coordination (Architecture Flow*) - Coordination of information regarding a pending or in-process evacuation. Includes evacuation zones, evacuation times, evacuation routes, forecast network conditions, and reentry times.
Data Flows*:
- foem-evacuation_information_from_other_em
- foem-evacuation_status
incident command information coordination (Architecture Flow*) - Information that supports local management of an incident. It includes resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response.
Data Flows*:
- foem-incident_command_information_coordination
incident report (Architecture Flow*) - Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate incident response.
Data Flows*:
- foem-incident_details
- foem-mayday_emergency_data
incident response coordination (Architecture Flow*) - Incident response procedures and current incident response status that are shared between allied response agencies to support a coordinated response to incidents. This flow provides current situation information, including a summary of incident status and its impact on the transportation system and other infrastructure, and current and planned response activities. This flow also coordinates a positive hand off of responsibility for all or part of an incident response between agencies.
Data Flows*:
resource coordination (Architecture Flow*) - Coordination of resource inventory information, specific resource status information, resource prioritization and reallocation between jurisdictions, and specific requests for resources and responses that service those requests.
Data Flows*:
threat information coordination (Architecture Flow*) - Sensor, surveillance, and threat data including raw and processed data that is collected by sensor and surveillance equipment located in secure areas.
Data Flows*:
transportation system status (Architecture Flow*) - Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
- foem-transportation_system_status_for_disaster
- foem-transportation_system_status_for_evacuation

Payment Administration Emergency Management

alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*:
- alert_notification_status_from_tolls
toll service change response (Architecture Flow*) - Response to toll service change requests indicating level of compliance with request.
Data Flows*:
- evacuation_toll_change_response

Personal Information Access Emergency Management

emergency notification (Architecture Flow*) - An emergency request for assistance automatically initiated by a vehicle or originated by a traveler using an in-vehicle or personal device.
Data Flows*:
- emergency_request_personal_traveler_details

Public Health System Emergency Management

public health response (Architecture Flow*) - Specific information or recommendation on how to treat or respond to an emergency involving biological or other medically related emergency.
Data Flows*:
- fphs-public_health_evacuation
- fphs-public_health_response

Rail Operations Emergency Management

emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- fro-disaster_response_plan_coordination
- fro-evacuation_plan_coordination
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
- fro-rail_incident_information
rail incident response status (Architecture Flow*) - Status of the rail system’s response to current incidents.
Data Flows*:
- fro-rail_incident_response_status
rail system status assessment (Architecture Flow*) - Assessment of damage sustained by rail lines and associated railroad infrastructure including location and extent of the damage, impact on current operations and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
- fro-rail_system_status_for_disaster
- fro-rail_system_status_for_evacuation
railroad schedules (Architecture Flow*) - Train schedules, maintenance schedules, and other information from the railroad that supports forecast of HRI closures.
Data Flows*:
- fro-railroad_schedules_for_emergency

Remote Traveler Support Emergency Management

alarm notification (Architecture Flow*) - Notification of activation of an audible or silent alarm by a traveler in a public area or by a transit vehicle operator using an on-board device.
Data Flows*:
- traveler_alarm_request
secure area sensor data (Architecture Flow*) - Data provided by threat sensors (e.g., thermal, acoustic, radiological, chemical), and intrusion, motion, and object detection sensors in secure areas indicating the sensor's operational status, raw and processed sensor data, and alarm indicators when a threat has been detected.
Data Flows*:
secure area surveillance data (Architecture Flow*) - Data collected from surveillance systems used to monitor secure areas. Includes video, audio, processed surveillance data, equipment operational status, and alarm indicators when a threat has been detected.
Data Flows*:

Security Monitoring Emergency Management

infrastructure monitoring sensor data (Architecture Flow*) - Data read from infrastructure-based sensors that monitor the condition or integrity of transportation infrastructure including bridges, tunnels, interchanges, pavement, culverts, signs, transit rail or guideway, and other roadway infrastructure. Includes sensor data and the operational status of the sensors.
Data Flows*:
- field_processed_infrastructure_integrity_sensor_data
- infrastructure_integrity_sensor_status
secure area sensor data (Architecture Flow*) - Data provided by threat sensors (e.g., thermal, acoustic, radiological, chemical), and intrusion, motion, and object detection sensors in secure areas indicating the sensor's operational status, raw and processed sensor data, and alarm indicators when a threat has been detected.
Data Flows*:
secure area surveillance data (Architecture Flow*) - Data collected from surveillance systems used to monitor secure areas. Includes video, audio, processed surveillance data, equipment operational status, and alarm indicators when a threat has been detected.
Data Flows*:

Shelter Providers Emergency Management

shelter information (Architecture Flow*) - Evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
Data Flows*:
- fsp-shelter_information

Surface Transportation Weather Service Emergency Management

transportation weather information (Architecture Flow*) - Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making.
Data Flows*:
- fstws-surface_trans_weather_forecasts
- fstws-surface_trans_weather_observations

Traffic Management Emergency Management

alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*:
- alert_notification_status_from_traffic
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- disaster_response_plan_coordination_from_traffic
- evacuation_plan_coordination_from_traffic
emergency routes (Architecture Flow*) - Suggested ingress and egress routes for access to and between the scene and staging areas or other specialized emergency access routes.
Data Flows*:
- emergency_route_response
emergency traffic control information (Architecture Flow*) - Status of a special traffic control strategy or system activation implemented in response to an emergency traffic control request, a request for emergency access routes, a request for evacuation, a request to activate closure systems, a request to employ driver information systems to support public safety objectives, or other special requests. Identifies the selected traffic control strategy and system control status.
Data Flows*:
incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*:
incident response status (Architecture Flow*) - Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
Data Flows*:
- current_traffic_incident_response
resource deployment status (Architecture Flow*) - Status of resource deployment identifying the resources (vehicles, equipment, materials, and personnel) available and their current status. General resource inventory information and specific status of deployed resources may be included.
Data Flows*:
- resource_deployment_status
resource request (Architecture Flow*) - A request for resources to implement special traffic control measures, assist in clean up, verify an incident, etc. The request may poll for resource availability or request pre-staging, staging, or immediate deployment of resources. Resources may be explicitly requested or a service may be requested and the specific resource deployment may be determined by the responding agency.
Data Flows*:
- em_resource_request_from_traffic
road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*:
road network status assessment (Architecture Flow*) - 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.
Data Flows*:
- network_status_from_traffic_for_disaster
- network_status_from_traffic_for_evacuation
traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
Data Flows*:
- incident_video_for_emergency_services

Transit Management Emergency Management

alert status (Architecture Flow*) - Information indicating the current status of the emergency alert including identification of the traveler and driver information systems that are being used to provide the alert.
Data Flows*:
- alert_notification_status_from_transit
emergency plan coordination (Architecture Flow*) - Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
Data Flows*:
- disaster_response_plan_coordination_from_transit
- evacuation_plan_coordination_from_transit
emergency transit schedule information (Architecture Flow*) - Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
Data Flows*:
- transit_schedule_information_during_emergencies
- transit_schedule_information_during_evacuation
emergency transit service response (Architecture Flow*) - Response indicating changes to transit service, fares, and/or restrictions that will be made and status of transit resources to be deployed to support emergency response and/or evacuation.
Data Flows*:
- response_for_emergency_transit_support
- transit_evacuation_status
transit emergency data (Architecture Flow*) - Initial notification of transit emergency at a transit stop or on transit vehicles and further coordination as additional details become available and the response is coordinated.
Data Flows*:
transit system status assessment (Architecture Flow*) - Assessment of damage sustained by the public transportation system including location and extent of the damage, current operational status including an estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Data Flows*:
- transit_system_status

Transit Vehicle Emergency Management

alarm notification (Architecture Flow*) - Notification of activation of an audible or silent alarm by a traveler in a public area or by a transit vehicle operator using an on-board device.
Data Flows*:
- secure_transit_vehicle_alarm_request
- transit_vehicle_location_for_alarms
secure area sensor data (Architecture Flow*) - Data provided by threat sensors (e.g., thermal, acoustic, radiological, chemical), and intrusion, motion, and object detection sensors in secure areas indicating the sensor's operational status, raw and processed sensor data, and alarm indicators when a threat has been detected.
Data Flows*:
secure area surveillance data (Architecture Flow*) - Data collected from surveillance systems used to monitor secure areas. Includes video, audio, processed surveillance data, equipment operational status, and alarm indicators when a threat has been detected.
Data Flows*:
transit vehicle location data (Architecture Flow*) - Current transit vehicle location and related operational conditions data provided by a transit vehicle.
Data Flows*:
- transit_vehicle_location_for_surveillance_and_security

Vehicle Emergency Management

emergency notification (Architecture Flow*) - An emergency request for assistance automatically initiated by a vehicle or originated by a traveler using an in-vehicle or personal device.
Data Flows*:

Weather Service Emergency Management

weather information (Architecture Flow*) - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
Data Flows*:
- fws-current_weather_observations
- fws-weather_forecasts