Search results

Exchange of formation data; Austausch von Wagenreihungen/Behängungsdaten The usecase describes the exchange of data between a software tool for short term

being framed. Do not edit manually! Certification: Compliance with the description in the Wiki is relevant for fulfilling the requirements (see below). Semantics:

vehicle. The activities mentioned can be carried out one after the other. Description of parallel work is not included in this use case. For the purposes of

apply to train coupling, sharing and "strengthening". See corresponding descriptions for further information.) Usage of tTimeScope="earliest" / ="latest"

RailTopoModel® compliant railway network description enriched with the design layout and infrastructure description including also the essential information

Maintenance Planning; Wartungsplanung The application focuses the transfer of infrastructure data from an asset management source system (e.g. DfA in Switzerland)

numberInStack="1" orientation="horizontal" usedForDirection="both"> <rail3:designator description="" entry="" register=""/> <rail3:hasCommand entityCode="" ref=""/> <rail3:hasIndication

Network Statement; Network Statement The Network Statement covers the requirements for access and use of the rail network (route network) of the infrastructure

Hardware and cable plan; Hardware und Kabelplan Cable plan Parts Lists Number of field element controller Hardware indoor, outdoor (number of point machines

Passenger Information System; Passagierinformationssystem The application focuses the transfer of timetable, traction and topology information from the

Traffic Management Plan The purpose of a TMS is to optimize rail traffic flow by providing decision support to dispatchers as well as automated functions

not be used as leading information, but rather as derived additional description. (obligatory; xs:integer; minInclusive: 0; maxInclusive: 15) *Notice:

downleft-rightup: Description of a logical position of a simple crossing within a route path from the lower left to upper right upleft-rightdown: Description of a logical

short name for the train clearance gauges in latin letters Children <description>: Internationalized name of the clearance gauge. <validFor>: Gives indication

Operation and Control; Betrieb und Kontrolle The operation and control systems for one railway operating company are normally provided by one selected

element Generic:vehicleBrakes of railML® version 3.2   Documentation Description of the type of vehicle brakes and their application as brake effort or

for element Generic:trainBrakes of railML® version 3.2   Documentation Description of the type of brakes within the formation and their application as brake

Main items Detailed description Topology Inclusion of use case "Schematic Track Plan" (SCTP) Track IS:Track

Passenger Information Inside the Train; Fahrgastinformation im Zug The use case describes the data of the timetable, which will be imported in a real time

number of the information. (optional; xs:nonNegativeInteger), description: The verbal description of the information. (optional; xs:string), normalState: The

number of the information. (optional; xs:nonNegativeInteger), description: The verbal description of the information. (optional; xs:string), normalState: The

[Wikipedia] Subschema infrastructure Parents* polygon Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (0..1)

Driver Advisory System (DAS); Fahrerassistentsystem The Driver Advisory System (DAS) is an on-train driver support system which advises a driver on the

Positioning and Map-Matching; Positionierung und Kartenabgleich With a train-borne positioning system, which is a multi-sensor on-board positioning device

Subschema generic Parents* hasCommunicationSettings Children None Attributes: description: should be interpreted in its elements' context, substantiates the name

Topology (schematic drawing) on micro, meso and macroscopic level, with description of data (values and position) Timetable graph, Platform occupation diagram

select such a group and configure the toplogy would be useful. There is no description of this as of today. If RailML is introduced, the system will need to

DirectPositionType. Subschema infrastructure Parents* gmlLocations Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (1..1)

[Wikipedia]. Subschema infrastructure Parents* circle Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (1..1)

Generic:hasName of railML® version 3.2   Documentation particular name and description of the system asset dependent on language Subschema generic Parents* controller

Railway Infrastructure Recording; Erfassung der Schieneninfrastruktur There are several systems and projects that follow the aim to record and visualize

Exchange of planning parameters for interlocking with suppliers; Austausch von Planungsparametern für Stellwerke mit Anbietern All the planning parameters

element Generic:objectName of railML® version 3.2   Documentation name and description of the object dependent on the language Subschema generic Parents* combinedRoute

*.xml or *.railml, that is the question. The answer is: Both. It was not a convention from the beginning, but best practice should be: *.railml shall only

number of the information. (optional; xs:nonNegativeInteger), description: The verbal description of the information. (optional; xs:string), normalState: The

downleft-rightup: Description of a logical position of a simple crossing within a route path from the lower left to upper right upleft-rightdown: Description of a logical

number of the information. (optional; xs:nonNegativeInteger), description: The verbal description of the information. (optional; xs:string), normalState: The

two. Subschema infrastructure Parents* gmlLocations Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (0..1)

tunnelGateIS, underCrossing, weightLimit Children None Attributes: description: description of the external identifier or reference, providing basic information

underCrossing, weightLimit Children None Attributes: description: Human-readable, more detailed description as addition to the entry. It should give additional

element Generic:assetName of railML® version 3.2   Documentation name and description of the asset dependent on the language Subschema generic Parents* derailerIL

Posession Management   Possession is a takeover of responsibility for a part of railway network from the “train operator” to the PICOP (Person In Charge

Site preparation data for Signal Controlled Warning Systems (SCWS); Daten zur Standortvorbereitung für signalkontrollierte Warnsysteme An SCWS is a system

Import complete timetable for vehicle working scheduling and vehicle workings; Umlaufbildung Fahrzeuge Jahresfahrplan A complete timetable shall be imported

passable during traversal of a vessel. (optional; xs:duration), description: Description of the logic. (optional; xs:string), elementNumber: element number

interlocking is depending on the way of control. In the generic type description the following information can be included: @isControlType – This describes

will be automatically relocked again. (optional; xs:duration), description: Description of the logic. (optional; xs:string), id: unique identifier (optional;

initiated or triggered from interlocking. (optional; xs:duration), description: Description of the logic. (optional; xs:string), id: unique identifier (optional;

ref: a reference to an external element (optional; xs:string), description: description of the external identifier or reference, providing basic information

be tolerated due to running self-test. (optional; xs:duration), description: Description of the logic. (optional; xs:string), elementNumber: element number

<rail3:etcsLevelTransition id="8c37ad44-990c-4130-8e16-ebe685f63db5"> <rail3:name description="ETCS Level Transition: L1LS -> L2" language="EN" name="etcsLevelTransition_BON"/>

path (given by OCPs) Station Tracks are used to provide a more detailed description which is the desired location inside the Operating Point. Station Track:

Guides and Developer Pages   This page provides an overview over pages from the Dev-namespace that offer User Guides, information for developers and connected

schema! Subschema infrastructure Parents* gmlLocations Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (1..1)

vehicle, vehiclePart, weightLimit, workZone Children None Attributes: description: description of the designator, which can be used to provide basic information

RS:brakes of railML® version 3.2 UML-visualization of RS Documentation The description and technical data of the installed brake system of the vehicle. Subschema

line network Construction: assets along the track / line Track layout description ETCS level transition locations Points Signals BaliseGroups (if available

schema! Subschema infrastructure Parents* gmlLocations Children description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (0..1)

release is indicated to the operator. (optional; xs:duration), description: Description of the logic. (optional; xs:string), elementNumber: element number

RS:tractiveEffort of railML® version 3.2 UML-visualization of RS Documentation The description of the tractive effort of this engine as x-y-curve vs. speed. Subschema

IL:deactivatedBy of railML® version 3.2 UML-visualization of IL Documentation The description of deactivation conditions for this level crossing. Subschema interlocking

RS:brakeEffort of railML® version 3.2 UML-visualization of RS Documentation The description of the resulting brake effort for regular brake application as x-y-curve

direction. Note that the linear ways should form a complete routable description of the watercourse [openStreetMap]. road: unknown road type secondaryRoad:

Description: Infrastructure Managers (IM) wish to represent their railway system in terms of standardised data types. Eulynx collects the types and attributes

IL:activationCondition of railML® version 3.2 UML-visualization of IL Documentation Description of the possible activation conditions of this level crossing. Subschema

Subschema generic Parents* hasCommunicationSettings Children None Attributes: description: should be interpreted in its elements' context, substantiates the name

Parents* hasHmiIndication, hasOperatorCommand Children None Attributes: description: should be interpreted in its elements' context, substantiates the name

Asset Status Representation for TMS Traffic Management Systems (TMS) consider various sorts of input data for the calculation of the current traffic situation

IL:routeEntry of railML® version 3.1 UML-visualization of IL Documentation Description of the start point of the route. This is normally a signal. Subschema

IL:overlapReleaseTimer of railML® version 3.1 UML-visualization of IL Documentation Description of overlap release timer (duration, start condition) Subschema interlocking

IL:deactivatedBy of railML® version 3.1 UML-visualization of IL Documentation The description of deactivation conditions for this level crossing. Subschema interlocking

Rtm4railml Parents* network Children networkResource (0..*) Attributes: descriptionLevel: specifies the network aggregation, such as micro, macro or meso

version 3.1 UML-visualization of IL Documentation Reference to physical description of level crossing interface with list of commands to the field and notifications

IL:interface of railML® version 3.1 UML-visualization of IL Documentation Description of a physical interface with definition of the information to be exchanged

IL:routeExit of railML® version 3.1 UML-visualization of IL Documentation Description of the route destination point. In most cases the route destination is

version 3.2 UML-visualization of IL Documentation Reference to physical description of level crossing interface with list of commands to the field and notifications

IL:activationCondition of railML® version 3.1 UML-visualization of IL Documentation Description of the possible activation conditions of this level crossing. Subschema

IL:interface of railML® version 3.2 UML-visualization of IL Documentation Description of a physical interface with definition of the information to be exchanged

IL:routeEntry of railML® version 3.2 UML-visualization of IL Documentation Description of the start point of the route. This is normally a signal. Subschema

IL:overlapReleaseTimer of railML® version 3.2 UML-visualization of IL Documentation Description of overlap release timer (duration, start condition) Subschema interlocking

IL:routeExit of railML® version 3.2 UML-visualization of IL Documentation Description of the route destination point. In most cases the route destination is

Réseau nl-BE: Netverklaring fr-BE: Infrabel nl-BE: Infrabel fr-BE: courte description et la source nl-BE: korte beschrijving en de bron Belgium () ENEE ENEE

range of signal aspects can be categorised in several groups for the description of their meaning – the so-called @genericAspect. There are the following

This article explains basic concepts of handling formation orientation within the timetable subschema. Dieser Artikel erklärt die grundlegenden Konzepte

downleft-rightup: Description of a logical position of a simple crossing within a route path from the lower left to upper right upleft-rightdown: Description of a logical

IL:reasonForConflict of railML® version 3.1 UML-visualization of IL Documentation Description of the reason for the conflict. Subschema interlocking Parents* conflictingRoute

InfrastructureInstallations OperationalPlanning Rollingstock SecondaryCauses, reasonDescription: May be used to provide a textual reasoning for the cancellation intended

IL:reasonForConflict of railML® version 3.2 UML-visualization of IL Documentation Description of the reason for the conflict. Subschema interlocking Parents* conflictingRoute

IL:routeActivationSection of railML® version 3.1 UML-visualization of IL Documentation Description of the route activation, i.e. automatic setting or locking when the route

IL:routeActivationSection of railML® version 3.2 UML-visualization of IL Documentation Description of the route activation, i.e. automatic setting or locking when the route

three <netElement> objects are fully covered by the <line>. The resulting description of the railway line looks like this: <lines> <line id="lin01" lineCategory="other:CE"

used to direct vehicles from one track to another track. To separate the description of the infrastructure topology from its construction, railML® 3 is based

vehicleManufacturer, vehicleOperator, weightLimit Children None Attributes: description: should be interpreted in its elements' context, substantiates the name

element Generic:vehicleBrakes of railML® version 3.2   Documentation Description of the type of vehicle brakes and their application as brake effort or

for element Generic:trainBrakes of railML® version 3.2   Documentation Description of the type of brakes within the formation and their application as brake

not be used as leading information, but rather as derived additional description. (obligatory; xs:integer; minInclusive: 0; maxInclusive: 15) *Notice:

elements' context (e.g. signal/name, vehicle/name) (obligatory; xs:string), description: should be interpreted in its elements' context, substantiates the name

Infrastructure The railML® Infrastructure subschema is focused on the description of the railway network infrastructure including all its various facets

direction. Note that the linear ways should form a complete routable description of the watercourse [openStreetMap]. road: unknown road type secondaryRoad:

Rtm4railml Parents* network Children networkResource (0..*) Attributes: descriptionLevel: This attribute is not documented in the schema! (optional; xs:string)