04.07.2015 Views

Guidance for Use of CSM Recommendation - ERA - Europa

Guidance for Use of CSM Recommendation - ERA - Europa

Guidance for Use of CSM Recommendation - ERA - Europa

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

European Railway Agency<br />

Collection <strong>of</strong> examples <strong>of</strong> risk assessments and <strong>of</strong> some possible tools<br />

supporting the <strong>CSM</strong> Regulation<br />

<br />

identified "restrictions <strong>of</strong> use" (i.e. safety related application conditions) that are applicable to<br />

the related generic products (respectively generic application). There<strong>for</strong>e, whenever a<br />

generic product and a generic application are used in operation in a specific application, the<br />

compliance with all these assumptions (10) and "restrictions <strong>of</strong> use" (or safety related<br />

application conditions) needs to be demonstrated in each specific application.<br />

1.1.6. The first step <strong>of</strong> the risk management process shall be to identify in a document, to be<br />

drawn up by the proposer, the different actors‟ tasks, as well as their risk management<br />

activities. The proposer shall coordinate close collaboration between the different actors<br />

involved, according to their respective tasks, in order to manage the hazards and their<br />

associated safety measures.<br />

[G 1] Very <strong>of</strong>ten, unless it is differently agreed in the contracts at the beginning <strong>of</strong> the project, each<br />

project has a document that describes the risk management activities. The relevant<br />

document is updated and reviewed whenever significant modifications are made to the<br />

original system.<br />

[G 2] Such a document sets out the organisational structure, the allocated staff responsibilities, the<br />

processes, procedures and activities which together ensure that the system under<br />

assessment satisfies the specified safety levels and safety requirements. The document<br />

needs to be compliant with the <strong>CSM</strong> as it supports and provides guidance to the assessment<br />

body. The CENELEC standards advise that this type <strong>of</strong> in<strong>for</strong>mation is included in a safety<br />

plan or, in another document with a part dedicated to those topics.<br />

[G 3] The proposer's safety plan in particular, or any other relevant document, presents the overall<br />

project organisation. It describes how the roles and responsibilities are shared between the<br />

involved actors. For detailed in<strong>for</strong>mation, reference can be made to the safety plans or<br />

safety organisations <strong>of</strong> the different involved actors. Usually, the sharing <strong>of</strong> responsibilities<br />

between the different actors is discussed and agreed during the preliminary system definition<br />

(i.e. at the beginning <strong>of</strong> the project), if there is one.<br />

[G 4] The safety plan is a living document that is updated when necessary during the project life.<br />

[G 5] More details can be found in the EN 50 126-1 standard {Ref. 8} and its associated 50 126-2<br />

Guideline {Ref. 9} about the content <strong>of</strong> a safety plan.<br />

1.1.7. Evaluation <strong>of</strong> the correct application <strong>of</strong> the risk management process described in this<br />

Regulation falls within the responsibility <strong>of</strong> the assessment body.<br />

[G 1] Additional explanation is not judged necessary.<br />

Continuation <strong>of</strong> the footnote<br />

If <strong>for</strong> a specific application, the compliance with some assumptions and restrictions <strong>of</strong> use cannot be<br />

achieved at a sub-system level (e.g. in case <strong>of</strong> operational safety requirements), the corresponding<br />

assumptions and restrictions <strong>of</strong> use can be transferred to a higher level (i.e. usually at system<br />

level). These assumptions and restrictions <strong>of</strong> use are then clearly identified in the "specific<br />

application safety case" <strong>of</strong> the related sub-system. This is essential to ensure in such examples <strong>of</strong><br />

dependency that the safety related application conditions <strong>of</strong> each safety case are fulfilled in the<br />

higher-level safety case, or else are carried <strong>for</strong>ward into the safety related application conditions <strong>of</strong><br />

the highest-level safety case (i.e. system safety case).<br />

<br />

Reference: <strong>ERA</strong>/GUI/02-2008/SAF Version: 1.1 Page 28 <strong>of</strong> 105<br />

File Name: Collection_<strong>of</strong>_RA_Ex_and_some_tools_<strong>for</strong>_<strong>CSM</strong>_V1.1.doc<br />

European Railway Agency ● Boulevard Harpignies, 160 ● BP 20392 ● F-59307 Valenciennes Cedex ● France ● Tel. +33 (0)3 27 09 65 00 ● Fax +33 (0)3 27 33 40 65 ● http://www.era.europa.eu

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!