1. 1 Briefing on the Washington Metropolitan Area Transportation Operations Coordination (MATOC) Program Presentation to the TPB Technical Committee Andrew J. Meese, AICP TPB Staff November 7, 2008 Item 6

2. 2 MATOC Background 9/11 & other incidents showed the need for regional coordination to manage ripple effects Led to creation of the Metropolitan Area Transportation Operations Coordination (MATOC) Program Being developed and operated jointly by DDOT, MDOT, VDOT, and WMATA – –With consultant and TPB staff support SAFETEA-LU grant funding through Congressman Moran, with state matching funds, adjusted total about $1.7 million over three years

3. 3 The immediate scenes of incidents are handled with skill by responsible police, fire, EMS, transportation, and other responder personnel… …MATOC is being established to address the ripple effects of those incidents

4. 4 Topics for Today’s Update Regional Operations and the Proof of Concept Regional Information Systems/Technology Outreach Key Expert Personnel Steering and Executive Committees Front Burner Issues Full Operations Launch

5. 5 Regional Operations and the Proof of Concept MATOC has created and filled a staff position for a MATOC Facilitator – Buddy Ey – –Longtime Montgomery County Fire and Rescue senior staff and FEMA Urban Search and Rescue team member – –Will be the face of MATOC Operations Subcommittee is meeting regularly, held Oct. 2 workshop – –Scenario based discussions on how MATOC will improve sharing of information during major incidents Proof of Concept test of live MATOC operations will be initiated in December as previously announced; now in pre-testing – –This will be the test/activity to provide evidence that the MATOC business model as proposed is feasible Developing initial set of MATOC Standard Operating Procedures (SOPs) to be tested/refined during proof of concept

6. 6 Information Systems/Technology The longstanding Regional Integrated Transportation Information System (RITIS) is the key technology system – –Developed by the University of Maryland Center for Advanced Transportation Technology – –RITIS is already “in service” sharing available information among member agencies, continues to undergo improvements An Information Systems Subcommittee of MATOC member agencies is now advising the application of RITIS to MATOC and member needs Technical documents and methods are being developed to ensure continued successful functioning of RITIS to provide information sharing RITIS will be the key source of real-time transportation information for personnel involved in MATOC for both the Proof of Concept and for the long term

7. 7 Outreach Looking at the needs for MATOC information by other agencies and the public Communications Plan under development – –Identifies stakeholder communication needs and mechanisms – –Focuses on Proof of Concept period External Focus Group formed – –Will help advise how MATOC will share information with others in the region – –Types of organizations represented: local traffic and transit, commuter rail, public information officers (PIOs), public safety, and the media

8. 8 Key Expert Personnel from Around the Region Are Involved Operations: – –Mark Miller (WMATA) – MATOC Steering Committee Liaison for Operations – –Alvin Marquess (SHA) – Subcommittee Chair – –Buddy Ey –MATOC Facilitator Information Systems/Technology: – –Mike Zezeski (SHA) – MATOC Steering Committee Liaison for Technology – –Patrick Chuang (DDOT) – Subcommittee Chair – –Michael Pack (U of Md) – RITIS Lead Developer – –David Yohanan – Consultant Team Lead Outreach: – –Focus Group members (invited) from 8 agencies, plus Bob Marbourg, WTOP Traffic Reporter (invited) – –Marie Travesky and Denise Nugent – Consultant Team experts Many other member agency personnel

9. 9 MATOC Steering and Executive Committees MATOC Steering Committee provides regular oversight and guidance for the program – –Richard Steeg, VDOT, Chair – –Soumya Dey, DDOT – –Mike Zezeski, Maryland SHA – –Mark Miller, WMATA – –Ron Kirby, TPB Liaison – –Gary Euler, Consultant Support MATOC Executive Committee – –Will meet occasionally (annually or semi-annually) to discuss long-term policy direction – –Anticipated to be DDOT Director, MDOT Secretary or SHA Administrator, VDOT Administrator, WMATA General Manager – –Seeking to have this meeting soon pending participant availability

10. 10 A Number of Important Issues are on MATOC’s “Front Burner” Defining MATOC operational needs (staffing, equipment, location, etc.) Improving SOPs through proof of concept testing Identifying needed enhancements to RITIS Developing a regional strategy for how MATOC will share information with other agencies and the media/public Identifying future budget needs and funding sources

11. 11 Full Operation Will Be Launched by July 2009 MATOC Facilitator and involved staff will be working under agreed SOPs More and more accurate information will be shared through RITIS Regional strategies for sharing transportation information with other agencies and the media/public will be defined, and procedures in place MATOC will be an integrated part of the way the major transportation agencies of the region use information to manage their systems