u/koka786

Most people think electricity pricing in Texas is simple — you pay what you pay. The reality is far more complex and frankly fascinating if you're running energy-intensive operations.

Last week ERCOT had one of its more volatile pricing events of the year. Here's what actually happened:

WHAT HAPPENED

North Zone: $175/MWh

Houston Zone: $105/MWh

West Zone: $9/MWh

Peak spike: $256/MWh

All of these prices existed simultaneously across the same grid at the same moment. That $246/MWh spread between West Zone and North Zone is not unusual — it happens regularly due to transmission congestion between wind-heavy West Texas and the demand centers in Dallas and Houston.

WHY THIS MATTERS FOR ENERGY-INTENSIVE OPERATIONS

A 10MW facility running at full load during that North Zone spike was consuming electricity at roughly $2,500 per hour — compared to $90 per hour during normal $9/MWh conditions.

That's a 28x difference in energy cost for the same workload.

THE PHYSICS BEHIND IT

ERCOT uses Locational Marginal Pricing (LMP). Every node on the grid has its own real-time price determined by three factors:

1. Energy component — the cost of generating the next megawatt on the system

2. Congestion component — transmission bottlenecks between zones

3. Loss component — electrical losses over distance

When West Texas wind farms are generating more power than the transmission lines can carry east, West Zone prices crater — sometimes going negative.

Meanwhile North Zone prices spike because local gas plants have to pick up the slack.

This is why location matters enormously in ERCOT. A facility in Abilene or Midland operates in a fundamentally different energy market than one in Dallas or Houston, even though they're on the same grid.

THE CONSERVATION OPPORTUNITY

Here's the part most operators miss: ERCOT actively wants large flexible loads to reduce consumption during price spikes. It's not just about saving money — it's about grid stability.

When large loads curtail during stress events, they prevent rolling blackouts for residential customers. ERCOT's demand response programs actually pay large operators to curtail during emergency conditions.

The math works both ways:

- Curtailing a 10MW load for 3 hours during a $150/MWh spike saves roughly $4,500 in energy costs

- Participating in ERCOT's voluntary demand response program generates additional revenue on top of the savings

WHAT MOST OPERATORS GET WRONG

The biggest mistake I see is treating curtailment as a manual decision. Someone watches prices, makes a judgment call, calls the operations team, and by the time anything happens the spike is already half over.

The economics only work if your response is automated and immediate. A price spike that lasts 45 minutes doesn't wait for a 20-minute decision chain.

Senate Bill 6, signed in Texas in 2025, now requires new large loads over 75MW to have automated curtailment capability built in from day one. The regulators are essentially forcing the industry to solve the manual response problem.

THE BIGGER PICTURE

Texas added 225 new large load interconnection requests in 2025 alone — mostly data centers and Bitcoin mining. EIA projects ERCOT wholesale prices could increase 79% by 2027 if demand growth outpaces new generation.

The operators who build energy flexibility into their operations now — treating their facility as a grid-responsive asset rather than a passive consumer — will have a significant cost advantage over those who don't.

Happy to answer questions about ERCOT pricing mechanics, LMP, demand response programs, or how SB6 changes the compliance landscape for large loads.

What are you all doing to manage energy costs in this environment?

Been doing a lot of work recently around QMSR readiness and wanted to share some observations because I'm seeing a lot of confusion out there — even among experienced QA teams.

Quick background: FDA's Quality Management System Regulation (QMSR) takes effect February 2026 and aligns 21 CFR Part 820 with ISO 13485:2016. On paper it sounds like a simple harmonization. In practice it's a meaningful shift for a lot of US-based device manufacturers.

Here's what I think is actually changing that teams are underestimating:

**1. Design controls get more rigorous**

ISO 13485 has stricter requirements around design and development planning than the old Part 820. If your DHF was built purely to legacy FDA expectations, you likely have gaps — particularly around design review records, verification/validation traceability, and transfer documentation.

**2. Complaint handling and feedback loops**

QMSR pushes harder on post-market surveillance integration. Your complaint handling process needs to feed into a documented feedback loop that demonstrably influences your risk management file. A lot of QMS setups I've seen treat these as separate silos.

**3. Risk management is now truly end-to-end**

ISO 14971 compliance has to be woven throughout — not just a standalone risk file you pull out for audits. Auditors will be looking at whether risk outputs actually connect to design decisions, labeling, and post-market data.

**4. Supplier controls**

ISO 13485 supplier requirements are more prescriptive than legacy Part 820. Supplier evaluation, monitoring, and re-evaluation cadences need to be documented and defensible.

**What's actually helping teams prepare:**

- Gap assessment against ISO 13485:2016 clause by clause, not just at the section level

- Updating your internal audit checklist to reflect QMSR language, not just old Part 820 language

- Making sure your design history file has a clear traceability matrix from user needs all the way through V&V

- Getting your risk management file genuinely integrated with your post-market surveillance process before an auditor asks for the connection

The teams I've seen handle this best are the ones treating QMSR transition as a full QMS audit — not just a documentation update exercise.

Happy to answer questions if anyone is working through specific gaps. This stuff is genuinely complex and every device category has its own wrinkles.