TxDOT TRAFFIC INCIDENT MANAGEMENT UPDATE ITS Texas 2016 November 10, 2016 TxDOT- Traffic Operations Division November 10, 2016
Performance Measures (Lonestar ATMS) Lonestar ATMS Upgraded to Support Incident Management Timeline T1, T2, T4, T5, T6, T7 drop down menu based input, configurable by district T3 (and T4 if needed) can be addressed using notes feature TxDOT- Traffic Operations Division November 10, 2016 2
Performance Measures (Lonestar ATMS) TxDOT- Traffic Operations Division November 10, 2016 3
Performance Measures Lonestar ATMS TxDOT- Traffic Operations Division November 10, 2016 4
Session 2- Performance Measures Lonestar ATMS TxDOT- Traffic Operations Division November 10, 2016 5
Session 2- Performance Measures Lonestar ATMS TxDOT- Traffic Operations Division November 10, 2016 6
Performance Measures (Lonestar ATMS) Data Collection Focus Incidents detection source Incident verification type Median incident duration Average delay across segments Travel Time Delay Number of crashes in work zones Lane Clearance Time Incident Clearance Time Number of secondary crashes Percentage of time that standard response plan activated for an event DMS message types (Incident, Travel Time, Construction, PSA, etc.) Travel Time data source (Inrix, Radar, Bluetooth) Time from incident detection to response plan activation % asset uptime % process uptime TxDOT- Traffic Operations Division November 10, 2016 7
Performance Measures (Lonestar ATMS) FHWA definitions of the secondary crashes and the two TIM performance measures that states are asking to be collect- Secondary Crashes The number (or percentage) of crashes beginning with the time of detection of the primary crash, where a crash occurs as a result of the original crash either within the incident scene or within the queue in either direction. Roadway Clearance Time (RCT) 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) 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. TxDOT- Traffic Operations Division November 10, 2016 8
Performance Measures Issues Impacting Performance Measure Data Collection- Staffing levels TMC staffing level is an issue where one or two operators are on duty working multiple incidents, the motivation is to get response plans out and contact emergency responders Austin District in process of privatization of TMC staffing which will increase staff size The National Operations Center of Excellence working with TxDOT is hosting a Virtual Peer Exchange, with multiple DOTs providing background on how current staff sizes were determined, achieved and maintained- (Missouri, Minnesota, Florida, Virginia) Goal is to provide justification for target staffing levels which will ensure maximum return on investment in ITS TxDOT- Traffic Operations Division November 10, 2016 9
Performance Measures Issues Impacting Performance Measure Data Collection- Investigating options for consultant/vendor to collect and process data- Presentations from TTI for Houston RIMS data collection and University of Maryland CATT Lab Training operators in common definitions of Incident Management Timeline measures Educating local partners on PM and KPI availability TxDOT- Traffic Operations Division November 10, 2016 10
Lonestar Event Report Lonestar Event Reports Being upgraded to provide a consistent format for all districts Will support After Action Reviews for Regional Traffic Incident Management Teams Will incorporate FHWA TIM Timeline parameters TxDOT- Traffic Operations Division November 10, 2016 11
Lonestar incident Report- Event Summary TxDOT- Traffic Operations Division November 10, 2016 12
Lonestar incident Report- TIM Timeline TxDOT- Traffic Operations Division November 10, 2016 13
Lonestar incident Report- Operator Notes & Responder Summary EVENT REPORT - FTW10062016_0001 Notes Time Public/Private Operator Notes 18:31 Service patrol reported injury requested EMS 18:32 HAZ Mat Spill reported 18:33 FWFD initiated evacuation protocol for 1 mile radius 18:35 Notifed PIO, DTO 18:38 EVENT FTW10062016_0001 Responder on Scene Time on Scene Agency Notes 18:31 Service Patrol 18:32 FWPD 18:33 TxDOT Maint 18:35 FWFD 18:38 ME TxDOT- Traffic Operations Division November 10, 2016 14
Lonestar incident Report- Email Notification Summary EVENT FTW10062016_0001 EMAIL Notification History Time Update Incident Geographic Number Severity Impact Email Message Text 18:31 1 Level 1 Local FTW10062016_0001 Minor Accident IH-820NL EASTBOUND AT BUS-287 / SAGINAW MAIN, LEFT LANE CLOSED IH-820NL WESTBOUND AT BUS- 287 / SAGINAW MAIN 18:32 2 Level 2 County FTW10062016_0001 Minor Accident IH-820NL EASTBOUND AT BUS-287 / SAGINAW MAIN, all lanes closed for Lifeflight 18:33 3 Level 3 District FTW10062016_0001 Major Accident IH-820NL EASTBOUND AT BUS-287 / SAGINAW MAIN, All lanes closed due to HAZ MAT Spill Recipients Fort Worth Level 1 notification Group Fort Worth Level 2 notification Group Fort Worth Level 3 notification Group 18:35 3 Level 4 District and HQ FTW10062016_0001 Major Accident IH-820NL EASTBOUND AT BUS-287 / SAGINAW MAIN, All lanes closed due to HAZ MAT Spill, evacuation underway 18:38 4 Closed FTW10062016_0001 Major Accident IH-820NL EASTBOUND AT BUS-287 / SAGINAW MAIN, Incident Cleared Fort Worth Level 4 notification Group Fort Worth Level 4 notification Group Automated email escalation/notification feature being added Email contact list will be expanded based on incident parameters (severity/duration/estimated duration/location/etc.) Parameters configurable by districts TxDOT- Traffic Operations Division November 10, 2016 15
Lonestar incident Report- Event History EVENT HISTORY FTW10062016_0001 Action Occurred User Description Detected 10/6/2016 18:29 jzeank:isd-750742-l:1220 Lane Data Entered 10/6/2016 18:29 jzeank:isd-750742-l:1220 Lane data has been entered: Roadway type: Freeway, Lanes: Lane: 0 - Type: Shoulder - Status: Blocked,Lane: 1 - Type: Main Lane - Status: Cleared,Lane: 2 - Type: Main Lane - Status: Cleared,Lane: 3 - Type: Main Lane - Status: Cleared,Lane: 4 - Type: Shoulder - Status: Cleared Detected By Changed 10/6/2016 18:29 jzeank:isd-750742-l:1220 Detected By Changed 10/6/2016 6:29 PM jzeank:isd-750742-l:1220 Event detected by initialized to 'CCTV Camera' Verified By Changed 10/6/2016 18:29 jzeank:isd-750742-l:1220 Event verified by initialized to 'CCTV Camera' Response Plan Activated 10/6/2016 6:31 PM jzeank:isd-750742-l:1220 Response Plan Activated 10/6/2016 6:31 PM jzeank:isd-750742-l:1220 Activating response plan from template IH-820NL E @ BUS-287 LEFT Message Queued 10/6/2016 6:31 PM jzeank:isd-750742-l:1220 Message '[fo2][jl3][pt31o0]ih-820nl EASTBOUND[nl]AT BUS-287 / SAGINAW MAIN[nl]LEFT LANE CLOSED[np]IH-820NL WESTBOUND[nl]AT BUS-287 / SAGINAW MAIN[nl]INCIDENT' on Dms I820.Marine Creek.NB:dms:dms:FTW was queued Response Plan Set 10/6/2016 18:31 jzeank:isd-750742-l:1220 Setting response plan from plan template IH-820NL E @ BUS-287 LEFT Message Displayed 10/6/2016 18:31 jzeank:isd-750742-l:1220 Message Displayed 10/6/2016 6:31 PM jzeank:isd-750742-l:1220 Message '[fo2][jl3][pt31o0]ih-820nl EASTBOUND[nl]AT BUS-287 / SAGINAW MAIN[nl]LEFT LANE CLOSED[np]IH-820NL WESTBOUND[nl]AT BUS-287 / SAGINAW MAIN[nl]INCIDENT' on Dms I820.Marine Creek.NB:dms:dms:FTW was successfully posted Verified 10/6/2016 18:31 jzeank:isd-750742-l:1220 Event state has been set to Verified Scene Cleared 10/6/2016 18:38 jzeank:isd-750742-l:1220 Event state has been set to Scene Cleared Closed 10/6/2016 18:38 jzeank:isd-750742-l:1220 Event state has been set to Closed Response Plan Deactivated 10/6/2016 18:38 jzeank:isd-750742-l:1220 Deactivating response plan from template IH-820NL E @ BUS-287 LEFT Message Removed 10/6/2016 18:39 jzeank:isd-750742-l:1220 Message '[fo2][jl3][pt31o0]ih-820nl EASTBOUND[nl]AT BUS-287 / SAGINAW MAIN[nl]LEFT LANE CLOSED[np]IH-820NL WESTBOUND[nl]AT BUS-287 / SAGINAW MAIN[nl]INCIDENT' on Dms I820.Marine Creek.NB:dms:dms:FTW was successfully removed TxDOT- Traffic Operations Division November 10, 2016 16
Traffic Incident Management Plan Development DISTRICT TIM SURVEY Survey to determine the state of the TIM Plans and Planning efforts underway in each district. TIM BEST PRACTICES Develop a set of suggested high level TIM practices and policies which could be used in all districts to reduce delays due to traffic blockages and incidents. STANDARD OPERATING PROCEDURES Working with reps from the metro districts, developing set of Standard Operating Procedures for TxDOT TMCs TxDOT- Traffic Operations Division November 10, 2016 17
Traffic Incident Management Plan Development WORK ZONE ITS STANDARDS Identify statewide standards and standard practices to be applied to all work zones TIM TRAINING Provide National Incident Management System / Strategic Highway Research Program 2 (NIMS) / (SHRP 2) training to the appropriate personnel involved with responses in Texas Austin District TIM planning Develop Joint Operating Policy Statement use by the Austin District in Regional TIM Coordination TxDOT- Traffic Operations Division November 10, 2016 18
TxDOT Traffic Incident Management Update Questions? Brian Fariello, P.E. Traffic Management Section Director, Traffic Operations Division Texas Department of Transportation brian.fariello@txdot.gov TxDOT- Traffic Operations Division November 10, 2016 19