Modular Urban Transport Safety and Security Analysis

Work package No. 4: Common Safety Requirements

Kick-off meeting 21st April, 2009UITP, Brussels

Draft Agenda

1. Presentation of involved partners 15’ all

2. WP structure and schedule of working tasks 45’ TelSys/UITP

3. Links to other WP within MODSafe 30’ TelSys

4. Deadlines of deliverables 20’ all

5. Notification and Involvement of National Experts 30’ UITP(Procedure)

6. Date and Place of next Meeting WP 4 10’ all

1. Involved Partners for WP4

1.5LU

2Ansaldo0.5TRIT

2.5MMA27TOTAL

2UITP10TelSys3.5TMB3RATP2AREVA

Person-months per beneficiaryParticipant

2. Objectives of WP4 § The identified HAZARDS must be covered, may not remain uncovered

§ “Safety Measures” can be technical solutions, procedures, human intervention, (physical) barriers, etc.

§ How safe do these Measures have to be? They shall reduce the probable worst case risk associated with the hazard to an acceptable rate!

§ How to calculate/allocate? Several schemes available, check if consistent, recommend good practice

§ Check in particular on-demand functions (“rare” demands, neutralizing factors etc.), how to calculate risk reductions/safety requirements ?

§ Check also consistency of Degraded Modes if possible

2. Input / Basis for WP 4

§ Safety Requirement allocations and analyses had been defined in the past, sometimes contentious, but they are available and look compatible

§ Problematic are issues like on-demand functions, degraded modes etc. including the treatment of neutralizing factors and rare initial occurrence rate

§ Also, must be careful not to conflict with other standards like EN50129, EN50126, therefore check against Functions/Object Model

2. Description of WP 4 tasks and Modes of Work Task 4.1: State of the Art Analysis and Compilation of Results from Previous

Projects

- Based on research projects such as MODURBAN, MODTRAIN and as well on real-life implemented projects such as METEOR, Barcelona, Nuremberg, Lausanne

- previously performed Safety Requirement Allocations shall be analyzed

- Recommendation of a Safety Requirement Allocation Process for continuous and on-demand functions

Suggested Mode of Work

- TelSys accumulates the current and previous methods and presents them to the Expert Group

- WP internal collection of information from operators (LU, MMA, RATP, TMB)

- Experts (like VDV etc.) will be proposed by UITP, Experts+UITP are invited to Brussels regularly (every 4 months?)

- Summary findings are presented in the deliverable D4.1

- important task, slightly delayed because of uncertain project start

à nominate experts as quickly as possible

2. Description of WP 4 tasks and Modes of Work

Suggested Mode of Work

- TelSys applies the recommended safety requirement assignment process to the functions and presents them to the Expert Group

- WP internal collection of information from operators (LU, MMA, RATP, TMB)

- Experts (like VDV etc.) will be proposed by UITP, Experts+UITP are invited to Brussels regularly

- Summary findings are presented in the deliverable D4.2

Task 4.2: Application of the Safety Requirement Allocation Process to MODSAFE continuous Safety Measures and Functions

- Depending on the Safety Requirement Assignment methods, application to all continuous mode safety functions and methods

- Can start early on “standard” safety functions such as Train Detection or Train Separation, Functions come from WP5 and WP3

- Shall ultimately be recommended to European operators

2. Description of WP 4 tasks and Modes of Work

Suggested Mode of Work

- Context Analysis, methods proposal, case study by TelSys, proposed to Experts

- Experts (like VDV etc.) will be proposed by UITP, Experts+UITP are invited to Brussels regularly

- Summary findings are presented in the deliverable D4.3

Task 4.3 Analysis of On Demand Functions and Systematic Failures

- Analysis of the currently unresolved SIL Allocation Issue for On Demand Functions and Systematic Failures, Case Selection (e.g.. Platform Edge)

- Definition of impacts like Operations, Exposure, Neutralizing Factors etc.

- Proposal of a Risk Analysis method application and Safety Requirement Analysis method

- Application of the methods for different operational situations to provide scenarios

3. Links to other WPs

WP 11 / WP 12

WP 1M1-M12

WP 2M1-M29

WP 8M9-M48

WP 10M1-M48

WP 9M8-M42

WP 6M7-M28

WP 7M7-M42

WP 3M15-M48

WP 4M6-M40

WP 5M7-M28

4. Deliverables of WP4

Start: 1 February 2009

Duration: M6-M40

Deliverables list

Due DateTitle

M 40Analysis of On Demand Functions and Systematic Failures

D4.3

M 24Analysis of Common SafetyRequirements Allocation forMODSAFE continuous SafetyMeasures and Functions

D4.2

M 14State of the Art Analysis and Compilation of Results from Previous Projects

D4.1 31 October 2009

31 August 2010

31 December 2010

5. Notification and Involvement of National Experts 1/2

§ Identification of target countries for involvement in the WP4 process:TELSYS and MODSAFE consortium partners – end April 09

§ Preparation of a questionnaire on Safety Requirements:TELSYS, checked by WP4 partners – end May 09

§ Identification of the relevant inputs from experts on Risk Analysis method application and Safety Requirement Analysis method – end May 09

§ Preparation of the expert’s consultation on Risk Analysis and Safety Requirements (brainstorming, conference call, email, questionnaire?) – end May 09

5. Notification and Involvement of National Experts 2/2

§ Identification of relevant National Experts from operators:UITP and WP4 partners – end May 09

§ Identification of relevant National Experts from Government/Public Authorities:how to proceed?

§ Contacting National Experts by email:drafting by TELSYS, acting by UITP, follow-up UITP – mid June 09

§ Meeting with National Experts – mid of June

§ Analysis of information received:TELSYS, reporting to WP4 partners – end September 09

6. Date and Place of next WP 4 meeting

Proposed date: Mid of June

Participants: WP members + invited National Experts