The "Why": Facilitating Compatibility
The primary goal of RINF is to facilitate the verification of technical compatibility between the fixed subsystems (the network) and the vehicles (trains).
Before a vehicle uses a specific route, Railway Undertakings (RUs) must check that their train is technically capable of running safe on that infrastructure. Does it fit the gauge? Can it handle the voltage? Is it compatible with the signaling system?
RINF provides the data to answer these questions. It also assists RUs in building their Route Books, which are operational manuals for drivers.
Legal Basis
RINF is mandated by the Interoperability Directive. The specific rules are laid out in the RINF Regulation (EU) 2019/777, which has been amended by (EU) 2023/1694.
- Directive (EU) 2016/797: The foundation for interoperability within the EU.
- Impl. Reg. (EU) 2019/777: The common specifications for RINF.
- Impl. Reg. (EU) 2023/1694: The latest amendment introducing the semantic data model (Version 3.1.0).
Scope
RINF covers the data related to the "fixed" (non-mobile) subsystems of the railway system:
- Infrastructure (INF): Tracks, bridges, tunnels.
- Energy (ENE): Catenary systems, substations.
- Trackside Control-Command and Signalling (CCS): Balises, signals, level crossings.
It also includes data relevant to Telematics Applications for Passenger (TAP) and Freight (TAF) services.
Target Audience & Roles
Infrastructure Managers (IMs)
Responsible for collecting, maintaining, and publishing inaccurate/up-to-date data describing their network.
Railway Undertakings (RUs)
The consumers of the data. They use RINF to plan routes and check vehicle compatibility.
National Registration Entities (NREs)
They oversee the data submission process at a national level (though in many cases, IMs manage their data directly in the central RINF application).