< < PM06 : PS01 : PS02 > >

PS01: Emergency Call-Taking and Dispatch

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 Centers supports emergency notification between agencies. Wide area wireless communications between the Emergency Management Center and an Emergency Vehicle supports dispatch and provision of information to responding personnel. This service package also provides information to support dynamic routing of emergency vehicles. Traffic information, road conditions, and weather advisories are provided to enhance emergency vehicle routing. The Emergency Management Center provides routing information based on real-time conditions and has the option to request an ingress/egress route from the Traffic Management Center.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Emergency Management Center Manager Emergency Management Center Manages
Emergency Management Center Manager Emergency Personnel System Usage Agreement
Emergency Management Center Manager Emergency System Operator System Usage Agreement
Emergency Management Center Owner Emergency Management Center Owns
Emergency Management Center Owner Emergency Management Center Manager Operations Agreement
Emergency Management Center Owner Emergency Telecommunications System Owner Information Exchange Agreement
Emergency Management Center Owner Emergency Vehicle OBE Owner Information Exchange Agreement
Emergency Management Center Owner Other Emergency Management Centers Owner Information Exchange Agreement
Emergency Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Emergency Management Center Supplier Emergency Management Center Owner Warranty
Emergency Personnel Emergency Management Center Operates
Emergency Personnel Emergency Vehicle OBE Operates
Emergency Personnel Location and Time Data Source Operates
Emergency System Operator Emergency Management Center Operates
Emergency Telecommunications System Manager Emergency Telecommunications System Manages
Emergency Telecommunications System Owner Emergency Management Center Owner Information Exchange Agreement
Emergency Telecommunications System Owner Emergency Telecommunications System Owns
Emergency Telecommunications System Owner Emergency Telecommunications System Manager Operations Agreement
Emergency Telecommunications System Supplier Emergency Telecommunications System Owner Warranty
Emergency Vehicle OBE Manager Emergency Personnel System Usage Agreement
Emergency Vehicle OBE Manager Emergency Vehicle OBE Manages
Emergency Vehicle OBE Owner Emergency Management Center Owner Information Exchange Agreement
Emergency Vehicle OBE Owner Emergency Vehicle OBE Owns
Emergency Vehicle OBE Owner Emergency Vehicle OBE Manager Operations Agreement
Emergency Vehicle OBE Supplier Emergency Vehicle OBE Owner Warranty
Location and Time Data Source Manager Emergency Personnel System Usage Agreement
Location and Time Data Source Manager Location and Time Data Source Manages
Location and Time Data Source Owner Location and Time Data Source Owns
Location and Time Data Source Owner Location and Time Data Source Manager Operations Agreement
Location and Time Data Source Supplier Location and Time Data Source Owner Warranty
Maint and Constr Management Center Manager Maint and Constr Management Center Manages
Maint and Constr Management Center Owner Emergency Management Center Owner Information Provision Agreement
Maint and Constr Management Center Owner Maint and Constr Management Center Owns
Maint and Constr Management Center Owner Maint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center Supplier Maint and Constr Management Center Owner Warranty
Other Emergency Management Centers Manager Other Emergency Management Centers Manages
Other Emergency Management Centers Owner Emergency Management Center Owner Information Exchange Agreement
Other Emergency Management Centers Owner Other Emergency Management Centers Owns
Other Emergency Management Centers Owner Other Emergency Management Centers Manager Operations Agreement
Other Emergency Management Centers Supplier Other Emergency Management Centers Owner Warranty
Rail Operations Center Manager Rail Operations Center Manages
Rail Operations Center Owner Emergency Management Center Owner Information Provision Agreement
Rail Operations Center Owner Rail Operations Center Owns
Rail Operations Center Owner Rail Operations Center Manager Operations Agreement
Rail Operations Center Supplier Rail Operations Center Owner Warranty
Surface Transportation Weather Service Manager Surface Transportation Weather Service Manages
Surface Transportation Weather Service Owner Emergency Management Center Owner Information Provision Agreement
Surface Transportation Weather Service Owner Surface Transportation Weather Service Owns
Surface Transportation Weather Service Owner Surface Transportation Weather Service Manager Operations Agreement
Surface Transportation Weather Service Supplier Surface Transportation Weather Service Owner Warranty
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Owner Emergency Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Traffic Management Center Owns
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Transit Management Center Manager Transit Management Center Manages
Transit Management Center Owner Emergency Management Center Owner Information Provision Agreement
Transit Management Center Owner Transit Management Center Owns
Transit Management Center Owner Transit Management Center Manager Operations Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Emergency Management Center Owner Information Provision Agreement
Transportation Information Center Owner Transportation Information Center Owns
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Weather Service System Manager Weather Service System Manages
Weather Service System Owner Emergency Management Center Owner Information Provision Agreement
Weather Service System Owner Weather Service System Owns
Weather Service System Owner Weather Service System Manager Operations Agreement
Weather Service System Supplier Weather Service System Owner Warranty

