IL:movableBridge

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:movableBridge of railML® version 3.2
Documentation The contained basculeBridge element
Subschema interlocking
Parents* movableBridges
Children assetName (0..*), belongsToOperationalPoint (0..1), designator (0..*), hasCommand (0..*), hasIndication (0..*), hasInterface (0..1), refersTo (0..1), takesControlOf (0..*)
Attributes:
  • technicalClosingTime: The time for the technical closing process of the bridge. (optional; xs:duration),

  • technicalOpenTime: The time needed for the opening process of the bridge. (optional; xs:duration),

  • typicalNonPassableTime: The typical time period the bridge is not passable during traversal of a vessel. (optional; xs:duration),

  • description: Description of the logic. (optional; xs:string),

  • 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

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

🗒️ There can be various logical devices like <keyLockIL> and <genericDetector>, which provide their state as input to the interlocking. Depending on their use it is also possible to send particular information from the interlocking to the logical device in order to provoke a specific reaction. It is an abstract class extended by the particular instances of it like keyLockIL or genericDetector. The common attributes and elements are:
  • @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.
  • @description – The string element takes a more detailed description of the logic. This is for information of the user only.
  • <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 device 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>.
  • <takesControlOf> – This is the reference to a movable element which can be controlled with the lock. In case of a detector, it is used as reference to any track asset, which is related to the logical device.
  • <hasInterface> – The reference to the physical interface of the logical device to the interlocking. For details refer to <interface>.
  • <refersTo> - The reference to the physical device like <keyLockIS> in the infrastructure. This element is optional as some detectors may not have a corresponding element in the infrastructure because they are not located at the track.
    The particular instantiation extends the abstract type of logicalDevice by some additional elements and attributes.
    There are further logical devices conceivable. Currently the <movableBridge> is implemented using this abstract class.
 

As <movableBridge> an <underCrossing> is seen, where a railway line is passed underneath by a waterway. This bridge is normally locked in the position for trains to run safely accross the bridge. But for the passing of a vessel the bridge needs to be moved out of the way. The particular construction of the moveable elements does not matter here as the drive for the bridge is normally outside of the railway control. Important is only the supervision and locking of the normal (closed) position. Therefore the <movableBridge> is modelled similar to <genericDetector> and <keyLockIL>.

  • @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.
  • @technicalClosingTime - The time period which is technically needed to close the bridge from full open to passable position.
  • @technicalOpenTime - The time period which is technically needed to open the bridge from the passable to full open position.
  • @typicalNonPassableTime - The average time period the bridge is not usable by railway during the passage of a vessel. This time period starts from unlocking the bridge until it is locked again.
  • <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> the <movableBridge> 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>.
  • <takesControlOf> - The reference to any other railway element, which is controlled only by the status of this movableBridge.
  • <hasInterface> - The reference to the physical interface definition needed for control this movableBridge from the related <signalBox>. For details refer to <interface>.
  • <refersTo> - The reference to the physical <underCrossing> as defined in the infrastructure.
<rail3:movableBridge description="" elementNumber="0" id="" technicalClosingTime="P1D" technicalOpenTime="P1D" typicalNonPassableTime="P1D">
  <rail3:designator description="" entry="" register=""/>
  <rail3:assetName description="" language="EN" name=""/>
  <rail3:belongsToOperationalPoint ref=""/>
  <rail3:hasCommand entityCode="" ref=""/>
  <rail3:hasIndication entityCode="" ref=""/>
  <rail3:takesControlOf ref=""/>
  <rail3:hasInterface ref=""/>
  <rail3:refersTo ref=""/>
</rail3:movableBridge>

Notes

Open Issues