1
00:00:05,440 --> 00:00:12,400
All right, good evening everyone. Thank
you so much for being here. We really

2
00:00:09,519 --> 00:00:17,600
appreciate you spending some of your
evening and your time to engage on this

3
00:00:15,120 --> 00:00:21,279
important community topic.
My name is Corin Manning. I'm the

4
00:00:19,600 --> 00:00:25,519
director of the department of planning
and development services for the city of

5
00:00:23,199 --> 00:00:30,560
Tucson. And I want to introduce some of
the team who will be here tonight to

6
00:00:27,760 --> 00:00:33,920
present on this topic. Um, we have
Carver Stru, principal planner with

7
00:00:32,559 --> 00:00:38,640
planning and development services,
Nicholas Martell, our long-range

8
00:00:36,079 --> 00:00:43,440
planning section manager, Dan Bersik,
planning administrator, as well as

9
00:00:40,800 --> 00:00:48,239
Tonnie Robertson, our facilitator for
this evening, here to support the

10
00:00:45,440 --> 00:00:54,960
conversation and dialogue. Uh, so
tonight's meeting is about regulations

11
00:00:51,200 --> 00:00:57,680
for largecale data centers. Um, this is
a really important topic that's

12
00:00:56,399 --> 00:01:01,600
generated a lot of community
conversation. So, we're really here to

13
00:01:00,000 --> 00:01:06,479
share information and have an
opportunity for feedback and discussion

14
00:01:03,440 --> 00:01:10,880
tonight. Um, so data centers are a
rapidly evolving technology. They're

15
00:01:08,320 --> 00:01:16,000
really new emerging use and our
responsibility as a city is to make sure

16
00:01:13,600 --> 00:01:20,880
that our land use regulations keep pace
with emerging trends in a way that

17
00:01:18,560 --> 00:01:24,320
reflects our community's values and
priorities. So that's really what we're

18
00:01:22,479 --> 00:01:27,320
trying to do with these proposed
regulations.

19
00:01:32,240 --> 00:01:40,400
Okay. So how tonight will go, what we
are here to do. We're going to explain a

20
00:01:37,840 --> 00:01:43,920
little bit of background um why we're
here, how we got here in terms of

21
00:01:42,000 --> 00:01:46,960
developing these regulations, talk a
little bit about some existing city

22
00:01:45,439 --> 00:01:52,479
policy
um and existing regulations.

23
00:01:49,920 --> 00:01:56,240
um talk about the process so far to
develop regulations for large scale data

24
00:01:54,240 --> 00:02:00,719
centers um including our technical
advisory committee and then share an

25
00:01:58,799 --> 00:02:05,840
overview of the proposed regulations for
large scale data centers um and have

26
00:02:03,520 --> 00:02:10,239
opportunity for feedback along the way.
So tonight's meeting is really about

27
00:02:07,600 --> 00:02:15,280
sharing some information about what's
proposed and then most importantly

28
00:02:13,280 --> 00:02:19,280
hearing from all of you. So there's
going to be opportunity for feedback

29
00:02:16,959 --> 00:02:23,920
throughout the presentation and then at
the end we do want to have time for

30
00:02:21,599 --> 00:02:29,280
questions and answers. So we do ask that
during the presentation um we limit

31
00:02:27,200 --> 00:02:35,599
questions and comments to just
clarifying questions um so that at the

32
00:02:32,080 --> 00:02:40,560
end we can have some dialogue and Q&A
about this topic.

33
00:02:37,760 --> 00:02:44,959
Um and there's also going to be there's
um comment cards and other ways to get

34
00:02:42,239 --> 00:02:49,360
input as well. Um, we have already
gotten a lot of input and feedback on

35
00:02:47,280 --> 00:02:55,680
this topic. Um, and we've started
developing a Q&A FAQ uh, form that some

36
00:02:53,599 --> 00:02:59,280
of you may have gotten when you came in.
So, we've really tried to take a lot of

37
00:02:57,440 --> 00:03:03,120
the key questions and comments that
we're getting and start responding to

38
00:03:01,200 --> 00:03:07,840
those and we will be building out that
FAQ as we go through this process and

39
00:03:05,840 --> 00:03:12,319
get additional questions and comments.
So all of your feedback is being

40
00:03:09,440 --> 00:03:20,159
reviewed by staff and uh responded to
and integrated into the process.

41
00:03:16,480 --> 00:03:25,040
So how we got here? Um we are here based
on direction from our mayor council to

42
00:03:22,480 --> 00:03:30,000
establish guardrails for our community
related to large scale data centers.

43
00:03:27,840 --> 00:03:36,159
Following the consideration of the
project blue proposal, mayor and council

44
00:03:32,799 --> 00:03:42,879
gave us direction to establish guard
rails for our community to develop a

45
00:03:38,319 --> 00:03:48,480
regulatory framework for the for the use
uh of large scale data centers to

46
00:03:45,120 --> 00:03:53,680
protect Tucson and our resources and to
develop standards for this new use as

47
00:03:51,200 --> 00:03:58,159
well as a review process.
So throughout the discussion of project

48
00:03:55,440 --> 00:04:01,920
bloom, we heard a range of questions and
concerns about large scale data centers.

49
00:04:00,319 --> 00:04:08,720
We heard from residents about issues
such as water, energy use, noise, visual

50
00:04:05,200 --> 00:04:13,439
impacts, whole range of community
concerns and issues um which are very

51
00:04:11,040 --> 00:04:17,519
important topics and a conversation that
really affects our whole community and

52
00:04:15,200 --> 00:04:21,600
quality of life. That's why we're here
today to engage in this dialogue and

53
00:04:19,680 --> 00:04:26,639
have more conversation about the impact
of this use and how we can ensure that

54
00:04:23,919 --> 00:04:31,840
we have appropriate regulations in place
to regulate um this emerging use. As we

55
00:04:30,560 --> 00:04:36,160
were going through the project blue
discussion, we found that our zoning

56
00:04:33,440 --> 00:04:40,800
code does not currently have data
centers as a clearly defined land use.

57
00:04:38,720 --> 00:04:45,600
So we don't have regulations for this
type of use. This creates a lack of

58
00:04:43,600 --> 00:04:49,759
clarity for our community, creates
uncertainty for neighborhoods, for our

59
00:04:47,120 --> 00:04:54,880
policy makers, um, and for potential
applicants. So, what we're trying to do

60
00:04:52,160 --> 00:05:00,720
now is take a more proactive approach to
develop these regulations and guard

61
00:04:56,720 --> 00:05:05,600
rails. Um, so rather than reacting to a
specific proposal, we're here trying to

62
00:05:03,440 --> 00:05:10,639
establish clear and enforceable
guidelines um, in advance of future

63
00:05:08,160 --> 00:05:15,840
proposals. So what we're trying to do is
create clear standards that protect our

64
00:05:13,199 --> 00:05:21,360
neighborhoods, our natural resources,
and provide predictability so that if a

65
00:05:19,039 --> 00:05:26,880
data center facility is proposed, we
have an appropriate set of land use

66
00:05:23,440 --> 00:05:31,440
regulations and standards to evaluate a
proposed development.

67
00:05:29,520 --> 00:05:35,919
Based on the direction from mayor
council, we have done a quite a bit of

68
00:05:33,520 --> 00:05:39,919
research into data center regulations in
other communities as well as the impact

69
00:05:37,600 --> 00:05:44,320
of data centers in other communities and
we established a technical advisory

70
00:05:41,840 --> 00:05:49,039
committee to help inform the proposed
standards that we're creating. We also

71
00:05:46,560 --> 00:05:53,199
developed a large quantity water users
ordinance in the city. That was actually

72
00:05:50,560 --> 00:05:57,919
something that was in progress um prior
to the project blue discussion and that

73
00:05:54,960 --> 00:06:02,400
has been adopted by the city um and is
being refined now based on public input.

74
00:06:00,479 --> 00:06:06,240
That ordinance is meant to work in
parallel with these proposed zoning

75
00:06:04,319 --> 00:06:10,080
regulations for large scale data centers
and we'll share a bit more about that a

76
00:06:08,080 --> 00:06:13,919
little later on. So again, tonight's
meeting is not to discuss a specific

77
00:06:11,919 --> 00:06:18,319
proposal. The discussion tonight is
about setting guard rails and

78
00:06:16,000 --> 00:06:23,360
establishing standards for our community
so that if a proposal comes forward, we

79
00:06:20,880 --> 00:06:28,720
have conditions and a process in place
to evaluate any proposals.

80
00:06:26,960 --> 00:06:32,880
So, I want to talk a little bit more
about zoning regulations because zoning,

81
00:06:31,759 --> 00:06:38,000
which is what we're here to talk about
tonight, is just one piece of a larger

82
00:06:35,440 --> 00:06:42,240
picture in terms of regulations that
affect large scale data centers. So

83
00:06:40,160 --> 00:06:46,319
there's other local regulations that
could shape where and how large scale

84
00:06:44,400 --> 00:06:50,560
data centers are developed. That
includes things like the large quantity

85
00:06:48,479 --> 00:06:56,240
water user ordinance that I mentioned as
well as economic development policies

86
00:06:53,280 --> 00:07:01,199
and other city policies. Um there's also
federal and state regulations that come

87
00:06:58,319 --> 00:07:05,520
into play such as state economic
incentives and the Arizona Pooperation

88
00:07:03,680 --> 00:07:11,759
Commission's regulation of our
utilities. So tonight's discussion is

89
00:07:08,400 --> 00:07:17,759
really focused on zoning and land use
regulations.

90
00:07:13,919 --> 00:07:22,240
Zoning is a uh zoning is a set of
regulations that focus on where

91
00:07:20,080 --> 00:07:27,840
development can occur, where different
uses can be located, how those uses are

92
00:07:25,280 --> 00:07:31,759
built, what specific conditions apply to
different types of land uses. um that

93
00:07:30,080 --> 00:07:36,240
could be conditions, development
standards like buffers, setbacks,

94
00:07:33,759 --> 00:07:41,280
screening, height limits, c certain
standards like that that can be applied

95
00:07:38,000 --> 00:07:49,520
to specific types of uses.
Um so zoning does not regulate water

96
00:07:45,360 --> 00:07:54,400
use, energy portfolios or energy
infrastructure decisions. um those are

97
00:07:52,479 --> 00:07:59,199
valid and important topics of
discussion, but those rest with other

98
00:07:57,120 --> 00:08:02,879
review bodies and other entities that
have purview in those areas. So

99
00:08:01,280 --> 00:08:07,440
tonight's discussion is really going to
focus on what is within the city's

100
00:08:05,120 --> 00:08:12,479
control and what is before us at this
time, which is zoning or land use

101
00:08:09,759 --> 00:08:16,800
regulations to provide appropriate
standards and regulations for large

102
00:08:13,919 --> 00:08:21,599
scale data centers in Tucson.
So let's get into that conversation. I

103
00:08:20,080 --> 00:08:25,199
want to thank you again for being here
tonight, for being part of this

104
00:08:23,120 --> 00:08:33,800
important conversation. And I'm going to
ask Tonnie to walk us through the

105
00:08:29,039 --> 00:08:33,800
process and ground rules for tonight.

106
00:08:34,800 --> 00:08:42,560
Good evening. Good to see you all. Uh my
name is Tony Robertson with Southwest

107
00:08:39,599 --> 00:08:47,200
Decision Resources and I just have two
slides. [snorts]

108
00:08:44,880 --> 00:08:53,120
Meeting format. I think we've seen
several of you were in the last meeting

109
00:08:49,440 --> 00:08:59,680
or two. So, good to see you again. Um,
so your feedback is going to be

110
00:08:55,600 --> 00:09:05,519
collected in writing in these meetings
via online survey which you'll be seeing

111
00:09:02,880 --> 00:09:10,880
a QR code and you can use your phone to
get access to that website. Um, the

112
00:09:08,880 --> 00:09:16,800
paper form, the green form on the
clipboard is the same questions. So

113
00:09:13,519 --> 00:09:20,320
either option works and you can take uh
provide your comments during the meeting

114
00:09:18,480 --> 00:09:25,360
or after the meeting. I believe it'll be
open through this month through the end

115
00:09:22,000 --> 00:09:30,080
of March. Um and then the sticky notes
on the posters in the lobby. All of that

116
00:09:27,440 --> 00:09:34,720
feedback is being compiled and the city
team is reading through everything very

117
00:09:31,760 --> 00:09:38,800
carefully. They did create the FAQ
document that was in the registration

118
00:09:36,800 --> 00:09:45,680
table like Corin mentioned and they'll
be adding more questions as they go. Um

119
00:09:43,519 --> 00:09:49,440
again, all written feedback will be made
publicly available and shared with both

120
00:09:47,839 --> 00:09:54,080
the planning commission and mayor and
council. Uh conversation and additional

121
00:09:52,800 --> 00:09:58,160
written feedback are encouraged with
city staff before and after the

122
00:09:56,480 --> 00:10:04,160
presentation
um we will have a like the last inerson

123
00:10:01,839 --> 00:10:09,120
meeting at Pua High School will have a
Q&A session here in the main in this

124
00:10:06,800 --> 00:10:12,959
room. Um, we're going to be asking that
people keep their comments to under a

125
00:10:11,120 --> 00:10:16,640
minute so that more people can have a
chance to speak. We had a number of

126
00:10:14,560 --> 00:10:20,560
people that wanted to be able to ask a
question or make a comment last time.

127
00:10:19,040 --> 00:10:25,040
Um,
this the website has all of the links,

128
00:10:22,640 --> 00:10:31,800
all of the information and uh we ask
that everybody respect each other's time

129
00:10:27,680 --> 00:10:31,800
and refrain from disruption.

130
00:10:32,000 --> 00:10:39,040
And again, so in this room is the
presentation.

131
00:10:36,959 --> 00:10:42,640
Um, we have different presenters from
the city that are going to be walking

132
00:10:40,399 --> 00:10:48,959
you through the different components of
the proposed zoning code and giving you

133
00:10:45,760 --> 00:10:55,279
a chance as you go to make comments in
the uh online survey or the written

134
00:10:51,200 --> 00:11:00,959
survey. Um feedback again can be
submitted in both both of those formats

135
00:10:58,000 --> 00:11:06,079
in and then the the uh the Q&A
afterwards in the lobby is the dialogue

136
00:11:03,839 --> 00:11:09,200
opportunity directly with city staff.
You're not restricted to any particular

