Timmons Group ArcGIS Explorer Emergency Operations Solution


Published on

This presentation focuses on Timmons Group capabilities for emergency planning and management using GIS, ArcGIS Explorer and GIS technologies.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Cut through, EMS vehicle routing, water resources / etc…
  • ERG based plume – not guassian; parcel IDs, reverse 911
  • VDEM impact / risk zones / sector 22.5 degrees / 1 or 5 miles out; prepositions iodine capsules
  • Guassian plume model wind speed and direction for population and demographic impacts….again could be against parcels
  • Timmons Group ArcGIS Explorer Emergency Operations Solution

    1. 1. Emergency Management <br />Integration, Visualization and Decision Support Toolkits<br />Interoperability and Advanced<br />Visualization Techniques<br />for Emergency Response<br />and Planning<br />
    2. 2. Agenda<br />Agenda<br />Introductions<br />BackgroundSummaryScope<br />Demo<br />Next Steps<br />
    3. 3. Discussion Topics<br />GIS in Emergency Management<br />Many capabilities, many capacities<br />Emergency Operations Plan<br />2 Hypothetical Scenarios<br />Advanced Visualization<br />Immersion into the data<br />Spatial Analysis<br />Making data into actionable information<br />Interface & Interoperate<br />Sharing information between platforms, agencies<br />
    4. 4. The Problem and Solution<br /><ul><li>The Question…
    5. 5. How to integrate event data from an EM application into a GIS environment enabling an Emergency Operations Plan to be ‘actionable’ by…
    6. 6. Administering the data
    7. 7. Visualizing the data
    8. 8. Analyzing the information
    9. 9. Coordinating the planning, response, and recovery
    10. 10. The Solution…
    11. 11. ESRI ArcGIS Explorer
    12. 12. ESi WebEOC</li></li></ul><li>ESi WebEOC <br />Crisis management information management application<br />Web based interface<br />Data managed via customizable ‘status boards’<br />Standard status boards based on FEMA’s 15 emergency support functions<br />Functions<br />Administer events, tasks, resources, reports, road closures, shelters, FEMA / ICS forms, press releases, etc<br />Manage users, roles, permissions<br />Supports Common Alerting Protocol (CAP) messages<br />User base<br />DoD, DoI, DHS, EPA, NASA, 30 states, 200 county & city EOC’s<br />Corporations, hospitals, utility companies, universities<br />
    13. 13. Emergency Operations Plan<br />How do you make the EOP into an actionable SOP…<br />Mission<br />Scope<br />Organization<br />Concept of Operations<br />Actions<br />Critical Tasks<br />Phases of Operations<br /><ul><li>EOP Scenario: Hazmat spill on Interstate 64
    14. 14. EOP Scenario: Release from Lake Anna Nuclear Power Plant</li></li></ul><li>Interstate HazMat SpillAGX Visualization – Base Data<br />
    15. 15. Interstate HazMat SpillAGX Visualization – Resources<br />
    16. 16. Interstate HazMat SpillAGX Visualization – Traffic Cameras<br />
    17. 17. Interstate HazMat SpillAGX Analysis – Imagery<br />
    18. 18. Interstate HazMat SpillAGX Visualization – Weather Feeds<br />
    19. 19. Interstate HazMat SpillAGX Visualization – River Gauges<br />
    20. 20. Interstate HazMat SpillAGX Analysis – Drive Time<br />
    21. 21. Interstate HazMat SpillAGX Analysis – Plume<br />
    22. 22. Interstate HazMat SpillAGX Analysis – Select and Report<br />
    23. 23. Visualization<br />
    24. 24. Lake Anna Scenario<br />
    25. 25. Toxic Release from Power PlantAGX Visualization – Area of Interest<br />
    26. 26. Toxic Release from Power PlantAGX Analysis – Plume Model<br />
    27. 27. Toxic Release from Power Plant AGX Analysis – Demographic Stats<br />
    28. 28. Toxic Release from Power PlantAGX Analysis – Daytime population<br />
    29. 29. Integration - WebEOC<br />
    30. 30. Integration - WebEOC<br />
    31. 31. Integration – WebEOC / AGX<br />
    32. 32. Services<br />Services<br />Drive<br />Task<br />Drive<br />Task<br />Buffer<br />Task<br />Plume<br />Task<br />Buffer<br />Task<br />Plume<br />Task<br />Imagery<br />Task<br />Geocode<br />Task<br />Imagery<br />Task<br />Geocode<br />Task<br />Interoperability - Web Services<br />Emergency<br />Response<br />Emergency<br />Response<br />Emergency<br />Readiness<br />Emergency<br />Recovery<br />Emergency<br />Readiness<br />Emergency<br />Recovery<br />Econ<br />Dev<br />Utilities<br />Econ<br />Dev<br />Utilities<br />Web Services are implemented in products from all the major software vendors, making web services the most prevalent approach to implementing an SOA<br />Land Use<br />Planning<br />Public<br />Works<br />Land Use<br />Planning<br />Public<br />Works<br />Comm<br />Dev<br />Comm<br />Dev<br />
    33. 33. Integration – Security & Data<br />
    34. 34. Maintenance - Dashboard<br />
    35. 35. Traditional Software Update<br />Typically, to add new functionality to a mission-critical application, you must conduct a change management process.<br />You roll new data and functions through Development, Test and Production Environments to ensure errors are trapped and system uptime is maintained.<br /> PRODUCTION<br />APPLICATIONS <br />ArcSDE<br />ArcSDE<br />ArcSDE<br />Dev Instance<br />Production <br />Test Instance<br />Instance<br /><ul><li>This approach allows for the deployment of new data and functionality (widgets / tasks) with basically no impact to any production systems.
    36. 36. Maintenance and “long term feeding” is last in this presentation…but was considered first during the design of this project</li></li></ul><li>Services<br />Services<br />Drive<br />Task<br />Drive<br />Task<br />Buffer<br />Task<br />Plume<br />Task<br />Buffer<br />Task<br />Plume<br />Task<br />Imagery<br />Task<br />Geocode<br />Task<br />Imagery<br />Task<br />Geocode<br />Task<br />AGX – Update<br />Emergency<br />Response<br />Emergency<br />Response<br />Emergency<br />Readiness<br />Emergency<br />Recovery<br />Emergency<br />Readiness<br />Emergency<br />Recovery<br />Econ<br />Dev<br />Utilities<br />Econ<br />Dev<br />Utilities<br />Web Services are implemented in products from all the major software vendors, making web services the most prevalent approach to implementing an SOA<br />Land Use<br />Planning<br />Public<br />Works<br />Land Use<br />Planning<br />Public<br />Works<br />Comm<br />Dev<br />Comm<br />Dev<br />
    37. 37. Questions…<br /><ul><li>Agenda Recap
    38. 38. Introductions
    39. 39. BackgroundSummaryScope
    40. 40. Demo
    41. 41. Next Steps</li>