Create energy system model (ES), aggregated to entire ABW region
Make it work with the interfaces (the general workflow (UI -> backend -> UI) is outlined in #8)
Energy system
You may wanna start by using the oemof-B3 model as it includes most of the components below. Maybe we can make use of the same structure.
(components I expect to be made variable through the app are marked bold)
buses: electricity, decentral heat, central heat
feedin
fixed
electricity
wind, PV roof, PV ground, bioenergy (UI setting for all: nominal power, use normalized feedin timeseries for all)
dispatched
electricity
import/shortage
electricity/heat
CCGT, small CHP
heat
other sources (wood, gas, ...)
transformers
electricity -> heat
decentral: heat pumps (maybe differentiate between ground- and air-sourced) (UI setting: share of HP in heating systems)
central: boilers or heat pumps (UI setting: ?)
demand
fixed
electricity
emobility (UI setting: share of EV), demand HH (UI setting: energy saving), demand CTSA (commerce, trade, services, agriculture) (UI setting: energy saving), demand industry (UI setting: energy saving)
heat
demand HH (UI setting: energy saving or refurbishment rate), demand CTSA (UI setting: energy saving or refurbishment rate), demand industry (UI setting: energy saving)
storages
large scale batteries (UI setting: nominal capacity or something more comprehensible)
decentral heat storages (UI setting: nominal capacity or something more comprehensible)
central heat storages (UI setting: nominal capacity or something more comprehensible)
Notes
For the other commodities (wood, gas, ..) needed for heating please check if we need additional buses and sources or if we can simplify this by using a shortage source (emissions need to be considered).
In this approach, flexibility can be freely used (e.g. heat storages of municipality 1 by municipality 2) disgegarding the actual location (or exchange capacity) which leads to a significant overestimation of flexibility. Maybe you have ideas on how to cope with or quantify this without blowing up the model too much? How has this been done in oemof-B3 which used a 2-node system?
With the two PRs it is possible to avoid the usage of transmissions between regions and the following components or energy carriers can be modelled within oemoflex:
Tasks
Energy system
You may wanna start by using the oemof-B3 model as it includes most of the components below. Maybe we can make use of the same structure.
(components I expect to be made variable through the app are marked bold)
Notes
Some material
Please drop me a note if something remains unclear.