137
00:11:07,680 --> 00:11:13,440
amount of time. There's posters that
have all the same information that's

138
00:11:10,800 --> 00:11:19,360
going to be in the presentation. Again,
this is about this proposed zoning uh

139
00:11:16,399 --> 00:11:25,120
code, but you a lot of you have feedback
beyond that and we're gathering all

140
00:11:21,360 --> 00:11:28,120
feedback. So, I will turn it over to
Parker.

141
00:11:40,720 --> 00:11:46,480
» All right. Good evening. Uh my name is
Carver Stru. I'm a principal planner

142
00:11:44,640 --> 00:11:50,399
here with the City of Tucson Department
of Planning and Development Services and

143
00:11:48,800 --> 00:11:55,360
I'm going to talk a bit about the
proposal that that we are here to

144
00:11:52,800 --> 00:12:00,560
discuss tonight. Um as was mentioned
earlier, this relates specifically to

145
00:11:57,680 --> 00:12:04,560
zoning and regulating largecale data
centers. One of the first things that

146
00:12:02,560 --> 00:12:10,000
you want to do if you are going to
regulate a land use is to define what it

147
00:12:07,519 --> 00:12:15,600
is that you're regulating. And so what
we've put forward Oh, I'm sorry. Let me

148
00:12:12,639 --> 00:12:19,519
back up. Um going going a little ahead
of myself. Uh I want to start talking

149
00:12:17,440 --> 00:12:22,880
first about what is a large-scale data
center. So what is it that we're talking

150
00:12:21,279 --> 00:12:28,000
about before we start discussing
regulating it? So a large scale data

151
00:12:25,519 --> 00:12:33,600
center is a warehouse filled with
thousands of computers working 24/7 to

152
00:12:30,959 --> 00:12:38,000
store, process, and deliver digital
services and data. uh data centers house

153
00:12:36,320 --> 00:12:42,880
computer equipment, networking
equipment, storage devices. These are

154
00:12:40,720 --> 00:12:48,800
the items that power all of the digital
infrastructure that we use.

155
00:12:47,120 --> 00:12:53,360
Most data centers have a number of
different key components. Um these

156
00:12:50,800 --> 00:12:58,480
include server racks uh that house and
organize servers, networking equipment

157
00:12:56,320 --> 00:13:04,000
uh which moves the data or processes the
data, storage systems to store data, uh

158
00:13:01,600 --> 00:13:09,440
power infrastructure which obviously
powers the equipment and cooling systems

159
00:13:06,800 --> 00:13:12,760
to remove the heat that is created by a
data center.

160
00:13:13,200 --> 00:13:21,360
So really when we're asked to regulate
data centers, the the purpose there is

161
00:13:18,480 --> 00:13:26,240
to set clear rules and standards for
their location and design. The intent of

162
00:13:24,160 --> 00:13:32,000
this is to protect senate sensitive
areas. Address impacts such as noise,

163
00:13:29,200 --> 00:13:37,040
scale, and other impacts early on in the
process. Develop a process that ensures

164
00:13:34,800 --> 00:13:43,200
public input as data center proposals
are developed. and be proactive in terms

165
00:13:40,240 --> 00:13:50,560
of what standards should be in place
versus uh reacting to a specific

166
00:13:46,240 --> 00:13:58,560
proposal as it comes forward.
So the city currently has very limited

167
00:13:55,120 --> 00:14:03,360
standards related to how we regulate
data centers. Traditionally as data

168
00:14:01,519 --> 00:14:10,000
centers were being developed is they
were small relatively small they were

169
00:14:05,839 --> 00:14:14,480
viewed as storage uses um these were you
know it made sense you're looking at it

170
00:14:11,440 --> 00:14:20,880
kind of like as a warehouse but for data
and so they were regulated as such.

171
00:14:17,279 --> 00:14:26,560
However, as we saw new large scale and
hypers scale data centers emerge as a

172
00:14:23,360 --> 00:14:30,639
land use that has never existed before,
we started to look at it differently.

173
00:14:28,480 --> 00:14:35,440
And the city zoning administrator
determined that a large-scale data

174
00:14:32,880 --> 00:14:41,519
center would be classified under the
city's zoning code as a utility

175
00:14:38,160 --> 00:14:46,480
generating system use. As such, it could
only be reviewed as a planned area

176
00:14:44,560 --> 00:14:50,720
development or a planned community
development.

177
00:14:48,000 --> 00:14:57,360
Um, so this is really just defining what
it would be as a stop gap measure and

178
00:14:54,480 --> 00:15:02,880
deciding what process could be used to
review a proposal for a data center.

179
00:15:00,399 --> 00:15:08,079
Under the current code, it's very clear
that we really don't have any existing

180
00:15:05,600 --> 00:15:12,160
standards to regulate their development
or place guard rails on their

181
00:15:09,760 --> 00:15:16,480
development. As such, it's really at
this point in time under the code

182
00:15:14,079 --> 00:15:21,920
largely up to a specific applicant to
propose how they would like to develop a

183
00:15:19,199 --> 00:15:26,480
data center. Uh so with additional
standards as we're going to be

184
00:15:23,760 --> 00:15:32,000
discussing tonight uh mayor and council
can provide limitations or guard rails

185
00:15:29,440 --> 00:15:38,480
on how data centers would be developed
which could reflect values of Tucson.

186
00:15:35,199 --> 00:15:44,320
So this next slide really just shows
what is currently in place under the red

187
00:15:41,279 --> 00:15:51,199
box which is essentially just a process
for reviewing a data center proposal and

188
00:15:47,839 --> 00:15:57,440
then proposed standards that we are
putting forward in this proposed zoning

189
00:15:54,560 --> 00:16:01,920
amendment and seeking your feedback on
related to any number of things. you

190
00:16:00,160 --> 00:16:06,959
know, defining a data center,
establishing where and how they would be

191
00:16:03,519 --> 00:16:12,240
allowed. Um, being establishing a clear
and transparent public review process

192
00:16:09,199 --> 00:16:18,399
for specific data center proposals,
requiring that a data center demonstrate

193
00:16:14,959 --> 00:16:25,120
access to water and power and disclose
the energy mix in such a proposal. Um,

194
00:16:22,800 --> 00:16:29,680
prohibit the use of portable water for
cooling if not subject to the large

195
00:16:27,040 --> 00:16:34,240
water user ordinance. requiring
additional setbacks which would relate

196
00:16:31,759 --> 00:16:38,480
to noise impacts or other impacts on the
community setting clear noise

197
00:16:36,240 --> 00:16:42,399
limitations any number of different
items and we'll be going through these

198
00:16:40,560 --> 00:16:46,320
in in subsequent slides but I really
just want to make the point that this

199
00:16:44,480 --> 00:16:51,680
demonstrates where we are looking at
establishing regulations for where none

200
00:16:49,120 --> 00:16:54,680
currently exist other than that simple
process.

201
00:16:54,720 --> 00:17:03,199
So as we talk about zoning, uh any
authority to regulate land through

202
00:17:00,160 --> 00:17:08,160
zoning by a city or town in Arizona is
given to them by the state. State law

203
00:17:05,919 --> 00:17:13,120
decides what can be regulated through
zoning and is very specific that that

204
00:17:10,959 --> 00:17:18,880
the cities or towns can regulate land
use, building size, shape, height,

205
00:17:15,919 --> 00:17:22,959
materials and purpose, site dimensions,
setbacks, lot coverage, what percentage

206
00:17:21,520 --> 00:17:28,240
of the lot would be covered by a
structure and the location and use of

207
00:17:25,120 --> 00:17:35,120
buildings. However, we are limited
through zoning on what can be regulated

208
00:17:31,760 --> 00:17:39,200
related to water and energy use. Uh,
however, there are other provisions as

209
00:17:36,960 --> 00:17:45,679
as Corin had mentioned, zoning is simply
one component of the entire process to

210
00:17:42,720 --> 00:17:49,919
regulate data centers. Um, and as
mentioned earlier, uh, it's critical to

211
00:17:47,760 --> 00:17:54,960
define a data center when you are
looking to regulate it. Additionally,

212
00:17:52,640 --> 00:18:00,400
due to the processes in place as well as
the process being proposed, any data

213
00:17:57,679 --> 00:18:07,240
center proposal would need to comply
with plan Tucson 2025, our new general

214
00:18:04,240 --> 00:18:07,240
plan.

215
00:18:07,600 --> 00:18:18,080
So the process for reviewing and
considering and developing reviewing and

216
00:18:14,080 --> 00:18:24,160
considering a ordinance for uh zoning
regulations for large-scale data centers

217
00:18:20,880 --> 00:18:29,200
is is outlined here. Um it begins with
mayor and council direction where Marin

218
00:18:26,240 --> 00:18:34,799
council requested that city staff
develop this code proposal. Uh we then

219
00:18:32,480 --> 00:18:39,440
formed a technical advisory committee
which is an advisory committee made up

220
00:18:37,360 --> 00:18:45,760
of volunteer subject matter experts
across a broad array of areas related to

221
00:18:42,559 --> 00:18:52,320
data centers who provided information
and best practices on regulating data

222
00:18:48,640 --> 00:18:56,880
centers. From there we moved into our
community meetings. This is the fourth

223
00:18:54,559 --> 00:19:01,520
of four community meetings that we have
scheduled. two in person and two virtual

224
00:18:59,520 --> 00:19:06,799
to receive community feedback on the
proposal. Now, for those of you who have

225
00:19:04,320 --> 00:19:11,520
been to the previous meetings, the the
rest of this is a little bit different.

226
00:19:08,960 --> 00:19:17,039
Um, we've received some guidance that
mayor and council would like us to uh go

227
00:19:14,160 --> 00:19:20,880
before them in April for a study session
to brief and council on what we have

228
00:19:19,039 --> 00:19:25,840
heard in these community meetings and
receive feedback. And so, that is the

229
00:19:23,520 --> 00:19:30,400
next step in the process that that will
be forthcoming. that is not a vote on

230
00:19:27,840 --> 00:19:35,360
anything. That is simply a study session
to brief them. Um, as we go through that

231
00:19:33,760 --> 00:19:40,000
process, we'll continue to gather
community feedback. The survey will

232
00:19:37,360 --> 00:19:45,120
remain open and then based on feedback
we received. Uh the next steps in the

233
00:19:42,160 --> 00:19:50,240
process are a planning commission study
session at a time yet to be determined,

234
00:19:47,760 --> 00:19:55,039
a planning commission public hearing
where the public will be invited to

235
00:19:52,720 --> 00:19:59,039
speak specifically on this proposal yet
to be determined and then mayor and

236
00:19:56,640 --> 00:20:02,720
council consideration. So more to come
on that and certainly as we have more

237
00:20:00,880 --> 00:20:08,320
information on the specifics, we will be
updating our web page on that.

238
00:20:06,720 --> 00:20:13,520
So, as we're considering developing
these regulations, we are really looking

239
00:20:11,039 --> 00:20:18,240
at guidance from other plans and
policies that are currently in effect

240
00:20:16,080 --> 00:20:23,039
within the city. These are plans and
policies which have either been ratified

241
00:20:20,160 --> 00:20:27,520
by the voters in the case of plan Tucson
or adopted by mayor and council as

242
00:20:25,200 --> 00:20:32,080
official policy. These include, as I
mentioned, plan Tucson, uh the Tucson

243
00:20:30,159 --> 00:20:37,120
resilient together, which is our climate
action plan, the city's comprehensive

244
00:20:34,559 --> 00:20:43,360
economic development strategy, the one
water 2100 master plan, the large

245
00:20:40,880 --> 00:20:47,840
quantity water user ordinance, building
codes, as well as other provisions

246
00:20:45,919 --> 00:20:51,919
within within the unified development
code, which is our zoning code. uh

247
00:20:50,320 --> 00:20:56,720
things related to items such as
rainwater harvesting or um other

248
00:20:54,880 --> 00:21:02,080
development standards that would be
applicable for a structure like a data

249
00:20:59,760 --> 00:21:07,120
center just like they apply already to
any other structure uh within the city.

250
00:21:05,520 --> 00:21:12,000
So the one item that I mentioned there
is the large quantity water users

251
00:21:08,960 --> 00:21:17,760
ordinance and we've got Scott Shadweller
here who is going to speak a little bit

252
00:21:14,159 --> 00:21:20,880
about that from Tucson water.
>> All right. Thanks Carver. Good evening

253
00:21:19,360 --> 00:21:24,960
everybody. As Cover mentioned, my name
is Scott Schwab. I'm deputy director at

254
00:21:22,640 --> 00:21:30,320
Tucson Water. Uh, similar to this
ordinance, um, we developed a large body

255
00:21:27,280 --> 00:21:33,679
water user ordinance. Um, last year, uh,
it was put in place because we didn't

256
00:21:31,919 --> 00:21:38,240
have any guardrails up. We didn't have
any, um, guidance on thresholds for

257
00:21:36,400 --> 00:21:43,280
water use. So, when a new developer, a
new development, um, came to Tucson

258
00:21:40,320 --> 00:21:46,080
looking for water, looking to develop,
um, we worked out the engineering piece,

259
00:21:44,880 --> 00:21:50,720
we worked out the hydraulics and
whatever infrastructure was required. um

260
00:21:48,640 --> 00:21:55,039
you know we move forward with that if uh
if applicable. So the large quality of

261
00:21:53,120 --> 00:22:00,640
water users ordinance was approved by
mayor and council in August of 25. Uh it

262
00:21:58,000 --> 00:22:06,720
is in place today. Um it really sets the
guardrails for um establishing what uh

263
00:22:04,799 --> 00:22:12,320
you know defining what a large water
quantity user is. And that threshold was

264
00:22:09,280 --> 00:22:18,240
set at 10,000 ccf or that was the
equivalent of about 7.4 7.5 million

265
00:22:16,080 --> 00:22:22,559
gallons per month. That's an annual
average. Uh so they could use a little

266
00:22:20,400 --> 00:22:26,720
bit more one month or a little bit less
one a month, you know, taking into

267
00:22:23,919 --> 00:22:31,120
account for weather, things like that.
Um just to put that into context, our

268
00:22:28,960 --> 00:22:36,000
average residential user uses about 8
CCF. Um so this is the equivalent of

269
00:22:33,520 --> 00:22:40,640
about 1,200 single family homes or so.
We do not have any portable customers on

