3: ETCS Specifications: SRS Catalog of requirements. ERTMS Platform, 14th March 2007; UIC HQ Paris

Transcription

1 3: ETCS Specifications: SRS Catalog of requirements

2 PREAMBLE & CONSIDERATIONS The aim of the ERTMS Platform is to share information from running processes The list of functional changes following the ERA process in the ERA Control Group is provided for information. It is an official list with 44 functional CR; 2 of them are already accepted by ERA Each Railway can verify if his functional needs are being taken into consideration in the ERA process, in fact this was already done by CER and EIM in which all railways participate In case of some missing functionalities the corresponding Railway / Operator must address an additional request either through the EIM or through the CER. EIM / CER are the speakers in front of ERA to present demands of additional functionalities agreed by consensus

3 ORGANIZATIONAL INTERFACES ERA CCM EC C. A21 Political Level ERTMS Platform information, support (basis: Declaration) support in technical & operational ETCS issues EIM ERIG ERTMS Users Group CER CR analysis, support and advice (basis: MoU) NPM ERTMS project* ERTMS project* ERTMS project* GSM-R Industry Group S.C & S.G UNIFE UNISIG *) national and corridor projects Strategic coordination Generic Technical work Conduct Code Deployment and Specific Technical work

4 UNISIG EEIG Railways Title EEIG KMS WG KMC EVC interface Q079 Nb1 (DB) Level X<>STM transitions ack Q064 CHR-01T019(GIF) TSR in L2/L Q073 F3QD10 v.3 (RFF) D_SR Stopping trains 299 B4.88 Nb67 (DB) Version compatibility check 342 Solution ERA Redefinition of train categories 372 B EG-TQN1(NR) FIS EVC - EIRENE voice radio 397 annex Conditions for Start/End Text Indication Nb72 (DB) Shunting in STM areas TSI CCS CR Level crossing modification n.2 (RFI) Supervision of the Radio Link CER Nb 79 (DB) Tilting malfunctioning 513 B Q350 (ORG) NL mode NEP-0019 Cold movement detection EEIG Default values if position unknown NEP-0020 Door control supervision NEP-0017 DMI planning area Q382 (ORG) Announcements of all level transitions EEIG JRU failure CR074 (AEIF CCB) Awakening on loops 637 solution FRS Limited Supervision F3QD098 (RFF) Non ETCS airgap data for STM CER Nb 91 (DB) Allowed current consumption List of Functional CR for SRS (I)

5 UNISIG EEIG Railways Title NEP-0030 Awakening performance requirement 732 Follow up U151; Eddy current brake GSMR packet switching CER RFI Radio infill CER Nb 95 (DB) National values CER Nb 96 (DB) Permitted braking distance CER Nb 99 (DB) Shunting in L2 in degraded situation CER Nb 101 (DB) Range of speed dial CER SBB Number of keys per onboard EEIG Speed restriction on downhill gradient Nb 97 (DB) Start of mission in level CER015 Crossing RBC border in SH CER016 Limited radio resources CER017 Lines under construction CER KMC RBC interface Q052 (ORG) Prevent selection of level 0 by mistake 228 ORG Data Entry procedure 229 ORG Awakening in level Adif CW balise 247 BV Ack feedback to RBC 253 EEIG Reconnection time limited List of Functional CR for SRS (II)

6 5: Test Cases

7 The consolidation Process through testing NEW Base line (SRS 2.3.0) Technical verification of conformity Operational verification of interoperability

8 The consolidation Process through testing A) Technical verification of conformity: 1. Test specification alignment: Features Test Cases Test Sequences + Test Seq. Debugger Reference Test Tools 2. EVC Test Campaign: All the suppliers in a common and independent reference Lab Participants: ERA / ERTMS Users Group / UNISIG / CEDEX / DLR / ERSA / IMA

