<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing with OASIS Tables v3.0 20080202//EN" "journalpub-oasis3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:oasis="http://docs.oasis-open.org/ns/oasis-exchange/table" dtd-version="3.0">
  <front>
    <journal-meta>
<journal-id journal-id-type="publisher">NHESS</journal-id>
<journal-title-group>
<journal-title>Natural Hazards and Earth System Sciences</journal-title>
<abbrev-journal-title abbrev-type="publisher">NHESS</abbrev-journal-title>
<abbrev-journal-title abbrev-type="nlm-ta">Nat. Hazards Earth Syst. Sci.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">1684-9981</issn>
<publisher><publisher-name>Copernicus Publications</publisher-name>
<publisher-loc>Göttingen, Germany</publisher-loc>
</publisher>
</journal-meta>

    <article-meta>
      <article-id pub-id-type="doi">10.5194/nhess-17-481-2017</article-id><title-group><article-title>Assessing the risk posed by natural hazards to infrastructures</article-title>
      </title-group><?xmltex \runningtitle{Assessing the risk posed by natural hazards to infrastructures}?><?xmltex \runningauthor{U.~M.~K.~Eidsvig et al.}?>
      <contrib-group>
        <contrib contrib-type="author" corresp="yes" rid="aff1">
          <name><surname>Eidsvig</surname><given-names>Unni Marie K.</given-names></name>
          <email>unni.eidsvig@ngi.no</email>
        </contrib>
        <contrib contrib-type="author" corresp="no" rid="aff1">
          <name><surname>Kristensen</surname><given-names>Krister</given-names></name>
          
        </contrib>
        <contrib contrib-type="author" corresp="no" rid="aff1">
          <name><surname>Vangelsten</surname><given-names>Bjørn Vidar</given-names></name>
          
        </contrib>
        <aff id="aff1"><institution>NGI, Natural hazards division, Oslo, Norway</institution>
        </aff>
      </contrib-group>
      <author-notes><corresp id="corr1">Unni Marie K. Eidsvig (unni.eidsvig@ngi.no)</corresp></author-notes><pub-date><day>24</day><month>March</month><year>2017</year></pub-date>
      
      <volume>17</volume>
      <issue>3</issue>
      <fpage>481</fpage><lpage>504</lpage>
      <history>
        <date date-type="received"><day>18</day><month>March</month><year>2016</year></date>
           <date date-type="rev-request"><day>11</day><month>April</month><year>2016</year></date>
           <date date-type="rev-recd"><day>31</day><month>January</month><year>2017</year></date>
           <date date-type="accepted"><day>24</day><month>February</month><year>2017</year></date>
      </history>
      <permissions>
<license license-type="open-access">
<license-p>This work is licensed under a Creative Commons Attribution 3.0 Unported License. To view a copy of this license, visit <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</ext-link></license-p>
</license>
</permissions><self-uri xlink:href="https://nhess.copernicus.org/articles/.html">This article is available from https://nhess.copernicus.org/articles/.html</self-uri>
<self-uri xlink:href="https://nhess.copernicus.org/articles/.pdf">The full text article is available as a PDF file from https://nhess.copernicus.org/articles/.pdf</self-uri>


      <abstract>
    <p>This paper proposes a model for assessing the risk posed
by natural hazards to infrastructures, with a focus on the indirect losses and
loss of stability for the population relying on the infrastructure. The
model prescribes a three-level analysis with increasing level of detail,
moving from qualitative to quantitative analysis. The focus is on a
methodology for semi-quantitative analyses to be performed at the second
level. The purpose of this type of analysis is to perform a screening of the
scenarios of natural hazards threatening the infrastructures, identifying
the most critical scenarios and investigating the need for further analyses
(third level). The proposed semi-quantitative methodology considers the
frequency of the natural hazard, different aspects of vulnerability,
including the physical vulnerability of the infrastructure itself, and the
societal dependency on the infrastructure. An indicator-based approach is
applied, ranking the indicators on a relative scale according to pre-defined
ranking criteria. The proposed indicators, which characterise conditions
that influence the probability of an infrastructure malfunctioning caused by
a natural event, are defined as (1) robustness and buffer capacity, (2) level
of protection, (3) quality/level of maintenance and renewal, (4) adaptability
and quality of operational procedures and (5) transparency/complexity/degree
of coupling. Further indicators describe conditions influencing the
socio-economic consequences of the infrastructure malfunctioning, such as
(1) redundancy and/or substitution, (2) cascading effects and dependencies,
(3) preparedness and (4) early warning, emergency response and measures. The
aggregated risk estimate is a combination of the semi-quantitative
vulnerability indicators, as well as quantitative estimates of the frequency
of the natural hazard, the potential duration of the infrastructure
malfunctioning (e.g. depending on the required restoration effort) and the
number of users of the infrastructure.</p>
    <p>Case studies for two Norwegian municipalities are presented for
demonstration purposes, where risk posed by adverse weather and natural
hazards to primary road, water supply and power networks is assessed. The
application examples show that the proposed model provides a useful tool for
screening of potential undesirable events, contributing to a targeted
reduction of the risk.</p>
  </abstract>
    </article-meta>
  </front>
<body>
      

<sec id="Ch1.S1" sec-type="intro">
  <title>Introduction</title>
      <p>Modern society is increasingly dependent on infrastructures to maintain
critical societal functions such as supply of food, water and energy, and
security. Disruptions in one of the infrastructure systems, such as water
and energy supply, transport or communication, may have severe consequences.
With a changing climate, the frequency and intensity of some extreme weather
events (e.g. intense precipitation) and related hazards (e.g. landslides and
floods) are expected to increase (Hanssen-Bauer et al., 2015), creating
challenges for the infrastructure providers. Challenges include, for example,
landslides threatening transportation lines, increased contamination of
water sources due to intense rain and flooding or storms leading to loss of power supply.</p>
      <p>Since the financial and workforce resources available to operators to
protect their infrastructure systems are limited, it is especially important
to use resources efficiently. To do so, it is essential to be aware of the
threats and risks and to assess and compare risk in order to set priorities.
This will be the basis for implementing targeted protection measures, as
stated by the Federal Ministry of the Interior (2008).</p>
      <p>The main purpose of performing risk assessment related to infrastructure
affected by natural events is to support well-founded risk management. An
extensive risk assessment is indispensable in order to identify adverse
events and vulnerabilities and evaluate the impact on infrastructures and their
users, taking into account the probability of the occurrence of these
adverse events. The risk assessment gives decision makers a better
understanding of risks and its uncertainties, describing and comparing the
vulnerability and resilience and potential risks related to the effects on
infrastructures from natural events. Careful assessment of risk and informed
analysis of dependencies between infrastructures can significantly
contribute to effective investment in planning and design and facilitate
preparedness actions in the event of failure. With regard to risk reduction,
discussion about acceptable levels of risk and of potential mitigation
measures to reduce the risk is required. Cost–benefit analyses could be used
to assess the feasibility and adequacy of mitigation measures. Optimal decisions
require that decision makers are aware of how their decisions may affect the expected loss.</p>
      <p>By law, the Norwegian municipalities are required to carry out a risk and
vulnerability analysis and plan and prepare for emergencies from a short- and
long-term perspective. The purpose of the duty/legislation is to ensure
that the municipalities are working holistically and systematically with
societal safety and preparedness across sectors in the municipality.
Knowledge about risk and vulnerability is important to reduce the
probability of undesirable events and to reduce the consequences should the
event occur (DSB, 2015a). The current format of the municipal risk and
vulnerability assessments is very similar to a preliminary hazard analysis
(PHA; IEC/FDIS 31010, 2009), where the starting point is the identification
of adverse events, followed by a simple probability and consequence
assessment of each event. In the municipal analysis, adverse events refer to
events in the municipality that may result in loss of life, health or
stability, monetary losses or damage to the environment. Through the
municipal involvement in the implementation of the risk and vulnerability
analysis, the stakeholders in the municipality obtain a better overview
over, and an increased consciousness about, the relevant risks and
vulnerabilities. In addition, the municipality can acquire knowledge about
how risks and vulnerabilities can be managed. The analysis is intended to
form a basis for an overall emergency plan that must be coordinated with
other relevant emergency and contingency plans. The ultimate goal of the
analyses is to help maintain important socio-economic functions and
safeguard citizens' lives, health and basic needs under various forms of
stress. This goal is further specified by defining four societal values with
corresponding consequence types as shown in Table 1. Vulnerability analysis
of the infrastructures and their interdependencies is an essential part of
the municipal risk and vulnerability analysis for the societal value named
stability, i.e. referring to consequences such as lack of basic
provisions and disruptions in daily life.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T1"><caption><p>Safety of the population specified through socio-economic values and
corresponding consequence types (DSB, 2014).</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="2">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:thead>
       <oasis:row rowsep="1">  
         <oasis:entry namest="col1" nameend="col2" align="center">Safety of the population </oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Socio-economic value</oasis:entry>  
         <oasis:entry colname="col2">Consequence type</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Life and health</oasis:entry>  
         <oasis:entry colname="col2">Fatalities,</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">injuries and diseases</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Stability</oasis:entry>  
         <oasis:entry colname="col2">Lack of basic provisions and</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">disruptions in daily life</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Nature and environment</oasis:entry>  
         <oasis:entry colname="col2">Long-term damage to the natural</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">environment</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Material assets</oasis:entry>  
         <oasis:entry colname="col2">Monetary losses</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

<sec id="Ch1.S1.SSx1" specific-use="unnumbered">
  <title>Terminology</title>
      <p>The terminology used in this paper is according to the definitions listed
below. The definitions are adapted from DSB (2014), Birkmann et al. (2013),
the National Academy of Sciences (2012), ISSMGE (2004) and Corominas et al. (2014).
<list list-type="bullet"><list-item><p><italic>Adverse event</italic>: an event that may result in loss of life, health or
stability, monetary losses or damage to the environment, DSB (2014). In this
paper the focus is on adverse events in terms of malfunctioning of
infrastructure (caused by natural events).</p></list-item><list-item><p><italic>Consequence</italic>: the outcomes or potential outcomes arising from the
occurrence of an adverse event, expressed qualitatively
in terms of loss, disadvantage or gain; or quantitatively in terms of damage, injury or
loss of life, adapted from Corominas et al. (2014).
Vulnerability is an
important component of the consequence. Consequences could be
characterized as direct and indirect. Direct consequences refer to the
physical destruction of exposed elements, and indirect consequences refer to
the consequences of that destruction, adapted from the Committee on Assessing
the Costs of Natural Disasters (1999). In this paper the focus is on the
indirect consequences/indirect losses.</p></list-item><list-item><p><italic>Exposed elements</italic>: population, buildings and engineering works,
infrastructure, environmental features and economic activities in the area
affected by the adverse event (ISSMGE, 2004).</p></list-item><list-item><p><italic>Resilience</italic>: the ability to prepare and plan for, absorb, recover
from or more-successfully adapt to actual or potential adverse events
(National Academy of Sciences, 2012).</p></list-item><list-item><p><italic>Risk</italic>: measure of the probability and severity of an adverse effect
to life, health, property, economic activities or the environment.
Quantitatively, risk <inline-formula><mml:math id="M1" display="inline"><mml:mo>=</mml:mo></mml:math></inline-formula> hazard <inline-formula><mml:math id="M2" display="inline"><mml:mo>⋅</mml:mo></mml:math></inline-formula> potential worth of loss. This
can be also expressed as the “probability of an adverse event times the
consequences if the event occurs” (ISSMGE, 2004).</p></list-item><list-item><p><italic>Vulnerability</italic>: vulnerability refers to the propensity of exposed
elements such as physical or capital assets, as well as human beings and
their livelihoods, to experience harm and suffer damage and loss when
impacted by single or compound hazard events (Birkmann et al., 2013).</p></list-item></list>
Dimensions of vulnerability, adapted from Birkmann et al. (2013), are as
follows.
<list list-type="bullet"><list-item><p><italic>Physical dimension</italic> refers to conditions of physical assets – including
built-up areas, infrastructure and open spaces that can be affected by natural
hazards.</p></list-item><list-item><p><italic>Social dimension</italic> refers to human welfare, including social integration,
mental and physical health, both at an individual and collective level.</p></list-item><list-item><p><italic>Economic dimension</italic> refers to the productive capacity, unemployment
and low-income conditions.</p></list-item><list-item><p><italic>Physical vulnerability indicators</italic> refer to properties
or characteristics of the infrastructure affecting the probability of malfunctioning
(here, due to the occurrence of a natural event).</p></list-item><list-item><p><italic>socio-economic vulnerability indicators</italic> refer to factors for human
welfare and the productive capacity of the society in relation to the malfunctioning
of the infrastructure.</p></list-item></list></p>
</sec>
</sec>
<sec id="Ch1.S2">
  <title>State-of-the-art assessment of infrastructure vulnerability and risk</title>
<sec id="Ch1.S2.SS1">
  <title>Overview and gaps</title>
      <p>Infrastructures have some basic traits in common, such as large size,
wide-area coverage, complexity and interconnectedness, but show significant
differences in detail. Methods for vulnerability assessment vary with the
type of system, the objective of the analysis, the analysis steps and the
available information. No all-encompassing method exists, but rather an
interplay of methods is necessary to provide trustworthy information about
vulnerabilities within and among infrastructures, including the effect of
(inter)dependencies (Kröger and Zio, 2011). Methods used for
vulnerability and risk assessment of infrastructure include susceptibility
functions, economic theory-based approaches, probabilistic modelling,
statistical analyses of past events, empirical approaches, risk analysis of
technological systems, network-based approaches, agent-based approaches,
system dynamics-based approaches, relational databases and use of
vulnerability and risk indices (Yusta et al., 2011; Kröger and Zio, 2011;
Ouyang, 2014). Meyer et al. (2013) give a broad review of the assessment of
costs of natural hazards affecting infrastructure (considering both direct
and indirect costs). There are several ways to classify levels and scopes
for assessment of infrastructure. Bouchon (2006) divides this into three
levels: (i) the level of the infrastructure itself (which could further be
subdivided into component level and network level), (ii) the level of the
interdependent infrastructures and (iii) the level of dependent territorial,
socio-economic, politically dependent sub-systems. Similarly, Giannopoulos et
al. (2012) distinguish between sectorial level, when each sector is treated
separately and system approaches that assess the infrastructures as an
interconnected network and use a system of systems topology. Yusta et al. (2011)
refer to two different scopes of modelling infrastructure
vulnerability and risk, namely methods and tools to describe the current
state of the infrastructure and methodologies and tools that focus on the
understanding of the dynamic behaviour of the infrastructure systems, which is
based on simulation techniques. The first scope focuses on the study,
analysis and understanding of the infrastructure from the earliest stages of
construction and assembly. This scope identifies methods, techniques, tools
and charts to describe the current state of the infrastructure, and it uses
methods of evaluating the threat to obtain a clearer view on the operation
of infrastructure. For this, it takes into account each of the possible
risks that affect a system and determines their possible consequences. It
should be noted that although many of the potential causes of hazards can be
detected with this approach, their consequences or impacts are not
necessarily perceived or understood. In resilience models for assessing
the interaction between hazard and engineered systems, the properties of
infrastructure, like robustness, redundancy, resourcefulness, and rapidity,
reduce the probability of failures in the systems (Cutter et al., 2008).
Solano (2010) reviews and evaluates methodologies to assess vulnerabilities
of infrastructures across a number of characteristics.</p>
      <p>The second scope focuses on understanding the dynamic behaviour of the
infrastructure systems and uses simulation techniques (systems dynamics,
Monte Carlo simulation, multi-agent systems, etc.) with which it explores
both processes and operation in order to identify the causes of instability
in a system infrastructure. Rinaldi et al. (2001) provide an overview of how
to identify, understand and analyse interdependencies between
infrastructures. To provide a detailed description and modelling of
interdependent infrastructures, many relevant data are required and often
are inaccessible due to, for example, confidentiality and privacy issues and a reluctance
to share data (Ouyang, 2014). In many cases, the risk assessment
methodologies for infrastructures are an adaptation of methodologies that
have been used for assessing risks within an organization. As a consequence,
these methodologies are tailored to the particular needs of this
organization and biased to consider only part of relevant threats.
Giannopoulos et al. (2012) have identified two main commonly used approaches
for the assessment of sectors for a variety of hazards: aggregated impact,
where the impact of infrastructure disruption is expressed in terms of
aggregated figures that account for the economic losses, and indicator-based
scoring approaches, which resemble a multi-criteria decision analysis in the
sense that the final score produced is the weighted mean of several scores.</p>
      <p>In the following, special attention is given to methods that apply
vulnerability and risk indices or identify factors relevant for
vulnerability and risk for infrastructures affected by adverse weather and
natural hazards, in particular those of the Federal Ministry of the Interior (2008),
Lenz (2009), Merz et al. (2010), Vatn et al. (2009) and Kröger (2008). The
Federal Ministry of the Interior (2008) provides guidelines for operators of
critical infrastructures, providing a management strategy to identify risks,
implement preventive measures and handle crises effectively. Lenz (2009)
provides a detailed overview of the vulnerability of critical
infrastructures, distinguishing between indicators relevant for
vulnerability of critical infrastructure and for coping capacity. Merz et
al. (2010) go through various aspects of the assessments of economic flood
damage. Vatn et al. (2009) has developed a methodology that identifies
adverse events as well as risk and vulnerability factors which may affect
the likelihood and consequences of undesirable events. Kröger (2008)
discusses the most significant factors related to the risks faced by
critical infrastructures. These include societal, system-related,
technological, institutional and natural factors, with a special focus on
issues associated with the increasing interdependence between
infrastructures. Even if these methods identify vulnerability indicators,
they do not contain explicit procedures for estimation of risk levels based
on the indicators, lacking either schemes for ranking or aggregation of the
indicators or for the relation between risk levels and vulnerability indicators.</p>
</sec>
<sec id="Ch1.S2.SS2">
  <title>Scope of study</title>
      <p>To utilise resources efficiently, the risk assessment is performed at
different levels of detail, starting with a coarse analysis to decide for
which areas or scenarios further analyses are necessary and subsequently
increase the degree of detail and limit the scope to the most critical
scenarios or areas. The coarsest analyses include methods like structured
interview and brainstorming, checklists, preliminary hazard analysis, hazard
and operability study (HAZOP), What If Technique (SWIFT) and scenario
analysis (IEC/FDIS 31010, 2009). In these methods, subjective assessments and
considerable use of expert judgment are necessary. For such analyses, both
diversity and depth of expertise are essential to ensure satisfactory quality
and consistency of the analysis results, avoiding too-coarse assessments or
overlooking important events. On the other hand, detailed quantitative
analyses for the assessment of the interdependent infrastructures and
society depending on the infrastructures, e.g. simulation techniques
or economic theory approaches, are often too complex and time consuming to be
applied as a tool to identify the most critical risk scenarios. An
alternative tool for screening the potential scenarios in a systematic,
transparent and repeatable way could bridge this gap. This paper proposes an
explicit methodology for such screenings, with the purpose of comparing
scenarios and providing an overview of the risks associated with each of the
identified scenarios. The application of the method within the municipal
risk and vulnerability analysis in Norway will be described in the next section.</p>
      <p>The aim of the work presented in this paper is to propose a comprehensive
