VPP software
Enterprise-grade VPP software for owners of solar and storage assets
The demo is a simulation. No real device is connected and no control command is sent.
We build the software layer of a virtual power plant: dispatch, site energy management, inverter and battery limits, measured response, settlement and audit.
Built to enterprise requirements
Enterprise-grade describes the standard the software is designed to. Each point below can be seen in the demo.
A fixed control priority, battery safety first.
Battery safety, then the grid export limit, then reserve, then local demand management, then market dispatch. A lower priority never overrides a higher one. A lower-priority request is reduced to fit; it is not dropped.
An independent rule checker.
Dispatch results are checked against 28 written rules in 50,000 randomized fault scenarios by a checker that shares no code with the dispatch engine.
Audit records in which changes can be detected.
Records are linked in a hash chain, for each site and for the fleet, and the chains refer to each other. A change to one chain is detected by the checks in the demo. The demo also states what this mechanism does not detect.
Four settlement bases, by service type.
Baseline measurement, metered energy, capacity availability and billing demand, each applied to the service it fits.
Fault detection and reallocation.
When a site stops responding or falls short, the fault is recorded and the remaining sites take up the shortfall within their own limits. What cannot be covered is recorded as unserved.
Tested on fleets of up to 1,000 simulated sites.
These are synthetic sites in a simulation, not real ones.
Device access is separate from dispatch logic.
A new device type is added through an adapter; the dispatch logic does not change.
What has been demonstrated
All of this is in simulation. The figures are read from the same summary files the demo shows.
- 28 rules checked across 50,000 randomly generated fault scenarios: 211,732,698 checks, 0 violations.
- 56,236 comparisons of values exchanged over SunSpec Modbus with an open-source simulator on the same machine: 0 failed.
- Simulated fleets of 100, 300 and 1,000 sites: 4,743,950 checks, 0 violations.
- 11 dispatch scenarios, each with its audit records and a settlement on one of four bases.
What has not been demonstrated yet
- No real device has been connected. Every site, inverter, battery and meter in the demo is simulated.
- One protocol only. SunSpec Modbus, and only against a software simulator, not against hardware.
- No real project. The software has not operated a real asset and has not taken part in any market or utility program.
- No utility, market or third-party approval or listing of any kind.
- Prices in the demo are assumptions. Settlement there shows how the calculation works; it is not a financial result for any asset.
How we work with an asset owner
Step 1 — Read-only validation.
We read data from your site and send no control command. You receive a written report: what was read, how it compares with what the software expects, and what does not match.
Step 2 — Attended control test.
A small number of limited commands on one site, agreed in writing beforehand, with your staff present and able to stop the test at any time.
Step 3 — Pilot.
A defined set of sites, a defined period, and measures of success agreed before it starts.
None of these steps has yet been carried out with an asset owner.
The demo is a simulation. No real device is connected and no control command is sent.
Questions: hello@gridvisionai.com
GridVision also provides data-center site advancement. That is a separate line of work, described on the rest of this site.
