Search results
Jump to navigation
Jump to search
- UC:IS:MaintenancePlanning (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)infrastructure data from an asset management source system (e.g. DfA in Switzerland) to the maintenance planning system of the infrastructure manager. The data flow10 bytes (133 words) - 16:12, 3 February 2020
- UC:IS:CADForRailwaySignaling (category UC reported by RailComplete) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)infrastructure manager. interlocking This section serves to specify the required data regarding certain aspects. weekly daily big (station/yard) Signaling Geometry10 bytes (127 words) - 16:12, 3 February 2020
- UC:TT:ATimetableForACompetition (category UC reported by iRFP) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)such as services or minimum seating capacities. The background behind such a data exchange with railML® files is, especially at competitions of large production10 bytes (1,903 words) - 16:12, 3 February 2020
- UC:IS:PassengerInformationSystem (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)manager. The data flow is one-directional: It goes from the resource planning system to the passenger information system. There are two types of data flows:10 bytes (157 words) - 16:12, 3 February 2020
- UC:IS:NetworkStatement (category UC reported by SŽDC) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)are responsible for exporting all the required data. none This section serves to specify the required data regarding certain aspects. static (not changing)10 bytes (169 words) - 16:12, 3 February 2020
- UC:RS:OperationalSimulation (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)infrastructure Provision of rollingstock data by railway operator and/or manufacturer Import of rollingstock data into the simulation system (currently manual)10 bytes (146 words) - 16:12, 3 February 2020
- UC:IL:OperationAndControl (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)traffic of the interlocking plus converting it human readable) Station specific data are derived from the interlocking configuration and imported into the operation10 bytes (209 words) - 16:12, 3 February 2020
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category UC reported by IVU) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)timetable changes_ usecase. Change train data (commercial or operational) in a given validity Precondition: Import data contains commercial train information10 bytes (209 words) - 16:12, 3 February 2020
- UC:RS:TractionPowerSupplySimulation (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)simulation“. Provision of rollingstock data by railway operator and/or manufacturer Import of rollingstock data into the simulation system (currently manual)10 bytes (236 words) - 16:12, 3 February 2020
- UC:IS:NREReporting (category UC reported by ÖBB) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)SCHIG none This section serves to specify the required data regarding certain aspects. yearly whole data set (network) Statistics10 bytes (225 words) - 16:12, 3 February 2020
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category UC reported by IVU) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)perspective Rolling stock static Template:Complexity whole data set, or region mid term base data of commercial and operational trains (validity, train numbers10 bytes (355 words) - 16:12, 3 February 2020
- UC:IS:RailwayInfrastructureRecording (category UC reported by Bahnkonzept) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)based simulation. Further, measured data can be exported for utilization in other railway applications. Infrastructure data provided by the recording system10 bytes (335 words) - 16:12, 3 February 2020
- UC:IS:DriverAdvisorySystem (category UC reported by IS) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)may be updated at any time) together with a range of static or near-static data relating to the track, namely: topology, topography, asset locations and10 bytes (306 words) - 16:12, 3 February 2020
- UC:IS:RINFReporting (category UC reported by SNCF Réseau) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)fulfilling the functional requirements published by ERA for RINF data, including all concepts and data required. In a first step, considering the current non-acceptance10 bytes (297 words) - 16:12, 3 February 2020
- UC:IS:Speeddirectory (category UC reported by ÖBB) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)application system. This database system is receiver and sender of several data flows which connect the system with almost every important OEBB infrastructure10 bytes (117 words) - 16:12, 3 February 2020
- UC:IS:PositioningAndMap-Matching (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)application only uses map data, but does not provide geo data to any further applications. Therefore, data flows include the import of map data from the above mentioned10 bytes (367 words) - 16:12, 3 February 2020
- UC:TT:LongTermStrategicTimetabling (category UC reported by SMA) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)connections between trains) in the timetable is maintained in the data. Typically, the data produced in this use case is transferred to LTP systems using a10 bytes (523 words) - 16:12, 3 February 2020
- UC:IL:Simulation (category UC reported by Jernbanedirektoratet) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)- releaseTime, reserveTime Interlocking data rely heavily on infrastructure data. In fact, the interlocking data mostly are pointers to objects defined10 bytes (969 words) - 16:12, 3 February 2020
- UC:IS:CapacityPlanning (category UC reported by Jernbaneverket) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)analyze with internal and external databases that store the input and output data. Here we describe the most important of many processes and their belonging10 bytes (687 words) - 16:12, 3 February 2020
- UC:IS:Track Geometry (category UC reported by ÖBB) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)several thousand data elements per occurrence. The data represent the following views: Construction Geometry Measurement Contract data Operational characteristics10 bytes (737 words) - 16:12, 3 February 2020