Virtual power plant platforms

Connecting sites to a virtual power plant

Separate the site system from the portfolio service

A virtual power plant can bring together battery storage, generation and controllable loads. The portfolio service needs to know what each asset can do, whether it is available and whether an instruction was carried out.

Edge runs locally on the Gateway. Operators use its dashboards, data tools and automation on site without an external platform. The partner integration connects the site to portfolio optimisation, commercial dispatch and any market-facing processes.

Define an asset model before adding sites

Agree a common identity for each site, asset and measurement. Keep the same units and sign conventions across the portfolio, but retain the context that makes readings meaningful.

For a battery, add state of charge, operating mode and limits to the electrical power readings. For a controllable load, the relevant state and permissible actions will be different. Confirm supported readings and commands for the exact equipment and firmware.

The battery storage guide explains the distinction between independent metering and battery-system telemetry.

Select the field hardware

Use the electricity monitoring range for electricity measurements and review demand response for monitoring and control of site loads. The current datasheets define their functions and available configurations.

Supported wired equipment and wireless monitoring can share the Edge data model. Choose the Gateway communications options and interfaces for the site. Match the controller to each asset, and keep existing meters whose data Edge can read.

Agree the command path

Document how a platform instruction identifies its target, who may send it and how its outcome is reported. Include operating limits, overrides, stale instructions, retries and communication failures in the integration design.

Distinguish an accepted command from a completed physical action. Compare the instruction, equipment state and resulting measurements during qualification. Measure timing across the whole path, from instruction to measured response.

Qualify a representative site before scaling

The demand response and VPP page and its customer projects show EpiSensor's role; qualify each new asset and programme on its own.

For a pilot, record hardware and software versions, test the agreed data and control behaviour, and establish who owns ongoing support. Add the applicable provider or programme acceptance tests before expanding the portfolio.

Explore platform profiles and how Edge sends data out.