A variety of techniques have been developed to manage incidents efficiently. However, very little guidance exists for agencies wishing to initiate such efforts. This document serves to provide this guidance by discussing the process of developing and implementing an incident management system. Generally, the process consists of seven steps: defining the problem, setting goals and objectives, developing alternatives, evaluating and selecting from those alternatives, implementing, re-evaluating after a specified time, and refining the system. The alternatives which were developed in this document fall under five basic categories depending on how they benefit incident management efforts. These categories include incident detection, response, site management, clearance, and motorist information. Specific information, including technique description, relative costs and benefits, operational requirements, and funding variations, is given for each incident management technique included in these categories. More generally, concerns such as jurisdictional issues, geographical constraints, available resources, operational procedures, training requirements, and administrative coordination are discussed in detail to aid in mitigating difficulties early in the incident management system development process.
June 30, 2007
Fred L. Mannering, Mark Hallenbeck, Jodi Koehne.
Washington State Transportation Center (TRAC)
- # of Pages: 300 p., 11,388 KB (PDF)
- Subject: Benefits, Costs, Detectors, Development, Driver information systems, Finance, Financing, Guides to information, Implementation, Incident management, Location, Management, Traffic incidents.
- Keywords: Incident management, incident detection, incident response, site management, incident clearance, motorist information.
- Related Publications: Incident Management Systems Framework: Impacts of Service Patrols, (WA-RD 221.1).
Development of Incident Management Systems: The Seattle Case Study, (WA-RD 221.2).
A Framework for Developing Incident Management Systems: A Summary, (WA-RD 224.2).
This abstract was last modified April 29, 2008