| [railML3] Additional Train Identifiers [message #3722] |
Wed, 17 September 2025 15:31  |
Edward Tollinton
Messages: 4
Registered: September 2025
|
Junior Member |
|
|
Dear All,
In the UK rail industry we are not yet moving over yet to the TAF/TAP TSI train ID conventions. Due to legacy software systems in the industry we also are unlikely to move across in the medium term future. We therefore would like alternative identifiers for an Operational Train to be available.
The key identifiers we need are:
1. Headcode - Up to 16 character identifier used in timetable planning in the UK, not date specific.
2. TSDUID - a unique identifier from the train service database used in the UK
3. TRUST ID - 8 character identifier used with a legacy system, TRUST, that reports and records train running information in the UK.
There're a couple of final identifiers we would like to be considered for modelling and data analytics requirements:
1. The unique ID for the timetable day, coming from the particular application / solution that the railML file originates from.
2. The unique ID that will go into the file exported, where more then one timetable day is stored in the file, coming from the particular application / solution that the railML file originates from.
Thank you. Thoughts on this welcome.
Regards
Ed Tollinton
Network Rail
United Kingdom
The Quadrant:MK
MK9 1EN
https://www.networkrail.co.uk/
|
|
|
|
| Re: [railML3] Additional Train Identifiers [message #3733 is a reply to message #3722] |
Mon, 06 October 2025 12:19  |
Milan Wölke
Messages: 209
Registered: April 2007
|
Senior Member |
|
|
Hi Edward,
thanks for your post. I have a few questions for better understanding your requirements:
The headcode you are talking about, is this for commercial or operational trains?
The TSDUID is just a secondary ID used beside the head code in another system?
Are you additionally also using operational and commercial train numbers? Or are the ones mentioned above basically your version of this? Is there any relationship to the commercial and operational train numbers as they are known in railML?
Regarding the TRUST ID, is this just a 3rd external ID or id this semantically a little different. From your post I understand that is is used for collecting data regarding the actual operation of a train (in contrast to the other ones that seem focused on the planning of a timetable). If this is the case does the same daily train have the same TRUST ID every day or do these IDs imply a specific day?
The unique ID for an operating day or like you say timetable day is something, that we have not included so far. Might be interesting adding this.
Regarding the last one, Im afraid, I did not understand that. Could you make an example of what that last ID is and in what relationship it is with the timetable days included in a railML document. Thanks in advance.
Best regards, Milan
Milan Hoffmann – Timetable schema coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
