Search results

tools use their own internal generic interlocking (table) model. Thus this use case does not require a interlocking table. This distinguishes this IL UC from

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"

cable plan Subschema: Interlocking For general information on use cases see UC:Use cases

interlockings has to be incorporated into the operation and control systems. They uses the interlocking to operate elements get element status schedule and manage

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

enters a warning area) ETCS ID of the SCWS Timeout for simplified search in case of a switch fault Signaling type of this SCWS (stationary, ETCS Level 1,

together especially when gathering information regarding topology. Future use case should handle integration towards 3D modelling for evaluation of e.g. sight

Current UML visualization A list of use cases for railML's interlocking scheme can be found here Category:Use_case_(IL). Interlocking Concepts — explanations

– IL Use Cases – IS Use Cases – RS Use Cases – TT Use Cases View/edit list on the separate source page   If you want to reactivate your inactive use case

RailTopoModel (external link). A list of use cases for the railML® interlocking schema can be found on page Category:Use case (IL). →Main Article: Infrastructure

n> </derailerIL> </derailersIL> Dependent on the language variant there are several terms in use: point, turnout, switch. railML will use the term „switch“

This marks the position, which the derailer shall have in normal case, i.e. when not in use of a route. The possible positions can be derailingPosition –

position. In case of switch actuators connected to the crossing for changing its position the attribute @numberOfFrogSwitchActuators shall be used to identify

station, train number field, timetable element) to the next. For example, one use case is a TMS that provides the current (dispatching) timetable and train positions

<hasExitSignal> – This is the reference to a <signalIL> which protects the exit from this TVD section. It shall be used in case @isBerthingTrack is set to true. Within

common module (common3.xsd) are used. In addition two basic types were created for use in interlocking subschema – entityIL and entityILref. They give the

route lock is only applied when a train is approaching the route. In that case this time is the minimum required before the final route lock can be applied

even not all information may be really “known” to the interlocking, i.e. in case of autonomous level crossing. @elementNumber - A positive integer number

released for removal. The key is a simple mean of authorisation transfer as its use allows the manual operation of a moveable element. The lock with control from

Infrastructure   Related subschemas: IL TT RS  Reported by: ProRail For general information on use cases see UC:Use cases

The Boolean value gives indication whether the key is of physical type for use in a mechanical lock.

which is neither used as block, entry, exit nor intermediate signal. This is the more general function in case no specific one can be used. repeater – The

than in use case ETCS-a because data such as balises or routes will be added. The amount of the data to be exchanged is the same as in use case ETCS-a.

unique identifier used to reference this element within railML. @indicatorType - There is currently only cautiousDriving defined for use. Other values might

the set of assets for which the permission is transferred. In the simple case the permission can only be changed for the entire station or interlocking

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

Subschema: Rollingstock   Related subschemas: IS IL TT  For general information on use cases see UC:Use cases

interlocking needs to trigger the self-test of the detector. It has to be used in combination with @triggeredSelfTest. <detectorType> – This is the reference

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

the infrastructure and state their validity. The infrastructure used in this use case is not based on the current infrastructure but an agreed future infrastructure

This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

von Schienenanlagen railML data will be used for engineering signalling and interlocking systems. Engineers are used to working with paper plans that schematically

This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

signal is showing. This element shall be used for “old-style” signalling systems with separate distant signals or in case of repeaters within the route. <signalsSpeedProfile>

master data for the use case "passenger information inside the train". The information from the <timetable> are data which will be used individually for every

control. This use case aims to cover all data exchange necessary for the functions listed above. A major difference to previous railML use cases is that this

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

element. @bitNr – This is the order number of the command in the list. In case of transmission as complete bitmask it defines the bit position in the byte

Export of planning tool: planning data, handing-over to the supplier (by using a database). interlocking (see also: Interlocking Engineering) This section

Infrastructure   Related subschemas: IL TT RS  Reported by: Jernbaneverket For general information on use cases see UC:Use cases

is the reference to the physical end of the route path. This is in most cases a signal but can also be a buffer stop or just a train detection device when

infrastructure subschema. In such cases just the suffix “IL” was added to the name, e.g. signalIS vs. signalIL. The element of <assetsForIL> is not only a collection

Automatic Schemaexport for Element switchIL

in infrastructure subschema. In such cases just the suffix “IL” was added to the name, e.g. signalIS vs. signalIL. The element of <assetsForInterlocking>

Automatic Schemaexport for Element switchIL

conflictingOverlap: This value is set in case of the overlap of either route causes the conflict. conflictingStatus: This value is used in case the status of any element

They deliver mainly the status information vacant, occupied or failed. In case of a failure the particular sections needs to be reset, i.e. declared clear

This element does not appear in railML® 3.1 within the IL subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further

conditions to conclude a train is approaching the level crossing. In first case this happens when the train crosses a detection point, i.e. an insulated

for element IL:relatedMovableElement of railML® version 3.2 UML-visualization of IL Documentation reference to other movable element in case of single/double