Aatish Mishra
Aatish Mishra
Last updated 
  • Different IM's have different needs, strategies and objectives. Hence strategies for migration has to be provided on a case-by-case basis.
  • Migration should be considered with least effect on cost and operation. For example new components should be compatible with existing systems.
  • The end result for each IM should be a modular, upgradable and a standardized CCS suited to their individual business requirements.

RCA Migration Roadmap 69.4 KB View full-size Download

Scope of the Cluster:
  • Describe how the system architectures of different infrastructure managers will evolve, starting at the legacy situation and following the whole period of migration towards the RCA target system architecture, taking into account both train systems and rail infrastructure.
  • Suggest an approach that can be projected onto the situation of each individual infrastructure manager.
  • Analyze and propose standardized and low-cost system developments that can support migration by interfacing with the existing system.

Focus of Migration w.r.t the Reference Archtiecture 182 KB View full-size Download
  • As mentioned before, migration strategies are developed based on the existing system of each IM. For this plateaus are considered.
  • A plateau represents a somewhat stable state of the architecture.
Plateaus in Migration 95.9 KB View full-size Download

Plateaus in Migration (taken from Migration Report) 228 KB View full-size Download
  • Plateau one includes application of Object controllers with RBC and IXL. Plateau 2 incorporates ATO in conjunction with plateau 1 and prepares for upgrading to higher plateaus.
  • Plateaus 3 and 4 incorporate on board localisation with APS. The difference is that in plateau 4 trackside assets are removed completely to reduce costs.
  • This approach is provided so to allow for the flexibility due to different requirements for various IM's (see below figure). Each IM can target a certain plateau, depending on their starting situation and business objectives . Objective is to reduce the diversity of systems from a national viewpoint.

Starting situations of each IM is different (not all are shown) 257 KB View full-size Download

Relation with Operational Harmonization:
  • Migration with respect to separation of functions also facilitates operational harmonization. The degree of harmonization is described for each plateau. An illustration for this is given below, where we start with standardization of ERTMS/EULYNX interfaces in Plateau 1, then IXL/RBC for Plateau 2 and finally full harmonization is achieved in Plateau 3 and 4.

Harmonization at each Plateau 23.3 KB View full-size Download

Long-term Goal of Migration- An integral approach:
  • An integral migration approach requires a long-term goal: as each step of migration has an influence on factors such as costs and time. The end result should be standardized systems (such as APS) that work in conjunction with national developments through standardized interfaces.
  • Milestone can be set, for example at 2030 (can be 2 or 4 years earlier or later). 
  • An illustration for this is given below. Here APS is standardized between each IM, while IXL/RBC systems, for example, should be able to operate with the APS through SCI-ILS interface . The path to this  depends on the objective and starting situation of each IM.
Integral Migration Approach 87.6 KB View full-size Download

Useful Documents/Deliverables:
Deliverables from RCA Gamma:
  1. RCA Migration 

For a more in-depth overview please click here

To go back please click here