| Requirements for RTCI-a (Infrastructure) UC [message #3131] |
Thu, 21 September 2023 16:57  |
Torben Brand
Messages: 158
Registered: March 2016
|
Senior Member |
|
|
With reference to the post to create a run time calculation input parameter use case in the TT forum ( https://www.railml.org/forum/index.php?t=msg&th=906& start=0&)
We are currently working on the RTCI-a UC (sub-UC for infrastructure) in the SCTP working group. But I would also like to include the rest of the community through this post.
I suggest to add the following infrastructure elements to the RTCI-a UC:
- metadata
- operational point (OP)
- Reference point OP
- Stop marker
- topology
- Mileage change
- speed
- Deflecting speed
- gradient
- Tunnel (resistance)
- (main)signal & route
- Clearance (for main signal)
- Operational rules (limiting)
- electrficationChange
- trainProtectionSystemChange
- restrictions
Se attached image for illustration, and attached Excel sheet for an overview table with simple mapping towards railML3.2 and comments on the elements.
I have mapped the elements towards railML3.2 in the table bellow and also to requirements in the attribute table for railML3.2 attached and in the cloud: https://cloud.railml.org/s/Xe3WXrpciBtjstS (You find it in the folder: "Working group IS/UseCases/uc_SCTP/03_elementSpecification")
The Excel contains two sheets. One "RTCI-a high level" for just the main elements (26 rows) and one sheet "railML_3.2_uc-SCTP+RTCI-a" for all the attributes (with 10515 rows!).
I have also made a smallest possible model for RTC in NorRailView:
https://railoscope.com/tickets/bRbcASDgBifKJ9rM?modelId=64e5 d0e6bd09d86eb8d810cb
You can access it with this open link and download it in certified railML2.4nor. As version 3.2 is pending certification, it is not available for open download, but I have attached the file here for illustration purpose only.
[Updated on: Fri, 29 September 2023 13:19] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
