GGS 685 Capstone: Part V: On-Site Deployment

1. Charles Chung Caleb Gaw Justin Miller 6 December 2010 GGS 685 Capstone:Part V: On-Site Deployment

2. Overview • Purpose • The objective of this assignment is to develop and recommend an On-Site Command Center for the Government of DC to be used in crisis scenarios that takes the key Geo-Spatial concepts that we have developed over the course of the semester and integrate them with the requirements laid out by FEMA and the Dept of Homeland Security • Mobile Command Team (MCT) and MO • Our recommendation for an EMMCC • Data Integration and Geo-Data Packets • How we will integrate our data to meet our recommendations • Scenario • Overview of a scenario where our MCT could provide a critical role to First Responders • Conclusion • A conclusion of our findings and recommendations

3. 10 Member MCT • 1 CIC: • Responsible for all final MCT decisions and overall MCT mission • 8 Functional Area specialists: • Responsible for the Monitoring, Communication, Coordination, Data and On-Site Recommendations within their respective AOIs and Corresponding First Response Elements • 1 IT Assistant/Driver • Driver of Mobile Command Center and on-site MCT IT technician and assistant.

4. MCT MO • Additional Notes: • MCT is not to replace any current DC First Response Operations or Command Center, but augment current capacities with a dedicated on-site staff that will provide enhanced analysis and communications between all levels through out the duration of the situation • If situation does not require specific needs of a particular Specialist, they will become a backup/secondary analyst for another specialist

5. Mobile Command Team

6. Mobile Command Center Frontline Communications: • C-40 MCB M2-106 • A straight truck designed as a Command and Communications Center with a modular body of eleven workstations, a gallery and a restroom

7. C-40 • Additional Notes: • External 26” LCD for comm./situational monitoring with onsite personal • Can link with DC power grid and communications lines • 20KW Diesel Generator and battery bays for backup

8. C-40 • Additional Notes: • Capable of allowing for all primary specialists to work at independent work stations as well as a briefing room with LCD display for CIC • All necessary equipment can be stored either internally or externally • Communications Link either via satellite or 4G network

9. C-40 • In addition to external comm. the C-40 maintains an independent data server for all onboard operations • Significant storage both inside and externally for additional equipment • Fully operational espresso maker as well as a lavatory with electric toilet

10. Mobile Command Center Command Structure

11. Transportation Specialist Primary Responsibilities • 1. Routing Specialist • Emergency routing of inbound personnel/equipment • Emergency routing from site to: Hospital, evacuation points,… • Coverage analysis, nearest facility analysis • 2. Transportation Network Monitoring • 3. Data: • Provided all necessary updates to Base-Layer transportation data • 4. Provide required analysis for MCT • 5. Identification of possible HLZ • 6. Identification of alternative Evac points and routes Required Training • Extensive GIS Transportation, Network Analysis and Coverage Analysis training • Transpiration Safety Required Experience • Min 5 years working for state or federal DOT Primary External Communications: • DDOT, VDOT, MDOT, WMATA Required On-Hand procedures • FEMA/DC Emergency Routing/Evacuation procedures • Emergency Vehicle Procedures and Guidance • DDOT/VDOT/MDOT/WMATA procedural documents • Road/Rail/Metro closures • Emergency Situation procedures Data Needs: • Real-time road/rail network availability/closures/hazards • Base-Layer facilities • Base-Layer Imagery/Weather • Base-Layer DEM/Slope • CCTV of Road Network • DOT Resource Inventory/Location • DOT vehicles (I.E. Snow Removal) • Barricades/ Road Cones…

