62
WVDOT TRAVEL DEMAND MODELING & TRAFFIC DATA HANDBOOKS Presented by: Gehan Elsayed, PhD, P.E., Planning Division, WVDOH John (Jay) Evans, P.E., AICP; Cambridge Systematics, Inc. WVDOT/FHWA/MPO 2017 Planning Conference

WVDOT TRAVEL DEMAND MODELING & TRAFFIC DATA HANDBOOKS · WVDOT TRAVEL DEMAND MODELING & TRAFFIC DATA HANDBOOKS ... Guidance on State Safety Data Systems 31 Chapter 1 ... 3.2 Data

Embed Size (px)

Citation preview

WVDOT TRAVEL DEMAND MODELING &

TRAFFIC DATA HANDBOOKS

Presented by:

Gehan Elsayed, PhD, P.E., Planning Division, WVDOH

John (Jay) Evans, P.E., AICP; Cambridge Systematics, Inc.

WVDOT/FHWA/MPO 2017 Planning Conference

Objectives

2

Travel Demand Modeling Handbook

➢ Guidelines for developing, validating, and applying

travel demand models

➢ Resource for public agency staff (MPOs) and

consultants

➢ Clarify expectations and requirements

3

Traffic Data Collection, Processing and Analysis

Handbook

“To develop a Traffic Data Collection, Processing and Analysis Handbook to support the traffic monitoring program responsibilities of the WVDOT”

1. Review current processes

2. Recommend and implement improvements

3. Document revised processes – Traffic Data Handbook

4. Document recommendations for further improvement –Data Business Plan

Objectives

Traffic Data Collection, Processing and Analysis

Handbook

Outline

1. Project Team

2. Project Scope

3. Traffic Data Collection Handbook Contents

4. Additional Tasks

5. Recommendations

6. Next Steps

5

Project Team

WVDOT Traffic Modeling & Analysis Unit (TM&A)

Gehan Elsayed,WVDOT Project Manager

TM&A staff

Cambridge Systematics, Inc.

Barbara Sloan, Principal in Charge

Anita Vandervalk, Project Manager

Kim Hajek, Transportation Analyst

Digital Traffic Systems

Liz Stolz

Peter Keen

6

7

Scope

Task 1Existing Traffic Processes

Task 2 Traffic Data Requirements

Task 3Gaps in Traffic processes

Task 4Recommendations

Task 5 Traffic Data Business Plan

Task 6Traffic Data Collection, Processing, and Analysis Handbook

8

➢Volume (AADT, VMT,

etc.)

➢Vehicle Classification

(motorcycles, passenger

cars, buses, trucks, etc.)

➢Weight (Weigh-in-Motion

(WIM))

➢Speed

WVDOT Traffic Modeling & Analysis (TM&A) Unit responsible for

collection, analysis, and reporting of traffic data for Continuous Count

(formerly Permanent) and Short-Duration (formerly Coverage Count)

stations

Task 1: Existing Traffic Processes

9

• Volume

• Continuous counts (73 locations statewide (2016))

• 2500 Short Duration counts annually

• Vehicle Classification

• Motorcycles

• Passenger Cars

• Buses

• Trucks

• Weight

• Trucks

• Speed

Task 1: Existing Traffic Processes

10

Traffic Data uses (State):

• Engineering Design (pavement, geometric)

• Construction

• Safety Projects

• Capacity Analysis

• Truck route planning

• Traffic Forecasting

• Traffic flow maps

• Continuous Count Station (formerly

PATR) Maps

• Performance-based Planning

• Project Identification & Prioritization

• Asset Management

Task 1: Existing Traffic Processes

11

• Traffic Data uses (Federal) and Guidelines:

• Highway Performance Monitoring System (HPMS) (AADT, annual vehicle miles traveled (VMT))

• Traffic Monitoring Guide (TMG)

• AASHTO Guidelines for Traffic Data programs

• Traffic Volume Trends (TVT) Report

• Pavement deterioration models

• Economic and freight research & planning

Task 1: Existing Traffic Processes

Task 1: Existing Traffic Processes

12

Documentation and evaluation of WVDOT’s existing Traffic Monitoring Program

Task 2- Traffic Data Requirements

13

Documentation of traffic data collection, analysis, and federal and

state reporting requirements

14

To determine and document gaps in the traffic data

collection and reporting processes at WVDOT that must

be addressed to comply with federal and state

guidelines and requirements

Task 2- Gaps in Traffic Processes

15

Gaps in Traffic Processes - Collection

16

Gaps in Traffic Processes - Collection

17

Gaps in Traffic Processes - Collection

18

Gaps in Traffic Processing - Processing

19

Gaps in Traffic Processing - Processing

20

