Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
Draft foundation accidents
Goal | Identification and consolidation of the high-level accidents list for operational level |
---|---|
Requirements met by this process step | CSM-RA (402/2013) §2.5 EN 50126-1:2017 §7.4 EN 50126-2:2017 §5 |
Inputs | Sources/References:
|
Outputs | Fintie and complete set of accidents within transportation systems in EXCEL and Mindmap format: DBS Accidents List |
Methodology | Definition/ScopeAccident is considered as "An unintended event or series of events that results in potential loss of life, loss of health or loss of environmental integrity. " Accident are understood as the following safety-related losses:
The "loss of a system or service"considered in CENELEC and CSM-RA is excluded from the analysis, this case will be considered separately as "incident". Specific harm/accident resulting from terrorism (e.g. bomb explosion), arson, vandalism are not considered. The consequences related to passenger security matter are also not considered. Although suicide is not differenciated in the accident list, the related consequence is covered by the accident list (considering a single person is affected). MethodologyThe hereafter steps have been followed for the definition of the accidents:
When performing the three last steps, some accidents have been renamed/reffined/supplemented (leave of the accident tree) if needed and sometimes the tree structure has been changed. Remark: DB (EDS - Safety-Datenbank) database for accidents and disturbances/malfunctions does implement the categories of BEU Three different consideration levels are considered for accident definition:
All identified accident have been asigned with the unique ID and structured in the hierarchical order. |
Tools and non-human resources |
|
Cardinality |
|
Completion criteria | Finite and complete list of consolidated applicable independent accidents in transportation with clear description. The cutset of accidents provided in the list shall be empty. |
Design review | Link to the corresponding design review where the completion of this activity is evaluated. |
Step done by (Responsible) | RAMS Expert, Risk Manager and/or System Architect |
Provides input to/assists (Contributes) | RU, IM, any competent expert |
Uses outputs (Informed) | System Architect, RAMS Expert, Risk Manager |