Emergency System Operator --> Emergency Management Center:
emergency operations input
Definitions
emergency operations input (Information Flow): Emergency operator input supporting call taking, dispatch, emergency operations, security monitoring, and other operations and communications center operator functions.
Emergency System Operator (Source Physical Object): 'Emergency System Operator' represents the public safety personnel that monitor emergency requests, (including those from the E911 Operator) and set up pre-defined responses to be executed by an emergency management system. The operator may also override predefined responses where it is observed that they are not achieving the desired result. This also includes dispatchers who manage an emergency fleet (police, fire, ambulance, HAZMAT, etc.) or higher order emergency managers who provide response coordination during emergencies.
Emergency Management Center (Destination Physical Object): The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It 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 Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers.
It 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). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system.
It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center 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.
It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor 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.
Included In
This Triple is in the following Service Packages:
- CVO14: CV Driver Security Authentication
- PS01: Emergency Call-Taking and Dispatch
- PS02: Emergency Response
- PS04: Mayday Notification
- PS09: Transportation Infrastructure Protection
- PS10: Wide-Area Alert
- PS11: Early Warning System
- PS12: Disaster Response and Recovery
- PS13: Evacuation and Reentry Management
- PS15: Stolen Vehicle Recovery
- PT05: Transit Security
- TM08: Traffic Incident Management System
- TM19: Roadway Closure Management
This triple is associated with the following Functional Objects:
- Emergency Call-Taking
- Emergency Commercial Vehicle Response
- Emergency Dispatch
- Emergency Early Warning System
- Emergency Evacuation Support
- Emergency Incident Command
- Emergency Notification Support
- Emergency Response Management
- Emergency Routing
- Emergency Secure Area Alarm Support
- Emergency Secure Area Sensor Management
- Emergency Secure Area Surveillance
- Emergency Stolen Vehicle Recovery
This Triple is described by the following Functional View Data Flows:
- feso-alerts_and_advisories
- feso-archive_commands
- feso-emergency_action_log_request
- feso-emergency_allocation_override
- feso-emergency_data_input
- feso-emergency_data_output_request
- feso-emergency_display_update_request
- feso-emergency_response
- feso-emergency_routing_input
- feso-image_processing_parameters
- feso-secure_area_sensor_surveillance_control
- feso-vehicle_recovery_inputs
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Emergency Management Center | Emergency System Operator | emergency operations status |
Communication Solutions
No communications solutions identified.Characteristics
None defined |
Interoperability | Description |
---|---|
Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | High | High | |
Basis | Emergency system controls should not be casually viewable as they impact the availability of emergency services, which if known could be leveraged for illegal activity. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. |