UC:Use cases: Difference between revisions
[checked revision] | [checked revision] |
(Data consolidation including default order.) |
|||
(21 intermediate revisions by 2 users not shown) | |||
Line 19: | Line 19: | ||
===List of active use cases=== | ===List of active use cases=== | ||
[[:UC:Use cases/table|View/edit list on the separate source page]] | <!-- [[wiki3:Template:UC:Use cases/table|View/edit list on the separate source page]] --> | ||
{{wiki3 | {{raw:wiki3:UC:Use cases/table}} | ||
===List of inactive use cases=== | ===List of inactive use cases=== | ||
Line 26: | Line 26: | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|- | |- | ||
! style="width:5%"|<div style="writing-mode: tb-rl;">Directing Subschema</div> !! <div style="writing-mode: tb-rl;">Involved Subschemas</div> !! <div style="writing-mode: tb-rl;">Implemented in {{rml}} version<br />(lowest)</div> !! <div style="writing-mode: tb-rl;">Implemented in {{rml}} version<br />(highest)</div> !! <div style="writing-mode: tb-rl;">Priority</div> !! style="width:15%"|Description (EN) !! style="width:15%"|Description (DE | ! style="width:5%"|<div style="writing-mode: tb-rl;">Directing Subschema</div> !! <div style="writing-mode: tb-rl;">Involved Subschemas</div> !! <div style="writing-mode: tb-rl;">Implemented in {{rml}} version<br />(lowest)</div> !! <div style="writing-mode: tb-rl;">Implemented in {{rml}} version<br />(highest)</div> !! <div style="writing-mode: tb-rl;">Priority</div> !! style="width:15%"|Description (EN) !! style="width:15%"|Description (DE) !! <div style="writing-mode: tb-rl;">Abbreviation</div> !! style="width:15%"|Reported by !! Status<br><span style="font-size:50%">[[UC:Use_cases#How_to_interpret_the_status|how to interpret the status]]</span> !! Reason<br><span style="font-size:50%">Why is this UC on hold?</span> | ||
|- | |- | ||
|TT | |TT | ||
| | |? | ||
| | | | ||
| | | | ||
Line 37: | Line 36: | ||
|{{Deu|Zuglenkung}} | |{{Deu|Zuglenkung}} | ||
| | | | ||
|<font color="red">writer: [https://www.railml.org/en/introduction/partners/detail/toshiba-corporation.html Toshiba Corporation]?</font color>; <br /> <font color="black">reviewer: [https://www.railml.org/en/introduction/partners/detail/psi-transcom.html PSI Transcom]</font color> | |||
|<font color="red">writer: [https://www.railml.org/en/introduction/partners/detail/toshiba-corporation.html Toshiba Corporation]?</font color> <font color="black">reviewer: [https://www.railml.org/en/introduction/partners/detail/psi-transcom.html PSI Transcom]</font color> | |||
|postponed | |postponed | ||
|Currently no demand | |Currently no demand | ||
|- | |- | ||
|IL | |IL | ||
| | |? | ||
| | | | ||
| | | | ||
Line 49: | Line 47: | ||
|[[UC:IL:EulynxDataPreparationInterlocking|Data prepration for signalling]] | |[[UC:IL:EulynxDataPreparationInterlocking|Data prepration for signalling]] | ||
|{{Deu|Datenbereitstellung für Stellwerkssysteme}} | |{{Deu|Datenbereitstellung für Stellwerkssysteme}} | ||
|DPRS | |DPRS | ||
|<font color="black">writer: | |<font color="black">writer: [https://eulynx.eu/ EULYNX]</font color> | ||
|postponed | |postponed | ||
|EULYNX withdrew from development | |EULYNX withdrew from development | ||
|- | |- | ||
|TT | |TT | ||
| | |? | ||
| | | | ||
| | | | ||
Line 63: | Line 60: | ||
|{{Deu|Betriebssimulation Fahrplan}} | |{{Deu|Betriebssimulation Fahrplan}} | ||
| | | | ||
|<font color="red">writer: [https://www.railml.org/en/introduction/partners/detail/opentrack-railway-technology.html Open Track Railway Technology]?</font color>; <br /> <font color="black">reviewer: [https://www.railml.org/en/introduction/partners/detail/sma-und-partner.html SMA+Partner]</font color> | |||
|<font color="red">writer: [https://www.railml.org/en/introduction/partners/detail/opentrack-railway-technology.html Open Track Railway Technology]?</font color> <font color="black">reviewer: [https://www.railml.org/en/introduction/partners/detail/sma-und-partner.html SMA+Partner]</font color> | |||
|postponed | |postponed | ||
|Currently no demand | |Currently no demand | ||
Line 75: | Line 71: | ||
|[[UC:IS:RailwayInfrastructureVisualisation|Railway Infrastructure Visualisation]] | |[[UC:IS:RailwayInfrastructureVisualisation|Railway Infrastructure Visualisation]] | ||
|{{Deu|Visualisierung von Schieneninfrastruktur}} | |{{Deu|Visualisierung von Schieneninfrastruktur}} | ||
|ISVI | |ISVI | ||
| | | | ||
|postponed | |postponed | ||
|Only outdated version available | |Only outdated version available | ||
|- | |||
|IL | |||
|IS | |||
| | |||
| | |||
|5 | |||
|[[UC:IL:SitePreparationDataForSignalControlledWarningSystems|Site preparation data for Signal Controlled Warning Systems]] | |||
|{{Deu|Daten zur Standortvorbereitung für Rottenwarnsysteme}} | |||
|SCWS | |||
|<font color="black">writer: [https://www.railml.org/en/introduction/partners/detail/thales-austria.html Thales Austria]</font color> | |||
|postponed | |||
|Currently no demand | |||
|} | |} | ||
Line 87: | Line 94: | ||
!rowspan=2| !!Status!!Description!!colspan=5|participation | !rowspan=2| !!Status!!Description!!colspan=5|participation | ||
|- | |- | ||
! !! !!<div | ! !! !!<div class="rotated">{{rml}} community</div>!!<div class="rotated">reporting party</div>!!<div class="rotated">{{rml}} scheme coordinator</div>!!<div class="rotated">{{rml}} governance board</div>!!<div class="rotated">{{rml}} scheme development group</div> | ||
|- | |- | ||
|rowspan=3|<div | |rowspan=3|<div class="rotated">'''pre development'''</div>||''planned'' | ||
|the use case is planned, but there is no draft available by now; usually there will be no article about this use case in the wiki; Sometimes some basic ideas will be published | |the use case is planned, but there is no draft available by now; usually there will be no article about this use case in the wiki; Sometimes some basic ideas will be published | ||
|style="text-align:center;"|× | |style="text-align:center;"|× | ||
Line 113: | Line 120: | ||
|style="text-align:center;"|× | |style="text-align:center;"|× | ||
|- | |- | ||
|rowspan=3|<div | |rowspan=3|<div class="rotated">'''development phase'''</div>||''requirements'' | ||
|the '''development phase''' begins with an assessment, if and how the {{rml}} schema has to be refined as to depict the use case | |the '''development phase''' begins with an assessment, if and how the {{rml}} schema has to be refined as to depict the use case | ||
|style="text-align:center;"|× | |style="text-align:center;"|× |
Revision as of 12:49, 24 June 2024
| ||||||||
| ||||||||
railML® 2 Wiki – RailTopoModel® Wiki |
Use cases
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*. 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 Modelling Language (UML). Examples are solutions to use cases.
railML® Use Cases
By category
CO Use Cases – IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases
List of active 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) |
Priority |
Description (EN) | Description (DE) | Abbreviation |
Reported by | Status how to interpret the status |
Edited |
---|---|---|---|---|---|---|---|---|---|---|
IL | IS | 3.1 | 3.2 | X | Interlocking module engineering data (former: Interlocking engineering) |
Stellwerksprojektierung | IMED | writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group |
implemented | June 26th 2024 by User:RailML Orga Ontology |
IS | – | 3.1 | 3.2 | X | Network statement of an infrastructure manager | Schienennetzbenutzungsbedingungen eines Infrastrukturbetreibers | NEST | writer: Správa železnic (former: SŽDC) / ProRail / Bane NOR, reviewer: NEST working group |
implemented | April 12th 2024 by User:RailML Orga Ontology |
IS | RS | 3.1 | 3.2 | X | RINF Reporting | RINF Meldung | RINR | writer: SNCF Réseau | merged into NEST | March 13th 2023 by User:RailML Coord Documentation |
IL | IS | 3.1 | 3.2 | X | Routes for timetable simulation (former: Capacity operational simulation) |
Fahrstrassen für Fahrplan simulieren (ehemals: Leistungsfähigkeit Simulation) |
RSIM | writer: Jernbanedirektoratet / Bane NOR (former: Jernbanedirektoratet Capacity Dpt), reviewer: ETCS subgroup of Interlocking working group |
implemented | December 07th 2023 by User:RailML Orga Ontology |
IS | IL | 3.1 | 3.2 | X | Schematic Track Plan | Schematische Gleisplandarstellung | SCTP | writer: Jernbanedirektoratet / Bane NOR, reviewer: SCTP working group |
implemented | February 13th 2023 by User:RailML Orga Ontology |
TT | IL, IS, RS | 3.2 | 3.2 | X | Integrated Traffic Management System | Integriertes Verkehrsmanagement | ITMS | writer: Thales Germany; reviewer: TT developer working group |
implemented | May 13th 2024 by User:RailML Coord Documentation |
IS | IL | 3.2 | 3.2 | X | ETCS track net | ETCS Streckenatlas | ETCS | writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group |
implemented | June 12th 2023 by User:RailML Coord Infrastructure |
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 | June 12th 2023 by User:RailML Coord Infrastructure | |||||
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 | June 12th 2023 by User:RailML Coord Infrastructure | |||||
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 | June 12th 2023 by User:RailML Coord Infrastructure | |||||
TT | IS, RS | 3.2 | 3.2 | X | Passenger information at stations | Fahrgastinformation am Bahnhof | PISY | writer: PSI Transcom (20. 05. 15); reviewer: init |
implemented | June 04th 2024 by User:RailML Coord Timetable |
TT | IS, RS, IL | 3.3 | 1 | Run Time Calculation Input Data | Eingangsdaten für die Fahrzeitrechnung | RTCI | writer: Jernbanedirektoratet / Bane NOR, reviewer: TT developer working group |
consolidated | March 25th 2024 by User:RailML Coord Timetable | |
Run Time Calculation Input Data – Infrastructure properties | Eingangsdaten für die Fahrzeitrechnung - Infrastruktur Eigenschaften | RTCI-a | writer: Jernbanedirektoratet, reviewer: TT developer working group |
draft | ||||||
Run Time Calculation Input Data – Rolling stock properties | Eingangsdaten für die Fahrzeitrechnung - Fahrzeug Eigenschaften | RTCI-b | writer: Jernbanedirektoratet, reviewer: TT developer working group |
draft | ||||||
Run Time Calculation Input Data – Timetable properties | Eingangsdaten für die Fahrzeitrechnung - Fahrplan Eigenschaften | RTCI-c | writer: Jernbanedirektoratet, reviewer: TT developer working group |
draft | ||||||
TT | IS, RS | 3.3 | 1 | Long Term Circulation Planning | Langfristige Umlaufplanung | LTCP | writer: IVU & TT developer working group, reviewer: TT developer working group |
draft | December 04th 2023 by User:RailML Coord Documentation | |
IS | TT | 3.3 | 1 | Posession Management | Daten für Betra und Gleissperrungen | POMA | writer: Siemens Mobility Germany (10. 01. 22); reviewer: HaCon Ingenieurgesellschaft |
draft | June 3rd 2024 by User:RailML Coord Timetable | |
IS | – | 2 | Track Geometry | Gleisgeometrie | TRGE | writer: ÖBB Infrastruktur | review | April 15th 2024 by User:RailML Coord Documentation | ||
IS | TT, RS | 2 | Driver Advisory System (DAS) | Fahrerassistenzsystem | DASY | writer: Siemens Mobility Germany? | draft | March 13th 2023 by User:RailML Coord Documentation | ||
IS | – | 2 | Railway Infrastructure Recording | Erfassung der Schieneninfrastruktur | ISRC | writer: Bahnkonzept | draft | March 13th 2023 by User:RailML Coord Documentation | ||
TT | IS, IL, RS | Passenger information inside the train | Fahrgastinformation im Zug | PISV | writer: Interautomation (17. 01. 17); reviewer: PSI Transcom and iRFP |
draft | June 04th 2024 by User:RailML Coord Timetable | |||
TT | IS, RS | A timetable for a competition (call for proposals) | Ausschreibungsfahrplan | writer: iRFP (21. 05. 15); reviewer: IVU Traffic Technologies (22. 09. 16) |
consolidated | March 13th 2023 by User:RailML Coord Documentation | ||||
TT | IS, RS, CO | Adopt vehicle working scheduling to timetable changes | Umlauf an Jahresfahrplan anpassen | writer: IVU Traffic Technologies (21. 05. 15); reviewer: HaCon Ingenieurgesellschaft |
consolidated | June 27th 2022 by User:RailML Coord Documentation | ||||
TT | RS, IS | Duty planning and staff shifts | Dienstplanung und Personalschichten | SHFT | writer: ÖBB Personenverkehr; reviewer: init |
consolidated | July 18th 2022 by User:RailML Coord Documentation | |||
TT | IS, RS | Exchange of formation data | Austausch von Wagenreihungen/ Behängungsdaten | writer: iRFP (21. 05. 15); reviewer: IVU Traffic Technologies (22. 09. 16) |
consolidated | March 13th 2023 by User:RailML Coord Documentation | ||||
TT | IS, IL, RS | Long Term Strategic Timetabling | Langfrist-Fahrplanerstellung | LTST | writer: SMA+Partner (22. 12. 16); reviewer: HaCon Ingenieurgesellschaft (28. 6. 22) |
consolidated | July 18th 2022 by User:RailML Coord Timetable | |||
TT | IS, RS | Timetable Information | Fahrplanauskunft | TINF | writer: HaCon Ingenieurgesellschaft (13. 03. 15); reviewer: IVU Traffic Technologies |
consolidated, under revision | March 13th 2023 by User:RailML Coord Documentation | |||
IS | TT, IL, RS | 3 | Asset status representation | Darstellung des Infrastrukturzustands | ASSR | writer: DLR for IN2Rail project | draft | September 27th 2023 by User:RailML Orga Ontology | ||
IS | IL | CAD for railway signaling | CAD für Zugsignalisierung | CASP | writer: Railcomplete AS | draft | December 07th 2023 by User:RailML Orga Ontology | |||
IS | IL, TT, RS | 3 | Capacity Planning | Kapazitätsplanung | CAPL | writer: Bane NOR (erstwhile: JBV) | draft | March 13th 2023 by User:RailML Coord Documentation | ||
IS | IL | 3 | Capture schematic visualisation information of track assets | Erstellung schematischer Visualisierungs-Informationen von Schienenanlagen | draft | March 13th 2023 by User:RailML Coord Documentation | ||||
IS | IL, RS, TT | Exchange of Logical Train Positions | writer: Siemens Mobility Switzerland; |
draft | July 18th 2022 by User:RailML Coord Documentation | |||||
IS | IL | 3 | 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 | March 13th 2023 by User:RailML Coord Documentation | ||
IL | IS, TT | 4 | Interlocking engineering for signalling | Stellwerkstechnik für Signalisierung | writer: Bane NOR (former: Jernbaneverket Signalling Dpt) | draft | March 13th 2023 by User:RailML Coord Documentation | |||
IS | RS | 3 | Maintenance Planning | Wartungsplanung | MAPL | draft | March 13th 2023 by User:RailML Coord Documentation | |||
IS | – | 3 | NRE Reporting | NRE Meldung | NRER | writer: ÖBB Infrastruktur | draft | March 13th 2023 by User:RailML Coord Documentation | ||
IL | IS | 4 | Operation and Control | Betriebsführung | draft | March 13th 2023 by User:RailML Coord Documentation | ||||
RS | IS, TT, IL | Operational simulation | Betriebssimulation | draft | March 13th 2023 by User:RailML Coord Documentation | |||||
IS | – | 3 | Positioning and Map-Matching | Positionierung und Kartenvergleich | POSI | draft | March 13th 2023 by User:RailML Coord Documentation | |||
IS | IL | 3 | Railway Simulation Laboratory | Eisenbahnbetriebslabor | RLAB | writer: Czech Technical University Prague | draft | June 27th 2022 by User:RailML Coord Documentation | ||
TT | IS, RS | Slot ordering | Trassenbestellung | writer: SMA+Partner (17. 09. 16); reviewer: iRFP |
draft | August 06th 2024 by User:RailML Orga Ontology | ||||
IS | 3 | Speed directory | Verzeichnis der zulässigen Geschwindigkeiten | SPED | writer: Bombardier Transportation | draft | March 13th 2023 by User:RailML Coord Documentation | |||
TT | IS | TAF/TAP TSI requirements | TAF/TAP TSI Anforderungen | writer: ERA; reviewer: Bahnkonzept |
draft | December 07th 2023 by User:RailML Coord Timetable | ||||
IS | IL, TT, RS | 3 | Timetabling | Fahrplanerstellung | ISTT | writer: ProRail | draft | March 13th 2023 by User:RailML Coord Documentation | ||
IL | IS | Hardware and cable plan | Aussenanlage und Kabelplan | draft | March 13th 2023 by User:RailML Coord Documentation | |||||
RS | IS, TT | Traction power supply simulation | Simulation der Bahnstromversorgung | draft | March 13th 2023 by User:RailML Coord Documentation | |||||
IS | Rail Inspection Data | Schienenprüfdaten | RIND | writer:DZSF & ZEDAS | draft | August 20th 2024 by User:RailML Orga Ontology | ||||
IS | TT, IL | Traffic Management Plan | TMPL | writer: Bombardier Transportation | implemented | May 13th 2024 by User:RailML Coord Documentation | ||||
Legend: Red: Writer known; reviewed |
List of inactive use cases
If you want to reactivate your inactive use case, write a post on the forum. 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) |
Priority |
Description (EN) | Description (DE) | Abbreviation |
Reported by | Status how to interpret the status |
Reason Why is this UC on hold? |
---|---|---|---|---|---|---|---|---|---|---|
TT | ? | Automatic Route Setting (ARS) Automatic Train Supervision (ATS) |
Zuglenkung | writer: Toshiba Corporation?; reviewer: PSI Transcom |
postponed | Currently no demand | ||||
IL | ? | 7 | Data prepration 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 | ||||
IS | – | 9 | Railway Infrastructure Visualisation | Visualisierung von Schieneninfrastruktur | ISVI | postponed | Only outdated version available | |||
IL | IS | 5 | Site preparation data for Signal Controlled Warning Systems | Daten zur Standortvorbereitung für Rottenwarnsysteme | SCWS | writer: Thales Austria | postponed | Currently no demand |
How to interpret the status
Status | Description | participation | |||||
---|---|---|---|---|---|---|---|
railML® community |
reporting party |
railML® scheme coordinator |
railML® governance board |
railML® scheme development group
| |||
pre development |
planned | the use case is planned, but there is no draft available by now; usually there will be no article about this use case in the wiki; Sometimes some basic ideas will be published | × | ||||
draft | a user has submitted a draft. Usually there will exist an article about the use case where you find the draft | ☒ | |||||
consolidated | the draft has been reviewed and accepted by the scheme coordinator | × | × | ☒ | × | ||
development phase |
requirements | the development phase begins with an assessment, if and how the railML® schema has to be refined as to depict the use case | × | ☒ | × | ||
model | the requirements of this use case have been implemented into the current railML® schema | ☒ | × | ||||
finished | the use case has been completely implemented, documented and released | × | ☒ | ||||
postponed | if an unfinished use case is not being barried further for several months, it 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.