Search results
Jump to navigation
Jump to search
- main element for this schema is <rollingstock>, which is the root for data about any rolling stock. It is intended to use this data schema for vehicle3 KB (458 words) - 17:20, 29 November 2023
- Infrastructure Reported by: Bahnkonzept For general information on use cases see UC:Use cases3 KB (335 words) - 13:48, 13 March 2023
- railML® for RINF Reporting; railML® für RINF Meldung This use case aims at providing a railML3 file, fulfilling the functional requirements published by3 KB (297 words) - 13:49, 13 March 2023
- UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers (category Use case (IS)) (section Use case / Anwendungsfall)software), have to be given to the supplier. The content of the data exchange is the result of the planning process, so the data are provided by a specialized3 KB (367 words) - 13:47, 13 March 2023
- Advisory System (DAS); Fahrerassistentsystem The Driver Advisory System (DAS) is an on-train driver support system which advises a driver on the most energy-efficient3 KB (306 words) - 13:48, 13 March 2023
- positioning system, which is a multi-sensor on-board positioning device, the train can determine its position itself. The digital map is a key component of such3 KB (367 words) - 13:49, 13 March 2023
- The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure state. It is important that any4 KB (523 words) - 11:14, 18 July 2022
- The objective of a possession is to ensure safe construction/maintenance works on the railway infrastructure. The safety is ensured by a set of safety measures:3 KB (394 words) - 12:02, 18 July 2022
- infrastructure is pulled from an asset management database. Future infrastructure is designed by hand from technical drawings. The timetable model is tested either5 KB (687 words) - 13:46, 13 March 2023
- verify the results of the work in very detailed manner. The track geometry use case deals with two major data flows between two major components. They are5 KB (737 words) - 16:12, 15 April 2024
- Infrastructure (section Infrastructure (IS))IS root element — IS use cases — Concepts & examples The railML® Infrastructure subschema is focused on the description of the railway network infrastructure3 KB (288 words) - 18:47, 20 March 2024
- Interlocking Rollingstock The use case comprises static and dynamic (status) asset data. For infrastructure, the focus is only on static data. Small (operational10 KB (129 words) - 16:01, 27 September 2023
- Current UML visualization A list of use cases for railML's interlocking scheme can be found here Category:Use_case_(IL). Interlocking Concepts — explanations1 KB (153 words) - 18:26, 3 November 2023
- electrical simulation is not possible with the necessary accuracy without simulating the process of railway operation. Thus this use case is always an addon2 KB (236 words) - 13:43, 13 March 2023
- Description of parallel work is not included in this use case. For the purposes of this use case, the vehicle group is represented by vehicle types that6 KB (926 words) - 17:00, 4 December 2023
- capacity operational simulation tools use their own internal generic interlocking (table) model. Thus this use case does not require a interlocking table7 KB (959 words) - 14:06, 7 December 2023
- IL:derailerIL (category Pages using Tabber parser tag)preferred position is the derailing one, which is automatically assumed after use. In addition the relation to the switch pt_swi03 is marked causing an5 KB (484 words) - 12:44, 27 May 2022
- this use case is the process description and the minimum data content for the timetable data exchange. The used data format is EDIFACT. The use case shall4 KB (592 words) - 18:06, 7 December 2023
- (sofern der Art entsprechend) Erforderliche Qualifikationen Der Use Case baut auf dem Use Case Fahrplanauskunft auf, das heißt für Dienste, die auf einer Fahrt3 KB (410 words) - 12:04, 18 July 2022
- offers a number of Use Cases. A Guideline to implementing Use Cases can be found under Dev:Use cases. In contrast to railML® 2, railML® 3 is not supposed to12 KB (1,475 words) - 15:28, 15 April 2024
- and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger5 KB (751 words) - 13:28, 13 March 2023
- IL:conflictingRoute (category Pages using Tabber parser tag)value is used in case of any TVD section of the route is also used by the conflicting one. ConflictingHeadProtection – This value is used in case any signal5 KB (573 words) - 12:09, 28 May 2022
- IL:switchIL (category Pages using Tabber parser tag)type is called switchIL in railML interlocking subschema, whereas its counterpart in infrastructure is called switchIS. The switch is commonly used for19 KB (1,714 words) - 09:32, 3 May 2023
- with us. To learn where to find, how to use and how to contribute use cases see Dev:Use cases. While use cases follow a top-down approach, starting out5 KB (674 words) - 15:49, 15 April 2024
- Main Page (section Infrastructure (IS))and track conditions. A list of use cases for the railML® infrastructure schema can be found on page Category:Use case (IS). →Main Article: Rollingstock10 KB (1,041 words) - 10:56, 2 May 2024
- for a railML® use case: A timetable for a competition (call for proposals) Ausschreibungsfahrplan The use case describes a timetable which is transferred16 KB (1,903 words) - 13:27, 13 March 2023
- Operational simulation; Betriebssimulation For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire1 KB (146 words) - 13:29, 13 March 2023
- UC:TT:AdoptVehicleWorkingSchedulingToTimetableChanges (category Use case (TT)) (section Use case / Anwendungsfall)complete timetable for vehicle working scheduling_. Postcondition The train is changed within the validity of the change request, and unchanged outside.2 KB (209 words) - 18:11, 27 June 2022
- This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will2 KB (273 words) - 13:26, 13 March 2023
- attributes. In case of consuming "wrong styled" id values the importing software is not required to extract semantics encoded in the id value. The use of this5 KB (463 words) - 12:22, 3 November 2023
- IL:movableCrossing (category Pages using Tabber parser tag)crossing whether this is physically needed or not. Subsequently the crossing as represented in the interlocking can have a position. In case of switch actuators15 KB (1,510 words) - 19:13, 14 February 2022
- and Rostering Related subschemas: IS RS Reported by: PSI For general information on use cases see UC:Use cases6 KB (691 words) - 13:28, 13 March 2023
- <rostering> is included, the element <rollingstock> is also required The elements <infrastructure> and <rollingstock> are master data for the use case "passenger9 KB (677 words) - 18:10, 27 June 2022
- commercial train elements.) A better modelling for this aspect is, in the author’s opinion, to use the concept of commercial trains in a different way than currently6 KB (688 words) - 13:26, 13 March 2023
- exchange format. This use case concerns the exchange of engineering data for tailoring an interlocking to fit a station. This use case focuses on "legacy"11 KB (828 words) - 13:25, 13 March 2023
- IL:reasonForConflict (category Pages using Tabber parser tag)value is used in case any signal that shall provide flank/head protection to either route is used as route destination for the other route, which is excluded520 bytes (9 words) - 18:50, 19 December 2019
- Dev:Use case example/old (category Use case (unknown subschema)) (section Use case / Anwendungsfall)good use case. For an actual example see UC:IS:Schematic Track Plan. To get more information on use cases and how to describe them, see Dev:Use cases. Please2 KB (220 words) - 16:25, 4 December 2023
- Information Category: Topology (origin: railML IS schema or classic track plan) Cable plan (origin: railML IS schema or classic track plan) infrastructure1 KB (119 words) - 13:51, 13 March 2023
- UC:IL:EulynxDataPreparationInterlocking (category Use case (IL))reflect the as-built situation. Please refer to the linked use cases that cover the Eulynx use case. For detailed information please refer to the website https://eulynx3 KB (450 words) - 17:54, 27 June 2022
- IS:baliseGroup (category Pages using Tabber parser tag)regular accuracy towards the measured location is +/- 5m (locationAccuracy="5"). UNISIG-baseline 3 is in use (mVersion="32"). Corresponding railML® description:19 KB (2,555 words) - 16:55, 18 January 2024
- IL:interlocking (category Pages using Tabber parser tag)register used. In case there is no officially used register the project-specific one shall be named with a leading underscore. The @id attribute is the “machine4 KB (493 words) - 10:38, 31 May 2021
- UC:IL:InterlockEngineeringForSignallingWithinJBV (category Use case (IL)) (section Use case / Anwendungsfall)The most normal in Norway is that whenever a change is made to the signalling system, the entire station is updated. This is defined as one interlocking5 KB (558 words) - 13:53, 13 March 2023
- UC:TT:ImportCompleteTimetableForVehicleWorkingSchedulingAndVehicleWorkings (category Use case (TT)) (section Use case / Anwendungsfall)working data Typically, the import is done manually using a file based interface. Common Infrastructure: the import uses elements from mesoscopic and macroscopic3 KB (355 words) - 18:11, 27 June 2022
- UC:IL:SitePreparationDataForSignalControlledWarningSystems (category Use case (IL)) (section Use case / Anwendungsfall)signalkontrollierte Warnsysteme An SCWS is a system used to warn working gangs on used tracks that a train is arriving and that they have to stop their4 KB (571 words) - 13:51, 13 March 2023
- IS:mileageChange (category Pages using Tabber parser tag)This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further2 KB (228 words) - 13:18, 17 April 2024
- features and therefore is not designed backward compatible. The most fundamental difference is difficult to recognize at the surface: It is based on RailTopoModel®3 KB (403 words) - 15:46, 15 April 2024
- about restrictions concerning the infrastructure shall not be part of this use case ITMS. On the other hand a restriction of the infrastructure can be the16 KB (1,744 words) - 18:21, 13 May 2024
- IL:tvdSection (category Pages using Tabber parser tag)section. It shall be used in case @isBerthingTrack is set to true. Within the simple example there are different kind of TVD sections. Here is a platform track7 KB (829 words) - 15:11, 27 May 2022
- interlockings has to be incorporated into the operation and control systems. They uses the interlocking to operate elements get element status schedule and manage2 KB (209 words) - 13:52, 13 March 2023
- RTM:anchor (category Pages using Tabber parser tag)<IS:mileageChange> page for the alternative approach, relevant for when there is a need for an explicit IS element. See the discussion in forum. Below you can see the source3 KB (269 words) - 17:11, 19 April 2024