The Role of Location in Incident and Disaster Management
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

The Role of Location in Incident and Disaster Management

  • 309 views
Uploaded on

Presentation at Multi-POS Winter School, Ruka (Finland) Tuesday 11th Februari 2014 16:30-17:45

Presentation at Multi-POS Winter School, Ruka (Finland) Tuesday 11th Februari 2014 16:30-17:45

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
309
On Slideshare
305
From Embeds
4
Number of Embeds
3

Actions

Shares
Downloads
9
Comments
0
Likes
0

Embeds 4

http://www.slideee.com 2
http://www.linkedin.com 1
https://www.linkedin.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. The Presentation… > The Role of Location in Incident and Disaster Management Erik van der Zee Geodan Amsterdam Multi-POS Winter School Tuesday 11th Februari 2014 16:30-17:45
  • 2. The Dream Team… > T2.4 Location integration in crisis management lifecycle Erik van der Zee PhD Researcher (part time) Multi-POS Supervisor Geodan / VU Amsterdam e2.vander.zee@vu.nl Luis Bausá López PhD Researcher (full time) VU Amsterdam luis.bausalopez@vu.nl
  • 3. About Geodan > > > > > > Geo-IT specialist for more than 25 years Independent system integrator in GIS and Geo-ICT Founded by Prof. Dr. Henk Scholten and Dr. Evert Meijer Highly innovative (large R&D dep.) 130 employees Offices in • Amsterdam • Den Bosch • Madrid > OGC member > Associated partner in Multi-POS > Website www.geodan.nl
  • 4. > Topics for today
  • 5. The Topics… 1. 2. 3. 4. 5. 6. 7. 8. Overview of Disaster Types Spatial aspects of Disasters Positioning people and objects during Disasters Disaster Management • Key players (in the field and in the crisis center) • ICT Challenges (internet connections) Common Operational Picture and Situational Awareness Technology behind a Common Operational Picture Disaster Management in smart(er) environments Conclusions
  • 6. > Disaster types
  • 7. Traffic and Transport 1. Aviation accident 2. Accident on water
  • 8. Traffic and Transport 3. Traffic accidents on land
  • 9. Dangerous substances 4. Accidents with inflamable or explosive substances 5. Accidents with poisonous gasses
  • 10. Dangerous substances 6. Nuclear accidents (Tsjernobyl, Fukushima)
  • 11. Public Health 7. Threat of public health 8. Contaminating disease wave
  • 12. Infrastructure 9. Accidents in tunnels 10. Fire in large building
  • 13. Infrastructure 11. Collapse of large building 12. Failure of critical infrastructure (electricity, gas, water, communication)
  • 14. Population 13. Panic in crowds 14. Large scale disruptions of order
  • 15. Natural Disasters 15. Flooding 16. Forest Fires
  • 16. Natural Disasters 17. Extreme weather (cold/warm/wet/dry) e.g. heavy storm, extreme (ice) rain or snow or a heat or cold wave 18. Disasters at distance (in neighboring countries which have an effect on our country, e.g. nuclear, floods, forest fire, etc.)
  • 17. > Spatial aspects of Disasters
  • 18. From Indicent… to Disaster… > Relation between scale (extent/severity) and involved parties
  • 19. Where are the risks… > Risk Map of The Netherlands… • Location of Risk generators (dangerous objects or areas) • Risk distance zones (10^-6) • Effect distance zones (m) Lethality • Locations of Risk receivers (vulnerable objects or areas) > www.risicokaart.nl
  • 20. Source Area vs Effect Area > “Gasmal” and “Sector mal” (danger zones)
  • 21. > Positioning people and objects during Disasters…
  • 22. Where the !#%^&@# is …………….. ?!
  • 23. Lelystad Detention Centre
  • 24. The Challenge… > Can a position be determined? Indoor and Outdoor for different disaster types? > Which positional accuracy is needed and what can be delivered technically (demand and supply)? • Sometimes a rough indication of position is enough, sometimes not (e.g. Prison LBS Use Case… in or out the geofence, Room A is GO area Room B nextdoor is NOGO area) • It really depends on the situation (type of disaster and use case scenario) and the technology used
  • 25. Positioning > Indoor incidents and disasters (buildings, tunnels) > Outdoor incidents and disasters
  • 26. Mobile Modem > MOMO (used by fire departments and police)(www.eal.nl) > GPS lokalisation I/O (inputs / outputs) • Netwerk connectie • GPRS / UMTS communicatie of RAM Mobitex communicatie • WIFI • Bluetooth • Dual carrier functionality
  • 27. > Disaster Management
  • 28. The Safety and Security Chain
  • 29. Mono- versus Multi-disciplinary > Mono-disciplinary incidents > Multi-disciplinary disasters
  • 30. ICT in a Disaster situation Satellite communication GSM/3G communication Ad hoc WIFI network Ad hoc WIFI network X X X X Ad hoc WIFI network X X
  • 31. Field control center (COPI)
  • 32. Regional Crisis Center (RCC)
  • 33. Control Center situation
  • 34. Devices in the control center
  • 35. Network Infrastructure
  • 36. > Common Operational Picture and Situational Awareness  Information Sharing
  • 37. Information demand and supply
  • 38. Information Sharing Architecture Municipalities Justice Domain experts Control Rool domain Ambulance Citizen and Companies Disaster coordination GHOR Fire Department Security regions Defence Police COMMON DOMAIN
  • 39. Data and Functionality… Geo OOV Architectuur Gelderland Midden Gebruikers Brandweer Politie GHOR Meldkamer Gemeente ArcGIS Server Client Presentatie en Visualisatie CCS desktop applicaties Gebruikersfunctionaliteit Gasmal en Sectormal Meetopdracht en meetbericht Actueel en verwacht weerbeeld (KNMI) Verkeers situatie (VCNL) Functionele en data ontsluitings webservices Delen ROT beeld Locatie zoeken Gevaarlijke Stof fen Scheepvaart IVS 90 (RWS) (LIOGS/LMIP/ CRP) Berichten (tekst, audio) GBKN Top kaarten Kadaster Luchtf otos ACN AHN Location Based Services Risicokaart Bestuurlijke Grenzen WMS services Arnhem Cyclomedia en BridGIS Commerciële Services NWB CBS Buurt & Wijk OOV Basisregistraties Overige GIS Functionaliteit ArcGIS Alarmering & Attendering (LBS) Provinciale services GDI Services Touch Table Print en Rapportage Hoogwater HIS (RWS) WMS Service o.a. Luchtf otos Locatie Server VTS NCC/DCC/LOCC Expirimentele visualisatie Overige services (toekomst) WMS Services Haagse Ring Communicatie netwerk/ Beveiliging Virtual Earth CCS web applicaties CCS Mobiel Impact Analyse Sherpa/GMS Koppeling Service OOV Basis registraties en Kernregistraties Gelderland Midden Provincie Falk Geostreets Cyclo media Service HGM en Gemeente Arnhem Sirenes Rampen bestrijdings plannen BridGIS Commerciële basisregistraties Webservice Bereikbaar heidsplannen Aanvals plannen Bereikbaar heids plannen Kernregistraties HGM Peer-to-Peer secure communicatie en bestandsuitwisseling Mobiel Koper en Glasvezel (C2000, GPRS, UMTS) (Intranet, OOVnet, Haagse Ring) Waterschap NUTS Overige Gegevens
  • 40. COP-SA-NCW > COP: Common Operational Picture > SA: Situational Awareness > NCW: Net-Centric Working
  • 41. Common Operational Picture (COP)
  • 42. Common Operation Picture (detail)
  • 43. Common Operational Picture
  • 44. > Technology behind a Common Operational Picture
  • 45. Central Architecture Model
  • 46. Distributed Architecture model (p2p)
  • 47. Geodan Concurrent Online WebGIS (COW)
  • 48. COW Connectors Web sockets Programming API JS API C# API Java API User Interface Service API API - Fire propagation model Flood model - COW client
  • 49. COW works cross domain User Interface COW client Service API Intranet API User Interface COW client Service API API User Interface COW client Service API Internet API User Interface COW client Service API API
  • 50. Demo COW DEMO COW Luis + Erik (or be a crisis manager yourself ... http://research.geodan.nl/sites/foss4g) (COW on GitHub http://github.com/Geodan/cow)
  • 51. Map UI on COW infrastructure
  • 52. Concurrent Online WebGIS (COW)
  • 53. Phoenix Touchtable
  • 54. > Disaster Management in smart(er) environments (by use of ICT)
  • 55. E-Call example
  • 56. Location Based Services > Use of Geofences for notification and alerting
  • 57. Conclusions… > The Conclusions
  • 58. Conclusions > Disaster happen everywhere, indoor AND outdoor positioning scenarios > …And under difficult conditions, special demands on equipment > Communication lines and connections can be severely disturbed in DM situations, alternatives needed (plan B…) or local caching > There are mono- and multi-disciplinary disasters > A Common Operation Picture improves the Situational Awareness, especially in multi-disciplinary situations > There are 2 types of IT architectures to create a COP, the central model and the distributed (P2P) model
  • 59. The end