TEL TSI - Technical
Go back to the main TEL TSI FAQs page.
APIs and web UIs for capacity management, train preparation, traffic management and freight wagon processes must comply with the Common Interface specification, TD104. Ticketing and passenger information follow the specifications of Annex section 4 instead. Several stakeholders may share one telematics application. Infrastructure managers must offer an API and web UIs for their network and, for multi-network processes, jointly use the common Union API and web UIs; for operators of rail freight service facilities and freight railway undertakings the common Union applications are optional (Article 14(4)–(6)).
Not necessarily. Data must use the semantics of the ERA Ontology subsets and the message sequences of TD100, but the serialisation format can be agreed between the parties. The XSD model of TD105 remains the reference for freight and operations messages.
Cybersecurity risk management under the NIS 2 and critical entities directives, a public key infrastructure according to TD106, and TCP/IP communication protocols (Annex 1.3). If you use shared data for the safety of operations, additional integrity and dependability levels are agreed between the parties and set out in your safety management system (Annex 1.1(3)).
A unique, stable identifier of the train (object type “TR”) set by the lead railway undertaking and used for the whole life cycle of the train across all networks, from path request to running information.
Where several RUs operate a direct service, they designate one of them (or another entity) to integrate the train identifiers, coordinate capacity requests, aggregate passenger timetable data, monitor wagons and share the consignment note. These tasks may be split between several undertakings (Article 13(2)). A single RU operating a service is its lead RU (Article 13(3)).