Gaps in Traffic Processing - Processing

21

Gaps in Traffic Processes – Analysis/Reporting

22

Gaps in Traffic Processes – Analysis/Reporting

23

Gaps in Traffic Processes - Technology

24

Gaps in Traffic Processes - Other

25

Task 4- Recommendations

To compile a comprehensive set of recommendations for

addressing needs and gaps in the traffic data collection,

processing, analysis, and reporting procedures used at

WVDOT

Provides documented vision and mission statements for the Traffic

Monitoring Program

Documents roles and responsibilities of staff who support the Traffic

Monitoring Program, including data stewards, business data owners,

and the community of interest (the group of stakeholder who have an

interest in the business uses of traffic data)

Documents new and improved business processes that include the

use of capabilities of the Traffic Server (application and database) not

previously used to support the Traffic Monitoring Program

Identifies and documents available sources of training for staff

responsible for supporting the Traffic Monitoring Program

26

Task 5- Traffic Data Business Plan

To develop a Traffic Data Business Plan for implementing

recommendations outlined in Task 4

27

➢ Use guidance from NCHRP 8-70 (NCHRP Report 666)

Target-Setting Methods and Data Management to Support

Performance-Based Resource Allocation by Transportation

Agencies

➢ NCHRP 8-70 - best practices from other state DOTs

• Data Management

• Data Business Planning

• Data Governance

• Performance-Management

Develop Action Plan to implement recommendations

from Task 4

Task 5- Traffic Data Business Plan

Task 6- WVDOT Traffic Data Collection Handbook

28

Chapter 1 – Introduction, Federal Requirements and State

Guidelines, Terminology

Chapter 2 – WVDOT Traffic Monitoring Program Overview

Chapter 3 – Continuous Count Program (formerly Permanent

Program); Equipment Installation/Evaluation, Data Collection,

Processing (QA/QC), Reporting (including TMAS)

Chapter 4 – Short-Duration Program (formerly Coverage Count

or Short-Term Program); Data Collection, Processing (QA/QC),

Reporting

Chapter 5 – Special Counts Program

Chapter 6 – Annual Process; Update RI-Log, Develop Factor

Groups, Develop and Apply Factors, Calculations, Maintain

LRS/Segmentation Process, Reporting

Chapter 7 – Highway Performance Monitoring System

(HPMS) Traffic Data

Chapter 8 – Long-Term Pavement Performance (LTPP)

Program Traffic Data

Chapter 9 – Traffic Forecast Data

Appendices (Acronyms, WVDOT CCS Sites, Continuous Count

Program QC Rules, List of Benchmarks, CRTS System, Traffic

Server, References)

29

Task 6-WVDOT Traffic Data Collection Handbook

Chapter 1 - Federal Requirements

Apportionment, performance management, and freight management

Mandate for the traffic monitoring program. It requires State highway departments to

furnish information deemed desirable in administering the Federal-aid highway

program.

Traffic monitoring system for highways

Rule making for preserving and protecting highways & Insuring safety of traffic

Measuring performance of surface transportation system

Management and Monitoring Systems – Traffic Monitoring System (TMS)

State DOTs must provide data that supports FHWA’s responsibilities to Congress and

the public

State’s Traffic Management System (TMS) precision of reported data shall meet the

statistical precisions established by FHWA for the HPMS.

State Public Road Mileage. Each state must annually submit a certificate of public

road mileage with the State to the FHWA Division Administrator.

30

Statewide data collection programs

Highway Performance Monitoring System (HPMS)

Guidelines for Traffic Data Programs

The Highway Community Exchange

Book of Standards for Construction, Section Four, Construction, Road and Paving

Materials: Vehicle-Pavement Systems

Model Inventory of Roadway Elements

Data Dictionary for Traffic Data Records

Traffic Safety Performance for States and Federal Agencies

Coal Resource Transportation System (CRTS) Roads

Guidance on State Safety Data Systems

31

Chapter 1 - Federal Requirements

32

Chapter 1 - Federal Requirements

Chapter 1 – New Information

33

Federal and State guidelines and requirements for traffic monitoring

programs

Introduction of new terminology (coincide with TMG; i.e., Continuous Count

(formerly PATR); Short-Duration (formerly Coverage))

Includes additional reference documents for guidance (TMG, AASHTO

Guidelines, HPMS Field Manual)

34

Chapter 2 – Traffic Monitoring Overview

Chapter 2 – Traffic Monitoring Overview

35

36

Chapter 2 – Traffic Monitoring Overview

37

Chapter 3 – Continuous Count Program

3.1 Data Collection» Field Crew Responsibilities – New Process for Site Inspections

» Annual Cycle – New Process for Annual Cycle (review of all CCS stations)

