By AGILE Consulting Engineers, Solar PV and Battery Energy Storage Systems (BESS) specialists.
Most home and commercial batteries sold in Australia today are technically capable of joining a Virtual Power Plant (VPP). Far fewer are actually enrolled, and the gap between “capable” and “enrolled” is almost entirely engineering paperwork and interoperability, not hardware. Getting a battery from installed asset to dispatchable, market participating resource involves a specific sequence of technical requirements that catches out a lot of otherwise well designed projects.
Table of Contents
- Power Conversion System Specification
- Telemetry and Communications Requirements
- Inverter and BMS Interoperability
- Metering and Revenue Grade Measurement
- Cyber Security Basics
- Compliance With AEMO’s Technical Requirements
- Commissioning Steps: FAT and SAT at Asset Level
- What to Do Next
- FAQ
Power Conversion System Specification
Every battery in a Virtual Power Plant has a power conversion system (PCS), the inverter or hybrid inverter hardware that converts between the battery’s direct current and the grid’s alternating current, sitting at the boundary between the asset and the network. For VPP participation, the PCS specification needs to cover more than rated power and efficiency. Ramp rate, meaning how quickly the unit can move from one output level to another, matters directly for Frequency Control Ancillary Services (FCAS) products with short response windows. Voltage and frequency ride through settings need to be configured to the requirements of the relevant distribution network service provider (DNSP) and to AS/NZS 4777.2, the Australian and New Zealand standard covering inverter requirements for grid connected energy systems, rather than left at factory default.
State of charge management is another PCS level consideration that is easy to under specify. A battery committed to a VPP program needs headroom reserved for both customer use and market dispatch, and the PCS and its control firmware need to expose enough configurability that the aggregator’s software can manage that headroom without the customer’s own usage patterns silently defeating the commitment. This is a design decision that has to be made before enrolment, not patched in afterwards.
Telemetry and Communications Requirements
A VPP is only as reliable as the data pipe carrying instructions down to the asset and status back up to the aggregator’s energy management system (EMS) or DER (distributed energy resource) management system (DERMS). For an individual battery to be enrolled, its communications link, typically over the customer’s home or business internet connection, needs to meet minimum requirements around latency, uptime and data resolution that the aggregator has agreed with AEMO or the relevant program.
In practice this means the telemetry stack has to report state of charge, active and reactive power, and fault or alarm status at a cadence tight enough to support dispatch verification, while also being resilient to the kind of intermittent home network outages that are entirely normal in a residential or small commercial setting. Aggregators typically build in local fallback logic, so the battery can continue operating safely and predictably if the communications link drops, rather than defaulting to an unsafe or non compliant state. This local intelligence requirement is a genuine engineering specification, not an afterthought, and needs to be tested rather than assumed.
Inverter and BMS Interoperability
The battery management system (BMS), which protects the cells and manages charge and discharge limits, and the inverter or hybrid inverter’s own control system need to communicate cleanly with each other and with the aggregator’s platform. Where the battery and inverter come from the same manufacturer as an integrated system, this is usually straightforward. Where they are paired from different manufacturers, which is common in the Australian residential and small commercial market, interoperability has to be verified rather than assumed, because a mismatch in communication protocol, firmware version or safety interlock behaviour between BMS and inverter can quietly limit what the VPP is actually able to instruct the asset to do.
This is one of the more common practical blockers in VPP enrolment. A battery that performs perfectly as a standalone backup or self consumption system can still fail interoperability testing for aggregation purposes if its BMS does not expose the right control points, or if firmware updates from the manufacturer periodically change register mappings the aggregator’s software depends on. AEMO’s own VPP Demonstrations program documented real world cases where firmware updates altered device settings without the aggregator’s knowledge, contributing to under delivery against dispatch instructions during the trial. Ongoing firmware governance, not just initial compatibility, needs to be part of the interoperability conversation.
Metering and Revenue Grade Measurement
To be paid for wholesale energy or FCAS participation, and for AEMO to verify that participation actually occurred, a VPP asset needs measurement that meets revenue grade accuracy requirements, not just the indicative reporting built into most consumer facing battery apps. Depending on the program and the market products involved, this may be satisfied through the customer’s existing smart meter, through dedicated metering at the battery, or through a combination verified against AEMO’s metering rules.
Getting this wrong does not just create a compliance problem, it directly affects revenue reconciliation. If the metering used to prove FCAS delivery or wholesale dispatch does not match what AEMO’s settlement systems recognise as revenue grade, disputes over performance and payment become far more likely. This is a detail worth resolving explicitly at the design stage of any VPP fleet rather than assuming the installed meter is automatically fit for purpose.
Cyber Security Basics
Aggregating thousands of individually owned, internet connected devices into a resource that can influence grid frequency creates a cyber security surface that a single large power station simply does not have. The Australian Energy Sector Cyber Security Framework (AESCSF), developed by AEMO with the Australian Cyber Security Centre and other stakeholders, provides specific guidance material for distributed and consumer energy resources (DER/CER) alongside its broader industry framework, reflecting how differently this risk profile behaves compared with traditional generation.
At the individual asset level, the practical basics include secure device authentication, encrypted communications between the asset and the aggregator’s platform, a defined process for firmware update verification so that updates cannot be used to push unauthorised changes to device behaviour, and clear segmentation between the customer’s home network and the control pathway used for market dispatch. None of this needs to be exotic, but it does need to be deliberate. A VPP aggregator’s platform is only as secure as the weakest commonly deployed device on the fleet, which is a very different risk model to securing one control room.
Compliance With AEMO’s Technical Requirements
Before an individual battery can be enrolled in a registered VPP, it generally needs to be recorded on AEMO’s DER Register, the data set AEMO maintains to give it visibility over small scale distributed resources sitting behind customer meters, separate from the generator registration categories used for traditional plant. AEMO has also run specific consultations amending the Market Ancillary Service Specification (MASS) to address measurement requirements for DER participating in contingency FCAS markets, and has published technical requirements addressing the connection of DER in the 200 kW to 5 MW range, a segment that previously sat in a gap between the low voltage AS/NZS 4777 series and the National Electricity Rules’ schedule for larger connections.
None of this compliance work is optional or able to be retrofitted cheaply after the fact. An aggregator building a fleet, or a battery manufacturer wanting its product to be VPP ready, needs to design against these requirements from the outset, because the DER Register data, the metering evidence and the measurement requirements all feed directly into whether AEMO will recognise the asset’s contribution to a registered VPP’s aggregate capacity.
Commissioning Steps: FAT and SAT at Asset Level
Even at the individual battery level, before fleet level testing begins, there is a genuine commissioning sequence. Factory acceptance testing (FAT), typically carried out by the manufacturer, confirms the PCS and BMS meet their design specification and relevant standards before the unit ships. Site acceptance testing (SAT) then confirms the installed system performs correctly in situ: protection settings are correctly configured, ride through behaviour matches the DNSP’s requirements, communications to the aggregator platform are established and verified, and the asset responds correctly to a test dispatch instruction under supervision before it is enrolled live.
This asset level SAT is where a surprising number of VPP enrolments stall in practice, usually because the installer configured the inverter to factory defaults rather than the specific settings the aggregator’s program requires, or because the communications link was verified for internet connectivity but never actually tested against a live dispatch signal. Building this test step into the standard installation process, rather than treating it as a separate exercise months later, avoids a lot of rework.
What to Do Next
The requirements above sound procedural individually, but they compound. A PCS specification gap discovered during SAT, a metering mismatch discovered at first settlement, or a cyber security gap discovered during an AEMO compliance review all cost considerably more to fix after the fact than during design. This is the point where a technical review of the battery, PCS and communications specification against AEMO’s actual requirements can save months of rework later. We have helped teams work through exactly this before committing to a hardware fleet or a specific battery model.
FAQ
Can any grid connected battery join a VPP?
Most modern batteries are technically capable, but enrolment depends on the PCS and BMS exposing the right control and telemetry points, meeting AS/NZS 4777.2 requirements, and passing the aggregator’s own interoperability and commissioning testing.
Does a home battery need special metering to join a VPP?
It needs measurement that meets revenue grade accuracy requirements for the specific market products it is enrolled in, which may be satisfied by an existing smart meter or may require additional dedicated metering depending on the program.
What is the DER Register and why does it matter for VPP batteries?
It is AEMO’s data set recording distributed energy resources sitting behind customer meters, separate from generator registration, and individual VPP connected batteries are generally recorded on it as part of the compliance pathway.
Why do firmware updates cause problems for VPP enrolled batteries?
Manufacturer firmware updates can change device settings or communication register mappings without the aggregator’s knowledge, which AEMO’s VPP Demonstrations program documented as a real cause of under delivery against dispatch instructions during its trial.
What cyber security basics apply to VPP connected batteries?
Secure device authentication, encrypted communications to the aggregator platform, verified firmware update processes and network segmentation are standard basics, guided in Australia by the Australian Energy Sector Cyber Security Framework’s DER specific guidance.
What does site acceptance testing (SAT) check for a VPP battery?
SAT confirms the installed inverter and BMS settings match the DNSP and aggregator’s requirements, that communications are properly established, and that the asset responds correctly to a supervised test dispatch instruction before it goes live.
