UC:IL:HardwareAndCablePlan: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][checked revision]
({{mirror}})
(-fra)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{mirror}}
{{UseCase|IL|title=Hardware and cable plan}}
 
{{UC title}}
Hardware and cable plan; {{Deu|Hardware und Kabelplan}}
 
{{UC description}}
* 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
 
{{UC flows}}
Information Category:
* Topology (origin: railML IS schema or classic track plan)
* Cable plan (origin: railML IS schema or classic track plan)
 
{{UC interference}}
* infrastructure
 
{{UC data}}
This section serves to specify the required data regarding certain aspects.
 
{{UC update}}
* static (not changing) on demand
 
{{UC complexity}}
* big (station/yard)
 
{{UC focus}}
* Energy
* Construction
 
{{UC elements|IL}}
* 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

Latest revision as of 13:51, 13 March 2023

Hardware and cable plan
Subschema: Interlocking
Stift.png (version(s) not yet specified)
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 IL 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