Language of Risk - FLOODsite
Language of Risk - FLOODsite
Language of Risk - FLOODsite
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>FLOODsite</strong> <strong>Language</strong> <strong>of</strong> <strong>Risk</strong> 2 nd Ed.<br />
Contract No:GOCE-CT-2004-505420<br />
Recommendation: An action that is taken to reduce either the probability <strong>of</strong> flooding or the<br />
consequences <strong>of</strong> flooding or some combination <strong>of</strong> the two.<br />
Rationale: Discussion at the <strong>FLOODsite</strong> Management team meeting (18.01.2005) on the Dresden<br />
paper (Schanze et al, 2005) identified the term ‘<strong>Risk</strong> Management Measure’ to be used within the<br />
context <strong>of</strong> flood risk management as opposed to “mitigation” in the Dresden paper. Mitigation in its<br />
common usage <strong>of</strong>ten has too narrow an interpretation <strong>of</strong> the actions involved whereas “management”<br />
without qualification was considered to have too broad an interpretation.<br />
4.11 Scenario<br />
A plausible description <strong>of</strong> how the future may develop, based on a coherent and internally consistent<br />
set <strong>of</strong> assumptions about key relationships and driving forces (e.g., rate <strong>of</strong> technology changes,<br />
prices). Scenarios are neither predictions nor forecasts. The results <strong>of</strong> scenarios (unlike forecasts)<br />
depend on the boundary conditions <strong>of</strong> the scenario.<br />
Green et al (2004)<br />
Recommendation: A plausible description <strong>of</strong> a situation, based on a coherent and internally<br />
consistent set <strong>of</strong> assumptions. Scenarios are neither predictions nor forecasts. The results <strong>of</strong><br />
scenarios (unlike forecasts) depend on the boundary conditions <strong>of</strong> the scenario.<br />
Rationale: The definition <strong>of</strong> Green et al (2004) has an underlying implication <strong>of</strong> climate change.<br />
Within flood system defence reliability analysis, the term ‘scenario’ is used to define potential<br />
combinations <strong>of</strong> defence failures under specified loading conditions. The definition <strong>of</strong> Green et al<br />
(2005) has therefore been broadened to encompass the defence reliability aspects.<br />
4.12 Strategy<br />
A strategy is defined as combination <strong>of</strong> long-term goals, aims, specific targets, technical measures,<br />
policy instruments, and process patterns (e.g. participation, intense horizontal communication) which<br />
are continuously aligned with the societal context. The societal context comprises economic, social,<br />
and political conditions, formal and informal institutions, resources and capabilities.<br />
Pettigrew & Whipp (1991), Volberda (1998)<br />
A strategy is defined as combination <strong>of</strong> measures and instruments as well as the necessary resources<br />
for actions to implement the basic long-term goals <strong>of</strong> a business organisation<br />
Whipp (2001)<br />
A strategy is a consistent set <strong>of</strong> measures, aiming to influence developments in a specific way<br />
Hooijer et al. 2004<br />
Recommendation: A strategy is a combination <strong>of</strong> long-term goals, aims, specific targets, technical<br />
measures, policy instruments, and process which are continuously aligned with the societal context.<br />
Rationale: Changing from the paradigm <strong>of</strong> flood protection to flood risk management raises<br />
challenging questions <strong>of</strong> formulating and implementing strategic alternatives within society. In<br />
particular strategies to reduce vulnerability and to increase preparedness require a comprehensive<br />
understanding <strong>of</strong> flood risk management.<br />
T32_04_01_ <strong>FLOODsite</strong>_<strong>Language</strong>_<strong>of</strong>_<strong>Risk</strong>_D32_2_v5_2_P1 30 April 2009<br />
18