ENH: energy-to-power ratio for storage technology

[Drowsle]

Feature Type

• Adding new functionality to tz-osemosys

• Changing existing functionality in tz-osemosys

• Removing existing functionality in tz-osemosys

Problem Description

Batteries usually have standardized storage capacity based on the power delivery. It is usually given as number of hours the battery can deliver at full power. For example, a [120MW, 4h] battery would equals to a [120MW, 480MWh] battery.

The power aspect and the storage aspect are de-coupled in OSeMOSYS and it can lead to situation where we would have 120MW battery with 20GWh worth of storage.

I think the solution is a fixed ratio between the power and the storage of a given technology

Feature Description

In the technologies.yaml setup file it would look like something like this :

• id: battery-technology
  long_name: Battery technology
  capacity_activity_unit_ratio: 31.536
  opex_fixed: 10
  capex: 1200
  operating_life: 40
  energy_to_power_ratio: 0.0144 #PJ/GW 4h -> 4/1000*3.6
  operating_modes:
  • id: GEN
    long_name: discharging mode
    description: discharging mode
    output_activity_ratio:
    primary-electricity: 1.
    from_storage: {

    all regions

    "*":
    # storage unit
    {"battery-storage": True}
    }
    opex_variable: 0
  • id: CHARGE
    long_name: charging mode
    description: charging mode
    input_activity_ratio:
    primary-electricity: 1.
    to_storage: {

    all region

    "*":
    # storage unit
    {"battery-storage": True}
    }
    opex_variable: 0
    capacity_gross_min: 0

--------------------------------------------

STORAGE UNITS

- Inputs are in petajoules (PJ)

- Outputs are in petajoules (PJ)

--------------------------------------------

storage:

• id: battery-storage
  capex: 0
  operating_life: 100
  residual_capacity: 0
  minimum_charge: 0
  initial_level: 0

If such a ratio is applied, in order to avoid confusion, one of the capex should take over the other. For example, consider the capex given by the power technology even if the storage has its own capex.