IL:switchIL/3.2

Automatic Schemaexport for Element switchIL

Autoexport from the XML-Schema for element IL:switchIL of railML® version 3.2      UML-visualization of IL
Documentation	The switch is a track asset where a train can change from one track to another. Here the functional aspects for interlocking operation are considered.
Subschema	interlocking
Parents*	switchesIL
Children	assetName (0..*), belongsToOperationalPoint (0..1), branchLeft (1..1), branchRight (1..1), branchTip (0..1), connectedToPowerSupply (0..1), designator (0..*), hasCommand (0..*), hasFoulingTrainDetectors (0..*), hasGaugeClearanceMarker (0..2), hasIndication (0..*), hasPositionRestriction (0..1), hasTvdSection (0..1), refersTo (1..2), relatedMovableElement (0..1)
Attributes: preferredPosition: This is the preferred position of the switch which it is switched to when not in use or in case of both positions required for flank protection. (optional; xs:string) Possible values: left: position of a switch for use of left branch right: position of a switch for use of right branch, isKeyLocked: One of boolean true or false. True means that the switch is clamped either mechanically or by any electric or electronic means. The interlocking shall never attempt to throw a clamped switch. (optional; xs:boolean), localOperated: This gives information, whether the derailer is locally operated independent of any <signalBox>. (optional; xs:string; patterns: other:\w{2,}) Possible values: electrical: For the local operation an electrical drive is used. mechanical: The local operation is made by means of mechanics, e.g. lever with counterweight. none: There is no possibility of local operation of this device., maxThrowTime: Maximum time in milliseconds during which the IL can drive the element. If it has not reached end-position before this timer expires, the interlocking stops throwing as to prevent damage. (optional; xs:duration), numberOfBladeSwitchActuators: number of switch actuators controlled from interlocking to throw the switch blades, 0 means no direct operation from the interlocking (optional; xs:nonNegativeInteger), numberOfFrogSwitchActuators: number of switch actuators controlled from interlocking to throw the frog nose(s), 0 means no movable frog (optional; xs:nonNegativeInteger), returnsToPreferredPosition: The automatic normalisation attribute is closely related to the preferred position. Whether or not the IL returns the element to its preferred position depends on this parameter. E.g. a derailer that is modelled as ... preferredPosition=engaged autoNormalisation=true ... will return to its engaged position when released. A switch modelled as preferredPosition=right autoNormalisation=false... will not automatically return to the right position when released. This combination of attributes is useful for geographical interlockings that automatically determine the preferred routes given the preferred position of intervening switches. (optional; xs:boolean), typicalThrowTime: typical throw time is the average time it takes between the moment the IL receives the call and the element reaches the new position. Switch throwing adds a delay to route setting that is of great interest to the use case simulation. For this purpose, we add an attribute typicalThrowTime that allows capacity planners to estimate the influence of slow throwing switches on train traffic. Note that this excludes controller (OCS) processing time and communication between controller (OCS) and interlocking. (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.