<?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>North Carolina &#8211; Jain.com</title>
	<atom:link href="/tag/north-carolina/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Data centers, connectivity, and security — news and analysis</description>
	<lastBuildDate>Tue, 05 May 2026 16:00:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>/wp-content/uploads/2026/08/jain-com-icon-512-150x150.png</url>
	<title>North Carolina &#8211; Jain.com</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>North Carolina Bill Would Make Hyperscalers Pay Their Grid Costs</title>
		<link>/north-carolina-ai-infrastructure-bill-hyperscale-grid-costs/</link>
		
		<dc:creator><![CDATA[Deepak Jain]]></dc:creator>
		<pubDate>Tue, 05 May 2026 16:00:00 +0000</pubDate>
				<category><![CDATA[Power Infrastructure]]></category>
		<category><![CDATA[AI infrastructure]]></category>
		<category><![CDATA[data centers]]></category>
		<category><![CDATA[Electricity Rates]]></category>
		<category><![CDATA[energy policy]]></category>
		<category><![CDATA[grid capacity]]></category>
		<category><![CDATA[hyperscale]]></category>
		<category><![CDATA[North Carolina]]></category>
		<category><![CDATA[regulation]]></category>
		<guid isPermaLink="false">/north-carolina-ai-infrastructure-bill-hyperscale-grid-costs/</guid>

					<description><![CDATA[North Carolina lawmakers have proposed an AI infrastructure bill that would require hyperscale data centers to cover the grid costs they create. It joins Oregon's POWER Act and a New Jersey tariff bill as states write large-load cost allocation into statute, reshaping how operators site capacity.]]></description>
										<content:encoded><![CDATA[<div class="jain-post-grid">
<div class="jain-post-main">
<p>North Carolina legislators have introduced an AI infrastructure bill that would push hyperscale data centers to shoulder the electricity system costs their load creates, according to a 5 May 2026 report from <em>Data Center Knowledge</em>. The measure places North Carolina among a growing set of states moving &#8220;large-load&#8221; cost allocation out of utility commission dockets and into statute.</p>
<p>The available source is headline-level: it establishes that such a bill has been proposed and that hyperscale cost recovery is its target. It does not, in the material we reviewed, supply a bill number, sponsor list, megawatt threshold, contract terms, or a legislative calendar. This analysis therefore treats the policy direction as reported and the mechanics as open questions.</p>
<h2>Executive Summary</h2>
<p>The proposal addresses a problem that has moved quickly from technical to political: when a single data center campus requests hundreds of megawatts, the utility must build transmission lines, substations and generation to serve it. Those assets are paid for over decades through rates charged to every customer. If the campus is delayed, downsized or shut down, the bill does not disappear — it shifts to households and existing businesses. &#8220;Cost causation,&#8221; the regulatory principle that the party creating a cost should bear it, is the framework North Carolina is reportedly trying to codify.</p>
<p>This matters because North Carolina is not a marginal market. Its low industrial power prices, data center sales-tax exemption and existing hyperscale footprint have made it a repeat destination for large campuses. A statutory cost-allocation regime in a top-tier state signals that the era of negotiating each large load quietly with a utility, case by case, is narrowing.</p>
<p>For operators, the practical question is not whether they will pay — large customers already pay substantial demand charges — but how much risk they must pre-commit to and for how long. Minimum-take obligations, multi-year contract terms, collateral and exit fees are the levers that determine whether a state&#8217;s rules are a manageable cost of doing business or a reason to site the next campus elsewhere.</p>
<h2>Why Cost Causation Became a Statehouse Fight</h2>
<p>Regulated electric utilities are, in effect, planning institutions. They forecast demand years out, build generation and wires against that forecast, and recover the capital through rates approved by a state commission. The model works when load grows predictably. AI-era data center requests break that assumption in two directions at once: individual projects are enormous relative to a utility&#8217;s existing peak, and the interconnection queue is full of speculative requests that may never be built.</p>
<p>Utilities have responded with &#8220;phantom load&#8221; screening and large-load tariffs designed to separate serious projects from optionality-shopping. But those instruments are negotiated inside regulatory proceedings that most voters never see. When residential bills rise for any reason — fuel costs, storm recovery, capacity additions — data centers become the visible explanation, whether or not they are the arithmetic one. Legislation is what happens when that political pressure outruns the docket process.</p>
<p>The industry has a serious counterargument that deserves to be stated plainly: large, flat, high-load-factor customers can improve system utilization and spread fixed costs across more kilowatt-hours, which can put downward pressure on everyone&#8217;s rates. That is genuinely true when the load materializes and stays. The entire policy question is what happens when it does not — and who is holding the asset.</p>
<h2>Three States, Three Instruments</h2>
<p>Oregon&#8217;s POWER Act is the clearest existing template. It directs that very large energy users — data centers and cryptocurrency operations above a defined megawatt threshold — be placed in their own customer class with dedicated long-term contract terms, so that the costs of serving them are recovered from them rather than blended into general rates. The mechanism is structural: create a separate class, then let the commission set terms for that class.</p>
<p>New Jersey&#8217;s approach has centered on a tariff mandate — instructing regulators to establish a distinct rate schedule for high-density load, which leaves more design discretion with the board while fixing the obligation in law. North Carolina&#8217;s reported bill sits somewhere in this family, but the reporting available does not specify which instrument it uses. The distinction is not academic. A separate-class statute changes who a customer legally is; a tariff-directive statute changes what a customer pays under rules regulators still write.</p>
<p>Comparing the three exposes the real design variables: the megawatt trigger, whether existing and already-announced projects are grandfathered, the minimum-take percentage, contract duration, credit and collateral requirements, and the exit fee if a customer walks. Two states can adopt the same headline principle and produce very different investment climates depending on where those dials are set.</p>
<h2>Who Gains, Who Pays, and Who Hedges</h2>
<p>The clearest winners from codified cost allocation are ratepayer advocates and, less obviously, incumbent operators with signed interconnection agreements. Grandfathering provisions — common in this legislation — convert an existing position into a durable cost advantage over a new entrant facing minimum-take obligations and collateral posting. Rules that raise the price of entry protect whoever is already inside.</p>
<p>The clearest losers are speculative developers holding land and queue positions without a committed tenant. A statutory minimum-take regime prices optionality directly, which is arguably the policy&#8217;s point. Utilities occupy an ambiguous position: they gain revenue certainty and reduced stranded-asset exposure, but lose flexibility to structure bespoke deals for anchor customers they want to attract.</p>
<p>The predictable hedge is to go around the tariff entirely. Behind-the-meter generation, on-site gas, fuel cells and co-located generation reduce a campus&#8217;s exposure to regulated rates — and correspondingly reduce its contribution to the shared system it still relies on for backup and reliability. Whether North Carolina&#8217;s bill addresses standby service and backup rates for self-supplied campuses is one of the more consequential details not visible in the source reporting.</p>
<h2>The Case For and Against Legislating It</h2>
<p>The argument against writing this into statute is real. Utility commissions have staff, evidentiary records and the ability to adjust terms as load forecasts change; legislatures have none of that and revise slowly. A megawatt threshold that is sensible in 2026 may be poorly calibrated by 2030, and statutory language is harder to fix than a tariff sheet.</p>
<p>The argument for it is equally real. Commission proceedings can be captured by the sophistication gap between utilities, hyperscalers and thinly-resourced consumer advocates, and they produce outcomes that are legally reversible in the next rate case. Legislation delivers durability, which is precisely what a developer underwriting a fifteen-year asset wants — even a developer who dislikes the specific terms.</p>
<p>The measured read is that predictability may matter more to capital than stringency. Operators can price a known minimum-take obligation. What they cannot price is a jurisdiction where the rules are relitigated every eighteen months. If North Carolina&#8217;s bill produces clear, stable terms, it may prove less damaging to the state&#8217;s competitiveness than opponents suggest and less protective of ratepayers than supporters claim.</p>
<h2>Background</h2>
<p>North Carolina has hosted large data center investment since the late 2000s, when major cloud and platform companies built campuses in the state&#8217;s western foothills, drawn by inexpensive power, cool-season climate and a state sales-and-use tax exemption for qualifying facilities. That footprint has since expanded toward the Charlotte region and the Research Triangle. Electricity service across most of the state is provided by vertically integrated regulated utilities whose rates and resource plans are approved by the North Carolina Utilities Commission.</p>
<p>The AI buildout changed the scale of the ask. Individual campus requests now arrive measured in hundreds of megawatts, comparable to serving a mid-sized city, and often on timelines far shorter than the multi-year cycles required to build generation and transmission. Utilities in several states have responded with dedicated large-load tariffs featuring long contract terms and minimum-take provisions. Oregon and New Jersey moved the question into legislation, and North Carolina&#8217;s proposed bill would extend that pattern to one of the Southeast&#8217;s most active data center markets.</p>
<p>Source: <a href="https://news.google.com/rss/articles/CBMiwgFBVV95cUxPSDREZDJhZGN2RlZsc1FybFYySUpPZmozbi1wY2dXZld1Qlc2em5IV0owdEYxYXZZMGxKMTVKeGkzM2lsVEZFd0Y0aC1KNzZvMWVUT04xOEt4Y0M0LTdjMEI3MWg4U01ZeHMzM0IyMkIyQ0xJbXJFUnktMEV6M1ZsVnJNU1RYWmhhcURvMGlnSlVqRS1BQkxOMGx2Y1ZrNVRZZThTQlhIdndMU0g1WmhjNHpHbEg1TzBVSzRGSGJqa253UQ?oc=5">North Carolina Targets Hyperscale Costs with Proposed AI Infrastructure Bill</a> — Data Center Knowledge, 5 May 2026, reporting that North Carolina legislators have proposed requiring hyperscale data centers to bear the grid costs their load creates.</p>
</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>
<p>The source reporting available is a headline-level item, and it leaves nearly all of the operative detail unresolved. The most material unanswered questions are structural: what megawatt threshold triggers the requirements, whether the bill creates a separate customer class or directs a tariff, and whether &#8220;AI infrastructure&#8221; is defined by load characteristics or by workload type — a distinction that determines whether conventional colocation and enterprise facilities are swept in.</p>
<ul>
<li><strong>Applicability and grandfathering:</strong> Does the bill reach existing campuses, projects with signed interconnection agreements, or only new requests after an effective date?</li>
<li><strong>Contract mechanics:</strong> Minimum-take percentage, contract term, credit and collateral requirements, and exit-fee formula — the terms that actually determine cost.</li>
<li><strong>Behind-the-meter treatment:</strong> How self-supplied or co-located generation is handled, and what standby and backup service such campuses would pay.</li>
<li><strong>Regulatory interaction:</strong> How the bill would interact with large-load tariff filings and resource planning already before the North Carolina Utilities Commission, and whether it supersedes or supplements them.</li>
<li><strong>Politics and process:</strong> Sponsors, committee assignment, session calendar, and the stated positions of the state&#8217;s utilities, hyperscale operators, industrial customers and consumer advocates — none of which are established by the source.</li>
</ul>
<p>Also unaddressed: any quantified estimate of how much cost is currently being socialized to general ratepayers in North Carolina. Without that figure, neither the case for the bill nor the case against it can be evaluated on its merits.</p>
</section>
<section class="jain-faq">
<h2>Frequently Asked Questions</h2>
<h3>What does the proposed North Carolina AI infrastructure bill do?</h3>
<p>As reported on 5 May 2026, it would require hyperscale data centers to cover the electricity grid costs their load creates, rather than having those costs recovered from the general body of ratepayers. The detailed mechanics were not disclosed in the available source reporting.</p>
<h3>What does &quot;large-load cost allocation&quot; actually mean?</h3>
<p>It is the practice of assigning the cost of new generation, transmission and substation capacity to the very large customer that made it necessary. The underlying regulatory principle is cost causation: whoever causes a cost should pay it, instead of spreading it across all customers.</p>
<h3>Why are states legislating this now instead of leaving it to regulators?</h3>
<p>AI-driven data center requests are large enough to move a utility&#8217;s entire load forecast, and rising residential bills have made the issue politically visible. Legislation moves the decision out of technical commission dockets, where consumer advocates are often outmatched, and into statute.</p>
<h3>What is Oregon&#x27;s POWER Act?</h3>
<p>It is Oregon legislation that places very large energy users, including data centers and cryptocurrency operations above a defined megawatt threshold, into a separate customer class with dedicated long-term contract terms so their service costs are recovered from them rather than blended into general rates.</p>
<h3>How does New Jersey&#x27;s approach differ from Oregon&#x27;s?</h3>
<p>New Jersey&#8217;s effort has centered on directing regulators to create a distinct tariff for high-density load, which leaves rate design discretion with the board. Oregon&#8217;s is structural, redefining what class of customer a large load belongs to. Both fix the obligation in law but at different levels of detail.</p>
<h3>Does North Carolina&#x27;s bill follow the Oregon or New Jersey model?</h3>
<p>The available reporting does not say. Determining whether it creates a separate customer class or directs a tariff is one of the most consequential open questions, because the two instruments distribute discretion between the legislature and the utilities commission very differently.</p>
<h3>Why is North Carolina an important market for data centers?</h3>
<p>The state combines relatively low industrial electricity prices, a sales-and-use tax exemption for qualifying data centers, and an established hyperscale footprint built out over more than fifteen years by major cloud and platform operators in the western and central parts of the state.</p>
<h3>Do data centers not already pay for the power they use?</h3>
<p>They do, through energy and demand charges that are typically substantial. The dispute is narrower: it concerns who bears the risk of capital built specifically to serve a project that is later delayed, downsized or cancelled, leaving assets whose costs still must be recovered.</p>
<h3>What is a stranded asset in this context?</h3>
<p>It is infrastructure — a substation, transmission line or generating unit — built to serve a customer who does not ultimately take the load. The utility is still entitled to recover its investment, so the cost migrates to remaining customers unless contract terms prevent it.</p>
<h3>What is a minimum-take obligation?</h3>
<p>It is a contract term requiring a large customer to pay for a set share of contracted capacity whether or not it uses that power, usually for a fixed number of years. It converts a speculative interconnection request into a financial commitment the utility can plan against.</p>
<h3>Could this legislation push data center investment to other states?</h3>
<p>It could at the margin, but siting decisions weigh power availability, interconnection timelines, fiber, land, water and tax treatment together. Clear and stable rules can partly offset higher costs, since developers underwriting long-lived assets place real value on regulatory predictability.</p>
<h3>Who benefits most if the bill passes?</h3>
<p>Ratepayer advocates gain the most direct protection, and existing operators with signed agreements may benefit if grandfathering shields them from terms applied to newcomers. Speculative developers holding queue positions without committed tenants face the highest cost increase.</p>
<h3>How might hyperscalers respond to stricter large-load rules?</h3>
<p>The common hedge is to reduce exposure to regulated rates through behind-the-meter generation, on-site gas or fuel cells, or co-located generation. That shifts the policy question to how such campuses are charged for standby and backup service they still draw from the grid.</p>
<h3>What should investors watch for next in this bill?</h3>
<p>The megawatt trigger, whether existing projects are grandfathered, the minimum-take percentage and contract length, the exit-fee formula, and committee action within the legislative session. Those variables, not the bill&#8217;s stated principle, determine its economic effect.</p>
<h3>Is there evidence that North Carolina ratepayers are currently subsidizing data centers?</h3>
<p>The source reporting does not provide a quantified estimate for the state. Absent that figure, the magnitude of any cross-subsidy remains unestablished, which is a genuine limitation on evaluating both the case for the bill and the case against it.</p>
<h3>What does this trend mean for buyers procuring capacity?</h3>
<p>Contracts signed in states with codified cost allocation are likely to carry longer terms, firmer volume commitments and collateral requirements. Buyers should model exit costs explicitly and confirm how a provider&#8217;s rate exposure is passed through in colocation agreements.</p>
</section>
</aside>
</div>
<p><script type="application/ld+json">{"@context": "https://schema.org", "@graph": [{"@type": "NewsArticle", "headline": "North Carolina Bill Would Make Hyperscalers Pay Their Grid Costs", "description": "North Carolina lawmakers have proposed an AI infrastructure bill that would require hyperscale data centers to cover the grid costs they create. It joins Oregon's POWER Act and a New Jersey tariff bill as states write large-load cost allocation into statute, reshaping how operators site capacity.", "image": ["/wp-content/uploads/2026/08/north-carolina-ai-infrastructure-bill-hyperscale-grid-costs.png"], "author": {"@type": "Organization", "name": "jain.com Editorial"}, "datePublished": "2026-08-29T23:31:00.663720+00:00"}, {"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What does the proposed North Carolina AI infrastructure bill do?", "acceptedAnswer": {"@type": "Answer", "text": "As reported on 5 May 2026, it would require hyperscale data centers to cover the electricity grid costs their load creates, rather than having those costs recovered from the general body of ratepayers. The detailed mechanics were not disclosed in the available source reporting."}}, {"@type": "Question", "name": "What does \"large-load cost allocation\" actually mean?", "acceptedAnswer": {"@type": "Answer", "text": "It is the practice of assigning the cost of new generation, transmission and substation capacity to the very large customer that made it necessary. The underlying regulatory principle is cost causation: whoever causes a cost should pay it, instead of spreading it across all customers."}}, {"@type": "Question", "name": "Why are states legislating this now instead of leaving it to regulators?", "acceptedAnswer": {"@type": "Answer", "text": "AI-driven data center requests are large enough to move a utility's entire load forecast, and rising residential bills have made the issue politically visible. Legislation moves the decision out of technical commission dockets, where consumer advocates are often outmatched, and into statute."}}, {"@type": "Question", "name": "What is Oregon's POWER Act?", "acceptedAnswer": {"@type": "Answer", "text": "It is Oregon legislation that places very large energy users, including data centers and cryptocurrency operations above a defined megawatt threshold, into a separate customer class with dedicated long-term contract terms so their service costs are recovered from them rather than blended into general rates."}}, {"@type": "Question", "name": "How does New Jersey's approach differ from Oregon's?", "acceptedAnswer": {"@type": "Answer", "text": "New Jersey's effort has centered on directing regulators to create a distinct tariff for high-density load, which leaves rate design discretion with the board. Oregon's is structural, redefining what class of customer a large load belongs to. Both fix the obligation in law but at different levels of detail."}}, {"@type": "Question", "name": "Does North Carolina's bill follow the Oregon or New Jersey model?", "acceptedAnswer": {"@type": "Answer", "text": "The available reporting does not say. Determining whether it creates a separate customer class or directs a tariff is one of the most consequential open questions, because the two instruments distribute discretion between the legislature and the utilities commission very differently."}}, {"@type": "Question", "name": "Why is North Carolina an important market for data centers?", "acceptedAnswer": {"@type": "Answer", "text": "The state combines relatively low industrial electricity prices, a sales-and-use tax exemption for qualifying data centers, and an established hyperscale footprint built out over more than fifteen years by major cloud and platform operators in the western and central parts of the state."}}, {"@type": "Question", "name": "Do data centers not already pay for the power they use?", "acceptedAnswer": {"@type": "Answer", "text": "They do, through energy and demand charges that are typically substantial. The dispute is narrower: it concerns who bears the risk of capital built specifically to serve a project that is later delayed, downsized or cancelled, leaving assets whose costs still must be recovered."}}, {"@type": "Question", "name": "What is a stranded asset in this context?", "acceptedAnswer": {"@type": "Answer", "text": "It is infrastructure \u2014 a substation, transmission line or generating unit \u2014 built to serve a customer who does not ultimately take the load. The utility is still entitled to recover its investment, so the cost migrates to remaining customers unless contract terms prevent it."}}, {"@type": "Question", "name": "What is a minimum-take obligation?", "acceptedAnswer": {"@type": "Answer", "text": "It is a contract term requiring a large customer to pay for a set share of contracted capacity whether or not it uses that power, usually for a fixed number of years. It converts a speculative interconnection request into a financial commitment the utility can plan against."}}, {"@type": "Question", "name": "Could this legislation push data center investment to other states?", "acceptedAnswer": {"@type": "Answer", "text": "It could at the margin, but siting decisions weigh power availability, interconnection timelines, fiber, land, water and tax treatment together. Clear and stable rules can partly offset higher costs, since developers underwriting long-lived assets place real value on regulatory predictability."}}, {"@type": "Question", "name": "Who benefits most if the bill passes?", "acceptedAnswer": {"@type": "Answer", "text": "Ratepayer advocates gain the most direct protection, and existing operators with signed agreements may benefit if grandfathering shields them from terms applied to newcomers. Speculative developers holding queue positions without committed tenants face the highest cost increase."}}, {"@type": "Question", "name": "How might hyperscalers respond to stricter large-load rules?", "acceptedAnswer": {"@type": "Answer", "text": "The common hedge is to reduce exposure to regulated rates through behind-the-meter generation, on-site gas or fuel cells, or co-located generation. That shifts the policy question to how such campuses are charged for standby and backup service they still draw from the grid."}}, {"@type": "Question", "name": "What should investors watch for next in this bill?", "acceptedAnswer": {"@type": "Answer", "text": "The megawatt trigger, whether existing projects are grandfathered, the minimum-take percentage and contract length, the exit-fee formula, and committee action within the legislative session. Those variables, not the bill's stated principle, determine its economic effect."}}, {"@type": "Question", "name": "Is there evidence that North Carolina ratepayers are currently subsidizing data centers?", "acceptedAnswer": {"@type": "Answer", "text": "The source reporting does not provide a quantified estimate for the state. Absent that figure, the magnitude of any cross-subsidy remains unestablished, which is a genuine limitation on evaluating both the case for the bill and the case against it."}}, {"@type": "Question", "name": "What does this trend mean for buyers procuring capacity?", "acceptedAnswer": {"@type": "Answer", "text": "Contracts signed in states with codified cost allocation are likely to carry longer terms, firmer volume commitments and collateral requirements. Buyers should model exit costs explicitly and confirm how a provider's rate exposure is passed through in colocation agreements."}}]}]}</script></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
