Legal information

Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)

Draft foundation hazard

GoalIdentification and consolidation of the high-level hazards for operational level [and assignment to the identified accidents]
Requirements met by this process step

CSM-RA (402/2013) §2.5

EN 50126-1:2017 §7.4

EN 50126-2:2017 §5

Inputs

AMOD-128 Safety compliance strategy

AMOD-129 Relevant safety legislation/regulations

The list of the analyzed norms, standards and projects (->Collection of Hazards):

  • Standards/Norms: EN62267_BB1.pdf (Bahnanwendungen - Automatischer städtischer schienengebundener Personennahverkehr)
    So maybe start with this task. It has already been initiated by me. The related page can be found in my Sandbox at EN 62267
    You can do me a favour, if you could check my translation, I already did for the hazards.
    Within this standard (EN 62267:BB1) and with respect to Table 1 in this standard, I got to "8 Sicherstellen des Erkennens und die Bewältigung von Notfallsituationen" at page 23, where you can proceed.
  • Standards/Norms: Railway applications, IEC 62290-1: Urban Guided Transport Management and Command/Control Systems, Part 1: System Principles and Fundamental Concepts, Date: 2004, IEC 62290-1_2004.pdf

  • Standards/Norms: Railway applications, IEC 62290-2: Urban Guided Transport Management and Command/Control  Systems, Part 2: Functional Requirements Specification, Date: 13.01.2009, IEC 62290-2_2009.pdf

  • Standards/Norms: IEEE 1474.1 Standard for Communications- Based Train Control (CBTC), Performance and Functional Requirements, Date: 25.02.2005, IEEE 1474.1-2004.pdf
  • Standards/Norms: IEEE 1474.2 Standard for Communications- Based Train Control (CBTC), Performance and Functional Requirements, Date: 12.12.2003, IEEE 1474.2-2003.pdf
  • Standards/Norms:IEC 61508-1: Railway applications, Functional safety of electrical/electronic/programmable electronic safety-related systems –  Part 1: General requirements, Ed. 2.0, 2010-04, IEC_61508-1_2010.pdf
  • MODSafe Project: MODSafe Hompage - Documentlist
    Especially, D4.2 "Analysis of Common Safety Requirements Allocation for MODSafe continuous Safety Measures and Functions" (starting from Chapter 10) shall be taken into account. You can also take a look in D2.1 "First List of Hazards, Preliminary Hazard Analysis (PHA)", if you need more information.
  • Neupro Risk Analysis: NeuPro.71_Risikoanalyse_V2.0.pdf bzw. Vornorm SafetyFunctions_VDE V 0831-103.PDF
    NeuPro Risk Analysis is based on the VDE standard. So they shall be more or less equal respectively similar. Just use both of them to mak a check for completeness.
    For the source Neupro, there are several informations distributed with respect to hazards (Gefährdung (Maßgebende Ausfallart)), system safety functions etc. in chapters 5 and 6. Accidents are somhow mentioned as "Ereignisart") - please alligne them with the accident list given in confluence (see references in the template). 
    For the VDE standard, take a look in Annex B. With "Ausfallarten der Funktion", the hazard is described (see also compared to Risk Analysis Neupro). The safety function is stated as headline. "Rahmenbedingungen" are external conditions, and "Auswirkungen" should be related to accidents. 
    I would start with Neupro, and complete information about hazards (if there are any additions not mentioned within related Risk Analysis) by using the VDE standard. You can do me a favour, if you can add THR (tolerable hazard rate) mentioned in NeuPro Risk Analysis within the corresponding coloumn comment. 
  • UNISIG SPecification: Subset-088, SUBSET-088 v3.5.4.zip, and Subset-091 (baseline v3.6.0R02), SUBSET-091_v360.pdf
    I think there should be only two mentioned: Something like overspeed and something like passing a danger point. Please have a look.
  • EBA - SIRF/TeSIP  TeSIP; s. SIRF/TeSIP (EBA, Sicherheitsregelung Fahrzeuge)
    There is an excel-sheet and the related information can be found in column "D" (function), "I" & "K" (hazard).
  • TSI's (e.g. TSI Loc&Pas, §4.2.5.5.8): see List of TSI's (ERA Homepage)
  • Other projects: e.g. Shift2Rail, X2Rail ... 

The consolidated list of the relevant accidents: DBS Accidents List

Expert knowledge

Outputs

Finite set of identified hazards including Accident-Hazard-Relation and relevant conditions and functions (if given) as Excel table:

https://rmt.jaas.service.deutschebahn.com/confluence/display/SSI/Collection+of+Hazards

 Set of hazards and acccident-hazard-relations (as Mindmaps):

Generic Hazard Identification with sub-websites

Methodology

In order to establish a complete list of typical hazards in railway operation different railway norms have been analyzed for the hazards incl. causes and related accidents and risk control measures including following steps:

1. Collection of hazards from relevant documents (see list of the analyzed norms, standards and projects listed above in Inputs-Section)

2. Consolidation of the hazards identified by relating them to the finite set of accidents identified (see consolidated list of the relevant accidents listed above in Inputs-Section)

Collection of hazards from relevant norm documents

The purpose of this task is to establish a complete list of typical hazards in railway operation. The analysis of the norm documents shall

  • present the completeness of the hazard list and
  • establish a generic description of hazards.

The memory location of the analysed norm documents in the storage system DB Confluence is:

https://rmt.jaas.service.deutschebahn.com/confluence/display/SSI/Collection+of+Hazards

Every document is considered in sub-sides in DB Confluence.

Hazard assignment and consolidation

The consolidation of hazards was done by 1:n mapping of hazards to the accidents (hazard are considered as the conditions that may lead to an accident, n hazards could be mapped to 1 accident). There is no constraint that a hazard is solely allocated / mapped to one accident.

For the consolidation of the hazards from reference norm documents the program “Freeplane” was used, which is carried out in a mind map. During consolidation it has been checked for every accident if full set of related hazard already exists in database, if necessary new hazard have been defined and added to database.

The author, the state of the mind map and the name of the person, who makes the review, are listed on the Cofluence-site given in the section Output. 

Every mind map is considered in sub sides in DB Confluence. The links to these sub sides are listed in the table. On these sub-pages the review comments can be entered. The review comments can be also inserted into the mind map for each accident category.

Tools and non-human resources
Cardinality
  • Created and provided as a first stable draft or baseline incl. reviews
  • Hazards will be further implemented and maintained in Capella (Risk-State-Model)
  • In case of significant changes, set of hazards will be changed and confirmed by review (ensured by implemented quality management system and related processes)
Completion criteriaList of consolidated applicable hazards with clear description [assigned to previously identified accidents] satisfying all working group members
Design review

Link to the corresponding design review where the completion of this activity is evaluated.

Remark: Internal review is documented in list in Generic Hazard Identification (in general still no quality management system implemented in DBS)

Step done by (Responsible)RAMS Expert or Risk Manager
Provides input to/assists (Contributes)

other RAMS Expert or Risk Manager

Uses outputs (Informed)

Identify the roles and/or process areas that make use of this information outside of the ARCH process area;