1.3.3.1: Respond to Current Incidents

This process shall provide responses, including roadside advisories, signal timing strategy changes, and notification of other agencies (Emergency Management, Maintenance and Construction, and Border Inspection Systems), to incidents that become current, i.e. active. Four general strategies for response to incidents can be supported by the process in conjunction with the Manage Incident Response Planning process: 1) Operator enters a response (there is no set of predetermined responses), 2) the operator selects a response from a set of predetermined responses (possibly modifying the response), 3) the process automatically accesses and implements a response from a set of predetermined responses (while informing the operator of the actions taken), and 4) the process receives a signal to activate an evacuation plan.
The process shall output the predetermined responses to an incident when it receives notification from another process in the Manage Incidents function that a new current incident has occurred. At the same time it shall also output the incident data to the process responsible for providing broadcast data to roadside processes (e.g., DMS/HAR) and to the Manage Maintenance and Construction process for coordination with its activities. The other process in the Manage Incidents function shall also provide details of incidents that have ceased to be current (terminated) so that this process can send out data to clear the actions requested and broadcast such information to the roadside. This process shall provide the Manage Emergency Services function with updates to the responses to the current traffic incidents, including any changes to traffic control strategies (e.g., signal timing plans, ramp metering, interchange control, lane control), commercial vehicle restrictions, HRI overrides, or evacuation procedures.

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

This process is associated with the following functional objects:

This process is associated with the following data flows: