corridor c - rfc-northsea-med.eu · history 1/4 two european directives launched the ertms...

35
Corridor C Sylvain Mosmann Corridor C ERTMS Coordinator ERTMS on Corridor C/2 27 June 2012

Upload: others

Post on 24-Jun-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Corridor C Sylvain Mosmann Corridor C ERTMS Coordinator

ERTMS on Corridor C/2

27 June 2012

Page 2: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

2/20 2/23

Agenda

1. What is ERTMS ?

2. Corridor C/2 ERTMS Rollout

3. Fitting ETCS on locomotives

Page 3: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

ATB / ATB-NG

AWS / TPWS

TVM / KVB

ASFA / LZB

EBICAB 700

BACC / SCMT

TBL

EVM

INDUSI /LZB

KHP

INDUSI / LZB

EBICAB 900

EBICAB 700 / 10000

ZUB 123

European signalling systems

SIGNUM / ZUB

MEMOR II +

3

Page 4: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

ERTMS

European signalling system

ERTMS

ERTMS

4

Page 5: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Glossary

ERTMS: European Rail Traffic Management System

ETCS: European Train Control System

To make it simple: ERTMS = ETCS + GSM-R

5

Page 6: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

History 1/4

Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional network

These directives set a deployment objective of 10 to 12 years, on a start-up core network, including freight corridors, then on the "ETCS Net"

They called for the application of the CCS TSI for new and renewed lines

In 2008 the two initial directives were merged into a single one: 2008/57/CE, and two decisions about CCS TSI (2006/679 and 2006/860) were recently merged into 2012/88

6

Page 7: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

History 2/4

On 17 March 2005, the European Commission and the rail industry signed a Memorandum of Understanding (MoU) establishing the basic principles of an EU deployment strategy for ERTMS

The main objective of that Memorandum of Understanding was to define the contribution of the actors in order to ensure the progressive setting up of an ERTMS equipped network within 10-12 years.

7

Page 8: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

History 3/4

A second MoU was signed on 4 July 2008, with the following specific objectives: To foster coordination and collaboration in order to ensure the

compatibility of existing lines. This compatibility shall be based on the SRS version 2.3.0d and the relevant GSM-R specifications

To foster coordination and collaboration with a view to ensuring that, by 2012, an error free, tested and legalised baseline 3 of the ETCS specifications is available

To clarify which specification baseline is to be used in tenders and as track access conditions

To improve the efficiency and the cost effectiveness of the existing testing and certification procedures, for both ETCS and GSM-R

To streamline the current procedure of testing and approvals in order to progressively reach a point where all procedures related to testing and approval of ETCS and GSM-R on board units can be completed following a common, unique and efficient procedure

To lay down the agreement of the sector on a number of measures aimed at speeding up the deployment of the ETCS

8

Page 9: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

History 4/4

The most recent MoU was signed in Copenhagen on 17 April 2012, with the following specific objectives: To ensure that the ERTMS specifications are maintained/upgraded in a

controlled way, by applying the ERA Change Control Management (CCM) process

To set up and support an appropriate mechanism to provide to ERA in a timely manner the return of experience of the early implementations of Baseline 3-based projects

To streamline the current procedure of testing and authorisation in order to progressively reach a point where all procedures related to testing and authorisation of on-board units can be completed following a common, unique and cost-effective procedure

To confirm the commitment of the European Rail sector Associations to bring forward concrete cases where requirements deviating from the TSI would be imposed and/or in cases where national rules or requirements would hamper the objectives above

To confirm the agreement of the sector on a number of measures aimed at speeding up the implementation of the ETCS considering economical aspects

9

Page 10: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Stakeholders

European Railway Agency (ERA), in charge of ERTMS specifications and TSI definitions

MoU Steering Committee, chaired by European Coordinator Karel Vinck, composed by: UNIFE CER UIC EIM GSM-R Industry Group ERFA

ERTMS Users Group 10

Page 11: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

ETCS Levels 1/3

Level 1 Based on punctual

information delivered by in-track balises

Track circuits or axle counters needed to localise the train

Infill function possible through advanced balises, euroloops or radio infill

In most cases overlaid on legacy lateral signalling systems

11

Page 12: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

ETCS Levels 2/3

Level 2

Based on continuous exchange of information through GSM-R

Track circuits or axle counters needed to localise the train

No lateral systems needed

May be overlaid on level 1 equipment

12

Page 13: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

ETCS Levels 3/3

Level 3 Based on continuous exchange of information through

GSM-R No more need to localise the trains through in-track

equipment The train reports its position The train ensures its own integrity No lateral systems needed Allow mobile block operation

Not implemented yet, but ERTMS Regional (Sweden) is

derived from Level 3 concepts

13

Page 14: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Some ETCS Modes

Full supervision (FS) : the system ensures the security alone

Shunting (SH) : mode for shunting, low level of control On Sight (OS) : mode including ceiling speed monitoring

and check danger point Staff Responsible (SR) : allow to pass an out of order

signal, no danger point check but ceiling speed monitoring

Non leading (NL) : mode to manage a train with several locomotives

STM National (SN) : to use national systems Limited Supervision: from stop/go conditions to ceiling

speed monitoring (Baseline 3 only)

