Annual Meeting Documentation - MODSafe · 2012. 1. 18. · short overview on the mandate for standardisation in the field of UGT (UITP) - discussion (all) - agreement on actions as

European Commission Seventh Framework programme

MODSafe Modular Urban Transport Safety and Security Analysis

Annual Meeting Documentation

Deliverable No. D11.3 (M36)

Doc Name: DEL_D11.3_TRC_WP11_2011-11-18_V01_M36.doc Date: 2011-11-18 ID: DEL_D11.3_TRC_WP11_2011-11-18_V01_M36 Revision: 0.1 page 2 of 49

Document Identification:

Contract No. 218606

Document type DEL

Version V 01

Status Final

Date 2011-11-18

WP WP 11

Lead Author Stefan Kuschel, TRC

Contributors (ModSafe)

Other Contributors -

Description Annual Meeting Documentation

Document ID DEL_D11.3_TRIT_WP11_111118_V01_M36

Dissemination level CO

Distribution Consortium members and EC

Document History:

Version Date Author Modification [very short description]

V01 18.11.2011 Stefan Kuschel First Issue

Approval:

Authority Name/Partner Date

EB members all Approval of the respective Meeting Minutes

WP responsible TRC / Stefan Kuschel 2011-11-18

Coordinator TRIT / Peter Wigger 2011-11-19


Table of Content 1. Summary .................................................................................................................. 4

2. Fifth Executive Board Meeting 4th of November 2010 ........................................... 5

3. Sixth Executive Board Meeting 22nd of February 2011 .........................................10

4. Seventh Executive Board Meeting 11th of May 2011 .............................................24

5. Fourth Plenary Group Meeting 11th of May 2011...................................................36


1. Summary

This Deliverable is a compilation of the documentation of the meetings of the Executive Board and Plenary Group during the period

1st September 2010 to 31st August 2011. The document “OTH_MODSafe Status and Planning_TRIT TRC_WP 11” is attached in the version 2011-11-15, only at the end of the document (to simplify and to avoid repetitions).

Four meetings took place during this period:

- Fifth Executive Board Meeting 4th of November 2010

- Sixth Executive Board Meeting 22nd of February 2011

- Seventh Executive Board Meeting 11th of May 2011

- Fourth Plenary Group Meeting 11th of May 2011


2. Fifth Executive Board Meeting 4th of November 2010 Venue: RATP – Val de Fontenay

Building DOLOMITES – 3rd Floor – Room D-OPERA

Time: 15:45h – 16:30h

Participants:

DC COINEAU, Daniel RATP

CH HOOGENDOORN, Caroline UITP

CR ROGGE, Catherine RATP

JS SCHÜTTE, Jörg, Prof. TUD

MT TENNEDAL, Mats Bombardier

PW WIGGER, Peter TRIT

BW WULLERSTORFF von, Bernhard UNIFE

WP 11 Izaskun Arebaza (TRC) was excused. WP1 and WP7 were not present.


Agenda

No. Start Item

1 15:45 Welcome and adoption of the agenda for the day

2 Follow up of action items of the previous meeting (ref. MoM 2010-06-16)

3 WP11: Status of Contract Amendment (TRC), as needed

4 WP11: Status of Periodic Reporting (TRC), as needed

5 WP12: Status of dissemination activities (UITP), as needed

6 Project Time schedule and handling of deliverable delays

7 Introduction of SECUREMETRO Project

8 Update and consolidation of work plan (TRIT)

9 Update and consolidation of calendar (TRIT)

10 Next EB Meeting

16:30h End of Meeting

Document History: This MoM was distributed as a draft 2010-11-10 for review and comment. Changes made: Comments received from RATP were incorporated in section 3. Comments received from UITP were incorporated in sections 5 and 10. Section 12 (next PG Meeting) has been added. The attachment has been updated as well as per 2010-12-01. The MoM at hand is considered to be the final version (V2), distributed 2010-12-01.


1) Welcome and adoption of the agenda for the day No further agenda topics were introduced in the beginning, the topic budget consumption popped up during the meeting (see below).

2) Follow up of action items of the previous meeting (ref. MoM 2010-06-16)

The previous actions items were closed. 3) WP11: Status of Contract Amendment (TRC), as needed

DC remarks that he has had to ask expressly for the D11.1, D11.2 and D11.3 to be disseminated, although it is noted in the DoW that these deliverables are available to the all consortium. So they should be sent to all members in due time, and not only to selected partners. The Coordinator explained the TRC / TRIT position that this report will be send to nominated persons as person in charge of administrative, legal and financial aspects as well as the person in charge of scientific/technological aspects in the project of the respective companies.

4) WP11: Status of Periodic Reporting (TRC), as needed

