ertms/etcs uic platform · pdf fileertms/etcs uic platform paris, 13 october 2006 ... no end...

46
ERTMS/ETCS UIC Platform Paris, 13 October 2006 RFI - Technical Direction

Upload: lamkhue

Post on 06-Mar-2018

238 views

Category:

Documents


7 download

TRANSCRIPT

Page 1: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

ERTMS/ETCS UIC Platform

Paris, 13 October 2006RFI - Technical Direction

Page 2: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Activities in progress (1a):

Functions adopted in the applications

(scheme based on all the subset 108 listed change requests, with

indication of the adopted ones with or without modifications)

The following list is referred on the CRs impacting track side

The list is considered open � additional change requests, i.e. the ones for the SRS 3.0.0., in case have been adopted (or is planned their adoption) in some application existing or future application (realized when 2.3.0 is in force), can be proposed by the interested railways when they will fill the list)

Page 3: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

The latest issue at 2.0.1. has not been released tothe Users Group

73

OUTEEIG ref 02Q079: Acknowledgement of STM transitions

OT70

NAEEIG ref 02Q090: Acceptance of "List of balises forSH areas" in SH mode

OT69

comment NID_STM in packet 72OT58

INImmediate level 2 transitionOT55

Telegram or Message CounterOT49

position report in case of passing an unlinked balisegroup

OT40

OUTMeaning of M_ERROR special valuesOT38

INpermitted maximum number of balise groups in the packet "Linking"

OT34

Clarification of termsOT31

Editorial clarificationsOT30

Pending communication sessionOT20

INNetwork address formatOT16

NID-C descriptionT15

Supervision of sequenceOT12

Message flow during termination of a communication session

OT10

INCrossing GSM-R network borderOT7

NAInterface KM centre and OBU6

Message namesOT5

NoteDeviation from agreed solution

or no solution availableClHeadlineO/T

CR

Page 4: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INImpossibility to shift location reference for messages15 & 34

OT207

M DRIVERACTIONS - ambiguous values182

Texts without reference179

End of Information packet by RadioOT172

EEIG ref 062: Indication of track conditionsOT170

EEIG ref 058: NID OPERATIONALOT166

INEEIG ref 056: Revocation of TSR in Level 1OT164

INEEIG ref 048: Types of radio messagesOT158

INEEIG ref 038: Eddy current brake switch offOT151

INEEIG ref 033: TSR sOT146

INEEIG ref 032: Establishment of radio sessionOT145

Position report in level transition142

Q EMERGENCYSTOP definitionOT137

Waiting for train data ack by RBC132

INEEIG ref 02Q1182-: Train Awakening procedureOT126

OUTEEIG ref 02Q073: Passing a signal in SR modeOT124

OUTEEIG ref 02Q064: TSROT123

Emergency Message regarding transmission errorOT96

INHigh priority channel (2)OT94

Specific engineering ruleT86

Page 5: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Repetition of data sent to RBC, but no acknowledgement received

318

OUTFailure of Packet 51 "ASP"OT317

INEngineering (Track Condition; Route Suitability)OT315

OUTPacket 39 Track Condition Change of traction PowerOT311

Contradiction of dimensioning dataT302

OUTEEIG 088 Version compatibility checkOT299

L MESSAGE size291

SRS version reference update289

Version updating error288

OUTTrain running number acquisition258

Last eight reported BG identities stored on board with regard to deletion of stored position data in SoMprocedure.

OT257

Minimum distance between balise groups250

INMinimum distance between the 1st balise of a balisegroup and the EoA

OT248

EEIG 074 ERTMS system version managementOT242

EEIG 073 RBC/RBC interface specificationT241

INWhich value for Q LINKACC shall be used On-boardOT226

INInfill and level transitionT215

INInfill Location ReferenceOT214

INRepositioningOT213

INList of common optional packetsOT209

Page 6: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

OUTEEIG119 Level crossing modificationOT413

OUTEEIG108 Gradients and traffic capacityOT409

RBC Identification406

EEIG116 Management of UIC variablesOT400

Message 153OT399

INSpecial value of L_TRAIN = "Unknown"OT398

OUTConditions for Start/End of Text IndicationOT397

Length of M_LOADINGGAUGE395

Definition of DriverAction "Not Used" in SUBSET027394

Message "JRU State"393

INNon Continuous Profile DataOT387

Special Position Report386

OUTKey Management documentation scope is unclear.385

Transmission media for packet 12 is not only baliseOT383

INOptional packet 49 possible in message 3 but not in messages 9, 33, 37

OT382

Storage of and text interpretation forQ_SLEEPSESSION

OT336

M_VOLTAGE variable331

Length of MA information during RBC handover322

Speed supervision behind LOAOT320

LRBG orientation for special position report319

Page 7: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INDefault information also for LoopT489

OUTImpossibility to discriminate MA request reasonOT487

INProposed Engineering rule for discussionT483

Balise detect function482

