Office of Operations
21st Century Operations Using 21st Century Technologies

Making the Business Case for Traffic Incident Management

Foreword

Notice

This document is disseminated under the sponsorship of the U.S. Department of Transportation in the interest of information exchange. The U.S. Government assumes no liability for the use of the information contained in this document. This report does not constitute a standard, specification, or regulation.

The U.S. Government does not endorse products or manufacturers. Trademarks or manufacturers' names may appear in this report only because they are considered essential to the objective of the document.

Quality Assurance Statement

The Federal Highway Administration (FHWA) provides high-quality information to serve Government, industry, and the public in a manner that promotes public understanding. Standards and policies are used to ensure and maximize the quality, objectivity, utility, and integrity of its information. FHWA periodically reviews quality issues and adjusts its programs and processes for continuous quality improvement.

Technical Report Documentation Page

1. Report No.

FHWA-HOP-16-084

2. Government Accession No.

3. Recipient's Catalog No.

4. Title and Subtitle

Making the Business Case for Traffic Incident Management

5. Report Date

December 2016

6. Performing Organization Code

7. Author(s)

Kelley Klaver Pecheux, Ph.D.; Vaishali Shah; Cara O'Donnell

8. Performing Organization Report No.

9. Performing Organization Name and Address

AEM Corporation
13880 Dulles Corner Ln, Suite 300
Herndon, VA 20171

Under contract with Cambridge Systematics, Inc.

10. Work Unit No. (TRAIS)

11. Contract or Grant No.

DTFH61-12-D-00036

12. Sponsoring Agency Name and Address

Federal Highway Administration
U.S. Department of Transportation
Office of Operations
1200 New Jersey Avenue, SE
Washington, DC 20590

13. Type of Report and Period Covered

Final Report

14. Sponsoring Agency Code

HOP

15. Supplementary Notes

Ms. Laurel Radow, Federal Highway Administration, Office of Operations, Technical Point of Contact

16. Abstract

In order to transform a traffic incident management (TIM) program or project from a stand-alone effort to a sustainable core function of an agency, the establishment of a solid business case is necessary. The purpose of this document is to support TIM agencies and partner agencies in the development of a strong business case for their TIM programs, as well as to introduce strategies that link investments with program results and, ultimately, with the strategic outcomes of the broader organization. This document is designed to be used throughout the entire lifecycle of an investment to ensure meaningful discussion between program managers and the approval or funding authority from the earliest possible time.

The document is organized around four primary chapters that correspond to the four phases of the TIM business case development process. Each of these four chapters begins by listing the essential elements to be developed for the TIM business case product and/or activities to be conducted within that stage of the process. Then, within the chapter, these elements/activities are described in more detail, and examples are presented to provide context. Each chapter concludes with a checklist of the important questions that should be answered by the end of each phase. The checklists are shaped such that once the questions in each chapter are answered and the phases are complete, the information needed to populate a full business case report template should be available.

17. Key Words

Traffic incident management. Business case. Financial resources. Funding sources. Strategic planning. Options analysis.

18. Distribution Statement

No restrictions

19. Security Classif. (of this report)

Unclassified

20. Security Classif. (of this page)

Unclassified

21. No of Pages

92

22. Price

N/A

Form DOT F 1700.7 (8-72) Reproduction of completed pages authorized

SI (Modern Metric) Conversion Factors

Approximate Conversions to SI Units
Symbol When You Know Multiply By To Find Symbol
Length
in inches 25.4 millimeters mm
ft feet 0.305 meters m
yd yards 0.914 meters m
mi miles 1.61 kilometers km
Area
in2 square inches 645.2 square millimeters mm2
ft2 square feet 0.093 square meters m2
yd2 square yard 0.836 square meters m2
ac acres 0.405 hectares ha
mi2 square miles 2.59 square kilometers km2
Volume
fl oz fluid ounces 29.57 milliliters mL
gal gallons 3.785 liters L
ft3 cubic feet 0.028 cubic meters m3
yd3 cubic yards 0.765 cubic meters m3
NOTE: volumes greater than 1000 L shall be shown in m3
Mass
oz ounces 28.35 grams g
lb pounds 0.454 kilograms kg
T short tons (2000 lb) 0.907 megagrams (or "metric ton") Mg (or "t")
Temperature (exact degrees)
°F Fahrenheit 5 (F-32)/9 or (F-32)/1.8 Celsius °C
Illumination
fc foot-candles 10.76 lux lx
fl foot-Lamberts 3.426 candela/m2 cd/m2
Force and Pressure or Stress
lbf poundforce 4.45 newtons N
lbf/in2 poundforce per square inch 6.89 kilopascals kPa
Approximate Conversions from SI Units
Symbol When You Know Multiply By To Find Symbol
Length
mm millimeters 0.039 inches in
m meters 3.28 feet ft
m meters 1.09 yards yd
km kilometers 0.621 miles mi
Area
mm2 square millimeters 0.0016 square inches in2
m2 square meters 10.764 square feet ft2
m2 square meters 1.195 square yards yd2
ha hectares 2.47 acres ac
km2 square kilometers 0.386 square miles mi2
Volume
mL milliliters 0.034 fluid ounces fl oz
L liters 0.264 gallons gal
m3 cubic meters 35.314 cubic feet ft3
m3 cubic meters 1.307 cubic yards yd3
Mass
g grams 0.035 ounces oz
kg kilograms 2.202 pounds lb
Mg (or "t") megagrams (or "metric ton") 1.103 short tons (2000 lb) T
Temperature (exact degrees)
°C Celsius 1.8C+32 Fahrenheit °F
Illumination
lx lux 0.0929 foot-candles fc
cd/m2 candela/m2 0.2919 foot-Lamberts fl
Force and Pressure or Stress
N newtons 02.225 poundforce lbf
kPa kilopascals 0.145 poundforce per square inch lbf/in2

Note: SI is the symbol for the International System of Units. Appropriate rounding should be made to comply with Section 4 of ASTM E380. (Revised March 2003)

Office of Operations