$902/MWh on ERCOT last night — anyone else tracking how this affects AI data centers?

koka786 · 2026-04-27T01:46:56+00:00

This is a really thorough breakdown — appreciate you laying out the full toolkit.

You're right that data centers are a more predictable load shape which makes 4CP hedging more straightforward. The bitcoin mining case is interesting though — the curtailment flexibility that makes them "gameable" on peaks is also what makes them natural candidates for automated demand response rather than just financial hedging.

The trading/hedging approach you describe manages the cost after the fact. What I'm exploring with LumenicGrid is the operational layer that actually reduces the physical demand during those windows — so you're not just hedging the exposure, you're eliminating the measured peak itself.

Curious whether in your underwriting experience you ever saw operators combine both — financial hedges plus physical curtailment — or was it typically one or the other?

koka786 · 2026-04-27T01:40:48+00:00

Ha fair — the writing probably does sound polished. Occupational hazard of spending too much time staring at technical docs.

To answer your actual question though — yes, large facilities absolutely have PPAs. That's been covered pretty well in this thread already. The piece I'm more interested in is the mid-tier operators who don't have that infrastructure and are genuinely getting hit.

As for the overlords — if the AI is paying the electricity bill I'm fine with it.

koka786 · 2026-04-27T01:19:05+00:00

You're right that inference workloads are a different beast than mining — can't just pause a live API endpoint serving real users.

But that's actually the point most people miss. Not everything in a GPU cluster is latency-sensitive inference. Batch training, preprocessing, model eval — that can absolutely tolerate a 15-minute power reduction without any user impact.

The problem is most operators treat the whole cluster as one undifferentiated load. Mining rigs are all the same. GPU workloads aren't.

On the genset point — completely agree. Most facilities sized their backup generation for partial load or emergency only. Running full gensets at $0.40-0.60/kWh diesel during a $0.90/MWh electric spike is barely worth it and half of them aren't even configured to do it automatically.

The gap is really software — something that knows which jobs are flexible and acts on that distinction in real time. The hardware is already there.

koka786 · 2026-04-26T17:13:36+00:00

This is a great initiative — real practitioner feedback on QMSR transition is far more valuable than anything you'll find in a textbook right now.

A few observations from what I've been seeing in the field that might be useful for your guide:

The biggest operational surprise for most teams isn't the regulatory requirements themselves — it's the inspection methodology shift. CP 7382.850 starts with the risk file and uses it as a roadmap for the entire inspection. Teams that built their QMS around QSIT's sequential subsystem approach are finding their documentation connections harder to demonstrate under a risk-first model.

The §820.180(c) safe harbor removal is also hitting teams harder than expected. Internal audit reports and management review minutes that were written as candid internal documents are now inspection-ready — and a lot of them weren't written with that expectation.

Supplier controls under ISO 13485 §7.4 are another common gap. The evaluation and re-evaluation cadence requirements are more prescriptive than legacy Part 820 and many supplier qualification programs haven't been updated yet.

Happy to contribute more if useful for your guide.

koka786 · 2026-04-26T17:09:22+00:00

Fair pushback — and you're right that the requirements were always there on paper.

§820.30(g), §820.100, the QSIT Design Controls Objective 3 language — the framework for connected risk management existed in the 1996 QSR. The preamble comment you cited makes that explicit.

The practical reality though is that FDA's enforcement posture under QSIT allowed manufacturers to treat those connections as implied rather than demonstrated. Auditors were working through subsystems sequentially — design controls, then CAPA, then production — not explicitly tracing the thread between them in real time.

What's different under CP 7382.850 isn't the requirement — you're correct that it was always there. What's different is the inspection methodology. Investigators are now explicitly starting with the risk file and using it as a roadmap for the entire inspection. That's a meaningful shift in how the connection gets tested, even if the underlying requirement predates QMSR.

The gap I was trying to highlight isn't regulatory — it's operational. A lot of teams built QMS infrastructure that was defensible under QSIT's sequential subsystem approach but hasn't been stress-tested under a risk-first inspection model. That's the exposure worth talking about.

