A “virtual” train journey for automation applications requires a “digital” rail network. In particular, systems in specific applications such as TMS, ETCS or ATO only function properly with precise data on the operational infrastructure. In general, precise digital infrastructure data is also central to planning, construction and operation. Depending on the application, different levels of detail and properties of the infrastructure are required (topology, topography, operational, geometry). Interlockings and control technology require logical connections for the control logic without topographical information. However, modern TMS systems, ETCS and ATO require certain topographical and operational information about the infrastructure, such as gradient profiles or permissible speed profiles with positions on the line. This is also known as a digital map and, in the case of a comprehensive and detailed image of the real infrastructure, a digital twin.
Depending on the application, there are different requirements for the safety and integrity of the data. Data for TMS and ATO is not safety-critical. However, the project planning data for an interlocking or for ETCS (e.g. route atlas in the RBC or rigid telegrams in Eurobalises or LEUs) must be recorded with a quality and integrity for SIL4 applications. Therefore, the requirements for validating the data are also higher. However, it is possible to generate “safe” project planning data for SIL applications from “non-safe” topology data through validations and checks. Conversely, the safe topology for the RBC route atlas can be used as the basis for topologies for TMS/ATO and enriched with non-safety-critical data.
At the topology level, efficient, high-quality data management is required to capture the necessary data. It is crucial how topology data and its databases are integrated into the IT system landscape of railway operations. Without topology data, there can be no digitalisation and automation of rail operations.
A migration towards digitalisation and automation therefore requires a well-thought-out concept for data management and the collection of topology data, including the differentiation between safety-critical and non-safety-critical data. The Enotrac team can provide you with expertise and support in the design of the topology, project planning rules (generic basic structure of the model), data project planning (specifics), verification and overall data management.
Enotrac offers extensive expertise in infrastructure data and data models required for ETCS (L1LS and L2 with RBC route atlas) and ATO (trackside), particularly based on the specifications that define the ERTMS data exchange language for communication with the onboard unit (OBU): Subset 026 for ETCS and Subset 126 for ATO.
