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
Goal | Identification 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):
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 documentsThe purpose of this task is to establish a complete list of typical hazards in railway operation. The analysis of the norm documents shall
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 consolidationThe 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 |
|
Completion criteria | List 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; |