Home » railML newsgroups » railML.infrastructure » railML 2.3 infrastructure extension proposal - controller (railML 2.3 infrastructure extension proposal - controller)
railML 2.3 infrastructure extension proposal - controller [message #1455] Tue, 20 December 2016 18:24 Go to previous message
Torben Brand is currently offline  Torben Brand
Messages: 156
Registered: March 2016
Senior Member
Dear railML infrastructure forum,
This posting contains the discussion to an extension towards the
controller
The controller (DE:Stellwerk) needs to be defined on a macroscopic level for what type and system is used. This as to give the capacity planner generic values of some capacity related values of the stations features.
Thus I have added the three new attributes:,@NO:model, @NO:type, @NO:technologyType and @NO:swVersion.
@NO:model: [datatype:string] Defines the model/system used. Examples are: SIMIS-C,Thales L-90, NSB-77, NSI-63,...
@NO:type [datatype:enumeration] Defines the type of controller on a general level. This is predefined with three Norwegian national presets, the value "none" and "other:" The presets are "NO:plussStasjon" (English: full interlocking), "NO:enkeltSikringsanlegg" (English: simplified interlocking) and "NO:enkeltInnkjørsignal" (English:simplified entry signal).
@NO:technologyType [datatype: enumeration] The predefined values are: "electric", "electromechanic", "electronic", "mechanic"
PS. The terms @type, @model, @system, @mode need to be defined more clearly in railML in general to be consistent throughout.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: railML 2.3 infrastructure extension proposal - a new "state"
Next Topic: Switch between parallel tracks
Goto Forum:
  


Current Time: Fri Mar 29 09:39:38 CET 2024