Emergency Management

The Emergency Management Subsystem operates in various emergency centres supporting public safety including police, fire and emergency medical service stations, search and rescue special detachments, HAZMAT response teams, and service patrols. The subsystem includes the functions associated with fixed and mobile public safety communications centres at local, regional, state, and federal levels. This subsystem monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. The subsystem creates, stores, coordinates, and utilizes emergency response and evacuation plans to facilitate coordinated response with other Emergency Management Subsystems. Interface with the Transit Management Subsystem allows coordinated use of transit vehicles to facilitate response to major emergencies and to support evacuation efforts. Interface with the Traffic Management Subsystem provides real-time input for emergency vehicle response selection and routing and allows for 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.

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 centres. In addition to these public safety and emergency management centres, 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 centres 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 centre. The availability requirements for an individual centre 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 centre in times of crisis. The emergency operations centre 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

• Centre Secure Area Alarm Support
  
  • 5.1.1.4.6 - Provide Operator Interface for Security
  • 5.1.7.4 - Manage Alarms
  
  
• Centre Secure Area Sensor Management
  
  • 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
  
  
• Centre Secure Area Surveillance
  
  • 5.1.1.4.2 - Manage Secure Area Surveillance
  • 5.1.1.4.5 - Analyze Traveller 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
  
  • 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
  
  • 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
  
  • 5.6 - Manage Emergency Services Data
  
  
• Emergency Dispatch
  
  • 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
  
  • 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
  
  • 5.1.4 - Manage Emergency Response
  
  
• Emergency Evacuation Support
  
  • 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
  
  • 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
  
  • 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
  
  • 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
  
  • 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
  
  • 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
  
  • 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 - 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 - Information provided to help receiving agency identify possible threats, including biometric image processing support data.
  Data Flows:
  • faas-threat_support_data
  • faas-image_search_data
  • faas-confirm_image_match
  
  

Archived Data Management Subsystem > Emergency Management

• archive requests - 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 - 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 - 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:
  • border_incident_information
  
  

Care Facility > Emergency Management

• care facility status - 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 Check > Emergency Management

• alarm - 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
  
  

Commercial Vehicle Subsystem > Emergency Management

• hazmat spill notification - 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
  
  

Emergency Management > Alerting and Advisory Systems

• threat data for analysis - Data from surveillance or sensor equipment in secure areas provided for further analysis.
  Data Flows:
  • taas-traveller_image
  • taas-threat_data_for_analysis
  • taas-traveller_image_matching_details
  
  
• threat information - 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 Subsystem

• emergency archive data - 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 - 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:
  • border_incident_response_status
  
  

Emergency Management > Care Facility

• care facility status request - Request for information regarding care facility availability and status.
  Data Flows:
  • tcf-care_facility_disaster_data
  • tcf-care_facility_status_request
  • tcf-care_facility_status_request_for_disaster
  
  

Emergency Management > Emergency Personnel

• incident command information presentation - 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 - 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 centre operator positions.
  Data Flows:
  • teso-wide_area_alert_status
  • teso-alerts_and_advisories
  • teso-archive_status
  • teso-emergency_action_log_output
  • teso-emergency_data_output
  • teso-emergency_request
  • teso-emergency_routing_information
  • teso-emergency_vehicle_dispatch_failure
  • teso-image_match
  • teso-secure_area_sensor_surveillance_information
  
  

Emergency Management > Emergency Telecommunications System

• incident information for public - Report of current desensitized incident information prepared for public dissemination through the telecommunications system.
  Data Flows:
  • tets-incident_information_dissemination
  
  
• incident notification response - 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 Subsystem

• decision support information - 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 - Emergency vehicle dispatch instructions including incident location and available information concerning the incident.
  Data Flows:
  • emergency_vehicle_dispatch_request
  
  
• suggested route - 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 - 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 - A request that a specific commercial vehicle should be safely disabled.
  Data Flows:
  • disable_commercial_vehicle
  
  
• HAZMAT information request - Request for information about a particular hazmat load.
  Data Flows:
  • cf_hazmat_request
  
  

