Traffic Incident Management PERFORMANCE METRIC ADOPTION CAMPAIGN. ITS Texas Annual Meeting November 10-12, 2010

Size: px

Start display at page:

Download "Traffic Incident Management PERFORMANCE METRIC ADOPTION CAMPAIGN. ITS Texas Annual Meeting November 10-12, 2010"

Magnus Elliott
8 years ago
Views:

1 Traffic Incident Management PERFORMANCE METRIC ADOPTION CAMPAIGN ITS Texas Annual Meeting November 10-12, 2010

2 BACKGROUND National Unified Goal (NUG) for TIM Strategy 3. Goals for Performance and Progress TIM partners should work together to establish and implement performance goals at the state, regional and local levels for increasing the effectiveness of TIM including methods for measuring and monitoring progress.

establish and implement performance goals at the state, regional and local

3 BACKGROUND Focus States Initiative: TIM Performance Measures Initiated by FHWA in states, including Texas 50 law enforcement and transportation practitioners 10 candidate TIM objectives 30 related performance measures Not everything that can be counted counts, and not everything that counts can be counted.

practitioners 10 candidate TIM objectives 30 related performance measures Not

4 BACKGROUND Focus States Initiative: TIM Performance Measures Recommended Performance Measures Roadway Clearance Time (11) Incident Clearance Time (11) Secondary Incidents (1) Incident Notification Time (1) Incident Recovery Time (1) Incident Response Time (2) Stakeholder Familiarity (3) Responder Communications (1) Traveler Information (2) Customer Feedback (0)

Incident Notification Time (1) Incident Recovery Time (1) Incident Response Time (2)

5 BACKGROUND Reduce Roadway Clearance Time Time between first recordable awareness and confirmation that all lanes are available for traffic flow. Reduce Incident Clearance Time Time between first recordable awareness and time at which the last responder has left the scene. Reduce Secondary Incidents Number of unplanned incidents (a) within the incident scene or (b) within the queue, including the opposite direction, resulting from the original incident.

Reduce Incident Clearance Time Time between first recordable awareness and time at which the last responder has

6 BACKGROUND TIM Performance Measurement Knowledgebase owledgebase/ TIM Performance Measurement LISTSERV and enter SUBSCRIBE in the subject line TIM Performance Metric Adoption Campaign

gov/eto_tim_pse/preparedness/tim/kn owledgebase/ TIM Performance

7 OBJECTIVES To determine: TIM-specific metrics collected in 40 metropolitan areas Existing definitions of secondary incident Consistency with FHWA definitions To establish national baseline for: Roadway clearance time Incident clearance time Secondary incidents To recommend methods for maintaining/expanding

definitions To establish national baseline for: Roadway clearance time

8 PRELIMINARY APPROACH Inventory TIM Performance Measurement Practices Site visits (20 metropolitan areas) Remote surveys (20 metropolitan areas) Information sought Metrics in use Data collection, processing, sharing, reporting and use Limited data sample Differences between observed and recommended metrics

Information sought Metrics in use Data collection, processing, sharing,

9 PRELIMINARY APPROACH Conduct Secondary Incident Study Site visit methods (6 states) Information sought Existing definitions Data collection, processing, sharing, reporting and use Frequency, severity, types, and causal factors Monitoring in Operations TIM-specific PM Initiatives Conduct of Special Studies FLORIDA MARYLAND MINNESOTA CAD-ATMS Integration ARIZONA UTAH WASHINGTON

use Frequency, severity, types, and causal factors Monitoring in Operations TIM-specific PM

10 PRELIMINARY FINDINGS General Observations TIM performance measurement increases with top down focus Current metrics focused on activities not outcomes Data sets often limited to: Distinct TIM programs Hours of agency operation Major incidents Few areas using FHWA s standard TIM metrics but potential exists to begin using

often limited to: Distinct TIM programs Hours of agency operation Major

11 PRELIMINARY FINDINGS Roadway Clearance Time First recordable awareness Most accurate from dispatcher logs and CAD/911 systems Most accessible from TMC operator logs and ATMS systems System integration can ensure common awareness times Challenged by multiple CAD/911 systems and jurisdictions All lanes available Recorded in-field and/or remotely (TMC operator/dispatcher) Check box or open-field formats Not routinely or consistently recorded Often motivated by Open Roads policies Reduce Roadway Clearance Time Time between first recordable awareness of incident by a responsible agency and first confirmation that all lanes are available for traffic flow.

