jain.com — data centers, connectivity and security, analyzed daily

Tag: Nevada

  • NV Energy’s 22 GW Queue Shows Why Data Center Power Priority Is Worth Suing Over

    NV Energy’s 22 GW Queue Shows Why Data Center Power Priority Is Worth Suing Over

    TL;DR · 30-second read

    The Short Version

    Nevada’s main electric company, NV Energy, is suing Tract, a company that builds huge campuses for data centers. Data centers are the warehouse-sized buildings full of computers that run websites, apps and artificial intelligence.

    The fight is over who gets electricity first, how much, and who pays for new power plants and lines. Requests for new power, driven largely by data centers, already add up to more than twice what the utility’s whole system uses on its busiest day.

    The utility says households could get stuck with the bill. Tract says it has promised nearly $1 billion toward the utility’s equipment and is paying its fair share.

    NV Energy, Nevada’s primary electric utility, has sued data center developer Tract in Washoe County’s Second Judicial District Court, The Nevada Independent reported on July 28, 2026. The complaint was filed Friday, July 24, and much of it is redacted because it was filed under seal. It alleges that Tract started private arbitration over when and how much power the utility must provide to its Peru Shelf and South Valley projects at the Tahoe Reno Industrial Center, and that this bypasses the Public Utilities Commission of Nevada (PUCN).

    NV Energy says Tract’s demands would shift infrastructure and energy costs onto existing customers. Tract says the complaint “seriously misstates the issues, the facts, and the contracts NV Energy signed.” It also says it has never sought subsidies, that it has committed nearly $1 billion to support NV Energy’s infrastructure, and that those contracts commit the dispute to arbitration.

    Executive Summary

    The suit pits Nevada’s dominant utility against one of the largest landholders in the state’s data center market. It turns on a question every fast-growing power market will eventually face: when a developer’s contract and a utility’s regulated resource plan collide, who decides the order in which new loads get electricity? NV Energy says only the PUCN can. Tract says the parties agreed to arbitrate.

    The backdrop explains the stakes. NV Energy’s latest integrated resource plan says it would need about 22 gigawatts (GW) just to serve existing requests for service, more than twice its current system peak, and it attributes that demand largely to data centers. When the grid is oversubscribed by that margin, a place in the queue has real economic value. Tract is already planning 362 megawatts (MW) of temporary gas and diesel generation because the grid cannot serve its projects right away.

    For ratepayers, the dispute is about who pays for growth. For developers and their financiers, it tests whether a large-load contract signed with a utility can be enforced on its own terms, or whether it stays subordinate to the regulator’s planning process.

    Twice the Peak: Why Queue Position Is Now the Prize

    NV Energy’s most recent integrated resource plan (IRP) says the utility would need roughly 22 GW of capacity just to meet requests for service already on file. That is more than twice the current system’s peak demand, and the utility says data centers are the main driver. A gigawatt is a thousand megawatts, and a single megawatt is a large industrial load on its own. When requests exceed what the grid can deliver by that much, the utility cannot connect everyone at once. The order of service then decides whether a campus opens on schedule, and it matters as much as the price of power.

    That order is exactly what this dispute concerns. According to the complaint, Tract’s arbitration seeks to settle when and how much power NV Energy should provide, how the utility generates and buys that power, and the priority of service among customers in its queue. Tract’s own contingency plan shows what a later place in line costs. NV Energy cannot serve the projects immediately, so Tract has proposed temporary natural gas and diesel plants: 144 MW for South Valley and 218 MW at Peru Ridge. These would be “behind-the-meter,” meaning on-site generation that feeds the campus directly rather than power drawn from the utility’s regulated grid.

    Three groups are affected. Other large customers in the queue are affected because capacity promised to one developer is capacity another does not get on that date. Existing ratepayers are affected if accelerated grid upgrades end up in general rates. Developers and their lenders are affected because a campus’s value depends heavily on when it can be energised. With that much at stake, both sides have escalated. Tract has gone to arbitration, and NV Energy has gone to court to stop the arbitration from deciding matters it says belong to the regulator.

    Contract Forum Versus Regulatory Forum

    NV Energy’s legal theory rests on jurisdiction. Generation, power purchasing and service priority are set through IRPs, which the utility must file with the PUCN and have approved at least every three years. The utility argues that an arbitrator cannot decide those questions outside that framework, especially while the Commission is weighing the same issues. That includes NV Energy’s proposal for a uniform large-load service agreement meant to standardise terms across data center customers. “Defendants cannot now short-circuit that regulatory process,” the filing says.

    Tract’s position rests on contract. It says the agreements NV Energy negotiated commit disputes to arbitration, and that it simply wants the utility “to live up to the commitments it made.” The agreements were executed under Rule 9, which governs how construction costs and responsibility are split between the utility and a new customer, weighing the project’s size, duration and risk. NV Energy says Rule 9 does not address the supply of electricity. The unresolved question is therefore whether the utility made supply or timing commitments in those contracts, and if it did, whether they can be enforced privately. With the agreements sealed, neither side’s reading can yet be checked publicly.

    The implications reach beyond Nevada. If construction-cost agreements can carry enforceable supply priority through arbitration, large-load contracts become a channel that runs parallel to resource planning. If they cannot, developers get less contractual certainty at the moment they are raising capital for multi-hundred-megawatt campuses. Either outcome carries costs for someone.

    Same Principle, Different Math

    Both parties invoke the same principle. “Customers that create new costs should cover new costs, and those costs should not be shifted,” said a person familiar with the matter. Tract says it “has committed to paying our fair share for infrastructure and generation needs” and never asked to be subsidised. The disagreement is not about whether growth should pay for itself. It is about what a fair share amounts to, and what the nearly $1 billion Tract cites actually buys in capacity, timing and priority.

    The growth figures explain why that math is contested now. NV Energy estimates it needs 52 percent more energy statewide than it forecast only two years ago. Data centers account for about 5 percent of its sales today, and the utility projects that share will reach 64 percent by 2046. On that trajectory, cost-allocation rules written now will govern who pays for most of the system’s future expansion. Questions that are traditionally settled in rate cases and resource plans are here being argued in court over the terms of a contract. That is one case, not yet a pattern, but it is a sign of how much weight these contracts now carry. The lawsuit also places the utility’s stated position near local concerns about data center electricity and water use, a shift in public posture for a utility that is simultaneously planning to serve that load.

    Land Is Not Power

    Tract has assembled more than 12,000 acres in Northern Nevada, including 1,060 acres in Lyon County that it says can support 1.6 GW of data center capacity. Land has not been the constraint, and grid access keeps proving to be one. Last year, Switch sued Tract to block certain developments on the same Peru Shelf parcels, arguing they would affect Switch’s ability to connect future projects to utilities. The court ruled in Tract’s favour. Two separate lawsuits over the same ground have now turned on access to power.

    For site selectors, investors and tenants, the practical lesson is that acreage, zoning and even signed construction agreements do not establish an energisation date. On-site gas and diesel generation is becoming part of the plan rather than an emergency fallback. That brings its own permitting, fuel and emissions questions, and it does not settle when the grid will take over.

    Background

    NV Energy is Nevada’s primary electric utility and a subsidiary of Berkshire Hathaway Energy. Like other regulated utilities, it plans new generation and power purchases through integrated resource plans filed with and approved by the PUCN at least every three years. It already has large-load agreements with multiple data centers. In its current plan it is asking regulators to approve a uniform service agreement for large-load customers, consistent with those existing contracts.

    Tract develops master-planned data center parks and has bought more than 12,000 acres across Northern Nevada. In 2024 it acquired 8,600 acres in Storey County between the Tahoe Reno Industrial Center (TRIC) and the Virginia City Highlands, bringing its holdings to 11,000 acres. It later added 1,060 acres in Lyon County just south of TRIC, which it says can support 1.6 GW of capacity. Last year Tract prevailed in a lawsuit brought by Switch, a longtime TRIC operator, over development of Tract’s Peru Shelf parcels.

    Sources

    Source: Nevada’s electric utility is suing a major data center company. Here’s why. (The Nevada Independent), on NV Energy’s lawsuit challenging Tract’s arbitration over power-supply agreements for two Storey County data center projects.

  • Nevada’s Cooling Tower Ban Moves Water Use Upstream

    Nevada’s Cooling Tower Ban Moves Water Use Upstream

    An independent analysis published on Substack on 13 May 2026 argues that Nevada’s restrictions on evaporative cooling towers at data centers do not eliminate the industry’s water consumption so much as relocate it. The piece, headlined “The $3 Billion Blind Spot,” estimates that roughly 100 million gallons of annual water use moves from data center sites to the thermoelectric power plants that supply the extra electricity air-cooled equipment requires.

    The item reached us as a syndicated Google News listing with the headline and a truncated summary; the full text and its underlying calculations were not available for review. The figures below are therefore reported as claims from a single, unverified source, and the analysis that follows tests the logic rather than endorsing the arithmetic.

    Executive Summary

    The claim is structural rather than scandalous, and that is what makes it worth taking seriously. Cooling a data center by evaporating water is thermodynamically cheap: the phase change from liquid to vapour carries away a great deal of heat for very little electricity. Remove that option, as a cooling tower ban does, and the heat still has to go somewhere. It goes into air-cooled chillers and dry coolers, which use no water on site but draw materially more power, particularly in desert summers when ambient air is hottest and the equipment is least efficient.

    That extra power is generated somewhere. If it comes from gas, coal or nuclear plants using recirculating cooling, those plants evaporate water of their own. The water has not disappeared; it has crossed a jurisdictional and accounting boundary. On the site’s books, water use falls toward zero. On a whole-system basis, it may not.

    Whether the net effect is good or bad for Nevada is a separate question from whether the accounting is complete, and the two are routinely conflated by both sides. Moving consumption out of a stressed groundwater basin into a different basin, or onto a grid increasingly served by solar and wind that consume almost no water, can be a genuine improvement even if the headline “zero water” figure overstates it. The problem is that current disclosure practice makes it nearly impossible to tell which is happening.

    The Trade Is Water for Electricity, and It Is Real

    Every cooling design is a choice about which resource to spend. An evaporative cooling tower sprays warm water over fill material and lets a fraction evaporate; the vapour leaves with the heat, and the site tops up the loss from the municipal supply or a well. A dry or air-cooled system rejects the same heat directly to the atmosphere using fans and refrigeration, consuming no water but more kilowatt-hours. In a hot, arid climate the penalty is largest exactly when demand peaks, because the temperature difference the equipment relies on is smallest on a 40°C afternoon.

    Industry has a shorthand for the water side of this: Water Usage Effectiveness, or WUE, measured in litres of water per kilowatt-hour of IT load. It is a site metric. It counts what comes through the meter at the fence line. It does not count the water evaporated at a power station a hundred miles away to make the electricity that ran the fans, and it was never designed to. That is a reasonable engineering convention, not a conspiracy — but a metric built for one purpose becomes misleading the moment it is used as a sustainability claim in a public filing or a permit hearing.

    The upstream figure is not fixed, and this is where the analysis’s headline number needs interrogation. Thermoelectric water intensity varies by an order of magnitude across generation types and cooling designs: once-through plants withdraw enormous volumes but return most of it, recirculating plants withdraw far less but evaporate most of what they take, and solar photovoltaic and wind consume essentially nothing beyond occasional panel washing. A 100 million gallon estimate is really a statement about an assumed grid mix, and reasonable analysts can differ on whether to use the average mix or the marginal generator that actually responds to new load.

    Accounting Boundaries Decide the Answer Before the Arithmetic Starts

    Carbon reporting solved a version of this problem years ago by splitting emissions into Scope 1 (direct), Scope 2 (purchased energy) and Scope 3 (everything else in the value chain). Water reporting has no equivalent convention in general use. There is no widely adopted “Scope 2 water” line item, so the electricity-embedded water footprint of a data center is, in most public disclosures, simply absent — not understated, absent.

    Two further distinctions do a lot of quiet work in arguments like this one. The first is withdrawal versus consumption: water taken from a river and returned warmer is not the same as water evaporated and gone from the basin, and figures that mix the two can inflate or deflate a result dramatically. The second is location. A gallon evaporated from an over-allocated desert aquifer and a gallon evaporated beside a well-supplied river are equivalent on a spreadsheet and completely different in hydrological reality. Water-stress-weighted accounting exists to handle this, but it is not what most headline totals use.

    Applied evenly, this cuts both ways. It undercuts an operator advertising an air-cooled campus as “water-free” when the phrase describes only the fence line. It equally undercuts a critic who books upstream gallons at full weight without asking whether that water leaves a stressed basin, whether the marginal generator is a gas plant or a solar farm, and whether the plant in question uses evaporative cooling at all.

    Who Gains, Who Absorbs the Cost

    The clearest winners are local water authorities and the residents they answer to. A ban on evaporative cooling gives a regulator a bright-line, enforceable rule that removes a visible, meterable draw from a constrained supply, and it does so without having to adjudicate every project’s efficiency claims. Whatever its system-wide merits, as local water policy it is administratively coherent.

    Developers absorb a cost that is real but survivable. Air-cooled plant is typically more capital-intensive per megawatt of rejected heat, occupies more space, and raises Power Usage Effectiveness — the ratio of total facility power to IT power — which in turn raises operating cost and increases the megawatts a campus must contract for. For an operator negotiating an interconnection queue position in a constrained market, that last point may matter more than the electricity bill. Rising energy demand also strengthens the case for on-site or contracted generation, which is where the water question becomes the operator’s own again rather than an anonymous grid externality.

    The party with the least voice is the community near the generating plant, which may sit in an entirely different county or state and has no standing in the data center’s permitting process. That asymmetry — decision made in one basin, consequence landed in another — is the substantive point the analysis raises, and it stands independently of whether the specific 100 million gallon estimate survives scrutiny.

    Reading the Claim Fairly

    A single Substack post working from public data is a legitimate contribution; independent analysis has repeatedly surfaced infrastructure issues before trade coverage did, and dismissing it on the basis of the venue would be lazy. But the same standard applied to a vendor sustainability report applies here: the estimate is only as good as its disclosed method, and we could not see the method.

    The “$3 billion” in the headline is the weakest element on the available evidence. The figure is not defined in the material we can see — it could denote capital investment in affected facilities, the economic value at stake, an avoided-cost estimate, or something else entirely. Large round numbers in headlines travel further than the caveats attached to them, and a reader encountering this claim second-hand is likely to acquire a precise-sounding figure with no idea what it measures.

    The responsible position, at this stage, is that the mechanism is sound and well understood, the direction of the effect is almost certainly correct, and the magnitudes are unverified. That is enough to justify better disclosure. It is not yet enough to justify a conclusion about whether Nevada’s policy makes the state’s water situation better or worse.

    Background

    Nevada sits at the sharp end of two trends at once. It depends heavily on Colorado River water through Lake Mead, where sustained drought and over-allocation have made every new consumptive use politically visible, and Southern Nevada has spent decades building one of the most aggressive urban water conservation programmes in the United States. At the same time, cheap land, favourable tax treatment and proximity to California demand have made the state a significant data center market, with large campuses clustered in Northern Nevada industrial parks and in the Las Vegas area.

    The collision was predictable. As AI workloads pushed rack densities and total facility power upward through the mid-2020s, cooling water became a permitting flashpoint in arid states generally, not only Nevada. Restricting evaporative cooling is one of the more direct policy levers available to a water authority. Whether it reduces total water consumption or mainly relocates it is the question this analysis raises, and it is a question the industry’s current reporting conventions are not equipped to answer.

    Source: The $3 Billion Blind Spot: How Nevada’s Cooling Tower Ban Is Shifting 100 Million Gallons of Hidden Water Consumption to Power Plants — an independent Substack analysis, published 13 May 2026, arguing that restricting on-site evaporative cooling relocates data center water consumption upstream to thermoelectric generation rather than eliminating it.