Maintenance Stage Roles and Relationships

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Emergency Management Center 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
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 Environmental Monitoring 5.1.4 Manage Emergency Response
Emergency Routing 5.2 Provide Operator Interface for Emergency Data
5.3.6 Maintain Vehicle Status
5.3.7 Provide Emergency Vehicle Route
5.5 Update Emergency Display Map Data
5.7.1 Assess System Status For Disasters
5.7.3 Assess System Status For Evacuation
Emergency Vehicle OBE EV On-Board En Route Support 5.3.3 Provide Emergency Vehicle Location
5.3.5 Provide Emergency Personnel Interface
5.3.9 Process Mobile Emergency Requests
Traffic Management Center TMC Incident Dispatch Coordination 1.1.4.1 Retrieve Traffic Data
1.1.5 Exchange Data with Other Traffic Centers
1.3.2.1 Store Possible Incident Data
1.3.2.2 Review and Classify Possible Incidents
1.3.2.3 Review and Classify Planned Events
1.3.2.6 Manage Traffic Routing
1.3.3.1 Respond to Current Incidents
1.3.4.1 Retrieve Incident Data
1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.4.3 Provide Media Incident Data Interface
1.3.4.4 Manage Resources for Incidents
1.3.5 Manage Incident Response Planning and Traffic Management Decision Support
1.3.6 Traffic Disaster Response Control
1.3.7 Traffic Evacuation Control

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Emergency Management Center Center 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.
Emergency Personnel Vehicle 'Emergency Personnel' represents personnel that are responsible for police, fire, emergency medical services, towing, service patrols, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle during dispatch to the incident site, but often work independently of the Emergency Vehicle while providing their incident response services.
Emergency System Operator Center '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 Telecommunications System Center The 'Emergency Telecommunications System' represents the telecommunications systems that connect a caller with a Public Safety Answering Point (PSAP). These systems transparently support priority wireline and wireless caller access to the PSAP through 9-1-1 and other access mechanisms like 7 digit local access numbers, and motorist aid call boxes. The calls are routed to the appropriate PSAP, based on caller location when this information is available. When available, the caller's location and call-back number are also provided to the PSAP by this interface. This facility may also be used to notify the public - residents and businesses - of emergency situations using a Reverse 911 capability.
Emergency Vehicle OBE Vehicle The Emergency Vehicle On-Board Equipment (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.
Location and Time Data Source ITS The 'Location and Time Data Source' provides accurate position information. While a Global Positioning System (GPS) Receiver is the most common implementation, this physical object represents any technology that provides a position fix in three dimensions and time with sufficient accuracy.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.

The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)

Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Other Emergency Management Centers Center 'Other Emergency Management Centers' provides a source and destination for information 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 transportation-related incidents, including disasters. The interface represented by this object enables emergency management activities to be coordinated across jurisdictional boundaries and between functional areas, supporting requirements for general networks connecting many allied agencies. It also supports interface to other allied agencies like utility companies that also participate in the coordinated response to selected highway-related incidents.
Rail Operations Center Center 'Rail Operations Center' represents the (usually) centralized control point for a substantial segment of a freight railroad's operations and maintenance activities. It is roughly the railroad equivalent to a highway Traffic Management Center. It is the source and destination of information that can be used to coordinate rail and highway traffic management and maintenance operations. It is also the source and destination for incident, incident response, disaster, or evacuation information that is exchanged with an Emergency Management Center. The use of a single object for multiple sources and destination for information exchange with railroads implies the need for a single, consistent interface between a given railroad's operations and maintenance activities and ITS.
Surface Transportation Weather Service Center The 'Surface Transportation Weather Service' represents the providers of value-added sector-specific meteorological services. These providers utilize National Weather Service data and predictions, road condition information and local environmental data provided by traffic management or maintenance organizations, and their own models to provide surface transportation related weather observations and forecasts including pavement temperature and conditions.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transportation Information Center Center The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Weather Service System Center The 'Weather Service System' provides weather, hydrologic, and climate information and warnings of hazardous weather including thunderstorms, flooding, hurricanes, tornadoes, winter weather, tsunamis, and climate events. It provides atmospheric weather observations and forecasts that are collected and derived by the National Weather Service, private sector providers, and various research organizations. The interface provides formatted weather data products suitable for on-line processing and integration with other ITS data products as well as Doppler radar images, satellite images, severe storm warnings, and other products that are formatted for presentation to various ITS users.

