See what’s available.
Look beyond connected capacity. Understand estimated flexibility for a particular window, informed by household needs, available energy and participation.
A clearer portfolio pictureFor retailers and VPP operators
VPPiQ Fleet · Planned capability
Bring participating homes into one coordinated energy portfolio. Our vision for VPPiQ Fleet combines household intelligence with fleet-level planning—so your team can set the objective while each home’s priorities shape the response.
Open for pilot discussions. VPPiQ Home provides the household foundation today; Fleet orchestration is planned.
The ambition for your team
Look beyond connected capacity. Understand estimated flexibility for a particular window, informed by household needs, available energy and participation.
A clearer portfolio pictureSet an objective for a portfolio, group or site. Explore how it could become suitable requests across participating homes, within their agreed limits.
One objective. Individual responses.Compare the intended contribution with device response and measured energy. Make shortfalls visible, so the next plan can draw on what actually happened.
Clarity beyond the requestHome + Fleet · The proposed connection
Every home has a day to plan for. That understanding would help Fleet estimate what a portfolio could contribute—and coordinate around the people behind it.
Home · VPPiQ Home today
Household visibility, forecasts and supported automation, shaped by preferences and equipment limits.
Explore a sample home. No signup needed.
Fleet · Planned capability
A view of participating homes and appropriate coordination requests. These Fleet capabilities are not yet built.
Explore the intelligence beneath itExplore the concept
See a battery fleet supply the grid, then absorb energy. Try a different request to see how household limits shape the response.
VPPiQ Fleet · Planned capability
Watch energy move both ways. Every home keeps its priorities.
Battery bank → Electricity grid18:00–20:00 · 2-hour example window
Illustrative net energy at site meters, after household use and generation. Estimated allocation is a plan, not confirmed delivery.
5 MW × 2 hours = 10 MWh requested. Each window has different fictional power and energy limits; a longer request does not create more stored energy or charging space.
The request fits the estimated envelope. This window allows up to 6 MW and 12 MWh. Local checks would still be required.
Estimated flexibility, not installed capacity or guaranteed delivery. Availability can change.
Representative households · fictional
Stored energy above the agreed reserve could support net export after household use.
Energy set aside for backup stays at home, limiting the contribution.
A ready-by goal keeps some energy for the car and reduces export flexibility.
Opted-out, unavailable or stale-data sites would receive no activation request.
The request is 10 MWh over 2 hours: 5 MW on average. Estimated flexibility is 6 MW / 12 MWh for that window, subject to local checks.
These homes illustrate constraints; they do not sum to the allocation. Fresh data, participation and control permissions would be checked before a request.
A request could target a portfolio, group or site. This example uses the eastern group. Allocation remains a plan; the result is simulated, with no assumed cause for a shortfall.
Response evidence and updated availability would inform replanning.
Your customers. Your direction.
Two planned delivery paths to explore together, built around your customer relationships.
Explore a hosted operator service for your participating portfolio, with VPPiQ Home as the household experience.
Discuss a hosted pilotExplore Fleet coordination together with a white-label household app for your end users. Your brand connects the operator workspace to each home’s visibility, preferences and participation.
Discuss a branded pilotBoth proposed paths include Fleet and a household app: VPPiQ Home or a white-label version for your customers. Fleet needs that household connection to understand priorities and participation. Branding and integration arrangements would be defined during pilot discovery.
Go a little deeper
Explore the design intentions and decisions we would work through together.
AEMO’s introduction to VPPsEducational context, not an endorsement.
A useful estimate would combine battery state, forecasts, household plans and connection limits for the requested window. Installed capacity is only a starting point. Estimates would need to change as conditions change, with power in MW and energy over time in MWh kept distinct.
The proposed approach is coordination within agreed participation, reserves and equipment limits. A household’s EV deadline or backup preference could constrain its contribution. Consent, withdrawal, overrides and event approval arrangements would be defined with the pilot partner.
An operator could request a response from a portfolio, selected group or individual site. The intended design would translate that objective into suitable site requests, with local checks before action. Targeted coordination requests do not imply identical commands or a specific broadcast or multicast protocol; those interfaces remain to be designed.
A pilot would identify supported equipment, available interfaces, operating limits and who has authority to control each asset. Existing retailer, VPP or device controls would need to be accounted for. We would agree how conflicting instructions, failed commands and a return to household automation should be handled.
The fleet design would need to distinguish current readings from stale, missing or unavailable information. A pilot would establish freshness thresholds and how uncertain sites are excluded or limited, rather than treating every connected asset as available.
A command being acknowledged is different from a device responding, and both differ from energy measured across a window. The proposed operator view would distinguish these stages and expose shortfalls. Forecast contribution, allocated contribution and measured results would remain separate.
Operator roles, organisation boundaries, approval responsibilities and an audit history are enterprise design topics for pilot discovery. We would agree what needs to be recorded, who can access it and how integrations exchange information. Enterprise access controls, service levels and deployment arrangements are not yet implemented.
Let’s explore a useful first pilot
Tell us about your portfolio and one thing you would like to make easier. We’ll explore technical fit, responsibilities and what a useful pilot could measure.
Dependable coordination comes first.
Operator effort, household experience, battery throughput and network value are outcomes to investigate together. Pilot scope and availability would be agreed.