» Daily Cycle – New Process for Daily Cycle

» Polling – New office process within Polling Procedure

» Site Selection – New Processes for Conducting Inventory of all sites; Site Selection to maintain sufficient number of sites per factor group(s); Caution noted for potential removal of WIM sites

3.2 Data Processing QA/QC

New Process for establishing CCS station in Traffic Server database, monthly checks on weight data, etc.; utilize more of QA/QC available in Traffic Server as noted in Handbook

3.3 Reporting (including TMAS)New documentation on preparing datasets for submission to FHWA via TMAS;

New process to utilize TMAS reports to validate WVDOT datasets prior to TMAS upload

38

Chapter 3 – Continuous Count Program

Chapter 4 – Short Duration Program

4.1Data CollectionNew procedures recommended in data collection contracts (i.e., request Per

Vehicle Data Collection, etc.); WVDOT notification to contractors of

scheduled holidays – avoid collecting on those days

4.2 Data Processing QA/QCNew processes outlined for use of Traffic Server for QA/QC of data

4.3 Reporting

39

Chapter 4 – Short Duration Program

40

Count Type Road Classification How Often Duration of Count

Volume Interstate mainline

(statewide)

Once in Spring 48 hrs.

Volume Interstate ramps

(statewide)

Once/yr. 48 hrs.

Volume Other than Interstate

(1/3 of state)

Once/yr. 48 hrs.

Vehicle

Classification

Interstate mainline Once in Fall 48 hrs.

Vehicle

classification

Other than Interstate

(1/3 of state)

Once/yr. 48 hrs.

Turning

Movement

Project-based Ad-hoc Machine – 24 hrs.

Manual - approx. 9

hrs. (always

daylight hrs.,

covering a.m. and

p.m. peaks)

41

Chapter 4 – Short Duration Program

Chapter 4 – Short Duration Program – Count Cycle

42

Chapter 4 – Short Duration Program – Count Cycle

NOTE: Conducting Interstate Short Duration counts for Volume data once/year

and for Classification data once/year each at different times of the year allows

the Traffic Monitoring Program staff sufficient time to process the large

amounts of data in a timely manner. This process includes but is not limited to

the following tasks:

» Determine if any recounts are needed for missing or error data and direct

contractors to conduct recounts

» Perform QA/QC on data in timely manner for payment to contractors

» Ensure data is available for engineering design work at WVDOT

» Ensure that data is available no later than October 31st of each year for use in

Annual Processing and federal reporting

43

Chapter 5 – Special Count Program

44

Chapter 6 – Annual Process

6.1 Annual Process Overview

6.2 Update RI Log

6.3 Develop Factor Groups

6.4 Develop and Apply Factors

New information on computing/applying growth factors using Traffic Server instead of

previous outdated methods

6.5 Maintain LRS/Segmentation Process

This entire section is new guidance on how to maintain the LRS/Segmentation

process

6.6 Reporting

New guidance on rules of release of traffic data to the public

45

Chapter 7 – Highway Performance Monitoring System

(HPMS) Traffic Data

46

Chapter 7 – HPMS Datasets – New Information

NOTE: New guidance is provided on how to produce Future Year AADT for

reporting in HPMS based on use of Forecast data derived from methods

described in Chapter 9

New Process – Close coordination between GTI Section and Traffic Monitoring

Program Section for development/processing/review of HPMS datasets prior to

HPMS submittal

47

Chapter 8 – Long Term Pavement Performance

(LTPP) Program Traffic Data

48

This chapter describes NEW processes for producing traffic forecast data to

replace previous methods of applying a percent (%) growth (outdated

procedure)

Use forecasts produced by a TDM

Use other forecasts previously developed by WVDOT or local highway

agencies for highway planning purposes

Use area-specific forecasts of the average percentage change in AADT

derived from forecasts developed using the above procedures or

Derive forecast changes in AADT from forecast changes in population and

employment developed by the Bureau of Business & Economic Research of

West Virginia University

49

Chapter 9 – Traffic Forecast Data

Inventory and Site Assessment

Task 1 – Continuous Count Station (CCS) (formerly PATR) Equipment

Evaluation

» Review the Continuous Count Station (CCS) sites

–Determine what type of new equipment (or equipment upgrades)

may be needed

–QA/QC of the hardware/software so that this information can be

documented in the Handbook

50

Scope- Additional Tasks

Task 2 – Documentation of Process for Continuous Count Station (CCS

(formerly PATR)) Installation and Maintenance

» Research and document the process of installing and maintaining the CCS equipment

– All steps of work currently carried out by current WVDOT employees

» Make recommendations on which work could be contracted out and what would need to

be included in a contract scope of work for installing and maintaining CCS equipment

51

Inventory and Site Assessment

