Date exchange plays a big role in the microstructure railway. In the past, data (e.g. timetables, circulation plans and so on) were transmitted in printed or handwritten form, but now the meaning of data transfer in digitalized form gets more and more important. By delivering digital data, entering effort on the side of the data's receiver can be reduced significantly.

FBS supports especially with it's FBS-RailML interface the digital data exchange of operational data. It can import as well as export data. A possible data format at the digital data exchange with FBS is railML, a data structure specially constructed for railway. If the operational data are exported and transmitted by railML, they can be imported directly into FBS by the receiver.

For a succesful import in FBS it is necessary, to export a minimum of operational data with railML from the sender's side. The compilation of this necessary operational data can be found in the following files. There is a differentation between data, which are transmitted at an rail passenger transport tendering procedure by a regional authority to the TOCs and that ones, which are send from the TOC to the regional authority, e.g. for a timetable preview or as an information at construction works. With vivid examples also the presentation of the needed data in the railML data structure can be examined.

Compilation of the needed data for the railML-export TOC-regional authority (PDF only in German)

example export railML TOC to regional authority