Function location [message #3157] |
Mon, 06 November 2023 09:29 ![Go to next message Go to next message](/forum/theme/default/images/down.png) |
Georg Boasson
Messages: 18 Registered: October 2020
|
Junior Member |
|
|
Our asset management system in Bane NOR will be extended with a "Functional location". A Functional location will represent a function which is located at a certain geographical location.
As an example, will Switch number 1 at a specified station be a functional location. Another example is the Entry and Exit signals at specified stations. The Functional location can be moved to another physical position due to reconstruction, but the Functional location will remain unchanged.
Several physical objects can be located at the same Functional location. A physical object can either have none or one Functional location. A definition of Functional location is find here:
https://help.sap.com/doc/saphelp_nw70/7.0.12/ja-JP/01/d5438b 4ab311d189740000e8322d00/content.htm?no_cache=true
The functional location might be implemented by a designator. The Functional location might look like the typeDesignator, where several objects might reference to the same rule in a rulebook.
Example of designators for a signalIS:
* The physical object: <designator register="BaneData" entry="SA-SIG-018434" />
* The Functional location: <designator register="Bane NOR Functional location" entry="FL-1503266" />
* The signal type: <typeDesignator entry="E35c" rulebook="TJN"/>
Any ideas how Functional location can be supported in railML?
|
|
|
Re: Function location [message #3162 is a reply to message #3157] |
Wed, 08 November 2023 14:09 ![Go to previous message Go to previous message](/forum/theme/default/images/up.png) |
christian.rahmig
Messages: 458 Registered: January 2016
|
Senior Member |
|
|
Dear Georg,
thank you for your input from practical experiences.
I think that the term "location" might be confusing for some railML 3 users that are working with spotLocation, linearLocation etc. As you mentioned with your solution proposal in your post, the topic is more related to designators, where the referenced register contains the functional location information. This means, that the functional location itself is not modelled in railML, but it is handled in the referenced register. As the designator is not an identifier, it doesn't have to be unique, and the same designator can be used also by several functional infrastructure elements.
Question to the community: who else is dealing with functional locations? And if so, how do you integrate them with railML at the moment?
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
|
|
|