The HPMS Checklist Project and The Arnold Pooled Fund ... GIS_T_Session 5.4.1 Arnold and Checklist.pdf · The HPMS Checklist Project and The Arnold Pooled Fund Study ... coordinator)

The HPMS Checklist Project and The Arnold Pooled Fund Study

Update

2016 AASHTO GIS for Transportation Symposium

Session 5.4.1April 6, 2016

3:30 pm

7/22/2016

April 6, 2016Developing New Business and Operational Guidance Ensuring Timely and Quality HPMS Data Submittal

Project Overview

HPMS Submittal Process

3

Import

• Routes

• Sections

• Summary

• Estimates

• Metadata

Samples

• Import Samples

• Create TOPS

Validate

• LRS

• Samples

• Sections

Verify

• Samples Adequacy

• Expansion Factors

• Sample Data Item Check

• Reports

• Spatial Intersection

Submit

• Import Status

• Confirm Message

• Confirm Validations

• Submission Comments

Mapping

• Create Geometries

• Routes/LRS, Sections, TOPS, Samples, Validations

Project Description

FHWA’s Office of Highway Policy Information

Responsible for collecting, processing and disseminating HPMS data

Provides HPMS Field Manual

However no business or operational guidance

Business and Operational Guidance

Exemplary practices by State DOTs

Efficient, logical and practical business process

Self-certifying checklist

HPMS Submittal Project – Objectives

© 2015 -Economic

Development Research

Group, Inc.

5

Improve timeliness and quality of submittals

Establish a business process template that states can use to

organize themselves for updating and submitting HPMS

Improve FHWA’s understanding of state challenges and

obstacles in meeting requirements

Build relationships between FHWA SMEs and HPMS

coordinators

Reduce burden on FHWA to identify and resolve HPMS

quality issues

Improve accuracy and validity of highway needs forecasts

ChallengesHPMS is a subsidiary use of state data

State DOT data collection cycle may not correspond with HPMS cycle

State DOT mileage certification process can be time consuming

HPMS coordinators rely on other departments for much of their data

6

Study Panel Composition

Study Charter

Project RFP

State Contact

Montana Viki Wilson

North Carolina John Farley

Florida Tina Hatcher

Mississippi Jeanette Nichols

Minnesota Scott Patnode

Ohio David Blackstone

Utah Linda Massie

Virginia Brak Dunn

Tennessee David Lee

Objectives and Roles of Study Panel

Exemplary Practices Manual

Respond to questionnaire

Provide input on draft manual

Business Process Manual

Provide insight and feedback on current DOT processes

Provide input on draft manual

HPMS Data Quality Self-certifying Checklist

Provide input

Study Panel’s Role

Time frame – 12 months

Two (2) in-person meetings

Six (6) teleconference/webinar meetings

Approximate time commitment

8 hours per month

Development of Practices Manual

Conduct interviews with nine state DOTs

HPMS Coordinators

HPMS Providers (Staff responding to data requests from HPMS

coordinator)

Travel Monitoring

Road Inventory

Pavement Management

GIS/LRS management

Division Manager (Individual(s) who manages the activities of the

HPMS Coordinator’s Division)

FHWA Division

Development of Practices ManualProcess Oriented Questions

◦ Context

◦ Communications

◦ FHWA Coordination

◦ Work Flow

◦ Enterprise Management

◦ Community of Practice

◦ Process Institutionalization

Practice Oriented Questions◦ Roadway Inventory

◦ Pavement Data

◦ Traffic Data

◦ Sampling

◦ Data Imputation

Business Process Manual

Develop Manual of Practice

Agency actions

Timelines

Technical processes

Coordinating activities

Working with partners

Quality control/quality assurance

Self-Certifying Checklist

Help verify all data elements are reviewed

Ability to assign and execute QA/QC procedures

Provide explanations for unresolved issues

Project OverviewObjective:To assist States in developing one of their significant capital assets – a statewide geospatial representation of their public road system. To build a nationwide ARNOLD this pooled fund study is open to a variety of approaches; however certain planning steps are required.

The Many Faces of ARNOLD:

14

The PFS Team

15

Joe Hausman – PFS Project ManagerTom RoffJustin ClarkeStuart ThompsonRobert PollackMark Sarmiento

John Wisdom - Deputy PFS Manager (NM, FL, PA)

Greg Yarbrough – PFS Manager (CA, UT, GA)Bill Land – State Project Manager (MN)Brian Sovik – State Project Manager (KS)Kim Hubble – State Project Manager (CO)

Federal Programs Support

16

Participating States

17

CaliforniaColoradoFloridaGeorgiaKansasMinnesotaNew MexicoPennsylvaniaUtah

18

Project Starts

State Project Start Project Completion

California Jan-2015 Aug-2016

Colorado May-2016 Aug-2016

Florida Nov-2015 Dec-2016

Georgia Apr-2016 Dec-2016

Kansas Mar-2015 Apr-2016

Minnesota Apr-2015 May-2016

New Mexico May-2015 Apr-2016

Pennsylvania Jan-2016 Sep-2016

Utah Jan-2016 Oct-2016

CaliforniaLRS System Development Plan

19

Task 1 Task Objectives

Business Needs/Requirements Conduct analysis of Caltrans’ LRS requirements, data structures, maintenance, data sharing and federal requirements regarding geospatial data

Develop a document summarizing and prioritizing Caltrans’ LRS business needs and technical requirements

Develop a document summarizing Statewide LRS requirements


20


Analysis of Alternatives Conduct a best practices review and develop whitepaper

Conduct a comparative analysis of industry standard LRS solutions to meet Caltrans requirements

Develop and deliver business case analyses documentation

Develop document which contains results of solution comparative analyses


21


System Implementation Plan System design guidelineso Methods, specifications and standards,

data architecture, and LRS architectureo Organizational responsibilitieso Data pipelines

System integration plan Training plan System operations and maintenance plan


22

Business

Requirements

Caltrans LRS

Requirements

Statewide Local

Roads LRS

Requirements

State Best Practices

Review

LRS Functional

Requirements Matrix

Vendor Solution

Functionality

Solicitation

Vendor Response

to LRS Functional

Requirements

Matrix

Caltrans LRS Vendor

Response Analysis &

Selection of

Maintenance Platform

Caltrans LRS Enterprise System

Development Plan

Final Report & Executive Summary

ColoradoHPMS Data Elements Collection

23


Data Collection for Unpaved Roads • Review unpaved road inventory with CDOT. • Schedule and Perform field collection• Perform QA/QC procedures

ColoradoHPMS Data Elements Collection

24


Populate HPMS Data Elements • Review list of HPMS Data Elements to be populated o Define existing data sources for HPMS Data

Elementso Define methodologies for extracting data and

populating HMPS Data Elementso Define database format, schema and

domains for populating datao Document extraction methodologies and

data requirements.• Develop and document QA/QC procedures• Extract Roadway Inventory items and attributes• Perform QA/QC • Deliver database of HPMS Roadway Elements to

CDOT

FloridaARNOLD Network Development Assistance

25


Develop Plan for Building ARNOLD Define existing business data requirements Define existing data resources Identify potential external, non-proprietary

data sources for public roads Research and develop methodologies for

building all-road networko Document existing FDOT LRS

development practiceso Sources of milepoint datao Workflows and Toolso QA/QC procedures

Develop data requirements and methodology document


26


Build/Develop the Network Build all-roads network (geometry, attributes, LRS)

Develop tools (LRS, database, etc.) for building and maintaining network and associated data

Conduct Quality Control testing on networko Support for FHWA requirementso Support of FDOT business requirementso Support of other requirements

Deliver network development tools Deliver first version of all-roads network


27

Tasks 3 & 4 Task Objectives

Develop ARNOLD Maintenance Plan Identify network maintenance workflowso Network geometryo Network measureso Network attribute datao Roadway IDs

Develop ARNOLD maintenance plan

Update Network Test the Plan and update

GeorgiaLocal Government Coordination and Portal Planning

28


Local Agency Coordination Identify Georgia Stakeholders Interview Key Local Agencies (Workshop and

Webinars) Conduct Local Stakeholder Data Gap Analysis Develop Data Supply Chain Model(s) Deliver Findings and Recommendations

Report


29


GDOT ARNOLD Portal Planning Define Portal Goals Define Data Resources and Requirements Develop System Workflows

Front End Workflows Back End Workflows Develop QA/QC protocols and acceptance

criteria for Locals and GDOT

Document Training Requirements


30

Tasks 3 & 4 Task Objectives

Design ARNOLD Portal Architecture Develop System Architecture Develop Implementation Strategy Deliver Technical Requirements and

Development Plan

Final Report and Executive Summary Develop Final Technical Report from Tasks 1-3

Develop ARNOLD Portal PowerPoint Presentation

Develop Executive Summary Findings Report

KansasARNOLD Implementation Plan

31


Implementation Plan Technical Requirements

Define Business Data Requirements Develop ARNOLD Data Model Requirements Develop Linear Reference System Methods

and Strategy Develop Implementation Plan Deliver Geospatial Technical Requirements

Documentation


32


Define Information Pipelines and Local Agency Coordination

Identify Kansas Stakeholders Interview Local Agencies Conduct Local Stakeholder Gap Analysis Conduct KDOT Gap Analysis


33

Task 3 & 4 Task Objectives

Project Pilot Define the Pilot Project Develop Pilot Project Plan Define Pilot Requirements and Measures Execute Pilot Project Develop Pilot Project Findings Report

