On the agenda: Bullhead City Special City Council Meeting - Nov 03, 2026 — data center (Nov 3)

MISSION STATEMENT
"IT IS THE GOAL OF THE CITY OF BULLHEAD CITY TO
ENHANCE THE QUALITY OF LIFE AND PROMOTE A SENSE
OF COMMUNITY TO RESIDENTS BY PROVIDING QUALITY
PUBLIC SERVICES IN A RESPONSIBLE, EFFICIENT AND
EFFECTIVE MANNER."
AGENDA
WORKSHOP
BULLHEAD CITY COUNCIL
TUESDAY, NOVEMBER 3, 2026 - 3:00 PM
CITY COUNCIL CHAMBERS
1255 Marina Boulevard, Bullhead City, Arizona

Discussion only regarding the creation of a data center ordinance.
No legal action will be taken by the Council during the Work Session.
ADJOURNMENT
Dated this 29th day of October 2026.

Q ~ ~~
C, CPM

Debie Ogden,
City Clerk

Pursuant to the Americans with Disabilities Act (ADA), the City of Bullhead City endeavors to ensure the
accessibility of all its programs, facilities and services to all persons with disabilities. If you need an
accommodation for this meeting, please contact Human Resources Department, at (928) 763-0153 at least
twenty-four (24) hours prior to the meeting so an accommodation may be arranged.

DISCUSSION ITEM-DATA CENTERS

CITY OF BULLHEAD CITY
COUNCIL COMMUNICATION

SUBJECT:

Data Center Workshop

DEPT OF ORIGIN:

City Manager's Office

DATE SUBMITTED:
SUBMITTED BY:

MEETING DATE:

November 3, 2026

10/28/2026
Toby Cotter, City Manager

SUMMARY:

Workshop on Data Centers. This item is for discussion only. No action will be taken by the City Council. The
Planning and Zoning Commission took up this item on September 17, 2026. The Planning and Zoning
Commissioners have also been invited to this workshop. The background information on this item can be found
online as item #6 in the September 17, 2026 Planning and Zoning Commission packet. This item includes
general information and numerous other city ordinances related to data centers. The City Council is encouraged
to review the ordinances and be prepared to discuss the creation of a Bullhead City Data Center ordinance
addressing: Electricity, water, noise, neighborhood protection, buffers from existing houses, building design
standards and aesthetics, emergency response, economic benefits, financial guarantees, enforceable
commitments, etc. The City Manager and Planning Manager will walk through those items at the City Council
workshop soliciting feedback from the City Council and Planning Commission.
FISCAL IMPACT:
REVIEWED BY: _ _ _ _ __

Finance Department
ATTACHMENTS:

LEGAL REVIEW:
APPROVED AS TO FORM: _ _ _ __

City Attorney
RECOMMENDATION:

Discussion only. No action will be taken at this meeting.
APPROVED FOR SUBMITTAL BY:

CITY CLERK ·s USE ONLY
COUNCIL ACTION TAKEN

Resolution No. _ _ _ _ _ __
Ordinance No. - - - - - - Approved - - - - - - Other _ _ _ _ _ __

BHC-16 (10/2001)

Continued To:
Referred To: - - - - - - Denied
File No. - - - - - - -

j:\forms\coundl comm form.doc

CITY OF BULLHEAD CITY
PLANNING & ZONING

DATE:

FOR THE SEPTEMBER 17, 2026 MEETING

TO:

PLANNING & ZONING COMMISSION

FROM:

JOHNNY LOERA, PLANNING MANAGER

SUBJECT:

DISCUSSION -DATA CENTERS

DESCRIPTION:
During the August 13, 2026 Planning and Zoning Commission meeting, a request was
made by members of the Commission to place a general discussion of data centers on the agenda
for the following Commission meeting. No action will be proposed or taken as part of this agenda
item.
Data centers are not currently defined in the Bullhead City municipal code. The most
similar use that is specified in the code is "warehousing", which is allowed only in C3 (Commercial
and Minor Industrial), Ml (Industrial: General Limited), and M2 (Industrial: Heavy) zoning
districts by right. Generally, data centers are facilities that house large quantities of computer
systems, servers, data storage, and networking hardware. There are several major concerns
associated with data centers, including energy demands, water usage, noise, and proximity to
residential areas, amongst others.
Several cities and counties throughout the state have passed ordinances defining, and
setting development standards for data centers. The Mohave County Board of Supervisors, for
example, passed an ordinance in 2025 requiring that data centers internalize their energy and water
needs to mitigate their environmental impact and lessen strain on County services. Staff reports
and ordinances from other jurisdictions within the state have been included as attachments. The
attachments also include an article from the Arizona Corporation Commission website outlining
the approval of an application by electric cooperatives in the state to protect existing customers
from the costs of new transmission and power demands from large-load customers.
Generally, the ordinances address several key issues, including the following:

Defining "data centers": As a relatively new use, county and municipal codes
typically did not define or contain any specific data center regulations.
Setbacks from other zoning districts: Setback requirements can vary. Some codes
require only that mechanical and electrical equipment be located a specific distance
from a property line abutting another zoning district, while some require substantial
building setbacks {112 mile or greater) from a data center to the nearest residential
zoning district.

Architectural design guidelines: Varied design guidelines for the architectural design
of buildings, landscaping, streetscape, lot coverage, building heights, etc.
Special use permit requirements: Several jurisdictions have specified that data
centers are not allowed by right in any district, but require special/conditional use
permits within specific commercial or industrial districts.
Noise: requirements for information/studies demonstrating that ambient noise levels
will either not increase, or increase only by a specific percentage.
Backup Generators: limitations on types of generators, notification requirements for
testing, etc.
Water usage: compliance with local water conservation standards, and submittal of
water consumption plans/studies. Some jurisdictions have policies requiring that these
facilities use closed-loop cooling systems to reduce water usage. The City of
Avondale, for example, states on their website that a recently approved data center
uses approximately 97% less water than an equivalently sized residential
neighborhood
(h!tPs://avondaleaz.gov/goverrunentlde,partments/economic-developmcntldatacenters-faaD.
Attachments: 1) Staff report and zoning code text amendment from City of Phoenix
2) Zoning ordinance from City of Chandler
3} Zoning ordinance from City of Tucson
4) Excerpt from Development Code for City ofTempe
5) Excerpt from Zoning Code City of Mesa
6) Arizona Corporation Commission article

City of Phoenix
PLANNING AND DEVELOPMENT DEPARTMENT

Staff Report
Zoning Ordinance Text Amendment
Z-TA-2-25-Y
May 1, 2025
Application No. Z·TA-2-25-Y: Amend the Phoenix Zoning Ordinance Chapter 2,
Section 202 (Definitions) to add a definition for data centers; amend Chapter 5, Section
507 Tab A.II.D (Guidelines for Design Review, City-Wide Design Review Guidelines,
Specialized Uses) to modify the section title and add design standards for data centers;
and amend Chapter 6, Section 647 (Special Permit Uses), Section 647.A.2 to add data
centers within the C-2 (Intermediate Commercial), C-3 (General Commercial), CP/GCP
(Commerce Park/General Commerce Park), A-1 (Light Industrial), and A-2 (Industrial)
zoning districts, with a Special Permit and performance standards
Staff recommendation: Staff recommends approval of Z-TA-2-25-Y as shown in the
proposed text in Exhibit A.

BACKGROUND
In 2024, the Mayor and City Council directed City staff to create new policy guidance
and zoning regulations related to data centers, in response to the increased frequency
and development of these types of facilities. Data centers house a large collection of
technological equipment designed to store, process, and manage vast amounts of
digital information. One major concern with data centers is that their energy demand is
expected to increase significantly, in large part due to Artificial Intelligence. Another
major concern is the scale at which these types of facilities are built and how they can
negatively affect the surrounding community they are built in. The companion general
plan amendment, GPA-2-25-Y is a request to amend the 2025 General Plan to add a
section to provide policy guidance for data centers addressing the major concerns they
pose to the community and to the city.
Staff researched other cities in the nation that have adopted ordinances related to data
centers for best practices and looked at ways Phoenix could enhance those ordinances.

