Home » railML newsgroups » railML.infrastructure » serviceSections extension (Consider serviceSections for purpose of Infrastructure Maintenence)
serviceSections extension [message #2944] Wed, 09 March 2022 15:52 Go to next message
Martin Zien is currently offline  Martin Zien
Messages: 14
Registered: December 2021
Junior Member
The current contents of the serviceSections are strongly driven by the needs of maintenence of the rolling stock.

Of course, there is also a need to do maintenece to the infrastructure assets.

One scenario which might apply here:
a) Identify a serviceSection which is capable to do maintenance of infrastructure equipment
b) staff with a GPS-equipped handheld device must be allocated at a certain landmark, before a switch is operated to check the successful maintenance.


So, what do you think of introducing optional attributes:
a) serviceSection@isInfrastructureMaintenanceWorkshop
b) serviceSection@isInfrastructureMaintenanceSafetyLocation

Of course, further scenarios for maintenance of the infrastructure may be possible, too.
Feel free to contribute with your ideas.
Re: serviceSections extension [message #2973 is a reply to message #2944] Tue, 22 March 2022 09:39 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 447
Registered: January 2016
Senior Member
Dear Martin,

as discussed in the ETCS working group meeting on 11.03.2022 the naming of the service section services (boolean) shall be unified according to the pattern @allows{domain}{service} or @is{domain}{service}. I filed a git issue for this topic [1].

This means for your proposed attribute a) @allowsInfrastructureMaintenance.

For your proposal b) I suggest to model it as an own extension (at least for railML 3.2), since the discussion in the working group did not come to a clear conclusion.

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

Best regards
Christian


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Identifiers in Infrastructure
Next Topic: [railML 3.2] How to handle different granularity in node-edge-models at the level="micro"?
Goto Forum:
  


Current Time: Thu Jul 25 09:34:29 CEST 2024