Extend definition of <controller> and add values
Description
The current implementation of (in the meaning of an interlocking) in railML 2.4 misses information about the time required for setting a route and the time between issuing a command and confirmation ("throw time").
Background
This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
is a high-level element in railML 2.4.
railML2.4nor allows the controller to be implicitly part of the OCP in very simple models. However, in most models, a separate element is modelled. In most cases one OCP has one controller. Larger stations can have multiple controllers for designated areas. Modern electronic controllers can control objects belonging to multiple OCPs.
The following new attributes of are introduced in railML2.4nor: @routeSetTime and @typicalThrowTime.
For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.5.
A controller sets the track side objects in a certain safe position or aspect defined by the routes. For instance, it sets the switch either in the position "left" or "straight". Usually this is referred to as an interlocking unit. However, interlocking is not modelled in railML2, which is why the term "controller" is used. A controller is located between an OCP and the objects the controller controls. It controls the objects on behalf of an OCP.
The controller in accordance to Norwegian usage is defined in TRV (https://trv.banenor.no/wiki/Signal/Prosjektering/Betjeningsanlegg#Systemoversikt_2) and TJN (https://orv.banenor.no/orv/doku.php?id=tjn:Kapittel_1#definisjoner_for_signalanlegg).
Links
- Forum discussion:
- Torben Brand, 20.12.2016: [https://www.railml.org/forum/index.php?t=msg&goto=1455&#msg_1455]
- Trac tickets:
- #304
- #430 (closed)
- Wiki documentation:
- IS:controller: [http://wiki2.railml.org/wiki/IS:controller]
Proposed solution in railML 2.5
It is suggested to model two new attributes in element :
- @routeSetTime to model the average time for a route to be set and locked
- @throwTime to model the typical time from the moment a command is issued until a new position is confirmed