OUTEEIG ref 134: Supervision of the Radio LinkOT481

EEIG ref 127: Insufficient test spec for togglingOT480

INManagement of renewed RV distance476

INEngineering rules extracted from Safety paperT475

INDefinition of variable Q_FRONTOT460

OUTNational values sent by radio during SoM459

INMeaning and use of Q_DIR of packet 135OT458

Linking to unknown orientation is not possibleOT452

Delete Cold Movement detector from TI FIS448

OUTImprovements of Reverse Movement444

INSupervision of former EoA in SR mode linked toOverride procedure

441

OUTUse of N_ITEROT437

Remembering to update SRS system versionOT428

Names NC_DIFF and V_DIFFOT423

Comment on variables Q_DIRLRBG and Q_DLRBG422

Application rules for packetsOT414

Page 8: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

OUTEEIG156: Triple DES ciphering537

OUTEEIG155: ETCS ID identifier byte536

NAEEIG152: Door control supervisionOT535

INEEIG130: Conditional level transition orderOT534

Reporting of fatal error by Sleeping and Non leadingengines.

OT524

Misleading sentences for RBC/RBC announcement.T522

INEEIG ref 146: Release speedOT517

INEEIG ref 144: Repositioning informationOT516

INDeactivation of T_NVCONTACT supervision in case of degraded RBC/RBC Handover

OT508

INUnwanted mode transition during train trip inhibitionOT507

Update of ETCS Safety Analyses needed506

Network address format at fixed interface / interfaceto GSM-R

OT503

NALoss of performance regarding release speed502

INEEIG ref 131: Conditional emergency stopOT499

Repetition of information between an in-fill balisegroup and the related main balise group

T497

Restriction of capacity within the Route RelatedInformation Request

T495

Communication of SR balise list on the RBC/RBCinterface

T494

Removal of Emergency Stop data from Route Related Information

T493

Missing information in the pre-announcementmessage

T492

Acknowledgement of the Route Related InformationT491

Page 9: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Shortening of track description – SSP and gradientprofile must not have “open end”

605

INEEIG ref 186: Use of MA request at entry into level 2OT600

NAEEIG ref 170: Braking curve calculationO595

EEIG ref 174: Speed definitionsOT594

OUTEEIG ref 171: Awakening on loopsOT593

NAEEIG ref 141: Track condition inhibit tiltOT587

EEIG ref 137: DMI planning areaOT586

Follow up from CR 257580

OUTRelease speed578

OUTShort Balise Telegram and National Value Packet577

OUTNew Message 45 'Assignment of coordinate system'568

OUTReporting / recording of balise errorsOT565

Missing Parameter in the Route Related Informationmessage

T564

Release Speed Warning Limit562

No End of mission reporting when no communicationestablished

560

Inconsistencies in procedure “Shunting initiated bydriver”

559

CEDEX JRU problem list553

Unclear definition of big metal masses544

OUTEEIG118: OS mode profileOT542

Page 10: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

NADanger for Shunting in Level 0647

Values of V_TRAIN and TRAIN_POSITION for eventlogging in the JRU

643

EEIG ref 201: Overpass EOA speed642

EEIG ref 200: Local time641

EEIG ref 199: DMI indication of default values640

Backward movement and already in FS/OS mode639

OUTSelection of Static Speed Profile according to TrainCategories

638

OUTLimited Supervision637

System Start-up / Execution of Self-Tests636

Extension of MA following TAF not clear635

OUTQ_EMERGENCYSTOP variable not in line withCLR91 and CLR532

634

Inconsistencies in stored/not stored info betweenA3.4 and 4.10

632

Backward movement after entry in FS/OS mode625

Use of variable Q_TRACKDEL unclearly defined622

INMessage counter (M_MCOUNT) rules and associated reaction unclear

OT620

Message Acknowledgement619

Inconsistencies between Subset 035 and Subset 026

618

Informing the RBC when track description has been614

Emergency stop revocation after level transition613

Shunting request information to be displayed in UN mode

607

Page 11: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Inconsistency in override procedure during SOM 659

OUTUpdate of Track Conditions (issue from CEDEX)658

OUTUnsuitability of RBC-RBC handover procedure in case of radio network change

657

OUTFollow-up of CR 126656

INLevel Transitions involving STM Levels655

Unsuited wording of variable description654

Contradiction Level transition immediately in PT653

Impossibility to perform mode transition PT => FS/OS in Level 1

652

Availability of "Shunting request" input for driver651

Train movement in L1 SB without Train Data650

Inconsistency in position report specification and Active Functions Table

649

Roll away protection when coasting648

Page 12: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Activities in progress (1b):

Functions adopted in the applications

(scheme based on all the subset 108 listed change requests, with

indication of the adopted ones with or without modifications)

The following list is referred on the CRs impacting on board

The list is considered open � additional change requests, i.e. the ones for the SRS 3.0.0., in case have been adopted (or is planned their adoption) in some application existing or future application (realized when 2.3.0 is in force), can be proposed by the interested railways when they will fill the list)

