1

Upgrade to 2.3.0.d

CCRCC 2013 Lille, 12 Novembre 2013

Silvia Domínguez

2

Index

1. Objective

2. ETCS deployment situation

3. Version management and migration plan

4. Compatibility analysis and B3 impact

5. Conclusions

3

1. Objective

2. ETCS deployment situation

3. Version management and migration plan

4. Compatibility analysis and B3 impact

5. Conclusions

The objective of the upgrade from our current ETCS

implementations 2.2.2 to version 2.3.0d is to

achieve:

• a fully interoperable system, no ETCS borders

• according to the European Reference Version

2.3.0d

Why to upgrade to 2.3.0.d?

4

European Version 2.3.0d is the reference version as stated:

• in the MoU clause 16:

SRS 2.3.0, as adopted by the European Commission on 23 April 2008, and

known as ‘2.3.0d’ currently constitutes the unique and interoperable

technical reference which will ensure the interoperability of all ETCS

equipment deployed in Europe.

• It is technically defined in Commission Decision 2012/88 and

amended in 2012/696

• ETCS version 2.3.0.d covers all the Spanish functional and

operational needs for the network

Why to upgrade to 2.3.0.d?

5

6

Index

1. Objective

2. ETCS deployment situation

3. Version management and migration plan

4. Compatibility analysis and B3 impact

5. Conclusions

Line Supplier ETCS Level Version Length

In service

Madrid - Lérida Ansaldo (CSEE) 1+2 2.2.2+ 490 km

Lérida - Barcelona Thales 1+2 2.2.2+ 190 km

Madrid - Valladolid Thales 1+2 2.2.2+ 180 km

Córdoba - Málaga Invensys (Dim.) 1+2 2.2.2+ 155 km

Madrid - Valencia Invensys (Dim.) 1+2 2.3.0.d 470 km

Zaragoza - Huesca Alstom 1 2.2.2+ 80 km

La Sagra – Toledo Thales 1+2 2.2.2+ 21 km

Barcelona – Figueras Thales 1+2 2.3.0d 131 km

Orense – Santiago Thales 1+2 2.3.0d 90 km

Commuter line Madrid Thales + Invensys 1+2 2.3.0d 50 km

Under construction

Albacete – Alicante Alstom 2 2.3.0d 165 km

Total 2.022 km

ETCS deployment Infrastructure

7

8 DIRECTION GÉNÉRALE DE DÉVELOPPEMENT DE L’INFRASTRUCTURE

Direction d’Innovation Technologique

Lleida-Barcelona ERTMS-N1-2 Thales

(2.2.2.+)

Madrid-Valladolid ERTMS-N1-2 Thales

(2.2.2.+)

La Sagra-Toledo ERTMS-N1-2 Thales

(2.2.2.+)

Córdoba-Malaga ERTMS-N1-2 (2.2.2.+)

Madrid-Lleida ERTMS-N1-2 Ansaldo

(2.2.2.+)

Zaragoza-Huesca N1- Alstom (2.2.2.+)

Madrid-Sevilla LZB ERTMS NSTM LZB

Madrid-Valencia-Albacete N1-2 Dimetronic (2.3.0.d)

Madrid Commuter lines ERTMS-N1-2 Thales and

Dimetronic (2.3.0.d)

Figueras-Perpignan ERTMS-N1-2 Ansaldo

(2.3.0)

Albacete-Alicante ASFA y N2 (2.3.0.d.)

Orense –Santiago (2.3.0.d.)

ETCS deployment Infrastructure (II)

8

ERTMS equipped trains

9

TRAIN ERTMS

SUPPLIER ERTMS LEVEL

No.

Units

S-100 ALSTOM L1 / L2 24

S-104 ALSTOM L1 / L2 20

S-114 ALSTOM L1 / L2 13

S-102/112 SIEMENS L1 / L2/ STM LZB 16/30

S-103 SIEMENS L1 / L2/ STM LZB 26

S-120/121 ANSALDO L1 / L2 57

S-130 BOMBARDIER

L1 / L2 / STM LZB /

STM EBICAB 44

Alaris INVENSYS L1 / L2/ STM EBICAB 10

v2.2.2.+ HS Total 240

TRAIN ERTMS

SUPPLIER

ERTMS

LEVEL

No.

units

S-446/447/450 INVENSYS L1 / L2 94

Civias ALSTOM L1 / L2 123

v.2.3.0.d LOCAL Total

217 LOCO

ERTMS

SUPPLIER

ERTMS

LEVEL

No.

units

252 SIEMENS L1 / L2 4

v.2.2.2.+ LOCOS 4

Total 244 vehicles to migrate

10

Index

1. Objective

2. ETCS deployment situation

3. Version management and migration plan

4. Compatibility analysis and B3 impact

5. Conclusions

Version management and migration plan

The work is coordinated by the Spanish ETCS versions working

group through the following tasks:

11

• Analyse the technical aspects related to compatibility between ETCS

versions 2.2.2 and 2.3.0.d, focusing on the Spanish implementations

• Follow up any incidence during APS or open point raised within the

projects and related to ERTMS specifications

• Define the migration technical conditions

It is formed by experts from Ministry of Fomento, Adif, Renfe,

Ineco and CEDEX.

Migration plan should be able to update infrastructure

and fleet to 2.3.0d while maintaining the commercial

timetable

In addition, there are the following requirements:

• Extend the level 2 version 2.3.0.d commercial operation

• Keep the fleet freedom over the network

