ISR - Overview

Overall scheme of all ISR functions:

You will find description of the basic (core) ISR system below, while descriptions of additional functions are under the link New functions.


ISR ensures exchange of movement information for wagons in international traffic through a central platform.

Basic ISR Components are:

  • Information systems of connected railway undertakings. They monitor wagons in their own trains and send movement information to the central ISR message broker. In opposite direction they may receive (and process) movement information from other ISR members, forwarded by the central message broker.
  • Central message broker (CDS) ensures reception of messages, their validation, storage as well as format conversion and distribution.
  • All data like the wagon movement events and the transport descriptions are stored in the central ISR database for the transport duration.
  • A subset of the consignment note data is taken over from ORFEUS to match the events to a Transport Description (TD).
  • The ISR web site allows to search in the stored data and to display different views on them.
  • Due to strict filtering rules, RUs can access the ISR database, depending on their role within the transport. The relationship with the customers remains within each RU.
  • Stability of both central systems and "national" railway applications is excellent thanks to service management and redundancy.

ISR architecture

Registered Wagon Events

Railway undertakings can report to the ISR the following wagon event types:

  • CreateTransportDossier - consignment note completed (event reported via the ORFEUS application)
  • UpdateTransportDossier - consignment note updated (event reported via the ORFEUS application)
  • DeleteTransportDossier - consignment note deleted (event reported via the ORFEUS application)
  • NoteCreated - consignment note completed (event reported directly) *
  • ReadyToPull - wagon can be pulled from customer
  • Pulled - wagon pulled from customer
  • LeftOrigin - wagon departed from shipping station
  • Arrival - wagon arrived to intermediate station (typically marshalling yard)
  • Departure - wagon left from intermediate station
  • PassedThrough - wagon went through a station with train without stop or processing
  • HandOverAdvice - planned border crossing (event reported via copy of H30 Train Preannounce)
  • ChangeOfCarrier - wagon crossed border (unspecified, type to be abandoned)
  • HandedOver - wagon given by the previous carrier to the next one
  • TakenOver - wagon taken over (accepted) by the next carrier
  • WagonRefused - wagon rejected by the next carrier, to be returned to previous one
  • WagonDamaged - technical problem occurred on the wagon, is out of service
  • WagonRepaired - wagon is restored, it can go again
  • ReachedDestination - wagon arrived to destination station
  • Delivered - wagon / goods is delivered to the customer
  • FreeForDisposition - wagon is unloaded and ready for disposition
  • KmCalculationResult - distance (km) done by wagon at a carrier during a period
  • ELTA-Forwarding - used to transmit the Estimated Latest Time of Arrival calculated by Xrail


  • ISR system processes all these new event types already. It is possible to receive and also forward these new event types with the WSM message. They are also displayed on the ISR website.
  • However, most of RU systems are able send and receive only some (larger or smaller subset) of the event types and no member provides all event types yet.
  • The ISR team maintains table, which shows which event types are sent and also received by each specific ISR user railway undertaking.
  • Currently exchanged events are as near to the reality as possible depending on the ability of the production system of each RU

Message Syntax:

The ISR central system receives messages using the CDS message broker. Several formats are allowed.

  • Enlarged XML wagon status message (eWSM), versions 04 and 05.
  • UIC application 30 message, for planned border crossing (XML versions 1.01, 1.03 , 1.04b, 1.04cs and 2.0)


  • ISR uses the FTP (file transfer protocol) for transmission of messages. FTP is an Internet standard (RFC 959).
  • For the specific needs of the ISR application, each connected system needs to install specific FTP client to communicate with the CDS.
  • Exception are the copies of the application 30 messages (border crossing) transmitted using the HOSA FTP clients.
  • The communication infrastructure used is mostly the HERMES IP VPN (Virtual Private Network) provided by Hit Rail.

Distribution Channels :

ISR offers three different data distribution channels

  • Forwarding - this is the standard way. Received information is automatically and immediately distributed to concerned ISR railway undertakings (RU) for further internal processing and use. The messages use the WSM format (presently in versions 04 and 05) and from historical reasons, also the Edifact IFTSTA message (will be abandoned soon).
  • ISR web site. This site offers access to the ISR information through several search criteria. Results are displayed as html pages or can be downloaded as csv files. This site is from data security reasons non public and it is open for authorized RU's staff only.
  • Web services. This option allows for members to provide an own web interface with local language and eventual added features, which then makes web service queries to the ISR system.

Each RU receives (only) information about wagons in which transport it is involved as carrier, and/or is wagon responsible (which may be not same as the keeper).

Testing and production support:

  • Separate production and testing environment, plus instant backup of the production system,
  • Permanent supervision of availability of the member's information systems (heartbeat functionality of the FTP modules)
  • Comprehensive tools for application statistics and for investigation of messages content,
  • Format control of incoming messages, including check of WSM's against XML schema,
  • Generation of error messages in case of error detectection (sent by e-mail to distribution address),
  • Audit trail to allow tracing of internal events,
  • All system information, specifications, formats, contacts are available (for members) on specific project website.