Page 13: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INOverride request from Driver in PTO46

specific output in case of braking due to unexpectedbalise messages

O44

INMA after reverse movementO43

position report in every train-to-track telegramO41

position report in case of passing an unlinked balisegroup

OT40

restricted use of duplicated balisesO39

OUTMeaning of M_ERROR special valuesOT38

failure on implementation side withrestriction for trackside

INOnboard deletion of data in case of overwriting anLTA

O36

failure on implementation sideINDriver Information when onboard commands the SB or EB due to a balise data inconsistency

O35

INpermitted maximum number of balise groups in the packet "Linking"

OT34

Clarification of termsOT31

Editorial clarificationsOT30

Pending communication sessionOT20

INNetwork address formatOT16

Supervision of sequenceOT12

Message flow during termination of a communication session

OT10

INCrossing GSM-R network borderOT7

NAInterface KM centre and OBU6

Message namesOT5

NoteDeviation from agreed solution

or no solution availableImplemente

dClHeadlineO/T

CR

Page 14: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

EEIG ref 02Q070: Odometry inaccuracy at exit of speed restriction

O78

EEIG ref 02Q068: Splitting of an ERTMS trainO76

EEIG ref 02Q062: STM speed supervisionO75

Subset Number the same as for the JRU FFFISO74

The latest issue at 2.0.1. has not been released tothe Users Group

73

EEIG ref 02Q074: Insertion of packet 0 in allmessages from train to RBC

O71

OUTEEIG ref 02Q079: Acknowledgement of STM transitions

OT70

NAEEIG ref 02Q090: Acceptance of "List of balises forSH areas" in SH mode

OT69

EEIG ref 02Q089: Reporting mode changes to the RBC

O68

EEIG ref 02Q083: Non relevant information for driverO66

EEIG ref 02Q082: default shunting speedO65

failure on implementation sideINOdo inaccuracy with track conditionsO63

comment NID_STM in packet 72OT58

Mode related speed restriction in SHO57

Reserved values in M DRIVERACTIONSO56

INImmediate level 2 transitionOT55

Position Report in RV modeO51

INSession Management in SH rejectedO50

Telegram or Message CounterOT49

provides a way out which wouldotherwise be a deadlock

missing transition from TR, PT to SLO47

Page 15: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

OUTEEIG ref 02Q064: TSROT123

INTrack Condition Change of traction powerO120

Non leading is endedO119

INTransition failureO115

INRepositioning and cross talkO110

Output informationO107

Availability of Acknowledgement buttonO105

There is no acceleration data specified as specifictrain data.

O103

INCommunication session establishmentO102

Permitted speed in RVO101

MMI versus mode tableO100

MMI versus internal informationO99

INHandling of Default Balise TelegramO98

Emergency Message regarding transmission errorOT96

INHigh priority channel insertion of MAO95

INHigh priority channel (2)OT94

INSpace Critical EMO91

High Priority channel (3)O90

INAdditional linking reactionO88

Transition to non fitted SE/SNO83

Page 16: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INEEIG ref 038: Eddy current brake switch offOT151

NAEEIG ref 036: TIMS data missingO149

EEIG ref 035: Leaving Isolation modeO148

INEEIG ref 033: TSR sOT146

INEEIG ref 032: Establishment of radio sessionOT145

INBalise Group Message Consistency check in SRO144

INStaff Responsible distance supervisionO143

Position report in level transition142

Geographical position in SHO141

Reversing distance sent by the RBCO140

Brakes release after max reversing distanceoverpassed

O138

Q EMERGENCYSTOP definitionOT137

INTransition SR>OS for further loc.O136

L_MAMODE for a shunting areaO134

Requirement doesn't belong to the chapterO133

Waiting for train data ack by RBC132

Confusing definition of Tamt.O130

Short number programmed in balise identification.O128

INEEIG ref 02Q1182-: Train Awakening procedureOT126

OUTEEIG ref 02Q073: Passing a signal in SR modeOT124

Page 17: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INUnconditional Emergency Stop in SRO197

EoMission during RBC HandoverO187

Message 42 further deletionsO186

Data from single balise groupsO183

M DRIVERACTIONS - ambiguous values182

Braking without indication of reason at standstillsupervision

O180

Texts without reference179

Loss of End of Profile elementsO177

INReq. for Nat. Values unclearO174

End of Information packet by RadioOT172

EEIG ref 062: Indication of track conditionsOT170

NAEEIG ref 061: Non stopping informationO169

EEIG ref 060: MA requestO168

EEIG ref 058: NID OPERATIONALOT166

INEEIG ref 056: Revocation of TSR in Level 1OT164

EEIG ref 052: KER interfaceO160

INEEIG ref 048: Types of radio messagesOT158

EEIG ref 047: Valid direction for Reverse MovementProtection in SR

O157

INOverride EOA inconsistencyO155

