Event priority
Event Priority determines the order in which overlapping events are settled (or which event is settled for which portion of the demand reduction).
Note: Settlement is calculated based upon energy consumption even though committed reduction is defined as a demand value. Committed reduction is shown as its equivalent consumption value in the example below.
Mandatory events using the "Firm Demand minus Actual" or "Baseline minus Firm Demand" settlement methods cannot overlap another event, but instead can be set to replace such an existing event.
Example - An operator issues the following events for the same meter.
|
Block |
Start Time |
End Time |
Committed Reduction (kWh) |
Baseline (kWh) |
Incremental Baseline (kWh) |
Actual (kWh) |
Actual Reduction (kWh) |
Compensated Reduction (kWh) |
|---|---|---|---|---|---|---|---|---|
|
1 |
12:00 |
13:00 |
100 |
500 |
500 |
310 |
190 |
190 |
|
2 |
13:00 |
14:00 |
100 |
500 |
500 |
320 |
180 |
180 |
|
3 |
14:00 |
15:00 |
100 |
500 |
500 |
315 |
185 |
100 |
|
4 |
15:00 |
16:00 |
100 |
500 |
500 |
325 |
175 |
100 |
|
Block |
Start Time |
End Time |
Committed Reduction (kWh) |
Baseline (kWh) |
Incremental Baseline (kWh) |
Actual (kWh) |
Actual Reduction (kWh) |
Compensated Reduction (kWh) |
|---|---|---|---|---|---|---|---|---|
|
1 |
14:00 |
15:00 |
100 |
500 |
400 |
315 |
85 |
85 |
|
2 |
15:00 |
16:00 |
100 |
500 |
400 |
325 |
75 |
75 |
|
3 |
16:00 |
17:00 |
100 |
500 |
500 |
320 |
180 |
180 |
|
4 |
17:00 |
18:00 |
100 |
500 |
500 |
320 |
180 |
180 |
The overlapping hours of 14:00 to 16:00 are settled for the high priority event first. That event gets credit for its committed reduction. The low priority gets credit for the remaining reduction.