Includes Functional Objects:

Functional Object Description Physical Object
Emergency Call-Taking 'Emergency Call-Taking' supports the emergency call-taker, collecting available information about the caller and the reported emergency, and forwarding this information to other objects that formulate and manage the emergency response. It receives 9-1-1, 7-digit local access, and motorist call-box calls and interfaces to other agencies to assist in the verification and assessment of the emergency and to forward the emergency information to the appropriate response agency. Emergency Management Center
Emergency Dispatch 'Emergency Dispatch' tracks the location and status of emergency vehicles and dispatches these vehicles to incidents. Pertinent incident information is gathered from the public and other public safety agencies and relayed to the responding units. Incident status and the status of the responding units is tracked so that additional units can be dispatched and/or unit status can be returned to available when the incident is cleared and closed. Emergency Management Center
Emergency Environmental Monitoring 'Emergency Environmental Monitoring' collects current and forecast road conditions and surface weather information from a variety of sources. The collected environmental information is monitored and presented to the operator and used to more effectively manage incidents. Emergency Management Center
Emergency Routing 'Emergency Routing' supports routing of emergency vehicles and enlists support from the Traffic Management Center to facilitate travel along these routes. Routes may be determined based on real-time traffic information and road conditions or routes may be provided by the Traffic Management Center on request. Vehicles are tracked and routes are based on current vehicle location. It may coordinate with the Traffic Management Center to provide preemption or otherwise adapt the traffic control strategy along the selected route. Emergency Management Center
EV On-Board En Route Support 'EV On-Board En Route Support' provides communications functions to responding emergency vehicles that reduce response times and improve safety of responding public safety personnel and the general public. It supports traffic signal preemption via short range communication directly with signal control equipment and sends alert messages to surrounding vehicles. Emergency Vehicle OBE
TMC Incident Dispatch Coordination 'TMC Incident Dispatch Coordination' formulates and manages an incident response that takes into account the incident potential, incident impacts, and resources required for incident management. It provides information to support dispatch and routing of emergency response and service vehicles as well as coordination with other cooperating agencies. It provides access to traffic management resources that provide surveillance of the incident, traffic control in the surrounding area, and support for the incident response. It monitors the incident response and collects performance measures such as incident response and clearance times. Traffic Management Center

Includes Information Flows:

