AB 1577 directs the California Energy Commission to establish registration and monthly reporting requirements for data centers that meet the bill's size threshold. The rule set spans electrical and IT capacity, total energy and water use, PUE and WUE ratios, onsite generation and storage, refrigerant types, waste heat reuse, demand‑flexibility participation, and sound levels at the property boundary.
The bill matters because it centralizes operational data that state planners have lacked, creates a public anonymized dataset for assessing data center demand on the grid and water systems, and forces operators to standardize and disclose many operational metrics — with compliance costs and measurement challenges for owners and verification and publication work for the commission.
At a Glance
What It Does
The bill requires owners of qualifying data centers to register with the California Energy Commission at energization and to submit a specified set of operational metrics monthly. The commission must publish anonymized, aggregated submissions annually and incorporate data‑center load analysis into the Integrated Energy Policy Report beginning in 2029.
Who It Affects
Owners and operators of larger data centers in California — specifically facilities that meet the bill's electrical capacity thresholds — plus the California Energy Commission, local permitting agencies, and neighboring communities who will see aggregated disclosures on energy, water, and noise.
Why It Matters
This creates one statewide source of standardized data for assessing data center impacts on grid capacity, peak demand, water resources, and local nuisances. For planners and compliance teams, the bill changes what operators must measure, document, and make available to state authorities.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 1577 sets up a two‑part reporting regime. First, when a covered data center is energized (or when earlier submitted details change), the owner must register basic facility metadata with the Energy Commission: name, addresses, operator and owner contact information, start date, floor area and IT‑occupied area, anticipated peak electrical capacity as listed in interconnection filings, and anticipated onsite generation by type.
That initial registration creates a central record and is the baseline for later monthly submissions.
Second, the owner must submit a fairly detailed monthly package of operational metrics. The bill lists electrical metrics (total and IT electrical capacity, monthly kWh consumption, power usage effectiveness, and participation in demand‑flexibility programs), water metrics (total and potable gallons and a water‑usage‑effectiveness ratio), heat‑recovery and thermal operation metrics (waste heat reused in kWh, waste heat temperature, IT intake air setpoint, refrigerant types, cumulative cooling degree days), onsite generation and fuel use (generation by type, fuel use for onsite generators), and granular accounting of renewable and carbon‑free electricity — separated into onsite/procured renewable generation as defined in state law, hydroelectric procured from plants over 30 MW, nuclear, and electricity associated with renewable energy credits identified by portfolio content category.
The bill also asks for energy storage details and average and maximum sound levels measured at the property boundary.To limit redundant compliance, the commission must design a submission process that reduces duplicated filings and permit owners to use substantially similar existing reports prepared for other legal requirements, provided they meet this bill's specifications. The commission must publish anonymized, aggregated results annually on its website, and starting with the 2029 Integrated Energy Policy Report, include a data‑center load assessment with future projections, potential peak demands, and mitigation recommendations for grid reliability, capacity, and emissions.
The statutory text ends before specifying enforcement mechanics, leaving a gap on penalties or audit authority that implementing regulations will need to fill.
The Five Things You Need to Know
The bill excludes facilities with installed IT electrical capacity under 500 kilowatts — only centers at or above that threshold fall under the reporting regime.
Monthly submissions must include both power usage effectiveness (PUE) and water usage effectiveness (WUE), plus total and potable water use in gallons.
Owners must report renewable and carbon‑free electricity by category: onsite/procured renewables (per Section 25741), hydroelectric procured from plants >30 MW, nuclear, and electricity associated with renewable energy credits identified under PUC Section 399.16.
Each monthly filing must include average and maximum A‑weighted decibel levels attributable to the data center, measured at the property boundary point with the highest average noise level.
The Energy Commission must publish anonymized, aggregated data annually and include a data‑center load assessment in the Integrated Energy Policy Report beginning with the 2029 edition.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions and scope
This section defines key terms used throughout the bill: "data center," "owner," "power usage effectiveness," "water usage effectiveness," and "cooling degree day." The text couples two size tests — an operational threshold tied to information‑technology load and an exclusion for facilities under 500 kW installed IT capacity — which together determine which facilities must report. Those dual thresholds matter because they set the population of covered facilities and may exclude smaller colocation suites within larger buildings unless the building as a whole meets the criteria.
Initial registration at energization
On energization (and after any substantive change), the owner must submit facility metadata: facility name and physical addresses, owner and operator contacts, month and year operations began, total floor area versus IT‑occupied floor area, anticipated peak electrical capacity (as reflected in interconnection filings), and anticipated onsite generation by type. Practically, this creates a statewide inventory that links interconnection expectations to on‑the‑ground deployments and gives planners baseline attributes for subsequent month‑to‑month comparisons.
Monthly operational metrics the owner must report
The bill enumerates a comprehensive set of monthly metrics grouped by energy, water, thermal, onsite generation/storage, and noise. Energy reporting spans maximum and installed IT electrical capacity, monthly kWh consumption, PUE, and demand‑flexibility participation. Water reporting requires total and potable water volumes and WUE. Thermal metrics cover waste heat reuse in kWh, waste heat temperature, intake air setpoints, refrigerant types, and cumulative cooling degree days. The owner must break out onsite generation and fuel use, specify energy storage type/capacity/chemistry, and subdivide renewable and carbon‑free electricity into narrowly defined categories (onsite/procured renewables, large hydro >30 MW, nuclear, and RECs by portfolio content category). Finally, the bill requires measurement of average and maximum A‑weighted decibels at the property boundary location with the highest average level. Those line‑item requirements create measurement and data‑format expectations that owners will need to operationalize.
Commission process, data reuse, and nonduplication
The commission must specify submission format and timing and is charged with minimizing duplicate filings. Owners are exempt from resubmitting information already on file, and the bill allows owners to satisfy requirements by submitting substantially similar reports prepared for other state, federal, or international obligations if they meet this bill's criteria. This is a practical concession to avoid multiple parallel compliance programs, but it shifts responsibility onto both owners and the commission to map equivalencies between different reporting standards.
Inclusion in the Integrated Energy Policy Report (IEPR)
Beginning with the 2029 IEPR, the commission must include an assessment of data‑center electrical load trends, projecting future loads, flagging potential net peak demands, and recommending mitigation measures to protect grid capacity, reliability, and emissions targets. This embeds data‑center operational data into long‑range state energy planning rather than treating centers as isolated consumers.
Annual public disclosure in anonymized, aggregated form
The commission must publish an anonymized, aggregated dataset of the submitted information annually on its website. That requirement increases public and planner access to sector trends while limiting facility‑level attribution. The statute stops short of specifying how aggregation thresholds will be set or how anonymization will reconcile with the commission's analytic needs, which are implementation questions for rulemaking.
This bill is one of many.
Codify tracks hundreds of bills on Energy across all five countries.
Explore Energy in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- California Energy Commission and grid planners — they gain standardized, monthly operational data to project demand, anticipate peak loads, and design mitigation strategies for reliability and emissions planning.
- Local permitting agencies and municipalities — the dataset provides consistent facility metadata and annual anonymized trends that can inform zoning, water use, and community noise planning without needing to collect separate ad hoc reports.
- Communities near data centers — required noise metrics and annual publication increase transparency about local impacts that were previously unevenly documented.
- State climate and water planners — granular breakdowns of onsite generation, renewable procurement categories, water use, and waste heat reuse create inputs for statewide decarbonization and water‑stress mitigation strategies.
Who Bears the Cost
- Data center owners and operators — the bill creates recurring measurement and submission obligations (monthly PUE/WUE, temperature and noise monitoring, fuel and REC accounting) that will require instrumentation, data collection systems, staff time, and possibly third‑party verification.
- The California Energy Commission — the commission must build submission portals, data processing workflows, anonymization and aggregation tools, and analytic capacity to incorporate the data into the IEPR, with associated administrative costs.
- Third‑party consultants and auditors — owners may need outside help to align existing reports with the bill's categories, perform acoustic boundary measurements, and document refrigerant inventories and waste‑heat reuse in the specified formats.
Key Issues
The Core Tension
AB 1577 pits the state's need for standardized, facility‑level operational transparency (to plan grid and water capacity and meet emissions goals) against data centers' need to protect commercially sensitive, security‑relevant operational details and to avoid onerous measurement and reporting costs; the statute must balance public planning value against the practical and competitive burdens it imposes on operators.
The statute mandates detailed metrics but leaves many practical measurement and attribution rules to the commission. That raises immediate implementation questions: how will PUE and WUE be calculated uniformly across operators with different measurement systems, how will the commission verify the accuracy of submissions, and what aggregation thresholds will protect commercial confidentiality while preserving analytic value?
The bill also prescribes fine‑grained electricity attribution (onsite renewables vs. procured renewables, large hydro, nuclear, and REC categories), but energy accounting for procured power depends on contracting arrangements and REC treatment that are already legally complex under existing PUC rules.
A second concern is security and commercial sensitivity. Facility‑level operational metrics are competitive and, in some cases, security‑sensitive.
The statute requires annual anonymized publication, but anonymization standards are not specified; overly aggressive anonymization will blunt the dataset's usefulness for planners, while insufficient anonymization risks revealing proprietary operational details. Finally, the bill text appears to cut off mid‑provision and does not include explicit enforcement, penalty, or audit authority—leaving open whether noncompliance will carry fines, withholding of permits, or other remedies.
Implementing regulations will need to address enforcement mechanics and verification protocols.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.