270
00:22:38,320 --> 00:22:45,280
our system right now that use 10,000 ccf
or more. We do have some on the reclam

271
00:22:42,799 --> 00:22:51,120
system, but those are mostly tied to
large uses such as golf courses or

272
00:22:48,000 --> 00:22:55,360
whatnot. Um, so this ordinance applies
to any large water user. In fact, this

273
00:22:53,840 --> 00:23:00,159
ordinance does not specifically call out
data centers. It does not mention them

274
00:22:57,679 --> 00:23:04,640
um by name at all. It is any large water
user that comes. So, any potential

275
00:23:02,000 --> 00:23:08,240
manufacturer um any other type of user
that would use this much water. It

276
00:23:06,320 --> 00:23:12,159
applies to any new development uh that
comes in. So from the ground up uh it

277
00:23:10,640 --> 00:23:16,400
would also apply to anybody who wants to
upgrade their facility. Uh for example,

278
00:23:14,000 --> 00:23:22,159
if they want to expand services and go
from uh you know a certain meter size up

279
00:23:19,120 --> 00:23:27,679
to above 10,000 ccf, they would have to
comply with this ordinance as well. Um

280
00:23:25,440 --> 00:23:32,320
what is required by this policy? Uh any
large water users would have to submit a

281
00:23:29,760 --> 00:23:36,960
sustainable uh water service application
which includes a conservation plan uh to

282
00:23:34,640 --> 00:23:39,679
Tucson Water for review. Uh this
includes things like defining how

283
00:23:38,640 --> 00:23:42,960
they're going to use the water, what
they're going to use, what their

284
00:23:40,640 --> 00:23:48,559
conservation policies are. Um is it
being done in the most efficient way? Uh

285
00:23:46,400 --> 00:23:52,880
if deemed complete by Tucson Water, it
will be put before mayor and council for

286
00:23:50,240 --> 00:23:57,200
their ultimate approval. Um where it
will be presented. So that ultimately

287
00:23:54,640 --> 00:24:02,400
this is each large water unit does need
to be approved by mayor and council. Uh

288
00:23:59,840 --> 00:24:06,320
similar to this ordinance as well, we
did have a technical advisory committee

289
00:24:04,559 --> 00:24:10,080
uh that finished up just recently. We
have stakeholders from the community

290
00:24:07,679 --> 00:24:15,520
from the economic development uh side,
the environmental uh stakeholder groups.

291
00:24:13,279 --> 00:24:19,760
Um they all provided comments that
information was presented to mayor and

292
00:24:17,039 --> 00:24:24,559
council uh last month uh for their
review. So that is that's information

293
00:24:21,919 --> 00:24:28,799
that they are uh looking over right now.
And if they do deem uh you know any

294
00:24:26,960 --> 00:24:33,840
updates or any modifications of the
policy necessary, that's something I'll

295
00:24:30,400 --> 00:24:37,559
come back for in future months.
That'll turn back over.

296
00:24:43,679 --> 00:24:47,159
» Thank you, Scott.

297
00:24:48,240 --> 00:24:54,720
So Scott mentioned a technical advisory
committee for the large quantity water

298
00:24:52,159 --> 00:24:59,919
users ordinance. Uh I want to clarify
that there was also a technical advisory

299
00:24:56,960 --> 00:25:04,000
committee formed for the data cent's
zoning code amendment. They are two

300
00:25:02,080 --> 00:25:08,559
different bodies. So just just to
clarify that they're comprised of of two

301
00:25:06,320 --> 00:25:14,000
different groups of people. However, the
technical advisory committee for data

302
00:25:10,720 --> 00:25:18,559
centers uh was established based on
direction that we received from mayor

303
00:25:15,840 --> 00:25:23,279
and council. Uh its purpose was to share
knowledge and expertise and discuss key

304
00:25:20,799 --> 00:25:28,159
issues related to land use environmental
concerns, resource consumptions,

305
00:25:25,840 --> 00:25:33,120
particularly water and power as well as
infrastructure needs for data centers.

306
00:25:30,559 --> 00:25:38,720
The committee was formed to uh help us
all learn about and provide input or on

307
00:25:35,520 --> 00:25:43,840
best practices, new technologies
and approaches that were undertaken in

308
00:25:40,880 --> 00:25:48,640
other cities or jurisdictions. Uh the
TAC was asked to advise on options to

309
00:25:46,400 --> 00:25:53,360
regulate large-scale data centers and
recommend topics and standards for the

310
00:25:51,200 --> 00:25:57,279
proposed zoning amendment. I want to be
clear that the TAC is not a

311
00:25:55,039 --> 00:26:03,039
decision-making body. They were simply
advisory that were providing input into

312
00:26:00,320 --> 00:26:09,279
the proposed standards. Uh there there
was a desire for consensus, but it

313
00:26:06,400 --> 00:26:14,000
wasn't always achieved. And so it we
aren't necessarily saying that every TAC

314
00:26:11,120 --> 00:26:20,320
member agreed with everything that um
came out of the recommendations but they

315
00:26:16,480 --> 00:26:25,679
did provide advisory input.
So the TAC uh includes 13 members from

316
00:26:23,440 --> 00:26:30,559
various groups. Uh they range from
watershed management to TE. So really we

317
00:26:28,720 --> 00:26:35,520
tried to get as many different groups as
we could involved in the committee to

318
00:26:32,799 --> 00:26:41,440
provide their input. Um, additionally,
we have uh had support from city staff

319
00:26:39,039 --> 00:26:46,080
across multiple different departments.
Uh, they were not members of the TAC,

320
00:26:43,039 --> 00:26:51,360
but they did provide input uh related to
uh sustainability, energy use, uh, water

321
00:26:48,960 --> 00:26:55,679
resources, economic development, um,
just across multiple areas to ensure

322
00:26:53,919 --> 00:27:01,760
that multiple different viewpoints were
considered when when developing uh, some

323
00:26:58,799 --> 00:27:05,760
of the proposed components. Um and again
these these the members of the TAC

324
00:27:03,760 --> 00:27:10,640
included environmental resources, power
supply, energy equity, people also

325
00:27:08,480 --> 00:27:16,799
involved in data consent data center
construction as well as people involved

326
00:27:13,600 --> 00:27:23,200
in the operation of data centers locally
within Tucson.

327
00:27:20,000 --> 00:27:27,600
Uh we also looked at uh what the TAC
thought was important at the very

328
00:27:25,120 --> 00:27:33,679
beginning of the process. uh we surveyed
TAC members on what components were of

329
00:27:30,880 --> 00:27:39,440
greatest concern to them individually.
Uh the feedback we received um was that

330
00:27:36,880 --> 00:27:44,159
water and energy consumption were of
greatest concern which is something we

331
00:27:41,760 --> 00:27:50,480
certainly are aware of. Um air quality
concerns also came ranked fairly high as

332
00:27:47,520 --> 00:27:56,480
did noise concerns and that was also
really closely related to setback from

333
00:27:53,600 --> 00:28:00,960
adjoining land uses. uh so that and
location so that they could be in areas

334
00:27:59,039 --> 00:28:05,840
that that were not already heavily
developed. Uh concerns were also

335
00:28:03,200 --> 00:28:10,480
expressed about heat impacts uh
provision of wildlife amenities,

336
00:28:08,240 --> 00:28:15,679
generator operation which certainly also
relates back to noise and air quality

337
00:28:13,200 --> 00:28:21,440
glare design aesthetic screening
vibration which also relates to noise

338
00:28:18,320 --> 00:28:26,240
and design features. Uh this is not
ultimately the category of items that a

339
00:28:24,080 --> 00:28:31,120
category list of items that we came up
with but during the process of kind of

340
00:28:28,880 --> 00:28:36,960
establishing where the concerns were it
was a useful exercise of the TAC. Uh all

341
00:28:34,480 --> 00:28:41,600
tech materials related to the meetings
including meeting notes and presentation

342
00:28:39,120 --> 00:28:46,559
slides are available on the city's
website uh which we will have a QR code

343
00:28:44,000 --> 00:28:52,240
for later in the presentation uh if you
would like to review those.

344
00:28:50,399 --> 00:28:56,159
So now we're going to shift gears a
little bit and talk about the actual

345
00:28:53,919 --> 00:29:03,440
zoning proposal that that we would like
to get your feedback on this evening.

346
00:29:00,159 --> 00:29:08,880
So when we developed these proposed
standards for large scale data centers

347
00:29:06,399 --> 00:29:12,720
uh we we essentially divided them into
five specific categories which we're

348
00:29:10,960 --> 00:29:18,640
going to talk about individually and
then poll feedback on. These include the

349
00:29:15,520 --> 00:29:24,640
definition, review process and location
proposal for large-scale data centers,

350
00:29:21,760 --> 00:29:29,840
energy and water use and sourcing to the
extent that we can regulate it through

351
00:29:26,480 --> 00:29:38,120
zoning setbacks, environmental
compatibility, landscaping and parking

352
00:29:32,000 --> 00:29:38,120
standards and noise and generator use.

353
00:29:38,559 --> 00:29:47,679
So during the these presentation slides,
uh we're asking or providing the

354
00:29:45,039 --> 00:29:53,120
opportunity for you to provide feedback
on each of these proposals. Uh this can

355
00:29:50,480 --> 00:29:58,080
be done either through a QR code which
will be up on the screen um in just a

356
00:29:55,120 --> 00:30:02,399
little bit or the paper sheets that some
of you have as well. If you'd rather

357
00:29:59,679 --> 00:30:06,399
provide that information that way, we'll
certainly accept it as well. I want to

358
00:30:04,159 --> 00:30:11,520
emphasize that both of those are the
same sets of questions. They will go

359
00:30:09,039 --> 00:30:17,279
into the same set of documented
responses that will be posted on the

360
00:30:14,799 --> 00:30:22,960
website and also provided to mayor and
counsel and the planning commission as

361
00:30:20,000 --> 00:30:27,679
feedback that we've received on this um
on this proposal. Uh there will also be

362
00:30:25,600 --> 00:30:33,200
the question and answer comment period
and then additional time in the lobby

363
00:30:29,919 --> 00:30:38,240
for uh people to provide further
feedback.

364
00:30:34,960 --> 00:30:43,520
So uh the next slide is really for those
of you who want to get into the survey.

365
00:30:41,200 --> 00:30:49,120
This is the QR code that links to the
survey. It's a series of questions that

366
00:30:46,240 --> 00:30:53,039
we'll go through section by section. Um,
if you don't want to do the survey

367
00:30:51,120 --> 00:30:56,480
online, but you want to provide
information, feel free to raise your

368
00:30:54,640 --> 00:31:02,240
hand. We've got some people out here who
can provide paper forms as well if you'd

369
00:30:59,200 --> 00:31:07,039
rather do that. The first two questions
on the online survey are name and email

370
00:31:04,399 --> 00:31:11,520
address. You are welcome to provide that
if you want. We do not require that as a

371
00:31:09,360 --> 00:31:16,480
required question. If you don't want to
provide that, we can simply move to the

372
00:31:14,159 --> 00:31:22,240
next questions as we get through the
process. But that's what you should be

373
00:31:19,039 --> 00:31:27,360
seeing if you're getting online.
Okay. Now, we're going to talk about the

374
00:31:24,880 --> 00:31:32,080
definition of a proposed large scale
data center. Uh, as I mentioned earlier,

375
00:31:30,000 --> 00:31:35,520
» that slide to accommodate people with
disabilities that may not be quick

376
00:31:34,000 --> 00:31:36,880
enough to get QR code.
>> Certainly.

377
00:31:36,240 --> 00:31:41,039
» Thank you.
>> And the QR code will also be posted at

378
00:31:39,279 --> 00:31:44,960
each set of survey questions. So, if
you're unable to capture it here, we can

379
00:31:43,200 --> 00:31:49,919
capture it at each survey question as
well. It's the same QR code.

380
00:31:48,240 --> 00:31:53,799
Has everybody had the opportunity to
capture the QR code?

381
00:31:54,720 --> 00:31:57,720
Okay.

382
00:31:57,919 --> 00:32:04,559
So, the next item is the definition of a
proposed large-scale data center. As I

383
00:32:03,120 --> 00:32:09,600
mentioned earlier, defining a
large-scale data center is key to

384
00:32:06,240 --> 00:32:15,519
regulating them. Uh currently we looked
at how large the data centers are that

385
00:32:12,559 --> 00:32:22,240
we have within the city of Tucson and
saw a natural break at around 30 to

386
00:32:18,640 --> 00:32:26,880
40,000 square ft. And we're looking at
those are the smaller data centers that

387
00:32:24,559 --> 00:32:31,840
we've just seen develop throughout time
in the city. And so we wanted to

388
00:32:29,519 --> 00:32:36,960
establish standards for the larger scale
ones that we are seeing being proposed

389
00:32:34,320 --> 00:32:43,919
elsewhere. And so we established a
proposed 50,000 square foot threshold

390
00:32:40,480 --> 00:32:47,840
where a data center above 50,000 square
feet would be classified as a

391
00:32:45,760 --> 00:32:53,519
large-scale data center. In the
definition, we also included a general

392
00:32:50,559 --> 00:33:00,480
description of equipment and use of the
site. We also included language about

393
00:32:56,480 --> 00:33:05,120
ownership and uh it being part of a
facility or multiple facilities um

394
00:33:03,360 --> 00:33:09,840
establishing this under contiguous
ownership. So it's to avoid people

395
00:33:07,600 --> 00:33:13,360
trying to essentially circumvent the
definition of a large scale data center

396
00:33:11,679 --> 00:33:18,559
by building a whole bunch of smaller
data centers in in a line. And so the

397
00:33:16,480 --> 00:33:24,159
intent of this again proposed language
is to uh establish something that would

398
00:33:21,760 --> 00:33:27,919
allow us to regulate large-scale data
centers as they were developed. And we

399
00:33:26,399 --> 00:33:34,440
will have a question on that on the
survey uh once we get through a couple

400
00:33:30,720 --> 00:33:34,440
of additional slides.

401
00:33:35,360 --> 00:33:43,973
So in addition to the definition, we
would need to figure out where these

402
00:33:40,960 --> 00:33:48,159
might be permitted within the city. We
[snorts] looked at our zoning code and

403
00:33:45,760 --> 00:33:54,080
determined that our existing I2
industrial zone would be the appropriate