Information Flow Description
current infrastructure 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.
emergency dispatch requests Emergency vehicle dispatch instructions including incident location and available information concerning the incident.
emergency dispatch response Request for additional emergency dispatch information and provision of en route status.
emergency operations input Emergency operator input supporting call taking, dispatch, emergency operations, security monitoring, and other operations and communications center operator functions.
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 center operator positions.
emergency personnel information presentation Presentation of information to emergency personnel in the field including dispatch information, incident information, current road network conditions, device status, and other supporting information.
emergency personnel input User input from emergency personnel in the field including dispatch coordination, incident status information, and remote device control requests.
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. It may also include a request for preemption/priority for the identified vehicle at all signalized intersections along the route.
emergency routes Suggested ingress and egress routes for access to and between the scene and staging areas or other specialized emergency access routes.
emergency vehicle tracking data The current location and operating status of the emergency vehicle.
incident notification The notification of an incident including its nature, severity, and location.
incident notification response Interactive acknowledgement and verification of the incident information received, requests for additional information, and general information on incident response status.
incident report Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate incident response.
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.
location and time The current geographic location in three dimensions (latitude, longitude, elevation) and the current time.
railroad schedules Train schedules, maintenance schedules, and other information from the railroad that supports forecast of HRI closures.
remote surveillance control The control commands used to remotely operate another center's sensors or surveillance equipment so that roadside surveillance assets can be shared by more than one agency.
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 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.
road network environmental situation data Aggregated environmental situation data collected from vehicles and other sources for the road network. Aggregated information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information for the region.
road weather advisories Segment-specific weather and road conditions including real-time advisories of deteriorating road and weather conditions, medium-term advisories for the next 2-12 hours, and long-term advisories more than 12 hours into the future. The advisories may include advisories that are issued based on locally collected environmental data (e.g., an ice on bridge advisory).
road weather advisories for emergency response Segment-specific weather and road conditions including real-time advisories of deteriorating road and weather conditions, medium-term advisories for the next 2-12 hours, and long-term advisories more than 12 hours into the future. This flow is filtered, tailored, and augmented to support emergency responders.
special vehicle restricted use information Parameters necessary for implementing unrestricted access to controlled access or toll facilities by special vehicles; e.g., maintenance vehicles, emergency vehicles, etc.
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.
traffic image meta data Meta data that describes traffic images. Traffic images (video) are in another flow.
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. Meta data that describes the images is contained in another flow.
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.
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.
weather information Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
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.

Goals and Objectives

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; Improve the national freight network, strengthen the ability of rural communities to access national and international trade markets, and support regional economic development
B. Increase the safety of the transportation system for motorized and nonmotorized users; Achieve a significant reduction in traffic fatalities and serious injuries on all public roads
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; Achieve a significant reduction in congestion
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; Improve the efficiency of the surface 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.
Increase the number of corridors in the region covered by regional coordinated incident response teams by X percent in Y years. Number of TIM corridors in the region covered by regional coordinated incident response teams.
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 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.

Needs and Requirements