and user-friendly method for identification and assessment of natural events
leading to the malfunctioning of infrastructure. The method is designed to be
consistent with, and a supplement to, the guidelines for municipal risk and
vulnerability analysis in Norway, provided by the Norwegian Directorate for
Civil Protection, DSB (2014). According to these guidelines, the analysis
consists of the following stages:
<list list-type="order"><list-item><p>identifying adverse events (considering threats within or outside the
municipality, but with consequences for the municipality),</p></list-item><list-item><p>assessing risk and vulnerability of adverse events,</p></list-item><list-item><p>providing an overview of the risks associated with each of the identified
adverse events (stage 1 above),</p></list-item><list-item><p>following-up and</p></list-item><list-item><p>reporting.</p></list-item></list>
The explicit method proposed in this paper targets the second and third
stages in the municipal risk and vulnerability analyses: assessing risk and
vulnerability of adverse events and providing an overview of the risks
associated with each of the identified adverse events in the municipality.
The proposed method is used to give a coarse overview of the risks used for
preliminary sorting of the adverse events. A more-detailed analysis of the
events is used as basis for decisions regarding risk acceptance, follow-up
and mitigation. We
chose not to include explicit criteria or risk
thresholds for recommendations regarding the follow-up, both because each
municipality must adapt the criteria for follow-up to their own situation
and capacity (scenarios with the highest risk must be prioritised regardless
of risk acceptance), and because the method is a coarse analysis where the
scale is relative and difficult to link to quantitative risk acceptance criteria.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F1" specific-use="star"><caption><p>Schematic representation of the scope. Factors that affect the
probability of the adverse event (malfunctioning of infrastructure) are shown
on the left side (i.e. causes, barriers and physical vulnerability of the
infrastructure). Factors that affect the socio-economic consequences of the
adverse event are shown on the right side.</p></caption>
          <?xmltex \igopts{width=284.527559pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/17/481/2017/nhess-17-481-2017-f01.pdf"/>

        </fig>

      <p>The proposed method is applicable to the main infrastructures (electricity
supply, water supply, transportation, and information and communications
technology, ICT) and to provide support for analysis of threats from
natural events, for planning and preparedness, and for prioritisation of risk-reduction
measures. The focus will be on the infrastructures of electricity
supply, water supply and transportation. They share a number of similarities
such as large size, wide-area coverage, complexity and interconnectedness.</p>
      <p>Strategies for risk reduction fall into two categories: those that minimise
the probability of infrastructure malfunctioning, and those that minimise
the negative effects of a malfunctioning (IRGC, 2007). The proposed method
takes into account the vulnerabilities of infrastructure and barriers that
affect the probability of infrastructure malfunctioning. It also considers
factors affecting the socio-economic consequences of malfunctioning of the
infrastructure. The scope is schematically illustrated in Fig. 1, using
and demonstrating terminology defined in the following.</p>
      <p>Figure 1 shows a cause and effect diagram with causes of the infrastructure
malfunctioning, influenced by the physical vulnerability of the
infrastructure to the natural event on the left side, and consequences of
this malfunctioning, influenced by the socio-economic vulnerability on the
right side. Malfunctioning of infrastructure refers to an interruption
(partly or fully) of the services provided by the infrastructure. The
scenarios could be controlled using barriers which could prevent causes of
malfunctioning of the infrastructure and barriers for mitigation and
recovery controls, i.e. barriers that limit the consequences of the
malfunctioning. Barriers could be physical or organisational, including human behaviour.</p>
      <p>The indicators identified as the most important for the scope of this paper
are based on generic indicators from the literature, as described in Sect. 2.1.
The indicators were thought to be relevant for assessing the exposure and
vulnerability levels and for the resulting risk level (Institute of
Operational Risk, 2010). They should be measurable, at least on a relative
scale, in order to enable comparison between different times or different
study areas. The ranking of the indicators should be based on data available
to the stakeholders or on the local knowledge of the stakeholder. The selected
indicators are summarised below.
<list list-type="bullet"><list-item><p><italic>Dependencies</italic>: dependencies of other infrastructures, specific
personnel and specific environmental conditions makes the infrastructure
more vulnerable (Federal Ministry of the Interior, 2008; Vatn et al., 2009;
Lenz, 2009; Kröger, 2008).</p></list-item><list-item><p><italic>Robustness</italic>: the physical robustness of risk elements (in particular
facilities, equipment, buildings) is an important factor determining damage
levels caused by an extreme event (Federal Ministry of the Interior, 2008;
Lenz, 2009).</p></list-item><list-item><p><italic>Buffer capacity</italic>: buffer capacity means that the systems impacted by
an event have redundancy or auxiliary capacity to sustain service to a
certain degree and for a certain time (Federal Ministry of the Interior, 2008; Lenz, 2009).</p></list-item><list-item><p><italic>Level of protection</italic>: robustness/strength of barriers protecting an
exposed element (i.e. a structure or a lifeline) from a threat
(Federal Ministry of the Interior, 2008; Lenz, 2009).</p></list-item><list-item><p><italic>Quality level/level of maintenance and renewal</italic>: to ensure
appropriate quality of the infrastructure, it needs to be maintained and
renewed systematically (Lenz, 2009; Vatn et al., 2009).</p></list-item><list-item><p><italic>Adaptability</italic>: ability to adapt to changing framework conditions
makes the infrastructure less vulnerable (Federal Ministry of the Interior, 2008).</p></list-item><list-item><p><italic>Quality in operational procedures</italic>: the vulnerability of the
infrastructure depends on how well it is operated (Vatn et al., 2009; Kröger, 2008).</p></list-item><list-item><p><italic>Transparency/complexity/degree of coupling</italic>: the complexity of the
infrastructure and its dependency on single components to work, contributes
to a higher vulnerability (Perrow, 1984; Federal Ministry of the Interior,
2008; Vatn et al., 2009; Kröger, 2008).</p></list-item><list-item><p><italic>Redundancy/substitutes</italic>: if there is an outage or reduced capacity
in the infrastructure, it is easier to handle if there are back-ups or
substitutes for the infrastructure (Federal Ministry of the Interior, 2008;
Vatn et al., 2009; Lenz, 2009).</p></list-item><list-item><p><italic>Restoration effort/duration</italic>: restoration effort refers to the
effort needed to restore a damaged element including monetary costs as well
as time and staff resources needed (Federal Ministry of the Interior, 2008;
Vatn et al., 2009; Lenz, 2009).</p></list-item><list-item><p><italic>Preparedness</italic>: an outage of an infrastructure is easier and more-quickly restored or better handled if the situation has been prepared for
(Lenz, 2009; Vatn et al., 2009; Merz et al., 2010).</p></list-item><list-item><p><italic>Early warning, emergency response and measures</italic>: if the warning time
is sufficiently long, an early warning system combined with emergency
response and measures may reduce the consequences of an infrastructure
outage (Merz et al., 2010).</p></list-item><list-item><p><italic>Cascading effects and dependencies</italic>: the definition and content of
the term cascading effects are discussed by Pescaroli and Alexander (2015)
and, in short, referred to as a “chain sequence of interconnected failures” or
as second-order/higher-order effects (Rinaldi et al., 2001). Cascading
effects and dependencies of other societal functions on the infrastructure
increase the societal consequences of the infrastructure loss (Vatn et al., 2009
Federal Ministry of the Interior, 2008; Lenz, 2009).</p></list-item></list></p>
</sec>
</sec>
<sec id="Ch1.S3">
  <title>Methodology</title>
      <p>The method presented in this paper covers Level 2 of a three-level analysis
for risk identification and risk assessment, with an increasing degree of
detailing and quantification.
<list list-type="bullet"><list-item><p>Level 1: qualitative, i.e. risk identification.</p></list-item><list-item><p>Level 2: semi-quantitative analysis to rank the risk, i.e. screening of the
scenarios of natural events threatening the infrastructures (identified in
the level 1 analysis), in which the scenarios with potential highest risk are
identified.</p></list-item><list-item><p>Level 3: quantitative analysis, i.e. detailed analysis of the scenarios
identified in the level 2 analysis.</p></list-item></list>
The second level consists of a semi-quantitative ranking of the risk and is
a mixture of a quantitative approach and an indicator-based approach. The
quantitative part of the approach is anchored in the probability and
consequence categories suggested by DSB (2014) (Tables 1 and 2). As
illustrated in Fig. 1, the risk is governed by causal factors, influencing
the likelihood of the malfunctioning of the infrastructure, as well as
factors relevant for the socio-economic consequences of the malfunctioning
infrastructure. The indicators are grouped into physical vulnerabilities and
socio-economic vulnerabilities accordingly. The indicators chosen for the
assessment of the physical vulnerability (including barriers reducing the
probability of the malfunctioning of the infrastructure) applied in this method are
<list list-type="bullet"><list-item><p>robustness and buffer capacity,</p></list-item><list-item><p>level of protection,</p></list-item><list-item><p>quality level/age/level of maintenance and renewal,</p></list-item><list-item><p>adaptability and quality in operational procedures, and</p></list-item><list-item><p>transparency/complexity/degree of coupling.</p></list-item></list></p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T2"><caption><p>Categorisation of the probability: application of the annual probability
of the natural event as an initial categorisation of the top event, simplified
from the guidelines from the Norwegian Directorate for Civil Protection
(DSB, 2014). Each category is described both with the frequency and the annual
probability of the natural event.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.93}[.93]?><oasis:tgroup cols="3">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Category</oasis:entry>  
         <oasis:entry colname="col2">Frequency of the natural event</oasis:entry>  
         <oasis:entry colname="col3">Annual probability</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">of the natural</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">event</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">E</oasis:entry>  
         <oasis:entry colname="col2">Higher than once every 10th year</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math id="M3" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 10 %</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">D</oasis:entry>  
         <oasis:entry colname="col2">Once per 10–50 years</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math id="M4" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 2, <inline-formula><mml:math id="M5" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 10 %</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">C</oasis:entry>  
         <oasis:entry colname="col2">Once per 50–100 years</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math id="M6" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 1, <inline-formula><mml:math id="M7" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 2 %</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">B</oasis:entry>  
         <oasis:entry colname="col2">Once per 100–1000 years</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math id="M8" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 0.1, <inline-formula><mml:math id="M9" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 1 %</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">A</oasis:entry>  
         <oasis:entry colname="col2">Lower than once per 1000 years</oasis:entry>  
         <oasis:entry colname="col3"><inline-formula><mml:math id="M10" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 0.1 %</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

      <?xmltex \floatpos{t}?><fig id="Ch1.F2" specific-use="star"><caption><p>Illustration of the method for semi-quantitative analyses. The
indicators with dotted frames are assessed quantitatively for an initial
categorisation of the probability and consequence (Step 1). The physical and
socio-economic vulnerability indicators (dash–dot frames) are assessed
semi-quantitatively (Step 2). The information from the first two steps is
aggregated in the third step to assess the probability of infrastructure
malfunctioning and the severity of the consequences.</p></caption>
        <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/17/481/2017/nhess-17-481-2017-f02.pdf"/>

      </fig>

      <p><?xmltex \hack{\noindent}?>The chosen indicators reflect different aspects of vulnerability of
infrastructures. The number of indicators was reduced compared to the
indicators listed in the Sect. 2.2: robustness and buffer capacity were
combined since they are closely related, but with the difference being that
buffer capacity also deals with the temporal aspect. Furthermore,
adaptability and quality of operational procedures were merged into one
indicator. Adaptability is related both to the adaptations that are
physically possible and to the quality and timing of the practical
implementation of adaptation. Adaptability therefore also depends on how the
infrastructure is operated. Grothmann et al. (2013) discuss and compare
frameworks for adaptive capacity for institutions. The indicators for the
dependencies on external factors for the infrastructure to work would
typically also be among the physical vulnerability indicators. These are,
however, omitted here, as they are considered less relevant for loss of
infrastructure caused directly by natural events and thus outside the scope
of this method. The method does not consider infrastructure malfunctioning
caused by loss of other infrastructures or by lack of resources.
Infrastructure owners/operators would look to improve values for the
physical vulnerability indicators to ensure that their infrastructure is
physically robust, can tolerate the effects of the natural event for a certain
time without being affected, is sufficiently protected against the natural
event, fulfils high quality requirements (i.e. is new or well maintained),
has the ability to adapt to changing framework conditions, is well operated and
is not dependent on single components to work.</p>
      <p>The chosen indicators for the socio-economic vulnerability in this study
include the following:
<list list-type="bullet"><list-item><p>redundancy/substitutes of the infrastructure in the study;</p></list-item><list-item><p>cascading effects and dependencies;</p></list-item><list-item><p>preparedness;</p></list-item><list-item><p>early warning, emergency response and measures.</p></list-item></list>
The duration of the infrastructure malfunction is included quantitatively in
the consequence assessment (see Fig. 2 and Table 3). Thus, the indicator
restoration effort/duration is omitted here to avoid double counting. Risk
managers could look to optimise the values of the socio-economic
vulnerability indicators (as listed above) by ensuring that there are
back-ups or substitutes to the infrastructure that could provide the same
service, that there are minimum dependencies of other societal functions on the
infrastructure, that the malfunctioning of the infrastructure has been prepared
for and that there is an early warning system combined with an emergency response
and measures to mitigate the consequences.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T3"><caption><p>Initial categorisation of consequence based on the number of
infrastructure users and duration of the outage, simplified from the guidelines
from the Norwegian Directorate for Civil Protection; DSB (2014). The consequence
categories are indicative and should be adapted to the municipality's size,
i.e. in terms of number of inhabitants.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.95}[.95]?><oasis:tgroup cols="5">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Number of</oasis:entry>  
         <oasis:entry colname="col2"><inline-formula><mml:math id="M11" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 50</oasis:entry>  
         <oasis:entry colname="col3">50–199</oasis:entry>  
         <oasis:entry colname="col4">200–999</oasis:entry>  
         <oasis:entry colname="col5"><inline-formula><mml:math id="M12" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 1000</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">infrastructure users/</oasis:entry>  
         <oasis:entry colname="col2">persons</oasis:entry>  
         <oasis:entry colname="col3">persons</oasis:entry>  
         <oasis:entry colname="col4">persons</oasis:entry>  
         <oasis:entry colname="col5">persons</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">duration of the</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">outage/infrastructure</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">loss</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math id="M13" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 7 days</oasis:entry>  
         <oasis:entry colname="col2">3</oasis:entry>  
         <oasis:entry colname="col3">4</oasis:entry>  
         <oasis:entry colname="col4">5</oasis:entry>  
         <oasis:entry colname="col5">5</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math id="M14" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 2 days, <inline-formula><mml:math id="M15" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 7 days</oasis:entry>  
         <oasis:entry colname="col2">2</oasis:entry>  
         <oasis:entry colname="col3">3</oasis:entry>  
         <oasis:entry colname="col4">4</oasis:entry>  
         <oasis:entry colname="col5">5</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math id="M16" display="inline"><mml:mo>≥</mml:mo></mml:math></inline-formula> 1 day, <inline-formula><mml:math id="M17" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 2 days</oasis:entry>  
         <oasis:entry colname="col2">1</oasis:entry>  
         <oasis:entry colname="col3">2</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">4</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"><inline-formula><mml:math id="M18" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 1 day</oasis:entry>  
         <oasis:entry colname="col2">1</oasis:entry>  
         <oasis:entry colname="col3">1</oasis:entry>  
         <oasis:entry colname="col4">2</oasis:entry>  
         <oasis:entry colname="col5">3</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

      <p>Figure 2 shows that risk could be decomposed into the probability of an adverse
event and the consequences if the event occurs, as in traditional risk assessment
approaches and in accordance with the definitions in the terminology section. However,
here,
the adverse event is not the natural event itself, in contrast to what is
usual within natural science, but rather the malfunctioning of infrastructure
caused by a natural event. The methodology presented in this paper is
adapted to be in accordance with the guidelines of the Norwegian Directorate
for Civil protection (DSB, 2014). In these guidelines, the addressed
probability is the probability of an adverse event involving, for example, a natural
event causing material destruction, i.e. not the probability of the natural
event itself. Similar subdivisions are found in DSB (2014), Lenz (2009),
IRGC (2007), and the Committee on Assessing the Costs of Natural Disasters
(1999): “It is useful to distinguish between the physical
destruction caused by natural disasters to human beings and property and
the consequences of that destruction”. The consequences referred to
are indirect consequences in terms of the societal value “stability”.</p>
      <p>Figure 2 illustrates the content of the explicit proposed method for
semi-quantitative risk assessment. The next subsection presents a more-detailed description of the analysis steps of that method.</p>
<sec id="Ch1.S3.SS1">
  <title>Methodology for semi-quantitative risk assessment (level 2 analysis)</title>
      <p>The method proposes to perform the semi-quantitative risk assessment in
three steps (Fig. 2) outlined in the following.
<list list-type="bullet"><list-item><p>Step 1: initial categorisation of the probability and consequence of the top
event (natural hazards causing malfunctioning of the infrastructure).</p></list-item><list-item><p>Step 2: vulnerability assessment, i.e. the ranking of the vulnerability
indicators and
estimation of the physical and socio-economic vulnerability scores.</p></list-item><list-item><p>Step 3: final categorisation of probability and consequence, based on the
initial categorisation and results from the vulnerability assessment.</p></list-item></list></p>
<sec id="Ch1.S3.SS1.SSS1">
  <title>Step 1: initial categorisation of probability and consequence of the top event (natural hazards causing malfunctioning of the infrastructure)</title>
      <p>In the initial probability classification, the analyst needs to assign the
probability of the natural event into one of five quantitatively defined
probability categories. The categories range from an annual probability
lower than 0.1 % (probability category A) to an annual probability higher
than 10 % (probability category E). Table 2 shows the scheme for the
categorisation into categories A–E. These probability categories
correspond to the categories suggested in DSB (2014).</p>
      <p>In the initial consequence categorisation, the analyst needs to assign the
consequences into one of five consequence categories. In this step, the
consequences are determined by the combination of duration of the
infrastructure malfunctioning and the number of users served by the
infrastructure. The lowest consequence category (consequence category 1)
corresponds to relatively few users combined with short duration, while the
highest consequence category (consequence category 5) corresponds to
a relatively high number of users combined with a long malfunction duration. The boundary of the categories of users and duration are
defined such that the number of person days (i.e. the product of persons and
days) increases exponentially with the consequence categories. Table 3 shows
the scheme for the categorisation of consequence into consequence categories 1–5.</p><?xmltex \hack{\newpage}?>
</sec>
<sec id="Ch1.S3.SS1.SSS2">
  <title>Step 2: vulnerability assessment, i.e. the ranking of the vulnerability indicators, estimation of the physical and socio-economic vulnerability scores</title>
      <p>The vulnerability assessment is performed using an indicator-based approach.