Emergency Management > Information Service Provider

• alert notification - 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:
  • traveller_information_restrictions_for_travellers
  • wide_area_alert_notification_for_travellers
  • deactivate_traveller_information_restrictions_for_travellers
  
  
• evacuation information - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows:
  • evacuation_data_for_isp
  
  
• incident information - 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
  
  
• shelter information - Evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
  Data Flows:
  • shelter_information_for_isp
  
  
• transportation system status - 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 - 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 - 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 - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows:
  • evacuation_information_for_m_and_c
  
  
• incident information - 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 - 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 - 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:
  • roadway_maint_action_req_from_emerg
  • m_and_c_resource_request_from_emerg
  • m_and_c_evacuation_resource_request
  
  
• security field equipment status - Identification of security sensors and surveillance equipment requiring repair and known information about the associated faults.
  Data Flows:
  • security_surveillance_equip_status_for_m_and_c
  • security_sensor_equip_status_for_m_and_c
  
  
• threat information - 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 - 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:
  • infrastructure_integrity_status_for_maint
  • m_and_c_transportation_system_status_for_evacuation
  • m_and_c_transportation_system_status_for_disaster
  
  
• work plan feedback - 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 - 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 - Report of current desensitized incident information prepared for public dissemination through the media.
  Data Flows:
  • tm-emergency_information
  
  

Emergency Management > Meteorological Service Provider

• transportation weather information request - 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:
  • tmsp-trans_weather_info_request
  
  

Emergency Management > Other Emergency Management

• alert notification coordination - 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 - 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-evacuation_plan_coordination
  • toem-disaster_response_plan_coordination
  
  
• evacuation coordination - 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 - 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 - 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 - 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:
  • toem-response_for_emergency_support
  • toem-incident_response_coordination
  • toem-request_for_emergency_support
  
  
• resource coordination - 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:
  • toem-evacuation_resource_response
  • toem-emergency_resource_response
  • toem-evacuation_resource_request
  • toem-emergency_resource_request
  
  
• threat information coordination - Sensor, surveillance, and threat data including raw and processed data that is collected by sensor and surveillance equipment located in secure areas.
  Data Flows:
  • toem-threat_analysis_results
  • toem-secure_area_surveillance
  • toem-secure_area_sensor_data
  • toem-threat_info
  • toem-verified_image_match
  
  
• transportation system status - 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 > Personal Information Access

• emergency acknowledge - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
  Data Flows:
  • emergency_request_personal_traveller_acknowledge
  
  

Emergency Management > Public Health System

• public health request - 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 - 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 - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows:
  • tro-evacuation_information_for_rail
  
  
• incident information - 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 - 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 - 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 - 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_evacuation
  • tro-transportation_system_status_for_disaster
  
  

Emergency Management > Remote Traveller Support

• alarm acknowledge - Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information.
  Data Flows:
  • secure_area_traveller_alarm_response
  • traveller_alarm_acknowledge
  
  
• secure area sensor control - 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:
  • traveller_threat_sensor_control
  • traveller_intrusion_motion_sensor_control
  • traveller_sensor_field_proc_parameters
  • traveller_object_detection_sensor_control
  
  
• secure area surveillance control - 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:
  • traveller_secure_area_surveillance_control
  • traveller_surveillance_field_proc_parameters
  
  

Emergency Management > Security Monitoring Subsystem

• infrastructure monitoring sensor control - Data used to configure and control infrastructure monitoring sensors.
  Data Flows:
  • infrastructure_integrity_sensor_control
  
  
• secure area sensor control - 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:
  • object_detection_sensor_control
  • intrusion_motion_sensor_control
  • secure_area_sensor_field_proc_parameters
  • threat_sensor_control
  
  
• secure area surveillance control - 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 - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows:
  • tsp-shelter_evacuation_information
  • tsp-shelter_information_request
  
  

Emergency Management > Toll Administration

• alert notification - 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 - Request to change pricing, modify restrictions, or modify operations of a toll road facility
  Data Flows:
  • evacuation_toll_change_request
  
  

