Use cases
Within the four railML® subschemas, use cases are utilised to describe, characterise, standardise and register potential scenarios. Specialists from various different countries define and review these use cases on an ongoing basis, with a view to further enhancing the railML® standard. Please also feel free to submit your own use case, if you do not find it in the lists below.
More information on why railML is developed use-case-driven and what the process of use case development itself looks like, is available in a corresponding news post: https://www.railml.org/en/news/use-case-driven-railml-development
Use cases employed in released railML versions
The following use cases have been employed in released railML versions and are considered stable. However, further development may occur if needed for use in another railML version.
In this list, the use cases have been sorted alphabetically, not according to their release date. For each use case you will find a short description as well as the use case description and element specification table for each railML version release.
Use cases proposed, drafted or under development
Further information on all railML use cases can be found in the complete use case list, which has been published on the railML 3 wiki. The use case list provides an overview with descriptions and examples of all use cases, regardless of their status (released, under development, to be revised or submitted) and subschema.
railML use case development benefits largely from community input. If you are looking for a use case to apply to a certain problem in your area of work, but cannot find an adequate solition neither on this website nor the raiML Wiki, please propose your use case using the form down below.
For any questions, comments or concerns, please contact the Organisational Team.
Use case submission templates
If you would like to submit a use case, please download the Excel and/or Word files below. Simply complete the templates in accordance with the instructions provided and send the document via email to the Organisational Team.
Feel free to contact railML.org for further questions and remarks at any time.