UC:IS:ETCS track net: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(adding proposal for changed use case description)
(exchanging the figure for visualizing the data flows of the use case)
Line 10: Line 10:


{{UC flows}}
{{UC flows}}
[[File:ETCS TrackNet DataFlows.png|thumb|Transfer of railway infrastructure data into the {{external|https://de.wikipedia.org/wiki/Radio_Block_Centre|Radio Block Centre|lang=de|visited=2018-04-23|comment=RBC on Wikipedia}}]]
[[File:ETCS_dataFlows_02a.png|thumb|Transfer of railway infrastructure data into the {{external|https://de.wikipedia.org/wiki/Radio_Block_Centre|Radio Block Centre|lang=de|visited=2018-04-23|comment=RBC on Wikipedia}}]]
{{missing information|topic=the data flows|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 17:53, 10 April 2018 (CEST)}}
{{missing information|topic=the data flows|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 17:53, 10 April 2018 (CEST)}}


Revision as of 13:11, 29 March 2019

ETCS Track Net
(ETCS)
Subschema: Infrastructure
 
Related subschemas: IL 
Reported by: Thales
Stift.png (version(s) 3.2)
For general information on use cases see UC:Use cases


Use case / Anwendungsfall

ETCS track net

Description / Beschreibung

ETCS track net covers the requirements for access and use of the rail network of the infrastructure manager in microscopic way. It provides all the technical and operational information that is necessary for entities entitled to access the network, determine train positions and generate a movement authority for the train.

On an ETCS equipped railway line, the onboard ATPs are controlled by Movement Authority (MA) messages from a wayside RBC or LEU. These messages contain detailed information about certain aspects of the infrastructure, e.g. balises, speed restrictions, gradients and track conditions. This use case aims at modelling all infrastructure data necessary for generating MAs, as defined by SUBSET-026, version 3.x.

Data Flows and Interfaces / Datenflüsse und Schnittstellen

Transfer of railway infrastructure data into the Radio Block Centre (external link, 🇩🇪, visited on 2018-04-23; RBC on Wikipedia)

Missinginformation.png In this article there is information missing with respect to the data flows. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion page. Ferri Leberl (talk) 17:53, 10 April 2018 (CEST)

Interference with other railML® schemas / Interferenz mit anderen railML®-Schemas

Characterizing Data / Charakterisierung der Daten

How often do the data change (update)?

  • Regular changes

How big are the data fragments to be exchanged (complexity)?

  • Big station (yard)
  • Huge (region)
  • Whole date set (network)

Which views are represented by the data (focus)?

  • Topology: track network, line network
  • Construction: assets along the track / line

Which specific data do you expect to receive/send (elements)?

Common
  • electrificationSystems
  • speedProfiles
Topology
  • netElements
  • netRelations
  • networks
Geometry
  • gradientCurve (slope)
FunctionalInfrastructue
  • balises
  • borders
  • bufferStops
  • electrifications
  • levelCrossings
  • lines
  • platforms
  • restrictionAreas
  • signals
  • speeds
  • switches
  • tracks
  • trainDetectionElements
  • Signalling (train radio; communication system)
Retrieved from "https://wiki2.railml.org/index.php?title=UC:IS:ETCS_track_net&oldid=9749"