UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
({{mirror}})
(-fra)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{mirror}}
{{useCase|IS|title=Exchange of planning parameters for interlocking with suppliers|IL=1|reporter=IS}}
 
{{UC title}}
Exchange of planning parameters for interlocking with suppliers; {{Deu|Austausch von Planungsparametern für Stellwerke mit Anbietern}}
 
{{UC description}}
All the planning parameters, which are necessary to build an interlocking (hard- and software), have to be given to the supplier. The content of the data exchange is the result of the planning process, so the data are provided by a specialized planning tool (e.g. ProSig).
Further usages for inventory queries are possible.
 
[[file:Interlocking use case.png|800px|Interlocking use case.png]]
{{UC flows}}
Import into planning tool: geo data, existing planning data, inventory data
Export of planning tool: planning data, handing-over to the supplier (by using a database).
 
{{UC interference}}
* interlocking (see also: [[IS:UC:InterlockingEngineering |Interlocking Engineering]])
 
{{UC data}}
This section serves to specify the required data regarding certain aspects.
 
Complete content of a planning for an interlocking:
<ul>
  <li> Topology and geometry of the track network (2-dimensional) with punctual information about height and superelevation
  <li> Parameters and position of hardware elements (signals, switches etc.)
  <ul> <li> Positioning for track-related elements based on topology
      <li> Positioning for other elements based on coordinates </ul>
  <li> Parameters of software elements (routes, flank protection for switches etc.) </ul>
 
{{UC update}}
* yearly
* monthly
* weekly
* daily
 
{{UC complexity}}
* very small (element)
* small (operational point)
* big (station/yard)
* huge (region)
* whole data set (network)
 
{{UC focus}}
* Signaling
* Geometry
* Construction
* Statistics
* Energy
* Topology
 
{{UC elements|IS}}
<ul>
<li> Topology of the track network
<ul> <li> Nodes, edges
      <li> Inner topology: connections between edges or marker at edges for correct routing at switches </ul>
<li> Geometry of the track network and lines
<ul> <li> Nodes, edges
      <li> For edges: length, radius/curvature
      <li> Additional: punctual information about height and superelevation </ul>
<li> Infrastructure elements, e. g.
<ul> <li> Platforms and platform edges: <i>position, height, length, identifier for user (e.g. “Bahnsteig A”)</i>
      <li> Signals: <i>name, position, effective direction, type, operational function, signaling system, construction details (e.  g. height, fundament type, height of light point, diffusion disc), functional details (e  g. passing non-stop allowed, clearance of overlap), energy and information supply</i>
      <li> Switches: <i>e. g. name, type, basic form, isolation, kind of switch signal, operation mode, priority position, radius and possible speed per leg, kind of point machine(s), energy and information supply</i>
      <li> Level crossings: <i>name, position, construction details, functional details, energy and information supply</i>
      <li> Elements of automatic train control: <i>position, construction details, functional details, energy and information supply</i>
      <li> Key locks or lock combination: <i>name, position, energy and information supply</i>
      <li> Bridges, tunnels: <i>position, length along the topology</i></ul>
</ul>
 
{{interwiki}}

Latest revision as of 13:47, 13 March 2023

Exchange of planning parameters for interlocking with suppliers
Subschema: Infrastructure
 
Related subschemas: IL 
Reported by: IS
Stift.png (version(s) not yet specified)
For general information on use cases see UC:Use cases


Use case / Anwendungsfall

Exchange of planning parameters for interlocking with suppliers; Austausch von Planungsparametern für Stellwerke mit Anbietern

Description / Beschreibung

All the planning parameters, which are necessary to build an interlocking (hard- and software), have to be given to the supplier. The content of the data exchange is the result of the planning process, so the data are provided by a specialized planning tool (e.g. ProSig). Further usages for inventory queries are possible.

Interlocking use case.png

Data Flows and Interfaces / Datenflüsse und Schnittstellen

Import into planning tool: geo data, existing planning data, inventory data Export of planning tool: planning data, handing-over to the supplier (by using a database).

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

Characterizing Data / Charakterisierung der Daten

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

Complete content of a planning for an interlocking:

  • Topology and geometry of the track network (2-dimensional) with punctual information about height and superelevation
  • Parameters and position of hardware elements (signals, switches etc.)
    • Positioning for track-related elements based on topology
    • Positioning for other elements based on coordinates
  • Parameters of software elements (routes, flank protection for switches etc.)

How often do the data change (update)?

  • yearly
  • monthly
  • weekly
  • daily

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

  • very small (element)
  • small (operational point)
  • big (station/yard)
  • huge (region)
  • whole data set (network)

Which views are represented by the data (focus)?

  • Signaling
  • Geometry
  • Construction
  • Statistics
  • Energy
  • Topology

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

  • Topology of the track network
    • Nodes, edges
    • Inner topology: connections between edges or marker at edges for correct routing at switches
  • Geometry of the track network and lines
    • Nodes, edges
    • For edges: length, radius/curvature
    • Additional: punctual information about height and superelevation
  • Infrastructure elements, e. g.
    • Platforms and platform edges: position, height, length, identifier for user (e.g. “Bahnsteig A”)
    • Signals: name, position, effective direction, type, operational function, signaling system, construction details (e. g. height, fundament type, height of light point, diffusion disc), functional details (e g. passing non-stop allowed, clearance of overlap), energy and information supply
    • Switches: e. g. name, type, basic form, isolation, kind of switch signal, operation mode, priority position, radius and possible speed per leg, kind of point machine(s), energy and information supply
    • Level crossings: name, position, construction details, functional details, energy and information supply
    • Elements of automatic train control: position, construction details, functional details, energy and information supply
    • Key locks or lock combination: name, position, energy and information supply
    • Bridges, tunnels: position, length along the topology