For OEMs · August 19, 2026 · 9 min read
The OEM Guide to Entering VPPs: Build, Partner, or Certify
For a hardware manufacturer, "VPP-ready" is a procurement checkbox with real engineering behind it: a controllable device, a cloud that can accept dispatch, telemetry a settlement engine will accept, and a commercial structure for who gets paid. This is the decision tree OEMs work through, and what each route costs.
Three routes to market
| Route | What you own | Best when |
|---|---|---|
| Partner with an aggregator | The device and cloud API only | You want program revenue fast with minimal market risk |
| Licence a DERMS / VPP platform | The customer relationship and brand | You have installed base scale and want a branded program |
| Operate your own VPP | Market registration, dispatch and penalty risk | You have tens of thousands of devices concentrated in a few territories |
Most OEMs start with route one, consider route two after proving device density and repeatable program economics in a utility territory, and only pursue route three when market-operations capability and performance risk are justified by the installed base.
What "VPP-ready" technically means
- A documented cloud-to-cloud API for setpoint or event dispatch, with authentication and rate limits an aggregator can design against.
- Telemetry at the cadence each program accepts, ranging from interval reporting to near-real-time telemetry for faster grid services.
- Per-device state reporting: state of charge, availability, opt-out status, fault state.
- Standards support where programs require it: OpenADR for event signalling, IEEE 2030.5 for utility-side control, CTA-2045 for water heaters, Matter for thermostat-class devices.
- Safety and interconnection compliance for grid-interactive storage, including UL 1741 SB / IEEE 1547 grid-support functions.
- Firmware update discipline — a fleet-wide regression during an event season is a program-ending failure.
The single most common blocker is not the control path. It is measurement: if the device cannot produce data a utility's settlement process will accept, the megawatts do not exist commercially.
Commercial structures OEMs actually sign
- Revenue share — the aggregator collects program revenue and splits it under negotiated terms that vary with incentives, performance risk, and customer ownership.
- Per-device-per-year platform fee — the OEM pays for enablement and keeps the program relationship.
- Enrollment bounty — a fixed payment per enrolled device, simplest to model but caps upside.
- Hardware-only supply — the OEM sells devices to a program operator and takes no ongoing grid-services revenue.
Decide early whether grid services are a margin line or a sales feature. Many OEMs treat VPP eligibility primarily as an attach-rate and differentiation play, then monetize later once enrollment density exists.
The build-versus-partner test
- Is your installed base concentrated? Program economics need density in one utility territory, not devices scattered across 40 states.
- Can you carry performance risk? Operating a VPP means penalties when the fleet under-delivers.
- Do you have market operations capability? Registration, bidding and settlement are ongoing staffed functions, not a project.
- Is your channel installer-led? Installers often control the customer relationship and expect a cut of enrollment.
- What is your firmware release risk tolerance during summer event season?
If three or more answers point the wrong way, partner first and revisit in two seasons with real event data.
A realistic 12-month entry plan
- Months 1–2: pick two target utility territories where your installed base is densest and a program is open.
- Months 2–4: publish a stable cloud API and telemetry spec; run an integration with one aggregator in a sandbox.
- Months 4–6: enroll a pilot cohort of a few hundred devices and complete a test dispatch.
- Months 6–9: run a full event season, measure delivered versus committed capacity, and fix opt-out and availability leakage.
- Months 9–12: negotiate the commercial structure using measured performance rather than nameplate, and decide whether to expand or to build your own program.
Sources and further reading
Frequently asked questions
What does it take for a device to be VPP-ready?
A remotely controllable device, a documented cloud API for dispatch, telemetry at the cadence the program requires, per-device availability and state reporting, and the relevant safety and interoperability compliance such as UL 1741 SB for storage or CTA-2045 for water heaters.
Should an OEM build its own VPP or partner with an aggregator?
Partner first in nearly all cases. Building a VPP means carrying market registration, dispatch obligations and financial penalties, which only pays off with high device density in a small number of utility territories.
How do OEMs make money from VPP participation?
Through revenue share with an aggregator, per-device enablement fees, enrollment bounties, or indirectly through higher attach rates and product differentiation rather than direct grid-services revenue.
Build an OEM partner brief
See potential partners based on technology, territory, market, and published interoperability signals.
Keep reading
Virtual Power Plant Companies: Who Runs VPPs in North America
Aggregators, OEM fleets, DERMS platforms and utility programs all call themselves VPPs. Here's the actual market structure and who sits in each layer.
What Is a Virtual Power Plant? A 2026 Guide
VPPs stitch thousands of batteries, EVs and thermostats into one dispatchable resource. Here's how they actually work, who operates them, and where the money comes from.