none

5) WP12: Status of dissemination activities (UITP), as needed The next newsletter #2 is finalised and will be sent to partners shortly. CH regretted that, although several reminders were sent, only 3 contributions were sent. It was decided that this newsletter will include only these three contributions because of lack of time, but that in the future more contributions are expected. The format of the newsletter is consistent with the first newsletter but two new parts were added: “message from the coordinator” and “any other business” (where partners can communicate on their news in direct link with MODSafe).

6) Project Time schedule and handling of deliverable delays In general, status and dependencies of the deliverables were discussed during the WP10 meeting. Various deliverables are delayed according to the latest schedule as per 2010-06-21 (ref. attachment of the MoM of the previous EB meeting 2010-06-16). The Coordinator reminded the Work Package leaders to aim to deliver in time since the EC has recently asked for the status of various delayed deliverables. Consensus was achieved that the appropriateness and quality of the deliverables has the highest priority since new aspects and inter-dependencies between the work packages may have an impact on the schedule as discussed during the WP10 meeting, e.g. the dependencies between WP’s 2 – 5. UNIFE (BW) recommended the Coordinator to provide a brief overview on the schedule (as well as the budget consumption situation) during the EB meetings. Agreed, the basis therefore will be the status and planning overview as to be regularly attached to the EB Minutes of Meeting.


7) Introduction of SECUREMETRO Project The Coordinator informed that he was invited to participate in the SECURMETRO Exploration Meeting held at October 27, 1010 at INRETS premises in France. Consensus was achieved that the projects might have an overlapping interest in the security area and that an information exchange should be established on the Coordinator level.

8) Update and consolidation of work plan (TRIT) 9) Update and consolidation of calendar (TRIT)

The work plan and calendar are part of the status and planning overview table, being regularly attached to the Minutes of Meeting of the EB meeting.

10) Budget Status / Potential Need of Budget Transfer UNIFE (BW) suggested that the EB meetings were a good place to discuss the MODSafe budget and the level of contribution of certain partners in light of their budget. TUV (PW) replied that indeed it was a good idea, especially considering the fact that some partners were not contributing as planned and that budget transfers were currently being envisaged for certain partners. The EB will in the future be a good place for such discussions.

11) Next EB Meeting 23 February, 2010 at RATP premises after the WP 10 meeting.

12) Next PG Meeting 23 February, 2010 at RATP premises after the WP 10 meeting. Action Items

No. Party Action Due date

1 TRC / TRIT Add a budget consumption overview to the status and planning overview table.

2010-11-15

Post meeting note: Done, refer to the attachment of this MoM

2 WP leaders

Inform TRC / TRIT on the potential need of budget transfer and respective argumentation / justification

2010-11-15

Post meeting note: Done by UITP related to WP8 / 9

Attachment OTH_MODSAFE Status and Planning_TRIT TRC_WP11_01.12.2010.xls



3. Sixth Executive Board Meeting 22nd of February 2011

Venue: RATP – Val de Fontenay, France

Building DOLOMITES – 3rd Floor – Room D-OPERA

Time: 11:00h – 16:00h

List of Participants

Name Organisation

YA AMSLER, Yves UITP

IA ARENAZA, Izaskun TRC (from 12:00h)

VB BERNARD, Vincent INRETS


FC COMBELLES, Françoise RATP

PD DILLENSEGER, Patrick RATP

MK EL-KOURSI, El-Miloudi, Dr. IFSTTAR (previously INRETS)


LM MICHEL, Ludovic RATP

BS SAGHI, Balázs, Dr. BME

JS SCHÜTTE, Jörg, Prof. TUD (until 13:00h)



BW WULLERSTORFF von, Bernhard UNIFE


No. Start Agenda Item

1 11:00 Welcome and agreement on the agenda for the day - Introduction of IFSTTAR (newly added to the agenda)

2 11:00

Introduction Message of the Coordinator

- motivation and communication within the project - common targets of the project - commitment from all project members

3 11:15

Consensus building process - common review and understanding of the DOW (Coordinator, all) - common review and understanding of the consensus building processes (Coordinator, all) - discussion of the handling of comments received from external experts as needed (all) - refreshment of the EB voting process to be applied in case of non-consensus (Coordinator)

4 11:30 D5.1 (no WP10 consensus achieved yet) - short overview on the status and on the open WP10 comments, if any (Coordinator) - agreement on actions on how to proceed with D5.1 (all)

5 12:00 EB Decision / Vote on D5.1 (if needed) - If needed, the EB shall decide / vote on the further proceeding with D5.1 (EB) - update of the consensus building process (if any) as needed

6 12:30 Lunch Break

