EM01-Emergency Call-Taking and Dispatch (Service Package*)

Description

This service package provides basic public safety call-taking and dispatch services. It includes emergency vehicle equipment, equipment used to receive and route emergency calls, and wireless communications that enable safe and rapid deployment of appropriate resources to an emergency. Coordination between Emergency Management Subsystems supports emergency notification between agencies. Wide area wireless communications between the Emergency Management Subsystem and an Emergency Vehicle supports dispatch and provision of information to responding personnel.

Service Package Graphic

Emergency Call-TakingOn-board EV En Route SupportEmergency DispatchEmergency ManagementTraffic ManagementEmergency System OperatorMap Update ProviderTransit ManagementOther Emergency ManagementEmergency Telecommunications SystemEmergency VehicleEmergency Personnelremote surveillance controltraffic imagesemergency operations statusmap updatesmap update requestincident notification responseincident notificationtransit emergency dataincident reportincident response coordinationemergency operations inputsemergency vehicle tracking dataemergency dispatch requestsemergency dispatch responseemergency personnel inputsemergency personnel information presentation

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

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Emergency Management emergency operations status Emergency System Operator Yes
Emergency Management incident notification response Emergency Telecommunications System Yes
Emergency Management emergency dispatch requests Emergency Vehicle Yes
Emergency Management map update request Map Update Provider Yes
Emergency Management incident report Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Emergency Management Yes
Emergency Management incident response coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Emergency Management Yes
Emergency Management remote surveillance control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Emergency Personnel emergency personnel inputs Emergency Vehicle Yes
Emergency System Operator emergency operations inputs Emergency Management Yes
Emergency Telecommunications System incident notification Emergency Management Yes
Emergency Vehicle emergency dispatch response Emergency Management Yes
Emergency Vehicle emergency vehicle tracking data Emergency Management Yes
Emergency Vehicle emergency personnel information presentation Emergency Personnel Yes
Map Update Provider map updates Emergency Management Yes
Other Emergency Management incident report Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Other Emergency Management incident response coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Transit Management transit emergency data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
    - This icon indicates that the associated architecture flow either has been or will be addressed by ITS Standards. Select the architecture flow for more information on relevant standards activities.

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Support regional economic productivity and development
B. Increase the safety of the transportation system for motorized and nonmotorized users; Improve the safety of the transportation system
C. Increase the security of the transportation system for motorized and nonmotorized users; Improve the security of the transportation system
D. Increase the accessibility and mobility of people and for freight; Enhance mobility, convenience, and comfort for transportation system users
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance the integration and connectivity of the transportation system
G. Promote efficient system management and operation; Increase operational efficiency and reliability of the transportation system

Associated Objective Categories

Objective Category
Emergency/Incident Management: Customer Satisfaction
Emergency/Incident Management: Incident Duration
Emergency/Incident Management: Inter-Agency Coordination
Emergency/Incident Management: Person Hours of Delay

Associated Objectives and Performance Measures

