Skip to content

Commit

Permalink
add support_policies documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
maurerle committed Jan 22, 2024
1 parent 4fb86b6 commit 8ea65ae
Show file tree
Hide file tree
Showing 2 changed files with 74 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/source/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,7 @@ Documentation
* :doc:`bidding_agents`
* :doc:`learning`
* :doc:`assume`
* :doc:`support_policies`

.. toctree::
:hidden:
Expand All @@ -90,6 +91,7 @@ Documentation
bidding_agents
learning
assume
support_policies


Indices and tables
Expand Down
72 changes: 72 additions & 0 deletions docs/source/support_policies.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
.. SPDX-FileCopyrightText: ASSUME Developers
..
.. SPDX-License-Identifier: AGPL-3.0-or-later
######################
Support Policies
######################

Support Policies are a very important feature when considering different energy market designs.
A support policy allows to influence the cash flow of unit, making decisions more profitable.

One can differentiate between support policies which influence the available market capacity (product_type=`energy``) and those which do not.

If the product_type is `energy`, the volume used for the contract can not be additionally bid on the EOM.


Example Policies
=====================================


Feed-In-Tariff - FIT
--------------------

To create a Feed-In-Tariff (Einspeisevergütung) one has a contract which sets a fixed price for all produced energy.
The energy can not be additionally sold somewhere else (product_type=`energy`).

The Tariff is contracted at the beginning of the simulation and is valid for X days (1 year).

The payout is executed on a different repetition schedule (monthly).
For this, the output_agent is asked how much energy an agent produced in the timeframe.

This is essentially the same as a Power Purchase Agreement (PPA), except that the payment of FIT is continuous and not monthly or yearly.


Fixed Market Premium - MPFIX
----------------------------

A market premium is paid on top of the market results, based on the results.
As the volume does not influcence the market bidding, the product_type is `financial_support`
So a Market premium is contracted at the beginning of the simulation and is valid for X days (1 year).

The payout is executed on a different repetition schedule (monthly).
For this, the output_agent is asked how much energy an agent produced in the timeframe and what the clearing price of the market with name "EOM" was.
The differences are then calculated and paid out on a monthly base.

This mechanism is also known as One-Sided market premium

Variable Market Premium - MPVAR
-------------------------------

The Idea of the variable market premium is to be based on some kind of market index (like ID3) received from the output agent.


Capacity Premium - CP
---------------------

A capacity premium is paid on a yearly basis for a technology.
This is done in € per installed MW of capacity.
It allows to influence the financial flow of plants which would not be profitable.

Contract for Differences - CfD
------------------------------

A fixed LCoE is set as a price, if an Agent accepts the CfD contract,
it has to bid at the hourly EOM - the difference of the market result is paid/received to/from the contractor.


Swing Contract
--------------

Actor
^^^^^

0 comments on commit 8ea65ae

Please sign in to comment.