2017 performance measures plan - nittec

2017 PERFORMANCE MEASURES PLAN

TABLE OF CONTENTS

PART I OUTCOME-DRIVEN MANAGEMENT 4

INTRODUCTION – MEASURING PERFORMANCE 5

CURRENT PERFORMANCE MEASUREMENT PRACTICE 6

PERFORMANCE MEASURES APPROACH 7

DATA MANAGEMENT 8

PART 2 PERFORMANCE MEASURES PLAN 12

NITTEC STRATEGIC OBJECTIVES 13

MEET THE TRANSPORTATION NEEDS OF PEOPLE AND CUSTOMERS IN THE REGION 15

MANAGE AND OPTIMIZE TRAFFIC FLOW 22

REDUCE CONGESTION ON THE REGIONAL TRANSPORTATION NETWORK 24

IMPROVE SAFETY AND OPERATIONS ON THE REGIONAL NETWORK 30

BECOME OMNISCIENT ABOUT THE REGIONAL TRANSPORTATION NETWORK 39

ACTIONS REQUIRED TO ACHIEVE PERFORMANCE EASURES CAPABILITIES 43

OUTCOME-DRIVEN MANAGEMENT PART I

5

Success must be defined and tracked. A robust system of performance measures is a critical management tool for NITTEC to gain insights about the effectiveness of operations and the impact of its services. This will become increasingly vital as NITTEC undertakes the recommended actions in the 2017 Strategic Plan.

The heart of the Performance Measures plan is a systems engineering approach of using performance measurement and data as a primary management tool to point NITTEC’s operations toward achieving desired objectives. We call it outcome-driven management. Its purpose is for NITTEC to more effectively manage its processes on a proactive, outcome-driven basis by helping NITTEC:

• Assess progress toward achieving strategic objectives throughout all management functions

and processes

• Determine if and to what extent an activity was completed

• Understand the impact of an activity or process

• Understand whether and to what extent key objectives are being met

• Compare relative performance of one activity with others

• Inform management decisions to modify, increase or eliminate an activity or process

• Inform budget decisions, determine resource allocations and measure return on investment

• Gain insight into the relative value of an activity regarding its cost, impact or contribution

• Inform managers when there is a problem that requires attention

• Track and highlight the overall needs of the total Buffalo-Niagara transportation network

How we define success determines what data we collect and analyze to then evaluate how well our objectives are being met. In measuring performance, NITTEC should balance the time and cost requirements of collecting and analyzing data with the benefits derived by gaining insights into progress, informing key decisions and optimizing operations. This is further challenged by the need to understand which data to analyze and what analysis will yield the most useful insights. Hence, we’d better make sure we’re measuring only that which truly matters. The NITTEC Performance Measures plan addresses these challenges.

INTRODUCTION: MEASURING PERFORMANCE

“What you measure is what you manage” ~Peter Drucker

62017 NITTEC CUSTOMER ENGAGEMENT PLAN

In its current performance measurement practices, NITTEC has identified key performance indicators (KPIs) relevant to its core operational areas and functions. NITTEC collects and analyzes requisite data on each KPI. NITTEC then publishes its findings in monthly reports shared with relevant committees and through its widely disseminated annual report. NITTEC members note, consider and discuss outcomes and performance, and this informs the management of NITTEC’s ongoing projects and internal work streams.

This laudable effort has established an operational practice of measuring and reporting performance on a consistent and regular basis. This process helps NITTEC evaluate and inform Coalition members about the impact of the various transportation-related initia-tives and progress toward the region’s shared goals.

NITTEC can but has not yet fully realized the potential benefits of leveraging metrics and data within its management processes and has significant room for improvement in its performance measures practice.

• Currently, analysis and findings presented in NITTEC’s Performance Measures reports do not directly link back to defined outcomes of success or strategic objectives.

• Performance metrics are not directly linked to clear and concise management processes and are thus less actionable in helping NITTEC or Coalition members manage or adjust operations toward better results.

• NITTEC has not defined relevant Measures of Effectiveness (MOEs) to help understand what data is most useful and yields the most important insights.

• We found that, outside of committees, NITTEC members do not place significant value on or use the performance measures data or reports in any meaningful or consistent way within their own operations.

• Despite a wealth of actionable data that Coalition members each collect and could potentially share, NITTEC receives very little data, if any, from them.

NITTEC must also address these additional obstacles to support its new performance measures plan.

• NITTEC’s current data collection is not comprehensive or verified. Many key statistics are inferred and calculated based on limited data, other key pieces of information remain entirely missing or vague.

• The region has not yet installed many ITS devices. NITTEC does not own any of the ITS equipment producing measurable data, and as a result, NITTEC relies primarily on members to provide data.

• NITTEC lacks a data strategy to guide what data to collect from what sources, how to authenticate and verify data, securely store it, and organize and maintain it for conducting analysis or creating reports.

• Nevertheless, there now exists a significant opportunity for NITTEC to build upon its

current foundation of for performance measures to achieve outcome-driven management

through a data-driven approach.

CURRENT PERFORMANCE MEASUREMENT PRACTICE

7

THE HIGH-LEVEL PLAN

The purpose of NITTEC’s performance measurement plan is three-fold.

• Enact outcome-driven management i.e., focus on managing the factors which achieve desired results

• Achieve regional omniscience through data

• Define aspirational performance measures to guide NITTEC’s future operations

• We define each of these in greater detail. Deploying this plan entails four concurrent operational objectives:

• Define and deploy priority performance measures into KPIs to initiate outcome-driven management

• Deploy a virtuous feedback loop of automated KPI dashboards to support outcome-driven management

