Search results

railML® version 3.2 UML-visualization of generic Documentation name and description of the asset dependent on the language Subschema generic Parents* derailerIL

format and language for the data to be exchanged. The aim of the use case description is to formulate requirements on the technical implementation of the data

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

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

railML® version 3.2 UML-visualization of generic Documentation name and description of the object dependent on the language Subschema generic Parents* combinedRoute

Downloading and using railML® This Guideline is intended to help you through the first steps in downloading and using railML®. If you are not yet registered

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

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

trainRadio, tunnelGateIS, underCrossing, weightLimit Children None Attributes: description: This attribute is not documented in the schema! (optional; xs:string)

typicalTimeToOpen="P1D"> <rail3:designator description="" entry="" register=""/> <rail3:assetName description="" language="EN" name=""/> <rail3:belongsToOperationalPoint

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:routeExit of railML® version 3.2 UML-visualization of IL Documentation Description of the route destination point. In most cases the route destination is

❗ Please note, that this page is made for saving ideas, concepts and descriptions for the upcoming railML® 3.2 Timetable scheme. This page shall be replaced

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

isSignalized="false" refersToTrain="endOfTrain"> <name name="JNA-201" description="Speed section" language="EN"/> <linearLocation id="spsec100_lloc" ap

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

{{Attr|processStatus}}, {{Attr|id}}, {{Attr|code}}, {{Attr|name}}, {{Attr|description}}, {{Attr|xml:lang}} Describe your changes with "Summary" or Zusammenfassung

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

Please, notice the basic Principles for joining this wiki, as explained here The working language of this wiki is English. The complete content should

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:deactivatedBy of railML® version 3.2 UML-visualization of IL Documentation The description of deactivation conditions for this level crossing. Subschema interlocking

version 3.2 UML-visualization of generic Documentation particular name and description of the system asset dependent on language Subschema generic Parents* controller

name="InterCity" description="Fast large city connection" trainUsage="passenger" my:colour="red"/> <category id="c2" code="RE" name="RegionalExpress" description="Fast

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

(optional; xs:string) Possible values: backward forward, fromDescription: Textual description of the origin. (optional; xs:string), ref: The actual reference

to reference this element within railML. @description – The string element takes a more detailed description of the logic. This is for information of the

– The name of the asset in the related language. @description – The additional optional description for the asset. @language – The identification of the

test the limmitations of applications. Good examples contain a brief description (abstract) information of the content (number, formats and functions of

<rail3:etcsAreas> <rail3:etcsArea id="etcsArea01" mVersion="33"> <rail3:name description="ETCS area Border: M_VERSION 1.1 -> 2.1" language="EN" name="etcsArea_Border_BON"/>

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

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

Exchange of Logical Train Positions   Current train positions should be exchanged between a TMS and other systems. Current position means: the position

Guideline for participating in the development process This guideline is supposed to explain the development of the railML® schema and how you can contribute

The following templates may be used at every wiki page for referring to a certain railML® element documentation page. The link is shown in angle brackets:

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

the objects associated with this route and set them accordingly. The description of a route starts with the following information: @locksAutomatically

Xerces with some additional flags/parameter: <target name="xml-validate" description="Validate ${xml-file} against its schema files"> <schemavalidate file="${xml-file}

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

Reason Commited changes have affects on XML-instance files and should be announced in advance in corresponding railML® newsgroups. Decision Tagging a major

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

<gmlLocations> <lineString> <description> <descriptionReference> <identifier> <name> <pos> <posList> <point> <description> <descriptionReference> <identifier>

Example entry <trainClearanceGauge code="GA"> <description>stucture gauge GA according European standard</description> <validFor>interoperable</validFor> </trainClearanceGauge>

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

information of the related network in the interlocking. Therefore the description of is mainly a list of references to the related items needed for the

</netRelation> </netRelations> <networks> <network id="nw01"> <level id="lv0" descriptionLevel="Micro"> <networkResource ref="ne_a01"/> <networkResource ref="ne_a02"/>

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

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

Timetabling; Fahrplan Each RU has to provide a timetable for their train- and shunting movements in a coming time period. Besides the RU itself the involved

document for the equipment of the interlocking logic. An interlocking description consists mainly of: Track and trackside signalling components, Route control

instance routesetting. An interlocking is required to set and lock routes. A description of routes in terms of railML is of interest to both engineering and simulation

Rail Inspection Data ; Schienenprüfdaten The application broaches the issue of railway track inspection and maintenance. With the help of railML data,

scope='commercial' connections: <commercialConnection> element(s) stop description: only <stop> elements which contain a <isCommercial> elemente will be

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

Traffic Management Plan Description / Beschreibung / Description The UseCase TrafficManagementPlan (TMP) defines exchange of information between Timetable

connections: <connection> element(s) with connType='commercial' stop description: only <stopDescription> elements with commercial='true' will be relevant including

elementNumber="0" id="" indicatorType="cautiousDriving"> <rail3:designator description="" entry="" register=""/> <rail3:hasCommand entityCode="" ref=""/> <rail3:hasIndication

tor elementNumber="0" id="" positionInRoute="end"> <rail3:designator description="" entry="" register=""/> <rail3:hasCommand entityCode="" ref=""/> <rail3:hasIndication

after finalizing the use case in the working groups alongside with this description. Rollingstock data usually includes the capabilities of the available

CAD for railway signalling; CAD für Zugsignalisierung Engineers of the railway signaling discipline use a Computer-Aided Design (CAD) tool to model a railway

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

Earliest departure Latest departure Minimum stop time Stop type, stop description Commercial connections Infrastructure <ocpTT> Ordered stops Rolling stock

Railway Infrastructure Visualisation; Visualisierung von Schieneninfrastruktur The typical railway planning process involves several iterations with different

ÖBB-SCHIG-Reporting (NRE Reporting Austria); NRE Meldung Österreich ÖBB Infrastructure reports several properties of the line and track network periodically

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

Speed directory; VzG – Verzeichnis zulässiger Geschwindigkeiten The VzG Process is the central interface between infrastructure business processes (building

Traction power supply simulation; Simulierung der Bahnstromversorgung For various purposes it is necessary to simulate the (electrical) traction power

Adopt vehicle working scheduling to timetable changes; Umlauf an Jahresfahrplan anpassen The importing system holds timetable and vehicle working data

Only commit to the master branch directly if the changes your are commiting are complete in themselves and don't change the syntax of railML®. Changes

Extending railML®   There exists a wide range of means to extend XML Schemas. As railML® is intended for collaboration with other parties, there is a frame

Automatic Schemaexport for Element description

Automatic Schemaexport for Element description

Automatic Schemaexport for Element descriptionReference

Automatic Schemaexport for Element descriptionReference

Railway Laboratory (Simulations and Research Support) The aim of our project is to simulate railway traffic in laboratory conditions in order to improve

Capture schematic visualisation information of track assets; Erstellung schematischer Visualisierungsinformationen von Schienenanlagen railML data will

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

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

Long Term Strategic Timetabling; Langfristfahrplanerstellung The timetable data prepared in this use case is not formally linked to the production process

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

Using xsi:type   Before implementing any extensions to the railML® schema, please consider Dev:Extending_railML#when. The means described in this page

the use case here. The headline is made with Template: UC description (type {{UC description}}) In this section the data flows should be drafted. The headline

Schematic Track Plan Infrastructure managers use maps for the visualization of their railway infrastructure. These maps comprise: Geographic maps Geoschematic

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

generic:trainBrakes of railML® version 3.2 UML-visualization of generic Documentation Description of the type of brakes within the formation and their application as brake

generic:vehicleBrakes of railML® version 3.2 UML-visualization of generic Documentation Description of the type of vehicle brakes and their application as brake effort or

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

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

RINF-XML, and therefore support and maintain natively the railML3 RINF file description according to the evolutions of the project. The railML3 file for RINF

(optional; xs:string) Possible values: backward forward, fromDescription: Textual description of the origin. (optional; xs:string), ref: The actual reference

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

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

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

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

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

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)

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

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

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