Two ERCOT changes, two different deadlines: TLS certificate rotation and NPRR1188


ISO Market Edge by Hartigen | Volume 10


What ERCOT market changes are coming in 2027?

  • TLS certificate rotation (IT and security). ERCOT expects to start renewing its TLS certificates monthly between June and the end of 2027. This affects anyone connecting to ERCOT's External Web Services (EWS) API. A Chain of Trust model becomes mandatory at the end of 2029.

  • NPRR1188 (real-time desk, metering and settlements). Controllable Load Resources (CLRs) that are not Aggregate Load Resources (ALRs) move from Load Zone to nodal dispatch and settlement. ERCOT is targeting January 2027.

The two changes aren't related. Here's what each one means and where to start.


At a glance

  Change 1:
TLS certificate rotation
Change 2:
NPRR1188 nodal dispatch for CLRs
What changes ERCOT’s TLS certificates move to monthly renewal Non-ALR CLRs move from Load Zone to Resource Node dispatch and settlement
Who it affects Every Market Participant connecting to ERCOT’s EWS API QSEs representing non-ALR CLRs
Teams involved IT, platform admins, security Real-time desk, market submissions, metering, settlements
Key dates Monthly renewal expected between June and end of 2027; Chain of Trust mandatory at end of 2029 Market trials December 18, 2026; go-live targeted for January 28, 2027 (2027 Release 1)
First step Audit your systems for pinned ERCOT certificates or thumbprints Confirm which CLRs are non-ALR and start meter planning


Change 1: ERCOT TLS certificate rotation

What's happening. In 2025, the CA/Browser Forum approved an industry-wide reduction in TLS certificate lifetimes. In response, ERCOT will move to monthly certificate renewal. ERCOT estimates this will begin between June and the end of 2027.

Why ERCOT is doing it. Shorter certificate lifetimes shrink the window in which a compromised key can be used. They also keep certificate details current. Revocation methods (CRL and OCSP) have proven unreliable, and frequent renewal closes that gap.

What it means for you. Your impact depends on how your systems validate ERCOT's certificates today.

  • If you pin a certificate or thumbprint: you'll need to update it by hand every month once rotation begins. ERCOT will not host an ACME service to automate client renewals. This approach stops being supported at the end of 2029.

  • If you validate through trusted Certificate Authorities: you may already be in good shape. ERCOT's certificates are issued by GlobalSign, which is broadly trusted.

ERCOT recommends a Chain of Trust model. Instead of trusting one ERCOT certificate, your systems trust the GlobalSign root and intermediate chain. Future ERCOT renewals are then recognized with no action on your side.

 Timeline

  1. Now through 2029: ERCOT keeps publishing individual certificates for participants still on the thumbprint model. Manual updates are your responsibility.

  2. Between June and end of 2027 (estimated): ERCOT begins monthly certificate renewal.

  3. End of 2029: Chain of Trust becomes mandatory. The legacy thumbprint process is no longer supported.

Your readiness checklist

  • Find out how your systems validate ERCOT's TLS certificates today: pinned thumbprint or trusted Certificate Authority.

  • Audit the places pinned certificates tend to hide: Java truststores, .NET certificate validation callbacks, API gateways, load balancers, middleware and firewall SSL inspection rules.

  • Remove hardcoded ERCOT thumbprints and validate through the GlobalSign root and intermediate CA chain.

  • If you stay on pinning for now, assign an owner for monthly certificate updates once rotation begins.


The practical takeaway: a planned migration in 2027 is easier than a forced one in late 2029.


Change 2: NPRR1188, nodal dispatch and settlement for Controllable Load Resources

Quick background. In ERCOT, large loads that can reduce demand register as Load Resources. A Controllable Load Resource (CLR) is dispatched much like a generator. It bids the price it's willing to pay, and Security-Constrained Economic Dispatch (SCED) moves its consumption up or down every five minutes. A Non-Controllable Load Resource (NCLR) doesn't follow SCED. It drops load through an under-frequency relay or when ERCOT sends a deployment instruction through its QSE. NPRR1188 applies to CLRs only, and its nodal dispatch and settlement changes apply to CLRs that are not Aggregate Load Resources (ALRs).

What's happening. The PUCT approved NPRR1188 in November 2024. Today, a CLR bids only in the Real-Time Market and settles at its Load Zone price. Under NPRR1188, CLRs that are not ALRs will be dispatched and settled at their own Resource Node, the same way a generator is. The price they pay will reflect conditions at their location on the grid. ALRs are not affected and keep settling at their Load Zone.

The other big change is in bidding. A new Energy Bid Curve replaces today's real-time energy bid and can be submitted in both the Day-Ahead Market (DAM) and Real-Time. For the first time, a CLR can lock in energy purchases a day ahead. A cleared Day-Ahead bid becomes a new award, the Awarded Energy CLR Bid, priced at the CLR's Resource Node Day-Ahead price.

Timing. ERCOT plans to begin market trials on December 18, 2026, and is targeting 2027 Release 1 on January 28, 2027, for go-live.

