Interconnecting a Utility-Scale BESS in ERCOT: The Complete Guide to the TNMP and AEP Texas Process

Battery Energy Storage Systems (BESS) are being deployed across Texas at a record pace, and for good reason. ERCOT's volatile energy prices, growing ancillary service markets, and rapid load growth make the grid one of the most attractive storage markets in the world. But between a signed land lease and a battery earning revenue sits one of the most consequential — and most frequently underestimated — phases of any project: interconnection.

This guide walks through the full interconnection process for a utility-scale BESS in the ERCOT region, with a specific focus on projects in Texas-New Mexico Power (TNMP) and AEP Texas service territories. It covers the classification thresholds that determine your pathway, the ERCOT study and registration process, the utility-side coordination, fees, timelines, and the commissioning gauntlet at the end. We close with answers to the questions developers ask us most, and four anonymized case studies from real projects in TNMP and AEP territory.

Why the 10 MW Threshold Changes Everything

Before anything else, a developer needs to know which of two very different pathways their project falls into, because the answer drives the timeline, the fees, the study burden, and the engineering scope.

In ERCOT, generation and storage resources below 10 MW are generally treated as Distributed Generation (DG). These projects avoid the full transmission-level review and are handled primarily through the local utility's (the Transmission/Distribution Service Provider, or TDSP's) streamlined interconnection process. The evaluation focuses on the local distribution system — line loading, voltage impacts, protection coordination — rather than the statewide transmission grid. DG projects commonly clear the process in 8 to 12 months.

Projects at 10 MW and above are a different animal. They enter ERCOT's Generation Interconnection or Change Request (GINR) process — the full large-resource pathway — with a rigorous sequence of interconnection studies, comprehensive modeling requirements, a standardized interconnection agreement, quarterly stability assessments, and a formal commissioning and registration program. These projects typically take 18 to 30 months from application to commercial operation.

An important nuance that trips up many developers: the threshold is measured in megawatts of power, not megawatt-hours of energy. A 10 MW / 20 MWh system is a 10 MW resource for classification purposes — the 20 MWh simply means it can sustain full output for two hours. And because the DG pathway applies to resources under 10 MW, a project at exactly 10 MW does not qualify for the streamlined treatment. It goes through the full GINR process.

This is also why nameplate strategy is a genuine engineering and commercial decision. ERCOT's framework recognizes Self-Limiting Facilities — projects that are physically and contractually limited to inject below a threshold at the point of interconnection. For some developers, configuring a project at 9.9 MW instead of 10 MW is the difference between a one-year process and a three-year process. For others, offtake commitments, market participation plans, or project economics make the full 10 MW (or more) worth the longer road. An experienced owner's engineer should pressure-test this decision before the first application is filed, because changing course mid-queue is expensive.

The remainder of this guide assumes a project of 10 MW or greater following the full GINR pathway, with notes on where the TNMP and AEP tracks differ.

The ERCOT GINR Process, Phase by Phase

ERCOT is unusual among North American grid operators. There is no traditional cluster queue; each project moves on its own schedule through a defined sequence of studies, though projects can still be affected by others studying the same part of the grid. The process is administered through ERCOT's online Resource Integration and Ongoing Operations – Interconnection Services (RIOO-IS) portal, and the governing requirements live in Planning Guide Section 5.

Phase 0: Preparation and Application



The entity submitting the request — the Interconnecting Entity (IE) — begins by creating a RIOO-IS user account, which requires registration and multi-factor authentication setup. The GINR application itself demands a well-developed project definition: the point of interconnection (POI), the proposed in-service date, equipment selections, and preliminary electrical design. Application quality matters. Deficient or incomplete submissions get kicked back, and in a process where a missed window can cost a full quarter, rework is expensive.

Applicable fees are set by the ERCOT Fee Schedule. For a project at or above 10 MW, the administrative fees paid directly to ERCOT stack up as follows:

These figures reflect the fee schedule at the time of writing and should always be verified against the current ERCOT Protocols before budgeting, as they are periodically revised. They also exclude TDSP study costs, third-party engineering, and — critically — financial security.

Phase 1: Screening Study (approximately 90 days)

Once the application is validated, ERCOT performs a screening evaluation of the proposed POI, looking for immediate fatal flaws and system constraints. Results are typically returned within 90 calendar days of a validated application.

After screening, the project must post interconnection financial security of $50,000 per MW to hold its position — $500,000 for a 10 MW project. A portion (roughly 20%) is refundable if the project withdraws early in the process, but the security converts to fully non-refundable once construction-stage agreements are finalized. This deposit, far more than the administrative fees, is the number that disciplines speculative projects out of the ERCOT development pipeline.

Phase 2: Full Interconnection Study (roughly 120 to 180 days)

The FIS is the technical heart of the process, and here is a detail many developers miss: the FIS is conducted by the TDSP — TNMP or AEP Texas for the projects this guide covers — under ERCOT's framework. The study package includes steady-state power flow analysis, dynamic stability simulation, short-circuit analysis, and facility design evaluation, with individual studies typically running 45 to 60 days each in sequence across a four-to-six-month block.

The FIS phase is also where the project's modeling obligations come due. Within 90 days of application, the IE must deliver comprehensive technical models: steady-state, dynamic, and transient inverter models suitable for ERCOT's simulation platforms. ERCOT's Model Quality Guide — which now includes formal Model Quality Testing requirements along with UDM and PSCAD model guidelines — governs what is acceptable. Inverter-based resources like BESS receive particular scrutiny here, because their behavior during grid disturbances is defined by control software rather than physics, and poorly validated models are one of the most common causes of study delays and restudy cycles.

Depending on the location and technology, ERCOT may also require a subsynchronous resonance (SSR) vulnerability study and will require a Reactive Power study demonstrating that the resource meets the reactive capability requirements of Nodal Protocol Section 3.15.

Phase 3: Agreements, Registration, and the QSA Cycle

With studies complete and any required network upgrades defined, the project executes a Standard Generation Interconnection Agreement (SGIA) with the TDSP. Note for current projects: all SGIAs executed on or after January 1, 2026 must use the updated SGIA form dated November 6, 2025, which incorporates changes approved by the Public Utility Commission of Texas in Project 58211. The older 2019 form survives only for amendments to pre-2026 agreements.

After the interconnection agreement is signed, BESS projects submit the Battery Request for Information Template through RIOO-IS, and the project enters ERCOT's Quarterly Stability Assessment (QSA) cycle, with submission requirements defined in Planning Guide 5.3.5. The QSA runs on fixed quarterly windows, and this is one of the least forgiving schedule mechanics in the entire process: miss a data-submission deadline and the project does not slip by a week — it slips into the next 90-day quarterly window. Disciplined data management during this phase is worth real money.

In parallel, once the planned resource has met the requirements of Planning Guide Section 6.9 for addition to the planning models, it can be registered with ERCOT. The entity that registers and takes responsibility for the resource — the Resource Entity (RE) — may be the same as the IE or a different entity. Registration involves the Resource Asset Registration Forms (RARF), which feed ERCOT's network operations model, along with the Collector System Template covering the site's internal cable segments and the Dynamic Model Templates with the Model Quality Test report. Projects planning to co-locate load under 75 MW with the storage resource also complete a Load Information Form to coordinate that arrangement during interconnection.

Phase 4: Commissioning and Energization (roughly 90 to 120 days)

The final phase transforms a construction project into a market-registered, dispatchable ERCOT resource. Key elements include the Commissioning Plan, submitted for ERCOT approval to energize, synchronize, and complete required testing; AVR (automatic voltage regulator) testing tailored to BESS resources, with data submitted on ERCOT's standard templates; PMU (phasor measurement unit) sample data submission for transmission-connected resources; frequency ride-through and voltage ride-through capability reporting; the New Generator Commissioning Checklist, executed with the project's Qualified Scheduling Entity (QSE) across ERCOT's market and control systems; and the attestation required under the Lone Star Infrastructure Protection Act.

Only after this sequence — plus telemetry validation and settlement metering verification — does ERCOT grant approval to connect and, ultimately, commercial operation status that allows the battery to transact in the wholesale energy market and provide ancillary services.

The TNMP Track: What to Expect in Texas-New Mexico Power Territory

For a project in TNMP territory, the TDSP coordination track runs alongside the ERCOT process. TNMP administers interconnection applications through its PowerClerk-based portal, where the applicant registers an account and works through a structured application covering customer and installer information, the service point and its ESI ID (TNMP ESI IDs are 17-digit identifiers), and the generation configuration — with Energy Storage as its own generator type, including configurations for integrated storage systems and separate inverter-plus-battery arrangements, and DC-coupled versus AC-coupled designs for hybrid projects.

