5.1.1.3: Collect Incident And Event Data

This process shall enable existing emergency centers to receive the calls, determine response requirements (enough to determine what responding agencies to notify), and route distress calls to those predesignated responding agencies. This process shall provide the identified emergency information in a standard format as required. This process receives emergency requests from the general public, public safety agencies, alerts and advisories, and other service providers (e.g. a Mayday service provider). Every set of emergency data received shall be assigned a level of confidence by the process depending on its source, so that the subsequent processes can assess the level of response to be provided. This process shall include verification, in that it shall determine if a number of inputs might all be referring to the same incident, then designate that incident in its notifications to the most appropriate responding agencies. By reconciling numerous reports and other collaborative information from the field (e.g. CCTV images, reports from field staff), the verification function confirms the existence, location, and nature of a reported emergency.

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

This process is associated with the following functional objects:

• Emergency Call-Taking
• Emergency Early Warning System
• Emergency Incident Command
• Emergency Response Management

This process is associated with the following data flows:

• alerts_and_advisories_for_incident_detection
• feps-planned_event_data
• fets-caller_information
• fets-incident_information
• fws-current_weather_observations
• fws-weather_forecasts
• incident_alert_details
• incident_and_event_data
• incident_info_for_emerg
• mayday_emergency_data
• silent_and_audible_alarm_data
• tevp-planned_event_confirmation
• transit_emergency_data
• transit_incident_details