ertms/etcs – class 1 - european union agency for ... · web viewsince the modifications in the cr...

EUROPEAN RAILWAY AGENCY

ERTMS/ETCS

Release Notes to Baseline 3 annex A documents

REF : ERA_ERTMS_040047

ISSUE : 1.1

DATE : 27/03/2012

1.1 Release Notes to Baseline 3 annex A documents /21


1. MODIFICATION HISTORYIssue Number

DateSection Number Modification / Description Author

0.1

08/03/2012

All New document AH

1.0

09/03/2012

Minor correction after internal review

AH

1.1

27/03/2012

5.1.1.1 Minor correction in the embedded Excel sheet (Renumber the EIRENE FRS and SRS cover CR)

AH



2. TABLE OF CONTENTS1. MODIFICATION HISTORY.................................................................................................................2

2. TABLE OF CONTENTS....................................................................................................................3

3. INTRODUCTION.........................................................................................................................4

4. SUBSET-026 V3.3.0....................................................................................................................6

4.1 Introduction........................................................................................................................6

4.2 CR’s implemented in version 3.0.0....................................................................................7

4.2.1 Preamble....................................................................................................................7

4.2.2 Functional CR’s retained for baseline 3......................................................................7

4.2.3 Error CR’s classified as “IN” in SUBSET-108 v1.2.0..................................................8

4.2.4 Other error CR’s listed in SUBSET-108 v1.2.0.........................................................10

4.2.5 Error CR’s not listed in SUBSET-108 v1.2.0............................................................16

4.3 CR’s added in version 3.1.0.............................................................................................17



4.6 CR’s withdrawn from version 3.2.0..................................................................................21

5. Other documents.......................................................................................................................22



3. INTRODUCTION3.1.1.1 According to the terms of the ERTMS Memorandum of Understanding signed on the

4th July 2008, this ERA recommendation 2012 materializes the final step of the new ETCS baseline 3, in the view to obtain a legalised baseline 3 in 2012.

3.1.1.2 The present release notes trace and justify the variations of the annex A documents, which are proposed in the ERA recommendation, with regards to the current CCS TSI annex A into force as per Commission Decision 2012/88/EU dated 25 th January 2012. Obviously, almost all the CRs were raised prior to the publication of this Commission decision 2012/88/EU, but nevertheless all the modifications described in the CR’s refer to the up to date version of the concerned documents referred to in this annex A currently into force.

3.1.1.3 All the variations from the previous official version (if any) of each document result from CR’s, which have been processed in the frame of the ERA CCM and they are materialised by revision marks. For each (not new) document a Word “doc” file with revision marks is therefore delivered, together with a file without revision mark (pdf and doc).

3.1.1.4 While for almost all the annex A documents (the so called “subdocs”) the processing of the modifications has been done in one single step, it has been necessary for the two main documents of the annex A (SRS and DMI specification) to organise distinct consolidation phases and corresponding intermediate releases, in order cope with the number and complexity of the CR’s related to these documents.



4. SUBSET-026 V3.3.0

4.1 Introduction

4.1.1.1 This new version of the SRS materializes the last step of the baseline 3 consolidation, according to the terms of the ERTMS Memorandum of Understanding signed on the 4th July 2008.

4.1.1.2 The present release notes trace and justify the variations with regards to SUBSET-026 v2.3.0 + SUBSET-108 v1.2.0; this consists of the list of the CR’s, which have been implemented in the first draft release in December 2008 (SUBSET-026 v3.0.0), in the first consolidation release in February 2010 (SUBSET-026 v3.1.0), in the second consolidation release in December 2010 (SUBSET-026 v3.2.0), and finally in this version 3.3.0.

4.1.1.3 As usual, these CR’s are implemented with revision marks, which are labelled with the number of the CR. This allows an easy traceability from the SRS text to the CR’s, which are published in the ERA CR database.

4.1.1.3.1 Exception: the error CR’s, classified as “IN” in the SUBSET-108 v1.2.0, were implemented in the version 3.0.0 of the SRS without revision marks. This is justified by the fact that the amended parts of the document, referred by these CR’s, are considered as being fully part of the baseline 2 currently into force.

