Complete the aggregator or program operator's DER enrollment process: submit device nameplate data (type, rated capacity, location, meter ID), execute the grid-services contract, and pass the ISO/utility's verification test (typically a test dispatch event confirming the DER responds correctly).
Establish the telemetry channel: most ISOs and VPP operators require 5-minute average real and reactive power telemetry; deliver via a secure SCADA/ICCP link, REST API push, or MQTT depending on the program operator's specification — confirm the exact protocol in the program manual.
Implement the baseline methodology as defined by the program: common approaches are the symmetric 10-of-10 (average of the 10 highest-use days in the prior 45 days excluding event days and weekends) or a regression-based customer baseline load (CBL) — the specific formula is program-specific and must match exactly for settlement.
Subscribe to dispatch signals from the program operator's notification channel (often REST webhook, OpenADR 2.0b VEN, or IEEE 2030.5 DERControl depending on the program); process the event payload to extract event start time, duration, target reduction, and any curtailment mode.
Execute the dispatch: translate the target reduction into per-device set-points, send commands to DER controllers, and confirm receipt; log command issuance time, acknowledgment time, and measured response within the required compliance window.
Submit settlement performance data after each event: actual measured load reduction versus baseline, per interval, in the program's required format; retain raw telemetry for audit for the duration specified in the contract.
Known gotchas
Baseline calculations are highly program-specific and the exact day-selection and adjustment rules are often buried in program tariff sheets or technical appendices; using a generic 'average of prior days' approach without matching the exact program formula will produce incorrect settlement amounts.
Many programs have minimum response time requirements (e.g., 10-minute notice to full response); DER controllers with slow communication or actuator latency will fail compliance tests — measure end-to-end dispatch latency from signal receipt to measured output change before enrolling.
Telemetry data gaps during an event are typically treated as non-performance by the program operator; implement redundant telemetry paths and local buffering so that data can be retransmitted after a communication outage.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp