Search results
Jump to navigation
Jump to search
- specify the required data regarding certain aspects. on demand or on changes of RS depending on the number of various vehicle types and train formations Technical1 KB (146 words) - 13:29, 13 March 2023
- accuracy without simulating the process of railway operation. Thus this use case is always an addon to the one of „Operational simulation“. Provision of2 KB (236 words) - 13:43, 13 March 2023
- Rollingstock (section Rollingstock (RS))the current railML® 3 RS subschema A list of use cases for the railML® rollingstock scheme can be found here Category:Use_case_(RS). Examples (link to the3 KB (458 words) - 17:20, 29 November 2023
- UC:Use cases (section What is a use case?)IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page If you want to reactivate your inactive use case7 KB (287 words) - 15:43, 8 April 2024
- station, train number field, timetable element) to the next. For example, one use case is a TMS that provides the current (dispatching) timetable and train positions16 KB (1,407 words) - 11:50, 18 July 2022
- Main Page (section Rollingstock (RS))RailTopoModel (external link). A list of use cases for the railML® interlocking schema can be found on page Category:Use case (IL). →Main Article: Infrastructure10 KB (1,041 words) - 10:56, 2 May 2024
- This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will2 KB (273 words) - 13:26, 13 March 2023
- (sofern der Art entsprechend) Erforderliche Qualifikationen Der Use Case baut auf dem Use Case Fahrplanauskunft auf, das heißt für Dienste, die auf einer Fahrt3 KB (410 words) - 12:04, 18 July 2022
- Infrastructure Related subschemas: IL TT RS Reported by: ProRail For general information on use cases see UC:Use cases3 KB (343 words) - 13:44, 13 March 2023
- and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger5 KB (751 words) - 13:28, 13 March 2023
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category Use case (TT)) (section Use case / Anwendungsfall)and Rostering Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases2 KB (209 words) - 18:11, 27 June 2022
- Traffic Management Plan Description / Beschreibung / Description The UseCase TrafficManagementPlan (TMP) defines exchange of information between Timetable3 KB (270 words) - 15:11, 27 June 2022
- the infrastructure and state their validity. The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure4 KB (523 words) - 11:14, 18 July 2022
- and Rostering Related subschemas: IS RS Reported by: PSI For general information on use cases see UC:Use cases6 KB (691 words) - 13:28, 13 March 2023
- RS:formation (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further512 bytes (38 words) - 16:19, 5 March 2021
- elements.) A better modelling for this aspect is, in the author’s opinion, to use the concept of commercial trains in a different way than currently described6 KB (688 words) - 13:26, 13 March 2023
- RS:vehicle (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further510 bytes (38 words) - 16:19, 5 March 2021
- master data for the use case "passenger information inside the train". The information from the <timetable> are data which will be used individually for every9 KB (677 words) - 18:10, 27 June 2022
- RS:administrativeData (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the RS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further521 bytes (38 words) - 21:53, 25 April 2022
- Subschema: Infrastructure Related subschemas: TT RS For general information on use cases see UC:Use cases1 KB (157 words) - 13:46, 13 March 2023
- Subschema: Infrastructure Related subschemas: RS For general information on use cases see UC:Use cases1 KB (133 words) - 13:47, 13 March 2023
- proposal for a railML® use case: A timetable for a competition (call for proposals) Ausschreibungsfahrplan The use case describes a timetable which is16 KB (1,903 words) - 13:27, 13 March 2023
- railML® for RINF Reporting; railML® für RINF Meldung This use case aims at providing a railML3 file, fulfilling the functional requirements published by3 KB (297 words) - 13:49, 13 March 2023
- Infrastructure Related subschemas: TT RS Reported by: IS For general information on use cases see UC:Use cases3 KB (306 words) - 13:48, 13 March 2023
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category Use case (TT)) (section Use case / Anwendungsfall)data Typically, the import is done manually using a file based interface. Common Infrastructure: the import uses elements from mesoscopic and macroscopic3 KB (355 words) - 18:11, 27 June 2022
- this use case even without reference to the timetable. This would be the case in a very early stage of planning. For the purposes of this use case, vehicle6 KB (926 words) - 17:00, 4 December 2023
- Infrastructure Related subschemas: IL TT RS Reported by: Jernbaneverket For general information on use cases see UC:Use cases5 KB (687 words) - 13:46, 13 March 2023
- Autoexport from the XML-Schema for element RS:administrativeData of railML® version 3.2 UML-visualization of RS Documentation This is the container for the680 bytes (5 words) - 21:53, 25 April 2022
- Autoexport from the XML-Schema for element RS:formation of railML® version 3.2 UML-visualization of RS Documentation The formation collects all data of2 KB (5 words) - 12:43, 8 February 2024
- element RS:vehicle of railML® version 3.2 UML-visualization of RS Documentation A vehicle is a set consisting of at least one vehiclePart which is used in operation3 KB (5 words) - 12:42, 8 February 2024
- railML® website). The code lists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity11 KB (422 words) - 15:50, 16 November 2022
- the railML® website). Codelists are intended to address certain frequently used entities with a single code, as to avoid repetitious work as well as ambiguity17 KB (299 words) - 15:10, 7 December 2023