Release Notes

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 Page 1/21


1. M

ODIFICATION

H

ISTORY

Section Number Issue Number

Date

0.1

08/03/2012

1.0

09/03/2012

1.1

27/03/2012

All

5.1.1.1

Modification / Description

New document AH

Minor correction after internal review

AH

Minor correction in the embedded Excel sheet

(Renumber the EIRENE

FRS and SRS cover CR)

AH

Author



2. T

ABLE OF

C

ONTENTS

1.

M ODIFICATION H ISTORY ................................................................................................................ 2

2.

T ABLE OF C ONTENTS .................................................................................................................... 3

3.

INTRODUCTION ........................................................................................................................ 4

4.

SUBSET-026 V 3.3.0 ................................................................................................................... 5

4.1

Introduction ....................................................................................................................... 5

4.2

CR’s implemented in version 3.0.0 .................................................................................... 6

4.2.1

Preamble ................................................................................................................... 6

4.2.2

Functional CR’s retained for baseline 3 ...................................................................... 6

4.2.3

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

4.2.4

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

4.2.5

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

4.3

CR’s added in version 3.1.0 ............................................................................................ 16

4.4


4.5


4.6

CR’s withdrawn from version 3.2.0 .................................................................................. 20

5.

O

THER DOCUMENTS

................................................................................................................... 21



3. INTRODUCTION

3.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

V

3.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 re voked 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.



CR’s implemented in version 3.0.0 4.2

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.



756

763

764

767

824

676

732

742

745

751

535

589

593

637

660

CR number Headline

123 TSR in L2/L1

342 Redefinition of the international train categories

410

413

481

513

514

Shunting in STM areas

Level crossing modification

Supervision of the Radio Link

Non Leading mode

Cold movement detection

Door control supervision

JRU failure

Awakening on loops

Limited Supervision

Non ETCS airgap data for STM

Allowed current consumption

Follow up U151; Eddy current brake

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

Permitted braking distance

Start of mission in level 2

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

Ack feedback to RBC

Reconnection time limited

Shunting and level transitions

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:


20 Pending communication session


613

619

653

664

530

531

560

601

390

392

396

397

500

257

268

319

320

344



51 Position Reporting in RV Mode

66

78

138

154

170

183

187

202

223

238

Non relevant information for driver

Odometry inaccuracy at exit of speed restriction

Brakes release after max reversing distance overpassed

Text message inconsistency

Indication of track conditions

Data from single balise groups

End of Mission during RBC Handover

Memorised balise groups for special position report not mentioned in table

4.10.1.3

Table of Supported Levels must be restored at Start of Mission

Shifted reference location

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

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

LRBG orientation for special position report

Speed supervision behind LOA

Loss of radio connection in announced radio hole

Balise consistency check in RV mode

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

OBU can receive MA and other information after End of Mission

Conditions for Start/End of Text Indication

Change of Train Data from sources different from the driver

Reporting of PT mode when no communication session established

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

No End of mission reporting when no communication established

OS acknowledgement

Emergency stop revocation after level transition

Message Acknowledgement

Contradiction Level transition immediately in PT

Unclear requirements for Route suitability




682 CR419 not in line with CR445

771

778

781

787

718

729

744

748

770

788

791

686

688

699

702

706

713

792

796

798

Ambiguities regarding reversing information in SRS v230

Consistency with old M_VERSION

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

Update of list of expected balises in SR

Mismatch between announced and read balise group direction

PT distance D_NVPOTRP origin location related conditions vs reverse movement in PT or roll-back

Single balises, assignment of a co-ordinate system

National values

Radio Link Supervision during RBC-RBC Handover

Train category spare values

Value NID_RBC is unknown

Geographical position reference balise groups

Relocation of data for MA in entry to Level 2

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

Repetition of linking reactions

Repositioning and cross talk

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

Compatible upgrade

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:


5 Message names

10 Message flow during termination of a communication session

12 Supervision of sequence




15 NID-C description

137

140

141

142

148

157

105

107

124

128

130

132

133

134

99

100

101

103

57

58

71

76

90

40

47

49

30

31

38

Editorial clarifications

Clarification of terms

Meaning of M_ERROR special values position report in case of passing an unlinked balise group missing transition from TR, PT to SL

Telegram or Message Counter

Mode related speed restriction in SH incorrect comment on NID_STM in packet 72

Insertion of packet 0 in all messages from train to RBC

Splitting of an ERTMS train

High Priority channel (3)

MMI versus internal information

MMI versus mode table

Permitted speed in RV

There is no acceleration data specified as specific train data.

Availability of Acknowledgement button

Output information

Passing a signal in SR mode

Short number programmed in balise identification.

Confusing definition of Tamt.

Waiting for train data ack by RBC

Requirement doesn t belong to the chapter

L MAMODE for a shunting area

Q EMERGENCYSTOP definition

Reversing distance sent by the RBC

Geographical position in shunting mode

Position report in level transition

Leaving Isolation mode

