1 / 6

Briefing on the Washington Metropolitan Area Transportation Operations Coordination (MATOC) Program

Item 13. Briefing on the Washington Metropolitan Area Transportation Operations Coordination (MATOC) Program. Presentation to the Transportation Planning Board Michael Zezeski Maryland State Highway Administration Chair, MATOC Steering Committee April 21, 2010. Major Activities to Report.

maisie
Download Presentation

Briefing on the Washington Metropolitan Area Transportation Operations Coordination (MATOC) Program

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. Item 13 Briefing on the Washington Metropolitan Area Transportation Operations Coordination(MATOC) Program Presentation to the Transportation Planning Board Michael Zezeski Maryland State Highway Administration Chair, MATOC Steering Committee April 21, 2010

  2. Major Activities to Report • Continuing regional coordination / monitoring / notification activities • Based out of the Capital Wireless Information Net (CapWIN) offices in Greenbelt • A 2nd operations staff person has been added, coverage now 5 days / 13 hours • Notifications on an average of about 20 regional incidents per month • The Regional Integrated Transportation Information System (RITIS) continues as the key MATOC support technology • Undergoing continuous improvement by the University of Maryland with guidance from MATOC committees • The MATOC Steering Committee is addressing outstanding issues • Funding availability to sustain MATOC for FY 2011 • Recruiting a new MATOC Facilitator (position is currently vacant) • Finalizing a cost-benefit analysis for MATOC

  3. MATOC Involvement in Regional Coordination: Example Major Incidents • March 12 • 14th Street NW at Constitution Avenue, vehicle accident, all lanes closed • MATOC monitored situation, notified regional partners; frequent media reports • March 15 • G.W. Parkway north of Spout Run, vehicle accident involving downed tree, all lanes closed, traffic diversions • MATOC monitored; notified VDOT, DDOT, Virginia transit agencies, WMATA, USDOT • Nuclear Security Summit, April 12 – 13 • Coordinated with stakeholders the prior week to determine needs and notification preferences • Extended MATOC hours to cover 5am to 9pm • Monitored multiple information sources and traffic cameras for congestion & delays • Provided hourly updates by phone or email to partner agencies on road closures (scheduled and unscheduled), parking restrictions, and congestion • Additional notifications when situations involving gridlock or accidents escalated

  4. Funding • Original federal grant provides funding through June 30, 2010 • Now looking at a short deadline extension for the original grant to Sept. 30 • $1.2 million per year estimated to fully sustain the program thereafter • Includes both MATOC and supporting RITIS activities • MATOC Steering Committee working to identify FY2011 sustainment funding • MDOT has pledged its full $400K share of the $1.2 million • DDOT pursuing use of federal aid funding (e.g. CMAQ) • VDOT letter expressed support for the program; awaiting benefit/cost analysis results • Potential $100K from Northern Virginia CMAQ (later in FY2011) • Continued TPB UPWP FY2011 funding for eligible planning expenses – $90K direct to the MATOC Program (includes $30K carry over from FY2010) • $200K Federal Transit Administration FY2011 earmark is in process – secured by Congressman Ruppersberger for “the greater coordination of the transportation and transit system[s] in the National Capital Region” • Overall level of funding secured will dictate FY2011 staffing, hours of coverage)

  5. Benefit – Cost Analysis of the MATOC Program • The MATOC Steering Committee directed the consultant team to develop benefit – cost estimates for MATOC • Funding for the study was from the original federal earmark • To find out how regional coordination of major traffic incidents across jurisdictional boundaries enhances existing local incident management actions and mobility savings (e.g. time, fuel, emissions) • Focusing on MATOC activities including monitoring and communicating mobility information during major incidents, maintaining information software (RITIS), and facilitating ongoing standard operating procedure improvements • Looked at “modified trips” - trips made at a later time, on another route, by another mode, or not made • Benefits were estimated from reduced delay, fuel consumption, emissions (including greenhouse gases), and secondary incidents • Looked at 3 case studies – 2 freeway incidents and 1 arterial incident • Summary report will be released soon • Study found an overall benefit / cost ratio conservatively estimated at 10 to 1

  6. Outlook • Activities – short-term • Finalize and share benefit – cost analysis • Seek to extend the eligibility period for the original federal grant to bolster the transition period • Develop FY2011 work activities congruent with available funding • Activities – long-term • Continue to operate the MATOC program and look for ways to strengthen it • Working on developing a MATOC traveler information website • Staffing • Will maintain 5 day/13 hour monitoring operations for the time being • Process to hire a new MATOC Facilitator has begun • Funding • Committed funding to date make the basis of a minimum program for FY2011 • Will make the best use of limited funding; will continue to seek full funding

More Related