railML® - capable software

In the following chart you'll find an overview of known software with railML® interfaces.

Filter by:

Application Country
Controlguide OCS
Controlguide OCS Germany Germany
D4RH TrackPlanner
D4RH TrackPlanner Italy Italy
FAS BackOffice
FAS BackOffice Germany Germany
FBS
FBS Austria Austria Germany Germany Czechia Czechia
Switzerland Switzerland Saudi Arabia Saudi Arabia Greece Greece
GPSinfradat
GPSinfradat Germany Germany France France
IVU.rail
IVU.rail Germany Germany Switzerland Switzerland
LUKS
LUKS Belgium Belgium Norway Norway Germany Germany
Maprex Train Simulator
Maprex Train Simulator South Korea South Korea
OpenTrack
OpenTrack United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland Switzerland Switzerland Sweden Sweden
Czechia Czechia Germany Germany Norway Norway
Netherlands Netherlands France France Japan Japan
Italy Italy
railML4RINF
railML4RINF Spain Spain Germany Germany France France
railOscope
railOscope Norway Norway Switzerland Switzerland
RailSys
RailSys Germany Germany Australia Australia
railVIVID
railVIVID Austria Austria Norway Norway Switzerland Switzerland
Sweden Sweden France France Czechia Czechia
Germany Germany Europe Europe
TPS
TPS Norway Norway Germany Germany Israel Israel
Switzerland Switzerland France France
VIAcommuta
VIAcommuta Germany Germany Saudi Arabia Saudi Arabia
Viriato
Viriato Germany Germany Switzerland Switzerland
VIS-ALL 3D
VIS-ALL 3D Germany Germany

Interfaces labelled with certified in the description are able to exchange data in accordance to the railML standard. However some of the programmes are not certified as they are either older programmes, under development or in the process of certification.

Information in the grayed box was provided by the railML.org partner and is not checked by railML.org. Please read the detailed information about the programmes carefully and don´t hesitate to contact railML.org for any further questions.

Currently we are improving the description of the use cases and the linkage to the programme support. Therefore these should be considered as beta descriptions.