Objective Performance Measure
Increase customer satisfaction with the region's incident management by X percent over Y years. Percentage of customers satisfied with region's incident management practices.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Number of agencies in the region with interoperable voice communications.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Number of participating agencies in a regional coordinated incident response team.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Percentage of incident management agencies in region participating in multi-modal information exchange network.
Reduce mean incident clearance time per incident by X percent over Y years. (Defined as the time between awareness of an incident and the time the last responder has left the scene.) Mean incident clearance time per incident.
Reduce mean incident notification time (defined as the time between the first agency's awareness of an incident and the time to notify needed response agencies) by X percent over Y years (i.e., through "Motorist Assist" roving patrol programs, reduction of inaccurate verifications, etc.). Average incident notification time of necessary response agencies.
Reduce mean roadway clearance time per incident by X percent over Y years. (Defined as the time between awareness of an incident and restoration of lanes to full operational status.) Mean roadway clearance time per incident.
Reduce mean time for needed responders to arrive on-scene after notification by X percent over Y years. Mean time for needed responders to arrive on-scene after notification.
Reduce mean time of incident duration (from awareness of incident to resumed traffic flow) on transit services and arterial and expressway facilities by X percent in Y years. Mean time of incident duration.
Reduce the person hours (or vehicle hours) of total delay associated with traffic incidents by X percent over Y years. Person hours (or vehicle hours) of delay associated with traffic incidents.


 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Related ITS Applications of ITS Taxonomy

Classification Category ITS Application Area ITS Application(s)
Intelligent Infrastructure Emergency Management Response & Recovery Response Management

User Services related to this Service Package:

User Service
4.5 Hazardous Material Security And Incident Response
5.2 Emergency Vehicle Management

Transaction Set Diagram

Note that this transaction set diagram (TSD) is only 1 of the 2 TSDs and so only a portion of the numbered items below refer to the TSD.
EM01 transaction set diagrams: Part 1, Part 2,



The source graphic, a Windows Metafile (WMF), for the TSDs can be downloaded here: TSD Part 1, TSD Part 2,

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

  1. The process is under the asynchronous monitoring and control of the Emergency System Operator. In the initial steps of this process, the Emergency System Operator represents the call-taker, who interacts with callers, monitors alarms, and other incident reports (emergency operations status) and enters incident information into the system to support incident tracking and response (emergency operations inputs).

  2. Incidents are reported by the public through the Emergency Telecommunications System (incident notification), including a description of the incident and information about the caller. This represents the Public Safety Answering Point’s (PSAPs) interface to 911 and other emergency access numbers. The Emergency System Operator interacts with the caller, collecting additional information and verifying the information provided and providing an indication of incident response status back to the caller (incident notification response).

  3. Transit Management can notify Emergency Management about incidents associated with the transit system (transit emergency data).

  4. If Traffic Management permits, the Emergency Management subsystem can control the field surveillance equipment (remote surveillance control) associated with a Traffic Management subsystem (e.g., pan, tilt, and zoom). Traffic images are returned that contain the product of that surveillance (traffic images). These images may be used by the call-taker to verify the incident location and gather additional information about the incident.

  5. Reported incident information is provided to the appropriate dispatcher based on location and the nature of the reported incident (incident report). This incident report may represent a positive hand-off of an incident between two systems in scenarios where the call-taker and dispatcher are on different systems, or it may represent the providing of incident information between peer response agencies. As a response is dispatched, incident response information is shared with the call-taker (incident response coordination) so that accurate response information can be conveyed back to the caller. In the case of peer response agencies the incident response coordination allows response coordination between the agencies.

  6. Like the call-taking process described in the previous steps, the dispatch process is also under the continuous asynchronous monitoring (emergency operations status) and control (emergency operations inputs) of the Emergency Systems Operator, representing the dispatcher in the final steps of this process. Note that the call-taker and dispatch positions may be operated by the same person, by different people in the same communications center, or by different people in different communications centers.

  7. An incident report is provided to the Emergency Management Subsystem, representing communication to the Computer-Aided Dispatch system. As a response is dispatched, incident response information is shared with other Emergency Management Subsystems, supporting coordinated dispatch in mutual aid scenarios and other scenarios where more than one agency is supporting the incident response (incident response coordination).

  8. One or more units are dispatched to the reported incident (emergency dispatch requests) and the information is made available to the emergency personnel in the vehicle (emergency personnel information presentation). Emergency personnel may confirm the dispatch request (emergency personnel inputs), which is relayed to the Emergency Management Subsystem (emergency dispatch response). In addition, vehicle location (emergency vehicle tracking data) is relayed to the Emergency Management Subsystem to facilitate dispatch of the vehicle.

  9. The Emergency Management Subsystem can keep its mapping system current by subscribing to a map update service. Map updates are provided on request (map update request) to support CAD system operation and facilitate interoperability between CAD systems.