You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Dutch large consumers, the peak cost component "resets" monthly. If the planning window spans across 2 months, this should be reflected in the commitment groups.
For a planning window spanning across 2 months, the monthly peak of the 1st month is used for the second month as well.
Workaround
Set both the site-peak-consumption and site-peak-production to "0 kW" to manually reset if the planning window crosses a month's end. This has the downside of not freely using the already established headroom in the 1st month (only for the part of the planning window that falls within the 1st month).
Expected behaviour
The commitment groups should be split up by event. For instance, if the sensor recording monthly peaks has an event resolution of 1 month, this should result in a separate commitment group for each month.
The text was updated successfully, but these errors were encountered:
For Dutch large consumers, the peak cost component "resets" monthly. If the planning window spans across 2 months, this should be reflected in the commitment groups.
Follow-up from #1144.
Current behaviour
For a planning window spanning across 2 months, the monthly peak of the 1st month is used for the second month as well.
Workaround
Set both the
site-peak-consumption
andsite-peak-production
to"0 kW"
to manually reset if the planning window crosses a month's end. This has the downside of not freely using the already established headroom in the 1st month (only for the part of the planning window that falls within the 1st month).Expected behaviour
The commitment groups should be split up by event. For instance, if the sensor recording monthly peaks has an event resolution of 1 month, this should result in a separate commitment group for each month.
The text was updated successfully, but these errors were encountered: