Embed Size (px)
Citation preview
D7.3
D7.3
HEIMDALL End-Users’ manual
Instrument Collaborative Project
Call / Topic H2020-SEC-2016-2017/H2020-SEC-2016-2017-1
Project Title Multi-Hazard Cooperative Management Tool for Data Exchange, Response Planning and Scenario Building
Project Number 740689
Project Acronym HEIMDALL
Project Start Date 01/05/2017
Project Duration 45 months (extended 3 months due to COVID-19)
Contributing WP WP 7
Dissemination Level PU
Contractual Delivery Date M42
Actual Delivery Date 09/11/2020
Editor David Martín (PCF)
Contributors Solange Martínez, Lena Schlegel (EKUT), Benjamin Barth, Monika Friedemann, Christian Knopp, Sandro Martinis,
HEIMDALL [740689] D7.3
Alberto Viseras Ruiz (DLR), Alexandros Bartzas, Spyros Pantazis, (SPH), Jordi Vendrell, Celia Conde (PCF), Miguel Mendes (TSYL), Diana Mathew, Angel Grablev, Joseph Muna (AVA), Stéphanie Battiston, Julien Briant (UNISTRA), Guido Luzi (CTTC), José Becerra, Jordi Marturià (ICGC), Flavio Pignone (CIMA), Daniel Milla (INT-PD), Edgar Nebot, Jordi Pagès, Laia Estivill, Claudi Gallardo (INT-CFRS), Jesper Bachmann (FBBR), Bruce Farquharson (SFRS), Silvia Venier, Nedim Jasic (CRI)
HEIMDALL [740689] D7.3
09/11/2020 i
Document History
Version Date Modifications Source
0.1 16/7/2020 First draft PCF
0.2 07/09/2020 Review on specific modules by technical partners DLR-KN, DLR-DFD, SPH, ICGC, CTTC, TSYL, CIMA
0.3 25/09/2020 Second draft PCF
0.4 08/10/2020 Overall technical review DLR-KN
0.5 15/10/2020 First full version PCF
0.6 22/10/2020 Quality Assessment INT-PD, INT-FRS
1.0.D 26/10/2020 Final adjustments PCF
1.0.F 09/11/2020 Approved version DLR-KN
HEIMDALL [740689] D7.3
09/11/2020 ii
Table of Contents
List of Figures......................................................................................................................iv
List of Images ...................................................................................................................... v
List of Tables ....................................................................................................................... x
List of Acronyms .................................................................................................................xi
Executive Summary ...........................................................................................................14
1 HEIMDALL platform ....................................................................................................15
1.1 Objectives ..............................................................................................................15
1.2 The HEIMDALL approach ......................................................................................15
1.3 Operational use ......................................................................................................16
2 System architecture ....................................................................................................17
3 System usage ..............................................................................................................19
3.1 Log in – HEIMDALL web portal ..............................................................................19
3.2 Graphical User Interfaces (GUI) .............................................................................19 Main screen features .......................................................................................20 Other features .................................................................................................24
3.2.2.1 Coordinates and map bounds ..................................................................24 3.2.2.2 Add Marker (Waypoints) ...........................................................................24 3.2.2.3 Weather forecast ......................................................................................26 3.2.2.4 Screenshots .............................................................................................28
3.3 Scenario management ...........................................................................................28 Scenario creation/edition .................................................................................28
3.3.1.1 Landscape scenario .................................................................................30 3.3.1.2 Incident scenario ......................................................................................32
Weather Conditions .........................................................................................36 Observed Hazard Behaviour ...........................................................................37 Response Plans ..............................................................................................40 Decisions ........................................................................................................45 Lessons Learnt ................................................................................................46 Images ............................................................................................................47 Documents ......................................................................................................48 Common Challenge Capabilities (CCC) ..........................................................49
Alerts ...............................................................................................................51
3.4 Hazard simulation tools ..........................................................................................57 Fire simulator ..................................................................................................58
3.4.1.1 Simulation settings ...................................................................................58 3.4.1.2 Simulation results .....................................................................................61
Landslide simulator .........................................................................................62 3.4.2.1 Rockfall simulator .....................................................................................63 3.4.2.2 Debris flows simulator ..............................................................................66 3.4.2.3 Rotational landslide simulator ...................................................................71 3.4.2.4 Landslide rainfall analysis ........................................................................74
Flood simulator ................................................................................................79 3.4.3.1 Simulation settings ...................................................................................79
HEIMDALL [740689] D7.3
09/11/2020 iii
3.4.3.2 Simulation results .....................................................................................83 Manage simulation results ...............................................................................83
3.4.4.1 Manage simulation from the active incident scenario ...............................84 3.4.4.2 Import simulations from other scenarios ...................................................86
3.5 Risk Assessment ....................................................................................................86 Impact Assessment .........................................................................................87
3.5.1.1 Impact buildings/GOIs ..............................................................................87 3.5.1.2 Impact Roads ...........................................................................................90
Impact Summary .............................................................................................92 3.5.2.1 Impact buildings/GOIs ..............................................................................92 3.5.2.2 Impact Roads ...........................................................................................94
3.6 Scenario Matching..................................................................................................96
3.7 Situation Report (SitRep)...................................................................................... 100
3.8 Data sources ........................................................................................................ 103 Satellite-based data: Earth Observation products .......................................... 104 Ground-based data: In-situ sensors and GB-SAR ......................................... 105
3.8.2.1 Geotechnical and hydrological landslide monitoring systems ................. 105 3.8.2.2 GB-SAR Landslide Monitoring system ................................................... 108
Aerial-based data: Drones ............................................................................. 110
3.9 Data sharing and communication ......................................................................... 111 Chat .............................................................................................................. 111 HEIMDALL application .................................................................................. 113
3.9.2.1 Log in – HEIMDALL application .............................................................. 113 3.9.2.2 Main screen features .............................................................................. 113 3.9.2.3 HEIMDALL app chat .............................................................................. 114 3.9.2.4 HEIMDALL app map .............................................................................. 115 3.9.2.5 HEIMDALL app Situation Report ............................................................ 115 3.9.2.6 HEIMDALL app share picture and share location options ....................... 116 3.9.2.7 HEIMDALL app Logout and Download Offline map options.................... 119 3.9.2.8 HEIMDALL app waypoints ..................................................................... 120
Catalogue ...................................................................................................... 121 3.9.3.1 Catalogue publication ............................................................................. 121 3.9.3.2 Catalogue subscription ........................................................................... 123
4 Conclusions ............................................................................................................... 127
5 References ................................................................................................................. 128
HEIMDALL [740689] D7.3
09/11/2020 iv
List of Figures
Figure 1-1. Vee model of system engineering. .....................................................................15
Figure 1-2. The HEIMDALL approach. .................................................................................16
Figure 2-1. Diagram of the HEIMDALL system architecture..................................................17
Figure 2-2. Catalogue structure with the example of two Local Units. ...................................18
Figure 3-1. Common Challenge Capabilities (CCC) matrix from the FIRE-IN project. ...........50
Figure 3-2. Landslide types simulated in HEIMDALL. ...........................................................62
HEIMDALL [740689] D7.3
09/11/2020 v
List of Images
Image 3-1. HEIMDALL user log in screen. ............................................................................19
Image 3-2. Main screen of the HEIMDALL platform. .............................................................20
Image 3-3. Existing scenarios. ..............................................................................................21
Image 3-4. User settings. .....................................................................................................21
Image 3-5. Notification message. .........................................................................................22
Image 3-6. Assets on the HEIMDALL platform. ....................................................................22
Image 3-7. Map Control options on the HEIMDALL platform. ...............................................23
Image 3-8. Map layer option on the HEIMDALL platform. .....................................................23
Image 3-9. Other features on the HEIMDALL platform GUI ..................................................24
Image 3-10. Coordinates and map bounds. ..........................................................................24
Image 3-11. Add marker on the GUI. ....................................................................................25
Image 3-12. Add marker – Send marker as Waypoints. ........................................................25
Image 3-13. Add marker – Create waypoint. ........................................................................25
Image 3-14. Add marker – List of waypoints associated with an active scenario. .................26
Image 3-15. Weather forecast – Get weather and get weather grid buttons on the GUI. ......26
Image 3-16. Weather forecast – Get weather. ......................................................................27
Image 3-17. Weather forecast – Get weather grid. ...............................................................27
Image 3-18. Weather forecast – Weather forecast on the GUI for various hourly time intervals. .............................................................................................................................................28
Image 3-19. Screenshots – Save screenshots......................................................................28
Image 3-20. Creation of a new scenario at landscape and incident level. .............................29
Image 3-21. Scenario structure. ...........................................................................................30
Image 3-22. Landscape scenario settings. ...........................................................................30
Image 3-23. Landscape scenario – Set Landscape Scenario Area. ......................................31
Image 3-24. Incident scenario parameters. ...........................................................................32
Image 3-25. Incident scenario – List of snapshots created in each scenario. ........................33
Image 3-26. Incident Scenario – Set Incident Location. ........................................................33
Image 3-27. Incident Scenario – Set Scenario Area. ............................................................34
Image 3-28. Weather conditions. ..........................................................................................36
Image 3-29. Weather conditions – Weather parameters. ......................................................37
Image 3-30. Observed Hazard Behaviour. ............................................................................38
Image 3-31. Observed Hazard Behaviour – Fire behaviour parameters. ..............................38
Image 3-32. Response Plans. ..............................................................................................40
Image 3-33. Response Plans – Settings. .............................................................................41
Image 3-34. Response Plans - Situation assessment. ..........................................................42
Image 3-35. Response Plans – Measures. ...........................................................................44
Image 3-36. Response Plans – Measures – New decision. ..................................................44
HEIMDALL [740689] D7.3
09/11/2020 vi
Image 3-37. Decisions. .........................................................................................................45
Image 3-38. Decisions – List of decision entered to the platform. .........................................45
Image 3-39. Lessons learnt. .................................................................................................46
Image 3-40. Lessons learned. ..............................................................................................46
Image 3-41. Images. ............................................................................................................48
Image 3-42. Images – Settings. ............................................................................................48
Image 3-43. Documents. ......................................................................................................49
Image 3-44. Documents – Settings. ......................................................................................49
Image 3-45. Common Capability Challenges. .......................................................................51
Image 3-46. Common Capability Challenges – Lessons learnt available associated with challenges and capabilities of the scenario. ..........................................................................51
Image 3-47. Alerts. ...............................................................................................................52
Image 3-48. Alerts – New Alert. ............................................................................................53
Image 3-49. Alerts – Alert area. ............................................................................................53
Image 3-50. Alerts – Audience. ............................................................................................53
Image 3-51. Alerts – Hazard. ................................................................................................53
Image 3-52. Alerts – Timing..................................................................................................54
Image 3-53. Alerts – Action. .................................................................................................54
Image 3-54. Alerts – Translations. ........................................................................................55
Image 3-55. Alerts – Resources. ..........................................................................................55
Image 3-56. Alerts – Sender. ................................................................................................55
Image 3-57. Alerts – Check and dispatch. ............................................................................55
Image 3-58. Alerts – New Situation Report. ..........................................................................56
Image 3-59. Create a New Simulation. .................................................................................58
Image 3-60. Fire simulator – Simulation settings. .................................................................58
Image 3-61. Fire simulator – Set Ignition Features. ..............................................................59
Image 3-62. Fire simulator – Set firebreak features. .............................................................60
Image 3-63. Fire simulator – Custom weather values. ..........................................................60
Image 3-64. Fire simulator – Display of fire perimeter output for 3 h, 6 h, 9 h and 12 h after the fire starts. .............................................................................................................................61
Image 3-65. Fire simulator – Display of other simulation outputs: A-Flame Length (m), B-Fire Line Intensity (kW/m2), C-Minimum Travel Time (h), D-Arrival Time (h). ...............................62
Image 3-66. Rockfall simulation settings...............................................................................63
Image 3-67. Rockfall simulator – Set simulation area. ..........................................................64
Image 3-68. Rockfall simulator – Sources. ...........................................................................64
Image 3-69. Rockfall simulator – Display of simulation results based on susceptibility of the area to be affected: high susceptibility (in red); medium susceptibility (in yellow); and low susceptibility (in green). ........................................................................................................66
Image 3-70. Debris flows simulation settings. .......................................................................67
Image 3-71. Debris flows simulator – Set simulation area. ...................................................68
HEIMDALL [740689] D7.3
09/11/2020 vii
Image 3-72. Debris flow simulator – Sources. ......................................................................68
Image 3-73. Debris flow simulator – Display of simulation results based on susceptibility of the area to be affected: high susceptibility (in red); medium susceptibility (in yellow); and low susceptibility (in green). ........................................................................................................70
Image 3-74. Rotational landslide simulation settings. ...........................................................71
Image 3-75. Rotational landslide simulator – Set simulation area. ........................................72
Image 3-76. Rotational landslide simulator – Display of simulation results based on susceptibility of the area to be affected: high susceptibility (in red); medium susceptibility (in yellow); and low susceptibility (in green). ..............................................................................74
Image 3-77. Landslide rainfall analysis simulation settings. ..................................................75
Image 3-78. Landslide rainfall analysis – Set simulation location. .........................................75
Image 3-79. Landslide rainfall simulation results – Event rainfall. .........................................76
Image 3-80. Landslide rainfall simulation results – Antecedent rainfall. ................................77
Image 3-81. Landslide rainfall simulation results – ID curve triggering rainfall. .....................77
Image 3-82. Landslide rainfall simulation results – ID curve forecasting rainfall for 24 h. ......78
Image 3-83. Landslide rainfall simulation results – ID curve forecasting rainfall for 3 days. ..78
Image 3-84. Landslide rainfall simulation results – ID curve forecasting rainfall for 7 days. ..79
Image 3-85. Flood simulator settings. ...................................................................................80
Image 3-86. Flood simulator – Set simulation area. ..............................................................81
Image 3-87. Flood simulator – Discharge points. ..................................................................82
Image 3-88. Flood simulator – Discharge value. ...................................................................82
Image 3-89. Flood simulator – Display of simulation results for a discharge value of 1,100 m3/s at time steps 4 h, 8 h, 12 h and 16 h after the river overflowing starts. .................................83
Image 3-90. Managing simulation results – Simulation and Other Associated Data. .............84
Image 3-91. Managing simulation results – List of simulation results. ...................................84
Image 3-92. Managing simulation results – Simulation results menu. ...................................85
Image 3-93. Managing simulation results – Display simulation results using the URL. ........85
Image 3-94. Managing simulation results – Display of simulation screenshot. ......................86
Image 3-95. Managing simulation results – Import simulation from other scenarios. ............86
Image 3-96. Impact Assessment – Select one simulation. ....................................................87
Image 3-97. Impact Assessment menu for Buildings/GOIs and Roads. ................................88
Image 3-98. Impact Assessment for buildings/GOIs – IA Request IA. ..................................88
Image 3-99. Impact Assessment for buildings and GOIs – Results. ......................................88
Image 3-100. Impact Assessment for buildings and GOIs – Impact information. .................89
Image 3-101. Impact Assessment for buildings and GOIs – Screenshot. .............................90
Image 3-102. Impact Assessment menu for Roads. .............................................................90
Image 3-103. Impact Assessment for Roads – IA Request. ..................................................90
Image 3-104. Impact Assessment for Roads – Results. .......................................................90
Image 3-105. Impact Assessment for Roads – Impact information. .....................................91
Image 3-106. Impact Assessment for Roads – Screenshot. .................................................92
HEIMDALL [740689] D7.3
09/11/2020 viii
Image 3-107. Impact Summary for buildings/GOIs – Select Area of Interest. .......................93
Image 3-108. Impact Summary for buildings/GOIs – Menu for visualisation of results. .........93
Image 3-109. Impact Summary for buildings/GOIs – Impact Summary in numbers. .............94
Image 3-110. Impact Summary for buildings/GOIs – Impacted buildings. .............................94
Image 3-111. Impact Summary for buildings/GOIs – Impacted buildings - GOIs. ..................94
Image 3-112. Impact Summary for Roads – Select Area of Interest. ....................................95
Image 3-113. Impact Summary for Roads – Menu for visualisation of results. ......................95
Image 3-114. Impact Summary for Roads – Impact Summary in numbers. ..........................96
Image 3-115. Impact Summary for Roads – Impacted roads. ...............................................96
Image 3-116. Scenario Matching – Main menu.....................................................................97
Image 3-117. Scenario matching – Outputs. ....................................................................... 100
Image 3-118. SitRep – Example of simulation included into the SitRep document. ............ 100
Image 3-119. SitRep – Generate SitRep document. ........................................................... 101
Image 3-120. SitRep – Example of SitRep for a fire incident. ............................................. 103
Image 3-121. Earth Observation – Search of layers for display on the GUI. ....................... 104
Image 3-122. Earth Observation – Examples of EO layers for hazard extend for fire (A), floods (B) and landslides (C). ........................................................................................................ 105
Image 3-123. In-situ sensors – Activation of sensors for visualisation on the GUI. ............. 106
Image 3-124. In-situ sensors – Display of stations with in-situ sensor on the GUI. ............. 106
Image 3-125. In-situ sensors – Aperture of cracks measured overtime by a crackmeter sensor for a defined time period. .................................................................................................... 107
Image 3-126. In-situ sensors – Pore water pressure measured overtime by a piezometer sensor for a defined time period. ........................................................................................ 107
Image 3-127. In-situ sensors – Degree of tilt measured overtime by a tiltmeter sensor for a defined time period. ............................................................................................................ 108
Image 3-128. GB-SAR – Search of GB-SAR layers for display on the GUI. ........................ 109
Image 3-129. GB-SAR – Deformation along the line of sight measured by the GB-SAR occurred during the temporal interval 26-27 May 2018. ...................................................... 109
Image 3-130. Drones – Cloud of drone images displayed on the GUI. ............................... 110
Image 3-131. Drones – Thermal and RGB images (left and right, respectively). ................. 111
Image 3-132. Chat service on the GUI. .............................................................................. 112
Image 3-133. Chat window for a HEIMDALL user. ............................................................. 112
Image 3-134. HEIMDALL app log in screen. ....................................................................... 113
Image 3-135. HEIMDALL app – Main screen. .................................................................... 114
Image 3-136. HEIMDALL app – Chat. ................................................................................ 114
Image 3-137. HEIMDALL app – Map. ................................................................................. 115
Image 3-138. HEIMDALL app – Situation Report. .............................................................. 116
Image 3-139. HEIMDALL app – Share Picture or Location. ................................................ 116
Image 3-140. HEIMDALL app – Send Picture. ................................................................... 117
HEIMDALL [740689] D7.3
09/11/2020 ix
Image 3-141. HEIMDALL app – Check location send form the app in the HEIMDALL platform. ........................................................................................................................................... 117
Image 3-142. HEIMDALL app – Send Location. ................................................................. 118
Image 3-143. HEIMDALL app – Check location send form the app in the HEIMDALL platform. ........................................................................................................................................... 118
Image 3-144. HEIMDALL app – Logout or Download Offline Map. ..................................... 119
Image 3-145. HEIMDALL app –Download map for offline use. ........................................... 119
Image 3-146. HEIMDALL app – Create waypoints. ............................................................ 120
Image 3-147. HEIMDALL app – Received waypoint. .......................................................... 120
Image 3-148. HEIMDALL app – Reply window for received waypoints. .............................. 121
Image 3-149. HEIMDALL app – Replied waypoint. ............................................................. 121
Image 3-150. Catalogue publication. .................................................................................. 122
Image 3-151. Catalogue – Publication menu. ..................................................................... 123
Image 3-152. Catalogue – Subscription menu. ................................................................... 124
Image 3-153. Catalogue – LU information. ......................................................................... 124
Image 3-154. Catalogue – Subscription to scenario products. ............................................ 124
Image 3-155. Catalogue – Check your own publications. ................................................... 125
Image 3-156. Catalogue – Subscribed products. ................................................................ 125
Image 3-157. Catalogue – Subscription to EO products. .................................................... 126
HEIMDALL [740689] D7.3
09/11/2020 x
List of Tables
Table 3-1. Rockfall simulator – Volume values to define the size of the rockfall as stated in the EIRG guide. ..........................................................................................................................65
Table 3-2. Rockfall simulator – Precision values to define the size of the rockfall. ................65
Table 3-3. Rockfalls susceptibility classes. ...........................................................................66
Table 3-4. Debris flow simulator – Mass, volume and area values to define the size of the debris flow as stated in the EIRG guide. ...............................................................................69
Table 3-5. Debris simulator – Precision values to define the size of the debris flow. .............69
Table 3-6. Debris flow simulator – Material types. ................................................................69
Table 3-7. Debris flows susceptibility classes. ......................................................................70
Table 3-8. Rotational landslide simulator – Soil humidity categories. ....................................72
Table 3-9. Rotational landslide simulator – Soil type categories. ..........................................72
Table 3-10. Rotational landslide simulator – Landslide type (size). .......................................73
Table 3-11. Rotational landslide susceptibility classes. .........................................................74
Table 3-12. Landslide rainfall analysis – Threshold Climatic area. .......................................76
HEIMDALL [740689] D7.3
09/11/2020 xi
List of Acronyms
AB Advisory Board
AVA Avanti Communications LTD
CA Consortium Agreement
CCC Common Challenge Capabilities
CFRS Catalan Fire and Rescue Service
CIMA Centro Internazionale in Monitoraggio Ambientale – Fondazione CIMA (CIMA Foundation)
COP Common Operation Picture
CRI Associazione della Croce Rossa Italiana (Italian Red Cross)
CTTC Centre Tecnològic de Telecomunicacions de Catalunya (Catalan Tecnological Telecommunications Centre)
DLR Deutsches Zentrum für Luft- und Raumfahrt e.V. (German Aerospace Center)
DRM Disaster Risk Management
EC European Commission
EKUT Eberhardt Karls Universität Tübingen
EUW End-User Workshop
FBBR Frederiksborg Brand og Redning (Frederiskborg Fire and Rescue Service)
GA Grant Agreement
GB-SAR Ground Based Synthetic Aperture Radar
GOI Geographical Object of Interest
GUI Graphical User Interface
ICGC Institut Cartogràfic I Geològic de Catalunya (Catalan Institute of Cartography and Geology)
ISAS Impact Summary Service
INT Departament d’Interior – Ministry of Home Affairs (Government of Catalonia)
IPR Intellectual Property Right
LU Local Unit
MoM Minutes of Meeting
HEIMDALL [740689] D7.3
09/11/2020 xii
PB Project Board
PC Project Coordinator
PCF Fundació d’Ecologia del Foc i Gestió d’Incendis Pau Costa Alcubierre (Pau Costa Foundation)
QMR Quarterly Management Report
SatCom Satellite Communication
SFRS Scottish Fire and Rescue Service
SKP Stage Key Points
SP Service Platform
SPH Space Hellas S.A.
TL Task Leader
TRL Technology Readiness Level
TM Technical Manager
ToC Table of Contents
TSYL Tecnosylva S.L.
UAV Unnamed Aerial Vehicle
UNISTRA Université de Strasbourg (University of Strasbourg)
URI Uniform Resource Identifier
VPN Virtual Private Network
WP Work Package
WPL Work Package Leader
HEIMDALL [740689] D7.3
09/11/2020 xiii
Intentionally blank
HEIMDALL [740689] D7.3
09/11/2020 14
Executive Summary
The HEIMDALL platform is a decision-support tool for multi-hazard emergency planning and management that has been developed in the frame of the H2020 EU HEIMDALL project the aim to improve preparedness of societies to cope with complex crisis situations. The present manual has been designed for potential users of the platform in order to facilitate their task of knowledge, use and learning. Therefore, the manual contains detailed guidance to carry out all the operations that the platform offers to the user with illustrated examples of use for each of the modules.
HEIMDALL [740689]
15
1 HEIMDALL platform
The HEIMDALL platform that is presented in this document has been developed in the frame of the H2020 EU HEIMDALL project as a tool for multi-hazard emergency planning and management with the aim to improve preparedness of societies to cope with complex crisis situations. To achieve that, the platform makes use of innovative technologies for the definition of multi-disciplinary scenarios and response plans while providing integrated assets to support emergency management, such as monitoring, modelling, situation and risk assessment, decision support and communication tools. Furthermore, the HEIMDALL platform fosters data and information sharing among the relevant operational organisations involved in crisis management, maximises the accuracy of valuable information and improves population awareness.
1.1 Objectives
The development of the HEIMDALL platform has been grounded on the following key aspects:
(i) improved data and information access and sharing among the involved stakeholders, including the population and first responders on the field;
(ii) better understanding of the situation by using advanced multi-hazard methods to develop realistic multi-disciplinary scenarios, risk and vulnerability assessment, information sharing and emergency response;
(iii) recognising the value of information by advanced data fusion, situation assessment and decision support tools.
The combination of these aspects has thus been integrated in a modular and highly flexible platform which makes use of a federated architecture to provide user-tailored interfaces and foster information sharing among the involved stakeholders. Additionally, the platform will provide citizens at risk and first responders on the field with valuable incident-related information, increasing population awareness.
1.2 The HEIMDALL approach
The challenging HEIMDALL objectives are achieved by following a detailed system engineering process, based on an iterative version of the well-established Vee model for system engineering (Figure 1-1) and a close cooperation with the relevant stakeholders (first responders), both the consortium partners and the members of the Advisory Board.
Figure 1-1. Vee model of system engineering.
HEIMDALL [740689]
16
The diagram in Figure 1-2 depicts the interaction between the system engineering and the stakeholder management layers. The HEIMDALL system engineering process has defined a series of milestones for the system development; namely, the initial system specification, three intermediate releases and the final release. These milestones are aligned with interactions with the relevant stakeholders (partners with first responder profiles and Advisory Board members), by means of the planned Advisory Board (AB) and End-Users Workshops. Therefore, the outcome of the different workshops is used to perform preliminary system demonstrations to evaluate the preliminary releases and gather end user feedback until the final operational demonstration.
Figure 1-2. The HEIMDALL approach.
1.3 Operational use
By the end of the scope of the project, the HEIMDALL platform has achieved a maturity of TRL7, i.e. a system prototype that has been demonstrated in an operational environment. This has been achieved through a collaborative design approach between research, industry and non-profit institutions and the large end-user involvement in the project who have provided their experience and lessons learned for the development of an end-user orientated decision support tool.
As a result, HEIMDALL is an integrated platform with tools, services and products that can assist end-users in evaluating the effectiveness of various pre-incident planning strategies and improves decision support and situational awareness for real-time operational purposes. Hence, by using the platform end-users can get a better understanding of the risks and constraints that operatives and at-risk communities may face in different large-scale hazard scenarios, which in turn facilitate the mitigation measures that emergency managers undertake in response.
HEIMDALL [740689]
17
2 System architecture
The final system architecture, which has been envisaged and designed based on the user requirements, is showed in Figure 2-1. This has resulted in a multi-modular platform that makes use of a federated architecture that provides user-tailored interfaces, allows to interface other external services, and fosters information sharing among the involved end-users.
Figure 2-1. Diagram of the HEIMDALL system architecture.
System inputs are displayed on the left-hand side of the diagram. Earth Observation Products, Landslide Monitors and Arial-based Data are developed by project partners, whereas other inputs like Weather Services and Other External Services consist of existing systems that are likewise plugged into the system.
The main system modules for response planning and scenario building are displayed in the centre of the diagram, whereas the modules to enable communication and data exchange among the users are placed on the right-hand side of the diagram.
The HEIMDALL system modules are briefly described below:
• Scenario management: This is the core unit of the HEIMDALL system that stores and manages all necessary information related to each of the scenarios entered. It allows for matching and generates standard compliant situation reports.
• Hazard simulation tools: This module supports three different hazard simulation tools, each tailored to concrete hazard: forest fires, floods and landslides. These tools serve to predict the hazard evolution, hence helping to anticipate those critical areas and elements that will be impacted, and the hazard evolution in a timely manner, hence helping to determine the time required for the hazard to reach critical areas and elements in the territory such as populated areas, roads or buildings.
• Risk Assessment, Impact Summary and Decision Support: these three modules allow for a more accurate assessment of the impacts and facilitates the deployment of operational procedures. They are all based on the simulation results provided by the simulation tools.
• Role management: this module is essential to enable user operability with the platform: e.g. manage access rights, user roles and profiles; enable and disable features; or create, modify and delete scenarios.
HEIMDALL [740689]
18
• Service Platform: this module is the node that interconnects all modules to one unique HEIMDALL system.
• GUI (Graphical User Interface): this module enables the overall control of the system and displays the outcomes of each of the modules.
• Information Gateway: this serves to enable communications with the users (first responders) in the field and with the general public via a HEIMDALL smartphone app. Communications are possible by means of Internet and SatCom (Satellite Communication) systems.
• Catalogue and Interface to other instances: These modules allow to connect multiple Local Units (LUs) (i.e. HEIMDALL system instances) to a network of end-users and systems building a federated architecture like presented in Figure 2-2 exemplary with two LUs.
Figure 2-2. Catalogue structure with the example of two Local Units.
HEIMDALL [740689]
19
3 System usage
The practical purpose of the present users’ manual is to facilitate the task of knowledge, use and learning of the developed HEIMDALL platform. To achieve that, this section contains information about all the basic operations that the platform offers to the user. This includes examples of use for each of the modules, while following the logical paths that the user would carry out and is accompanied by useful screenshots to follow the explanation.
3.1 Log in – HEIMDALL web portal
Access to the HEIMDALL server is possible only via an OpenVPN connection supported by the company SPH.
Once connected to the VPN network, the user can log into the HEIMDALL web portal via a web browser (e.g. Firefox, Chrome, etc.) by an URL as described below (Image 3-1).
Image 3-1. HEIMDALL user log in screen.
Multiple instances are provided for the HEIMDALL end-users such that each organisation has access to their own platform with various roles (e.g. Incident Commander, hazard analyst, local police, Red Cross…). They can simultaneously utilise the platform to make use of its modules and to interact with other users. The URLs for each organisation are the following:
• Catalan Fire and Rescue Service (INT-FRS): http://gui.it.heimdall.sp
• Catalan Police Department (INT-PD): http://gui.heimdall.sp
• Scotish Fire and Rescue Service (SFRS): http://gui.a.heimdall.sp
• Italian Red Cross (CRI): http://gui.b.heimdall.sp
• Frederiksborg Fire and Rescue Service (FBBR): http://gui.c.heimdall.sp
3.2 Graphical User Interfaces (GUI)
This involves the main features shown on the main screen of the HEIMDALL platform and other features that are accessed by right-clicking on the mouse across the main screen.
HEIMDALL [740689]
20
Main screen features
Image 3-2 shows the main features that appear on the main screen of the HEIMDALL platform.
Image 3-2. Main screen of the HEIMDALL platform.
The contents of the main screen numbered in Image 3-2 are indicated below:
1. Main map: cartographic display showing multiple layers of information. Use left click to move the map, mouse wheel for zooming, press and hold middle click mouse key for rotating and changing perspective.
2. Local Unit: organisation name of the user who is logged into the platform.
3. Mode: HEIMDALL can be set to three scenario modes relevant to different emergency phases: training, preparedness and response. Though the platform offers the same functionalities irrespective of the selected mode, this array of functionalities has been designed to support end-user’s decision-making through each of the emergency phases:
a. Training: develop existing skills and acquire new competences that will enable end-users to assume significant responsibility when confronted with the need to manage crisis and emergency situations.
b. Preparedness: support improved hazard forecasting and prevention that lead to a safe, efficient, and cost-effective management through appropriate planning and coordination.
c. Response: support the execution of emergency operations plans as well as mitigation activities designed to limit the loss of life, personal injury, property damage, and other unfavourable outcomes.
4. Active Incident Scenario: scenario on which the user is working at that moment.
5. Create a new scenario: create an empty scenario from scratch.
6. List of scenarios: access to the repository of scenarios stored in the platform. The user can here select, visualise and edit any of the existing scenarios (Image 3-3).
HEIMDALL [740689]
21
Image 3-3. Existing scenarios.
The scenario that is active appears with the icon , whereas the user can switch
to another scenario by clicking on .
7. Scenario matching: match the active scenario with scenarios from the database. Scenario matching functionality is described in section 3.6 Scenario Matching.
8. Catalogue: manage publications and subscriptions in the platform catalogue. The Catalogue is described in section 3.9.3 Catalogue.
9. List of waypoints: check the waypoints entered in the platform. Waypoints are further described in 3.2.2.2 Add Marker (Waypoints).
10. Settings: change the “Active Incident Scenario” and/or the mode in which the scenario is set (see Image 3-4). In the example showed in Image 3-4, the “Active Incident Scenario” can be changed by typing the scenario ID number in the “Value” column next to the Name instance “activeScenarioId”. The number “249” corresponds to a scenario ID number that would activate that scenario. On the other hand, the mode of the scenario can be changed by typing which mode we want to set in the “Value” column next to the Name instance “mode”. The mode can be set to preparedness, response or
training. Once this is done the user need to click on for the changes to be applied.
Image 3-4. User settings.
HEIMDALL [740689]
22
11. Notifications: every time that a module is triggered and its results are ready for display (e.g. simulations, impact assessment, alerts, reception of drone images…) the bell appears with a number indicating that there is a notification message. By clicking on the bell, the user can access to the last notification message (see Image 3-5).
Image 3-5. Notification message.
12. User information: details about the logged-in user.
13. Log-out: logout from the current session.
14. Assets: access to the chat functionality (see 3.9.1 Chat), for communication with other platform users, and to drones images, for visualisation of images taken by UAVs (see 3.8.3 Aerial-based data: Drones) (Image 3-6).
Image 3-6. Assets on the HEIMDALL platform.
15. Go to scenario area: zoom in to show a detailed view of the scenario area.
16. Map Controls: customise the information displayed on the map (Image 3-7).
HEIMDALL [740689]
23
Image 3-7. Map Control options on the HEIMDALL platform.
Display options can be turned on/off by clicking on the selection button . Display colour can be customised by clicking on the layer colour box which opens a colour palette. The main map can be viewed in basic, satellite or topographic mode.
17. Layers: dropdown list of map layers that can be displayed over the main map (Image 3-8). Map layers include, among others, EO imagery data, topographic maps, remote sensing and geospatial data layers and 3D-models of infrastructure. Selecting/De-
selecting the selection button allows displaying/hiding the layers. Opacity level can be adjusted by moving the slider for some layers. The order of the layers on the main map can be adjusted by dragging and dropping the active layers. The highest layer in the active layer section is also the top level on the map.
Image 3-8. Map layer option on the HEIMDALL platform.
18. Locator Map: study area in the context of a larger area.
19. Scale: graphical scale on the map.
20. LineString tool: draw a line on the map.
21. Polygon tool: draw a polygon shape on the map.
22. Marker tool: place a point at exact location on the map.
23. Delete tool: delete any of the three above element types created.
HEIMDALL [740689]
24
Other features
Furthermore, by right-clicking on the mouse the user can access to the following additional features (Image 3-9):
Image 3-9. Other features on the HEIMDALL platform GUI
Each of the above features are explained in the following sub-sections.
3.2.2.1 Coordinates and map bounds
The user can right click the mouse and selects to copy the coordinates in “longitude, latitude” format. Likewise, the user can right click the mouse to check the coordinates of that specific location on the map as well as the SW and NE bounds of the area displayed on the map (see Image 3-10).
Image 3-10. Coordinates and map bounds.
3.2.2.2 Add Marker (Waypoints)
Markers can be used as waypoints in order to send notifications or warnings associated with specific locations to other users of the platform: e.g. observed hazard impacts, blocked roads, location of specific resources or units, locations where assistance is needed...
The user can place markers as waypoints at any location on the map. To do so, the user first needs to right click the mouse and select “Add marker” (Image 3-11).
HEIMDALL [740689]
25
Image 3-11. Add marker on the GUI.
The windows displayed Image 3-12 appears, with the option to send the specific location as a waypoint.
Image 3-12. Add marker – Send marker as Waypoints.
Then, another window appears (Image 3-13) where the user can create a waypoint by clicking
on . This, in turn, prompts a box to specify the asset (i.e. specific user platform) to whom the waypoint is addressed as well as a description.
Image 3-13. Add marker – Create waypoint.
HEIMDALL [740689]
26
Every time a new Waypoint is created it is added to the list shown at the bottom part of Image
3-13. Finally, the Waypoint can be added to the map by clicking . The box should then
turn green with a tick sign on the left: .
By clicking in the upper part of the main screen (Image 3-2) the user gets access to the list of waypoints created in that scenario (see Image 3-14). For each waypoint that has been created the user can check the messages included in the waypoint (info), the user who has sent the waypoint (owner), and the user to whom that waypoint has been sent (users).
Image 3-14. Add marker – List of waypoints associated with an active scenario.
The creation/reception of waypoints can be also done through the HEIMDALL mobile phone app as described in section 3.9.2.8 HEIMDALL app waypoints.
3.2.2.3 Weather forecast
The weather forecast can be checked and displayed at any time by the user in the platform Graphical User Interface. This can be done in two ways (Image 3-15):
Image 3-15. Weather forecast – Get weather and get weather grid buttons on the GUI.
• Right click and then left click on “Get weather” to obtain weather data for that specific point (Image 3-16):
HEIMDALL [740689]
27
Image 3-16. Weather forecast – Get weather.
• Right click and then left click on “Get weather grid” to obtain weather data for a larger area. The scope of the weather grid is proportional to the zoom level (Image 3-17):
Image 3-17. Weather forecast – Get weather grid.
Both in “Get weather” and “Get weather grid” options, the weather forecast can be displayed
by clicking on the weather icon (e.g. , ) for various hourly time intervals before (e.g. T-12) or after (e.g. T+12) the current time, namely (Image 3-18):
• T-12, T+12
• T+1, T+3, T+6
• T+3, T+6, T+9
• T+4, T+8, T+12
Additionally, the user can display the current time weather values (T+0) by clicking on
(see Image 3-18).
HEIMDALL [740689]
28
Image 3-18. Weather forecast – Weather forecast on the GUI for various hourly time intervals.
3.2.2.4 Screenshots
The user can take screenshots of the GUI map at any time by right clicking on the mouse and then selecting “Save screenshot to file” or “Save screenshot to active scenario” (Image 3-19). In the former, the screenshot is saved to a file on the user’s ladptop/computer, whereas in the latter the screenshot is saved internally in the platform and the user can view it in the tab “Images” from the ““Active Incident Scenario”” menu.
Image 3-19. Screenshots – Save screenshots.
3.3 Scenario management
Scenario management is the most basic module of the HEIMDALL platform that enables the basic features and functionalities for scenario building. The module allows for the creation of a knowledge database consisting of user generated information of past and current incidents. This information comprises an extensive collection of relevant information such as the prevailing weather conditions, the spatiotemporal evolution of the hazard across the territory, emergency and response planning taken by the various emergency organisation to mitigate the hazard impacts, or the comparison between current and historical scenarios, among others.
Scenario creation/edition
By clicking on in the upper part main screen (Image 3-2) the user can create a new scenario from scratch. The following window pops up (Image 3-20).
HEIMDALL [740689]
29
The characteristics of the scenario can be entered at two scale levels: landscape (i.e. larger area that is defined by a given synoptic situation) and incident (i.e. area impacted by the hazard).
Image 3-20. Creation of a new scenario at landscape and incident level.
Moreover, past scenarios in the stored in repository can be consulted and edited by clicking
on the List of scenarios button in the upper part main screen (Image 3-2).
Each particular scenario presents the following structure that is displayed in Image 3-21. Each of the modules therein are described in the following sub-sections.
HEIMDALL [740689]
30
Image 3-21. Scenario structure.
3.3.1.1 Landscape scenario
Firstly, the user may want to enter the synoptic situation that could be conducive to a potential
incident. By clicking on in the Landscape scenario menu (see Image 3-20) the user can set the characteristics of the landscape scenario (Image 3-22).
Image 3-22. Landscape scenario settings.
HEIMDALL [740689]
31
The contents of the landscape scenario in Image 3-22 are indicated below:
1. Name of the Landscape scenario: unique identification name for that scenario.
2. Set scenario area: draw a polygon indicating the geographical area with homogeneous synoptic situation. To adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest (Image 3-23). Double-click for ending the drawing.
Image 3-23. Landscape scenario – Set Landscape Scenario Area.
3. Pick synoptic situation: synoptic situation refers to the general state of the atmosphere in terms of pressure pattern, fronts, wind direction and speed and how they will change and evolve overtime. Select the concrete synoptic situation from a pre-defined list of situations. The following situations are included [1]:
1. Atmospheric instability
2. Storm winds
3. Valleys and mountain slopes topographic winds
4. Winds from sea to land and from land to sea due to day-night changes
5. Hot wave and low relative humidity
6. Dry and hot wind moderate or/and strong
7. Strong wind
4. Explanation: free text box to provide additional explanation about the synoptic situation.
HEIMDALL [740689]
32
5. Synoptic situation assessment: free text box to provide additional assessment on the synoptic situation.
3.3.1.2 Incident scenario
Once the incident starts, the user may want to enter the characteristics of the ongoing incident. This information will be associated with the landscape scenario that was previously created.
Image 3-24. Incident scenario parameters.
The contents of the incident scenario in Image 3-24 are indicated below:
1. Name of the incident: unique identification name for that scenario.
2. Snapshot: information available for a scenario at a specific point in time. A new
snapshot can be created by clicking on within the “Active Incident
Scenario” menu. Then, click on to check and manage all the snapshots created within that scenario (see Image 3-25).
HEIMDALL [740689]
33
Image 3-25. Incident scenario – List of snapshots created in each scenario.
Only one representative snapshot can be selected at a time. The representative snapshot reflects the most significant character and behaviour of the scenario. It is used for scenario matching (see 3.6 Scenario Matching) and situation report generation (see 3.7 Situation Report (SitRep)). Moreover, the user can mark specific snapshots as “selected” (i.e. reflecting relevant changes).
The “Base” flag cannot be changed by the user. The base snapshot is the scenario that the user is working on. Continuous changes are stored in the base snapshot. When the user creates a new snapshot, a copy of the base snapshot is made.
3. Incident location: place a point at an exact location on the map where the incident occurs. To get to the Area of Interest on the map, drag the marker on the map or search by latitude and longitude coordinates (Image 3-26). Searching will not modify the zoom level, so it is recommended to zoom in before searching. The incident location will be used for certain services, e.g. to request automatically weather conditions at the scenario.
Image 3-26. Incident Scenario – Set Incident Location.
HEIMDALL [740689]
34
4. Scenario area: draw a polygon delimiting the geographic area that is being affected by the hazard. Again, to adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest.
Image 3-27. Incident Scenario – Set Scenario Area.
5. Incident place name: provide a specific name for the place where the hazard occurs.
6. Set incident times: different times can be set; namely, the time at which the user creates the scenario, the incident start and end time, and the current time. Times can be entered manually, but if the user wants to enter the current time, this can be
automatically loaded by clicking on . Only the creation time is mandatory and needs to be set when creating the scenario.
7. Hazard type: select the hazard type and sub-type among a series of pre-defined categories:
• Landslide
• Landslide: Debris fall
• Landslide: Rockfall
• Flood
• Flood: Estuarine/coastal
• Flood: Storm surge
• Flood: Flash flooding
• Flood: Fluvial flooding
• Forest fire
• Forest fire: Storm-dominated fire
HEIMDALL [740689]
35
• Forest fire: Convection-dominated fire producing pyrocumulus clouds
• Forest fire: Convection-dominated fire with wind
• Forest fire: Standard convection-dominated fire
• Forest fire: Wind-driven with subsidence
• Forest fire: Wind-driven fire in mountainous terrain
• Forest fire: Topographic fire in main valleys and canyons
• Forest fire: Coastal topographic fire
• Forest fire: Standard topographic fire
8. Risk level: select the current risk level among a series of pre-defined categories:
• Unknown
• Very high
• High
• Medium
• Low
• Very low
9. Causalities: specify number of people death since the start of the incident. Default is unknown. In order to set it to unknown on purpose, type in -1 into the field.
10. Injured: specify number of people injured since the start of the incident. Default is unknown. In order to set it to unknown on purpose, type in -1 into the field.
11. Status: the status of the emergency can be set to:
• Unknown: the hazard situation is unknown.
• Training: historical or fictional scenarios are used for training exercises.
• Actual: the hazard situation is real.
12. Urgency: the level of urgency can be set to:
• Expected: the incident can occur within the next few hours.
• Fictional: unreal scenarios with made-up hazard situations.
• Historic: historical incident that affected the territory.
• Future: pre-hazard conditions suggest a great chance that an incident can occur in the foreseeable future.
• Immediate: the incident can occur immediately.
13. Challenge: the scenario is associated to one of the following challenges based on the “Common Challenge Capabilities Matrix” from H2020 FIRE-IN Project [3]:
• High rate of effort in hostile environments
• Low frequency, high impact
• Multi-agency / multi leadership environment
• High level of uncertainty
14. Sensor Thresholds: the system alerts the user if a sensor exceeds this threshold. This field is not for the moment operative in the platform.
HEIMDALL [740689]
36
15. Source: source from which information has been obtained.
16. Cross-Border Incident: if the incident affects two or more countries/regions/jurisdictions, the user can set it to “Cross-Border incident” by ticking in the box.
Weather Conditions
Weather conditions can be accessed from the “Active Incident Scenario” main menu (Image 3-28).
Image 3-28. Weather conditions.
The user can add conditions that include the current weather situation and the forecast (Image 3-29).
HEIMDALL [740689]
37
Image 3-29. Weather conditions – Weather parameters.
The whole set of weather conditions, including the date and time can either be set manually by the user or loaded automatically (only when they are current weather conditions) from an
external weather service by clicking on . Thus, weather conditions are retrieved from the nearest weather station to the “Incident location” (see 3.3.1.2 Incident scenario).
Weather conditions can be current or forecasted. If forecasted, the user can set a number in
the text box different from 0. Conditions with forecast hours 0 and 1 will be used for the automatically created Situation Report (see 3.7 Situation Report (SitRep)).
Finally, the user can tick in the box in case that weather conditions provided by the external weather service have been verified in the field or by other means.
Observed Hazard Behaviour The information provided by the various services, products and tools integrated into the HEIMDALL platform provide valuable information for the end-users to make better informed decisions about the management of the incident. However, for these decisions to be grounded on a more complete risk assessment, the end-users may need to combine this information with data sources that are external to HEIMDALL and with observations that are made from the field. Along these lines, the HEIMDALL platform has a section called “Observed hazard behaviour” where the users can enter additional hazard information that is not directly provided by any of the platform services. Currently, this has only been designed for wildfire-specific incidents.
Observed hazard behaviour can be accessed from the “Active Incident Scenario” main menu (Image 3-30).
HEIMDALL [740689]
38
Image 3-30. Observed Hazard Behaviour.
Image 3-31 shows the various fire behaviour parameters that can be entered in the “Observed Hazard Behaviour”
Image 3-31. Observed Hazard Behaviour – Fire behaviour parameters.
HEIMDALL [740689]
39
1. Registration number: unique identification number associated with a fire type [1]. This number should help characterise fire patterns, and so potential fire spread and impacts, regardless of the region of the world where the fire occurs.
2. Fire Propagation Type: main fire spread pattern across the landscape. This can be set to one of the following options:
• Crown active
• Crown passive
• Sustained torching
• High intensity surface
• Medium intensity surface
• Low intensity surface
• No description
MEAN/AVERAGE FLAME LENGTH: flame length in the advancing fire front measured along the slant of the flame from the midpoint of its base to its tip. The flame length is expressed in m.
3. Sustained in the head: mean of the flame length at the head of the fire.
4. Sustained in the flank: mean of the flame length at the flanks of the fire.
5. Maximum length: maximum flame length observed across the fire perimeter.
PROPAGATION VELOCITY: measurement of the speed at which a fire front moves across a landscape. The propagation velocity is expressed in km/h.
6. Mean/Average: mean of the fire propagation speed.
7. Maximum (run distance): maximum speed observed in the fire propagation.
DISTANCE OBSERVED SECONDARY FOCUS: distance reached by sparks and embers that are transported through the air by the wind or convection column. The distance observed secondary focus is expressed in m.
8. Massive: distance reached by massive rain of sparks and embers landing ahead of the fire front.
9. Punctual maximum: distance reached by the spark or ember that is transported at the maximum distance from the fire front.
10. Fire type: singular and repeated spreading patterns and weather (synoptic conditions). Select the fire type among a series of pre-defined categories [1]:
• Storm-dominated fire
• Convection-dominated fire producing pyrocumulus clouds
• Convection-dominated fire with wind
• Standard convection-dominated fire
• Wind-driven with subsidence
• Wind-driven fire in mountainous terrain
• Topographic fire in main valleys and canyons
• Coastal topographic fire
HEIMDALL [740689]
40
• Standard topographic fire
11. Observations: free text box to provide additional information about the observed hazard behaviour.
Response Plans
Users from different organisation involved in the management of the incident can all work on a common response plan to cooperatively face the emergency where they can likewise plan for actions that are specific to their organisations.
Response Plans can be accessed from the “Active Incident Scenario” main menu (Image 3-32).
Image 3-32. Response Plans.
Response plans can be entered in the platform as displayed in Image 3-33.
HEIMDALL [740689]
41
Image 3-33. Response Plans – Settings.
1. Hazard type: select hazard type and sub-type among a series of pre-defined categories:
HEIMDALL [740689]
42
• Landslide
• Landslide: Debris fall
• Landslide: Rockfall
• Flood
• Flood: Estuarine/coastal
• Flood: Storm surge
• Flood: Flash flooding
• Flood: Fluvial flooding
• Forest fire
• Forest fire: Storm-dominated fire
• Forest fire: Convection-dominated fire producing pyrocumulus clouds
• Forest fire: Convection-dominated fire with wind
• Forest fire: Standard convection-dominated fire
• Forest fire: Wind-driven with subsidence
• Forest fire: Wind-driven fire in mountainous terrain
• Forest fire: Topographic fire in main valleys and canyons
• Forest fire: Coastal topographic fire
• Forest fire: Standard topographic fire
2. Response Plan Description: free text box to provide descriptions about the common response plan shared with other organisations.
3. Situation assessment: include in the response plan a situation assessment with data/information generated in our modules; namely, weather conditions (see 3.3.2 Weather Conditions), screenshot of the simulation (see 3.4 Hazard simulation tools), Impact Summary (see 3.5.2.2 Impact Roads) and other screenshots of the platform interface.
Image 3-34. Response Plans - Situation assessment.
4. Incident Start and End Time: time at which the incident starts and ends in “hh:mm:ss”.
5. Strategy: set the four specific strategies below with the following aims:
• Management: this can vary based on the hazard type:
o Fires: to stabilise the fire perimeter using technical fire or to let the fire burn until it reaches fire break for safety and for landscape management purposes.
HEIMDALL [740689]
43
o Floods: to redirect the flow to a specific area to lessen the damage.
o Landslides: to allow or force the instable area to fall under controlled conditions to avoid bigger damages.
• Confinement: this can vary based on the hazard type:
o Fires: to restrict the fire within determined boundaries.
o Floods: to restrict the flooded area by using physical (e.g. sand bags, etc.).
o Landslides: to stabilise the landslide using engineering measures.
• Offensive: this can vary based on the hazard type:
o Fires: to reduce the surface of the fire with specific operations
o Floods: to reduce the area that is affected by removing water (e.g. pumps, digging drainage ditches, etc.), and prevent more water from entering using physical barriers (e.g. dam, etc.)
o Landslides: to rescue buried victims.
• Defensive: to protect vulnerable elements (for all hazard types).
Additionally, the user can describe further details about the common strategy in the free text box.
6. Common objectives: set the common objective type and the specific objectives associated with the objective type. The following options are available:
• Objective type 1: Hazard
o Specific objectives (tailored to each hazard):
▪ Fire: Extinguish
▪ Fire: Confine
▪ Fire: Manage
▪ Flood: Remove water (use mechanic means)
▪ Flood: Contain
▪ Flood: alter the course
▪ Flood: Regulate the flow (e.g. closing the floodgates of a dam)
▪ Flood: Unblock (remove obstacles to ease the flow)
▪ Landslide: Stabilise
▪ Landslide: Uncover
▪ Landslide: Contain
▪ Landslide: Mobilise
• Objective type 2: Damage over people, goods, properties
o Specific objectives (common to all hazards):
▪ Rescue
▪ Protect
▪ Evacuate (people)
▪ Confine (people)
HEIMDALL [740689]
44
7. Objective description: free text to provide further description of the objective.
8. Organisational complexity: this can be set to four different levels depending on the geographical area affected by the hazard:
• Local
• Regional
• National
• International
9. Incidental Challenge Level: the incident can be associated to one of the following challenges based on the “Common Challenge Capabilities Matrix” from H2020 FIRE-IN Project [3]:
• High rate of effort in hostile environments
• Low frequency, high impact
• Multi-agency / multi leadership environment
• High level of uncertainty
10. Agencies: number of agencies/organisations involved in the management of the incident.
11. Agency specific actions: free text box where each agency/organisation can enter their own actions to undertake in the frame of the common response plan.
12. Measures: indicate specific measures to be taken to mitigate the hazard impacts.
By clicking on the window in Image 3-35 pops up:
Image 3-35. Response Plans – Measures.
The user needs to indicate location, data and time, select one of the three pre-defined measure types (water tubes, sandbags, fire breaks), and add additional decisions. In
turn, by clicking on the user accesses to the window showed in Image 3-36:
Image 3-36. Response Plans – Measures – New decision.
HEIMDALL [740689]
45
Here the user sets the location, data and time, a description of the decision, and has the option to indicate the level of Command at which that decision is taken. The level of command can be:
• Unit, Team or Force (Leader)
• Group (Supervisor)
• Division (Supervisor)
• Branch (Director)
• Section (Chief)
• Command Staff Member (Officer)
• Incident Commander
13. File upload: upload any document related to Response Plan, if required.
Decisions
Decisions taken by incident managers can be documented and shared in HEIMDALL. Decisions can be associated with a Response Plan as seen in section 3.3.4 Response Plans (see Image 3-36), but they can likewise be entereded through the decision module (see Image 3-37).
Image 3-37. Decisions.
The resulting decisions will be then listed in the decision module as displayed in Image 3-38
Image 3-38. Decisions – List of decision entered to the platform.
HEIMDALL [740689]
46
Lessons Learnt
Lessons learnt from incident disasters can be documented and stored on the platform hence being available for consultation by other users. This way users can share their experience and provide their insights gained during the conduct of management activities that can result in very valuable information for the management of future incidents.
The lessons learnt module can be accessed from the “Active Incident Scenario” main menu (Image 3-39).
Image 3-39. Lessons learnt.
Lessons learned are entered in the platform as displayed in Image 3-40.
Image 3-40. Lessons learned.
1. File upload: upload documents with relevant information about the management of the incident.
HEIMDALL [740689]
47
2. Date and time: set date and time for the added lessons learnt.
3. Level of command: associate the lesson learned with one of the following pre-defined levels of command:
• Unit, Team or Force (Leader)
• Group (Supervisor)
• Division (Supervisor)
• Branch (Director)
• Section (Chief)
• Command Staff Member (Officer)
• Incident Commander
The user has the option to use an alias for each of the level of command from abeve in order to name it with a terminology that is more common is their organisations or that they are more familiar with.
4. Lesson: free text box for lesson description.
5. Capability: associate the lesson learned to one of the following capabilities based on the “Common Challenge Capabilities Matrix” from H2020 FIRE-IN Project [3]:
• Technology
• Community involvement
• Information management
• Knowledge cycle
• Standardisation
• Pre-planning
• Incident Command Organisation
6. Evaluation: select one of the two options:
• Positive, if the lessons learnt report a positive outcome.
• Negative, if the lessons learnt report a negative outcome.
Images
The user can upload images/photos/maps to the platform that can be relevant for the management of the emergency. These images will be stored in the platform. Furthermore, the user can also send images from the HEIMDALL app that will also be stored in the platform. All these images are thus shared with other users operating the platform.
Images can be uploaded and consulted from the “Active Incident Scenario” main menu (Image 3-41).
HEIMDALL [740689]
48
Image 3-41. Images.
To upload an image to the platform the user needs to specify the image type (i.e. simulation image, Geo Tagged Image or screenshot) and can optionally specify the latitude and longitude coordinates and (Image 3-42). The procedure to send images from the HEIMDALL app is described in section 3.9.2 HEIMDALL application.
Image 3-42. Images – Settings.
Documents
Emergency authorities may need to consult documents that contain relevant information for the management of the emergency, such as demographic data, evacuation plans, emergency action plans or intervention protocols or inventory of critical elements to protect.
The user can upload and consult this type of documents from the “Active Incident Scenario” main menu (Image 3-43).
HEIMDALL [740689]
49
Image 3-43. Documents.
When uploading a document in the platform, a description needs to be specified for other users to identify the type of document attached (Image 3-44).
Image 3-44. Documents – Settings.
Common Challenge Capabilities (CCC)
The incident scenario can be associated to one of the following challenges and capabilities based on the “Common Challenge Capabilities Matrix” from H2020 FIRE-IN Project [3] (Figure 3-1).
HEIMDALL [740689]
50
Figure 3-1. Common Challenge Capabilities (CCC) matrix from the FIRE-IN project.
Common Capability Challenges can be accessed from the “Active Incident Scenario” main menu (Image 3-45).
HEIMDALL [740689]
51
Image 3-45. Common Capability Challenges.
The user selects the “challenge” associated with the incident when setting the incident scenario parameters within the “Active Incident Scenario” main menu (see 3.3.1.2 Incident scenario). Then, the user selects the “capability” when creating the Lessons Learnt (see 3.3.6 Lessons Learnt). Provided these two parameters have been set, the user can access to the tab “Common Capability Challenges” within the “Active Incident Scenario” main menu to see what lessons learnt are available associated with the current scenario challenge and what the capabilities are documented (see Image 3-46).
Image 3-46. Common Capability Challenges – Lessons learnt available associated with challenges and capabilities of the scenario.
Alerts
The alert tool allows the user to send customised alerts to other organisations participating in the emergency and to the population. The user can create and alert from the “Active Incident Scenario” main menu (Image 3-47).
HEIMDALL [740689]
52
Image 3-47. Alerts.
By clicking on the plus button , the user can select between creating a “New Alert” or creating a “New Situation Report”. If “New Alerts” is selected, the alert can be sent as a warning notification, where the user can include the details of the incident. If “New Situation Report” is created, the user can generate a document that synthetizes the current status of the situation and send it as an alert. Alerts are notified in real time on the platform and on the smartphone app.
The procedures to create a “New Alert” or creating a “New Situation Report” on the platform are described below:
New Alert
The main screen when creating a “New Alert” is displayed in Image 3-48. Mandatory fields are marked with an asterisk symbol (*).
HEIMDALL [740689]
53
Image 3-48. Alerts – New Alert.
1. Incident: incident associated with the alert. Automatically the active scenario
2. Alert area: pick the area where the alert is issued (Image 3-49). A pop-up window with a map is shown and allows to select the area as polygon, cycle or as predefined area according to the NUTS regions.
Image 3-49. Alerts – Alert area.
3. Audience: the alert can be set to private, meaning that it is only addressed to specific users (e.g. members of the same organisation, message from firefighters that is solely intended for the police), or to public, meaning that it is addressed to all the users,
including citizens might make use of the smartphone app. Click on to manually add the platform users that will receive the alert (Image 3-50).
Image 3-50. Alerts – Audience.
4. Hazard: define the hazard type, the certainty and the severity (Image 3-51).
Image 3-51. Alerts – Hazard.
Each of the three above items include the following categories:
• Hazard: forest fire, flood, landslide.
• Certainty: observed, likely, possible, unlikely, unknown. There is also a free text option for the user to add specific comments.
• Severity: extreme, severe, moderate, minor, unknown. Again, there is a free text option for the user to add specific comments.
5. Timing: set the onset and expiration time for the alert (Image 3-52). Note that while the onset time is mandatory, the expiration time is optional, i.e. do not need to be set unless the user is sure about when the alert issue must finish.
HEIMDALL [740689]
54
Image 3-52. Alerts – Timing.
6. Action: define the action and the urgency to undertake that action (Image 3-53).
Image 3-53. Alerts – Action.
The user can select among several pre-defined response types, namely:
• Shelter
• Evacuate
• Prepare
• Execute
• Monitor
• None
There is also a free text option for the user to add specific response type.
In turn, the urgency associated with one of the above response types can be set to:
• Immediate
• Expected
• Future
• Past
• Unknown
• None
Again, there is a free text option for the user to add specific urgency.
Finally, there is a free text box for the user to add additional instructions if necessary.
7. Translations: translate the alert message issued by some organisations (Image 3-54). To overcome language barriers, the user can optionally translate alert message and contents with the purpose to facilitate inter-agency cooperation in case of cross-border incidents, or to reach tourist/foreign population who do not understand the local language.
HEIMDALL [740689]
55
Image 3-54. Alerts – Translations.
The user will need to set the language translation (e.g. English to Spanish), the headline (i.e. name) of the alert and the content.
8. Resources: upload a file or type in an URL address with information about the resources available to respond to the emergency (Image 3-55).
Image 3-55. Alerts – Resources.
9. Sender: indicate the name of the organisation that sends the alert and, if required, the link to their website (Image 3-56).
Image 3-56. Alerts – Sender.
10. Check and dispatch: once the above fields have been entered the alert can be
dispatched by clinking on (Image 3-57).
Image 3-57. Alerts – Check and dispatch.
New Situation Report
When the user creates an alert as a “New Situation Report” the following window pops up:
HEIMDALL [740689]
56
Image 3-58. Alerts – New Situation Report.
1. Sender ID: organisation sending the Alert – New Situation Report.
2. Expires: set the date up to which the document can be considered as valid.
3. Distribution Status: this can be set to the following categories [2]:
• Actual: "Real-world" information for action.
• Exercise: Simulated information for exercise participants.
• System: Messages regarding or supporting network functions.
• Test: Discardable messages for technical testing only.
• Unknown: The distribution Status is not known.
4. Confidentiality: this can be set to classified, meaning that only users of the same organisation can access it, or to unclassified, meaning that everyone can access it.
5. Language: set the language in which the “Situation Report Alert” is provided.
6. Recipient role: select the position held by the recipient of the document. The following position are available:
• First responder
• Incident Commander
• Crisis manager
• Communications officer
• Administration and finance
• Sector commander
• Command and control
• Training coordinator
• Resilience manager
7. Address: name of the organisation to whom the Situation Report is sent.
8. Pick area: select the area where the alert will be issued.
HEIMDALL [740689]
57
9. Generate situation report: generate the situation report before being dispatched.
Once the above fields have been entered the alert can be dispatched by clinking on
.
3.4 Hazard simulation tools
The Modelling and Simulation module is composed of three types of simulators, each tailored to a specific hazard: forest fires, floods and landslides. The forest fire simulator provides predictions of the fire behaviour, progression and impacts in space and time. The landslide simulator provides displacement predictions for several types of landslides, including rockfalls, debris flows and rotational landslides, as well as estimates of rainfall behaviour. Finally, the flood simulator provides predictions of the flood extent, water depth within the flooded area and water velocity. The simulators are triggered by the Service Platform (SP), which provides the necessary input parameters to run the simulations and produce the results. These simulation results are stored locally by each simulator, provided back to the SP on demand, and then they can be displayed on the Graphical User Interface (GUI) or they can be forwarded to other HEIMDALL components [9].
The hazard simulation results (i.e. maps showing the hazard extent and data related to the hazard behaviour) can be used to support risk-informed decision making across preparedness and response emergency contexts, as well as for training purposes. Moreover, those simulation results that provide information about the extent and intensity of the hazard can be further used by the Risk and Vulnerability Assessment (RVA) module (see 3.5 Risk Assessment) to perform simulation-based impact assessment [9].
The user can create a new simulation by clicking on within the “Active Incident Scenario” main menu. Then the user needs to select what type of hazard to simulate (see Image 3-59). There is one unique simulation module for forest fire and flood hazards, respectively. However, for landslide hazards four different module are available: Rockfall, Debris and Rotational landslide, which are related to specific landslide sub-types, and Landslide Rainfall analysis, which serves for landslide hazard forecasting based on rainfall intensity analysis.
HEIMDALL [740689]
58
Image 3-59. Create a New Simulation.
The procedure to run simulations for each specific hazard type as well as the display of simulation results are described in the following sections.
Fire simulator
The forest fire simulation services that are integrated into the HEIMDALL platform are based on the popular Wildfire Analyst® forest fire simulator [16]. Wildfire Analyst provides overall forest fire simulation capabilities for planning and for operational purposes in the management of forest fires, the latter due to its automatic input of data and fast processing of the simulations and the corresponding results [9].
3.4.1.1 Simulation settings
The following windows appears when selecting to run a forest fire simulation in HEIMDALL (Image 3-60). The step-by-step procedure to run a simulation is described below:
Image 3-60. Fire simulator – Simulation settings.
1. Name: set the simulation name. It is important to identify each simulation with a unique name, considering that the user might want to run successive simulations throughout the same hazard scenario.
2. Description: free text box to provide details of the simulated fire hazard. 3. Number of hours to be simulated: scroll bar to set the number of hourly time steps
(intervals) at which simulated fire perimeters will be produced. If the “Weather” is set to “Use current weather conditions (automatic)”, it uses this timestamp for retrieving the weather data.
HEIMDALL [740689]
59
4. Use same weather values for all simulation hours: click on this check box to set constant weather values for every hourly simulated perimeter. If the text box is disabled different weather values are used to generate each hourly simulated fire perimeter.
5. Start Time: set simulation start time. In live emergencies, set the current time by
clicking on . 6. Set ignition features: mark the start location of the fire. The ignition feature type can
be a line or a point. To adjust the position in order to set the ignition features, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest (see Image 3-61).
Image 3-61. Fire simulator – Set Ignition Features.
7. Set firebreak features: mark the position of fire breaks that will prevent the fire from advancing further. The firebreak feature type can be a line, a polygon or a point. Again, to adjust the Area of Interest in order to set the firebreak features, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest (see Image 3-62).
HEIMDALL [740689]
60
Image 3-62. Fire simulator – Set firebreak features.
8. Weather: the platform gives the user two options in order to set the weather values: “use current conditions”, which means that the weather values are loaded automatically from an external weather service, or “custom”, which means that the user can set the weather values manually for each hourly time step. When “custom” is selected, the window in Image 3-63 is displayed, where the user can use the scroll bars to set each specific weather input parameter to run the simulation.
Image 3-63. Fire simulator – Custom weather values.
HEIMDALL [740689]
61
Once all the parameters are set the user can run the simulation by clicking on .
3.4.1.2 Simulation results
When the simulation is ready a notification pop-up appears at the bottom of the main screen allowing the user to show the simulation results.
Moreover, all simulations are stored in the tab “Simulations & Other Associated Data” within the “Active Incident Scenario”, where the user can access the simulation outputs and manage them for their use in other platform modules. The managing of simulation results is explained is section 3.4.4 Manage simulation results.
An example of fire simulation output is displayed in Image 3-64.
Image 3-64. Fire simulator – Display of fire perimeter output for 3 h, 6 h, 9 h and 12 h after the fire starts.
For the fire perimeter output the user can check how the fire perimeter evolves overtime. By moving the scroll bar “Hours”, the fire perimeter is displayed in the form of isochrones, each isochrone representing the contour of the fire perimeter corresponding to an hourly time step.
In addition to the fire perimeter, the user can select to display other outputs relevant to fire behaviour and spread characteristics, namely Flame Length, Fire Line Intensity, Minimum Travel Time, Arrival Time, Rate of Spread, Suppression, Impact Relevance Buildings, Impact Relevance Transportation. Image 3-65 shows examples of some of them.
HEIMDALL [740689]
62
Image 3-65. Fire simulator – Display of other simulation outputs: A-Flame Length (m), B-Fire Line Intensity (kW/m2), C-Minimum Travel Time (h), D-Arrival Time (h).
Landslide simulator
The landslide simulator offers three distinct simulation modes depending on the expected landslide type in the study area: rockfalls, debris flows and rotational landslides (Figure 3-2). While the main concern in rockfalls is the extension of the area under movement, the areas exposed to the maximum risk for debris flows and rotational landslides are not the areas that are moving but the areas that can be reached by rapid moving masses (transported through the air or as a fluid) [9].
Rotational landslide Rockfall Debris flow
The mass breaks off through a curved concavely upward surface and slides
downslope.
Masses of soil or rock dislodge from a steep
slope and fall downwards.
The mass is saturated with water and viscous enough to flow rapidly
downslope.
Figure 3-2. Landslide types simulated in HEIMDALL.
Additionally, the landslide simulator includes a fourth simulation mode, called Landslide rainfall analysis, which is used to analyse the conditions that triggered the event and provides a trend of the landslide stability based on the weather forecast [9].
HEIMDALL [740689]
63
3.4.2.1 Rockfall simulator
This simulation mode analyses the probability that a specific location can be reached by rocks falling from sources defined by the user. This is performed throughout a digital landscape, represented by a digital elevation model (DEM). Usually rockfalls occurs from barerock outcrops on steep slopes as cliffs, escarpments or rock walls. These kind of rock outcrops should be delineated as sources when a simulation is run [13].
3.4.2.1.1 Simulation settings
The following windows appears when selecting to run a rockfall simulation in HEIMDALL (Image 3-66). The step-by-step procedure to run a simulation is described below:
Image 3-66. Rockfall simulation settings.
1. Name: set the simulation name. It is important to identify each simulation with a unique name, considering that the user might want to run successive simulations throughout the same hazard scenario.
2. Set simulation area: draw a polygon delimiting the geographic area that is expected to be affected by the hazard. To adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest (Image 3-67).
HEIMDALL [740689]
64
Image 3-67. Rockfall simulator – Set simulation area.
3. Sources: draw a polygon or a line delimiting the area where the rockfall will start. Sources must be inside the Simulation Area and can only be set once the this is defined (Image 3-68).
Image 3-68. Rockfall simulator – Sources.
HEIMDALL [740689]
65
4. Size: this can be set to three different classes depending on the expected rockfall volumes: small, medium and large. Indicative volume values to define the size of the rockfall based on the EIRG guide [14] as shown in Table 3-1:
Table 3-1. Rockfall simulator – Volume values to define the size of the rockfall as stated in the EIRG
guide.
Parameter Classes Category in the
EIRG guide Explanation
Size
Small M3 Rockfall volume less than 20 m3
Medium M4 Rockfall volume between 20 and 400 m3
Large M5 Rockfall volume between 400 and 25000 m3
5. Precision: this can be set to high precision or medium precision depending on the level
of resolution wished by the user for the simulation results (Table 3-2). Note that high precision simulations require a larger amount of computing time.
Table 3-2. Rockfall simulator – Precision values to define the size of the rockfall.
Parameter Classes Explanation
Precision
High precision DEM resolution < 5 m
Medium precision
DEM resolution > 5 m
Once all the parameters are set the user can run the simulation by clicking on .
3.4.2.1.2 Simulation results
When the simulation is ready a notification pop-up appears at the bottom of the main screen allowing the user to show the simulation results.
Moreover, all simulations are stored in the tab “Simulations & Other Associated Data” within the “Active Incident Scenario”, where the user can access the simulation outputs and manage them for their use in other platform modules. The managing of simulation results is explained is section 3.4.4 Manage simulation results.
An example of rockfall simulation output is displayed in Image 3-69.
HEIMDALL [740689]
66
Image 3-69. Rockfall simulator – Display of simulation results based on susceptibility of the area to be affected: high susceptibility (in red); medium susceptibility (in yellow); and low susceptibility (in green).
Simulation results indicate the susceptibility based on the probability that a DEM cell could be reached by a rockfall from the defined sources. The probability is calculated based on propagation algorithms analysis, performed using Flow-R [13], a computer program developed at the University of Lausanne. The susceptibility is represented in three classes: high, medium and low (Table 3-3).
Table 3-3. Rockfalls susceptibility classes.
Susceptibility class
Colour Meaning
1 Red High susceptibility: This area is very likely to be reached by a rockfall. Occupation or emergency activities are not recommended in this area and landslide experts support is required.
2 Yellow Medium susceptibility: This area is very likely to be reached by a rockfall. Occupation is not recommended in this area, but emergency activities may be considered. Support from landslide experts is recommended.
3 Green Low susceptibility: There is a small probability that this area will be reached by a rockfall. Temporal occupation may be considered in this area.
0 No colour Not detected
3.4.2.2 Debris flows simulator
This simulation mode analyses the probability that a specific location can be reached by a debris flow moving downslope from sources defined by the user. This is performed throughout a digital landscape, represented by a digital elevation model (DEM). Debris flows are generated in drainage basins of steeped streams with loose soil available for erosion during
HEIMDALL [740689]
67
heavy rainfalls. These loose soils should be delineated as sources when a simulation is run [13].
3.4.2.2.1 Simulation settings
The following windows appears when selecting to run a debris flows simulation in HEIMDALL (Image 3-70). The step-by-step procedure to run a simulation is described below:
Image 3-70. Debris flows simulation settings.
1. Name: set the simulation name. It is important to identify each simulation with a unique name, considering that the user might want to run successive simulations throughout the same hazard scenario.
2. Set simulation area: draw a polygon delimiting the geographic area that is expected to be affected by the hazard. To adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest (Image 3-71).
HEIMDALL [740689]
68
Image 3-71. Debris flows simulator – Set simulation area.
3. Sources: draw a polygon or a line delimiting the area where the debris flow will start. Sources must be inside the Simulation Area and can only be set once the this is defined (Image 3-72).
Image 3-72. Debris flow simulator – Sources.
HEIMDALL [740689]
69
4. Size: this can be set to two different classes depending on the expected debris flow volumes: small-medium and large. Indicative mass, volume and area values to define the size of the debris flow based on the EIRG guide [14] as shown in Table 3-4:
Table 3-4. Debris flow simulator – Mass, volume and area values to define the size of the debris flow
as stated in the EIRG guide.
Parameter Classes Category in the
EIRG guide Explanation
Size
Small - Medium
M3 – M4 Mobilized material less than 5000 t, or 3000 m3. Distance reached by the flow less than 1 km. Spreading area of deposits less than 10.000 m2.
Large M5
Mobilized material greater than 5000 t, or 3000 m3. Distance reached by the flow greater than 1 km. Spreading area of deposits greater than 10.000 m2.
5. Precision: this can be set to high precision or medium precision depending on the level of resolution wished by the user for the simulation results (Table 3-5). Note that high precision simulations require a larger amount of computing time.
Table 3-5. Debris simulator – Precision values to define the size of the debris flow.
Parameter Classes Explanation
Precision
High precision DEM resolution < 5 m
Medium precision
DEM resolution > 5 m
6. Material type: this can set to coarse, coarse-fine or fine, depending on the structure of particle size distributions typically observed in the area (Table 3-6).
Table 3-6. Debris flow simulator – Material types.
Parameter Classes Explanation
Material Type
Coarse Material mainly composed by gravel/boulder-size particles.
Coarse and fine
Mix of coarse and fine particles. No size predominates over the others.
Fine Material mainly composed by fine particles or sand.
Once all the parameters are set the user can run the simulation by clicking on .
3.4.2.2.2 Simulation results
When the simulation is ready a notification pop-up also appears at the bottom of the main screen allowing the user to show the simulation results.
Moreover, all simulations are stored in the tab “Simulations & Other Associated Data” within the “Active Incident Scenario”, where the user can access the simulation outputs and manage
HEIMDALL [740689]
70
them for their use in other platform modules. The managing of simulation results is explained is section 3.4.4 Manage simulation results.
An example of debris flow simulation output is displayed in Image 3-73.
Image 3-73. Debris flow simulator – Display of simulation results based on susceptibility of the area to be affected: high susceptibility (in red); medium susceptibility (in yellow); and low susceptibility (in
green).
Simulation results indicate the susceptibility based on the probability that a DEM cell could be reached by a debris flow from the defined sources. The probability is calculated based on propagation algorithms analysis, performed using Flow-R [13], a computer program developed at the University of Lausanne. The susceptibility is represented in three classes: high, medium and low (Table 3-7).
Table 3-7. Debris flows susceptibility classes.
Susceptibility class
Colour Meaning
1 Red High susceptibility: This area is very likely to be reached by a debris flow. Occupation or emergency activities are not recommended in this area and landslide experts support is required.
2 Yellow Medium susceptibility: This area is very likely to be reached by a debris flow. Occupation is not recommended in this area, but emergency activities may be considered. Support from landslide experts is recommended.
3 Green Low susceptibility: There is a small probability that this area will be reached by a debris flow. Temporal occupation may be considered in this area.
0 No colour
Not detected
HEIMDALL [740689]
71
3.4.2.3 Rotational landslide simulator
This simulation mode analyses the slope stability throughout a digital landscape, represented by a digital elevation model (DEM). It searches for potential landslides within a wide range of mass movement volumes that potentially could affect different parts of the DEM [16].
3.4.2.3.1 Simulation settings
The following windows appears when selecting to run a rotational landslide simulation in HEIMDALL (Image 3-74). The step-by-step procedure to run a simulation is described below:
Image 3-74. Rotational landslide simulation settings.
1. Name: set the simulation name. It is important to identify each simulation with a unique name, considering that the user might want to run successive simulations throughout the same hazard scenario.
2. Set simulation area: draw a polygon delimiting the geographic area that is expected to be affected by the hazard. To adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest (Image 3-75).
HEIMDALL [740689]
72
Image 3-75. Rotational landslide simulator – Set simulation area.
3. Soil humidity: this can be set to four different classes depending on the amount of humidity on the ground: dry, low, medium and wet (Table 3-8).
Table 3-8. Rotational landslide simulator – Soil humidity categories.
Parameter Classes Explanation
Soil humidity
Dry Dry ground
Low Low moisture on the ground
Medium Wet ground when touched
Wet Moisture spots on most of the ground
4. Soil type: this can be set to four different classes depending on the size fractions of the soil granular material (Table 3-9).
Table 3-9. Rotational landslide simulator – Soil type categories.
Parameter Classes Explanation
Soil type
Gravel Ground composed mainly by coarse particles (pebbles, boulders…)
Sand Ground composed mainly by sand
Silt Ground composed mainly by very fine sand
Clay Ground composed mainly by clay
5. Landslide type: this can be set to four different classes depending on the expected mass movement volumes: small, medium, big and very big. Indicative volume values
HEIMDALL [740689]
73
to define the type (size) of the rotational landslide based on the EIRG guide [14] as shown in Table 3-10.
Table 3-10. Rotational landslide simulator – Landslide type (size).
Parameter Classes Category in the EIRG
guide Explanation
Size
Small M2 Landslides volume between 100 and 1000 m3
Medium M3 Landslides volume between 100 and 10000 m3
Big M4 Landslides volume between 100 and 100000 m3
Very Big
M5 Landslides volume between 100 and 1000000 m3
Once all the parameters are set the user can run the simulation by clicking on .
3.4.2.3.2 Simulation results
When the simulation is ready a notification pop-up appears at the bottom of the main screen allowing the user to show the simulation results.
Moreover, all simulations are stored in the tab “Simulations & Other Associated Data” within the “Active Incident Scenario”, where the user can access the simulation outputs and manage them for their use in other platform modules. The managing of simulation results is explained is section 3.4.4 Manage simulation results.
An example of Rotational landslide simulation output is displayed in Image 3-76.
HEIMDALL [740689]
74
Image 3-76. Rotational landslide simulator – Display of simulation results based on susceptibility of the area to be affected: high susceptibility (in red); medium susceptibility (in yellow); and low susceptibility
(in green).
Simulation results indicate the susceptibility based on the minimum factor of safety for the potential slip surfaces affecting each DEM cell throughout the landscape. The factor of safety is calculated based on a limit equilibrium analysis, performed using Scoops3D [16], a computer program developed by the U.S. Geological Survey that evaluates slope stability throughout a digital landscape represented by a DEM. The susceptibility is represented in three classes: high, medium and low (Table 3-11).
Table 3-11. Rotational landslide susceptibility classes.
Susceptibility class
Colour Meaning
High Red
High susceptibility: This area is very likely to become unstable and can slide. Occupation or emergency activities in this area are not recommended and support from landslide experts is required.
Medium Yellow Medium susceptibility: This area is very likely to become unstable and can slide. Occupation is not recommended in this area, but emergency activities may be considered. Support from landslide experts is recommended.
Low Green Low susceptibility: There is a small probability that this area will become unstable and slide. Temporal occupation can be considered in this area.
No Data No colour
Not detected
3.4.2.4 Landslide rainfall analysis
This simulation mode aims to know the triggering rainfall but above all, the probability that the hazard will increase or not in the days following the emergency. The purpose is two-fold: a) the comparison of the Intensity-duration (ID) curves of the occurred and forecasted rainfalls with existing thresholds, for different climate zones, in order to determine whether they may be critical, and b) to feed a database of the rainfall-landslide triggering events in order to be available for being used in future scenario matching. The algorithm gathers rainfall recorded at the nearest weather station and compares it with the threshold in order to plan rescue operations safely.
3.4.2.4.1 Simulation settings
The following windows appears when selecting to run a landslide rainfall analysis in HEIMDALL (Image 3-77). The step-by-step procedure to run the analysis is described below:
HEIMDALL [740689]
75
Image 3-77. Landslide rainfall analysis simulation settings.
1. Name: set the simulation name. It is important to identify each simulation with a unique name, considering that the user might want to run successive simulations throughout the same hazard scenario.
2. Set simulation location: place a point at an exact location on the map where the rainfall analysis wants to be performed. To get to the Area of Interest on the map, drag the marker on the map or search by latitude and longitude coordinates (Image 3-78).
Image 3-78. Landslide rainfall analysis – Set simulation location.
3. Date: set the date of the event.
HEIMDALL [740689]
76
4. Threshold Climatic Area: this can be set to three different classes depending on the expected rockfall volumes: Warm Mediterranean Climate, Cold Mediterranean Climate and Mountain Climate. Criteria to classify different weather classes is based on the Köppen climate classification [15] as indicated in Table 3-12.
Table 3-12. Landslide rainfall analysis – Threshold Climatic area.
Parameter Classes Explanation
Threshold Climatic
Area
Warm Mediterranean climate
Csa Climate in Köppen climate classification
Cool Mediterranean climate
Csb Climate in Köppen climate classification
Mountain climate H Climate in Köppen climate classification
Once all the parameters are set the user can run the weather analysis by clicking on .
3.4.2.4.2 Simulation results
When the simulation is ready a notification pop-up appears at the bottom of the main screen allowing the user to show the simulation results.
Moreover, all simulations are stored in the tab “Simulations & Other Associated Data” within the “Active Incident Scenario”, where the user can access the simulation outputs and manage them for their use in other platform modules. The managing of simulation results is explained is section 3.4.4 Manage simulation results.
Results of the landslide rainfall analysis come in the form of graphics showing the accumulated rainfall or the intensity overtime. Notably, five different results are available for display:
• Event rainfall: hourly accumulated rainfall (in mm) during an ongoing event (Image 3-79).
Image 3-79. Landslide rainfall simulation results – Event rainfall.
• Antecedent rainfall: accumulated rainfall (in mm) 7 days, 3 days and 24 hours before the event starts (Image 3-80).
HEIMDALL [740689]
77
Image 3-80. Landslide rainfall simulation results – Antecedent rainfall.
• ID curve triggering rainfall: rainfall intensity (in mm/h) during an ongoing event (Image 3-81). Guzzetti’s curve (in orange) shows the thresholds for the possible initiation of rainfall-induced landslides. Having the rainfall event curve (in blue) above Guzzetti’s curve is indicative of an eventual hazard increase.
Image 3-81. Landslide rainfall simulation results – ID curve triggering rainfall.
• ID curve forecasting rainfall for 24h: rainfall intensity (in mm/h) during the event and 24 h after the event (Image 3-82). Guzzetti’s curve (in orange) shows the thresholds for the possible initiation of rainfall-induced landslides. Having the rainfall event curve (in blue) or the rainfall post-event curve (in green) above Guzzetti’s curve is indicative of an eventual hazard increase.
HEIMDALL [740689]
78
Image 3-82. Landslide rainfall simulation results – ID curve forecasting rainfall for 24 h.
• ID curve forecasting rainfall for 3 days: rainfall intensity (in mm/h) during the event and 3 days after the event (Image 3-83). Guzzetti’s curve (in orange) shows the thresholds for the possible initiation of rainfall-induced landslides. Having the rainfall event curve (in blue) or the rainfall post-event curve (in green) above Guzzetti’s curve is indicative of an eventual hazard increase.
Image 3-83. Landslide rainfall simulation results – ID curve forecasting rainfall for 3 days.
• ID curve forecasting rainfall for 7 days: rainfall intensity (in mm/h) during the event and 7 days after the event (Image 3-84). Guzzetti’s curve (in orange) shows the thresholds for the possible initiation of rainfall-induced landslides. Having the rainfall event curve (in blue) or the rainfall post-event curve (in green) above Guzzetti’s curve is indicative of an eventual hazard increase.
HEIMDALL [740689]
79
Image 3-84. Landslide rainfall simulation results – ID curve forecasting rainfall for 7 days.
Flood simulator
The flood simulator is based on the complete 2D hydraulic model (FloS-complete), which allows to generate flood scenarios also defining the flood dynamics with high spatial and temporal resolution (with a fully 2D grid-based inundation model). This can run a inundation model, using different simulation parameters defined by the user such as area of simulation, discharge location, peak discharge value [9].
3.4.3.1 Simulation settings
The following windows appears when selecting to run a flood simulation in HEIMDALL (see Image 3-85). The step-by-step procedure to run a flood simulation is described below:
HEIMDALL [740689]
80
Image 3-85. Flood simulator settings.
1. Name: set the simulation name. It is important to identify each simulation with a unique name, considering that the user might want to run successive simulations throughout the same hazard scenario.
2. Set simulation area: draw a polygon delimiting the geographic area that is expected to be affected by the hazard. To adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest (Image 3-86).
HEIMDALL [740689]
81
Image 3-86. Flood simulator – Set simulation area.
3. Set streams: set discharge values for every stream within the simulation area. Discharge values need to be entered in m3/s. To set a discharge point, specify the discharge location at some point along the river basin (Image 3-87).
HEIMDALL [740689]
82
Image 3-87. Flood simulator – Discharge points.
Then a window pops up to set the discharge rate in m3/s (Image 3-88).
Image 3-88. Flood simulator – Discharge value.
4. Resolution (m): scroll bar to set the display of resolution for the simulation results. The user can set values between 5 m (finest resolution) and 20 m (courser resolution).
5. Speed of the river flow (m/s): scroll bar to set the speed of the water flow as a result of the flood event. The user can set values between 1 and 10 m/s.
6. Durations (hours): scroll bar to set the number of hourly time steps (intervals) at which the state of the simulated flood extent will be generated. The user can set values between 1 and 24 h.
7. Initial time: set simulation start time. In live emergencies, click on to set the current time.
8. Save interval (hours): scroll bar to set the interval length in hours for each simulated time step. The user can set values between 1 and 6 h.
Once all the parameters are set the user can run the simulation by clicking on .
HEIMDALL [740689]
83
3.4.3.2 Simulation results
When the simulation is ready a notification pop-up appears at the bottom of the main screen allowing the user to show the simulation results.
Moreover, all simulations are stored in the tab “Simulations & Other Associated Data” within the “Active Incident Scenario”, where the user can access the simulation outputs and manage them for their use in other platform modules. The managing of simulation results is explained is section 3.4.4 Manage simulation results.
An example of flood simulation output using a discharge value of 1,100 m3/s is displayed in Image 3-89.
Image 3-89. Flood simulator – Display of simulation results for a discharge value of 1,100 m3/s at time steps 4 h, 8 h, 12 h and 16 h after the river overflowing starts.
For the flood extent output the user can check how the flooding event evolves overtime. By moving the scroll bar “Hours”, the flood extent is displayed for each time step.
Manage simulation results
The user can display the simulation results by clicking on the tab “Simulations & Other Associated Data” within the “Active Incident Scenario” menu and selecting one the simulations from the list (Image 3-90).
HEIMDALL [740689]
84
Image 3-90. Managing simulation results – Simulation and Other Associated Data.
Then the window in Image 3-91 is unfold where the user can select one of the current
simulation results from the list clicking on the unfold button , or import a simulation from
another scenario in the platform by clicking on the plus button .
Image 3-91. Managing simulation results – List of simulation results.
3.4.4.1 Manage simulation from the active incident scenario
When the user select one of simulations from the list, the menu for that specific simulation appears like in Image 3-92 (the example shows the simulation called “firetest 23 firebreak”).
HEIMDALL [740689]
85
Image 3-92. Managing simulation results – Simulation results menu.
By clicking on the user can display the simulation. The graphical representation of the simulated hazard is displayed on the main map.
By clicking on the user can create a new simulation based on the existing one. The user can here adjust any simulation input parameters from the previous simulation and thus obtain new simulation results.
By clicking on , in the upper part of the menu, or on , next to “Simulation type”, the user can copy the URL of the simulation. Thus, previous simulations can be likewise
accessed entering their URL. To do so, the user needs to click on , at the upper right side of the “Simulations & Other Associated data”, menu (see Image 3-91) that prompts to the following window (Image 3-93):
Image 3-93. Managing simulation results – Display simulation results using the URL.
Here the user needs to add a description and select “Simulation” in the Data Type dropdown menu.
Finally, by clicking on the button, next to “Simulation Image” (Image 3-92), the user can add a screenshot of the simulation. An example of screenshot for a wildfire simulation is displayed in Image 3-94.
HEIMDALL [740689]
86
Image 3-94. Managing simulation results – Display of simulation screenshot.
3.4.4.2 Import simulations from other scenarios
The user can click on the plus button (see Image 3-91), the window in Image 3-95 appears where the user can import a simulation that has been generated outside “Active Incident Scenario”.
Image 3-95. Managing simulation results – Import simulation from other scenarios.
1. Description: free text with information of the simulation that is imported into the active incident scenario.
2. Data type: This can be set to “Simulation” or to “What-if simulation”. The user selects “What-if simulation”, if the imported simulation is going to be used to perform what-if analysis.
3. URI: Uniform Resource Identifier where the imported simulation is stored.
By clicking on the button, the simulation is added to the list of existing simulations in the active incident scenario.
3.5 Risk Assessment
The Risk Assessment module has the purpose of processing and providing exposure and impact assessment products inside the HEIMDALL system. Thus, the user can obtain and estimation of the potential hazard impact for a certain area based on a simulation perimeter resulting from the hazard simulation module. To achieve that purpose, the risk assessment module is designed with two main sub-modules: the Exposure Assessment sub-module and the Impact assessment sub-module. The first identifies exposed elements, i.e. elements that could be adversely affected (including life and property) by the hazard(s). At this stage, no quantitative information about damage percentage due to interaction with the hazard(s) is available. The second provides an impact estimation of the hazard(s) on people and assets using the characteristics of the exposed elements (e.g. building type). The outputs and results
HEIMDALL [740689]
87
of the exposure sub-module will serve as an input for the impact estimation sub-module, accounting for the expected losses and adverse effects in relation to a specific hazard [10] [11].
The outputs generated by the Risk Assessment module can be used to improve the resource allocation in the field during disaster response, response training and post-disaster. In addition, the information provided could help to communicate the financial needs of the respective emergency response organisations to cope with the number of affected people and assets [11].
Impact Assessment
Provided a simulation has been triggered and the results are available, the user can trigger an Impact Assessment based the hazard simulation results. To do so, the user must click on the tab “Simulations & other associated data” from the main menu in ““Active Incident Scenario””, and then select one of the existing simulations (see Image 3-96).
Image 3-96. Impact Assessment – Select one simulation.
Then, the settings displayed in Image 3-97 unfold, where Impact Assessment can be triggered for two type of elements: Buildings/GOIs (Geographical Objects of Interest) and Roads. The procedure to trigger and Impact Assessment on buildings/GOIs and roads is described below, whereas the procedure to trigger an Impact Summary is separately described in section 3.5.2 Impact Summary.
3.5.1.1 Impact buildings/GOIs
this module estimates the expected human, physical and economic damage based on identified assets/GOIs, damage/vulnerability functions and simulated hazard intensity information.
HEIMDALL [740689]
88
Image 3-97. Impact Assessment menu for Buildings/GOIs and Roads.
1. Impacted Buildings: click on the button next to Impacted buildings to request an Impact Assessment on buildings and GOIs based on the results of the simulation (Image 3-98).
Image 3-98. Impact Assessment for buildings/GOIs – IA Request IA.
Here, the user only needs to specify the name and set the exposure layer to DEMO Buildings Exposure to calculate the potential impact on buildings and GOIs. An example of Impact Assessment results for buildings is displayed in Image 3-99, where the fire perimeter isochrones are displayed in red and buildings affected are coloured based on the percent damage on the structure.
Image 3-99. Impact Assessment for buildings and GOIs – Results.
Furthermore, by clicking on an individual building, the user can get information about the damage on the specific element (see Image 3-100).
HEIMDALL [740689]
89
Image 3-100. Impact Assessment for buildings and GOIs – Impact information.
Relevant information about the impact on each building includes:
• Economic damage (structure) expressed in $.
• Fire linear intensity expressed in kW/m2.
• Percent damage (structure) expressed in %.
• build_use: building use (e.g. education, not residential, single family house…).
• pop_night: number of people expected to be affected if the hazard impact occurs at night.
• popul_day: number of people expected to be affected if the hazard impact occurs in the daytime.
While the rest of the data displayed is required for the platform back-end, it is irrelevant for the user.
2. Buildings Assessments Screenshot: click on the button next to Buildings Assessment Screenshot to attach a screenshot of the Impact Assessment (Image 3-101). The procedure to create a screenshot is described in section 3.2.2.4 Screenshots.
HEIMDALL [740689]
90
Image 3-101. Impact Assessment for buildings and GOIs – Screenshot.
3.5.1.2 Impact Roads
This module identifies affected/non-affected roads using the simulation results.
Image 3-102. Impact Assessment menu for Roads.
1. Impact Assessment: click on the button next to Impact Assessment to request an Impact Assessment on roads based on the results of the simulation (Image 3-103).
Image 3-103. Impact Assessment for Roads – IA Request.
Here, the user only needs to specify the name and set the exposure layer to DEMO Transportation to calculate the potential impact on roads. An example of Impact Assessment results for roads is displayed in Image 3-104.
Image 3-104. Impact Assessment for Roads – Results.
HEIMDALL [740689]
91
Furthermore, by clicking on an individual road segment, the user can get information about the damage on the specific element (see Image 3-105).
Image 3-105. Impact Assessment for Roads – Impact information.
Relevant information about the impact on each road includes:
• Fire linear intensity expressed in kW/m2.
• Meters affected of that road segment.
• length: total length of the road segment (including both the part affected and the part not affected.
• percent_damage expressed in %.
While the rest of the data displayed is required for the platform back-end, it is irrelevant for the user.
2. Impact Assessment Screenshot: click on the button next to Buildings Assessment Screenshot to attach a screenshot of the Impact Assessment (Image 3-106). The procedure to create a screenshot is described in section 3.2.2.4 Screenshots.
HEIMDALL [740689]
92
Image 3-106. Impact Assessment for Roads – Screenshot.
Impact Summary This module deals with the generation of aggregated Impact Summary Information (ISA Information) for pre-defined target areas on relevant infrastructure and people at risk, which supports, together with simulation and Risk Assessment tools, the evaluation of simulated scenarios during the analysis of potential impacts. Impact summary generation is part of the impact assessment activity and makes use of other products generated here such as physical and human impact assessment products [12].
Impact Summary is enabled provided an Impact Assessment has been generated before. The procedure to generate an Impact Summary for buildings/GOIs or for roads is described in the following two subsections.
3.5.2.1 Impact buildings/GOIs
When an Impact Assessment has been generated for buildings/GOIs, the user can click on the
button next to Impact Summary. Then, the window in Image 3-107 appears where the user needs to select the area of interest to identify the buildings/GOIs affected by the hazard. To adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest.
HEIMDALL [740689]
93
Image 3-107. Impact Summary for buildings/GOIs – Select Area of Interest.
When the Impact Summary is ready, the options showed in Image 3-108 appear next to Impact Summary section.
Image 3-108. Impact Summary for buildings/GOIs – Menu for visualisation of results.
1. Total affected buildings and population: quantitative estimates of the number of buildings and population affected. Affected population during the daytime is distinguished from affected population during the night-time, considering that the population distribution may differ depending on the time of day.
2. Show more: quantified information about the hazard impact in human, physical and economic terms (Image 3-109).
HEIMDALL [740689]
94
Image 3-109. Impact Summary for buildings/GOIs – Impact Summary in numbers.
3. Download affected buildings: download an Excel file listing all the buildings affected and the human and physical damage associated with each of them (Image 3-110).
Image 3-110. Impact Summary for buildings/GOIs – Impacted buildings.
4. Download affected buildings – GOIs: download an Excel file listing all the GOI-specific buildings affected and the human and physical damage associated with each of them (Image 3-111).
Image 3-111. Impact Summary for buildings/GOIs – Impacted buildings - GOIs.
5. Remove: delete the Impact Summary generated.
3.5.2.2 Impact Roads
When an Impact Assessment has been generated for roads, the user can click on the button next to Impact Summary. Then, the window in Image 3-112 appears where the user needs to select the area of interest to identify the roads affected by the hazard. To adjust the Area of Interest on the map, drag the marker on the map or specify the latitude and longitude coordinates of the Area of Interest.
HEIMDALL [740689]
95
Image 3-112. Impact Summary for Roads – Select Area of Interest.
When the Impact Summary is ready, the options showed in Image 3-113 appear next to Impact Summary section.
Image 3-113. Impact Summary for Roads – Menu for visualisation of results.
1. Total affected roads: quantitative estimates of the number of roads affected. 2. Show more: quantified information about the hazard impact in human, physical and
economic terms (Image 3-114).
HEIMDALL [740689]
96
Image 3-114. Impact Summary for Roads – Impact Summary in numbers.
3. Download affected roads: download an Excel file listing all the roads affected and the human and physical damage associated with each of them (Image 3-115).
Image 3-115. Impact Summary for Roads – Impacted roads.
4. Remove: delete the Impact Summary generated.
3.6 Scenario Matching
The Scenario Matching functionality allows the user to find other scenarios from the local storage with a similar context, environmental conditions, hazard behaviour and stressed capabilities. The combination of recording and matching scenarios from prior incidents can improve the ability of stakeholders to learn and evolve from complex situations and thereby to respond more effectively and operate more efficiently during disasters. During the preparedness phase of the emergency, scenario matching helps the user identify other scenarios that occurred under similar synoptic situations, which indicates that a given synoptic situation could be conducive to the development of a hazard with similar characteristics. During the response phase, scenario matching helps the user identify other scenarios that exhibited similar behaviour patterns to the ones that are being observed at that moment, thus facilitating better assessment of the evolution of the hazard.
Scenario matching tool is accessed by clicking on in the upper part of the main screen (see Image 3-2), which opens the window displayed in Image 3-116.
HEIMDALL [740689]
97
Image 3-116. Scenario Matching – Main menu.
The matching parameters displayed in Image 3-116 are described below:
1. Use landscape parameters of active scenario and filter only: click on this check box to enable the Weighted Criteria section (3), thus allowing to add to the matching criteria parameters that have been entered in the active scenario. These parameters can be used for the matching by assigning them a weighted criteria that serves for a more accurate search of matching results (described in label 3).
2. Filters: specify at least one of the following parameters for the matching:
• Hazard type: select among a series of hazard types and subtypes, namely:
o Landslide
o Landslide: Debris fall
o Landslide: Rockfall
o Flood
o Flood: Estuarine/coastal
HEIMDALL [740689]
98
o Flood: Storm surge
o Flood: Flash flooding
o Flood: Fluvial flooding
o Forest fire
o Forest fire: Storm-dominated fire
o Forest fire: Convection-dominated fire producing pyrocumulus clouds
o Forest fire: Convection-dominated fire with wind
o Forest fire: Standard convection-dominated fire
o Forest fire: Wind-driven with subsidence
o Forest fire: Wind-driven fire in mountainous terrain
o Forest fire: Topographic fire in main valleys and canyons
o Forest fire: Coastal topographic fire
o Forest fire: Standard topographic fire
• Status: this can be set to:
o Unknown: the hazard situation is unknown.
o Training: historical or fictional scenarios are used for training exercises.
o Actual: the hazard situation is real.
• Urgency: this can be set to:
o Expected: the incident can occur within the next few hours.
o Fictional: unreal scenarios with made-up hazard situations.
o Historic: historical incident that affected the territory.
o Future: pre-hazard conditions suggest a great chance that an incident can occur in the foreseeable future.
o Immediate: the incident can occur immediately.
• Synoptic Situation: general state of the atmosphere in terms of pressure pattern, fronts, wind direction and speed and how they will change and evolve overtime. this can be set to [1]:
o Atmospheric instability
o Storm winds
o Valleys and mountain slopes topographic winds
o Winds from sea to land and from land to sea due to day-night changes
o Hot wave and low relative humidity
o Dry and hot wind moderate or/and strong
o Strong wind
• Hazard category: this can be set to:
o Landslide
o Flood
o Forest fire
HEIMDALL [740689]
99
• Fire type: only in case of forest fire scenarios, the user can select the specific fire type for the matching. Fire types refers to singular and repeated spreading patterns and weather (synoptic conditions). The user can here select the fire type among a series of pre-defined categories [1]:
o Storm-dominated fire
o Convection-dominated fire producing pyrocumulus clouds
o Convection-dominated fire with wind
o Standard convection-dominated fire
o Wind-driven with subsidence
o Wind-driven fire in mountainous terrain
o Topographic fire in main valleys and canyons
o Coastal topographic fire
o Standard topographic fire
• Fire propagation type: only in case of forest fire scenarios, the user can select the specific fire propagation type for the matching:
o Crown active
o Crown passive
o Sustained torching
o High-intensity surface
o Medium intensity surface
o Low intensity surface
o No description
3. Weighted criteria: use additional parameters for the matching, notably those parameters that the user has entered in the “Active Incident Scenario” (see Image 3-116). The user can consider that some parameters are more relevant than others for the matching and therefore establish a criterion by assigning them a weight value from 0 to 10 according to their relevance. To use each of these parameters with their associated weighted value, the user needs to directly drag the scroll bar next to them (see Image 3-116).
As indicated before, Weighted Criteria is only enabled provided when the user has selected the option “Use landscape parameters of active scenario and filter only” (see label 1).
The output of scenario matching consists of a list of scenarios like the real situation, based on several matching parameters set by the user (see Image 3-117).
HEIMDALL [740689]
100
Image 3-117. Scenario matching – Outputs.
3.7 Situation Report (SitRep) The Situation Report (SitRep) component provides an interface for system clients to transform all information available for a scenario at a given point of time (scenario snapshot) into a situation report in a standardized message format. The goal is to create means for sharing a COP in a standards-based way in order to foster interoperability between systems. The idea is that a system client (e.g. a mobile app on a field responder’s phone) can request scenario information from a HEIMDALL system in a different location, e.g. in a control room in a different country. If that client includes a tool to interpret the message protocol and format, it can present information included in the message in an editable format such as word, including map layers [12].
SitRep documents include general information about the hazard and the weather conditions as well as outputs obtained from the simulation and Impact Assessment modules.
As indicated in Image 3-118, for a given simulation to be included in a SitRep, the user needs to tick the box “Include in SitRep?” within the tab “Simulations & Other Associated Data”. In this instance, only the simulation called “Jonquera” is selected to be included in the SitRep that will be generated.
Image 3-118. SitRep – Example of simulation included into the SitRep document.
Once one simulation or various simulations are selected, the user can generate the SitRep by
clicking on in the ““Active Incident Scenario”” menu (see Image 3-119).
HEIMDALL [740689]
101
Image 3-119. SitRep – Generate SitRep document.
The HEIMDALL platform generates SitRep documents specific to fire, landslide and flood events. The SitRep is fed with some of the outputs generated by the user in the platform; nevertheless, the fact that it comes in word editable format allows the user to fill it in with additional information obtained from other sources. The following information is automatically reported on the SitRep document that generates the platform:
• General information about the incident (e.g. municipality, incident start date and time, incident location…) as entered by the user in the main Incident Scenario menu (see 3.3.1.2 Incident scenario).
• Weather conditions: Temperature, Relative Humidity, Wind Speed… as entered by the user in the “Weather conditions” tab associated with that “Active Incident Scenario” (see 3.3.2 Weather Conditions).
• Hazard perimeter extent: expected surface affected as calculated by the fire simulator.
• Simulation image: screenshot associated with the simulation included in the SitRep. For the image to be included in the SitRep, the user needs should have made the screenshot before (see 3.2.2.4 Screenshots) and added it to the associated simulation (see 3.4.4 Manage simulation results).
• Hazard behaviour characteristics (only for fire-specific hazards): Flame Length, Fire Intensity and Rate of Spread, as calculated by the fire simulator.
• Impact Assessment:
o For roads: list with the name and type (e.g. primary, secondary…) of roads affected as generated in the Impact Summary (see 3.5.2.2 Impact Roads).
Roads Impact Assessment image: screenshot of the Impact Assessment associated with the simulation included in the SitRep. For the image to be included in the SitRep, the user should have added an screenshot to the associated simulation (see 3.5.1.2 Impact Roads).
HEIMDALL [740689]
102
o For GOIs and critical infrastructure: listing the function (single family, factory, school, hospital…) municipality and population affected of each item affected as generated in the Impact Summary (3.5.2.2 Impact Roads).
Buildings/GOIs Impact Assessment image: screenshot of the Impact Assessment associated with the simulation included in the SitRep. For the image to be included in the SitRep, the user should have added an screenshot to the associated simulation (see 3.5.1.1 Impact buildings/GOIs).
Image 3-120 shows an example of SitRep document for a fire hazard incident.
HEIMDALL [740689]
103
Image 3-120. SitRep – Example of SitRep for a fire incident.
3.8 Data sources
HEIMDALL incorporates a wide range of data sources including satellite-, ground- and aerial-based sensors that are combined for the detection and monitoring of forest fires, floods and terrain movements. The following sections provide a detailed description of these data products that use those sensors, the information they provide to the HEIMDALL platform, and the way how this information can be consulted on the platform by the users.
HEIMDALL [740689]
104
Satellite-based data: Earth Observation products
The objectives of the HEIMDALL Earth Observation (EO) services are to provide reliable and high-quality satellite-based information as input for modelling and risk assessment as well as for supporting emergency response activities in case of fire, flood, and landslide events. The EO services integrate satellite products of various optical and radar sensors. The data are automatically or semi-automatically processed and the final EO-based crisis information products are provided to the HEIMDALL Service Platform via Web Feature Services (WFS) or Web Mapping Services (WMS) [5].
To display the Earth Observation layers on the GUI the user must click on the tab “Layers” on the right-hand side of the screen and then filter the layers available by typing in the name. When an EO layer is selected is appears as an “Active layer” in the panel (see Image 3-121).
Image 3-121. Earth Observation – Search of layers for display on the GUI.
The module offers several crisis products based on multi-sensorial Earth Observation data including the following products: flood masks, burn scars, fire hot spots, masks showing the extent of abrupt landslides as well as information about the velocities of slow-moving landslide events.
The products are provided as vector and/or raster files to the Service Platform via Web Feature Services (WFS) or Web Mapping Services (WMS) and derived by the following semi-automatic and automatic services [7]:
• Automatic Sentinel-1 and TerraSAR-X flood processing chains
• Automatic Sentinel-2 burn scar mapping chain
• Automatic MODIS-based hotspot service for wildfire detection
• Automatic Sentinel-2 flood processing chain
• VHR optical flood processing chain
• Sentinel-2 landslide mapping chain
• Processing chain for updating landslide activity based on Sentinel-1 interferometric data.
HEIMDALL [740689]
105
Typically, the following EO layers are generated for fire, floods and landslides:
• Hazard extent
• Fire hotspots (only for fire-specific hazards)
• Impact on buildings
• Impact on population
• Impact on roads
• Impact on Land Use Land Cover
An example of EO layer relevant to the hazard extent is provided in Image 3-122.
Image 3-122. Earth Observation – Examples of EO layers for hazard extend for fire (A), floods (B) and landslides (C).
Ground-based data: In-situ sensors and GB-SAR
The HEIMDALL platform is equipped with a module for Landslide Monitoring with a goal to monitor the terrain stability conditions of an area that has been identified as unstable, by installing several sensors in-situ. These sensors will measure parameters that are directly or indirectly related to the stability of the terrain. Data from in-situ sensor can provide relevant information to predict failures in advance and act as warning systems [8].
Two types of sensors systems are integrated in HEIMDALL for landslide monitoring, the geotechnical and hydrological landslide monitoring systems and the GB-SAR Landslide Monitoring system [8].
3.8.2.1 Geotechnical and hydrological landslide monitoring systems
The geotechnical and hydrological landslide monitoring systems are designed to measure physical properties related to the stability of the terrain in areas that have been identified as notably susceptible to the occurrence of landslides. These data are useful to warn about approaching unstable conditions that can trigger landslides.
To display them on the GUI, the user must click first on the tab “Map Controls” on the right-
hand side of the screen and make sure that “sensors” is enabled, and then click on to navigate to the actual location (see Image 3-123).
HEIMDALL [740689]
106
Image 3-123. In-situ sensors – Activation of sensors for visualisation on the GUI.
Red points in Image 3-124 correspond to a set of stations with in-situ sensors that are strategically placed across a landslide-prone area.
Image 3-124. In-situ sensors – Display of stations with in-situ sensor on the GUI.
Sensors placed in these stations are intended to monitor if the terrain is moving, how fast it is doing and how much water is inside the terrain. The most common automatic measurements provided on the HEIMDALL platform are conducted using the following analogue and digital sensors [8]:
• Analogue: o Crackmeters to measure the aperture of cracks (in mm). They are installed by
anchoring two threaded anchors with ball joints on opposite sides of the crack.
HEIMDALL [740689]
107
The user can check the oscillations on the crack aperture for the period preceding a specific date (see Image 3-125).
Image 3-125. In-situ sensors – Aperture of cracks measured overtime by a crackmeter sensor for a
defined time period.
o Piezometers to measure groundwater pore water pressure (in mWG). The user can check the oscillations on the pore water pressure for the period preceding a specific date (see Image 3-126).
Image 3-126. In-situ sensors – Pore water pressure measured overtime by a piezometer sensor for a
defined time period.
• Digital:
HEIMDALL [740689]
108
o Tiltmeters to measure the tilt of buildings or structures (in degrees). The user can check the oscillations on the degree of tilt for buildings or structures for the period preceding a specific date (Image 3-127).
Image 3-127. In-situ sensors – Degree of tilt measured overtime by a tiltmeter sensor for a defined
time period.
3.8.2.2 GB-SAR Landslide Monitoring system
The GB-SAR (Ground Based Synthetic Aperture Radar) Landslide Monitoring system is designed to estimate the degree of deformation, or displacement, of the selected slope where the landslide occurs. This data is provided to the users as close to real time as possible, especially when it is used in addition to a warning and alarm system. They are installed in a stable area in front of the landslide in order to provide radar images, similar to those from a spaceborne radar, but using a system installed in situ, within a few kilometres from the slope, based on a linear rail where a microwave transceiver moves continuously [8].
To display the GB-SAR layers on the GUI the user must click on the tab “Layers” on the right-hand side of the screen and then filter the layers available by typing in the name. When an GB-SAR layer is selected is appears as an “Active layer” in the panel (Image 3-128).
HEIMDALL [740689]
109
Image 3-128. GB-SAR – Search of GB-SAR layers for display on the GUI.
The cloud of points in Image 3-129 corresponds to the deformation measured during a temporal interval of 32 hours. Legend colours indicate direction and magnitude of the deformation cumulated during the selected lapse: green points represent stable pixels (no deformation); points with negative range values −from red to yellow− indicate pixels moving along the line of sight, i.e. toward the radar; finally, points with positive range values −from blue sky to navy blue− indicate the rare case of a displacement stepping away from the radar, which can occur in complex scenarios. In this instance, the predominance of green points shows that the landslide is in a stable condition.
Image 3-129. GB-SAR – Deformation along the line of sight measured by the GB-SAR occurred during the temporal interval 26-27 May 2018.
HEIMDALL [740689]
110
Aerial-based data: Drones
HEIMDALL offers an aerial-based data product to support firefighters during wildfire-specific emergencies that consists of a swarm of drones to monitor the affected area and detect hotspots.
Data from drones constitute an input to the service platform that transmits RGB (Red, Green, Blue) and thermal pictures taken by drones as well as the drones’ real time position. A satellite link is established as the communication channel to transmit the data, since forest fires may take place in regions with limited signal coverage. The use of a satellite link allows the operator to transmit information from remote locations directly to the HEIMDALL service platform [8].
Drones images can be visualised on the platform by clicking on the “Assets” tab on the left-
hand side of the screen, selecting “DRONES” and clicking on the location sign that takes the user to the location of the drone images. Image 3-130 shows a cloud of drone images that have been captured by two different drone devices and transferred to the HEIMDALL platform.
Image 3-130. Drones – Cloud of drone images displayed on the GUI.
As observed in Image 3-131, by clicking on the user can visualise the thermal and RGB images taken by the drones in the field. Drones images can be sent as waypoints (see 3.2.2.2 Add Marker (Waypoints) to field responders in the field using the mobile app (see 3.9.2 HEIMDALL application).
HEIMDALL [740689]
111
Image 3-131. Drones – Thermal and RGB images (left and right, respectively).
3.9 Data sharing and communication
One major goal of HEIMDALL is to foster data and information sharing among stakeholders of multiple organisations and multiple disciplines also in international context in order to improve the cooperation capabilities. For this, HEIMDALL sets up a federated architecture of multiple Local Units (LU) for sharing data, information and to provide collaboration services. A LU is an instance of a HEIMDALL system which can be accessed by a single organisation, e.g. fire fighters in Catalonia or France, medical services, police, civil protection, command and control [5].
Three HEIMDALL modules are designed for the purposes of data sharing and communication: The information gateway, the smartphone application and the Catalogue. For text based communication an XMPP based chat tool has been integrated into the GUI which is hosted by the SP.
Chat The chat is used for collaboration and direct communication of involved personnel through the exchange of messages, locations and pictures from the field. Communication can effectively be:
• Between users operating the platform;
• or between one user operating the platform and another using the mobile phone app.
This “Chat” section will describe how to use the chat function for the first option: “between users operating the platform”. For the two later see 3.9.2 HEIMDALL application.
The user can access to the chat service by clicking on the “Assets” tab on the left-hand side of the screen and selecting “FIRST RESPONDERS” (see Image 3-132). Those users who are logged into the platform have a green dot to the left, whereas those who are not logged have a grey dot.
HEIMDALL [740689]
112
Image 3-132. Chat service on the GUI.
HEIMDALL users have their own chat windows where other users can text messages, send locations and pictures. Image 3-133 shows a chat window of a specific user.
Image 3-133. Chat window for a HEIMDALL user.
1. Username: unique identification name of the user. The green dot to the left indicated that this user is logged into the platform.
2. Location: last location of this user. This is only functional for users operating the smartphone app.
3. Picture: send a picture to this user. This is only functional for users operating the smartphone app.
4. Chat panel: main panel where the current chat stream is. 5. Message: text box where the user can type and a message.
HEIMDALL [740689]
113
HEIMDALL application
The HEIMDALL application (android version only) is the tool that allows data sharing and communication between first responders in the field and Control Rooms Operators using the platform, or between two first responders in the field. The information provided by first responders on the ground using the HEIMDALL app is crucial for the assessment of the hazard behaviour and evolution in real time.
3.9.2.1 Log in – HEIMDALL application
Similarly, to the HEIMDALL web portal, access to the HEIMDALL app is possible only via an OpenVPN connection, which is supported by SPH. For that, the user can download an OpenVPN from the app store at this link: https://play.google.com/store/apps/details?id=net.openvpn.openvpn&hl=de.
Once connected to the VPN network, the user needs to install the HEIMDALL app on a smartphone or tablet device. Up to date (October 2020) the HEIMDALL app is not available on the Google Play Store, but can be internally downloaded by HEIMDALL partners.. Upon successful installation the user can log into the app by entering the username and password (Image 3-134).
Image 3-134. HEIMDALL app log in screen.
3.9.2.2 Main screen features
Image 3-135 shows the main features that appear on the main screen of the HEIMDALL platform.
HEIMDALL [740689]
114
Image 3-135. HEIMDALL app – Main screen.
1. Chat 2. Map 3. Situation Report 4. Share pictures and locations 5. Logout and download offline maps
Each of the above HEIMDALL app functionalities are explained in the following sections:
3.9.2.3 HEIMDALL app chat
This is window where the user can communicate with other users using the platform or the app by sending and receiving text messages. Alike the HEIMDALL platform, Smartphone app users have their own chat windows where the interaction with other users takes place (see Image 3-136).
Image 3-136. HEIMDALL app – Chat.
HEIMDALL [740689]
115
3.9.2.4 HEIMDALL app map
The map allows the visualisation of the geographical area. The user can click on to focus on current position (Image 3-137).
Image 3-137. HEIMDALL app – Map.
3.9.2.5 HEIMDALL app Situation Report
The HEIMDALL app displays a summarised situation report with key incident scenario data relevant to the active incident scenario. The incident data provided in the Situation Report is showed in Image 3-138. It is worth noting that users on the platform can generate a downloadable Situation Report document with additional data on the incident scenario (see 3.7 Situation Report (SitRep)).
HEIMDALL [740689]
116
Image 3-138. HEIMDALL app – Situation Report.
3.9.2.6 HEIMDALL app share picture and share location options
By clicking on the user can send a picture or the current location (see Image 3-139).
Image 3-139. HEIMDALL app – Share Picture or Location.
1. Picture: take a picture from the smartphone or tablet device and send it to the HEIMDALL platform (see Image 3-140).
HEIMDALL [740689]
117
Image 3-140. HEIMDALL app – Send Picture.
Then, the picture can be visualised by users operating the HEIMDALL platform from the chat menu in the chat windows of the user who has sent the picture by clicking
on (see Image 3-141).
Image 3-141. HEIMDALL app – Check location send form the app in the HEIMDALL platform.
Furthermore, users operating the HEIMDALL platform will receive a notification that an image has been sent from the app, and that will be stored in the tab “Images” within the “Active Incident Scenario” main menu (see section 3.3.7 Images), along with other pictures.
HEIMDALL [740689]
118
2. Location: send the current location at a certain point in time (see Image 3-142).
Image 3-142. HEIMDALL app – Send Location.
Then, the location can be checked by users operating the HEIMDALL platform from the chat menu in the chat windows of the user who has sent the location by clicking
on (see Image 3-143).
Image 3-143. HEIMDALL app – Check location send form the app in the HEIMDALL platform.
HEIMDALL [740689]
119
3.9.2.7 HEIMDALL app Logout and Download Offline map options
By clicking on the user can either logout or download a map for offline consultation (see Image 3-144).
Image 3-144. HEIMDALL app – Logout or Download Offline Map.
6. Logout: exit the session. 7. Download Offline Map: download the map, with all the incident data that it may
incorporate (Image 3-145). The map will thus be available for offline use.
Image 3-145. HEIMDALL app –Download map for offline use.
HEIMDALL [740689]
120
3.9.2.8 HEIMDALL app waypoints
HEIMDALL app users can also create and receive waypoints. The procedure in this case is simpler that doing it from the HEIMDALL platform (see section 3.2.2.2 Add Marker (Waypoints)).
To create a waypoint from the app, the user needs to press and hold on the location where the waypoint will be a created. Then, a windows like in Image 3-146 will pop up where the user will need to add a description about the waypoint and press “OK” to send it. Then, users operating the HEIMDALL platform will receive a notification that a waypoint has been sent from the app. From this moment, the waypoint will be able to be visualised on the main map of the HEIMDALL platform as well as of the smartphone or tablet device.
Image 3-146. HEIMDALL app – Create waypoints.
When a HEIMDALL platform user sends a waypoint to a HEIMDALL app user (see 3.2.2.2 Add Marker (Waypoints)), the app user will be able to see it on the app map as a question mark icon (Image 3-147).
Image 3-147. HEIMDALL app – Received waypoint.
By clicking on the waypoint, the app user can send a response message to the platform user who has sent the waypoint (Image 3-148).
HEIMDALL [740689]
121
Image 3-148. HEIMDALL app – Reply window for received waypoints.
Once the response has been submitted, the app user will see the waypoint as a green tick icon (Image 3-149).
Image 3-149. HEIMDALL app – Replied waypoint.
Catalogue The communication and data sharing of the LUs (Local Units) is performed in HEIMDALL through a global catalogue that provides publication and subscription services. Users who won a given scenario can thus grant access to data and always keep an overview of who can access their data. The catalogue also enables the discovery of data and with this supports the connection to other authorities. The system tailors the data so that every user can access it in the preferred or mandatory format [5].
3.9.3.1 Catalogue publication
By clicking on in ““Active Incident Scenario”” menu (see Image 3-150) the user who has created the scenario can share the scenario data with other entities (e.g. LUs, users from specific countries, or users who hold specific roles and disciplines).
HEIMDALL [740689]
122
Image 3-150. Catalogue publication.
By default, when a given user creates a scenario only other users belonging to the same Local Unit (i.e. users from the same organisation) can access and edit it. Hence, when publishing the scenario data, the user can select those users that will be granted the rights to access the published data by filtering a set of specific user characteristics (Image 3-151).
HEIMDALL [740689]
123
Image 3-151. Catalogue – Publication menu.
1. Content URI: this is the URI to the content. This way a subscriber will be able to access contents using a direct link.
2. Countries: if selected, only users from specific countries can access the published data.
3. LUs: if selected, only specific Local Units can access the published data. Local Units can be specific organisations using the platform: e.g. Catalan Fire and Rescue Service, Catalan Police, Space Hellas, Scottish Fire and Rescue Service, Frederiksborg Fire and Rescue Service, Italian Red Cross.
4. Roles: if selected, only users holding specific roles can access the published data. One or more of the following roles can be selected: Control Room Operator, Field Unit, Fire Analyst Coordinator, Dispatcher Operator, Incident Commander, Police Department, Alarm Reception Centre, Fire Service.
5. Disciplines: if selected, only users of specific disciplines can access the published data. One or more of the following disciplines can be selected: Fire and Rescue Service, Local Police, Fire and Rescue Service – Command and Control, Medical Service, Fire and Rescue Service – Civil Protection.
3.9.3.2 Catalogue subscription
It is not until one scenario is published in the catalogue that users from other Local Units (i.e. other organisations) can access the shared content, provided they have been granted the rights to access it. Users can then subscribe and access data in the catalogue by clicking on
in the upper part of the main screen. Four options are available from the main Catalogue menu (see Image 3-152):
HEIMDALL [740689]
124
Image 3-152. Catalogue – Subscription menu.
1. My LU: general information about the LU where the user logged in (see Image 3-153).
Image 3-153. Catalogue – LU information.
2. All publications: subscribe to one or more scenario products that have been
published by a LU (Image 3-154). Every time that other users publish these products in the catalogue the user that is subscribed will receive a notification.
Image 3-154. Catalogue – Subscription to scenario products.
3. My publications: check the scenario products shared with other LUs (see Image 3-155). Information provided in this section includes access rules associated with
HEIMDALL [740689]
125
that product (i.e. users who access the published contents filtered by LU, country and role in the emergency) and the specific products that are being shared.
Image 3-155. Catalogue – Check your own publications.
4. My subscriptions: manage the existing subscriptions from the LU (see Image 3-156).
Image 3-156. Catalogue – Subscribed products.
Moreover, by clicking on the user can add new subscriptions to the catalogue filtering them by a specific product type:
• Scenario: includes all the scenario meta-data.
• EO: Earth Observation products.
• ISAS: Impact Summary Service products.
• IA: Impact Assessment products.
• Simulation: Simulation output products (see Image 3-157).
• SD: Sensor Data.
Specific information is required for each product subscription. As an example, Image 3-157 shows the information required for Earth Observation products.
HEIMDALL [740689]
126
Image 3-157. Catalogue – Subscription to EO products.
HEIMDALL [740689]
127
4 Conclusions
While by the end of the scope of the project the HEIMDALL platform has achieved a maturity such that emergency services can make use of it in an operational environment under controlled conditions, it is worth noting that it is still a prototype and as a such needs further development to be able to be used in real emergency scenarios. The present manual compiled all the modules that are currently implemented and ready for use, however some of the functionalities that integrate those modules are not fully finalised, whereas other still have room for improvement until the users can see some actual value in them. Furthermore, at the Graphical User Interface level, the platform can still improve the design towards a more user-friendly format for users to configure scenarios and leverage the features provided by the different platform services.
These are all requirements that have been identified by the project end-users based on the latest state of development of the platform and documented by the technical partners for future developments. Project deliverables D2.5 (HEIMDALL System Engineering Report - Issue 5) D2.10 (HEIMDALL Requirements Report - Issue 5) will report on long-term platform developments, thus paving the way for their operational applicability in real emergency scenarios.
Certainly, one of the strengths reflected on the HEIMDALL platform is that it has been designed on the grounds of a collaborative approach between technical partners and end-users, which draws on the experiences gathered during the former EU PHAROS Project, and fosters cooperative, interactive and iterative efforts between both parties, leading to the design and implementation of effective and accepted system capabilities. Hence, the tool that is presented in this document is the result of a testing and evaluation process undertaken by the project end-users on a regular basis during the frame of several end-user workshops, training sessions and other dedicated sessions, each coincident with different system releases. Because of this, from the onset of the project the platform has gone through an iterative and incremental improvement that has eventually achieved a remarkable gain in terms of usage, functionalities available and flexibility to accommodate further services for improved hazard risk knowledge and decision-making.
HEIMDALL [740689]
128
5 References
[1] Costa, P., Castellnou, M., Larrañaga, A., Miralles, M. and Daniel, P. (2011). Prevention of Large Wildfires Using the Fire Types Concept; Direccio General de Prevencio, Extincio D’incendis I Salvaments, Departament D’interior; Generalitat de Catalunya: Barcelona, Spain.
[2] Emergency Data Exchange Language (EDXL) Distribution Element Version 2.0. (2013). OASIS Committee Specification 02. http://docs.oasis-open.org/emergency/edxl-de/v2.0/cs02/edxl-de-v2.0-cs02.html.
[3] FIRE-IN EU project: “Common Capability Challenges Matrix”, available at: http://fire-in.eu/index.php/matrix-ccc/ [Last accessed: 08.2020].
[4] Guzzetti, F., Peruccacci, S., Rossi, M. and Stark, C. (2007) “Rainfall thresholds for the initiation of landslides in central and southern Europe”, Meteorology and Atmospheric Physics, vol. 98, no. 3–4, pp. 239–267.
[5] HEIMDALL Deliverable D4.14 Communications and Information Sharing – Specifications.
[6] HEIMDALL Deliverable D5.1 EO Tools and Products – Specifications.
[7] HEIMDALL Deliverable D5.2 EO Tools and Products – Specifications – Final.
[8] HEIMDALL Deliverable D5.5 Drone sensors and in-situ sensors.
[9] HEIMDALL Deliverable D5.12 Modelling and Simulation Services - Specifications.
[10] HEIMDALL Deliverable D6.1 Concept design for risk analysis methods and components – Detailed concept design and documentation of methods on risk analysis.
[11] HEIMDALL Deliverable D6.5 Technical Specifications on Hazard, Scale and User-Specific Risk Assessment Information, Products and Service Workflows – Final.
[12] HEIMDALL Deliverable D6.8 Situation Assessment, Impact Summary Generation and sCOP/SITREP Specification and Implementation Report – Final.
[13] Horton, P., Jaboyedoff, M., Rudaz, B. and Zimmermann, M. (2013) “Flow-R, a model for susceptibility mapping of debris flows and other gravitational hazards at a regional scale,” Natural Hazards and Earth System Science, vol. 13, no. 4, pp. 869–885.
[14] ICGC (2020) AP-0002-20. Guia per l’elaboració d’Estudis d’Identificació de Riscos Geològics per a urbanisme.
[15] Peel, M. C., Finlayson, B. L. and McMahon, T. A. (2007). Updated world map of the Köppen-Geiger climate classification.
[16] Ramírez, J. et al. (2011). “Wildfire Analyst: practical approach to operational wildfire simulation”, 5th Wildfire Conference, Sun City, South Africa.
[17] Reid, M., Christian, S., Brien, D. and Henderson, S. (2015). “Scoops3D- Software to Analyze Three-Dimensional Slope Stability Throughout a Digital Landscape”, US Geological Survey.
[18] U.S. Geological Survey (2015). Mineral commodity summaries 2015. USGS Unnumbered Series, Reston, VA (US), 196.
HEIMDALL [740689]
129
End of document
