Annex II
Survey template for participants’ contributions (deadline 22nd of January)
Interested participants are invited to contribute to the preparation of discussions to be held at
the 3rd workshop in providing their information with the format proposed hereinafter.
The format is based on the assumption that each event can be described with information on:
1. the description of the central event itself, including its context of occurrence,
2. the causes having led to this event, and,
3. the consequences of the central event.
Describing the transport events in this way facilitates the use of collected data for risk
management purpose as it follows the well known ‘Bow-Tie’ approach to risk evaluation.
Causes level 4
Consequtive event Level 1
Causes level 3
Impacts/Consequences
Consequtive events Level 2
… Level 3
Level 4…
Indirect causes
(Level 2)
Direct cause
(level 1)
cause(s)
Central event
(e.g. collision, spontaneous release…)
Please use the templates below to describe the taxonomy of your database (part A) and the
reporting process (part B):
Note 1: Please, list all types of information / attributes collected for each event, adding rows or
columns as needed.
Note 2: If certain type of information is collected only for certain types of events, please specify it
accordingly.
Part A: Template for types of information collected on events
Main category
E.1: e.g. Type of event
E: Description of event
Sub-Category
E.1.1 Rail event
E.1.2 Road event
Page 1 of 4
Sub-sub-category
E.1.1.1: Trains collision
E.1.1.2: Train derailment
…
E.1.2.1 Frontal collision
E.1.2.2 Rear collision
…
E.2: e.g. Date of event
E.3: e.g. Time of event
E.4: e.g. Location
E.5: e.g. Weather
E.6: e.g. Vehicle type
E.4.1: Open line
E.4.2: Station
…
E.5.1: Rain
E.5.1.1: Light
E.6.1: Freight train
E.6.2: …
E.7: e.g. Text field for the
description of a specific
parameter or of the event
context
C: Description of the causes
Name of the causes
Name of the causes
Name of the causes
(Level 1 – direct (immediate) (Level 2 – indirect (underlying) (Level 3 – root causes)
causes)
causes)
C1: e.g. Failure to observe C1.1: e.g. Driver fatigue
signal
C1.1.1: e.g. Disease
C1.1.2: e.g. Over working
time
C1.2: e.g. Usage of mobile C1.2.1: e.g. Received call
phone
(employer)
C1.2.2: e.g. Placed call
(private)
C2: e.g. Failure to stop on time
C2.1.: e.g. Overspeeding
C2.2.: Later recognition
preceding vehicle
C3: e.g. Mechanical failure
C3.1: Failure on vehicle
C3.2: Failure on infrastructure
…
C2.1.1: e.g. Inattention
C2.1.2: …
of C2.2.1: e.g. Low visibility
(weather)
C2.2.2: e.g. Default of
preceding vehicle rear lights
…
C3.1.1:…
C3.1.2: …
Cn…
I: Description of the consequences
(consequences from the central event leading to following events and different type of impacts)
Name of the Impact
(Level 1 – direct impact)
Name of the Impact
(Level 2 – indirect impact)
Page 2 of 4
Name of the Impact
(Level 3 – follow-up impact)
I1: e.g. Rear collision
I1.1: e.g. Only rear/front vehicle I1.1.1: e.g. Injuries (number)
part
I1.1.2: e.g. Material damages
I1.1.3:
e.g.
Fatalities
(number)
I1.1.4: e.g. Impact on traffic
I1.2: e.g. Chain collision (e.g for I1.2.2: e.g. Number
road)
concerned vehicles
…
I2: e.g. Front collision
…
I2.1: …
of
I2.1.1: …
I2.1.2: …
Part B: Template for the description of the reporting process
For each database/reporting system the interested participants are invited to describe the data
collection process.
The description shall contain information on the administration of the database, the users, the
confidentiality and timing aspects.
On these aspects it is proposed to answer the questions below and if necessary to complement
these information with free text information and/or a workflow diagram.
Basic information about the database (if any)
Country: (e.g. Iceland)
Owner: (e.g. Ministry of Transport)
Scope: (e.g. national, since 2000)
Name of the database: (e.g. Database of events in DG transport)
B.1.0:
B.1.1:
Requesting
entity(ies)
B.1: Administration of the database
Legal base, or ‘voluntary’ if applicable
Pls
specify Pls
specify …
entity 1
entity 2, if
applicable
B.1.2:
Reporting
entity(ies)
Pls
specify Pls
specify …
entity 1
entity 2, if
applicable
…
B.1.3:
Reported
entity(ies)
Pls
specify Pls
specify …
entity 1
entity 2, if
applicable
…
B.1.4:
Administration
Pls
specify Pls
entity 1
entity
…
specify …
2, if
Page 3 of 4
…
entity
B.1.5:
Entity
responsible of
the content of
the database
B.1.6:
User(s),
including public
access
if
applicable
B.2.0: The
notification of
occurrence of
an event is
reported to
B.2.1: The
detailed causes
are
reported/made
available
on
request to
B.2.2: The
detailed
impacts
are
reported/made
available
on
request to
applicable
Pls
specify Pls
specify …
entity 1
entity 2, if
applicable
…
Pls
specify Pls
specify …
entity 1
entity 2, if
applicable
…
B.2: Confidentiality, Thresholds & Timing
Pls, specify the Pls, specify the Pls, specify the
entity(ies) as
reporting
maximum time
declared in
criteria
allowed
section B.1
(quantitative or
qualitative) if
applicable
Pls, specify the Pls, specify the Pls, specify the
entity(ies) as
reporting
maximum time
declared in
criteria
(e.g. allowed
section B.1
level
1
causes…)
if
applicable
Pls, specify the Pls, specify the Pls, specify the
entity(ies) as
reporting
maximum time
declared in
criteria
(e.g. allowed
section B.1
main impacts,
sub-category…)
as applicable
Page 4 of 4
Pls, specify the
minimum time,
if applicable
Pls, specify the
minimum time,
if applicable
Pls, specify the
minimum time,
if applicable