T3 Webinar Files

Guidance Tool for Implementation of Traffic Incident Management Performance Measures (NCHRP 07-20)
(December 16, 2014)

Guidance for Implementation of TIM Performance Measurement

Presenter:   Kelley Klaver Pecheux
Presenter's Org:   Applied Engineering Management Corporation (AEM)

HTML version of the presentation
Image descriptions are contained in brackets. [ ]
Back to Webinar Files

T3 Webinars are brought to you by the Intelligent Transportation Systems (ITS) Professional Capacity Building Program (PCB) of the U.S. Department of Transportation's (U.S. DOT) ITS Joint Program Office (JPO). References in this webinar to any specific commercial products, processes, or services, or the use of any trade, firm, or corporation name is for the information and convenience of the public, and does not constitute endorsement, recommendation, or favoring by the U.S. DOT.


Slide 1:  Guidance for Implementation of TIM Performance Measurement

Kelley Klaver Pecheux, PhD

U.S. Department of Transportation
T3 Webinar Program
December 16, 2014

[This slide contains the Applied Engineering Management Corporation (AEM) logo.]

Slide 2:  Overview of Presentation

Slide 3:  Project Background

Slide 4:  Research Approach

Slide 5:  Research Products

[This slide contains two logos: the TIM Network logo and the TIMPM (Performance Measurement) logo: Guidance for Implementation of Traffic Incident Management Performance Measurement.]

Slide 6:  Overview of Guidance

Slide 7:  General Guidance on TIM Performance Measurement - Content Overview

Slide 8:  TIM Performance Measures

[This slide contains a photograph showing traffic being diverted to the right lane of a three-lane roadway: orange traffic cones and pickup trucks carrying traffic redirect signage (arows pointing to the right).]

Slide 9:  Incident Timeline

Guidance presents and explains the incident timeline and the associated time-based TIM performance measures.

[This slide contains a graphic of an incident timeline marked with incident benchmarks that are used to define how the time-based TIM performance measures are determined. The performance measurements are listed and described in the table in the following slide. These measurements, in both slides, use the timeline benchmarks listed below.]

Slide 10:  TIM PM Definitions and Calculations

Measure Calculation Definition
Detection Time T1 – T0 Time between the incident occurring and the incident being reported. Detection time is not typically reported due to the fact that the actual time the incident occurred is often unknown.
Verification Time T2 – T1 Time between incident being reported and the incident being verified. TMCs can typically assist with verification through the use of their CCTV cameras.
Response Time T4 – T2 Time between the incident being verified and the first responder arriving on the scene. Law enforcement may not always be the first to arrive on the scene.
Roadway Clearance Time (RCT) T5 – T1 Time between the first recordable awareness of the incident by a responsible agency and the first confirmation that all lanes are available for traffic flow.
Incident Clearance Time (ICT) T6 – T1 Time between the first recordable awareness of the incident by a responsible agency and the time at which the last responder has left the scene.
Time to Return to Normal Flow T7 – T0 Time between the incident occurring and the traffic has returned to normal flow after all clearance activities are complete.

Slide 11:  3 National TIM Performance Measures and Current Practices

Guidance provides definitions and current practices regarding the 3 national TIM performance measures.

Slide 12:  Data Sources for TIM PMs

[This slide contains charts that show the TIM performance measurement inputs for: (1) TMC (operators and CCTV), (2) FSP (operators, CCTV, and freeway service patrols), and (3) Law Enforcement (operators, CCTV, and law enforcement).]

Slide 13:  FAST Incident Input Screen

Collecting data for 2 of the national TIM performance measures.

[This slide contains a screenshot of the FAST “Add New Incident” input form, with two input elements circled in red: the “Lane cleared” dropdown and the “Secondary” checkbox.]

Slide 14:  Florida Highway Patrol Electronic Crash Form

Collecting data for all 3 national TIM performance measures.

[This slide contains a screenshot of a Florida Highway Patrol Electronic Crash Form displaying the input fields of the “Crash Identities & Roadway” tab, with the following input elements circled in red: “Reported to Agency Date/Time,” “Roadway Cleared Date/Time,” “Cleared Scene Date/Time,” and “Crash Sequence Order.”]

Slide 15:  Data Mining, Reporting, and Visualization Example Practices

Slide 16:  FDOT D4 Weekly Incident Duration Report

Performance measures summary, including RCT and ICT for current week, previous week, and 52-week average.

Average open roads duration.

