General sales
AuraScore 83/100

Grid Flexibility and Demand Response Enrollment Specification

Specify commercial terms and technical dispatch rules for industrial demand response enrollment.

Use this template when selling demand-side management and grid balancing programs to large power consumers. It generates an actionable enrollment specification detailing capacity revenues, telemetry requirements, and event dispatch criteria.

Template

Role: Principal Grid Flexibility Sales Engineer specializing in industrial demand-side management and ancillary service monetization.

Context

  • Regional Grid Operator: {{grid_operator_name}}
  • Facility Type and Operations: {{facility_type}}
  • Available Curtailable Load: {{curtailable_load_mw}}
  • Required Notification and Response Time: {{response_time_minutes}}
  • Commercial Incentive Model: {{incentive_model}}
  • Existing Telemetry & Metering: {{metering_infrastructure}}

Task

Develop a technical and commercial sales onboarding specification that qualifies the facility for grid flexibility programs and outlines revenue realization terms.

Method

  1. Analyze {{facility_type}} baseline energy profiles to validate that {{curtailable_load_mw}} can be reliably shed or shifted without operational failure.
  2. Map dispatch parameters against {{grid_operator_name}} market rules for capacity and fast frequency response.
  3. Audit {{metering_infrastructure}} to identify necessary telemetry gateways and revenue-grade sub-metering additions.
  4. Detail operational response protocols capable of achieving full load drop within {{response_time_minutes}}.
  5. Structure the commercial yield forecast under {{incentive_model}}, distinguishing between availability payments and dispatch event energy payments.
  6. Define penalties, non-performance thresholds, and safe-harbor maintenance windows for the asset owner.
  7. Outline data integration protocols linking the facility's control systems with {{grid_operator_name}} dispatch signals.

Constraints

  • MUST detail exact operational curtailment steps and telemetry latency requirements.
  • MUST NOT exceed the operational limits native to {{facility_type}}.
  • Financial models MUST segregate fixed capacity revenue from variable dispatch earnings.
  • Telemetry specifications must directly reference {{metering_infrastructure}}.

Output format

A 4-section technical sales specification:

  1. Program Eligibility & Asset Profile (max 200 words)
  2. Operational Dispatch & Curtailment Architecture (step-by-step workflow)
  3. Commercial Revenue & Settlement Specification (structured data table)
  4. Integration & Commissioning Prerequisite Checklist (6-8 items)

Self-review

  • Ensure response latency aligns with {{response_time_minutes}}.
  • Verify revenue mechanics match {{incentive_model}}.
  • Check that constraints regarding facility operational continuity are strictly honored.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-general
energy-utilities
grid-services
demand-response
utilities