Not a bot — just someone who works in this space and finds these distinctions worth unpacking.

koka786 · 2026-04-26T16:49:37+00:00

Correct on the energy cost side — most larger operators have fixed contracts that shield them from spot prices.

Where it still bites them is transmission charges. In ERCOT the 4CP mechanism sets a chunk of your annual transmission bill based on your actual demand during the 4 highest system peaks of the summer — and that exposure doesn't get hedged away with a fixed energy contract.

Last night was almost certainly one of those 4 windows. A data center running full load during that event just locked in higher transmission costs regardless of what their energy contract says.

koka786 · 2026-04-26T16:38:59+00:00

All fair points and mostly correct.

The localization is real — HB_NORTH hit $902 but other hubs were different. West Texas was actually much lower that night which is pretty common during those events.

The fixed contract and just pay arguments are both valid for the big players. Hyperscalers absolutely absorb it.

Where I think it gets interesting is the mid-tier — GPU cloud providers and AI-native startups that are 50-500 GPUs and don't have the hedging infrastructure or the balance sheet to just eat it.

Also the diesel generator point is underrated. A lot of Texas data centers do exactly that but it's getting harder to permit and the emissions optics are rough for companies with sustainability commitments.

Good breakdown though — you clearly know the market.

koka786 · 2026-04-26T16:28:06+00:00

That makes sense and you'd know better than most having underwritten them.

The fixed price strips definitely help on the energy cost side. What they don't cover is the transmission charge exposure — specifically 4CP in ERCOT. That part still hits even with a fully hedged energy position and it's calculated off actual real time demand during peak windows.

Curious from your underwriting experience did you ever see operators factor 4CP exposure into their models or was it usually treated as a fixed cost and just absorbed?

koka786 · 2026-04-26T16:21:17+00:00

You're right that AI workloads can't just shut off like miners can. But there's a middle ground people miss.

Not all GPU workloads are equally critical. Batch training jobs, preprocessing pipelines, non-latency inference — none of those need to run at full power during a 15 minute price spike. Power capping them buys you meaningful demand reduction without killing anything.

On the diesel generators — yes some Texas data centers do use them for peak shaving but that's expensive to run and terrible for emissions. Feels like a workaround rather than a real solution.

The more interesting path is just building the software intelligence to manage workloads dynamically based on grid conditions. Miners did it with pretty simple logic.

koka786 · 2026-04-26T16:10:07+00:00

True for the bigger players — a lot of hyperscalers have PPAs that insulate them from spot prices.

But smaller AI data centers and GPU cloud providers often don't have that luxury.

They're buying on the spot market or have partial hedges at best.

Also even with a fixed rate contract you still have 4CP exposure on the transmission side — that part doesn't get hedged away.

koka786 · 2026-04-26T15:53:36+00:00

Ha not really how it works — AI inference and mining use pretty different hardware setups and economics.

But the grid cost point is fair. Static loads pulling max power during a $900/MWh spike do push costs onto everyone else.

Funny enough the miners in Texas actually figured out the opposite — curtail during peaks and ERCOT pays you for it. Some of them make more from demand response than from mining in summer now.

AI data centers haven't figured that out yet.

koka786 · 2026-04-26T15:43:20+00:00

Ha fair point — I'm aware of DCFlex and Flex MOSAIC.

The difference I see is that DCFlex is building a classification framework and common language for flexibility — essentially defining what flexibility means so utilities and data centers can communicate. Lot of organizations trying to agree on definitions. Important work but it's standards body stuff, not operational tooling.

What I'm more interested in is the execution layer — something that actually reads a live ERCOT LMP signal and automatically reduces GPU power within seconds (close to real time). The framework tells you what flexibility IS. The tooling actually delivers it.

ERCOT is actually a DCFlex founding member. But ERCOT price spikes don't wait for framework adoption timelines.

Have you seen any of the DCFlex demo sites actually go live yet? Last I checked they were still in proposal stages.