404
00:33:50,799 --> 00:33:57,519
zoning district for a large scale data
center. [clears throat] This is really

405
00:33:55,360 --> 00:34:03,440
the zoning district that is most intense
and it's intended to be for those land

406
00:34:00,480 --> 00:34:08,000
uses that would provide the greatest
impacts uh around the community. As

407
00:34:06,240 --> 00:34:12,159
such, these are the areas that are
located, as you can see on the map, in

408
00:34:09,919 --> 00:34:17,760
areas with very little development that
are far away from the urbanized areas of

409
00:34:14,320 --> 00:34:22,879
the city. So, we are proposing that data
centers be permitted through a specific

410
00:34:20,800 --> 00:34:27,760
process called the Marin Council special
exception, and I'll talk a little bit

411
00:34:24,399 --> 00:34:31,679
more about that within the I2 zone. So,
this would be something that is not by

412
00:34:29,839 --> 00:34:36,079
right, meaning that somebody could not
simply come in and say, I want to build

413
00:34:33,760 --> 00:34:40,879
a data center. Here's my build. You have
my permit application. Approve it. It

414
00:34:38,480 --> 00:34:46,960
would be a process where there would be
a public hearing before our zoning

415
00:34:43,280 --> 00:34:50,800
examiner who is the uh um quasi judicial
reviewer. There would be a neighborhood

416
00:34:48,879 --> 00:34:55,200
meeting and there would be consideration
by mayor and council. So there would be

417
00:34:53,040 --> 00:35:00,400
steps in the process that would be
public for public input on any proposal

418
00:34:57,599 --> 00:35:04,880
for a data center. Um this is
essentially the highest level of review

419
00:35:02,240 --> 00:35:10,800
that we have for any land use. It's it's
kind of very similar to a reszoning that

420
00:35:08,079 --> 00:35:17,119
would take place within a community. So
in addition to doing a merit council

421
00:35:13,119 --> 00:35:21,440
special exception uh within the I2 zone,
we would also consider permitting data

422
00:35:20,000 --> 00:35:26,960
centers through a planned area
development or a planned community

423
00:35:23,680 --> 00:35:32,000
development which are also very similar
to a resoning where there would be the

424
00:35:29,599 --> 00:35:36,960
neighborhood meeting, zoning examiner
review and merit council consideration.

425
00:35:34,720 --> 00:35:41,280
um those are very sort of project
specific where there's a little bit more

426
00:35:39,119 --> 00:35:46,079
flexibility in the process but also the
opportunity for additional community

427
00:35:43,359 --> 00:35:50,640
benefits. But it's really key to note in
in those instances again that there

428
00:35:48,240 --> 00:35:54,040
would be a public process and mayor and
council review.

429
00:35:55,119 --> 00:36:02,560
As I mentioned earlier, the process
either through a Marin council special

430
00:36:00,160 --> 00:36:07,359
exception or a PAD or a PCD, planned
area development or planned community

431
00:36:04,160 --> 00:36:12,400
development would require a neighborhood
meeting. A neighborhood meeting is a

432
00:36:09,520 --> 00:36:19,119
public meeting where the public is
invited to come to hear about the

433
00:36:15,760 --> 00:36:25,119
proposed data center project or whatever
the project is um and ask questions of

434
00:36:22,240 --> 00:36:29,119
the developer at that point in time.
Under our current zoning code,

435
00:36:27,040 --> 00:36:35,040
neighborhood meetings are required for
any Marin Council special exception, any

436
00:36:32,240 --> 00:36:40,320
PAD or any PCD development. It is part
of our process that is baked into all

437
00:36:37,440 --> 00:36:46,079
land use change. Under the current code
for any of those, there's a notice

438
00:36:43,280 --> 00:36:49,760
requirement of 400 ft from the property
line that property owners be notified of

439
00:36:48,400 --> 00:36:56,240
the neighborhood meeting and the
proposed change as well as notification

440
00:36:53,599 --> 00:37:00,320
of all neighborhood associations within
one mile.

441
00:36:58,079 --> 00:37:06,079
We are looking at propo or we are
proposing extending that notification

442
00:37:03,119 --> 00:37:12,560
area due to the impacts of large-scale
data centers as well as their potential

443
00:37:09,280 --> 00:37:17,280
location in largely rural areas. We're
looking at extending that from 400 ft to

444
00:37:14,880 --> 00:37:21,200
half a mile and also requiring
notification of all neighborhood

445
00:37:19,599 --> 00:37:25,839
associations
within 2 miles. And so it's really

446
00:37:23,760 --> 00:37:31,359
seeking to have a broader notice area
for the proposal than we would have for

447
00:37:28,720 --> 00:37:35,680
for any other type of land use change
within the city

448
00:37:33,040 --> 00:37:39,440
» and the lovely property owners.
>> That is correct under the current code.

449
00:37:37,520 --> 00:37:43,760
But if there's feedback on that, that is
certainly feedback that that we would uh

450
00:37:41,760 --> 00:37:46,800
like to receive from you as well.
>> You mean renters don't get notified

451
00:37:45,599 --> 00:37:50,800
under the current code?
>> They do not. That is correct.

452
00:37:48,320 --> 00:37:54,560
» So they would not be notified under this
code. the the property owner would be

453
00:37:53,359 --> 00:37:59,040
notified and the neighborhood
associations would be notified and they

454
00:37:56,960 --> 00:38:02,720
would have the opportunity to notify
their tenants or not. But that is how

455
00:38:01,040 --> 00:38:06,400
the code is currently structured.
>> What about the schools?

456
00:38:04,480 --> 00:38:10,920
» Schools are property within the
notification area and they would be

457
00:38:07,920 --> 00:38:10,920
notified.

458
00:38:16,480 --> 00:38:24,240
So the next slide before we get to the
survey is the proposed procedure for

459
00:38:21,920 --> 00:38:28,720
data center review. This is something
I've already talked about, but I just

460
00:38:25,920 --> 00:38:32,400
want to lay it out in a uh diagram
because I know it's it's a complex

461
00:38:30,560 --> 00:38:38,400
process and there are a lot of steps and
steps sound similar. So I can certainly

462
00:38:34,960 --> 00:38:41,680
appreciate um trying to to really wrap
your head around what all those steps

463
00:38:40,079 --> 00:38:46,560
are. But the first one is the
neighborhood meeting and that is the

464
00:38:43,440 --> 00:38:50,480
public meeting where the developer of
the proposal would meet with the public

465
00:38:48,800 --> 00:38:54,640
to provide property owners and
neighborhood associations and anyone

466
00:38:52,480 --> 00:39:01,680
else who comes to the meeting with
feedback on the proposal. Uh from there

467
00:38:58,560 --> 00:39:08,000
an applicant would uh meet with city
staff and then submit an application.

468
00:39:05,119 --> 00:39:13,680
Um there would be again public notice of
a zoning examiner public hearing that is

469
00:39:10,640 --> 00:39:19,119
fully public notice and a public hearing
would occur with our zoning examiner who

470
00:39:16,000 --> 00:39:24,240
is a again a quasi judicial person who
reviews zoning cases and then makes

471
00:39:21,200 --> 00:39:27,680
recommendations to mayor and counsel.
Zoning examiner would make that

472
00:39:25,599 --> 00:39:33,119
recommendation and then mayor and
counsel would consider the proposal.

473
00:39:30,400 --> 00:39:38,000
Mayor and council could approve, deny,
or modify a proposal based on feedback

474
00:39:36,320 --> 00:39:42,800
received.
>> Is any of this required to be bilingual

475
00:39:40,560 --> 00:39:48,960
or interpreted through ASL?
>> Certainly any ADA compliance would would

476
00:39:45,440 --> 00:39:53,520
be met and um certainly bilingual
translation is available just like it is

477
00:39:50,880 --> 00:39:56,720
through all other city processes.
>> Is the neighborhood meeting required to

478
00:39:55,280 --> 00:40:00,800
be in person? in the neighborhood
meeting for project blue with just two

479
00:39:58,800 --> 00:40:04,560
people from the county, one person from
the state, and a lawyer for project blue

480
00:40:02,960 --> 00:40:09,280
because that's the only people who are
living anywhere near the area.

481
00:40:07,920 --> 00:40:12,240
» I really don't know about the
neighborhood meeting that took place for

482
00:40:10,800 --> 00:40:17,760
project blue because it was in the
county and so it was not a city process

483
00:40:15,119 --> 00:40:23,040
that was followed. But that really
speaks to our intention to expand the

484
00:40:20,320 --> 00:40:27,520
notice area in the proposal for exactly
that reason because if there's nobody

485
00:40:24,960 --> 00:40:32,760
that lives within the area, we want to
notice a larger area to ensure that.

486
00:40:33,680 --> 00:40:44,079
Okay. Um so the next slide is back to
the survey. If you'd like to provide

487
00:40:41,839 --> 00:40:49,599
feedback on the next section of
questions, these relate specifically to

488
00:40:47,680 --> 00:40:56,960
the definition of large scale data
centers and our notice requirements. And

489
00:40:52,480 --> 00:41:01,040
I can come back to the definition slide
for a minute or so if people would like

490
00:40:58,880 --> 00:41:06,079
to review that again and provide any
feedback whether you believe this

491
00:41:03,200 --> 00:41:10,560
definition um essentially goes far
enough or needs to go further. And if

492
00:41:08,160 --> 00:41:16,920
you have any written feedback on this
definition, uh that will certainly help

493
00:41:12,800 --> 00:41:16,920
us to receive that as well.

494
00:41:32,880 --> 00:41:38,680
» Oh, certainly. Yeah. Hold on. Here we
go.

495
00:41:39,760 --> 00:41:45,680
Have you considered expanding the
notification

496
00:41:43,280 --> 00:41:51,040
range because the sound profile of data
centers is so much different and and

497
00:41:48,720 --> 00:41:54,960
propagates so much farther especially in
this particular climate to capture more

498
00:41:53,680 --> 00:41:58,000
people that are affected.
>> I think that's certainly something that

499
00:41:56,319 --> 00:42:04,160
we consider and I would encourage you to
place that in the comments as well if if

500
00:42:00,319 --> 00:42:04,160
you believe that that is important.

501
00:42:04,240 --> 00:42:11,280
Back to your definition of large scale,
have you considered putting an upper

502
00:42:09,599 --> 00:42:17,680
limit
to this definition? So then you know we

503
00:42:14,240 --> 00:42:20,640
don't have a medium acre
data center. I

504
00:42:19,119 --> 00:42:27,560
» think that's something again please
provide feedback on that that will be

505
00:42:22,720 --> 00:42:27,560
very helpful for us to receive as well.

506
00:42:32,640 --> 00:42:35,640
Okay.

507
00:42:36,560 --> 00:42:46,480
» So, the next question really goes back
to the the process for allowed zones and

508
00:42:43,119 --> 00:42:51,200
also the review process. Uh, so we
certainly ask for feedback on the review

509
00:42:48,319 --> 00:42:56,319
process of the proposal of notifying to
half an half a mile property owners as

510
00:42:53,680 --> 00:43:00,079
well as two miles to neighborhood
associations. Do you feel that's

511
00:42:58,400 --> 00:43:05,920
adequate? If you have any other feedback
to provide um please write it in the

512
00:43:02,960 --> 00:43:09,880
survey or on the sheet um so that we can
document that as well.

513
00:43:18,000 --> 00:43:25,839
» Certainly
>> go back to the one where it says 50,000

514
00:43:22,800 --> 00:43:30,319
square feet. So if they build something
49,000 square feet, they don't have to

515
00:43:28,319 --> 00:43:33,599
go through this process.
>> That would be correct. It wouldn't meet

516
00:43:31,760 --> 00:43:38,240
the definition of a large scale data
center, but that's part of the reason

517
00:43:35,599 --> 00:43:44,440
why we are looking at 50,000 square feet
and we weren't looking at 100,000 square

518
00:43:40,000 --> 00:43:44,440
feet or something like that because

519
00:43:44,560 --> 00:43:50,560
» we we certainly looked at that as well
and and there there are challenges from

520
00:43:48,560 --> 00:43:56,640
a zoning standpoint of regulating that,
but please provide that feedback as

521
00:43:52,560 --> 00:44:00,640
well. Oh, we will
>> again and again and again.

522
00:43:59,040 --> 00:44:04,160
» Are answers to the survey going to be
made public?

523
00:44:01,680 --> 00:44:08,400
» Yes, they will all be posted online on
the PDSD website, provided to mayor and

524
00:44:06,800 --> 00:44:15,119
council and provided to the planning
commission.

525
00:44:11,119 --> 00:44:21,119
» So, the input that we provide, questions
and clarification that are requested, we

526
00:44:18,480 --> 00:44:27,520
indicated that a committee or a group
are going to compile it to the convey it

527
00:44:24,400 --> 00:44:37,280
to the mayor. Is there going to be any
representation from someone outside of

528
00:44:32,560 --> 00:44:42,319
the city um group included in conveying
that? Because there could be a conflict

529
00:44:39,839 --> 00:44:48,000
of interest. Um we don't really have
representation as to how the data is

530
00:44:44,960 --> 00:44:52,319
manipulated or conveyed.
So actual verbatim comments for

531
00:44:50,480 --> 00:44:58,079
everything that we received will be
conveyed. We may provide an overview of

532
00:44:55,440 --> 00:45:03,040
the number of comments received or even
categories but the actual if you will

533
00:45:00,720 --> 00:45:07,200
metadata of every single specific
comment that we receive whether it's

534
00:45:05,280 --> 00:45:11,680
through the survey through comments in
the registration through post-it notes

535
00:45:09,599 --> 00:45:16,720
that were posted out in the lobby
through chat comments that we've

536
00:45:13,440 --> 00:45:22,079
received from the online meetings. Um,
it's any other comments that we receive,

537
00:45:18,960 --> 00:45:27,960
emails, those will all be provided to
mayor and council in a single document

538
00:45:23,920 --> 00:45:27,960
as well as the planning commission.

539
00:45:34,079 --> 00:45:41,359
People uh have an opportunity to answer
the survey questions specific to this.

540
00:45:39,599 --> 00:45:45,680
I do want to say also that the survey
will be left open for some time. So, if

541
00:45:44,240 --> 00:45:50,599
you don't get it tonight, you can come
back and provide additional feedback as

542
00:45:47,599 --> 00:45:50,599
well.