• Build required data collection, storage, management and analytics capabilities to achieve data omniscience

• Use data benchmarking to affirm aspirational performance metrics for future deployment

This encompasses a single vision for a unified, integrated and virtuous system that drives continuous performance improvement whereby data is the primary fuel. For implementation, there are distinct stages.

Stage 1 – Collect data (i.e., current state)> Some outputs are measured and reported > Some output results are used directly in some

management processes and operations

Stage 2 – Improve management> Data collection is expanded to ingest all available

data from current partners and field elements> Data is organized and analyzed against interim KPIs> Data is made easily available and pre-digested via

KPI dashboards> Performance insights applied to management

functions and committees for program improvements> Outcome measures identified, initial benchmarks

established, and KPIs are revised as needed

Stage 3 – Achieve integration> Data collection is expanded via roadway

deployment of ITS data sensors and other sources> Data collection and digestion is automated with automatic feeds from sources

Stage 4 – Achieve optimization> Enhanced performance measures reported for

continuous improvement in operations

PERFORMANCE MEASURES APPROACH


Outcome-driven management means managing the factors that directly achieve desired results in all of NITTEC’s operational functions and committee work. This elevates the role of performance measures as a management tool, and entails using mutually estab-lished quantifiable metrics to manage projects and operations. This in turn allows NITTEC and its commit-tees to maintain focus on broader strategic objectives.

This approach has certain benefits:

• Keeps management focused on outcomes rather than on administrative and individual task-level minutiae by linking performance measures directly to strategic objectives

• Demonstrates tangible results and return-on- investment (ROI) to justify funding for regional

projects

• Motivates and guides managers to optimize opera-tions and activities to achieve better performance

• Improves productivity and effectiveness by priori-tizing which actions achieve desired outcomes

• Improves multi-agency collaboration by creating a common insight into problems and required actions

• Clarifies how each member’s contribution affects overall progress toward shared objectives

Outcome-driven management would be supported by automated KPI dashboards reflecting the key information that NITTEC and its committees need in order to assess progress and make decisions. The dashboards would be cloud-hosted by NITTEC and would be automatically populated by requisite data and pre-formulated analysis. All NITTEC members would have secure, remote access on an always-on basis.

DATA MANAGEMENT

9

Omniscience through data is the general rule that NITTEC should collect as much relevant data as possible from as many available sources as possible, beginning with Coalition members and eventually other regional entities. This would entail the implemen-tation of the operations necessary to receive and store data in a safe, secure environment, and then derive value and insights from it.

The objective is to establish a data warehouse of the regional transportation network that over time becomes clearer, more robust and more valuable with the ongoing addition of data. This data would be available to NITTEC members (i.e., GBNRTC, University at Buffalo) for deep analysis and research.

The value of having complete data, and the value of its multiple applications and the insights it yields, will soon be far more valuable than the resources required to obtain and store its pieces.

Data omniscience is the idea that public sector entities of the near-term future will have the capability, as well as the need, to understand a wide range of human behaviors (i.e., driving habits) and needs of their constituencies through the process of collecting and analyzing the data that will result from everyday activity.

The transportation network in the region is a foundation for regional life. Its everyday usage and management will produce terabytes of data daily, and presents an opportunity to achieve data collection on a mass scale.

Insights and learnings from such large-scale data analysis will not only be commonplace, but public sector entities will be unable to fulfill their most basic missions or provide public services without such analysis. The world is rapidly becoming data driven and public sector entities have no choice and must adapt accordingly.

For example, where NITTEC members instrument the major roadways with sensors or collects probe data from mobile devices, it is both desirable and possible to know of every single vehicle and every single trip undertaken on any given day in any section of those roadways.

The capability to derive information at this degree of granularity, such as origin destination (OD) data, will at first be a significant competitive advantage to fuel the economic development and effective and efficient provision of public services in a region.

But in the not-so-long-term future, it will soon be a competitive necessity whereby the regional competition for business and residents will hinge on the capabilities of public-sector entities to use data to improve mobility, quality of life conditions and other regional capabilities that attract and retain people and businesses.

OMNISCIENCE THROUGH DATA


Performance measures are the key feature in an outcome-driven, systems engineering approach. It is vital to establish comprehensive performance metrics linked directly to desired strategic outcomes as a core function within NITTEC’s operations.

These establish priorities and guide ongoing process optimizations and resource allocation decisions to ensure these are closely linked to desired outcomes. They also incorporate guidelines to align the region with data reporting requirements and desired outcomes at the state and federal level.

However, in its current state, NITTEC lacks a complete capability to produce and analyze the quantity of data necessary to support a comprehensive performance measures plan. It would be counter-productive to recommend a broad and robust set of operations that NITTEC is not able to deploy or manage.

For example, NITTEC currently cannot but should be able to calculate travel times in real-time between the most common travel points within NITTEC’s jurisdiction at any time. NITTEC should be able to compare same data points against historical or other circumstances e.g., same date on different year, during holiday periods, typical for time of day, typical given construction activity. Without this basic capability, more robust measurements are not feasible.

NITTEC would need to instrument its major roadways or engage a sufficient number of regional travelers with smart phones or connected vehicles to opt-in to automatically and passively provide probe data back to NITTEC to produce requisite data from which such calculations can be derived.

Hence, our recommendations feature a phased-in approach to a 2017 performance measures plan which define initial, high-priority metrics that are aligned with NITTEC’s current capabilities and a pathway toward a more robust plan. The aspirational performance measures are those success metrics which reflect to what extent progress has been made toward desired outcomes across the entire region members.