4.1.1.4 The necessity to define intermediate releases may cause some revision marks highlighting revoked text from the CR’s that were previously implemented in the versions 3.0.0, 3.1.0 and 3.2.0. Since the modifications in the CR “Agreed Solution” field refer to one of these versions 3.0.0, 3.1.0 and 3.2.0 and in order to keep a full traceability of the various steps that led to this version 3.3.0, a Word “doc” file with these cumulated revision marks is provided.

4.1.1.5 Moreover a Word “doc” file with revision marks showing only the variations with regards to the current official referential (SUBSET-026 v2.3.0 + SUBSET-108 v1.2.0) is also provided, offering a better readability for the users for whom the CCM detailed steps are not relevant.



4.2 CR’s implemented in version 3.0.0

4.2.1 Preamble

4.2.1.1 Most of the CR’s listed in this section are put in perspective with the SUBSET-108 v1.2.0, which is also part of the current official baseline. It must be underlined that all the consolidation issues (error CR’s) listed in the SUBSET-108 v1.2.0, which affect the SUBSET-026, have been solved and implemented in the version 3.0.0.

4.2.2 Functional CR’s retained for baseline 3

4.2.2.1.1 The following functional CR’s, which were part of the list published by the Agency by end of September 2008, have been implemented in the SUBSET-026 v3.0.0.

CR number Headline

123 TSR in L2/L1

342 Redefinition of the international train categories

410 Shunting in STM areas

413 Level crossing modification

481 Supervision of the Radio Link

513 Non Leading mode

514 Cold movement detection

535 Door control supervision

589 JRU failure

593 Awakening on loops

637 Limited Supervision

660 Non ETCS airgap data for STM

676 Allowed current consumption

732 Follow up U151; Eddy current brake

742 Change Requests for an optimized use of the Radio In-fill function

745 Permitted braking distance

751 Start of mission in level 2

756Solution for ETCS to pass line sections under construction or refurbishment without isolation of ETCS

763 Ack feedback to RBC

764 Reconnection time limited



767 Shunting and level transitions

824 Jumping braking curves (follow up of CR601)

4.2.2.1.2 Note: There is no revision mark referred to CR754, which is superseded by CR767.

4.2.3 Error CR’s classified as “IN” in SUBSET-108 v1.2.0

4.2.3.1.1 All the CR’s, which are classified as “IN” in the SUBSET-108 and affect the SRS, have been implemented in the SUBSET-026 v3.0.0:

CR number Headline

20 Pending communication session

51 Position Reporting in RV Mode

66 Non relevant information for driver

78 Odometry inaccuracy at exit of speed restriction

138 Brakes release after max reversing distance overpassed

154 Text message inconsistency

170 Indication of track conditions

183 Data from single balise groups

187 End of Mission during RBC Handover

202Memorised balise groups for special position report not mentioned in table 4.10.1.3

223 Table of Supported Levels must be restored at Start of Mission

238 Shifted reference location

257Last eight reported BG identities stored on board with regard to deletion of stored position data in SoM procedure

268 End of mission: terminate communication session, if comm. session exists

319 LRBG orientation for special position report

320 Speed supervision behind LOA

344 Loss of radio connection in announced radio hole

390 Balise consistency check in RV mode

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

396 OBU can receive MA and other information after End of Mission

397 Conditions for Start/End of Text Indication

500 Change of Train Data from sources different from the driver



CR number Headline530 Reporting of PT mode when no communication session established

531 Start of Mission procedure re-engaged when session is not terminated.

560 No End of mission reporting when no communication established

601 OS acknowledgement

613 Emergency stop revocation after level transition

619 Message Acknowledgement

653 Contradiction Level transition immediately in PT

664 Unclear requirements for Route suitability

682 CR419 not in line with CR445

686 Ambiguities regarding reversing information in SRS v230

688 Consistency with old M_VERSION

699 List of balises in SH deleted in A3.4 for situations a-f, g-j, l

702 Update of list of expected balises in SR

706 Mismatch between announced and read balise group direction

713 PT distance D_NVPOTRP origin

718 location related conditions vs reverse movement in PT or roll-back

729 Single balises, assignment of a co-ordinate system

