Description of controller for operational purposes

Description

Until railML version 2.3 the element has been just a placeholder element, which indicates that the railway infrastructure is controlled from some kind of interlocking. All the detailed features of the controller that describe its functionality etc. are part of the upcoming interlocking schema.

However, it makes sense to describe basic attributes of the controller already in the infrastructure. In particular, attributes that are important for the macroscopic description of the controller for operational purposes shall be added.

Background

...

Links

• Forum discussion
• Torben Brand, February 2017: [http://www.railml.org/forum/index.php?t=msg&th=481&start=0&]
• Wiki documentation
• [http://wiki.railml.org/index.php?title=IS:controller]

Proposed solution for railML 2.x

Add a parameter for storing the (product) name of the controller: @model. The value shall be of type "xs:string".

Add a parameter for the classification of the controller regarding the complexity or responsibility: @type. The classification shall allow a generic hierarchy of a controller network. Therefore, an enumeration is suggested. Possible values:

• none
• singleElement
• local
• regional
• crossRegional

Add a parameter for defining the type of technology the controller is based on: @technologyType. This enumeration may contain the following values:

• manual
• mechanical
• electro-mechanical
• electrical
• electronic

Add a parameter for naming the controller software version: @swVersion. A string value is suggested.

It should be possible to reference multiple controllers from one : Add a sub-element instead of using an attribute.

<locallyControlledArea>
  <controllerRef ref="co0815"/>
  <controllerRef ref="co4711"/>
</locallyControlledArea>

Further, it shall be also possible to reference multiple controllers from one OCP. This shall be realized with a repeatable child element .

Last, but not least, the hierarchy of controllers need to be modelled using a new attribute @parentControllerRef.

Proposed solution for railML v3

...