EEIG ref 044: Text message inconsistencyO154

Page 18: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

EEIG 043: Unknown text messageO232

INTransitions from SN/SE/UN to SRO231

INWhich value for Q LINKACC shall be used On-boardOT226

Table of Supported Levels must be restored at Start of Mission

O223

failure on implementation sideINShunting ordered by tracksideO219

failure on implementation sideINState chart for OS procedure is partly incorrect & mode transition conditions 34 & 40 unclear

O218

Transition TR/SNO217

ambiguity of distance information in profile dataO216

INInfill Location ReferenceOT214

INRepositioningOT213

Requirement for Data Entry Request and Train Data Input Information to be Active/Available Post Trip Technical Mode.

O211

failure on implementation sideINTransitions form Post Trip mode to Non-Leadingmode

O210

INList of common optional packetsOT209

INImpossibility to shift location reference for messages15 & 34

OT207

Note to be removedO205

Report of train position when change of trainorientation

O204

Default gradient of TSR forgottenO203

Memorised balise groups for special position reportnot mentioned in table 4.10.1.3

O202

Supervision of radio link : unclear requirementO201

Revocation of Emergency Stop in SRO198

Page 19: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Indication of supervision limits in SR modeO264

Length of DRIVER IDO262

Transition from PT to SH when ordered by tracksideO259

OUTTrain running number acquisition258

Last eight reported BG identities stored on board with regard to deletion of stored position data in SoMprocedure.

OT257

INAck window different for OS and SHO256

Procedure Train Trip : coexistence of a conditionalemergency stop and a trip due to a different reason

O254

INValidity direction of transmitted information : requirement 3.6.3.1.3 too restrictive and inconsistentwith figure 11

O253

INPriority problem between mode transitions [39] & [44]

O252

Minimum distance between balise groups250

INMinimum distance between the 1st balise of a balisegroup and the EoA

OT248

List of expected balises in SR modeO247

EEIG 074 ERTMS system version managementOT242

EEIG 072 JRU changesO240

EEIG 070 Train data on TIUO239

EEIG 069 Shifted reference locationO238

EEIG 067 Service Brake T NVCONTACTO237

EEIG 065 Train data after loss of radio communication

O235

INEEIG 064 Override EOA and stop in SRO234

OUTEEIG 050: Managing track conditionsO233

Page 20: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INcorrection of mode transition tableO314

Level Transition at estimated - or maximum safefront end

O312

OUTPacket 39 Track Condition Change of traction PowerOT311

RBC transition order analog to level transition orderO309

INInhibition of transition to the trip mode for OverrideEoA

O308

ETCS functions access by the STM in SL ModeO301

OUTEEIG 088 Version compatibility checkOT299

EEIG 087 Level selection by driverO298

EEIG 086 Override requestO297

EEIG 085 Linking reaction info to RBC.O296

EEIG 083 Indication to braking curve areaO294

End of MissionO293

L MESSAGE size291

SRS version reference update289

Version updating error288

Smooth transition and continuous supervision at the level Transition

O285

ETCS accepted information from STM X (SE)O284

Transition SB-->SN after ACK [58]O269

End of mission: terminate communication session, ifcomm. session exists

O268

Information to driver about reason of train tripO265

Page 21: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

OUTKey Management documentation scope is unclear.385

Transmission media for packet 12 is not only baliseOT383

INOptional packet 49 possible in message 3 but not in messages 9, 33, 37

OT382

Display of maximum shunting speedO381

INEOM possible from RV modeO379

NAEEIG111 Position accuracyO378

INEEIG104 Rejection of info after not ignored Em stopO375

EEIG103 Reason for TR on DMIO374

EEIG097 Mixed level transition announcementO373

NAEEIG095 FIS EVC - EIRENE Voice RadioO372

Some Errors in Active Functions TableO338

Storage of and text interpretation forQ_SLEEPSESSION

OT336

M_VOLTAGE variable331

Length of MA information during RBC handover322

failure on implementation sideSpeed supervision behind LOAOT320

LRBG orientation for special position report319

Repetition of data sent to RBC, but no acknowledgement received

318

OUTFailure of Packet 51 "ASP"OT317

failure on implementation sideLevel Tr. for which on-board not fittedO316

INEngineering (Track Condition; Route Suitability)OT315

Page 22: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

EEIG113 STM transition in trip situationO411

NAEEIG112 Shunting in STM areasO410

OUTEEIG108 Gradients and traffic capacityOT409

Brake application and revocation by the samesystem

O408

RBC Identification406

Ack of train data also in TR and PTO403

When is linking used onboardO402

EEIG116 Management of UIC variablesOT400

Message 153OT399

INSpecial value of L_TRAIN = "Unknown"OT398

OUTConditions for Start/End of Text IndicationOT397

OBU can receive MA and other information after End of Mission

O396

Length of M_LOADINGGAUGE395

Definition of DriverAction "Not Used" in SUBSET027394

Message "JRU State"393

