Search results

Jump to navigation Jump to search

  • UC:Use case example (category UC without specified reporter)
    for a header or introduction. The headline is made with Template: UC title (type {{UC title}}) What is the application behind the use case? Which data in
    2 KB (263 words) - 17:26, 5 February 2024
  • UC:RS:OperationalSimulation (category UC without specified reporter)
    (currently manual) infrastructure timetable interlocking This section serves to specify the required data regarding certain aspects. on demand or on changes of
    1 KB (146 words) - 13:29, 13 March 2023
  • UC:IS:RailwayInfrastructureVisualisation (category UC without specified reporter)
    geo-referenced coordinates and can thus be visualized. none This section serves to specify the required data regarding certain aspects. irregularly, depending on the
    2 KB (180 words) - 13:43, 13 March 2023
  • UC:RS:TractionPowerSupplySimulation (category UC without specified reporter)
    fields The electrical simulation is not possible with the necessary accuracy without simulating the process of railway operation. Thus this use case is always
    2 KB (236 words) - 13:43, 13 March 2023
  • UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (category UC without specified reporter)
    (version(s) not yet specified)
    3 KB (383 words) - 13:44, 13 March 2023
  • UC:IL:InterlockingEngineering (category UC without specified reporter)
    planning parameters for interlocking with suppliers This section serves to specify the required data regarding certain aspects. Depends on the frequency of
    11 KB (828 words) - 13:25, 13 March 2023
  • UC:IL:HardwareAndCablePlan (category UC without specified reporter)
    IS schema or classic track plan) infrastructure This section serves to specify the required data regarding certain aspects. static (not changing) on demand
    1 KB (119 words) - 13:51, 13 March 2023
  • UC:IS:PassengerInformationSystem (category UC without specified reporter)
    topology data: Once a day. rolling stock timetable This section serves to specify the required data regarding certain aspects. Bulk transfer: regular changes
    1 KB (157 words) - 13:46, 13 March 2023
  • UC:IS:MaintenancePlanning (category UC without specified reporter)
    Delta transfer of updated elements rolling stock This section serves to specify the required data regarding certain aspects. monthly tiny Signaling Construction
    1 KB (133 words) - 13:47, 13 March 2023
  • UC:IL:OperationAndControl (category UC without specified reporter)
    temporary local operation Routes infrastructure This section serves to specify the required data regarding certain aspects. only on configuration changes
    2 KB (209 words) - 13:52, 13 March 2023
  • Dev:Use case example/old (category UC without specified reporter)
    Template: UC data (type {{UC data}}) How often are the data updated? Does this happen routinely? The headline is made with Template: UC update (type {{UC update}})
    2 KB (220 words) - 16:25, 4 December 2023
  • UC:IS:PositioningAndMap-Matching (category UC without specified reporter)
    digital track map used for the application. none This section serves to specify the required data regarding certain aspects. Static: map is considered to
    3 KB (367 words) - 13:49, 13 March 2023
  • UC:IS:PosessionManagement (category UC without specified reporter)
    assigned to one PICOP one big possession could be split into two small once, without deactivation/reactivation phase PICOP could require to move possessed switches
    3 KB (394 words) - 12:02, 18 July 2022
  • UC:TT:LongTermCirculationPlanning (category UC without specified reporter)
    possible to describe the circulation data exchanged for this use case even without reference to the timetable. This would be the case in a very early stage
    6 KB (926 words) - 17:00, 4 December 2023
Retrieved from "https://wiki3.railml.org/wiki/Special:Search"