TEL TSI compliance for infrastructure managers
Commission Implementing Regulation (EU) 2026/253 places the widest set of digital obligations in the sector on infrastructure managers - from capacity allocation to publishing the working timetable. Here is exactly what your organisation must implement, and by when.
No credit card required · Role-traced IM obligations · PDF compliance report included
Your answers become an action plan
The readiness check is not a quiz that ends in a score. Every gap it finds becomes a task: the action to take, the article that requires it, and the deadline it must meet. Complete the tasks one by one and you are implementing TEL TSI - with progress you can show an auditor.
See your action plan - free →Reference data & location codes
Every deadline for infrastructure managers - counting down live
Every EU 2026/253 obligation for infrastructure managers, plus the ERA milestones, ticking down to the day.
See every TEL TSI obligation and deadline - dated, cited and in plain text →
The obligations only you carry - and the ones you share
Infrastructure managers sit at the centre of the TEL TSI data model. Some duties fall on IMs alone; others are shared telematics obligations that every stakeholder must meet.
IM-only obligations
These duties have no railway-undertaking equivalent. As the manager of the network, you are the single source of truth for locations, capacity and the timetable.
- ✓ Register and maintain Primary Location Codes for the whole network in the ERA Common Central Repository
- ✓ Integrate allocated paths into the working timetable and publish it publicly (CC BY-ND 4.0) via the common Union web UI
- ! Share network-specific data requirements with ERA under Art. 11(2) - an IM-only deadline of 2 December 2026
- ✓ Send IM-to-IM train running forecasts at cross-border handover points
- ✓ Provide passenger station managers with real-time deviation information
Obligations you share with RUs
These duties apply to every telematics stakeholder. As an IM you exchange this data with railway undertakings, adjacent IMs and facility operators.
- ✓ Process electronic path requests from lead and passenger RUs
- ✓ Send train running information at defined reporting points
- ✓ Exchange delay, disruption and interruption messages
- ✓ Connect to and operate through the Common Interface (CI)
- ✓ Secure all message exchange with PKI and the ERA ontology
- ✓ Maintain a historic data record and Article 5 public web UI access
The six workflows infrastructure managers must implement
These are the primary implementation areas for infrastructure managers under EU 2026/253. Each maps to specific Articles and Annexes of the regulation.
Reference data & location codes
IMs must create, maintain and register the Primary Location Codes for every reporting point on the network - departure, handover, interchange, intermediate and destination - in the ERA Common Central Repository before any message can reference them.
Capacity allocation & path requests
IMs receive PathRequestMessages from lead and passenger RUs and process them through the TEL TSI message sequence via standardised APIs or web UIs. Cross-border services require coordination with the adjacent infrastructure manager.
Working timetable publication
A publication obligation RUs do not have: integrate all allocated paths into a working timetable and make it publicly available under CC BY-ND 4.0 through the common Union web UI - plus share network-specific data requirements with ERA under Art. 11(2).
Train running information & forecast
IMs send train running information at defined reporting points and issue train running forecasts to RUs and, at cross-border handover, to the adjacent IM. This is the backbone of real-time operational data exchange under TEL TSI.
Passenger station information
Where cross-border passenger services call at stations on your network, IMs must feed the passenger station manager with real-time deviations so travellers receive accurate information - a duty unique to infrastructure managers.
Common Interface & secure exchange
All IM data flows must run through the TEL TSI Common Interface, secured with PKI and expressed through the ERA ontology. IMs must also maintain a historic data record and the Article 5 public web UI, and track ERA CCM schema changes on an ongoing basis.
Know your compliance gap in 30 minutes
The TEL TSI Compliance Companion walks your team through the full infrastructure-manager module set - with every question traced to the specific Article or Annex of EU 2026/253.
Confirm your IM scope
The assessment loads the infrastructure-manager module set - capacity, timetable, train running, passenger station information and more - filtered to your network's services.
Answer scenario questions
Work through scenario-based questions built around a real cross-border corridor. Each question cites its exact Article in EU 2026/253.
Get your action plan
Receive an instant score, module-by-module breakdown, and a prioritised action plan to close every gap before your applicable deadlines.
Download your PDF report
Export an audit-ready compliance report with every finding traced to regulation - shareable with your board, regulator, or ERA.
How the TEL TSI relates to the OPE TSI
Your network statement, train running information and traffic management duties connect to a second regulation: the OPE TSI (Commission Implementing Regulation (EU) 2019/773). Here is exactly how the two relate - and where the OPE TSI's own text still points the wrong way.
The TEL TSI formally interfaces with the OPE TSI - Appendix A.2 is a dedicated interface table. The OPE TSI does not return the favour: its interface chapter (point 4.3) lists infrastructure, control-command, rolling stock, energy, safety and noise, but no telematics. More strikingly, OPE point 4.2.3.4.2.1(c) still directs infrastructure managers to provide train-position-reporting data "according to Commission Regulation (EU) No 1305/2014 (TAF TSI) and Commission Regulation (EU) No 454/2011 (TAP TSI)" - the two TSIs the TEL TSI repealed and replaced. Read literally today, the OPE TSI's own cross-reference points at instruments that no longer describe the current telematics regime.
- Train ready for network access - the duty arises in OPE point 4.2.3.3.2; the TEL TSI TrainReadyMessage (Annex pt. 2.5.2) and readiness forecast (pt. 2.5.3) carry it.
- Train composition - the duty arises in OPE point 4.2.2.5.2; the TEL TSI TrainCompositionMessage (Annex pt. 2.5.1) carries it.
- Train running, forecast and delay - the duty arises in OPE points 4.2.3.4 (traffic management) and 4.2.3.4.2.1 (train position reporting); the TEL TSI TrainRunningInformationMessage, TrainRunningForecastMessage and delay-cause data (Annex pt. 2.6.3–2.6.5) carry it.
- Service disruption - the duty arises in OPE point 4.2.3.4; the TEL TSI TrainRunningInterruptionMessage (Annex pt. 2.6.6) carries it.
The TEL TSI governs the data exchange. The operational duty itself sits in the OPE TSI and is demonstrated through your Safety Management System when you apply for a safety certificate or safety authorisation - the OPE TSI has no interoperability constituents (OPE point 5.2) and none of its requirements is assessed by a Notified Body (OPE point 6.2.1). This tool does not assess OPE TSI compliance.
Full analysis: The OPE TSI still points to TAF and TAP. Here's what replaced them. →
Quick answer: Does this tool assess our OPE TSI compliance? →
TEL TSI questions from infrastructure manager teams
What does TEL TSI require from infrastructure managers?
Under EU 2026/253, infrastructure managers must process electronic path requests, publish the working timetable via the common Union web UI, send train running information and forecasts to RUs and adjacent IMs, feed passenger station managers with real-time deviations, and register Primary Location Codes for the whole network in the ERA Common Central Repository. IMs also carry the Article 11(2) duty to share network-specific data requirements with ERA - an obligation with no RU equivalent.
Which obligations are unique to infrastructure managers?
Registering and maintaining Primary Location Codes for the network, producing and publicly publishing the working timetable under CC BY-ND 4.0, sharing network-specific data requirements with ERA (Art. 11(2)), IM-to-IM train running forecasts at cross-border handovers, and passenger station manager information are all IM-only duties. Railway undertakings do not carry them.
When do the TEL TSI deadlines fall for an infrastructure manager?
The ERA CCM process applies from 2 September 2026; the IM-only Art. 11(2) data-requirements duty from 2 December 2026; common reference data from 13 December 2026; the IM implementation report to ERA from 2 September 2027; passenger train running and forecast information from 10 December 2028; and full Common Interface deployment for freight train traffic, composition and train-ready messages from 9 December 2029.
How does an IM's role relate to railway undertakings under TEL TSI?
Infrastructure managers are the counterpart to railway undertakings in almost every TEL TSI workflow: IMs receive path requests from freight RUs and passenger RUs, return capacity and timetable data, and exchange train running information throughout the journey. Getting your IM data model right depends on understanding the RU obligations on the other side of each message.
Does the TEL TSI Compliance Companion cover infrastructure-manager workflows?
Yes. The tool includes a dedicated infrastructure-manager module set covering capacity allocation, the working timetable, train running information, IM-to-IM handover, passenger station information, PKI and secure exchange, and CCM governance - each traced to the relevant Article of EU 2026/253. The Team plan supports collaborative workspaces for larger IM compliance teams.
Does this tool assess our OPE TSI compliance?
No - and the distinction matters more than it might first appear. The TEL TSI (Reg. (EU) 2026/253) governs the data exchange: the messages you send and receive for train composition, train readiness, train running, forecasts and interruptions. That is what this tool assesses. The operational obligations behind those same facts arise in the OPE TSI (Reg. (EU) 2019/773). For example, it is OPE - not the TEL TSI - that requires the railway undertaking to inform the infrastructure manager when a train is ready for access to the network (OPE point 4.2.3.3.2). The TEL TSI then specifies the TrainReadyMessage that carries that information. A useful way to hold it: OPE creates the duty; the TEL TSI carries the message that implements it. The two are also demonstrated by completely different routes. The OPE TSI is a functional subsystem: it has no interoperability constituents (OPE point 5.2), and none of its requirements is assessed by a Notified Body. Instead, railway undertakings and infrastructure managers demonstrate OPE compliance within their Safety Management System, when applying for a safety certificate or safety authorisation (OPE point 6.2.1). So a strong result here means you are ready to exchange the data the TEL TSI requires. It does not mean - and cannot mean - that your OPE obligations are met. Those belong in your SMS. Sources: Commission Implementing Regulation (EU) 2019/773 (consolidated), points 4.2.3.3.2, 5.2, 6.2.1; Commission Implementing Regulation (EU) 2026/253.
Check your network's TEL TSI readiness - free
30 minutes, scenario-based, built around the infrastructure-manager module set. Get your action plan and PDF report today.
Start free - no card requiredQuestions?
TSI Solution GmbH checked this content against the Official Journal text on .