Other Emergency Management (Terminator*)
Representing other Emergency Management centers, systems or subsystems, this terminator provides a source and destination for ITS data flows between various communications centers operated by public safety agencies, emergency management agencies, other allied agencies, and private companies that participate in coordinated management of highway-related incidents, including disasters. The interface represented by this terminator enables emergency management activities to be coordinated across jurisdictional boundaries and between functional areas. In the Physical Architecture this terminator is a reciprocal Emergency Management Subsystem (EM) implying the requirements for general networks connecting many allied agencies. The interface between this terminator and the EM supports coordination of incident management information between many different centers providing Public Safety Answering Point (both public or private sector implementations), Public Safety Dispatch, Emergency Operations Centers, and other functions that participate in the detection, verification, response, recovery and clearance of incidents, including disasters. This terminator also supports interface to other allied agencies like utility companies that also participate in the coordinated response to selected highway-related incidents.
Inputs/Outputs: Architecture Flows* and Data Flows*
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*: - 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*: - 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*: - 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*: - 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*: - 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*:
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*: - 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*: - 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*: - 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*: - 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*: - 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*:
