Search results

relatedSwitchAndPosition, relatedSwitchInPosition, requiredCrossingPosition, requiredDerailerPosition, requiredDetectorState, requiredKeyLockState, requiredLevelCrossingState

relatedSwitchAndPosition, relatedSwitchInPosition, requiredCrossingPosition, requiredDerailerPosition, requiredDetectorState, requiredKeyLockState, requiredLevelCrossingState

related track asset the overlap is connected to. This can be e.g. the destination signal of one or several routes. <requiresAssetInPosition> – This is the

enforcement. <requiredDerailerPosition> – This is the reference to the related derailer, its position and the level of enforcement. <requiredCrossingPosition> – This

</relatedDerailerInPosition> </hasPositionRestriction> </switchIL> </switchesIL> <derailersIL> <derailerIL returnsToPreferredPosition="true" id="dr_der01"

<delayBySwitchPosition> – The activation may be delayed by the position of a switch. @delay – The time between the switch detected in the required position and the

<designator> - A coded name as per a specified register for the asset. <assetName> - A name for the asset in a given language. <belongsToOperationalPoint> - The

ref="rt_sig02_sig04"/> <requiresSwitchInPosition mustOrShould="should" proving="oneOff"> <relatedSwitchAndPosition inPosition="left"> <refersToSwitch ref="pt_swi02"

track. @preferredPosition – This marks the switch position, which the crossing shall have when not in use of a route. The possible positions can be downleft-rightup

<facingSwitchInPosition> of type SwitchAndPosition extending AssetAndState and <requiredSwitchPosition> of type SwitchAndGivenPosition extending AssetAndGivenState

<objectName> <requiredCrossingPosition> <relatedCrossingAndPosition> <refersToCrossing> <requiredDerailerPosition> <relatedDerailerAndPosition> <refersToDerailer>

ConflictingSwitchPosition – This value is used in case any movable element, not only switches, required by the route needs another position then the conflicting

conflictingSwitchPosition: This value is used in case any movable element, not only switches, required by the route needs another position then the conflicting

IL:trackAssetInArea IL:trackIL IL:tracksIL IL:trailingSwitchInPosition IL:trainNumberField IL:trainNumberFields IL:tunnelGateIL IL:tunnelGatesIL IS:applicationType

relatedSwitchAndPosition, relatedSwitchInPosition, requiredCrossingPosition, requiredDerailerPosition, requiredDetectorState, requiredKeyLockState, requiredLevelCrossingState

relatedSwitchAndPosition, relatedSwitchInPosition, relatedToTunnelGateAndState, requiredCrossingPosition, requiredDerailerPosition, requiredDetectorState, requiredKeyLockState

<name> <positioning> <geometricPositioningSystems> <geometricPositioningSystem> <isValid> <name> <linearPositioningSystems> <linearPositioningSystem> <anchor>

relatedSwitchAndPosition, relatedSwitchInPosition, requiredCrossingPosition, requiredDerailerPosition, requiredDetectorState, requiredKeyLockState, requiredLevelCrossingState

relative position. Furthermore, infrastructure managers require that traffic control systems schematically display track assets at defined positions. railML

terms of types and attributes mainly for the purpose of asset Management. These Eulynx-defined asset data are internal to the IM whereas railML focuses on