Home » railML newsgroups » railML.infrastructure » [railML 3.2] Modelling of Operational Rules
[railML 3.2] Modelling of Operational Rules [message #3390] Fri, 15 November 2024 15:17 Go to next message
David Lichti is currently offline  David Lichti
Messages: 47
Registered: December 2020
Member
Dear community,

In the context of a new railML 3.2 infrastructure export, we have the need to transmit a set of properties that describe special operational rules for individual tracks:



  • unsupervised operations: defines the type of operations that are permitted on a track while the station is not supervised by a dispatcher.

  • permissive working: indicates that the track is equiped for operations of more than one train, f.ex. for coupling of trains in portion working.

  • partial block allocation: indicates that special rules for partial block allocation applies for train movements that stop on that track.
Do you have any advice regarding the mapping of this information in railML 3.2?

Best regards

David

[Updated on: Tue, 19 November 2024 07:23]

Report message to a moderator

Re: [railML 3.2] Modelling of Operational Rules [message #3420 is a reply to message #3390] Mon, 06 January 2025 14:54 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 496
Registered: January 2016
Senior Member
Dear David,

I think, railML 3.2 data model does not provide the information requested by you. The best place for locating appropriate attributes or elements is maybe //line/lineOperation [1].

Question to the community: who else needs the information/data requested by David? And in case: how do you model these data today?

[1] https://wiki3.railml.org/wiki/IS:lineOperation

Thank you very much and best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Re: [railML 3.2] Modelling of Operational Rules [message #3424 is a reply to message #3420] Wed, 08 January 2025 12:05 Go to previous messageGo to next message
David Lichti is currently offline  David Lichti
Messages: 47
Registered: December 2020
Member
I should have mentioned that we are specifically dealing with station tracks. In particular, different rules may apply to tracks in different stations of the same line, or even to different tracks of the same station. So, the line element doesn't seem like the best place.

At the same time, some of these rules are business entities and apply at many different locations across the entire network. So our current proposal has them as top-level objects with document ids and designators.
<!-- XPath: /railML/infrastructure/tps:operationalRules -->
<tps:trackOperationalRule id="or-1" supervisionRequired="dispatchingOperations" allowsPermissiveWorking="true" shortBlockAllocation="true"/>
<tps:signalOperationalRule id="gr-1" supervisionRequired="allOperations" belongsToParent="gz-1"/>
<tps:signalOperationalRule id="gz-1" allocateBeyondStop="false" speedRestrictionRelease="headOfTrain">
  <designator register="_tpsRestrictionCode" entry="RC1"/>
</tps:signalOperationalRule>
We would then add an operationalRuleRef attribute to the relevant track and signal elements.

Best Regards

David

Report message to a moderator

Re: [railML 3.2] Modelling of Operational Rules [message #3427 is a reply to message #3424] Mon, 13 January 2025 13:48 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 496
Registered: January 2016
Senior Member
Dear David,

thank you for your feedback.
As a reaction, I re-opened the Gitlab issue #392 [1] and set it to next version 3.4. The aim of this step is to have the topic on our list, as we already have an implementation of operating rules in railML 2.5. Until then, we may discuss here in the forum how this railML 2.5 solution should be adapted for railML 3.4 development.

[1] https://development.railml.org/railml/version3/-/issues/392

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Re: [railML 3.2] Modelling of Operational Rules [message #3431 is a reply to message #3427] Tue, 14 January 2025 09:18 Go to previous messageGo to next message
David Lichti is currently offline  David Lichti
Messages: 47
Registered: December 2020
Member
Thank you for the reference to railML 2.5 operating rules. I was not aware of this element.

Report message to a moderator

Re: [railML 3.2] Modelling of Operational Rules [message #3441 is a reply to message #3431] Fri, 17 January 2025 09:56 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 496
Registered: January 2016
Senior Member
Dear community,

in railML 2.5 we introduced in infrastructure the element //operatingRule to "describe a single special operating rule that differs from the generic rule book and applies for specific physical objects. The generic rule book shall not be mapped here." [1]

Considering the implementation of operating rules also in railML 3, I want to ask you: Which information related to operating rules are important to be modelled from your applications' perspective? Please provide your ideas and requirements here in the forum. After consolidation I will add them to the development issue #392 [2].

[1] https://wiki2.railml.org/wiki/IS:operatingRule
[2] https://development.railml.org/railml/version3/-/issues/392

Thank you very much and best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Previous Topic: [railML 3.2] Modelling of (Station) Track Equipment
Next Topic: [railML 3.2] Modelling of Scheduling Rules
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Mar 13 21:06:48 CET 2025