UC:IS:NetworkStatement: Difference between revisions
Jump to navigation
Jump to search
Topology
Geometry
Assets
Operational infrastructure elements
[unchecked revision] | [unchecked revision] |
m (1 revision imported) |
No edit summary |
||
Line 1: | Line 1: | ||
{{ | {{UseCase|IS|2.3|title=Network Statement|abbr=NEST|reporter=SŽDC|pdf={{UCpdf|3.1|https://documents.railml.org/schemas/usecase/railml-use-case_is-nest.pdf}}}} | ||
{{Missing information|topic=the use case|user=[[Benutzer:Vasco Paul Kolmorgen|Vasco Paul Kolmorgen]] ([[Benutzer Diskussion:Vasco Paul Kolmorgen|Diskussion]]) 14:23, 15. Mär. 2016 (CET)}} | |||
{{UC title}} | |||
Network Statement; {{Deu|Network Statement}}; {{Fra|nom Network Statement}} | |||
{{UC 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. | |||
{{UC flows}} | |||
The infrastructure managers are responsible for exporting all the required data. | |||
{{UC interference}} | |||
* none | |||
{{UC data}} | |||
This section serves to specify the required data regarding certain aspects. | |||
{{UC update}} | |||
* static (not changing) | |||
* yearly | |||
{{UC complexity}} | |||
* big (station/yard) | |||
* huge (region) | |||
* whole data set (network) | |||
{{UC focus}} | |||
* Geometry | |||
* Construction | |||
* Railway Operation | |||
{{UC elements|IS}} | |||
<li> Topology | |||
<ul> <li> micro level topology (tracks + track nodes)</li></ul> | |||
<ul> <li> macro level topology (lines + operational points)</li></ul> | |||
<ul> <li> support of different levels of detail</li></ul> | |||
<ul> <li> location referencing</li></ul> | |||
<ul> <li> orientation</li></ul> | |||
<ul> <li> grouping of elements</li></ul> | |||
<li> Geometry | |||
<ul> <li> <horizontalCurve> (radius)</li></ul> | |||
<ul> <li> <gradientCurve> (slope)</li></ul> | |||
<ul> <li> <superelevationCurve> (superelevation)</li></ul> | |||
<li> Assets | |||
<ul> <li> Signalling (train radio; communication system)</li></ul> | |||
<ul> <li> Electrification (voltage, frequency, contactLineType)</li></ul> | |||
<ul> <li> Rails (track gauge; clearance gauge; switch; crossing)</li></ul> | |||
<li> Operational infrastructure elements | |||
<ul> <li> <operationControlPoints> (id, name) | |||
<ul> <li> <propOperational> (operationalType)</li></ul> | |||
<ul> <li> <propService> (passenger)</li></ul> | |||
<ul> <li> <designator> (register, entry)</li></ul> | |||
</li></ul> | |||
( * no railML-attribute available for this information yet) |
Revision as of 17:58, 3 February 2020
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 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
The infrastructure managers are responsible for exporting all the required data.
Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen
- 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)
- <superelevationCurve> (superelevation)
- 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)
( * no railML-attribute available for this information yet)