Capacity Resource Qualification: A Documentation Checklist for Operators

ISO capacity resource qualification for a DER aggregation is, fundamentally, a documentation exercise on top of a technical one. The technical work — building the telemetry pipeline, completing the dispatch test, establishing the aggregation entity — gets most of the attention. But the documentation that supports each step of the process is what the ISO actually reviews, and incomplete or incorrectly formatted documentation is the most common cause of enrollment delays that have nothing to do with technical readiness.

This checklist covers the documentation requirements for PJM, with notes on where ISO-NE and NYISO differ materially. It's organized by enrollment stage, not by document type — the sequence matters as much as the completeness.

Pre-Enrollment: Entity and Program Structure Documents

Before filing any ISO-specific documentation, the aggregator needs the foundational entity documents in order. These are not ISO-specific but are required by the ISO market participant registration process:

• Entity formation documents: Certificate of incorporation, LLC operating agreement, or equivalent. The ISO market participant application requires the legal name and entity structure of the registering organization.
• Authorized signatory documentation: Board resolution or equivalent authorizing specific individuals to execute ISO market participant agreements on behalf of the entity. ISOs require executed agreements, not just applications.
• Financial security documentation: Evidence of the letter of credit, cash deposit, or surety bond that satisfies the ISO's credit requirement. PJM, ISO-NE, and NYISO each specify their credit requirements in their tariffs; amounts vary based on the size of the capacity obligation being sought.
• Federal tax identification number: Required for ISO settlement and tax reporting purposes.

Operators who work through a market services provider or capacity broker rather than registering directly as market participants should still understand these requirements, because even indirect market participation typically requires the program operator to hold sub-agreements that reference the market participant's position.

Asset Inventory Documentation

The asset inventory is the core technical filing for DER aggregation registration. PJM's DER aggregation tariff specifies the required data elements for the asset inventory filing; ISO-NE and NYISO have analogous requirements. The inventory must include, for each constituent DER:

• Asset location: ISO zone, locational deliverability area (for PJM), load zone (for ISO-NE and NYISO), and electric distribution company service territory. The location data must be accurate because it determines which LDA clearing price applies to the resource.
• Technology type: Solar photovoltaic, battery energy storage, controllable load, or combination. ISOs classify these differently for ELCC and UCAP calculation purposes.
• Nameplate capacity: AC nameplate rating for solar, rated power and energy capacity for storage, rated load reduction for demand response assets. ISO format requirements vary — confirm the unit and measurement basis required by each ISO.
• Meter point identifier: The ISO and/or EDC meter identification number for the settlement meter associated with each asset. This is the link between the asset inventory and the metering record. Missing or incorrect meter IDs are the most common data quality error in asset inventory filings.
• Interconnection agreement reference: The interconnection agreement or net metering agreement number for each asset. For behind-the-meter assets, this is typically the net energy metering agreement with the distribution utility.
• EDC territory designation: For PJM, the specific electric distribution company serving each asset. This drives the EDC notification requirement.

Metering and Telemetry Compliance Documentation

ISO capacity resource qualification requires verification that the aggregation's metering and telemetry infrastructure meets ISO requirements. The documentation for this includes:

• Meter qualification records: Evidence that revenue meters are installed, certified, and operating within the ISO's accuracy tolerance. For aggregated BTM resources, this typically means the EDC-owned AMI meters plus any supplemental submeters. Meter certificates from the EDC or meter testing records may be required.
• Telemetry interface specification documentation: Description of the aggregator's telemetry reporting system — the software platform, connection protocol (ICCP, web services, or equivalent), data refresh rate, and data accuracy specifications. ISOs review this as part of telemetry testing approval.
• Data coverage calculation: For aggregated DER, ISOs typically require a minimum percentage of the aggregation's capacity to be covered by qualifying telemetry. The coverage calculation should be documented — showing which assets contribute to the real-time telemetry path and demonstrating that the coverage threshold is met.

EDC Notification and Coordination Records

• EDC notification letters: Written notification to each relevant electric distribution company of the DER assets being enrolled in the ISO aggregation. The format may be specified in the ISO's tariff or the EDC's interconnection procedures. Retain proof of delivery.
• EDC response records: Any written response from the EDC acknowledging notification or raising distribution constraints. If the EDC raises constraints, document the resolution — either a modification to the dispatch parameters for affected assets or the EDC's confirmation that the proposed dispatch is acceptable.
• Local distribution agreements (if required): Some EDC territories require a local distribution operating agreement for DER dispatch programs. Check each EDC's interconnection and distribution tariff provisions before assuming no agreement is needed.

Dispatch Test Documentation

The dispatch test event must be documented regardless of outcome. Required records include:

• Pre-test notification to ISO: The formal request to schedule a dispatch test event, submitted through the ISO's enrollment portal. Retain the ISO's confirmation of the test date and time.
• Dispatch test protocol: The ISO typically specifies the test parameters — the dispatch level, duration, and response time requirement. Retain the ISO's test specification document for the specific test event.
• Test execution log: A timestamped record of the dispatch instruction receipt, asset response initiation, and telemetry-reported output during the test period. This is generated by the aggregation platform's dispatch management system.
• Post-test ISO determination: The ISO's written determination that the dispatch test was passed (or the specific deficiency identified if failed). For a passed test, this document is the prerequisite for capacity auction enrollment.

We're not saying that every program will pass its first dispatch test. Tests fail for documented, fixable reasons — storage systems not fully charged, a telemetry latency issue that wasn't caught in pre-test simulation, an asset that went offline in the hours before the test window. What matters is that the failure is documented with root cause, the remediation is tracked, and the retest is scheduled with the specific deficiency addressed. An ISO reviewer who sees a clear root-cause and remediation record for a failed first test is in a different position from one who sees an unexplained failure with no documented follow-up.

Ongoing Compliance Records

After capacity auction enrollment, the documentation requirement continues. For each delivery year, operators should maintain:

• Updated asset inventory reflecting any additions or removals from the aggregation
• Annual capacity capability test records (ISOs require periodic re-testing)
• Performance Assessment Interval response records with telemetry evidence
• Settlement reconciliation records showing ISO capacity payments against metered performance
• Any ISO compliance audit correspondence

The ongoing documentation requirement is less intense than the enrollment documentation burden, but it's continuous. Programs that establish a document management system during enrollment — rather than storing ISO correspondence in email threads and test results in a shared drive — are in a substantially better position when an ISO compliance inquiry arrives. Capacity resource compliance audits can request records going back multiple delivery years; having organized, retrievable records shortens the response time from weeks to days.

A final note on document version control: ISO enrollment documentation is typically prepared over weeks or months, with multiple rounds of submission and ISO comment. Maintaining clear version control on the asset inventory, telemetry specification, and enrollment application documents — with submission dates and ISO response dates noted — prevents the confusion of having multiple versions of the same document with no clear indication of which one the ISO has accepted. This sounds like basic record-keeping, and it is — but it's where a surprising number of programs with otherwise solid technical preparation create administrative delays.