Docstoc

matoc furry

Document Sample
matoc furry Powered By Docstoc
					 National Capital Regional Initiatives:
          Topics & Speakers
Metropolitan Area Transportation Operations
Coordination (MATOC)
  Doug Ham, Manager, Telvent Farradyne
Regional Integrated Transportation
Information System (RITIS)
  Michael Pack, Director, CATT Lab
Capital Wireless Integrated Network
(CapWIN)
  Thomas A. Henderson, Executive Director
      Metropolitan Area
  Transportation Operations
Coordination Program (MATOC)
National Capital Region Incident Management
      and Homeland Security Conference

             November 8, 2006
                 Topics

What is MATOC?
Background
Status
Organization
Next Steps
           What is MATOC?

MATOC = Metropolitan Area Transportation
Operations Coordination
CapCom          RTCP       MATOC
Regionally oriented program to:
  Improve technological systems for data sharing
  Enhance standard operating procedures &
  notification practices
  Provide more timely & accurate transportation
  information to the public during incidents
Political Impetus
        “We need to coordinate
        construction schedules. We
        need to coordinate the way
        we address traffic incidents.
        And we certainly need to
        communicate better so that
        we can immediately figure
        out the most efficient way
        to deal with transportation
        crises as they arise.”
        — U.S. Congressman Jim
        Moran
             Background
In October 2005, TPB amended the CLRP/TIP to
include the MATOC
  SAFETEA-LU funding from Congressman Moran
  Match provided equally by DDOT, MDOT, and VDOT
Three DOTs plus WMATA working as a Steering
Committee to address MATOC
USDOT Volpe Center developed several guiding
documents under DDOT sponsorship
Program manager & consultant team selected
through COG/TPB procurement process
       Where Are We Today?
MATOC Steering Committee organizing itself
Funding agreement being worked to fund
program activities and consultant team
Program Implementation Manager on board
under an MDOT work order for limited
services
University of Maryland developing RITIS
                 Organization

Partner agencies
  DDOT, MDOT, VDOT, WMATA
Steering Committee
Supported by:
  MWCOG
  Telvent Farradyne
   • Program Implementation
     Manager
   • Technical Support Team
  University of Maryland
        Program Organization
                                 Member Agencies
                           DDOT, MDOT, VDOT, WMATA

                                Steering Committee
                               Supported by MWCOG




                         Transportation Management Centers
                                   DDOT TMC
                                   MDOT SOC
                                   VDOT STC
                                 WMATA R/BOCCs                    Other Stakeholders
  RITIS Developer                                            Other Transportation Agencies
University of Maryland                                          Other Transit Agencies
                                                             Other Public Safety Agencies

                              Program Implementation
                                     Manager
                               Other Key Personnel/
                              Technical Support Team
    Range of Incidents

Traffic            9/11 Attack
           MATOC-type Incidents

Attributes     Transportation primary focus
               Regional scale
               Multi-modal
               Multi-agency
               2-24 hours to return to normal
               Not a declared emergency
Examples       Major crashes
               Extended lane or station closure
               Significant hazmat spills
               Severe weather
   MATOC = Coordination

           Operational




Systems     MATOC           Institutional




          Public Outreach
       Anticipated Regional Systems
           & Information Flows
Transportation     MATOC       Communications         Users
   Centers       Integration     Interfaces

                  MATOC                  511,        Travelers
 Manual Inputs   Operations
                                       Internet,
                 & Planning
                                        Media
                                   Operations
                                Centers’ Software
                                (e.g. WebEOC &        PSAPs &
                                     EMMA)           Emergency
                                                    Management

   Automated
     Inputs
                                    Field
                   RITIS        Communications         First
                                                    Responders
                Next Steps

Defining MATOC as a program
  Priority of several components
  Initial organizational decisions
  Defining “success”
  Relationship of MATOC, RITIS & Other Systems
Beginning to “build” MATOC
  Leverage current agency systems, centers &
  personnel
  Basic program of formal coordination
      Thank You

    For more information:

          Doug Ham
     Telvent Farradyne Inc.
         301-984-6463
doug.ham@telvent.abengoa.com

				
DOCUMENT INFO
Shared By:
Tags: matoc, furry
Stats:
views:325
posted:1/9/2009
language:English
pages:15