• Coordinate the migration of vehicles and infrastructure

• Coordinate the migration of 6 different ERTMS suppliers

Migration strategy. Challenges

12

• Network generic engineering rules:

Avoid the use of functions on the infrastructure that are not backwards

compatible and not essential for the operation.

• Specific migration guidelines:

Use of specific engineering rules (2.3.0d compatible) for the

implementation of some functions.

• Resolution of shortcomings in the reference specifications:

Consider mitigation measures possible with the already existing 2.3.0.d

functionality.

Migration is financed by the TEN-T Executive Agency through the

project "2011-ES-60001-P Upgrade of Spanish high-speed lines and

trains to ERTMS 2.3.0.d"

Migration strategy. Compatibility Key points

13

Train\ Track 2.2.2+

Level 1 Train 2.2.2+

Level 2 Train 2.2.2+

2.3.0d

Train 2.3.0d

Train 2.3.0d

Current

infrastructure

Migrated

infrastructure

• Current 2.2.2.+ Renfe fleet is able to run over all Adif infraestructure in L1.

However, this fleet needs to be migrated to run in all L2 2.3.0.d lines.

• Compatibility achieved in L1 allows the migration of the trains and the

infrastructure in L2 without disruption of the commercial service.

Migration strategy. Summary version compatibility

(+ CR 458)

(+CR 458)

Train 2.2.2+

(with engineering

rules)

14

1. Migration of Level 1 trackside to 2.3.0.d

APS of CCS trackside subsystem + impact analysis on existing vehicles

2. Migration of vehicles to 2.3.0.d

APS of the CCS onboard subsystem + integration with Level 1 network

3. Migration of Level 2 trackside to 2.3.0.d

APS of CCS trackside subsystem + integration of vehicles for the Level 2

operation

Migration strategy. Placing in service

It is required the use of the recommendation 2011/217 after adapting

the works performed in previous APS while better allocating

the responsibilities and strengthening the role of NoBos and

Assessment bodies

15

16

Index

1. Objective

2. ETCS deployment situation

3. Version management and migration plan

4. Compatibility analysis and B3 impact

5. Conclusions

The backwards compatibility analysis between Baseline 3 and Baseline 2

(2.3.0d) must be completed and agreed at the sector level with the

highest priority before the maintenance release

All Baseline 3 trains must be able to run over 2.3.0d infrastructure. All

modifications to Baseline 3 must include a explicit backwards

compatibility analysis.

Baseline 3 Baseline 2

Art 19 of 2012 MoU: As laid down in the 2008 MoU, trains equipped with ERTMS Baseline 3 will be able to run on lines equipped with Baseline 2 version 2.3.0d without any additional technical or operational restrictions created by ERTMS/ETCS. Baseline 3 specifications are based on this principle of backward compatibility. This principle has been the basis of the

work performed by the sector and ERA throughout the writing of the specifications and will be validated as a priority during the finalisation of the Baseline 3 specifications.

Art 17 of 2012 MoU. This MoU recognizes that this version (2.3.0.d) shall remain in force in the future. This will protect the investments made by the sector and interoperability in

countries that have chosen Baseline 2 as their reference.

17

18

Index

1. Objective

2. ETCS deployment situation

3. Version management and migration plan

4. Compatibility analysis and B3 impact

5. Conclusions

Lessons Learnt, what do we need? Stable set of specifications

• This has been achieved in the MoU for the SRS 2.3.0.d and there are active groups working on the rest of specifications

• Migration of the lines to a version compatible with v230d trains, 2.3.0.d covers all the functional and operational needs in the Spanish network

• Backwards compatibility for the new baseline 3 has to be guaranteed

Strengthen the role of the NoBo and assessment bodies

• Harmonised process and certificates

• The certificates contain all the relevant information (deviations)

Clear process for authorisation of placing in service

• Engineering & operational guidelines for critical points

• Separation of authorisation processes: trackside, train and integration.

• All the entities involved should have a clear role

19

Tren 2.3.0.d Tren ‘Baseline

3’

2000 2006 2005 2004 2001 2002 2003 2007 2008 2009 2010 2011 2012 2013

Primeras especificaciones

técnicas del

ERTMS

TSI CCS 2006/679/EG

TSI CCS 2004/446/EG

TSI CCS 2002/731/CE

Incluye

SRS 2.2.2

TSI CSS 201/73/EC

(HS Y CR)

TSI CCS 2007/153/CE

TSI CSS 2006/860/CE

Incluye

SRS 2.3.0

TSI CSS 2008/386/CE

Incluye

SRS 2.3.0.d

MADRID-LERIDA

LERIDA-TARRAGONA

SEGOVIA-VALLADOLID MADID SEGOVIA

CORDOBA-MALAGA LA SAGRA-TOLEDO

TARRAGONA-BARCELONA ZARAGOZA-HUESCA

CERCANIAS MADRID-VALENCIA

BARCELONA-FRONTERA FRANCESA

S121

S130 S103

S120

S102 S102

S104 S104

SRS Baseline 3

LÍNEA PILOTO ALBACETE-VILLAR DE

CHINCHILLA

2015

TSI CCS 2012/88

SRS Baseline

3.4.0

ALBACETE - ALICANTE

??

Modifications of the ETCS specifications

Backwards compatibility of any modification of

the Baselines

Conclusion

Trains equipped with the new ETCS version shall be

able to run in the lines designed with the reference

version baseline 2.3.0.d

20