Below for each of the key desired outcomes we outline the data elements that, when available and reliable, will provide insights into success.

ASPIRATIONAL PERFORMANCE MEASURES

11

Public leaders in the Buffalo Niagara region must embrace the growing importance of data. It is the fuel that public entities will be increasingly required to collect and apply for daily operational functions of government, the effective delivery of public goods, the efficient allocation of increasingly scarce public resources, and insights into the overall state and needs of the region. Robust data and analytics capa-bilities are already becoming critical in managing the economic health of the region as a source of regional competitive advantage.

The importance of data for NITTEC cannot be overstated. Data is inextricably connected to performance measures and is the vital fuel for a systems engineering approach to management. Data is the primary tool that NITTEC must deploy to successfully achieve outcome-driven management. Hence, it is vital NITTEC define a comprehensive data strategy, i.e., an approach for how NITTEC will:

• Identify and select relevant data to capture and measure

• Create / generate data (from NITTEC operations)

• Capture and receive data (from other sources)

• Authenticate and verify data

• Classify and organize data

• Store data (i.e., physical servers / hosting services)

• Ensure data integrity (e.g., security protocols, addressing data obsolescence, etc.)

• Retrieving & sharing data for analysis (i.e., protocols for access and dissemination)

Data alone, regardless of quantity or accuracy, provides no useful insights or application without being organized into useful metrics which quantify progress toward desired outcomes or measure vital manage-ment functions. The right metrics must be selected and the right data must be available.

There are three different but equally important roles for the three types of metrics and the corresponding data that we have recommended for NITTEC to deploy in its Performance Measures plan:

(1) metrics that illuminate the impact of overall efforts toward broader strategic objectives;

(2) metrics which illustrate quantifiable progress toward a defined goal; and

(3) data which help indicate the successful function of certain processes.

While data may be deployed to populate metrics in all three categories, this will help determine which data to measure, at which times, and for what purpose as NITTEC considers its approach to data management.

DATA MANAGEMENT


PERFORMANCE MEASURES PLAN PART 2

13

The 2017 NITTEC Performance Measures Plan is designed to quantify progress toward NITTEC’s core strategic objectives and reflects certain necessary conditions:

• It is designed to link directly to NITTEC’s strategic objectives and is organized accordingly

• It assumes robust data collection and related capabilities will be developed over time as a priority

• It incorporates current Federal requirements for reporting and data collection

• It defines initial metrics that are achievable now and pathway to aspirational metrics assuming required technology is properly integrated to generate and collect necessary data

PERFORMANCE MEASURES FOR STRATEGIC OBJECTIVES

NITTEC STRATEGIC OBJECTIVES

• Know and meet the transportation needs of people and customers in the region

• Manageandoptimizetrafficflow

• Reduce congestion on the regional transportation network

• Improve safety and operations on the regional transportation network

• Become omniscient about the regional transportation network

15

MEET THE TRANSPORTATION NEEDS OF PEOPLE ANDCUSTOMERS IN THE REGION

CapturinginsightsintohoweffectivelyNITTECcommunicateswithcoreaudiences

Management Objective Definition of Success

Keep travelers informed Maximize use of digital and owned media

Initial Performance Metric Key Performance Indicators (KPIs) & Data

Maximize audience reach on social media • Quantity of Twitter and Facebook followers• Change in quantity of followers by month / year

Maximize audience reach on digital media • Quantity of site unique user sessions per day • Quantity of total site visits per day and month• Website uptime (Goal = 99.999%)

Maximize audience engagement on digital media • Average time-on-site per unique visit• Average quantity of page views per visit• Bounce rate (visit only one page, under 5 seconds)

Maximize audience engagement on social media • Quantity of Twitter reactions, i.e., likes, reposts, favorites, responses, etc.• Quantity of Facebook reactions, i.e., likes, shares, comments, etc.

Maximize NITTEC usage of digital & social media • Quantity of website updates: minimum 1 per day• Quantity of Twitter posts: minimum 10 per day• Quantity of Facebook posts: minimum 1 per day• Quantity of content pieces developed for publication (by format, video, image, text, etc.)• Quantity of HAR & DMS messages broadcasted • Capture data by time period (hour, day, week, month, year)

Maximize audience reach on mobile media • Quantity of total MYNITTEC subscribers• Quantity of daily and monthly new downloads

Maximize audience engagement on mobile media • Average daily and monthly active users• Quantity of usage by functionality e.g., “plan trip”• Quantity of alerts / updates: minimum 10 per day• Capture data by geographical location • Capture data by function • Capture data by time period (hour, day, week, month, year)


Aspirational Performance Metric Key Performance Indicators (KPIs) & Data

Maximize ability to analyze data • Capture and manage data by geographical area or point of interest (i.e., correlated using GPS) such as city, roadway, event location, etc.• Capture and manage data by vehicle (i.e., using LPR, BT and/or GPS)

Maximize ability to analyze data • Automated capture of all data elements


Create broadcast partnerships with news organizations • Quantity of broadcast partnerships developed• Capture by category (i.e., newspaper, television, blog, organization, etc.)

Maximize publication of NITTEC information • Quantity of content pieces developed for partners• Quantity of content pieces delivered to partners• Quantity of total content pieces published by partners• Quantity of new content pieces published by partners• Capture data by content format i.e., widget, video, data, text, image, interview, etc.• Capture data by time period: day, week, month, year• Capture data by topic: weather, road conditions, traf-fic conditions and congestion, traffic incident, planned event, construction, etc.

Maximize audience reach via earned media • Quantity of impressions per publication or broadcast e.g., video views, TV viewers, etc.• Average quantity of viewers / impressions per publication or broadcast• Capture data by publisher, piece, by format, by time period (day, week, month, year)

