Date exchange plays a big role in the microstructure railway. Once there was a time, when data (e.g. timetables, circulation plans and so on) were transmitted in printed or handwritten form, but now the meaning of the transfer of the data in digitalized form gets more and more important. By delivery of the digital data entering effort on the side of the receiver of the data can be reduced significantly.
FBS supports especially with it's FBS-RailML interface the digital data exchange of operational data. It can import data as well as export. A possible data format at the digital data exchange with FBS is railML, a data structure specially tailored for the railway. If the operational data are exported and transmitted by railML, they can be imported by the receiver directly in FBS.
For a succesful import in FBS it is necessary, that a minimum of operational data is exported with railML from the side of the sender. The compilation of this needed operational data can be found in the following files. There is a differentation between data, which are transmitted at an SPNV 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.
TOC to regional authority
Compilation of the needed data for the railML-export TOC-regional authority (PDF only in German)