<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="https://www.jain.com/assets/img/6adafce5-1.1"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Wind Energy &#8211; Jain.com</title>
	<atom:link href="https://www.jain.com/tag/wind-energy/feed" rel="self" type="application/rss+xml" />
	<link>https://www.jain.com/</link>
	<description>Data centers, connectivity, and security — news and analysis</description>
	<lastBuildDate>Fri, 25 Sep 2026 00:41:19 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.jain.com/assets/img/e2794d1c-jain-com-icon-512-150x150.png</url>
	<title>Wind Energy &#8211; Jain.com</title>
	<link>https://www.jain.com/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Texas&#8217;s 260 MW Wind Ruling Shows AI Co-Location Is a Grid Deal, Not an Exit</title>
		<link>https://www.jain.com/texas-puc-approves-crusoe-260-mw-ai-data-center-wind-farm-co-location</link>
		
		<dc:creator><![CDATA[Deepak Jain]]></dc:creator>
		<pubDate>Thu, 30 Jul 2026 16:00:00 +0000</pubDate>
				<category><![CDATA[Power Infrastructure]]></category>
		<category><![CDATA[co-location]]></category>
		<category><![CDATA[Crusoe]]></category>
		<category><![CDATA[data center power]]></category>
		<category><![CDATA[demand response]]></category>
		<category><![CDATA[ERCOT]]></category>
		<category><![CDATA[SB 6]]></category>
		<category><![CDATA[Texas PUC]]></category>
		<category><![CDATA[Wind Energy]]></category>
		<guid isPermaLink="false">https://www.jain.com/texas-puc-approves-crusoe-260-mw-ai-data-center-wind-farm-co-location</guid>

					<description><![CDATA[Texas regulators approved Crusoe's 260 MW AI data center beside a wind farm, but it must cut its full load within 30 minutes in grid emergencies. The ruling signals that co-location in ERCOT secures power supply, not freedom from grid reliability duties.]]></description>
										<content:encoded><![CDATA[<div class="jain-post-grid">
<div class="jain-post-main">
<section class="jain-tldr" aria-label="Plain-English summary">
<p class="jain-tldr-kicker">TL;DR · 30-second read</p>
<h2>The Short Version</h2>
<p>Texas regulators approved a giant artificial intelligence computing center, essentially a warehouse full of computers, built right beside a wind farm. The catch: whenever the state&#8217;s power grid is in trouble, the center must shut off completely within 30 minutes, even if that means flipping its main breakers.</p>
<p>The center uses roughly as much electricity as the wind farm produces, about what a small city draws. Its builders called the rule excessive. Regulators disagreed, because in an emergency the grid needs that wind power. The message to everyone else: building next to a power plant does not free you from the grid&#8217;s rules.</p>
</section>
<p>The Public Utility Commission of Texas has approved a net metering arrangement for a 260 MW AI data center co-located with a wind farm of 265.5 MW, Utility Dive reported. Net metering here means the data center draws power directly from the adjacent generator, with only the difference between the two settled against the grid. The project is developed by Crusoe and will be operated by Ensign, the large-load customer. It is the second data center planned at the site, bringing combined load to about 525 MW.</p>
<p>In an order dated July 23, 2026, the commission required the new facility to be able to curtail its full load within 30 minutes during grid emergencies, by physical breaker disconnection if necessary. It also barred the project from paid demand response programs tied to the arrangement. The commission rejected the developer&#8217;s argument that the second facility should be exempt from the curtailment conditions applied to the first.</p>
<h2>Executive Summary</h2>
<p>Texas has approved one of the first behind-the-meter AI data centers under SB 6, the 2025 state law that set new rules for large electricity users on the ERCOT grid and gave the grid operator authority to disconnect data centers during emergencies. Behind-the-meter means the load sits on the generator&#8217;s side of the grid connection and consumes its output directly. The approval lets the project proceed, but on terms that commissioners largely adopted from ERCOT&#8217;s proposed reliability conditions rather than writing a project-specific exception.</p>
<p>Those terms matter well beyond one site. Because the commission chose a general framework over a bespoke deal, the order is likely to serve as a reference point for other co-located loads in Texas. They include a pending application from Amazon and Vistra for a data center campus beside the Comanche Peak nuclear plant southwest of Fort Worth.</p>
<p>The practical takeaway for developers is that sitting next to a generator secures a power supply in normal conditions. It does not remove the load from the grid&#8217;s emergency claims. In a grid emergency, the wind farm&#8217;s output is treated as a grid resource, and the data center must be able to step aside quickly and without payment.</p>
<h2>Why the Commission Counted Both Buildings</h2>
<p>The heart of the dispute is simple arithmetic. The wind farm is rated at 265.5 MW. The first data center at the site accounts for roughly 265 MW, and the new one adds 260 MW, for a combined load of about 525 MW. Crusoe and Ensign argued that the first facility was already subject to curtailment and that the earlier reliability condition on the co-located wind project made further curtailment unnecessary. In their view, forcing the entire site offline was disproportionate.</p>
<p>The commission saw the mechanism differently. If the first facility were curtailed during an emergency while the second stayed online, the second facility&#8217;s 260 MW could absorb nearly all of the wind farm&#8217;s 265.5 MW nameplate output on-site. Almost nothing would reach the grid at the moment the grid most needed it. Commissioners, adopting the administrative law judge&#8217;s recommendation with revisions from Chairman Thomas Gleeson, concluded that this would undermine the goal of keeping generation available to the grid during emergencies. That reasoning is what turns co-location from a private supply arrangement into a conditional deal with the grid: the load gets the generator&#8217;s output in ordinary hours, and the grid gets it back when reliability is at stake.</p>
<p>This is the substance behind the headline. The order does not treat an adjacent wind farm as a private power plant that exits the data center from ERCOT&#8217;s reliability regime. The generator remains, in the commission&#8217;s framing, capacity the grid can call on. Any co-located load large enough to consume that capacity must be able to get out of the way.</p>
<h2>The 30-Minute Clock and the Backup-Power Question</h2>
<p>The operating requirements are specific. The data center must be able to shed its full load within 30 minutes, including by physically opening breakers. ERCOT should give 60 minutes&#8217; advance notice when practicable, and the operator may voluntarily commit to a faster 10-minute response. This is more flexibility than traditional industrial loads have been asked to provide, and it reframes the ability to shut down rapidly as a condition of operating behind generation rather than an optional grid service.</p>
<p>For an AI operator, disconnection means lost compute time unless something else carries the load. Chris Talley, co-founder of GridTracker, wrote after the decision that the order is not a “death blow” to co-location in ERCOT but that “this architecture now essentially requires full backup capacity.” He later clarified that he meant resources able to carry the load off-grid for a meaningful period, not just ride through a brief interruption, and he called this an “untested assumption.” That caveat is worth keeping. The order sets a curtailment obligation; it does not mandate backup generation. Whether operators respond by building on-site capacity, by accepting downtime, or by designing workloads that tolerate interruption is a commercial choice the ruling leaves open.</p>
<p>What the ruling does settle is that the cost of staying online through an emergency now sits with the developer. For any co-location pitch built on the idea that an adjacent generator guarantees uninterrupted power, that is a material change in the assumptions.</p>
<h2>Emergency Duty Is Not a Paid Service</h2>
<p>The ban on paid demand response programs tied to the arrangement is the order&#8217;s quieter economic lever. Demand response programs typically pay large users to reduce consumption when the grid is stressed, and flexible loads can earn meaningful revenue from them. By prohibiting compensation here, the commission drew a line between mandatory emergency curtailment, which is a condition of the co-location arrangement, and voluntary grid services, which can be sold.</p>
<p>The effect is to remove an offsetting revenue stream from the project&#8217;s economics. A developer cannot count the same flexibility twice: once as the price of permission to co-locate and again as a product sold back to the grid. For project finance models that assumed curtailment could be partly monetised, that assumption no longer holds under this framework.</p>
<h2>A Template Under SB 6, With Comanche Peak as the Next Test</h2>
<p>Because commissioners largely adopted ERCOT&#8217;s proposed conditions rather than negotiating a one-off exception, the order reads as a template for future behind-the-meter projects in Texas. Utility Dive has reported that Texas faces a large-load interconnection queue of 438 GW, so the rules governing how big loads connect, and how they behave in emergencies, affect a very large pipeline of proposed projects.</p>
<p>Not every stakeholder agrees the template is sound. The Texas Competitive Power Advocates and natural gas producer BKV filed arguments that the framework could discourage future co-location. PUCT staff contended those parties lacked standing under the governing statute, and the final order did not address their arguments on the merits. Their concern therefore remains an open policy question rather than a resolved one. The next data point will likely be the Amazon and Vistra application at Comanche Peak, a co-location next to nuclear generation rather than wind. Talley said that how ERCOT and the commission treat that arrangement “will be very telling.”</p>
<h2>Background</h2>
<p>Texas runs most of its electricity through ERCOT, a grid largely separate from the rest of the US, and it has become a leading destination for large AI data centers because of available land and generation. That demand has pushed lawmakers and regulators to write rules specifically for very large loads. SB 6, enacted in 2025, set requirements for such loads and gave ERCOT authority to disconnect data centers during grid emergencies.</p>
<p>Co-location, placing a data center directly beside a power plant, has attracted developers as a way to secure supply faster than a conventional grid connection allows. Regulators, however, have had to decide whether generation consumed on-site should still count toward the grid&#8217;s reliability during emergencies. The Crusoe and Ensign case is among the first to answer that question under SB 6.</p>
<section class="jain-sources" aria-label="Sources">
<h2>Sources</h2>
<p>Source: <a href="https://news.google.com/rss/articles/CBMitgFBVV95cUxPTGJYS0wza1BuY2xTYk0wclB3MWtPQ0U4aXktdzhGZDh6UjFVZE4wTlhXSWVacDNSRHdZRWcyWDN2ejVXbXlhd0hQdjhhdU13SXdzZ0ctcHlTdVJaODJaOXVXS2sxd1I0WWdGVklFYkdGdFJnRFA1M0V4LXJpb2I1dVU2MURSMEhLZl96OHN5RGhwVjRzX1Y0eldpSVpBSl9BM3g2N2hZUXBkM09BTGtZX1BvMkhQUQ?oc=5">Texas approves AI data center co-location next to wind farm, with curtailment caveats</a>. Utility Dive on the Public Utility Commission of Texas order approving a 260 MW co-located AI data center with emergency curtailment conditions.</p>
</section>
</div>
<aside class="jain-rail">
<section class="jain-gaps" aria-label="What the release does not say">
<p class="jain-gaps-kicker">⚠ What They Aren’t Saying</p>
<h2>What the Release Doesn&#8217;t Say</h2>
<ul>
<li><strong>Backup and ride-through plans:</strong> Crusoe and Ensign have not said whether they intend to install on-site resources capable of carrying the 260 MW load during a disconnection, or whether they will accept downtime. They also have not said whether they will commit to the voluntary 10-minute response.</li>
<li><strong>Customer, financing and timeline:</strong> The companies have not disclosed who will use the AI compute capacity, how the second facility is financed, or when it is expected to be energized.</li>
<li><strong>Next steps and precedent:</strong> Crusoe and Ensign have not said whether they will seek rehearing of the curtailment conditions. The commission has not addressed on the merits the concerns raised by the Texas Competitive Power Advocates and BKV about the framework&#8217;s effect on future co-location projects.</li>
</ul>
</section>
<section class="jain-faq">
<h2>Frequently Asked Questions</h2>
<h3>What did the Public Utility Commission of Texas approve?</h3>
<p>It approved a net metering arrangement for a 260 MW AI data center co-located with a 265.5 MW wind farm. The approval came with reliability conditions requiring rapid full-load curtailment during grid emergencies and barring paid demand response tied to the arrangement.</p>
<h3>Who is behind the project?</h3>
<p>Crusoe is the developer of the AI data center. Ensign is the large-load customer that plans to operate the site. The new facility is the second data center planned at the same wind farm location.</p>
<h3>What does co-location mean for a data center?</h3>
<p>Co-location here means building the data center directly beside a power plant so it can consume that plant&#8217;s output behind the meter, on the generator&#8217;s side of the grid connection, rather than drawing all of its electricity through the wider transmission network.</p>
<h3>How fast must the data center curtail its load?</h3>
<p>It must be able to curtail its full load within 30 minutes during grid emergencies, using physical breaker disconnection if necessary. ERCOT should give 60 minutes&#8217; notice when practicable, and the operator may voluntarily commit to a 10-minute response.</p>
<h3>Why did the developer object to the curtailment rule?</h3>
<p>Crusoe and Ensign argued that forcing the whole site offline was disproportionate and that additional curtailment was unnecessary given an earlier reliability condition on the co-located wind project. They noted combined site load of about 525 MW exceeds the 265.5 MW wind capacity.</p>
<h3>Why did the commission reject that argument?</h3>
<p>Commissioners concluded that letting the second 260 MW load stay online while the first was curtailed would undermine the goal of keeping generation available to the grid during emergencies, since that load could absorb nearly all of the wind farm&#8217;s output.</p>
<h3>What is SB 6?</h3>
<p>SB 6 is a Texas law enacted in 2025 that set new rules for large electricity loads in ERCOT&#8217;s territory, including giving the grid operator authority to disconnect data centers during grid emergencies. This case is one of the first major tests of the law.</p>
<h3>What is ERCOT?</h3>
<p>The Electric Reliability Council of Texas operates the grid serving most of the state. It manages real-time supply and demand and, under SB 6, can require large loads such as data centers to disconnect during grid emergencies.</p>
<h3>Why can&#x27;t the data center earn demand response payments?</h3>
<p>The order bars the project from paid demand response programs tied to the arrangement. It treats emergency curtailment as a mandatory condition of co-locating, distinct from voluntary grid services that loads are normally paid to provide.</p>
<h3>Does this ruling end co-location in Texas?</h3>
<p>No. The arrangement was approved and can proceed. GridTracker co-founder Chris Talley said it is not a death blow, but argued the design now essentially requires full backup capacity, which he described as an untested assumption.</p>
<h3>Will other data center projects face the same rules?</h3>
<p>Likely, though not automatically. Commissioners largely adopted ERCOT&#8217;s proposed conditions rather than a project-specific exception, so the order is widely viewed as a template for future behind-the-meter loads in Texas.</p>
<h3>What is the Comanche Peak co-location case?</h3>
<p>Amazon and Vistra have a pending application to build a data center campus beside the Comanche Peak nuclear plant southwest of Fort Worth. It is seen as the next test of how Texas regulators treat large co-located loads.</p>
<h3>Who else opposed the framework?</h3>
<p>The Texas Competitive Power Advocates and natural gas producer BKV argued it could discourage future co-location. PUCT staff said they lacked standing, and the final order did not address their arguments.</p>
<h3>What does this mean for AI data center developers in Texas?</h3>
<p>Developers should plan for full-load emergency disconnection and should not count on demand response revenue from the same flexibility. Keeping compute online through emergencies likely means on-site backup resources, at the developer&#8217;s cost.</p>
</section>
</aside>
</div>
<p><script type="application/ld+json">{"@context": "https://schema.org", "@graph": [{"@type": "NewsArticle", "headline": "Texas's 260 MW Wind Ruling Shows AI Co-Location Is a Grid Deal, Not an Exit", "description": "Texas regulators approved Crusoe's 260 MW AI data center beside a wind farm, but it must cut its full load within 30 minutes in grid emergencies. The ruling signals that co-location in ERCOT secures power supply, not freedom from grid reliability duties.", "image": ["https://www.jain.com/assets/img/b15a1e90-texas-ai-data-center-wind-farm-co-location-ercot-curtailment.webp"], "author": {"@type": "Organization", "name": "jain.com Editorial"}, "datePublished": "2026-09-25T00:41:12.105167+00:00"}, {"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What did the Public Utility Commission of Texas approve?", "acceptedAnswer": {"@type": "Answer", "text": "It approved a net metering arrangement for a 260 MW AI data center co-located with a 265.5 MW wind farm. The approval came with reliability conditions requiring rapid full-load curtailment during grid emergencies and barring paid demand response tied to the arrangement."}}, {"@type": "Question", "name": "Who is behind the project?", "acceptedAnswer": {"@type": "Answer", "text": "Crusoe is the developer of the AI data center. Ensign is the large-load customer that plans to operate the site. The new facility is the second data center planned at the same wind farm location."}}, {"@type": "Question", "name": "What does co-location mean for a data center?", "acceptedAnswer": {"@type": "Answer", "text": "Co-location here means building the data center directly beside a power plant so it can consume that plant's output behind the meter, on the generator's side of the grid connection, rather than drawing all of its electricity through the wider transmission network."}}, {"@type": "Question", "name": "How fast must the data center curtail its load?", "acceptedAnswer": {"@type": "Answer", "text": "It must be able to curtail its full load within 30 minutes during grid emergencies, using physical breaker disconnection if necessary. ERCOT should give 60 minutes' notice when practicable, and the operator may voluntarily commit to a 10-minute response."}}, {"@type": "Question", "name": "Why did the developer object to the curtailment rule?", "acceptedAnswer": {"@type": "Answer", "text": "Crusoe and Ensign argued that forcing the whole site offline was disproportionate and that additional curtailment was unnecessary given an earlier reliability condition on the co-located wind project. They noted combined site load of about 525 MW exceeds the 265.5 MW wind capacity."}}, {"@type": "Question", "name": "Why did the commission reject that argument?", "acceptedAnswer": {"@type": "Answer", "text": "Commissioners concluded that letting the second 260 MW load stay online while the first was curtailed would undermine the goal of keeping generation available to the grid during emergencies, since that load could absorb nearly all of the wind farm's output."}}, {"@type": "Question", "name": "What is SB 6?", "acceptedAnswer": {"@type": "Answer", "text": "SB 6 is a Texas law enacted in 2025 that set new rules for large electricity loads in ERCOT's territory, including giving the grid operator authority to disconnect data centers during grid emergencies. This case is one of the first major tests of the law."}}, {"@type": "Question", "name": "What is ERCOT?", "acceptedAnswer": {"@type": "Answer", "text": "The Electric Reliability Council of Texas operates the grid serving most of the state. It manages real-time supply and demand and, under SB 6, can require large loads such as data centers to disconnect during grid emergencies."}}, {"@type": "Question", "name": "Why can't the data center earn demand response payments?", "acceptedAnswer": {"@type": "Answer", "text": "The order bars the project from paid demand response programs tied to the arrangement. It treats emergency curtailment as a mandatory condition of co-locating, distinct from voluntary grid services that loads are normally paid to provide."}}, {"@type": "Question", "name": "Does this ruling end co-location in Texas?", "acceptedAnswer": {"@type": "Answer", "text": "No. The arrangement was approved and can proceed. GridTracker co-founder Chris Talley said it is not a death blow, but argued the design now essentially requires full backup capacity, which he described as an untested assumption."}}, {"@type": "Question", "name": "Will other data center projects face the same rules?", "acceptedAnswer": {"@type": "Answer", "text": "Likely, though not automatically. Commissioners largely adopted ERCOT's proposed conditions rather than a project-specific exception, so the order is widely viewed as a template for future behind-the-meter loads in Texas."}}, {"@type": "Question", "name": "What is the Comanche Peak co-location case?", "acceptedAnswer": {"@type": "Answer", "text": "Amazon and Vistra have a pending application to build a data center campus beside the Comanche Peak nuclear plant southwest of Fort Worth. It is seen as the next test of how Texas regulators treat large co-located loads."}}, {"@type": "Question", "name": "Who else opposed the framework?", "acceptedAnswer": {"@type": "Answer", "text": "The Texas Competitive Power Advocates and natural gas producer BKV argued it could discourage future co-location. PUCT staff said they lacked standing, and the final order did not address their arguments."}}, {"@type": "Question", "name": "What does this mean for AI data center developers in Texas?", "acceptedAnswer": {"@type": "Answer", "text": "Developers should plan for full-load emergency disconnection and should not count on demand response revenue from the same flexibility. Keeping compute online through emergencies likely means on-site backup resources, at the developer's cost."}}]}]}</script></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
