gsm-r network verification€¦ · gsm-r network verification framework conditions • assessment...

GSM-R Network Verification


Roman Herunter – Austrian Federal Railways (ÖBB)Christian Bose – German Railways (DB)Gerhard Fritze – team Communication Technology Management GmbH

ERTMS CCRCC 2015Lille, September 23, 2015

Experiences from obtaining an EC Certificate of Verification

for the Austrian and for the German GSM-R network


Total network: ~5000 km

GSM-R: ~3000 km

ETCS: ~300 km

For ETCS operation, the

Ministry of Transportation

requested an EC Certificate

of Verification of the

underlying GSM-R

network

GSM-R and ETCS at ÖBB

Sept. 23, 2015ERTMS CCRCC 2015 2

ETCS equipped sections

in operation

planned

not planned


FRAMEWORK CONDITIONS

• Assessment of GSM-R network, that has already been in operation for several years

• ETCS Level 2 lines already certified since putting into operation

SUPPORT

• Commissioning of external partner „team“ because of extensive experience in formerÖBB projects (e.g. ETCS Level 2 implementation)

NOTIFIED BODY

• First cost estimation led to the necessity of a nationwide tender to get a NoBo

• Common understanding about all relevant TSI requirements

• GSM-R assessment using Module SG (Unit Verification) incl. technical dossier

Process at ÖBB



Timeline at ÖBB


12/2013

04/2015

Commissioning of „team“, creating tender documents; Analysis and

classification of TSI requirements and legal framework

03/2014 Publishing tender documents

04/2014 Acceptance; Gathering all kinds of relevant documents and reports

05/2014 Offerer filed a lawsuit; ÖBB cancelled tender (diff. Module SG interpretation)

07/2014 Abandon of lawsuit; Execution & documention of additional tests

New cost estimation direct placing of an order08/2014

09/2014 Start coordination and alignment with NoBo („SCHIG mbH“)

EC Certificate of Verification + technical dossier

Analysing and updating verification documents,

Question + Answering with NoBo, compiling data for the

Register of Railway Infrastructure (RINF),

change management concept for future updates


In April 2015, the EC Certificate of

Verification was issued by the

Notified Body for the entire GSM-R

Network of ÖBB

EC Certificate of Verification



Total network: ~33000 km

GSM-R: ~29000 km

ETCS: will start in Dec. 2015

between Erfurt and Leipzig

To allow operation

of ETCS, the National

Safety Authority (EBA)

requested an EC Certificate

of Verification of the

underlying GSM-R

network

GSM-R and ETCS at DB



FRAMEWORK CONDITIONS

• Assessment of GSM-R network, that has already been in operation for several years

• GSM-R Certificate basis for ETCS Level 2 Certification

SUPPORT

• Commissioning of external partner „team“ because of extensive experience at ÖBB

NOTIFIED BODY

• Common understanding about all relevant TSI requirements

• Certification of MI and M Requirements

• GSM-R assessment using Module SG (Unit Verification) incl. technical dossier

Process at DB


same as ÖBB

GSM-R Network Verification 8ITS INVTNFC-Meeting

4321 1211109 8765

Analysis and preparation of additional tests

Considerations and Analysis of legal framework

Classification of TSI requirements

121110943218765

Certificate released

Final discussion of open issues

Compiling of relevant documents and reports

Timeline and Milestones at DB

2014 2015


In August 2015, the EC Certificate of

Verification was issued by the

Notified Body for the entire GSM-R

Network of DB

EC Certificate of Verification



• Focus on interoperability on the air interface

• Verify the interface to the „CCS Train Protection“

system separately (part of the RBC verification)

• Distinguish between

Functional requirements

(e.g. MORANE features)

Trackside requirements

(e.g. coverage)

Configuration requirements

(e.g. numbering plan)

• Reuse the results of the system

acceptance tests as much as possible to prove TSI compliance

• Define and perform additional tests for full TSI compliance

• Seek close cooperation between railway operator, Notified Body and

National Safety Authority to enable a smooth process

Approach to streamline the process

Defining the scope is crucial


Command-Control and Signalling

Track-side Subsystem

Radio Communication


• Analysis of the legal framework

• Classification of relevant requirements

• Evaluation of existing test reports and acceptance protocols

• Performance and documentation of additional tests

• Drafting of verification documents

• Compilation of data for the Register of Railway Infrastructure (RINF)

• Change management concept for future updates

Roadmap to the Certificate

Tasks to carry out during the process



Directive 2008/57/EC: “all modules are possible”

→ it should be clarified, which module to use

Decision 2012/88/EU (TSI): several unclear or unneeded requirements,

e.g. “4.6. Professional competences” (importance for interoperability ???)

→ it should be clearly stated, which requirements must be fulfilled

bearing in mind, how evidence of fulfillment could look like

EIRENE FRS and SRS: the assignment of requirements to subsystems (trackside or

train-borne) is sometimes ambiguous

→ there should be a clear mapping table requirement vs. subsystem

→ it should be considered, how evidence of fulfillment could look like

Emergency Calls: The requirements on the setup time for Railway Emergency Calls are

vague and leave room for interpretation

→ it should be clarified, what measurements must be fulfilled

Points for improvement - 1

There are several areas were requirements could be sharpend:



The draft ERA Test Catalogue is of limited relevance

→ some MI requirements are missing e.g. „FRS 2.2.3 Point-to-Point Voice Connection“

→ some test cases go beyond requirements e.g. “5.1.12 Supplementary Service CLIP –

MTM with CFU” - not mandated combination of supplementary services

→ a clear mapping of requirements to subsystems and interoperability components

would be more important than a test catalogue

Conclusion→ documents should be as concise and clear as possible

→ there should be as few options as possible

→ redundancies should cleared out

→ mapping between requirement and component should be provided

→ requirements should be provable!

Points for improvement - 2

There are several areas were requirements could be sharpend:



Who is next ?

go for GSM-R Network Verification, it does not hurt

Thank your for your attention !


gsm-r network verification€¦ · gsm-r network verification framework conditions • assessment...

Documents