Emergency Management > Traffic Management

• alert notification - 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_traffic
  • traveller_information_restrictions_for_traffic
  • deactivate_traveller_information_restrictions_for_traffic
  
  
• emergency plan coordination - 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 - 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 - 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:
  • roadway_information_data_to_traffic
  • safeguard_system_activation_request_from_emerg
  • emergency_traffic_control_request
  • barrier_system_activation_request_from_emerg
  
  
• evacuation information - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows:
  • evacuation_information_for_traffic_management
  
  
• incident information - 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 - 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 - The control commands used to remotely operate another centre'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 - 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 - 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:
  • traffic_evacuation_resource_request
  • resource_request
  
  
• road closure notification - 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 - 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 - 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:
  • evacuation_transportation_system_status_for_traffic
  • infrastructure_integrity_status_for_traffic
  • disaster_transportation_system_status_for_traffic
  
  

Emergency Management > Transit Management

• alert notification - 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:
  • traveller_information_restrictions_for_transit
  • deactivate_traveller_information_restrictions_for_transit
  • wide_area_alert_notification_for_transit
  
  
• emergency plan coordination - 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:
  • evacuation_plan_coordination_to_transit
  • disaster_response_plan_coordination_to_transit
  
  
• emergency transit service request - 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:
  • transit_evacuation_resource_request
  • request_for_emergency_transit_support
  
  
• evacuation information - Evacuation instructions and information including evacuation zones, evacuation times, and reentry times.
  Data Flows:
  • evacuation_information_for_transit_management
  
  
• incident information - 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 - 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
  
  
• shelter information - Evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
  Data Flows:
  • shelter_information_for_transit
  
  
• threat information - 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 - 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_transit
  • infrastructure_integrity_status_for_transit
  • evacuation_transportation_system_status_for_transit
  
  

Emergency Management > Transit Vehicle Subsystem

• alarm acknowledge - Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information.
  Data Flows:
  • secure_transit_vehicle_alarm_acknowledge
  • on_board_traveller_alarm_response
  
  
• secure area sensor control - 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:
  • vehicle_threat_sensor_control
  • vehicle_secure_area_sensor_field_proc_parameters
  • vehicle_object_detection_sensor_control
  
  
• secure area surveillance control - 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_field_proc_parameters
  • vehicle_secure_area_surveillance_control
  
  

Emergency Management > Vehicle

• emergency acknowledge - Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements.
  Data Flows:
  • emergency_request_vehicle_acknowledge
  • emergency_request_driver_acknowledge
  
  
• emergency data request - 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 traveller.
  Data Flows:
  • vehicle_security_system_commands
  • emergency_data_request
  
  

Emergency Personnel > Emergency Management

• incident command inputs - 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 - Emergency operator inputs supporting call taking, dispatch, emergency operations, security monitoring, and other operations and communications centre operator functions.
  Data Flows:
  • feso-emergency_data_input
  • feso-alerts_and_advisories
  • feso-archive_commands
  • feso-emergency_action_log_request
  • feso-emergency_data_output_request
  • feso-emergency_allocation_override
  • feso-emergency_display_update_request
  • feso-emergency_response
  • feso-emergency_routing_input
  • feso-secure_area_sensor_surveillance_control
  • feso-image_processing_parameters
  
  

Emergency Telecommunications System > Emergency Management

• incident notification - The notification of an incident including its nature, severity, and location.
  Data Flows:
  • fets-incident_information
  • fets-caller_information
  
  

Emergency Vehicle Subsystem > Emergency Management

• emergency dispatch response - Request for additional emergency dispatch information and provision of en route status.
  Data Flows:
  • emergency_vehicle_dispatch_response
  
  
• emergency vehicle tracking data - The current location and operating status of the emergency vehicle.
  Data Flows:
  • emergency_vehicle_tracking_data
  
  
• incident status - 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 - Plans for major events possibly impacting traffic.
  Data Flows:
  • fevp-planned_event_data
  
  

