NDOT Statewide Integrated Transportation Reliability Program ______

______NDOT Statewide Integrated Transportation Reliability Program ______

DRAFT Technical Memorandum No. 6 – Performance Measurement Plan

Prepared by:

October, 2009 092202013

1. OVERVIEW OF PERFORMANCE MEASUREMENT PLAN ...... 1 1.1 What is Performance Measurement and Why Use it? ...... 1 1.2 How Performance Measurement is Used in Other States ...... 2 1.3 How Can Performance Monitoring Benefit NDOT and its Partners? ...... 4 1.4 How is Transportation Performance Currently Being Monitored? ...... 4 1.5 What is the Best Way to Measure Reliability in Nevada? ...... 5 1.6 How Do Performance Measures Relate to ITRP Strategies?...... 10

2. OUTCOME-BASED PERFORMANCE MEASURES ...... 11

3. ACTIVITY-BASED PERFORMANCE MEASURES ...... 23

4. PERFORMANCE MEASUREMENT REPORTING ...... 33 1.1 Overview of the Process and Progress ...... 33 1.2 Performance Scorecard ...... 33 1.3 Performance Measure Summaries ...... 33

APPENDIX A – LITERATURE REVIEW ...... 39

APPENDIX B – PERFORMANCE MEASUREMENT PLAN DEVELOPMENT ...... 43 B.1 Initial Development and Refinement of Performance Measures ...... 43

APPENDIX C – EXISTING PERFORMANCE MONITORING ...... 45 C.1 Performance Monitoring Per Assembly Bill 595 ...... 45 C.2 FAST Performance Measures...... 46 C.3 Planned ITS Improvements ...... 46 C.4 FAST Performance Measures...... 48

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc DRAFT Performance Measurement Plan i 10/09 TABLE OF CONTENTS DRAFT – PERFORMANCE MEASUREMENT PLAN

LIST OF FIGURES

Figure 1 – UDOT Assessment of Freeway Commute Speeds Over Time ...... 3 Figure 2 – NDOT ITRP Performance Measures Categories ...... 7 Figure 3 – Outcome-Based Performance Measures ...... 8 Figure 4 – Activity-Based Performance Measures ...... 9 Figure 6 – Example Overview Section of Performance Measurement Report ...... 35 Figure C.1 – FAST Freeway Network ...... 47

LIST OF TABLES

Table 1 – WSDOT Before and After Analysis of Congestion Relief Projects ...... 2 Table 2 – WSDOT Before and After Analysis of Collision Rates after Cable Barrier Installation ...... 3 Table 3 – Relationship of Performance Measures and Strategies ...... 10 Table 4 – Example of a Performance Measurement Scorecard ...... 36 Table A.1 – Documents Reviewed ...... 39

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc DRAFT Performance Measurement Plan ii 10/09 1. OVERVIEW OF PERFORMANCE MEASUREMENT PLAN The goal of the Nevada Statewide Integrated Transportation Reliability Program (ITRP) is to identify regional and statewide strategies to improve the reliability of travel. A key element of this project is the development of a performance measurement plan to evaluate transportation system operation conditions and to quantify the level of congestion on the system. This document provides an overview of how performance measurement can benefit the Nevada Department of Transportation (NDOT) and its partners to support ITRP and reliability focused planning.

1.1 What is Performance Measurement and Why Use it? Performance measurement is the collection, analysis, and reporting of data to track and assess resources used, work produced and whether specific goals are achieved. An important aspect of performance measurement is an analysis of why goals are (or are not) being achieved, and accomplishments to meet goals. Performance measurement is a tool that provides both the public and public agency staff with a way to assess what improvements are working, how the transportation system is operating, and how funding can be used most efficiently to improve the transportation system. Performance measurement provides benefits as shown below.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 1 10/09 1.2 How Performance Measurement is Used in Other States Many Federal, State and local agencies are using performance measurements to assess progress in meeting goals. Appendix A provides a summary of literature that was reviewed to assess best practices in performance measurement. More and more states are using performance measures to demonstrate to the public that wise investments are being made in their transportation systems, and to assess the effectiveness of transportation improvements. Some examples of how performance measurement has improved operations and reliability are provided below. Technical Memorandum Number 3, Best Practices Reference Guide, also provides additional examples, particularly in the area of travel time reliability measures. Washington Department of Transportation: Washington State Department of Transportation (WSDOT) produces a “Gray Notebook” on a quarterly basis, which provides in-depth reports on agency and transportation system performance. The purpose of the Gray Notebook is to keep WSDOT accountable to the Governor, the Legislature, Washington State citizens, and transportation organizations. The Gray Notebook is organized into five sections devoted to those strategic goals, each marked by a page that recaps WSDOT’s goals for Safety, Preservation, Mobility/Congestion Relief, Environment, and Stewardship. Although The Gray Notebook is WSDOT’s main performance reporting tool, there are many other related accountability and performance products available through the WSDOT website. Performance measurement was used to demonstrate the effectiveness of congestion relief projects. Table 1 shows how speeds were increased and travel times reduced as a results of road widening projects.

Table 1 – WSDOT Before and After Analysis of Congestion Relief Projects

Source: Washington State Department of Transportation, Delivering Safety and Congestion Relief on State Highways, Oct 2008 Performance measurement showed how crash rates were reduced by installing safety improvements such as cable median barriers and centerline rumble strips. These projects showed measureable safety benefits. Table 2 shows an excerpt of this analysis for an assessment of cable barrier installations.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 2 10/09 Table 2 – WSDOT Before and After Analysis of Collision Rates after Cable Barrier Installation

Source: Washington State Department of Transportation, Delivering Safety and Congestion Relief on State Highways, Oct 2008 Utah Department of Transportation: The Utah Department of Transportation focuses on four main strategic goals which are: Take Care of What We Have - Focusing on keeping the transportation system in good condition, so its serviceable life can be maximized. Make the System Work Better - Managing traffic congestion and optimizing performance by incorporating new technologies, strategies and design features. Improve Safety - Reducing the number of traffic-related fatalities on state roads to zero. Increase Capacity - Implementing capacity improvement projects. Performance measures are summarized in an annual document. The current document is entitled “2009 Strategic Direction and Performance Measures.” An example of how performance measurement is used is shown in Figure 1, which shows how average freeway commute speeds from downtown Salt Lake City were reduced as a result of road improvements. The graphic shows that measurable improvements in travel speeds occurred.

