Documentation of flood damage on railway infrastructure - Lakeside ...

<strong>Documentation</strong> <strong>of</strong> <strong>flood</strong> <strong>damage</strong> on railway
infrastructure
Andrew P. Moran, Andreas Schöbel, Christian Rachoy, Annegret Thieken
Lakeside Conference 2010
alpS – Centre for Natural Hazard and Risk Management
Lakeside Conference 2010

Introduction
This presentation is embedded in a larger project for the Austrian
Federal Railways (ÖBB) to analyse the <strong>flood</strong> risk <strong>of</strong> rail infrastructure.
The network <strong>of</strong> the Austrian Federal Railways (ÖBB) are affected by
several risks due to various natural hazards.
The 2006 <strong>flood</strong> event <strong>of</strong> the March River caused extensive <strong>damage</strong>
and led to a closure <strong>of</strong> the Austrian Northern Railway Line for several
months. Replacement transport services were necessary.
Lakeside Conference 2010

Introduction
Focus on <strong>flood</strong> <strong>damage</strong> documentation
Aims:
Generation and improvement <strong>of</strong> data availability on the long term
Development <strong>of</strong> a consistent, standardized <strong>flood</strong> <strong>damage</strong>
documentation scheme as part <strong>of</strong> a modern risk management for
railway infrastructure
Derivation <strong>of</strong> a foundation for <strong>damage</strong>-loss-functions
Work steps:
Close examination <strong>of</strong> rail infrastructure data. Identification <strong>of</strong> most
important elements in regard to assets and operational relevance
Definition <strong>of</strong> object classes and <strong>damage</strong> classes
Application to the 2006 <strong>flood</strong> event
Elaboration <strong>of</strong> a standardized catalogue for <strong>damage</strong> documentation
Lakeside Conference 2010

Test Railway Line
Austrian Northern Railway Line: (Vienna) – Gänserndorf –
Bernhardsthal
Lakeside Conference 2010

Test Railway Line
Austrian Northern Railway Line: (Vienna) – Gänserndorf –
Bernhardsthal
47 km
2 tracks
Electrified
Core network
Bernhardsthal
Gänserndorf
Vienna
Lakeside Conference 2010

Definition <strong>of</strong> object classes
Identification <strong>of</strong> most important infrastructural elements
-> Definition <strong>of</strong> essential object classes
Criteria: Financial assets, operational relevance
Standard cross section (base section, track super structure,
contact line)
Signal towers
Station buildings
Bridges
Transformer substations
Stock Values per object class
Lakeside Conference 2010

Classification <strong>of</strong> structural <strong>damage</strong>
Definition <strong>of</strong> structural <strong>damage</strong> classes for each object class
Five <strong>damage</strong> classes are allocated to each object class
Consideration <strong>of</strong> direct and indirect effects
Lakeside Conference 2010

Classification <strong>of</strong> structural <strong>damage</strong>
Standard cross section
# Description Indirect effects
1 Flooding reaches the base section
without notable <strong>damage</strong>
none
2 Flooding reaches the base section. Possible operational limitations (slower speeds,
Erosion occurs
delays)
3 Track super structure is <strong>flood</strong>ed. Track is closed. Detours or replacement transport
services are necessary.
4 Erosion <strong>of</strong> the track super structure. Detours or replacement transport services for
Reconstruction is necessary. several days are necessary.
5 Additional <strong>damage</strong> <strong>of</strong> the overhead Detours or replacement transport services for
contact line, signals etc.
several weeks are necessary.
Lakeside Conference 2010

Application: Damage documentation
Description and visualisation <strong>of</strong> the
<strong>damage</strong>s along the standard cross
section (Austrian Northern Railway 2006)
Lakeside Conference 2010

Bridges
Classification <strong>of</strong> structural <strong>damage</strong>
# Description Indirect effects
1 No adverse effects due to <strong>flood</strong>ing.
2 No restrictions, maintenance necessary in the none
course <strong>of</strong> the next inspection.
3 Log jam, removal is required.
In general no operational limitations. Speed
reductions or short closures are possible during
the removal <strong>of</strong> the jam.
4 Formation <strong>of</strong> a scour. Repair is necessary.
Rail operations are closed for many days or
weeks.
5 Scour or major structural <strong>damage</strong>. Bearing strength All rail operations are closed for many weeks to
is no longer guaranteed. Bridge is closed.
months.
none
Lakeside Conference 2010

Standardised <strong>damage</strong> documentation
Lakeside Conference 2010

