UC:IS:CADForRailwaySignaling: Difference between revisions
| [unchecked revision] | [unchecked revision] |
m (1 revision imported) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{ | {{useCase|IS|2.3|title=CAD for railway signalling|IL=1|reporter=RailComplete}} | ||
{{UC title}} | |||
CAD for railway signalling; {{Deu|CAD für Zugsignalisierung}}; {{Fra|nom descriptif en Francais}} | |||
{{UC 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. | |||
{{UC flows}} | |||
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. | |||
{{UC interference}} | |||
* interlocking | |||
{{UC data}} | |||
This section serves to specify the required data regarding certain aspects. | |||
{{UC update}} | |||
* weekly | |||
* daily | |||
{{UC complexity}} | |||
* big (station/yard) | |||
{{UC focus}} | |||
* Signaling | |||
* Geometry | |||
* Construction | |||
{{UC elements|IS}} | |||
Tracks, operation control elements (signal, balise, derailer, signs, etc.), interlocking, other infrastructure data. | |||
Revision as of 17:58, 3 February 2020
| CAD for railway signalling Subschema: Infrastructure Related subschemas: IL Reported by: RailComplete | |||
| |||
| For general information on use cases see UC:Use cases |
Use case / Anwendungsfall
CAD for railway signalling; CAD für Zugsignalisierung;
Description / Beschreibung
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
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®-Schemas
- interlocking
Characterizing Data / Charakterisierung der Daten
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.