Home » railML newsgroups » railML.infrastructure » Balise group values for IS:functionalType
Balise group values for IS:functionalType [message #3174] Thu, 14 December 2023 15:16 Go to previous message
Terje Nordal is currently offline  Terje Nordal
Messages: 9
Registered: December 2023
Junior Member
Dear railML experts,

I have just recently gotten access to post on the forum, and as requested by the administrators at railML.org I will start my first post with a brief introduction of myself. In the context of railML I represent Bane NOR (part of the railway administration in Norway), working as one of our technical in-house admins for the NRV tool (delivered to us by TrafIT solutions). I work on developing new functionality in the tool, mainly to help our engineers in their day-to-day work and for the tool to process and export data that let's us work with our signalling system suppliers in the best way possible. Other than that I work as a user of the same tool, doing signalling system design and other project related work in that regard, with 10 years of experience from that field.

Moving on to the reason for posting. Referring to https://wiki3.railml.org/wiki/IS:functionalType for balises, several values are possible. In our signalling design we have tried to map our different balise types. So far we have been able to find mapping for four of these, using the values networkRegistration, sessionEstablishment, sessionTermination and announcementLevelTransition. For the case of a level transition scenario, we have an additional two balise functions that we want to map, making a total of three balise functions for a successful level transition implementation.

Our names for these three balise groups are LTA (Level Transition Announcement), which is the one we have already mapped to announcementLevelTransition, LTC (Level Transition Cancellation) and LTO (Level Transition Order). LTC is located in diverging tracks where the Level Transition shall not take place, between the Level Transition Announcement balise group and the signaling system border. It's function is to cancel the transition to another level, in cases where the announcement has already been received by the train. LTO is located at the signaling system border, ordering the transition to the signaling system on the opposite side of the border. I have attached an image to hopefully explain the scenario and functions.

The question is, are there any values in IS:functionalType meant to handle these LTC and LTO balise groups? I have tried reading the value descriptions, but I could not find a perfect match in these cases.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Restricting aggregation of RailTopoModel
Next Topic: [railML3] Usage of //network/networkResource
Goto Forum:
  


Current Time: Mon May 20 23:54:53 CEST 2024