Q: Which usage of the fill level should FRBC.UsageForecast contain?

[lfse-slafleur]

FRBC.UsageForecast details the expected changes in the fill level. Should this profile contain all usages of the fill level? (Including the forecasted usage by operation modes) Or should it contain the usage except for the forecasted usage by operation modes?

An example to show why the difference is important:

1. Assuming it should contain all usage, then optimizing future behaviour of the asset becomes quite difficult. An optimisation algorithm wouldn't know with which operation modes the usage forecast is generated so it doesn't know how much fill level would be altered if another operation mode is chosen.

2. Assuming it is only the usage outside of expected operation modes, than this optimization becomes easier. The usage forecast will show the usage regardless of which operation mode is active when so an optimization algorithm can add the usage of the usage forecast to its optimum path of operation modes.

This latter case would then mean:

• An at-home-battery would NOT include charging or discharging in the usage forecast if it is part of the energy balancing strategy of the battery, but it could contain usage of the household on the battery if the strategy of the battery is to generate revenue on the energy markets.
• A full-electric heatpump would NOT include the effect on the inside temperature of the house when the heatpump is turned on (cooling or heating) but it could contain the effect on the inside temperature of the house due to other behaviours (such as opening the windows at a given point in time, heating up the house due to solar radiation)

[lfse-slafleur]

@wcoenraads @wilcowijbrandi @konsmanmj Perhaps you could outline the intent of FRBC UsageForecast?

[wcoenraads]

Good question! The intention is for the usage forecast to exclude any usage flowing from the current operation mode/actuator status. The CEM determines what the actuator should do, so that's in principle not a forecast but a controlled variable.

As you mention, this allows for much simpler optimization from the CEM. :)