| oprational point attribute simulatniousEntry missing [message #4082] |
Thu, 09 July 2026 19:51 |
Torben Brand
Messages: 214
Registered: March 2016
|
Senior Member |
|
|
It seems the operational point attribute <simultaniousEntry> is missing in railML3.3 that was present in railML2.5 [1].
The attribute is required for LTST, SCTP and NEST UC (amongst others).
The toppic was discussed in the July SCTP/NEST WG meting. The object is required by Bane NOR and Trafikverket for NEST purposes [2] and by Bane NOR and SBB for ETCS planning requirement purpose.
There were wories on redundancy between overlap modelling in interlocking schema and a potantial agregated (and potentially vague definition) for the whole OP in the infrastrucutre schema.
There are two challenges here. Not all UC allow the usasge of the interlocking schema, wich would be required with using the overlap. Furthermore the details of the overlaps can be unknown (or not relevant for the TT UC).
The WG agreed on the requirement for a clear definition of "simulatanious entry".
Th norwegian definition is "Authorizing entry into a station may be displayed for more than one train, provided the track layout or a technical system ensures that movement from one train route into the other is impossible." (TJN 5.7.4)
[1] https://wiki2.railml.org/wiki/IS:propOperational
[2] https://orv.banenor.no/strekningsbeskrivelse-for-jernbanenet tet/tillegg/artikler/stasjoner-med-mulighet-for-innkjoring-a v-flere-tog/
[Updated on: Thu, 09 July 2026 19:53] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