Staff Report: Z-TA-2-25-Y
May 1, 2025
Page2
PURPOSE
The intent of the proposed text amendment is to create a regulatory framework for data
centers. Data centers are not defined nor are they explicitly listed as a permitted use in
the Phoenix Zoning Ordinance; therefore were addressed via informal interpretation .
This text amendment will create a new definition for "data center"; create design
guidelines such as setback requirements and screening design standards for equipment
enclosures and accessory public utility buildings and facilities, such as electrical
substations; and create enhanced landscaping, architectural, and streetscape standards
to soften the design of data centers so they can better blend into the surrounding
environment they are built in; and develop location criteria and performance standards
for data centers. This includes spacing from high-capacity transit; noise standards to
reduce the impact of data centers when located within a certain distance from
residential; and allow data centers only the following zoning districts: C-2, C-3, CP/GCP,
A-1 and A-2 with a Special Permit.
DESCRIPTION OF THE PROPOSED TEXT
The proposed text amendment includes three main components: Definitions, Data
Center-Specific Design Guidelines, and special permit requirements and performance
standards:

1. Definitions:
The Zoning Ordinance currently does not have a definition for the term "data center".
The proposed definition states generally what a data center is and when it may be
considered as an accessory use to a non-residential use, if it occupies no more than
10 percent of the building footprint, is used to serve the enterprise functions of the
on-site property owner, is not used to lease data storage and processing services to
third parties and is not housed in a separate stand-alone structure on the site.
2. Data Center.Seecific Design Guidelines:
The proposed regulations for data centers were based and built upon established
practices in other municipalities. Equipment enclosures would need to be setback a
minimum of 150 feet from abutting rights-of-way and residentially zoned properties,
and screened by a decorative solid wall or building. Mechanical equipment, such as
an electrical substation, would also need to meet similar setbacks and decorative
screening requirements. Since data centers are very large in scale, enhanced
streetscape, landscape setback and planting standards will help to soften the edges
of data center sites and will beautify the edges of the site that interacts with the
surrounding community. Enhanced architectural design guidelines, such as variation
in colors, materials, patterns, textures, height, window fenestration , and articulation,
and standards for art in private development, will help to avoid large, monotonous,
undifferentiated surfaces and avoid large, monolithic buildings, and instead will
provide an enhanced design interface with a visual interest for the surrounding
community.

Staff Report: Z-TA-2-25-Y
May 1, 2025
Page 3

3. Special Permit Requirements and Performance Standards:
The Zoning Ordinance currently does not have development regulations for data
centers. The proposed text amendment would allow data centers in the C-2, C-3,
CP/GCP. A-1 and A-2 zoning districts with a Special Permit. The performance
standards for data centers include a half a mile spacing from approved high-capacity
transit, noise study and noise mitigation requirements for data centers located within
300 feet of a residential zoned district and a will-server letter from the utility company
that it can serve the energy demand within two years.

Conclusion:
This text amendment will create a process for data centers to be proposed and
evaluated through a public hearing process. The text amendment will provide standards
to address major concerns that data centers cause. By adding a definition for the term
"data center", clarifying the districts in which they are permitted, and adding standards
for data centers to follow, Phoenix will be leading in ensuring that data centers blend
with the surrounding environment while limiting negative impacts to existing
communities.
Staff recommends approval of the changes to the Zoning Ordinance as proposed in Exhibit

A.
Writer
Adrian Zambrano
May 1, 2025

Team Leader
Racelle Escolar

Exhibit
A. Proposed Language

'

Staff Report: Z-TA-2-25-Y
May 1, 2025
Page4

Exhibit A
Staff Proposed Language That May Be Modified During the Public Hearing Process is
as follows:

Amend Chapter 2, Section 202 (Definitions) to add a definition for data centers.
Section 202. Definitions.
***

DATA CENTER: A FACILITY USED PRIMARILY FOR DATA SERVICES, INCLUDING
THE STORAGE, PROCESSING, MANAGEMENT, AND TRANSMISSION OF DIGITAL
DATA. A FACILITY SHALL NOT BE CONSIDERED A DATA CENTER WHEN IT DOES
NOT EXCEED 10% OF THE GROSS FLOOR AREA OF ALL ON-SITE BUILDINGS; IS
USED TO SERVE THE ENTERPRISE FUNCTIONS OF THE ON-SITE PROPERTY
OWNER; AND IS NOT USED TO LEASE DATA SERVICES TO THIRD PARTIES.
***

Amend Chapter 5, Section 507 Tab A.II.D (Guidelines for Design Review, City-Wide
Design Review Guidelines, Specialized Uses) to modify the section title and add
design standards for data centers, and to read as follows:
Section 507 Tab A. Guidelines for design review.
***
II.

CITY-WIDE DESIGN REVIEW GUIDELINES. The design review guidelines
iRdisale spesifis staRetaFEts of implemeRtatioR aRd are sategorized as RequiremeRt&
(R), PresumptioRs (P), or CoRsieteratioR& (C). INDICATED WITH THE MARKERS
(R), (R*), (P), (T), AND (C) SHALL BE APPLIED AND ENFORCED IN THE SAME
MANNER AS INDICATED IN SECTION 507.1TEMS NOT INDICATED WITH AN
(R), (R*), (P), (T), AND (C) SHALL BE TREATED AS (R).
***

D.

Specialized Uses.
***

5.

DATA CENTERS.

Staff Report: Z-TA-2-25-Y
May 1, 2025
Page 5
5.1.

SETBACKS. ALL MECHANICAL EQUIPMENT,
INCLUDING BUT NOT LIMITED TO ELECTRICAL
TRANSFORMERS AND GENERATORS, SHALL BE SET
BACK A MINIMUM OF 150 FEET FROM ABUTTING RIGHTOF-WAY OR RESIDENTIALLY ZONED PROPERTY; IN
ADDITION TO THE FOLLOWING: (R*)
5.1.1. THE EQUIPMENT MUST BE FULLY SCREENED BY
A BUILDING THAT IS VISUALLY INTEGRATED
WITH THE DESIGN OF THE OVERALL
DEVELOPMENT; OR
5.1.2 THE EQUIPMENT MUST BE FULLY SCREENED BY
A DECORATIVE SCREEN WALL HAVING
VARIATIONS IN COLORS, MATERIALS,
PATTERNS, TEXTURES, AND/OR AN ART
INSTALLATION SUCH AS A MURAL.
RATIONALE: GROUND EQUIPMENT SHOULD BE
ENCLOSED AND SET BACK TO PROVIDE VISUAL
SCREENING AND REDUCE NOISE LEVELS.

5.2.

LANDSCAPE SETBACK. A MINIMUM 30-FOOT WIDE
PERIMETER LANDSCAPE SETBACK SHALL BE
PROVIDED, SUBJECT TO THE FOLLOWING:
5.4.1. TWO STAGGERED ROWS OF LARGE CANOPY
SHADE TREES PLANTED 20 FEET ON CENTER OR
IN EQUIVALENT GROUPING SHALL BE
PROVIDED, AS APPROVED BY THE POD
LANDSCAPE ARCHITECT. (T)
5.4.2 FIVE 5-GALLON SHRUBS PER TREE SHALL BE
PROVIDED, AT A MINIMUM. (T)
5.4.3 GROUNDCOVERS SHALL BE PROVIDED TO
SUPPLEMENT THE TREES AND SHRUBS SO THAT
A MINIMUM 75% LIVE COVERAGE IS ATTAINED.
(T)
RA T/ONALE: AN ENHANCED LANDSCAPE SETBACK
WITH A DENSE NUMBER OF TREES AND SHRUBS
HELPS TO MITIGATE NEGATIVE VISUAL IMPACTS.

