1 / 93

FHWA Integration of State, Tribal, and Local Safety Data

This guide provides information on the integration of safety data from various sources to meet user needs. It explores the benefits, data governance, and data business planning for seamless integration. The guide also includes case studies, work plans, and pilot studies to help agencies implement data integration projects successfully.

mporter
Télécharger la présentation

FHWA Integration of State, Tribal, and Local Safety Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FHWA Integration of State, Tribal, and Local Safety Data Guide and Data Business Planning Technical Assistance Traffic Records Forum August 2017

  2. Introductions

  3. Purpose and Goal • Understand the data integration process • Understand its development & implementation • Know its benefits • Fit into Data Governance & Data Business Planning • Develop a roadmap for data integration

  4. Data Integration • Link multiple data sources to meet users’ needs • Integration can take place: • Across jurisdictions • Among safety databases • Safety Data = Crash, Roadway, and Traffic

  5. All-Public Road Network of Linear Referenced Data • ARNOLD • Requirement for geospatial network • State responsible for: • All Public Non Federal Owned Highways

  6. Strategic Highway Safety Plan • SHSP needs to have a data emphasis area • Qualify for HSIP funding

  7. Subset of MIRE to be Collected The FHWA developed the MIRE, a recommended listing of roadway and traffic elements critical to safety management. • MAP-21 required the Secretary to establish a subset of the MIRE – Adjusted in FAST Act • The FDEs are categorized by roadway functional classification and surface type and include three tables, one each for non-local paved roads, local paved roads, and unpaved roads • Further refined into subcategories of data elements for road segments, intersections and interchanges

  8. Collecting and Using the MIRE FDEs • States shall incorporate specific quantifiable and measurable anticipated improvements for collection of MIRE FDEs into their State Traffic Records Strategic Plan update by July 1, 2017. • States shall have access to the FDEs on all public roads by September 30, 2026.

  9. Collecting and Using the MIRE FDEs States should develop strategies that consider: • The current status of MIRE FDE collection efforts • Appropriate data collection methodology • Coordination with other agencies • Prioritization criteria for collecting MIRE FDE • The schedule and estimated costs for data collection efforts Planning effort should be specific, measurable, achievable, realistic and time-bound strategies for the collection, maintenance, and management of MIRE FDE

  10. Prioritization • Base layer • Crash Location • MIRE FDE

  11. Background State Safety Data System Safety Data MIRE FDE Roadway Data System Analysis and Evaluation Highway Safety Improvement Program All Public Roads Common Base Map Crash Data System Traffic Data System

  12. Benefits of Safety Data Integration

  13. Benefits of Safety Data Integration • Availability • Timeliness • Accuracy and Integrity • Consistency and Clarity • Completeness • Reduce Duplication

  14. Benefits of Safety Data Integration(continued) • Faster Processing Time • Lower Data Acquisition and Storage Cost • Informed and Defensible Decisions • Enhanced Program Development • Greater Accountability

  15. Current Challenges • Lack of formal processes • Partnerships across agencies • Move to all public roads network

  16. Data Business Planning • A formal planning process • Describes data needs and how to fill them • Includes a roadmap to completion • Action / implementation plan • Inclusive and cooperative

  17. Data Management & Governance • Data Management: Top-down decisions on IT environment, methods, and tools. • Data Governance: Implements those decisions in specific domains or enterprise-wide. • Stakeholders: The people who collect, store, extract, translate, load, and use the data.

  18. Integration of State and Local Data • Built on the results of the RSDPCA • Research, case studies, and pilot studies • Resulted in guidance to assist agencies

  19. Case Studies • Identified States & agencies for case studies • Identified potential candidates for pilot project • Researched noteworthy practices by States

  20. Case Studies

  21. Case Studies • Michigan’s Roadsoft • Ohio’s Location Based Response System • Tennessee Roadway Information Management System • Wisconsin Information System for Local Roadways

  22. Case Study Findings • Less duplication of data collection efforts • Many paths to safety data integration • States do best if they pay for the effort • Local input is required • Executive-level support is key

  23. Work Plans and Pilot Studies Fort Belknap Reservation/ Northern Plains TTAP

  24. Purpose of Work Plans • Develop a plan for implementation • Provide examples on how to structure a safety data integration project • A total of 6 work plans developed, of which 4 went on to full pilot studies

  25. Pilot Study & Work Plan Outcomes • Informational guide • Strategic plan • Nine-step data integration process

  26. Informational Guide for State, Tribal, and Local Safety Data Integration FHWA SA-16-118

  27. Purpose of the Guide • Provide easy-to-use information to support data integration efforts • Show examples from other States and agencies • Identify potential partner agency needs • Direct users to web resources • Make data integration approachable!

  28. Safety Data Integration

  29. Safety Data Integration Steps

  30. Technical Assistance Overview

  31. Purpose of Technical Assistance • Assist States in developing Steps 1–5 of data integration plan • Provide States with guidance on how to complete Steps 6–9

  32. Needs and Barriers Typical Needs • Integration of local data • Improved data quality on local roads • Improved asset management procedures • Data governance process • Analytic tool selection & training • Data business plan: collect, store, and use • Upper management buy in

  33. Needs and Barriers Barriers • Inter-office responsibilities • Staffing, capabilities, and availability of tools at local agencies • Institutional inertia

  34. Safety Data Integration:Steps 1 – 5

  35. Step 1: Lay the Foundation

  36. Objective • Bring together people responsible for managing safety related data and their consumers • ALL PUBLIC ROADS LRS • Crash Records • Roadway Inventory • Traffic Volumes • Identify Safety Data Users • Establish roles and responsibilities

  37. Potential Partners

  38. Challenges • Data silos • Proprietary interests of data owners or users • Support from all levels of management • Communication with all stakeholders • Partners’ business needs & reporting requirements vary

  39. Step 1 Summary • Secure the commitment of executive management • Forge partnerships • Establish needed MOUs and Data Sharing Agreements to establish expectations • Establish communication processes to inform and involve all stakeholders

  40. Step 2: Conduct Gap Analysis

  41. Objective • Document business needs and reporting requirements • Identify existing and future safety analysis tools • Generate list of supporting data requirements • Identify common data between departments • Compare available data sources • Identify needed improvements

  42. Challenges • Funding and development schedule trade-offs • Partnerships among agencies • Data gaps analysis shouldn’t be stand-alone • System life-cycle management & sustainability

  43. Data Gaps Analysis as Part of Data Governance Process • Integration steps 1-3 form a three-part cycle as an agency matures • Partnerships need to evolve as users’ needs change • Updated gap analysis can help with business planning and promote discussion Data Governance Lay the Foundation Conduct Gap Analysis

  44. Step 2 Summary • Establish a team to perform the gap analysis • Perform a survey of user needs and available data sources • Plan to repeat the gap analysis periodically • Recognize the interactions between forging partnerships, gap analysis, and data governance efforts

  45. Step 3: Establish Data Governance Process

  46. Objective • Formal process • Address data systems and management issues • Data definitions • Data standards • Lines of authority and ownership • Access rights and usage • Data lifecycles • Requires input from key stakeholders

  47. FHWA Data Governance Plan • Six Strategic Goals • Leadership • Quality • Prioritization • Cooperation • Flexibility • Utilization

  48. FHWA Data Governance Plan Management (top level decisions) Governance (implementation) Stewardship (the people) Stewardship Governance Management

  49. FHWA Data Governance Plan

  50. Data Governance Challenges Challenge • Data sharing may be new experience for some agencies • Control over data may be compromised • Roadways constantly change • All-Public-Roads expands data requirements • Queries are complex using distributed data

More Related