Travel Forecasting Subcommittee

Overview

The Travel Forecasting Subcommittee (TFS) was formed in 1991 to provide oversight of activities related to development of the regional travel demand forecasting model. The TFS is one of several subcommittees that report to the TPB Technical Committee, which, in turn, reports to the National Capital Region Transportation Planning Board (NCRTPB, or simply TPB). 

The mission of the TFS is to “provide guidance to, review of, and oversight to the COG/TPB information, analysis, and forecasting systems, and to serve as a forum for coordinating and enhancing such systems throughout the greater Washington region” (adopted April 21, 1995). In FY 2004, the Travel Monitoring Subcommittee was merged into the TFS, so the mission of the TFS now also includes oversight of travel monitoring activities.

Membership

The TFS is composed of representatives from TPB member jurisdictions, state departments of transportation (DOTs), and the Washington Metropolitan Area Transit Authority (WMATA). Also invited to participate are consultants engaging in travel demand forecasting. Consultants do not vote on subcommittee matters, but they often provide valuable review of and comment about COG/TPB work activities. In return, consultants keep posted on the latest developments of the region’s travel forecasting process, thereby informing work they are doing in corridor and sub-regional studies for their clients.

Meeting Schedule

The TFS generally meets on the Friday following the third Wednesday of the month in January, March, May, July, September, and November.  Meetings generally run from 9:30 AM to noon.

Unified Planning Work Program

The TFS provides oversight for the following activities from the FY 2017 Unified Planning Work Program (UPWP):

  • Travel Forecasting
    • Network Development
    • Models development and Support
  • Travel Monitoring and Data Programs
    • Household Travel Survey
    • Travel Monitoring Counts/Studies

TFS E-mail Distribution List

TPB staff maintains an e-mail distribution list for the TFS, which is used to inform the TFS about upcoming meetings and is used to transmit meeting agendas and highlights. If you would like to be added to the TFS e-mail distribution list, please send an e-mail request to Mark Moran with the following information:

Person-level information

Prefix, e.g., Mr., Ms., Dr.
First name
Middle initial (optional)
Last name
Suffix, e.g., Jr., III (optional)
Designation, e.g., Ph.D., AICP, P.E. (optional)
Job title
E-mail address
Work phone number

Organization/agency/company information

Name
Jurisdiction represented, if a government organization
Main phone number
Address
Address type (business or home)

Participation on the subcommittee

Affiliation, i.e., the state/local jurisdiction you are representing or 1) regional organization, 2) federal government, 3) vendor/contractor, 4) business association

Requested role (“position”) on the subcommittee:

  • Committee member: Serves in official representative capacity within a committee
  • Alternate committee member: Serves in official representative capacity if Committee Member not present
  • Information only: Receives committee communications but does not regularly attend meetings
  • Participant: Attends meetings but does not serve in official representative capacity

For requested role, consultants should select “information only” or “participant,” since they are not representing a local, state, or regional entity.

Recent Chairs of the Subcommittee

  • 2016, Mr. Robert Josef, VDOT, Virginia
  • 2015, Mr. Ryan J. Westrom, DDOT, District of Columbia
  • 2014, Mr. Dial Keju, Div. of Community Development, Frederick Co., Maryland
  • 2013, Ms. Wendy Jia, WMATA
  • 2012, Mr. Bahram Jamei, VDOT, Virginia
  • 2011, Mr. Jamie Henson, DDOT, District of Columbia
  • 2010, Mr. Subrat Mahapatra, MDOT, Maryland
  • 2009, Ms. Wendy Jia, WMATA

Page updated 3/17/17

Featured Documents

View Documents
  • Publications

    Scan of Best Practices in Travel Demand Modeling, 2015

    Sep 23, 2016

    Beginning in 2005 (FY 2006), the TPB established a consultant-assisted project to provide assistance with the development and application of the COG/TPB travel demand forecasting model. For fiscal year 2015, the contract was awarded to Cambridge Systematics, Inc.

  • Publications

    Scan of Best Practices in Travel Demand Modeling, 2012-2014

    Sep 22, 2016

    Beginning in 2005 (FY 2006), the TPB established a consultant-assisted project to provide assistance with the development and application of the COG/TPB travel demand forecasting model. For fiscal years 2012-2014, the contract was awarded to AECOM.

  • Publications

    Scan of Best Practices in Travel Demand Modeling, 2009-2011

    Sep 22, 2016

    Beginning in 2005 (FY 2006), the TPB established a consultant-assisted project to provide assistance with the development and application of the COG/TPB travel demand forecasting model. For fiscal years 2009-2011, the contract was awarded to Cambridge Systematics, Inc.

  • Publications

    Scan of Best Practices in Travel Demand Modeling, 2006-2008

    Sep 22, 2016

    Beginning in 2005 (FY 2006), the TPB established a consultant-assisted project to provide assistance with the development and application of the COG/TPB travel demand forecasting model. For fiscal years 2006-2008, the contract was awarded to Vanasse Hangen Brustlin, Inc. (VHB). 

  • Publications

    TPB Version 2.3.57a Travel Model Documentation

    Oct 21, 2015

    The TPB Version 2.3 Travel Model, Build 57a, also known as the Version 2.3.57a Travel Mode became the adopted travel model on October 21, 2015.

    The TPB Version 2.3 Travel Model was calibrated to year-2007 conditions in 2012, and this work was documented in the attached calibration report.

    In 2013, the Version 2.3 Travel Model was validated to year-2010 conditions. Updates to the model resulting from this validation work were part of Build 52. The model validation effort was documented in the attached memo.

    The user's guide for the current model, Ver.2.3.57a, is attached in two volumes, one for the main report (including Appendix A) and one for Appendices B, C & D.

    The current documentation for the highway and transit networks used by the regional travel demand model are attached.