This type of approach enables the combination of information from different
sources and different formats, e.g. qualitative and quantitative data. The
indicators are grouped into physical vulnerability indicators and
socio-economic vulnerability indicators. First, in the vulnerability
assessment, each of the vulnerability indicators are assigned an integer
score value on the scale 1–5, with 1 meaning the lowest vulnerability and
5 meaning the highest vulnerability. To limit the use of subjective interpretation
of the user, and to make the method easy to use, a description for each score
level for each indicator is provided in Tables 4 and 5.</p>

<?xmltex \floatpos{p}?><table-wrap id="Ch1.T4" specific-use="star"><caption><p>Criteria for ranking of the physical vulnerability indicators and
barriers affecting the probability of infrastructure loss. For each indicator,
the criteria for score values 1–5 are described, where score value 1
corresponds to the lowest vulnerability and 5 to the highest vulnerability.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.97}[.97]?><oasis:tgroup cols="3">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:thead>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1">Physical vulnerability indicator</oasis:entry>

         <oasis:entry namest="col2" nameend="col3" align="left">Criteria for choice of score value 1–5 </oasis:entry>

       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>

         <oasis:entry colname="col1">Robustness and buffer capacity</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="2">1</oasis:entry>

         <oasis:entry colname="col3">The infrastructure is robust towards the natural event and/or</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">could withstand the natural event for a duration more than 2</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">times the median duration of the natural event.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">2</oasis:entry>

         <oasis:entry colname="col3">The infrastructure is quite robust towards the natural event</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">and/or could withstand the natural event for 1–2 times the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">median duration of the natural event.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">3</oasis:entry>

         <oasis:entry colname="col3">The infrastructure could withstand the natural event if the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">intensity is low–medium and/or the duration is 0.5–1 times</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">the median duration of the natural event.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">4</oasis:entry>

         <oasis:entry colname="col3">The infrastructure could only withstand the natural event if</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">the intensity is low and the duration is less than 0.5 times</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">the median duration of the natural event.</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col2">5</oasis:entry>

         <oasis:entry colname="col3">The infrastructure is fragile to the natural event.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">Level of protection (including physical</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="2">1</oasis:entry>

         <oasis:entry colname="col3">Infrastructure is not exposed to, or well protected from, the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">mitigation measures and exposure)</oasis:entry>

         <oasis:entry colname="col3">natural event. It is well adapted both to the current and future</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">climate.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">2</oasis:entry>

         <oasis:entry colname="col3">Infrastructure has a low exposure to or protected from the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">natural event in the study. Well adapted to current climate and</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">partially adapted to future climate.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">3</oasis:entry>

         <oasis:entry colname="col3">Partially protected from the natural event in the study. Well</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">adapted to current climate, but not to future climate.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">4</oasis:entry>

         <oasis:entry colname="col3">To a large extent, exposed to the natural event and insufficiently</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">adapted to current climate.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">5</oasis:entry>

         <oasis:entry colname="col3">To a large extent, exposed to the natural event and infrastructure</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">is not adapted to current climate.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">Quality level/age/level of maintenance and</oasis:entry>

         <oasis:entry rowsep="1" colname="col2">1</oasis:entry>

         <oasis:entry rowsep="1" colname="col3">Well maintained or age is <inline-formula><mml:math id="M19" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 15 % of expected lifetime.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">renewal</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="1">2</oasis:entry>

         <oasis:entry colname="col3">Generally well maintained or age is 15–30 % of expected</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">lifetime.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2">3</oasis:entry>

         <oasis:entry rowsep="1" colname="col3">Some planning of renewal and maintenance.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">4</oasis:entry>

         <oasis:entry colname="col3">Scarce planning of renewal and maintenance. Shortage of</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">resources.</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col2">5</oasis:entry>

         <oasis:entry colname="col3">Corrective maintenance only and ageing infrastructure.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">Adaptability and quality in operational</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="2">1</oasis:entry>

         <oasis:entry colname="col3">Infrastructure is operated by an operator and staff with long</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">procedures</oasis:entry>

         <oasis:entry colname="col3">experience and/or a high ability to adapt to changing framing</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">conditions.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">2</oasis:entry>

         <oasis:entry colname="col3">Infrastructure is operated by an experienced operator and/or</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">ability to adapt to changing framing conditions.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">3</oasis:entry>

         <oasis:entry colname="col3">Infrastructure is operated by an operator with some</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">experience and/or some ability to adapt to changing framing</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">conditions.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">4</oasis:entry>

         <oasis:entry colname="col3">Infrastructure is operated by an operator with very limited</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">experience and/or a low ability to adapt to changing framing</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">conditions.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col2" morerows="2">5</oasis:entry>

         <oasis:entry colname="col3">The infrastructure is operated by an unexperienced</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">operator/staff and/or a minimum ability to adapt to changing</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">framing conditions.</oasis:entry>

       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

<?xmltex \hack{\addtocounter{table}{-1}}?><?xmltex \floatpos{t}?><table-wrap id="Ch1.T5" specific-use="star"><caption><p>Continued.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="3">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:tbody>

       <oasis:row>

         <oasis:entry colname="col1">Transparency/complexity/degree of</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="2" align="center">1</oasis:entry>

         <oasis:entry colname="col3">The system is not dependent on the exposed part of the</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1">coupling</oasis:entry>

         <oasis:entry colname="col3">infrastructure to work and is, to a low extent, dependent on</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">single components to work.</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1" align="center">2</oasis:entry>

         <oasis:entry colname="col3">The exposed component interacts with a few other</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">components with a low degree of coupling.</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1" align="center">3</oasis:entry>

         <oasis:entry colname="col3">The exposed component interacts with many components</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">and the system has a high degree of coupling.</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1" align="center">4</oasis:entry>

         <oasis:entry colname="col3">The exposed component is part of a system with a high</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">degree of complexity.</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col2" morerows="1" align="center">5</oasis:entry>

         <oasis:entry colname="col3">The exposed part of the infrastructure is a component in a</oasis:entry>

       </oasis:row>

       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">system with a high degree of complexity and coupling.</oasis:entry>

       </oasis:row>

     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

<?xmltex \floatpos{p}?><table-wrap id="Ch1.T6" specific-use="star"><caption><p>Criteria for ranking of socio-economic vulnerability indicators. For
each indicator, the criteria for score values 1–5 are described, where
score value 1 corresponds to the lowest vulnerability and 5 to the highest
vulnerability.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="3">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:thead>
       <oasis:row>

         <oasis:entry colname="col1">Socio-economic</oasis:entry>

         <oasis:entry namest="col2" nameend="col3">Criteria for choice of score value 1–5 </oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1">vulnerability indicator</oasis:entry>

         <oasis:entry colname="col2"/>

         <oasis:entry colname="col3"/>

       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>

         <oasis:entry colname="col1">Redundancy/substitutes</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="1">1</oasis:entry>

         <oasis:entry colname="col3">There are adequate alternatives or back-up systems for the infrastructure</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">with sufficient capacity.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">2</oasis:entry>

         <oasis:entry colname="col3">There are alternatives or back-up systems for the infrastructure, which</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">implies few disadvantages for the users.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">3</oasis:entry>

         <oasis:entry colname="col3">There are alternatives or back-up systems for the infrastructure, but with</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">limited capacity or which implies disadvantages for the users.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">4</oasis:entry>

         <oasis:entry colname="col3">There exist alternatives, but with low (insufficient) capacity or which</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">imply major disadvantages to the users.</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col2">5</oasis:entry>

         <oasis:entry colname="col3">There are no back-up systems or practical alternatives.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">Cascading effects and</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="1">1</oasis:entry>

         <oasis:entry colname="col3">The exposed infrastructure is of negligible importance for societal</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">dependencies</oasis:entry>

         <oasis:entry rowsep="1" colname="col3">functions, with no potential cascading effects.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">2</oasis:entry>

         <oasis:entry colname="col3">The exposed infrastructure has little importance for societal functions,</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">with potentially small cascading effects.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">3</oasis:entry>

         <oasis:entry colname="col3">The exposed infrastructure has moderate importance for societal</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">functions, with potentially moderate cascading effects.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">4</oasis:entry>

         <oasis:entry colname="col3">The exposed infrastructure has considerable importance for societal</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">functions, with potentially considerable cascading effects.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">5</oasis:entry>

         <oasis:entry colname="col3">Important societal functions depend on the exposed infrastructure. Malfunctioning</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">of the infrastructure would potentially have large cascading effects.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">Preparedness</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="1">1</oasis:entry>

         <oasis:entry colname="col3">Very high risk awareness regarding the natural event, exhaustive</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">emergency response plans are available and frequent targeted drills.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">2</oasis:entry>

         <oasis:entry colname="col3">High risk awareness regarding the natural event, emergency response</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">plans are available and targeted drills are performed.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">3</oasis:entry>

         <oasis:entry colname="col3">Some risk awareness regarding the natural event and simple emergency</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">response plans are available.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2">4</oasis:entry>

         <oasis:entry rowsep="1" colname="col3">Low risk awareness and insufficient emergency response plans.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="1">5</oasis:entry>

         <oasis:entry colname="col3">Lack of risk awareness and knowledge about the natural event, with no</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">explicit emergency response plans.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">Early warning, emergency</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="3">1</oasis:entry>

         <oasis:entry colname="col3">The event is usually predictable well ahead of time and there is enough</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">response and measures</oasis:entry>

         <oasis:entry colname="col3">time for early warning. Thoroughly prepared routines exists for warning</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">and the implementation of measures to mitigate the consequences of the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">natural event.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">2</oasis:entry>

         <oasis:entry colname="col3">The event is usually predictable in time for early warning. There exist</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">routines for warning and the implementation of measures to limit the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">consequences of the natural event.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="3">3</oasis:entry>

         <oasis:entry colname="col3">The natural event can potentially be predicted, but the routines for</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">warning are insufficient; the warning time is short or the mitigation action</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">could potentially only have a small mitigating effect on the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">consequences.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col2" morerows="2">4</oasis:entry>

         <oasis:entry colname="col3">Low predictability and very short warning time or mitigation action</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">could potentially only have a minor mitigating effect on the</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry rowsep="1" colname="col3">consequences.</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col2" morerows="1">5</oasis:entry>

         <oasis:entry colname="col3">It is not possible to predict the natural event or there exist no known</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col3">mitigation measures to limit the consequences.</oasis:entry>

       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <p>Second, it is beneficial, both for the sake of simplicity and in order to
formulate user-friendly explicit procedures, to estimate one aggregated
physical vulnerability score and one aggregated socio-economic vulnerability
score. There are different ways of performing such a combination. The Department
for Communities and Local Government (2009) and JRC (2008) give an overview
on how to undertake and make the best use of multi-criteria analysis
techniques. Approaches for combining the indicators may be to, for example, estimate
arithmetical or geometric averages, to perform a fuzzy set analysis or to
apply a multi-criteria decision approach. In this paper it is chosen to
aggregate the indicator scores into two vulnerability scores: (i) a physical
vulnerability score, estimated as a weighted average of the individual score
of the physical vulnerability indicators, and (ii) a socio-economic
vulnerability score, estimated as a weighted average of the individual score
of the socio-economic vulnerability indicators. Each indicator is weighted
based on its overall degree of influence. The weights vary with the
scale, type and importance of the infrastructure in the study. The weighting
system is introduced to account for the relative importance of each
indicator for the total vulnerability level. If all the indicators are
believed to be of equal significance, equal weighting should be applied.
Techniques to determine weights include expert judgment, the analytical
hierarchy process (AHP), principal component analysis and factor analysis
(JRC, 2008). In the case examples presented in this paper, the weights are
chosen based on experience and local knowledge, on the scale of 1 (least
influential), 2 (moderately influential) or 3 (most influential). The final
vulnerability estimate is formulated as a weighted average of the individual
indicator scores, where the score for each indicator is multiplied with its
corresponding weight:

                  <disp-formula specific-use="align" content-type="numbered"><mml:math id="M20" display="block"><mml:mtable displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mstyle displaystyle="true" class="stylechange"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mi mathvariant="normal">Weighted</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd><mml:mtd><mml:mrow><mml:mstyle displaystyle="true" class="stylechange"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mi mathvariant="normal">average</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">vulnerability</mml:mi><mml:mo>=</mml:mo><mml:munder><mml:mo movablelimits="false">∑</mml:mo><mml:mrow><mml:mi mathvariant="normal">All</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">indicators</mml:mi></mml:mrow></mml:munder><mml:mi mathvariant="normal">Indicator</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">score</mml:mi><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd></mml:mtr><mml:mlabeledtr id="Ch1.E1"><mml:mtd/><mml:mtd><mml:mstyle class="stylechange" displaystyle="true"/></mml:mtd><mml:mtd><mml:mrow><mml:mstyle displaystyle="true" class="stylechange"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mo>⋅</mml:mo><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">Indicator</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">weight</mml:mi><mml:mo>/</mml:mo><mml:munder><mml:mo movablelimits="false">∑</mml:mo><mml:mrow><mml:mi mathvariant="normal">All</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">indicators</mml:mi></mml:mrow></mml:munder><mml:mi mathvariant="normal">Indicator</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">weight</mml:mi><mml:mo>.</mml:mo><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd></mml:mlabeledtr></mml:mtable></mml:math></disp-formula>

              <?xmltex \hack{\newpage}?><?xmltex \hack{\noindent}?>The flexibility introduced by allowing weight adjustments, combined with the
generic formulation of the indicators, makes the method suitable to different
types of infrastructures and different types of natural events. All the
steps of the procedure are implemented on an Excel work sheet to provide a
simple and user-friendly tool for the risk assessments, described
below.
<list list-type="custom"><list-item><label>a.</label><p>Physical vulnerability assessment: score values 1–5 need to be assigned to
each of the physical vulnerability indicators. A choice of score value 1
implies a low physical vulnerability of the infrastructure, indicating high
robustness and high buffer capacity, a high level of protection against the
analysed natural event, a high quality level, a new or very well-maintained
infrastructure, a high degree of adaptability and quality in operational
procedures, a high degree of transparency and that the infrastructure system
has a manageable degree of complexity and coupling. Score value 5 implies
that
the analysed infrastructure has a severe weakness with respect to the
analysed indicator, which means that the indicator contributes to a high
physical vulnerability. The criteria chosen to describe the physical
vulnerability for each indicator are outlined in Table 4. After the scoring
of the indicators, the physical vulnerability score is estimated using Eq. (1)
for the physical vulnerability indicators.</p></list-item><list-item><label>b.</label><p>Socio-economic vulnerability assessment: score values 1–5 need to be
assigned to each of the socio-economic vulnerability indicators. A choice of
score value 1 implies that the society has an optimized solution with
respect to the analysed indicator and infrastructure, contributing to lower
socio-economic vulnerability. This is the case if the society has parallel
systems to the infrastructure or substitutes that could offer the same
services as the analysed infrastructure, if the infrastructure is less
important for the society and the malfunctioning is not associated with
potential cascading effects, and if there are routines for preparedness and
an emergency response to mitigate the consequences. Score value 5 implies that
the society is especially vulnerable to the malfunctioning of the
infrastructure with respect to the analysed indicator, i.e. the indicator
contributes to a higher socio-economic vulnerability. The criteria chosen to
describe the socio-economic vulnerability for each indicator are outlined in
the scheme in Table 5. After the scoring of the indicators, the
socio-economic vulnerability score is estimated using Eq. (1) for the
socio-economic vulnerability indicators.</p></list-item></list></p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T7" specific-use="star"><caption><p>Indicative criteria for determining the probability category using
vulnerability indicators and adaptation of initial categorisation to final
categorisation.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="2">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Physical</oasis:entry>  
         <oasis:entry colname="col2">Adjustment of probability category</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">vulnerability</oasis:entry>  
         <oasis:entry colname="col2"/>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">score</oasis:entry>  
         <oasis:entry colname="col2"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Low (e.g. <inline-formula><mml:math id="M21" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 2)</oasis:entry>  
         <oasis:entry colname="col2">The final probability category is two categories lower than the initial one.</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Medium (e.g. 2–3.5)</oasis:entry>  
         <oasis:entry colname="col2">The final probability category is one category lower than the initial one.</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">High (e.g. <inline-formula><mml:math id="M22" display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> 3.5)</oasis:entry>  
         <oasis:entry colname="col2">The final probability category is equal to the initial one.</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

</sec>
<sec id="Ch1.S3.SS1.SSS3">
  <title>Step 3: final categorisation of probability and consequence, based on the initial categorisation and results from the vulnerability assessment</title>
      <p>The aggregation of steps 1 and 2 into final probability and consequence
