Virtual power plant

Coordinate many local decisions as one dispatchable portfolio.

The Atmosphere VPP model preserves client ownership and site constraints while allowing an asset manager to form multiple VPPs and manage those VPPs as a portfolio under one account.

The model

Aggregation is not a claim about scale. It is a way to organise control.

Sites become useful to a wider programme when their eligibility, operating limits, availability, and owner intent can be understood together. Atmosphere models those boundaries before it models dispatch.

Illustrative sequence

Sites group into regional VPPs and expose coordinated pathways.

The markers and three VPP groups below are synthetic, and the sequence is qualitative. They do not show actual sites, customers, coverage, capacity, or dispatch activity.

3 illustrative VPP groupsEE
Great Britain distribution licence areasSynthetic regional markers connect to three illustrative virtual power plant groups. Select a region to read its name and network operator. The sequence is illustrative and does not show Atmosphere customers or portfolio coverage.

EE · UK Power Networks

East England

Contains data from NESO’s GB DNO licence areas (2024), used under the NESO Open Data Licence. Boundaries are approximate. Signals, markers, connections, and VPP groups illustrate an aggregation model only, not customer coverage, site locations, or portfolio size.

Participation pathway

Establish the guardrails before the event.

01 · Qualify

Define eligibility

Document asset capability, local priorities, participation rules, and the data needed to assess readiness.

02 · Group

Build regional units

Organise eligible flexibility without removing the constraints that protect each participating site.

03 · Coordinate

Control as one portfolio

Translate programme intent into governed actions with status, permissions, and recovery pathways visible.

Operator guardrails

Unified dispatch should never mean invisible control.

Operators need to know what was requested, what can respond, what is constrained, who can intervene, and how the portfolio recovers. Those questions shape the VPP design from the start.

01
Site opt-in, limits, and priority rules
02
Portfolio readiness and exception visibility
03
Dispatch confirmation and recovery state
Follow the dispatch lifecycle

Operating scenarios

Follow the portfolio logic from observation to review.

The scenarios are qualitative and illustrative. They do not represent live assets, performance, capacity, or dispatch.

Illustrative operating logic

Coordinate storage as a controllable portfolio

01

Observe

State of charge, availability, site limits and service signals

02

Decide

Select eligible capacity and an operating plan

03

Orchestrate

Coordinate approved battery schedules or dispatch

04

Verify

Measured portfolio response and operational evidence

Illustrative workflow only. It does not represent live assets, dispatch, performance, or market participation.

VPP questions

Define the boundary before the event.