Valid direction for Reverse Movement Protection in SR




166 NID OPERATIONAL

312

317

336

338

373

374

269

284

285

293

296

297

301

309

235

237

242

247

203

204

205

216

232

168

177

180

186

198

201

MA request

Loss of End of Profile elements

Braking without indication of reason at standstill supervision

Message 42 further deletions

Revocation of Emergency Stop in SR

Supervision of radio link : unclear requirement

Default gradient of TSR forgotten

Report of train position when change of train orientation

Note to be removed ambiguity of distance information in profile data

Unknown text message

Train data after loss of radio communication

Service Brake T NVCONTACT

ERTMS system version management

List of expected balises in SR mode

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

ETCS accepted information from STM X (SE)

Smooth transition and continuous supervision at the level Transition

End of Mission

Linking reaction info to RBC.

Override request

ETCS functions access by the STM in SL Mode

RBC transition order analog to level transition order

Level Transition at estimated - or maximum safe front end

Failure of Packet 51 "ASP"

Storage of and text interpretation for Q_SLEEPSESSION

Some Errors in Active Functions Table

Mixed level transition announcement

Reason for TR on DMI


455

459

461

463

466

471

478

433

437

438

446

416

418

423

426

450

451

452

453



381 Display of maximum shunting speed

383

399

402

403

408

411

412

414

415

Transmission media for packet 12 is not only balise.

Message 153

When is linking used onboard

Acknowledgement of train data also in TR and PT

Brake application and revocation by the same system

STM transition in trip situation

Brake command in NP mode

Application rules for packets

Transition between STM levels

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

Target speed & distance output information to driver

Names NC_DIFF and V_DIFF

SRS reference missing

Linking reaction, logging thereof

Use of N_ITER

Mistake in Active Function Table for SH mode

Resuming initial state for non continuous profile data

Mode transition condition not correctly worded.

Further changes with reference to CR 66 and CR 91

Linking to unknown orientation is not possible

National/Default values

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

National values sent by radio during SoM

Inconsistency: Sent train data and accept Acknowledgement in NL

MA shortening due to change of train data

Transition from TR to UN

No acknowledgement of termination of a communication session received

Establishment of Safe Connection - Retries


521

522

524

540

546

497

505

506

509

511

548

557

558

559

561

563

564

565

582

583



485 Review of SRS by STM WG

487

488

490

491

492

493

494

495

Impossibility to discriminate MA request reason

Geographical position handling in RV mode

No driver indication if permittted distance is exceeded in PT mode

Acknowledgement of the Route Related Information

Missing information in the pre-announcement message

Removal of Emergency Stop data from Route Related Information

Communication of SR balise list on the RBC/RBC interface

Restriction of capacity within the Route Related Information Request

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

Train Orientation not well defined

Update of ETCS Safety Analyses needed

Confusing reference in table 4.5.2

Train speed indication in SB mode.

Train location function for non leading and sleeping engines

Misleading sentences for RBC/RBC announcement.

Reporting of fatal error by Sleeping and Non leading engines.

SR mode acknowledgement

No train data in shunting and non leading

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

Reset of MA request parameters and position report parameters

Wording inconsistencies for linking

Inconsistencies in procedure "Shunting initiated by driver"

Availability of "Start" button in SE/SN mode

MA request if section timer expires

Missing Parameter in the Route Related Information message

Reporting / recording of balise errors

Permitted speed in UN mode

Indications on DMI in SR/OS mode


636

641

649

650

651

652

654

656

657

659

782

605

607

614

618

625

632

634

635



591 Change of train length

594

595

597

599

604

Speed definitions

Braking curve calculation

Communication session in SL mode

Reconnection after unexpected radio hole

Override procedure

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

Shunting request information to be displayed in UN mode

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

Inconsistencies between Subset 035 and Subset 026

Backward movement after entry in FS/OS mode

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

Q_EMERGENCYSTOP variable not in line with CLR91 and CLR532

Extension of MA following TAF not clear

System Start-up / Execution of Self-Tests

Local time

Inconsistency in position report specification and Active Functions Table

Train movement in L1 SB without Train Data

Availability of "Shunting request" input for driver

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

Unsuited wording of variable description

Follow up of CR126

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

Inconsistency override procedure during SoM

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

801

804

807

821

757

777

779

786

789

684

685

696

697

698

701

717

724

727

663

665

671

672

679

4.2.5.1.1 Th e 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:


343 Time between attempts to establish a safe connection

345

346

661

Text messages in SH, SE. SN mode

List of trackside supported levels

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

Onboard management of TAF request update

Session Termination order received when establishment still on-going

Inconsistency of Requests Parameter

Definition of Level transition acknowledgement

Inconsistency in 4.5.2 for Manage Emergency Stops

Using Override for overpassing SR distance

Using Override in case of Conditional Emergency stop

Follow up of CR382 clarification

Deletion of level transition when entering SR mode

Train Data not entered by driver

List of balises in SR missing in 4.8