5.3.

ARCHITECTURE.

Staff Report: Z-T A-2-25-Y
May 1, 2025
PageS

5.3.1. BUILDING FACADES THAT EXCEED 100 FEET
SHOULD CONTAIN ARCHITECTURAL
EMBELLISHMENTS AND DETAILING SUCH AS
TEXTURAL CHANGES, PILASTERS, OFFSETS,
RECESSES, WINDOW FENESTRATION
(INCLUDING FAUX WINDOWS), SHADOW BOXES,
AND OVERHEAD/CANOPIES. (P)
5.3.2. ALL SIDES OF A BUILDING/STRUCTURE SHOULD
PROVIDE AN ENHANCED DESIGN INCLUDING A
VARIATION IN COLORS, MATERIALS, PATTERNS,
TEXTURES, HEIGHT, WINDOWS (INCLUDING
FAUX WINDOWS), ARTICULATION, AND/OR ART
INSTALLATIONS. (P)

5.3.3. EACH MAIN ENTRANCE SHOULD INCLUDE A
FEATURE THAT DIFFERENTIATES IT FROM THE
REMAINDER OF THE BUILDING FACADE BY A
CHANGE IN BUILDING MATERIAL, PATTERN,
TEXTURE, COLOR, AND/OR ACCENT MATERIAL,
AND THAT PROJECTS OR IS RECESSED FROM
THE ADJOINING BUILDING PLANE. (P)
5.3.4. ARCHITECTURAL DESIGN SHOULD TAKE INTO
ACCOUNT THE SOLAR CONSEQUENCES OF
BUILDING HEIGHT, BULK, AND AREA. (C)
RATIONALE: DATA CENTER BUILDINGS SHOULD
INCLUDE ENHANCED ARCHITECTURAL DESIGN
FEATURES IN ORDER TO PROVIDE VISUAL INTEREST,
TO BREAK UP THE MASS OF THE
BUILDING/STRUCTURE AND TO PROVIDE AN
ENHANCED DESIGN INTERFACE WHERE VISIBLE FROM
A RIGHT-OF-WAY AND/OR RESIDENTIALLY ZONED
PROPERTY.

5.4.

STREETSCAPE. FOR EACH STREET FRONTAGE, A
MINIMUM 6-FOOT-WIDE DETACHED SIDEWALK
SEPARATED FROM THE CURB BY A MINIMUM 8-FOOTWIDE LANDSCAPE STRIP, SUBJECT TO THE
FOLLOWING:

Staff Report: Z-T A-2-25-Y
May 1, 2025
Page 7
5.4.1. SINGLE-TRUNK, LARGE CANOPY SHADE TREES,
PLANTED 20 FEET ON CENTER OR IN
EQUIVALENT GROUPINGS, SHALL BE PROVIDED
ON BOTH SIDES OF THE SIDEWALK AND
PROVIDE A MINIMUM OF 75% SHADE. (T)
5.4.2 A MIXTURE OF SHRUBS, ACCENTS, AND
VEGETATIVE GROUNDCOVERS WITH A MAXIMUM
MATURE HEIGHT OF TWO FEET SHALL BE
DISTRIBUTED THROUGHOUT THE LANDSCAPE
AREAS TO ACHIEVE A MINIMUM OF 75% LIVE
COVERAGE. (T)
5.4.3 ALL EXISTING OVERHEAD UTILITIES WITHIN THE
RIGHTS-OF-WAY ABUTTING THE DEVELOPMENT
SHALL BE PLACED UNDERGROUND, UNLESS
OTHERWISE APPROVED THROUGH A TECHNICAL
APPEAL. (T)
RATIONALE: AN ENHANCED STREETSCAPE HELPS TO
SOFTEN THE EDGE OF THE DEVELOPMENT OF A
LARGER NON-RESIDENTIAL USE.

5.5.

SHADE.
5.5.1. ALL ON-SITE PEDESTRIAN PATHWAYS SHOULD
BE SHADED A MINIMUM OF 75% BY A
STRUCTURE, LANDSCAPING, OR A
COMBINATION OF THE TWO. (P)
5.5.2 DEDICATED MULTI-USE TRAILS ADJACENT TO
THE SITE SHOULD BE SHADED A MINIMUM OF
50% AT TREE MATURITY. (P)
RATIONALE: ENHANCED PEDESTRIAN COMFORT
SHOULD BE PRIORITIZED ADJACENT TO AND WITHIN
DATA CENTER DEVELOPMENTS ACROSS THE CITY.

***

Staff Report: Z-TA-2-25-Y
May 1, 2025
Page 8
Amend Chapter 6, Section 647 (Special Permit Uses), Section 647 .A.2 to add data
centers within the C-2 (Intermediate Commercial), C-3 (General Commercial),
CP/GCP (Commerce Park/General Commerce Park), A-1 (Light Industrial) and A-2
(Industrial) zoning districts, with performance standards to read as follows:
Section 647. Special Permit Uses.

•••
A.

Permitted uses. There shall be permitted, in addition to the uses enumerated in
the several use districts, certain additional uses subject to the requirements of this
section.

•••
2.

A special permit may be granted by the Council upon recommendation of
the Commission to establish the following uses in the use districts named:
***
KK.

DATA CENTERS IN THE C-2, C-3, CP/GCP, A-1 AND A-2 ZONING
DISTRICTS, SUBJECT TO THE FOLLOWING:
(1)

THE DEVELOPMENT SHALL BE NO CLOSER THAN 2,640
FEET FROM AN APPROVED HIGH-CAPACITY TRANSIT
STATION.

(2)

PRELIMINARY SITE PLAN APPROVAL WILL NOT BE
GRANTED FOR A DATA CENTER UNTIL SUCH TIME
THAT A LOCAL UTILITY COMPANY CONFIRMS IN
WRITING WITH A "WILL-SERVE" LETTER THAT IT CAN
SERVE THE ENERGY DEMAND WITHIN TWO YEARS
FOR THE PROPOSED DATA CENTER. THE LETTER
FROM THE UTILITY COMPANY SHALL BE SUBMITIED
TO POD CONCURRENT WITH THE PRELIMINARY SITE
PLAN.

(3)

THE FOLLOWING SHALL APPLY WHEN THE SITE IS
LOCATED WITHIN 300 FEET OF A RESIDENTIAL ZONING
DISTRICT:

Staff Report: Z-TA-2-25-Y
May 1, 2025
Page 9

(4)

~

PRELIMINARY SITE PLAN APPROVAL FOR A DATA
CENTER SHALL NOT BE GRANTED UNLESS IT
HAS BEEN DEMONSTRATED THAT THE DATA
CENTER, INCLUDING ALL ON-SITE MECHANICAL
EQUIPMENT AND FACILITIES, WILL NOT EXCEED
THE EXISTING AMBIENT NOISE LEVEL FOR THE
SITE BY MORE THAN 5%. (T)

