1. TSM&O Performance Measures Plan Traffic Incident Management and Program Management Stakeholder Meeting #2 July 2016

2. 2 Agenda Welcome Back & Meeting Objectives Meeting #1 Recap Draft Performance Measures & Implementation Group Discussion Wrap-Up

3. Meeting Objectives Recap Meeting #1 Confirm TSMO metrics Discuss Implementation  Useful to Your Job? Identify outstanding items to address in plan 3

4. Meeting #1 Recap 4

5. 5 Dispatch Dispatch Time T3 – T1 Time between the first recordable awareness of the incident by a responsible agency and the time the agencies resources are dispatched. Adapted from Figure 4: http://www.ops.fhwa.dot.gov/publications/fhwahop15007/chapter1.htm On-Scene Time

6. TIM – National Metrics Identified 4 National TIM Metrics – 2006 FHWA Focus State Initiative & 2011 NCHRP 20-24(37)D – Roadway Clearance Time (RCT) First report to restoration of all traffic lanes – Incident Clearance Time (ICT) First report to last responder departure from scene – Secondary Crashes Either direction, cont. by primary crash – Arrival Time (2011) First report to first assets on-scene 6 Source: http://ops.fhwa.dot.gov/publications/fhwahop10010/presentation.htm Source: http://onlinepubs.trb.org/onlinepubs/nchrp/docs/NCHRP20-24(37)D_FR.pdf

7. TOC Group Discussion - Meeting #1 7 Work load – How do you quantify “busy”? – How do you project staffing needs? – Scheduling Quality assurance – SOG compliance Assets – What is the work load priority and “injured reserve” list? – Location and status

8. TOC Group Discussion - Meeting #1 Work LoadQuality AssuranceAssets Weather/Special eventsImpact within 10 minutes by incident typeWorkload priority report Day of week Notification/page withing specified time limit by incident type Downtime by device and device priority HolidayKey event timelinePortable device locations Phone calls/radio transmissionsUpdates from other agenciesTraffic signal status (recall) Incident volume by TOD/DOW Timer notifications and usage rates (by call type) Equipment on "injured reserve" list Actions by TOD/DOW (all systems, not just TOC) Time between construction project status updates Repeat service request on same device Filter by weather event characteristics (ex. Duration, severity) Traveler info updates by incident type and severity Workload activity threshold triggerDevice activation Statewide staffing needs projectionIncidents without notifications Maintenance crew schedulesExternally-generated incidents without action Key construction project milestones and schedulesTime in pending status Overload notifications by TOC White Board Discussion 8

9. 9 Group Discussion/Feedback Is the measure clear & understandable? Does ODOT have the needed data? How will the perf. meas. be actionable? Are perf. meas. missing from the list? Implementation? How would you prioritize them?

10. OR

11. Traffic Incident Management 11

12. 12

13. Current Reports Event-scale 13

14. Current Reports 14 Unit-scale District-scale State-scale

15. Metric Category: Incident Timeline 15 Proposed Metrics From TIM Strategic PlanImportance Data easily available? (data sources) detection timeyeslow NO (OnStar) verification timeyeshigh YES (CCTV, CAD) dispatch time (shown in TOC metrics as well) yeshigh YES (CAD, 911) response time (various TIM disciplines) yesmedium-high YES (ODOT and OSP data) roadway clearance timeyeshigh YES (incident report) incident clearance timeyeshigh PARTIAL (incident report)

16. Current Statewide Roadway Clearance Report for Lane Blocking Crashes on OSP Patrolled Routes 16

17. 17

18. 18

19. Refining the Roadway Clearance Measure Urban (OSP is not primary coverage/inside city limits) vs. Rural (OSP is primary coverage/outside city limits) Incident classification – Fatal – Intermediate Injury, HazMat, Motor Carrier – Minor All others Future: By Resource Proximity – County / Fire District 19

20. Draft Refined Roadway Clearance Analysis 20 MUTCD Temp Traffic Control (6I.01) Major = 2+ hours Intermediate = 30 min. – 2 hrs. Minor = >30 min.

21. 21

22. 22

23. 23

24. Metric Category: 2 nd Order Incident Metrics 24 Proposed Metrics From TIM Strategic PlanImportance Data easily available? (data sources) roadway closure durationyeshigh YES (incident report) % of crash incidents meeting goal for roadway clearance time nohigh YES (incident report) roadway clearance time mediannohigh YES (incident report)

25. Metric Category: Incident Status – Tow Related 25 Proposed Metrics From TIM Strategic PlanImportance Data easily available? (data sources) tow arrival timenohighNO time tow was callednohighNO length of time to complete tow tasks nohighNO % of incidents where tow companies arrive without correct equipment yeslowNO

