UC:IS:NetworkStatement

From wiki.railML.org
Jump to: navigation, search
Network Statement
(NEST)
Subschema: Infrastructure
Reported by: SŽDC
This page refers to version 2.3 of railML®.
Therefore the content is possibly outdated.
The current version is 2.4.
For general information on use cases see UC:Use cases

Missinginformation.png In this article there is information missing with respect to the use case. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion pageVasco Paul Kolmorgen (Diskussion) 14:23, 15. Mär. 2016 (CET)

Use case / Anwendungsfall / Scénario d’utilisation

Network Statement; Network Statement; nom Network Statement

Description / Beschreibung / Description

The Network Statement covers the requirements for access and use of the rail network (route network) of the infrastructure manager. It provides all the technical and operational information that is necessary for entities entitled to access the network and use track capacity to carry out their rail traffic services and operate their rollingstock on the rail network.

Data Flows and Interfaces / Datenflüsse und Schnittstellen / Flux de données et interfaces

The infrastructure managers are responsible for exporting all the required data.

Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen / Interaction avec autres schemas railML®

  • none

Characterizing Data / Charakterisierung der Daten / Caractérisation des données

This section serves to specify the required data regarding certain aspects.

How often do the data change (update)?

  • static (not changing)
  • yearly

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

  • big (station/yard)
  • huge (region)
  • whole data set (network)

Which views are represented by the data (focus)?

  • Geometry
  • Construction
  • Railway Operation

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

  • Topology
    • micro level topology (tracks + track nodes)
    • macro level topology (lines + operational points)
    • support of different levels of detail
    • location referencing
    • orientation
    • grouping of elements
  • Geometry
    • <horizontalCurve> (radius)
    • <gradientCurve> (slope)
    • <superelevationCurve> (superelevation)
  • Assets
    • Signalling (train radio; communication system)
    • Electrification (voltage, frequency, contactLineType)
    • Rails (track gauge; clearance gauge; switch; crossing)
  • Operational infrastructure elements
    • <operationControlPoints> (id, name)
      • <propOperational> (operationalType)
      • <propService> (passenger)
      • <designator> (register, entry)


    ( * no railML-attribute available for this information yet)