Ambiguity: SSP and gradient must cover "the full length of the MA"

O392

failure on implementation sideBalise consistency check in RV modeO390

INOverride in SB mode regarding shuntingO389

INNon Continuous Profile DataOT387

Special Position Report386

Page 23: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

OUTImprovements of Reverse Movement444

INSession management and ack of term of commsessto be immediately accepted if received fromaccepting RBC.

O442

INSupervision of former EoA in SR mode linked toOverride procedure

441

Mistake in Active Function Table for SHO438

OUTUse of N_ITEROT437

INReversing area boundaries not clearO436

Linking reaction, logging thereofO433

Remembering to update SRS system versionOT428

SRS reference missingO426

Names NC_DIFF and V_DIFFOT423

Comment on variables Q_DIRLRBG and Q_DLRBG422

INTreatment of inconsistency between duplicatedbalise telegrams.

O421

partly and failure on implementationside

INInconsistencies for stored/accepted infoO419

Target speed & distance output information to driverO418

INRejection of track description information beforerevocation of conditional emergency stop.

O417

"No track condition information will be received" message to the driver in NL mode.

O416

Transition between STM levelsO415

Application rules for packetsOT414

OUTEEIG119 Level crossing modificationOT413

EEIG114 Brake command in NP modeO412

Page 24: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INEoA at the end of the On Sight areaO470

INCompleteness of dataO469

Transition from TR to UNO466

INLocation reference for in-fill informationO464

MA shortening due to change of train dataO463

Inconsistency: Sent train data and acceptAcknowledgement in NL

O461

INDefinition of variable Q_FRONTOT460

OUTNational values sent by radio during SoM459

INMeaning and use of Q_DIR of packet 135OT458

INHandling V_LOA, MA section time outO457

Position report sending when passing level transitionlocation with train rear end

O455

partlyINGeographical positionO454

National/Default valuesO453

Linking to unknown orientation is not possibleOT452

Further changes with reference to CR 66 and CR 91O451

Mode transition condition not correctly wordedO450

INShunting init. by Driver, missing modeO449

Delete Cold Movement detector from TI FIS448

Resuming initial state for non continuous profile dataO446

INTSR deleted when entering SR modeO445

Page 25: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Train Orientation not well definedO505

INRelease Speed after Section TimeoutO504

Network address format at fixed interface / interfaceto GSM-R

OT503

NALoss of performance regarding release speed502

INAccepted information depending on modeO501

OUTEEIG ref 133: Tilting malfunctioningO500

INEEIG ref 131: Conditional emergency stopOT499

Exc. permitted distance in PT modeO490

Geographical position handling in RV modeO488

OUTImpossibility to discriminate MA request reasonOT487

Review of SRS by STM WGO485

Balise detect function482

OUTEEIG ref 134: Supervision of the Radio LinkOT481

EEIG ref 127: Insufficient test spec for togglingOT480

EEIG ref 125: Establishment of Safe Connection -Retries

O478

INEEIG ref 123: Big metal massO477

INManagement of renewed RV distance476

Additional data input by driverO473

INOrder to contact a different RBC from the one currently in session

O472

No acknowledgement of termination of a communication session received

O471

Page 26: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Start of Mission procedure re-engaged when sessionis not terminated.

O531

Reporting of PT mode when no communicationsession established.

O530

Reactivation of Radio link supervision after a radio hole

O529

INContradictionO528

INTAF request is a stored informationO525

Reporting of fatal error by Sleeping and Non leadingengines.

OT524

INAbortion of SoM while in SB mode.O523

Train location function for non leading and sleepingengines

O521

OUTEEIG148: Use of default values after NP modeO519

INEEIG ref 146: Release speedOT517

INEEIG ref 144: Repositioning informationOT516

OUTEEIG ref 138: Cold movement detectionO514

NAEEIG080 Non Leading modeO513

INAccepted information received by radio when the train orientation is unknown

O512

Train speed indication in SB modeO511

INAcceptance of Mode profile when MA is rejected.O510

Confusing reference in table 4.5.2O509

INDeactivation of T_NVCONTACT supervision in case of degraded RBC/RBC Handover

OT508

INUnwanted mode transition during train trip inhibitionOT507

Update of ETCS Safety Analyses needed506

Page 27: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INCriteria for sending position reportO556

INExit of On Sight area to a Shunting areaO555

INEEIG ref 167: MA/track condition in Trip modeO554

CEDEX JRU problem list553

RBC handover, degraded situationsO552

Transition from TR to UN in level 0 when the onboard equipment was previously in SH mode.

O548

INNo reactivation of train trip when passing a baliseout of the SH list when in SH mode.

O547

No train data in shunting and non leadingO546

Unclear definition of big metal masses544

Driver information missingO543

OUTEEIG118: OS mode profileOT542

EEIG151: SR mode acknowledgementO540

NAEEIG096: Set speed indication for driverO539

INEEIG152: Geographical position in SE modeO538