744 National values

748 Radio Link Supervision during RBC-RBC Handover

770 Train category spare values

771 Value NID_RBC is unknown

778 Geographical position reference balise groups

781 Relocation of data for MA in entry to Level 2

787 Activation of supervision of safe radio connection/ Follow-up CR529

788 Repetition of linking reactions

791 Repositioning and cross talk

792Storage of information in case of level transition announcement or RBC/RBC handover

796 Compatible upgrade

798 Mechanism for deletion of information on-board missing

4.2.3.1.2 The following “IN” CR’s do not impact the SRS: CR695, CR797.



4.2.4 Other error CR’s listed in SUBSET-108 v1.2.0

4.2.4.1.1 The following error CR’s, which are not classified as “IN” in the SUBSET-108 and affect the SRS, have been implemented in the SUBSET-026 v3.0.0:

CR number Headline

5 Message names

10 Message flow during termination of a communication session

12 Supervision of sequence

15 NID-C description

30 Editorial clarifications

31 Clarification of terms

38 Meaning of M_ERROR special values

40 position report in case of passing an unlinked balise group

47 missing transition from TR, PT to SL

49 Telegram or Message Counter

57 Mode related speed restriction in SH

58 incorrect comment on NID_STM in packet 72

71 Insertion of packet 0 in all messages from train to RBC

76 Splitting of an ERTMS train

90 High Priority channel (3)

99 MMI versus internal information

100 MMI versus mode table

101 Permitted speed in RV

103 There is no acceleration data specified as specific train data.

105 Availability of Acknowledgement button

107 Output information

124 Passing a signal in SR mode

128 Short number programmed in balise identification.

130 Confusing definition of Tamt.

132 Waiting for train data ack by RBC

133 Requirement doesn t belong to the chapter

134 L MAMODE for a shunting area

137 Q EMERGENCYSTOP definition



CR number Headline

140 Reversing distance sent by the RBC

141 Geographical position in shunting mode

142 Position report in level transition

148 Leaving Isolation mode

157 Valid direction for Reverse Movement Protection in SR

166 NID OPERATIONAL

168 MA request

177 Loss of End of Profile elements

180 Braking without indication of reason at standstill supervision

186 Message 42 further deletions

198 Revocation of Emergency Stop in SR

201 Supervision of radio link : unclear requirement

203 Default gradient of TSR forgotten

204 Report of train position when change of train orientation

205 Note to be removed

216 ambiguity of distance information in profile data

232 Unknown text message

235 Train data after loss of radio communication

237 Service Brake T NVCONTACT

242 ERTMS system version management

247 List of expected balises in SR mode

269 Transition SB-->SN after ACK from driver (Condition [58])

284 ETCS accepted information from STM X (SE)

285 Smooth transition and continuous supervision at the level Transition

293 End of Mission

296 Linking reaction info to RBC.

297 Override request

301 ETCS functions access by the STM in SL Mode

309 RBC transition order analog to level transition order

312 Level Transition at estimated - or maximum safe front end



CR number Headline

317 Failure of Packet 51 "ASP"

336 Storage of and text interpretation for Q_SLEEPSESSION

338 Some Errors in Active Functions Table

373 Mixed level transition announcement

374 Reason for TR on DMI

381 Display of maximum shunting speed

383 Transmission media for packet 12 is not only balise.

399 Message 153

402 When is linking used onboard

403 Acknowledgement of train data also in TR and PT

408 Brake application and revocation by the same system

411 STM transition in trip situation

412 Brake command in NP mode

414 Application rules for packets

415 Transition between STM levels

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

418 Target speed & distance output information to driver

423 Names NC_DIFF and V_DIFF

426 SRS reference missing

433 Linking reaction, logging thereof

437 Use of N_ITER

438 Mistake in Active Function Table for SH mode

446 Resuming initial state for non continuous profile data

450 Mode transition condition not correctly worded.

451 Further changes with reference to CR 66 and CR 91

452 Linking to unknown orientation is not possible

453 National/Default values

455Position report sending when passing level transition location with train rear end



CR number Headline459 National values sent by radio during SoM

461 Inconsistency: Sent train data and accept Acknowledgement in NL

