Search results
Jump to navigation
Jump to search
- 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,571 words) - 18:13, 14 February 2022
- (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) - 11:04, 18 July 2022
- 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) - 12:28, 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 (59 words) - 17:50, 19 December 2019
- 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,055 words) - 11:48, 28 October 2024
- 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) - 12:29, 13 March 2023
- 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 (275 words) - 12:04, 23 September 2024
- 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) - 17:11, 27 June 2022
- 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 (628 words) - 11:09, 28 May 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 to14 KB (1,719 words) - 12:48, 30 September 2024
- and Rostering Related subschemas: IS RS Reported by: PSI For general information on use cases see UC:Use cases6 KB (691 words) - 13:06, 4 June 2024
- <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) - 13:07, 4 June 2024
- 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) - 12: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) - 14:45, 26 June 2024
- 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) - 13:43, 14 August 2024
- 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) - 14:49, 15 April 2024
- 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) - 12:51, 13 March 2023
- 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) - 12:53, 13 March 2023
- 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,724 words) - 11:42, 28 October 2024
- 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,609 words) - 15:55, 18 January 2024