Items #2 and 3

1. Items #2 and 3 Review of Emergency Transportation Workshop Results and Review of Updated Draft Regional Emergency Evacuation Transportation Coordination (REETC) Annex Andrew J. Meese, AICP Metropolitan Washington Council of Governments/ National Capital Region Transportation Planning Board Presentation to the Regional Emergency Support Function 1 – Emergency Transportation Work Group December 18, 2003

2. Overview • The RESF 1 – ETWG held a series of three workshops to aid revision of the Regional Emergency Evacuation Transportation Coordination (REETC) Annex of the Regional Emergency Coordination Plan (RECP)

3. Workshops • Workshops examined regional transportation coordination of selected scenarios • October 29, 2003: selective evacuation scenario (Nat’l Airport & Crystal City) • November 14, 2003: phased/staged evacuation (exploring both a weather event & potential explosion) • December 3, 2003: extended, complete closure of Metrorail • Workshops provided input to REETC revisions • “Kits” also under development as templates for nine additional emergency transportation workshops • Additional documentation will include supporting transportation and associated protective actions technical information

4. Workshops Focused on Situations • A range of twelve emergency transportation situations have been identified as the basis for • Technical analysis and workshops • Enhanced REETC Annex transportation and communications strategies • Had ability to hold workshops for 3 of the 12 situations in this time frame

5. October 29 Workshop - Scenario • Threatened explosion of a minivan filled with explosives at a Reagan National Airport parking garage • Starting on a weekday at noon, lasting until 8:00 PM • Estimated evacuation radius of about one-half mile • Affecting mostly airport property, but also a portion of Crystal City • A number of key surface transportation routes affected • Metrorail Yellow & Blue Lines, VRE, US 1, GW Parkway • Needed to accomplish an afternoon rush hour with these facilities closed to traffic and passengers • Eventually, explosives defused without an actual explosion occurring • Limited area evacuation still had regional impacts

6. October 29 Workshop - Scenario

7. November 14 Workshop - Scenarios • “Surprise” announcement at 10AM that an ice storm will hit the region starting at 4PM • Calls for a phased release-staged evacuation • Definitive amount of time of safety for transportation before the “danger” begins • Followed the ice storm scenario with a new, separate scenario: large cache of explosives in central Washington found at 10AM, with a threat to explode if ransom demands are not met by 4PM • Explored differences of danger and reaction between a weather event and a terrorist event

8. November 14 Workshop - Scenarios

9. December 3 Workshop - Scenario • Considered what would happen if the Metrorail system had to be closed for an extended period of time • Scenario assumed a number of apparent biological agent attacks causing a complete system closure • Discussed transportation agency coordination of the closure, stranded passengers, and other affected transit and roadways • Discussed planning for that evening’s rush hour, and for commutes in the days to come, without Metrorail • Considered transportation implications of law enforcement, emergency management, and health actions

10. Participants in the 3 Workshops • Departments of transportation: DDOT, MDOT (SHA, MTA/MARC), VDOT, Alexandria, Arlington, Fairfax, Prince George’s • Transit agencies: WMATA, Alexandria, Arlington, Fairfax, Montgomery, NVTC, PRTC, VDRPT • Emergency management & law enforcement: FEMA, MEMA, VDEM, WMATA, US Park Police • Federal: DHS – Office of National Capital Region Coordination, Federal Protective Services; USDOT – FHWA, FTA, RSPA; Naval District of Washington; US Army Corps of Engineers • Airports: Reagan National, BWI

11. Workshop Discussions • Lively, engaged – scenarios were realistic and appropriate, workshop format was successful • Focused on the question of regional impacts requiring coordination (beyond direct response to the incident) • Participants explicitly mentioned that they appreciated this focus • Dialog among law enforcement, emergency management, and regional transportation management representatives • Strong support of workshop format, interest in more workshops

12. Workshop Findings • RICCS utilization critical – focus on who will initiate and use RICCS, when will it be used, and what will be discussed • RESF 1 coordination depends upon “Level A” agencies (DDOT, MDOT, VDOT, WMATA, NPS) • Triggering, ensuring RESF 1 RICCS communications remains a challenge

13. Workshop Findings • Workshops reinforced need from the RESF 1 perspective to get timely, effective messages or instructions out to the public on what they need to do in the emergency • People in the immediately affected area or perimeter, who may be in danger • People outside but near the affected area, who may need to act, move, or stay where they are according to the emergency • People in the rest of the region, whose travel patterns (or choice not to travel) will greatly impact the regional transportation system’s ability to handle the incident

14. Workshop Findings • Ensuring information flow from law enforcement or emergency management to transportation remains a challenge • Transportation can provide assistance as requested, but the lead time necessary should be taken into account (e.g., calling in bus drivers) • Transportation management impacts of “small” incidents quickly become widespread, regional

15. Workshop Findings • Incident evolution and public safety responses impact transportation response • Length of time taken to verify the incident affects transportation system conditions • Uncertain duration as incident unfolds • Need for transportation sector to manage systems in an uncertain atmosphere

16. Workshop Findings • Need for upcoming workshops, preparedness coordination activities to be “emergency management-centric” covering functional areas beyond transportation

17. How Workshop Outcomes Will Be Incorporated into the Revised REETC Annex • Refined guidance on RESF 1 use of RICCS in emergencies • When to initiate a call; who should initiate • Key information to be communicated among agencies • RESF 1 input to shaping coordinated public messages • Help ensure public safety • Aid demand management, demand reduction where possible • Sharing information on associated protective actions • Timing of subsequent calls through the incident

18. Revised Draft REETC Annex – Outline Follows Overall RECP • Introduction Listing of participating agencies and overview of the REETC • Policies Relationship of REETC to participating agency actions • Situations Examination of twelve situations critical to emergency transportation planning • Concept of Coordination A focal point of the REETC, addressing how RESF 1 will coordinate – similar to a “concept of operations” • Responsibilities Including systems responsibilities and “essential elements of information” to be shared with RESF 5 • Preparedness Cycle Outlook to maintain readiness

19. Revised Draft REETC Annex – Format Is Strategy-Oriented • Follows same format as existing RECP, with revised and improved details • Communications strategies among transportation stakeholders • Systems management strategies to get the optimum performance out of roadways and transit in the evacuation or other emergency • Demand-oriented strategies to encourage prioritization of use of transportation infrastructure by those who most need it

20. Revised Draft REETC Annex – Structure Follows How Incidents Evolve • Structurerevised to reflect the typical chronology or evolution of an incident and its key stages • Discovery of an incident • Initial transportation reaction and advice • Convening of transportation representatives (RESF 1) • Convening of regional decision-makers (RESF 5) • Agency follow-through actions, and advice to the public (RESF1 through RESF 5 to RESF 14) • Continuance and updates (feedback loops) • Recovery or re-entry actions

21. Revised Draft REETC Annex – Features Address Incident Specifics • Reflection of twelve emergency transportation situations within four protective actions categories (shelter-in-place; selective, staged, or full evacuation) • Playbook elements following from the twelve situations • Transportation strategies • Guidance for regional coordination through RECP and RICCS • Clear, direct, action-oriented language

22. Summary • Workshop format a very productive means to address regional emergency coordination planning • Upcoming shift to emergency management-led workshops, training, exercises will broaden scope and better address current needs • Revised final draft REETC Annex by December 31, 2003, will be finalized and published ASAP in 2004