Need Functional Object Requirement
01 Emergency Management needs to provide basic public safety call-taking and dispatch of emergency vehicles in order to provide safe and rapid deployment of appropriate resources to an emergency. Emergency Call-Taking 01 The emergency call-taking center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7-digit call routing) to receive emergency notification information and provide it to the emergency system operator.
02 Theemergency call-taking center shall receive emergency call information from 911 services and present the possible incident information to the emergency system operator.
04 The emergency call-taking center shall receive emergency call information from other emergency management centers, e.g. mayday service providers, and present the possible incident information to the emergency system operator.
07 The emergency call-taking center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls and internal analysis of security sensor and surveillance data, and assign each a level of confidence.
10 The emergency call-taking center shall update the incident information log once the emergency system operator has verified the incident.
Emergency Dispatch 01 The center shall dispatch emergency vehicles to respond to verified emergencies under center personnel control.
02 The center shall store the current status of all emergency vehicles available for dispatch and those that have been dispatched.
03 The center shall relay location and incident details to the responding vehicles.
04 The center shall track the location and status of emergency vehicles responding to an emergency based on information from the emergency vehicle.
05 The center shall store and maintain the emergency service responses in an action log.
EV On-Board En Route Support 01 The emergency vehicle, including roadway service patrols, shall track its current location.
02 The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the center for emergency management and dispatch.
03 The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when dispatched to a scene.
04 The emergency vehicle shall send the current en route status (including estimated time of arrival) and requests for emergency dispatch updates.
06 The emergency vehicle shall provide the personnel on-board with dispatch information, including incident type and location, and forward an acknowledgment from personnel to the center that the vehicle is on its way to the incident scene.
02 Emergency Management needs to coordinate with other emergency management operations in order to support emergency notification between agencies. Emergency Call-Taking 05 The emergency call-taking center shall receive emergency notification information from other public safety agencies and present the possible incident information to the emergency system operator.
06 The emergency call-taking center shall receive emergency notification information from public transit systems and present the possible incident information to the emergency system operator.
08 The emergency call-taking center shall send a request for remote control of Closed-circuit Television (CCTV) systems from a traffic management center in order to verify the reported incident.
09 The emergency call-taking center shall forward the verified emergency information to the responding agency based on the location and nature of the emergency.
Emergency Dispatch 06 The center shall coordinate response to incidents with other Emergency Management centers to ensure appropriate resources are dispatched and utilized.
07 The center shall receive traffic images to support dispatch of emergency vehicles.
08 The center shall provide the capability to request remote control of traffic surveillance devices.
03 Emergency Management needs to process current and historical weather and road conditions data from multiple sources in order to generate warnings and route advisories for individual emergency responders or emergency response dispatchers. Emergency Dispatch 01 The center shall dispatch emergency vehicles to respond to verified emergencies under center personnel control.
09 The center shall process road and weather conditions to provide updates to responding personnel.
Emergency Environmental Monitoring 01 The center shall collect current and forecast road and weather information from weather service providers (such as the National Weather Service and value-added sector specific meteorological services).
02 The center shall collect road network conditions data, including advisories, from traffic management and traveler information centers.
03 The center shall collect asset restrictions information from roadway maintenance operations.
04 The center shall assimilate current and forecast road conditions and surface weather information to support incident management.
Emergency Routing 01 The center shall collect current traffic and road condition information for emergency vehicle route calculation.
04 The center shall receive asset restriction information to support the dispatching of appropriate emergency resources.
05 The center shall receive current railroad schedule information for emergency vehicle route calculation.
07 The center shall calculate emergency vehicle routes, under center personnel control, based on the collected traffic and road conditions information.
EV On-Board En Route Support 02 The emergency vehicle, including roadway service patrols, shall send the vehicle's location and operational data to the center for emergency management and dispatch.
TMC Incident Dispatch Coordination 07 The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
04 Emergency Management needs to provide emergency responders with road weather warnings and advisories. Emergency Environmental Monitoring 05 The center shall provide the road and weather warning and advisories to the emergency responders.
Emergency Routing 10 The center shall provide the calculated route for emergency vehicles to the dispatch function.
05 Emergency Management needs to provide routing information to the emergency responders. Emergency Routing 06 The center shall track current emergency vehicle location and status along with other emergency vehicle characteristics.
08 The center shall request and receive ingress and egress routes or other specialized emergency access routes from the traffic management center.
EV On-Board En Route Support 03 The emergency vehicle, including roadway service patrols, shall receive incident details and a suggested route when dispatched to a scene.
TMC Incident Dispatch Coordination 03 The center shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption.

Related Sources

