UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
mNo edit summary
No edit summary
Line 1: Line 1:
'''Use case / {{Deu|Anwendungsfall}} / {{Fra|Scénario d’utilisation}}:'''
{{useCase|IS|2.3|title=Exchange of planning parameters for interlocking with suppliers}}


{{UC title}}
Exchange of planning parameters for interlocking with suppliers; {{Deu|Austausch von Planungsparametern für Stellwerke mit Anbietern}}; {{Fra|nom descriptif en Francais}}
Exchange of planning parameters for interlocking with suppliers; {{Deu|Austausch von Planungsparametern für Stellwerke mit Anbietern}}; {{Fra|nom descriptif en Francais}}


 
{{UC description}}
'''Description / {{Deu|Beschreibung}} / {{Fra|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).
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.
Further usages for inventory queries are possible.
Line 11: Line 10:
[[Datei:Interlocking use case.png|Interlocking use case.png]]
[[Datei:Interlocking use case.png|Interlocking use case.png]]
   
   
 
{{UC flows}}
'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}'''
 
Import into planning tool: geo data, existing planning data, inventory data
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).
Export of planning tool: planning data, handing-over to the supplier (by using a database).


 
{{UC interference}}
'''Interference with other railML<sup>®</sup> schemas / {{Deu|Interferenz mit anderen railML<sup>®</sup>-Schemen}} / {{Fra|Interaction avec autres schemas railML<sup>®</sup>}}'''
 
* interlocking (see also: [[IS:UC:InterlockingEngineering |Interlocking Engineering]])
* interlocking (see also: [[IS:UC:InterlockingEngineering |Interlocking Engineering]])


 
{{UC data}}
'''Characterizing Data / {{Deu|Charakterisierung der Daten}} / {{Fra|Caractérisation des données}}'''
 
This section serves to specify the required data regarding certain aspects.
This section serves to specify the required data regarding certain aspects.


Line 35: Line 28:
   <li> Parameters of software elements (routes, flank protection for switches etc.) </ul>
   <li> Parameters of software elements (routes, flank protection for switches etc.) </ul>


<u>How often do the data change (update)?</u>
{{UC update}}
 
* yearly
* yearly
* monthly
* monthly
Line 42: Line 34:
* daily
* daily


<u>How big are the data fragments to be exchanged (complexity)?</u>
{{UC complexity}}
 
* very small (element)
* very small (element)
* small (operational point)
* small (operational point)
Line 50: Line 41:
* whole data set (network)
* whole data set (network)


<u>Which views are represented by the data (focus)?</u>
{{UC focus}}
 
* Signaling
* Signaling
* Geometry
* Geometry
Line 59: Line 49:
* Topology
* Topology


<u>Which specific timetable data do you expect to receive/send (elements)?</u>
{{UC elements}}
 
<ul>
<ul>
<li> Topology of the track network
<li> Topology of the track network

Revision as of 17:54, 23 June 2016

Exchange of planning parameters for interlocking with suppliers
Subschema: Infrastructure
Stift.png (version(s) 2.3)
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 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
Retrieved from "https://wiki2.railml.org/index.php?title=UC:IS:ExchangeOfPlanningParametersForInterlockingWithSuppliers&oldid=5187"