{Q1

TO DETERMINE COMPLIANCE WITH THE PRIOR
SUBSECTION, THE DEVELOPER SHALL SUBMIT A
NOISE STUDY TO POD PRIOR TO OR
CONCURRENT WITH THE PRELIMINARY SITE
PLAN. THE NOISE STUDY SHALL BE
PERFORMED BY A THIRD-PARTY ACOUSTICAL
ENGINEER TO DOCUMENT BASELINE NOISE
LEVELS IN THE AREA OF THE PROPOSED DATA
CENTER, INCLUDING NOISE LEVELS MEASURED
AT THE PROPERTY LINE OF THE NEAREST
RESIDENTIAL ZONING DISTRICT TO THE
PROPOSED DATA CENTER PROPERTY.

{g

UPON APPROVAL OF THE NOISE STUDY, THE
METHODS PROPOSED TO MITIGATE NOISE
SHALL BE STIPULATED AS A CONDITION OF
FINAL SITE PLAN APPROVAL. A FINAL
CERTIFICATE OF OCCUPANCY SHALL NOT BE
ISSUED IF THE AMBIENT NOISE EXCEEDS THE
PRIOR EXISTING NOISE LEVEL BY MORE THAN
5%.

THE DEVELOPMENT IS SUBJECT TO ALL APPLICABLE
DESIGN GUIDELINES SET FORTH IN SECTION 507 TAB
A, INCLUDING THOSE FOR SECTION II.D.5, DATA
CENTERS.

***

DocuSign Envelope 10. A7E42978-D6B749C6-A7BD·F602DBAB151F

ORDINANCE NO. 5033
AN ORDINANCE OF THE CITY COUNCIL OF THE CITY OF CHANDLER,
ARIZONA, AMENDING ARTICLES II. DEFINITIONS, AND XXII.
ADDITIONAL HEIGHT AND AREA REGULATIONS OF CHAPTER 35 OF
THE CITY CODE OF THE CITY OF CHANDLER, RELATING TO OATA
CENTERS.
WHEREAS, in accordance with A.R.S. 9-462, the legislative body may adopt by ordinance, any
change or amendment to the regulations and provisions as set forth in the Chandler Zoning Code;
and
WHEREAS, this amendment, including the draft text, has been published as an 118-page display
ad in a local newspaper with general circulation in the City of Chandler, giving fifteen ( 15) days'
notice of time, date and place of public hearing; and
WHEREAS, a public hearing was held by the Planning and Zoning Commission as required by
the Zoning Code, on October 19, 2022.
NOW, THEREFORE, BE IT ORDAINED by the City Council of the City of Chandler, Arizona,
as follows:
Section 1.

Section 35-200, of Article II. Definitions, of Chapter 35 of the City Code of the
City of Chandler, is hereby amended by adding the following defmition:

Data Center: A facility or portion of a facility housing networked computer
systems and telecommunications equipment used for remote storage, processing,
and distribution of data.
Section 2.

Section 35-2214, of Article XXII. ADDITIONAL HEIGHT AND AREA
REGULATIONS, of Chapter 35, of the City Code of the City of Chandler, is
hereby added to read as follows:
35-2214. Data Centers.
(I) Data Centers are not permitted to operate in the City of Chandler unless
explicitly approved as part of a Planned Area Development zoning
district. Data Centers that are ancillary to another primary use are
permitted if they a) occupy no more than ten percent of the building
footprint, b) are used to serve the enterprise functions of the on-site
property owner and are not used to lease data storage and processing
services to third parties, and c) are not housed in a separate stand-alone
structure on the parcel.
(2) Before a Data Center is constructed within a Planned Area
Development zoning district, the property owner proposing to build a
Data Center must comply with the following:

DocuSign Envelope 10: A7E42978-D6B7-49C6-A7BD-F602DBAB151F

Ordinance No. 5033
Page2
a. The Data Center operator or property owner must notify residents
within a half-mile radius of the parcel, including any affiliated
homeowners' association operating within the half-mile radius,
that the property owner intends to build and operate a Data Center
on the property. The notice required in this section must be mailed
to all postal addresses and homeowners' association addresses
contained within a half-mile radius extending from the property
line where the proposed Data Center will be built.
b. The Data Center operator must schedule and attend two
neighborhood meetings with residents to describe the project and
the proposed sound-mitigation aspects of the project design. Notice
of the neighborhood meetings must be mailed to all residents and
homeowners associations within a half-mile radius of the parcel. A
representative of the developer or owner with decision-making
authority on the design of the Data Center must attend the
neighborhood meetings. The Data Center operator or property
owner must also post a sign on the subject property, at least fifteen
days before each neighborhood meeting, in accordance with design
standards specified in Section 35-2601.1. The sign must be located
along an arterial street or other high-visibility location as reasonably
determined by the Zoning Administrator. The content of the sign
shall (i) be consistent with the City's generally applicable sign
guidelines for posting signs for notification of neighborhood
meetings, (ii) include the applicant name and contact information,
a brief description of the Data Center project, and the date, time,
and location of the neighborhood meeting, and (iii) must be
reviewed and approved by the Zoning Administrator before
installation. The applicant must remove the sign at the conclusion
of the citizen review process.
(3) Upon request by City staff after issuance of a certificate of occupancy
and commencement of the operation of the Data Center, the operator
of a Data Center must provide an on-site neighborhood liaison between
the hours of 8:00 am and 10:00 pm MST each day to respond to
complaints about noise emanating from the Data Center.
(4) Before the first neighborhood meeting is held, the property owner
proposing to build a Data Center must conduct a sound study
performed by a third-party acoustic engineer to document baseline
sound levels in the area of the proposed Data Center, including noise
levels measured at the property line of the nearest property to the Data
Center property that is planned or zoned for residential land uses, or
other noise sensitive use as reasonably determined by the Zoning
Administrator. The property owner must provide a copy of the results
of the study to the City before the first neighborhood meeting.
(5) The Data Center must be designed and built to incorporate sound
mitigation methods sufficient to prevent the sound levels emanating
from the Data Center (as determined by a third-party acoustic

DocuSign Envelope 10 A7E42978·06B7-49C6-A7BD·F602DBAB151 F

Ordinance No. 5033
Page 3
engineer) from exceeding the ambient noise levels that were observed
in the baseline study. Design specifications for such sound mitigation
must be provided to the City before building permit approval.
(6) Upon issuance of a certificate of occupancy or certificate of
completion, whichever occurs first, the Data Center operator must
conduct a noise study performed by a third-party acoustical engineer
to document noise levels emanating from the Data Center measured at
the property line of the nearest property to the Data Center property
that is planned or zoned for residential land uses, or other noise
sensitive use as reasonably determined by the Zoning Administrator
during peak operation of the Data Center mechanical equipment. The
Data Center operator must also conduct an additional noise study, as
measured at the property line of the nearest property to the Data Center
property that is planned or zoned for residential land uses, or other
noise sensitive use as reasonably determined by the Zoning
Administrator, annually during peak operation of the Data Center
mechanical equipment for five years after completion of the initial
post-construction noise study. The Data Center operator must provide
the results of the noise study to the City within thirty days of the
anniversary of the date on which the certificate of occupancy or
certificate of completion was issued by the City.
(7) If the Data Center operator intends to use backup power generators on
the parcel, the operator must maintain a public website announcing the
times when the generators will be in operation. Any routine operation
of the backup generators, including for testing purposes, must be
announced on the website at least twenty-four hours in advance. The
operator shall also notify the City of Chandler Communications and
Public Affairs Department at least 24 hours in advance of a test. Unless
the generators are supplying backup electrical supply during a power
outage, backup generators may operate between the hours of 9:00 am
and 5:00 pm, Monday through Friday, excluding holidays. Upon
request by City staff, the Data Center operator must provide the address
of the website where the notices required by this section are published.
Section 3.

Providing for Repeal of Conflicting Ordinances.
All ordinances or parts of ordinances in conflict with the provisions of this
ordinance, or any parts hereof, are hereby repealed.

Section 4.

Providing for Severability.
If any section, subsection, sentence, clause, phrase, or portion of this ordinance
is for any reason held to be invalid or unconstitutional by the decision of any court
of competent jurisdiction, such decision shall not affect the validity of the
remaining portions thereof.

DocuSign Envelope ID: A7E42978-D687-49C6-A7BD-F602DBAB151F

Ordinance No. 5033
Page4
INTRODUCED AND TENTA TlVEL Y APPROVED by the City Council of the City of
Chandler, Arizona, this 5
day of December
2022.
ATTEST:

MAYOR

CITY CLERK

PASSED AND ADOPTED by the City Council of the City of Chandler, Arizona, this 8
of December
, 2022.

