Versions Compared

Old Version 62

changes.mady.by.user Support

Saved on

compared with

New Version Current

changes.mady.by.user Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel3

...

The following available drivers are available:

per section are listed on the following page: Driver

Input FieldDescriptionUnitPresetting

Name

Sales entity nameFree text"FIT" + Index

Revenue Model


Feed-in-Tariff 

Select this option if you receive a feed-in-tariff. In addition, you can enter a market price and then choose how the two prices interact.

PPA

Select this option if you have a Power Purchase Agreement (PPA). The following PPAs are available: 

  • Pay-as-Produced: In case you have a variable production profile. This means that a fixed tariff is paid for each produced unit, regardless of current market prices.
  • Annual Baseload: In case you have a fixed delivery profile which is constant during the year. The difference between the amount of electricity actually generated and the defined amount must be bought and sold on the electricity market. 
  • Monthly Baseload: In case you have a fixed delivery profile which varies from month to month. The difference between the amount of electricity actually generated and the defined amount must be bought and sold on the electricity market. 
Market PriceSelect this option if the electricity produced is sold on the electricity market.


SelectionSelection

Anchor
Intera
Intera
Interaction Group

Selection of the Interaction Group (compare Price Interaction):


Feed-in-Tariff Group

Sale entities of this group are summed up with Sales of the same Group (Feed-in-Tariff Group) before the interaction takes effect.

For example for the German Renewable Energy Act "Erneuerbare-Energien-Gesetz" (EEG).

Market Price Group

Sale entities of this group are summed up with Sales of the same Group (Market Price Group) before the interaction takes effect.

For sells on the energy market, for example direkt sells.

NoneSale entities (remaining) are directly summed up and Interaction takes effect.


SelectionFeed-in-Tariff Group

Anchor
Treiber
Treiber
Driver

Include Page
Driver
Expand
titleDriver details
SelectionProduction

Value

Input of a value proper to the selected driver.

Bounds

With these functions caps and floors can be defined for the Sales.

Floor

The Sales corresponds to a floor which depends on a driver.

The following drivers are available:


Expand
titleDriver details

Include Page
Driver
Driver


Cap

The Sales corresponds to a cap which depends on a driver.

The following drivers are available:


Expand
titleDriver details

Include Page
Driver
Driver


Include Page
Min/Max
Min/Max

SelectionFix per Production Unit

Start

Beginning of the Sales entity defined through a Date Choice Box. For example: "first time at transaction", that is Transaction + 0 months.

The entered month corresponds to the first day of this month (inclusive). For example: Start 01 /2015 means that the Sales entity is considered from 01.01.2015 according to the Driver/Value input.



Model


Fix

The End is defined by a Date Choice Box.

Quotal

The End depends on the attainment of an accumulated Production per assigned Production Unit since Production Unit Start.


SelectionFix

Anchor
ErlösE
ErlösE
End


Fix

For example: "Production Unit Start + 20 years".

The entered month refers to the last day of this month (inclusive). For example: An end 12 /2015 mean that the Sale entity is considered till 12.31.2015 according to Driver/Value input

Quotal

For example: "10'000 MWh" & "From First Production Unit Start", which means the accumulated Production > 10'000 MWh from first Production Unit start will not be remunerated according to this Sale entity.

The End of the Sale entity is defined as the accumulated Production per assigned Production Unit since Production Unit Start. This means the Sales entity is considered till the attainment of the accumulated Production according the End input of the corresponding Production Unit

For example: An input of "10'000 MWh with 2 assigned Production Units" means that the Sale entity is valid till the particular Production Unit produced 10'000 MWh since Production Unit Start. A accumulated Production > 10'000 will not be remunerated according to this Sale entity.

Note: For projects with heterogeneous properties according the quotal end (for example Production Unit 1 has 10'000 MWh and Production Unit 2 has 15'000 MWh) you should use two different Sale entities.


Date Choice Box

or

MWh


Production Unit End + 0 months

or

0

Production Units

Selection of the concerned Production Units. The presetting is that all Production Units  are selected. With a change to "Some" individual Production Units can be added.

Production Unit AllocationAll

Indexation

Allocation to an Indexation, for example an inflation of 2%. Is no Indexation allocated the concerned values stay constant over time.

Indexation AllocationNone

Methods of Payment

Include Page
Method of Payment
Method of Payment
Methods of Payment AllocationNone

...