Fleet and Freight Management > Emergency Management

• alarm - 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 - 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 - Information indicating the current status of the emergency alert including identification of the traveller and driver information systems that are being used to provide the alert.
  Data Flows:
  • alert_notification_status_from_travellers
  
  
• transportation information for operations - 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:
  • transportation_information_for_disaster_operations
  • transportation_information_for_evac_operations
  • transportation_information_for_emerg_routing
  • transportation_information_for_emerg_operations
  
  

Maintenance and Construction Management > Emergency Management

• alert status - Information indicating the current status of the emergency alert including identification of the traveller and driver information systems that are being used to provide the alert.
  Data Flows:
  • alert_notification_status_from_maint
  
  
• current asset restrictions - 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 - 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:
  • evacuation_plan_coordination_from_m_and_c
  • disaster_response_plan_coordination_from_m_and_c
  
  
• incident information - 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 - 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 - 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 - 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 - 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 - 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 - Current status of security surveillance and sensor field equipment maintenance actions.
  Data Flows:
  • security_surveillance_equip_maint_status
  • security_sensor_equip_maint_status
  
  
• work zone information - 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 - 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
  
  

Meteorological Service Provider > Emergency Management

• transportation weather information - 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:
  • fmsp-surface_trans_weather_forecasts
  • fmsp-surface_trans_weather_observations
  
  

National Meteorological Service > Emergency Management

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

Other Emergency Management > Emergency Management

• alert notification coordination - 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 - 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 - 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_status
  • foem-evacuation_information_from_other_em
  
  
• incident command information coordination - 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 - 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 - 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:
  • foem-incident_response_coordination
  • foem-request_for_emergency_support
  • foem-response_for_emergency_support
  
  
• resource coordination - 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:
  • foem-evacuation_resource_request
  • foem-emergency_resource_response
  • foem-emergency_resource_request
  • foem-evacuation_resource_response
  
  
• threat information coordination - Sensor, surveillance, and threat data including raw and processed data that is collected by sensor and surveillance equipment located in secure areas.
  Data Flows:
  • foem-threat_analysis_results
  • foem-verified_image_match
  • foem-secure_area_surveillance
  • foem-threat_info
  • foem-secure_area_sensor_data
  
  
• transportation system status - 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_evacuation
  • foem-transportation_system_status_for_disaster
  
  

Personal Information Access > Emergency Management

• emergency notification - An emergency request for assistance automatically initiated by a vehicle or originated by a traveller using an in-vehicle or personal device.
  Data Flows:
  • emergency_request_personal_traveller_details
  
  

Public Health System > Emergency Management

• public health response - 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_response
  • fphs-public_health_evacuation
  
  

Rail Operations > Emergency Management

• emergency plan coordination - 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 - 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 - Status of the rail system’s response to current incidents.
  Data Flows:
  • fro-rail_incident_response_status
  
  
• rail system status assessment - 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
  
  

Remote Traveller Support > Emergency Management

• alarm notification - Notification of activation of an audible or silent alarm by a traveller in a public area or by a transit vehicle operator using an on-board device.
  Data Flows:
  • traveller_alarm_request
  
  
• secure area sensor data - 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:
  • traveller_secure_area_sensor_threat_data
  • traveller_object_detection_sensor_status
  • traveller_threat_sensor_data
  • field_processed_traveller_object_detection_sensor_data
  • field_processed_traveller_threat_sensor_data
  • field_processed_traveller_intrusion_motion_sensor_data
  • traveller_intrusion_motion_sensor_status
  • traveller_threat_sensor_status
  • traveller_object_detection_sensor_data
  • traveller_intrusion_motion_sensor_data
  
  
• secure area surveillance data - 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:
  • field_processed_traveller_secure_area_audio
  • field_processed_traveller_secure_area_images
  • traveller_secure_area_images
  • traveller_secure_area_audio
  • traveller_secure_area_surveillance_status
  • traveller_secure_area_surveillance_threat_data
  
  

Security Monitoring Subsystem > Emergency Management

