Home » railML newsgroups » railml.infrastructure » [railML3] Suggestion for sub-use cases of use case "ETCS Track Net" (Suggestion to consider sub-use cases in the use case "ETCS Track Net")
[railML3] Suggestion for sub-use cases of use case "ETCS Track Net" [message #3029] Tue, 19 July 2022 08:16 Go to next message
Karl-Friedemann Jerosch is currently offline  Karl-Friedemann Jerosch
Messages: 10
Registered: May 2020
Junior Member
During the certification process, it became apparent that the use case "ETCS Track Net" is too general.
The different ways how infrastructure managers work can result in the following approach to introduce sub-use cases.

That's why we propose the railML sub-use cases within the "ETCS Track Net" use case:

  1. Data transfer from Infrastructure Manager (IM) to signaling supplier for decentralized ETCS solution (without balise group locations): ETCS Level 1
  2. Data transfer from Infrastructure Manager (IM) to signaling supplier for decentralized ETCS solution (with balise group locations): ETCS Level 1
  3. Data transfer from Infrastructure Manager (IM) to the signaling supplier for central ETCS solution (without balise group locations): ETCS Level 1 or Level 2 or Level 1+2
  4. Data transfer from Infrastructure Manager (IM) to the signaling supplier for central ETCS solution (with balise group locations): ETCS Level 1 or Level 2 or Level 1+2
  5. Data transfer from Signaling Supplier to Infrastructure Manager only with infrastructure data (control data set)
  6. Data transfer from Signaling Supplier to Infrastructure Manager with infrastructure data including the railML subschema "interlocking" with ETCS data (based on sub-use case 2)
  7. Data transfer from Signaling Supplier to Infrastructure Manager with infrastructure data including the railML subschema "interlocking" with ETCS data (based on sub-use case 4)
Note:
The schema version railML 3.2 currently contains the generally required information for an ETCS trackside project.
In individual cases, required but not yet available information in railML 3.3 must be supplemented or transferred in a traditional way outside railML (applies in particular to sub-use cases 1 and 2).

We are looking forward to your opinions.
Thank you and best regards from Karl & Martin.
Re: [railML3] Suggestion for sub-use cases of use case "ETCS Track Net" [message #3033 is a reply to message #3029] Mon, 01 August 2022 15:51 Go to previous message
Jörgen Strandberg is currently offline  Jörgen Strandberg
Messages: 15
Registered: August 2017
Junior Member
Hi,

I too recognize that there is a need to define what contents to be expected of a railml file at the different stages of data preparation:
-- Basic Signaling
-- ETCS specific design
-- Solution specific configuration

Let's build on this idea and see how we can agree on the details.
Previous Topic: [railML 2] IS:005 - ocp/@parentOcpRef Semantic Constraint
Goto Forum:
  


Current Time: Tue Aug 16 00:32:24 CEST 2022