The gating requirement: settlement metering. ERCOT will create a new Resource Node and separate settlement metering for each affected CLR (an EPS meter for CLRs co-located with a generator; TDSP-read meters for most others). Each CLR must have its meter installed and complete ERCOT qualification before go-live. Resources that miss either step won't be eligible to participate when the change takes effect. Meter procurement and field installation run on their own timeline, so start here first.

What changes, by team

Real-time desk (SCED)

  • Dispatch moves from the Load Zone to the Resource Node, using a nodal shift factor.

  • Two new Load Resource statuses arrive: ONTEST and ONHOLD. For both, the Base Point is set to telemetered MW.

  • OUTL handling is updated: the resource is not consuming energy, and telemetered MW is 0.

Market submissions (DAM)

  • Non-ALR CLRs can submit energy bids in the DAM at their Resource Node.

  • Low Power Consumption (LPC) is set to 0, with a DAM dispatch range of 0 to Maximum Power Consumption (MPC) minus LPC. 

  • The RTMEnergyBid submission is renamed EnergyBidCurve, since it will serve both Real-Time and Day-Ahead.

Settlements

Non-ALR CLR consumption settles at the nodal price instead of the Load Zone price. NPRR 1188 builds CLR Load into existing settlement calculations. Expect changes to:

  • Resource Node versus Load Zone price selection.

  • CLR metering and mappings. Every CLR that isn’t an ALR gets its own Resource Node and must be metered separately. CLRs co-located with a generator need an ERCOT-Polled Settlement (EPS) meter. Others can use Transmission and/or Distribution Service Provider (TDSP) read meters, or opt for EPS at 10 MW or more if they’re the only load at their delivery point.

  • The Real-Time Energy Imbalance Amount (RTEIAMT) and Set Point Deviation Amount (SPDAMT) charge codes, which will use the new CLR meter mappings. For RTEIAMT, CLR metered energy will be settled in the Resource Node imbalance calculation at the CLR’s Real-Time Settlement Point Price, along with any Day-Ahead Energy Bid Curve awards at that Resource Node.

  • Location-level settlement reporting and tie-outs, which will need to reflect the new CLR meter mappings so each CLR’s settlement ties to its own Resource Node.

IT and data teams

XSD changes are coming to reports including the Current Day Report (CDR) and DAM Aggregate Credit Exposure. Expect updates to 2-Day DAM and SCED Energy Curves, 2-Day DAM Bids and Offers, and 60-Day DAM and SCED Disclosure reports. ERCOT will share XSD timelines in future Technology Working Group (TWG) meetings.

Your readiness checklist

  • Confirm which of your CLRs are non-ALR. Only these are in scope.

  • Start meter procurement and installation now (EPS or, where allowed, TDSP-read).

  • Work with your meter provider and ERCOT to complete qualification before go-live.

  • Review bid, Current Operating Plan (COP), telemetry and offer validation processes for the new statuses and Resource Nodes.

  • Review shadow settlement logic for nodal pricing, loss treatment and Unaccounted for Energy (UFE).

  • Watch for ERCOT's API and XSD specifications, and plan for testing in ERCOT's Market Operations Test Environment (MOTE) ahead of market trials.

 

Why this matters beyond ERCOT

If you trade in three or more markets, ERCOT is rarely the only change on your calendar. Every ISO/RTO rule change ripples through bids, telemetry, meters and settlements, often at the same time. Tracking each one, translating it into system changes and testing before go-live is the work that keeps you market-ready.

That's the work our team does every day. We don't just build software for energy markets. We come from them. With 15+ years in ISO/RTO markets, over 99.997% SaaS uptime and 54,000+ hours saved by clients, we read the TWG decks so you don't have to.

Our job isn't done at go-live. It's done when you see results, and even then, we stay.

Have questions about ERCOT’s changes?

Connect with us to start the conversation.

———

Sources: ERCOT TWG, TLS Certificate Lifetime Reduction (March 2026); Hartigen market change notes on NPRR1188 (ERCOT TWG updates April, May and July 2026).


A thank you to the people behind this issue

Volume 10 of ISO Market Edge comes from inside our own team. Emilio Torres followed both of these changes through ERCOT's Technology Working Group sessions this year, and his market notes shaped every section above. Rashmi Karnik, our director of product development, helped translate each rule change into what it means for your systems and day-to-day work. Thank you both for turning a stack of TWG decks into something our readers can act on.


Frequently asked questions

Are the ERCOT TLS certificate change and NPRR1188 related?

No. The TLS change is a security update to how systems connect to ERCOT's EWS API. NPRR1188 is a market rule change to how non-ALR Controllable Load Resources are dispatched and settled. They have separate timelines and affect different teams.

When will ERCOT start monthly TLS certificate renewals?

ERCOT estimates monthly renewal will begin between June and the end of 2027. Migration to a Chain of Trust model becomes mandatory at the end of 2029.

What is NPRR1188, and when does it go live?

NPRR1188 moves Controllable Load Resources that are not Aggregate Load Resources from Load Zone to nodal dispatch and settlement. It adds Resource Nodes, separate CLR metering and new ONTEST and ONHOLD statuses. ERCOT is targeting 2027 Release 1 on January 28, 2027.

What happens if a CLR's meter isn't in place by go-live?

It will not be eligible to participate under the new framework until its meter is installed and qualification is complete.

Next
Next

DERs Are Entering the Market. What It Means for You.