Installed capacity and dispatchable capacity

Residential batteries were built first for their owners, to store solar energy, cut bills and run the home. A VPP asks them to do one more job: deliver a set amount of power for a set window. Makers expose different readings and commands for that job. As a result, installed capacity can run well above dispatchable capacity. Installed capacity is the sum of the battery ratings. Dispatchable capacity is the power the portfolio can deliver on request.

What the control layer has to do

The operator asks for one thing, such as a discharge rate over a window, and the control layer handles the differences between batteries.

One dispatch request becomes the command each battery accepts.
What a control layer has to do
JobWhat it covers
Read each batteryState of charge, available charge and discharge power, limits and connection status, in one format.
Take one requestThe operator asks for a discharge rate over a window. The layer turns it into the command each battery supports.
Respect limitsOwner reserve, equipment limits, opt-outs and export limits apply to every dispatch.
Keep a recordEach dispatch keeps a record that is compared with the metered response.

How dispatch is validated covers the comparison. Elastic's platform shifts batteries toward the hours a program sets, by direct command or through mode and tariff settings.

Cloud connection or local controller

A maker's cloud service lets an aggregator enroll batteries with no added site hardware. A local controller adds one device at the site and reaches the equipment directly. Each route has its own limits.

Cloud connection and local controller
QuestionCloud connectionLocal controller
Site hardwareNone addedOne device at the site
Commands availableThe ones the maker's service allowsThe ones the equipment accepts through a local driver
What it depends onThe maker's permissions, service uptime and integration termsThe site's local connection and a driver for the model
Work at the siteNoneAn installation visit

Elastic takes both paths through the Energy Router. The Energy Router controls a battery locally over the protocols the equipment speaks, or through the maker's cloud service where the equipment requires it.

When the site internet drops

A site's internet connection drops now and then. The Energy Router falls back to cellular when the site internet drops and the site still has power.

Where compatibility sets the limit

Compatibility and program eligibility are separate. A battery on the compatibility list can still sit outside a program, because enrollment, metering, telemetry, owner consent and market rules all apply. Owners also choose whether their equipment takes part. How opt-outs and device availability work covers that choice. Start with the model-level list at Check compatibility, then check each program's own requirements.

A 300-battery portfolio

For illustration, an aggregator holds 300 batteries rated at 5 kW each. Installed capacity is 1,500 kW. The aggregator sorts the batteries by how they can be reached.

Installed to dispatchable, for illustration
StepBatteriesPower
Installed3001,500 kW
Reachable through a local driver180900 kW
Reachable through the maker's cloud service80400 kW
Not reachable by either route40200 kW
Controllable by either route2601,300 kW
After 20 owners opt out2401,200 kW

The aggregator can plan on 1,200 kW at most, before state of charge and owner reserve at the time of an event. The model-level compatibility check turns the 1,500 kW on paper into the number a dispatch can use.

Common questions.

Can one request go to batteries with different power ratings?

Yes. Each battery stays within its own rating, owner reserve and state of charge, so the delivered total can be lower than the sum of the ratings.

Ask your assistant.

Explain this page from Elastic Energy in plain language: https://elasticenergy.com/hardware-agnostic-virtual-power-plant

Keep exploring.