12. Communications Specialist Primary Responsibilities • 1. Provide/Maintain all comm./data links with outside sources • 2. Provide/Maintain comm./data links with GIS Database Server • 3. Provide/Maintain comm./data links with on-site units • 4. External/Public Warnings • “Alert DC” Required Training • State/Federal Emergency Planning • State/Federal Emergency Management • State/Federal Emergency Comm. Protocols Primary External Communications: • GIS Database HQ • DC Incident Command Center • FEMA/DHS Command Centers Required Experience • FEMA/DHS Command Center • Previous experience working with other Units • DC Emergency Command Center or other Emergency Ops Center Required On-Hand procedures • Comm. Equipment procedures/manuals • Comm. Protocol Data Needs: • All data needs of other Specialists • Contact Info. to all emergency personal • Contact Info. to all on-call specialists/experts Equipment Needs • Comm. Vehicle

13. Public Health/Medical Specialist Primary Responsibilities • 1. Evaluation of incident medical needs and the corresponding availability at local hospitals • 2. Monitoring of Local Hospitals for Mass-Public Medical Incidents • 3. Planning and Coordination for Mass Casualty incidents • 4. Coordination with DC Epidemiological Surveillance and Investigation • CBRNE Detection • Foodborne Disease Surveillance Investigation • Bioterrorism Surveillance program • Isolation And Quarantine Required Training • CBRNE Identification and Response • Mass Casualty Management • Hospital Management • USDA/FDA Emergency Planning and Response Primary External Communications: • Hospitals (DC, N.VA, & MD) • DC Laboratories • USDA Emergency Center • FDA Emergency Center • BSL3 Lab Required Experience • HHS/FEMA Command Center • Hospital Management Required On-Hand procedures • CBRNE Identification and Response Procedures • Equipment Manuals for CBRNE equipment • USDA/FDA Identification and Response of Foodborne Disease Procedures • FEMA/HHS/DHS Mass-Pandemic/Casualty Response and Planning Procedures Data Needs: • USDA/FDA database on Foodorne Disease • CBRNE reports from Test Sites and Hospitals • Libratory Results • Current Hospital Data • Availability, Staffing, Capabilities Equipment Needs • CBRNE mobile identification platforms • Foodborne Disease mobile identification platforms • Hazmat Suites for MCT

14. Public Health/Medical Specialist Epidemiological Surveillance and Investigation • Center for Policy Planning and Epidemiology, Division of Disease Surveillance and Investigation (DOH 825 North Capital ST, NE) • Foodborne Disease Surveillance Investigation • Bioterrorism Surveillance program (collecting data from eight of the major hospitals within the district) • Bacillus Anthracis, Yersiniapestis, Fracisellatularensis, Clostridium botulinum Public Health Laboratory Testing • BSL3 (Bio-Safely Level Three) lab at D.C. Village, 2-A Village, Lane, S.W. CBRNE Detection • Fixed: • Recommend a review of current stand-alone systems for coverage and accuracy for redeployment within DC to include all Hospitals, Fire Stations, Police Stations and Federal Buildings • Mobile: • M8/M9 Chemical Detection paper • M256A1 Chemical Agent Detection kit • Colorimetric tubes with chip measurement system analyzer • Ion Mobility Spectroscopy (IMS), M86/M90 • Advanced Portable Detector (APD) • Technology vs. Training • “Technology is not a strategy” –Margaret N Carter, Army War College • Every Specialist will be fully CBRNE trained for detection, response and planning.

15. Fire Dept / EMS Specialsit Primary Responsibilities • 1. Coordination with Fire Dept. for response to incident, including personnel and equipment • 2. Coordination with EMS units for evacuation of injured persons to hospitals or evacuation points • 3. Identification of specialty emergency teams/equipment needed • 4. Identification of on-site medical response area • 5. Urban Search and Rescue Operations Required Training • Fire Emergency Planning and Response • On-site EMS Response Planning Required Experience • Fire Dept or EMS • HHS Emergency Ops Center or DC Emergency Command Center Primary External Communications: • DC Fire Department • EMS service centers/organizations Required On-Hand procedures • Fire Dept. Response Procedures • EMS Response Procedures Data Needs: • Fire / EMS personal and equipment locations and conditions • Fire/EMS onsite reporting • Helmet mounted Cameras, EMS reports • City Supporting Infrastructure • Fire-hydrant grid (availability and condition)