Scope- Additional Tasks

Task 3 – Additions to Traffic Data Collection Handbook

» Procedures for review and evaluation (on-going basis) of CCS (formerly PATR) and

Short-Duration (formerly Coverage Count) sites to ensure operability of equipment and

functionality within 2 weeks if any sites are down

» Procedures for WVDOT to conduct annual review of CCS and Short-Duration sites

statewide to ensure there is sufficient coverage within Factor Groups recommended in

the TMG

» Equipment installation procedures

» QA/QC procedures to ensure that hardware/software at the CCS site is working

properly

» Responsibilities of WVDOT Field staff in monitoring polling functionality of equipment

on a daily basks

» Responsibilities of WVDOT Office staff in monitoring polling functionality of equipment

on a weekly basis

52

Inventory and Site Assessment

Scope- Additional Tasks

Recommendations - Immediate

53

Request Per Vehicle data from traffic data collection

contractors

Short Duration

Perform the QA/QC checks documented in the TDH for volume

and vehicle classification data collected by short-duration

counters

Short Duration

Do not perform short-duration counts during holidays or days

preceding or following holidays when traffic might be

unusually high or low

Short Duration

Ensure that all stations are assigned a functional class per the

FHWA FC schema

Annual Process

Maintain the LRS/Segmentation process in accordance with

procedures described in the TDH

Annual Process

Determine rules of release of traffic data Annual Process

54

Implement Grounding Test Procedures and BusinessProcesses

Equipment

Installation Process

Recommendations

Implement Proper Installation of Grounding RodsEquipment

Installation Process

Recommendations

Follow the instructions for this program as described inChapter 5 of the TDH

Special Counts Program

Ensure that CCSs are operational within a two-week periodafter outages are reported

PreventativeMaintenance

Perform series of QA/QC checks on data in Traffic Server on adaily and monthly basis

PreventativeMaintenance

Use the reports available in the TMAS system to performQA/QC checks on traffic data prior to submission of the datain TMAS

PreventativeMaintenance

Training for TM&A staff On-going or One-time Practice

Recommendations - Immediate

Recommendations – 3 Months

Review HPMS data sets containing traffic data prior toHPMS submittal

Annual Processes

Coordination with GTI Section regarding HPMS Annual Processes

TM&A staff to provide AADT values by RoadwayFunctional Classification to the GTI Section

Annual Processes

TM&A staff consider use of Traffic Server to calculateVMT for Local Roads

Annual Processes

Use traffic forecast data to develop Future Year AADT (20yr)

Traffic Forecasting Processes

Alternatives for developing AADT forecasts for trafficsegments

Traffic Forecasting Processes

55

Recommendations – 6 Months

Report classification and weight data to LTPP

program contractor (First set of WVDOT LTPP data

submitted January 2017)

Annual Processes

56

Recommendations - One Year

Implement a Site Selection Business Process Site Selection Processes

Develop and Archive Site Evaluation Records Business

ProcessSite Selection Processes

Develop an Annual Factor Group Development Business

Process

Factor Group

Develop a CCS Validation Business Process Factor Group

Allocate WIM Paving Funds to Other Program Needs Financial

Performance measures for the Traffic Monitoring Program On-going or One-time Practice

Annual review of station record fields in Traffic Server On-going or One-time Practice

Annual review and update of the Traffic Data Handbook and

Traffic Data Business Plan

On-going or One-time Practice

57

Recommendations - One Year

Transition Field Crew to role of inspectors of contractors’

work

One-time Practice

Purchase two vans to increase productivity of inspectors One-time Practice

58

Recommendations – 2 Years

Managing Class Factors On-going or One-time Practice

ITS Coordination Develop an ITS

Communication and

Coordination Business Process

ITS Coordination Develop a Documented

ITS and Traffic

Monitoring Program Coordination Project

Preventative Maintenance Implement a

comprehensive

preventative maintenance program

Reduce number of WIM sites by 2/3 WIM

Consider procurement of alternative equipment (i.e., Peek,

TDC, Diamond, Black Cat) at lower cost

WIM

59

Recommendations – 2 Years

Allocate WIM Site funding to other program needs WIM

Use of load spectra data in weight factoring Load Spectra

Manage CCS as part of a comprehensive asset

management program

Other

Impact of migration to ERP Other

Executive summary reports Other

Develop website for public Other

60

Recommended Next Steps

1. Adopt Handbook and DBP (Implementation Plan)

2. Start Implementation Project

» Proceed with recommendations by timeframe

» Bring all CCS sites up to highest quality standards

» Develop/Implement a WIM Site Selection Methodology

» Implement some co-location of ITS sites

3. At end of Year 2 – Evaluate for further privatization

61

Thank You!