7 13:30 WP8 / WP9: Refreshment on previous EB meeting agreement (UITP) - Reminder on previous EB agreement (for refreshment info, only) need for WP8/9 consultation in case a safety delivery writes about security and vice versa (UITP)

8 13:40

Availability of (restricted) WP8/9 reports as input to SECUR-ED - short overview on SECUR-ED (UITP) - discussion (all) - agreement on actions as needed (all)

9 14:00

MODSafe process for identification of potential need for standardisation - short overview on the mandate for standardisation in the field of UGT (UITP) - discussion (all) - agreement on actions as needed (all)

10 14:15

WP11: Overview on Status and Planning (TRC, TRIT) - overview on the status of deliverables - deliverables already being delayed or probably facing a delay - time schedule and handling of deliverable delays - critical paths and corrective actions as needed

11 14:30

Update and consolidation of work plan / calendar (TRC, TRIT) - all work package leaders shall be prepared to announce reliable planning for their deliverables - update of the work plan / calendar (in terms of updating the status and planning table) - update of Quality Plan, as needed

12 14:45

WP11: Overview on Budget and Payment (TRC) - overview on the budget and payment (TRC) - Amendment to the Grand Agreement (TRC) - discussion as needed (e.g. need for budget transfer) (all) - agreement on actions as needed (all)

13 15:15 WP11: Status of Periodic Reporting (TRC) - Overview in the status of periodic reporting, as needed (TRC)

14 15:30 WP12: Status of dissemination activities (UITP) - Overview in the status of dissemination activities, as needed (UITP)

15 15:45 Action Items - Follow up of action items of the previous meeting (ref. MoM 2010-11-04) - New Action Items as needed

16 16:00 Next EB Meeting / Next PG Meeting

17 16:00 End of Meeting


1) Welcome and agreement on the agenda for the day

The agenda was agreed.

El-Miloudi El-Koursi, informed on the fusion of INRETS and LCPC to IFSTTAR; see attached presentation.

2) Introduction Message of the Coordinator

See attached presentation, slides 2 – 5.

The coordinator‘s wish is to have everybody‘s pro-activeness and solution-oriented contribution and motivation to successfully finish the project in time.

3) Consensus building process

See attached presentation, slides 10 – 12.

The process was discussed, however no formal change requested / decided upon. The Coordinator reminded the work package leaders to inform in an early stage in case of facing potential lacks or delays. In such cases the Coordinator and / or the EB shall support.

4) D5.1 (no WP10 consensus achieved yet)

See attached presentation, slide 13.

The Coordinator (PW) has worked out a suggestion on how to solve the remaining open comments from WP10 (21 RATP comments). Both, TUD (JS) and RATP (DC) confirmed acceptance.

The respective files shall be attached to the MoM of the WP10 meeting 2011-02-23.

5) EB Decision / Vote on D5.1 (if needed)

No EB decision / vote was needed, see above item 4).

6) Lunch Break 7) WP8 / WP9: Refreshment on previous EB meeting agreement (UITP)

CH gave a refreshment on a previous EB agreement of March 2010, namely that each safety work package leader shall inform the security work package (WP 8 – 9) leader (UITP) in case a safety work package report touches security issues and vice versa the security work package leader shall inform the safety work package leaders in case a security work package P 8 – 9 report touches safety issues. This will make sure that there is coherence between all MODSafe deliverables.

8) Availability of (restricted) WP8/9 reports as input to SECUR-ED

YA gave a brief overview on the SECUR-ED (Secured Urban Transportation - European Demonstration) project (start 2011-04-01, duration 3,5 years, budget 40 Mio EUR, EC funding 25 Mio EUR, 39 partners, main objective is to promote public with mass transit security solutions).

PD explained that there is no disclosure policy / statement throughout Europe and the various document classifications (restricted, confidential, secret, etc.). Clearance is not required for documents classified as “restricted” (as in MODSafe).


The Coordinator shall sort out with SECUR-ED and SECURE-METRO (Inherently secure blast resistant and fire safe metro vehicles) these projects’ preparedness for exchanging security related deliverables; see Action Item #1.

The EB agrees to exchange security documents between the cited projects on the condition that WP8 and WP9 members agree thereto; see Action Item #2.

MODSafe security documents being consulted by the cited projects shall be referenced in these project’s deliverables accordingly. The Coordinator shall draft a respective disclaimer statement, see Action Item #3.

9) MODSafe process for identification of potential need for standardization

YA gave a brief overview on the EC mandate M/438 of 2011-02-04 “mandate for programming and standardization addressed to the European Standardisation Bodies in the field of urban rail”. The first phase will work out recommendations for standardization (by analyzing existing rail standards and studies), while standards as such will be developed accordingly in the second phase with the focus on system standards and procedures. MODSafe is one of the R&D projects mentioned to be analyzed.