The application requires the technical package that defines the project electrically: a one-line diagram, a layout sketch showing a lockable, visible disconnect device, equipment certifications (IEEE 1547 / UL 1741), voltage and phase configuration, kVA rating and power factor, export intentions, and confirmation that the inverter manufacturer has supplied dynamic modeling values to the utility. The application concludes with selection of the interconnection agreement party structure — TNMP's agreement contemplates four options depending on whether the end-use customer, a separate generator owner, the premises owner, or a contracted energy-rights holder acts as the counterparty.

From there, TNMP's workflow proceeds through defined stages: application review (TNMP targets returning an executable interconnection agreement within about ten business days for standard applications), electronic signatures, construction, field inspection, service order generation, meter installation, and finally Permission to Operate. For utility-scale projects, expect substantially deeper engagement than the standard portal flow implies — direct coordination with TNMP engineering on substation or feeder connection design, easement and right-of-way review where TNMP facilities cross the project property or third-party land, and encroachment review for any construction near existing TNMP facilities. And as noted above, for a ≥10 MW project TNMP is also the entity conducting the ERCOT Full Interconnection Study, which makes a constructive working relationship with TNMP's planning engineers doubly valuable.

The AEP Texas Track: What to Expect in AEP Territory

AEP Texas administers its interconnection intake through the AEP Texas interconnection portal, with an application fee and a documentation package that will look familiar: one-line wiring diagram, inverter specification sheets, site plans, and a visible AC disconnect diagram. AEP engineering performs impact and safety studies evaluating whether the project will overload local facilities or cause voltage disruptions, and approved projects execute an Interconnection Service Agreement (ISA) with AEP, including payment for any physical grid upgrades the studies identify.

For projects below the DG threshold, AEP's process is the streamlined path — the utility-level review substitutes for the full ERCOT study sequence, and the ERCOT side reduces to registration, EPS (ERCOT-Polled Settlement) metering, and model verification with ride-through testing. For projects at 10 MW and above, the AEP track functions like the TNMP track described above: the utility coordination and ISA run alongside the full GINR process, with AEP as the studying TDSP.

In both territories, the closing sequence is the same shape: construction, utility field verification, bidirectional/settlement meter installation, the utility's Permission to Operate letter, and then ERCOT commercial operation status.

Beyond the Utilities: Permitting, Codes, and Fire Protection

Interconnection is necessary but not sufficient. Before energization, a BESS project must also clear local and state permitting, and battery storage presents a wrinkle: most local zoning ordinances were written before BESS existed, so the use is rarely listed. Projects frequently need a Conditional Use Permit (CUP) or Special Use Permit (SUP) from the local authority having jurisdiction, which introduces a public-facing, discretionary approval into the schedule.

On the code side, the installation must comply with the National Electrical Code and, centrally for BESS, NFPA 855, the Standard for the Installation of Stationary Energy Storage Systems. NFPA 855 drives siting and separation distances, fire suppression and detection design, deflagration protection, emergency response planning, and the hazard mitigation analysis that fire marshals increasingly demand. Fire protection engineering is not a checkbox at the end of design — separation requirements and suppression infrastructure affect site layout, and site layout affects the one-line, the collector system design, and even the interconnection application. It belongs in the design process from day one.

Case Studies

The following case studies are drawn from utility-scale BESS interconnection projects in ERCOT. Client names, locations, and identifying details have been anonymized.

Case Study 1 — TNMP Territory: The Threshold Decision That Saved a Year

A developer approached us with a planned 10 MW / 20 MWh standalone BESS on a distribution-adjacent site in west Texas TNMP territory, assuming the project would follow the utility's standard DG process. Our first-week screening flagged the problem: at exactly 10 MW, the project sat on the wrong side of ERCOT's DG threshold and was headed into the full GINR pathway — roughly $17,000 in ERCOT fees, a half-million-dollar security posting, and an 18-to-30-month clock, against a revenue model built on a 12-month energization target.

We ran a two-track analysis: the market revenue impact of derating to a 9.9 MW self-limiting configuration versus the carrying cost and schedule risk of the full GINR route. For this project's merchant strategy, the lost margin on 0.1 MW was immaterial next to a year of earlier revenue. We redesigned the power conversion system controls and protection settings to enforce the self-limiting configuration at the POI, documented it to ERCOT's self-limiting facility requirements, and filed through TNMP's process with a complete one-line, layout with lockable visible disconnect, and manufacturer dynamic modeling data on day one. The project cleared studies without a restudy cycle and energized inside its original financing window — approximately 14 months ahead of the GINR counterfactual.

