| Extended data for radioBlockCentre [message #4030] |
Tue, 09 June 2026 20:35 |
Lukas Affolter
Messages: 5
Registered: May 2026
|
Junior Member |
|
|
Dear railML-Community
A few weeks ago, I created a post to extend the IS:functionalType for the balise data. SBB also wants to include high-level engineering data for the Radio Block Centre (RBC) inside railML.
Here are a few examples where there is a need to extend the current railML3.3 schema (list not exhaustive).
First section are global parameters for the RBC:- ETCS parameters like Movement Authority Request and Train Position Report (Packet 57/58)
- Track Ahead Free Display length (D_TAFDISPLAY)
- Mode Profile On Sight acknowledgement area (L_ACKMAMODE)
- Reversing safety distance
Second section covers element-specific parameters for the RBC:- RBC handover transition commanded by RBC (Packet 131)
- Level transition order commanded by RBC (Packet 41)
In order to model this data completely and consistently, appropriate extensions of the railML schema are required. From our review, we can see that we want to extend the schema in the following types:- IL:etcsGeneralData
- IL:signalIL
- IS:etcsLevelTransition
- IS:radioBlockCentreBorder
- IS:functional type
Some of these extensions are based on requirements that are specific to SBB and therefore belong in extensions. Other parameters would probably also be relevant for other users and could be included in the schema.
Do you consider this list of examples useful to include in railML?
Does anyone else already deal with this topic or has already formulated extensions on it?
More information can be found in the presentation in the cloud: https://cloud.railml.org/f/710590
Thank you for your feedback and your experiences!
Best regards
Lukas Affolter
System Engineer
SBB AG
Infrastruktur - Netzdesign, Anlagen und Technologien - Bahnsteuerung
Hilfikerstrasse 3, 3000 Bern 65
+41 79 904 77 32
lukasaffolter(at)sbbch / www.sbb.ch
|
|
|
|
Members
Search
Help
Login
Home
