TAF/TSI Working Groups of relevance to Timetabling
Defines
the train ready and train composition messages.
Task:
Based on the requirements stated in the TAF TSI regulation, working group developed the business process description for Train Preparation process and defined and analysed the messages to support the information exchange during the whole process.
Project Status:
The WG has created two process descriptions for Train preparation process. One process is to be used in the open access mode, so if one RU is operating the train along the several IM networks and second process is reflecting the situation when several RUs are cooperating in train operation. Also the first analyses of content and structure of the related messages were made.
Task:
Based on the requirements stated in the TAF TSI regulation, working group developed the business process description for Train Preparation process and defined and analysed the messages to support the information exchange during the whole process.
Project Status:
The WG has created two process descriptions for Train preparation process. One process is to be used in the open access mode, so if one RU is operating the train along the several IM networks and second process is reflecting the situation when several RUs are cooperating in train operation. Also the first analyses of content and structure of the related messages were made.
→ WG 4 - Infrastructure restriction database
Will be a
reference database containing the existing infrastructure restrictions
on the network. It is not planned to use this source for
security-related issues.
Task:
Based on TAF/TSI regulation, an RU is obliged to take into account all restrictions in the Infrastructure Restriction Notice Database (IRNDB) affecting its train running until the pre-departure period. For this the IMs must install and fill-in IRNDBs. WG 4 “IRNDB” should secure that each country will produce their own system based on a common European approach.
Project status:
The ongoing project work showed that there are various open points and questions without clear answers. As they have an influence on several TSIs, the implementation of an IRNDB as it is foreseen by the TAF/TSI regulation is impossible. Governance bodies have to solve first all the open points.
Task:
Based on TAF/TSI regulation, an RU is obliged to take into account all restrictions in the Infrastructure Restriction Notice Database (IRNDB) affecting its train running until the pre-departure period. For this the IMs must install and fill-in IRNDBs. WG 4 “IRNDB” should secure that each country will produce their own system based on a common European approach.
Project status:
The ongoing project work showed that there are various open points and questions without clear answers. As they have an influence on several TSIs, the implementation of an IRNDB as it is foreseen by the TAF/TSI regulation is impossible. Governance bodies have to solve first all the open points.
→ WG 5 - Short-Term Path Request
Defines
the information flow between IMs and RUs for short-term path requests.
Task:
Due to exceptions during the train running or due to transport demands on a short-time basis, a railway undertaking must have the possibility to get an ad-hoc path on the network. According processes including detail descriptions for placing short term path requests as well as for cancellations and alterations of already contracted paths have to be developed. Even if the long-term planning of the timetables is out with the scope of TAF TSI, the WG has to clarify in addition if at some points there will be reference to the outcome of the long-term planning.
Project status:
The WG has created two processes, one for a full and one for a partial harmonisation by the IMs. These processes had been validated on company level (IM & RU members of the WG).
Task:
Due to exceptions during the train running or due to transport demands on a short-time basis, a railway undertaking must have the possibility to get an ad-hoc path on the network. According processes including detail descriptions for placing short term path requests as well as for cancellations and alterations of already contracted paths have to be developed. Even if the long-term planning of the timetables is out with the scope of TAF TSI, the WG has to clarify in addition if at some points there will be reference to the outcome of the long-term planning.
Project status:
The WG has created two processes, one for a full and one for a partial harmonisation by the IMs. These processes had been validated on company level (IM & RU members of the WG).