Search results
Jump to navigation
Jump to search
- UC:IS:CADForRailwaySignaling (category UC reported by RailComplete) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)in the CAD model can correspond to a railML element type (where relevant). The allows graphical modelling of railML documents which can then be exchanged1 KB (127 words) - 14:12, 7 December 2023
- UC:Use cases (section By category)follow our UC guideline. Generally speaking, contributions to railML® and this wiki are appreciated. For contributing use cases, please follow our UC guideline7 KB (287 words) - 15:43, 8 April 2024
- UC:TT:TimetableInformation (category UC reported by HaCon) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)Update: with the release of railML 3.2 a version of railML has been published that allows partial exports. This means that a railML with a train that references5 KB (751 words) - 13:28, 13 March 2023
- UC:IL:Simulation (category UC reported by Jernbanedirektoratet) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)does not require a interlocking table. This distinguishes this IL UC from other IL UC. A route description with attributes (primarily timings and speed)7 KB (959 words) - 14:06, 7 December 2023
- UC:IS:Speeddirectory (category UC reported by ÖBB) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)other hand. It is a combination of defined organizational processes and a complete database application system. This database system is receiver and sender3 KB (117 words) - 13:45, 13 March 2023
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category UC reported by IVU) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)there is a pre-planning that is to be completed. Concatenation of operating trains to vehicle workings that are served by the same (abstract) vehicle Shunting3 KB (355 words) - 18:11, 27 June 2022
- UC:IS:Schematic Track Plan (category UC reported by JBD) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)CTC handling, overlap/safety zone/slip, timers, speeds), which is demanded by JBV. static (not changing) yearly big (station / yard) huge (region) whole4 KB (198 words) - 16:57, 13 February 2023
- UC:IL:EulynxDataPreparationInterlocking (category UC reported by EULYNX)input to the railML interlocking model. By adopting the objects and object-relations described in this data platform railML gains acceptance by IM's and ensures3 KB (450 words) - 17:54, 27 June 2022
- UC:TT:FGIInTrain (category UC reported by Interautomation) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)transport cloud service by using a standardized interface, for example according to VDV-DFI (VDV-453). The quality and the completeness of the timetable import9 KB (677 words) - 18:10, 27 June 2022
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category UC reported by IVU) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)Infrastructure Rolling stock could be daily small (single train run) any see _Import complete timetable for vehicle working scheduling_ We describe different subtypes2 KB (209 words) - 18:11, 27 June 2022
- UC:IS:IntegratedTMS (category UC reported by Bombardier) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)Integrated Traffic Management System The purpose of a TMS is to optimize rail traffic flow by providing decision support to dispatchers as well as automated functions2 KB (179 words) - 17:27, 13 February 2023
- UC:IS:RINFReporting (category UC reported by SNCF Réseau) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)published by ERA RINF project team. The railML for RINF file will be produced by Infrastructure Managers from their national repository or by National Register3 KB (297 words) - 13:49, 13 March 2023
- UC:TT:ATimetableForACompetition (category UC reported by iRFP) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)corresponding infrastructure manager. This can be done by a unique attribute of the <track> elements (like code) or by a direction of the track in conjunction with16 KB (1,903 words) - 13:27, 13 March 2023
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category UC reported by IS) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)data exchange is the result of the planning process, so the data are provided by a specialized planning tool (e.g. ProSig). Further usages for inventory queries3 KB (367 words) - 13:47, 13 March 2023
- UC:IS:Track Geometry (category UC reported by ÖBB) (section Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen)track alignment and its required parameters. All of the above data is used by automatic guiding computers on the machines. Sensors on the machines produce5 KB (737 words) - 16:12, 15 April 2024