1

BanedanmarkSøren Degnegaard

Legacy signalling

to

ERTMS Level2 Baseline3 R2 +

2

Basic requirements:

• Business continuity

• Interoperability

• LifeCycleCost optimisation

• Growth potential (+50% capacity 2030)

Basic plan:

• Country wide "brownfield" rollout

• One set of Operational Rules

• ERTMS Level2 + IP enabled/ready

3

Legacy Radio -> GSM-R Plan

2011-2013

1. GSM-R Voice rollout

2. CabRadio migration window

2015-2016

3. GSM-R ETCS enhancements rollout

5

+ GSM-R Voice Network

+ eLBA

+ Analog/GSM-R WS

GSM-R CabRadio

Network first migrationTrackside voice:

Analog Radio Network

Location Data Base

Analog Voice CTS

Trains:

Analog CabRadiotwo year window

6

ETCS

• 3-Step plan

1. Joint Test Lab functional test

2. EDL east and west > APIS STM, COS, B3R2

3. Infrastructure rollout line by line from EDL

7

ETCS B3R2 STM DK/SE/DE

ETCS ATC/B3 DMI

New OR

+ marker boards

+ axel counters

New points +COS

New IXL +COS

RBC and DNS

TMS East /West

ATC > ETCS Train first migration:

ATC ZUB123

DMI ATC

Trackside:

Track separations

Legacy points

Legacy IXL

Light signals

Legacy signalling (17)

8

Conclusions

• Business continuity important

• CTS > TMS Voice integration problematic

• Cross over entities needed

• APIS takes time and ther is a lot of them (yellow marked)

• GSM-R must be available in migration-window

• Migration to All IP from B3R2

• Two step migration (ETCS and voice)

9

Train:

ETCS B3R2 STM SE/DE

EDOR GSM-R CS/PS

B3R2 > NextGeneration TEL

MigrationWindow 10years

10

ETCS B3R2.x STM SE/DE..

EDOR GSM-R+ LTE

USIM with GSM-R + LTE

B3R2.x

New SS037 supporting alternative MNC, MCC

New SS037 R2.X

+ LTE overlay coverage from public LTE network(s)

+ APN ETCS from LTE GGSN

DNS + MNC,MCC option

+ All IP voice integration

Trackside:

GSM-R ETCS B3R2

RBC

DNS

TMS East /West

B3R2 > NextGeneration TEL

11

Thank you for your attention

12