ertms deployment in spain

11
ERTMS DEPLOYMENT IN SPAIN ERTMS DEPLOYMENT IN SPAIN ERTMS CCRCC 2015 T i Mt S t it B i C ERTMS CCRCC 2015 T i Mt S t it B i C T urning a Mature System intoa Business Case T urning a Mature System intoa Business Case Lille, 22 nd 23 rd September 2015 Lille, 22 nd 23 rd September 2015 1

Upload: vuongthuan

Post on 05-Jan-2017

241 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: ERTMS DEPLOYMENT IN SPAIN

ERTMS DEPLOYMENT IN SPAINERTMS DEPLOYMENT IN SPAIN

ERTMS CCRCC 2015T i M t S t i t B i C

ERTMS CCRCC 2015T i M t S t i t B i CTurning a Mature System into a Business CaseTurning a Mature System into a Business Case

Lille, 22nd‐23rd September 2015Lille, 22nd‐23rd September 2015

1

Page 2: ERTMS DEPLOYMENT IN SPAIN

INDEX

1. SPANISH INFRASTRUCTURE ERTMS DEPLOYMENT

2 ERTMS ON BOARD EQUIPMENT CURRENT SITUATION2. ERTMS ON BOARD EQUIPMENT. CURRENT SITUATION

3.   MIGRATION

3.1  VERSION COMPATIBILITY3.2  MIGRATION REQUIREMENTS3.3  MIGRATION STRATEGY3.4  BUDGET AND PROGRESS3.5  SPANISH VIEW FOR B2 SPECS. MIGRATION SUMMARY

4 SPANISH APPROACH TO BASELINE 3 – CONCLUSION4. SPANISH APPROACH TO BASELINE 3  CONCLUSION

2

Page 3: ERTMS DEPLOYMENT IN SPAIN

 

Page 4: ERTMS DEPLOYMENT IN SPAIN

2. ERTMS ON BOARD EQUIPMENTCurrent situation 

362 vehicles running in commercial operation• 2.2.2 + CR*: Upgrading is needed• 2.3.0.d – CR: Some CR are disabled in order to be

compatible with 2.2.2 lines

Onboard systems currently in service:

* CR Ch R t

42001 2019

* CR: Change Request

Page 5: ERTMS DEPLOYMENT IN SPAIN

3.MIGRATION. 3.1 Version Compatibility 

In 2008, European Commission adopts 2.3.0.d version as standard

SRS 2.3.0d

2.3.0d version is not compatible with previous versionsSub‐108 v1.2.0Update Annex A

2.3.0d

Reference laboratory (CEDEX) have been used for testingReference laboratory (CEDEX) have been used for testingcompatibility level between different SRS versions in order tomanage the migration process

In order to guarantee interoperability between track and trainsIn order to guarantee interoperability between track and trainsand to avoid captive trains, it is neccesary to define a complexmigration plan that requires coordination between RU (RENFE)and IM (ADIF) with Ministerio de Fomento leadershipand IM (ADIF), with Ministerio de Fomento leadership

5

Page 6: ERTMS DEPLOYMENT IN SPAIN

 

Page 7: ERTMS DEPLOYMENT IN SPAIN

3. MIGRATION. 3.3 Migration Strategy 

L1 2 3 0d

Level 1 / 2 KEYSL1 backup system availability

L1 compatibility between 2.2.2 train & 2.3.0d track

BarcelonaLleida

L1 + L2 v2.3.0.d L1 + L2

2.3.0.d

L1 2.3.0d-L1/2 2.2.2+L1/2 2.2.2+ Current

Guadalajara

Tarragona

Valladolid

Segovia

Zaragoza

Madrid

L1 + L2 v2.3.0.d

L1 2.3.0d-L1/2 2.2.2+

Level 1 / 2

Madrid

1. Infrastructure L1 migration to v2.3.0.d. (2014-2015)Infrastructure Engineering rules compatible with

L1 2.3.0d + Eng. Rules

L2 2.2.2+

Level 1

1

Córdoba

ast uctu e g ee g u es co pat b e tv2.2.2+ in trains.

2. Train migration to 2.3.0.d. (2015-2019)

Trains run in L1 v2.3.0.d-CR & v2.2.2+ and in L2 v2.2.2+ 2.2.2.+ 2.3.0d

L1 2.3.0d + Eng. Rules 2

Málaga

Infrastructure L2 unsubscribe (v2.2.2+).Trains run in L1 v2.3.0.d & v2.2.2+

3 Infrastructure L2 migration to 2 3 0 d (2016)

L1 + L2 v2.3.0.d

2.3.0d

Level 1 / 2

7

3. Infrastructure L2 migration to 2.3.0.d. (2016)2.3.0d

L1 2.3.0d + Eng. Rules

L2 2.3.0d3

Page 8: ERTMS DEPLOYMENT IN SPAIN

 

Page 9: ERTMS DEPLOYMENT IN SPAIN

3. MIGRATION. 3.5 Spanish view for B2 specs. Summary  

2.3.0d is a reference version and it works properly2.3.0d is a reference version and it works properly

We cannot afford a change of specifications that would imply

Backwards compatibility must be guaranteed

the upgrading of lines and current fleet

Backwards compatibility must be guaranteed

Otherwise we should stop ERTMS deployment This is notOtherwise, we should stop ERTMS deployment. This is notpossible because systems are in service

A commitment for 2.3.0d products maintenance must beguaranteed

9

Page 10: ERTMS DEPLOYMENT IN SPAIN

4. SPANISH APPROACH TO B3 ‐ CONCLUSION  

InfrastructureADIF d i i O l 2 3 0 d i ill b i t ll d th t kADIF decision: Only 2.3.0.d version will be installed across the network

• B3 infrastructure deployment is not an option to be considered and it is not scheduled

• Next steps: End migration process and mantain consistency and homogenity in the network

OnboardAll future versions of onboard equipment must be compatible with lines version 2.3.0d

The compatibility analysis (BCA report) and the impact should be performed before each new release of the specifications

• B3 products aren’t mature and fully tested and we need to keep our trains moving on ourinfrastructure.

• Next steps: 2.3.0.d lines already in service and, right now, we need onboard equipmentcompatible with 2 3 0 d lines in service as soon as possible Only 2 3 0d trains is the optioncompatible with 2.3.0.d lines in service as soon as possible. Only 2.3.0d trains is the option.

IM & RU investments must be guaranteed

10

g

Page 11: ERTMS DEPLOYMENT IN SPAIN

Thank you for your attention

11