Expanding NITTEC’s audience reach through regional stakeholders


Keep travelers informed Maximize use of earned media

17


Maximize ability to analyze data • Automated data capture by geographical location and roadway sector• Automated data capture by time period (hour, day, week, month, year)

MEET THE TRANSPORTATION NEEDS OF PEOPLE ANDCUSTOMERS IN THE REGION, Continued

Communicatingtothepublicthroughfieldelements


Keep travelers informed Optimizeuseoffieldelements


Quantity of fixed and portable dynamic messaging signs deployed

• Quantity of devices deployed • Capture data by format, make and model• Capture data by geographical location and roadway sector• Capture data by time period (hour, day, week, month, year)

Usage • Quantity of messages deployed, by owner• Topic of message (by category)• Duration of message posting• Capture data by implement location

Capabilities • Quantity with remote take-over by other entities• Quantity with graphical screen• Capture data by implement location

Reliability • Percentage of uptime • Quantity of elements in operation• Quantity of elements in disrepair or maintenance• Average duration of unavailability due to disrepair• Capture data by make and model


Achieving audience reach through active promotions


Keep travelers informed Maximize promotion of NITTEC


Placements of NITTEC content in interior partner envi-ronments e.g., DMV or post office lobby

• Quantity of total placements by location• Quantity of placements by format i.e., brochures, signs, etc.• Capture data by organization • Capture data by geographical location• Capture data by time period (day, week, month, year)

Placements of NITTEC content in exterior out-of-home environments e.g., on a bus, at a bus stop

• Quantity of total placements by location• Quantity of placements by format i.e., brochures, signs, etc.• Capture data by organization • Capture data by geographical location• Capture data by time period (day, week, month, year)

19



Maximize ability to analyze data Automated capture of all data elements

Getting accurate on-the-ground information and data from the public


Maximize inbound communication from the Coalition members or other regional stakeholders

• Quantity of inbound calls• Quantity of inquiries via digital media• Capture data by organization • Capture data by topic and reason• Capture data by source (phone, site, app, etc.)• Capture data by time period (hour, day, week, month, year)

Maximize inbound communication from the public • Quantity of individuals making contact• Quantity of inbound calls or inquiries• Quantity of inquiries via digital media• Capture data by topic and reason• Capture data by user scenario (tourist/visitor, traveler, resident, commuter, etc.)• Capture data by source (phone, site, social platform, mobile app, email, etc.)• Capture data by time (hour, day, week, month, year)

Maximize information requests by external media • Quantity of requests• Capture data by organization • Capture data by topic and request• Capture data by time (hour, day, week, month, year)


Keep travelers informed Maximize incoming audience communications


Publishing content from members of the public to inform others


Participation by members of the public • Quantity of people providing inbound content • Capture data by topic and user-case categories • Capture data by organization affiliation, if any• Capture data by format (video, audio, image, text)• Capture data by time (hour, day, week, month, year)• Capture source by location (i.e., GPS, roadway, city or town, etc.)

Solicit and receive publishable content from Coalition members and regional stakeholders

• Quantity of total content pieces received • Quantity of content pieces re-published by NITTEC on NITTEC’s website and other digital• Quantity of social media posts shared or re-posted• Captured by organization • Capture data by format i.e., post, video, data, etc.• Capture data by time (hour, day, week, month, year)

Solicit and receive publishable content from broadcast partners

• Quantity of total content pieces received • Quantity of content pieces re-published by NITTEC on NITTEC-owned properties• Quantity of social media posts shared or re-posted• Capture data by organization • Capture data by format i.e., post, video, data, etc.• Capture data by time (hour, day, week, month, year)

Solicit and receive publishable content from the public • Quantity of total content pieces received • Quantity of content pieces re-published by NITTEC on NITTEC-owned properties• Ratio of pieces received vs. approved and re-published• Quantity of social media posts shared or re-posted• Capture data by geographical location• Capture data by format i.e., post, video, data, etc• Capture data by time period (hour, day, week,

month, year)


Keep travelers informed Publish 3rd-party & user-generated content (UGC)

21




Publish alerts related to information accuracy • The designed accuracy for a real-time information program shall be 85 percent accurate at a minimum, or have a maximum error rate of 15%

Publish alerts related to information availability • The designed availability for a real-time information program shall be 90 percent available at a minimum

Timely travel alerts


Publish alerts related to construction activities • The timeliness for the availability of information about full construction activities that close or reopen roadways is 20 minutes or less (10 minutes if in Metropolitan areas)

Publish alerts related to travel time information • The timeliness for the availability of travel time information along limited access roadways segments in Metropolitan areas is 10 minutes or less (from time the travel time calculation is completed)

Publish alerts related to roadway or lane blocking incidents

• The timeliness for the availability of information about lane blocking incidents is 20 minutes or less (10 minutes if in Metropolitan areas)

Publish other alerts as needed (e.g., Amber, etc.) • The timeliness for the availability of information for other alerts is 20 minutes or less

Include information updates on 511 and website • Publish within 15 minutes of status change


Keep travelers informed Maximize speed of publication of public alerts per anticipated federal standards


MANAGE AND OPTIMIZE TRAFFIC FLOW

Managingtrafficmobility


Measure traffic mobility via Travel Time Index (TTI) • Average conditions indicating how much longer travel times are on average during congestion compared to during free-flow travel times

• For US highways, free flow travel time is calculated as 55 mph• For Canadian highways, free flow travel time is calculated using 100 km/h and 60 km/h, based on certain roads