543
00:45:52,160 --> 00:45:59,960
» Yeah. At this point, I'm going to turn
it over to Dan Versk, who's going to

544
00:45:55,200 --> 00:45:59,960
talk about energy and water use.

545
00:46:07,040 --> 00:46:13,119
» Great. Um, thank you, Carver. Thank you
everyone for joining us today. Really

546
00:46:11,760 --> 00:46:17,680
appreciate it. I do want to point out
one quick thing um that might make it a

547
00:46:16,400 --> 00:46:23,520
little easier for people who are
following along using the QR codes. So

548
00:46:19,920 --> 00:46:28,079
this QR code goes to uh the survey, but
it's the same QR code every single time.

549
00:46:25,920 --> 00:46:33,119
So if you keep that page open, you're
able to kind of follow along. So you can

550
00:46:30,560 --> 00:46:37,920
potentially if I go to the next slide,
you could put it in your comments as I'm

551
00:46:35,040 --> 00:46:41,839
speaking. Um, and it'll keep you keep us
from having to jump back and forth and

552
00:46:39,920 --> 00:46:46,720
having to remember kind of what we're
going going over the specifics of it.

553
00:46:44,079 --> 00:46:52,000
So, just a little tip. Um, might help
with some of the logistics of the

554
00:46:49,119 --> 00:46:56,480
survey. Um, but as well you also have
the opportunity for the the written ones

555
00:46:54,800 --> 00:47:03,280
which is exactly the same.
>> Excellent. Great. So, um, wanted to talk

556
00:46:59,599 --> 00:47:08,640
a little bit about energy and water. Um
as uh Corin and Carvin Carver had

557
00:47:05,920 --> 00:47:14,560
mentioned earlier um these are two items
that um zoning really um is very limited

558
00:47:11,920 --> 00:47:17,520
in what um can be regulated through
these which is part of the reason why

559
00:47:16,400 --> 00:47:22,160
you know we're looking at things like
the large water uh large quantity water

560
00:47:19,599 --> 00:47:25,920
use ordinance and other methods in order
to really try to address these things as

561
00:47:24,079 --> 00:47:31,440
we know they are very important to the
community and very important to to the

562
00:47:27,599 --> 00:47:38,400
city of Tucson. And so um related to
energy consumption and sourcing um we do

563
00:47:34,800 --> 00:47:41,599
have um some regulations and things that
we are proposing related to this. We

564
00:47:40,319 --> 00:47:47,599
definitely want to get your feedback on
this. Um, but the idea here is to

565
00:47:44,880 --> 00:47:51,839
provide information, public information
that would be part of the application,

566
00:47:49,920 --> 00:47:56,000
part of the materials that make its way
through through the review and to mayor

567
00:47:53,760 --> 00:48:00,560
and counsel so our mayor and council can
make really the best decision possible

568
00:47:58,800 --> 00:48:06,079
and have all the information that they
need in front of them. And so the idea

569
00:48:02,960 --> 00:48:09,119
here is that every applicant that if
they were to come in, there are no

570
00:48:07,520 --> 00:48:14,880
applicants that have currently come in
that are in um but demonstrate access to

571
00:48:12,640 --> 00:48:20,079
adequate energy supply at the time of
the application. And so they have to

572
00:48:16,720 --> 00:48:24,640
show that through disclosure um that
they have adequate energy um supply at

573
00:48:22,960 --> 00:48:27,839
the time of application. It's not
something to where there is an adequate

574
00:48:26,240 --> 00:48:31,440
supply and then all of a sudden
infrastructure has to be created leading

575
00:48:29,760 --> 00:48:37,440
to rate increases and things of that
sort. Additionally, um the applicant

576
00:48:34,400 --> 00:48:41,440
must disclose proposed amount of energy,
energy mix including renewables and

577
00:48:39,680 --> 00:48:45,040
application materials related to this.
So again, you're providing all of that

578
00:48:43,359 --> 00:48:48,960
information so you can make that
decision. Um again, mayor and council,

579
00:48:47,520 --> 00:48:53,599
this is part of their decision-m
process. Um they don't have to approve

580
00:48:51,520 --> 00:48:58,000
this. They can approve this, deny this.
they could uh ask for additional

581
00:48:55,200 --> 00:49:02,400
conditions uh related to that based off
that information. So again, putting the

582
00:49:00,319 --> 00:49:07,200
information in front of the public and
front in front of our mayor council so

583
00:49:04,000 --> 00:49:12,480
they can make that decision. Um related
to kind of water use um we have a little

584
00:49:09,920 --> 00:49:17,280
more leeway on this one um as far as
what we can regulate and what we can do.

585
00:49:14,800 --> 00:49:24,160
Um but it's just not necessarily within
zoning. Um, so what pretty much anything

586
00:49:22,240 --> 00:49:28,160
that any applicant that comes in must
comply with the city's large quantity

587
00:49:25,760 --> 00:49:32,160
water user ordinance um if a Tucson
water um customer and Scott had talked a

588
00:49:30,880 --> 00:49:37,119
little bit about this earlier, but it
requires a water conservation plan. Um

589
00:49:34,480 --> 00:49:41,440
recycling water requirements impossible
um and really require it and requires

590
00:49:38,880 --> 00:49:46,400
monitoring and compliance. um if they
don't comply with it, there are um

591
00:49:44,000 --> 00:49:53,599
pretty steep penalties
um as far as related to this um and and

592
00:49:50,400 --> 00:50:00,319
and for that. Um so if they don't fall
within that however um which would be

593
00:49:56,800 --> 00:50:07,119
that 10,000 CFS that's got talked about
um they would be um required or actually

594
00:50:04,000 --> 00:50:11,280
we would it'd be required to meet that
the the the standard that is basically

595
00:50:09,520 --> 00:50:15,280
prohibiting the use of portable water.
So they wouldn't be able to utilize

596
00:50:12,720 --> 00:50:19,280
portable water for data center cooling
um if they weren't subject to the large

597
00:50:17,440 --> 00:50:24,160
quantity water use ordinance.
Additionally to this um similar to the

598
00:50:21,839 --> 00:50:28,720
energy um they would be required to
demonstrate access to water supply at

599
00:50:26,720 --> 00:50:32,319
the time of application as well. So yeah
bringing all that information making

600
00:50:30,640 --> 00:50:36,000
sure that all that information makes it
in front of mayor and council so they

601
00:50:33,520 --> 00:50:38,800
can make um a decision and understand
kind of what's in front of them. All

602
00:50:37,440 --> 00:50:42,240
that information would be public. It
would be submitted at the time of

603
00:50:40,160 --> 00:50:44,960
application early on in the process. So
it's available to the public. It's

604
00:50:43,599 --> 00:50:48,160
available to the zoning examiners. It's
available to staff. It's available to

605
00:50:46,160 --> 00:50:54,160
everyone.
Um, we have a couple questions. I'm

606
00:50:50,160 --> 00:50:58,000
going to hold up for a second. Um,
hopefully. Yes.

607
00:50:55,440 --> 00:51:05,599
» Will there be a requirement that they
have some percentage of renewables

608
00:51:01,839 --> 00:51:13,599
or recycled water usage?
>> Um, so there it's a great comment and a

609
00:51:10,480 --> 00:51:17,359
good one to submit and let us know. Um,
as of now in the proposal, there are not

610
00:51:15,920 --> 00:51:21,839
a requirement for a percentage of
renewable or or a percentage necessarily

611
00:51:19,520 --> 00:51:25,520
of recycled water. Um, they aren't
allowed to use utilize portable water.

612
00:51:23,760 --> 00:51:28,880
Um, if they're under that and then that
would be probably part of the water

613
00:51:27,040 --> 00:51:31,359
conservation plan if they were to do a
large quantity of water user ordinance,

614
00:51:30,720 --> 00:51:34,559
right?
>> Why not?

615
00:51:33,040 --> 00:51:37,920
» Um,
>> that is that is why we are in front of

616
00:51:36,000 --> 00:51:41,119
you to get feedback related to that. So,
that's that that is helpful. We

617
00:51:39,359 --> 00:51:43,839
appreciate it.
Um,

618
00:51:41,920 --> 00:51:49,359
» you mentioned state penalties. Could you
elaborate on that? How big of

619
00:51:47,760 --> 00:51:54,319
a
second?

620
00:51:50,720 --> 00:51:58,319
» Um, related to that, I and and
Scott and Chris.

621
00:51:57,040 --> 00:52:01,440
You know what we'll do? We'll look it up
and then when we're doing Q&A, I'll make

622
00:51:59,920 --> 00:52:06,319
sure that we respond to that. Um, and
make sure that, you know, it's it's

623
00:52:02,880 --> 00:52:09,520
pretty steep and it gets it multiplies
as you have more less and less

624
00:52:08,160 --> 00:52:12,400
compliance over time. I can get those
numbers

625
00:52:10,319 --> 00:52:15,359
» dollars. How are you going to They just
cut you a check. How you going to How

626
00:52:14,160 --> 00:52:17,920
you going to counter that when somebody
has millions of dollars will just be

627
00:52:16,880 --> 00:52:22,559
cutting your check? It's already
happening across the country.

628
00:52:20,640 --> 00:52:27,119
» Anyway, so um I'm going to have to move
on, but we will have Hold on one second.

629
00:52:24,160 --> 00:52:31,680
I'm going to I will let
>> Chris will come up and talk real quickly

630
00:52:28,720 --> 00:52:34,000
about this because he has the details
related to it and then then we'll have

631
00:52:33,359 --> 00:52:39,040
to move on.
>> Just to clarify, if they're using more

632
00:52:36,400 --> 00:52:44,319
than 7.8 million gallons per month since
they can use more portable water.

633
00:52:41,920 --> 00:52:51,720
» Um, it would be a part of their water
conservation plan. In general, they have

634
00:52:46,800 --> 00:52:51,720
to offset all of that water use, but

635
00:52:52,720 --> 00:52:58,960
» my name is Chris Ary. I work at the
Tucson City Attorney's Office. I'm going

636
00:52:56,480 --> 00:53:03,040
to answer the question about water use
penalties in the large quantity water

637
00:53:01,280 --> 00:53:09,280
user ordinance that's been adopted by
mayor council. There are of course some

638
00:53:06,800 --> 00:53:14,160
u financial penalties that occurred to
folks who violate the slaughter

639
00:53:11,760 --> 00:53:18,079
conservation plan that they submit as
part of the large quantity water user

640
00:53:15,760 --> 00:53:24,319
ordinance. But at the end stage of that
there is the ability of the city to um

641
00:53:21,520 --> 00:53:29,520
enact flow restrictions or to restrict
the water use manually and there's no

642
00:53:26,720 --> 00:53:34,800
amount of money that can um stop that.
So I just want to point that out. Um, as

643
00:53:32,319 --> 00:53:39,760
far as offsets, again, what we're asking
for in the large quantity water user

644
00:53:37,599 --> 00:53:45,040
ordinance is for applicants to
demonstrate the most efficient use of

645
00:53:41,680 --> 00:53:52,079
water for the technology that they have
and to also site their uh facilities in

646
00:53:49,760 --> 00:53:56,640
areas where there's proximity to
reclaimed water if possible and to use

647
00:53:54,000 --> 00:53:59,680
as much reclaimed water as they can. Um,
there are different perspectives about

648
00:53:58,160 --> 00:54:03,760
that and we'd love to hear your comments
about whether you think

649
00:54:02,079 --> 00:54:07,920
these large facilities should use
portable water or reclaim water or both.

650
00:54:06,240 --> 00:54:11,512
» Can you tell us where that valve is? We
won't tell anyone. You told us

651
00:54:09,492 --> 00:54:11,512
[laughter]

652
00:54:12,720 --> 00:54:17,960
» which I did not understand that
question.

653
00:54:18,480 --> 00:54:24,960
» Who gets to decide when the water gets
shut off if a large water user goes too

654
00:54:23,440 --> 00:54:29,920
far?
So the the language in the large

655
00:54:27,680 --> 00:54:34,000
quantity water user ordinance doesn't
talk about shut offs. It talks about

656
00:54:31,760 --> 00:54:38,880
flow restrictions. So they ask a large
quantity water user will be submitting a

657
00:54:36,000 --> 00:54:44,240
water use plan and if that plan is not
met then we will meter the usage so that

658
00:54:42,240 --> 00:54:48,319
it complies with that plan.
>> Who determines how much reclaimed water

659
00:54:46,000 --> 00:54:52,640
they should be using? Who decides what
what's the best? There are a set of

660
00:54:50,640 --> 00:54:57,280
recommendations that are made on that in
that respect by the city of Tucson water

661
00:54:55,599 --> 00:55:00,640
department director and some of that is
related to proximity to the reclaim

662
00:54:59,200 --> 00:55:04,040
system but ultimately it's a mayor
council decision.

663
00:55:07,200 --> 00:55:12,880
» Great. Thank you Chris. I appreciate it.
Okay. Um moving on and we will have Q&A

664
00:55:11,440 --> 00:55:16,880
at the end. Just want to let everyone
know um where we'll have the opportunity

665
00:55:14,640 --> 00:55:22,079
to be able to uh provide comments, ask
questions, etc.

666
00:55:18,880 --> 00:55:25,440
Um so talk a little bit about proposed
setbacks and this is something we've

667
00:55:23,520 --> 00:55:29,599
gotten a lot of feedback on so far and
we do really appreciate a lot of the

668
00:55:27,280 --> 00:55:33,760
feedback um especially related to kind
of noise impacts and things of that

669
00:55:31,040 --> 00:55:38,400
sort. So um in the proposal that is in
front of you the one we've that we've

670
00:55:35,599 --> 00:55:43,920
that we've put in front of you um we
have a required 400t setback from data

671
00:55:41,280 --> 00:55:50,240
center use uh to urban residential areas
and noise sensitive uh areas such as

672
00:55:46,240 --> 00:55:56,240
schools. Um and additionally we have uh
a required 200 foot setback um from data

673
00:55:54,160 --> 00:56:00,480
center use to commercial or office use
is just understanding that the

674
00:55:58,319 --> 00:56:04,480
incompatibility of these of these
facilities um really related to

675
00:56:03,040 --> 00:56:09,040
commercial or related to office
especially related to residential um is

676
00:56:06,880 --> 00:56:12,559
not there and so this is intended to
make sure that it's set back. We've

677
00:56:10,559 --> 00:56:17,680
seen, you know, a lot of situations up
in um the Phoenix area where they didn't