day

ATTEST:

MAYOR

CITY CLERK

CERTIFICATION
I HEREBY CERTIFY that the above and foregoing Ordinance No. 5033 was duly passed and
adopted by the City Council of the City of Chandler, Arizona, at a regular meeting held on the
8
day of December
, 2022, and that a quorum was present thereat.

CITY CLERK
APPROVED AS TO FORM:

CITY ATTORNEY

1A

Published in the Arizona Republic on: December 16, and December 23, 2022.
*REFERENCED EXHIBIT(S) AND/OR ATTACHMENT(S) ON FILE AT THE CITY CLERK'S OFFICE.*

ADOPTED BY THE
MAYOR AND COUNCIL ON
August 5. 2026

ORDINANCE NO 12268

RELATING TO PLANNING AND ZONING; AMENDING THE TUCSON CODE,
CHAPTER 238, UNIFIED DEVELOPMENT CODE, SECTIONS 4.9.11, and 11.3.11; AND
SETTING AN EFFECTIVE DATE.

WHEREAS, the City of Tucson has experienced increasing interest in the
development of large-scale data centers, which present unique characteristics and
potential impacts not adequately addressed by the use and development standards
currently set forth in the Unified Development Code; and

WHEREAS, the Mayor and Council find that the establishment of specific zoning
standards for large-scale data centeFs •s necessary to protect the public health, safety,
and welfare of Tucson residents, and to ensure compatibility between such development
and surrounding land uses through an appropriate approval pathway; and

WHEREAS, in August 2025 the Mayor and Council held a study session to direct
City staff to revise relevant portions of the Unified Development Code (UDC) in order to
develop zoning regulations for large-scale data centers; and

WHEREAS, the Planning Commission held a publicly noticed meeting on the
proposed text amendment on June 3, 2026, and voted 6-2 on a motion to forward a
recommendation of approval to the Mayor and Council on the proposed regulations for
large-scale data centers; and,

WHEREAS, Because the motion received six and not seven concurring votes, the
Planning Commission did not make a formal recommendation of approval or denial on
the proposed code amendment to Mayor and Council as required in Rule IV(K) of the
Rules of Procedure of the Planning Commission 6; and
WHEREAS, the City of Tucson acting through public meetings and hearings,
citizen participation and in conjunction with the Planning Commission, a Technical
Advisory Committee, and various other stakeholders, City staff have conducted a
complete review of, and amendments and revisions to, the UOC at Articles 4, and 11;
BE IT ORDAINED BY THE MAYOR AND COUNCIL OF THE CITY OF TUCSON,
ARIZONA AS FOLLOWS:
SECTION 1. The Tucson Code, Chapter 238, Unified Development Code, Article
4, Zones, Section 4.9, Use Specific Standards, is hereby amended to read as follows:

UNIFIED DEVELOPMENT CODE
ARTICLE 4, ZONES
SECTION 4.9.11, UTILIITES USE GROUP
4.9.11. UTILITIES USE GROUP

***
D. Large-Scale Data Centers
1. The Large-Scale Data Center site shall be located a minimum of:
a. 2,640 feet (one-half mile) from the following residential zones: RX1, RX-2, MH-1, MH-2, R-1, R-2, and R-3.
b. 2,640 feet (one- half mile) from all educational and residential uses,
or similar uses as determined by the Zoning Administrator.
c. 1,000 feet from all commercial and office zones.
d. Other uses such as natural areas, riparian corridors, or open space
may warrant a separation distance of up to 2,640 feet (one-half
mile), as determined by the Zoning Administrator in consultation

2

with other City of Tucson staff based on review of the required
Environmental Resource Report.
2. A Large~Scale Data Center shall not exceed 50 feet in height.
3. Sound
a. Facility must comply with Section 16~31, Excessive Noise, of the
Tucson Code.
b. Baseline noise study and noise contour exhibits are required as
part of the application. The study is to be signed and sealed by an
independent acoustic engineer and shall address both decibels
and frequency, including infrasound.
c. Sound blocking and screening for generators and other noise~
producing mechanical equipment are required through solid
screened walls or rooftop screening.
d. A noise mitigation plan is required with the submittal of a building
permit application that demonstrates compliance with the following
minimum standards:
1. Proposed generators must be for backup use only, with a
preference for low-emitting (less than or equal to 100kg
C02e/kW} models. Where high-emitting generation is
proposed, only Tier IV, or natural gas I dual fuel generators
are permitted.
2. Backup energy shall be provided by a combination of
generators and batteries~Storage must be sized to provide
2~hours of typical data center operations. Storage and lowemitting backup generators must be used prior to high~
emitting generators to support data center operations when
disconnected from the grid.
3. Ability to disconnect electrical load from the grid system at
the request of the servicing electric utility.
4. Certification that generator operation will occur only at the
request of the electric utility, during grid instability or power
outages or for preventive maintenance and periodic testing.
5. Certification that non-emergency maintenance operations
will be limited to 9 am - 5 pm MST, Mondays through
Fridays.
6. Upon request by City staff after issuance of a certificate of
occupancy and commencement of the operation of the data
center, the operator of a data center must provide an on~site
neighborhood liaison to be available between the hours of
8:00 am and 10:00 pm Mountain Standard Time (MST) each
3

day to respond to complaints about noise emanating from
the Data Center.
4. Certification of access to an adequate energy supply and documentation
of the proposed energy mix, including what renewable energy sources are
being utilized, is required at the time of application submittal.
5. Water
a. Certification of access to an adequate water supply is required at
the time of application submittal.
b. Development must comply with the Large Quantity Water Users
Ordinance, if applicable. If not applicable, the use of potable water
for data center cooling is prohibited.
6. Enhanced landscape borders (per UDC Section 7.6.4.) of 40 feet are
required.
7. An Environmental Resource Report (ERR) is required. The ERR shall
identify the most appropriate area for development. Lot coverage is limited
to 40% and the remaining land area shall be dedicated as natural open
space and reserved in perpetuity, unless an offsite mitigation plan with a
minimum 2 to 1 offset of land area is approved through the PAD/PCD.
Salvage of native plants shall be permitted on the development area. Any
disturbed area shall be revegetated with native plants.
8. No minimum parking is required. Applicant shall submit a parking
statement justifying the amount of parking needed for the use.
Notice for all-required neighborhood meetings and public hearings shall follow Section
3.2.4 Public Notice. However, the requirements shall follow the Public Notice and
Procedural Requirements for a Rezoning to Establish a PCD (Table 3.2-1) which
requires notice to recipients within 2,640 feet (one-half mile) of the boundaries of the
proposed rezoning site and to all neighborhood associations within two miles of the
boundary.

***

SECTION 2.

The Tucson Code, Chapter 238, Unified Development Code,

Article 11, Definitions and Rules of Construction, Section 11.3., Definitions of Land Use
Groups, Classes, and Types, is hereby amended to read as follows:

4

UNIFIED DEVELOPMENT CODE
ARTICLE 11: DEFINITIONS AND RULES OF CONSTRUCTION
SECTION 11 .3.11. UTILITIES USE GROUP

The Utilities Use Group includes Land Use Classes that involve the generation,
transmission, and/or distribution of basic services, such as sanitation, water, gas,
and electrical services. The following Land Use Classes constitute the Land Use
Group.

F. Large-Scale Data Centers
Any facility, multiple facilities, or portion of a facility on a contiguous site, and a gross
floor area greater than 25,000 square feet or uses greater than 20 megawatts (MW) of
energy, housing networked computer systems and/or telecommunications equipment
used for remote storage, processing, and distribution of data. Large·Scale Data Centers
are permitted through adoption or major amendment of a Planned Area Development
(PAD) or a Planned Community Development (PCD) and are subject to Use Specific
Standards 4.9.11.0.