categories is described below.
<list list-type="custom"><list-item><label>a.</label><p>Final probability category of the adverse event:
the difference between the probability of the natural event (as assessed in
Step 1) and the probability of the adverse event (i.e. infrastructure
malfunctioning) is assessed using the physical vulnerability score. The
assessment is based on the definition of conditional probability and a
quantitative interpretation of the vulnerability score, as a proxy for the
probability that the natural event in study will lead to infrastructure
malfunctioning. Expressing the relation between the probability of the
adverse event and the natural event using conditional probability, yields:<disp-formula specific-use="align" content-type="numbered"><mml:math id="M23" display="block"><mml:mtable displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mstyle class="stylechange" displaystyle="true"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mi>P</mml:mi><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd><mml:mtd><mml:mrow><mml:mstyle class="stylechange" displaystyle="true"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mo>(</mml:mo><mml:mi mathvariant="normal">infrastructure</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">malfunctioning</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">caused</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">by</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">natural</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">event</mml:mi><mml:mo>)</mml:mo><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd></mml:mtr><mml:mtr><mml:mtd><mml:mstyle class="stylechange" displaystyle="true"/></mml:mtd><mml:mtd><mml:mrow><mml:mstyle displaystyle="true" class="stylechange"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mo>=</mml:mo><mml:mi>P</mml:mi><mml:mo>(</mml:mo><mml:mi mathvariant="normal">natural</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">event</mml:mi><mml:mo>)</mml:mo><mml:mo>⋅</mml:mo><mml:mi>P</mml:mi><mml:mo>(</mml:mo><mml:mi mathvariant="normal">infrastructure</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">malfunctioning</mml:mi><mml:mo>|</mml:mo><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd></mml:mtr><mml:mlabeledtr id="Ch1.E2"><mml:mtd/><mml:mtd><mml:mstyle class="stylechange" displaystyle="true"/></mml:mtd><mml:mtd><mml:mrow><mml:mstyle class="stylechange" displaystyle="true"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mi mathvariant="normal">natural</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">event</mml:mi><mml:mo>)</mml:mo><?xmltex \hack{$\egroup}?><mml:mo>.</mml:mo></mml:mrow></mml:mtd></mml:mlabeledtr></mml:mtable></mml:math></disp-formula></p><p>The physical vulnerability score could serve as a proxy for the conditional
probability <inline-formula><mml:math id="M24" display="inline"><mml:mi>P</mml:mi></mml:math></inline-formula>(infrastructure malfunctioning<inline-formula><mml:math id="M25" display="inline"><mml:mo>|</mml:mo></mml:math></inline-formula>natural
event). If the infrastructure has a high physical vulnerability score, then
this probability is approximately 1 and Eq. (2) reads<disp-formula specific-use="align" content-type="numbered"><mml:math id="M26" display="block"><mml:mtable displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mstyle displaystyle="true" class="stylechange"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mi>P</mml:mi><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd><mml:mtd><mml:mrow><mml:mstyle class="stylechange" displaystyle="true"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mo>(</mml:mo><mml:mi mathvariant="normal">infrastructure</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">malfunctioning</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">caused</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">by</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">natural</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">event</mml:mi><mml:mo>)</mml:mo><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd></mml:mtr><mml:mlabeledtr id="Ch1.E3"><mml:mtd/><mml:mtd><mml:mstyle class="stylechange" displaystyle="true"/></mml:mtd><mml:mtd><mml:mrow><mml:mstyle class="stylechange" displaystyle="true"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mo>≈</mml:mo><mml:mi>P</mml:mi><mml:mo>(</mml:mo><mml:mi mathvariant="normal">natural</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">event</mml:mi><mml:mo>)</mml:mo><?xmltex \hack{$\egroup}?><mml:mo>.</mml:mo></mml:mrow></mml:mtd></mml:mlabeledtr></mml:mtable></mml:math></disp-formula></p><p>The probability that the infrastructure will fail (due to the natural event)
is thus similar to the probability of the natural event and, consequently,
the final probability categorisation is equal to the initial one (assessed
in Step 1).</p><p>On the other extreme, if the physical vulnerability score is very low, the
conditional probability, <inline-formula><mml:math id="M27" display="inline"><mml:mi>P</mml:mi></mml:math></inline-formula>(infrastructure malfunctioning<inline-formula><mml:math id="M28" display="inline"><mml:mo>|</mml:mo></mml:math></inline-formula>natural
event), is low – e.g. in the order of 10 %, the relation yields<disp-formula specific-use="align" content-type="numbered"><mml:math id="M29" display="block"><mml:mtable displaystyle="true"><mml:mtr><mml:mtd><mml:mrow><mml:mstyle displaystyle="true" class="stylechange"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mi>P</mml:mi><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd><mml:mtd><mml:mrow><mml:mstyle class="stylechange" displaystyle="true"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mo>(</mml:mo><mml:mi mathvariant="normal">infrastructure</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">malfunctioning</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">caused</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">by</mml:mi><mml:mspace width="0.25em" linebreak="nobreak"/><mml:mi mathvariant="normal">natural</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">event</mml:mi><mml:mo>)</mml:mo><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd></mml:mtr><mml:mlabeledtr id="Ch1.E4"><mml:mtd/><mml:mtd><mml:mstyle class="stylechange" displaystyle="true"/></mml:mtd><mml:mtd><mml:mrow><mml:mstyle class="stylechange" displaystyle="true"/><?xmltex \hack{\hbox\bgroup\fontsize{9.5}{9.5}\selectfont$\displaystyle}?><mml:mo>≈</mml:mo><mml:mn mathvariant="normal">0.1</mml:mn><mml:mo>⋅</mml:mo><mml:mi>P</mml:mi><mml:mo>(</mml:mo><mml:mi mathvariant="normal">natural</mml:mi><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mi mathvariant="normal">event</mml:mi><mml:mo>)</mml:mo><mml:mo>.</mml:mo><?xmltex \hack{$\egroup}?></mml:mrow></mml:mtd></mml:mlabeledtr></mml:mtable></mml:math></disp-formula></p><p>Accordingly, a multiplication of the probability with 0.1 corresponds to a
reduction in probability category (A–E, as shown in Table 2) of
1–2 categories, based on the quantitative relationship between the probability
categories, i.e. <inline-formula><mml:math id="M30" display="inline"><mml:mi>P</mml:mi></mml:math></inline-formula>(infrastructure malfunctioning caused by natural event)
is 1–2 probability categories lower than <inline-formula><mml:math id="M31" display="inline"><mml:mi>P</mml:mi></mml:math></inline-formula>(natural event). The step from the
<inline-formula><mml:math id="M32" display="inline"><mml:mi>P</mml:mi></mml:math></inline-formula>(natural event), used in the initial categorisation, to P(infrastructure
malfunctioning caused by natural event), assessed in the final
categorisation,
is thus accounted for through an adjustment of the probability categories.
The physical vulnerability score is applied to adjust the probability
category according to the suggested criteria shown in Table 6. However,
judgment should be used when applying these criteria, taking into account,
for example, whether the probability of the natural event belongs to the lower range
within the category or to a higher range and whether one of the
vulnerability indicators is considered as having a much higher importance
than the others in the analysed case.</p></list-item><list-item><label>b.</label><p>Final consequence categorisation:
the socio-economic vulnerability score affects the socio-economic
consequences of the infrastructure malfunctioning. The final consequence
category depends on the duration of the infrastructure malfunctioning
and the number of infrastructure users (as assessed in Step 1) as well as the
socio-economic vulnerability score.</p><p>Adjustment of the consequence category: the number of people affected by the
malfunctioning infrastructure could be higher or lower than the number of
infrastructure users, depending on how the situation is handled and how
important the malfunctioning infrastructure is for the society. The
socio-economic vulnerability score is a proxy for the societal capacity to
maintain its functions without the specific infrastructure and to cope with
malfunctioning infrastructure. Accordingly, if the socio-economic
vulnerability score is low, then the number of affected people will be lower
than the number of infrastructure users, e.g. if the infrastructure
malfunctioning is managed well and substitutes for the service provided by
the malfunctioning infrastructure are established. Accordingly, the final
consequence category should be adjusted down from the initial consequence
category, as assessed by using Table 3. However, if the socio-economic
vulnerability score is high, then the number of affected people will be higher than
the number of infrastructure users, e.g. if there are large cascading
effects. Then, the final consequence category could be higher than the
initial one. The socio-economic vulnerability score is applied to adjust the
consequence category according to the suggested criteria in Table 7.</p></list-item></list></p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T8" specific-use="star"><caption><p>Indicative criteria for determining the consequence category using
vulnerability indicators and adaptation of initial categorisation to final
categorisation.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="2">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Socio-economic</oasis:entry>  
         <oasis:entry colname="col2">Adjustment of consequence category</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">vulnerability</oasis:entry>  
         <oasis:entry colname="col2"/>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">score</oasis:entry>  
         <oasis:entry colname="col2"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Low (e.g. <inline-formula><mml:math id="M33" display="inline"><mml:mo>&lt;</mml:mo></mml:math></inline-formula> 2)</oasis:entry>  
         <oasis:entry colname="col2">The final consequence category is one category lower than the initial one.</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Medium (e.g. 2–3.5)</oasis:entry>  
         <oasis:entry colname="col2">The final consequence category equals the initial one.</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">High (e.g. 3.5–5)</oasis:entry>  
         <oasis:entry colname="col2">The final consequence category is one category higher than the initial one.</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

      <?xmltex \floatpos{t}?><fig id="Ch1.F3" specific-use="star"><caption><p>Location of the study area in Norway (left panel source: ESRI) and
the spatial extent of Stryn and Hornindal municipalities in Western Norway (right
panel source: The Norwegian Mapping Authority).</p></caption>
            <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/17/481/2017/nhess-17-481-2017-f03.png"/>

          </fig>

      <p><?xmltex \hack{\noindent}?>When steps 1–3 are performed, each analysed scenario is assigned a
probability category (A–E) and a consequence category (1–5). The risk level
is determined by the combination of these, subdivided into seven risk levels
as shown in Table 10. Even if the vulnerability is assessed relatively, the
initial classification is quantitative and each cell could therefore be
anchored in quantitative risk estimates. By applying the quantitative
criteria as a basis to assign a risk range to each cell in the risk matrix, it
may be shown that the diagonal lines in the risk matrix approximately
represent equivalent risk levels, i.e. that the risk is largely equal along
diagonal lines. The approach is useful for prioritisation of mitigation
measures, e.g. those that give priority to a certain sector ahead of another. Explicit
criteria or risk thresholds for recommendations regarding the follow-up and
risk acceptance are not given, both because each municipality must adapt the
criteria for follow-up to their own situation and capacity (scenarios with
the highest risk must be prioritised regardless of risk acceptance) and
because the method is coarse, with a relative risk scale making it difficult
to relate to objective risk acceptance criteria.</p>
</sec>
</sec>
</sec>
<sec id="Ch1.S4">
  <title>Demonstration examples for the municipalities of Stryn and Hornindal</title>
      <p>The methodology proposed in Sect. 3 was tested and demonstrated through
application examples for the municipalities Stryn and Hornindal. Stryn and
Hornindal are municipalities in the county Sogn og Fjordane in Western
Norway. The characteristics for the area are the combination of fjords,
glaciers, rivers and lakes. There are tall and steep mountains, deep valleys
with forested and fertile mountainsides and valley floors. The
municipalities are situated just west of the water divide separating Western
and Eastern Norway (Fig. 3), with strong orographic effects on
precipitation and weather. The industries are varied, but consist mainly of
small and medium size industrial establishments. The main road overcrossing
the mountain has a rather high proportion of utility transportation (Fakta
om Stryn, 2017). The study area is exposed to different types of natural
hazards, especially landslides and avalanches, including floods and storms,
which need to be considered during the development of infrastructure and
residential and commercial buildings in the municipality. Natural hazards
have affected infrastructure repeatedly in the past (Stryn kommune Rådmannsavdelinga, 2014).</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F4" specific-use="star"><caption><p>Overview of the locations of the site-specific scenarios. The location
of each scenario is identified with a red star, referring to the scenario number
in the list above. Star 1 shows the location of RV 15 in Stryn, but the actual
scenario is located at a part of the road outside the map. Source: The Norwegian
Mapping Authority.</p></caption>
        <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/17/481/2017/nhess-17-481-2017-f04.png"/>

      </fig>

      <p>Based on the qualitative municipal risk and vulnerability analysis for Stryn
and Hornindal, as described in Stryn kommune Rådmannsavdelinga (2014),
the following site-specific scenarios were selected for testing of the
proposed method:
<list list-type="order"><list-item><p>snow avalanche overrunning main road RV 15 at Strynefjellet;</p></list-item><list-item><p>debris flow reaching Innvik waterworks;</p></list-item><list-item><p>snow avalanche overrunning main road 724 to Oldedalen;</p></list-item><list-item><p>storm leading to failure in electricity distribution and communication to
the municipal centre;</p></list-item><list-item><p>landslide across main road E39 at Skredestranda;</p></list-item><list-item><p>ice jam breakup in the Storelva river in Hornindal and failure in sewage system;</p></list-item><list-item><p>storm leading to the closure of the ferry service between Anda and Lote.</p></list-item></list>
The location of these scenarios is indicated in Fig. 4. As Fig. 4
shows, the analysis also considers scenarios located outside the
municipalities that may affect the municipalities.</p>
      <p>Explanations for the risk assessment of the scenarios are provided in Appendix A.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T9" specific-use="star"><caption><p>Ranking of indicators and determination of physical and socio-economic
vulnerability scores. The first column shows the indicator group (i.e. physical
or socio-economic vulnerability), the second column the vulnerability indicator
and the next columns the score values for the scenarios.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="9">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="right"/>
     <oasis:colspec colnum="4" colname="col4" align="right"/>
     <oasis:colspec colnum="5" colname="col5" align="right"/>
     <oasis:colspec colnum="6" colname="col6" align="right"/>
     <oasis:colspec colnum="7" colname="col7" align="right"/>
     <oasis:colspec colnum="8" colname="col8" align="right"/>
     <oasis:colspec colnum="9" colname="col9" align="right"/>
     <oasis:thead>
       <oasis:row>  
         <oasis:entry colname="col1">Group</oasis:entry>  
         <oasis:entry colname="col2">Factor</oasis:entry>  
         <oasis:entry rowsep="1" namest="col3" nameend="col9" align="center">Score values, for scenario no. </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">1</oasis:entry>  
         <oasis:entry colname="col4">2</oasis:entry>  
         <oasis:entry colname="col5">3</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7">5</oasis:entry>  
         <oasis:entry colname="col8">6</oasis:entry>  
         <oasis:entry colname="col9">7</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Vulnerability</oasis:entry>  
         <oasis:entry colname="col2">Robustness and buffer capacity</oasis:entry>  
         <oasis:entry colname="col3">4</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">4</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7">4</oasis:entry>  
         <oasis:entry colname="col8">2</oasis:entry>  
         <oasis:entry colname="col9">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">factors,</oasis:entry>  
         <oasis:entry colname="col2">Level of protection</oasis:entry>  
         <oasis:entry colname="col3">5</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">5</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7">4</oasis:entry>  
         <oasis:entry colname="col8">3</oasis:entry>  
         <oasis:entry colname="col9">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">physical</oasis:entry>  
         <oasis:entry colname="col2">Quality level/age/level of maintenance and renewal</oasis:entry>  
         <oasis:entry colname="col3">3</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">3</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7">2</oasis:entry>  
         <oasis:entry colname="col8">2</oasis:entry>  
         <oasis:entry colname="col9">2</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">vulnerability</oasis:entry>  
         <oasis:entry colname="col2">Adaptability and quality in operational procedures</oasis:entry>  
         <oasis:entry colname="col3">2</oasis:entry>  
         <oasis:entry colname="col4">2</oasis:entry>  
         <oasis:entry colname="col5">2</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7">3</oasis:entry>  
         <oasis:entry colname="col8">2</oasis:entry>  
         <oasis:entry colname="col9">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">of the</oasis:entry>  
         <oasis:entry colname="col2">Transparency/complexity/degree of coupling</oasis:entry>  
         <oasis:entry colname="col3">2</oasis:entry>  
         <oasis:entry colname="col4">4</oasis:entry>  
         <oasis:entry colname="col5">2</oasis:entry>  
         <oasis:entry colname="col6">2</oasis:entry>  
         <oasis:entry colname="col7">2</oasis:entry>  
         <oasis:entry colname="col8">2</oasis:entry>  
         <oasis:entry colname="col9">2</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">infrastructure</oasis:entry>  
         <oasis:entry colname="col2"><italic>Average score, physical vulnerability</italic></oasis:entry>  
         <oasis:entry colname="col3">3.5</oasis:entry>  
         <oasis:entry colname="col4">2.9</oasis:entry>  
         <oasis:entry colname="col5">3.5</oasis:entry>  
         <oasis:entry colname="col6">2.9</oasis:entry>  
         <oasis:entry colname="col7">2.9</oasis:entry>  
         <oasis:entry colname="col8">2.2</oasis:entry>  
         <oasis:entry colname="col9">2.7</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Vulnerability</oasis:entry>  
         <oasis:entry colname="col2">Redundancy/substitutes</oasis:entry>  
         <oasis:entry colname="col3">4</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">5</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7">4</oasis:entry>  
         <oasis:entry colname="col8">3</oasis:entry>  
         <oasis:entry colname="col9">2</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">factors,</oasis:entry>  
         <oasis:entry colname="col2">Cascading effects and dependencies</oasis:entry>  
         <oasis:entry colname="col3">3</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">3</oasis:entry>  
         <oasis:entry colname="col6">4</oasis:entry>  
         <oasis:entry colname="col7">3</oasis:entry>  
         <oasis:entry colname="col8">3</oasis:entry>  
         <oasis:entry colname="col9">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">socio-economic</oasis:entry>  
         <oasis:entry colname="col2">Preparedness</oasis:entry>  
         <oasis:entry colname="col3">1</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">2</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7">2</oasis:entry>  
         <oasis:entry colname="col8">3</oasis:entry>  
         <oasis:entry colname="col9">3</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">vulnerability</oasis:entry>  
         <oasis:entry colname="col2">Early warning, emergency response and measures</oasis:entry>  
         <oasis:entry colname="col3">5</oasis:entry>  
         <oasis:entry colname="col4">3</oasis:entry>  
         <oasis:entry colname="col5">3</oasis:entry>  
         <oasis:entry colname="col6">3</oasis:entry>  
         <oasis:entry colname="col7">3</oasis:entry>  
         <oasis:entry colname="col8">2</oasis:entry>  
         <oasis:entry colname="col9">2</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2"><italic>Average score, socio-economic vulnerability</italic></oasis:entry>  
         <oasis:entry colname="col3">3.4</oasis:entry>  
         <oasis:entry colname="col4">3.0</oasis:entry>  
         <oasis:entry colname="col5">3.4</oasis:entry>  
         <oasis:entry colname="col6">3.5</oasis:entry>  
         <oasis:entry colname="col7">3.0</oasis:entry>  
         <oasis:entry colname="col8">2.8</oasis:entry>  
         <oasis:entry colname="col9">2.5</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T10" specific-use="star"><caption><p>Initial and final categorisation of probability and consequence. The