Enhance mobility through more accurate planning time estimates via Planning Time Index (PTI)

• The amount of extra time a traveler should allow to ensure an on-time arrival 95% of the time

Measure Free Flow Travel Time • Estimated travel time when traveling at the posted speed limit

Congested Hours (Daily Avg.) • The average number of hours between 6am – 10pm in which instrumented road sections show average speeds below a specified threshold

• For US highways, congestion threshold travel time is calculated as 45 mph• For Canadian highways, congestion threshold travel time is calculated using 80 km/h and 64 km/h, based on certain roads


Optimizetrafficflow Minimize additional required travel time

23

MANAGE AND OPTIMIZE TRAFFIC FLOW, Continued


Freight traffic (i.e., when capability to capture this data becomes available)

• Quantity of freight vehicles • Volume of goods transported (metric tons)• Cumulative trips by individual freight operators• Capture data by source & destination (US or Canada)• Capture data by company affiliation

Freight traffic mobility via Truck Travel Time Reliability (TTTR) Index

• The TTTR ratio will be generated by dividing the 95th percentile time by the normal time (50th percentile) for each segment. Then, the TTTR Index will be generated by multiplying each segment’s largest ratio of the five periods by its length, then dividing the sum of all length-weighted segments by the total length of Interstate.

• Reporting is divided into five periods:• Mondays through Fridays morning peak (6-10 a.m.)• Mondays through Fridays midday (10 a.m.-4 p.m.) • Mondays through Fridays afternoon peak (4-8 p.m.) • Weekends (6 a.m.-8 p.m.) • Overnights for all days (8 p.m.-6 a.m.)

Enhance freight movement on the Interstate system


Measurefreighttrafficflow Minimize additional required travel times


Trafficcongestion

Reducingcongestionoffreighttrafficatbordercrossings


Deploy Green Lanes Reduced inspection time and waiting time


Peak hour excessive delay (PHED) • Excessive delay will be based on travel time at 20 miles per hour or 60 percent of the posted speed limit travel time, whichever is greater, during in 15-minute intervals per vehicle.• Peak travel hours under this rule will be:

• Morning period is 6-10 a.m. local time on weekdays • Afternoon period is 3-7 p.m. or 4- 8 p.m. local time


Maximize “green lane” participation • Quantity of total enrolled participants• Quantity of freight drivers using green lanes• Average improved border crossing times relative to non-participating freight traffic• Capture data each bridge

• Lewiston-Queenston Bridge• Peace Bridge• Rainbow Bridge

• Capture data by operator• Capture data by time period (hour, day, week, month, year, holiday periods)

Maximize program integrity • Quantity of green lane random inspections• Quantity of green lane participants who fail random inspections

REDUCE CONGESTION ON THE REGIONAL TRANSPORTATION NETWORK


Reducetrafficcongestion Measuretrafficcongestioninurbanareasofpopulation > 200,000

25



Border crossing times at each border



Average crossing time • Average time from arrival to completed crossing• Capture data each bridge

• Lewiston-Queenston Bridge• Peace Bridge• Rainbow Bridge

• Capture data by type of vehicle• Capture data by time period (hour, day, week, month, year, holiday periods)

Incidence of border crossing delay • Percentage of vehicle traffic that experience delays• Reports on categories:

• No delay • 0-60 minutes • 60-120 minutes• Over 120 minutes

• Capture data each bridge• Lewiston-Queenston Bridge• Peace Bridge• Rainbow Bridge

• Capture data by type of vehicle • Capture data by time period (hour, day, week, month, year, holiday periods)


Reduce congestion Reduce delays at border crossing


Coordinating construction projects across the region


Project coordination • Quantity of projects in process• Quantity of projects detected not coordinated under NITTEC process• Capture data by NITTEC member• Capture data by time period (hour, day, week, month, year, holiday periods)

Maximize member participation • Quantity of logins and views• Capture data by NITTEC member• Capture data by project• Capture data by time period (hour, day, week, month, year, holiday periods)

Enhance collaboration on upstream planning • Time elapsed between project entry into NITTEC system and project commencement

Number of projects in process • Quantity of projects in process• Capture data by location• Capture data by time period (hour, day, week, month, year, holiday periods)





Reducetrafficimpactfromprojects Quantity of coordination

27



Coordinatingtrafficduringplannedeventsacrosstheregion

REDUCE CONGESTION ON THE REGIONAL TRANSPORTATION NETWORK, Continued


Project coordination for planned public events • Quantity of events in process• Qty of events detected not coordinated under NITTEC process• Capture data by NITTEC member and event organizer• Capture data by time (hour, day, week, month, year, holiday periods)

Maximize member coordination • Quantity of NITTEC member logins and views• Capture data by NITTEC member• Capture data by project• Capture data by time (hour, day, week, month, year, holiday periods)

Traffic impact from public events • TTI and mobility metrics compared to free-flow• Quantity of lane closures or restrictions and duration• Quantity of road closures and duration• Quantity of alternative route deployments and duration• Capture data by event• Capture data by location• Capture by time (hour, day, week, month, year, holiday periods)


Managetrafficfromlargepublicevents Reducetrafficandcongestion


Regional signal coordination


Regional traffic signal presence • Quantity of regional traffic signals• Percentage of traffic signals with connectivity• Capture data by make and model• Capture data by owner and locations• Quantity of regional traffic signals with remote management capabilities

Regional traffic signal capability • Quantity of regional traffic signals with remote management capabilities Percentage of traffic signals with capability to change timing either using adaptive algorithms or by receiving command from ATMS• Percentage of signals NITTEC can remotely manage • Capture data by make and model• Capture data by owner and locations



