Tag: Tax Incentives

  • Pennsylvania’s $517M Tax-Break Vote Moves AI Data Center Leverage to Local Zoning

    Pennsylvania’s $517M Tax-Break Vote Moves AI Data Center Leverage to Local Zoning

    TL;DR · 30-second read

    The Short Version

    Pennsylvania’s state House voted 201 to 1 to let towns stop considering new data centers for six months while they write rules for them. Data centers are the huge warehouses of computers that run artificial intelligence and online services.

    Lawmakers also voted to end a tax break for these buildings that was expected to cost the state $517 million a year by 2030. That break was the reward in the governor’s plan to get builders to promise jobs, clean power and water limits.

    If the break disappears, local town boards become the place these projects are decided. The state Senate still has to act.

    With the June 30 state budget deadline days away, the Pennsylvania House passed three bills on data center development on June 24 and 25, 2026, the Pennsylvania Capital-Star reported. House Bill 2496 lets municipalities pause consideration of data center applications for 180 days and passed 201-1. House Bill 2650 writes Gov. Josh Shapiro’s Governor’s Responsible Infrastructure Development (GRID) Standards into law and passed 134-68. House Bill 2198 repeals the state’s 6% sales and use tax exemption on data center computer equipment and passed 197-5.

    The tax exemption is projected to cost the commonwealth $517 million a year by 2030. On the afternoon of the House vote, the Senate adopted the repeal language as an amendment to a separate tax code bill. The other two bills now sit with the Republican-led Senate, which could send them to Shapiro or leave them unconsidered.

    Executive Summary

    Pennsylvania’s House has moved from courting large data centers to regulating them. In two days it voted for a local construction-review pause, a certification regime that ties tax benefits to disclosure and job commitments, and the repeal of the tax benefit that regime depends on.

    The votes point in different directions. The GRID Standards are voluntary. Developers who meet targets on in-state clean energy, investment, prevailing-wage construction jobs and permanent jobs would get a sales tax exemption and faster permits. The repeal bill, which drew a 197-5 vote and quick Senate action, would eliminate that exemption. That leaves the standards with little to offer beyond permitting speed.

    The measure with the broadest support was the local pause, which passed 201-1. For developers of AI-scale facilities in one of the country’s most active data center markets, the practical gate is moving from state tax terms to municipal land-use calendars. That shift is not yet final, because the Senate has not acted on the pause or the GRID bill.

    The Incentive Is Going Before the Standards Arrive

    Pennsylvania’s 6% sales and use tax exemption on data center computer equipment is about five years old. House Environmental Resources Committee Chairperson Greg Vitali, who sponsored the repeal, said it was passed “during an era when lawmakers were trying to attract them to the commonwealth.” It is now projected to cost $517 million a year by 2030. For a facility filled with servers, networking gear and storage, a sales tax on equipment is a real line item. Across a whole state’s pipeline, it has become a budget question.

    The repeal has the most momentum of the three bills. It passed the House 197-5, and the Senate adopted the same language as an amendment to another tax code bill within hours. That creates a sequencing problem. HB 2650, passed a day earlier, is built on the exemption: it would make the tax break contingent on certification from the Department of Revenue. Rep. Craig Williams (R-Delaware) put it bluntly: “Like Lucy holding the football for Charlie Brown, we’re going to pull that football away.” Repeal supporters such as Rep. Kyle Mullins (D-Lackawanna) described the industry as “no longer an emerging sector looking for a foothold.” In their view the subsidy has simply outlived its purpose.

    Why Leverage Shifts From Harrisburg to the Township Board

    The GRID Standards are designed as a trade. A developer discloses its ownership structure, energy procurement strategy, water usage, community engagement and environmental plans, and meets investment and job floors. In return it gets the sales tax exemption and expedited permitting. Remove the exemption and the state’s offer shrinks to faster permits. That is a thinner inducement for a program that is voluntary. Critics were already skeptical that the largest companies would participate even with the tax benefit.

    The tool that drew near-unanimous support is local. Under HB 2496, a municipality could stop considering data center applications for 180 days and use that time to adopt, amend or repeal the parts of its land use ordinance that cover data centers. Any application received during the pause would be treated as received the day after the pause ends. That detail matters. The pause does not reject projects. It holds them until new rules exist, so a proposal filed mid-pause would be judged against whatever ordinance the township writes. Rep. Paul Friel (D-Chester) noted that many rural municipalities have no zoning ordinance at all, and others lack provisions for facilities of this scale.

    The people most affected are data center developers and their site-selection teams. Their schedule risk would be set by municipal meeting calendars rather than state tax terms. Landowners holding land options are also exposed, as are the utilities and power suppliers whose planning depends on when large new loads actually arrive. One borough in Lackawanna County faces 16 data center applications, according to Mullins, which shows how concentrated these decisions can become. There is an important caveat. If the repeal becomes law and the pause bill stalls in the Senate, Pennsylvania would have neither the state incentive nor the new local pause. Projects would proceed under existing ordinances, which Friel says many townships lack.

    What the GRID Terms Say About Power and Scale

    The certification requirements go beyond jobs. Developers would need to increase their use of clean energy from Pennsylvania sources step by step, reaching 32% by 2035. That makes the standards a power procurement rule, not just an economic development one. The other floors are:

    • at least $250 million in cumulative new investment;
    • at least 200 prevailing-wage construction jobs;
    • 50 permanent jobs paying at least 125% of the statewide average wage within four years;
    • at least $1.5 million a year in compensation to full-time employees after that.

    Energy procurement and water usage both appear on the application. That reflects the pressures lawmakers cited: large AI facilities draw heavily on water resources, energy infrastructure and public services. Pennsylvania sits inside PJM Interconnection, the regional grid operator for much of the mid-Atlantic and Midwest, where large new loads weigh directly on grid planning. The state’s most visible project shows how developers are responding to power constraints. The former Homer City Generating Station in Indiana County, once Pennsylvania’s largest coal-burning power plant, is being turned into a natural gas-powered data center campus, and construction was under way as of mid-May.

    Testing Both Sides’ Claims

    Williams argued that companies such as Google and the parent company of X “don’t care” about the sales tax exemption and would forgo it rather than accept conditions. The $517 million projection suggests the break is worth a lot in total, so it is hardly trivial. But total cost does not show that the exemption decides where any particular facility goes, and the debate did not include a developer saying either way.

    Repeal supporters argue the break is “not needed,” and the volume of applications supports the claim that demand exists without it. Current filings, though, do not show what happens to marginal projects once the benefit is gone. Neither does the phrase “speculative gold rush,” which one legislator used, tell us how many of the dozens of hyperscale applications have tenants, power and financing behind them. A 180-day pause may be the mechanism that sorts firm projects from speculative land positions.

    Background

    Pennsylvania spent much of the past half-decade trying to attract data centers, including through a sales and use tax exemption on their computer equipment. The race to build artificial intelligence capacity has since produced hyperscale proposals across the commonwealth, and local officials are now weighing dozens of applications. Some of the most prominent projects repurpose power-plant sites, such as the former Homer City Generating Station, which is being converted from coal to a gas-powered data center campus.

    Gov. Josh Shapiro outlined his approach to data center development in his February 2026 budget address and released details in May as the GRID Standards. The state is part of PJM Interconnection, the regional grid operator where the arrival of large new electricity loads has become a central planning concern. That places Pennsylvania’s policy choices at the intersection of land use, tax policy and power supply.

    Sources

    Source: Pa. House passes data center ‘pause’ along with Shapiro’s plan for ‘responsible’ development (Pennsylvania Capital-Star), covering House passage of HB 2496, HB 2650 and HB 2198 on data center regulation and tax policy.

  • Ohio Would Halve a $1.6B Data Center Break. The Harder AI Fight Is Who Pays for the Grid

    Ohio Would Halve a $1.6B Data Center Break. The Harder AI Fight Is Who Pays for the Grid

    TL;DR · 30-second read

    The Short Version

    Ohio lawmakers want to shrink a tax break for data centers, the giant warehouses of computers that run artificial intelligence and online services. The break cost the state roughly $1.6 billion last year. The bill would cut it in half.

    The bigger fight is over electricity bills. These buildings use so much power that new power lines and power plants have to be built. Manufacturers and environmental groups warn that ordinary households could end up paying part of that cost.

    Senators aimed to pass the bill within a day.

    Ohio state Sen. Brian Chavez unveiled a sweeping data center bill on Tuesday, June 9, attaching a long list of policy changes to a measure originally written only to study the issue, the Ohio Capital Journal reported. The proposal would cut the state’s discretionary sales and use tax exemption for data centers from 100% to 50%, or 75% for projects that build on brownfields and bring their own power. The exemption has grown to roughly $1.6 billion in the last year. The bill would also cap local property tax abatements at 50%, end data center access to Ohio’s 30-year mega project job creation grant, require data centers to track and report water use, and direct the Public Utilities Commission of Ohio (PUCO) to create a separate electricity rate class for data centers.

    The Senate Energy Committee was scheduled to advance the bill Wednesday morning, June 10, with a full Senate vote planned for later the same day.

    Executive Summary

    Ohio’s bill is one of the broadest state-level rewrites of data center policy so far. It covers tax incentives, nondisclosure agreements, water monitoring, utility billing, and a new surety bond meant to protect local governments. The tax provisions are the most concrete part. A roughly $1.6 billion incentive would be cut in half, with a larger 75% break reserved for projects on brownfields (previously developed, often contaminated land) that supply their own electricity.

    The provision that drew the sharpest testimony was the proposed data center rate class. It is modeled on the tariff PUCO approved for AEP Ohio last year, which the Ohio Manufacturers’ Association is now challenging in the Ohio Supreme Court. The underlying question is the one now running through every state served by PJM Interconnection, the regional grid operator: when AI-era data centers drive new transmission, distribution and generation spending, who ends up paying for it? PJM plans a backstop auction in September to secure 15 gigawatts of new generation. It has warned that without state rules, those costs could fall on other consumers, including residential customers.

    With a committee vote and a floor vote planned within about a day of introduction, the chance to refine the rate-class language before the Senate acts was limited.

    Tax Policy That Doubles as Power Policy

    The headline change is a 50% cut to the sales and use tax exemption. The more revealing detail is the exception. Projects keep a 75% break only if they build on brownfields and bring their own power. That condition ties Ohio’s largest data center incentive to a developer’s grid footprint as well as its capital spending. In practice, the state would be paying a premium for sites that reuse industrial land and lean less on utility-supplied electricity.

    Other provisions point the same way. Capping local property tax abatements at 50% and removing access to the 30-year mega project job creation grant both reduce the long-term public subsidy a single campus can collect. Together, these changes suggest Ohio is trying to stay open to data center investment while no longer competing mainly on how much tax it will forgo. Developers already planning Ohio sites will need to revisit their project economics. Those able to secure their own generation gain a relative advantage. The bill does not define what counts as bringing their own power, and that definition will matter.

    The Harder Fight Is the Rate Class

    The tax changes drew relatively little objection in testimony. The utility billing provision did not. The bill directs PUCO to create a data center rate class that assigns generation, distribution and transmission costs to data centers, similar to AEP Ohio’s existing data center tariff. The Ohio Manufacturers’ Association, already challenging that tariff in court, opposed extending the model statewide. Its energy consultant, John Seryak, described one project in AES Ohio’s territory that would need roughly $230 million in supplemental grid equipment. He said that once the cost is financed over 40 years with return on equity and interest, it comes to about $850 million, and the tariff would recover only $300 million of it. These are the association’s estimates, not audited figures. But the mechanism is plain. If a rate class spreads a project’s costs over years and collects less than the full lifetime cost, the gap has to be paid by someone else on the system.

    Seryak raised a second concern about the minimum monthly demand payments these tariffs impose. Minimum payments are generally meant to ensure a large customer covers the capacity built for it. He argued they could also inflate utilities’ load forecasts, pushing them to plan for more capacity whose cost is then spread across all ratepayers. They could also weaken a data center’s incentive to use power efficiently. The Ohio Environmental Council Action Fund raised a related gap. Nolan Rutschilling asked lawmakers to add explicit language telling PUCO how to handle PJM’s September backstop auction for 15 gigawatts of new generation. He said the large-load tariff might cover it, but the bill should make sure it does. The affected parties are clear. Manufacturers and households pay if costs leak out of the rate class. Developers pay more if it is written tightly. Utilities have to forecast and build against whatever the final design encourages.

    Water, NDAs and Local Leverage

    On water, the bill directs the Ohio EPA to develop a water quality testing plan and report any anomalies. Data centers would have to track and report their water use and adopt conservation practices, including closed-loop cooling, which recirculates coolant rather than continually drawing fresh water. This gives regulators data they currently lack. It does not set usage caps.

    The nondisclosure agreement provision drew criticism from both parties. The bill states that an NDA cannot prohibit or limit the release of a public record. Sen. Bill DeMora, D-Columbus, said this “does nothing to stop NDAs,” because it does not ban them. Sen. Jerry Cirino, R-Kirtland, worried from the other direction that the bill could hurt data centers’ ability to negotiate with local governments. The proposed surety bond is the most unusual local protection. It would equal the average salary of all of a data center’s workers over ten years, which Chavez described as “financial insurance” for affected communities. Save Ohio Parks asked for some carbon-free energy requirements and pointed to diesel backup generators as a pollution concern. The bill as introduced does not include such a requirement.

    Speed Leaves the Details Unsettled

    Chavez’s timeline, with a floor vote potentially one day after introduction, means the most contested language faced little revision in the Senate. DeMora warned that “anything the legislature does in a swift amount of time ends up being bad for everybody.” The risk is concentrated in the rate-class provision. The tax percentages are simple numbers. The cost-allocation rules are not, and they would be left largely to PUCO to design while the AEP tariff remains in litigation.

    For the wider PJM region, Ohio’s bill is a sign of where state policy is heading. Incentives are being trimmed and made conditional, while the real policy work moves to utility commissions and tariff design. That is where the costs of AI-driven load growth will actually be divided.

    Background

    Ohio, particularly central Ohio, has become a major destination for large data center campuses. Its utilities, including AEP Ohio and AES Ohio, are part of the PJM Interconnection grid, which covers all or parts of 13 states and Washington, D.C. As AI-driven demand for computing power has grown, PJM and its member states have struggled with how to pay for the transmission lines, substations and power plants needed to serve that load without shifting costs onto existing customers.

    PUCO approved a data center tariff for AEP Ohio last year to assign more of those costs to data centers. The tariff is now under challenge by the Ohio Manufacturers’ Association in the Ohio Supreme Court. Chavez’s bill draws on testimony from the Ohio Senate’s Select Committee on Data Centers and would extend a similar rate-class approach across the state’s utilities.

    Sources

    Source: Ohio lawmakers introduce sweeping new data center legislation (Ohio Capital Journal), covering Sen. Brian Chavez’s bill on data center tax breaks, water use, NDAs and utility rate classes.

  • Meta Confirms Hyperscale Data Center in East Tulsa

    Meta Confirms Hyperscale Data Center in East Tulsa

    Meta has confirmed that it will operate a hyperscale data center in east Tulsa, Oklahoma, according to the Tulsa World on 21 April 2026. The confirmation resolves the identity of the operator behind a large industrial computing project in the city’s eastern industrial corridor.

    The report establishes the operator and the general location. It does not, in the material available to us, attach a published megawatt figure, capital investment number, employment commitment, construction schedule or incentive package to the project — all of which remain the substantive questions for Tulsa residents, ratepayers and suppliers.

    Executive Summary

    The news is the confirmation itself. Large data center projects are routinely assembled under placeholder corporate names and non-disclosure agreements while land is optioned, utility service is negotiated and incentives are cleared; the operator’s name is often the last thing to surface. Meta putting its name to an east Tulsa campus turns a speculative local story into a fixed point that utilities, contractors, county assessors and competing site selectors can now plan around.

    It matters because “hyperscale” is not a small industrial category. A single modern hyperscale campus can become one of the largest electricity customers in its host utility’s territory, reshaping load forecasts, transmission planning and the economics of new generation for everyone else on the system. Whatever this specific site’s final size, its arrival changes the planning assumptions in northeastern Oklahoma.

    It also matters for Oklahoma’s position in the national compute map. The state already hosts one of Google’s long-running campuses at Pryor, roughly an hour from Tulsa. A second major operator in the same region begins to look less like an isolated deal and more like a cluster — with the labor pool, contractor base and transmission attention that clusters attract, and the concentration risks that come with them.

    What “Hyperscale” Confirms — and What It Doesn’t

    “Hyperscale” describes an operating model, not a unit of measurement. It means a facility built and run at the scale of the largest cloud and platform companies: standardized building templates, tens of thousands of servers, custom networking, and power delivered at transmission voltage rather than the distribution voltage a typical factory takes. It says nothing precise about how many megawatts the site will draw or how many buildings will eventually stand on it.

    That distinction matters here because the confirmation carries no published capacity figure. Industry framing around new campuses has drifted toward gigawatt-class language — a gigawatt being roughly the output of a large power plant, or the demand of a mid-sized city — and the largest recent US announcements have been in that range. But an unstated capacity is an unstated capacity. The honest reading on 21 April 2026 is that Meta has confirmed an operator and a location, and that anyone quoting a wattage for east Tulsa is extrapolating from the industry’s recent pattern rather than from the announcement.

    The same caution applies in the other direction. Absence of a headline number is not evidence the project is modest; hyperscale campuses are typically phased, with each phase authorized against demand that does not yet exist when ground breaks. The realistic expectation is a site that grows in steps over years, with the final footprint set by demand and by how much power the local grid can actually deliver.

    Tulsa’s Grid Math: PSO, SPP and the Wind Belt

    Tulsa is served by Public Service Company of Oklahoma, an American Electric Power subsidiary, inside the Southwest Power Pool — the regional grid operator covering much of the central plains. That footprint has two relevant characteristics. It has abundant wind generation, which has historically made Oklahoma power cheap and carbon-light on an annual-average basis, and it has the classic wind-region problem that supply peaks when the wind blows rather than when a data center is drawing its steady, around-the-clock load.

    Hyperscale load is close to flat: high utilization, day and night, largely indifferent to weather. Marrying that profile to a wind-heavy system means firm capacity, storage, transmission upgrades, or some combination — and the question of who pays for them is the central regulatory issue in nearly every large-load interconnection in the country right now. Utilities increasingly seek special large-load tariffs with minimum take obligations and exit fees, precisely so that if a campus is cancelled or shrinks, the infrastructure built for it does not land on residential bills.

    Nothing in the confirmation tells us which structure applies here. That is the thing worth watching: the utility filings and any state regulatory dockets will disclose more about the real terms of this project than any ribbon-cutting will. If the arrangement is well designed, a very large customer paying full freight for its own upgrades can spread fixed system costs across more kilowatt-hours and mildly benefit other ratepayers. If it is poorly designed, the transfer runs the other way. Both outcomes are common enough that the question is not rhetorical.

    Water, Land and the Terms of the Bargain

    Water is the second recurring flashpoint, and it turns almost entirely on cooling design. Evaporative cooling is efficient with electricity but consumes water continuously; closed-loop and air-cooled designs consume far less water while drawing more power for the same heat rejection. Operators have moved toward lower-water designs in dry regions, and several publish water-use figures, but a design choice for east Tulsa has not been stated. Tulsa’s municipal supply comes from northeastern Oklahoma reservoirs and is not the constrained desert supply that has made this a crisis issue elsewhere — which lowers the temperature of the question without settling it.

    On the fiscal side, Oklahoma has long used sales-tax exemptions on qualifying computing equipment and local property-tax abatements to compete for capital-intensive facilities. These tools work as intended: they lower the effective cost of the single most expensive input in a data center, the servers and electrical plant. They also produce the familiar asymmetry that makes such deals contentious. Construction employment is large and temporary — often well over a thousand trades workers at peak on a big campus — while permanent operations staffing at even very large sites is measured in the low hundreds. The durable local benefit is usually the property tax base after abatements expire, plus utility revenue and construction spending, not headcount.

    That is an argument to be had on specifics, and the specifics have not been published. A fair assessment of this deal requires the abatement schedule, the assessed valuation assumptions, any clawback provisions, and the wage and hiring commitments. Until those are on the table, both boosterish jobs claims and blanket assertions that the community gets nothing are running ahead of the evidence.

    A Second Oklahoma Cluster, and Who Gains From It

    The clearest beneficiaries are regional and immediate: electrical and mechanical contractors, civil and earthworks firms, switchgear and transformer suppliers, fiber builders, and the trades unions and training pipelines that staff them. Data center construction is unusually equipment-heavy and schedule-driven, which tends to pull skilled labor from a wide radius and bid up local rates for the duration. Tulsa’s existing industrial and aerospace workforce is a reasonable base for that.

    The second-order winner is Oklahoma’s site-selection story. Google’s long presence at Pryor gave the state a reference customer; a Meta campus near Tulsa gives it two independent validations, which is what site selectors for the next tenant actually look for. Clusters compound — transmission gets built, permitting staff get experienced, suppliers open local branches. The corresponding risk is concentration: a region that leans on a handful of very large loads inherits their capital cycles, and the AI build-out that is driving current demand is not guaranteed to hold its present pace.

    The parties with the most at stake and the least information right now are residential and commercial ratepayers, and the neighborhoods nearest the site. Their exposure runs through utility tariffs, transmission cost allocation, construction traffic and noise, and the local tax base. Those are all decided in public proceedings — utility commission filings, county assessor records, municipal permits — and that is where scrutiny is best directed, by supporters and critics alike.

    Background

    Meta operates a global fleet of company-built data centers supporting its social platforms and, increasingly, large-scale AI training and inference. Like other hyperscalers, it typically develops campuses in phases on large rural or industrial parcels chosen for power availability, land, fiber routes and tax treatment, and it has expanded that program substantially through the current AI infrastructure cycle.

    Oklahoma has competed for these projects on cheap land, a wind-heavy generation mix within the Southwest Power Pool, and long-standing tax exemptions for computing equipment. Google’s Pryor campus in the MidAmerica Industrial Park has been the state’s anchor example for over a decade. Tulsa itself brings an industrial and aerospace workforce and a metro-scale utility system, which is what distinguishes it from the small rural sites that have hosted most recent hyperscale announcements in the region.

    Source: It’s official: Meta will operate hyperscale data center in east Tulsa — Tulsa World, 21 April 2026, reporting Meta’s confirmation that it will operate a hyperscale data center in east Tulsa, Oklahoma.