•••
SECTION 3. If any provisions of this Ordinance, or of its application to any
person or circumstance is declared invalid or unenforceable, as determined by a court
of competent jurisdiction, the invalidity or unenforceability shall not affect other
provisions or applications of this Ordinance which can be given effect without the invalid
provision or circumstance, and to this end, the provisions of this Ordinance are
severable.

II
II
II
II
5

SECTION 4. This Ordinance becomes effective thirty (30) days after it is adopted
by the Mayor and Council and is available from the City Clerk.
PASSED, ADOPTED, AND APPROVED by the Mayor and Council of the City of
Tucson, Arizona, August 5. 2026.

ATTEST:

Cl~
REVIEWED BY:

APPROVED AS TO FORM:

CITY A
JA!tt
0712212026

6

Tempe, AZ Zoning and Development Code

9/7/26, 6:36AM

Section 3-429 • Data Centers.

A. Purpose and Applicability. the purpose of this section is to allow data centers in areas that limit
the impact of identified innovation hubs and rail corridors where job employment growth and
commerce are desired. sustainability measures are addressed through appropriate land
planning, energy and water consumption are mitigated through Infrastructure evaluation, and
design standards adopted to mitigate noise levels. data centers are allowed in the mu-ed. gid and
hid zoning districts only, subject to approval of a use permit, pursuant to sectjon 6-308.

B. Location Requirements.
1. Data center buildings shall not be located within 500 feet of the property line of a site
containing a residential use or a residential district.

2. Generators for data centers shall be located within an enclosed building with necessary
ventilation to reduce impacts on noise to surrounding area.
C. Approval Criteria. in addition to such use complying with use permit approval criteria, section 6-

3.Qa (e), an economic impact study shall be submitted, for review by the economic development
director, or designee, to evaluate any potential impacts that limit locating a data center in either
an innovation hub or rail corridor intended to attract a high concentration of permanent
employment jobs and public consumers. data centers that are defined as an "extreme-water use"
shall also submit for review with the public works department, a water use plan, pursuant to the
tempe city code, section 33-142.
(Ord. No. 02025.23. 7 -1-2025)

aboutblank

111

Mesa, AZ municipal code

11-31-36: DATA CENTERS
A.

Applicability.

1.

Data Center as an Accessory Use. A Data Center that meets all of the criteria (a through c below) may
be considered an accessory use and is not subject to the requirements ofthis Section 11-31-36.
Accessory use criteria:

a.

The Data Center exclusively serves the enterprise functions of the on-site property owner or
tenant.

b.

The Data Center does not lease data storage or processing services to third parties.

c.

The Data Center occupies no more than 10% of the total gross floor area of all buildings on the
site.

2.

B.

C.

Data Center as a Principal Use. Data Center, as defined in Section 11-86-5, is prohibited in every
zoning district, except that a Data Center may be permitted in the Planned Area Development (PAD)
Overlay District that is used in combination with the General Industrial (GI) or Heavy Industrial (HI)
Base Zoning District only if the Data Center is specifically permitted by the City Council with the
approval of the rezoning to the subject PAD Overlay District. Additionally, all Data Centers as a principal
use shall be located, developed, and operated in compliance with the Land Use Regulations in Article 2
and the following standards.

Purpose. The purpose of this Section is to:

1.

Promote public health, safety, and general welfare by ensuring that potential adverse impacts from
Data Centers and their associated mechanical equipment, including impacts on the availability,
capacity, and distribution of utility services, including water, wastewater, gas, and electricity are
mitigated; and

2.

Minimize the phystcal, environmental, and visual impacts of Data Centers and their associated
mechanical equipment on surrounding areas by promoting high-quality design and ensuring
compatibility with adjacent land uses and the community.

Permitted Zoning Districts.

1.

PAD Overlay District Required. A Data Center may be permitted within a PAD Overlay District when
applied in combination with the General Industrial (GI) or Heavy Industrial (HI) Base Zoning Districts,
but only if specifically authorized by the City Council as part of the PAD Overlay District approval.

2.

Data Center as an Accessory Use. A Data Center may be permitted as an accessory use in the
Commercial and Employment Zoning Districts without requiring a PAD Overlay District and is not
subject to the requirements of this Section 11-31-36.

D.

Relation to Other Regulations. Where a conflict occurs between the provisions of this Section and any other
City Code, ordinance, resolution, or regulation, the more restrictive provision shall control.

E.

Application Requirements. In addition to the application requirements of Section 11-67-2 and application
guides posted on the Development Services website, all development applications for a Data Center shall
include all the following:

1.

Project Narrative. A project narrative that describes how the Data Center is consistent with the
General Plan, any other applicable City plan or policies, and is compatible with surrounding uses.

2.

Operational Plan. An operational plan that provides evidence of compliance with all zoning, building,
and fire safety regulations.