Improveregionaltrafficflow Capabilitytocoordinatetrafficsignals

29


Variable speed limits • Road miles where this measure is available• Quantity of deployments• Average duration of deployments• Capture data by owner and locations• Capture data by time period (hour, day, week, month, year, holiday periods)

Hard shoulder running • Road miles where this measure is available• Quantity of deployments• Average duration of deployments• Capture data by owner and locations• Capture data by time period (hour, day, week, month, year, holiday periods)

Traffic impact from deployment • TTI and mobility metrics compared to free-flow• Quantity of traffic incidents during deployment• Capture data by location• Capture data by time period (hour, day, week, month, year, holiday periods)

Deploymentoftrafficmitigation



ManagetrafficcongestionviaActiveTrafficManagement (ATM) techniques

Deployactionstoreducetrafficcongestion


Measuring road safety



Improve road safety Reducetrafficincidents

IMPROVE SAFETY AND OPERATIONS ON THE REGIONAL NETWORK




Traffic incidents in the region • Quantity of traffic incidents detected• Incidents per vehicle mile traveled • Serious injuries per vehicle miles traveled • Fatalities injuries per vehicle miles traveled• Capture data by location i.e., roadway segment• Capture data by vehicle type• Capture data by time period (hour, day, week, month, year, holiday periods)

Incident impact • Quantity of serious injuries• Quantity of serious fatalities• Quantity of disabled or overturned trucks• Capture data by location i.e., roadway segment• Capture data by vehicle type• Capture data by time period (hour, day, week, month, year, holiday periods)

Open roads • Quantity of days since most recent incident• Quantity of days since most recent road blockages due to an incident• Most consecutive days without incidents• Most consecutive days without road blockages • Capture data by location and roadway segment• Capture data by time period (day, week, month)

31

Develop enhanced incident detection capabilities


Faster incident detection and response Time from incident occurrence to detection

IMPROVE SAFETY AND OPERATIONS ON THE REGIONAL NETWORK, Continued




Incident detection • Type of incident (per categories for planned vs. un-planned incident types)• Time of incident occurrence• Elapsed time between occurrence and detection• Capture data by location• Capture data by time period (hour, day, week, month, year, holiday periods)

Incident severity (i.e., for traffic collisions) • Quantity of incidents for each category of severity• Minor - Typically one or two vehicle crashes with no or very minor injuries (expected lane closures of less than 30 minutes)• Intermediate - Typically multiple vehicle crashes involving injuries (expected duration or lane closure of greater than 30 minutes and less than 2 hours)• Major – Typically crashes involving hazardous ma-terials, fatalities, tractor trailers or full road closures with detouring of traffic (expected duration or lane closure of greater than two hours)

• Capture data by location i.e., roadway segment• Capture data by vehicle type• Capture data by time period (hour, day, week, month, year, holiday periods)


Accelerate incident response in the TOC


Faster incident detection and response Time from incident detection to response


Incident verification • Elapsed time from event detection to verification• Achieve target of response > 1 minute • Capture data by location i.e., roadway segment• Capture data by vehicle type• Capture data by time period (hour, day, week, month, year, holiday periods)

Incident notification • Elapsed time from event detection to verification• Achieve target of response > 1 minute • Capture data by location i.e., roadway segment• Capture data by vehicle type• Capture data by time period (hour, day, week, month, year, holiday periods)

33

Coordinatingtrafficduringunplannedeventsacrosstheregion


Managetrafficaroundunplannedevents Reducetrafficandcongestion





Project coordination for unplanned traffic events • Quantity of unplanned events under NITTEC• Capture data by event type and severity• Capture data by time period (hour, day, week, month, year, holiday periods)

Maximize member coordination • Quantity of NITTEC member logins and views• Capture data by NITTEC member• Capture data by discreet event• Capture data by time period (hour, day, week, month, year, holiday periods)

Traffic impact from unplanned events • TTI and mobility metrics compared to free-flow• Quantity of lane closures or restrictions and duration• Quantity of road closures and duration• Quantity of alternative route deployments and dura-tion (if deployed)• Capture data by event• Capture data by location• Capture data by time period (hour, day, week, month, year, holiday periods)


Optimizeincidentresponseinthefield


Faster incident response Time from incident detection to response


Arrival times • Arrival headway (A key metric to help determine how many services patrol vehicles, where they should patrol (beat) and number is to determine what is the maximum headway permitted)• Elapsed time event notification to first responder arrival• Average distance traveled to event• Capture data by location i.e., roadway segment• Capture data by incident type and severity• Capture data by responder (type and organization)• Capture data by time period (hour, day, week, month, year, holiday periods)

HELP performance • HELP personnel first on the scene vs others • Average response times• Average clearance times• Average incident times• Data is reported for incidents with HELP assistance vs. without HELP assistance• Data is reported for specified road segments and compared across calendar years• Separate HELP data for truck incidents • Capture by type of HELP service (if delivered)• Capture data by vehicle type• Capture data by location i.e., roadway segment• Capture data by incident type and severity• Capture data by time period (hour, day, week, month, year, holiday periods)

Incentive times (i.e., when incentive programs are deployed)

• Increased speed (less elapsed time) by incentivized responders vs. non-incentivized responders• Capture data by location• Capture data by incident type and severity• Capture data by responder (type and organization)• Capture data by time period (hour, day, week, month, year, holiday periods)

35

Manage incident duration


Reduce incident duration and faster clearance Time from incident response to normal conditions





Incident clearance times • Time of roadway clearance • Time elapsed from event occurrence to clearance

