UC:RS:TractionPowerSupplySimulation: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Standardization)
No edit summary
Line 35: Line 35:
* Energy
* Energy


{{UC elements}}
{{UC elements|RS}}
Expected elements/attributes in addition to “Operational simulation”:
Expected elements/attributes in addition to “Operational simulation”:



Revision as of 16:49, 22 September 2016

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


Use case / Anwendungsfall

Traction power supply simulation; Simulierung der Bahnstromversorgung;

Description / Beschreibung

For various purposes it is necessary to simulate the (electrical) traction power supply network during the process of railway operation for a fragment or an entire network in order to investigate questions like:

  • rating of new equipment
  • load evaluation of existing equipment
  • evaluation for weak points
  • feasibility of network changes (time table, rolling stock, electrical equipment)
  • investment strategy for electrical equipment
  • calculation of electromagnetic fields

The electrical simulation is not possible with the necessary accuracy without simulating the process of railway operation. Thus this use case is always an addon to the one of „Operational simulation“.

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

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
  • Energy

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

Expected elements/attributes in addition to “Operational simulation”:

  • Mandatory elements for motored vehicles: propulsion (voltage, frequency, power, tractiveCurrent[valueTable], totalTractEfficiency/tractiveVehicleEfficiency[valueTable], auxiliarySupply (power)
  • Additional mandatory elements for vehicles with regeneration brake: propulsion (brakeCurrent[valueTable], brakeCurrentLimitation[valueTable], totalBrakeEfficiency/brakeVehicleEfficiency[valueTable], maxRegenerativeVoltage)
  • Additional mandatory elements for vehicles with voltage dependent control: propulsion (tractiveCurrentLimitation[valueTable], tractionOffUndervoltageThreshold)
  • Additional mandatory elements for vehicles with energy storage: energyStorage (maximumCurrentCharging, maximumCurrentDischarging, maximumPowerCharging, maximumPowerDischarging, maximumChargingEnergy, meanStorageEfficiency/{chargingEfficiency, dischargingEfficiency})
  • Mandatory elements for non-motored vehicles: wagon (auxiliaryPowerConsumption)