EM02-Emergency Routing (Market Package*)

Market Package Graphic       Transaction Set Diagram

Description

This market package supports automated vehicle location and dynamic routing of emergency vehicles. Traffic information, road conditions, and suggested routing information are provided to enhance emergency vehicle routing. Special priority or other specific emergency traffic control strategies can be coordinated to improve the safety and time-efficiency of responding vehicle travel on the selected route(s). The Emergency Management Subsystem provides the routing for the emergency fleet based on real-time conditions and has the option of requesting a route from the Traffic Management subsystem. The Emergency Vehicle may also be equipped with dedicated short range communications for local signal preemption and the transmission of alerts to surrounding vehicles. The service provides for information exchange between care facilities and both the Emergency Management Subsystem and emergency vehicles.

Includes Equipment Packages and Subsystems:

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Care Facility care facility status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Care Facility care facility status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Vehicle Subsystem Yes
Emergency Management care facility status request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Care Facility Yes
Emergency Management emergency operations status Emergency System Operator Yes
Emergency Management suggested route Emergency Vehicle Subsystem Yes
Emergency Management map update request Map Update Provider Yes
Emergency Management emergency route request Traffic Management Yes
Emergency Management emergency traffic control request 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 Subsystem Yes
Emergency System Operator emergency operations inputs Emergency Management Yes
Emergency Vehicle Subsystem care facility status request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Care Facility Yes
Emergency Vehicle Subsystem patient status Care Facility Yes
Emergency Vehicle Subsystem emergency vehicle tracking data Emergency Management Yes
Emergency Vehicle Subsystem emergency personnel information presentation Emergency Personnel Yes
Emergency Vehicle Subsystem local signal preemption request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Subsystem Yes
Emergency Vehicle Subsystem emergency vehicle alert Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Vehicle Yes
Location Data Source position fix Emergency Vehicle Subsystem No
Maintenance and Construction Management current asset restrictions Emergency Management Yes
Maintenance and Construction Management roadway maintenance status Emergency Management Yes
Maintenance and Construction Management work zone information Emergency Management Yes
Map Update Provider map updates Emergency Management Yes
Roadway Subsystem request for right-of-way Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Roadway Subsystem signal control status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Traffic Management emergency routes Emergency Management Yes
Traffic Management emergency traffic control information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management signal control data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Subsystem 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.

Early Deployment

This market package has been identified as an early deployment due to a promising combination of low risk implementation characteristics, developing public or private markets for the package, and tangible system or user benefits. An area of active private sector interest and public sector procurement, this Market Package leverages the same vehicle location, wide area digital communications, dispatch support, and in-vehicle interactive interface technologies that are instrumental to the related commercial and transit fleet support Market Packages. New standards are not required to support basic implementations. Progressive implementations which address more extensive inter-agency coordination in routing may be added as new standards become available and are adopted for the implementing region.

ITS Goals Supported

    ITS Goal Satisfaction Level
    Increase Transportation System Efficiency and Capacity *
    Improve Safety * * *
    Reduce Energy Consumption and Environmental Costs *
    Increase Economic Productivity * *
    Create an Environment for an ITS Market *
    * Features that marginally satisfy the goals
    * * Features that almost satisfy every aspect of the goals
    * * * Features completely satisfy every aspect of the goals

User Services related to this Market Package:

Problem / Solution Pairs this Market Package Addresses


Hypertext Architecture Version 6.1 generated on 1/7/2009 from the following databases
Physical Architecture dated 12/15/2008,
Logical Architecture dated 12/2/2008,
Market Packages dated 12/14/2008,
Security dated 11/13/2008,
User Services dated 4/9/2007,
Theory of Operations dated 12/14/2008,
AppMap dated 12/19/2008 and the
SDOMAP dated 12/12/2008