678
00:56:14,640 --> 00:56:20,720
have regulations in place um for this
and we have data centers right across

679
00:56:19,359 --> 00:56:24,799
the street from a lot of residential
neighborhoods. Um they've measured you

680
00:56:23,119 --> 00:56:29,599
know heat impacts and noise impacts and
things of that sort and this is really

681
00:56:26,319 --> 00:56:34,240
intended to um to mitigate some of that.
Um we've had we've had several comments

682
00:56:31,599 --> 00:56:37,839
related to uh you know whether this is
enough or not. Um we do really

683
00:56:36,319 --> 00:56:42,319
appreciate that. It's something we will
be looking at. um as far as looking at

684
00:56:40,079 --> 00:56:48,400
potential revisions to um as we move
forward um with this proposal. Um so

685
00:56:45,359 --> 00:56:53,359
that that's the current proposal um uh
that we have kind of in front of you um

686
00:56:50,799 --> 00:56:57,599
related to proposed setbacks um as well
for this

687
00:56:55,359 --> 00:57:01,680
um related to that uh there is a
question in there related to that

688
00:56:58,960 --> 00:57:06,559
whether it's um appropriate or not um as
well as you know open-ended question to

689
00:57:04,319 --> 00:57:11,040
be able to provide your comments. Huh?
>> Two questions. How come the slide

690
00:57:09,040 --> 00:57:16,160
doesn't have the same amount of stuff on
it as the sheet? The sheet has two more

691
00:57:13,680 --> 00:57:21,240
items, landscaping.
>> Oh, yeah. We're uh we'll be talking

692
00:57:17,599 --> 00:57:21,240
about that in a second.

693
00:57:21,440 --> 00:57:26,960
» We're already within the times for
community questions. It's 7:30.

694
00:57:24,799 --> 00:57:32,160
» Yeah, we're we we're almost there. Okay,
we'll be there. Okay. No, we

695
00:57:29,359 --> 00:57:36,799
» How come the notification thing is is so
large, but that setback is only 400 ft?

696
00:57:35,200 --> 00:57:39,599
I mean, that's nothing.
>> Nothing.

697
00:57:37,680 --> 00:57:43,880
» That's so tiny. That's not a quarter of
a mile.

698
00:57:40,880 --> 00:57:43,880
» Yeah.

699
00:57:44,000 --> 00:57:51,960
» Good things to comment on. We will take
your feedback related, but we are

700
00:57:47,680 --> 00:57:51,960
looking at it. So, we appreciate it.

701
00:57:56,000 --> 00:58:03,280
» I'll let you know. Okay. A couple of
other things that zoning can regulate.

702
00:58:00,240 --> 00:58:06,720
Uh, one of them being um noise.
>> What's your name?

703
00:58:04,160 --> 00:58:12,799
» Regulation. My name is Nick Martell.
>> Thank you. Um, so our proposal right now

704
00:58:09,760 --> 00:58:16,720
is to require a independent noise study
that measures sound levels and tone. Um,

705
00:58:15,040 --> 00:58:22,480
that's something that would be in that
5565 decel area when it reaches a

706
00:58:19,839 --> 00:58:27,280
property line. So on the outside or the
actual property line between um the

707
00:58:24,799 --> 00:58:31,280
proposed data center and any other land
use. Um the other thing would be to set

708
00:58:29,520 --> 00:58:36,160
clear noise limits on that property line
like I just said with those decibb um

709
00:58:33,680 --> 00:58:41,040
and then require sound walls or roof
screening around generators um and then

710
00:58:39,359 --> 00:58:46,559
other loud equipment. So that's just to
kind of uh a to block some of the uh the

711
00:58:44,799 --> 00:58:51,760
uh generators and some of those other
visual aspects of it and also to block

712
00:58:48,480 --> 00:58:51,760
some sound.

713
00:58:53,680 --> 00:59:02,000
Is there any accommodation on that on
the decel level for duration? Because

714
00:58:58,079 --> 00:59:06,880
even though it's 50 dB, 50 dB at a
constant 247

715
00:59:04,240 --> 00:59:09,760
pace has a different effect than just
checking for a single.

716
00:59:08,400 --> 00:59:12,799
» So I believe that would be covered in
the sound study that would be required

717
00:59:11,520 --> 00:59:18,880
for this.
>> What what waiting scale are you using to

718
00:59:16,160 --> 00:59:25,960
the sound? a waiting specifically
derates the sal of these facilities.

719
00:59:21,680 --> 00:59:25,960
» I'd have to get back to you on that one.

720
00:59:26,079 --> 00:59:33,119
» Okay. Uh some proposed regulations for
generator use. Um so generators are part

721
00:59:30,720 --> 00:59:38,079
of data centers in terms of backup power
usually. Um so our proposal would be to

722
00:59:35,839 --> 00:59:44,000
use cleaner high efficiency generators
such as tier 4 or natural gas or dual

723
00:59:40,799 --> 00:59:48,000
fuel. Um battery backups would be used
first during power disruptions. So if

724
00:59:46,160 --> 00:59:52,160
there were a power disruption to use
that backup uh battery first before

725
00:59:50,160 --> 00:59:56,319
getting into generators. Um there would
be no load shifting allowed which is the

726
00:59:54,400 --> 01:00:01,680
uh running of generators instead of
using grid power. Um and then generators

727
00:59:59,200 --> 01:00:06,160
run only during emergencies or required
maintenance. Um and then that would be

728
01:00:03,839 --> 01:00:12,640
non-emergency uh maintenance would only
be limited to 9 to5s on weekdays.

729
01:00:09,599 --> 01:00:16,400
» Who's going to regulate that and and how
do you file complaints if they're not in

730
01:00:14,480 --> 01:00:20,000
compliance? So this would be regulated
through our code enforcement. Uh code

731
01:00:18,400 --> 01:00:23,680
enforcement, you have a website, you can
use um 311. There's several ways you can

732
01:00:22,559 --> 01:00:29,319
call code enforcement.
>> Who monitors the load?

733
01:00:26,319 --> 01:00:29,319
» Sorry.

734
01:00:30,240 --> 01:00:35,839
» Um that would just be a regulation and
if they were out of code with it, then

735
01:00:33,760 --> 01:00:38,400
they could be issued a violation.
>> How would anybody know they were out of

736
01:00:37,280 --> 01:00:41,520
code?
>> That would be up to our code enforcement

737
01:00:39,920 --> 01:00:46,640
department to enforce.
>> Teen will take care of that.

738
01:00:43,359 --> 01:00:53,280
» All right. I will leave this up for one
minute um just in case nobody got it and

739
01:00:49,440 --> 01:00:56,480
then I'll move on just a second.
>> I'm going to go back to the compliance

740
01:00:54,640 --> 01:01:00,640
thing again. These guys have billions of
dollars. So what are you going to do

741
01:00:58,400 --> 01:01:04,079
when they just keep cutting you a check
and they keep violating stuff? You going

742
01:01:02,799 --> 01:01:07,440
to shut them off? You going to tell them
to get the hell out? You can't do

743
01:01:05,760 --> 01:01:11,119
anything. You don't have the money
against these companies. Why are you

744
01:01:09,520 --> 01:01:16,079
guys not thinking about this?
>> Thank you for that feedback. that stuff

745
01:01:12,720 --> 01:01:21,280
we would love to hear.
Okay, moving on to proposed landscaping.

746
01:01:18,720 --> 01:01:25,200
Um so one of the proposed landscape um
items here would be to require an

747
01:01:22,880 --> 01:01:29,359
enhanced landscaping border of 20 ft. Um
that would be around the property line

748
01:01:26,960 --> 01:01:34,559
that helps eliminate some visual aspects
of these data centers. It also um

749
01:01:31,599 --> 01:01:40,559
provides areas to provide um low water
plants um uh desert plants for desert

750
01:01:38,640 --> 01:01:44,079
landscaping. Um and then to define a
minimum parking ratio. That's also one

751
01:01:42,160 --> 01:01:47,920
of the aspects of zoning. Um a lot of
these do not require a lot of parking

752
01:01:46,000 --> 01:01:52,720
and so we would not be requiring a lot
of parking for them to use it. Um kind

753
01:01:50,240 --> 01:01:58,920
of limiting imperous surfaces at data
centers.

754
01:01:55,200 --> 01:01:58,920
» So there are no jobs.

755
01:01:59,760 --> 01:02:05,440
» Cool. Thanks.
>> Okay. Environmental compatibility. So we

756
01:02:04,240 --> 01:02:09,359
are going to utilize some of our
existing standards. Uh we are not

757
01:02:07,359 --> 01:02:13,280
proposing any changes to environmental
compatibility. Uh we would require

758
01:02:11,440 --> 01:02:18,079
applicants to adhere to any overlays
such as the environmental resource zone

759
01:02:16,079 --> 01:02:21,520
um the wash overlays the water course
amenity safety and habitat zones. They

760
01:02:20,240 --> 01:02:27,160
would have to utilize commercial
rainwater harvesting and hillside

761
01:02:23,680 --> 01:02:27,160
development standards.

762
01:02:27,520 --> 01:02:34,720
This includes protection of existing
aoyos and washes. Uh the use of low

763
01:02:32,079 --> 01:02:40,400
water and drought tolerant plants. Uh as
well as a requirement of harvesting 50%

764
01:02:37,520 --> 01:02:43,520
of total landscape water demands. Um
just then touching on some of those uh

765
01:02:42,160 --> 01:02:48,720
desert landscapes that I was talking
about. Um and then utilizing an existing

766
01:02:45,839 --> 01:02:52,480
airport hazard district uh requirements
on glare. A lot of our I2 zones are

767
01:02:51,200 --> 01:02:56,880
pretty close to the airport. So they
would have to comply with all airport

768
01:02:54,079 --> 01:03:02,799
environment zone uh requirements.
>> Okay. On that last point, what where

769
01:02:59,920 --> 01:03:05,839
would I find Can you go back?
>> Uh where would I find those standards?

770
01:03:04,559 --> 01:03:08,880
The state standards.
>> These are in our unified development

771
01:03:07,440 --> 01:03:12,880
code. These would be in the overlay
section of the UDC. Um if you would

772
01:03:11,280 --> 01:03:16,920
like, I can talk to you afterward and
show you if you'd like to see them.

773
01:03:17,760 --> 01:03:23,680
» Okay. Um going to give you another
minute if you would like to put any

774
01:03:21,680 --> 01:03:26,303
feedback in for those landscape parking
and compatibility. [clears throat]

775
01:03:36,079 --> 01:03:41,559
» Then no need to go back to the good

776
01:03:52,880 --> 01:03:58,720
All right, we just have a couple more
slides before we can get to the question

777
01:03:56,160 --> 01:04:03,920
and answer comment section. U just
wanted to emphasize I already covered

778
01:04:01,520 --> 01:04:09,680
some of this opportunities for further
input and discussion. This QR code is

779
01:04:06,799 --> 01:04:14,240
for the PDSD website where information
is going is all posted. Uh, as I

780
01:04:12,400 --> 01:04:19,680
mentioned earlier, we're looking at
probably a mayor and council special or

781
01:04:16,160 --> 01:04:23,039
a study session in April and then to be
determined on planning commission study

782
01:04:21,599 --> 01:04:30,240
session, planning commission public
hearing and merit council consideration.

783
01:04:26,319 --> 01:04:36,720
Uh, we also have a um
FAQ document that we are continuing to

784
01:04:33,520 --> 01:04:41,920
update and it's posted to the website.
Uh, this is again the process uh that we

785
01:04:39,680 --> 01:04:47,920
outlined earlier. you've already seen
that. Um, and so now we're getting set

786
01:04:44,880 --> 01:04:52,319
up for the Q&A section. Uh, microphone
is being set up by Cesar. Uh, please

787
01:04:50,079 --> 01:04:57,119
line up behind the microphone to speak.
Uh, we ask that you please be succinct

788
01:04:54,480 --> 01:05:02,240
and speak for no more than 60 seconds so
that we can ensure that everybody has an

789
01:04:58,960 --> 01:05:08,079
opportunity to speak wishes to. And your
questions during this Q&A uh, session

790
01:05:05,280 --> 01:05:12,480
will be included on the record of public
input. um these are being filmed and

791
01:05:10,319 --> 01:05:17,400
these will be documented and sent to
parent council and the planning

792
01:05:13,920 --> 01:05:17,400
commission as well.

793
01:05:17,920 --> 01:05:24,640
» Okay, great. So, we have about 20
minutes for Q&A. Again, no more than 60

794
01:05:22,880 --> 01:05:28,240
seconds. We want everybody to have a
chance their chance to to ask questions

795
01:05:26,799 --> 01:05:31,720
or speak.
>> Can you give us

796
01:05:32,400 --> 01:05:41,280
» the full 30 minutes?
>> Well, spoke pretty slow. So,

797
01:05:38,480 --> 01:05:46,880
So, um, Colleen is holding going to hold
up cards to remind you of your seconds.

798
01:05:44,400 --> 01:05:50,319
Um, we know that in public hearings, you
get three minutes. This is one minute

799
01:05:48,640 --> 01:05:56,240
because this is not a public hearing and
we want more people that have a chance.

800
01:05:52,559 --> 01:06:00,400
So, um, and Cesar will be making sure
that you also know when it's time to

801
01:05:58,640 --> 01:06:03,920
stop, but we really value your comments.
So, go ahead. First, let's hopefully the

802
01:06:02,720 --> 01:06:07,839
mic is working.
>> Yes. Hi. Uh, my name is Vake. I'm a

803
01:06:06,480 --> 01:06:12,079
member of the no desert data center
coalition um can you bring up the slide

804
01:06:10,000 --> 01:06:17,520
of the map please with the with the I2
zones. Um and while that's happening um

805
01:06:15,359 --> 01:06:21,839
I encourage everyone here to leave
comments that say prohibit large scale

806
01:06:20,480 --> 01:06:25,599
data centers. I think we've heard
tonight that whatever restrictions there

807
01:06:23,520 --> 01:06:30,400
are incredibly hard to enforce if at
all. Um and so please do say just

808
01:06:28,559 --> 01:06:35,039
prohibit large scale data centers. It's
not up to us to explain how to do that

809
01:06:32,880 --> 01:06:39,920
legally. It's up to our city staff to
figure that out. Um so if you do know