463 MA shortening due to change of train data

466 Transition from TR to UN

471 No acknowledgement of termination of a communication session received

478 Establishment of Safe Connection - Retries

485 Review of SRS by STM WG

487 Impossibility to discriminate MA request reason

488 Geographical position handling in RV mode

490 No driver indication if permittted distance is exceeded in PT mode

491 Acknowledgement of the Route Related Information

492 Missing information in the pre-announcement message

493 Removal of Emergency Stop data from Route Related Information

494 Communication of SR balise list on the RBC/RBC interface

495 Restriction of capacity within the Route Related Information Request

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

505 Train Orientation not well defined

506 Update of ETCS Safety Analyses needed

509 Confusing reference in table 4.5.2

511 Train speed indication in SB mode.

521 Train location function for non leading and sleeping engines

522 Misleading sentences for RBC/RBC announcement.

524 Reporting of fatal error by Sleeping and Non leading engines.

540 SR mode acknowledgement

546 No train data in shunting and non leading

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

557 Reset of MA request parameters and position report parameters

558 Wording inconsistencies for linking

559 Inconsistencies in procedure "Shunting initiated by driver"



CR number Headline561 Availability of "Start" button in SE/SN mode

563 MA request if section timer expires

564 Missing Parameter in the Route Related Information message

565 Reporting / recording of balise errors

582 Permitted speed in UN mode

583 Indications on DMI in SR/OS mode

591 Change of train length

594 Speed definitions

595 Braking curve calculation

597 Communication session in SL mode

599 Reconnection after unexpected radio hole

604 Override procedure

605Shortening of track description - SSP and gradient profile must not have "open end"

607 Shunting request information to be displayed in UN mode

614 Informing the RBC when track description has been deleted on-board

618 Inconsistencies between Subset 035 and Subset 026

625 Backward movement after entry in FS/OS mode

632 Inconsistencies in stored/not stored info between A3.4 and 4.10

634 Q_EMERGENCYSTOP variable not in line with CLR91 and CLR532

635 Extension of MA following TAF not clear

636 System Start-up / Execution of Self-Tests

641 Local time

649 Inconsistency in position report specification and Active Functions Table

650 Train movement in L1 SB without Train Data

651 Availability of "Shunting request" input for driver

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

654 Unsuited wording of variable description

656 Follow up of CR126

657Unsuitability of RBC-RBC handover procedure in case of radio network change



CR number Headline659 Inconsistency override procedure during SoM

782 Reset of confidence interval

4.2.4.1.2 The remaining error CR’s listed in SUBSET-108 v1.2.0 have not been implemented in the SUBSET-026 v3.0.0, for the following reasons:

CR’s that have been rejected or superseded: CR44, CR68, CR83, CR119 CR264, CR298, CR579, CR580, CR638, CR639, CR642

CR’s that do not affect the SRS: CR239, CR240, CR262, CR265, CR302, CR394, CR400, CR406, CR448, CR480, CR482, CR503, CR584, CR643

4.2.5 Error CR’s not listed in SUBSET-108 v1.2.0

4.2.5.1.1 The following error CR’s, even if not listed in the SUBSET-108 v1.2.0, have been solved in the frame of the ERA CCM:

CR number Headline

343 Time between attempts to establish a safe connection

345 Text messages in SH, SE. SN mode

346 List of trackside supported levels

661 JRU, Inconsistencies between SRS and FFFIS JRU Downloading I/F

663 Onboard management of TAF request update

665 Session Termination order received when establishment still on-going

671 Inconsistency of Requests Parameter

672 Definition of Level transition acknowledgement

679 Inconsistency in 4.5.2 for Manage Emergency Stops

684 Using Override for overpassing SR distance

685 Using Override in case of Conditional Emergency stop

696 Follow up of CR382 clarification

697 Deletion of level transition when entering SR mode

698 Train Data not entered by driver

701 List of balises in SR missing in 4.8

717 Validity of "Former EOA" data

724 Clarification on cooperative shortening of MA decision criterion

727 Missing ack input

757 Insufficient provisions for management of future ERTMS/ETCS system



CR number Headlineversions

777 ETCS Override speed Supervision in SE/SN modes