9 SYSTEM TEST SPECIFICATION Feature (650): A feature is a group of requirements, which fulfilment can be tested at the available interfaces. Features shall be characteristics expected from a system by the operator and therefore outwardly visible. Test cases (1.276): These are the formal functional and technical descriptions of the test cases needed to prove interoperability. It is expected that for trackside test cases due to lack of technical description of interfaces only functional test case descriptions are possible. Test sequence (62): Test sequences are used for automatic execution of the test cases, namely by grouping test cases into scenarios which are sensible from an operations point of view and which can be run on the test environments generally used in industry and similar to the test environment used in EMSET.

10 REFERENCE TOOLS ARCHITECTURE ETCS LEVEL STM TRACKSIDE SIMULATOR LSTMTS STM CODING & COMMUNICATION STMCC JRU DOWNLOAD EVALUATION MODULE DEM FFFIS JRU FFFIS STM LOOP DRIVER DMI EVENT OR RECORDER EMULATOR DER DMI ODO ON BOARD INDUSTRIAL EQUIPMENT TIU BTM EURORADIO SPEE D TIU Signals ADAPTOR FFFIS SPEED SENSOR ODO SIMULATOR ADAPTOR SSS TIU TIU SIMULATOR ADAPTOR TIUS ADAPTOR FFFIS EUROLOOP SIGNAL GENERATOR LSG FFFIS FFFIS EUROBALISE SIGNAL GENERATOR BSG FFFIS (wired) EURORADIO COM. SIMULATOR RCS TRAIN MOTION SIMULATOR TMS SCENARIO GENERATOR SG ETCS L1 TRACKSIDE SIMULATOR L1TS ETCS L2 TRACKSIDE SIMULATOR L2TS SCENARIO CONTROLLER SC DATA EXCHANGE TRIP ANALYSIS & VALIDATION TAV MODULE EVENT RECORDER MER Air gap is used Equipment to be tested

11 The consolidation Process through testing Documentation on testing incorporated to the TSI: System Test Specification. Informative documents: Subset 076-0, v 2.2.2: Test Plan Subset 076-2, v 2.2.2: Methodology to Prepare Features Subset 076-3, v : Methodology of testing Subset , v 2.2.2: Test Sequence Generation: Methodology and Rules Subset , v 2.2.2: ERTMS Class 1 States for Test Sequences Subset , v 2.2.2: On-board Data Dictionary Subset , v 2.2.2: SRS v Traceability Subset , v 2.2.2: Test Cases Database Subset , v 2.2.2: Test Cases Coverage Subset , v 2.2.2: Test Sequences Database System Test Specification. Mandatory documents: Subset , v 2.2.2: Features list reviewed Subset , v 2.2.2: Test cases reviewed Subset , v 2.2.2: Test Sequences with sequence bit maps Subset 094-0, v 2.0.0: UNISIG Functional Requirements for an on board Reference Test Facility

12 Assessment of ETCS Cross-interoperability 2 Structured cross tests considering the operational conditions By knowing all (?) the differences, unified tests can be performed to check the behaviour of the system at each line or railway suppliers have to provide 1. register of Cr used in products / assemblies of each supplier 2. register of national add on used in products for safe and proper operation 3. register of interoperability components which are certified by NoBo including exceptions / restrictions if necessary RU and IM provide 4. register of assemblies which are certified by NoBo including exceptions / restrictions if necessary This way is more efficient than trouble-shooting A unified test catalogue has to be elaborated and to be established by a European Body LTZF 431,

13 The consolidation Process through testing B) Operational verification of Interoperability: Operational scenarios for cross tests Cross tests campaigns in line At National level: Pilot and Commercial lines: Track cross tests in France: Ansaldo (CSEE) + Alstom Track cross tests in Holland: Alstom + Bombardier + Siemens Track cross tests in Italy: Ansaldo + Alstom Track cross tests in Spain: Ansaldo(CSEE) + Alstom + Siemens + Invensys + Bombardier Track cross tests in Switzerland: Alstom + Alcatel + Siemens Cross tests between different countries Reference Test Track (RFF test track in Valenciennes) Cross tests between Belgium, France, Luxembourg and the Netherlands Cross tests between Italy and Switzerland Cross tests between Germany and Switzerland Cross tests between Austria and Hungary