IL:tunnelGateIL

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

See example visualization at tz.de (external link)


Documentation

Syntax

Autoexport from the XML-Schema for element IL:tunnelGateIL of railML® version 3.3
    
Documentation The tunnel gate is a movable structure for completely closing the tunnel tube at the portal to cover the tunnel from bad weather conditions like icing or it intersects a tunnel to prevent ingress of water or smoke. It thus prevents train traffic in blockedClosed position. Dependent on train approach the gate is moved to passableOpen position. The gate movements and positions are controlled by the interlocking system in similar manner like a level crossing.
Subschema interlocking
Parents*

tunnelGatesIL

Children

activationCondition (0..*), assetName (0..*), belongsToOperationalPoint (0..1), deactivatedBy (0..*), designator (0..*), elementState (0..*), hasCommand (0..*), hasGateSection (0..*), hasIndication (0..*), hasInterface (0..1), hasTvdSection (0..*), refersTo (1..1)

Attributes:
  • preferredPosition: The preferred position of the tunnel gate. For route dependent gates this would be the blocking position. (optional; xs:string)
Possible values:
  • blockingClosed: The gate is in a closed position, which blocks the railway traffic through it.
  • passableOpen: The gate is in an open position, which allows the passage of railway traffic through it.
  • unknown: The gate position is not known,

  • typicalTimeToOpen: The typical time required to open the tunnel gate, i.e. the time to bring the gate from blocking into the supervised open/passable position. (optional; xs:duration),

  • elementNumber: element number for internal referencing in the engineering data (optional; xs:nonNegativeInteger),

  • id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory; xs:ID); compare: Dev:Identities
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

 

Autoexport from the XML-Schema for element IL:tunnelGateIL of railML® version 3.2
    
Documentation The contained tunnelGateIL element
Subschema interlocking
Parents*

tunnelGatesIL

Children

activationCondition (0..*), assetName (0..*), belongsToOperationalPoint (0..1), deactivatedBy (0..*), designator (0..*), hasCommand (0..*), hasGateSection (0..*), hasIndication (0..*), hasInterface (0..1), hasTvdSection (0..*), refersTo (1..1)

Attributes:
  • preferredPosition: The preferred position of the tunnel gate. For route dependent gates this would be the blocking position. (optional; xs:string)
Possible values:
  • blockingClosed: The gate is in a closed position, which blocks the railway traffic through it.
  • passableOpen: The gate is in an open position, which allows the passage of railway traffic through it.
  • unknown: The gate position is not known,

  • typicalTimeToOpen: The typical time required to open the tunnel gate, i.e. the time to bring the gate from blocking into the supervised open/passable position. (optional; xs:duration),

  • elementNumber: element number for internal referencing in the engineering data (optional; xs:nonNegativeInteger),

  • id: unique identifier (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

 

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


Changes 3.1→3.2

There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.

Introduced with version 3.2.

Changes 3.2→3.3

There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.

The element documentation has been changed.

The children have been changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

The tunnelGateIL is installed at tunnel portals or within the tunnel to fulfill various purposes. When installed at the portals they are mainly used to control the tunnel climate, i.e. temperature and air flow. Especially in winter time this might be necessary to reduce icing on tunnel walls inside. An installation of gates inside the tunnel devides the tunnel in specific sections. This might be necessary to reduce the effect from ingressing smoke or water.

Depending on the purpose and their normal position the gates are operated like the barriers of a level crossing with each route set. Therefore the tunnelGateIL is modelled similar to levelCrossingIL with activation conditions and deactivation triggers. However, the open position is definitely supervised for any train route even the tunnel gate is normally open.

  • @elementNumber - A positive integer number unique within one <signalBox> to index the element in internal lists of engineering data.
  • @id - The unique identifier used to reference this element within railML.
  • @preferredPosition - In most cases the preferred position of a tunnel gate is passableOpen, i.e. allowing railway traffic to pass freely. However, there might be cases when the tunnel gate is normally blockingClosed and opened for railway traffic only on route setting. The normal closed status is used for tunnel climate control.
  • @typicalTimeToOpen - This is the time the interlocking shall expect required between commanding the tunnel gate and the notification of the open position. After elapse of the timer an alarm might be raised to indicate the problem. In general it is assumed that closing and opening do take the same amount of time.
  • <designator> - A coded name as per a specified register for the asset.
  • <assetName> - A name for the asset in a given language.
  • <belongsToOperationalPoint> - The reference to an <operationalPoint> this tunnelGateIL belongs to from operational point of view.
  • <hasCommand> - The reference to any predefined operator command, which can be used with this element. For details refer to <hasOperatorCommand>.
  • <hasIndication> - The reference to any predefined indication on HMI, which is used with this element. For details refer to <hasHmiIndication>.
  • <refersTo> – This the reference to the physical tunnel gate <tunnelGateIS> in the infrastructure.
  • <hasInterface> – This is the description of the physical interface between the interlocking and the tunnel gate. It mainly contains the list of commands and messages exchanged on this interface. For details refer to <interface>.
  • <deactivatedBy> – This describes the deactivation (closing) of the tunnel gate. For details refer to <deactivatedBy>.
  • <activationCondition> – This describes the conditions for activating (opening) the tunnel gate. For details refer to <activationCondition>.
  • <hasTvdSection> – This is the reference list to all <tvdSection> located directly at the tunnel gate.
  • <hasGateSection> – This is a similar reference list as for TVD sections but for all <trackIL> located directly at the tunnel gate.


<rail3:tunnelGateIL elementNumber="0" id="" preferredPosition="blockingClosed" typicalTimeToOpen="P1D">
	<rail3:designator description="" entry="" register=""/>
	<rail3:assetName description="" language="EN" name=""/>
	<rail3:belongsToOperationalPoint ref=""/>
	<rail3:hasCommand entityCode="" ref=""/>
	<rail3:hasIndication entityCode="" ref=""/>
	<rail3:refersTo ref=""/>
	<rail3:hasInterface ref=""/>
	<rail3:deactivatedBy delay="P1D">
		<rail3:tvdDetectorRef ref=""/>
	</rail3:deactivatedBy>
	<rail3:activationCondition andOr="AND">
		<rail3:delayBySwitchPosition delay="P1D" inPosition="left" isNegated="true">
			<rail3:refersToSwitch ref=""/>
		</rail3:delayBySwitchPosition>
		<rail3:aspectRelatedDelay delay="P1D" isNegated="true">
			<rail3:refersToSignal ref=""/>
			<rail3:showsAspect ref=""/>
		</rail3:aspectRelatedDelay>
		<rail3:signalDelayTime delay="P1D">
			<rail3:hasDelayedSignal ref=""/>
		</rail3:signalDelayTime>
		<rail3:activatedBy delay="P1D">
			<rail3:refersTo ref=""/>
		</rail3:activatedBy>
	</rail3:activationCondition>
	<rail3:hasTvdSection ref=""/>
	<rail3:hasGateSection ref=""/>
</rail3:tunnelGateIL>

Notes

Open Issues

Retrieved from "https://wiki3.railml.org/index.php?title=IL:tunnelGateIL&oldid=9584"