| Suggestion for a new use case: run time calculation [message #3082] |
Thu, 04 May 2023 09:44  |
Torben Brand
Messages: 162
Registered: March 2016
|
Senior Member |
|
|
Dear railML timetable community,
I have made a mapping of the UC suite of ISO RailDax with railML3 and found that there are some UC missing in railML:
- Schematic track plans for infrastructure planning OK, "SCTP"
- Runtime calculations (builds on 1), missing!
- Network statement of an infrastructure manager annex asset descriptions OK, "NEST"
- Passenger assets of rolling stock for operational planning, missing!
- Operational timetable planning (builds on 2,3&4), needs clarification
- Operational timetable simulation (builds on 5,2&1) OK, "RSIM"
See attached illustration.
Most important here is the UC run time calculation. I hereby suggest creating the use case in the railML community. As ownership relevant use is closest in the timetable community, I suggest doing the work in the TT working group. The good news is that Most of the work is already done! All infrastructure items required are already part of the SCTP UC! 😊 There is need for some minor clean-up work in relation between RTC and SCTP. I will post about this in the IS forum. What is missing is the rolling stock items. Thus, I suggest making a UC «RTCR»: RunTime Calculation for Rolling stock. Although the UC is RS scheme related, the use stems from the TT community (also there is currently no RS working group), thus the suggestion to do the work in the TT working group. I will make a cross post in the RS forum.
If I get the green light for the TT working group, I volunteer to make the first draft. 😊
High level content of RTCI:
- Tractive capabilities (like effort curve, adhesion...)
- Braking capabilities
- Physical properties (like weight and length)
What does the TT community think of this proposal?
Kind regards Torben Brand, Jernbanedirektoratet
[Updated on: Thu, 01 June 2023 19:33] by Moderator Report message to a moderator |
|
|
|
| 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: 162
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