Created: 2826-88·83 11:19:48 (ESTJ

(Supp. No. 22)

Page 1 of 8

Mesa, AZ municipal code

3.

4.

Good Neighbor Policy. A good neighbor policy describing all the following :

a.

The measures that will be taken to ensure ongoing compatibility with adjacent uses including
sound attenuat ion, lighting control measures, vehicular access and traffic control, and litter
control measures.

b.

Complaint response procedures, including the name and telephone number of the person
responsible for the operation of the facility; and procedures for investigation, remedial action,
and follow-up.

Water Consumption and Thermal Management Report. A water consumption and thermal
management report which describes all the following:

a.

Cooling System. The proposed cooling system for the Data Center and whether the Data Center
will be water cooled or air-cooled.

b.

Water Usage.

i.

The estimated amount of total water in acre feet that will be used by the proposed project
and associated land use for a calendar year, along with a monthly breakdown of projected
water demand for each month within that year.

ii.

The estimated amount of water in million gallons per day that will be used by the proposed
project during a typical 24-hour operational period under normal conditions, including
anticipated usage patterns.

iii.

The estimated amount of water in million gallons per day to be used by the proposed
project in a 24-hour period on its highest water consumption day.

iv.

The estimated highest instantaneous flow rate in million gallons per day that will be used
by the project along with the minimum, average, and maximum durations and frequencies
of these flow conditions.

v.

Indicate high consumption operational flexibility. Identify if high water demands can be
aligned with the City's low-demand periods.

vi.

The number of the proposed water meters and the size of each water meter for the
proposed project.

vii.

Proof that the applicant or property owner submitted a complete Sustainable Water
Service Application to the City's Water Resources Department.

S.

Wastewater Report. Proof that the applicant or property owner submitted a complete Industrial User
Survey, or its equivalent under City Code Title 8, Chapter 4 (Sanitary Sewer Regulations) to the City's
Water Resources Department.

6.

Electric and Natural Gas (Energy) Service Report. If located in the City's service area for electric or
natural gas utility services:

7.

a.

The estimated annual and monthly demand for electric and natural gas utility services.

b.

An assessment of future energy needs for the proposed project.

Initial Sound Study. An initial sound study performed by a third-party acoustical consultant which
documents all the following :

a.

The baseline sound levels on the project site.

Cre~ted :

(Supp. No . 22)
Page 2 of 8

24U6·88·8J 11 :19:48 (EST]

Mesa, AZ municipal code

b.

8.

Citizen Participation. In addition to the Citizen Participation requirements of Section 11-67-3, all the
following Citizen Participation measures are required:

a.

b.

c.

F.

The baseline sound levels measured at the property line of the nearest Residential Zoning
District, residential use, or other sensitive uses as reasonably determined by the Planning
Director.

Neighborhood Meeting.
i.

The applicant shall hold a minimum of two (2) neighborhood meetings with residents to
describe the project, including the project design, proposed sound-mitigation, lighting
control measures, vehicular access and traffic control, and litter control measures.

ii.

A representative of the developer or owner with decision-making authority on the design
of the Data Center shall attend the neighborhood meetings.

Neighborhood Meeting Notification.

i.

Moiled Notice. The applicant shall notify all property owners and homeowners' associations
within a half-mile radius of the exterior boundary of the property that is the subject of the
application, based on the last assessment.

ii.

Notice Timefrome. Written notice shall be provided by first class mail a minimum of 15days prior to each neighborhood meeting.

Site Posting.
i.

The applicant shall post a sign on the proposed Data Center site at least 15-days before
each neighborhood meeting.

ii.

The sign shall be located along an arterial street or other high-visibility location as
reasonably determined by the Planning Director.

iii .

The sign shall include all the following content and shall be reviewed and approved by the
Planning Director before installation:
(1)

The applicant name and contact information.

(2)

A brief description of the Data Center project.

(3)

The date, time, and location of the neighborhood meeting.

(4)

The applicant shall remove the sign after the neighborhood meeting(s), but not
sooner.

Development Standards.
1.

Modifications and De11iatlons Not Permitted. The development standards contained within this
Section and the development standards contained within Chapter 7 of the Zoning Ordinance, when
applied to a Data Center, may not be modified through a Planned Area Development (PAD) Overlay,
Bonus Intensity Zone (BIZ) Overlay, Alternative Compliance, or Special Use Permit (SUP), except for the
maximum building height specified in Subsection (3) below.

2.

Separation from Residentiolloning Districts and Residential Uses. A Data Center and all associated
mechanical equipment, including but not limited to battery storage, power generation, cooling,
ventilating, or other equipment that supports the Data Center, shall be located at least 400 feet from
the property line of the nearest Residential Zoning District, residential use, or other sensitive use as
reasonably determined by the Planning Director.

3.

Height. The maximum height of a Data Center, including all associated equipment, is 60 feet.

C•eated: 2&26·&8·&1 11:19:48 (EST)

(Supp. No. 22)

Page 3 of8

Mesa, AZ municipal code

4.

5.

Building Placement and Design. In addition to the development standards contained within Chapter 7
of the Zoning Ordinance, a Data Center shall adhere to all the following standards:
a.

Quality Development Design Guidelines. Be designed in compliance with Chapter 5 of the City's
Quality Development Design Guideltnes.

b.

Orientation. The Data Center's primary (front) fa~ade shall be oriented towards adjacent arterial
roadways and intersections.

c.

Building Design Based on Sound Study.

i.

Based on the results of the initial sound study, the Data Center shall be designed and built
to incorporate sound mitigation methods sufficient to prevent the sound levels emanating
from the Data Center (as determined by a third-party acoustical consultant) from
exceeding the ambient noise levels at the property line of the nearest Residential Zoning
District, residential use, or other sensitive use as determined by the Planning Director that
were observed in the baseline study.

ii.

Design specifications for such sound mitigation shall be provided to the City and
incorporated into the building design before building permit approval.

Architectural Design. In addition to the requirements of Chapter 7 of the Zoning Ordinance, a Data
Center shall adhere to all the following standards:

a.

Quality Development Design Guidelines. Be designed in compliance with Chapter 5 of the City's
Quality Development Design Guidelines.

b.

All Side Architecture. Architectural detailing on fa~ades may vary depending on visibility and
orientation. However, all fa~ades that are publicly visible-whether from the street, neighboring
properties, or public vantage points-shall have architectural detailing equivalent to the primary
fa~ade.

c.

Multi-planar Fa~ades. In addition to the Site Planning and Design Standards of Chapter 7, a Data
Center shall include multi-planar fa~ades every 150 feet which are offset a minimum three (3)
feet vertically and horizontally from the main building fa~ade.

d.

Glazing Requirements. A Data Center building shall incorporate windows or glass panels on a
minimum of 40% of the front fa~ade and 15% on all other fa~ades.

e.

Architectural Features. Architectural features shall be integrated into the design of Data Center
buildings to create visual interest and establish a cohesive architectural identity-particularly at
entryways and areas of public interface. All buildings shall incorporate at least five (5) of the
following architectural features~

i.

Overhangs. Overhangs shall project a minimum three (3) feet from the building fa~ade.

ii.

Canopies. Canopies shall extend a minimum four (4) feet from the building fa~ade.

iii.

Arcades. Arcades shall provide a clear depth of six (6) feet and a minimum height of 10
feet.

iv.

Window Shrouds. Window shrouds shall project a minimum of six (6) inches around the
entire window frame.

v.

Raised Corniced Parapets Over Primary Entrances. Raised corniced parapets shall extend a
minimum of 18 inches above the adjacent roofline and six (6) inches horizontally from the
wall.

Cr&•ted: 2826·88·93 11:19:48 (EST)

(Supp. No. 22)
Page 4 of 8

Mesa, AZ municipal code

vi.

Tower Elements. Tower elements shall be either one (1) story taller than the adjacent
massing.

vii.

Frameless Corner Glass. Each glass wall shall be a minimum eight (8) feet wide, with a
seamless corner radius or joint.

viii.

Flying Roof Forms. Roofs elements shall have a slope of at least 15 degrees and project a
minimum four (4) feet beyond the main wall.

ix.

Murals. Murals shall encompass an area of SO square feet.

x.

Decorative Architectural Grilles, Laser·Cut Metal Screens, or Louvres. Decorative
architectural grilles, laser-cut metal screens, or louvres shall be a minimum four (4) feet
wide or 12 square feet in area.

xi.

Architectural Lighting. Architectural lighting shall illuminate at least 25% of the primary
fa~ade length or highlight a minimum of three (3) distinct architectural components.

xii.

6.

7.

8.

Other architectural feature approved by the Planning Director.

Truck Docks, Loading, and Service Areas.
a.

Truck docks, loading, and service areas shall not face or be visible from public rights-of-way or
residential uses.

b.

When possible, bufldings should be used to screen truck docks, loading, and service areas.

c.

Where building locations do not offer screening or in the case of phased development plans,
truck docks, loading, and service areas shall be fully screened by a solid masonry wall at least
eight (8) feet in height.

Fences and Freestanding Walls. In addition to the development standards of Section 11-30-4, Data
Centers shall adhere to all the following standards:
a.

Architectural Compatibility. Walls and fences shall be designed to complement the architectural
style of the Data Center and surround ing development.

b.

Articulation. Walls and fences shall be articulated every 40 feet through the use of either of the
following:
i.

A column that is offset a minimum eight (8) inches from the horizontal plane of the wall or
fence and extends a minimum eight (8) inches above the main body of the wall or fence.

ii.

A landscape pocket which is three (3) feet deep by five (S) feet wide.

c.

Decorative Cap. All wall or fence columns shall have a decorative cap.

d.

Prohibited Materials.
i.

The use of barbed wire, razor wire, embedded glass shards, or ultra barrier is prohibited.

ii.

The use of chain link or electrified fencing may only be used for internal security purposes
and shall be fully screened from public view.

Mechanical Equipment. Mechanical equipment, including but not limited to battery storage, power
generation, cooling, ventilating, or other equipment that supports the Data Center, shall adhere to all
the following standards:

a.

Screening. Be screened to reduce visual and noise impact using one (1) or more of the following
methods:

Crnted: 2826-88·81 11:19:48 {EST]

(Supp. No. 22)
Page 5 of 8

Mesa, AZ municipal code

9.

Integrated into the building architecture and screened by a wall that appears as a natural
extension of the building.

ii.

With a solid masonry wall at least eight (8) feet in height or tall enough to fully screen the
tallest piece of equipment.

b.

Location. Be located away from primary entrances, public-facing fa~ades, residential uses or
zoning districts, private or public roadways, and when possible, at the rear or side of the building.

c.

Architectural Consistency.
i.

Screening elements shall be designed as a seamless extension of the Data Center's
architecture, avoiding exposed industrial-looking enclosures.

ii.

Screening elements shall use materials and colors that match the primary Data Center
building.

Substation Screening.

a.

b.

10.

i.

Height.

i.

Substations, whether private or public, shall be screened to a height at least one (1) foot
above the tallest piece of ground-mounted equipment.

ii.

If the required screen wall exceeds 10 feet in height, vertical articulation is permitted,
provided that:
(1)

A line of-sight study demonstrates that the tallest piece of groundmounted
equipment is fully screened from public viewpoints at multiple angles; and

(2)

The vertical modulation does not exceed 15% of the wall's total height.

Enclosure Design. Substations, whether private or public, shall be screened using walls, fencing,
berming, landscaping, or other alternative methods.
i.

Screen Walls 10 Feet in Height or Shorter. Substation screen walls that are 10 feet in height
or shorter shall comply with the development standards in Section 11-31-16(F)(7) and
Section 11·30·4 for Fences and Freestanding Walls, and be designed to match any
proposed publicly facing wall within the development.

ii.

Screen Walls Greater than 10 Feet in Height. Substation screen walls greater than 10 feet in
height shall :
(1)

Consist of a 10-foot solid masonry wall that uses materials and finishes that
match any proposed publicly facing wall within the development; and

(2)

A decorative louvered, slated, or perforated upper screen, no more than 75%
opaque, mounted above the masonry wall.

Utilities.
a.

The Data Center shall bear the full cost of undergrounding any adjacent or on-site electrical
infrastructure that would otherwise be provided via overhead distribution and/or transmission as
deemed necessary by the City of Mesa Development Services Department in its sole discretion
and approved by the applicable utility.

b.

When the Data Center is located within the City's electric or natural gas service territories, the
City may require a Data Center to source and transmit its own electric or natural gas commodity
to a point of the City's electric or natural gas system as determined in the City's sole discretion.

Creotod: 2t26·t 8· 8l 11:19:48 [EST)

(Supp. No. 221
Page 6 of 8

Mesa, AZ municipal code

c.

G.

The Data Center may be subject to other requirements from the applicable energy utility when
located outside of the City's electric or natural gas service territories.

Operational Requirements.
1.

Modifications and Deviations Not Permitted. The operational standards contained within this Section
may not be modified through a Planned Area Development (PAD) Overlay, Bonus Intensity Zone (BIZ)
Overlay, Alternative Compliance, Special Use Permit (SUP), Variance or otherwise.

2.

Sound Study at Certificate of Occupancy or Certlficote of Completion Stoge.

3.

4.

a.

Within 30 days of the issuance of a certificate of occupancy or certificate of completion,
whichever occurs first, the Data Center operator shall conduct a sound st udy performed by a
third·party acoustical consultant.

b.

The study shall document noise levels emanating from the Data Center measured at the property
line of the nearest Residential Zoning District, residential use, or other sensitive uses as
reasonably determined by the Planning Director, during peak routine operation of the Data
Center mechanical equipment.

Annuol Sound Study Required.
a.

The Data Center operator shall perform an annual sound study during peak routine operation of
the Data Center mechanical equipment for five (5) years after completion of the initial postconstruction sound study.

b.

The study shall document noise levels emanating from the Data Center as measured at the
property line of the nearest Residential Zoning District, residential use, or other sensitive uses as
reasonably determined by the Planning Director.

c.

The Data Center operator shall provide the results of the sound study to the City within 30 days
of the anniversary of the date on which the certificate of occupancy or certificate of completion
was issued by the City.

Backup Generators. If the Data Center operator intends to use backup power generators on the parcel,
the operator shall maintain a public website announcing the times when the generators will be in
operation.
a.

Any routine operation of the backup generators, including for testing purposes, shall be
announced on the website at least 24 hours in advance.

b.

The operator shall also notify the City of Mesa Public Information Office at least 24 hours in
advance of a test.

c.

Unless the generators are supplying backup electrical supply during a power outage or an electric
utility demand response event, backup generators may only operate between the hours of 9:00
a.m. and 5:00p.m., Monday through Friday, excluding holidays.

d.

Upon request by City staff, the Data Center operator shall provide the address of the website and
QR code where the notices required by this Section are published.

e.

Any generating systems that are capable of operating in parallel with the City of Mesa's electric
utility or in an islanded manner within the City of Mesa's electric utility will be subject to a
generator interconnection process and interconnection study. In all instances, the Data Center
operator shall be responsible for all interconnection costs and costs of distribution system
protection related to the operation of the generating system.

(Ord. No. 5957, § 3, 7-8-25)

c~.~~ed :

(Supp. No. 221
Page 7 of 8

2926· 98-U 11 :19:411 { EST]

Mesa, AZ municipal code

!Supp. No. 22)

Page 8 ~f8

917126, 8:20AM

ACC Approves Measure to Ensure Electric Cooperative Customers Don't Pay for Large-Load Growth

ACC Approves Measure to Ensure Electric Cooperative
Customers Don't Pay for Large-Load Growth
Aug 13, 2026, 10:17 by Nicole Garcia
Phoenix, Ariz . - The Arizona Corporation Commission voted unanimously during the August 12, 2026
Open Meeting to approve a joint application by several electric cooperatives that creates a streamlined
process to protect its existing ratepayers from the costs of new transmission and infrastructure
demands brought on by new large-load customers. Arizona Electric Power Cooperative, Inc.
(AEPCO), Duncan Valley Electric Cooperative, Inc., Sulphur Springs Valley Electric Cooperative, Inc,
Mohave Electric Cooperative, Inc., Graham County Electric Cooperative, Inc. and Trico Electric
Cooperative, Inc. (collectively, the "Distribution Cooperatives") collaborated on the application, which
would request ACC approval for electric service agreements between large-load customers, such as
data centers , and the cooperatives. This procedure supports the Commission's "Growth Pays for
Growth" approach when it comes to the addition of new large-load customers.
"This new large load process gives Arizona cooperative utilities, a clear standardized framework for
bringing data centers and large load users online while protecting existing ratepayers from bearing the
costs," said Chairman Nick Myers. "Large load customers are becoming increasingly interested in rural
areas of Arizona . This new process allows rural Arizona to capture the economic growth responsibly
without being subsidized by other customers of the utilities."
"I applaud our electric retail cooperatives for addressing the challenge of large load customers
interested in rural Arizona," said Commissioner Lea Marquez Peterson. "As we know, every
cooperative is structured a little differently and represent diverse communities across the state. It's
important that the process for onboarding large loads reflects this difference. I was proud to support
their effort to streamline their processes and to protect their members and ratepayers."
The Commission commended the Distribution Cooperatives for being proactive in helping to protect
the afford ability and reliability of service for their existing members. The Distribution Cooperatives say
they are in talks with several prospective large-load businesses looking to build new facilities in their
service territories, which would create the necessity for new electric service agreements between
AEPCO (the wholesale electricity provider), the Distribution Cooperatives (the electric retail company)
and the large load customer (the retail customer).
The proposed process for establishing prospective large-load service agreements would adhere to a
common set of guidelines, a checklist of application requirements that the Commission would
ultimately approve, deny or amend . The Commission's Utilities Division Staffs review of the
application will include at a minimum three criteria : whether the agreement is in the public interest,
whether the rates charged are reasonable, and whether the agreement ensures that no other
customer class of AEPCO or the Distribution Cooperatives subsidizes the customer's commercial
activities.
"As we confirmed in our meeting, large load customers will be required continue to cover all costs
associated with commercial services under this framework, including new infrastructure and
transmission construction," said Commissioner Kevin Thompson. "This further protects ratepayers
from potentially subsidizing costs attributed to serving "cost causers" such as manufacturing facilities
and data centers."
All documents related to this application can be found in the ACC's
eDocket b!lps :/ledocket.azcc.g~ under Docket No. E-01773A-26-0123.

https://azcc.gov/newslhome/2026/08113/acc-approves-measure-to-ensure-electric-cooperative-customers-don-t-pay-for-large-load.growth

1/1