difference between the final and initial probability category is determined by
the physical vulnerability score. The difference between the final and initial
consequence category is determined by the socio-economic vulnerability score. Sc. means scenario.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="9">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:colspec colnum="6" colname="col6" align="left"/>
     <oasis:colspec colnum="7" colname="col7" align="left"/>
     <oasis:colspec colnum="8" colname="col8" align="left"/>
     <oasis:colspec colnum="9" colname="col9" align="left"/>
     <oasis:thead>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1">Group</oasis:entry>  
         <oasis:entry colname="col2"/>  
         <oasis:entry colname="col3">Sc. 1</oasis:entry>  
         <oasis:entry colname="col4">Sc. 2</oasis:entry>  
         <oasis:entry colname="col5">Sc. 3</oasis:entry>  
         <oasis:entry colname="col6">Sc. 4</oasis:entry>  
         <oasis:entry colname="col7">Sc. 5</oasis:entry>  
         <oasis:entry colname="col8">Sc. 6</oasis:entry>  
         <oasis:entry colname="col9">Sc. 7</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>  
         <oasis:entry colname="col1">Probability</oasis:entry>  
         <oasis:entry colname="col2">Initial probability category</oasis:entry>  
         <oasis:entry colname="col3">E</oasis:entry>  
         <oasis:entry colname="col4">D</oasis:entry>  
         <oasis:entry colname="col5">E</oasis:entry>  
         <oasis:entry colname="col6">E</oasis:entry>  
         <oasis:entry colname="col7">E</oasis:entry>  
         <oasis:entry colname="col8">D</oasis:entry>  
         <oasis:entry colname="col9">E</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry rowsep="1" colname="col2">according to Table 2.</oasis:entry>  
         <oasis:entry rowsep="1" colname="col3"/>  
         <oasis:entry rowsep="1" colname="col4"/>  
         <oasis:entry rowsep="1" colname="col5"/>  
         <oasis:entry rowsep="1" colname="col6"/>  
         <oasis:entry rowsep="1" colname="col7"/>  
         <oasis:entry rowsep="1" colname="col8"/>  
         <oasis:entry rowsep="1" colname="col9"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">Final probability category</oasis:entry>  
         <oasis:entry colname="col3">E</oasis:entry>  
         <oasis:entry colname="col4">C</oasis:entry>  
         <oasis:entry colname="col5">E</oasis:entry>  
         <oasis:entry colname="col6">D</oasis:entry>  
         <oasis:entry colname="col7">E<inline-formula><mml:math id="M35" display="inline"><mml:msup><mml:mi/><mml:mo>*</mml:mo></mml:msup></mml:math></inline-formula></oasis:entry>  
         <oasis:entry colname="col8">C</oasis:entry>  
         <oasis:entry colname="col9">D</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">according to physical</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">vulnerability scores in Table 8</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9"/>
       </oasis:row>
       <oasis:row rowsep="1">  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">and criteria in Table 6.</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1">Consequence</oasis:entry>  
         <oasis:entry rowsep="1" colname="col2">Number of infrastructure users.</oasis:entry>  
         <oasis:entry rowsep="1" colname="col3">800</oasis:entry>  
         <oasis:entry rowsep="1" colname="col4">250</oasis:entry>  
         <oasis:entry rowsep="1" colname="col5">100</oasis:entry>  
         <oasis:entry rowsep="1" colname="col6"><inline-formula><mml:math id="M36" display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> 1000</oasis:entry>  
         <oasis:entry rowsep="1" colname="col7"><inline-formula><mml:math id="M37" display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> 1000</oasis:entry>  
         <oasis:entry rowsep="1" colname="col8">800</oasis:entry>  
         <oasis:entry rowsep="1" colname="col9">100</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">Duration of the outage/</oasis:entry>  
         <oasis:entry colname="col3">1–2</oasis:entry>  
         <oasis:entry colname="col4">2–7</oasis:entry>  
         <oasis:entry colname="col5">1–2</oasis:entry>  
         <oasis:entry colname="col6">2–7</oasis:entry>  
         <oasis:entry colname="col7">2–7</oasis:entry>  
         <oasis:entry colname="col8">2–7</oasis:entry>  
         <oasis:entry colname="col9">1–2</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry rowsep="1" colname="col2">infrastructure loss (days).</oasis:entry>  
         <oasis:entry rowsep="1" colname="col3"/>  
         <oasis:entry rowsep="1" colname="col4"/>  
         <oasis:entry rowsep="1" colname="col5"/>  
         <oasis:entry rowsep="1" colname="col6"/>  
         <oasis:entry rowsep="1" colname="col7"/>  
         <oasis:entry rowsep="1" colname="col8"/>  
         <oasis:entry rowsep="1" colname="col9"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">Initial consequence category</oasis:entry>  
         <oasis:entry colname="col3">3</oasis:entry>  
         <oasis:entry colname="col4">4</oasis:entry>  
         <oasis:entry colname="col5">2</oasis:entry>  
         <oasis:entry colname="col6">5</oasis:entry>  
         <oasis:entry colname="col7">5</oasis:entry>  
         <oasis:entry colname="col8">4</oasis:entry>  
         <oasis:entry colname="col9">2</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry rowsep="1" colname="col2">according to Table 3.</oasis:entry>  
         <oasis:entry rowsep="1" colname="col3"/>  
         <oasis:entry rowsep="1" colname="col4"/>  
         <oasis:entry rowsep="1" colname="col5"/>  
         <oasis:entry rowsep="1" colname="col6"/>  
         <oasis:entry rowsep="1" colname="col7"/>  
         <oasis:entry rowsep="1" colname="col8"/>  
         <oasis:entry rowsep="1" colname="col9"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">Final consequence category</oasis:entry>  
         <oasis:entry colname="col3">3</oasis:entry>  
         <oasis:entry colname="col4">4</oasis:entry>  
         <oasis:entry colname="col5">3</oasis:entry>  
         <oasis:entry colname="col6">5</oasis:entry>  
         <oasis:entry colname="col7">5</oasis:entry>  
         <oasis:entry colname="col8">3</oasis:entry>  
         <oasis:entry colname="col9">2</oasis:entry>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">according to socio-economic</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">vulnerability scores in Table 8</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9"/>
       </oasis:row>
       <oasis:row>  
         <oasis:entry colname="col1"/>  
         <oasis:entry colname="col2">and criteria in Table 7.</oasis:entry>  
         <oasis:entry colname="col3"/>  
         <oasis:entry colname="col4"/>  
         <oasis:entry colname="col5"/>  
         <oasis:entry colname="col6"/>  
         <oasis:entry colname="col7"/>  
         <oasis:entry colname="col8"/>  
         <oasis:entry colname="col9"/>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table><table-wrap-foot><p><inline-formula><mml:math id="M34" display="inline"><mml:msup><mml:mi/><mml:mo>*</mml:mo></mml:msup></mml:math></inline-formula> This probability category was not adjusted downwards even
if the physical vulnerability score would indicate that. The reason for this is that
the actual landslide probability is much higher than the lower limit of the
probability category.</p></table-wrap-foot></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T11"><caption><p>Results from the semi-quantitative analyses.</p></caption>
  <?xmltex \igopts{width=236.157874pt}?><graphic xlink:href="https://nhess.copernicus.org/articles/17/481/2017/nhess-17-481-2017-t10.pdf"/>
</table-wrap>

<sec id="Ch1.S4.SSx1" specific-use="unnumbered">
  <title>Results</title>
      <p>The main aim of the analyses was to demonstrate the methodology and test its
usefulness, rather than the actual results. The results are, to a large
extent, based on expert judgment and should be considered as preliminary. The
ranking was performed together with a representative for the stakeholders in
Stryn, who was leading the municipal risk and vulnerability analyses in
Stryn and Hornindal in 2014 and who was knowledgeable about the hazard and
risk situation in the area.</p>
      <p><?xmltex \hack{\newpage}?>The resulting ranking of the vulnerability indicators for each of the
scenarios are presented in Table 8. The initial and final categorisation of
probability and consequence, as well as the basis for the categorisation
(i.e. the frequency or probability of the natural event, the duration and
number of people served by the infrastructure), are shown in Table 9.
Explanation of and reasoning for the ranking is given in Appendix A. The
method has been implemented in an Excel sheet in which the ranking,
weighting and calculations have been performed.</p>
      <p>The results of the analyses are placed in a matrix with increasing severity
of consequence along the first axis and increasing probability along the
second axis (Table 10). The corresponding risk level is determined by
location in the matrix, subdividing the risk into seven risk levels
illustrated with colour codes. In this way, the risk associated with each of
the scenarios could easily be compared and the most critical scenarios identified.</p>
      <p>As Table 10 shows, the ranking of the risk associated with the analysed
scenarios is as follows.
<list list-type="bullet"><list-item><p>Risk level 7: storm leading to failure in electricity distribution and
communication to the municipal centre; landslide across main road E39 at
Skredestranda.</p></list-item><list-item><p>Risk level 6: snow avalanche overrunning main road RV 15 at
Strynefjellet;
landslide across main road 724 to Olderdalen.</p></list-item><list-item><p>Risk level 5: debris flow reaching Innvik waterworks.</p></list-item><list-item><p>Risk level 4: ice jam breakup in the Storelva river in Hornindal; failure in
sewage system; storm leading to closure of the ferry service between Anda and Lote.</p></list-item></list>
None of the analysed scenarios ended up being low risk scenarios. This is
unsurprising, since the selected scenarios are based on generic scenarios,
identified in Stryn kommune Rådmannsavdelinga (2014), that are believed
to pose significant risk to the municipalities. In addition, in order to
facilitate the data collection for the site-specific scenarios, previous
events were tested to demonstrate the application of the model.</p>
      <p>The results of the analyses provide a better overview of the relevant
risks and vulnerabilities and contribute to an increased awareness in the
municipalities. Knowledge about risk and vulnerability associated with the
identified scenarios is an important first step to reduce the risk. Risk
reduction is especially important for the scenarios with the highest risk,
e.g. at risk level 6 and risk level 7. All the three scenarios with
a landslide or avalanche across roads emerge as the most critical scenarios,
in addition to the failure in electricity and communication caused by
storms. The risk could either be reduced by reducing the probability of the
scenario (e.g. through implementation of physical mitigation measures for
landslides on the most exposed parts of the road) or by reducing the
associated consequences (e.g. through an improvement of the socio-economic
vulnerability indicators, such as establishing redundant infrastructure
systems). Through systematic and repeated risk analyses, as described in Sect. 2.2
and in DSB (2014), followed by associated risk management actions, the
municipality can move step by step towards increased safety and stable
infrastructure services for the inhabitants.</p>
</sec>
</sec>
<sec id="Ch1.S5">
  <title>Discussion</title>
<sec id="Ch1.S5.SS1">
  <title>Usefulness and advantages</title>
      <p>The purpose of the municipal vulnerability and risk analysis is, among
others,
to provide an overview of adverse events that pose a risk to the
municipality, assess risk and vulnerability across sectors, and provide a
basis for objectives, priorities and decision making for civil protection
and emergency planning in the municipality. It is also within the
responsibility of the municipalities to help maintain critical societal
functions during and after adverse events. The proposed method is designed
to be consistent with, and a supplement to, the guidelines for municipal
risk and vulnerability analysis in Norway provided by the Norwegian
directorate for Civil Protection, DSB (2014). The focus of the method, as
described in Sect. 3, is to propose a tool for the screening of the potential
scenarios of malfunctioning infrastructure caused by natural events in an
explicit, systematic, transparent and repeatable way that could be applied
at the semi-quantitative second level in a three-level approach. Due to
interdependencies between the infrastructures and societal dependencies, a
full analysis of risk associated with infrastructure systems is a
complicated and labour intensive task. The three-level strategy offers a
practical approach to reduce the analysis effort related to the risk
assessment (Liu et al., 2015; Bowles et al., 2013). The proposed method is a
risk assessment method with low to intermediate precision and resolution.
Application of the method assigns a relative risk level to each of the
scenarios, where risk level 1 implies the lowest risk and risk level 7 the highest risk.</p>
      <p>The risk ranking provides a useful basis for prioritisation, where the
scenarios with the highest risk levels should be analysed further and
followed up, e.g. by giving priority to one sector over another. The
scenarios associated with the highest risk also form the basis for the
allocation of resources to preparedness in the municipality, including
execution of emergency management drills. The risk expressed by risk levels
serve, due to their simplicity, as a good tool to compare risk between
different scenarios and thus also to communicate the risk (Oboni and Oboni, 2013).</p>
      <p>There is no all-encompassing method available to analyse all aspects of
infrastructure risks, but different methods serve different purposes and
have different advantages (and disadvantages). The advantages with the
proposed method is that it is generic and has a very broad scope (applicable
for assessment of socio-economic risk associated with malfunctioning in
different infrastructure sectors). It aims to be applicable within the main
types of infrastructure (electricity supply, water supply and
transportation). Methods are often tailored to the
particular needs of the sector they are defined within (Giannopoulos et al.,
2012).
Risk assessment methods are a compromise between the time and cost (and
data) necessary to perform the analysis, and its ability to offer
information at a level of detail allowing the risk manager to understand the
risk (and resilience) and allowing informed and efficient decision
making. Indicator approaches applying a weighted mean of several scores (as in
this method) are often used in sectorial approaches (Giannopoulos et al.,
2012). Indicators are useful for reducing complexity, measuring progress,
mapping and setting priorities and they could serve as an important tool for
decision makers (Cutter et al., 2008). The proposed method serves the
purpose of screening scenarios of natural events threatening critical
infrastructure in a municipal risk and vulnerability analysis, even if it
does not allow a detailed study of the risk and vulnerability. The method is
comprehensive, yet fast. It does not require a large amount of data. The
indicator-based approach for the vulnerability assessment enables a
combination of different types of data from different sources and knowledge
domains and on different formats. However, the user needs to have
a comprehensive knowledge of the local conditions, properties of the
infrastructure and how the infrastructure is operated. The user also needs
to be aware of the hazard situation in the area, with respect to natural
events, and be capable of assessing the frequency of the hazard and the
importance of the various vulnerability factors for the infrastructure.</p>
      <p>The method's purpose is to invite
municipal stakeholders with different types of expertise to a collaborative effort.
A representative
for the stakeholders in Stryn helped in testing the method and found it (and
the excel sheet in which the method was implemented) useful. It is desirable
that the municipalities lead this analysis themselves, in order to ensure
that the analysis is followed up and forms an integrated part of municipal
risk management. The preparation of the municipal risk and vulnerability
analysis is also a learning process, which may increase risk awareness. The
proposed method guides the user with respect to which vulnerability factors
to assess, both for assessment of the probability of the infrastructure
malfunctioning and the societal consequences. It provides, through the
explicit ranking criteria, guidance for the assessment of how each indicator
contributes to the overall vulnerability and how to aggregate the
information into a final result, even if some judgment is required when
using the method.</p>
      <p>The proposed method could, in addition to the risk ranking, provide implicit
guidance on how to reduce the vulnerability and, consequently, also the risk.
The method assesses several aspects of vulnerability and resilience, and the
results from the physical and socio-economic vulnerability assessment could
be used to identify the indicators contributing most to the vulnerability
for each case. Special attention should be paid to indicators with a high
vulnerability score, especially in combination with high importance, i.e. a
high weight. The identification of the most critical indicators helps
identify where to focus further efforts. Within the application examples in
Sect. 4, the scenarios with the highest risk were scenario 4, storm
leading to failure in electricity distribution and communication to the
municipal centre, and scenario 5, landslide across main road E39 at
Skredestranda. For scenario 4, almost all of the physical vulnerability indicators were
assigned a score value of 3, except for the transparency/complexity/degree of
coupling indicator, which was assigned a value of 2. The most important physical
vulnerability indicators were considered to be related to robustness and
buffer capacity and level of protection. In order to reduce the
probability of infrastructure malfunctioning in the most efficient way,
measures involving an increase in the robustness and/or buffer capacity of the
electricity network as well as measures involving protection of the network
should be considered. The socio-economic vulnerability indicators,
redundancy/substitutes and cascading effects and dependencies were
assigned a score of 4 and were both considered to be of high importance. To
efficiently reduce the socio-economic consequences, measures to reduce these
vulnerabilities should be considered, e.g. investing in substitutes to the
electricity distribution, like gasoline, diesel or wind power generators,
batteries or solar panels. Today, society is highly dependent on
electricity. Reduction of this dependency will be complicated in general,
but it can also cover a wide range of distributed initiatives, e.g. implementing
electricity-independent central heating systems.</p>
</sec>
<sec id="Ch1.S5.SS2">
  <title>Limitations, uncertainties and future needs</title>
      <p>Semi-quantitative, indicator-based methods will necessarily require the use of
(knowledge-based) judgment and accordingly be associated with subjectivity
and uncertainties, both within the definition of the method and the use of
the method. Indicators are commonly used in vulnerability and resilience
assessment, since it is often difficult to quantify vulnerability and
resilience in absolute terms without any external reference with which to
validate the calculations. Indicators are typically used to assess relative
levels of vulnerability and resilience, either to compare between places or
to analyse trends over time (Cutter et al., 2008). Assigning score values to
the indicators requires interpretation and subjective judgment. This is thought
to reduce the effect of subjective interpretation through descriptions of
the different score levels for each indicator. The method is applicable for
different infrastructures (electricity supply, water supply and
transportation) and uses generic factors for infrastructure vulnerability.
Therefore, the need for precise descriptions of criteria for ranking of the
indicators to limit the effect of subjectivity, needs to be balanced against
descriptions that are general enough to be valid for the different
infrastructures. In addition, the interpretation of the data used to rank
the indicators requires subjective judgment, especially when using
qualitative data. In this paper, an indicator-based approach is combined
with an initial quantitative categorisation, based on explicit quantitative
criteria, with the purpose of increasing transparency and reducing the
effect of individual interpretation on the results. The anchoring of the
risk categories in the quantitative categories enables and justifies
the comparison between risk levels resulting from the use of the method for
different scenarios. However, in this study, the quantitative, initial
categorisation of probability and consequence governs the outcome of the
risk analysis, and this categorisation is dependent on the quality of the
background knowledge.</p>
      <p>The weighting system and linear weighted average approach to aggregate the
indicators could be improved and made more sophisticated. However, the level
of sophistication need to be balanced against the user friendliness with
respect to the use of the method and understanding of the results. Linear
averaging (as applied in this method) implicitly assumes that the indicators
are independent of each other and that their influence is independent of the
scoring of other indicators. Accordingly, a high vulnerability associated
with one indicator could be compensated by a low vulnerability associated
with another indicator. This is only partly true. A mixture of geometric and
linear averaging will be considered in further developments of the method,
where (partly) dependent indicators will be averaged geometrically,
e.g. indicators for preparedness and early warning systems. The weighting system
will also be redefined to allow weights that express a larger
difference in importance than the choice between integer weights 1, 2 or 3
does.
These weights were introduced for simplicity, to make the method easy
to use. A possible improvement of the method would be to allow a continuous
range of weights, i.e. in the range between 0 and 1, e.g. as applied by
Kappes et al. (2012) and Nadim et al. (2006). In addition, these weights
could be determined through an analytical hierarchy process, rather
than by direct expert judgment.</p>
      <p>Finally, there are uncertainties associated with the interpretation of the
results, as each risk level corresponds to a range of risks. The uncertainty
within each risk level should be kept in mind when interpreting the results
and comparing risk levels. The accuracy of the method is lower than for a
purely quantitative assessment and cannot be immediately used for
cost–benefit analyses for mitigation strategies. Whenever possible, the
method should be compared with and calibrated against quantitative data from
real events corresponding to the scenario. The probability of infrastructure
malfunctioning obtained by the method could be calibrated against empirical
data on the frequency of infrastructure malfunctioning, where such data exist.
For the socio-economic consequences, however, a calibration is more
difficult, as they refer to indirect consequences and not to a measurable
quantity. The most relevant data for comparison and calibration would be
other estimated data after an occurred event, such as indirect economic
losses or a combination of data on the duration of the infrastructure
malfunctioning and estimated numbers of people affected by the malfunctioning.</p>
</sec>
</sec>
<sec id="Ch1.S6" sec-type="conclusions">
  <title>Conclusions</title>
      <p>This paper shows the development and demonstration of a method for screening
of scenarios posing a potential high risk in terms of stability for the local
society in accordance with the Norwegian guidelines from the Norwegian
Directorate for Civil Protection, DSB (2014). The method is intended to be
the second level of a three-stage methodology for risk assessments, where
level 1 consists of risk identification and level 3 consists of a detailed
quantitative risk analysis. While the proposed methodology could be applied
to all types of natural events and all types of infrastructures, level 3
analyses will, to a larger extent, need to be adapted to the specific
infrastructure and types of hazard. The analysis may be part of a municipal
risk and vulnerability analysis. It can be used on different scales by
adapting the consequence categories and can be adapted to different
infrastructures through the flexible weighting system.</p>
      <p><?xmltex \hack{\newpage}?>The indicator approach and ranking criteria for the physical as well as the
