Lesson

Solicit executive support for an incident management program, but rely on staff-level champions and administrative support for day-to-day guidance of the program.

Major metropolitan areas' experiences with formalized incident management programs.


5/1/2001
Atlanta,Georgia,United States; Houston,Texas,United States; Seattle,Washington,United States; Milwaukee,Wisconsin,United States; Chicago,Illinois,United States; Los Angeles,California,United States; San Francisco,California,United States; Detroit,Michigan,United States; San Antonio,Texas,United States; Maryland,United States


Background (Show)

Lesson Learned

While no single approach can be prescribed for all incident management efforts, a flexible framework based on experiences from successful incident management programs in the United States can be considered a highly effective approach to building a successful program. Today's best incident programs have developed from small beginnings under the leadership of self-styled champions (from one or two agencies) who have rallied the support of their peers in partner agencies. The following lessons are based on the experience of other ITS professionals regarding the importance of having both executive level support as well as staff-level and administrative support for building a successful incident management program.
  • Involve the right people as stakeholder representatives. Key program committees will need to have someone attend from each key stakeholder group who has adequate authority to speak for his/her organization. These representatives should also have the ear of the senior executives at their organizations. It is important to also involve middle and working level people in the organizations who can serve as organizational champions for incident management. It can be detrimental to depend exclusively on the participation of very senior people, as they will often not have the time to meet on a regular basis.
  • Commit to administrative support of an ongoing inter-organizational structure, and communication and decision-making events and meetings. Any undertaking as complex as an incident management program requires some level of administrative support, and a regular forum (or forums) at which performance is reviewed, issues are raised, information is shared, and program change and evolution are discussed and approved. An incident management program will require this type of support and activity in order to function effectively. It is important, however, to arrive at a level of activity acceptable to all partners, some of whom may have difficulty justifying extended absences from the workplace to attend meetings. This is particularly true if the program has a steering committee composed of senior executives from participating organizations. Obtaining a significant commitment of time from such officials is often difficult or impossible. To increase productivity, a much better plan is to ask for a realistic time commitment and to carry out a larger portion of the work in subordinate committees.

Involving mid-level personnel that can commit to regularly meeting on key program committees and obtaining administrative support of the inter-organizational program can help the success of an interagency incident management program. This lesson portrays the idea that involving the right people as stakeholder representatives and committing the required administrative support to the inter-organizational structure can lead to increased program productivity.


Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

Regional Traffic Incident Management Programs: Implementation Guide

Author: Vincent Pearce

Published By: U.S. Department of Transportation, FHWA ITS Joint Program Office, Federal Transit Administration

Source Date: 5/1/2001

EDL Number: 13149

Other Reference Number: FHWA-OP-01-002/FTA-TRI-11-00-03

URL: http://ntl.bts.gov/lib/jpodocs/repts_te/13149.pdf

Other Lessons From this Source

Lesson Contacts


Agency Contact(s):

David Helman
FHWA
202-366-8042
David.Helman@fhwa.dot.gov

Lesson Analyst:

Jane Lappin
Volpe National Transportation Systems Center
617-494-3692
jane.lappin@volpe.dot.gov


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Application Areas

None defined

Countries

United States

Systems Engineering

Show the V

None defined

Focus Areas

None defined

Goal Areas

Productivity

Keywords

None defined

Lesson ID: 2006-00180