1. 7/10/2019 7/10/2019 TIS Advisory Board 1030 Vienna, Oelzeltgasse 3/9
13. March 2019
10:30 – 15:30
7/10/2019

2. TIS Advisory Board Agenda
1. Welcome of the Participants
TIS-2020 Presentation
New User Interface
New Architecture
Modified user management
Timeline, Iterations
2. New Data Sharing Concept
Cooperating Companies sharing data automatically
General Agreements remain
3. TIS Advisory Board
Rigths and Roles
4. Merging of Trains
Introductions of Linking Regions
Basis for automated links
Basis for semi automated links (linking table)
Supporting procedures and tools (TrainCompositon Message)
Reports about missing links
5. Estimated Time of Arrival
State of Play
6. Reports for RUs
Presentation and state of play
7. Feedback and Proposals from the Participants
New requirements ...
Misceleanous
10 July 2019

3. TIS 2020 - Project Objectives
Eliminate known functional limitations and workarounds, mainly those implied by structures and processing based on former UIC messages
Increase usability and eliminate current limitations of user experience
Establish future-proof architecture, remove redundant implementations
Identify new business requirements & eliminate outdated requirements
Deal with known performance issues of the current solution and prepare for future volume requirements
10 July 2019

4. TIS architecture Current TIS architecture Future TIS architecture
10 July 2019