779 Distances for Axle Load Speed Profiles

786 Management of track condition excluding Big Metal Masses

789 Inconsistency in level transition conditions

801 Precedence of chapter 4 transitions over chapter 5 procedures

804 National value for default location accuracy of balise group

807 Inconsistencies radio in-fill area information

821 Removal of the STM European from the ETCS specifications

822 Single balise group with M_MCOUNT = 254

826 Transition from SR to OS/SH for a further location

843 Message with several non-revocable TSRs is discarded

855Establishment of radio communication session when manually changing the level to 2 or 3

856 FRS references embedded in SRS

4.3 CR’s added in version 3.1.0CR number Headline

484 Clarification required: Mode profile and Infill MA

623 ETCS communication session

710Clarify if received but not yet applicable National Values shall be deleted in NP

716 Definition of Available STM

719 Ambiguity on Text Message Conditions

753 Use of the term DMI

784 Accepting track condition information in TR mode

794 Inconsistency in level transition announcement

800 Conditional level transition order overrides normal level transition order

805 SR mode inconsistencies

808 Train location/position unclear

811 Level 3 is missing



CR number Headline813 FIFO principle for ack requests

817 Shunting request pending

819 Balise group message consistency

820 Inconsistency in SRS 4.8.3 and 4.8.4

823 Delete route suitability function

827 Ambiguity in CR223

829 Adhesion cannot be unknown

841 Validity direction of transmitted information in RV mode (follow-up 253)

854Exception [5] does not apply to acceptation of “Co-operative shortening of MA” in table of section 4.8.3 of the SRS

857 RIU is missing in 3.5.3.7

858 Inappropriate driver's indications

859 Awakening on loop unclear

862 Indication limit vs new speed and monitoring chapter

864 Unclear steps in start of mission procedure

865 Mode transitions [62] vs [68]

868 Driver's navigations during SoM

869 Issues related to management of session / radio connection

871 "End of Non Leading" selection still existing (follow up of CR513)

872 Train running number set to "unknown" (follow up CR656)

875 New Q_TEXT value “Acknowledgement”

879 Missing release condition in PT

880 Gaps/inconsistencies in speed/distance monitoring chapter

881 findings from DMI WG (mainly SRS table 4.7.2)

883 Unclear requirement on downwards compatibility

884 Missing train category

893 TSR revocation in TR mode

894 Driver selection of Level in SoM opens second radio session

895Unintended extension of the permitted distance to run in Reversing due to filtering of info Onboard

896 Rejection of the Acknowledgement of Train Data when received in RV mode



CR number Headline901 Braking curves correction factors

902 Conversion model and brake build up time related issues

903 Driver confirmation of Train Data received from External Sources

905Capture of brake percentage when more than one combination of special brakes is possible

906 Findings from SRS 3.0.0 editorial review

4.4 CR’s added in version 3.2.0CR number Headline

680 Definition of expectation window

689 M_LOADINGGAUGE value 0

712 Confusion in packets not transmitted by infill devices

731 Inconsistencies between SRS chapter 7 and SUBSET-054

733 Button protection

802 Controversial onboard implementations

809 Direction of balise arrows in figures

828 Add language as stored information

842 Activation of supervision of safe radio connection /Follow-up 787

844 Unspecified train movement supervision after PT or RV distance is overpassed

847 Handling of direction dependent data from RBC without coordinate system

866 Entry into Level 2 questions

873 Discrepancies between Level and RBC id/phone number selections

878 Improvements for Passive Shunting (follow up of CR751)

897 End Section / Overlap Timer

899 Replacement of track description and linking information

907 Hazardous brake command in RV

909 New text message to be confirmed with the same ID (Follow up CR763)

910Location dependent Speed Restrictions to be deleted behind the train rear (Follow up of CR798)

911 Contradictions in the display of track conditions (Follow up of CR170)

912 Train speed in position report

913 Misleading remarks in message description

914 Missing repeat condition

915 Start/ End conditions for SoM

916 Traceability 4.7.2

917 Display of permitted speed in RV



CR number Headline918 Clause 5.8.2.1 a) vs a speed limit for triggering the override function equal to 0