socio-economic indicators make the model easy to use for people
knowledgeable of the municipality and its infrastructures. The proposed
method is seen as a useful screening tool for the identification of the most
critical scenarios and produces results that are easy to understand and to communicate.</p>
      <p>The assessment of potential threats and their related risks, including
the identification of the most critical scenarios, is essential for setting
priorities for more-detailed risk analyses and infrastructure protection.
The risk assessments contribute to targeted investment in planning and design
and facilitate preparedness actions in the event of failure.</p><?xmltex \hack{\clearpage}?>
</sec>

      
      </body>
    <back><app-group>

<app id="App1.Ch1.S1">
  <title>Risk assessment of the demonstration example scenarios</title>
      <p>The description of the assessment of each scenario as well as the explanation of
the ranking is given in the following. Some of the identified scenarios are
scenarios that have already occurred and are expected to occur again. Other
scenarios have not occurred but were considered plausible. For scenarios that already
occurred, observations and newspaper reports were used as data
sources to support the ranking of the indicators. As previously mentioned,
the ranking was performed together with a representative for the
stakeholders and is largely based on experience and local knowledge. The
purpose of the provided information is not to enable the reader to rank the
indicators for the given scenarios, but rather to demonstrate the use of the method.</p>
<sec id="App1.Ch1.S1.SS1">
  <title>Scenario 1: snow avalanche overrunning main road RV 15 at Strynefjellet</title>
      <p>The ranking of this scenario is performed by expert judgment, based on
Kristensen (2005) and observations and records of previous events from the
area. The selected ranking scores for each of the scenarios are given in
parentheses.
<list list-type="order"><list-item><p>Probability assessment:
<list list-type="bullet"><list-item><p><italic>frequency of natural hazard</italic>: every 5 years, i.e. 20 % per year
for the largest snow avalanche. This corresponds to the probability category E in Table 2.</p></list-item></list></p></list-item><list-item><p>Assessment of the physical vulnerability:
<list list-type="bullet"><list-item><p><italic>robustness and buffer capacity</italic>: the road will be closed in
the case of high avalanche danger (4);</p></list-item><list-item><p><italic>level of protection</italic>: some parts of the road are especially
exposed to snow avalanches because of the lack of any physical protection (5);</p></list-item><list-item><p><italic>quality level/age/level of maintenance and renewal</italic>: the road
is relatively old but is satisfactorily maintained (3);</p></list-item><list-item><p><italic>adaptability and quality in operational procedures</italic>: the
infrastructure is operated by an experienced operator (2);</p></list-item><list-item><p><italic>transparency/complexity/degree of coupling</italic>: relatively low degree
of complexity and coupling (2).</p></list-item></list></p></list-item><list-item><p>Socio-economic consequence assessment:
<list list-type="bullet"><list-item><p><italic>number of infrastructure users</italic>: the annual daily traffic (ADT)
is
800 (NPRA, 2012);</p></list-item><list-item><p><italic>duration</italic>: good routines for clearing of the road. Large
avalanche is
duration 2 days, and small avalanche duration is 8 h. The duration can be
longer if the road is closed because of avalanche danger or in combination
with adverse weather.</p></list-item></list></p></list-item></list>
The above-mentioned combination of users and duration qualify for consequence
category 3–4 according to Table 3.</p>
      <p>Assessment of the socio-economic vulnerability:
<list list-type="bullet"><list-item><p><italic>redundancy/substitutes</italic>: alternative roads offer long diversions on
partly avalanche-exposed roads (4);</p></list-item><list-item><p><italic>cascading effects and dependencies</italic>: moderate cascading effects,
mainly economic consequences as there is a high proportion of utility
transportation on the road (3);</p></list-item><list-item><p><italic>preparedness</italic>: very high risk awareness and high level of
preparedness (1);</p></list-item><list-item><p><italic>early warning, emergency response and measures:</italic> early warning and
closure of the road can act as a measure to save human lives but does not
prevent the economic consequences of the road closure (5).</p></list-item></list></p>
</sec>
<sec id="App1.Ch1.S1.SS2">
  <title>Scenario 2: debris flow reaching Innvik waterworks</title>
      <p>The ranking is performed by expert judgment, based on observations from a
similar historic event in 2014 and information given in the reports from DSB (2015b)
and past Stryn kommune Rådmannsavdelinga (2014). The selected
ranking scores for each of the scenarios are given in parentheses.
<list list-type="order"><list-item><p>Probability assessment:
<list list-type="bullet"><list-item><p><italic>frequency of natural hazard</italic>: once per 10–50 years, i.e. probability
category D according to Table 2.</p></list-item></list></p></list-item><list-item><p>Assessment of the physical vulnerability:
<list list-type="bullet"><list-item><p><italic>robustness and buffer capacity</italic>: the waterworks can
withstand moderate intensities of debris flows (3);</p></list-item><list-item><p><italic>level of protection</italic>: partially protected from debris flows (3);</p></list-item><list-item><p><italic>quality level/age/level of maintenance and renewal</italic>: medium age,
satisfactory renewal and maintenance (3);</p></list-item><list-item><p><italic>adaptability and quality in operational procedures</italic>:
operated by an experienced operator, with the ability to adapt to changing framing
conditions (2);</p></list-item><list-item><p><italic>transparency/complexity/degree of coupling</italic>: system with large
complexity and many interdependencies (4).</p></list-item></list></p></list-item><list-item><p>Socio-economic consequence assessment:
<list list-type="bullet"><list-item><p><italic>number of infrastructure users</italic>: 250;</p></list-item><list-item><p><italic>duration</italic>: 2–7 days.</p></list-item></list></p></list-item></list>
The above-mentioned combination of users and duration qualify for consequence
category 4 according to Table 3.</p>
      <p><?xmltex \hack{\newpage}?>Assessment of the socio-economic vulnerability:
<list list-type="bullet"><list-item><p><italic>redundancy/substitutes</italic>: water can be delivered with a tank lorry, but
at some point after the event the water needs to be boiled to obtain
drinking water quality (3);</p></list-item><list-item><p><italic>cascading effects and dependencies</italic>: moderate cascading effects (3);</p></list-item><list-item><p><italic>preparedness</italic>: some risk awareness and simple emergency response plans (3);</p></list-item><list-item><p><italic>early warning, emergency response and measures</italic>: limited
possibilities for warning (3).</p></list-item></list></p>
</sec>
<sec id="App1.Ch1.S1.SS3">
  <title>Scenario 3: snow avalanche overrunning main road 724 to Oldedalen</title>
      <p>The ranking is performed by expert judgment, based on observations from
similar historic events. The selected ranking scores for each of the scenarios
are given in parentheses.
<list list-type="order"><list-item><p>Probability assessment:
<list list-type="bullet"><list-item><p><italic>frequency of natural hazard</italic>: more often than once every 10 years,
i.e. probability category E according to Table 2.</p></list-item></list></p></list-item><list-item><p>Assessment of the physical vulnerability:
<list list-type="bullet"><list-item><p><italic>robustness and buffer capacity</italic>: the road will be closed in the case of high avalanche danger (4);</p></list-item><list-item><p><italic>level of protection</italic>: only partial physical protection against snow
avalanches (5);</p></list-item><list-item><p><italic>quality level/age/level of maintenance and renewal</italic>: the road has a
relatively high age but is satisfactorily maintained (3);</p></list-item><list-item><p><italic>adaptability and quality in operational procedures</italic>: infrastructure
is operated by an experienced operator (2);</p></list-item><list-item><p><italic>transparency/complexity/degree of coupling</italic>: low degree of coupling. (2).</p></list-item></list></p></list-item><list-item><p>Socio-economic consequences:
<list list-type="bullet"><list-item><p><italic>number of infrastructure users</italic>: 100;</p></list-item><list-item><p><italic>duration</italic>: 1–2 days.</p></list-item></list></p></list-item></list>
The above-mentioned combination of users and duration qualify for consequence
category 2 according to Table 3.</p>
      <p>Assessment of the socio-economic vulnerability:
<list list-type="bullet"><list-item><p><italic>redundancy/substitutes</italic>: no alternative roads to Oldedalen (5);</p></list-item><list-item><p><italic>cascading effects and dependencies</italic>: moderate cascading effects,
which would affect utility transportation of the Olden mineral water producer (3);</p></list-item><list-item><p><italic>preparedness</italic>: high risk awareness and preparedness regarding snow
avalanches (2);</p></list-item><list-item><p><italic>early warning, emergency response and measures</italic>: limited
possibilities and risk-reducing effects of a warning (3).</p></list-item></list></p>
</sec>
<sec id="App1.Ch1.S1.SS4">
  <title>Scenario 4: storm leading to failure in electricity distribution and communication to the municipal centre</title>
      <p>The ranking is performed by expert judgment, partly based on observations
from a similar historic event in December 2011. The selected ranking score
for each of the scenarios are given in parentheses.
<list list-type="order"><list-item><p>Probability assessment:
<list list-type="bullet"><list-item><p><italic>frequency of natural hazard</italic>: severe storms more than once every
10 years. Consideration of historic frequency of storms and an increase in
frequency due to climate change suggests a probability category E in Table 2.</p></list-item></list></p></list-item><list-item><p>Assessment of the physical vulnerability:
<list list-type="bullet"><list-item><p><italic>robustness and buffer capacity</italic>: electricity network could withstand
storms for some time (3);</p></list-item><list-item><p><italic>level of protection</italic>: partially protected and well adapted to
current climate, but not to future climate (3);</p></list-item><list-item><p><italic>quality level/age/level of maintenance and renewal</italic>: increasing age
of the components in the electricity network in Norway in general (Fridheim
et al., 2009) (3);</p></list-item><list-item><p><italic>adaptability and quality in operational procedures</italic>: some ability to
adapt to changing framing conditions (3);</p></list-item><list-item><p><italic>transparency/complexity/degree of coupling</italic>: low degree of coupling (2).</p></list-item></list></p></list-item><list-item><p>Socio-economic consequences:
<list list-type="bullet"><list-item><p><italic>number of infrastructure users</italic>: population in Stryn municipal
centre is 2372 and a large number could be potentially affected;</p></list-item><list-item><p><italic>duration</italic>: 2–7 days.</p></list-item></list></p></list-item></list>
The above-mentioned combination of users and duration qualify for consequence
category 5 according to Table 3.</p>
      <p>Assessment of the socio-economic vulnerability:
<list list-type="bullet"><list-item><p><italic>redundancy/substitutes</italic>: there exists alternative energy
distribution, for example, for critical care facilities, but not for the whole municipality (4);</p></list-item><list-item><p><italic>cascading effects and dependencies</italic>: considerable importance for
societal function (4);</p></list-item><list-item><p><italic>preparedness</italic>: some risk awareness and preparedness regarding storms (3);</p></list-item><list-item><p><italic>early warning, emergency response and measures</italic>: storms could be
warned, but mitigation actions could potentially only have a small reduction
effect on the consequences (3).</p></list-item></list></p>
</sec>
<sec id="App1.Ch1.S1.SS5">
  <title>Scenario 5: landslide overrunning main road E39 at Skredestranda</title>
      <p>The ranking is performed by expert judgment, based on observations from
previous historic events, e.g. in November 2015. The selected ranking scores for
each of the scenarios are given in parentheses.
<list list-type="order"><list-item><p>Probability assessment:
<list list-type="bullet"><list-item><p><italic>frequency of natural hazard</italic>: more often than once every 10 years,
with probability category E according to Table 2. (This scenario occurred twice in 2015.)</p></list-item></list></p></list-item><list-item><p>Assessment of the physical vulnerability:
<list list-type="bullet"><list-item><p><italic>robustness and buffer capacity</italic>: the road will be closed in case of
a landslide of the considered size (4);</p></list-item><list-item><p><italic>level of protection</italic>: to a large extent exposed to the event (4);</p></list-item><list-item><p><italic>quality level/age/level of maintenance and renewal</italic>: well-maintained
road (2);</p></list-item><list-item><p><italic>adaptability and quality in operational procedures</italic>: some ability to
adapt to changing framing conditions (3);</p></list-item><list-item><p><italic>transparency/complexity/degree of coupling</italic>: low degree of coupling (2).</p></list-item></list></p></list-item><list-item><p>Socio-economic consequences:
<list list-type="bullet"><list-item><p><italic>number of infrastructure users</italic>: <inline-formula><mml:math id="M38" display="inline"><mml:mo>&gt;</mml:mo></mml:math></inline-formula> 1000 (NPRA, 2011);</p></list-item><list-item><p><italic>duration</italic>: 2–7 days.</p></list-item></list></p></list-item></list>
The above-mentioned combination of users and duration qualify for consequence
category 5 according to Table 3.</p>
      <p>Assessment of the socio-economic vulnerability:
<list list-type="bullet"><list-item><p><italic>redundancy/substitutes</italic>: alternative roads imply major delays (4);</p></list-item><list-item><p><italic>cascading effects and dependencies</italic>: moderate importance for
socio-economic functions (3);</p></list-item><list-item><p><italic>preparedness</italic>: high risk awareness and preparedness regarding snow
avalanches (2);</p></list-item><list-item><p><italic>early warning, emergency response and measures</italic>: limited
possibilities and risk-reduction effects of warning (3).</p></list-item></list></p><?xmltex \hack{\newpage}?>
</sec>
<sec id="App1.Ch1.S1.SS6">
  <title>Scenario 6: ice jam breakup in the Storelva river in Hornindal and failure in sewage system</title>
      <p>The ranking is performed by expert judgment, partly based on observations
from similar historical events. The selected ranking scores for each of the
scenarios are given in parentheses.
<list list-type="order"><list-item><p>Probability assessment:
<list list-type="bullet"><list-item><p><italic>frequency of natural hazard</italic>: every 10–50 years, i.e. probability
category D according to Table 2.</p></list-item></list></p></list-item><list-item><p>Assessment of the physical vulnerability:
<list list-type="bullet"><list-item><p><italic>robustness and buffer capacity</italic>: quite robust, could withstand the
event for some time (2);</p></list-item><list-item><p><italic>level of protection</italic>: partially protected (3);</p></list-item><list-item><p><italic>quality level/age/level of maintenance and renewal</italic>: well maintained (2);</p></list-item><list-item><p><italic>adaptability and quality in operational procedures</italic>: experienced
operator, ability to adapt to changing framing conditions (2);</p></list-item><list-item><p><italic>transparency/complexity/degree of coupling</italic>: low degree of coupling (2).</p></list-item></list></p></list-item><list-item><p>Socio-economic consequences:
<list list-type="bullet"><list-item><p><italic>number of infrastructure users</italic>: 800;</p></list-item><list-item><p><italic>duration</italic>: 2–7 days.</p></list-item></list></p></list-item></list>
The above-mentioned combination of users and duration qualify for consequence
category 4 according to Table 3.</p>
      <p>Assessment of the socio-economic vulnerability:
<list list-type="bullet"><list-item><p><italic>redundancy/substitutes</italic>: alternatives which imply disadvantages (3);</p></list-item><list-item><p><italic>cascading effects and dependencies</italic>: moderate cascading effects (3);</p></list-item><list-item><p><italic>preparedness</italic>: some risk awareness (3);</p></list-item><list-item><p><italic>early warning, emergency response and measures</italic>: routines for
warning and implementation of measures exist (2).</p></list-item></list></p>
</sec>
<sec id="App1.Ch1.S1.SS7">
  <title>Scenario 7: storm leading to the closure of the ferry service between Anda and Lote</title>
      <p>The ranking is performed by expert judgment, based on observations from
previous occurrences of this scenario and on information from Stryn kommune
Rådmannsavdelinga (2014). The selected ranking scores for each of the
scenarios are given in parentheses.
<?xmltex \hack{\newpage}?>
<list list-type="order"><list-item><p>Probability assessment:
<list list-type="bullet"><list-item><p><italic>frequency of natural hazard</italic>: more than once every 10th year,
with
probability category E according to Table 2.</p></list-item></list></p></list-item><list-item><p>Assessment of the physical vulnerability:
<list list-type="bullet"><list-item><p><italic>robustness and buffer capacity</italic>: the ferries can operate in strong
winds and relatively high waves (3);</p></list-item><list-item><p><italic>level of protection</italic>: to some extent exposed, but well adapted to
current climate (3);</p></list-item><list-item><p><italic>quality level/age/level of maintenance and renewal</italic>: well maintained (2);</p></list-item><list-item><p><italic>adaptability and quality in operational procedures</italic>: experienced
operator, with some ability to adapt to changing framing conditions (3);</p></list-item><list-item><p><italic>transparency/complexity/degree of coupling</italic>: low degree of coupling (2).</p></list-item></list>
<?xmltex \hack{\newpage}?></p></list-item><list-item><p>Socio-economic consequences:
<list list-type="bullet"><list-item><p><italic>number of infrastructure users</italic>: 100;</p></list-item><list-item><p><italic>duration:</italic> 1–2 days.</p></list-item></list></p></list-item></list>
The above-mentioned combination of users and duration qualify for consequence
category 2 according to Table 3.</p>
      <p>Assessment of the socio-economic vulnerability:
<list list-type="bullet"><list-item><p><italic>redundancy/substitutes</italic>: travellers can use alternative roads with
small delays (2);</p></list-item><list-item><p><italic>cascading effects and dependencies</italic>: moderate cascading effects (3);</p></list-item><list-item><p><italic>preparedness</italic>: emergency response plans are available (3);</p></list-item><list-item><p><italic>early warning, emergency response and measures</italic>: routines for
warning and implementation of measures to limit the consequences exist (2).</p></list-item></list></p><?xmltex \hack{\clearpage}?>
</sec>
</app>
  </app-group><notes notes-type="competinginterests">

      <p>The authors declare that they have no conflict of interest.</p>
  </notes><notes notes-type="disclaimer">

      <p>The information and views set out in this paper are those of the
author(s) and do not necessarily reflect the official opinion of the European Union.
Neither the European Union institutions and bodies nor any person acting on
their behalf may be held responsible for the use which may be made of the
information contained therein. Reproduction is authorised provided the
source is acknowledged.</p>
  </notes><ack><title>Acknowledgements</title><p>The work described in this paper was supported by the Strategic Project GRAM
(GeoRisk Assessment and Management) at NGI. The research leading to these
results has also received funding from the European Union Seventh Framework
Programme (FP7/2007-2013) under grant agreement no. 606799. The support is
gratefully acknowledged. <?xmltex \hack{\newline}?><?xmltex \hack{\newline}?>
Edited by: M. Keiler <?xmltex \hack{\newline}?>
Reviewed by: M. Papathoma-Koehle and one anonymous referee</p></ack><ref-list>
    <title>References</title>

      <ref id="bib1.bib1"><label>1</label><mixed-citation>Birkmann, J., Cardona, O. D., Carreno, M. L., Barbat, A. H., Pelling, M.,
