Soldato
Nearly, 10 day average for the two hour session but only on the day of the session for the 3 hours window. Apparently there is an algorithm that varies the benefit based on 1, 2, 3 hours etc session - in this case it works on around 2/3 of the usage difference.
I don't think it is.
before we had the technical definition rather than the power point which was in some weird semi coded language and equations.
However I think below bolded is key, it infers like we thought before that same days baselines would be used as the days used to calculate the actual usage.
"To correct for all day specific effects such as weather conditions the baseline profile will be in day adjusted by using actual Metered Data over the three hour period up until one hour before the relevant Settlement Period where the unit is delivering the service. This will be compared to the calculated baseline values and an additive adjustment applied to ensure that the profile created by the baseline best matches real data for the run up to the Settlement Period."
The net effect of 10 very low "normal" days or one "normal" day vs a highly increased single 3 hour period prior to the actual session is going to be very similar. Otherwise what are they comparing to to calculate the adjustment.
As ever they get a little wonky with language since you could take the very first statement "To create a Baseline Profile, at unit level, the last 60 days of actual metered data is used" as that when they are doing the in day check vs baseline they are in fact referring to this 60 day actual metered data.
However reading this (below) and per the original semi understandable version I am pretty convinced its the same benchmark being used (last 10 days of weekday non saving session usage for a weekday, or last 4 weekend days for a weekend one)