16. Public Works / Engineering Energy Specialist Primary Responsibilities • Technical advice and evaluation • Coordinates engineering services • Debris Management • Utility Management Required Training • Utilities management and planning • Search and Rescue Required Experience • Utility Management • Civil Engineering • Emergency Planning Primary External Communications • District Department of the Environment • MPD • Office of Property Management • DC Water and Sewer Authority • National Park Service Required On-Hand Procedures • Debris Management Plan • Emergency Power Plan • Structural Assessment Plan Data Needs • Blue Prints • Utility Lines • Energy/Utility Plants • Utility Trucks Inventory/Location Equipment Needs • Utility repair equipment • Debris removal equipment

19. Natural Hazard Specialist Primary Responsibilities • Monitor weather forecast • Monitor damages to infrastructures, public, private, and government properties • Debris Management Required Training • Population evacuation • Search and Rescue • Damage assessment Required Experience • Natural Disaster Management • Weather forecasting • Emergency Planning Primary External Communications • FEMA • DDOT • Fire Department/EMS Required On-Hand Procedures • FEMA/DC Emergency Routing procedures Data Needs • Transportation Network • Base-Layer Imagery/Weather • Base-Layer DEM/Slope • Weather Forecasts • DOT Resource Inventory/Location • DOT vehicles (I.E. Snow Removal) Equipment Needs • Snow plows • Chain Saws • Debris Removal equipment

21. Oil/Hazardous Materials Specialist Primary Responsibilities • Identify hazardous material • Monitor hazardous substances, pollutants, and contaminants • Monitor potential spread and secondary effects • Plan response, control of material, and clean up Required Training • Fire-related emergency protocols • Resource management • Evacuating the public Required Experience • HAZMAT Identification • Controlling and clean up of HAZMAT • HAZMAT personnel management Primary External Communications • Fire Department/EMS • Police • Hospitals Required On-Hand Procedures • DC Comprehensive Hazardous/Toxic Materials Emergency Response and Weapons of Mass Destruction • DC Fire and Emergency Medical Services Department ICS/Standard Operating Guidelines for Hazardous Material Incidents/Weapons of Mass Destruction Data Needs • Industry data • Gas station data • Storage areas of oil/hazardous materials • Base-Layer DEM/Slope • Hydrology network • Storm Sewershed data • Weather Data Equipment Needs • CBRNE mobile identification platforms • HAZMAT suites • Vehicles to cleanup, store, and transport the materials

22. Ammonia Processing Plant Reported Ammonia Spill of 100 gallons

23. Safety and Security Specialist Primary Responsibilities • Perimeter control • Traffic and Crowd Control • Force Protection • Evacuation • Bomb detection (K-9 Units) • Vehicle escort Required Training • Crowd control • Evacuating the public • Situational containment • Intelligence collection and analysis Required Experience • Police Procedures • Site management • Weapons and Tactical operations Primary External Communications • Fire Department/EMS • FBI • Hospitals • DOT Required On-Hand Procedures • MPD Enforcement Policies • MPD Field Operations Data Needs • Real-time road/rail network availability/closures/hazards • Police onsite reporting • Police Personnel positions Equipment Needs • Barriers • Weapons • K-9 • Riot equipment

24. Car #3567 Driver: Joe Smith Partner: Jack Miller Action: Traffic Stop Vehicle Camera District: 1 PSA: 103

25. Mobile Command Center Data Integration and Geo-Data Packets

26. Command Center Applications • WebEOC Professional 7 by ESi • Web-enabled, user-friendly, and locally configurable crisis information management system (CIMS) • Secure real-time information sharing to help managers make decisions quickly. • Used by government at every level from city to federal agencies such as Departments of Defense, Energy, Agriculture, and Health & Human Services. • Comply with the provisions and standards for Incident Command System (ICS) • Comply with the provisions of the Emergency Support Functions (ESF) • Integrate with other systems such as mapping applications and telephonic alert notification systems • Works with IE 6.0 or higher, Safari 3.0.4, or Firefox 2.0.0.11 • WebEOC® Mapper Professional with ESRI ArcGIS Server 9.3 • View live, dynamic, multi-user WebEOC board data on a map. • Combine WebEOCboard data with other GIS data or services (i.e. WMS) on a single map to gain a common operating picture. • Dynamically push and pull data in and out of WebEOC. • Configure the map with data from local and remote services on the fly using ArcGIS Server services, OGC WMS services, and KML