919 Rejection of List of balises for SH area, error in solution of CR 650

922 Reduce 5 min on loss of connection

924 Inappropriate definition of the speed monitoring

925 Missing transition from TR mode

927 Safe speed supervision for calculation of EBI

928 Driver's indication of brake command(s)

929 Indication of the reasons of non stopping areas

942 Requirement for text display ambiguous in case start and end conditions are fulfilled

943 Standstill while capturing data

945 Incorrect SoM start condition

946 Train category 210 mm cant deficiency

947 Data view for fixed train data entry

948 Change of Driver ID in SH mode

949 "Balise read error" indication in NL mode

951 Train Data entry mechanism

953 Train related speed restriction

955 Availability for use of level 2/3

956 Override when override is active

957 Overlapping of CR solutions

958 Ambiguous exception

959 Braking curve problems

961 Standardised balise IDs for LS projects

963 Ambiguities in case of shortening of MA to the current position of the train

964 Computation of distances displayed on the planning information

965 Inconsistency in LS-->OS and OS-->LS transitions

966 Inconsistencies related to Track Conditions "Door Control" and "Current Consumption"

969 Clarification chapter 6 table headings

972 Safe areas management

976 Isolation mode inconsistency

986 Start of Reversing movement

989 Unclear LX icon display conditions

995Feedback from the review of document for early implementation of braking curves in baseline 2

996 Service brake build up time

1000 Sound horn

1001 Editorial improvements to procedure

1002 M_NVEBCL=0 (follow-up CR901)

1003 Miscellaneous editorial findings in SRS 3.1.0



CR number Headline1004 Wrong definition for M_AXLELOAD

1008 Inconsistency between clauses 3.18.3.8 and A3.6.2.1

1009 Ambiguity in conditional transition order: can it be sent by an RBC or not

1015 Unsuitability of non-stopping areas announcement mechanism

1018 Obtaining list of available networks

1019 System version management in reversing

1020 Unnecessary brake reaction at SoM

1022 Communication Session/Safe radio connection request in radio hole

4.5 CR’s added in version 3.3.0CR number Headline752 ERTMS-reference architecture

772 Overlap between SRS and Subset 027

818 ETCS-STM Header Issue

904 V_LOA for STM

923 Danger for SH in level 0 and STM

977 Impact of message processing time

992 LUC completion

1024 Maximum value for M_POSITION

1025 Missing condition for start in SR

1027 Change of Train Data in RV mode

1030 Reduced adhesion areas

1032 Management of Balises transmitting system version number X equal to 0

1036 Unclarities regarding the ETCS function change of traction system

1038 Mismanagement of Packet 39 in B3

1050 Inconsistency regarding ack for SR mode

1053 Trip situation is reported by STM

1068 STM National Trip Procedure use for ETCS DMI Shunting and Level buttons

1079 Inconsistent definition of leaving the indication status

1092 Errors in formula for release speed calculation

1096 Unclear brake release conditions after an unwanted further movement in PT/RV mode

1097 Miscellaneous editorial findings in SRS&DMI spec 3.2.0

1098 Handling of "No track conditions will be received" message in NL mode

1108 ETCS FRS removal from TSI annex A

1121 Unsafe handling of track conditions inhibiting special brakes

1131 Unnecessary reset of V_NVLIMSUPERV

1133 Tunnel stopping area functionality on B2 lines

1135 SUBSET-023 upgrade to baseline 3



CR number Headline1140 Translation of M_AXLELOAD in SRS chapter 6

1141 Conversion model for long trains

1143 Freezing of ETCS variables not reflected in chapter 6

4.6 CR’s withdrawn from version 3.2.0CR number Headline State589 JRU failure Rejected

756Solution for ETCS to pass line sections under construction or refurbishment without isolation of ETCS.

Superseded (CR992)



5. OTHER DOCUMENTS

5.1.1.1 The modifications to the other annex A documents, or the creation of new annex A documents, have been processed according the specific rules defined in the ERA CCM Procedure (see section A.2.3). In particular, the list of cover CRs and the other impacting CRs are detailed in the file embedded below:


ertms/etcs – class 1 - european union agency for ... · web viewsince the modifications in the cr...

Documents