Search results

Jump to navigation Jump to search
  • UC:RS:OperationalSimulation (category Use case (RS)) (section Use case / Anwendungsfall)
    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 Technical
    1 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 of
    2 KB (236 words) - 13:43, 13 March 2023
  • 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 the
    3 KB (458 words) - 17:20, 29 November 2023
  • IL Use Cases – IS Use CasesRS Use Cases – TT Use Cases View/edit list on the separate source page   If you want to reactivate your inactive use case
    7 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 positions
    16 KB (1,407 words) - 11:50, 18 July 2022
  • RailTopoModel (external link). A list of use cases for the railML® interlocking schema can be found on page Category:Use case (IL). →Main Article: Infrastructure
    10 KB (1,042 words) - 15:08, 3 April 2024
  • UC:TT:SlotOrdering (category Use case (TT)) (section Use case / Anwendungsfall)
    This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will
    2 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 Fahrt
    3 KB (410 words) - 12:04, 18 July 2022
  • UC:IS:Timetabling (category Use case (IS)) (section Use case / Anwendungsfall)
    Infrastructure   Related subschemas: IL TT RS  Reported by: ProRail For general information on use cases see UC:Use cases
    3 KB (343 words) - 13:44, 13 March 2023
  • UC:TT:TimetableInformation (category Use case (TT)) (section Use case / Anwendungsfall)
    and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger
    5 KB (751 words) - 13:28, 13 March 2023
  • and Rostering   Related subschemas: IS RS CO Reported by: IVU For general information on use cases see UC:Use cases
    2 KB (209 words) - 18:11, 27 June 2022
  • UC:TT:TrafficManagementPlan (category Use case (TT)) (section Use case / Anwendungsfall)
    Traffic Management Plan Description / Beschreibung / Description The UseCase TrafficManagementPlan (TMP) defines exchange of information between Timetable
    3 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 infrastructure
    4 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 cases
    6 KB (691 words) - 13:28, 13 March 2023
  • UC:TT:ExchangeOfFormationData (category Use case (TT)) (section Use case / Anwendungsfall)
    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 described
    6 KB (688 words) - 13:26, 13 March 2023
  • UC:TT:FGIInTrain (category Use case (TT)) (section Use case / Anwendungsfall)
    master data for the use case "passenger information inside the train". The information from the <timetable> are data which will be used individually for every
    9 KB (677 words) - 18:10, 27 June 2022
  • 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 further
    512 bytes (38 words) - 16:19, 5 March 2021
  • 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 further
    510 bytes (38 words) - 16:19, 5 March 2021
  • Subschema: Infrastructure   Related subschemas: TT RS  For general information on use cases see UC:Use cases
    1 KB (157 words) - 13:46, 13 March 2023
  • UC:IS:MaintenancePlanning (category Use case (IS)) (section Use case / Anwendungsfall)
    Subschema: Infrastructure   Related subschemas: RS  For general information on use cases see UC:Use cases
    1 KB (133 words) - 13:47, 13 March 2023
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)