IL:signalBox

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IL:signalBox of railML® version 3.2
Documentation Container with the characteristics of an individual interlocking system.
Subschema interlocking
Parents* signalBoxes
Children any (0..*), belongsToOperationalPoint (0..*), controlledBy (0..*), controlsCombinedRoute (0..*), controlsInterface (0..*), controlsRoute (0..*), controlsSystemAsset (0..*), controlsTrackAsset (0..*), designator (0..*), hasCommunicationSettings (0..1), hasConfiguration (0..*), hasConflictingRoutes (0..*), hasName (0..*), hasPermissionZone (0..*), implementsElementGroup (0..*), implementsSignalplan (0..*)
Attributes:
  • id: unique identifier (optional; 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}\})
*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:signalBox of railML® version 3.1
Documentation Container with the characteristics of an individual interlocking system.
Subschema interlocking
Parents* signalBoxes
Children any (0..*), controlledBy (0..*), controlsCombinedRoute (0..*), controlsInterface (0..*), controlsRoute (0..*), controlsSystemAsset (0..*), controlsTrackAsset (0..*), designator (0..1), hasConfiguration (0..*), hasConflictingRoutes (0..*), hasPermissionZone (0..*), implementsElementGroup (0..*), implementsSignalplan (0..*)
Attributes:
  • id: unique identifier (optional; xs:ID; 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}\})
*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.

Semantics

Best Practice / Examples

The logic for control of track assets and train traffic is housed in a physical compartment traditionally called signalbox. In order to avoid ambiguity one has to bear in mind the clear discrimination. The entire sub-scheme is called as “interlocking” but the term is not used here without addition of “scheme”. Whenever the pure term interlocking is used, it will refer to a particular interlocking logic located inside a signalbox.

The <signalBox> combines the information of the related network in the interlocking. Therefore the description of is mainly a list of references to the related items needed for the interlocking logic.

  • <controlsSystemAsset> – This is the reference to any system asset which is controlled by this interlocking. In addition it gives also the extent of control the interlocking has of the asset.
  • <controlsTrackAsset> – This is the reference to any track asset which is controlled by this interlocking. In addition it gives also the extent of control the interlocking has of the asset.
  • <controlsRoute> – This is the reference to any route the interlocking controls.
  • <controlsCombinedRoute> – This is the reference to any route combination the interlocking controls. For details refer to chapter 1.31.
  • <controlsInterface> – This the reference to any defined interfaces to other interlocking. For details refer to chapter 1.38.
  • <controlledBy> – This is the reference to any controller which can control this interlocking.
  • <implementsSignalplan> – This contains the list of signal aspect relations the interlocking has to consider when steering any signals. For details refer to chapter 1.34.
  • <implementsElementGroup>- This contains the list of element groups that are operated together with a common command. Additionally the type of group is given as reference to a definition in <hasElementGroupType>. The referred elements in this list must be all controlled by this interlocking to the same level of extent.
  • <hasPermissionZone>– This is the reference to any permission zone within the area controlled by this interlocking.
  • <hasConflictingRoutes> – This is the reference to any route pairing that cannot be used simultaneously. For details refer to chapter 1.30.
  • <hasConfiguration> – This gives some general information about the particular interlocking. For details refer to chapter 1.35.


The example shows an interlocking with a simplified list of features. It gets status information from the power supply ups01. It fully controls the TVD section A01T and the switch pt_swi01. It commands the virtual signal mb_sig01 without getting any status information back. This @extentOfControl is explained here. This interlocking controls the routes rt_sig02_sig04 and rt_sig01_sig04 and has a related signalplan for the routes. In addition it knows the group estop01 to set the listed signals to stop and has some configuration information.

<signalBox id="ilx01">
        <designator register="_SimpleRegister entry="ILX-ARN"/>
        <controlsSystemAsset extentOfControl="notificationOnly">
                <connectedSystemAsset ref="ups01"/>
        </controlsSystemAsset>
        <controlsTrackAsset extentOfControl="fullControl">
                <connectedTrackAsset ref="A01T"/>
        </controlsTrackAsset><controlsTrackAsset extentOfControl="fullControl">
                <connectedTrackAsset ref="pt_swi01"/>
        </controlsTrackAsset>
        <controlsTrackAsset extentOfControl="steeringOnly">
                <connectedTrackAsset ref="mb_sig01"/>
        </controlsTrackAsset><controlsRoute ref="rt_sig02_sig04"/>
        <controlsRoute ref="rt_sig01_sig04"/>
        <implementsSignalplan id="sipaAC">
                <designator register="_SimpleRegister entry="signalplan ARN-CST"/>
                <aspectRelation expectingSpeed="0.0 passingSpeed="60.0 endSectionTime="PT30S id="sip01">
                        <designator register="_SimpleRegister entry="aspects 68N1-69A"/>
                        <masterAspect>
                                <refersToSignal ref="ls_sig04"/>
                                <showsAspect ref="sig_caution_23"/>
                        </masterAspect>
                        <slaveAspect>
                                <refersToSignal ref="mb_sig02"/>
                                <showsAspect ref="sig_reducproceed_21"/>
                        </slaveAspect>
                        <signalsSpeedProfile ref="sps01"/>
                        <appliesToRoute ref="rt_sig02_sig04"/>
                </aspectRelation></implementsSignalplan>
        <implementsElementGroup id="estopARN">
                <designator register="_SimpleRegister entry="Stop ARN"/>
                <groupType ref="estop01 />
                <refersToMember ref="mb_sig01 />
                <refersToMember ref="mb_sig02 />
                <refersToMember ref="mb_sig03 />
        </implementsElementGroup>
        <hasConfiguration technologyType="electronic model="Westrace 0815 signalSystem="ETCS L2 SWversion="WR31.0.12 />
</signalBox>

Additional Information

Notes

Open Issues