OUTEEIG156: Triple DES ciphering537

OUTEEIG155: ETCS ID identifier byte536

NAEEIG152: Door control supervisionOT535

INEEIG130: Conditional level transition orderOT534

NAEEIG124: Availability of speedometer display in IS mode

O533

INAcknowledgement of Emergency Stop message.O532

Page 28: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

NAEEIG154: JRU failureO589

NAEEIG ref 141: Track condition inhibit tiltOT587

EEIG ref 137: DMI planning areaOT586

EEIG ref 132: STM max speedO584

EEIG ref 068: Indications on DMI in SR/OS modeO583

Permitted speed in UN modeO582

INM_VERSION spare valuesO581

Follow up from CR 257580

Target speed at target distanceO579

OUTRelease speed578

OUTShort Balise Telegram and National Value Packet577

OUTNew Message 45 'Assignment of coordinate system'568

OUTReporting / recording of balise errorsOT565

MA request if section timer expiresO563

Release Speed Warning Limit562

Availability of "Start" button in SE/SN modeO561

No End of mission reporting when no communicationestablished

560

Inconsistencies in procedure “Shunting initiated bydriver”

559

Wording inconsistencies for linkingO558

Reset of MA request parameters and position reportparameters

O557

Page 29: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

INMessage counter (M_MCOUNT) rules and associated reaction unclear

OT620

Message Acknowledgement619

Inconsistencies between Subset 035 and Subset 026

618

INTwo communication sessions between OBU and the same RBC.

O616

INContradiction between 4.4.2.2. and 4.6.2O615

Informing the RBC when track description has been614

Emergency stop revocation after level transition613

Shunting request information to be displayed in UN mode

607

Shortening of track description – SSP and gradientprofile must not have “open end”

605

EEIG ref 181: Override procedureO604

EEIG ref 192: OS acknowledgementO601

INEEIG ref 186: Use of MA request at entry into level 2OT600

EEIG ref 191: Reconnection after unexpected radio hole

O599

EEIG ref 184: Communication session in SL modeO597

NAEEIG ref 170: Braking curve calculationO595

EEIG ref 174: Speed definitionsOT594

OUTEEIG ref 171: Awakening on loopsOT593

OUTEEIG ref 172: Managing route suitabilityO592

EEIG ref 169: Change of train lengthO591

Page 30: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Train movement in L1 SB without Train Data650

Inconsistency in position report specification and Active Functions Table

649

Roll away protection when coasting648

NADanger for Shunting in Level 0647

INEEIG ref 203: Beginning of SR distanceO645

Values of V_TRAIN and TRAIN_POSITION for eventlogging in the JRU

643

EEIG ref 201: Overpass EOA speed642

EEIG ref 200: Local time641

EEIG ref 199: DMI indication of default values640

Backward movement and already in FS/OS mode639

OUTSelection of Static Speed Profile according to TrainCategories

638

OUTLimited Supervision637

System Start-up / Execution of Self-Tests636

Extension of MA following TAF not clear635

OUTQ_EMERGENCYSTOP variable not in line withCLR91 and CLR532

634

INRepetition of packet 254 in a balise group messageO633

Inconsistencies in stored/not stored info betweenA3.4 and 4.10

632

Backward movement after entry in FS/OS mode625

Use of variable Q_TRACKDEL unclearly defined622

INClarify use of M_DUP and P44O621

Page 31: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

forbidden in baseline 2.3.0OUT

included in baseline 2.3.0IN

not applicableNA

LEGEND

……

……

Inconsistency in override procedure during SOM 659

OUTUpdate of Track Conditions (issue from CEDEX)658

OUTUnsuitability of RBC-RBC handover procedure in case of radio network change

657

OUTFollow-up of CR 126656

INLevel Transitions involving STM Levels655

Unsuited wording of variable description654

Contradiction Level transition immediately in PT653

Impossibility to perform mode transition PT => FS/OS in Level 1

652

Availability of "Shunting request" input for driver651

Page 32: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Activities in progress (1c):

Tested Functions and related

(scheme of the tests with indication of the tests done and the criticalities found in these tests, indicating also the adopted solutions to solve the found criticalities)

The list is considered open � additional tests can be proposed by the interested railways when they will fill the list)

Page 33: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

testedRemarksimpacts by operation/specification[difference

or selection]

testedFunctionality

......

…..

ytwo mobils

yymaintaining Radio Communication Session with RBC

Maintaining Radio Communication Session

nnTermination of Radio Communication Session with RIU

ycould only be tested in laboratory

yTermination of Radio Communication Session with RBC

Termination of Radio Communication Session

none mobil

ntwo mobils

nnInitiated by RBC

nCR is proposed toUNISIG and will beinside version 2.3.0

if the radio connaction tothe new RBC is notestablished (failure toGSM-R or elsewhere) trainis not superviced due toT_NVCONTACT

Management RBC-RBC transion with one mobile with a separat timer

ynational solutionSolution of Italysolved by a addional on-board timer

