Compendium of the data to be exchanged between Railway Undertakings (RUs) for the purpose of conveying freight traffic

This IRS specifies the data to be exchanged as necessary for the operation of trains and the forwarding of wagons, intermodal units, or other rail vehicles.

In rail freight transport, data required for operation of a train, and the wagons, loading units and other rail vehicles that it contains, must be shared with the RUs that continue train operation and individual transport operations. This serves as the basis for safe, efficient, and economical train and transport operations.

If such data is transmitted to the next RU in a timely manner, the data does not have to be collected and/or recorded again by the participating RUs.

The RUs (see Abbreviations and Symbols - page 6) agree bilaterally as to which version is to be used.

Data is exchanged in respect of the train, wagon, loading units and consignments.

Data is exchanged using the XML message format.

The XSD schema (technical description) for version 2.0 (see Reference documents - page 5) and subsequent versions can be found in a zip folder available with the download file of this IRS.

The XLS representation of the message contents (functional description) for version 2.0 (see Reference documents) and subsequent versions can be found in a zip folder available with the download file of this IRS.

Information is compiled for all vehicles in freight trains and traction units in principle.

HERMES message timing and updates

The HERMES message (see Abbreviations and Symbols) should be sent as soon as possible upon completion of train composition before handover to the next RU.
The information concerning traction transmitted in the HERMES message is up to date at the last handling station prior to handover to the next RU.

The HERMES message should be sent as early as possible, even when the traction at the handover location is not yet known. A further HERMES message should be sent when the information on traction is available.