Search results
Jump to navigation
Jump to search
- Dev:Use case example/old (category UC without specified reporter) (section Which views are represented by the data (focus)?)Template: UC focus (type {{UC focus}}) Please list all elements that are part of the data in this use case. The headline is made with Template: UC elements10 bytes (220 words) - 16:47, 4 December 2023
- eporter=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} For10 bytes (1,035 words) - 21:45, 23 January 2020
- UC:TT:SlotOrdering (category UC reported by SMA) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:SlotOrdering in The railML® 3 wiki.10 bytes (273 words) - 16:12, 3 February 2020
- UC:IL:HardwareAndCablePlan (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IL:HardwareAndCablePlan in The link=norailML® 3 wiki.10 bytes (119 words) - 16:12, 3 February 2020
- UC:IS:RailwayInfrastructureVisualisation (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:RailwayInfrastructureVisualisation in The railML® 3 wiki.10 bytes (180 words) - 16:12, 3 February 2020
- UC:IS:Timetabling (category UC reported by ProRail) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:Timetabling in The railML® 3 wiki.10 bytes (343 words) - 16:12, 3 February 2020
- UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets in The railML® 3 wiki.10 bytes (383 words) - 16:12, 3 February 2020
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category UC reported by IS) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers in The link=norailML® 3 wiki.10 bytes (367 words) - 16:12, 3 February 2020
- UC:TT:TimetableInformation (category UC reported by HaCon) (section Which views are represented by the data (focus)?)material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger information.10 bytes (751 words) - 16:12, 3 February 2020
- UC:TT:TAF/TAP TSI (category UC reported by ERA) (section Which views are represented by the data (focus)?)at least for 12 months after such data have expired." This use case will focus on the definition of the minimum requirements for passenger information.10 bytes (592 words) - 16:12, 3 February 2020
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (category UC reported by Thales Austria) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IL:SitePreparationDataForSignalControlledWarningSystems in The railML® 3 wiki.10 bytes (571 words) - 16:12, 3 February 2020
- UC:IS:Railway Simulation Laboratory (category UC reported by Czech Technical University in Prague (ČVUT)) (section Which views are represented by the data (focus)?)students with different railway issues). At present, our project is mainly focused to develop and implementing new technology of intelligent traffic system10 bytes (427 words) - 16:12, 3 February 2020
- UC:IS:Schematic Track Plan (category UC reported by JBD) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:Schematic Track Plan in The railML® 3 wiki.10 bytes (198 words) - 16:12, 3 February 2020
- UC:IL:InterlockEngineeringForSignallingWithinJBV (category UC reported by Jernbaneverket) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IL:InterlockEngineeringForSignallingWithinJBV in The railML® 3 wiki.10 bytes (558 words) - 16:12, 3 February 2020
- UC:TT:FGIInTrain (category UC reported by Interautomation) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:FGIInTrain in The railML® 3 wiki.10 bytes (677 words) - 16:12, 3 February 2020
- UC:IL:InterlockingEngineering (category UC without specified reporter) (section Which views are represented by the data (focus)?)etc) (origin: Railway regulations or other plain text requirements) The focus should be on data reliability because IL and IS data will be used for producing10 bytes (828 words) - 16:12, 3 February 2020
- UC:IS:CADForRailwaySignaling (category UC reported by RailComplete) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:CADForRailwaySignaling in The railML® 3 wiki.10 bytes (127 words) - 16:12, 3 February 2020
- UC:IS:MaintenancePlanning (category UC without specified reporter) (section Which views are represented by the data (focus)?)Maintenance Planning; Wartungsplanung The application focuses the transfer of infrastructure data from an asset management source system (e.g. DfA in Switzerland)10 bytes (133 words) - 16:12, 3 February 2020
- UC:IL:OperationAndControl (category UC without specified reporter) (section Which views are represented by the data (focus)?)from page UC:IL:OperationAndControl in The railML® 3 wiki.10 bytes (209 words) - 16:12, 3 February 2020
- UC:IS:PassengerInformationSystem (category UC without specified reporter) (section Which views are represented by the data (focus)?)Passenger Information System; Passagierinformationssystem The application focuses the transfer of timetable, traction and topology information from the resource10 bytes (157 words) - 16:12, 3 February 2020
- UC:RS:OperationalSimulation (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:RS:OperationalSimulation in The railML® 3 wiki.10 bytes (146 words) - 16:12, 3 February 2020
- UC:IS:NetworkStatement (category UC reported by SŽDC) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:NetworkStatement in The link=norailML® 3 wiki.10 bytes (169 words) - 16:12, 3 February 2020
- UC:RS:TractionPowerSupplySimulation (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:RS:TractionPowerSupplySimulation in The link=norailML® 3 wiki.10 bytes (236 words) - 16:12, 3 February 2020
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category UC reported by IVU) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges in The railML® 3 wiki.10 bytes (209 words) - 16:12, 3 February 2020
- UC:IS:RINFReporting (category UC reported by SNCF Réseau) (section Which views are represented by the data (focus)?)In this article there is information missing with respect to the data focus. Please help improving the railML® wiki by filling the gaps. Possibly, you10 bytes (297 words) - 16:12, 3 February 2020
- UC:IS:NREReporting (category UC reported by ÖBB) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:NREReporting in The link=norailML® 3 wiki.10 bytes (225 words) - 16:12, 3 February 2020
- UC:IS:RailwayInfrastructureRecording (category UC reported by Bahnkonzept) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:RailwayInfrastructureRecording in The railML® 3 wiki.10 bytes (335 words) - 16:12, 3 February 2020
- UC:IS:DriverAdvisorySystem (category UC reported by IS) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:DriverAdvisorySystem in The railML® 3 wiki.10 bytes (306 words) - 16:12, 3 February 2020
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category UC reported by IVU) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings in The railML® 3 wiki.10 bytes (355 words) - 16:12, 3 February 2020
- UC:IS:Speeddirectory (category UC reported by ÖBB) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:Speeddirectory in The railML® 3 wiki.10 bytes (117 words) - 16:12, 3 February 2020
- UC:IS:PositioningAndMap-Matching (category UC without specified reporter) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:PositioningAndMap-Matching in The railML® 3 wiki.10 bytes (367 words) - 16:12, 3 February 2020
- UC:TT:LongTermStrategicTimetabling (category UC reported by SMA) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:LongTermStrategicTimetabling in The railML® 3 wiki.10 bytes (523 words) - 16:12, 3 February 2020
- UC:IL:Simulation (category UC reported by Jernbanedirektoratet) (section Which views are represented by the data (focus)?)does not require a interlocking table. This distinguishes this IL UC from other IL UC. A route description with attributes (primarily timings and speed)10 bytes (969 words) - 16:12, 3 February 2020
- UC:IS:CapacityPlanning (category UC reported by Jernbaneverket) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:CapacityPlanning in The railML® 3 wiki.10 bytes (687 words) - 16:12, 3 February 2020
- UC:IS:ETCS track net (category UC reported by Thales) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:ETCS track net in The railML® 3 wiki.10 bytes (441 words) - 16:12, 3 February 2020
- UC:TT:ExchangeOfFormationData (category UC reported by iRFP) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:ExchangeOfFormationData in The railML® 3 wiki.10 bytes (688 words) - 16:12, 3 February 2020
- UC:IS:Track Geometry (category UC reported by ÖBB) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:Track Geometry in The railML® 3 wiki.10 bytes (737 words) - 16:12, 3 February 2020
- UC:TT:ATimetableForACompetition (category UC reported by iRFP) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:TT:ATimetableForACompetition in The railML® 3 wiki.10 bytes (1,903 words) - 16:12, 3 February 2020
- UC:IS:Asset status representation (category UC reported by DLR for In2Rail project) (section Which views are represented by the data (focus)?)comprises static and dynamic (status) asset data. For infrastructure, the focus is only on static data. Small (operational point) Big (station/yard) Whole10 bytes (129 words) - 16:12, 3 February 2020
- UC:IS:PosessionManagement (category UC without specified reporter) (section Which views are represented by the data (focus)?)page UC:IS:PosessionManagement in The railML® 3 wiki.10 bytes (400 words) - 12:03, 18 July 2022
- UC:IS:ExchangeOfLogicalTrainPositions (category UC reported by Siemens Mobility) (section Which views are represented by the data (focus)?)🗒️ This page is mirrored from page UC:IS:ExchangeOfLogicalTrainPositions in The railML® 3 wiki.10 bytes (1,443 words) - 11:51, 18 July 2022
- UC:TT:LongTermCirculationPlanning (category UC without specified reporter)exchanged with other systems that further enrich, refine or process it. The focus here is on the so-called planning aspect. This means that no assignment of10 bytes (926 words) - 14:45, 30 November 2023
- UC:TT:RunTimeCalculationInput (category UC reported by Jernbanedirektoratet/Bane NOR)simulation tools or driver advisory systems. The typically necessary data for this UC can be separated into 3 general domains: Infrastructure (RTCI-a) Rollingstock10 bytes (860 words) - 16:39, 8 June 2023
- a few vehicles and formations) Which views are represented by the data (focus)? Long term planning (starting typically 1..5 years in future with a duration16 KB (2,372 words) - 16:07, 12 November 2021
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This622 bytes (61 words) - 16:58, 23 June 2016
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This571 bytes (54 words) - 16:46, 14 September 2023
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This600 bytes (57 words) - 16:47, 14 September 2023
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This639 bytes (61 words) - 16:56, 23 June 2016
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This647 bytes (58 words) - 13:22, 13 March 2023
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This617 bytes (58 words) - 13:23, 13 March 2023
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This613 bytes (61 words) - 16:57, 23 June 2016
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This617 bytes (58 words) - 13:22, 13 March 2023
- >|title=}} {{UC title}} {{UC description}} {{UC flows}} {{UC interference}} {{UC data}} {{UC update}} {{UC complexity}} {{UC focus}} {{UC elements}} This721 bytes (68 words) - 17:16, 22 September 2016