Deliver Final Implementation Plan Develop draft Final Implementation Plan with Data Model Diagrams

Develop and deliver Final Report with Executive Summary

MinnesotaARNOLD Geospatial Plan

34


Shared Centerline Geospatial Requirements

• Develop White Paper for State DOT local data collection

• Define Portal Goals • Host Technical Solutions Sub-Group Meetings • Develop System workflows (for Locals and

MnDOT)• Define Data Resources and Requirements• Conduct Gap Analysis (MRCC, MDOT,

ARNOLD)• Develop Portal Data Model• Develop QA/QC protocols and acceptance

criteria (for Locals and MnDOT)

MinnesotaARNOLD Geospatial Portal Plan

35


Long Term Strategy for Improving the ARNOLD Network

Assess Shared Centerline Pilot Data from local stakeholders.

Develop whitepaper review of new and emerging data collection technologies and methodologies.

Develop summary of recommendations

New MexicoARNOLD Development and Strategic Plan

36


All Roads Network Development Planning and Review

Conduct a review and gap analysis of NMDOT business data required to support HPMS and ARNOLD reporting requirements.

Define ARNOLD Data Model and local road measure specifications.

Develop LRS Route ID in conjunction with NMDOT Staff

Create a Development Plan which identifies appropriate spatial and attribute (e.g. Road Name, Functional Class, urban boundaries, Ownership, Facility Type, etc) resources as well as procedures for creating the initial all roads network that will meet federal reporting requirements.


37


All Roads Network Development Assist in the development of the State system dual carriageways, ramps and LRS.

Develop the all roads network centerline files and LRS. o Local and State system centerline

integrationo Perform Network Rules and Topology

QA/QCo Assign LRS ID Key to networko Develop local road measures and LRS

Perform network system and data connectivity testing and validation.

Engage in Pilot submission to FHWA


38

Task Task Objectives

Develop ARNOLD Maintenance Strategic Plan

Develop a high-level plan for migrating the all roads network to Esri Roads and Highways

Deliver the NMDOT ARNOLD Strategic Maintenance Plan

PennsylvaniaData Integration – ARNOLD Development

39


Develop Plan for building the ARNOLD Network

Develop and document practices for developing Liquid Fuels and Non-Liquid Fuels networkso Sources of network data (geometry)o Sources of milepoint datao Procedures for building LRS/measures,

route IDso QA/QC procedures

Develop procedures for integrating Liquid Fuels and Non-Liquid Fuels networks

Develop methodology document for building the all-roads network


40


Build/Develop the ARNOLD Network

Perform QC on Liquid Fuels network LRS Develop LRS on Non-Liquid Fuels network Perform QC on Non-Liquid Fuels network

geometry, LRS and attribute datao Identify remaining public roads not included in

current networko Identify data sources for missing public roads

Integrate Liquid Fuels and Non-Liquid Fuels networks to create ARNOLD network

Perform QC on combined network (topology, LRS)

Deliver first version of all-roads network


41


Develop ARNOLD Maintenance Plan Identify network maintenance workflows Network geometry Network measures, IDs, other

Develop maintenance plan for maintaining ARNOLD network

UtahGeospatial Data Assessment and Local Stakeholder Involvement Program

42


UDOT Geospatial Data Summary Assessment

Interview UDOT Divisions and Districts to identify LRS business needs to support management of local roads.

Define high-level workflows to support data management and reporting activities by UDOT and local stakeholders.

Develop Executive Summary Findings Report summarizing UDOT’s Geospatial data and its readiness to meet ARNOLD and Federal Safety Reporting Requirements.

Develop Geospatial Data Guidance Report for developing and maintaining an all public roads centerline database that supports ARNOLD, NG-911, MIRE and HPMS.


43


Local Outreach and Regional Workshops

Develop technical and organizational workshop materials.

Organize and conduct regional workshops with local governments.

Develop Regional Workshop Summary Report


44

Task 2 - Continued Task Objectives

Workshop Topics -Organizational

Education regarding ARNOLD and NG-911 and impact on local data workflows.

Establishment of better communication protocols for data producers and consumers.

Better understanding of the relationships and differences between AGRC, NG-911, UDOT and local data schemas.

Impacts of MAP-21 on the maintenance of local roads data to support asset management, operations, and maintenance.


45

Task 2 - Continued Task Objectives

Workshop Topics - Technical Review of State Data schemas and discussion of impacts on local data maintenance activities.

Communication needs during the data maintenance life-cycle.

Interactive discussion regarding centerline geometry requirements and attribute data collection at the local level to support MIRE.

Discussion of QA/QC needs and requirements for all stakeholders.

Questions?

46

Documents

The HPMS Checklist Project and The Arnold Pooled Fund ... GIS_T_Session 5.4.1 Arnold and Checklist.pdf · The HPMS Checklist Project and The Arnold Pooled Fund Study ... coordinator)