Management RBC-RBC transion with one mobile without supervisen by ETCS as specification

yyone mobil

yytwo mobils

yyEstablish Communication Session to RBC

nnEstablish Communication session with RIU

yyInitiated by Onboard

Establishing Radio Communication Session

Radio Communication

Page 34: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

testedRemarksimpacts by operation/specification[difference

or selection]

tested

Functionality

nnTransitions to Reversing Mode

in atto per omologazio

ne SSB

national system withbehavior of STM

yTransitions to STM National Mode

nnTransitions to STM European Mode

yspecial button at the OBUyTransitions to Isolation Mode

yyTransitions to System Failure Mode

yyTransitions to Post Trip Mode

yyTransitions to Trip Mode

yused if NE is not availablediff.yTransitions to Unfitted Mode

nnTransitions to Non Leading Mode

nnTransitions to Sleeping Mode

nwill be activated by a special signal (Zs7/11)

yTransitions to On Sight Mode

ywill be activated by a special signal (Zs1) or action by driver

yTransitions to Staff Responsible Mode

ywill be activated by a master signal (Hp 0 or 1or 2)

yTransitions to Full Supervision Mode

nnTransitions to Shunting Mode

yyTransitions to Stand By Mode

yyTransitions to No Power Mode

……

The listed test pattern concerns about 200 scenariosList shall be performed at each supplier subdivided toOBU and RBC or LEU; result will be indicated to a matrix

Page 35: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Activities in progress (2):

Interfaces (Trackside and on board) list proposal

(list based on the Unisig architecture with indication for eachone of the interest of different railways to agreed / define a standard)

The list is considered open � additional interfaces can be proposed by the railways that will fill the scheme

Page 36: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

( F I S )

M M I T I U

F I S F F F I S

F F F I S F F F I S

F I S F I S F F F I S

( F F F I S )

F I S

F F F I S

( F F F I S )

E T C S

O n b o a r d

E T C S T r a c k s i d e

F I S

F I S

F I S

F I S

E U R O R A D I O

E U R O R A D I O B T M L T M

K e r n e l O d o m e t r y

J u r . R e c o r d i n g

G S M - M o b i l e

G S M f i x e d n e t w o r k

R B C 1

R B C 2

K e y M a n a g e m e n t

C e n t r e

E U R O B A L I S E E U R O L O O P

I n t e r l o c k i n g a n d L E U

S T M

C o n t r o l C e n t r e

N a t io n a l S y s t e m

D r i v e r T r a i n J R U

D o w n l o a d i n g t o o l

R a d i o in f i l l u n i t

E U R O - R A D I O

ETCS lay ETCS lay -- outout

Page 37: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

PrioRFIPrioDB AG CER Cr

intendedTSI

requirementCommentsInterfaces

Yeson-boardExisting spec. to be improvedEVC - TIU (Diagnostic;

Automatic speed control; Pantho management)

on-board97E881-6(G?)EVC - Pneumatic brake

YesYesYeson-board / track-side

KMC

YesYesYeson-boardGaderos (FP5)GPS information

YesYesYeson-boardEVC - service

YesYesYeson-boardEVC - BTM/LTM or Antennae

YesYesYeson-boardIndex 55JRU - Downloading

YesYesYesFRSon-boardEirene, 99E5362EVC - GSM-R

YesYesYeson-boardIndex 55EVC - JRU

YesYesYesCCS Annex A (FIS)

on-boardEEIG 97E267 - to be checkedEVC/STM - Odometry

Yesshallshall

YesHS RST (4.2.7.15, 4.3.5.40)

on-board05E446 (EEIG); TS 50459; UIC

612-01,02,06; including DEDMI -Driver

YesshallYesYesHS RST (4.2.7.15, 4.3.5.40)

on-board

FFFIS based on WG12, MODTRAIN/MODCONTROL FIS

on interface ETCS - DDU (Driver-Display-Unit = DCPU)

EVC-DMIh

On Board interfaces

Page 38: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

PrioRFIPrioDB AG CER Crintended

TSI requirement

CommentsInterfaces

Yestrack-sideRIU, Encoder, EurobaliseTrackside-tracksideobjects

track-sideETCS Regional,

Eurointerlocking (for LX, Switches (signals))

RBC/IL - Track-sideobjects

YesYestrack-sideto be investigated by BVRBC-RBC national

track-sideRBC -IL

Track side interfaces

Links with SBB, OBB and Banverket are in progress, and will start the links with other railways (France, Spanish, Holland, …) As a first step all the platform attending railways could add their own column on these tables filling their data and eventually adding other Interfaces (track side and on board), that they consider to be standardized.

Page 39: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Activities in progress (3):

Definition of a costs scheme for the (trackside and on board) costs allocation

(The already known SubSystems Brekdown Structure of the Roma Naples application, has been improved. A verification of its usability and also the data confidence is planned using the same approach for the Torino Novara application. In parallel some French colleagues started the assessment for the usability of this or similar approach in applications using the level 1 solution, over posed or not on existing systems)

