Template:UC:UseCases/implemented

Return to UC:Use_cases in the railML^® 3 wiki/in the railML^® 2 wiki

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	December 1st 2025 by User:RailML Coord Documentation
IS	–	3.1	3.3	Network statement of an infrastructure manager	Schie­nen­netz­be­nut­zungs­be­din­gun­gen eines Infrastrukturbetreibers	NEST	writer: Správa železnic (former: SŽDC) / ProRai / Bane NOR, reviewer: NEST working group	implemented	December 18th 2025 by User:RailML Coord Documentation
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	February 2nd 2026 by User:RailML Coord Documentation
IS	IL	3.1	3.3	Schematic Track Plan	Schematische Gleisplandarstellung	SCTP	writer: Jernbanedirektoratet / Bane NOR, reviewer: SCTP working group	implemented	February 2nd 2026 by User:RailML Coord Documentation
TT	IL, IS, RS	3.2	3.3	Integrated Traffic Management System	Integriertes Verkehrsmanagement	ITMS	writer: Thales Germany; reviewer: TT developer working group	implemented	February 2nd 2026 by User:RailML Coord Documentation
IS	IL	3.2	3.3	ETCS track net	ETCS Streckenatlas	ETCS	writer: Thales Germany, reviewer: ETCS subgroup of Interlocking working group	implemented	October 05th 2025 by User:RailML Coord Documentation
				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	October 05th 2025 by User:RailML Coord Documentation
				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	October 05th 2025 by User:RailML Coord Documentation
				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	October 05th 2025 by User:RailML Coord Documentation
TT	IS, RS	3.2	3.3	Passenger information at stations	Fahrgastinformation am Bahnhof	PISY	writer: PSI Transcom (May 20th 2015); reviewer: init	implemented	September 29th 2025 by User:RailML Coord Documentation
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	February 2nd 2026 by User:RailML Coord Documentation
				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	June 30th 2025 by User:RailML Coord Documentation
IS	TT	3.3	3.3	Posession Management	Daten für Betra und Gleissperrungen	POMA	writer: Siemens Mobility Germany (January 10th 2022); reviewer: HaCon Ingenieurgesellschaft	implemented	January 20th 2025 by User:RailML Coord Documentation
Legend: Red: No railML.org e.V. partner so far reviewed this use case. Green: Review was performed by the railML.org e.V. partner given in the table. Priority: "X" means that work is finished, but Use case will be updated when needed by the community. "1" is the highest priority. Status: How to interpret the status