Demand Response 101: Program Foundations
A practical primer on program structure, event timelines, participant performance, and where baseline and telemetry fit in real demand response operations.
What demand response teams are actually coordinating
Demand response programs sit between customer load, utility or ISO market goals, and the control systems that coordinate event execution. Whether the signal is economic, reliability-driven, or tied to flexible DER orchestration, teams still need a common operating model: identify who is participating, decide what the event is asking them to do, and prove later what happened.
This is why baseline engineering and telemetry QA matter so much. Programs do not get judged only on whether an event was sent. They get judged on whether the event was measurable, attributable, and auditable.
The event lifecycle in simple terms
A typical program lifecycle includes enrollment, telemetry qualification, event dispatch, participant response, and post-event performance review. Different programs rename these steps, but the engineering burden is similar: event timing must be clear, data needs to arrive with the expected interval structure, and performance calculations must be explainable to internal reviewers or external market operators.
GridMango is most useful in the middle of that lifecycle: validating data before analysis, testing protocol signals before production rollout, and stress-testing baseline assumptions before they affect settlement outcomes.
Why baseline and telemetry are inseparable
Baseline methods are not independent of data quality. The most elegant same-day adjustment configuration will still produce misleading outputs if timestamps drift, interval coverage is incomplete, or event windows do not align to the same convention across tools and utility systems.
A strong DR team treats baseline setup and telemetry QA as a single workflow. That is the mindset we encourage throughout the Academy and the platform.