| [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/
|
|
|
|
Members
Search
Help
Login
Home
