|Suggested refined definitions and extension to organizationalUnits [message #2325]
||Mon, 10 February 2020 15:25
Registered: March 2016
For a clearer use of organisational units the Norwegian railway sector recommends to further refine the existing definitions to make them more clear and to introduce on extension. |
There are 8 fixed types of organisations in railML2:
We suggest extending railML2.5 with a new sub element/type "vehicleOwner" and to allow extensions with <any> element.
I tried to find some background information in the forum, but only found this string without any clear definitions: https://www.railml.org/forum/index.php?t=msg&th=348& goto=1102&#msg_1102
We would like to ask the community how they define the 8 types of organisations. To start the discussion, we suggest the following definition improvements of the terms:
Container element for pre-defining organizational units, that will be referred from within the railML file.
Organisational units are railway related organisations that can be a government authority, local authority, corporation, enterprise, public company, private company, undertaking/body or other legal entity.
Each element may be used several times for several entries, as e.g. a network may be divided into areas with different infrastructure managers, and as within the network there will usually move vehicles from different producers. Every element entry within this container has, at least, an attribute name plus an attribute id. It can be addressed via this id from certain other places within the railML®-file
Note that as in railML2 the type of organisation is declared by the element. So, you need to register the same organisation in each relevant element if it has more than one role.
An organisation that is responsible for establishing and maintaining railway infrastructure, which may also include the management of infrastructure control and safety systems. The functions of the infrastructure manager on a network or part of a network may be allocated to different bodies or undertakings.
Via code it can be linked to the codelist infrastructureManagers.xml, where numerous infrastructure managers are listed.
Semantics: An organisation that produces railway vehicles.
Semantics: An organisation responsible for operating the railway vehicle on behalf of a railway undertaking (usually as a sub-contractor).
Semantics: An organisation that orders transportation service from a railway undertaking. The customer can have exclusive transportation ownership rights (concessions) or operate on open access.
Semantics: An organisation, licensed according to applicable legislation, which principal business is to provide services for the transport of goods and/or passengers by rail with a requirement that the undertaking must ensure traction and is commercially responsible for the service.
Semantics: An organisation responsible for the operational performance of a railway undertakings service (usually as a sub-contractor). Examples are organisations responsible for catering, cleaning or vehicle maintenance.
Semantics: A <railwayUndertaking> that has received and operates under a concession from a <customer>.
Forum note: As this is over specific and the UC is not clear, we suggest deprecating this element. If there is a need for the contract status between customer or railway undertaking, that should be mapped in a separate construct.
Semantics: Any relevant organisation not fitting to the other sub elements of <organisationalUnits>
Semantics: An organisation which purpose is to make railway vehicles available for railway undertakings.
|Re: Suggested refined definitions and extension to organizationalUnits [message #2329 is a reply to message #2325]
||Thu, 13 February 2020 13:49
Registered: March 2008
I don't know why Torben's link did not become clickable, so I'll try to post it again, as well as the related trac issue:
I have not found any further context, and in the old forum thread a "vehicleOwner" value was also suggested, but it was apparently not included at the end. Are there anyone in the community who can provide (best practice) examples of current usage? Would Torben's suggestions break any current functionality?
In addition to Torben's suggested changes, I would as if we really need both <railwayUndertaking>, <vehicleOperator> and <operationalUndertaking>. I propose to also deprecate at least one of the last two. Again, please comment!
Thomas Nygreen - Coordinator Across Schemes
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|Re: Suggested refined definitions and extension to organizationalUnits [message #2408 is a reply to message #2329]
||Thu, 26 March 2020 13:33
Registered: August 2008
Dear Thomas, Torben and all others,|
some time ago I agreed to read the documentation  of DB Netz AG (German Infrastructure Manager) on their planned Slot ordering data format concerning how they use what in railML would be "organisationalUnits". Here a short summary (with my own additions and translation):
de: Führendes/Koordinierendes EVU
en: leading or coordinating RU
de: Besteller, Vertragspartner
en: ordering contractor (not necessarily a RU)
de: die Zugfahrt durchführendes EVU
en: RU operating the train
de: fahrplanerstellendes EIU
en: IM creating (responsible for) the timetable
de: für die betriebliche Durchführung der Zugfahrt verantwortliches EIU; Eigentümer der Infrastruktur
en: IM responsible for operating the train = owner of infrastructure
DB Netze says this is harmonised with ERA concerning TAF/TAP. So this may be general. But I think it still could change
only time can show how other IM use this. So far, I would regard it as a German view.
What I miss is:
- No distinguishing between "ResponsibleRU" (as above), RU which owns the vehicle(s) and RU which contributes the driver.
I don't know whether this helps us, but we should keep it in mind because there is a chance that this will become "best practice" in the catchment area of ERA. May be it's ok if we produce an "assign-list" of railML values to these German/ERA values? May be a list which can be extended later with values or best practice of other countries?
Can anybody prepare this?
 DB Netze: Dokumentation der Schnittstelle des Bestellsystems der DB Netz für EVU-Systeme. Gültig ab Netzfahrplan 2024. Version 4.1.1, last update 25.02.2020.