Upload
lamtu
View
225
Download
1
Embed Size (px)
Citation preview
1
Signaling Programme
Signaling Programme - Laboratory Test
05.05.2015 Gitte Oberbossel
2
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
3
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.
4
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
5
Simple solution overview of signaling programme and scope of Joint Test Lab (JTL) test
TMS
Point Machine
Axle Counter
LX/ PWS/SC
IXL RBC
Balise
SIL2
TMS
Point Machine
Axle Counter
LX/ PWS/SC
RBC IXL
Balise
SIL2
On-line Scheduler
Key Management
Server
Long Time Planner
Decision Support System
Hand Held Terminal
Hand Held Terminal
TRIS
Enterprise Service
Bus
External
GSM-R
Integration between different suppliers
6
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
7
Test organizations
8
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
9
Test environments
Joint test Lab (Lysgårdsvej)
ESB TEST &
External interface(Otto Busses Vej)
Interface
Supplier Test(At there own adress)
Supplier test(At there own address)
F-BanenIn
terf
ace
10
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
11
JTL test process
12
Configurations management - test baselines
– All test cycles are under configurations management responsibility
– All test cycles are baselined in the the Baseline Log on SharePoint
EMO entry document
for each test cycle Baseline IDIs documented in
the following documents
Entry baseline ID
New
bas
elin
e ID
du
rin
g te
st
exec
uti
on
s
Defect reports
JTL test schedule
JTL test schedule
Final baseline ID
EMO exit document for
each test cycle
Test reports
Test procedure result
13
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
14
JTL test schedule – updated processes
15
Entering & exiting each test cycle