EM03-Mayday and Alarms Support (Market Package*)

Market Package Graphic       Transaction Set Diagram

Description

This market package allows the user (driver or non-driver) to initiate a request for emergency assistance and enables the Emergency Management Subsystem to locate the user, gather information about the incident, and determine the appropriate response. The request for assistance may be manually initiated or automated and linked to vehicle sensors. This market package also includes general surveillance capabilities that enable the Emergency Management Subsystem to remotely monitor public areas (e.g., rest stops, parking lots) to improve security in these areas. The Emergency Management Subsystem may be operated by the public sector or by a private sector telematics service provider.

Includes Equipment Packages and Subsystems:

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Basic Vehicle basic vehicle measures Vehicle Yes
Driver request for service Vehicle Yes
Emergency Management emergency operations status Emergency System Operator 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 emergency acknowledge Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Personal Information Access Yes
Emergency Management alarm acknowledge Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Remote Traveler Support Yes
Emergency Management secure area surveillance control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Remote Traveler Support Yes
Emergency Management emergency acknowledge Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Vehicle Yes
Emergency Management emergency data request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Vehicle Yes
Emergency System Operator emergency operations inputs Emergency Management Yes
Location Data Source position fix Personal Information Access No
Location Data Source position fix Vehicle No
Personal Information Access emergency notification Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Personal Information Access traveler interface updates Traveler Yes
Remote Traveler Support alarm notification Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Remote Traveler Support secure area surveillance data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Remote Traveler Support traveler interface updates Traveler No
Secure Area Environment secure area characteristics Remote Traveler Support Yes
Traveler traveler inputs Personal Information Access Yes
Traveler traveler inputs Remote Traveler Support No
Vehicle driver updates Driver Yes
Vehicle emergency notification 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.

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. Active private sector deployment of Mayday systems as value-added options on new automobiles highlights the potential for this package as an early deployment. Based on outreach performed through the Architecture program and other industry activity, this appears to be an area of near-term and active development. Early deployments establish interactive, digital communications capabilities in the vehicle which can be leveraged by other Market Packages. National standards may enhance the performance and reliability of the service provided.

Rural Development

For the Traffic Management Rural Development Track, this market package is applicable to a significant number of rural user needs, may require some augmentation for the rural environment. It addresses the needs of the broad rural development track by the following: Allows agencies to automatically know the location of a vehicle calling in an incident, as travelers/users don’t always know where they are. This type of service will further be enhanced as efforts in the E911 community continue.

For the Tourism and Travel Rural Development Track, this market package is applicable to a significant number of rural user needs, may require some augmentation for the rural environment. It addresses the needs of the broad rural development track by the following: Provides the ability to automatically transmit Mayday information from traveler personal device or vehicle. For vehicle crashes, can include vehicle location and extent of crash damage.

For the Emergency Services Rural Development Track, this market package is highly applicable to rural user needs and suitable for the rural environment. It addresses the needs of the broad rural development track by the following: Allows the user of the system (driver or non-driver) to initiate a request for emergency assistance and enables the emergency management center to locate the user and determine the appropriate response.

ITS Goals Supported

    ITS Goal Satisfaction Level
    Improve Safety * * *
    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