Criteria Catalogue: Event Information I
Information Specific measurement, documentation Specification <strong>of</strong> parameters, details
E1: Time and duration
Begin <strong>of</strong> event [jjjj.mm.tt:hh] Time <strong>of</strong> first impact on <strong>damage</strong>d object
End <strong>of</strong> event [jjjj.mm.tt:hh] End <strong>of</strong> affectedness
OR Duration [tt:hh] Flooding duration <strong>of</strong> object
Time <strong>of</strong> first <strong>of</strong>ficial <strong>flood</strong> warning [jjjj.mm.tt:hh] Time <strong>of</strong> first <strong>flood</strong> warning for the object
E2: Hydraulic endangerment <strong>of</strong> the object
Type <strong>of</strong> <strong>flood</strong> event
List <strong>of</strong> multiple choices
- Flooding (no to low flow velocities < 1 m/s)
- Dynamic <strong>flood</strong>ing (medium to high
velocities > 1m/s).
- Flash <strong>flood</strong>
- Free flowing surface water
- Ground water
- Backwater in storm-water drainage
systems
-Debris flow
-Other
Explanations [Text]
Incase the <strong>flood</strong> occurs with a high content <strong>of</strong> solids, the
criteria “drift wood/material should also be documented.
Incase <strong>of</strong> dynamic <strong>flood</strong>ing the criteria “flow velocity
should be considered.
e.g. specification under “other” e.g. wave overtopping
Lakeside Conference 2010

Criteria Catalogue: Event Information II
River name
[Text]
Official name <strong>of</strong> river inducing <strong>damage</strong>
OR
List <strong>of</strong> choices
Damage triggering or amplifying characteristics
Probability <strong>of</strong> local event
List <strong>of</strong> multiple choices
- Uncontrolled breach <strong>of</strong> levee, dam etc.
- Controlled <strong>flood</strong>ing (polder)
- Morphological change <strong>of</strong> river channel
- Log jam and backwater
-Ice dam
-Other
Explanations [Text]
[Ordinal scale]
1: very <strong>of</strong>ten
2: <strong>of</strong>ten
3: occasionally
4: seldom
5: very seldom
6: First time observation
Further events triggering or amplifying <strong>damage</strong>
e.g. Explanation <strong>of</strong> “other”
Classification <strong>of</strong> events according to occurrence intervals
based on hazard maps or statistical analyses <strong>of</strong> run<strong>of</strong>f
data for respective river segments
Average event occurrence 1-2 years or more <strong>of</strong>ten
Average event occurrence 2-10 years
Average event occurrence 10-50 years
Average event occurrence 50 – 100 years
Average event occurrence < 100 years
Such an event was observed for the first time
Lakeside Conference 2010

Criteria Catalogue: Event Information III
E3: Local <strong>flood</strong> effects
Highest water level - outside [cm] above ground level or railway track level This means the highest water level on the outside <strong>of</strong> an
object / building.
Note: The ground level is requested with the object
information
Flow velocity
[m/s] at the object
Estimating flow velocity is advised for dynamic <strong>flood</strong>s.
CONDITIONAL
E4: Floating/Suspended material
OR
[Ordinal scale]
0: standing Nearly standing water
1: low Walking in water is still possible (2m/s)
Contamination
Multiple choice list
- No contamination
- Sewerage
- Paint and varnish
- Oil and fuel
- Other chemicles
e.g. heating oil, diesel, gasoline
e.g. pesticides, solvents
-Other
Explanations [Text]
Specification <strong>of</strong> “other”.
Lakeside Conference 2010

Outlook
Organizing data acquisition is an integral part <strong>of</strong>
precautionary procedures and efficient risk management
strategies.
Damage documentation -> user-friendly guideline to simplify
the <strong>damage</strong> assessment.
Standard Implementation and application <strong>of</strong> the concept and
procedure for the entire core network <strong>of</strong> the ÖBB.
Damage documentation as an important basis for the
development <strong>of</strong> <strong>damage</strong> models
Lakeside Conference 2010

Outlook
Risk = Hazard x Value/Exposition x Vulnerability
HORA
Hydraulic
Simulation
Book Value
Stock value
Replacement Value
Strd. cross section Bridges Buildings Other object class
…
Damage Model 1
DM 2
DM 3
DM…
Mitigation
Measure
Structural
Damage Class
Mit.
Me.
Str.
DC.
Mit.
Me.
Str.
DC.
Mit.
Me
Str.
DC.
Lakeside Conference 2010

Outlook
Definition <strong>of</strong> a <strong>damage</strong> model per object class
Floods
(water height h,
Flow velocity v)
Mitigation
measures
Structural <strong>damage</strong>
classes
Monetary loss
Current state <strong>of</strong>
maintanance
D structural = f (h, v, Object type, prevention measures)
D monetary = f (D structural )
Verification <strong>of</strong> feasibility by applying <strong>damage</strong> data and results from
hydraulic simulation data from the 2006 <strong>flood</strong> event.
Lakeside Conference 2010

Outlook
Thank you!
Andrew P. Moran
alpS GmbH
Grabenweg 3, A-6020 Innsbruck
Tel.: +43-512-39292911
moran@alps-gmbh.com
Lakeside Conference 2010