General Hints Concerning the FBS-railML-Interface

Navigation: General Hints Concerning the FBS-railML-Interface

For many years, FBS has had special interfaces to third-party systems that are in productive use with a large number of customers. Since 2002, iRFP has been intensively involved in the development of an exchange format for railway data that is as uniform as possible - the XML exchange format railML®. FBS data can therefore be exchanged more easily with third-party systems via the railML® format.

In the current version, the FBS-railML interface enables an import of almost all timetable data from the railML format into FBS. It is also possible to export timetable data to railML, for which a separate description exists. This document describes the import.

Please note that the railML standard does not automatically mean that two programmes can always exchange data without errors. This is due to the fact that the railML standard does define the general structure of infrastructure and vehicle data - however, on the one hand, the scope of the data (the completeness) and on the other hand, the details of some special data differ depending on the application in different programmes. For this reason, there is a special interface description for the FBS implementation of the RailML format. It describes the specific data fields used by FBS and their contents. The current version of the interface description and the scheme documents (*.xsd) can be found at

http://www.en.irfp.de/technical-advice-to-railml.html

Therefore, please bear in mind that before using the interface, it is usually necessary to use some test data from the software supplier of the other programme involved in the data exchange for test imports. We are, of course, happy to support our customers with the pre-conversion of user-specific test data and the discussion of the interface contents.

Of course, it is also possible to exchange timetable data in an uncomplicated way via this interface if both applications involved are FBS.

The implementation of the interface is not to be regarded as completed at any time, i.e., extensions or adjustments can be made at any time.