The term "virtual power plant" gets used loosely in the energy industry — sometimes to describe any aggregation of DERs, sometimes specifically to mean an aggregation that participates in wholesale markets, and sometimes as a marketing label for demand response programs that don't interact with ISO markets at all. For community solar operators pursuing ISO capacity market participation, the distinction matters: a VPP in the wholesale market sense requires achieving ISO recognition as a capacity resource, which is a specific regulatory and technical status, not a product feature.
This post describes the pathway from having a portfolio of subscriber solar and storage accounts to holding an ISO-registered capacity resource designation — the technical and regulatory steps, in sequence, and where the common friction points arise.
Stage 1: Establishing the Aggregation Entity
ISO capacity market participation requires the aggregator to register as a market participant — a legal and contractual relationship with the ISO that establishes billing, compliance, and settlement terms. For a community solar operator new to wholesale markets, this is often the step that takes longest because it requires the operator to understand which entity within their corporate structure will hold the market participant agreement, establish credit requirements with the ISO (typically a financial security deposit or letter of credit), and execute the relevant ISO tariff agreements.
In PJM, the entity that registers as a market participant is typically the DER Aggregation Entity (DERAE). In ISO-NE, the analogous role is the DER Aggregator. In NYISO, the Aggregator registers under the DRI (Distributed Resource Integration) program framework. The registration process varies by ISO but all involve application documentation, tariff agreement execution, and financial security posting.
New community solar operators often underestimate the time this step takes. The ISO market participant registration process, from initial application to approved status, can take 4-8 weeks under normal processing times. Some ISOs also require a credit review that depends on the financial history of the entity, which may be thin for programs launched within the last 2-3 years. Starting this step well in advance of the enrollment deadline is critical.
Stage 2: Asset Inventory Filing and EDC Notification
Once the aggregation entity is registered, the next step is filing the asset inventory — a structured list of every DER in the aggregation, with the technical and location attributes the ISO requires. Each ISO specifies the required data elements and format, but all include: asset location (ISO zone and delivery point), technology type, nameplate capacity, storage duration if applicable, and meter point identification.
The asset inventory filing triggers the Electric Distribution Company notification process. Each EDC whose service territory includes assets in the aggregation must be notified, and the EDC has a right to flag distribution constraints that would affect dispatch. In practice, most EDCs acknowledge receipt without raising specific objections, but the timeline needs to account for EDC response windows — typically 30-60 days depending on the ISO's tariff provisions.
This is also where the quality of the aggregator's internal asset registry directly affects enrollment speed. An aggregator that can generate an ISO-formatted asset inventory export from a maintained registry completes this step in days. An aggregator who needs to manually compile asset data from multiple systems, reconcile meter IDs against EDC billing records, and verify that storage ratings match installed specs may spend weeks on data collection before filing.
Stage 3: Telemetry Testing and Approval
ISO capacity resources must be able to report their real-time output to the ISO's telemetry systems. For aggregated DER, this means the aggregator's platform must connect to the ISO's SCADA or equivalent telemetry interface and deliver aggregated MW readings at the required resolution and accuracy during dispatch windows.
Telemetry testing involves the ISO verifying that the aggregator's reporting system can deliver data at the required protocol, at the required polling interval, and within the ISO's accuracy tolerance. Testing is conducted before the dispatch capability demonstration event and must be passed before the resource can be eligible for capacity market participation.
The telemetry testing step is where community solar programs most commonly encounter delays. The reason is specific: the aggregator's telemetry reporting depends on having reliable, low-latency data from the aggregated assets — but BTM solar and storage assets were typically installed for behind-the-meter optimization purposes, not for ISO telemetry reporting. The data pipeline that's adequate for monthly subscriber billing reports is not necessarily adequate for real-time ISO telemetry polling during a dispatch event.
Stage 4: Dispatch Capability Demonstration
Before a DER aggregation is eligible to participate in a capacity auction, ISOs require a demonstration that the aggregation can actually deliver its committed capacity when dispatched. This dispatch test event involves the ISO issuing a dispatch instruction at a specified capacity level and observing whether the aggregation responds within the required timeframe and meets the capacity level for the required duration.
For a BTM community solar and storage aggregation, the dispatch test demonstrates: (a) the aggregator's ability to receive and route the dispatch instruction to the constituent assets; (b) the assets' ability to respond — storage assets discharging, load flexibility assets curtailing — at the committed level; and (c) the telemetry system's ability to report the response accurately in near-real-time.
Scheduling the dispatch test requires coordination with the ISO, which typically maintains a test event calendar. An aggregation that fails its first dispatch test must remediate and reschedule, which can push the timeline by a full seasonal cycle if test windows are limited. Testing preparation — verifying that all storage systems are charged, that telemetry paths are confirmed live, and that the dispatch instruction routing has been end-to-end tested in simulation — is worth investing in seriously before the first real test date.
Stage 5: Capacity Auction Enrollment
With market participant registration, asset inventory filing, EDC notification, and dispatch test all complete, the aggregation is eligible to submit a capacity offer in the next available ISO auction cycle. The capacity offer specifies the MW quantity being offered, the delivery year, and the minimum clearing price (offer price) at which the aggregator will accept a capacity commitment.
For DER aggregators new to capacity auctions, the offer price decision deserves careful thought. Offering at or below the clearing price in the relevant LDA ensures the resource clears in the auction — but clearing at a low price when the clearing price is later higher than your offer reduces realized revenue. The offer price strategy depends on the aggregator's assessment of the likely clearing price, their financial need for predictable capacity revenue, and their risk tolerance for being non-cleared in a given auction cycle.
We're not saying that the offer price decision requires in-house wholesale power trading expertise. PJM publishes historical BRA clearing prices by LDA, and ISO-NE and NYISO publish equivalent historical data. An aggregator can establish a reasonable offer strategy from public data without specialized market advisory services — though for large programs, some form of market intelligence is worth the cost.
The Full Timeline in Realistic Terms
Community solar operators with an existing BTM portfolio who start this process from scratch should plan for 9-14 months from initiating market participant registration to completing the first dispatch test event. The range reflects differences in EDC responsiveness, ISO telemetry testing queue times, and the operator's starting point on asset registry quality and telemetry infrastructure. Programs that start the enrollment process with a clean asset registry and an existing telemetry connection to a DER management system with ISO-compatible output will be at the low end of that range. Programs starting from a collection of installer spreadsheets and utility AMI exports will be at the high end.
The auction timing is fixed by the ISO's calendar. The enrollment timeline is the variable the operator controls. Starting early and tracking enrollment milestones against the auction deadline is the only way to avoid arriving at the auction window with an incomplete enrollment — and missing a full delivery year of capacity revenue as a result.