Telematic Applications for Freight - TAF TSI

On 23 December 2005 the European Commission published the TAF Regulation (Telematic Applications for Freight) – the first IT-related TSI* (Technical Specification for Interoperability). National implementation has to be completed by 2014. Most member states have delivered a national deployment plan which was aggregated to the SEDP (Strategic European Deployment Plan). This national commitment was the basis for the original TAF TSI implementation timeline.

The aim of the TAF TSI is to define the data exchange between Infrastructure Managers (IMs) and Railway Undertakings (RUs) and between the members of these two groups. But the TAF TSI itself is not ready to be implemented by the rail industry, which needs to review some parts of it. Then it will be possible to modify the original timeline and some parts of the TAF TSI. This work is being done within the TAF TSI Working Groups, which are part of the TAF TSI implementation project.

In addition to IT issues, the TAF TSI describes business processes involving IMs and RUs. For this reason the TAF TSI could have a deep impact on the existing international rail infrastructure business processes as well. The TAF, or at least the IT interfaces with other partners, must be implemented in a similar way by all TAF TSI partners, including the IMs.

As it was the IMs’ aim to co-ordinate the international implementation of the TAF TSI, RNE was mandated by its members to carry out this task during the TAF TSI development phase. This includes the management of the TAF TSI IM Cluster, which represents IMs in the project, and the joint cluster Working Groups (WG), which were set up and defined together with the TAF TSI RU Cluster. In this way, it was possible to use the RNE business process for Timetabling and Operations as the basis for the TAF TSI processes. The TAF TSI project organisation and the mapping with the RNE WGs are presented in the graph below.
It must be stressed that most of the work required to implement the TAF TSI must be done by the rail industry itself – the WGs will define the detailed, internationally-agreed specifications for the TAF TSI functions. Therefore national action will be necessary to develop the agreed specifications for the national IT systems. Most of the WG’s are in the final phase or have already finalized their work. The WG’s have developed the detailed coding for the specific messages and an implementation guide. These two documents should ensure that the company's developments will fit together. It is planned to agree on the results, after a company endorsement phase on the TAF TSI IM/RU Cluster on the 14th April 2011.  

TAF TSI Project Organisation:

TAF TSI - Project Organisation

These functions, reviewed by the Working Groups (WGs), require to define

  • When (at which point in a specific process)
  • What (which kind of information and content ) has to be sent to
  • Whom (partner or partners) and
  • How (which format) the data must be exchanged between the partners.

The various IM-related TAF TSI functions which are covered by WGs are:
→ WG 1 - Reference Files (click for details)
→ WG 2 - Train run information
→ WG 3 - Train preparation
→ WG 4 - Infrastructure restriction database
→ WG 5 - Short-Term Path Request
→ WG 10 - Train Transport ID

Telematic Applications for Passenger Services - TAP TSI

Furthermore the IMs have proposed that the TAP (Telematic Applications for Passenger Services) TSI should match the above-mentioned functions of the TAF TSI as much as possible. Therefore the RNE and TAF TSI WG leaders have checked the TAP TSI. Until now, besides new functions such as the station manager, no major differences with the TAF TSI have been detected.