Validity of "Former EOA" data

Clarification on cooperative shortening of MA decision criterion

Missing ack input

Insufficient provisions for management of future ERTMS/ETCS system versions

ETCS Override speed Supervision in SE/SN modes

Distances for Axle Load Speed Profiles

Management of track condition excluding Big Metal Masses

Inconsistency in level transition conditions

Precedence of chapter 4 transitions over chapter 5 procedures

National value for default location accuracy of balise group

Inconsistencies radio in-fill area information

Removal of the STM European from the ETCS specifications




822 Single balise group with M_MCOUNT = 254

826

843

855

856

Transition from SR to OS/SH for a further location

Message with several non-revocable TSRs is discarded

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

FRS references embedded in SRS

4.3 CR’s added in version 3.1.0

800

805

808

811

813

817

819

820

823

827

829

841

716

719

753

784

794


484 Clarification required: Mode profile and Infill MA

623

710

ETCS communication session

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

Definition of Available STM

Ambiguity on Text Message Conditions

Use of the term DMI

Accepting track condition information in TR mode

Inconsistency in level transition announcement

854

Conditional level transition order overrides normal level transition order

SR mode inconsistencies

Train location/position unclear

Level 3 is missing

FIFO principle for ack requests

Shunting request pending

Balise group message consistency

Inconsistency in SRS 4.8.3 and 4.8.4

Delete route suitability function

Ambiguity in CR223

Adhesion cannot be unknown

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

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


895

896

901

902

903



857 RIU is missing in 3.5.3.7

880

881

883

884

869

871

872

875

879

893

894

858

859

862

864

865

868

905

906

Inappropriate driver's indications

Awakening on loop unclear

Indication limit vs new speed and monitoring chapter

Unclear steps in start of mission procedure

Mode transitions [62] vs [68]

Driver's navigations during SoM

Issues related to management of session / radio connection

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

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

New Q_TEXT value “Acknowledgement”

Missing release condition in PT

Gaps/inconsistencies in speed/distance monitoring chapter findings from DMI WG (mainly SRS table 4.7.2)

Unclear requirement on downwards compatibility

Missing train category

TSR revocation in TR mode

Driver selection of Level in SoM opens second radio session

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

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

Braking curves correction factors

Conversion model and brake build up time related issues

Driver confirmation of Train Data received from External Sources

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

Findings from SRS 3.0.0 editorial review






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)

910

Location 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

918 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

995

Feedback 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

1004 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






1121

1131

1133

1135

1140

1141

1143

1053

1068

1079

1092

1096

1097

1098

1108

752

772

818

904

923

977

992

1024

1025

1027

1030

1032

1036

1038

1050

ERTMS-reference architecture

Overlap between SRS and Subset 027

ETCS-STM Header Issue

V_LOA for STM

Danger for SH in level 0 and STM

Impact of message processing time

LUC completion

Maximum value for M_POSITION

Missing condition for start in SR

Change of Train Data in RV mode

Reduced adhesion areas

Management of Balises transmitting system version number X equal to 0

Unclarities regarding the ETCS function change of traction system

Mismanagement of Packet 39 in B3

Inconsistency regarding ack for SR mode

Trip situation is reported by STM

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

Inconsistent definition of leaving the indication status

Errors in formula for release speed calculation

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

Miscellaneous editorial findings in SRS&DMI spec 3.2.0

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

ETCS FRS removal from TSI annex A

Unsafe handling of track conditions inhibiting special brakes

Unnecessary reset of V_NVLIMSUPERV

Tunnel stopping area functionality on B2 lines

SUBSET-023 upgrade to baseline 3

Translation of M_AXLELOAD in SRS chapter 6

Conversion model for long trains

Freezing of ETCS variables not reflected in chapter 6

4.6

CR number

589

756

CR’s withdrawn from version 3.2.0

Headline State

JRU failure

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

Rejected

Superseded (CR992)



5. O

THER DOCUMENTS

5.1.1.1 The modifications to the other annex A documents, or the creation of new annex A documents, ha ve 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:

AnnexAdocs_vs_CRs_

120327.xls


Release Notes

ERTMS/ETCS

ODIFICATION

ISTORY

ABLE OF

ONTENTS

V

4.1 Introduction

CR’s implemented in version 3.0.0 4.2

4.3 CR’s added in version 3.1.0

4.4 CR’s added in version 3.2.0

4.5 CR’s added in version 3.3.0

4.6

CR’s withdrawn from version 3.2.0

THER DOCUMENTS

Related documents

Products

Support

Release Notes

ERTMS/ETCS

ODIFICATION

ISTORY

ABLE OF

ONTENTS

V

4.1 Introduction

CR’s implemented in version 3.0.0 4.2

4.3 CR’s added in version 3.1.0

4.4 CR’s added in version 3.2.0

4.5 CR’s added in version 3.3.0

4.6

CR’s withdrawn from version 3.2.0

THER DOCUMENTS

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib