Distributed Energy Resource Aggregation

Aggregation platforms must normalize a diverse mix of asset types—rooftop solar, battery energy storage systems (BESS), smart thermostats, and EV chargers—spread across different nodes of the distribution grid.

• Protocol translation: Converts proprietary OEM APIs (e.g., Enphase, Tesla, SolarEdge) into a unified control schema.
• Locational awareness: Maps each asset to its specific Locational Marginal Price (LMP) node to value its contribution accurately.
• Latency compensation: Accounts for varying network latencies from residential Wi-Fi to cellular backhaul to ensure synchronous dispatch.

A DER aggregator must maintain a live, second-by-second model of the aggregate's available capacity. This requires continuous polling of behind-the-meter (BTM) assets that are not directly visible to the utility SCADA system.

• State of charge (SoC) for batteries and curtailment status for solar inverters are ingested at sub-second intervals.
• Kalman filtering and other state estimation techniques reconcile noisy, intermittent telemetry streams into a coherent aggregate view.
• The system must distinguish between a device that is offline versus one that is simply idle to avoid over-committing capacity.

A single dispatch signal from the grid operator—e.g., 'reduce load by 50 MW for 2 hours'—must be algorithmically decomposed into thousands of individual device-level commands.

• Optimization solvers allocate the dispatch across assets to minimize customer impact while respecting individual device constraints (e.g., minimum battery SoC, maximum HVAC temperature drift).
• Load shaping creates a synthetic aggregate response curve that matches the grid operator's requested ramp rate and duration.
• The system continuously re-optimizes the allocation mid-event if individual assets fail to respond as predicted.

Financial settlement in wholesale markets depends on proving how much load was actually reduced compared to a counterfactual baseline. The aggregator's Measurement and Verification (M&V) engine is its profit center.

• Calculates Customer Baseline Load (CBL) using methodologies like '10-in-10' or weather-adjusted regression models.
• Must pass rigorous performance audits by independent market monitors to avoid financial penalties.
• Settlement engines reconcile meter data with dispatch records to allocate revenue shares to individual asset owners.

An aggregator controlling millions of distributed assets represents a critical attack surface. Compromised dispatch signals could destabilize the grid rather than support it.

• IEEE 2030.5 and OpenADR protocols enforce certificate-based mutual authentication between the aggregator and every endpoint.
• Role-based access control (RBAC) ensures that customer overrides (e.g., opting out of an event) are respected and cannot be bypassed by automated dispatch logic.
• Continuous SCADA anomaly detection monitors for command injection patterns that deviate from normal operational cadence.

A sophisticated aggregator maximizes revenue by bidding the same portfolio into multiple value streams simultaneously, a practice known as value stacking.

• A residential battery can provide frequency regulation (fast response) while also contracted for peak shaving (slower, sustained response).
• The optimization engine must respect the physical limits of the asset to avoid double-counting capacity.
• Participation spans wholesale ancillary service markets, distribution-level non-wires alternatives, and retail time-of-use arbitrage.

A cloud-based network that aggregates decentralized energy resources—such as residential batteries, smart thermostats, and EV chargers—to provide grid services equivalent to a centralized power plant. The VPP operator uses a central control system to monitor, forecast, and dispatch the aggregated capacity in real-time.

• Replaces the need for fossil-fuel peaker plants
• Participates in wholesale energy, capacity, and ancillary service markets
• Requires sub-second latency for frequency regulation services

A software platform that enables real-time monitoring, control, and optimization of aggregated distributed assets. Unlike a simple aggregator, a DERMS manages grid constraints by modeling the local distribution topology to prevent backfeed and voltage violations.

• Integrates with ADMS and SCADA systems
• Enforces locational dispatch based on feeder capacity
• Supports IEEE 2030.5, OpenADR, and DNP3 protocols

Any energy generation, storage, or flexible load located on the customer's side of the utility meter. These assets are typically invisible to the grid operator unless aggregated by a third-party entity.

• Includes rooftop solar, home batteries, and smart appliances
• Net metering policies significantly impact aggregation economics
• Requires customer consent and secure telemetry gateways

The competitive marketplace where grid operators procure specialized services necessary to maintain system reliability. Aggregated DERs are increasingly qualifying to bid into these high-value markets.

• Frequency Regulation: Continuous adjustment to maintain 60 Hz
• Spinning Reserve: Capacity synchronized and ready within 10 minutes
• Voltage Support: Reactive power injection to maintain local voltage profiles

A standard communication protocol for smart grid applications, commonly used to manage DERs and enable secure demand response interactions via internet protocols. It defines a common interface for utilities to communicate with aggregators and end-devices.

• Supports function sets for pricing, metering, and flow reservation
• Uses RESTful architecture over TLS for cybersecurity
• Mandated by California Rule 21 for smart inverter communications

The rigorous analytical process of quantifying the actual load reduction delivered by a DER aggregation against its baseline. This determines financial settlement in capacity and demand response markets.

• Customer Baseline Load (CBL) is the statistical counterfactual
• Accuracy is critical to avoid performance penalties
• Advanced M&V uses meter-level sub-second data for precision