The Coordinator shall ask the work package leaders on their point of view on the potential need for standardisation; see Action Item #4.

10) WP11: Overview on Status and Planning (TRC, TRIT)

IA provides an overview in the status and planning. See attachment. 11) Update and consolidation of work plan / calendar (TRC, TRIT)

IA reminded to inform on work package meetings performed or planned to allow proper update of the work plan / calendar. See attachment.

12) WP11: Overview on Budget and Payment (TRC)

IA provided an overview on the budget and payment. See attachment.

Thales is still lacking providing the bank account. BW offered to provide the bank account known from another EC project; see Action Item #5.

Bombardier is still lacking the submission of Form C; see Action Item #6. 13) WP11: Status of Periodic Reporting (TRC)

IA provided an overview on the status of periodic reporting. The 2nd period report is under preparation, covering the period from 2010-03-01 till 2011-02-28.

The work package leaders are asked to fill in the template submitted 2011-02-16. 14) WP12: Status of dissemination activities (UITP)

This topic was shifted to the WP10 meeting, see MoM WP10 2011-02-23.

15) Contribution by external parties (new agenda topic)

The Coordinator informed that the operator Rheinbahn Düsseldorf and Wiener Linien – both being present at the latest SUG meeting – invited the Coordinator to participate in their Stadtbahnkomitee working group safety meeting in Düsseldorf on 2011-02-02. Other operators were present as well. Rheinbahn and Wiener Linien announced their interest to review / to contribute to the WP7 deliverables.

The EB has to decide on the introduction of new experts into the MODSafe project.


BW (UNIFE) disagrees in general to introduce new experts into the MODSafe project.

The Coordinator shall contact Rheinbahn to clarify their intention and attitude, first; see Action Item #7. EB decision to be made afterwards; during the next EB meeting at the latest.

16) Action Items

The action items from the previous EB meeting (ref. MoM 2010—11-04) were closed.

New action items

No. Party Action Due date

1 TRIT The Coordinator shall contact both, the SECUR-ED coordinator (Yves Perreal from Thales, [email protected]) and the SECURE-METRO coordinator (Conor O’Neill from Newrail, [email protected]) and sort out these projects’ preparedness to exchange security related deliverables.

2011-03-15

2 UITP UITP shall check with WP8 and WP9 members and confirm the WP’s agreement to exchange security deliverables with SECUR-ED and SECURE-METRO

2011-03-15

3 TRIT The Coordinator shall draft a disclaimer statement for the exchange of security deliverables between MODSafe, SECUR-ED and SECURE-METRO.

2011-03-30

4 TRIT The Coordinator shall contact the MODSafe work package leaders and ask them for a justified work package statement on the potential need for future standardization and whether and which deliverables they identity to be potentially used for future standardization.

2011-03-15

5 UNIFE / TRC

BW to provide Thales bank account known from other EC project.

TRC to check Thales bank account.

2011-03-15

6 BT / TRC

MT to arrange submission of Form C. 2011-03-15

7 TRIT The Coordinator shall contact Rheinbahn, having expressed their interest to contribute to WP7, to clarify their intention and attitude.

2011-03-15

mailto:[email protected]


17) Next EB / PG Meeting

The next EB meeting shall take place 11 May, 2011 from 09:00h to 11:00h at RATP premises (before the WP 10 meeting).

The next PG meeting shall take place 11 May, 2011 from 11:00h to 16:00h at RATP premises (in parallel with the WP 10 meeting).

For the next EB meeting, the following agenda topics were already announced:

- EB decision regarding Rheinbahn / Wiener Linien contribution to WP7

- Confirmation that no project schedule extension is needed

- WP leaders shall report and confirm budget values

- Confirmation of Thales bank account

- Confirmation of Bombardier Form C submission

- Follow op of ERRAC recommendations

Attachment

MEE_Presentation EB6_IFSTTAR (INRETS)_110222.pdf

MEE_Presentation EB6_TRIT_110222.pdf

OTH_MODSAFE Status and Planning_TRIT TRC_WP11_28.02.2011.pdf










4. Seventh Executive Board Meeting 11th of May 2011

Venue: RATP – Val de Fontenay, France Building DOLOMITES – 3rd Floor – Room D-OPERA

Time: 09:00h – 11:00h


Name Organisation

YA AMSLER, Yves UITP

IA ARENAZA, Izaskun TRC

VB BENARD, Vincent INRETS


PD DILLENSEGER, Patrick RATP


CR ROGGE, Catherine RATP

RS SADHEURA, Rajinder Bombardier

BS SAGHI, Balázs, Dr. BME

