Go to market · 4 min read
DER Software Pilot to Production: A Utility Evidence Checklist
By VPPdirectory · Published · Reviewed and updated · Editorial contact: Jared Theaman
Moving a DER or VPP software pilot into production requires an agreed operating scope, measured results, system integration, cybersecurity review and accountable owners. A successful demonstration is evidence for the tested conditions, not proof of a production deployment or guaranteed utility procurement.
Stage 1: define what the pilot will prove
- Choose a measurable objective and state the starting condition.
- Identify the utility operations owner, technical owner and decision maker.
- Describe real versus synthetic data, device count and operating environment.
- Agree the measurement method, limitations and acceptance criteria before testing.
- Record customer consent and permissions for any public results.
Early-access, sandbox and pilot are useful status labels when they describe the actual work. Do not imply contracted capacity, live control or certification that the pilot has not established.
Stage 2: assemble deployment-specific evidence
| Area | Evidence to request | Scope limit |
|---|---|---|
| Cybersecurity | System boundary, control assessment, test findings and remediation | A certificate or framework mapping alone does not cover every deployment |
| Interoperability | Version/profile conformance and tested device/system interfaces | A roadmap connector is not a production integration |
| Measurement | Data lineage, quality checks, baseline where applicable and observed results | Pilot delivery is not automatically a future service guarantee |
| Operations | Runbooks, monitoring, incident and rollback procedures | A demo interface does not establish staffed operations |
| Commercial continuity | Support scope, pricing, exit and data portability | A pilot agreement may not include production obligations |
DOE/NARUC’s baselines and the NIST smart-grid profile provide review resources. The utility must decide the evidence required for its system and risk. SOC 2 reporting is not a universal utility or VPP approval.
Stage 3: validate interfaces and qualification
Document what the product connects to, what it controls and which systems remain authoritative. Resolve authentication, data ownership, timestamps, update behavior and degraded communications.
Where a deployment requires OpenADR, CSIP or an ERCOT qualification process, state the exact tested scope and the approving counterparty. A protocol demonstration and market-service qualification are distinct milestones.
Stage 4: agree a production decision and transition plan
- Compare results with the original acceptance criteria, including failures and exclusions.
- List remaining approvals, integration work and customer obligations.
- Assign production support, security, monitoring and incident responsibilities.
- Agree operating limits, pricing, service levels and change control.
- Plan staged activation, rollback and a review of actual production results.
Whether software replaces or integrates with an ADMS/DERMS depends on the utility architecture. This review establishes no rule that an orchestration layer automatically qualifies for an operating budget or closes faster.
Publish proof without overstating it
- Date results and explain the tested devices, location, period and method.
- Label synthetic, simulated, sandbox and live operation separately.
- Describe certification as completed, in progress or outside scope accurately.
- Publish partner names, logos and customer metrics only with permission.
- Keep unsuccessful tests and unresolved constraints visible to the buyer.
This is an editorial delivery framework, not a measured claim about how often pilots succeed. Schedule the work from the actual review dependencies rather than a universal six-to-twelve-month promise.
Sources and further reading
Frequently asked questions
How long does a utility DER software pilot take?
There is no universal timeline established by this review. Scope, integrations, security work, approvals and the event season determine the schedule.
Does every VPP software vendor need SOC 2 Type II?
No universal requirement is established here. The utility should specify security evidence for the system and access involved. A report does not replace deployment-specific assessment.
Does an OpenADR or CSIP certificate prove production readiness?
It supports conformance within a defined scope. Production readiness also requires the actual integrations, operating procedures, approvals, support and measurement evidence.
Can an early-stage vendor have a directory profile?
Yes, if the stage, source status and unverified claims are clear. A listing does not certify production scale, capacity or utility acceptance.
Find the operators serving your market
Compare source-linked VPP aggregators and flexible capacity providers by state, technology, and program status.
Keep reading
DERMS vs VPP Platform: Functions, Services and Procurement
Product boundaries overlap. Map the utility’s actual requirements to grid functions, customer operations, software and contracted services.
The OEM Guide to Entering VPPs: Build, Partner, or Certify
Start with a real target program, then define control, measurement, safety, support and contractual responsibility. VPP-ready is not a universal certification.