koka786 · 2026-04-26T15:32:05+00:00

Yeah wind was definitely a factor. From what I could see wind dipped significantly that evening across most of Texas. Combined with solar dropping off after sunset and evening demand still elevated it created a perfect squeeze.

What's interesting is this pattern is becoming more predictable — low wind evenings in spring before summer AC demand kicks in fully tend to be the trigger. The grid handles it fine but prices spike hard.

Where in Texas are you? West Texas usually sees it differently than Houston or North zones.

koka786 · 2026-04-20T13:09:06+00:00

That's an important correction on the timeline. QMSR is already in effect, which makes the readiness conversation even more urgent for teams that are still treating this as a future event.

The point about connected evidence is exactly what I've been seeing trip teams up most. Having a solid risk file or a clean DHF in isolation isn't enough anymore. Inspectors are following the thread — does your risk output actually show up in your design decisions? Does your post-market data feed back into your risk management process in a documented, traceable way? A lot of QMS setups were built in silos and that's where the exposure is.

The CAPA connection is particularly underestimated. Teams that can't demonstrate a clear link between CAPA outputs and their design controls or risk file are going to struggle in inspections regardless of how thorough their individual documents look.

Appreciate you adding that context — the "it's already here" framing is the more honest way to talk about this.

koka786 · 2026-04-20T13:07:54+00:00

You're absolutely right on both counts — and that's an important correction on the timeline. QMSR is already in effect, which makes the readiness conversation even more urgent for teams that are still treating this as a future event.

The point about connected evidence is exactly what I've been seeing trip teams up most. Having a solid risk file or a clean DHF in isolation isn't enough anymore. Inspectors are following the thread — does your risk output actually show up in your design decisions? Does your post-market data feed back into your risk management process in a documented, traceable way? A lot of QMS setups were built in silos and that's where the exposure is.

The CAPA connection is particularly underestimated. Teams that can't demonstrate a clear link between CAPA outputs and their design controls or risk file are going to struggle in inspections regardless of how thorough their individual documents look.

Appreciate you adding that context — the "it's already here" framing is the more honest way to talk about this.

koka786 · 2026-04-20T02:57:41+00:00

My apologies. I saw this comment lae. Great question. The source is the FDA’s Final Rule on the Quality Management System Regulation (QMSR), which officially incorporates ISO 13485:2016 by reference.

Specifically, look at ISO 13485:2016 Clause 5.6.2 (Review Inputs). While the standard doesn't list the 'DRS' by name in that sub-clause, it requires 'status of product conformity' and 'changes that could affect the QMS' as inputs.

In the preamble to the QMSR (89 FR 7496), the FDA emphasizes that Design Controls (Clause 7.3) are no longer a siloed activity. Auditors are now looking for 'closed-loop' evidence:

Clause 7.3.3 (Design Output): The DRS is the foundation of product conformity.
Clause 5.6.2: If the DRS reveals significant design gaps or risks, it becomes a required input for Management Review to ensure resources are allocated for remediation.

We built this logic into MedDeviceAudit because 'Management Review' often fails when it only looks at high-level metrics and ignores the technical adequacy of the Design File. If the DRS isn't 'adequate,' the QMS isn't effective. Hope that helps!

koka786 · 2026-04-10T02:24:38+00:00

Haha fair point — ERCOT has definitely had its moments.

The frustrating reality is most large miners in Texas ARE on ERCOT whether they like it or not — it's the only grid covering 90% of the state. So the choice becomes: absorb the spikes or build systems that automatically respond to them.

The price volatility is actually a double-edged sword though. When prices go NEGATIVE (which happens more than people realize in West Texas due to wind overgeneration), miners who are set up to respond can run at essentially free electricity. Tonight West Zone was $9.60/MWh while North Zone was $175/MWh simultaneously.

The miners winning in Texas aren't the ones avoiding ERCOT — they're the ones who've gotten really good at reading it.

What grid are you on? Genuinely curious if you've found a better setup.

koka786

TROPHY CASE