5. TIS-2020 first Iteration – March 2019
Train Search Engine Optimized
Replacing of Contracted Time Table (CTT) with PathDetailsMessage (PD). A CTT wizard an exterior tool besides TIS-2020 is assembling CTTs to PD
Introduction of “Linking Region” instead of Handover/Transfer Points for connecting national PathSections to entire international trains
New keys for merging of PathSections (IM, ReferenceNumber, ServiceNumber and Date instead of IM, ReferenceNumber and TransferpointTime
Setting up of the TIS-2020 test environment for test purposes and user training
10 July 2019

6. The new TIS – visual design – Searching Engine
Based on the user report about Train Information requests, the train info page is the most used page on the TIS application. Therefore this page has our utmost attention in regard to
Usability
Desktop and Smart Devices (Smartphones, Tablets)
Performance
Export and Reporting Functions
Topology is based on RNE BIG DATA and Google Map
Simplification
Train Request page will be merged to Train Search Engine
Finally only one page will cover the Train Information Request for static and dynamic information requests.
10 July 2019

7. The new TIS Train Search Engine
10 July 2019

8. TIS-2020 – Optimized Usermanagement Approach
TIS Usermanagement
Every Company is responsible for their own users
TIS user contract as basis for the sign up
User can request account directly via TIS user interface
Validation by the company admin
Companies with TIS User Agreements flaged in the database
Deactivation of user (leaving the company)
Management of users without activity
Users will be removed automatically, set to inactive, if no action is recorded in a defined time frame
10 July 2019

9. TIS-2020 User Management - Workflow

10. TIS-2020 User Management – User Experience
Login or Account Creation page

11. TIS-2020 User Management – User Experience
User provides necessary details

12. TIS-2020 User Management – User Experience
User verifies account

13. TIS-2020 User Management – User Experience
Account verification

14. Iterative project approach
Iteration 1:
Iteration 2:
Iteration 3:
Go Live: Q4 2019
Inbound interfaces (message processing)
Pathdetails, CTT, Train Running Information
Search engine
Nerork overview
Outbound interfaces
Train Running Forecast, Train delay cause
Data defect indicators
Historical train details – DWH data
Train linking
Path section notification, train composition (subset), train interruption, train ready message
Edit train data (i.e. Train delay data)
Message performance checks
10 July 2019

15. Logging - Kibana
Caused be a lot of inbound and outbound interfaces and millions of messages processed every day, the logging of data is essential to investigate data issues especially in regard to our clients.
Therefore a professional logging tool will be used to provide information about the data processing to our client.

16. TIS-2020 – Data Sharing New Approach
Cooperating companies will share the data by defalt
General agreements will remain, but mutual agreemens will be obsolete
Company admin can steer the sharing of data
10 July 2019

17. TIS-2020 – Data Sharing Conditions
Datasharing new approach:
By signing this Agreement, the TIS User agrees to RNE sharing train information with cooperating TIS Users.
The TIS User shall have access to the Data relating to its own trains and to the trains of other TIS-Users if they cooperate in the same train run (data sharing by default).
The Data shared by default includes all messages as defined in Annex A.1 The data sharing of messages defined in Annex A.2 can be managed by the TIS User via the dashboard of TIS.
TIS-User is able to exclude cooperating TIS User/s from the data sharing of all messages defined in Annex A.1 and Annex A.2 via the dashboard of TIS.
The exclusion is set in both directions (i.e. the TIS User who is excluding cooperating TIS User will as well not see the trains of the excluded TIS User).
10 July 2019

18. TIS-2020 – TIS Advisory Board
TIS Advisory Board Definition:
TIS Advisory Board is an advisory body within RNE organization open to all applicants (Railway Undertakings and non-Railway Undertakings Applicants),Terminal Operators (TOs) and Wagon Keepers who have signed this Agreement with RNE.
The membership of the board is respecting the following rules:
The board is informed about TIS-related decisions and developments
The board is allowed to propose developments in TIS
The board has no decision-making rights
The board meets once or twice a year in Vienna, RNE JO; attendance is not mandatory.
The list of TIS Members (IMs) and TIS Users (as defined above) is published and regularly updated on TIS website ( Availability
10 July 2019

19. TIS-2020 Merging Region – Linking National Train Section
TIS-2020 introduces “Merging Regions”
Merging Region will behave similar as Master Station in current version of TIS
Merging Region is composed of several points
In order for two national trains to be merged together, following conditions must be met:
Trains must start or end in the Merging Region
Trains must have same date at Merging Region
Trains must have same reference number (reference OTN) and/or same service number (OTN)
Optional:
Additional look up will be performed into mapping table, where mapping of trains numbers is defined in advance.
Advantages
Trains can be linked based on operational train number (OTN) as well, currently linking is based on Reference OTN only

20. TIS-2020 Merging Region - Example 1
Trainnumber Mapping Table
Locations
Trainnumber(s)
Breclav, Lanzhot, Bernhardsthal
47315, 42557, 47111, 45789
Merging Region
Břeclav os.n. (CZ)
Ref. OTN: | OTN: |
Incoming train
Lanžhot (CZ)
Ref. OTN: | OTN: |
Outgoing train
Bernhardsthal Fbf (AT)
Ref. OTN: | OTN: 44750, |
Merged train
Kúty (SK)

21. TIS-2020 – Linking of Trains advanced Features
TrainCompositionMessage (TCM)
Using of optional information about AttachedOperational TrainNumber from previsous or next IM
Comparison of consecutive TCMs to find out if key information like count of wagons, wagon numbers, Load ... does vary only to a definde extend
Train driver can provide information about previous or next Reference or Operational Trainnumber
Linking of trains via User interface
Linking via user interface will be simplified and link will performed directly in the database no resending of messages will be required anymore
All above mentioned features will be obsolete as soon as the the trainid is available
10 July 2019

22. Overview of linked trains and not linked trains
Bane NOR
Between 80% – 85% of trains are linked in most of cases
Some networks have very low rate of linked trains and high rate of not linked trains (IP, SZ-I, ZSR …)
TRV
BDK
ProRail
SZDC
PKP PLK
DBNetz
Infrabel
OEBB
LINKED TRAINS
SNCF
MAV
GYSEV
NOT LINKED TRAINS
BLS
SBB IP
RFI
ADIF
*data from November 2018

23. DBNetz and neighboring networksIM
Border section
linked trains
not linked trains
BDK
Flensburg Friedensweg <=> Padborg
37.1%
62.9%
Flensburg Friedensweg <=> Padborg Grænse
80.9%
19.1% IM
Border section
linked trains
not linked trains
PKP PLK
Forst (Lausitz) <=> Zasieki (Gr)
96.9%
3.1%
Frankfurt (Oder) Oderbrücke <=> Kunowice (Gr)
88.3%
11.7%
Guben <=> Gubin (Gr)
75.7%
24.3%
Horka Gbf => Bielawa Dolna (Gr)
95.3%
4.7%
Tantow => Szczecin Gum/Tan(Gr)
82.2%
17.8% IM
Border section
linked trains
not linked trains
ProRail
Bad Bentheim <=> Oldenzaal Grens
81.9%
18.1%
Emmerich <=> Zevenaar grens
92.4%
7.6%
Kaldenkirchen <=> Venlo grens
89.6%
10.4% IM
Border section
linked trains
not linked trains
Infrabel
Aachen Süd <=> HERGENRATH-FRONTIERE
51.9%
48.1%
Aachen West Pbf <=> MONTZEN-FRONTIERE
31%
69%
Aachen-Gemmenich <=> MONTZEN-FRONTIERE
93.6%
6.4% IM
Border section
linked trains
not linked trains
SŽDC
Furth im Wald <=> Česká Kubice
97.5%
2.5%
Schirnding <=> Cheb
95.6%
4.4%
Schöna <=> Dolní Žleb
95.9%
4.1% IM
Border section
linked trains
not linked trains
SNCF Réseau
Kehl <=> Strasbourg-Port-du-Rhin
67.1%
32.9%
Perl <=> Apach
87.2%
12.8%
Saarbrücken Saardamm <=> Forbach
62.9%
37.1%
Saarbrücken Saardamm <=> Stiring-Wendel
91.8%
8.2% IM
Border section
linked trains
not linked trains
OEBB INFRA
Freilassing <=> Salzburg Liefering (in Sb)
89.1%
10.9%
Kiefersfelden <=> Kufstein
97.6%
2.4%
Passau Hbf Voglau <=> Wernstein
82.5%
17.5%
Simbach (Inn) <=> Braunau am Inn
91.8%
8.2% IM
Border section
linked trains
not linked trains
SBB INFRA
Basel Bad Bf <=> Gellert
91.6%
8.4%
Konstanz <=> Konstanz Grenze (Abzw)
98.3%
1.7%
*data from November 2018

24. TIS-2020 Measures for solving the train linking problem
Already defined international processes
Not all stakeholders involved in train run are fulfilling defined international processes
Train ID
Expected to be available in 2024
Possibility to link train
TIS offers several ways to link a train (manually, automatic)
Train composition pilot
Combining data from composition of a train, there is a possibility to recognize same train even if it changes train number
GPS pilot
Additional GPS data from train can provide more accurate data about train run