JS SCHÜTTE, Jörg, Prof. TUD



All work packages were represented by the respective leaders, UNIFE was not present.

Mats Tennendal (Bombardier) informed that he is leaving the MODsafe project in June 2011 and introduced his successor Rajinder Sadheura.


Agenda

No. Start Item

1 09:00 Welcome and agreement on the agenda for the day

2 09:00 WP11: Overview on Status and Planning (TRC, TRIT) - Overview on the status of deliverables - Confirmation that no project schedule extension is needed

3 09:15 WP11: Overview on Budget and Payment (TRC) - Overview on the budget and payment (TRC), as needed - WP Leaders shall report and confirm budget values

4 09:30 WP11: Status of Periodic Reporting (TRC) - Overview in the status of periodic reporting, as needed (TRC) - Status of previous action items 5-6 as per MoM EB 2011-02-22

5 09:45 WP12: Status of dissemination activities (UITP) - Overview in the status of dissemination activities, as needed (UITP) ref. MoM WP10 2011-05-11 - Short Briefing of Coordinator’s visit at EUMASS Final Workshop in Madrid 2011-04-11 (for info)

6 10:00

Status regarding availability of (restricted) WP8/9 reports to SECUR-ED and SECURE Metro - Short Briefing on the WP8 / 9 position on this question (UITP) - Status of previous action items 1-3 as per MoM EB 2011-02-22 - Discussion / Decision / New Action as needed

7 10:15

Potential need for future standardization - Status of previous action item 4 as per MoM EB 2011-02-22

- Follow up of ERRAC recommendations (UITP) cancelled - Discussion / Decision / new Action as needed

8 10:30

Operator’s (Rheinbahn) contribution to WP7 - Status of previous action item 7 as per MoM EB 2011-02-22

- Discussion / EB Decision regarding Rheinbahn / Wiener Linien contribution to WP7 / new Action as

needed

9 10:45

Action Items - Status of previous action items as per MoM EB 2011-02-22 (covered by above topics) - Confirmation of Thales Bank Account - Confirmation of Bombardier Form C submission - New Action Items as needed

10 11:00 Next EB Meeting / Next PG Meeting





2) Overview on Status and Planning

Izaskun Arenaza provided an overview on the status of deliverables, namely D5.2, D5.3 and the 2nd Periodic Report were delivered since the last EB meeting 2011-02-22.

Deliverables D2.3, D6.3, D7.2 and D7.3 are delayed. Consensus on D2.3 and D6.3 can be expected within May 2011, consensus on D7.2 is planned for June 2011.

Given the current status of deliverables (see figure below) and considering the remaining deliverables in the light of the remaining time schedule, the Executive Board sees no reason for a project extension.

The status and planning table dated 2011-05-11 is attached.

3) Overview on Budget and Payment

Izaskun Arenaza provided an overview on the budget and payment, both for the entire project (consumption per project partners) as well as for the individual work packages. Approximately 50% of the planned project budget has spent used so far.

In the light of the status of deliverables, it appears obvious that the project will not use the entire budget as originally planned.

The Executive Board decided to apply for budget transfers for WP1 (INRETS has overspent), for WP7 (to serve the R&B offer to contribute thereto) and for WP8 / WP9 (to handle the fact that LU is not in a position to contribute as planned and to cope with the increased KITE effort spent) while the other work packages do not need budget transfers. Free budget can be used from LU, BME and TRIT, if needed.

The Plenary Group shall be informed accordingly (done in the PG / WP10 meeting 2011-05-11).

The budget and payment overview is attached as part of the status and planning table dated 2011-05-11.


4) Status of Periodic Reporting

Izaskun Arenaza informed, that the 2nd Periodic Report was submitted to the EC on 2011-05-09. It has taken multiple reminders to the project partners (approximately 150 e-mails) to collect the respective input from the work packages.

In particular

- Bombardier filled in Form C only after multiple reminders Bombardier Form C was filled in with “zero”, since Bombardier does not request payment for the project contribution. (ref. MoM EB Meeting 2011-02-22, Action Item 5, now closed)

- Thales has still not confirmed their Bank Account. (ref. MoM EB meeting 2011-02-22, Action Item 6, still open)

The Coordinator reminded that all project partners are obliged to provide the required information and contribution in time as per the consortium contract.

5) Status of Dissemination activities

This topic was postponed to the WP10 / PG meeting since there is nothing to report specifically to the Executive Board.

6) Status regarding availability of (restricted) WP8/9 reports as input to SECUR-

ED and SECUREMETRO

The Coordinator informed that WP8/9 provided their statement of principle agreement to exchange security deliverables under conditions. (ref. MoM EB meeting 2011-02-22, Action Item 2, now closed)