Schneiderbauer, S., Kienberger, S., Keiler, M., Alexander, D., Zeil, P., and
Welle, T.: Framing vulnerability, risk and societal responses: the MOVE framework,
Nat. Hazards, 67, 193–211, <ext-link xlink:href="http://dx.doi.org/10.1007/s11069-013-0558-5" ext-link-type="DOI">10.1007/s11069-013-0558-5</ext-link>, 2013.</mixed-citation></ref>
      <ref id="bib1.bib2"><label>2</label><mixed-citation>
Bouchon, S.: The Vulnerability of interdependent Critical Infrastructures Systems:
Epistemological and Conceptual State-of-the-Art, EUR 22205 EN, European Commission
Directorate, General Joint Research Centre Institute for the Protection and
Security of the Citizen, Ispra, Italy, 2006.</mixed-citation></ref>
      <ref id="bib1.bib3"><label>3</label><mixed-citation>Bowles D., Brown, A., Hughes, A., Morris, M., Sayers, P., Topple, A., Wallis,
M., and Gardiner, K.: Guide to risk assessment for reservoir safety management,
Vol. 2: Methodology and supporting information, Report – SC090001/R2, Environment
Agency, Bristol, UK, available at: <uri>https://www.gov.uk/government/publications/guide-to-risk-assessment-for-reservoir-safety-management</uri>
(last access: 18 November 2015), 2013.</mixed-citation></ref>
      <ref id="bib1.bib4"><label>4</label><mixed-citation>Committee on Assessing the Costs of Natural Disasters: The impacts of natural
disasters: a framework for loss estimation, committee on assessing the costs
of natural disasters, National Research Council, Washington, USA,
<uri>http://www.nap.edu/catalog/6425.html</uri> (last access: 15 January 2017), 1999.</mixed-citation></ref>
      <ref id="bib1.bib5"><label>5</label><mixed-citation>Corominas, J., van Westen, C., Frattini, P., Cascini, L., Malet, J.-P., Fotopoulou,
S., Catani, F., Van Den Eeckhaut, M., Mavrouli, O., Agliardi, F., Pitilakis, K.,
Winter, M. G., Pastor, M., Ferlisi, S., Tofani, V., Hervás, J., and Smith,
J. T.: Recommendations for the quantitative analysis of landslide risk, Bull.
Eng. Geol. Environ., 73, 209–263, <ext-link xlink:href="http://dx.doi.org/10.1007/s10064-013-0538-8" ext-link-type="DOI">10.1007/s10064-013-0538-8</ext-link>, 2014.</mixed-citation></ref>
      <ref id="bib1.bib6"><label>6</label><mixed-citation>
Cutter, S. L., Barnes, L., Berry, M., Burton, C., Evans, E., Tate, E., and Webb,
J.: A place-based model for understanding community resilience to natural
disasters, Global Environ. Change 18, 598–606, 2008.</mixed-citation></ref>
      <ref id="bib1.bib7"><label>7</label><mixed-citation>Department for Communities and Local Government: Multi-criteria analysis: a
manual, London, <uri>http://www.communities.gov.uk</uri> (last access: 26 September 2016), 2009.</mixed-citation></ref>
      <ref id="bib1.bib8"><label>8</label><mixed-citation>DSB: Veileder for helhetlig risiko- og sårbarhetsanalyse i kommunen,
Tønsberg, Norway, available at: <uri>https://www.dsb.no/globalassets/dokumenter/risiko-sarbarhet-og-beredskap/pdf-er/20156984-helhetlig-ros-final-web-ny.pdf</uri>,
last access: 25 November 2014.</mixed-citation></ref>
      <ref id="bib1.bib9"><label>9</label><mixed-citation>DSB: Veiledning til forskrift om kommunal beredskapsplikt, Tønsberg, Norway,
available at: <uri>https://www.dsb.no/globalassets/dokumenter/risiko-sarbarhet-og-beredskap/pdf-er/veileder-forskrift-kommunal-beredskapsplikt.pdf</uri>
(last access: 6 September 2016), 2015a.</mixed-citation></ref>
      <ref id="bib1.bib10"><label>10</label><mixed-citation>DSB: Evaluering av forebygging og håndtering av flommen på Vestlandet
høsten 2014, Tønsberg, Norway, available at: <uri>http://www.dsbinfo.no/DSBno/2015/Rapport/Evalueringflomvestlandet2014/?Page=17</uri>
(last access: 19 February 2016), 2015b.</mixed-citation></ref>
      <ref id="bib1.bib11"><label>11</label><mixed-citation>Fakta om Stryn: <uri>https://stryn.kommune.no/Artikkel.aspx?AId=47&amp;back=1&amp;MId1=798&amp;MId2=&amp;MId3=&amp;</uri>,
last access: 27 February 2017.</mixed-citation></ref>
      <ref id="bib1.bib12"><label>12</label><mixed-citation>Federal Ministry of the Interior: Protecting Critical Infrastructures – Risk
and Crisis Management A guide for companies and government authorities, Federal
Ministry of the Interior, Berlin, Germany, available at: <uri>http://www.bmi.bund.de</uri>
(last access: 16 October 2014), 2008.</mixed-citation></ref>
      <ref id="bib1.bib13"><label>13</label><mixed-citation>Fridheim, H., Røstum, J., Kjølle, G., Bertelsen, D., Tøndel, I. A.,
Vatn, J., Vatn, G. Å., and Utne, I.: DECRIS – Problemstillinger rundt
tversektorielle risikoanalyser. Kritisk infrastruktur, DECRIS arbeidsnotat 1,
available at: <uri>http://www.sintef.no/globalassets/project/samrisk/decris/documents/arbeidsnotat-1-problemstillinger-kritisk-infrastruktur.pdf</uri>
(last access: 24 October 2014), 2009.</mixed-citation></ref>
      <ref id="bib1.bib14"><label>14</label><mixed-citation>Giannopoulos, G., Filippini, R., and Schimmer, M.: Risk assessment methodologies
for Critical Infrastructure Protection. Part I: A state of the art, JRC Technical
Notes, Publications Office of the European Union, Luxembourg, p. 53, <ext-link xlink:href="http://dx.doi.org/10.2788/22260" ext-link-type="DOI">10.2788/22260</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib15"><label>15</label><mixed-citation>Grothmann, T., Grecksch, K., Winges, M., and Siebenhüner, B.: Assessing
institutional capacities to adapt to climate change: integrating psychological
dimensions in the Adaptive Capacity Wheel, Nat. Hazards Earth Syst. Sci.,
13, 3369–3384, <ext-link xlink:href="http://dx.doi.org/10.5194/nhess-13-3369-2013" ext-link-type="DOI">10.5194/nhess-13-3369-2013</ext-link>, 2013.</mixed-citation></ref>
      <ref id="bib1.bib16"><label>16</label><mixed-citation>Hanssen-Bauer, I., Førland, E. J., Haddeland, I., Hisdal, H., Mayer, S.,
Nesje, A., Nilsen, J. E. Ø., Sandven, S., Sandø, A. B., Sorteberg, A.,
and Ådlandsvik, B.: Klima i Norge 2100 Kunnskapsgrunnlag for klimatilpasning
oppdatert i 2015, NCCS report no. 2/2015, Norsk klimaservicesenter (NKSS),
available at: <uri>https://klimaservicesenter.no/</uri> (last access: 11 March 2016), 2015.</mixed-citation></ref>
      <ref id="bib1.bib17"><label>17</label><mixed-citation>
IEC/FDIS 31010:2009(E): Risk management – Risk assessment techniques, International
ISO and IEC standard, Geneva, Switzerland, 2009.</mixed-citation></ref>
      <ref id="bib1.bib18"><label>18</label><mixed-citation>Institute of Operational Risk: Operational Risk Sound Practice Guidance, Key
Risk Indicators, The Institute of Operational Risk (IOR), available at:
<uri>https://www.ior-institute.org/</uri> (last access: 20 January 2017), 2010.</mixed-citation></ref>
      <ref id="bib1.bib19"><label>19</label><mixed-citation>
IRGC – International Risk Governance Council: Policy brief on Managing and
reducing social vulnerabilities from coupled critical infrastructures, Geneva, 2007.</mixed-citation></ref>
      <ref id="bib1.bib20"><label>20</label><mixed-citation>ISSMGE Glossary of Risk Assessment Terms: listed on TC304 web page:
<uri>http://140.112.12.21/issmge/2004Glossary_Draft1.pdf</uri> (last access: 19 October 2016), 2004.</mixed-citation></ref>
      <ref id="bib1.bib21"><label>21</label><mixed-citation>JRC: Handbook on Constructing Composite Indicators, Methodology and user guide,
OECD, available at: <uri>http://www.oecd.org/std/leading-indicators/42495745.pdf</uri>
(last access: 15 October 2010), 2008.</mixed-citation></ref>
      <ref id="bib1.bib22"><label>22</label><mixed-citation>
Kappes, M. S., Papathoma-Köhle, M., and Keiler, M.: Assessing physical
vulnerability for multi-hazards using an indicator-based methodology, Appl.
Geogr., 32, 577–590, 2012.</mixed-citation></ref>
      <ref id="bib1.bib23"><label>23</label><mixed-citation>
Kristensen, K.: Rv. 15 i Grasdalen Skredforhold ved Riksveg 15 gjennom Grasdalen,
Strynefjellet, Arbeidsgruppa for Rv15 – skredsikring av Strynefjellet, NGI
report 20051040-1, NGI, Oslo, Norway, 2005.</mixed-citation></ref>
      <ref id="bib1.bib24"><label>24</label><mixed-citation>Kröger, W.: Critical infrastructures at risk: A need for a new conceptual
approach and extended analytical tools, Reliab. Eng. Syst. Saf., 93, 1781–1787,
<ext-link xlink:href="http://dx.doi.org/10.1016/j.ress.2008.03.005" ext-link-type="DOI">10.1016/j.ress.2008.03.005</ext-link>, 2008.</mixed-citation></ref>
      <ref id="bib1.bib25"><label>25</label><mixed-citation>Kröger, W. and Zio, E.: Vulnerable Systems, Springer-Verlag, London,
<ext-link xlink:href="http://dx.doi.org/10.1007/978-0-85729-655-9" ext-link-type="DOI">10.1007/978-0-85729-655-9</ext-link>, 2011.</mixed-citation></ref>
      <ref id="bib1.bib26"><label>26</label><mixed-citation>Lenz, S.: Vulnerabilität Kritischer Infrastrukturen, Forschung im
Bevölkerungsschutz, Bundesamt für Bevölkerungsschutz und
Katastrophenhilfe, Bonn, available at: <uri>http://www.bbk.bund.de/SharedDocs/Downloads/BBK/DE/Publikationen/PublikationenForschung/FiB_Band4.pdf?__blob=publicationFile</uri>
(last access: 17 September 2015), 2009.</mixed-citation></ref>
      <ref id="bib1.bib27"><label>27</label><mixed-citation>Liu, Z., Nadim, F., Garcia-Aristizabal, A., Mignan, A., Fleming, K., and
Quan Luna, B.: A three-level framework for multi-risk assessment, Georisk,
9, 59–74, <ext-link xlink:href="http://dx.doi.org/10.1080/17499518.2015.1041989" ext-link-type="DOI">10.1080/17499518.2015.1041989</ext-link>, 2015.</mixed-citation></ref>
      <ref id="bib1.bib28"><label>28</label><mixed-citation>Merz, B., Kreibich, H., Schwarze, R., and Thieken, A.: Review article “Assessment
of economic flood damage”, Nat. Hazards Earth Syst. Sci., 10, 1697–1724,
<ext-link xlink:href="http://dx.doi.org/10.5194/nhess-10-1697-2010" ext-link-type="DOI">10.5194/nhess-10-1697-2010</ext-link>, 2010.</mixed-citation></ref>
      <ref id="bib1.bib29"><label>29</label><mixed-citation>Meyer, V., Becker, N., Markantonis, V., Schwarze, R., van den Bergh, J. C. J. M.,
Bouwer, L. M., Bubeck, P., Ciavola, P., Genovese, E., Green, C., Hallegatte, S.,
Kreibich, H., Lequeux, Q., Logar, I., Papyrakis, E., Pfurtscheller, C., Poussin,
J., Przyluski, V., Thieken, A. H., and Viavattene, C.: Review article: Assessing
the costs of natural hazards – state of the art and knowledge gaps, Nat. Hazards
Earth Syst. Sci., 13, 1351–1373, <ext-link xlink:href="http://dx.doi.org/10.5194/nhess-13-1351-2013" ext-link-type="DOI">10.5194/nhess-13-1351-2013</ext-link>, 2013.</mixed-citation></ref>
      <ref id="bib1.bib30"><label>30</label><mixed-citation>
Nadim, F., Kjekstad, O., Peduzzi, P., Herold, C., and Jaedicke, C.: Global
landslide and avalanche hotspots, Landslides, 3, 159–174, 2006.</mixed-citation></ref>
      <ref id="bib1.bib31"><label>31</label><mixed-citation>National Academy of Sciences: Disaster Resilience: A National Imperative, The
National Academies Press, Washington, D.C., available at: <uri>https://www.ncbi.nlm.nih.gov/books/NBK285736/</uri>
(last access: 17 September 2015), 2012.
</mixed-citation></ref><?xmltex \hack{\newpage}?>
      <ref id="bib1.bib32"><label>32</label><mixed-citation>NPRA – Norwegian Public Roads Administration: Konseptvalutgreiing E39 Skei – Ålesund,
Report, Region Vest, Region Midt, available at: <uri>http://www.vegvesen.no/Europaveg/e39skeiaalesund</uri>
(last access: 26 September 2016), 2011.</mixed-citation></ref>
      <ref id="bib1.bib33"><label>33</label><mixed-citation>NPRA – Norwegian Public Roads Administration: KVU Rv. 15 Strynefjellet, Report,
Region vest, Styring og strategistab, available at: <uri>http://www.vegvesen.no/_attachment/326969/binary/589809</uri>
(last access: 26 September 2016), 2012.</mixed-citation></ref>
      <ref id="bib1.bib34"><label>34</label><mixed-citation>Oboni, F. and Oboni, C.: What you need to know about risk management methods,
Is it true that PIGs fly when evaluating risks of projects, operations, and
corporations?, White paper, Riskope International, Froideville, Switzerland,
available at: <uri>http://www.riskope.com/wp-content/uploads/2013/06/Riskope-White-Paper.pdf</uri>
(last access: 9 October 2015), 2013.</mixed-citation></ref>
      <ref id="bib1.bib35"><label>35</label><mixed-citation>
Ouyang, M.: Review on modeling and simulation of interdependent critical
infrastructure systems, Reliab. Eng. Syst. Saf., 121 43–60, 2014.</mixed-citation></ref>
      <ref id="bib1.bib36"><label>36</label><mixed-citation>
Perrow, C.: Normal Accidents: Living with High-Risk Technologies, Basic Books, New York, 1984.</mixed-citation></ref>
      <ref id="bib1.bib37"><label>37</label><mixed-citation>
Pescaroli, G. and Alexander, D.: A definition of cascading disasters and
cascading effects: Going beyond the “toppling dominos” metaphor, in:
Planet@Risk, Global Risk Forum GRF Davos, Davos, 58–67, 2015.</mixed-citation></ref>
      <ref id="bib1.bib38"><label>38</label><mixed-citation>Rinaldi, S. M., Peerenboom, J. P., and Kelly, T. K.: Identifying, understanding,
and analysing critical infrastructure interdependencies, in: IEE Control
Systems Magazine, 11–25, available at: <uri>http://user.it.uu.se/~bc/Art.pdf</uri>
(last access: 2 October 2012), 2001.</mixed-citation></ref>
      <ref id="bib1.bib39"><label>39</label><mixed-citation>Solano, E.: Methods for Assessing Vulnerability of Critical Infrastructure.
Research Brief by Institute for Homeland Security Solutions, March 2010, p. 8,
available at: <uri>https://pdfs.semanticscholar.org/42bb/cb145680d7cefe924c1c4439ce7d002ead26.pdf</uri>
(last access: 12 June 2014), 2010.</mixed-citation></ref>
      <ref id="bib1.bib40"><label>40</label><mixed-citation>
Stryn kommune Rådmannsavdelinga: Notat om: ROS-analyse for Stryn og Hornindal
kommunar, Dok. Ref. 13/711-18/K1-233,K2-X20//HAR, Stryn, Norway, 2014.</mixed-citation></ref>
      <ref id="bib1.bib41"><label>41</label><mixed-citation>Vatn, J., Utne, I. B., Vatn, G. Å., and Hokstad, P.: DECRIS – Beskrivelse
av grovanalyse-metodikk, DECRIS arbeidsnotat 4, deliverable of the SAMRISK
project, available at: <uri>http://www.sintef.no/globalassets/project/samrisk/decris/documents/arbeidsnotat-4-metodikk-for-grovanalyse.pdf</uri>
(last access: 9 October 2014), 2009.</mixed-citation></ref>
      <ref id="bib1.bib42"><label>42</label><mixed-citation>
Yusta, J. M., Correa, G. J., and Lacal-Arántegui, R.: Methodologies and
applications for critical infrastructure protection: State-of-the-art, Energy
Policy, 39, 6100–6119, 2011.</mixed-citation></ref>

  </ref-list><app-group content-type="float"><app><title/>

    </app></app-group></back>
    <!--<article-title-html>Assessing the risk posed by natural hazards to infrastructures</article-title-html>