Source: 2009 Strategic Direction and Performance Measures, UDOT Figure 1 – UDOT Assessment of Freeway Commute Speeds Over Time

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 3 10/09 1.3 How Can Performance Monitoring Benefit NDOT and its Partners? Performance measurements are a way to ensure that Nevada transportation system’s investments are protected and that the operation of the transportation system is optimized to the greatest extent possible. In particular, performance measures can target ways to assess reliability in the transportation system, particularly non-recurring congestion due to incidents, work zones, and other related causes. Performance monitoring can benefit NDOT and its partners in the following ways: It shows the effects of construction projects and ITS improvements on travel time, speeds, and delays, thus quantifying the project benefits It shows how strategies related to traffic incident management can reduce crashes It provides data to prioritize projects in a number of ways, such as demonstrating which roadways have the highest level of delays (and thus the greatest needs), and which strategies are most effective in helping traffic congestion and improving safety. It shows how strategies on traffic incident management and work zones can help to reduce non-recurring congestion It shows how expanded communication strategies can help drivers to better plan their trips to avoid delays

1.4 How is Transportation Performance Currently Being Monitored? Transportation system performance monitoring in Nevada is currently accomplished in a number of ways: NDOT conducts performance monitoring to conform to the requirements of Assembly Bill 595, which mandates performance monitoring requirements. Key performance measures (relating to reliability) include: o Percentage of daily vehicle miles traveled that occur at Level of Service E or worse on the state system; and o Number of fatalities on Nevada’s streets and highways Performance monitoring that is under development by the Freeway and Arterial System of Transportation (FAST), an operational division within the RTC of Southern Nevada. FAST is a unique operations entity in that it manages and controls both the freeway and arterial networks from the FAST Traffic Management Center (TMC). Appendix C further describes these performance monitoring efforts. A brief overview of transportation data that is currently available for performance monitoring is: Travel Time Data – FAST is currently able to collect volume, speed and occupancy data along the following freeway segments, which are instrumented: I-15 from Lake Mead to the 215 Beltway US-95/I-515 from Craig Road to Charleston

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 4 10/09 FAST is also able to collect volume, speed and occupancy data at ramp meter locations. In addition, FAST is currently able to collect volume, speed and occupancy data along one arterial roadway, Craig Road from US-95 to Las Vegas Boulevard. FAST has been doing their own travel time runs on arterials to help validate some of the coordination and timing strategies. They have about 1,800 runs in their database. According to the FAST 2010 – 2011 FMS Scope of Services FAST will conduct travel time studies, and develop speed profiles for eight roadway segments during AM and PM peak periods. The road segments are located on I-15, I-515, and US 95. FAST also has conducted before and after travel time studies for signal retiming projects (this is on a project by project basis). Traffic Count Data - NDOT maintains a traffic count program. Reports are published annually. NDOT also has a TRaffic INformation Access (TRINA) web-based GIS application that provides maps and reports of traffic count and classification data. Speed Monitoring – NDOT conducted an annual speed monitoring program through 2004 at 29 locations. The results were published annually. Signal Timing Data - FAST has created a regional signal synchronization network that currently has approximately 1,120 signals, with an average of 3-5 new signals being added to the network every month. FAST has established communications and implemented signal coordination plans at approximately 600-700 of those signals. All arterial and signal information is run by the I2TMS software. A potential project in the implementation plan is to determine if this software is currently able to collect data. Crash Database - Law enforcement and other agencies contribute state-wide traffic data to the Nevada Citation and Accident Tracking System known as NCATS. NCATS is hosted by the Nevada Department of Public Safety Records and Technology Division and supplies traffic crash data to agencies through Nevada Department of Transportation Safety Engineering. NDOT publishes a Nevada Traffic Crashes Report (there is a 2-3 year delay on these reports). 511 System – The number of calls made to the 511 system and website statistics are available. Dynamic Message Signs – FAST can collect the sign data (messages) that have been displayed on DMS and trailblazers. It is assumed that data is available on the number of DMS signs statewide. Vehicle Miles of Travel – NDOT maintains an annual Vehicle Miles of Travel Report

1.5 What is the Best Way to Measure Reliability in Nevada? A key objective of this project is to provide NDOT with a system of performance measures that provide a meaningful way to improve operations, better inform planning and programming, and track progress in providing a more reliable transportation system. The focus was to identify performance measures that will enhance reliability as well as measure progress addressing gaps in each region. Two main categories of performance measures were identified, outcome based performance measures and activity–based performance measures, shown in Figure 2. Outcome-based performance measures provide policy makers, elected officials, and the public with information regarding the reliability of roadways in Nevada. These measures tell us how the system is operating and describe the ‘state of the roadway system’. These

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 5 10/09 reliability measures include average travel times and delays on selected corridors. Each of these performance measures are described in Figure 3, which provides an overview of the performance measure, what it will accomplish, where (in general) it would be measured, and what the general goal of the performance measure would be. Activity based performance measures are designed for use by NDOT staff responsible for operating and maintaining the state roadway system. These are measures of activities performed by NDOT transportation professionals that indirectly improve the reliability of the transportation system. These measures are described in Figure 4, which, similar to Figure 3, provides an overview of the performance measure, what it will accomplish, where (in general) it would be measured, and what the general goal of the performance measure would be.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 6 10/09 Figure 2 – NDOT ITRP Performance Measures Categories

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 7 10/09 Figure 3 – Outcome-Based Performance Measures

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 8 10/09 Figure 4 – Activity-Based Performance Measures

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 9 10/09 1.6 How Do Performance Measures Relate to ITRP Strategies? Performance measures for the NDOT Statewide Integrated Transportation Reliability Program were developed with the main focus of improving the reliability of travel. While reliability is most directly affected by non-recurring sources of congestion, such as an incident or construction related lane closures, recurring congestion was also examined as part of the ITRP process. Performance measures were developed in coordination with implementation strategies in order to more fully address reliability issues. Table 3 shows the relationship between recommended performance measures and the categories of strategies that were defined in Technical Memorandum #5 - Short and Long Range Strategies. As can be seen from Table 3, outcome- based performance measures primarily address infrastructure and work zone management areas. Activity–based performance measures primarily address the areas of traveler information, incident and work zone management.

Table 3 – Relationship of Performance Measures and Strategies

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 10 10/09 2. OUTCOME-BASED PERFORMANCE MEASURES Section 1 provided an overview of the two types of performance measures recommended, outcome – based and performance based performance measures. This chapter discusses outcome-based performance measures in more detail. Outcome-based performance measures are designed to provide policy makers, elected officials, and the public with information regarding the reliability of roadways in Nevada. These measures will describe the ‘state of the roadway system’ and will include reliability measures such as average travel times and delay on selected corridors. These measures assess the quality of travel on specific travel facilities and are geographically focused. Each outcome-based performance measure is summarized in the following forms which provide more detail on how each performance measure can be applied to the Nevada road system. These forms include an example of how the performance measures could be presented, and provides the following data:

General Information Performance Measurement Number, Title and Category Performance Measure Description Target Goal Value of the Performance Measure Supports Strategy or Strategies Performance Measurement Plan Data to be collected Frequency of data collection Data collection location Data analysis technique Database management requirements Performance analysis reporting period Data Collection roles and responsibilities (lead agency and partner agencies) Phasing of performance monitoring measure

The descriptions refer to the four geographic regions defined for this study, which are: Region 1 – Las Vegas Metropolitan Area Region 2 – Reno/Sparks/Carson City/Lake Tahoe Area Region 3 – I-80 Corridor Area Region 4 – Rural Corridors Area, and Region 5 – Statewide.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 11 10/09 Performance Measure ID#: OB-1 Performance Measurement Category: Outcome - Based Title: 95% Reliable Travel Time – Peak Periods Performance Measure Description: 95% reliable travel time on selected state highways segments. The 95% reliable travel time performance measure is the amount of time necessary to make it to a destination 19 out of 20 work days. The 95th percentile reliable travel time can be described as "the worst traffic day of the month". Target Goal: A 5% decrease in the 95% reliable travel times on a year to year basis. Value of Performance Measure: Better than a simple average, travelers can depend on this travel time estimate as a reasonable estimate of how bad delay will be on the heaviest travel days. Supports Strategy or Strategies: SN-4: Corridor System Management Plan SN-6, NN-5: Test Adaptive Traffic Signal Control (ATCS) SN-9: Enhance ADUS Software and Reporting of Real-Time Data SN-10: Expand Travel Time Program to Southern Nevada Freeway System Performance Measurement Plan Data to Be Collected x Travel times on route segments – these can be developed by: 1. Directly calculated from continuous probe vehicle data; 2. Estimated from continuous point-based detector data; 3. Collected in periodic special studies (e.g., floating car runs); and 4. Estimated using computer simulation, sketch planning, or demand forecasting models.

