1 / 20

Building Disaster Resiliency through an Integrated Critical Infrastructure Alerting Program

Building Disaster Resiliency through an Integrated Critical Infrastructure Alerting Program. Daniel Stevens Manager, Emergency Planning. Background and project overview Demonstration – Vancouver 2010 Lessons learned and next steps Q&A. Integrating Situational Awareness. Three parts:

ann
Télécharger la présentation

Building Disaster Resiliency through an Integrated Critical Infrastructure Alerting Program

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Building Disaster Resiliency through an Integrated Critical Infrastructure Alerting Program Daniel StevensManager, Emergency Planning

  2. Background and project overview • Demonstration – Vancouver 2010 • Lessons learned and next steps • Q&A

  3. Integrating Situational Awareness Three parts: • Critical Infrastructure Alert Publishing • Emergency Information Data Publishing • Road Impact Data Publishing

  4. Integrating Situational Awareness Collaborators • City of Vancouver • EmerGeo Solutions Worldwide Inc. • E-Comm 911 • GeoConnections (Federal Government) • GeoBC (Provincial Government) • Translink

  5. Critical Infrastructure Those physical resources, services, and information technology facilities, networks and assets which, if disrupted or destroyed, would have a serious impact on the operation of an organization, industry sector, community, region or government. -Public Safety Canada

  6. Problem Situational awarenessWhat is happening that may impact the critical infrastructure I manage?

  7. Critical Infrastructure Operators Emergency Response Structure inBritish Columbia PECC PROVINCIAL CENTRAL COORDINATIONProvincial Emergency Coordination Centre PREOC PROVINCIAL REGIONAL COORDINATIONProvincial Regional Emergency Operations Centre(s) EOC SITE SUPPORTEmergency Operations Centre(s) AgencyDispatch(Police, Fire, Ambulance, etc.) ICP E-Comm & Others

  8. Considerations • Information overload: situational awareness - relevant, unobtrusive, and timely • Day-to-day benefit • Low or no learning curve • Automatic and manual alerting • Geospatial view (COP) • Security of CI data • Security of incident data • Scalability

  9. Police CAD Fire CAD E-Mail EmerGeoNav. COP Ambulance CAD E2MV/WS EmerGeoFusionPoint Solution Delivery methods/User interfaces Incidentdata source

  10. Alert E-Mail bob.smith@cicorporation.ca Alert Subscriberbob.smith@cicorporation.ca ALERT Info about the CI assetEmergency Contact:Security – 604-555-2345 Data is simulated and does not reflect actual locations of infrastructure assets

  11. Use during 2010 Winter Olympic Games • Office of Emergency Management tested system • Used to alert of moderate to severe motor vehicle incidents on roads with Olympic Lanes

  12. DEMO

  13. Benefit - Security • Security of critical infrastructure asset data • Security of incident data

  14. Benefit - Scalable • Planned/upcoming incidents • Multiple incident sources • Multiple CI layers

  15. Benefit – relevant information • Alerts are targeted – not everyone gets the same alerts

  16. Benefit – Low learning curve and day-to-day use • No need for user to take a course or do anything other than check e-mail • Actionable information can be included in e-mail • Day-to-day use, not only for disasters.

  17. Benefits – Geospatial View • Includes ability to log-in and see what’s going on via Common Operating Picture (COP).

  18. Lessons Learned • Data mapping between systems • Avoid black box • Data agreements just as complex as technical development • Work closely with developers and data providers to minimize misunderstandings

  19. Conclusion and Next Steps • Use by OEM Staff and Emergency Social Services • Fine-tune criteria for issuing alerts • Roll-out alerting to all COV CI owners • Pilot alerting with external CI owners • Add additional incident data sources • Pilot use for upcoming planned events • Expand to other alerting methods(e.g. SMS, via CAP-CP capable systems)

More Related