UC:RS:OperationalSimulation: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(insert of content)
 
(Standardization)
Line 1: Line 1:
'''Use case / {{Deu|Anwendungsfall}} / {{Fra|Scénario d’utilisation}}:'''
{{useCase|RS||title=Operational simulation|IS=1|TT=1|IL=1}}


{{UC title}}
Operational simulation; {{Deu|Betriebssimulation}}; {{Fra|nom descriptif en Francais}}
Operational simulation; {{Deu|Betriebssimulation}}; {{Fra|nom descriptif en Francais}}


 
{{UC description}}
'''Description / {{Deu|Beschreibung}} / {{Fra|Description}}'''
 
For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire network in order to investigate questions like:
For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire network in order to investigate questions like:
* construction/fine tuning of time table
* construction/fine tuning of time table
Line 14: Line 13:
* feasibility studies for new infrastructure
* feasibility studies for new infrastructure


 
{{UC flows}}
'''Data Flows and Interfaces / {{Deu|Datenflüsse und Schnittstellen}} / {{Fra|Flux de données et interfaces}}'''
 
* Provision of rollingstock data by railway operator and/or manufacturer
* Provision of rollingstock data by railway operator and/or manufacturer
* Import of rollingstock data into the simulation system (currently manual)
* Import of rollingstock data into the simulation system (currently manual)


 
{{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
* timetable
* timetable
* interlocking
* interlocking


 
{{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}}
 
* on demand or on changes of RS
* on demand or on changes of RS


<u>How big are the data fragments to be exchanged (complexity)?</u>
{{UC complexity}}
 
* depending on the number of various vehicle types and train formations
* depending on the number of various vehicle types and train formations


<u>Which views are represented by the data (focus)?</u>
{{UC focus}}
 
* Technical, Performance
* Technical, Performance


<u>Which specific timetable data do you expect to receive/send (elements)?</u>
{{UC elemens}}
 
Mandatory elements/attributes:
Mandatory elements/attributes:
* formation (ID, name); trainOrder; vehicleRef (orderNumber, vehicleRef, vehicleCount)
* formation (ID, name); trainOrder; vehicleRef (orderNumber, vehicleRef, vehicleCount)

Revision as of 17:45, 21 July 2016

Operational simulation
Subschema: Rollingstock
 
Related subschemas: IS IL TT 
Stift.png (version(s) )
For general information on use cases see UC:Use cases


Use case / Anwendungsfall

Operational simulation; Betriebssimulation;

Description / Beschreibung

For various purposes it is necessary to simulate the process of railway operation for a fragment or an entire network in order to investigate questions like:

  • construction/fine tuning of time table
  • feasibility of time table
  • stability of time table
  • driving capability of rollingstock
  • capacity of infrastructure
  • feasibility studies for new infrastructure

Data Flows and Interfaces / Datenflüsse und Schnittstellen

  • Provision of rollingstock data by railway operator and/or manufacturer
  • Import of rollingstock data into the simulation system (currently manual)

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

  • infrastructure
  • timetable
  • interlocking

Characterizing Data / Charakterisierung der Daten

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

How often do the data change (update)?

  • on demand or on changes of RS

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

  • depending on the number of various vehicle types and train formations

Which views are represented by the data (focus)?

  • Technical, Performance

Template:UC elemens Mandatory elements/attributes:

  • formation (ID, name); trainOrder; vehicleRef (orderNumber, vehicleRef, vehicleCount)
  • vehicle (ID, name, length, speed, bruttoWeight, tareWeight/nettoWeight, bruttoAdhesion), engine (propulsion-ID, rotationMassFactor, tractiveEffort[valueTable]), wagon (rotationMassFactor), vehicleBrakes (mechanicalBrakeEffort[valueTable])

optional:

  • formation (trainResistance[valueTable]); trainBrakes (meanDeceleration)