and/or remotely (TMC operator/dispatcher) Check box or open-field formats Not routinely or consistently recorded Often motivated by Open Roads policies Reduce

12 PRELIMINARY FINDINGS Incident Clearance Time First recordable awareness Ditto Reduce Incident Clearance Time Time between first recordable awareness of incident by a responsible agency and time at which the last responder has left the scene. Last responder to leave scene Transportation (may not respond to every incident) Law enforcement (may include off-site reporting time) Towing and recovery Queue dissipation

13 PRELIMINARY FINDINGS Secondary Incidents Post-incident data analysis Percent of total incidents Pre-defined temporal/spatial thresholds Real-time ATMS data determining extent of queue at time of incident Reduce Secondary Incidents Number of unplanned incidents beginning with the time of detection of the primary incident where a collision occurs either (a) within the incident scene or (b) within the queue, including the opposite direction, resulting from the original incident. Ongoing operations Recorded in-field and/or remotely Check box or open-field formats Not routinely or consistently recorded Limited by lack of definition and responder/operator/ dispatcher training

collision occurs either (a) within the incident scene or (b) within the queue, including the opposite direction, resulting from the original incident.

14 PRELIMINARY FINDINGS Data Collection TRANSPORTATION TMC operator logs ATMS/automated sensors FSP on-scene reports LAW ENFORCEMENT Dispatcher logs CAD/911 systems Officer on-scene reports Data systems differ in purpose Transportation agency systems support access to and analysis of aggregate data Law enforcement agency systems provide careful documentation of singular events Data systems in state of change

systems differ in purpose Transportation agency systems support access to and analysis of aggregate

15 PRELIMINARY FINDINGS Data Processing Infrequent annual or on demand data processing Data Sharing Between: Different offices, regions, or TMCs within a single law enforcement or transportation agency Law enforcement and transportation agencies Transportation agencies and universities Law enforcement/transportation agencies and various public access portals (511 system websites) Challenged by inconsistent definitions, format, quality

and transportation agencies Transportation agencies and universities Law enforcement/transportation agencies

16 PRELIMINARY FINDINGS Data Reporting and Use PURPOSE Internal performance reporting Operational refinement or contract management/oversight Funding requests External reporting RECIPIENT Agency administration Operations level managers Agency administration/elected officials Elected officials/public APPLICATIONS REPORT FREQUENCIES AGGREGATION Operations Higher Lower Administrative Lower Higher

administration Operations level managers Agency administration/elected officials Elected

17 PRELIMINARY FINDINGS Data Reporting and Use Challenging improved TIM operations, reports may: be difficult or time consuming to produce not be in an actionable format not be well understood by recipients at all levels TIM performance measurement benefits include: reduced clearance times (Fort Lauderdale, FL, Norfolk, VA) adoption of quick clearance polices and pending legislation (Minneapolis, MN) justification for FSP program expansion (Tampa, FL) improved regional coordination (Norfolk, VA)

benefits include: reduced clearance times (Fort Lauderdale, FL, Norfolk, VA) adoption of quick clearance polices and pending

18 PRELIMINARY FINDINGS Recommendations Enhance understanding of Roadway vs. Incident Clearance Detail secondary incident definition Types of events that constitute a secondary incident Temporal and spatial parameters to describe extent of primary incident influence Use transportation data to quick-start implementation of TIM performance metrics Account for potential lack of comprehension Investigate extent of lag notification times and missing data Transition to a more accurate, comprehensive data source

spatial parameters to describe extent of primary incident influence Use transportation data to quick-start implementation of

19 NEXT STEPS Early 2011 Conduct web conference Performance measurement best practices Secondary incident study results Develop and populate database Develop database design/structure Populate with data from 40 metropolitan areas Recommend database maintenance/expansion FHWA s TIM Self Assessment or other

Develop database design/structure Populate with data from 40 metropolitan

20 QUESTIONS

Traffic Incident Management Where are we focused? Captain Mike Prochko Arizona Department of Public Safety Highway Patrol Division mprochko@azdps.

Traffic Incident Management Where are we focused? Captain Mike Prochko Arizona Department of Public Safety Highway Patrol Division mprochko@azdps.gov Notable issues in AzDPS past Major Incidents generating