Short answer
Aggregation means jointly controlling many controllable generators, storage units, buildings and chargers. It requires metering, telemetry, forecasting, baselines, dispatch logic and user consent. HUBCORE is developing in this direction; we claim no completed virtual power plant and no electricity retail activity.
What aggregation consists of
Aggregation is not one function but a chain. Every link must be trustworthy, otherwise the whole is not.
| Link | Why it matters |
|---|---|
| Metering | Without trustworthy metering nothing can be evidenced or settled |
| Telemetry | State and command feedback must arrive within acceptable latency |
| Forecasting | Load and generation forecasts determine what can be promised |
| Baseline | Without a baseline you cannot measure how much flexibility was delivered |
| Dispatch | Distributing commands across resources within safe limits |
| Consent | The user must know and permit what is done with their device |
Data and metering accuracy
As 15-minute settlement becomes more widely used, accurate timing matters even more. We need timestamped data, a known metering point and clarity on which meter is the settlement meter and which is auxiliary.
Partners, settlement and security
Market participation requires roles and contracts HUBCORE does not carry alone. We work with partners while keeping the brand, standard, data logic and customer relationship. On security the same requirement applies as to devices: authenticated access, scoped permissions, logs and auditability.
HUBCORE is not an electricity retailer or grid operator, does not currently retail electricity and does not operate a completed virtual power plant. What is described is a development direction that may require licensed partners and market participant roles.
Fallback and safe limits
Aggregated control must always fall back to a safe state. If comms fail, a forecast is wrong or a partner does not respond, the site must continue independently within its own limits — charging continues at a sensible level, the battery does not discharge impermissibly, and the user sees the true state.
- Every resource knows its local safe limit
- Comms-loss behaviour is defined and tested
- The user can pause participation at any time
- All commands and outcomes are logged and auditable
HUBCORE fit filter
- Controllability — Can the device be safely limited, started and stopped through a documented interface?
- Measurability — Do we get trustworthy measurements (power, energy, phases, state, faults) at sufficient resolution?
- Integrability — Is the interface publicly documented (e.g. Modbus, SunSpec, REST, MQTT, OCPP) and versioned?
- Local operation — Do critical control and safety keep working when the vendor cloud or internet is down?
- Security — Is access authenticated, are rights scoped, is traffic encrypted and firmware updatable?
- Serviceability — Is it clear who owns maintenance, spare parts, firmware and fault resolution?
- Scalability — Can the solution grow (more points, kWh, sites) without redesigning the architecture?
HUBCORE's position
Aggregation is HUBCORE's long-term direction, but it starts from thousands of properly measured and controlled sites. Without trustworthy metering, a safe fallback and clear consent, aggregation is not responsible.
Not yet verified
- Which baseline methods are fair for Estonian apartment-building profiles?
- How to share revenue fairly between members of an apartment association?