From railML 3 Wiki
Revision as of 16:58, 3 February 2020 by Documentation (talk | contribs) (1 revision imported)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
CAD for railway signalling
Subschema: Infrastructure
Related subschemas: IL 
Reported by: RailComplete
Stift.png                   (version(s) 3.1)
For general information on use cases see UC:Use cases

Use case / Anwendungsfall / Scénario d’utilisation

CAD for railway signalling; CAD für Zugsignalisierung; nom descriptif en Francais

Description / Beschreibung / Description

Engineers of the railway signaling discipline use a CAD tool to model a railway construction project. Each symbol in the CAD model can correspond to a railML element type (where relevant). The allows graphical modelling of railML documents which can then be exchanged with other tools.

Data Flows and Interfaces / Datenflüsse und Schnittstellen / Flux de données et interfaces

For the railway signalling discipline: track import, signalling import. Infrastructure + interlocking export. Generic topology information (e.g. electrification, track classification, ocp attributes) can be imported from external sources, e.g. from a database provided by the infrastructure manager.

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

  • interlocking

Characterizing Data / Charakterisierung der Daten / Caractérisation des données

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

How often do the data change (update)?

  • weekly
  • daily

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

  • big (station/yard)

Which views are represented by the data (focus)?

  • Signaling
  • Geometry
  • Construction

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

Tracks, operation control elements (signal, balise, derailer, signs, etc.), interlocking, other infrastructure data.