<abstract-html><p class="p">This paper proposes a model for assessing the risk posed
by natural hazards to infrastructures, with a focus on the indirect losses and
loss of stability for the population relying on the infrastructure. The
model prescribes a three-level analysis with increasing level of detail,
moving from qualitative to quantitative analysis. The focus is on a
methodology for semi-quantitative analyses to be performed at the second
level. The purpose of this type of analysis is to perform a screening of the
scenarios of natural hazards threatening the infrastructures, identifying
the most critical scenarios and investigating the need for further analyses
(third level). The proposed semi-quantitative methodology considers the
frequency of the natural hazard, different aspects of vulnerability,
including the physical vulnerability of the infrastructure itself, and the
societal dependency on the infrastructure. An indicator-based approach is
applied, ranking the indicators on a relative scale according to pre-defined
ranking criteria. The proposed indicators, which characterise conditions
that influence the probability of an infrastructure malfunctioning caused by
a natural event, are defined as (1) robustness and buffer capacity, (2) level
of protection, (3) quality/level of maintenance and renewal, (4) adaptability
and quality of operational procedures and (5) transparency/complexity/degree
of coupling. Further indicators describe conditions influencing the
socio-economic consequences of the infrastructure malfunctioning, such as
(1) redundancy and/or substitution, (2) cascading effects and dependencies,
(3) preparedness and (4) early warning, emergency response and measures. The
aggregated risk estimate is a combination of the semi-quantitative
vulnerability indicators, as well as quantitative estimates of the frequency
of the natural hazard, the potential duration of the infrastructure
malfunctioning (e.g. depending on the required restoration effort) and the
number of users of the infrastructure.</p><p class="p">Case studies for two Norwegian municipalities are presented for
demonstration purposes, where risk posed by adverse weather and natural
hazards to primary road, water supply and power networks is assessed. The
application examples show that the proposed model provides a useful tool for
screening of potential undesirable events, contributing to a targeted
reduction of the risk.</p></abstract-html>
<ref-html id="bib1.bib1"><label>1</label><mixed-citation>
Birkmann, J., Cardona, O. D., Carreno, M. L., Barbat, A. H., Pelling, M.,
Schneiderbauer, S., Kienberger, S., Keiler, M., Alexander, D., Zeil, P., and
Welle, T.: Framing vulnerability, risk and societal responses: the MOVE framework,
Nat. Hazards, 67, 193–211, <a href="http://dx.doi.org/10.1007/s11069-013-0558-5" target="_blank">doi:10.1007/s11069-013-0558-5</a>, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib2"><label>2</label><mixed-citation>
Bouchon, S.: The Vulnerability of interdependent Critical Infrastructures Systems:
Epistemological and Conceptual State-of-the-Art, EUR 22205 EN, European Commission
Directorate, General Joint Research Centre Institute for the Protection and
Security of the Citizen, Ispra, Italy, 2006.
</mixed-citation></ref-html>
<ref-html id="bib1.bib3"><label>3</label><mixed-citation>
Bowles D., Brown, A., Hughes, A., Morris, M., Sayers, P., Topple, A., Wallis,
M., and Gardiner, K.: Guide to risk assessment for reservoir safety management,
Vol. 2: Methodology and supporting information, Report – SC090001/R2, Environment
Agency, Bristol, UK, available at: <a href="https://www.gov.uk/government/publications/guide-to-risk-assessment-for-reservoir-safety-management" target="_blank">https://www.gov.uk/government/publications/guide-to-risk-assessment-for-reservoir-safety-management</a>
(last access: 18 November 2015), 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib4"><label>4</label><mixed-citation>
Committee on Assessing the Costs of Natural Disasters: The impacts of natural
disasters: a framework for loss estimation, committee on assessing the costs
of natural disasters, National Research Council, Washington, USA,
<a href="http://www.nap.edu/catalog/6425.html" target="_blank">http://www.nap.edu/catalog/6425.html</a> (last access: 15 January 2017), 1999.
</mixed-citation></ref-html>
<ref-html id="bib1.bib5"><label>5</label><mixed-citation>
Corominas, J., van Westen, C., Frattini, P., Cascini, L., Malet, J.-P., Fotopoulou,
S., Catani, F., Van Den Eeckhaut, M., Mavrouli, O., Agliardi, F., Pitilakis, K.,
Winter, M. G., Pastor, M., Ferlisi, S., Tofani, V., Hervás, J., and Smith,
J. T.: Recommendations for the quantitative analysis of landslide risk, Bull.
Eng. Geol. Environ., 73, 209–263, <a href="http://dx.doi.org/10.1007/s10064-013-0538-8" target="_blank">doi:10.1007/s10064-013-0538-8</a>, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib6"><label>6</label><mixed-citation>
Cutter, S. L., Barnes, L., Berry, M., Burton, C., Evans, E., Tate, E., and Webb,
J.: A place-based model for understanding community resilience to natural
disasters, Global Environ. Change 18, 598–606, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib7"><label>7</label><mixed-citation>
Department for Communities and Local Government: Multi-criteria analysis: a
manual, London, <a href="http://www.communities.gov.uk" target="_blank">http://www.communities.gov.uk</a> (last access: 26 September 2016), 2009.
</mixed-citation></ref-html>
<ref-html id="bib1.bib8"><label>8</label><mixed-citation>
DSB: Veileder for helhetlig risiko- og sårbarhetsanalyse i kommunen,
Tønsberg, Norway, available at: <a href="https://www.dsb.no/globalassets/dokumenter/risiko-sarbarhet-og-beredskap/pdf-er/20156984-helhetlig-ros-final-web-ny.pdf" target="_blank">https://www.dsb.no/globalassets/dokumenter/risiko-sarbarhet-og-beredskap/pdf-er/20156984-helhetlig-ros-final-web-ny.pdf</a>,
last access: 25 November 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib9"><label>9</label><mixed-citation>
DSB: Veiledning til forskrift om kommunal beredskapsplikt, Tønsberg, Norway,
available at: <a href="https://www.dsb.no/globalassets/dokumenter/risiko-sarbarhet-og-beredskap/pdf-er/veileder-forskrift-kommunal-beredskapsplikt.pdf" target="_blank">https://www.dsb.no/globalassets/dokumenter/risiko-sarbarhet-og-beredskap/pdf-er/veileder-forskrift-kommunal-beredskapsplikt.pdf</a>
(last access: 6 September 2016), 2015a.
</mixed-citation></ref-html>
<ref-html id="bib1.bib10"><label>10</label><mixed-citation>
DSB: Evaluering av forebygging og håndtering av flommen på Vestlandet
høsten 2014, Tønsberg, Norway, available at: <a href="http://www.dsbinfo.no/DSBno/2015/Rapport/Evalueringflomvestlandet2014/?Page=17" target="_blank">http://www.dsbinfo.no/DSBno/2015/Rapport/Evalueringflomvestlandet2014/?Page=17</a>
(last access: 19 February 2016), 2015b.
</mixed-citation></ref-html>
<ref-html id="bib1.bib11"><label>11</label><mixed-citation>
Fakta om Stryn: <a href="https://stryn.kommune.no/Artikkel.aspx?AId=47&amp;back=1&amp;MId1=798&amp;MId2=&amp;MId3=&amp;" target="_blank">https://stryn.kommune.no/Artikkel.aspx?AId=47&amp;back=1&amp;MId1=798&amp;MId2=&amp;MId3=&amp;</a>,
last access: 27 February 2017.
</mixed-citation></ref-html>
<ref-html id="bib1.bib12"><label>12</label><mixed-citation>
Federal Ministry of the Interior: Protecting Critical Infrastructures – Risk
and Crisis Management A guide for companies and government authorities, Federal
Ministry of the Interior, Berlin, Germany, available at: <a href="http://www.bmi.bund.de" target="_blank">http://www.bmi.bund.de</a>
(last access: 16 October 2014), 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib13"><label>13</label><mixed-citation>
Fridheim, H., Røstum, J., Kjølle, G., Bertelsen, D., Tøndel, I. A.,
Vatn, J., Vatn, G. Å., and Utne, I.: DECRIS – Problemstillinger rundt
tversektorielle risikoanalyser. Kritisk infrastruktur, DECRIS arbeidsnotat 1,
available at: <a href="http://www.sintef.no/globalassets/project/samrisk/decris/documents/arbeidsnotat-1-problemstillinger-kritisk-infrastruktur.pdf" target="_blank">http://www.sintef.no/globalassets/project/samrisk/decris/documents/arbeidsnotat-1-problemstillinger-kritisk-infrastruktur.pdf</a>
(last access: 24 October 2014), 2009.
</mixed-citation></ref-html>
<ref-html id="bib1.bib14"><label>14</label><mixed-citation>
Giannopoulos, G., Filippini, R., and Schimmer, M.: Risk assessment methodologies
for Critical Infrastructure Protection. Part I: A state of the art, JRC Technical
Notes, Publications Office of the European Union, Luxembourg, p. 53, <a href="http://dx.doi.org/10.2788/22260" target="_blank">doi:10.2788/22260</a>, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib15"><label>15</label><mixed-citation>
Grothmann, T., Grecksch, K., Winges, M., and Siebenhüner, B.: Assessing
institutional capacities to adapt to climate change: integrating psychological
dimensions in the Adaptive Capacity Wheel, Nat. Hazards Earth Syst. Sci.,
13, 3369–3384, <a href="http://dx.doi.org/10.5194/nhess-13-3369-2013" target="_blank">doi:10.5194/nhess-13-3369-2013</a>, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib16"><label>16</label><mixed-citation>
Hanssen-Bauer, I., Førland, E. J., Haddeland, I., Hisdal, H., Mayer, S.,
Nesje, A., Nilsen, J. E. Ø., Sandven, S., Sandø, A. B., Sorteberg, A.,
and Ådlandsvik, B.: Klima i Norge 2100 Kunnskapsgrunnlag for klimatilpasning
oppdatert i 2015, NCCS report no. 2/2015, Norsk klimaservicesenter (NKSS),
available at: <a href="https://klimaservicesenter.no/" target="_blank">https://klimaservicesenter.no/</a> (last access: 11 March 2016), 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib17"><label>17</label><mixed-citation>
IEC/FDIS 31010:2009(E): Risk management – Risk assessment techniques, International
ISO and IEC standard, Geneva, Switzerland, 2009.
</mixed-citation></ref-html>
<ref-html id="bib1.bib18"><label>18</label><mixed-citation>
Institute of Operational Risk: Operational Risk Sound Practice Guidance, Key
Risk Indicators, The Institute of Operational Risk (IOR), available at:
<a href="https://www.ior-institute.org/" target="_blank">https://www.ior-institute.org/</a> (last access: 20 January 2017), 2010.
</mixed-citation></ref-html>
<ref-html id="bib1.bib19"><label>19</label><mixed-citation>
IRGC – International Risk Governance Council: Policy brief on Managing and
reducing social vulnerabilities from coupled critical infrastructures, Geneva, 2007.
</mixed-citation></ref-html>
<ref-html id="bib1.bib20"><label>20</label><mixed-citation>
ISSMGE Glossary of Risk Assessment Terms: listed on TC304 web page:
<a href="http://140.112.12.21/issmge/2004Glossary_Draft1.pdf" target="_blank">http://140.112.12.21/issmge/2004Glossary_Draft1.pdf</a> (last access: 19 October 2016), 2004.
</mixed-citation></ref-html>
<ref-html id="bib1.bib21"><label>21</label><mixed-citation>
JRC: Handbook on Constructing Composite Indicators, Methodology and user guide,
OECD, available at: <a href="http://www.oecd.org/std/leading-indicators/42495745.pdf" target="_blank">http://www.oecd.org/std/leading-indicators/42495745.pdf</a>
(last access: 15 October 2010), 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib22"><label>22</label><mixed-citation>
Kappes, M. S., Papathoma-Köhle, M., and Keiler, M.: Assessing physical
vulnerability for multi-hazards using an indicator-based methodology, Appl.
Geogr., 32, 577–590, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib23"><label>23</label><mixed-citation>
Kristensen, K.: Rv. 15 i Grasdalen Skredforhold ved Riksveg 15 gjennom Grasdalen,
Strynefjellet, Arbeidsgruppa for Rv15 – skredsikring av Strynefjellet, NGI
report 20051040-1, NGI, Oslo, Norway, 2005.
</mixed-citation></ref-html>
<ref-html id="bib1.bib24"><label>24</label><mixed-citation>
Kröger, W.: Critical infrastructures at risk: A need for a new conceptual
approach and extended analytical tools, Reliab. Eng. Syst. Saf., 93, 1781–1787,
<a href="http://dx.doi.org/10.1016/j.ress.2008.03.005" target="_blank">doi:10.1016/j.ress.2008.03.005</a>, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib25"><label>25</label><mixed-citation>
Kröger, W. and Zio, E.: Vulnerable Systems, Springer-Verlag, London,
<a href="http://dx.doi.org/10.1007/978-0-85729-655-9" target="_blank">doi:10.1007/978-0-85729-655-9</a>, 2011.
</mixed-citation></ref-html>
<ref-html id="bib1.bib26"><label>26</label><mixed-citation>
Lenz, S.: Vulnerabilität Kritischer Infrastrukturen, Forschung im
Bevölkerungsschutz, Bundesamt für Bevölkerungsschutz und
Katastrophenhilfe, Bonn, available at: <a href="http://www.bbk.bund.de/SharedDocs/Downloads/BBK/DE/Publikationen/PublikationenForschung/FiB_Band4.pdf?__blob=publicationFile" target="_blank">http://www.bbk.bund.de/SharedDocs/Downloads/BBK/DE/Publikationen/PublikationenForschung/FiB_Band4.pdf?__blob=publicationFile</a>
(last access: 17 September 2015), 2009.
</mixed-citation></ref-html>
<ref-html id="bib1.bib27"><label>27</label><mixed-citation>
Liu, Z., Nadim, F., Garcia-Aristizabal, A., Mignan, A., Fleming, K., and
Quan Luna, B.: A three-level framework for multi-risk assessment, Georisk,
9, 59–74, <a href="http://dx.doi.org/10.1080/17499518.2015.1041989" target="_blank">doi:10.1080/17499518.2015.1041989</a>, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib28"><label>28</label><mixed-citation>
Merz, B., Kreibich, H., Schwarze, R., and Thieken, A.: Review article “Assessment
of economic flood damage”, Nat. Hazards Earth Syst. Sci., 10, 1697–1724,
<a href="http://dx.doi.org/10.5194/nhess-10-1697-2010" target="_blank">doi:10.5194/nhess-10-1697-2010</a>, 2010.
</mixed-citation></ref-html>
<ref-html id="bib1.bib29"><label>29</label><mixed-citation>
Meyer, V., Becker, N., Markantonis, V., Schwarze, R., van den Bergh, J. C. J. M.,
Bouwer, L. M., Bubeck, P., Ciavola, P., Genovese, E., Green, C., Hallegatte, S.,
Kreibich, H., Lequeux, Q., Logar, I., Papyrakis, E., Pfurtscheller, C., Poussin,
J., Przyluski, V., Thieken, A. H., and Viavattene, C.: Review article: Assessing
the costs of natural hazards – state of the art and knowledge gaps, Nat. Hazards
Earth Syst. Sci., 13, 1351–1373, <a href="http://dx.doi.org/10.5194/nhess-13-1351-2013" target="_blank">doi:10.5194/nhess-13-1351-2013</a>, 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib30"><label>30</label><mixed-citation>
Nadim, F., Kjekstad, O., Peduzzi, P., Herold, C., and Jaedicke, C.: Global
landslide and avalanche hotspots, Landslides, 3, 159–174, 2006.
</mixed-citation></ref-html>
<ref-html id="bib1.bib31"><label>31</label><mixed-citation>
National Academy of Sciences: Disaster Resilience: A National Imperative, The
National Academies Press, Washington, D.C., available at: <a href="https://www.ncbi.nlm.nih.gov/books/NBK285736/" target="_blank">https://www.ncbi.nlm.nih.gov/books/NBK285736/</a>
(last access: 17 September 2015), 2012.

</mixed-citation></ref-html>
<ref-html id="bib1.bib32"><label>32</label><mixed-citation>
NPRA – Norwegian Public Roads Administration: Konseptvalutgreiing E39 Skei – Ålesund,
Report, Region Vest, Region Midt, available at: <a href="http://www.vegvesen.no/Europaveg/e39skeiaalesund" target="_blank">http://www.vegvesen.no/Europaveg/e39skeiaalesund</a>
(last access: 26 September 2016), 2011.
</mixed-citation></ref-html>
<ref-html id="bib1.bib33"><label>33</label><mixed-citation>
NPRA – Norwegian Public Roads Administration: KVU Rv. 15 Strynefjellet, Report,
Region vest, Styring og strategistab, available at: <a href="http://www.vegvesen.no/_attachment/326969/binary/589809" target="_blank">http://www.vegvesen.no/_attachment/326969/binary/589809</a>
(last access: 26 September 2016), 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib34"><label>34</label><mixed-citation>
Oboni, F. and Oboni, C.: What you need to know about risk management methods,
Is it true that PIGs fly when evaluating risks of projects, operations, and
corporations?, White paper, Riskope International, Froideville, Switzerland,
available at: <a href="http://www.riskope.com/wp-content/uploads/2013/06/Riskope-White-Paper.pdf" target="_blank">http://www.riskope.com/wp-content/uploads/2013/06/Riskope-White-Paper.pdf</a>
(last access: 9 October 2015), 2013.
</mixed-citation></ref-html>
<ref-html id="bib1.bib35"><label>35</label><mixed-citation>
Ouyang, M.: Review on modeling and simulation of interdependent critical
infrastructure systems, Reliab. Eng. Syst. Saf., 121 43–60, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib36"><label>36</label><mixed-citation>
Perrow, C.: Normal Accidents: Living with High-Risk Technologies, Basic Books, New York, 1984.
</mixed-citation></ref-html>
<ref-html id="bib1.bib37"><label>37</label><mixed-citation>
Pescaroli, G. and Alexander, D.: A definition of cascading disasters and
cascading effects: Going beyond the “toppling dominos” metaphor, in:
Planet@Risk, Global Risk Forum GRF Davos, Davos, 58–67, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib38"><label>38</label><mixed-citation>
Rinaldi, S. M., Peerenboom, J. P., and Kelly, T. K.: Identifying, understanding,
and analysing critical infrastructure interdependencies, in: IEE Control
Systems Magazine, 11–25, available at: <a href="http://user.it.uu.se/~bc/Art.pdf" target="_blank">http://user.it.uu.se/~bc/Art.pdf</a>
(last access: 2 October 2012), 2001.
</mixed-citation></ref-html>
<ref-html id="bib1.bib39"><label>39</label><mixed-citation>
Solano, E.: Methods for Assessing Vulnerability of Critical Infrastructure.
Research Brief by Institute for Homeland Security Solutions, March 2010, p. 8,
available at: <a href="https://pdfs.semanticscholar.org/42bb/cb145680d7cefe924c1c4439ce7d002ead26.pdf" target="_blank">https://pdfs.semanticscholar.org/42bb/cb145680d7cefe924c1c4439ce7d002ead26.pdf</a>
(last access: 12 June 2014), 2010.
</mixed-citation></ref-html>
<ref-html id="bib1.bib40"><label>40</label><mixed-citation>
Stryn kommune Rådmannsavdelinga: Notat om: ROS-analyse for Stryn og Hornindal
kommunar, Dok. Ref. 13/711-18/K1-233,K2-X20//HAR, Stryn, Norway, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib41"><label>41</label><mixed-citation>
Vatn, J., Utne, I. B., Vatn, G. Å., and Hokstad, P.: DECRIS – Beskrivelse
av grovanalyse-metodikk, DECRIS arbeidsnotat 4, deliverable of the SAMRISK
project, available at: <a href="http://www.sintef.no/globalassets/project/samrisk/decris/documents/arbeidsnotat-4-metodikk-for-grovanalyse.pdf" target="_blank">http://www.sintef.no/globalassets/project/samrisk/decris/documents/arbeidsnotat-4-metodikk-for-grovanalyse.pdf</a>
(last access: 9 October 2014), 2009.
</mixed-citation></ref-html>
<ref-html id="bib1.bib42"><label>42</label><mixed-citation>
Yusta, J. M., Correa, G. J., and Lacal-Arántegui, R.: Methodologies and
applications for critical infrastructure protection: State-of-the-art, Energy
Policy, 39, 6100–6119, 2011.
</mixed-citation></ref-html>--></article>