28. Provides a visual, easy-to-understand view of the entire incident. • Users can zoom in to explore details “on the ground” and update WebEOC entries directly from the map. • Automatically displays the most current information from WebEOC combined with GIS data layers and live feeds. • Updates automatically as the situation changes. • Users always have access to the latest information to enable them to make the best decisions.

29. Common Operating Picture Result of geoprocessing operations

30. WebEOC - Resource Manager • Inventory, track, and deploy resources in a manner that complies with FEMA’s National Incident Management System (NIMS).

31. WebEOC - EMResource Interface • Communicate critical hospital bed count data to public health officials and emergency operation center managers. • Provides real-time monitoring of healthcare resources for everyone involved in emergency medical response. • WebEOC - EMTrack Interface • First responders providing on-site triage and emergency physicians in hospitals can provide patient-specific data to public health officials and emergency operations center managers. • Enables WebEOC users to view EMTrack patient and evacuee treatment and location data on a WebEOC status board. • Provides users with advance notification of incoming patients, alerting hospitals of critical patient status information necessary to prepare and respond with appropriate care teams.

32. WebEOC Team Manager • Maintain a record of qualifications, such as medical training, languages spoken, and certification programs. • Attach a photograph to the member record. • Activate and deploy team members. • Track disbursements, travel details, and assigned equipment. • Maintain detailed time records for each team member. • Search and filter team member information. • Configure the data fields that will be displayed in certain screens. • Pre-populate a host of drop-down lists based on local operations and nomenclature. • Create pre-defined templates for importing and exporting Team • Management data residing in the database. • Assign read/write permissions to specific functions and screens in WebEOCTeam Manager.

33. WebEOC Team Manager

34. WebEOC – KML Interface • Integrates WebEOCand Google Earth • WebEOC status board data is automatically transferred to Google Earth, displaying any geocoded data records • By selecting the link in the Places pane of Google Earth, or selecting the pushpin icon on the map, users are able to view WebEOC board data.

35. Web Server Hardware Requirement • Processors: Two - Quad Core Intel Xeon, 2.6GHz, • 2x6MB Cache • Memory: 4GB • Hard Drive: Two - 73GB SAS, 15K • Hard Drive Configuration: RAID1 • NIC: GB NIC • CD-ROM: DVD ROM • Power Supply: Redundant Power Supply • Operating System: Windows Server 2003 or 2008 [32-bit, • 64-bit], Standard Edition, • Microsoft .NET 2.0 Framework • Note: IA64 is not supported.

36. Database Server Hardware Requirement • Processors: Two - Quad Core Intel Xeon 3.33GHz, • 2x6MB Cache, • Memory: 4GB • Hard Drive: Six - 73GB SAS, 15K • Hard Drive Configuration: RAID1 / RAID5 • NIC: GB NIC • CD-ROM: DVD ROM • Power Supply: Redundant Power Supply • Operating System: Windows Server 2003 or 2008 [32-bit, 64- • bit], Standard Edition • Microsoft .NET 2.0 Framework • Note: IA64 is not supported • Database Software: Microsoft SQL Server 2005 or 2008 • (CPU or CAL)

37. Geospatial Data Package • iPad like tablet pc with touch screen, Wi-Fi+4G, video conferencing, GPS enabled, 100GB internal storage, > 2 pounds, battery life for 10 hours. • Google Earth application • Log in to WebEOC to enter incident report. • MapPro WMS application displays OGC compliant WMS.

38. Data Flow MCT

39. Mobile Command CenterOn-Site Scenario DC Metro Incident