• Minor – Roadway blockage duration of less than 30 minutes• Intermediate – Roadway blockage duration of greater than 30 minutes and less than 2 hours• Major – Roadway blockage duration of greater than 2 hours

• Capture data by each incident• Capture data by location i.e., roadway segment• Capture data by incident type and severity• Capture data by responder (type and organization)• Capture data by time period (hour, day, week, month, year, holiday periods)

Roadway blockage • Quantity of lanes blocked or closed per incident• Capture data by each incident


Reduce secondary incidents

Roadway conditions detection


Reducetrafficincidents Fewer secondary incidents at incident locations


Enhanced weather detection Detect&measurefactorsaffectingroadconditions


Secondary incidents • Quantity of secondary incidents• Severity of secondary incident• Capture data by location i.e., roadway segment• Capture data by vehicle type• Capture data by time period (hour, day, week, month, year, holiday periods)


Inclement weather • Presence of rain, snow, or other weather events adversely affecting road conditions • Elapsed time to detection (retroactively measured)• Elapsed time to verification• Elapsed time to notification• Capture data by weather event type• Capture data by location i.e., roadway segment• Capture data by time period (hour, day, week, month, year)

Roadway conditions • Presence of non-weather road condition factors • Elapsed time to detection (retroactively measured)• Elapsed time to verification• Elapsed time to notification• Capture data by event type• Capture data by location i.e., roadway segment• Capture data by time period (hour, day, week, month, year, holiday or special event)

37

Develop incident reduction capabilities


Preventtrafficincidents Ability to detect occurrence of high-risk conditions



Identify areas of highest risk • Quantity of incidents by location• Capture data by location characteristics categories, i.e., roadway type, speed limit, visibility • Capture data by vehicle type• Capture data by time period (hour, day, week, month, year, holiday periods)

Correlated highest-risk factors • Quantify presence of adverse conditions • Capture data by category of conditions, e.g., sunlight, fog, rain, snow, ice, temperature, etc.• Capture data by time period (hour, day, week, month, year, holiday periods)

Create incident predictive models to identify when risk threshold is met (specific locations)

• Quantify degree of incident risk when highly-correlated conditions are met

Forecast accuracy • Quantify incidents that risk conditions are present


Trafficsafetytrainingandassessment

Condition of bridges and roadways (national highway system)


Improve safety Enhanced safety capabilities


Safe road conditions Proper bridge and roadway maintenance


Safety training • Quantity of first-responder personnel who attend traffic and highway safety training events• Quantity of available events• Capture by organization• Capture by event type

FHWA incident self-assessment • The percentage results of the FHWA Traffic Incident Management Self-Assessment




Bridge conditions • Performance metrics using National Bridge Inventory (NBI) condition ratings for Deck, Superstructure, Sub-structure, and Culvert• Percentage of NHS bridges in Good condition• Percentage of NHS bridges in Poor condition• Capture data by location i.e., bridge• Capture by time period (month, year)

39

Capturing data on regional transportation network usage


Know and understand transportation network usage and demand through measurement

Acquire complete and accurate usage information

BECOME OMNISCIENT ABOUT THE REGIONAL TRANSPORTATION NETWORK


Capture usage of regional transportation networks • Presence of vehicles (in specified location)• Volume of vehicles (quantity per hour)• Speed of vehicles i.e., average MPH• Occupancy (traffic density)• Capture data vehicle type• Capture volume goods transported by freight• Capture data by geographical location and roadway• Capture data by time period (hour, day, week, month, year)

Maximize geographical coverage of data collection capabilities

• Quantity of total sensor deployments• Quantity of new sensor deployments• Quantity of roadway miles instrumented for data collection (100% = each 1/2 mile in urban areas or each 1 mile in rural areas):

• full coverage > 75% • partial coverage = 25% - 75%• some coverage < 25%• no coverage

• Quantity of roadway miles not instrumented for data collection where data can be estimated• Quantity of roadway miles not instrumented for data collection where data cannot be estimated• Capture data by geographical location i.e., by corridor, individual roadway sector, town, etc. • Capture data by time (day, week, month, year)

Ensure maximum data accuracy • Average uptime for instrumentation (Goal = 99.9% for each implement)• Quantity of periodic manual test counts• Percentage of accuracy between manual test counts and reports counts 95% or higher for volume and 90% for speed• Capture data by each metric tested• Capture data by time and duration of each test


Complete data coverage of key transportation corridors in the region


Eliminate roadway surveillance gaps Visualknowledgeoftrafficactivity


Traffic flow viewing capacity • Percentage of roadway miles with video coverage• Percentage of roadway miles with video coverage within high-priority corridors (goal = 100%)• Capture data by location i.e., roadway segment• Capture data by owner• Capture data by time period (hour, day, week, month, year, holiday periods)

Video coverage • Quantity of total cameras on roadways• Average uptime (Goal = 99.9% for each camera)• Percent of cameras with remote PTZ capabilities • Percent of cameras feeding into NITTEC • Percent of road miles covered by NITTEC feeds• Quantity of cameras not accessible by NITTEC• Capture data by location i.e., roadway segment• Capture data by owner• Capture data by responder (type and organization)• Capture data by time period (hour, day, week, month, year, holiday periods)

Video usage • Number of NITTEC members accessing NITTEC cameras• Number of total video feeds accessed• Number of total video feeds to public site• Capture video data by location i.e., roadway • Capture video data by owner• Capture video data by responder (type and organization)• Capture video data by time period (hour, day, week, month, year, holiday periods)

41

TappingthecollectivedataofNITTECmembersforgreatermutualbenefit