Source: State of Washington, Office of Financial Management – Statewide Mobility (http://www.ofm.wa.gov/budget/pog/indicators/mobility/mobility_01a.asp)

Frequency of Data Collection x Annual Data Collection Location (s) x Focus on I-15, I-515/US-93/95, and the 215 Beltway as initial corridors for expanding the travel time program

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 12 10/09 Performance Measure ID#: OB-1 Performance Measurement Category: Outcome - Based Data Analysis Technique x Travel time runs, data from vehicles equipped with Automated Vehicle Identification (AVI ) Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x FAST x NDOT x Clark County (Bruce Woodbury Beltway) x McCarran International Airport (for access to/from 215 via airport tunnel)

x Private sector data companies (such as Traffic.com or INRIX) Phasing of Performance Monitoring Measure x Evaluate the use of private company data collection information to calculate travel times for traveler information purposes (website, DMS, radio/television, other media) x Expand to the Reno/Northern Nevada region when Northern Nevada TMC is established. Focus on key congested road state segments in the Reno and Sparks area x Eventually expand to I-80, selected rural corridor segments, and a limited number of the highest volume routes

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 13 10/09 Performance Measure ID#: OB-2 Performance Measurement Category: Outcome - Based Title: Buffer Index – Peak Periods Performance Measure Description: The buffer index represents the extra buffer time (or time cushion) that most travelers add to their average travel time when planning trips to ensure on-time arrival. This extra time is added to account for any unexpected delay. Target Goal: A decrease in the buffer index on a year to year basis. Value of Performance Measure: Better than a simple average, travelers can depend on this travel time estimate as a reasonable estimate of how bad delay will be on the heaviest travel days. Supports Strategy or Strategies: SN-4: Corridor System Management Plan SN-6, NN-5: Test Adaptive Traffic Signal Control (ATCS) SN-9: Enhance ADUS Software and Reporting of Real-Time Data SN-10: Expand Travel Time Program to Southern Nevada Freeway System Performance Measurement Plan Data to Be Collected x Average Travel times on route segments – these can be developed by 1. Directly calculated from continuous probe vehicle data; 2. Estimated from continuous point-based detector data; 3. Collected in periodic special studies (e.g., floating car runs); and 4. Estimated using computer simulation, sketch planning, or demand forecasting models. x The buffer Index is computed as: Buffer Index(%)= [(95th % travel time (minutes) - average travel time(minutes) / average travel time (minutes)] *100%

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 14 10/09 Performance Measure ID#: OB-2 Performance Measurement Category: Outcome - Based Frequency of Data Collection x Annual Data Collection Location (s) x Focus on I-15, I-515/US-93/95, and the 215 Beltway as initial corridors which are expanding the travel time program Data Analysis Technique x Travel time runs, data from taxis equipped with Automated Vehicle Identification (AVI) Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x FAST x NDOT x Clark County (Bruce Woodbury Beltway) x McCarran International Airport (for access to / from 215 via airport tunnel)

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 15 10/09 Performance Measure ID#: OB-3 Performance Measurement Category: Outcome - Based Title: Peak Period Delay Performance Measure Description: Peak period delay measures on selected routes Target Goal: A 5% decrease in the average peak period delay on a year to year basis on selected routes Value of Performance Measure: Expanding the delay information shared with travelers would be beneficial for enhancing the reliability of the transportation network. Supports Strategy or Strategies: SN-6: Continue testing Adaptive Traffic Signal Control (ATCS) SN-9: Enhance ADUS Software and Reporting of Real-Time Data SN-10: Expand Travel Time Program to Southern Nevada Freeway System NN-3: Corridor System Management Plan Performance Measurement Plan Data to Be Collected x Delay per vehicle per mile; total delay, and total delay per mile. x Delay is calculated by subtracting travel time under ideal conditions (for example, posted speeds) from actual travel times measured while driving each segment(s): o Actual Travel Time (in hours) = Distance (in miles) /Actual Average Speed (in miles per hour) o Optimal Travel Time (in hours) = Distance (in miles)/Posted Speed (in miles per hour) o Delay (in hours) = Actual Travel Time (in hours) – Optimal Travel Time (in hours)

Source: FHWA, Office of Operations – Travel Time Reliability Report (http://ops.fhwa.dot.gov/publications/tt_reliability/TTR_Report.htm#90th) Frequency of Data Collection x Annual Data Collection Location (s) x Focus on I-15, I-515/US-93/95, and the 215 Beltway as initial corridors for developing delay data, in coordination with travel time data

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 16 10/09 Performance Measure ID#: OB-3 Performance Measurement Category: Outcome - Based Data Analysis Technique x Travel time runs, data from taxis equipped with Automated Vehicle Identification (AVI ) Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x FAST x NDOT x Clark County (Bruce Woodbury Beltway) x McCarran International Airport (for access to / from 215 via airport tunnel)

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 17 10/09 Performance Measure ID#: OB-4 Performance Measurement Category: Outcome - Based Title: Percent of days when speeds were less than 35 mph on selected routes Performance Measure Description: Peak period delay measures on selected routes Target Goal: A reduction in the percentage of days with average peak period speeds less than 35 mph Value of Performance Measure: Expanding the delay information shared with travelers would be beneficial for enhancing the reliability of the transportation network. Supports Strategy or Strategies: SN-6: Continue testing Adaptive Traffic Signal Control (ATCS) SN-9: Enhance ADUS Software and Reporting of Real-Time Data SN-10: Expand Travel Time Program to Southern Nevada Freeway System NN-3: Corridor System Management Plan Performance Measurement Plan Data to Be Collected x Average Trip Speed over a defined period (e.g. one month) , over peak periods x Calculate the percent of days the average trip speed fell to below 35 mph x Graph this data and compare on an annual basis

Source: Washington Department of Transportation , Gray Notebook Excerpt, GNB Edition 31, September 30, 2008 Frequency of Data Collection x Annual Data Collection Location (s) x Focus on I-15, I-515/US-93/95, and the 215 Beltway as initial corridors for developing delay data, in coordination with travel time data Data Analysis Technique x Calculate average speeds during travel time runs, using probe vehicle Database Management Requirements x Spreadsheet 092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 18 10/09 Performance Measure ID#: OB-4 Performance Measurement Category: Outcome - Based Performance Analysis Reporting x Annual Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x FAST x NDOT x Clark County (Bruce Woodbury Beltway) x McCarran International Airport (for access to / from 215 via airport tunnel)

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 19 10/09 Performance Measure ID#: OB-5 Performance Measurement Category: Outcome - Based Title: Travel times before and after construction projects – peak periods Performance Measure Description: Before and after travel times on selected construction projects Target Goal: Improvement (reduction) in peak period travel time as a result of road widening projects Value of Performance Measure: This measure will demonstrate a measurable benefit for travelers as a result of roadway improvements Supports Strategy or Strategies: SN- 8: Maintain and Enhance the RTC Transportation Capacity Improvement Program SN-9: Enhance ADUS Software and Reporting of Real-Time Data Performance Measurement Plan Data to Be Collected x Before and after peak period travel times on construction projects

Source: 2009 Strategic Direction and Performance Measures, UDOT Frequency of Data Collection x Annual Data Collection Location (s) x Focus on major projects throughout the state on the state highway system Data Analysis Technique x Travel time runs Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 20 10/09 Performance Measure ID#: OB-5 Performance Measurement Category: Outcome - Based Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x NDOT x FAST x RTC of Washoe County

x Private sector data companies (such as Traffic.com or INRIX) Phasing of Performance Monitoring Measure

x Evaluate the use of private company data collection information to calculate travel times for traveler information purposes (website, DMS, radio/television, other media)

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 21 10/09 Performance Measure ID#: OB-6 Performance Measurement Category: Outcome - Based Title: Travel times delay due to construction projects Performance Measure Description: Before and after travel times on selected construction corridors Target Goal: Reduction in average delays on construction projects Value of Performance Measure: This measure can show how improvements to work zones, alternate route plan and other construction strategies can improve travel time delays during construction. Supports Strategy or Strategies: SN- 8: Maintain and Enhance the RTC Transportation Capacity Improvement Program SN-9: Enhance ADUS Software and Reporting of Real-Time Data Performance Measurement Plan Data to Be Collected x Peak period travel times on construction projects

Frequency of Data Collection x Annual Data Collection Location (s) x Focus on major projects on the state highway system Data Analysis Technique x Travel time runs Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x NDOT x FAST x RTC of Washoe County

x Private sector data companies (such as Traffic.com or INRIX) Phasing of Performance Monitoring Measure

x Evaluate the use of private company data collection information to calculate travel times for traveler information purposes (website, DMS, radio/television, other media) 092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 22 10/09 3. ACTIVITY-BASED PERFORMANCE MEASURES Activity-based performance measures will be designed for use by NDOT staff that is responsible for operating and maintaining the state roadway system. These will be measures of activities performed by NDOT transportation professionals that indirectly improve the reliability of the transportation system. Examples are 511 system usage and incident clearance times. A form summarized the performance measurement plan for each outcome based performance measure is summarized in the following forms. Each form provides the following data:

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 23 10/09 Performance Measure ID#: AB-1 Performance Measurement Category: Activity - Based Title: 5-1-1 System Usage – Website Metrics Performance Measure Description: Metrics to describe 5-1-1 system usage Target Goal: 10% increase in website metrics annually Value of Performance Measure: Supports Strategy or Strategies: SW-5:Centralized Database for Regional and Statewide Information SW-6: Traveler Information Business Plan NN-9: Integrate CCTV Images to Traveler Information Services I80-3: Freight Traveler Information Support Plan Performance Measurement Plan Data to Be Collected x Number of calls per month; website statistics including page views, total number of visitors, most popular pages

Frequency of Data Collection x Monthly, or may want to consider analysis quarterly to correspond with seasonal travel , when weather is a consideration

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 24 10/09 Performance Measure ID#: AB-1 Performance Measurement Category: Activity - Based Data Collection Location (s) x NDOT 5-1-1 System Call Center records, website statistics counter Data Analysis Technique x Calculate quarterly statistics and compare x May want to relate website traffic increases to seasonal events, such as weather-related road closures Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual performance metrics Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x NDOT 5-1-1 System Call Center – Meridian Phasing of Performance Monitoring Measure This performance measure can be implemented for the 511 system in its entirety. Over time, relate system usage to specific events, e.g. weather-related events

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 25 10/09 Performance Measure ID#: AB-2 Performance Measurement Category: Activity - Based Title: Number of Dynamic Message Sign Alerts Per Month Performance Measure Description: Number of Dynamic Message Sign Alerts per Month on Selected State Highways Target Goal: Increase usage of dynamic message sign alerts, e.g. 10% increase by 2010, compared to 2009 Value of Performance Measure: Demonstrates that Dynamic Message Signs are providing more information to the traveling public Supports Strategy or Strategies: SW-6: Traveler Information Business Plan SW-1, SN-1, NN-1 : Alternate Route Plan for freeways and State Highway Diversion I80-2: Weather Condition Reporting /Coordination Plan Across State Boundaries on I-80

Performance Measurement Plan Data to Be Collected x Number of Dynamic Message Signs at Selected Locations

Frequency of Data Collection x Annually Data Collection Location (s) x To be determined Data Analysis Technique x Calculate monthly statistics and compare Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual performance metrics Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x NDOT Phasing of Performance Monitoring Measure This performance measure can be implemented over a larger number of routes and route segments over time. Initial measurement would likely be on I-80 and routes in the Southern Nevada area.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 26 10/09 Performance Measure ID#: AB-3 Performance Measurement Category: Activity - Based Title: Increase in Number of Dynamic Message Sign Installations Performance Measure Description: Increase in Number of Dynamic Message Sign Installations on all State Highways Target Goal: Increase installations of dynamic message signs on an annual basis Value of Performance Measure: Demonstrate that travelers can obtain more real-time information on their travels. A dynamic message sign can provide motorists with important information about congestion, incidents, roadwork zones, travel times, special events, or speed limits on a specific highway segment. They may also recommend alternative routes, limit travel speed, warn of duration and location of problems, broadcast AMBER Alerts, or simply provide alerts or warnings. Supports Strategy or Strategies: SW-6 Traveler Information Business Plan I80-2: Weather Condition Reporting /Coordination Plan Across State Boundaries on I-80 Performance Measurement Plan Data to Be Collected x Number of Dynamic Message Signs installations statewide

Frequency of Data Collection x Annually Data Collection Location (s) x All state highways Data Analysis Technique x Calculate yearly number of installations and compare on a year to year basis Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual comparisons Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x NDOT Phasing of Performance Monitoring Measure This performance measure can be implemented for the entire state route system on an annual basis

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 27 10/09 Performance Measure ID#: AB-4 Performance Measurement Category: Activity - Based Title: Increase in Number of Traveler Alert Notifications (Future) Performance Measure Description: Number of Traveler Alert Notifications (Future) sent via e-mail, or text Target Goal: Increase in the number of traveler alerts sent by text message or e-mail Value of Performance Measure: Demonstrate that travelers can obtain more real-time information on their travels Supports Strategy or Strategies: SW-1- Alternate Route Plan for Freeways and State Highway Diversion SW-5 –Centralized Database for Regional and Statewide Information SW-6 Traveler Information Business Plan Performance Measurement Plan Data to Be Collected x Number of Traveler Alert Notifications sent

x NDOT Phasing of Performance Monitoring Measure This performance measure can be implemented for the entire state route system on an annual basis

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 28 10/09 Performance Measure ID#: AB-5 Performance Measurement Category: Activity - Based Title: Average Incident Clearance Time Performance Measure Description: Average incident response time on selected routes stratified by state route and time period Target Goal: Reduction in Average Incident Clearance Time, by Route NHP has established an incident clearance policy with target clearance times of 30 minutes for property damage only, 60 minutes for injury accidents, and 90 minutes for fatal accidents Value of Performance Measure: Improve non-recurring congestion Supports Strategy or Strategies: SW-2- Incident Clearance Program SW-4, SN-7, NN-6, I80-1:MOUs for Incident Response Resource Sharing SN-2 – Include Arterial Transportation and Public Safety Agencies in the TIM Coalition NN-2: Traffic Incident Management (TIM) Coalition Performance Measurement Plan Data to Be Collected x Average Incidence response time on selected routes

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 29 10/09 Performance Measure ID#: AB-5 Performance Measurement Category: Activity - Based

Frequency of Data Collection x Annually Data Collection Location (s) x Nevada Highway Patrol Data Analysis Technique x Calculate monthly statistics and compare Database Management Requirements x Spreadsheet Performance Analysis Reporting x Average response time comparisons , by route and time period Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x NDOT x Nevada Highway Patrol x Tow Operators x Other related TIM agencies

x Nevada State Towing Association Phasing of Performance Monitoring Measure Working in conjunction with TIM, define routes and time periods to initiate this performance measure.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 30 10/09 Performance Measure ID#: AB-6 Performance Measurement Category: Activity - Based Title: Crash Data in Work Zones Performance Measure Description: Reduction in number of crashes in work zones Target Goal: Reduce the number of crashes in work zones on an annual basis Value of Performance Measure: This measure can demonstrate greater safety in work zones as a result of the Traffic Incident Management Plan for Major Work Zone Policy Supports Strategy or Strategies: SW-9 – Project Specific Traffic Incident Management Plan for Major Work Zone Policy Performance Measurement Plan Data to Be Collected x Number of crashes in work zones x Fatalities can also be shown, as depicted below

Source: 2009 Strategic Direction and Performance Measures, UDOT Frequency of Data Collection x Annually Data Collection Location (s) x Varies, depending on work zones Data Analysis Technique x Calculate annual crash statistics and compare Database Management Requirements x Spreadsheet Performance Analysis Reporting Period x Annual

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 31 10/09 Performance Measure ID#: AB-6 Performance Measurement Category: Activity - Based Data Collection Roles and Responsibilities Lead Agency(s) Partner Agency(s)

x NDOT x Nevada Highway Patrol Phasing of Performance Monitoring Measure This is a future performance measure to measure the result of strategy SW-9 – Project Specific Traffic Incident Management Plan for Major Work Zone Policy

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 32 10/09 4. PERFORMANCE MEASUREMENT REPORTING The previous chapters have provided details about individual performance measurements. This chapter focuses on providing examples of how these performance measures can be summarized in a report to provide an overall view of how the system is operating. Three report components are discussed: an overview, performance scorecard, and individual performance measure summaries.

1.1 Overview of the Process and Progress An overview of the report can provide the reader with a quick summary and entice the reader to explore the details within the report. Some topics can include: An overview of goals Key progress and improvements made during the reporting periods Overview of trends affecting transportation An example of an overview is provided in Figure 6.

1.2 Performance Scorecard A performance scorecard can provide a clear indication of tracking progress with respect to the performance measurements and associated goals. An example of the scorecard concept is provided in Table 4. Key elements of the scorecard are: Measure – brief description of the measure Measure Statistic for the previous period – reporting the measure statistic for the prior period (typically on a yearly or quarterly basis) Measure Statistic for the current period – reporting the measure statistic for the current period (typically on a yearly or quarterly basis) Percent Increase or Decrease – reporting the percent increase or decrease in the measure by comparing periods Goal – describing the measure goal to be achieved Goal Met? – reporting whether the goal was met for the current period Trend – describing whether trends are generally going up, down, or relatively unchanged Comments – a description of factors that are responsible for the trend. The comment section would also note special situations that have occurred during the analysis period.

1.3 Performance Measure Summaries The main body of the report will focus of separate reporting of each performance measure. Chapters 2 and 3 show examples of ways to present the performance measures. Key elements of these discussions are: Presentation of the data

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 33 10/09 Discussion of what projects or changes in policies and procedures have been occurring that may affect the data A more detailed discussion of trends and reasons for the trends

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 34 10/09 Figure 6 – Example Overview Section of Performance Measurement Report

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 35 10/09 Table 4 – Example of a Performance Measurement Scorecard

Measure Previous Period Current Period Percent Goal Goal Trend Comments Increase or Met? Decrease

Outcome-based Performance Measures

95% reliable 95% reliable travel 95% reliable travel - 14% A 5% decrease The 95% reliable travel times on 3 travel time times on 10 routes times on 10 routes in the 95% routes have decreased as a result average 35 minutes average 30 minutes reliable travel of road widening projects times

Buffer Index The buffer index on 10 The buffer index on +20% Decrease in The buffer index is increasing, routes averages 8 10 routes averages the buffer index indicating less reliable travel minutes 10 minutes on a year to times year basis Travel time delay Travel time delay on 10 Travel time delay on - 12.5% A 5% decrease Travel time delays decreased on (peak period) routes during peak 10 routes during peak in the average 5 routes periods averaged 32 periods averaged 28 peak period minutes minutes delay on a year to year basis on selected routes Percent of days On 5 selected corridors, On 5 selected -5% A reduction in The percent of days where route where average the average percent of corridors, the average the percentage speeds were less than 35 mph route speed was days with average route percent of days with of days with decreased, due to less travel less than 35 mph speeds less than 35 average route speeds average routes demand on those routes mph were 20% less than 35 mph speeds less were 15%% than 35 mph Travel times Average travel time = Average travel time 16.6% Reduction in A review of before and after travel before and after 24 minutes on 5 after construction = peak period times on 5 construction projects construction projects 20 minutes on 5 travel time as a showed that travel times projects projects result of road decreased by an average of 8% widening projects

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 36 10/09 Measure Previous Period Current Period Percent Goal Goal Trend Comments Increase or Met? Decrease

Travel time delay Average peak period Average peak period + 14% Reduction in Peak period delays on 5 corridors due to delays on 5 corridors delays on 5 corridors average delays under construction increased by construction under construction under construction on construction 14%. During the next period, a averaged 28 minutes averaged 32 minutes projects new work zone strategy will be implemented to reduce delays Activity-Based Performance Measures

511 System 5,000 page views 6,000 page views 20% increase 10% increase 511 system usage increased on I- Usage annually 80, particularly during the storms that occurred on March 14-18, 20- -

Number of 50 alerts 65 alerts 30% increase 10% increase More alerts were provided in 20--, Dynamic in number of especially in the southern Nevada Message Signs alerts area alerts per month

Increase in 5 DMS installed 8 DMS installed 60% increase Increase in DMS were installed on 3 state Number of in sign number of routes Dynamic installations DMS Message Sign installations Installations Increase in 0 50 N/A Increase in A new program of traveler alerts Number of number of sent via text message, resulted in Traveler Alert traveler alerts 50 text messages being sent in Notifications sent by text or 20-- . (Future measure) e-mail Incidence Average clearance time Average clearance -4% Reduction in Since Implementation of the TIM Clearance Times for fatal crashes time for fatal crashes average Coalition in Northern Nevada in statewide is 89 minutes is 85 minutes clearance time 20--, incident clearance times for fatal crashes have reduced by 4%

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 37 10/09 Measure Previous Period Current Period Percent Goal Goal Trend Comments Increase or Met? Decrease

Crash data in There were 10 crashes There were 6 crashes -40% Reduction in Crashes in work zones have work zones in work zones in 20-- in work zones in 20-- the number of decreased significantly since the crashes in work Traffic Incident Management zones Plan for Work Zones Policy was implemented

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 38 10/09 APPENDIX A – LITERATURE REVIEW A literature review was conducted to determine current practices regarding performance measurement nationwide. Table A-1 summarizes the documents that were reviewed that deal with performance measurement. The references are stratified into the categories of general references, state references, and Nevada references.

Table A.1 – Documents Reviewed

Document Name Summary General References An Interim Guidebook on the Congestion Management Process This guidebook provides information on in Metropolitan Transportation Planning, USDOT, February how to create a objectives driven 2008 performance based congestion management process A Primer on Performance – Based Highway Program This primer reviews performance Management – Examples from Selected States, January 2008 management plans from 11 states Archived Data Management Systems- A Cross-Cutting Study This report discusses archived data Linking Operations and Planning, Federal Highway management systems, including case Administration, December 2005 studies in Washington State, California, Detroit, Minnesota, Maricopa County, and King County Cost Effective Performance Measures for Travel Time Delay, Report discusses selection of performance NCHRP Report 618, Variation and Reliability, 2008 measures, data collection and processing, before/after studies, identification of deficiencies, forecasting future performance, alternatives analysis, and using travel time data in planning and decision-making. Guide to Effective Freeway Performance Measurement, Guide discusses freeway performance NCHRP Research Results Digest 312, February 2007 measures. Investigation of System Operations Performance Measures for Research study describes systems the Virginia Department of Transportation, Virginia operations performance measures in the Transportation Research Council, June 2007 areas of traffic, incidents, traveler information, and ITS device reliability

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 39 10/09 Table A.1 – Documents Reviewed (continued)

Document Name Summary General References Performance Measures for Rural Transportation Systems - Guidebook provides a toolbox for Guidebook, June 2006 development of performance measures in 7 areas: safety, system preservation, mobility, accessibility, reliability, productivity, and return on investment Predicting Performance with Traffic Analysis Tools – Final This report discusses how well simulation Report, Report Number FHWA-HOP-08-055, Science and traffic analysis tools predict Applications International Corporation, March 2008. performance. Travel Time Reliability: Making It There On Time, All The Time, Guide to development of travel time FHWA, prepared by Texas Transportation Institute and reliability measures Cambridge Systematics, January 1, 2006 Using Performance Management to Deliver Accountability, Discusses candidate performance AASHTO 2008 Annual Meeting, PowerPoint presentation, measures in the area of safety, October 2008 preservation, congestion, system operation and other categories. Using Travel Time Reliability Measures to Improve Regional Discusses reliability measures such as Transportation Planning and Operations, Lyman, Kate and 95% travel time, buffer index, planning time Bertini, Robert, 2008 TRB Conference paper, November 3, index, and frequency that congestion 2007 exceeds some expected threshold, e.g. percent of days or time that mean speed falls below a certain speed. Washington State Department of Transportation Performance This website provides links to state and Measurement Library, national websites on performance http://www.wsdot.wa.gov/Accountability/Publications/Library.htm management State Examples California Caltrans Performance Measures for the quarter ending March Caltrans mobility performance measures 31, 2009 include statewide vehicle hours of delay, percent of good (operating) detectors , percent of detector coverage, percent variation from predicted travel time, percent of major incidents cleared in less than 90 minutes, Performance Measures for Rural Transportation Systems- Provides a toolbox for development of Guidebook, June 2006 performance measures in 7 areas: safety, system preservation, mobility, accessibility, reliability, productivity, and return on investment Maryland Annual Attainment Report on Transportation System Performance measures related to mobility Performance 2004, Maryland Department of Transportation included percentage of lane-miles with annual volumes below congested levels, Locations of peak period freeway congestion in the Baltimore and Washington region

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 40 10/09 Table A.1 – Documents Reviewed (continued)

Document Name Summary General References Minnesota 2008 Annual Transportation Performance Measures, Minnesota MnDOT performance measures include Department of transportation percentage of miles of urban freeway system congested. Congestion is defined as traffic speed below 45 mph for 5 minutes or more in weekday peak periods. Incident- related performance measures include average clearance time, with an overall goal of less than or equal to 35 minutes. Utah Utah Performance Reports, Performance reports include metrics on http://performance.utah.gov/agencies/udot.shtml accident clearance time, number of fatalities, and travel times on selected commute routes in the AM and PM peak periods Virginia Investigation of System Operations Performance Measures for This report identifies performance the Virginia Department of Transportation, Virginia measures for traffic, incidents, traveler Transportation Research Council, 2007 information, and intelligent transportation systems device reliability. Washington The Gray Notebook, GBN 33, quarter ending March 31, The Gray Notebook is the basis for 2009,Washington State Department of Transportation WSDOT performance reporting that links performance measures for the strategic plan, legislative, and executive policy directions, as well as federal reporting requirements. Measuring Delay and Congestion Annual Update, Gray This report focuses on congestion –related Notebook Excerpt for the quarter ending September 30, 2008, data and incident response. It also Washington State Department of Transportation features special reports, e.g. this report features fuel prices and travel conditions during the first half of 2008. Mobility performance measures include travel time analyses (average travel times, 95% reliable travel times, duration of congestion, percent of days when speeds were less than 35 mph, travel time comparison graphs), HOV lane performance standards, throughput productivity, hours of delay and vehicle– miles traveled Nevada References FAST Traffic Patterns Studies, Visual presentation of weekly arterial travel www.nvfast.org/trafficpatterns.html volumes for various areas of southern Nevada and major freeways.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 41 10/09 Table A.1 – Documents Reviewed (continued)

Document Name Summary General References FY 2008 Annual Report for 2007 Assembly Bill 595 to the Assembly Bill 595 provides additional Board of Directors, NDOT bonding capacity for super and mega (major) projects identified as priorities by NDOT. The bill requires NDOT to develop and report on performance measurement. This report documents performance measures for FY 2008. (Requirements are discussed in more detail in Chapter 2). Regional Transportation Plan FY 2006-2030, Regional RTC Long-Range Transportation Plan, Transportation Commission of Southern Nevada, July 2006 including congestion management program element, highway element, and other multimodal elements. Safestat Report, Nevada Highway Patrol, Central Command, Summarizes crash analysis, field January 5, 2009 enforcement activity, and administrative services and other related Nevada Highway Patrol services on a monthly basis

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 42 10/09 APPENDIX B – PERFORMANCE MEASUREMENT PLAN DEVELOPMENT The Performance Measurement Plan was developed using the following approach: A literature review was performed to determine what other states are using as performance measures and researching available transportation information and sources. An initial list of performance measures was developed and linked to the gaps and strategies identified in Working Papers 4 and 5, respectively. Performance measures were refined and stratified to outcome based and activity based performance measures, in order to better define the audience and value of the measures. These general categories were discussed with NDOT staff, and subsequently further refined.

B.1 Initial Development and Refinement of Performance Measures The development of performance measures involved a multi-step process that can be summarized as follows: An initial list of performance measures was developed to address reliability enhancing strategies that were developed in response to gaps identified in Working Paper 4- Gap Analysis. Gaps were defined in six categories: Capacity Improvements and Travel Demand Management – Combines physical capacity deficiencies and travel demand management (TDM) efforts such as managed lanes, trip reduction strategies, and transit. Traffic Incident Management – Covers all aspects of traffic incident management, including incident related traveler information. Work Zone Management – Covers all aspects of work zone management, including construction related traveler information. Traveler Information – Focuses on broad traveler information services such as mobile access to real-time information and the availability of road weather information. Planning and Policy – Examines planning related processes and the policies that define them such as land use planning and access management. Operations and Management – Combines day to include discussion of stakeholder involvement Strategies were developed (in Working Paper 5) to address these gaps, and were stratified by area. Performance measures were then developed to coordinate with strategies wherever possible. A team meeting was held to discuss each draft strategies and performance measures. The discussion resulted in development of two sets of performance measures, each geared towards a different audience: Outcome-based geographic focused performance measures: Outcome-based performance measures that are designed to provide policy makers, elected officials, and the public with information regarding the reliability of roadways in Nevada. These measures will describe the ‘state of the roadway system’ and will include reliability measures such as average travel times and delay on selected corridors. These performance measures are geographically focused. Activity-based, system-focused performance measures: Activity-based performance measures will be designed for use by NDOT staff that is responsible for operating and

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 43 10/09 maintaining the state roadway system. These will be measures of activities performed by NDOT transportation professionals that indirectly improve the reliability of the transportation system. Examples are 511 system usage and incident response and clearance times. A teleconference was held with the NDOT on August 18, 2009 to discuss performance measures. They provided valuable insights and direction for the performance measurement development process. Key comments included: Outcome based and activity based performance measures are an effective way to categorize the performance measures. Currently the only significant performance measurement data is available in the Las Vegas region. Therefore it is logical to start the performance measurement program with a focus in the Las Vegas / southern Nevada region and gradually expand it to other Nevada urban areas and eventually to the state as a whole. If a Traffic Management Center is developed in Northern Nevada, mobility performance data could be gathered there, similar FAST. The ultimate goal will be to create automated systems for gathering data throughout the state. Focus on developing measures that are meaningful to the public. Show how the performance measures bring value to the public and to policy makers and how they can be communicated to the public. How is what we are doing saving travelers and taxpayers money? Investigate how performance measures can be used to prioritize projects. Can performance measures be used to support funding requests? Consider how performance measures address non-recurring congestion and recurring congestion. Consider using report card metrics to report performance measures– this is an easy way to communicate to the public. Prioritize performance measures.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 44 10/09 APPENDIX C – EXISTING PERFORMANCE MONITORING Transportation system performance monitoring in Nevada is currently accomplished in two main ways: NDOT performance monitoring to conform with the requirements of Assembly Bill 595, which mandates performance monitoring requirements; and Performance monitoring that is under development by the Freeway and Arterial System of Transportation (FAST), an operational division within the RTC of Southern Nevada. FAST is a unique operations entity in that it manages and controls both the freeway and arterial networks from the FAST Traffic Management Center (TMC). Each of these programs is discussed below:

C.1 Performance Monitoring Per Assembly Bill 595 Performance monitoring is currently undertaken as a requirement of Assembly Bill 595. Passed in 2007, this bill provided the Department of Transportation additional bonding capacity for super and mega (major) projects identified by the Department as priority projects for the State of Nevada. The bill requires the Department to develop a plan for measuring its performance, which must include performance measures approved by the Board of Directors of the Department of Transportation (defined as ‘Board’ by NRS 408.033). The bill also included requirements for reporting to the Governor, Board, and Legislative Counsel Bureau. Assembly Bill 595 included four main reporting requirements: three are for annual reports and one is for a quarterly report. The Department has developed fifteen proposed performance measures among the four major divisions, the Administrative Division (5 measures), the Planning Division (1 measure), the Operations Division (5 measures), and the Engineering Division (4 measures). These performance measures are intended to quantify progress in meeting those goals. The performance measures for the Planning Division, the Operations Division, and the Engineering Division are listed below: PLANNING DIVISION 1. Reduce Congestion on the State System Percentage of daily vehicle miles traveled that occur at Level of Service E (unstable traffic flow) or worse on the state system OPERATIONS DIVISION 1. Streamline Project Delivery – Schedule and Estimate from Bid Opening to Construction Completion Percentage of projects within established range of cost estimate and schedule to completion 2. Maintain State Roadways Percentage of state maintained pavements needing annual preservation in order to maintain the pavement International Roughness Index rating of fair or better condition 3. Maintain State Fleet Percentage of fleet meeting (requiring) replacement criteria and percentage of fleet in compliance with condition criteria 4. Maintain State Facilities Percentage of Department building facilities in compliance with regulatory building and safety codes

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 45 10/09 5. Provide Continuity of Business Operations Percentage of seven Department Emergency Plans that have been completed ENGINEERING DIVISION 1. Reduce Fatal Crashes Number of fatalities on Nevada’s streets and highways 2. Streamline Project Delivery – Schedule and Estimate from Project Initiation to Bidding Percentage of projects completed within range of established estimate and schedule after the environmental process 3. Maintain State Bridges Percentage of Department-owned bridges which are eligible for federal funding and are categorized as structurally deficient or functionally obsolete 4. Streamline Permitting Process Percentage of permits issued or rejected within 45 days of receipt

C.2 FAST Performance Measures FAST operates all of the arterial and interchange traffic signals, dynamic message signs (DMS), CCTV, ramp meters and other ITS devices in the Las Vegas metropolitan area. There are approximately 1,150 traffic signals on the centralized TMC network. Approximately 750 of these signals have coordinated control and communications. At the time this report was prepared, there were approximately 27 miles of ITS freeway management system infrastructure. NDOT and the RTC/FAST are working to expand the traffic signal communications network as well as the freeway management network throughout the Las Vegas Valley. Arterial CCTV cameras are in place on several key arterials, including Las Vegas Boulevard, Charleston Boulevard, Decatur Boulevard, Tropicana Avenue, Flamingo Road, and Craig Road, among others. The FAST TMC is a facility that houses the following organizations: NHP Headquarters and Southern Command dispatch personnel; FAST personnel; Las Vegas Freeway Service Patrol (FSP); and NDOT personnel. The FAST TMC and NHP’s Southern Command dispatch share a video wall whereby FAST operators can display specific freeway cameras to support incident and event management. In addition to data obtained through the FAST FMS instrumentation, FAST also obtains data from field devices installed by Traffic.com. This data comes into the TMC through the FMS system. FAST is currently evaluating the use of Traffic.com data to bolster the FAST database and expand the current travel time program. Other improvements to ITS and traffic signal timing coordination along arterial roadways are included in the current TIP for 2011 and 2012 totaling $6M.

C.3 Planned ITS Improvements The RTC TIP also includes improvements to the freeway network on I-515 and the 215 Beltway. These improvements (called FAST Packages) are planned to install detection, surveillance, dynamic message signs, fiber optic communications, and other freeway management system infrastructure. The FAST Packages are currently funded for the following fiscal years: 2010 ($7M), 2011 ($7M), and 2012 ($8M). There are plans to implement additional packages beyond 092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 46 10/09 the 2012 timeframe. The FAST network in its existing state, portions of the freeway network which are in development and future FAST Packages programmed for funding are shown in Figure 3. In addition to ITS projects, the RTC TIP contains intersection improvement projects, I- 15 Express Lanes, I-15 North Design Build, and the US-95 Project. These projects will enhance system efficiency and operation.

Figure C.1 – FAST Freeway Network

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 47 10/09 C.4 FAST Performance Measures FAST currently posts travel times along portions of the freeway network within the Las Vegas Valley. This program is limited to sections of the freeway that are equipped with data collection and information dissemination devices (DMS). FAST is committed to expanding the travel time program as new sections of the freeway are equipped with the necessary infrastructure and devices, or as other public/private partnerships are developed. According to the FAST 2010-2011 FMS Scope of Services, FAST will conduct travel time studies on eight road segments, including four segments on I-15, two segments on I-515 and two segments on US95. The agencies within the Las Vegas Valley have the ability to access the data stored within the ADUS database. The local agencies all operate a Joint Management Center (JMC) which allows them to view data directly. ADUS data is also accessible by website as long as the correct authorized access is used. There are enhancements that could improve the user interface and available data in the ADUS database, such as allowing manual data uploading and modifications to the reporting of real-time data. FAST personnel are currently working on defining performance measures. Their focus is on generating performance measures for the freeways, primarily because the freeways have the greatest equipment deployment. The next priority would be arterials. FAST plans to focus on fundamental performance measures that can be easily quantified by governmental agencies and be translated well to the general public (travel time, speed, etc.). Once they get these basic performances measures defined and the process automated, they will focus on expanding the program. FAST has been doing their own travel time runs on arterials to help validate some of the coordination and timing strategies. They have about 1,800 runs in their database, but have not reported the data externally. FAST noted that they are also investigating using the Global Positioning System (GPS) data on paratransit vehicles to help bolster the database. Stakeholders also pointed out that the Valley’s taxi fleet is well equipped with Automated Vehicle Identification (AVI), data which FAST believes they may be able to tap into and use in their database; FAST is focused on the 90-95% percentile day as their benchmark for volumes and operations. This is based on recent national literature and the desire to plan for a typical day, rather than planning for the “worst day” scenario. FAST is unable to accommodate or manage the worst- case scenario simply because the capacity is not there.

092202013 NDOT Statewide ITRP Draft Tech Memo #6.doc Performance Measurement Plan 48 10/09