Home » railML newsgroups » railml.common » RE: [railML3] Refactoring of OrganizationalUnits
RE: [railML3] Refactoring of OrganizationalUnits [message #3310] Mon, 05 September 2022 12:02 Go to next message
David Lichti is currently offline  David Lichti
Messages: 20
Registered: December 2020
Junior Member
During the last TT Dev meeting, we discussed the definition
and difference between a railway undertaking and an
operational undertaking.

Both are exported in our (HaCon, TPS) legacy railML 2.2 and
upcoming railML 2.5 export. The understanding is that the
railway undertaking is the responsible entity for operating
the planned trains. It may delegate the actual operation to
a sub-contractor. In this case, there would be a different
operational undertaking.

Best Regards

David Lichti
Re: RE: [railML3] Refactoring of OrganizationalUnits [message #3316 is a reply to message #3310] Fri, 06 September 2024 14:26 Go to previous messageGo to next message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 78
Registered: March 2008
Member
Dear David,

This is in line with my understanding of these categories. They are currently documented as follows:
isRailwayUndertaking: The undertaking that is commercially responsible for the service
isOperationalUndertaking: The unit that is responsible for the operational planning of this service.

We also have another related category:
isVehicleOperator: Some kind of subcontractor (railway undertaking) that operates the vehicle, if different from the one that is responsible for the commercial service.

How do you suggest that we improve the documentation to clarify it?

Best regards,
Thomas


Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: RE: [railML3] Refactoring of OrganizationalUnits [message #3379 is a reply to message #3316] Sun, 27 October 2024 15:32 Go to previous messageGo to next message
Torben Brand is currently offline  Torben Brand
Messages: 165
Registered: March 2016
Senior Member
Dear Thomas,

In RS there are organizational units that are referenced from administrative data [1].
The vehicle keeper seems to be missing as a sub element in common <organizationalUnit> [2]
I would suggest to add <isVehicleKeeper> in railML3.3


[1] https://wiki3.railml.org/wiki/RS:administrativeData
[2] https://wiki3.railml.org/wiki/CO:organizationalUnit
Re: RE: [railML3] Refactoring of OrganizationalUnits [message #3380 is a reply to message #3379] Mon, 28 October 2024 14:57 Go to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 78
Registered: March 2008
Member
Dear Torben,

Thank you for pointing out this missing detail in organizationalUnit. We have added isVehicleKeeper to the model for 3.3.

https://development.railml.org/railml/version3/-/issues/599

Best regards,
Thomas


Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Mon, 28 October 2024 14:57]

Report message to a moderator

Previous Topic: [railML3] Refactoring of states (e.g. infrastructure states)
Next Topic: [railML3] How to deal with UUIDs
Goto Forum:
  


Current Time: Thu Nov 14 06:17:47 CET 2024