Search results

and print material as well as ticketing and real-time information. This use case will focus on the definition of the minimum requirements for passenger

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 signal

type is called switchIL in railML interlocking subschema, whereas its counterpart in infrastructure is called switchIS. The switch is commonly used for

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 out

and track conditions. A list of use cases for the railML® infrastructure schema can be found on page Category:Use case (IS). →Main Article: Rollingstock

for a railML® use case: A timetable for a competition (call for proposals) Ausschreibungsfahrplan The use case describes a timetable which is transferred

Operational simulation; Betriebssimulation For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire

complete timetable for vehicle working scheduling_. Postcondition The train is changed within the validity of the change request, and unchanged outside.

This use case covers the ordering of slots by Railway Undertakings from Infrastructure Manager(s) and other managers of capacity. A related use case will

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 this

crossing whether this is physically needed or not. Subsequently the crossing as represented in the interlocking can have a position. In case of switch actuators

and Rostering   Related subschemas: IS RS  Reported by: PSI For general information on use cases see UC:Use cases

<rostering> is included, the element <rollingstock> is also required The elements <infrastructure> and <rollingstock> are master data for the use case "passenger

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 currently

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"

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 excluded

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. Please

Information Category: Topology (origin: railML IS schema or classic track plan) Cable plan (origin: railML IS schema or classic track plan) infrastructure

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://eulynx

regular accuracy towards the measured location is +/- 5m (locationAccuracy="5"). UNISIG-baseline 3 is in use (mVersion="32"). Corresponding railML® description: