Commission Regulation (EU) No 1305/2014 of 11 December 2014 on the technical specification for interoperability relating to the telematics applications for freight subsystem of the rail system in the European Union and repealing the Regulation (EC) No 62/2006 Text with EEA relevance
Modified by
- Commission Implementing Regulation (EU) 2018/278of 23 February 2018amending the Annex to Regulation (EU) No 1305/2014 as regards the structure of the messages, data and message model, Wagon and Intermodal Unit Operating Database, and to adopt an IT standard for the communication layer of the Common Interface, 32018R0278, February 24, 2018
- Commission Implementing Regulation (EU) 2019/778of 16 May 2019amending Regulation (EU) No 1305/2014 as regards Change Control Management(Text with EEA relevance), 32019R0778, May 27, 2019
(a) the trans-European conventional rail system network as defined in Annex I, Section 1.1 of Directive 2008/57/EC; (b) the trans-European high-speed rail system network as defined in Annex I, Section 2.1 of Directive 2008/57/EC; (c) other parts of the network of the rail system in the Union.
| Abbreviation | Definition |
|---|---|
| ANSI | American National Standards Institute |
| CI | Common Interface |
| CR | Change Request |
| EC | European Commission |
| ERA | European Railway Agency (also referred to as Agency) |
| ERTMS | European Rail Traffic Management System |
| ETCS | European Train Control System |
| IM | Infrastructure Manager |
| ISO | International Organisation for Standardisation |
| LAN | Local Area Network |
| LCL | Less than Container Loads |
| LRU | Lead Railway Undertaking |
| ONC | Open Network Computing |
| OTIF | Intergovernmental Organisation for International Carriage by Rail |
| PVC | Permanent Virtual Circuit |
| RISC | Rail Interoperability and Safety Committee |
| RU | Railway Undertaking |
| TAF | Telematics Applications for Freight |
| TAP | Telematics Applications for Passengers |
| TCP/IP | Transmission Control Protocol/Internet Protocol |
| TEN | Trans European Network |
| TSI | Technical Specification for Interoperability |
| WK | Wagon Keepers |
| WP | Working Party organised by ERA |
| Ref. No | Document Reference | Title | Last Issue |
|---|---|---|---|
| (1) | Directive 2008/57/EC | Directive 2008/57/EC of the European Parliament and of the Council of | |
| (2) | TAP TSI Regulation (EU) No 454/2011 | Commission Regulation (EU) No 454/2011 of | |
| (3) | Directive 2012/34/EU | Directive 2012/34/EU of the European Parliament and of the Council of | |
| (4) | ERA-TD-105 | TAF TSI — ANNEX D.2: APPENDIX F — TAF TSI DATA AND MESSAGE MODEL. | |
| (5) | TAF TSI Regulation No 62/2006 | Commission Regulation (EC) No 62/2006 of | |
| (6) | Commission Regulation (EU) No 280/2013 | Commission Regulation (EU) No 280/2013 of | |
| (7) | Commission Regulation (EU) No 328/2012 | Commission Regulation (EU) No 328/2012 of | |
| (8) | C(2010)2576 final | Commission Decision of | |
| (9) | Directive 2004/49/EC | Directive 2004/49/EC of the European Parliament and of the Council of | |
| (10) | Directive 2001/13/EC | Directive 2001/13/EC of the European Parliament and of the Council of |
the trans-European conventional rail system network (TEN) as described in Annex I Section 1.1 "Network" of Directive 2008/57/EC (1), the trans-European high-speed rail system network (TEN) as described in Annex I Section 2.1 "Network" of Directive 2008/57/EC (1), other parts of the network of the whole rail system, following the extension of scope as described in Annex I Section 4 of Directive 2008/57/EC (1).
applications for freight services, including information systems (real-time monitoring of freight and trains), marshalling and allocation systems, whereby under allocation systems is understood train composition, reservation systems, whereby here is understood the train path reservation, management of connections with other modes of transport and production of electronic accompanying documents.
Wagons Locomotives Drivers Switching and Hump shunting Slot selling Shipment management Train composition Train Operation Train monitoring Train controlling Shipment monitoring Inspections & Repair of Wagon and/or Locomotive Customs clearance Operating Intermodal Terminals Haulage management
Infrastructure Manager (IM) (Directive 2012/34/EU (3)) means any body or firm responsible in particular for establishing, managing and maintaining railway infrastructure, including traffic management and control-command and signalling; the functions of the infrastructure manager on a network or part of a network may be allocated to different bodies or firms. Where the infrastructure manager, in its legal form, organisation or decision-making functions, is not independent of any railway undertaking, the functions referred to in Sections 2 and 3 of Chapter IV shall be performed respectively by a charging body and by an allocation body that are independent in their legal form, organisation and decision-making from any railway undertaking; Based on this definition, this TSI regards an IM as the service provider for the allocation of paths, for controlling/monitoring the trains and for train/path related reporting. Applicant (Directive 2012/34/EU (3)) means a railway undertaking or an international grouping of railway undertakings or other persons or legal entities, such as competent authorities under Regulation (EC) No 1370/2007 and shippers, freight forwarders and combined transport operators, with a public-service or commercial interest in procuring infrastructure capacity; Railway Undertaking (Directive 2004/49/EC (9)) means railway undertaking as defined in Directive 2001/14/EC, and any other public or private undertaking, the activity of which is to provide transport of goods and/or passengers by rail on the basis that the undertaking must ensure traction; this also includes undertakings which provide traction only;. Based on this definition, this TSI regards the RU as the service provider for operating trains.
Path information. Train Running Information on agreed reporting points, including at least departure, interchange/handover and arrival points of the contracted transport. Estimated Time of Arrival (ETA) to the final destination including yards and intermodal terminals. Service Disruption. When the Lead RU learns about a service disruption, it shall deliver to the Customer in due time.
DEFINING: services in terms of price and transit times, wagon supply (where applicable), wagon/Intermodal unit information (location, status and the wagon/Intermodal unit related estimated time of arrival "ETA"), where shipments can be loaded on empty wagons, containers etc., DELIVERING: the service that has been defined in a reliable, seamless manner through the use of common business processes and linked systems. There must be a capability for RUs, IMs and other service providers and stakeholders such as customs to exchange information electronically, MEASURING: the quality of the service delivered compared to what was defined. i.e. billing accuracy against price quoted, actual transit times against commitments, wagon ordered against supplied, ETAs against actual arrival times, OPERATING: in a productive manner in terms of utilisation: train, infrastructure and fleet capacity through the use of business processes, systems and data exchange required to support wagon/Intermodal unit and train scheduling.
when the wagons departed from or arrived at a yard or at defined locations (Chapter 4.2.7 Wagon Movement), when the responsibility for the wagons was transferred from one RU to the next RU in the transport chain (Chapter 4.2.8 Interchange Reporting).
for — in the medium term — planning the production process in greater detail, and for — in the long term — carrying out strategic planning exercises and capacity studies (e.g. network analyses, definition of siding and marshalling yards, rolling stock planning), but above all for improving the quality of the transport service and productivity (Chapter 4.2.9 Data Exchange for Quality Improvement).
Identification of rolling stock, Technical/design data, Assessment of compatibility with the infrastructure, Assessment of relevant loading characteristics, Brake relevant characteristics, Maintenance data, Environmental characteristics.
the interface to the subsystem Operation and Traffic Management referred to in Article 5(3) of Directive 2008/57/EC (1), the requirements for the content of the Network Statement, which are set out in Directive 2012/34/EU (3), Article 27 and Annex IV, the information available on the freight wagon rolling stock and the requirements regarding maintenance from the Rolling Stock TSI.
Safety, Reliability and Availability, Health, Environmental protection, Technical compatibility.
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
that the databases, software and data communication protocols are developed in a manner allowing maximum data interchange between different applications and operators, excluding confidential commercial data, easy access to the information for users."
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
Consignment Note data, Path Request, Train Preparation, Train Running Forecast, Service Disruption Information, Wagon/Intermodal unit ETI/ETA, Wagon Movement, Interchange Reporting, Data Exchange for Quality Improvement, The Main Reference Data, Various Reference Files and Databases, Networking & Communication.
Consignor and consignee information, Routing information, Consignment identification, Wagon information, Place and time information.
Load weight (Gross weight of the load), CN/HS Number, Dangerous goods information, Transportation unit.
Departure from departure point, arrival at destination, Arrival and departure at handover points, interchange points and at agreed reporting points based on contract (e.g. handling points).
Wagon Release notice Wagon Departure notice Wagon Yard arrival Wagon Yard departure Wagon Exceptions message Wagon Arrival notice Wagon Delivery notice Wagon Interchange reporting, will be described separately in Chapter 4.2.8: Interchange Reporting
Wagon Interchange Notice, Wagon Interchange Sub Notice, Wagon Received At Interchange, Wagon Refused At Interchange.
Identification of rolling stock, Assessment of the compatibility with the infrastructure, Assessment of relevant loading characteristics, Brake relevant characteristics, Maintenance data, Environmental characteristics.
Administrative data, related to certification and registration items such as reference to the EC registration file, id of the notified body, etc.; this may include historical data related to ownership, rental, etc. Additionally, according to Commission Regulation EU 445/2011, article 5, the Wagon Keepers may store the ECM certification identification number in the individual Rolling Stock Reference Databases. The following steps have to be taken into account: EC certification, Registration in the "home" State, Date put into service in the state of registration, Registration in other countries for the use on their national network, Safety certification for all Rolling Stock which does not comply with the Rolling Stock TSI.
The keeper is obliged to ensure that these data are available and the processes behind have been conducted. Design data, which shall include all constitutive (physical) elements of the rolling stock, including characteristics related to the environment, and all information that is expected to remain valid throughout the life of the rolling stock — this part may contain a history of major modifications, major maintenance, overhaul, etc.
Railway Undertaking as Duty holder during its transport control, Keeper of rolling stock, and User (Hirer) of rolling stock.
(a) Reference File of the emergency services, correlated to type of hazardous goods.
(b) Reference File of the Coding for all IMs, RUs, Service provider companies; (c) Reference File of the Coding for Freight Transport Customers; (d) Reference File of the Coding of Locations (Primary and subsidiary),
Wagon and Intermodal Unit Operational Database, Trip plan for wagon/Intermodal unit.
Status: loading of the rolling stock This status is required for the information exchange between the RU and the IMs and to other railway undertakings involved in the transport journey. Status: loaded wagon on journey This status is required for the information exchange between the IM and the RU, with other infrastructure managers and with other railway undertakings involved in the transport journey. Status: empty wagon on journey This status is required for the information exchange between the IM and the RU, with other infrastructure managers and railway undertakings involved in the transport journey. Status: unloading of rolling stock This status is required for the information exchange between the RU at destination and the Lead RU for the transport. Status: empty wagon under fleet management control This status is required to get the information about availability of a vehicle of defined characteristics.
1. Authentication A database must support the authentication of users of the systems before they can gain access to the database. 2. Security A database must support the security aspects in the meaning of controlling access to the database. The possible encryption of the database contents itself is not required. 3. Consistency A database selected shall support the ACID principle (Atomicity, Consistency, Isolation and Durability). 4. Access Control A database must allow access to the data to users or systems that have been granted permission. The access control shall be supported down to a single attribute of a data record. The database shall support configurable, role based access control for insertion, update or deletion of data records. 5. Tracing A database must support logging all actions applied to the database to allow for tracing the detail of the data entry (Who, What, When did the contents change). 6. Lock strategy A database must implement a locking strategy which allows access to the data even when other users are currently editing records. 7. Multiple access A database must support that data can be accessed simultaneously by several users and systems. 8. Reliability The reliability of a database must support the required availability. 9. Availability A database must have an availability on demand of at least 99,9 %. 10. Maintainability A maintainability of the database must support the required availability. 11. Safety Databases themselves are not safety-related. Hence safety aspects are not relevant. This is not to be confused with the fact that the data — e.g. wrong or not actual data — may have impact on the safe operation of a train. 12. Compatibility A database must support a data manipulation language that is widely accepted, such as SQL or XQL. 13. Import facility A database shall provide a facility that allows the import of formatted data that can be used to fill the database instead of manual input. 14. Export facility A database shall provide a facility that allows to export the contents of the complete database or its part as formatted data. 15. Mandatory Fields A database must support mandatory fields that are required to be filled before the relevant record is accepted as input to the database. 16. Plausibility Checks A database must support configurable plausibility checks before accepting the insertion, update or deletion of data records. 17. Response times A database must have response times that allow users to insert, update or delete data records in a timely manner. 18. Performance aspects The reference files and databases shall support in a cost effective manner the queries necessary to allow the effective operation of all relevant train runs and wagon movements that are covered by the provisions of this TSI. 19. Capacity aspects A database shall support the storage of the relevant data for all freight wagons respectively the network. It shall be possible to extend the capacity by simple means (i.e. by adding more storage capacity and computers). The extension of the capacity shall not require replacement of the subsystem. 20. Historical data A database shall support the management of historical data in the meaning of making of data available that has been already transferred into an archive. 21. Back-up strategy A back-up strategy shall be in place to ensure that the complete database contents for up to a 24 hour period can be recovered. 22. Commercial aspects A database system used shall be available commercially off-the-shelf (COTS-product) or be available in the public domain (Open Source).
is designed to reconcile heterogeneous information models by semantically transforming the data that is exchanged between the systems and by reconciling the business process and application-level protocol differences, has minimum impact on the existing IT architectures implemented by every actor, safeguards IT investments made already.
metadata — structured data describing the content of messages, Public Key Infrastructure (PKI), Certification Authority (CA),
message formatting of outgoing messages according to the metadata, signing and encryption of outgoing messages, addressing of the outgoing messages, authenticity verification of the incoming messages, decryption of incoming messages, conformity checks of incoming messages according to metadata, handling the single common access to various databases.
(i) positive send ACK; (ii) negative send NACK.
Path contract, where within the line segment description the relevant information about usable command control and signalling equipment is given, and various Rolling Sock Reference Databases, where the command control and signalling equipment of the rolling stock must be stored.
| Interface | Reference Telematics Applications for Freight TSI | Reference Telematics Applications for passengers TSI |
|---|---|---|
| Train ready | ||
| Train running forecast | ||
| Train running information | ||
| Train running interrupted to RU | ||
| Handling of short term timetable data | ||
| Common Interface | ||
| Central Repository | ||
| Reference Files |
are Error free: accessible, accurate, timely, complete, consistent with other sources, etc., and possess desired features: relevant, comprehensive, proper level of detail, easy-to-read, easy-to-interpret, etc.
Accuracy, Completeness, Consistency, Timeliness.
The central repository also contains the certification authority (Open CA PKI). This is mainly an administration act, which is physically implemented. Wrong entries become obvious immediately. No assessment procedure needed. The central repository contains the message metadata (according to document "TAF TSI — Annex D.2: Appendix F — TAF TSI Data and Message Model", listed in Appendix I) as the basis for message exchange in a heterogeneous information environment. The metadata must be administrated and updated in the central repository. Any incompatibility in the message structure or content of the messages for sending or receiving data will be recognised immediately and the transfer will be refused. No assessment procedure needed. The common interface at each actor's node contains mainly the local "mirror" of the central repository for shortening the response time and reducing the load on the repository. It must be ensured, that the data versions in the central repository and in the common interface are always the same. Therefore the data update must be done on the central level and new versions must be downloaded from there. No assessment procedure needed.
phase one: detailed IT specifications and master plan; phase two: development; phase three: deployment.
1. The Steering Committee shall be composed of: the representative bodies from the railway sector acting on a European level as defined in Article 3(2) of Regulation (EC) No 881/2004 ("the rail sector representative bodies"), the European Railway Agency, and the Commission.
2. This Steering Committee shall be co-chaired by (a) the Commission and (b) a person nominated by the rail sector representative bodies. The Commission assisted by the members of the steering committee shall draft the rules of procedure of this Steering Committee, on which the steering committee shall agree. 3. The members of the Steering Committee may propose to the Steering Committee that other organisations be included as observers where there are sound technical and organisational reasons for doing so.
provide the necessary efforts and resources needed for the implementation of this Regulation, comply with the principles of access to the TAF TSI common components which shall be available to all market participants at a unified, transparent and lowest possible service cost structure, ensure that all market participants have access to all data exchanged required for fulfilling their legal obligations and for the performance of their functions in accordance with the TAF TSI functional requirements, protect the confidentiality of customer relationships, set-up a mechanism which will enable "late comers" to join the TAF development and to profit from achieved TAF developments related to the common components in a way which is satisfactory both for above stakeholders and for the "new comers" in particular with view to fair cost sharing, report of progress with implementation plans to the TAF Steering Committee. This reporting includes also — where appropriate — deviations from the master plan.
represent their individual stakeholder members at the TAF-TSI Steering Committee, raise awareness of their members on their obligations related to the implementation of the present regulation, ensure current and complete access for all above stakeholders to status information on the work of the Steering Committee and any other groups in order to safeguard each representative's interests in the implementation of TAF-TSI in a timely manner, ensure the efficient information flow from their individual stakeholder members to the TAF Steering Committee so that the stakeholders' interest is duly taken into account for decisions affecting the TAF development and deployment, ensure the efficient information flow from the TAF Steering Committee to their individual stakeholder members so that the stakeholders are duly informed about decisions affecting the TAF development and deployment.
the identification of the technical constraints underpinning the change, a statement of who takes responsibility for the change implementation procedures, the procedure for validating the changes to be implemented, the policy for change management, release, migration and roll-out, the definition of the responsibilities for the management of the detailed specifications and for both its quality assurance and configuration management.
1. The change requests affecting the documents are submitted either via the Member States or via the representative bodies from the railway sector acting on a European level as defined in Article 38(4) of Regulation (EU) 2016/796 of the European Parliament and of the Council Regulation (EU) 2016/796 of the European Parliament and of the Council of 11 May 2016 on the European Union Agency for Railways and repealing Regulation (EC) No 881/2004 (OJ L 138, 26.5.2016, p. 1 ).2. The Agency shall gather and store the change requests. 3. The Agency shall present the change requests to the dedicated ERA working party, which will evaluate them and prepare a proposal accompanied by an economic evaluation, where appropriate. 4. Afterwards the Agency shall present each change request and the associated proposal to the change control board that will or will not validate or postpone the change request. 5. If the change request is not validated, the Agency shall send back to the requester either the reason for the rejection or a request for additional information about the draft change request. 6. If the change request is validated, the technical document shall be amended. 7. If no consensus about the validation of a change request can be reached, the Agency shall submit to the Commission a recommendation to update the documents listed in Appendix I together with the draft new version of the document, the change requests and their economic evaluation and shall make these documents available on their web site. 8. The new version of the technical document with the validated change requests shall be made available at the site of the Agency. The Agency will keep the Member States informed via the Committee established in accordance with Article 29(1) of Directive 2008/57/EC. 9. If a change request would require a change of the legal text of the TAF TSI, the Agency shall send a request to the European commission to request a revision of the TAF TSI and/or request the technical opinion from the Agency.
(a) the trans-European conventional rail system network as defined in Annex I, Section 1.1 of Directive 2008/57/EC; (b) the trans-European high-speed rail system network as defined in Annex I, Section 2.1 of Directive 2008/57/EC; (c) other parts of the network of the rail system in the Union.
| Abbreviation | Definition |
|---|---|
| ANSI | American National Standards Institute |
| CI | Common Interface |
| CR | Change Request |
| EC | European Commission |
| ERA | European Railway Agency (also referred to as Agency) |
| ERTMS | European Rail Traffic Management System |
| ETCS | European Train Control System |
| IM | Infrastructure Manager |
| ISO | International Organisation for Standardisation |
| LAN | Local Area Network |
| LCL | Less than Container Loads |
| LRU | Lead Railway Undertaking |
| ONC | Open Network Computing |
| OTIF | Intergovernmental Organisation for International Carriage by Rail |
| PVC | Permanent Virtual Circuit |
| RISC | Rail Interoperability and Safety Committee |
| RU | Railway Undertaking |
| TAF | Telematics Applications for Freight |
| TAP | Telematics Applications for Passengers |
| TCP/IP | Transmission Control Protocol/Internet Protocol |
| TEN | Trans European Network |
| TSI | Technical Specification for Interoperability |
| WK | Wagon Keepers |
| WP | Working Party organised by ERA |
| Ref. No | Document Reference | Title | Last Issue |
|---|---|---|---|
| (1) | Directive 2008/57/EC | Directive 2008/57/EC of the European Parliament and of the Council of | |
| (2) | TAP TSI Regulation (EU) No 454/2011 | Commission Regulation (EU) No 454/2011 of | |
| (3) | Directive 2012/34/EU | Directive 2012/34/EU of the European Parliament and of the Council of | |
| (4) | ERA-TD-105 | TAF TSI — ANNEX D.2: APPENDIX F — TAF TSI DATA AND MESSAGE MODEL. | |
| (5) | TAF TSI Regulation No 62/2006 | Commission Regulation (EC) No 62/2006 of | |
| (6) | Commission Regulation (EU) No 280/2013 | Commission Regulation (EU) No 280/2013 of | |
| (7) | Commission Regulation (EU) No 328/2012 | Commission Regulation (EU) No 328/2012 of | |
| (8) | C(2010)2576 final | Commission Decision of | |
| (9) | Directive 2004/49/EC | Directive 2004/49/EC of the European Parliament and of the Council of | |
| (10) | Directive 2001/13/EC | Directive 2001/13/EC of the European Parliament and of the Council of |
the trans-European conventional rail system network (TEN) as described in Annex I Section 1.1 "Network" of Directive 2008/57/EC (1), the trans-European high-speed rail system network (TEN) as described in Annex I Section 2.1 "Network" of Directive 2008/57/EC (1), other parts of the network of the whole rail system, following the extension of scope as described in Annex I Section 4 of Directive 2008/57/EC (1).
applications for freight services, including information systems (real-time monitoring of freight and trains), marshalling and allocation systems, whereby under allocation systems is understood train composition, reservation systems, whereby here is understood the train path reservation, management of connections with other modes of transport and production of electronic accompanying documents.
Wagons Locomotives Drivers Switching and Hump shunting Slot selling Shipment management Train composition Train Operation Train monitoring Train controlling Shipment monitoring Inspections & Repair of Wagon and/or Locomotive Customs clearance Operating Intermodal Terminals Haulage management
Infrastructure Manager (IM) (Directive 2012/34/EU (3)) means any body or firm responsible in particular for establishing, managing and maintaining railway infrastructure, including traffic management and control-command and signalling; the functions of the infrastructure manager on a network or part of a network may be allocated to different bodies or firms. Where the infrastructure manager, in its legal form, organisation or decision-making functions, is not independent of any railway undertaking, the functions referred to in Sections 2 and 3 of Chapter IV shall be performed respectively by a charging body and by an allocation body that are independent in their legal form, organisation and decision-making from any railway undertaking; Based on this definition, this TSI regards an IM as the service provider for the allocation of paths, for controlling/monitoring the trains and for train/path related reporting. Applicant (Directive 2012/34/EU (3)) means a railway undertaking or an international grouping of railway undertakings or other persons or legal entities, such as competent authorities under Regulation (EC) No 1370/2007 and shippers, freight forwarders and combined transport operators, with a public-service or commercial interest in procuring infrastructure capacity; Railway Undertaking (Directive 2004/49/EC (9)) means railway undertaking as defined in Directive 2001/14/EC, and any other public or private undertaking, the activity of which is to provide transport of goods and/or passengers by rail on the basis that the undertaking must ensure traction; this also includes undertakings which provide traction only;. Based on this definition, this TSI regards the RU as the service provider for operating trains.
Path information. Train Running Information on agreed reporting points, including at least departure, interchange/handover and arrival points of the contracted transport. Estimated Time of Arrival (ETA) to the final destination including yards and intermodal terminals. Service Disruption. When the Lead RU learns about a service disruption, it shall deliver to the Customer in due time.
DEFINING: services in terms of price and transit times, wagon supply (where applicable), wagon/Intermodal unit information (location, status and the wagon/Intermodal unit related estimated time of arrival "ETA"), where shipments can be loaded on empty wagons, containers etc., DELIVERING: the service that has been defined in a reliable, seamless manner through the use of common business processes and linked systems. There must be a capability for RUs, IMs and other service providers and stakeholders such as customs to exchange information electronically, MEASURING: the quality of the service delivered compared to what was defined. i.e. billing accuracy against price quoted, actual transit times against commitments, wagon ordered against supplied, ETAs against actual arrival times, OPERATING: in a productive manner in terms of utilisation: train, infrastructure and fleet capacity through the use of business processes, systems and data exchange required to support wagon/Intermodal unit and train scheduling.
when the wagons departed from or arrived at a yard or at defined locations (Chapter 4.2.7 Wagon Movement), when the responsibility for the wagons was transferred from one RU to the next RU in the transport chain (Chapter 4.2.8 Interchange Reporting).
for — in the medium term — planning the production process in greater detail, and for — in the long term — carrying out strategic planning exercises and capacity studies (e.g. network analyses, definition of siding and marshalling yards, rolling stock planning), but above all for improving the quality of the transport service and productivity (Chapter 4.2.9 Data Exchange for Quality Improvement).
Identification of rolling stock, Technical/design data, Assessment of compatibility with the infrastructure, Assessment of relevant loading characteristics, Brake relevant characteristics, Maintenance data, Environmental characteristics.
the interface to the subsystem Operation and Traffic Management referred to in Article 5(3) of Directive 2008/57/EC (1), the requirements for the content of the Network Statement, which are set out in Directive 2012/34/EU (3), Article 27 and Annex IV, the information available on the freight wagon rolling stock and the requirements regarding maintenance from the Rolling Stock TSI.
Safety, Reliability and Availability, Health, Environmental protection, Technical compatibility.
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
that the databases, software and data communication protocols are developed in a manner allowing maximum data interchange between different applications and operators, excluding confidential commercial data, easy access to the information for users."
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
Chapter 4.2.10: The Main Reference Data, Chapter 4.2.11: Various Reference Files and Databases, Chapter 4.2.12: Networking & Communication.
Consignment Note data, Path Request, Train Preparation, Train Running Forecast, Service Disruption Information, Wagon/Intermodal unit ETI/ETA, Wagon Movement, Interchange Reporting, Data Exchange for Quality Improvement, The Main Reference Data, Various Reference Files and Databases, Networking & Communication.
Consignor and consignee information, Routing information, Consignment identification, Wagon information, Place and time information.
Load weight (Gross weight of the load), CN/HS Number, Dangerous goods information, Transportation unit.
Departure from departure point, arrival at destination, Arrival and departure at handover points, interchange points and at agreed reporting points based on contract (e.g. handling points).
Wagon Release notice Wagon Departure notice Wagon Yard arrival Wagon Yard departure Wagon Exceptions message Wagon Arrival notice Wagon Delivery notice Wagon Interchange reporting, will be described separately in Chapter 4.2.8: Interchange Reporting
Wagon Interchange Notice, Wagon Interchange Sub Notice, Wagon Received At Interchange, Wagon Refused At Interchange.
Identification of rolling stock, Assessment of the compatibility with the infrastructure, Assessment of relevant loading characteristics, Brake relevant characteristics, Maintenance data, Environmental characteristics.
Administrative data, related to certification and registration items such as reference to the EC registration file, id of the notified body, etc.; this may include historical data related to ownership, rental, etc. Additionally, according to Commission Regulation EU 445/2011, article 5, the Wagon Keepers may store the ECM certification identification number in the individual Rolling Stock Reference Databases. The following steps have to be taken into account: EC certification, Registration in the "home" State, Date put into service in the state of registration, Registration in other countries for the use on their national network, Safety certification for all Rolling Stock which does not comply with the Rolling Stock TSI.
The keeper is obliged to ensure that these data are available and the processes behind have been conducted. Design data, which shall include all constitutive (physical) elements of the rolling stock, including characteristics related to the environment, and all information that is expected to remain valid throughout the life of the rolling stock — this part may contain a history of major modifications, major maintenance, overhaul, etc.
Railway Undertaking as Duty holder during its transport control, Keeper of rolling stock, and User (Hirer) of rolling stock.
(a) Reference File of the emergency services, correlated to type of hazardous goods.
(b) Reference File of the Coding for all IMs, RUs, Service provider companies; (c) Reference File of the Coding for Freight Transport Customers; (d) Reference File of the Coding of Locations (Primary and subsidiary),
Wagon and Intermodal Unit Operational Database, Trip plan for wagon/Intermodal unit.
Status: loading of the rolling stock This status is required for the information exchange between the RU and the IMs and to other railway undertakings involved in the transport journey. Status: loaded wagon on journey This status is required for the information exchange between the IM and the RU, with other infrastructure managers and with other railway undertakings involved in the transport journey. Status: empty wagon on journey This status is required for the information exchange between the IM and the RU, with other infrastructure managers and railway undertakings involved in the transport journey. Status: unloading of rolling stock This status is required for the information exchange between the RU at destination and the Lead RU for the transport. Status: empty wagon under fleet management control This status is required to get the information about availability of a vehicle of defined characteristics.
1. Authentication A database must support the authentication of users of the systems before they can gain access to the database. 2. Security A database must support the security aspects in the meaning of controlling access to the database. The possible encryption of the database contents itself is not required. 3. Consistency A database selected shall support the ACID principle (Atomicity, Consistency, Isolation and Durability). 4. Access Control A database must allow access to the data to users or systems that have been granted permission. The access control shall be supported down to a single attribute of a data record. The database shall support configurable, role based access control for insertion, update or deletion of data records. 5. Tracing A database must support logging all actions applied to the database to allow for tracing the detail of the data entry (Who, What, When did the contents change). 6. Lock strategy A database must implement a locking strategy which allows access to the data even when other users are currently editing records. 7. Multiple access A database must support that data can be accessed simultaneously by several users and systems. 8. Reliability The reliability of a database must support the required availability. 9. Availability A database must have an availability on demand of at least 99,9 %. 10. Maintainability A maintainability of the database must support the required availability. 11. Safety Databases themselves are not safety-related. Hence safety aspects are not relevant. This is not to be confused with the fact that the data — e.g. wrong or not actual data — may have impact on the safe operation of a train. 12. Compatibility A database must support a data manipulation language that is widely accepted, such as SQL or XQL. 13. Import facility A database shall provide a facility that allows the import of formatted data that can be used to fill the database instead of manual input. 14. Export facility A database shall provide a facility that allows to export the contents of the complete database or its part as formatted data. 15. Mandatory Fields A database must support mandatory fields that are required to be filled before the relevant record is accepted as input to the database. 16. Plausibility Checks A database must support configurable plausibility checks before accepting the insertion, update or deletion of data records. 17. Response times A database must have response times that allow users to insert, update or delete data records in a timely manner. 18. Performance aspects The reference files and databases shall support in a cost effective manner the queries necessary to allow the effective operation of all relevant train runs and wagon movements that are covered by the provisions of this TSI. 19. Capacity aspects A database shall support the storage of the relevant data for all freight wagons respectively the network. It shall be possible to extend the capacity by simple means (i.e. by adding more storage capacity and computers). The extension of the capacity shall not require replacement of the subsystem. 20. Historical data A database shall support the management of historical data in the meaning of making of data available that has been already transferred into an archive. 21. Back-up strategy A back-up strategy shall be in place to ensure that the complete database contents for up to a 24 hour period can be recovered. 22. Commercial aspects A database system used shall be available commercially off-the-shelf (COTS-product) or be available in the public domain (Open Source).
is designed to reconcile heterogeneous information models by semantically transforming the data that is exchanged between the systems and by reconciling the business process and application-level protocol differences, has minimum impact on the existing IT architectures implemented by every actor, safeguards IT investments made already.
metadata — structured data describing the content of messages, Public Key Infrastructure (PKI), Certification Authority (CA),
message formatting of outgoing messages according to the metadata, signing and encryption of outgoing messages, addressing of the outgoing messages, authenticity verification of the incoming messages, decryption of incoming messages, conformity checks of incoming messages according to metadata, handling the single common access to various databases.
(i) positive send ACK; (ii) negative send NACK.
Path contract, where within the line segment description the relevant information about usable command control and signalling equipment is given, and various Rolling Sock Reference Databases, where the command control and signalling equipment of the rolling stock must be stored.
| Interface | Reference Telematics Applications for Freight TSI | Reference Telematics Applications for passengers TSI |
|---|---|---|
| Train ready | ||
| Train running forecast | ||
| Train running information | ||
| Train running interrupted to RU | ||
| Handling of short term timetable data | ||
| Common Interface | ||
| Central Repository | ||
| Reference Files |
are Error free: accessible, accurate, timely, complete, consistent with other sources, etc., and possess desired features: relevant, comprehensive, proper level of detail, easy-to-read, easy-to-interpret, etc.
Accuracy, Completeness, Consistency, Timeliness.
The central repository also contains the certification authority (Open CA PKI). This is mainly an administration act, which is physically implemented. Wrong entries become obvious immediately. No assessment procedure needed. The central repository contains the message metadata (according to document "TAF TSI — Annex D.2: Appendix F — TAF TSI Data and Message Model", listed in Appendix I) as the basis for message exchange in a heterogeneous information environment. The metadata must be administrated and updated in the central repository. Any incompatibility in the message structure or content of the messages for sending or receiving data will be recognised immediately and the transfer will be refused. No assessment procedure needed. The common interface at each actor's node contains mainly the local "mirror" of the central repository for shortening the response time and reducing the load on the repository. It must be ensured, that the data versions in the central repository and in the common interface are always the same. Therefore the data update must be done on the central level and new versions must be downloaded from there. No assessment procedure needed.
phase one: detailed IT specifications and master plan; phase two: development; phase three: deployment.
1. The Steering Committee shall be composed of: the representative bodies from the railway sector acting on a European level as defined in Article 3(2) of Regulation (EC) No 881/2004 ("the rail sector representative bodies"), the European Railway Agency, and the Commission.
2. This Steering Committee shall be co-chaired by (a) the Commission and (b) a person nominated by the rail sector representative bodies. The Commission assisted by the members of the steering committee shall draft the rules of procedure of this Steering Committee, on which the steering committee shall agree. 3. The members of the Steering Committee may propose to the Steering Committee that other organisations be included as observers where there are sound technical and organisational reasons for doing so.
provide the necessary efforts and resources needed for the implementation of this Regulation, comply with the principles of access to the TAF TSI common components which shall be available to all market participants at a unified, transparent and lowest possible service cost structure, ensure that all market participants have access to all data exchanged required for fulfilling their legal obligations and for the performance of their functions in accordance with the TAF TSI functional requirements, protect the confidentiality of customer relationships, set-up a mechanism which will enable "late comers" to join the TAF development and to profit from achieved TAF developments related to the common components in a way which is satisfactory both for above stakeholders and for the "new comers" in particular with view to fair cost sharing, report of progress with implementation plans to the TAF Steering Committee. This reporting includes also — where appropriate — deviations from the master plan.
represent their individual stakeholder members at the TAF-TSI Steering Committee, raise awareness of their members on their obligations related to the implementation of the present regulation, ensure current and complete access for all above stakeholders to status information on the work of the Steering Committee and any other groups in order to safeguard each representative's interests in the implementation of TAF-TSI in a timely manner, ensure the efficient information flow from their individual stakeholder members to the TAF Steering Committee so that the stakeholders' interest is duly taken into account for decisions affecting the TAF development and deployment, ensure the efficient information flow from the TAF Steering Committee to their individual stakeholder members so that the stakeholders are duly informed about decisions affecting the TAF development and deployment.
the identification of the technical constraints underpinning the change, a statement of who takes responsibility for the change implementation procedures, the procedure for validating the changes to be implemented, the policy for change management, release, migration and roll-out, the definition of the responsibilities for the management of the detailed specifications and for both its quality assurance and configuration management.
1. The change requests affecting the documents are submitted either via the Member States or via the representative bodies from the railway sector acting on a European level as defined in Article 38(4) of Regulation (EU) 2016/796 of the European Parliament and of the Council Regulation (EU) 2016/796 of the European Parliament and of the Council of 11 May 2016 on the European Union Agency for Railways and repealing Regulation (EC) No 881/2004 (OJ L 138, 26.5.2016, p. 1 ).2. The Agency shall gather and store the change requests. 3. The Agency shall present the change requests to the dedicated ERA working party, which will evaluate them and prepare a proposal accompanied by an economic evaluation, where appropriate. 4. Afterwards the Agency shall present each change request and the associated proposal to the change control board that will or will not validate or postpone the change request. 5. If the change request is not validated, the Agency shall send back to the requester either the reason for the rejection or a request for additional information about the draft change request. 6. If the change request is validated, the technical document shall be amended. 7. If no consensus about the validation of a change request can be reached, the Agency shall submit to the Commission a recommendation to update the documents listed in Appendix I together with the draft new version of the document, the change requests and their economic evaluation and shall make these documents available on their web site. 8. The new version of the technical document with the validated change requests shall be made available at the site of the Agency. The Agency will keep the Member States informed via the Committee established in accordance with Article 29(1) of Directive 2008/57/EC. 9. If a change request would require a change of the legal text of the TAF TSI, the Agency shall send a request to the European commission to request a revision of the TAF TSI and/or request the technical opinion from the Agency.