40. 1. Report of a incident at the Smithsonian Metro Stop • A train has derailed due to unknown track error, slamming into the side wall of the tunnel • 854 people reported to be involved in the incident • Possible Electrical Fire • Reports of “odd smell” • Unknown if it is a gas leak or possible terrorist attack • DC Command Center Initiates Standup of MCT

41. 2. In-route • TRAN • Analysis of current DC road network for routing • Review of situation with Metro • COM • Establishes Com. Link with Data Center and First Responders on-site • MED • Evaluation of resource and staffing of nearby hospitals • FDMS • Assessment of responding units reporting • ID of additional recourse on standby • ENG • Acquiring Metro station building blue prints • ID utility lines in area • OHZ • Back up for ENG: Acquiring Gas Line data for possible leak • NHZ • Back up for FDMS • SEC • Acquiring inventory and locations of personal for site management • IT • Drives to Site

42. 3. On Site • TRAN • Work with DDOT to secure appropriate road closures and rerouting of traffic to support EMS • COM • Maintain Comm. • Compile Geo-Data Packets • MED • Because of earlier traffic accident, all non-critical individuals needing hospital car are being re-routed to Howard University • Notify GWU of burn and smoke inhalation cases in-route • FDMS • Request additional EMS for on-site medical care • ENG • Assessing Structure damage • Call in Civil Engineers for additional structure support • OHZ • Onsite personal ID leaks as natural gas, Washington Gas called in to repair • NHZ • Back up for FDMS: ID of secondary emergency response • SEC • Work with TRAN to set up road blocks , escorts and onsite crowd control • IT • Set up external LCD for onsite personal observation of incident • Fixing Technical problems inside command center

43. 4. Incident Duration • TRAN • Monitor traffic, Back up for COM as needed • COM • Push Reports back to DC command center • Publish public alerts through DC Alert • MED • Coordinate with EMS for transfer of individuals to appropriate hospitals • Work with FDMS for on-site medical administration • FDMS • Call in for additional resources: stretchers, medical supplies and “Jaw’s of Life” • Working with ENG on Search and Rescue • ENG • Monitoring structural vulnerability • ID of alternate Metro Access points • OHZ • Back up of ENG: Monitor and request additional supplies for Civil Engineers • NHZ • Back up for FDMS and MED: Manage Supplies for on-site medical administration • SEC • Because of nearby rally on the N. Mall, direct all attendees away from site • IT • Maintain Geo-Data Packets and tablet devices

44. 5. Incident Conclusion • TRAN • Notify DDOT when roads can be opened • Helping Metro establish extra transportation for Metro riders • COM • Providing incident reporting back to appropriate agencies • Update public on incident • MED • Coordinate patient transfer to other specialty hospitals in the area • FDMS • Review all individuals not taken to hospital are OK’d for release • ENG • Coordinate debris clean up /area safety • ID of neighboring structural damage • OHZ • ID secondary affects due to gas leak • NHZ • Back up ENG: Help with debris clean up and calling in heavy lifting equipment • SEC • Coordinate the establishment of parameter for inbound Accident Investigators • IT • Insure return of all Tablets and Equipment • Drives to nearest bar with best happy hour and large enough parking space

45. Conclusion • Mobile Command Vehicle • EMMCC Command Structure • Intelligence Data Structure and Distribution

46. Sources • U.S. Department of Homeland Security, Target Capabilities List: A companion to the National Preparedness Guidelines, (http://www.fema.gov/pdf/government/training/tcl.pdf )September 2007 • Homeland Security and Emergency Management Agency, http://www.dcema.dc.gov/dcema/site/default.asp?dcemaNav_GID • DC GIS Data Clearinghouse/Catalog, http://dcatlas.dcgis.dc.gov/catalog/ • Frontline Communications: http://www.frontlinecomm.com/index.cfm • Emedicine, CBRNE –Chemical Detection Equipment, http://emedicine.medscape.com/article/833933-overview • WebEOS, http://www.esi911.com • DC Government, http://www.dc.gov