810
01:06:37,760 --> 01:06:45,280
that though, please let them know. Um so
this map, the purple area is the large

811
01:06:42,079 --> 01:06:48,640
is the um heavy industrial area to the
south of the airport. If you see that

812
01:06:46,960 --> 01:06:52,960
little carve out south of that purple
area, that's Summit. They have no uh

813
01:06:51,280 --> 01:06:57,760
representation in the city of Tucson,
but they are 80% Latin. And they border

814
01:06:55,839 --> 01:07:01,599
the largest section of industrial, heavy
industrial. You can see the western

815
01:06:59,200 --> 01:07:06,480
border there is the San Javier district
of the Kona nation. So these are folks

816
01:07:04,000 --> 01:07:09,280
who are disenfranchised by these data
centers and that's the heaviest

817
01:07:07,839 --> 01:07:12,920
concentration right there. This is
environmental racism.

818
01:07:15,280 --> 01:07:20,720
So hi, my name is L. I'm here to
represent myself as a geoccientist from

819
01:07:18,720 --> 01:07:25,440
the University of Arizona and I'm also
here as a member of Tucson Red Action.

820
01:07:23,200 --> 01:07:28,720
Uh our group has made a list of demands
and I'm just going to go over that real

821
01:07:26,799 --> 01:07:33,920
quick. Our first one, a complete
dedication to the not one drop policy.

822
01:07:31,039 --> 01:07:38,480
This includes uh water and it's been
amended to be an airbased project. We

823
01:07:36,400 --> 01:07:44,960
want to include that also all natural
resources including petroleum, gas uh

824
01:07:41,359 --> 01:07:51,599
etc. Um our second demand uh we want a
commitment to the prohibition of any

825
01:07:48,559 --> 01:07:56,079
data center. Um we demand that the city
at every stage if you have spoken that

826
01:07:54,079 --> 01:08:02,559
you are only able to control this from a
building code standpoint. Um all the

827
01:07:59,119 --> 01:08:06,720
other groups um need to work with you to
make sure that no data center can be

828
01:08:04,480 --> 01:08:12,799
made. Uh and most importantly we want a
seat at the table. Uh this TAC board

829
01:08:09,760 --> 01:08:17,040
lacks proper representation by the
people who will be affected most. We

830
01:08:14,720 --> 01:08:22,480
want energy experts, water experts from
nonprivate, non um for-profit

831
01:08:20,319 --> 01:08:27,040
organizations along with gender and
racial tribal voices.

832
01:08:24,880 --> 01:08:31,839
» Great.
>> And I'll just like if you have written

833
01:08:29,839 --> 01:08:36,679
comments for this this opportunity at
the mic, please also submit those in

834
01:08:33,679 --> 01:08:36,679
writing.

835
01:08:36,799 --> 01:08:44,400
» Um my name is Reyes or doesn't really
matter. Um, but if I go home and I turn

836
01:08:41,679 --> 01:08:49,040
on the faucets in my house, um, I will
be shut off water eventually. So, why

837
01:08:46,880 --> 01:08:50,560
does this standard not, you know, follow
liquid status centers?

838
01:08:50,239 --> 01:08:53,759
» Y,
>> our water is our most precious resource

839
01:08:52,400 --> 01:08:58,480
in the desert. And they're already
talking about cutting us off from the

840
01:08:55,279 --> 01:09:03,199
Colorado River water. Um, and the second
point is the last time I was here that

841
01:09:00,719 --> 01:09:08,640
your tag group of experts, none of them
were explicitly against data centers,

842
01:09:05,520 --> 01:09:12,080
which you have a bias in there. If you
have true expertise, some of them would

843
01:09:10,400 --> 01:09:16,159
lead to the fact that they don't believe
data centers are are a viable option in

844
01:09:13,839 --> 01:09:20,000
our desert. You're picking first on if
these people are pro data center and

845
01:09:17,920 --> 01:09:24,960
then decide their expertise among them.
It's not fair. Um, finally, there needs

846
01:09:23,120 --> 01:09:29,440
to be a prohibitive uses of this data
center. There is obnoxious uses such as

847
01:09:27,359 --> 01:09:33,762
immigration enforcement and mass
surveillance. Um, that needs to be

848
01:09:31,742 --> 01:09:33,762
[applause]

849
01:09:38,319 --> 01:09:45,920
My name is Kathy Thompson. Um, I'd like
to quantify what an actual need is. We

850
01:09:44,080 --> 01:09:50,739
don't need a data center. We need
schools. We need hospitals. We need

851
01:09:48,400 --> 01:09:57,199
homes. We need food distribution. We
[applause] don't need data center all of

852
01:09:53,359 --> 01:10:01,679
our use to just sell us more crap. It's
going to end up in the landfill. Um

853
01:09:59,280 --> 01:10:05,520
these companies are rushing to build
these data centers because the private

854
01:10:03,360 --> 01:10:11,199
capital is drying up. Companies like
Blue Owl, Apollo, they have seen great

855
01:10:08,719 --> 01:10:15,600
drops in their stock prices recently.
They they are just rushing to just take

856
01:10:12,880 --> 01:10:19,840
advantage of communities. Um I'd like to
also find out if you're going to find

857
01:10:17,440 --> 01:10:23,280
for excess water use, what are you going
to do? Go to the Midwest or the

858
01:10:21,280 --> 01:10:27,600
Northwest and buy more and ship it here?
I mean, the fine doesn't do anything.

859
01:10:25,280 --> 01:10:32,480
The water is a precious resource for
life. It's not for this technology

860
01:10:30,480 --> 01:10:38,609
behemoth that we're going to look at in
10 years and say, "Who the heck let them

861
01:10:34,719 --> 01:10:38,609
build that thing?" [applause]

862
01:10:42,000 --> 01:10:48,640
Hi there. My name is Melissa Westbrook.
Um, number one, looking at that panel,

863
01:10:46,560 --> 01:10:54,960
it looks about white. Uh, [laughter]
secondly, um, this thing has grammatical

864
01:10:52,400 --> 01:10:59,920
and one very glaring numerical error. If
you need someone to proofread, I used to

865
01:10:56,480 --> 01:11:04,880
be a proofreader and editor. Um, I will
say to you that again, we do need to

866
01:11:02,400 --> 01:11:11,760
understand why are we building these
things? Why this rush for AI? It's

867
01:11:09,600 --> 01:11:17,840
dangerous. It's dangerous in our public
schools. And that's my area of

868
01:11:13,440 --> 01:11:24,400
expertise. So, I don't I grew up here.
I'm a pr proud wildcat. Water is our

869
01:11:21,280 --> 01:11:31,440
most precious resource. We are not going
to give it away. We don't have it. The

870
01:11:28,159 --> 01:11:35,679
Colorado River, you guys have got to
Somebody's got to put the brakes on. If

871
01:11:33,520 --> 01:11:40,120
it's all about money, I got you. If it's
all about money, hey,

872
01:11:40,779 --> 01:11:42,799
[applause]

873
01:11:46,320 --> 01:11:54,080
my name is Aiden. I'm a member of local
IU 140 or I local 140. Uh, I just have

874
01:11:51,920 --> 01:11:58,560
two things to say. one, as far as I can
tell, AI has been used to power the

875
01:11:56,159 --> 01:12:02,000
worst elements in our society just over
and over again. I can't see any real

876
01:12:00,239 --> 01:12:06,000
reason that it would be a benefit to our
city to have one of these data centers.

877
01:12:03,840 --> 01:12:09,440
On a more procedural point, uh I have
experience working with a lot of large

878
01:12:07,440 --> 01:12:14,159
corporations. They're going to violate
your policies. They violate policies,

879
01:12:11,920 --> 01:12:19,520
safety policies, environmental policies
constantly and with no regard. And so if

880
01:12:16,640 --> 01:12:23,360
your first thought is not how are we
going to prevent them or stop them when

881
01:12:21,920 --> 01:12:26,080
they do violate these policies, you're
looking at it from the wrong

882
01:12:24,320 --> 01:12:29,679
perspective, you're you're not going to
stop them from using too much water or

883
01:12:27,920 --> 01:12:33,120
too much power or too much whatever.
They do it on a regular basis. They will

884
01:12:31,440 --> 01:12:36,000
easily put their employees at risk.
They'll take the blood out of your veins

885
01:12:34,480 --> 01:12:40,719
if you let them. And so if you're not
looking at them as your enemy, you're

886
01:12:37,280 --> 01:12:40,719
looking at this wrong.

887
01:12:41,040 --> 01:12:43,060
» [applause and cheering]

888
01:12:43,440 --> 01:12:52,159
» HI, MY NAME IS DIANE Rosia and I'm a
proud Tucson of 56 years and I'm a

889
01:12:48,400 --> 01:12:56,960
realtor. So, I house people here in our
city. I have a question.

890
01:12:54,880 --> 01:13:02,640
Since Tucson already has a data center
operating within the city limits at

891
01:12:59,520 --> 01:13:07,840
roughly 40,000 square ft of raised floor
space, why wasn't that considered

892
01:13:05,120 --> 01:13:12,880
sufficient reason earlier to review
whether the land use codes should

893
01:13:10,239 --> 01:13:17,920
address impacts such as setbacks,
energy, water use, environmental

894
01:13:15,120 --> 01:13:24,040
compatibility, noise and generator use,
and appropriate zoning before future

895
01:13:20,239 --> 01:13:24,040
applications arise.

896
01:13:24,926 --> 01:13:31,320
» [applause]
>> have an answer before the next comment.

897
01:13:33,440 --> 01:13:40,880
» Okay, sorry about that. Um, yes. So,
honestly, we hadn't heard any concerns

898
01:13:38,480 --> 01:13:46,159
related to that and it wasn't until we
heard concerns from the public that we

899
01:13:43,280 --> 01:13:50,320
really needed we needed to go in and
actually create regulations related to

900
01:13:48,080 --> 01:13:54,560
this and look at those attacks. And so
that is the reason why those data

901
01:13:52,800 --> 01:14:00,080
centers were just functioning within
industrial areas and it really we hadn't

902
01:13:58,480 --> 01:14:07,080
had any complaints by neighbors around
there or anything else. That's the

903
01:14:01,920 --> 01:14:07,080
reason why until this point we hadn't.

904
01:14:08,960 --> 01:14:17,040
» Hi guys, it's April. I wanted to bring
up two things. When my neighborhood

905
01:14:14,640 --> 01:14:23,120
wanted to install a traffic calming
device with a grant in our neighborhood,

906
01:14:19,520 --> 01:14:29,280
we had to get signatures from 60% of the
residents on that street.

907
01:14:26,159 --> 01:14:35,679
And yet, these proposed
notifications are actually nowhere near

908
01:14:32,400 --> 01:14:39,360
the amount that should be compared to
something like a community trying to get

909
01:14:37,600 --> 01:14:46,080
a very real benefit like a traffic
calming. Secondly, I know that we know

910
01:14:43,600 --> 01:14:52,239
as people who have code and write code
and deal with code in Tucson, we know

911
01:14:48,960 --> 01:14:58,239
how to make land uses prohibited. We
know how to make it prohibited for

912
01:14:55,040 --> 01:15:03,600
shelters, for rehabs, for many other
actual useful land uses. And that's why

913
01:15:00,719 --> 01:15:07,760
Mayor Castle just had to declare an
emergency around homelessness to get

914
01:15:05,199 --> 01:15:11,600
over those codes. I encourage you to
learn from what you do well already

915
01:15:10,382 --> 01:15:15,400
[laughter] and apply that to this
situation. Thank you.

916
01:15:19,600 --> 01:15:29,760
» Hi, my name is Reed. Um, I'm
I'm tired. I'm tired of this. I'm tired

917
01:15:27,600 --> 01:15:33,600
of coming to these meetings. I'm tired
of saying the same things over and over

918
01:15:31,840 --> 01:15:38,480
again to the city officials,
specifically mayor and council, who do

919
01:15:36,080 --> 01:15:43,440
not appear to be listening. Why should
we expect mayor and council to listen to

920
01:15:40,880 --> 01:15:49,199
you or to listen to the feedback that we
have given you when they were spending

921
01:15:46,560 --> 01:15:53,280
they spent a couple years before they
told anyone about project blue working

922
01:15:51,199 --> 01:15:59,520
behind the scenes to make it happen?
They were meeting regularly with Amazon

923
01:15:55,760 --> 01:16:04,719
every few weeks. I think 2024, 2025 to
get advice from Amazon about Arizona

924
01:16:02,239 --> 01:16:09,360
water law and they never thought to tell
the people of Tucson. These are the

925
01:16:06,560 --> 01:16:14,560
people you're reporting to. My question
for you is, how are you, given that

926
01:16:12,159 --> 01:16:18,719
betrayal, how are you going to get them
to listen to you? How are you going to

927
01:16:16,320 --> 01:16:23,798
get them to listen to us? Cuz I don't
have any faith that they will.

928
01:16:21,778 --> 01:16:23,798
[applause]

929
01:16:26,239 --> 01:16:31,760
Hi there, Derek Espalos. I am an
accountant, a data analyst, and a

930
01:16:30,400 --> 01:16:35,600
current candidate for the Arizona
Corporation Commission, which I can

931
01:16:33,360 --> 01:16:41,520
assure you is not going to protect
anyone from anything that happens. So, I

932
01:16:39,520 --> 01:16:46,800
have three questions. I'm just going to
throw them out there. Why should we

933
01:16:43,280 --> 01:16:50,400
trust this process? Because there, as
was just mentioned, we've been through

934
01:16:48,560 --> 01:16:55,520
this process. We keep going through this
process and no trust is never

935
01:16:52,400 --> 01:16:59,520
established. The second question is, are
you going to disclose how you're

936
01:16:57,360 --> 01:17:05,280
scraping and putting together this data?
Because having the binary options mixed

937
01:17:02,159 --> 01:17:09,440
with the comment option leads to a lot
of statistical bias. And finally, when

938
01:17:08,159 --> 01:17:14,040
will [clears throat] Tucson understand
that no means no?

939
01:17:11,040 --> 01:17:14,040
» No.

940
01:17:14,719 --> 01:17:19,199
» Response before the next.
>> Yeah, I want to respond to that question

941
01:17:17,600 --> 01:17:23,040
and the previous question about the
process and where is this feedback

942
01:17:20,960 --> 01:17:27,600
going? How do you know this is going to
be listened to? So, our mayor council is