The Coordinator has contacted SECUR-ED and SECUREMETRO. (ref. MoM EB meeting 2011-02-22, Action Item 1, now closed)

SECUR-ED has given a principle agreement. This topic will be discussed on their next project management board meeting in June 2011. For SECUR-ED the EC Officer need to be informed since in SECUR-ED, EC representative(s) are part of the project management board.

SECUREMETRO has not yet formally replied, however they verbally announced their principle agreement during the Explanation Group Meeting back in October 2010.

It was noted, that the MODSafe project might be already finished when the other project’s security deliverables will be available in the future.

The Coordinator informed that a disclaimer has not yet been drafted. Further, some legal copyright questions and the involvement of the EC might need to be clarified. (ref. MoM EB meeting 2011-02-22, Action Item 3, open)

It was agreed to wait for the further SECUR-ED and SECUREMETRO reply. (new Action Item)


7) Potential need for future standardization

The Coordinator informed that he has distributed the question, whether there is a need for future standardization and whether and which MODSafe deliverables may be potentially used for future standardization to the work package leaders. The initial reply is attached. (ref. MoM EB meeting 2011-02-22, Action Item 4, now closed)

A discussion took place, basically with the results that

- there is no need for standardization for the technical safety areas represented by work packages 2-4, it is recommended that the respective MODSafe deliverables may be used as “Support Material”

- there might be the need for standardization for the process aspects represented by work packages 6 and 7, it is recommended that the respective MODSafe deliverables may be used as “Support Material”

- there is a need for standardization for the security aspects represented by work packages 8 and 9, in particular relevant aspects for standardization shall be mentioned (ref attachment)

- it is a common understanding to better use the term “Support Material” instead of “Guideline” since the term guideline is used on the context of application of standards.

- PD highlighted that there is an EC's strategic drive for standardization in urban guided transport safety and security. This includes the MODsafe deliverables.

It was agreed, that Prof. Schütte (for the technical safety aspects), Dr. Saghi (for the process aspects) and Patrick Dillenseger (for the security aspects) shall provide a short 3-3 lines text statement / justification for the above need for standardization. (new Action Item)

It was agreed, that the Coordinator shall further collect the work package contributions and draft a potential MODSafe project reply to the EC mandate. (new Action Item)

8) Operator’s (Rheinbahn) contribution to WP7

The Coordinator informed that Rheinbahn and Wiener Linien are members of the UITP Light Rail Sub-Committee and therein, the Working Group Safety has announced their interest in MODSafe, in particular in WP7. Their interest is to understand the proposal of potential future approval processes, in particular in the light rail sector.

Rheinbahn offers to be the communication counterpart to MODSafe, they offer to review and comment on draft WP7 deliverables. They do not intend to actively participate in meetings.

Since the members of this Working Group Safety belong to the UITP Sub-Committee, the EB agreed to their contribution. It was also agreed that the communication shall be via UITP and that the Coordinator shall trigger UITP accordingly. (new Action Item)


9) Action Items

The Action Items 1, 2, 4, 6 and 7 from the previous EB meeting (ref. MoM 2011-02-22) are declared closed. The Action Items 3 and 5 from the previous EB meeting (ref. MoM 2011-02-22) are still open, they are transferred.

Action Items

No. Party Due date

1 TRIT Transferred from EB 2011-02-22

The Coordinator shall draft a disclaimer statement for the exchange of security deliverables between MODSafe, SECUR-ED and SECURE-METRO.

2011-06-30

2 Thales Transferred from EB 2011-02-22

Thales to confirm Bank Account.

2011-05-31

3 TRC To make a proposal to the EB for the transfer of budget between partners

2011-06-30

3 TUD BME RATP

Provide a 3-5 lines text statement / justification on the need for standardization - Prof. Schütte for the safety aspects - Dr. Saghi for the process aspects - P. Dillenseger for the security aspects

2011-05-20

4 TRIT The Coordinator shall further collect the work package contributions and draft a potential MODSafe project reply to the EC mandate.

2011-06-30

5 TRIT UITP

The Coordinator shall trigger UITP once WP7 deliverables are in place, suitable for Rheinbahn / Wiener Linien review and comment.

UITP shall forward the respective deliverables and collect the comments.

permanent action for

the duration of WP7

10) Executive Board decisions to be announced to the Plenary Group

The following EB decision(s) as of 2011-05-11 are to be announced to the Plenary Group:

- Decision to apply for Budget Transfer


The next EB meeting shall take place 27 September 2011 from 09:00h to 11:00h at RATP premises (before the WP 10 meeting).

The next PG meeting shall take place 27 September 2011 from 11:00h to 17:00h at RATP premises (in parallel to the WP 10 meeting).

