UC:IS:NetworkStatement
Jump to navigation
Jump to search
Topology
Geometry
Assets
Operational infrastructure elements
| Network Statement (NEST) Subschema: Infrastructure Reported by: SŽDC | |||||||||
| |||||||||
| For general information on use cases see UC:Use cases |
Use case / Anwendungsfall
Network Statement; Network Statement
Description / Beschreibung
The Network Statement (external link, 🇬🇧) covers the requirements for access and use of the rail network (route network) of the Railway_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
The Railway_infrastructure_manager ()s are responsible for exporting all the required data.
Interference with other railML® schemas / Interferenz mit anderen railML®-Schemas
- none
Characterizing Data / Charakterisierung der Daten
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)?
- micro level topology (tracks + track nodes)
- macro level topology (lines + operational points)
- support of different levels of detail
- location referencing
- orientation
- grouping of elements
- <horizontalCurve> (radius)
- <gradientCurve> (slope)
- Signalling (train radio; communication system)
- Electrification (voltage, frequency, contactLineType)
- Rails (track gauge; clearance gauge; switch; crossing)
- <operationControlPoints> (id, name)
- <propOperational> (operationalType)
- <propService> (passenger)
- <designator> (register, entry)