California VPP Case Study: Sunrun and Tesla's September 2026 Dispatch

The reported deployment result

The release also reports a separate September 10 dispatch above 140 MW. Its combined figure above 720 MW describes what might have been possible if the events coincided. It is not a reported single-event result. Some Sunrun-operated batteries are Tesla Powerwalls, so company and equipment fleets overlap.

How the program structure fits the deployment

The California Energy Commission describes DSGS as a reliability program with incentives for reducing customer net load, including capacity commitments and performance-based payments. CPUC describes ELRP as a utility-managed demand-response program with distinct participation groups. A shared battery technology does not make those programs commercially interchangeable.

For a deployment plan, identify the party that enrolls the resource, the party that can dispatch it and the party responsible for measuring performance. Then check the applicable utility territory and agreement. This is the link between a fleet's control software and a service the grid can actually call on.

The event is evidence of an existing fleet in operation, rather than a newly announced construction project. PG&E separately documented a statewide Sunrun/Tesla battery test in July 2025 involving its territory, SCE and SDG&E. That earlier utility account supplies operating context; it is not corroboration of the September 2026 numbers.

What the sources verify, and what remains unverified

The verified item here is the existence and content of the cited public records. A procurement-grade performance review would additionally need the measurement boundary, time series, resource roster, validation method and settlement outcome. A regulator hosting a program description is not the same as a regulator auditing this dispatch.

Read peak power, energy and capacity on their own terms

• Peak MW describes a moment or measurement interval. It does not establish the average throughout an event.
• Delivered MWh requires the output over time. Multiplying a reported peak by the full dispatch window assumes constant delivery, so it cannot establish observed energy.
• Firm capacity needs a defined location, duration, availability obligation and contractual remedy. One operating event does not supply all of those terms.
• Device counts need an asset boundary. Track unique resources across the operator, equipment manufacturer and program so the same battery is counted once.

These are measurement and diligence principles, not a recalculation of the event. This article does not infer customer earnings, realized utility savings, avoided outages or a currently available capacity offer from the headline output.

A deployment checklist for a utility or OEM buyer

1. Define the service: where, when, for how long and under which dispatch trigger you need delivery.
2. Request the event curve and meter boundary. Separate battery output, site export and any adjustment against a baseline.
3. Ask for asset-level eligibility, dispatch rights and overlap controls, with a roster appropriate to the procurement review.
4. Review repeated events and lower-performing conditions, including communications loss, backup reserves and customer opt-outs.
5. Assign responsibility for enrollment, controls, reporting, settlement disputes and underperformance before comparing commercial bids.

Use the accompanying comparison workbook to keep evidence and unanswered questions beside each written offer. The practical lesson is to carry operational evidence into the contract discussion, then test the service at the location and conditions that matter to your project.

Frequently asked questions