Attachments

- Status of Action Items of MODSafe EB Meeting 2011-02-22 as per 2011-05-10

- Status of Action Item 4 of MODSafe EB Meeting 2011-02-22 as per 2011-05-10

- OTH_MODSAFE Status and Plannung_TRIT TRC_WP11_09.05.2011.xls

- Signed List of Participants


Status of Action Items of MODSafe EB Meeting 2011-02-22 as per 2011-05-10

No. Party Action Due date Status

1 TRIT The Coordinator shall contact both, the SECUR-ED coordinator (Yves Perreal from Thales, [email protected]) and the SECURE-METRO coordinator (Conor O’Neill from Newrail, [email protected]) and sort out these projects’ preparedness to exchange security related deliverables.

2011-03-15 Contact done 2011-05-06 (after Action Item 2 due to linkage)

SECUR-ED principle agreement received 2011-05-09 (see below), will be discussed on their next project management board meeting in June. Yves Perreal states that at least for SECUR-ED the EC Officer need to be informed.

Waiting for formal SECURE-METRO reply, however they already verbally announced their principle agreement during the Explanation group Meeting back in Oct 2010.

2 UITP UITP shall check with WP8 and WP9 members and confirm the WP’s agreement to exchange security deliverables with SECUR-ED and SECURE-METRO

2011-03-15 WP8 / 9 provided the statement of principle agreement under conditions on 2011-04-22.

Closed 2011-04-22

3 TRIT The Coordinator shall draft a disclaimer statement for the exchange of security deliverables between MODSafe, SECUR-ED and SECURE-METRO.

2011-03-30 Open

Linked with and depending on the outcome of Action Item 1.

Furthermore, some legal copyright questions and the involvement of the EC might need to be clarified.

4 TRIT The Coordinator shall contact the MODSafe work package leaders and ask them for a justified work package statement on the potential need for future standardization and whether and which deliverables they identity to be potentially used for future standardization.

2011-03-15 Done 2011-03-08

Reply received from:

- RATP (WP10)

- TUD (WP2 / WP5

- Bombardier (WP3)

- TRIT (WP6)

- UITP (WP8 / WP9)

No Reply received from

- IFSSTAR (INRETS) (WP1)

- BME (WP7)

- UITP (WP4)

mailto:[email protected]


No. Party Action Due date Status

5 UNIFE / TRC

BW to provide Thales bank account known from other EC project.

TRC to check Thales bank account.

2011-03-15 Open

Thales bank account known from other EC project received from UNIFEE.

Formal Thales confirmation still outstanding.

6 BT / TRC

MT to arrange submission of Form C.

2011-03-15 Filled in 2011-05-06

Following Coordinator’s deadline, From C was filled in by Bombardier 2011-05-06 with “Zero” since Bombardier does not request payment for MODSafe for some internal formal reasons.

7 TRIT The Coordinator shall contact Rheinbahn, having expressed their interest to contribute to WP7, to clarify their intention and attitude.

2011-03-15 Closed 2011-03-18

Rheinbahn and Wiener Linien are members of the UITP Light Rail Sub-Committee and therein, the Working Group Safety has announced their interest in MODSafe, in particular in WP7. Their interest is to understand the proposal of potential future approval processes, in particular in the light rail sector.

Rheinbahn offers to be the communication counterpart to MODSafe, they offer to review and comment on draft WP7 deliverables. They do not intend to actively participate in meetings.

Since the members of this Working Group Safety belong to the UITP Sub-Committee, the MODSafe Coordinator’s recommendation is to agree thereon.


Status of Action Item 4 of MODSafe EB Meeting 2011-02-22 as per 2011-05-10

Work Package

potential need for future standardization “yes” or “no”

identification whether and which deliverables to be potentially used for future standardization

Comment / Justification

WP1

WP2 Not a standard, but a Guideline

Standard means “obligation” to respect, it is not appropriate, but D2.2 is considered very helpful as a Guideline.

As the risk analysis shows, operators shall be supported by an inventory guideline, but for detailed estimation of how hazards and risks are covered, the local specificities are too important for inflexible fixings.

WP3 No D3.1 and D3.2 are working tools for finding the safety requirements and not suitable for future standardization.

WP4

WP5 Not a standard, maybe a Guideline

D4.2 contains the functions, may serve as guideline for SIL allocation process AND Functional Model. (D5.2 not necessary)

The discussion on the object model and interpretation of Functions has shown, that we have probably already passed the limits of what is “normalizable” in highly diverse local urban guided transport. No further standard recommended. (But maybe guidelines).

WP6 Yes Life Cycle Approach EC Mandate requires checking the MODSafe results as a potential source for identifying areas for potential future standardization.

WP7

WP8 / 9 Yes 1. Urban transport security terminology (Definition of terms, abbreviations, and multilingual glossary of such terms) 2. Typology of threats to urban transport systems 3. Typology of offences in urban transport systems 4. Security zoning of public spaces in urban transport systems 5. Risk analysis methodology in urban transport systems

WP10 no


Signed List of Participants




5. Fourth Plenary Group Meeting 11th of May 2011

Presentations of the WP status were made during the meeting of WP10. WP10 meetings are always organised back to back to the Executive and Plenary Group in order to avoid duplication of the work.

Venue: RATP – Val de Fontenay, France Building DOLOMITES – 3rd Floor – Room D-OPERA

Time: 11:00h – 17:00h


Name Organisation

CAPEL, Robert Alstom

LEGOFF, Gilles Ansaldo

GIRKA, Regis AREVA TA

SAGHI, Balázs, Dr. BME

SADHEURA, Rajinder Bombardier

TENNEDAL, Mats Bombardier

ALONSO, Alfonso Garcia Dimentronic

BENARD, Vincent IFSTTAR

CASSANI, Mirella KITE

PARRIS, Gab LUL

SCHMIDT, Hartmut Rail & Bus

COINEAU, Daniel RATP

DILLENSEGER, Patrick RATP

LOVELUCK, Thimothee RATP

LUDOVIC, Michel RATP

ROGGE, Catherine RATP

PELLOT, Michael TMB

PICAS, Jordi TMB

ARENAZA, Izaskun TRC

WIGGER, Peter TRIT

SCHÜTTE, Jörg, Prof. TUD

AMSLER, Yves UITP

HOOGENDOORN, Caroline UITP

SCHÖN, Walter UTC

POLET, Philippe UVAL / UHVC


Agenda

No. Start Item

1 11:00 Welcome and agreement on the agenda for the day

2 11:00

WP11: Administrative / Financial Overview (TRIT / TRC)

- Status of the Project and Overview on the deliverables, as needed (TRIT)

- Overview on Budget and Payment, as needed (TRC)

3 11:30 WP 10 Meeting running in parallel, see WP10 agenda

4 17.00 Next EB Meeting / Next PG Meeting





2) Overview on Status and Planning