The scheme (s) for the different situations will be considered a proposal to be improved / modified to be finalized after the platform railways agreement on the usability of it for the allocation of the known costs of existing application.A significant progress will be the use of the same scheme to drive the definition of the costs for the future applications, at least for a part of the whole costs, clearly defined in the scheme, that can be considered indipendent from the application.

Page 40: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

CCS System Cost AnalysisCase Study: Roma-Napoli High Speed Line

• The information are normally strictly confidential

• The proposed “Cost Analysis” approach concerns a “Turn-Key” system and takes into account all the technologies related with the CCS system (such as: SCC, TLC, Interlocking, etc.)

• The Cost Analysis data and elements have been derived from the contract for the design and construction of the complete Roma-Napoli High Speed line, managed by an unique General Contractor totally responsible of the whole project

Page 41: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

CCS Sub-System Cost AnalysisCase Study: Roma-Napoli High Speed Line

• The structure of the system under consideration is based on the “Work Breakdown Structure (WBS)” defined in the contract

• The data concerning the costs are referred to the date of contract drawing up. The up today cost adjustment can be obtained multiplying each cost by the adjustment factor (in our case the factor value is K= 1,2223)

Page 42: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Vital Routing Equipments, Indoor FieldLocations, (NVP)

ISSEGNALAMENTO

Field (Switching stations and Full Line)

MV/LV POWER STATION

Power Supplying, Central Office UPS & Diesel Generator

Air-conditioning, Central Office

Antintrusion, Central Office

Fire Fighting, Central Office

SISTEMA TELEFONICO

ST

Long Distance TLC (LD), central office

LD

GSM-R (Wayside - Train) TLC, central office

TTERTMS Telecommunications

Comandi protetti

Telecomunications Control System

Energy Control System

Alarm Monitoring, Diagnostic & Maintenance

Traffic control,

GDCommand and Control Centre (SCC)

VMMI SIL4

Apparecchiature e finiture

Funzioni Aggiuntive RBC

ISRadio Block Centre (RBC)

Local Central Office (PCS)

Groups (3)Equipments (2)Sub-Systems (1)

First 3 First 3 levelslevels

(complete data available till 5° level.some 4° level haveto be consideredfor the costsallocation)

Page 43: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Activities in progress (4):

Braking status of the art and additional elements derived from the existing applications adopted solutions.

Elements to consider in order to guaratee a real interoperable behaviour (Trackside and on board conditions to fulfill), referenced both to the documents EEIG, UIC, … and to the choice done in existing applications.

The most important result should be to separate the constraints for the trains and the ones for the track side subsystem. The track conditions have to be clearly stated in the applications and the trains can run there only if they comply with this conditions (at least have to comply with the defined train constraints for the interoperability,

Page 44: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Activities in progress (5):

STM – current situation, foreseen needs, possible strategies

Elements to consider concern where and when and in which form should be available the STMs.

The most useful STM is the lower cost modular one, whit a standardized interface to the ETCS.The activities to collect the experiences related to the existing applications, mostly based on an integrated solution, started. The goal is to demonstrate the advantages and the problems derived from these solutions in order to establish the best future approach for this question.

Page 45: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Summary:

For some of the previous activities (Adopted functions, interfaces, Costs) is ready a first draft scheme, perhaps to upgrade with the contribution of the platform raiways. The agreed schemes will be the form to which the platform railways will address the data available.

Other activities (braking, STM) started at national level , to collect the reference documents and the use of them on the Rome – Naples).

Before the next platform, the schemes should be improved, distributed and filled by the railways with their available data.

A dedicated workshop concerning the finalization of this first sA dedicated workshop concerning the finalization of this first step and the tep and the definition of the following steps will be organized in a proper definition of the following steps will be organized in a proper time, inviting time, inviting the interested bodies (at least the ones in red in the followingthe interested bodies (at least the ones in red in the following slide) in order slide) in order to allow, in the next platform, to have some first basic resultsto allow, in the next platform, to have some first basic results..

Page 46: ERTMS/ETCS UIC Platform · PDF fileERTMS/ETCS UIC Platform Paris, 13 October 2006 ... No End of mission reporting when no communication ... logging in the JRU 64 3

Interoperability interested bodies and linkssemplified scheme

Art 21Art 21

UICUIC

ERTMS Platform UICERTMS Platform UIC

ERTMS Platform RFI Mirror Group

ERAERA

CERCER

EIMEIM

Safety Platform UIC

Corr. C Corr. D Corr. E Corr. FCorr. B

Steering Steering MoUMoU (EC (EC MigrationMigration CoordinatorCoordinator))

UN

ISIG

UN

ISIG

EEIGEEIG

Executive Board Management Commitee

Project Managers

Executive Board Management Commitee

Project Managers

Corr. A

Europea JournalEuropea Journal

MinistersMinisters I MI M