Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Seattle Fire Emergency Response Power Point - GITA 2008

720 views

Published on

Presented at GITA 2008 conference in Emergency Management Symposium track.

  • Be the first to like this

Seattle Fire Emergency Response Power Point - GITA 2008

  1. 1. GIS at the Seattle Fire Department: New Tools in the Emergency Management Arsenal Peter Di Turi, GIS Analyst Thomas Richardson, Battalion Chief
  2. 2. Presentation Items <ul><li>The Force: Seattle Fire Operations </li></ul><ul><li>First Shots: GIS Emergence </li></ul><ul><li>Big Wave: CAD Goes Geospatial </li></ul><ul><li>Latest Tools: First Responder Applications </li></ul><ul><li>Next Stages: Opportunities for the Future </li></ul>
  3. 3. The Force: Seattle Fire Operations <ul><li>The “Where”: </li></ul><ul><ul><li>84 square-mile land area, the city of Seattle </li></ul></ul><ul><ul><li>34 fire stations (32 land, 1 water, 1 land/water) </li></ul></ul><ul><ul><li>Medic One facility @ Harborview Medical Center </li></ul></ul><ul><ul><li>New Fire Alarm Center (with City EOC) </li></ul></ul><ul><ul><li>New Joint Training Facility </li></ul></ul><ul><ul><li>5 Operational battalion areas, Medic One battalion </li></ul></ul><ul><ul><li>Mutual aid to surrounding King County jurisdictions </li></ul></ul>
  4. 4. Some of our stations…
  5. 5. “ Our” world…
  6. 6. The Force: Seattle Fire Operations <ul><li>The “What”: </li></ul><ul><ul><li>Fire: 32 Engines, 11 Ladder trucks </li></ul></ul><ul><ul><li>EMS: 3 Aid Cars, 7 Medic Vans, Cycle Medic </li></ul></ul><ul><ul><li>H 2 O: 2 fireboats (Fresh and Salt) </li></ul></ul><ul><ul><li>Specialty: Command Van, HazMat Van, Tech Rescue Van, Air Units, Hose Wagons </li></ul></ul><ul><ul><li>Admin Cars: 6 BCs, Deputy1, Staff10, Safety, Fire Marshal, Command Staff, MIS </li></ul></ul>
  7. 7. Some common apparatus…
  8. 8. Our specialty units…
  9. 9. The Force: Seattle Fire Operations <ul><li>Most Importantly, The “Who”: </li></ul><ul><ul><li>2000 Population: 563,400 </li></ul></ul><ul><ul><li>Daytime population: 1,500,000 (est.) </li></ul></ul><ul><ul><li>Personnel Profile (2007): </li></ul></ul><ul><ul><ul><li>Uniformed: 1,030 (all EMT certified) </li></ul></ul></ul><ul><ul><ul><li>On-duty strength: 210 </li></ul></ul></ul><ul><ul><ul><li>Department Chiefs: 36 </li></ul></ul></ul><ul><ul><ul><li>Paramedics: 81 </li></ul></ul></ul><ul><ul><ul><li>Civilian: 80 </li></ul></ul></ul>
  10. 11. Presentation Items <ul><li>The Force: Seattle Fire Operations </li></ul><ul><li>First Shots: GIS Emergence </li></ul><ul><li>Big Wave: CAD Goes Geospatial </li></ul><ul><li>Latest Tools: First Responder Applications </li></ul><ul><li>Next Stages: Opportunities for the Future </li></ul>
  11. 12. First Shots: GIS Emergence <ul><li>Seattle Fire Early GIS Milestones: </li></ul><ul><ul><li>First GIS work: 1993 – Geocoding for CAD </li></ul></ul><ul><ul><li>First GIS deliverable: 1994 - Map Book </li></ul></ul><ul><ul><li>First GIS large map: 1995 – Battalion 7 Map </li></ul></ul><ul><ul><li>First GIS dataset created: 1996 - Areaways </li></ul></ul><ul><ul><li>First GIS application: 1997 – PreFire </li></ul></ul><ul><ul><li>First GIS business analysis: 1999 – Deccan </li></ul></ul>
  12. 13. Sample Map Book page…
  13. 14. Battalion 7 Map – 2 nd edition of first large map…
  14. 15. Original PreFire program interface…
  15. 16. Original PreFire program interface…requiring ArcView…
  16. 17. Original PreFire program interface… MS Access…
  17. 18. Original PreFire program interface…PowerPoint files…
  18. 19. Original PreFire program interface…only for BC’s…
  19. 20. Original PreFire program interface…not on all rigs…
  20. 21. CAD Data Turnkey Analysis…
  21. 22. First Shots: GIS Emergence <ul><li>Seattle Fire Early Millennium Milestones: </li></ul><ul><ul><li>First GIS analyst hired: December, 2000 </li></ul></ul><ul><ul><li>First GIS application modified: PreFire </li></ul></ul><ul><ul><li>First GIS maps: Nisqually Earthquake set </li></ul></ul><ul><ul><li>2001: Developed map standards for station, inspection, thematic and area maps </li></ul></ul><ul><ul><li>2002: Acquired GIS hardware and software, hired intern to support sudden demand </li></ul></ul>
  22. 23. Nisqually 02/28/01 Quake: Just down the sidewalk…
  23. 24. Nisqually 02/28/01 Quake: The immediate area map…
  24. 25. Nisqually 02/28/01 Quake: Neighborhood isolation?…
  25. 26. Nisqually 02/28/01 Quake: Analyzing responsiveness…
  26. 27. So the requests begin to pour in: Standard Station/ Rig Maps…
  27. 28. Standard Inspection District Maps…
  28. 29. Specific Area Maps…
  29. 30. First Shots: GIS Emergence <ul><li>First GIS Major Event: TOPOFF2 (2003) </li></ul><ul><ul><li>GIS staff reported to Fire Ops instead of MIS </li></ul></ul><ul><ul><li>36-hour around-the-clock GIS support </li></ul></ul><ul><ul><li>Created small and large-scale maps on-the-fly </li></ul></ul><ul><ul><li>Incorporated NARAC plume-model shapefiles </li></ul></ul><ul><ul><li>Provided data support to City EOC GIS staff </li></ul></ul>
  30. 31. TOPOFF2: The site…
  31. 32. TOPOFF2: First Map (One Mile Diameter)…
  32. 33. TOPOFF2: Geiger Counter Readings with GPS
  33. 34. TOPOFF2: Using NARAC’s GIS data of plume model…
  34. 35. First Shots: GIS Emergence <ul><li>GIS support is now part of every event/drill </li></ul><ul><ul><li>Map series provided for Resource Management Center (RMC) central support </li></ul></ul><ul><ul><li>Detailed/area maps provided as part of Incident Action Plans for events and drills </li></ul></ul><ul><ul><li>2004: GIS client viewer application deployed in RMC, Command Van with localized data sets </li></ul></ul><ul><ul><li>GIS staff available for on-site, on-call support </li></ul></ul>
  35. 36. So one event map…
  36. 37. … leads to another event map…
  37. 38. ..and leads to another…(you get the idea)…
  38. 39. First Shots: GIS Emergence <ul><li>But, as in TOPOFF2, drawbacks happen… </li></ul><ul><ul><li>Getting the font sizes right – while in a hurry </li></ul></ul><ul><ul><li>Disconnect between IC needs and GIS products </li></ul></ul><ul><ul><li>GIS expertise really needed at command post </li></ul></ul><ul><ul><li>No runner to help facilitate map/data exchanges </li></ul></ul><ul><ul><li>No GIS data provided on-site - just paper maps </li></ul></ul><ul><ul><li>GIS staff overwhelmed by HQ and EOC needs </li></ul></ul>
  39. 40. Presentation Items <ul><li>The Force: Seattle Fire Operations </li></ul><ul><li>First Shots: GIS Emergence </li></ul><ul><li>Big Wave: CAD Goes Geospatial </li></ul><ul><li>Latest Tools: First Responder Applications </li></ul><ul><li>Next Stages: Opportunities for the Future </li></ul>
  40. 41. Big Wave: CAD Goes Geospatial <ul><li>Seattle Fire implements new CAD in November, 2003 </li></ul><ul><li>GIS-Specific Impacts : </li></ul><ul><ul><li>New mapping interface for Ops and dispatchers </li></ul></ul><ul><ul><li>Live Routing replaces run stream dispatching </li></ul></ul><ul><ul><li>Improved geolocation of common place names </li></ul></ul><ul><ul><li>Two-way data exchange with RMS </li></ul></ul>
  41. 42. Big Wave: CAD Goes Geospatial <ul><li>GIS-specific solutions to CAD’s success: </li></ul><ul><ul><li>User-customizable map interface </li></ul></ul><ul><ul><li>Update process provides accurate map data </li></ul></ul><ul><ul><li>Update process provides accurate street network </li></ul></ul><ul><ul><li>Update process improves geovalidation and geolocation </li></ul></ul><ul><ul><li>QA process increases accuracy of premises </li></ul></ul>
  42. 43. CAD Implementation: Before - Shapefiles in GIS…
  43. 44. CAD Implementation: After – Fire Stations, Incidents, Units, Battalion Areas, Shortest Path Dispatch, etc.…
  44. 45. CAD Premise QA: From Authoritative Inspection DB.…
  45. 46. CAD Premise QA: …to RMS QA module for 2 nd check…
  46. 47. CAD Premise QA: …to CAD, where it HAS to be right…
  47. 48. Big Wave: CAD Goes Geospatial <ul><li>GIS-related remaining challenges </li></ul><ul><ul><li>Map interface in MDC not maintainable </li></ul></ul><ul><ul><li>Map interface in CAD can be easier to maintain </li></ul></ul><ul><ul><li>CAD’s geovalidation isn’t GIS validation </li></ul></ul><ul><ul><li>Desire to incorporate inspection & prefire data </li></ul></ul><ul><ul><li>Additional desire for reporting from the MDC </li></ul></ul><ul><ul><ul><li>Pandemic situations </li></ul></ul></ul><ul><ul><ul><li>Disaster management </li></ul></ul></ul>
  48. 49. Presentation Items <ul><li>The Force: Seattle Fire Operations </li></ul><ul><li>First Shots: GIS Emergence </li></ul><ul><li>Big Wave: CAD Goes Geospatial </li></ul><ul><li>Latest Tools: First Responder Applications </li></ul><ul><li>Next Stages: Opportunities for the Future </li></ul>
  49. 50. First Responder Applications <ul><li>PreFire Data and Drawings </li></ul><ul><li>Pandemic Situation Reporting </li></ul><ul><li>Disaster Incident Reporting </li></ul>
  50. 51. First Responder Applications <ul><li>PreFire Data and Drawings </li></ul><ul><ul><li>New joint Inspection/Prefire Database (IPD) </li></ul></ul><ul><ul><li>Authoritative Source for CAD Premise Data </li></ul></ul><ul><ul><li>Target users are no longer only Battalion Chiefs </li></ul></ul><ul><ul><li>Drawings/data maintained by Fire Ops, not MIS </li></ul></ul><ul><ul><li>MDC application is fairly easy to use </li></ul></ul>
  51. 52. PreFire: Now Maintained WITH Inspections BY Ops…
  52. 53. PreFire: Mobile Data Client (MDC) Without PreFire…
  53. 54. PreFire: MDC With PreFire search capability…
  54. 55. PreFire: MDC With PreFire Data at a touch – literally…
  55. 56. PreFire: MDC With PreFire Drawings at night…
  56. 57. First Responder Applications <ul><li>Disaster Incident Reporting </li></ul><ul><ul><li>Piloted for 2007 Earthquake drills </li></ul></ul><ul><ul><li>Ease of reporting in MDC </li></ul></ul><ul><ul><ul><li>Minimal amount of data to collect </li></ul></ul></ul><ul><ul><ul><li>Easy to use </li></ul></ul></ul><ul><ul><ul><li>Keyboard needed only for desired comments </li></ul></ul></ul><ul><ul><ul><li>Lots of quick error checking </li></ul></ul></ul><ul><ul><li>GIS prototype reporting application </li></ul></ul>
  57. 58. Disaster reporting: MDC Event Entry Web application…
  58. 59. Disaster reporting: Event reporting application…
  59. 60. Disaster reporting: The GIS view…
  60. 61. First Responder Applications <ul><li>Pandemic Situation Found Reporting </li></ul><ul><ul><li>Piloted in early 2007 </li></ul></ul><ul><ul><li>Ease of reporting in MDC </li></ul></ul><ul><ul><ul><li>Minimal amount of data to collect </li></ul></ul></ul><ul><ul><ul><li>Easy to use </li></ul></ul></ul><ul><ul><ul><li>Keyboard NOT NEEDED!!! </li></ul></ul></ul><ul><ul><ul><li>Lots of quick error checking </li></ul></ul></ul><ul><ul><li>GIS prototype reporting application </li></ul></ul>
  61. 62. Pandemic Situation Found: MDC Data Selection…
  62. 63. Pandemic Situation Found: MDC Data Entry…
  63. 64. Pandemic Situation Found: The GIS view…
  64. 65. First Responder Applications <ul><li>Good, but not good enough </li></ul><ul><ul><li>Balancing big visuals versus big buttons </li></ul></ul><ul><ul><li>Having readable, usable, rapidly-acquired data </li></ul></ul><ul><ul><li>Maps need accuracy; layers fully displayable </li></ul></ul><ul><ul><li>Best routing capabilities needed </li></ul></ul><ul><ul><li>Prefire entry done by hand instead of PC/PDA </li></ul></ul><ul><ul><li>Need 3-D geolocation of FFs with 1’ accuracy </li></ul></ul><ul><li>GIS needs to serve the intelligence cycle (monitoring, evaluation, feedback) </li></ul>
  65. 66. Presentation Items <ul><li>The Force: Seattle Fire Operations </li></ul><ul><li>First Shots: GIS Emergence </li></ul><ul><li>Big Wave: CAD Goes Geospatial </li></ul><ul><li>Latest Tools: First Responder Applications </li></ul><ul><li>Next Stages: Opportunities for the Future </li></ul>
  66. 67. Opportunities for the Future <ul><li>Derivative Products </li></ul><ul><ul><li>PreFire MDC app today -> New integrated CAD/PreFire application on MDC tomorrow… </li></ul></ul><ul><ul><li>Disaster drill GIS app today -> New ICS-compliant application tomorrow… </li></ul></ul><ul><ul><li>Situation found GIS app today -> Advanced situation found application...TODAY!!! </li></ul></ul><ul><li>Better Communication Methods </li></ul>
  67. 68. Opportunities for the Future <ul><li>I ntegrated CAD/PreFire application on MDC </li></ul><ul><ul><li>Uses a mapping interface where the map is now easily maintainable </li></ul></ul><ul><ul><li>Simplifies IT application maintenance needs </li></ul></ul><ul><ul><li>The PreFire is called from the CAD view if requested and can be better controlled </li></ul></ul><ul><ul><li>Use GIS wider search option to catch exposures </li></ul></ul>
  68. 69. The new Mobile app: A map that can be maintained!…
  69. 70. Integrated PreFire Button In 1 MDC App Instead of 2…
  70. 71. Opportunities for the Future <ul><li>New ICS-compliant disaster application </li></ul><ul><ul><li>Integrate CAD and situational reports (data from disaster drill application) </li></ul></ul><ul><ul><li>Uses Standard NIMS-compliant on-line forms for unplanned/planned incident management </li></ul></ul><ul><ul><li>Incorporates Virtual Earth and leverages existing GIS data investment </li></ul></ul>
  71. 72. ICS Compliant Application…
  72. 73. ICS Compliant Application… with spatial components
  73. 74. Opportunities for the Future <ul><li>New advanced situation found application </li></ul><ul><ul><li>Includes ability to create triggers based upon </li></ul></ul><ul><ul><ul><li>Time period </li></ul></ul></ul><ul><ul><ul><li>Criteria met </li></ul></ul></ul><ul><ul><ul><li>Geographic location or cluster </li></ul></ul></ul><ul><ul><ul><li>Number of occurrences </li></ul></ul></ul><ul><ul><li>Tracking and reporting on continual basis </li></ul></ul><ul><ul><li>Has mapping interface </li></ul></ul><ul><ul><li>Not restricted to EMS incidents </li></ul></ul>
  74. 75. Pandemic Situation App: Tracking The Events…
  75. 76. Pandemic Situation App: In Place and Gaining Ground…
  76. 77. Pandemic Situation App: In Place and Gaining Ground…
  77. 78. Opportunities for the Future <ul><li>Better Communication Methods </li></ul><ul><ul><li>GIS professionals need access to National Geospatial Agency (NGA) resources </li></ul></ul><ul><ul><li>Avoid lack of or wrong communication: </li></ul></ul><ul><ul><ul><li>E.g., 2007 California wildfires </li></ul></ul></ul><ul><ul><ul><ul><li>wrong tools were used to assess situations </li></ul></ul></ul></ul><ul><ul><ul><ul><li>limited data was collected </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Information shared with state EOC but not with IC </li></ul></ul></ul></ul>
  78. 79. Presentation Items <ul><li>The Force: Seattle Fire Operations </li></ul><ul><li>First Shots: GIS Emergence </li></ul><ul><li>Big Wave: CAD Goes Geospatial </li></ul><ul><li>Latest Tools: First Responder Applications </li></ul><ul><li>Next Stages: Opportunities for the Future </li></ul>
  79. 80. Summary <ul><li>Seattle Fire has and will continue to have diverse needs for GIS applications. </li></ul><ul><li>Past success and positive feedback always increases the appetite for more GIS products. </li></ul><ul><li>Easy data entry and query applications provide opportunities for better real-time decisions. </li></ul><ul><li>COMMUNICATION and GIS go hand-in-hand in emergency management </li></ul><ul><li>Today’s solutions are great tools in the arsenal, but they form the need for better ones tomorrow. </li></ul>
  80. 81. Questions? Please ask! <ul><li>Peter Di Turi, GIS Analyst, Admin/MIS </li></ul><ul><ul><li>E-mail: [email_address] </li></ul></ul><ul><ul><li>Phone: 206.386.1542 </li></ul></ul><ul><li>Thomas Richardson, Battalion 4 Chief, Ops A shift </li></ul><ul><ul><li>E-mail: [email_address] </li></ul></ul><ul><ul><li>Phone: 206.386.1418 </li></ul></ul><ul><li>Seattle Fire Department Headquarters </li></ul><ul><li>301 2 nd Avenue South </li></ul><ul><li>Seattle, WA 98104-2680 USA </li></ul>

×