Search results
Jump to navigation
Jump to search
- 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
- Dev:Use case example/old (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)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}})10 bytes (220 words) - 16:47, 4 December 2023
- UC:IL:EulynxDataPreparationInterlocking (category UC reported by EULYNX)protection<br />The result of this analysis is called a data platform, for it is more than a simple static data dictionary, that acts as input to the railML interlocking10 bytes (450 words) - 16:12, 3 February 2020
- application of data exchange between at least two IT systems in the railway domain, where railML® can be used as a format and language for the data to be exchanged10 bytes (287 words) - 16:31, 3 February 2020
- UC:Use case example (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)The headline is made with Template: UC title (type {{UC title}}) What is the application behind the use case? Which data in general is required? Which kind10 bytes (263 words) - 21:42, 23 January 2020
- UC:TT:SlotOrdering (category UC reported by SMA) (section Characterizing Data / Charakterisierung der Daten)related use case will be the slot offer by the Infrastructure Manager. The data has to be provided by the Railway Undertaking to the relevant Infrastructure10 bytes (273 words) - 16:12, 3 February 2020
- UC:IL:HardwareAndCablePlan (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)classic track plan) infrastructure This section serves to specify the required data regarding certain aspects. static (not changing) on demand big (station/yard)10 bytes (119 words) - 16:12, 3 February 2020
- UC:IS:RailwayInfrastructureVisualisation (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)infrastructure shall be fed back into a visualization software. The infrastructure data to be modified contains railway topology, track and operational elements10 bytes (180 words) - 16:12, 3 February 2020
- UC:IS:Timetabling (category UC reported by ProRail) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)tractive power, braking characteristics. These data comes from the wagon keepers. Data flows: Basic infra data: Engineering dept -> timetabling and capacity10 bytes (343 words) - 16:12, 3 February 2020
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category UC reported by IS) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)possible. Import into planning tool: geo data, existing planning data, inventory data Export of planning tool: planning data, handing-over to the supplier (by10 bytes (367 words) - 16:12, 3 February 2020
- UC:IS:CaptureSchematicVisualisationInformationOfTrackAssets (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)Parties who exchange railML data for engineering purpose will want to make prints or displays where infrastructural data always appear in the same relative10 bytes (383 words) - 16:12, 3 February 2020
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (category UC reported by Thales Austria) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)Inputs: Inputs for the data preparation of a SCWS are the topology data from the interlocking system. These interlocking data (IxL-data) describe the track-topology10 bytes (571 words) - 16:12, 3 February 2020
- UC:IS:Railway Simulation Laboratory (category UC reported by Czech Technical University in Prague (ČVUT)) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)a complex data model of the model railway infrastructure to become a common base for the related abovementioned applications. The current data flows – concerning10 bytes (427 words) - 16:12, 3 February 2020
- UC:IS:Schematic Track Plan (category UC reported by JBD) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)depicted in the following figure: The infrastructure manager uses data from their own data bases to visualize them in the mentioned different types of maps10 bytes (198 words) - 16:12, 3 February 2020
- UC:TT:TAF/TAP TSI (category UC reported by ERA) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)case is the process description and the minimum data content for the timetable data exchange. The used data format is EDIFACT. The use case shall cover the10 bytes (592 words) - 16:12, 3 February 2020
- UC:IL:InterlockEngineeringForSignallingWithinJBV (category UC reported by Jernbaneverket) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)time used. This section serves to specify the required data regarding certain aspects. The data change every time some work is done on a station or location10 bytes (558 words) - 16:12, 3 February 2020
- UC:TT:TimetableInformation (category UC reported by HaCon) (section Characterizing Data / Charakterisierung der Daten)for passenger information. The required data includes stations, timetables, service categories. Furhtermore, data regarding links among stops and interchange10 bytes (751 words) - 16:12, 3 February 2020
- UC:TT:FGIInTrain (category UC reported by Interautomation) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)imported in the RTPIS or the AVMS. According to the data contained in the timetable import, data amount and data complexity can vary. At least this use case needs10 bytes (677 words) - 16:12, 3 February 2020
- UC:IL:InterlockingEngineering (category UC without specified reporter) (section Data Flows and Interfaces / Datenflüsse und Schnittstellen)conversion of railML data, rather than picking data from paper plans, into the suppliers tool chain will reduce cost. Better still, if the input data are known to10 bytes (828 words) - 16:12, 3 February 2020
- The timetable subschema is part of the complete railML® schema providing a data structure in XML for the exchange of any kind of timetable for operational2 KB (260 words) - 21:06, 22 January 2024