Home » railML newsgroups » railml.infrastructure » railML 2.3 infrastructure extension proposal operational properties of an OCP (railML 2.3 infrastructure extension proposal operational properties of an OCP)
railML 2.3 infrastructure extension proposal operational properties of an OCP [message #1457] Tue, 20 December 2016 18:27 Go to previous message
Torben Brand is currently offline  Torben Brand
Messages: 27
Registered: March 2016
Junior Member
Dear railML infrastructure forum,
This posting contains the discussion to an extension towards the
propOperational
In Norway trains are by default only allowed to enter a station one by one, due to safety reasons. If a station is equipped/designed with simultaneous entry features (NO:samtidig innkjør) trains may enter simultaneously. This is necessary to know for the capacity planner, timetable planner and train driver.
The element <propOperational> is extended with the new attribute @NO:samtidigInnkjør [datatype: enumeration]. The attribute has 4 Norwegian preset values and the values "partial" and "none". The precise values of the value "partial" needs to be defined in another system/model.
The attribute @operationalType is extended with the value "siding". In Norway a "siding" is an additional track on the path (section of line between stations). It is not a station according to Norwegian definition as it does not have a main-home signal. Thus the path on the siding needs to be blocked during the operation of entering and leaving the siding. PS. There is a trackType under track with value "sidingTrack" This is described in the Wiki as: "This is a siding"
The attribute @operationalType is extended with the value "halt". In Norway we need to separate between a halt within a station and outside the station (on the path). I suggest to use the existing operationalType "stopingPoint" with halts within the station (As this correlates with the Norwegian name "stoppested"="stoppingplace"). And the new operationalType "halt" for halts on the path.
It needs to be defined if a station is remote controlled (by CTC). Thus we have added the new bolean attribute @NO:remoteControlled. Later extensions could define which remote controller (CTC) is controlling the interlocking controller.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: railML 2.3 infrastructure extension proposal line sections
Goto Forum:
  


Current Time: Thu Jul 27 14:33:00 CEST 2017