U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000


Skip to content
Facebook iconYouTube iconTwitter iconFlickr iconLinkedInInstagram

Policy and Governmental Affairs
Office of Highway Policy Information

FHWA Home / Policy & Governmental Affairs / Highway Policy Information / Office of Highway Policy Information

Office of Highway Policy Information (OHPI) – Travel Monitoring and Traffic Volume – Traffic Monitoring Guide

Traffic Monitoring Guide

Appendix L. ADDITIONAL STATE TRAFFIC MONITORING PROGRAM EXAMPLES

L.1 ALASKA DEPARTMENT OF TRANSPORTATION AND PUBLIC FACILITIES

The example below summarizes the ADOT&PF process for traffic data collection in the regions. This information is excerpted from the Traffic Data Systems Concept of Operations report for ADOT&PF (June, 2011).

The traffic data collection process is the responsibility of the regions, with the Headquarters Program Development Division being responsible for maintaining the database of the traffic data for analysis and reporting in the Highway Analysis System (HAS).

There are two types of volume counts that are taken in the regions: the continuous counts and the coverage counts. These are identified as “collect traffic data” in Figure L-1.

FIGURE L-1 ADOT&PF REGIONAL TRAFFIC DATA COLLECTION

ADOT&PF Regional Data Collection: This diagram illustrates Alaska’s flow of traffic data and agency responsibilities. The process begins with portable and permanent equipment producing data. These data are then managed and stored at the regional traffic collection level, where the majority of the activity occurs. The final step at the regional level is to load HAS data, at which point the HAS system computes AADT and VMT statistics.

Source: Alaska Department of Transportation

L.2 GEORGIA DEPARTMENT OF TRANSPORTATION (GDOT)

In 2006, the Georgia Department of Transportation (GDOT) conducted a Traffic Count Strategy Plan to maximize the value and return-on investment of scarce transportation revenues, and to ensure that customers’ needs for traffic data were being met. The following elements were included:

  • Existing Traffic Data Program Methodology and Business Processes:

    - Overview of Existing Traffic Data Systems;

    - Equipment Set Up and Maintenance;

    - Quality Assurance;

    - Description of Existing Georgia DOT Office of Transportation Data Reporting and Data Sharing Process;

    - Description of Additional Programs; and

    - Summary of Business Processes.

  • Federal Literature Review:

    - Federal Requirements Related to Traffic Data Collection; and

    - Summary of Other Key Federal Literature Related to Traffic Data Collection.

  • Select Summary of Processes Implemented in Other Departments of Transportation.
  • Stakeholder Workshops and Interviews.
  • Business Process Strategy.
  • Federal Highway Administration (FHWA) Needs:

    - Traffic Monitoring Guide (TMG);

    - Highway Performance Monitoring System (HPMS) Field Manual; and

    - AASHTO’s Guidelines for Traffic Data Programs.

  • GDOT Business and Customer Needs:

    - Short-Term Actions for OTD;

    - Mid-Term Strategies; and

    - Long-Term Strategies.

  • Traffic Program Issues:

    - Documentation;

    - Retrieval of Data/Reports;

    - System Design;

    - Specials Program Improvement; and

    - Balancing Resources.

  • Recommendations:

    - Documentation;

    - Retrieval of Data/Reports;

    - System Design;

    - Specials Program Improvement; and

    - Balancing Resources.

  • Strategy Plan.

This project enabled GDOT to move forward with the recommended improvements including procuring a traffic data software solution.

L.3 COLORADO DEPARTMENT OF TRANSPORTATION (CDOT)

The Colorado Department of Transportation (CDOT), Division of Transportation Development (DTD) and Traffic Analysis Unit (TAU), has been very proactive in improving the CDOT traffic data program. In 2008, CDOT embarked on a business planning process review project. Phase 1 of the Traffic Analysis Business Process and Integrated Software Recommendations project resulted in the development of a comprehensive set of business process diagrams and maps documenting the existing and recommended business process overview. The report included specific evaluations of the capability of their traffic software project to streamline and improve CDOT’s collection and analysis processes. The recommended processes resulted in an estimated reduction of 318 different business processes. Recommendations of the Phase 1 report also included specific areas of improvement for CDOT associated with resources, processes, and tools. Phase 2 included follow-up on the recommendations from Phase 1; update of business process diagrams and creation of new process diagrams; improvement of the process of local traffic data sharing; development of a digital portal and requirements report; and recommendations for further enhancement of the CDOT traffic data program.

The following figure documents the high-level processes. There are numerous other detailed diagrams and process steps.

FIGURE L-2 COLORADO DOT HIGH-LEVEL BUSINESS PROCESSES

Colorado DOT High-Level Business Processes. This flow diagram illustrates traffic monitoring business processes within Colorado DOT. The first three processes are 1) collection, which flows into 2) analysis (including daily processing, monthly processing, and annual processing), which flows into 3) other (including 20 year growth factor creation and permanent traffic location evaluation). These three processes then have a mutual flow with storage. Following storage, the last process is reporting/distribution.

Source: Colorado Department of Transportation.

Page last modified on November 7, 2014
Federal Highway Administration | 1200 New Jersey Avenue, SE | Washington, DC 20590 | 202-366-4000