Signaling Programme
Signaling Programme Signaling Programme - Laboratory Test 05.05.2015 Gitte Oberbossel 1 Agenda – F-Banen signaling programme and migration strategy – Simple solution overview of signaling programme and scope of Joint Test Lab (JTL) test – Signaling programme organization – Who is using the JTL laboratory and what is being tested? – Test organizations – JTL test phase & cycle – Test environments – Laboratory programme test strategy – Configurations management - test baselines – JTL test schedule – Entering & exiting each test cycle TEST I SP 2 F-Banen signaling programme and migration strategy A replacement of all signaling on the entire Banedanmark railway network with ERTMS by the end of 2021 That is the objective of the Danish signaling programme decided by the Danish parliament in 2009. The decision to fund a total replacement programme was made by a broad political majority. It was a historic decision. A total renewal of all signaling on a national rail network in a single programme has never been attempted on this scale before in Europe. Denmark will be the first country to carry out a countrywide implementation of ERTMS level 2, the newest European common signaling standard. The programme represents a major change in technology intended to maximize the possibilities and benefits of re-signaling the Danish railway network. It is unique in its approach of focusing on economies of scale and creating a competitive market situation to ensure optimized price and quality. This may be a normal market situation in many other businesses but unusual in the signaling business. 3 F-Banen signaling programme and migration strategy Rail – – – – – – – – – – – data (F-Banen + S-Banen) 2.700 trains/day 40.000 daily departures + 190 mio. passengers + 15 mio. tonnes freight Line: 2.132 km / track: 3.240 km Bridges: 2.342 Interlockings: 480 Remote control/signalbox: 16 Stations: 307 Level crossings: 1096 Commercial trains: 590 F-Banen solutions ERTMS 2 Baseline 3 and modern centralized signalling infrastructure and Onboard More interfacing projects: 2 major infrastructure contracts All Onboard equipment Fixed transmission network DK-STM GSM-R: voice and GPRS Traffic Control Centres New operational rules All training activities All safety approvals Enterprise Service Bus 4 Simple solution overview of signaling programme and scope of Joint Test Lab (JTL) test Decision Support System TRIS Integration between different suppliers Long Time Planner On-line Scheduler External TMS TMS Enterprise Service Bus SIL2 Hand Held Terminal Hand Held Terminal SIL2 Key Management Server IXL RBC RBC IXL GSM-R Point Machine Axle Counter LX/ PWS/SC Balise Point Machine Axle Counter LX/ PWS/SC Balise 5 Who is using the JTL laboratory and what is being tested? Who is using the JTL laboratory All suppliers – Alstom, Thales, Alstom (Onboard) Customer for customer testing External interface integration tests ESB – external interface tests Demo’s, inspections, witnessing What is being tested? All integration testing between the different deliveries from Supplier and Customer. End-to-end tests Performance tests Security IT tests Failover/recovery tests Customer operation tests Customer usability tests Customer acceptance tests e.g. within ETCS & IXL Customer’s own system integration test Maintenance processes 6 Test organizations 7 JTL test phase & cycles JTL test phase – split into x number of test cycles JTL runs in accordance with a joint test schedule constituting that all tests are grouped into one test cycle 8 Test environments Supplier test Supplier Test (At there own address) (At there own adress) In te rfa ce F-Banen Joint test Lab (Lysgårdsvej) Interface ESB TEST & External interface (Otto Busses Vej) 9 Laboratory programme test strategy A test model & process used for all test phases running like a factory as it uses the same overall process in which the only content is change Definition of process Tools to do it the right way 10 JTL test process 11 Configurations management - test baselines – All test cycles are under configurations management responsibility – All test cycles are baselined in the the Baseline Log on SharePoint JTL test schedule Test reports Baseline ID Is documented in Entry baseline ID the following documents Final baseline ID New baseline ID during test executions EMO entry document for each test cycle Defect reports EMO exit document for each test cycle JTL test schedule Test procedure result 12 JTL test schedule – JTL primavera project will be used to show 3 views: o Full JTL schedule: A primavera schedule which is to document all activities during the JTL test phase o 8 week JTL schedule: An excel sheet showing this week’s and the next 7 weeks’ test activities within installations, smoke test and test executions o Test cycle F-Banen E/W schedule: For both Alstom & Thales, it shows the test cycle planned/running from FAT test to completed review of test report 13 JTL test schedule – updated processes 14 Entering & exiting each test cycle 15
© Copyright 2024