The steps of an event

A dispatch event runs from request to outcome, and each step leaves evidence.

Five steps of an event: request, accepted, metered, baseline, outcome.
  1. Record the requested action and time window.
  2. Check that the device accepted the instruction.
  3. Observe the metered response, meaning the power measured at the meter.
  4. Compare the response with the defined test or baseline.
  5. Record the outcome and investigate exceptions.

What a baseline is

Settle the reference first for a fair comparison. A baseline is the reference case that a result is compared with, such as usual energy use before the event. How it is built depends on the program or test.

Time and metering

A correct number can still answer the wrong question. Align the event window with the measurement timestamps. Then confirm the units, the direction of flow and where the meter sits.

Validation and settlement

Evidence of what a device did is not proof of what is payable. Settlement is the program's process for deciding payment. A command record alone does not establish payment.

Category reference: U.S. Department of Energy.

Common questions.

Does acceptance prove delivery?

Acceptance and measured outcome are separate parts of the record.

What if a result is outside tolerance?

Tolerance is the allowed gap between request and result. Record the exception, investigate the cause, and repeat the test after a correction.

Can a pilot establish the evidence?

Yes. Set the success criteria, measurements and review process before testing.

Ask your assistant.

Explain this page from Elastic Energy in plain language: https://elasticenergy.com/how-dispatch-is-validated

Keep exploring.