Oregon DOT ITS & Systems Operations: Performance Measures ...
Oregon DOT ITS & Systems Operations: Performance Measures & Program Overview
Chris Wright, GISP Traveler Information & Operations Performance Measures Coordinator
Western States Regional Operations Peer Exchange: Performance Management 11/16/2015
Presentation Outline • • • • •
Collaboration Data Performance Measures TSM&O Performance Measure Plan Q&A
Performance Measures/Indicators Team • Cross-functional team • Knowledge sharing • Outcome, not output, focused • Think tank for: – New data & analysis procedures – Technology validation (internal tools vs. external)
Data: Internal • Traffic Operations Center (TOC): Incidents – Responded to 106,344 events in ’14 – Average 11% in events recorded over past 3 years
• Micromain: ITS roadside devices – 463 cameras – 108 RWIS – 259 VMS
• Mobility: Data imported every 15 minutes – Calculated 95th (peak travel time), 15th (free flow)
Data: External • INRIX: – 1 Minute intervals. – Last data upload from April ’14. – Aggregated speeds
• HERE: – 5 minutes via NPMRDS. – Truck, auto, combo speed.
• Waze: – Data sharing agreement – User submitted incident and traffic data – Use in TripCheck and modeling
Data Warehouse & Analytics Tools
Key Performance Measure: Percent of lane blocking crashes cleared within 90 minutes
Program Level Performance Measures • QBR: Four unique measures submitted to Highway management team – – – –
ATIS Duration Roadway Clearance Highway Closure Duration TripCheck visits
Roadway Clearance Duration 2014 Duration, Incident Count, Percentage 91-120 Minutes 375, 6%
121-150 Minutes 188, 3%
>150 Minutes 519, 9%
1-15 Minutes 1635, 28% 61-90 Minutes 807, 14%
16-30 Minutes 923, 16% 31-60 Minutes 1362, 23%
13
Causes Impacting >90 minute lane clearing - 2014
Urban vs. Rural
• 1st plan of its type for ODOT • Cross functional and multi-discipline • Timing aligns with other agency efforts • Topic Areas: TIM, System Management, Program Management
What are other DOTs doing in the following areas? • Data quality measures for Part 511 (23 CFR 511): Real-Time System Management Information Program • Asset management for Operations & ITS • Secondary incident definition & reporting • Reporting architecture: Internal vs. External
Causes of crashes over 90 minutes •
Extended Recovery
•
Specialized Recovery Equipment
•
Investigation
•
Emergency Vehicle(s) Obstruction
•
Lack of Field Communication
•
Law Enforcement Response Time
•
Necessary Repairs
•
ODOT Response Time
•
Debris Removal •
Hazmat Response Time
•
Tow Response Time
•
Delayed Data Entry
•
Data Entry Error
•
Hazmat Cleanup
•
Tow Request Time
•
Delayed Notification From Others
•
Medical Examiner Response Time
•
Dispatch Delay
•
Utility Company Response Time
BREAKDOWN BY MONTH
% Crashes/Fatal Per District - 2014
ODOT & OSP working together • ODOT – OSP Mutual Assistance Agreement – clear all lanes impacted during a crash in 90 minutes or less.
Chris Wright, GISP Traveler Information & Operations Performance Measures Coordinator
Western States Regional Operations Peer Exchange: Performance Management 11/16/2015
Presentation Outline • • • • •
Collaboration Data Performance Measures TSM&O Performance Measure Plan Q&A
Performance Measures/Indicators Team • Cross-functional team • Knowledge sharing • Outcome, not output, focused • Think tank for: – New data & analysis procedures – Technology validation (internal tools vs. external)
Data: Internal • Traffic Operations Center (TOC): Incidents – Responded to 106,344 events in ’14 – Average 11% in events recorded over past 3 years
• Micromain: ITS roadside devices – 463 cameras – 108 RWIS – 259 VMS
• Mobility: Data imported every 15 minutes – Calculated 95th (peak travel time), 15th (free flow)
Data: External • INRIX: – 1 Minute intervals. – Last data upload from April ’14. – Aggregated speeds
• HERE: – 5 minutes via NPMRDS. – Truck, auto, combo speed.
• Waze: – Data sharing agreement – User submitted incident and traffic data – Use in TripCheck and modeling
Data Warehouse & Analytics Tools
Key Performance Measure: Percent of lane blocking crashes cleared within 90 minutes
Program Level Performance Measures • QBR: Four unique measures submitted to Highway management team – – – –
ATIS Duration Roadway Clearance Highway Closure Duration TripCheck visits
Roadway Clearance Duration 2014 Duration, Incident Count, Percentage 91-120 Minutes 375, 6%
121-150 Minutes 188, 3%
>150 Minutes 519, 9%
1-15 Minutes 1635, 28% 61-90 Minutes 807, 14%
16-30 Minutes 923, 16% 31-60 Minutes 1362, 23%
13
Causes Impacting >90 minute lane clearing - 2014
Urban vs. Rural
• 1st plan of its type for ODOT • Cross functional and multi-discipline • Timing aligns with other agency efforts • Topic Areas: TIM, System Management, Program Management
What are other DOTs doing in the following areas? • Data quality measures for Part 511 (23 CFR 511): Real-Time System Management Information Program • Asset management for Operations & ITS • Secondary incident definition & reporting • Reporting architecture: Internal vs. External
Causes of crashes over 90 minutes •
Extended Recovery
•
Specialized Recovery Equipment
•
Investigation
•
Emergency Vehicle(s) Obstruction
•
Lack of Field Communication
•
Law Enforcement Response Time
•
Necessary Repairs
•
ODOT Response Time
•
Debris Removal •
Hazmat Response Time
•
Tow Response Time
•
Delayed Data Entry
•
Data Entry Error
•
Hazmat Cleanup
•
Tow Request Time
•
Delayed Notification From Others
•
Medical Examiner Response Time
•
Dispatch Delay
•
Utility Company Response Time
BREAKDOWN BY MONTH
% Crashes/Fatal Per District - 2014
ODOT & OSP working together • ODOT – OSP Mutual Assistance Agreement – clear all lanes impacted during a crash in 90 minutes or less.
