UC:RS:OperationalSimulation: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
m (Ferri Leberl moved page RS:UC:OperationalSimulation to UC:RS:OperationalSimulation: Vereinheitlichung)
 
({{mirror}})
Line 1: Line 1:
{{useCase|RS||title=Operational simulation|IS=1|TT=1|IL=1}}
{{mirror}}
 
{{UC title}}
Operational simulation; {{Deu|Betriebssimulation}}; {{Fra|nom descriptif en Francais}}
 
{{UC 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:
* 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
 
{{UC flows}}
* Provision of rollingstock data by railway operator and/or manufacturer
* Import of rollingstock data into the simulation system (currently manual)
 
{{UC interference}}
* infrastructure
* timetable
* interlocking
 
{{UC data}}
This section serves to specify the required data regarding certain aspects.
 
{{UC update}}
* on demand or on changes of RS
 
{{UC complexity}}
* depending on the number of various vehicle types and train formations
 
{{UC focus}}
* Technical, Performance
 
{{UC elements|RS}}
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)

Revision as of 17:41, 24 November 2019

🗒️ This page is mirrored from page UC:RS:OperationalSimulation in The railML® 2 wiki.  

Template loop detected: Template:Mirror