Automated process and sharing


Ubiquitous info and data across NITTEC Complete anytime, anywhere access to all data


Faster response capabilities Enhanced operational capabilities

BECOME OMNISCIENT ABOUT THE REGIONAL TRANSPORTATION NETWORK, Continued


Development of NITTEC data strategy • Completion and deployment (i.e., non-recurring)

Data warehouse capabilities • Completion of database capability development• Completion of establishing common data definitions and format standards• Completion of data feed capabilities• Completion of data security implementation • Regular completion of testing processes

Automated data feeds in • Number of NITTEC members providing performance measures data feeds to NITTEC

• Goal = 100% of all data • 75% - 99% of all data• 50% - 75% of all data• 25% - 50% of all data• Below 25% of all data• no data

• Percentage of data feeds automated vs. manual


Automated process documentation with a single single-point of data entry

• Quantity of NITTEC members receiving automated event and incident notifications• Quantity of total incidents with logged events and notifications delivered electronically vs. manually• Capture data by organization• Capture data by event / incident type• Capture data by time period (hour, day, week, month, year)


Customizable visualization dashboard and analytics tools with automated reporting


Outcome-based management Automatic access to KPI information


Established KPIs • Completion of KPI development• Completion of identifying required data• Completion of pre-defined KPI calculations

Automated KPI dashboards • Completion of sourcing automated data• Development of cloud-based dashboard tool• Completion of test and verification processes• Completion of launch to NITTEC members• Capture data by organization• Capture data by time period (day, month, year)

Dashboard usage • Quantity of dashboard logins• Average duration of usage• Percentage of NITTEC member organizations who use the tool• Capture data by organization• Capture data by time period (day, month, year)

Automated reports • Quantity of automated reports generated• Capture data by organization• Capture data by time period (day, month, year)

43

ACTIONS REQUIRED TO ACHIEVE PERFORMANCE MEASURES CAPABILITIES

Achieve cost savings by implementing shared ownership and usage of common services and equipment.

NITTECmembersdeploysensorstofilldataandinformationgap

Action item Now 2-3 yrs 4-7 yrs

Accelerate the collection of all currently available transportation and relevant data cross the region for NITTEC to centrally store, manage and analyze

X

Enact integrated and automated data collection across Coalition members X

Initiate required upgrades to IT infrastructure, systems and software required to support broader data collection, management and analytical processes

X


Determine high-priority corridors for instrumentation and key point of deploy-ment (i.e., ideally every half mile, every mile at minimum)

X

Deploy sensors to collect traffic data at designated locations X

Acquire probe data from traveler mobile devices X

Deploy sensors and expand probe data acquisition to other priority roadways X

Achieve 100% regional coverage of roadways with probe data and sensors X

NITTEC must take actions to support outcome-driven management and the required investments which will enable adequate data collection capabilities to support the aspirational metrics defined in the 2-3 year term.


Develop automated KPI dashboards

Data benchmarking

Deploy outcome-based management principles


Create automated dashboards to provide ongoing insights into performance X

Pre-defined calculations to enable automatic data feeds to populate dashboards X

Automated report generation for insights about progress toward all key outcomes; ability to create local or regional reports

X

Enable cloud-based access by NITTEC members to dashboards and raw data X

Publish KPI highlight reports for committee meetings (i.e., regular monthly reports)

X


Assess performance for establishing KPIs X

Establish interim averages and standards as performance benchmarks X

Establish target performance levels based on benchmarks X

Use performance benchmarks to mark progress and competitive position X

Comprehensive data management with data security, privacy, accessibility X


Elevate the role of performance measures in NITTEC operations and all committees by defining quantifiable metrics for success for outcome metrics and key process metrics and other data of interest

X

Enact data-driven management processes integrated into NITTEC operations with performance measures for management efficiency, effectiveness and accountability

X

Define clear definitions of success for each NITTEC work stream and which relate directly to strategic objectives

X

Clear definitions of “key performance indicators” to reflect performance against objectives

X

Implement initial metrics of Performance Management Plan X

Fully implement aspirational metrics of Performance Management Plan X


Global Dynamic Group, LLC (GDG) provides Internet of Things (IoT) consulting services to clients in the public and private sectors. GDG was founded in 2005 with headquarters in New York City, New York and an office in Buffalo, New York. In addition to projects in Western New York, GDG has consulted for Federal government sponsored university research centers in New York and New Jersey related to the deployment of connected and autonomous vehicles and supported several IoT related projects in New York State. GDG and SwRI have worked together since 2014. GDG and SwRI share a deep conviction in maintaining independence. GDG and SwRI do not form long-term partnerships with other vendors. GDG and SwRI form teams that provide the best value and service for a given project based on a client’s needs. For additional information, please visit http://www.gdgiot.com.

Southwest Research Institute (SwRI) is headquartered in San Antonio, Texas. It is one of the oldest and largest independent, nonprofit, applied research and development (R&D) organizations in the US. Founded in 1947, SwRI is governed by a board of directors, which is advised by approximately 100 trustees. SwRI has a staff of approximately 2,700 that specialize in the creation and transfer of technology in engineering and the physical sciences. A leader in design, development, and deployment of Advanced Traffic Management Systems (ATMS), SwRI has been implementing ATMS since the early 1990s. SwRI integrates new technologies and equipment into existing ATMS and Traffic Management Centers (TMCs). We are focused on integrating intelligent vehicle development activities including vehicle-to-vehicle communications, vehicle-to-infrastructure communications and autonomous vehicles. For additional information, see: http://www.swri.org/intelligent-transportation-systems

2017 performance measures plan - nittec

Documents