Document Name Version Publication Date
Concept of Operations For Road Weather Connected Vehicle Applications Draft v1.4.2 6/26/2012
ITS User Services Document 1/1/2005


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Emergency Management Center High High High Class 5
Emergency Telecommunications System Moderate Moderate Moderate Class 2
Emergency Vehicle OBE Moderate High High Class 5
Location and Time Data Source Moderate High High Class 5
Maint and Constr Management Center Low High High Class 5
Other Emergency Management Centers High High Moderate Class 4
Rail Operations Center Low Moderate Moderate Class 1
Surface Transportation Weather Service Low Moderate Moderate Class 1
Traffic Management Center High High High Class 5
Transit Management Center Moderate High High Class 5
Transportation Information Center Low High Moderate Class 3
Weather Service System Low Moderate Moderate Class 1



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Emergency Management Center Emergency System Operator emergency operations status Moderate High High
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.
Emergency Management Center Emergency Telecommunications System incident notification response Moderate Moderate Moderate
May contain information specific to an incident and certainly includes follow-on information, which if observed would provide context for the status of an incident, which could be used by a hostile actor for target identification, damage assessment or similar activities. As a part of incident management activities, this flow must be available, correct and uncorrupted, or management of the incident may be suboptimal, harming safety and or mobility. As a part of incident management activities, this flow must be available, correct and uncorrupted, or management of the incident may be suboptimal, harming safety and or mobility.
Emergency Management Center Emergency Vehicle OBE emergency dispatch requests Moderate High Moderate
Contains emergency vehicle identity and incident details that could include PII. Could be HIGH, depending on the scenario. Emergency response information that has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for providing dispatch and response, so MODERATE.
Emergency Management Center Emergency Vehicle OBE road weather advisories for emergency response Moderate Moderate Moderate
Weather alert data may be specific to the emergency vehicle's location, which if known may enable criminal activity (though avoidance for example). This information will be used by emergency personnel in their decision making, so should be timely and accurate. Given that they will likely have other means of learning this information, including personal observation, MODERATE and not HIGH. This information will be used by emergency personnel in their decision making, so should be timely and accurate. Given that they will likely have other means of learning this information, including personal observation, MODERATE and not HIGH.
Emergency Management Center Emergency Vehicle OBE suggested route Moderate High Moderate
It is important for this route to be kept confidential to prevent everyone from attempting to travel this route. The emergency vehicle must receive an accurate Suggested Route. If the emergency vehicle is dispatched to an incorrect location it could lead to a significant delay in the vehicle responding to the emergency. This delay could lead to the loss of life or limb of a person. Therefore, if received, the suggested route must be trustworthy. The alternative to use of a Suggested Route is that drivers select the route themselves. Without the Suggested Route the driver may get stuck in traffic or behind an accident that slows down their response time. This is a degradation of the business service being provided, and could lead to an emergency vehicle not responding to an incident in the quickest manner.
Emergency Management Center Other Emergency Management Centers incident report High Moderate Moderate
This data contains all information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. DISC: WYO believes this to be MODERATE. Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TMC has received a message.
Emergency Management Center Other Emergency Management Centers incident response coordination Moderate Moderate Moderate
Will include incident-specific information that could be used by a hostile attacker to target emergency resources, or to avoid those resources in the commission of a crime. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility.
Emergency Management Center Traffic Management Center emergency route request High High High
Traffic management emergency routing information is distributed as needed to those that need to know. Interception by an unintended recipient enables abuse, particularly for an actor interested in disturbing the situation further. if this information is corrupted the EMC or Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects. if this information is corrupted the EMC or Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects.
Emergency Management Center Traffic Management Center remote surveillance control Moderate High Moderate
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: NYC believes this to be low: "This information is directly observable." Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. From NYC: The information sent from TMC directly affect the ITS-RE speed "announcement". Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.. From NYC: The ITS-RE can work accordingly or in fail-safe if information is not available.
Emergency Management Center Traffic Management Center special vehicle restricted use information Moderate Moderate Moderate
Contents of this flow enable specialized or elevated use of transportation facilities, which if copied could enable misuse of transportation assets. Incorrect data or unvailability will hamper legitimate maintenance, incident management and emergency use, which can have a significant effect. However, alternative means to allow those behaviors should already exist, at least for well marked emergency and safety vehicles, thus MODERATE and not HIGH. Incorrect data or unvailability will hamper legitimate maintenance, incident management and emergency use, which can have a significant effect. However, alternative means to allow those behaviors should already exist, at least for well marked emergency and safety vehicles, thus MODERATE and not HIGH.
Emergency Personnel Emergency Vehicle OBE emergency personnel input Moderate Moderate Moderate
Some of the information, such as incident status information, is sensitive, and should be protected. The system must know that these requests came from actual Emergency Personal. Additionally, incorrect information here may lead to the system responding incorrectly to the incident These messages are important for the system to operate properly. Additionally, the system must know if messages are not received so that it can act accordingly.
Emergency System Operator Emergency Management Center emergency operations input Moderate High High
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.
Emergency Telecommunications System Emergency Management Center incident notification Moderate Moderate Moderate
May contain information specific to an incident and certainly includes follow-on information, which if observed would provide context for the status of an incident, which could be used by a hostile actor for target identification, damage assessment or similar activities. As a part of incident management activities, this flow must be available, correct and uncorrupted, or management of the incident may be suboptimal, harming safety and or mobility. As a part of incident management activities, this flow must be available, correct and uncorrupted, or management of the incident may be suboptimal, harming safety and or mobility.
Emergency Vehicle OBE Emergency Management Center emergency dispatch response Moderate High Moderate
Contains emergency vehicle identity and incident details that could include PII. Could be HIGH, depending on the scenario. Emergency response information that has a time-critical and life-saving and property saving component. Ideally HIGH, but there are altenative mechanisms for providing dispatch and response, so MODERATE.
Emergency Vehicle OBE Emergency Management Center emergency vehicle tracking data Moderate Moderate Moderate
Emergency Vehicles give obvious visual and audio indicators about their location and operating status. Knowing the location of every single emergency vehicle within a city could be extremely useful information to a criminal. Additionally, although this is observable data, it is transmitted on a regional level, which means that someone who is able to intercept it would be able to read the location of all emergency vehicles, not just the ones they could directly observed. A sufficiently motivated criminal can however get this information by other means. Incorrect data here could lead to incorrect decisions being made about the closure of lanes, or incorrect information being shared with the emergency vehicles. There should be other indicators that would contradict incorrect information transmitted here. This information may be used to determine which emergency vehicle is dispatched, and having this information available could lead to a quicker response from the emergency vehicle. However, the system would still be able to operate properly if only most messages make it through.
Emergency Vehicle OBE Emergency Personnel emergency personnel information presentation Moderate Moderate Moderate
Some of this information, such as incident information, is sensitive and should be protected. This information could affect how the Emergency Personnel respond to the event, and should be as accurate as possible. This information needs to be available for the Emergency Personnel in order for them to respond accurately to the system. If they do not acknowledge this information, dispatch needs to know, so they can attempt to contact the Emergency Personnel via another channel, such as radio.
Location and Time Data Source Emergency Vehicle OBE location and time Moderate High High
While time reference should be universally available, time reference coupled with vehicle location is tracking data. This flow is internal to a vehicle, but should probably be encrypted to discourage hacking and snooping on the vehicle bus. Thus MODERATE. Location and time data is the basis for crash imminent safety and a host of other applications. Corruption of this flow could lead directly to a vehicle accident. If this information is not available, crash imminent safety applications depending on this information will not function properly.
Maint and Constr Management Center Emergency Management Center current infrastructure restrictions Low High High
This information is intended to be publicly distributed, so there is no reason to obfuscate. If this flow is compromised a vehicle may enter an area that it should not, potentially placing it at risk of an incident due to oversize. Moving violations are possible as well, but the impact of those is trivial compared to the potential of a container impacting a low bridge for example. While the eventual flow to the vehicle will be wireless and likely cannot achieve HIGH, setting this HIGH ensures that compromise of this flow is difficult and thus not to blame for the vehicle to not receive the wireless flow.
Maint and Constr Management Center Emergency Management Center work zone information Low Moderate Moderate
Probably not a significant issue if this data is observed. If the area under construction is sensitive in nature, may be MODERATE. Triples originating with the EMC imply a potential incident, so are rated MODERATE. Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc. Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.
Other Emergency Management Centers Emergency Management Center incident report High Moderate Moderate
This data contains all information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. DISC: WYO believes this to be MODERATE. Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TMC has received a message.
Other Emergency Management Centers Emergency Management Center incident response coordination Moderate Moderate Moderate
Will include incident-specific information that could be used by a hostile attacker to target emergency resources, or to avoid those resources in the commission of a crime. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility.
Rail Operations Center Emergency Management Center railroad schedules Low Moderate Moderate
Does not contain any personal or confidential information. While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally. While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally, though it could be LOW depending on the level of projected updates.
Surface Transportation Weather Service Emergency Management Center transportation weather information Low Moderate Moderate
Typically intended for public distribution. While there are many sources of weather information, some guarantee of correctness is justifiable to keep confidence in provided service. In areas with severe weather it may be justifiable to raise this to HIGH. There should be other sources of this data. It does need to be reliable however; weather can change quickly, and depending on the destination and its operational strategies, timely response may be important. In areas with severe weather it may be justifiable to raise this to HIGH.
Traffic Management Center Emergency Management Center emergency routes High High High
Traffic management emergency routing information is distributed as needed to those that need to know. Interception by an unintended recipient enables abuse, particularly for an actor interested in disturbing the situation further. if this information is corrupted the EMC or Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects. if this information is corrupted the EMC or Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects.
Traffic Management Center Emergency Management Center road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Traffic Management Center Emergency Management Center traffic image meta data Low Moderate Moderate
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally.
Traffic Management Center Emergency Management Center traffic images Low Moderate Moderate
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. While availability of imagery is useful for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally, though it could be LOW.
Transit Management Center Emergency Management Center transit emergency data Moderate High High
Security event or other emergency could be used by an attacker to confirm or further a crime in progress. This must be accurate to ensure correct response, as human safety may be at stake. Human safety could be at stake, which suggest sever consequences.
Transportation Information Center Emergency Management Center road network environmental situation data Low High Moderate
Aggregated data, but indicates the types of systems and status of those systems on vehicles. Should be LOW, but if identifiers are preserved could be MODERATE. Weather Service providers will have many sources of data, and depend on consistent, quality data inputs, so this data needs to meet similar standards at least in terms of transmission quality. MODERATE or HIGH depending on the context; if critical to some operation then HIGH, if not critical then MODERATE. Weather Service providers will have many sources of data, and depend on consistent, quality data inputs, so this data needs to meet similar standards at least in terms of transmission quality.
Transportation Information Center Emergency Management Center road weather advisories Low High Moderate
Typically intended for public distribution. Road weather advisory information may be used as part of routing decisions; any corruption of or delay in acquiring this information may lead to suboptimal routing or related decisions, which have a direct impact on safety. HIGH for areas with severe weather consequence. May lower to MODERATE for areas with less severe weather. Road weather advisory information may be used as part of emergency routing decisions; any corruption of or delay in acquiring this information may lead to suboptimal routing or related decisions, which have a direct impact on safety.
Weather Service System Emergency Management Center weather information Low Moderate Moderate
Typically intended for public distribution. While there are many sources of weather information, some guarantee of correctness is justifiable to keep confidence in provided service. Even for areas with significant weather events that drive emergency activities, it would be difficult to justify HIGH for this flow. While the repurcussions of inaccurate data may be significant, they are probably not catastrophic. The Emergency Management Center relies on weather data for planning and decision making, so this flow needs to be reliable. In areas with flash-weather issues, this might be HIGH.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems Traffic Management Center