5.1.6: Process Mayday Messages

This process shall receive mayday messages from vehicles and drivers, or via personal handheld devices, determine whether the mayday message indicates an emergency that requires the attention of public safety agencies, and forward mayday emergency data to the appropriate agency when assistance is required. The content of the data flow 'mayday emergency data' shall include all the key data from the incoming data flow 'emergency request details' and an agency ID indicating the mayday provider that received and processed the mayday message. While not depicted in the logical architecture, the process will also be heavily dependent on voice communications to better ascertain the nature and severity of the emergency and to report this information to the appropriate local agency. This process shall also receive and keep a historical log of signals sent in the mayday vehicle tracking data store.

This process is associated with the Emergency Management Center physical object.

This process is associated with the following functional objects:

• Emergency Notification Support

This process is associated with the following data flows:

• driver_status_update
• emergency_data_request
• emergency_notification_relay_from_vehicle
• emergency_request_driver_acknowledge
• emergency_request_driver_details
• emergency_request_personal_traveler_acknowledge
• emergency_request_personal_traveler_details
• emergency_request_vehicle_acknowledge
• emergency_request_vehicle_details
• foem-mayday_emergency_data
• mayday_emergency_data
• mayday_request_to_operator
• mayday_response_from_operator
• toem-mayday_emergency_data
• vehicle_security_system_commands
• vehicle_security_system_commands_request
• vehicle_status_update