26. Incident TIM staffing/resource attributes 911-ODOT Dispatch Integration (OIS) to help with event reconciliation (TOCS v. Crash Analysis Unit). 26 Proposed Metrics From TIM Strategic PlanImportance Data easily available? (data sources) locationnomedium YES (incident report) incident densitynomedium YES (incident report) incident typenomedium YES (incident report)

27. 27

28. WAZE and HERE Data as Secondary Crash Tools 28

29. ADOT Secondary Crash Example Source: http://nchrptimpm.timnetwork.org/?page_id=73 29

30. TraCS Example from FDOT 30 Same software used by ADOT and others Source: Guidance for Implementation of Traffic Incident Management Performance Measurement Website (http://nchrptimpm.timnetwork.org/?page_id=47)

31. Metric Category: Secondary Crashes 31 Proposed Metrics From TIM Strategic PlanImportance Data easily available? (data sources) secondary crash = within the queue of the existing incident yeshigh NO (only in text) Ratio of secondary crashes to primary crashes nolow NO (only in text)

32. Metric Category: Incident Responder Risk 32 Proposed Metrics From TIM Strategic PlanImportance Data easily available? (data source) average time on scene per incident type nohigh PARTIAL (ODOT and OSP data) incident responder struck-bys yesmedium-highNO incident responder fatalities yesmedium-highNO On-Scene Time

33. Metric Category: Staff Training 33 Proposed Metrics From TIM Strategic PlanImportance Data easily available? (data source) number of responders trained in National TIM training classes yeshighNO number of responders trained in specific discipline nohighNO

34. TOC Operations 34

35. Current Reports Actions/dispatcher 35

36. Metric Category: Efficiency/Scheduling of Staff Time 36 Proposed MetricsImportance Data easily available? (data source) TOC total workload by hour of day and day of week high PARTIAL (TOCS, Pantel) Employee total workload by hour of day and day of week or month (seasonality) high PARTIAL (TOCS, Pantel)

37. Metric Category: Dispatch time ODOT-only resources vs. all events (911 Dispatch) 37 Proposed MetricsImportance Data easily available? (data source) dispatch timehigh YES (TOCS)

38. Current Reports 38

39. Current Reports 39

40. Metric Category: SOG Compliance/QA 40 Proposed MetricsImportance Data easily available? (data source) lane blocking crashes with no ATISmedium YES (TOCS) average time to notificationmedium YES (TOCS) ATIS posting in less than 10 minutesmedium YES (TOCS) events with no notificationmedium YES (TOCS) timer usage by dispatcher (timeline reporting)medium PARTIAL (TOCS) traveler info updatesmedium-high YES (TOCS)

41. 41 Group Discussion/Feedback Is the measure clear & understandable? Does ODOT have the needed data? How will the perf. meas. be actionable? Are perf. meas. missing from the list? Implementation? How would you prioritize them?

42. Meeting #1 / #2 Action Items Send ideas or comments on PMs to Chris Use the forum tab on the project website for discussions – http://sites.kittelson.com/TSMOPM/Forums http://sites.kittelson.com/TSMOPM/Forums TIM – Report back to respective groups; gather feedback – InView / perf. meas. Feedback Program Management – ODOT to continue to share new/custom reports with other districts 42

43. TSMO Performance Measures Plan Wrap Up Recap Discussion – Consensus items – Please contact Chris with any additional thoughts/questions/comments that come up 43

44. Thank you. 44

45. Lit Review Recommendations Outcomes drive perf. meas. Keep it simple Useful for wide audiences Well-defined metrics Data quality Data fusion and automation 45

46. Metric Statistical Considerations Mean v. Median  distinguish outliers Percentile Results – 5 th v. 95 th Standard Deviation – range of results Sample Size  normalize data sets Data bias 46

47. Draft Refined Roadway Clearance Analysis 47

48. Performance Measure Development Decision matrix 48

49. Decision Matrix Columns 49 Metric category Proposed metric Existing? Data source requirements Issues addressed, sensitivity trying to capture Importance Data easily available? TIM also includes: – From TIM Strategic Plan – Strategic Plan Timeframe

50. Metric Category: TIM/Traveler Info 50 Proposed MetricsImportance Data easily available? (data source) traveler info updatesmedium-high YES (TOCS)

51. Mock Asset Management Summary Report Consensus on… – Metrics? – Prioritization? – Implementation? – Desired Outcomes? – Will you use it? 51