[This slide contains a screenshot of a Weekly Incident Duration Performance Measures Report for Florida DOT's district 4. The report features a Performance Measures Summary table (TIM measurements for the current week, the previous week, and the 52-week average), an Incident Duration Summary horizontal bar graph (displaying the table data), and two vertical bar graphs: Open Roads Duration/Week, and Roadway Clearance Duration/Week.]

Slide 17:  FDOT D4 Real-Time Display of TIM PMs

Current district wide average RCT.

Compare current RCT to RCT at the same time the previous year.

Track status in each county (number of current minor, intermediate, and major incidents; average RCT for each type of incident).

[This slide contains a photograph of an FDOT D4 real-time display of TIM PMs within an FDOT TMC. Dozens of desktop monitors on numerous workstations display CCTV feeds. A large wall, just beyond the monitors, displays a grid of larger CCTV feeds, data, maps, and graphics.]

Slide 18:  VDOT Dashboard

Percentage/ number of incidents by incident duration.

Searchable by district, incident severity, incident type, and date.

[This slide contains a screenshot of VDOT's Highway Performance - Incident Duration webpage, which has four elements: (1) a menu to customize the data displayed (type of measure, district, severity, incident type, and data range); (2) text that describes the measure and how to use the menu fields to customize the measure data display; (3) a pie chart of the data (in this measure: the percentage of incidents that are less than 30 minutes, between 30 and 60 minutes, between 60 and 90 minutes, and greater than 90 minutes); and (4) a line graph of the data.]

Slide 19:  VDOT Hampton Roads Quarterly Report

[This slide contains two images from VDOT's Hampton Roads Quarterly Report: (1) a line graph plotting three measures (Safety Service Patrol (SSP) Response Time, Incident Clear Time, and Verification to Clear Time) for the months of July through December of 2012. The graph shows that the Verification to Clear Time goal of an average of 26 minutes was not met in any of the six months (32.5 minutes to 30.0 minutes); and (2) a “Fourth Quarter Event Clearance” distribution curve that plotting the percentage of incidents cleared within different time durations. Included is the following data: Of the 18,424 events logged by the Hampton Roads Transportation Operations Center in the fourth quarter of 2012, 92% (16,905 events) were cleared within 90 minutes of verification. Of the approximately 1,500 events that lasted more than 90 minutes, the top event types were: Roadwork (41%), Choke Point (29%), and Accidents (8%). At ten minutes, 44% of total events or 8,107 events were cleared in the fourth quarter of 2012. At 30 minutes, 76% of total events or 14,002 events were cleared in the fourth quarter of 2012.]

Slide 20:  FAST Archived CCTV Incident Snap Shots

Review snap shots to obtain details about incidents.

Helps generate 30-60-90 calculations (of roadway clearance times) for Nevada DOT.

[This slide contains a screenshot of the FAST Archived CCTV Incident Snap Shot website showing a detailed table of incidents and a grid of snapshot animations from CCTVs from 2:40 P.M. to 3:50 P.M. on August 4, 2014.]

Slide 21:  UMD CATT Lab Incident Timeline

Combined timeline showing TMC communications, notifications and responders, lane status, and overhead sign messages.

[This slide contains four parallel incident timelines for I-95 North past MD 32 from 12:33:11 P.M. to 2:43:18 P.M. on May 17, 2010. The four timelines display TMC communications, notifications and responders, lane status, and overhead sign messages.]

Slide 22:  UMD CATT Impact of Incident - Heat Map

[This slide contains a color-coded heat map showing an incident's traffic speed impact severity and duration upstream of that incident.]

Slide 23:  Model TIM Performance Measurement Database - Content Overview

Slide 24:  Data Elements and Database Schema

[This slide contains a database schema, which includes elements associated with incident timeline, conditions, and severity; roadway and location of incident; lanes involved; vehicles involved; participants involved; emergency responders involved.]

Slide 25:  Populating the Database

Guidance includes a simple example incident data entry screen for use with the model TIM PM database.

Guidance also includes a discussion on importing existing datasets into the database.

[This slide contains a screenshot of an example of a “New Incident” data entry form for use with the model TIM PM database.]

Slide 26:  Querying the Database - SQL

Slide 27:  Analysis of Performance Using the Database

Performance Measures:

Slide 28:  Example Applications of the Model Database

Slide 29:  Demonstration of Online Tool

timnetwork.org

Slide 30:  For Further Information

AEM Corporation
Kelley Klaver Pecheux
Associate Director of Transportation
kelley.pecheux@aemcorp.com
(703) 464-7030 ext 8117

Texas A&M Transportation Institute
Robert Brydia
Research Scientist
r-brydia@tamu.edu
(979) 845-8140

TRB
Ray Derr
Senior Program Officer
rderr@nas.edu
(202) 334-3231

FHWA Office of Operations
Paul Jodoin
Traffic Incident Management Program Manager
paul.jodoin@dot.gov
(202) 366-5465

Back to Top