Copyright DB Netz AG, licensed under CC-BY SA 3.0 DE (see full text in CC-BY-SA-3.0-DE)
ARCH.026 Define the state model of accidents, hazardous and safe state
SM-2762
-
Populate Confluence page for activity definition: ARCH.026 Identify operational safety risks (hazard-accident mapping)
Finished
SM-2480
-
Update modelling rules and ARCH.026 / ARCH.020 for operational level safety elements
Finished
SM-5059
-
Update ARCH.026 after feedback from RAMS manager
Finished
---------- Tickets from TaskForce ---------------
- ARCH.026 Define the state model of accidents, hazardous and safe state, including required content and formal semantics of the model.
Described method- has to be verified and validated (by review and/or example) and (DBSRAMS-17, previously SM-6191):
- by example (DBSRAMS-23)
- by review (DBSRAMS-48 incl. Subtasks)
- if necessary to be adapted and/or completed (DBSRAMS-18, previously: SM-6200), or
- implement a new ARCH.<id> process stop (DBSRAMS-108) and
- adapt sequence of processes if necessary (DBSRAMS-157)
- an example has to be prepared and provided (DBSRAMS-16, previously SM-5754 resp. DBSRAMS-23)
- Finally, update terms and definitions (DBSRAMS-218)
- has to be verified and validated (by review and/or example) and (DBSRAMS-17, previously SM-6191):
---------- Tickets from TaskForce ---------------
Goal | Provide a consistent starting point for safety risk analysis |
---|---|
Requirements met by this process step | CSM-SMS guidance 1.1 b), 3.1.1.1 a) CSM-RA EN 50126-1/2 EN 50129 |
Inputs | AMOD-128 Safety compliance strategy |
Outputs | AMOD-030 Accident & hazard state model |
Methodology | ContentScopeIn this process activity a risk model is set up. The risk model contains all identified accidents and their related hazards. Further it contains a non-hazard, which is the opposite of the hazard. Accidents, hazards and non-hazards are represented as states (accident state, hazardous state, safe state). Transition between these states represent identified conditions that lead to the leaving of one state and the entering of another state. Conditions may be unwanted events that have to be prevented, wanted events that are desired and combinations of both (e.g. train movement and an obstacle on the track). The scope of ARCH.026 is limited to the definition of the bespoken states (by using AMOD-109 as input) and the definition of following transitions:
Not in the scope of ARCH.026 is:
Process StepsPreconditions / Considerations for implementationBefore defining a new risk model via the process steps below the following shall be noted:
ImplementationFollowing steps shall be implemented:
The resulting risk model should look as follows after ARCH.026: Notes:
|
Tools and non-human resources | Team for Capella |
Cardinality | One-off with possiblity of revisions - refinement in several model if the conditions transitions cannot be put together |
Completion criteria | The accident states and hazard states set is complete The accident states and hazard states set covers the needs of the relevant safety legislation/regulations The output view conforms to its modelling rules |
Design review | ARCH.R.2 Operational review - consolidated |
Step done by (Responsible) | RAMS Architect |
Provides input to/assists (Contributes) | Operational concept architect |
Uses outputs (Informed) | None directly |