UC:UseCases
Jump to navigation
Jump to search
|
In this page you learn what is a use case and find a list of railML® use cases.
While the emphasis of the railML® Wiki lies in documenting single elements in a bottom-up approach, we also try to help users to capture the concepts of railML® via examples and use cases in a top down approach.
What is a use case?
A use case can be defined as a single task, performed by the end user of a system, that has some useful outcome[1][2]. It is described as a list of steps (actions or events) to achieve this outcome.
A use case in terms of railML® is an application of data exchange between at least two IT systems in the railway domain, where railML® can be used as a format and language for the data to be exchanged. The aim of the use case description is to formulate requirements on the technical implementation of the data exchange.
What distinguishes a use case from an example is, that examples will typically consist of pieces of railML®-code, whereas use cases will typically be formulated in natural language or Unified Modeling Language (
) (UML). Examples are solutions to use cases.
railML Use Cases
Categories by Subschema
Use case pages get automatically categorized by their directing subschema:
CO Use Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases
List of implemented use cases
View/edit list on the separate source page
| Legend (↓) | ||||||||||
Directing Subschema |
Involved Subschemas |
Implemented in railML® version (lowest) |
Implemented in railML® version (highest) |
Description (EN) | Description (DE) | Abbreviation | Reported by | Status how to interpret the status |
Edited | |
|---|---|---|---|---|---|---|---|---|---|---|
| IL | IS | 3.1 | 3.3 | Interlocking module engineering data (former: Interlocking engineering) |
Stellwerksprojektierung | IMED | writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group |
implemented | FIXME Page does not exist yet. | |
| IS | – | 3.1 | 3.3 | Network statement of an infrastructure manager[3] | Schienennetzbenutzungsbedingungen eines Infrastrukturbetreibers | NEST | writer: Správa železnic (former: SŽDC) / ProRai / Bane NOR, reviewer: NEST working group |
implemented | FIXME Page does not exist yet. | |
| IL | IS | 3.1 | 3.3 | Routes for timetable simulation (former: Capacity operational simulation) |
Fahrstrassen für Fahrplansimulation (ehemals: Leistungsfähigkeit Simulation) |
RSIM | writer: Jernbanedirektoratet / Bane NOR (former: Jernbanedirektoratet Capacity Dpt), reviewer: ETCS subgroup of Interlocking working group |
implemented | FIXME Page does not exist yet. | |
| IS | IL | 3.1 | 3.3 | Schematic Track Plan | Schematische Gleisplandarstellung | SCTP | writer: Jernbanedirektoratet / Bane NOR, reviewer: SCTP working group |
implemented | FIXME Page does not exist yet. | |
| TT | IL, IS, RS | 3.2 | 3.3 | Integrated Traffic Management System | Integriertes Verkehrsmanagement | ITMS | writer: Thales Germany; reviewer: TT developer working group |
implemented | FIXME Page does not exist yet. | |
| IS | IL | 3.2 | 3.3 | ETCS track net | ETCS Streckenatlas | ETCS | writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group |
implemented | FIXME Page does not exist yet. | |
| ETCS track net: Input for Detailed Design of ETCS Trackside | ETCS Streckenatlas: Übergabe der allgemeingültigen Streckendateninformationen (vom Netzbetreiber an den Lieferanten) | ETCS-a | writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group |
implemented | FIXME Page does not exist yet. | |||||
| ETCS track net: Output of Detailed Design of ETCS Trackside | ETCS Streckenatlas: Übergabe der Ergebnisdaten der Projektierung (vom Lieferanten an den Netzbetreiber) | ETCS-b | writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group |
implemented | FIXME Page does not exist yet. | |||||
| ETCS track net: Alignment on Topology and Properties of Trackside Equipment Before ETCS Balise Placement | ETCS Streckenatlas: Aktualisierung der Streckendaten vor Balisengruppenplatzierung | ETCS-c | writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group |
implemented | FIXME Page does not exist yet. | |||||
| TT | IS, RS | 3.2 | 3.3 | Passenger information at stations | Fahrgastinformation am Bahnhof | PISY | writer: PSI Transcom (May 20th 2015); reviewer: init |
implemented | FIXME Page does not exist yet. | |
| TT | IS, RS, IL | 3.3 | 3.3 | Run Time Calculation Input Data | Eingangsdaten für die Fahrzeitrechnung | RTCI | writer: Jernbanedirektoratet / Bane NOR, reviewer: TT developer working group |
implemented | FIXME Page does not exist yet. | |
| Run Time Calculation Input Data – Infrastructure properties | Eingangsdaten für die Fahrzeitrechnung - Infrastruktur Eigenschaften | RTCI-a | writer: Jernbanedirektoratet, reviewer: TT developer working group |
implemented | ||||||
| Run Time Calculation Input Data – Rolling stock properties | Eingangsdaten für die Fahrzeitrechnung - Fahrzeug Eigenschaften | RTCI-b | writer: Jernbanedirektoratet, reviewer: TT developer working group |
implemented | ||||||
| Run Time Calculation Input Data – Timetable properties | Eingangsdaten für die Fahrzeitrechnung - Fahrplan Eigenschaften | RTCI-c | writer: Jernbanedirektoratet, reviewer: TT developer working group |
implemented | ||||||
| TT | IS, RS | 3.3 | 3.3 | Long Term Circulation Planning | Langfristige Umlaufplanung | LTCP | writer: IVU & TT developer working group, reviewer: TT developer working group |
implemented | FIXME Page does not exist yet. | |
| IS | TT | 3.3 | 3.3 | Possession Management | Daten für Betra und Gleissperrungen | POMA | writer: Siemens Mobility Germany (January 10th 2022); reviewer: HaCon Ingenieurgesellschaft |
implemented | FIXME Page does not exist yet. | |
| Legend: Red: No railML.org e.V. partner so far reviewed this use case. | ||||||||||
List of emerging use cases
View/edit list on the separate source page
| Legend (↓) | ||||||||||
Directing Subschema |
Involved Subschemas |
Implemented in railML® version (lowest) |
Implemented in railML® version (highest) |
Description (EN) | Description (DE) | Abbreviation | Reported by | Status how to interpret the status |
Edited | |
|---|---|---|---|---|---|---|---|---|---|---|
| TT | IS, IL, RS | 3.4 | Long Term Strategic Timetabling[4] | Langfrist-Fahrplanerstellung | LTST | writer: SMA+Partner (December 22nd 2016); reviewer: HaCon Ingenieurgesellschaft (June 28th 2022); also used in ISO RailDax project |
consolidated | FIXME Page does not exist yet. | ||
| TT | IS, RS | 3.4 | Service Concept for a Tender[4] | Ausschreibungsfahrplan | SCOT (former TTFT) |
writer: iRFP (May 21st 2015); reviewer: IVU Traffic Technologies (September 22nd 2016); Jernbanedirektoratet |
consolidated | FIXME Page does not exist yet. | ||
| TT | – | 3.4 | Replacement Service Planning | Schienenersatzverkehr | RPLS | writer: TT developer working group (July 10th 2025); reviewer: TT developer working group (October 20th 2025) |
consolidated | FIXME Page does not exist yet. | ||
| TT | – | 3.4 | Capacity Reservation for Tracks | CARE | writer: HaCon Ingenieurgesellschaft (July 22nd 2025); reviewer: TT developer working group (October 20th 2025) |
consolidated | FIXME Page does not exist yet. | |||
| IS | – | 3.4 | Infrastructure Asset Status Representation[5] | Zustandsdaten | IASR | writer: DLR for IN2Rail projectreviewer: ERDMANN-Softwaregesellschaft | consolidated | FIXME Page does not exist yet. | ||
| IS | – | 3.4 | Maintenance Planning for Infrastructure[5] | Instandhaltungsdaten | MAPI | writer: IDX4rail consortium reviewer: ZEDAS GmbH | consolidated | FIXME Page does not exist yet. | ||
| IS | – | 3.4 | Track Geometry and Alignment | Gleisgeometrie und Trassierung | TRGE | writer: ÖBB-Infrastruktur (May 2nd 2017) reviewer: ERDMANN-Softwaregesellschaft | consolidated | FIXME Page does not exist yet. | ||
| IS | – | 3.4 | Automated Train Operation Information | Automatischer Zugbetrieb | ATOI | writer: Hitachi Rail GTS Germany | outlined | FIXME Page does not exist yet. | ||
| IS | RS | 3.4 | Route Compatibility Check Input Data | Fahrzeug-Strecken-Kompatibilitätsprüfung | RCCI | writer: ÖBB Infrastruktur | outlined | FIXME Page does not exist yet. | ||
| Route Compatibility Check Input Data – RCCI-a | Fahrzeug-Strecken-Kompatibilitätsprüfung – RCCI-a | RCCI-a | writer: ÖBB Infrastruktur | outlined | ||||||
| Route Compatibility Check Input Data – RCCI-b | Fahrzeug-Strecken-Kompatibilitätsprüfung – RCCI-b | RCCI-b | writer: ÖBB Infrastruktur | outlined | ||||||
| IS | TT, RS | Driver Advisory System (DAS) | Fahrerassistenzsystem | DASY | writer: Siemens Mobility Germany | draft | FIXME Page does not exist yet. | |||
| IS | – | Railway Infrastructure Recording | Erfassung der Schieneninfrastruktur | ISRC | writer: Bahnkonzept | draft | FIXME Page does not exist yet. | |||
| TT | IS, IL, RS | Passenger information inside the train | Fahrgastinformation im Zug | PISV | writer: Interautomation (January 17th 2017); reviewer: PSI Transcom and iRFP |
draft | FIXME Page does not exist yet. | |||
| TT | IS, RS, CO | Adopt vehicle working scheduling to timetable changes | Umlauf an Jahresfahrplan anpassen | writer: IVU Traffic Technologies (May 21st 2015); reviewer: HaCon Ingenieurgesellschaft |
consolidated | FIXME Page does not exist yet. | ||||
| TT | RS, IS | Duty planning and staff shifts | Dienstplanung und Personalschichten | SHFT | writer: ÖBB Personenverkehr; reviewer: init |
consolidated | FIXME Page does not exist yet. | |||
| TT | IS, RS | Exchange of formation data | Austausch von Wagenreihungen/ Behängungsdaten | writer: iRFP (May 21st 2015); reviewer: IVU Traffic Technologies (September 22nd 2016) |
consolidated | FIXME Page does not exist yet. | ||||
| TT | IS, RS | Timetable Information | Fahrplanauskunft | TINF | writer: HaCon Ingenieurgesellschaft (March 13th 2015); reviewer: IVU Traffic Technologies |
consolidated, under revision | FIXME Page does not exist yet. | |||
| IS | IL, TT, RS | Capacity Planning | Kapazitätsplanung | CAPL | writer: Bane NOR (erstwhile: JBV) | draft | FIXME Page does not exist yet. | |||
| IS | IL, RS, TT | Exchange of Logical Train Positions | writer: Siemens Mobility Switzerland; |
draft | FIXME Page does not exist yet. | |||||
| IS | – | Positioning and Map-Matching | Positionierung und Kartenvergleich | POSI | writer: DLR | draft | FIXME Page does not exist yet. | |||
| IS | IL | Railway Simulation Laboratory | Eisenbahnbetriebslabor | RLAB | writer: Czech Technical University Prague | draft | FIXME Page does not exist yet. | |||
| TT | IS, RS | Slot ordering[6] | Trassenbestellung | writer: SMA+Partner (September 17th 2016); reviewer: iRFP |
draft | FIXME Page does not exist yet. | ||||
| IS | Speed directory | Verzeichnis der zulässigen Geschwindigkeiten | SPED | writer: Bombardier Transportation | draft | FIXME Page does not exist yet. | ||||
| TT | IS | TAF/TAP TSI requirements | TAF/TAP TSI Anforderungen | writer: ERA; reviewer: Bahnkonzept |
draft | FIXME Page does not exist yet. | ||||
| RS | IS, TT | Traction power supply simulation | Simulation der Bahnstromversorgung | writer: Institut für Bahntechnik | draft | FIXME Page does not exist yet. | ||||
| Legend: Red: No railML.org e.V. partner so far reviewed this use case. | ||||||||||
List of inactive use cases
If you want to reactivate your inactive use case, write a post on the railML® forum (link to the railML® website). For more information about use cases you can also follow our UC guideline.
Directing Subschema |
Involved Subschemas |
Implemented in railML® version (lowest) |
Implemented in railML® version (highest) |
Description (EN) | Description (DE) | Abbreviation |
Reported by | Status How to interpret the status |
Reason Why is this UC on hold? | |
|---|---|---|---|---|---|---|---|---|---|---|
| IS | RS | 3.1 | 3.3 | RINF Reporting | RINF Meldung | RINR | writer: SNCF Réseau | implemented | merged into NEST | |
| IS | TT, IL | 3.2 | 3.3 | Traffic Management Plan | TMPL | writer: Bombardier Transportation | implemented | merged into ITMS | ||
| TT | IS, RS | 3.2 | 3.3 | Timetabling | Fahrplanerstellung | ISTT | writer: ProRail | implemented | merged into RTCI, ITMS, NEST, POMA and others | |
| IS | 3.4 | Rail Inspection Data | Schienenprüfdaten | RIND | writer:DZSF & ZEDAS reviewer: ERDMANN-Softwaregesellschaft |
draft | merged into IASR | |||
| TT | ? | Automatic Route Setting (ARS) Automatic Train Supervision (ATS) |
Zuglenkung | writer: Toshiba Corporation?; reviewer: PSI Transcom |
postponed | Currently no demand from community | ||||
| IL | ? | Data preparation for signalling | Datenbereitstellung für Stellwerkssysteme | DPRS | writer: EULYNX | postponed | EULYNX withdrew from development | |||
| TT | ? | Operational simulation timetable | Betriebssimulation Fahrplan | writer: Open Track Railway Technology?; reviewer: SMA+Partner |
postponed | Currently no demand from community | ||||
| IS | – | Railway Infrastructure Visualisation | Visualisierung von Schieneninfrastruktur | RAIV | postponed | Only outdated version available | ||||
| IL | IS | Site preparation data for Signal Controlled Warning Systems | Daten zur Standortvorbereitung für Rottenwarnsysteme | SCWS | writer: Thales Austria | postponed | Currently no demand from community | |||
| IL | IS | Hardware and cable plan | Aussenanlage und Kabelplan | postponed | Currently no demand from community | |||||
| IS | IL | CAD for railway signaling | CAD für Zugsignalisierung | CASP | writer: Railcomplete AS | postponed | Currently no demand from community | |||
| IL | IS, TT | Interlocking engineering for signalling | Stellwerkstechnik für Signalisierung | writer: Bane NOR (former: Jernbaneverket Signalling Dpt) | draft | |||||
| IS | IL | Capture schematic visualisation information of track assets | Erstellung schematischer Visualisierungs-Informationen von Schienenanlagen | draft | ||||||
| IS | IL | Exchange of planning parameters for interlocking with suppliers | Austausch von Planungsparametern für Stellwerke mit Herstellern | ISIL | writer: ETCS subgroup of Interlocking working group | draft | ||||
| IS | – | NRE Reporting | NRE Meldung | NRER | writer: ÖBB Infrastruktur | draft | ||||
| Legend: Red: No railML.org e.V. partner so far reviewed this use case. | ||||||||||
How to interpret the status
| Status | Description | Participation | ||||||
|---|---|---|---|---|---|---|---|---|
railML® community |
reporting party |
railML® schema coordinator |
railML® governance board |
railML® schema development group
| ||||
Phase
|
pre development
|
outlined | The use case has been outlined, a rough idea has been discussed but there is no document, nor draft of one yet. Usually no article about this use case is available in the Wiki yet, however, sometimes some basic ideas will have been published | × | ||||
| draft | A member of the community has submitted a draft of the use case description. This draft is available in the Wiki and can be found above. | ☒ | ||||||
| consolidated | The submitted draft of the use case description has been reviewed by another community member and the schema coordinator has accepted it. | × | × | ☒ | × | |||
development
|
in progress | The work for integrating the use case requirements into the railML® schema has begun. A working group is discussing the use case and developing possible additions to the schema. Interested parties are invited to join the working group. | × | ☒ | × | |||
| implemented | The requirements of this use case have been implemented into the railML® schema. The implementation work of the working group is done. However, not all documents have been finished (PDF documentation of the use case). | ☒ | × | |||||
| released | The previously implemented use case has been fully documented and is thus released. | × | ☒ | |||||
| postponed | If an unfinished use case is not being updated for several months and no members of the community have expressed interest in following up with it, the use case will be listed as postponed. | ☒ | ||||||
| ×=participates — ☒=is responsible | ||||||||
How to contribute a use case
Generally speaking, contributions to railML® and this Wiki are appreciated. For contributing use cases, please follow our UC guideline.
References
- ↑ OO design process: Use cases, an introduction: Designing the dynamic (runtime) behavior of a program (external link, 🇬🇧)
- ↑ https://www.engr.sjsu.edu/fayad/current.courses/cmpe202-Fall2009/docs/lecture2/CmpE202-Use-Cases-3.pdf (external archive link, 🇬🇧)
- ↑ https://rne.eu/legal-matters-sales/network-statements/
- ↑ 4.0 4.1 the text of this use case was updated with input from RailDax project (external link)
- ↑ 5.0 5.1 the text of this use case was updated with input from IDX4rail project (external link)
- ↑ Train_slot ()