The TTR IT Landscape project approached the need for IT in several steps:
Based on the definition of the TTR main process, the basic needs and requirements for IT were analysed. Following this first analysis, the project team determined which IT elements and services were already available and which were still missing. The resulting list of IT requirements represents an integral part of the RNE and FTE agreement to implement TTR.
For the new IT solutions to function properly in the new process, specifications must be coordinated precisely, and implementation at national level in the IMs’ and RUs’ systems is just as important as the implementation of centrally managed components. Without successful IT implementation in the respective companies, the central components are essentially empty shells. Added value can only be achieved through uniform implementation across the sector.
Definition of TTR IT Landscape
Starting in 2017, a document was created, defining all relevant aspects of the TTR IT landscape. The future IT landscape shall be based on a modular IT architecture, addressing the increased need to move from simple path management to capacity management and combining central systems with national systems.
In parallel, a detailed ‘as-is’ analysis was done. It enabled the team to roughly evaluate the rollout timeline by comparing the current situation with the envisioned landscape.
Since major work must be done in this area by IMs and RUs, a feasibility check involving all members of RNE and FTE was conducted in early 2019 to elaborate the exact rollout timeline, identify pressure points in the IT landscape concept and estimate the resources required for implementation. On this basis technical specifications have been created, the last open points of which are to be clarified by May 2020.
The TTR IT Landscape
The future TTR IT landscape is split into two main blocks:
- The central IT framework, developed by RNE
- National and external systems, which need to communicate with the central IT framework
Being the centerpiece of the IT landscape, which takes into account the needs of the railway undertakings/applicants (RUs) and infrastructure managers/allocation bodies (IMs/ABs), the central TTR IT framework is defined in modules and contains layers for RUs and IMs, as well as a common layer. Each module contains its own functionalities (‘micro services’). Existing tools, such as PCS and the TCR Tool, will be integrated into this architecture. National IM and RU systems, as well as other external IT systems will communicate with the central TTR IT framework, complementing the TTR IT Landscape.