• infrastructure monitoring sensor data - 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:
  • infrastructure_integrity_sensor_status
  • field_processed_infrastructure_integrity_sensor_data
  
  
• secure area sensor data - 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:
  • infrastructure_integrity_sensor_data
  • field_processed_intrusion_motion_sensor_data
  • field_processed_object_detection_sensor_data
  • field_processed_threat_sensor_data
  • object_detection_sensor_status
  • intrusion_motion_sensor_data
  • intrusion_motion_sensor_status
  • secure_area_sensor_threat_data
  • threat_sensor_status
  • threat_sensor_data
  • object_detection_sensor_data
  
  
• secure area surveillance data - 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:
  • secure_area_surveillance_status
  • field_processed_secure_area_images
  • secure_area_audio
  • secure_area_surveillance_threat_data
  • secure_area_images
  • field_processed_secure_area_audio
  
  

Shelter Providers > Emergency Management

• shelter information - Evacuation shelter information including location, hours of operation, special accommodations, and current vacancy/availability information.
  Data Flows:
  • fsp-shelter_information
  
  

Toll Administration > Emergency Management

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

Traffic Management > Emergency Management

• alert status - Information indicating the current status of the emergency alert including identification of the traveller and driver information systems that are being used to provide the alert.
  Data Flows:
  • alert_notification_status_from_traffic
  
  
• emergency plan coordination - 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:
  • evacuation_plan_coordination_from_traffic
  • disaster_response_plan_coordination_from_traffic
  
  
• emergency routes - 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 - 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:
  • emergency_traffic_control_response
  • barrier_system_status_to_emerg
  • safeguard_system_status_to_emerg
  • traffic_evacuation_status
  • roadway_information_status_from_traffic
  
  
• incident information - 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_clear
  • wrong_way_vehicle_detection
  • incident_alert_details
  • planned_events_for_em_response
  
  
• incident response status - 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 - 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 - 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 - 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:
  • roadway_detours_and_closures_for_em_response
  • roadway_detours_and_closures_for_em
  • traffic_data_for_em_response
  • traffic_data_for_emergency_services
  
  
• road network status assessment - 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 - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images and the operational status of the surveillance system.
  Data Flows:
  • incident_video_for_emergency_services
  
  

Transit Management > Emergency Management

• alert status - Information indicating the current status of the emergency alert including identification of the traveller and driver information systems that are being used to provide the alert.
  Data Flows:
  • alert_notification_status_from_transit
  
  
• emergency plan coordination - 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 - 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 - 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:
  • transit_evacuation_status
  • response_for_emergency_transit_support
  
  
• transit emergency data - 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_coordination_data
  • transit_emergency_data
  • transit_incident_details
  
  
• transit system status assessment - 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 Subsystem > Emergency Management

• alarm notification - Notification of activation of an audible or silent alarm by a traveller in a public area or by a transit vehicle operator using an on-board device.
  Data Flows:
  • transit_vehicle_location_for_alarms
  • secure_transit_vehicle_alarm_request
  
  
• secure area sensor data - 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:
  • vehicle_object_detection_sensor_status
  • field_processed_vehicle_threat_sensor_data
  • transit_vehicle_location_for_sensors
  • field_processed_vehicle_object_detection_sensor_data
  • vehicle_secure_area_sensor_threat_data
  • vehicle_threat_sensor_data
  • vehicle_object_detection_sensor_data
  • vehicle_threat_sensor_status
  
  
• secure area surveillance data - 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:
  • vehicle_secure_area_surveillance_status
  • vehicle_secure_area_surveillance_threat_data
  • field_processed_vehicle_secure_area_audio
  • vehicle_secure_area_audio
  • vehicle_secure_area_images
  • field_processed_vehicle_secure_area_images
  
  
• transit vehicle location data - 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 - An emergency request for assistance automatically initiated by a vehicle or originated by a traveller using an in-vehicle or personal device.
  Data Flows:
  • emergency_request_vehicle_details
  • driver_status_update
  • emergency_request_driver_details
  • vehicle_status_update
  • vehicle_security_system_commands_request