Case Study 2 — TNMP Territory: Recovering a Stalled Application

A storage owner-operator engaged us to rescue a BESS interconnection in TNMP territory that had been in process for months without reaching an executable interconnection agreement. Our review found the application had been submitted with an incomplete technical package: the one-line diagram did not match the as-designed collector system, the layout sketch omitted the required lockable visible disconnect detail, and the inverter manufacturer's dynamic modeling values had never been transmitted to the utility — each deficiency individually minor, collectively fatal to review progress.

We rebuilt the submission as a coherent package: corrected one-line and site layout, IEEE 1547/UL 1741 certification documentation, complete generation detail with verified kVA and power factor data, and direct coordination with the inverter OEM to deliver validated dynamic models. We also restructured the interconnection agreement party designation, which had been filed under the wrong option for the project's ownership structure. The resubmitted application moved through TNMP review to an executable agreement in under three weeks, and the project proceeded through inspection and meter installation to Permission to Operate without further deficiency notices. The lesson we emphasize from this engagement: in interconnection, application quality is schedule.

Case Study 3 — AEP Texas Territory: Parallel-Tracking Utility and ERCOT Workstreams

A developer of a 9.95 MW / 20 MWh BESS in AEP Texas territory engaged us as owner's engineer with a hard commercial operation deadline driven by an offtake commitment. The project qualified for AEP's streamlined DER pathway, but the developer's baseline schedule treated the process as sequential: AEP application, then studies, then agreement, then ERCOT registration, then metering, then testing. Run that way, the timeline missed the deadline by roughly a quarter.

We restructured the program to run the tracks in parallel. While AEP's engineers conducted their impact and safety studies, we simultaneously prepared the ERCOT registration package — RARF data, collector system information, and dynamic models — and pre-coordinated the EPS settlement metering design so meter procurement started before the Interconnection Service Agreement was signed. Ride-through capability documentation was assembled from manufacturer test data during construction rather than after it. When AEP issued Permission to Operate, the ERCOT side was already staged: commissioning tests were scheduled, telemetry was validated within days, and the project reached commercial operation about ten weeks sooner than the sequential baseline — inside the offtake deadline.

Case Study 4 — AEP Texas Territory: Fire Protection as a Design Driver, Not an Afterthought

A 10 MW-class BESS project in a growing AEP Texas municipality came to us after receiving pushback from the local fire marshal on its preliminary site plan. The original layout, produced before any fire-protection engineering, placed battery enclosures at spacings that did not satisfy NFPA 855 separation requirements once the enclosure listing and fire-testing documentation were examined — and the municipality, with limited prior BESS experience, was requiring a full hazard mitigation analysis and emergency response plan before it would advance the project's Special Use Permit.

We took over the fire protection engineering scope and integrated it with the electrical design rather than bolting it on. The site was re-planned around compliant separation distances and fire-apparatus access; enclosure-level detection, suppression, and deflagration protection were specified against the manufacturer's large-scale fire test data; and we produced the hazard mitigation analysis and emergency response plan, then supported the developer in working sessions with the fire marshal and at the public SUP hearing. The revised layout required rerouting the DC collection and shifting the interconnection switchgear — changes that would have been catastrophic if discovered after the utility design package was submitted, but manageable because the site plan, one-line, and AEP application were finalized together. The project secured its Special Use Permit, cleared AEP's review on the corrected package, and avoided what we conservatively estimate would have been a six-month redesign loop had the original plan reached the utility first.

The Bottom Line

Interconnecting a utility-scale BESS in ERCOT is a multi-front campaign: ERCOT's study, modeling, registration, and commissioning machinery on one front; the TDSP's application, design review, agreement, and inspection process on another; and local permitting, codes, and fire protection on a third. The projects that reach commercial operation on schedule are the ones that treat these fronts as one integrated program — where the nameplate strategy is settled before the application is filed, the models are validated before ERCOT asks, the QSA deadlines are managed like the schedule cliffs they are, and NFPA 855 shapes the site plan instead of tearing it up.

That integration is the core of what an owner's engineer does. If you are developing battery storage in TNMP, AEP Texas, or anywhere in the ERCOT region — whether you are sizing your first project against the 10 MW threshold or untangling a stalled application — our team has walked this road and can help you plan it, de-risk it, and deliver it.

Contact us to discuss your project's interconnection strategy.

Frequently Asked Questions