UC:IL:HardwareAndCablePlan: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
m (Ferri Leberl moved page IS:UC:HardwareAndCablePlan to IL:UC:HardwareAndCablePlan: Namenskonvention)
(Standardization)
Line 1: Line 1:
'''Use case / {{Deu|Anwendungsfall}} / {{Fra|Scénario d’utilisation}}:'''
{{UseCase|IL||title=Hardware and cable plan}}


{{UC title}}
Hardware and cable plan; {{Deu|Hardware und Kabelplan}}; {{Fra|nom descriptif en Francais}}
Hardware and cable plan; {{Deu|Hardware und Kabelplan}}; {{Fra|nom descriptif en Francais}}


 
{{UC description}}
'''Description / {{Deu|Beschreibung}} / {{Fra|Description}}'''
 
* Cable plan
* Cable plan
* Parts Lists
* Parts Lists
Line 14: Line 13:
* Technical room, number of CPU boards, Container
* Technical room, number of CPU boards, Container


 
{{UC flows}}
'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}'''
 
Information Category:
Information Category:
* Topology (origin: railML IS schema or classic track plan)
* Topology (origin: railML IS schema or classic track plan)
* Cable plan (origin: railML IS schema or classic track plan)
* Cable plan (origin: railML IS schema or classic track plan)


 
{{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>}}'''
 
* infrastructure
* infrastructure


 
{{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.


<u>How often do the data change (update)?</u>
{{UC update}}
 
* static (not changing) on demand
* static (not changing) on demand


<u>How big are the data fragments to be exchanged (complexity)?</u>
{{UC complexity}}
 
* big (station/yard)
* big (station/yard)


<u>Which views are represented by the data (focus)?</u>
{{UC focus}}
 
* Energy
* Energy
* Construction
* Construction


<u>Which specific timetable data do you expect to receive/send (elements)?</u>
{{UC elements}}
 
* Number of elements (signals,  distant signals, repeater, supplementary signals,  point machines, Track vacancy detection ( axle counter)…..)
* Number of elements (signals,  distant signals, repeater, supplementary signals,  point machines, Track vacancy detection ( axle counter)…..)
* Position of elements
* Position of elements

Revision as of 16:00, 26 August 2016

Hardware and cable plan
Subschema: Interlocking
Stift.png (version(s) )
For general information on use cases see UC:Use cases


Use case / Anwendungsfall

Hardware and cable plan; Hardware und Kabelplan;

Description / Beschreibung

  • Cable plan
  • Parts Lists
  • Number of field element controller
  • Hardware indoor, outdoor (number of point machines, number of axle counters, number of signals, …)
  • Network components (router, switches, cable)
  • Power supply
  • Technical room, number of CPU boards, Container

Data Flows and Interfaces / Datenflüsse und Schnittstellen

Information Category:

  • Topology (origin: railML IS schema or classic track plan)
  • Cable plan (origin: railML IS schema or classic track plan)

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

  • infrastructure

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) on demand

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

  • big (station/yard)

Which views are represented by the data (focus)?

  • Energy
  • Construction

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

  • Number of elements (signals, distant signals, repeater, supplementary signals, point machines, Track vacancy detection ( axle counter)…..)
  • Position of elements
  • Block interface to foreign IXL
  • Level crossing
  • Tunnel gates
  • Bascule bridges
  • Slide detector