| Fwd: Suggestion for a new use case: run time calculation [message #3092 is a reply to message #3082] |
Mon, 29 May 2023 23:24   |
Torben Brand
Messages: 158
Registered: March 2016
|
Senior Member |
|
|
Dear railML timetable community,
We agreed in our TT working group telco on 4. May that there is a requirement for the runtime calculation use case. Selected members of the TT community volunteered to participate in the development of the UC in a temporary separate subgroup that will report to the TT working group (for the duration of the subgroup). see meeting minutes in railML cloud for details.
The UC will cover input data for runtime calculation, thus the abbreviation "RTCI" was chosen.
Goal is to finish the draft work before summer holiday and do final clean-up in August.
In the SCTP working group telco on the 12.May we agreed that we should make separate sub use cases for a clean approach. This like the ETCS track net use case.
The sub use cases will be:
- RTCI-a for infrastructure (and possibly interlocking) schema
- RTCI-b for rolling stock schema
- RTCI-c for timetable schema
RTCI-a will be first solved in a temporary sub use case "RTC" under SCTP (additional column in the mandatory attribute Excel sheet) in the SCTP working group. I will make a draft, before next SCTP meeting 9. June. Data from here will be moved to RTCI-a later in the clean-up phase.
RTCI-b will be developed by the new TT subgroup RTCI. It will convene on its first meeting online on 6. June 12:00-13:30. Please contact me or railML if you are interested in participating. I will make a draft prior to the meeting.
[Updated on: Thu, 01 June 2023 19:37] by Moderator Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