The following figure provides an overview on the status of deliverables.

3) Overview on Budget and Payment

Izaskun Arenaza (TRC) provided an overview on the budget and payment, both for

the entire project (consumption per project partners) as well as for the individual

work packages. Approximately 50% of the planned project budget has spent used

so far.

In the light of the status of deliverables, it appears obvious that the project will not

use the entire budget as originally planned.

The budget and payment overview is attached as part of the status and planning

table dated 2011-05-11.

4) Executive Board decisions to be announced to the Plenary Group

The following EB decision(s) as of 2011-05-11 was announced to the Plenary

Group:

Decision to apply for Budget Transfer

Izaskun Arenaza (TRC) informed, that the Executive Board decided to apply for

budget transfers for WP1 (INRETS has overspent), for WP7 (to serve the R&B offer

to contribute thereto) and for WP8 / WP9 (to handle the fact that LU is not in a

position to contribute as planned and to cope with the increased KITE effort spent)

while the other work packages do not need budget transfers. Free budget can be

used from LU, BME and TRIT, if needed.


5) Overview on the Work Packages

Refer to the Minutes of Meeting of the WP10 meeting, which was running in parallel

with the 4th PG meeting with the same forum present.

6) Potential “Final MODSafe Workshop”

It was discussed, whether or not the project shall have a final workshop at the end of

the project (as other EC projects do). So far, such an event is not foreseen

according to the Description of Work (DoW) and the budget. The Coordinator

offered to clarify this possibility in the light of the contract and budget and regarding

a potential event location.

7) Action Items

No. Party Due date

1

TRC To make a proposal to the EB for the transfer of budget between partners. (taken from EB 2011-05-11 action 3, same for PG)

2011-06-30

2 TRIT / TRC

Clarify the possibility of a final workshop in the light of the contract and budget and regarding a potential event location.

2011-09-27 (next PG meeting)


The next EB meeting shall take place 27 September 2011 from 09:00h to 11:00h at

RATP premises (before the WP 10 meeting).

The next PG meeting shall take place 27 September 2011 from 11:00h to 17:00h at

RATP premises (in parallel to the WP 10 meeting).

Attachments

- Signed List of Participants

- OTH_MODSAFE Status and Plannung_TRIT TRC_WP11_11.05.2011.xls











Documents

Annual Meeting Documentation - MODSafe · 2012. 1. 18. · short overview on the mandate for standardisation in the field of UGT (UITP) - discussion (all) - agreement on actions as