943
01:17:25,440 --> 01:17:31,440
very interested in the feedback from the
public and the technical advisory

944
01:17:29,120 --> 01:17:36,480
committee. That's actually why they put
a pause on project blue last summer so

945
01:17:34,480 --> 01:17:39,920
that we could have a broader community
conversation about what are the

946
01:17:38,159 --> 01:17:43,920
safeguards we need to have in place for
our community as these uses are

947
01:17:41,760 --> 01:17:48,239
proposed. So, I think it's exactly in
reaction to what they heard from the

948
01:17:45,840 --> 01:17:52,080
community that they directed staff to
make sure we have protections and guard

949
01:17:50,400 --> 01:17:56,719
rails in place for our community. So,
that's their intent with this process.

950
01:17:54,320 --> 01:18:02,159
Um, and we will be taking all of this
feedback to mayor and council in the

951
01:17:58,880 --> 01:18:06,640
next month or so um to give them an
update on what we've heard so far and

952
01:18:04,880 --> 01:18:10,679
give them an opportunity to provide
additional feedback and direction.

953
01:18:13,920 --> 01:18:23,280
Hi, my name is Leilani. Um, a comment
and then a question. Um, under the

954
01:18:19,360 --> 01:18:29,920
location and design section, I believe
there was a bullet that said the

955
01:18:25,440 --> 01:18:35,040
applicant would propose the regulations.
I find that comical. Why would we afford

956
01:18:32,719 --> 01:18:42,800
the applicant the right to propose the
regulations? I don't know if you're

957
01:18:38,400 --> 01:18:50,400
looking for feedback on how we should
incorporate or mandate the process as

958
01:18:46,719 --> 01:18:56,320
well as the feedback on the impacts. Um,
and then also with regards to the

959
01:18:53,679 --> 01:19:02,159
penalties that have been assessed, I'd
like to know over the last 10 years what

960
01:18:59,840 --> 01:19:06,400
the financial penalties that have been
assessed. He didn't mention, Chris did

961
01:19:04,640 --> 01:19:11,360
not mention
uh and because we know there no one's

962
01:19:08,640 --> 01:19:16,239
monitoring it. Um and that would show
that it would support that no one's

963
01:19:14,480 --> 01:19:22,719
monitoring it. So the financial
penalties I'm curious what that amount

964
01:19:18,320 --> 01:19:25,360
is. Um yeah, I know. But um
>> you're good.

965
01:19:24,159 --> 01:19:31,840
» Okay.
>> Yeah. Okay. Um with regards to the

966
01:19:29,280 --> 01:19:38,560
applicant demonstrating the access to
energy Okay. Okay. Go ahead and respond.

967
01:19:35,600 --> 01:19:42,560
» I'll get back in line if there's still
by the way I'm happy to speak and talk

968
01:19:40,880 --> 01:19:47,760
through the details of some of those.
I'm not entirely sure about the um

969
01:19:45,199 --> 01:19:51,440
applicant proposing. Um I will say
related to the large quantity water use

970
01:19:49,440 --> 01:19:59,679
ordinance. It was just put in place in
August and as Scott has mentioned

971
01:19:53,920 --> 01:20:02,560
previously um existing there are no uh
large quantity water people that would

972
01:20:01,360 --> 01:20:06,400
actually qualify for that that are on
the portable system and the only ones

973
01:20:04,320 --> 01:20:10,080
that are really in the in the city.
There's only a handful and they're on

974
01:20:07,760 --> 01:20:14,800
the reclaimed system as of now. And so
that kind of gives you an understanding

975
01:20:12,320 --> 01:20:17,760
of how large of the that threshold is,
but it also gives you an understanding

976
01:20:16,239 --> 01:20:21,440
of kind of the reason why there wouldn't
be any penalties because no one is

977
01:20:19,760 --> 01:20:24,440
actually a part of that program at this
point.

978
01:20:26,640 --> 01:20:32,719
» Good evening. Thank you for taking my
question. My name is Albert. I am a

979
01:20:31,199 --> 01:20:37,280
retired
uh environmental biology teacher. And

980
01:20:35,600 --> 01:20:44,719
one of the things I used to teach my
students when it became the topic of

981
01:20:40,480 --> 01:20:48,159
water was the concept of water mining.
And most people don't understand what

982
01:20:46,480 --> 01:20:53,360
water mining is. So I'm going to address
you guys. That is when you take more

983
01:20:51,280 --> 01:20:59,120
water out of the ground than
reflections. There's nothing in a hole

984
01:20:55,679 --> 01:21:04,719
and pumping water. Just water was
limited by 2025 by law to stop water

985
01:21:02,960 --> 01:21:11,120
mining. And that's why we started
blending cap water. Any development in

986
01:21:08,159 --> 01:21:19,280
town has to be a guaranteed 100year
water supply. How is billions of gallons

987
01:21:15,440 --> 01:21:26,320
a month going to guarantee that this
data center will will have enough water

988
01:21:22,800 --> 01:21:31,360
supply for a 100 years. And how are we
going to do that without water mining?

989
01:21:28,719 --> 01:21:37,880
That would be my question perhaps for
the lawyer of Susan. Thank you. I think

990
01:21:34,640 --> 01:21:37,880
the [applause] change

991
01:21:39,120 --> 01:21:44,360
2030
used to be 2025.

992
01:21:46,661 --> 01:21:51,360
[clears throat]
>> All right.

993
01:21:49,440 --> 01:21:55,679
» So to help answer that question, one of
the requirements of the large quantity

994
01:21:53,440 --> 01:21:59,360
water users policy was that they do have
to fall within our assured water supply.

995
01:21:57,920 --> 01:22:02,880
So that is one of the requirements that
we would look at to make sure that we're

996
01:22:00,560 --> 01:22:07,840
not going above and beyond. Um so that
is one of the things that we have that

997
01:22:04,480 --> 01:22:11,360
much water in the desert.
>> We have that much water.

998
01:22:09,280 --> 01:22:14,520
» We have a very resilient supply as of
right now.

999
01:22:18,080 --> 01:22:25,760
» Okay. I want to let you know we have our
hard stuff at 8 because we have to leave

1000
01:22:23,120 --> 01:22:30,080
this room. It will continue in the lobby
and staff will stick around for at least

1001
01:22:27,679 --> 01:22:35,280
a half an hour and can talk individually
with all of you. So, let's continue. We

1002
01:22:32,320 --> 01:22:41,040
can get in hopefully three more people.
>> Hi, Elena native Tonan. Um, I want a

1003
01:22:38,480 --> 01:22:46,320
future in Tucson, which is why I'm here.
Um, I just want to add my voice to the

1004
01:22:44,080 --> 01:22:50,320
many voices here who are asking to see
more prohibitive zoning that would

1005
01:22:48,159 --> 01:22:56,880
actually prohibit hypers scale data
centers in the city t of Tucson limits.

1006
01:22:53,840 --> 01:23:02,800
Um, I see some of the efforts in the
proposed code to mitigate harms um from

1007
01:23:00,239 --> 01:23:06,719
this development. I appreciate that and
frankly it's just not enough. Um, I

1008
01:23:05,280 --> 01:23:11,360
think we're still seeing that
communities are facing disproportionate

1009
01:23:09,040 --> 01:23:16,080
harms while we don't really get to see
any of the benefits, frankly, of these

1010
01:23:13,600 --> 01:23:20,639
projects. Um, I have major concerns
about enforcement and monitoring. Who

1011
01:23:18,639 --> 01:23:23,679
does this? Is this sufficient?
Particularly, as folks have mentioned,

1012
01:23:22,080 --> 01:23:27,920
for companies that are making billions
of dollars. Um, you seem to imply in

1013
01:23:26,080 --> 01:23:32,159
some of your answers and some of what I
saw written that it's up to the public

1014
01:23:29,679 --> 01:23:36,960
to like call in. Um, so anyway, I want
to understand the enforcement and the

1015
01:23:33,840 --> 01:23:43,120
monitoring mechanisms. Um, how do data
centers fit into plan Tucson and how

1016
01:23:40,960 --> 01:23:49,600
you're prioritizing economic development
in the city? A plan Tucson general plan

1017
01:23:46,320 --> 01:23:55,960
is a reflection of a city's values. Is
like, do we value this? Is this within

1018
01:23:51,840 --> 01:23:55,960
our values? Is this something

1019
01:23:57,008 --> 01:23:59,028
[applause]

1020
01:23:59,199 --> 01:24:05,840
about us?
Hi. Um, I am not an expert in anything

1021
01:24:03,760 --> 01:24:09,120
unfortunately. Um, I just had a couple
of like facts that I just kind of

1022
01:24:07,120 --> 01:24:14,719
Googled really quickly. Um, so that's a
quick quick Google search. Um, you can

1023
01:24:11,440 --> 01:24:21,520
see that AI in 2025 used about give or
take 3 312 to 764 billion water liters

1024
01:24:19,040 --> 01:24:26,159
of water this year, last year alone. And
it's projected that in Phoenix um, data

1025
01:24:24,080 --> 01:24:30,719
centers could consume up to 3.8 billion
gallons of water per year. Tucson

1026
01:24:28,400 --> 01:24:34,320
doesn't have that kind of water. Do we
want the water to go to people in

1027
01:24:32,719 --> 01:24:39,638
communities or do we want it to go to
data centers here? Yep. [applause]

1028
01:24:39,920 --> 01:24:44,960
» Hi, my name is Brandon. This might be
normally where I take do the courageous

1029
01:24:43,679 --> 01:24:47,360
thing and thank you for hosting this
meeting, but we're not thankful that we

1030
01:24:46,320 --> 01:24:50,800
have to keep coming out to these
meetings and talking to you guys. Last

1031
01:24:49,440 --> 01:24:54,000
summer, we told you we don't want a data
center in the desert. It does not make

1032
01:24:52,159 --> 01:24:58,159
sense for us. no matter what regulations
you put on the screen, um it's just not

1033
01:24:56,719 --> 01:25:01,120
right for the desert. It doesn't make
any sense here. Um and instead of

1034
01:24:59,840 --> 01:25:04,719
listening to us, you guys have jumped to
this inevitability that the data center

1035
01:25:03,600 --> 01:25:06,239
has to be here. So, let's just go ahead
and figure out how we're going to

1036
01:25:05,600 --> 01:25:08,719
regulate that.
>> They're not inevitable.

1037
01:25:07,520 --> 01:25:11,679
» They're not inevitable. That's what
we're here to tell you. We don't have to

1038
01:25:10,159 --> 01:25:14,400
have a data center in the desert. It
doesn't make sense to do it. The first

1039
01:25:13,199 --> 01:25:17,840
question on your frequently asked
questions flyer is, can we prohibit a

1040
01:25:16,560 --> 01:25:19,520
data center from being here?
>> Yeah.

1041
01:25:18,239 --> 01:25:22,320
» Instead of answering that, you've just
told us what a data center is. If you

1042
01:25:21,040 --> 01:25:25,840
look at that, the question should be,
"What is it actually?" You didn't answer

1043
01:25:23,840 --> 01:25:28,960
the question. Um, but I think in one of
your slides, you maybe did because it

1044
01:25:27,199 --> 01:25:30,719
says that the city is able to control
land use.

1045
01:25:30,000 --> 01:25:34,000
» Yeah.
>> So, instead of having these regulations

1046
01:25:32,560 --> 01:25:37,679
and these conversations, how about we
stop stop and talk about how we're going

1047
01:25:36,239 --> 01:25:41,000
to not have a data center here. It does
not make sense.

1048
01:25:41,154 --> 01:25:46,880
[applause]
We'll take the last question, but I

1049
01:25:44,800 --> 01:25:50,800
think it should be noted that there's a
complete error in the response to the

1050
01:25:48,880 --> 01:25:54,960
first question. That's not actually the
response. They just discovered this.

1051
01:25:52,719 --> 01:25:59,679
Final question for comments.
>> Hi, my name is Lee and my question is

1052
01:25:57,199 --> 01:26:02,880
why was TEP allowed on the technical
advisory committee when they have a

1053
01:26:01,120 --> 01:26:07,520
vested interest in building data
centers? [applause]

1054
01:26:05,600 --> 01:26:12,480
The for-profit company, the Canadian
company that owns TP said they plan to

1055
01:26:09,600 --> 01:26:15,520
spend$ 1.5 to2 billion on additional
generation. So, it seems like we

1056
01:26:14,159 --> 01:26:19,440
shouldn't have someone with a vested
interest guiding this. Um, I also want

1057
01:26:17,760 --> 01:26:23,120
to know if you're looking at all about
the connection of this map and

1058
01:26:20,960 --> 01:26:26,560
environmental racism cuz these seem like
the communities like on the southside

1059
01:26:25,040 --> 01:26:29,920
that have been poisoned for generations
and generations. So, if you're not going

1060
01:26:28,239 --> 01:26:33,600
to put one in the foothills, I don't
think you should put a data center

1061
01:26:31,120 --> 01:26:36,880
anywhere in
the final question. Why is there so many

1062
01:26:35,360 --> 01:26:41,360
police here? This is a community
meeting. It feels like to have a whole

1063
01:26:39,360 --> 01:26:44,960
line of police here. So,
>> yeah, I would really like to look at

1064
01:26:43,120 --> 01:26:51,295
facts to include environmental justice
and the history of of pollution in

1065
01:26:47,199 --> 01:26:51,295
Tucson. Thank you. [cheering]

1066
01:26:51,895 --> 01:26:53,915
[applause]

1067
01:26:54,239 --> 01:27:01,040
» We really need all the feedback. Thank
you for sharing your concerns,

1068
01:26:58,480 --> 01:27:04,639
questions, and input in this process. It
is definitely going to shape what we

1069
01:27:02,880 --> 01:27:08,159
take to Mayor Council and where this
process ultimately goes for our

1070
01:27:06,159 --> 01:27:12,960
community. So, thank you all for being
here tonight. We will be around um in

1071
01:27:10,880 --> 01:27:16,400
the lobby for more questions and
discussion if folks have more time and

1072
01:27:14,639 --> 01:27:20,560
more questions that you want to ask. Um
but we do need to leave the auditorium

1073
01:27:17,920 --> 01:27:24,880
now so that uh Ringcon High can close up
for the evening. Thank you very much to

1074
01:27:22,400 --> 01:27:28,600
Ringcon High for hosting us and thank
you all for being here.