14

Page 15: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Baselines 1/2

Baseline 2 The only current legal version is 2.3.0d Drawback of this version: the braking curves are

not defined Recommendation from the Corridor ERTMS

Committee: to use the available definition of Baseline 3 braking curves to implement on-board systems

Old 2.2.2X systems are required to be upgraded to 2.3.0d

15

Page 16: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Baselines 2/2

Baseline 3 Specifications are expected to be validated and

officialised by the end of 2012 One of the main upgrades concerns the definition

of the braking curves The second main upgrade is the incorporation of L1

Limited Supervision promoted by SBB (technical interoperability, no operational interoperability)

Better management of level crossings Improvement of track conditions descriptions Nota: either in B2 or B3, the subset of functions

used for trackside engineering depends on the network: all functions are not used!

16

Page 17: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

2.3.0d B3

2.3.0d

2.3.0d

17

Interoperability 2.3.0d – Baseline 3

B3 B3

2.3.0d

B3

17

Page 18: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

18

On board components

Page 19: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

19

On board components

Page 20: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

20

150100

4000

2000

1000

500

0

1

250

200

30050

0 400

17:33:25

Over-ride

Data view

Spec

Main

67

0+

5

+

Driver Machine Interface: DMI

Permitted speed

Actual speed

Target distance

Mode

ERTMS level

Target speed

Area for text

messages

Planning area

Time

Speed reduction

Gradient

Speed control

Page 21: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

21

SvL

Speed

EoA

MRSP

Driving with ETCS 150

100

1

162

200

30050

0 400

61

30

150100

1

271

200

30050

0 400

67

30

150100

1

491

200

30050

0 400

67

30

150100

1

934

200

30050

0 400

67

30

150100

1

200

30050

0 400

67

150100

1

1134

200

30050

0 400

67

150100

1

200

30050

0 400

67

150100

1

39

200

30050

0 400

25

30

Intervention Overspeed Indication Pre-Indication

Page 22: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

ETCS Advantages for drivers

The most restricted speed limit is always displayed: no longer need to memorize speed sequences

The permitted speed is dynamically displayed: the driver always know where he is compared to an emergency brake intervention

Cab-signalling: not dependent on weather conditions

Harmonisation of operating rules

22

Page 23: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

23/20 23/23

Agenda

1. What is ERTMS ?

2. Corridor C/2 ERTMS Rollout

3. Fitting ETCS on locomotives

Page 24: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Rotterdam Gent

Lille

Lyon

Ambérieu

Anvers

Metz

Strasbourg

Bâle

Bettembourg

Nancy

Longuyon

Dijon

Namur

Rollout 2020

24

Page 25: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Anvers

Metz

Strasbourg

Bâle

Bettembourg

Namur

Rollout 2015

2.3.0d Level 1

25

Page 26: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Rollout 2016 Anvers

Metz

Strasbourg

Bâle

Bettembourg

Namur

2.3.0d Level 1

26

Page 27: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Important milestones

2017: ETCS mandatory to run on the CFL network (2.3.0d L1)

2022: entire Infrabel network equipped with ETCS, either 2.3.0d or B3, L1 or L2, with some sections with L1 LS

RFF: KVB will be deactivated on routes 10 years after their ETCS fitment -> ETCS becomes mandatory on these routes

27

Page 28: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Access to Muttenz

From 2013 fitment with KVB+PZB or ZUB will be mandatory to run between St Louis and Muttenz

From 2015 the Basel area will be equipped with ETCS B3 L1 LS

2.3.0d trains will have to be fitted with KVB+PZB (STM or standalone) to access Muttenz

28

Page 29: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

29/20 29/23

Agenda

1. What is ERTMS ?

2. Corridor C/2 ERTMS Rollout

3. Fitting ETCS on locomotives

Page 30: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Feedback on known problems

Homologation process

Associated costs and delays

30

Page 31: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Relationship with NSAs

Cross Acceptance: B-NL-F-L-CH agreement signed in 2008 by the

respective NSA’s for locomotives and passenger trains.

D-B-L agreement signed in 2010 by the respective NSA’s for locomotives and passenger trains.

What is the feeling about their effectiveness ?

31

Page 32: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

Test facilities

Who manages the homologation process : RUs, ROSCOs or suppliers ?

Would a test tool with Corridor scenarios be useful ?

32

Page 33: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

33/20 33/23

Agenda

1. What is ERTMS ?

2. Corridor C/2 ERTMS Rollout

3. Fitting ETCS on locomotives

4. What's next?

Page 34: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

What's next ?

Which ERTMS topics to be covered in the next RU Advisory group?

Which ERTMS information to be displayed on the Corridor Web site?

Attendance in the ERTMS Committee meetings

34

Page 35: Corridor C - rfc-northsea-med.eu · History 1/4 Two European Directives launched the ERTMS deployment: in 1996, 96/48 for the high speed network in 2001, 2001/16 for the conventional

35/20 35/23 © Corridor C

Contacts Head Office 9, place de la Gare L-1616 Luxemburg [email protected] www.corridorc.eu www.corridorc.eu

The sole responsibility of this publication lies with the author. The European Union is not responsible for any use that may be made of the information contained there in.

ACF

35