Traffic Monitoring Guide

1. DBP Traffic Monitoring Guide 2012 Update Roadway Transportation Data Business Plan May 9 , 2013 presented to Data Palooza U.S. Department of Transportation By Anita Vandervalk, PE, PMP

2. Introduction • The Data Business Plan Story: • What is the Problem? • What did we do? • What were the Outcomes? • What were the Recommendations? • What would be the benefits?

3. Introduction • What is the Problem? • FY2010 - Office of Operations identified need to investigate consistencies between U.S. DOT Data Programs • What did we do? • Developed White Paper on Needs and Gaps in the Operations and Coordination of U.S. DOT DCM Programs • Developed a Data Business Plan to mitigate Data Gaps

4. Introduction • What was the Outcome of the White Paper? • Data Gaps – resulting from: • Inconsistencies in the definition of performance measures(e.g. travel time reliability); • Use of default valuesfor data elements, in some cases the data is not independently validated; • Redundancies in the collections efforts(inventory is needed); • Inconsistencies in location referencingof data; and • Varying standards • Coordination Gaps– due to: • U.S. DOT staffs are often unawareof what projects others are working on. Resulting in duplication of studies (funding & wasted efforts) • Data Standards and Governance Gapsto facilitate integration – these include: • Minimum data quality standards for: Data collection & processing

5. Introduction • What was the Recommendation? (cont.) • Goals of the Data Business Plan are to: • Provide leadership by suggesting or offering best data collection / management practices to the primary data collectors • Foster coordination and communication across U.S. DOT offices to: • Avoid duplications /redundancies in the collections efforts of data related programs • Address inconsistencies in the definition of performance measures(e.g. travel time reliability) • Address inconsistencies in location referencing of data • Address varying standards

6. Introduction • What would be the Benefit? • More transparency and accountability • More efficient ways to locate and take advantage of available data and information • Standard data integration methods from multiple sources • Processes and systems that: • Reduce redundancy and • Promote consistency in data results • More timely data and information • More department-wide spatial data tools

7. Overview of Data Business Plan • Purpose of the DBP • Address gaps identified in the Data Gaps paper (e.g. improve the coordination and communication mechanism across U.S. DOT offices to avoid investing resources to the same or similar types of data related programs); • Serve as prototype for other U.S. DOT offices; and • Provide leadership by suggesting or offering best data collection/management practices to primary data collectors.

8. Overview of Data Business Plan • Data Business Plan Components • Recommendations to address U.S. DOT needs in serving data end-users and address overlaps and gaps • Best practices and recommendations on data services and knowledge management tools and procedures • Recommendations for coordinating data-related efforts within US DOT with the goal of reducing redundant or uncoordinated efforts • Recommendations for improved governance and coordination among data-related programs and offices within U.S. DOT ***Designed to be a “living document”***

9. Overview of Data Business Plan • Goals of the DBP: • GOAL 1. Improve the coordination and communication mechanism across U.S. DOT and FHWA offices involved with roadway travel mobility data to avoid investing resources in the same or similar types of data related programs. • Objective 1.1. Identify gaps and redundancies in roadway travel mobility data programs. • Objective 1.2. Devise “rules of engagement” regarding collaboration of the data functions for roadway travel mobility data.

10. Overview of Data Business Plan • Goals of the DBP (cont.): • GOAL 2. Improve the coordination of the data capture activities associated with ITS JPO-sponsored research in wirelessly connected vehicle technologies with roadway travel mobility data programs within U.S. DOT and FHWA. • Objective 2.1. Identify how current and planned data from the connected vehicle initiative can support existing roadway travel mobility data programs. • Objective 2.2. Identify how data from roadway travel mobility data programs within U.S. DOT and FHWA can support the connected vehicle initiative. • Objective 2.3. Identify existing/future data inventory and data structures/ policies/governance practices that could be applicable to the Research Data Exchange.

11. Data Management Practices • Data Governance • Data Acquisition • Data Quality • Data Standards • Business Analysis Tools • Data Privacy and Security • Data Storage and Access

12. Data Management Practices • Traceability • Performance Measures • Risk Assessment • Value of Data Programs • Knowledge Management

13. Stakeholder Needs and Gap Analysis: Stakeholder Group • ITS JPO • BTS • Office of Human Environment – Bike/PedProgram • HPPI • Office of Operations – Road Weather Management • Office of Operations – HOTM • TFHRC • FAA • Office of Freight Management & Operations • FMCSA • Research & Development – Visualization • Office of Performance Management

14. Stakeholder Needs and Gaps Analysis • Areas for Improvement • Data Scope (Gaps) • Data Acquisition and Updating • Data Quality • Data Standards • Business Analysis Tools • Data Privacy and Security • Data Storage and Access • Internal Coordination • Traceability • Performance Measures • Data Governance Framework • Data Catalog • Value of Data Programs • Knowledge Management System

15. Data Coordination Framework • Major Components: • Formal designation of Mobility Data Coordination Group • Data Coordination Model Diagram • Roles and Responsibilities for Data Coordination • Rules of Engagement • Outreach Mechanisms

16. Data Coordination Framework Coordinates FHWA Data A. U.S. DOT with Governance Mobility Data Advisory Council Coordination Group D. Community of Interest (Internal) Data Data Data Data Data Data Value of Business Traceability Performance Risk Knowledge Governance Acquisition Quality Standards Privacy & Storage & Measures Data Analysis Assessment Management Security Access Programs Tools Infrastructure/Inventory Data Working Group Travel Data Working Group Climate Data Working Group Use Modal Data Working Group Connected Vehicle Data Capture Working Group E. Community of Interest (External) • Data Coordination Model Diagram

17. Overview of Data Governance Relationship of Data Governance Groups FHWA Data Governance Advisory Council FHWA Office of Operations Data Governance Team Roadway Travel Mobility Data Community of Interest Connected Vehicle Data Community of Interest

18. Mobility Data Coordination Group • Formal Designation of Mobility Data Coordination Group to coordinate on data issues: • Data gaps/overlaps in specific types of roadway mobility data • Infrastructure/inventory • Roadway travel mobility data (speed/volume) • Climate data • Modal data • Data capture activities associated with ITS JPO-sponsored research in wirelessly connected vehicle technologies • Cross-cutting data management issues that impact all data types • Data quality • Standards • Privacy/security

19. Rules of Engagement • Example Rules of Engagement • Understand and promote the value of data as a U.S. DOT-wide asset • Share RFPs for current and upcoming initiatives • Identify needs and opportunities to create links between data sets to support performance measurement and asset management purposes • Share current activities and best practices related to data strategies, policies, standards, metadata, architecture, procedures, and metrics • Develop data standards and stewardship recommendations for consideration by the FHWA Data Governance Advisory Council

20. Data Integration Test Pilots • Applicability of Connected Vehicle Data for National Performance Monitoring • Reconciliation of Speed Data from Multiple Sources • Intended outcomes • Creation of a link between an existing data set and a connected vehicle data set in the future, • Maximize integration of national data sets for performance measurement and asset management purposes, • Creation of value added to the Research Data Exchange or other USDOT research data sets, and • Documentation of lessons learned for the USDOT, State DOTs and regions.

21. Next Steps • Execute Data Business Plan Coordination • Conduct Integration Test Pilots • Execute Data Governance within FHWA Office of Operations

22. Questions