5.1 - Provide Emergency Service Allocation DFD

This DFD shows the processes that make up the Provide Emergency Services Allocation facility within the Manage Emergency Services function. These processes receive reported incident data and initiate the appropriate response. They also detect and verify emergencies and threats and provide traveler and remote area security.

The key points about the facility are as follows:

Facilities are provided to identify the type of emergency dependent on source;
Response plan is determined from allocation criteria and sent to the vehicle dispatch function;
Emergency services status reporting facility is provided for other ITS functions;
Emergencies and threats are detected and verified from video/audio surveillance and from sensors in the roadway, in the transportation infrastructure, or on a transit vehicle;
Traveler and remote area security is managed and coordinated between processes in this DFD and other areas of the architecture, such as Manage Traffic, Manage Transit, and Manage Emergencies.

There are eight processes in this DFD, and two are also DFDs:
a) Detect and Verify Emergencies (DFD 5.1.1)
b) Determine Coordinated Response Plan (5.1.2)
c) Communicate Emergency Status (5.1.3)
d) Manage Emergency Response (5.1.4)
e) Manage Emergency Service Allocation Store (5.1.5)
f) Process Mayday Messages (5.1.6)
g) Provide Traveler and Remote Area Security (DFD 5.1.7)
h) Manage Wide Area Alerts And Advisories (5.1.8)

The data about incidents is received by process (a) which formats it and passes it to process (b). In the event that the incident has been declared a disaster, threat, or major emergency, this process recognizes that additional coordination between multiple agencies may be required which is beyond normal incident response. In this event, data is passed on to the Manage Disaster Response and Evacuation Function (DFD 5.7) for the additional coordination and management needs. Process (b) requests the appropriate response data from the store of predefined responses through process (e). The response is loaded into a coordination plan which is sent to processes (c) and (d). Process (c) sends data acknowledging the receipt of the incident data back to the source of the data and also provides access to the log of incident responses maintained by process (d). This process manages the response to the incident, sending data to the dispatch vehicles facility and obtaining data about hazardous cargoes when commercial vehicles are involved. Process (g) manages traveler and remote area security from video/audio surveillance and from sensors in the roadway, in the transportation infrastructure, or on a transit vehicle. This data is sent to processes in DFD 5.1.1 to determine if a threat exists, then to DFD 5.7 to coordinate the response to a threat or disaster.

These processes are intended to work as a coordinated group in a single implementation. If necessary some of the sources of emergency data for process (a) can be omitted if they do not exist in some implementations.

DFD: 5.1 - Provide Emergency Service Allocation

Parent DFD: 5 - Manage Emergency Services

Child DFDs:

PSpecs in this DFD: