City Council Minutes 2025 06-10-251
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
1
UNITED CITY OF YORKVILLE
KENDALL COUNTY, ILLINOIS
CITY COUNCIL MEETING
PUBLIC HEARING
651 Prairie Pointe
Yorkville, Illinois
Tuesday, June 10, 2025
7 :00 p .m .
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
2
PRESENT: (In-person and via Zoom)
Mr. John Purcell, Mayor;
Mr. Ken Koch, Alderman;
Mr. Dan Transier, Alderman;
Mr. Craig Soling, Alderman;
Mr. Arden Joe Plocher, Alderman;
Mr. Chris Funkhouser, Alderman;
Mr. Matt Marek, Alderman;
Mr. Rusty Hyett, Alderman.
ALSO PRESENT:
Mr. Bart Olson, City Administrator;
Ms. Jori Behland, City Clerk;
Ms. Erin Willrett, Assistant City
Administrator;
Mr. Rob Fredrickson, Finance Director;
Mr. Eric Dhuse, Public Works Director;
Mr. James Jensen, Chief of Police;
Mr. Tim Evans, Parks and Recreation
Director;
Ms. Krysti Barksdale-Noble, Community
Development Director;
Mr. Brad Sanderson, City Engineer.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
3
APPEARANCES:
OTTOSEN, DiNOLFO, HASENBALG & CASTALDO,
LTD.
BY: MS. KATHLEEN FIELD ORR
1804 North Naper Boulevard, Suite 350
Naperville, Illinois 60563
(630) 682-0085
appeared on behalf of the United City of
Yorkville;
MAHONEY, SILVERMAN & CROSS, LLC
BY: MR. DAVID J . SILVERMAN
822 Infantry Drive, Suite 100
Joliet, Illinois 60435
(815) 730-9500
appeared on behalf of the Project
Cardinal development company;
MICKEY, WILSON, WEILER, RENZI, LENERT &
JULIEN, P .C .
BY: MR. BERNARD K . WEILER,
140 South Municipal Drive
Sugar Grove, Illinois 60554
(630) 801-9699
appeared on behalf of several homeowners
near Project Cardinal development.
- - - - -
REPORTED BY: Christine M . Vitosh
Illinois C .S .R . License No. 084-002883
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
4
I N D E X
WITNESS: PAGE
DAVID J . SILVERMAN 5
MATT McCARRON 9
BERNIE WEILER 18
JAMIE DAMITZ 34
DAVID HOLTZMAN 39
KEITH LANDOVITZ 41
JACK SCHLUETER 45
MAGDALENA EMMERT 48
MITCH HOLTZ 60
- - - - -
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
5
(WHEREUPON, the following
proceedings were had in public
hearing, commencing at 7 :59 p .m .
as follows:)
MAYOR PURCELL: So I am opening public
hearing for Project Cardinal for the Pioneer Data
Center. And this is for the annexation, correct?
MS. NOBLE: Annexation agreement.
MS. BEHLAND: Agreement.
MAYOR PURCELL: Annexation agreement. I
knew there was a word I forgot to add. I left my
agenda in the truck.
So the public hearing is now open.
Are we going to start? Who wants to go first?
Petitioner have something they want to --
MR. OLSON: The developer has seven
slides I think they wanted to kind of intro
everything if that's okay.
MAYOR PURCELL: Okay, I guess, yep. Oh,
my God, you are right there in the front. I was
leaning back the whole time --
MR. SILVERMAN: Right here, Mayor.
MAYOR PURCELL: -- with the screen, I
couldn't figure out why it was so handsome, the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
6
glow, but it was coming from you.
How are you doing, David?
MR. SILVERMAN: Doing fine, thank you.
MAYOR PURCELL: Good to see you.
MR. SILVERMAN: Good to see you.
MAYOR PURCELL: Thank you.
MR. SILVERMAN: Are we ready?
MAYOR PURCELL: Yes.
DAVID J . SILVERMAN,
testified before the City Council as follows:
MR. SILVERMAN: Mr. Mayor, members of
the Council, members of the public, my name is
David Silverman. I am attorney with the law firm
of Mahoney, Silverman & Cross with offices in
Oswego, Joliet and Morris, and I am here tonight
to represent the Pioneer Development Company in
its development of Project Cardinal within the
city of Yorkville.
I 'd like to thank everybody for
coming out. I know we've met several of you
before. We have had a couple community meetings,
one for the folks on the west side of 47, and
then Matt McCarron, who is here representing
Pioneer, has had a meeting last week with the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
7
folks from Bristol Bay subdivision, so we are
here to hopefully answer your questions.
If we can't answer them tonight, we
will certainly get answers for you, communicate
those through the city, or have those when we
come back to the Planning and Zoning Commission
public hearing.
So what the board has before it
tonight is an annexation agreement in draft form.
We are still working with the city staff, who I
would like to thank very much for their
cooperation.
It's been a pleasure to work with
the staff and they have been very responsive to
us, holding our feet to the fire, but certainly
always there to answer questions for us and to
help us through this process.
So the annexation, right there in
the blue, you can see the portion of Project
Cardinal which is already annexed in the city
limits.
In the red are approximately
300 acres, which are the subject of this
annexation agreement tonight.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
8
The total Project Cardinal footprint
is a little over 1 ,000, a thousand and -- say
1 ,040 acres, consisting of 2 1 parcels, and there
are seven parcels there in the red which have not
been annexed yet.
This is the concept plan for Project
Cardinal. As Mr. Olson mentioned, it's about a
little over 1 ,000 acres. There are seven --
excuse me, approximately 14 buildings on this
site, which will have about 17,000,000 square
feet of data centers.
It's intended to be an integrated
campus. The thought is that it will probably be
one end user that comes to the project, although
that could change, there may be several users,
but the hope is to have one user and one
consolidated cam -- one consolidated campus.
The facility will be powered by one
new utility switchyard and two new ComEd
substations.
Pioneer will partner with a
nationally recognized firm to bring Project
Yorkville -- or, excuse me, Project Cardinal to
Yorkville.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
9
As you can see, the project is
bordered on the east by Route 47, on the south by
Galena Road, on the west by Ashe Road, and on the
north by Base Line Road.
The annexation of these 300 acres,
members of the Council and Mayor, will allow this
to act as one consolidated campus for all the
data center projects within the 1 ,000 acres.
It will be built in multiple phases
and each phase will most likely be one building
at a time. It's not the intent that there be
buildings built on speculation, but rather
buildings will be built when an end user comes
and is willing to commit to be on the site.
The project could take up to
ten years, we are projecting a ten-year plus or
minus total build-out for the center, and the
construction, if all goes well, as Mr. Olson
mentioned, we have several hurdles to climb over
with ComEd, our partners feel very confident that
we are getting through those hurdles, but
without ComEd's power, this project does not
work.
The project will most likely start
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
10
on the west side and proceed to the east, and
that's driven mostly by the fact of where the
ComEd power lines are at and where the ComEd
facilities will be built.
The portion -- If you were at the
Economic Development Commission meeting, there
was a n area to the south of Galena Boulevard
there that was shown as a water tank farm.
Given some new approaches that we
are taking with the water consumption on the
project, we don't think those water tanks would
be necessary, so those can be reserved in case
they are needed either by the developer or by the
city at some point in the future.
As Bart mentioned, there will be
substantial setbacks around the entire project,
will be set back at least 500 feet from any
existing residential building, there will be a
lot of landscaping and berming.
The plans will concentrate the
landscaping and even higher berms where they
impact residential users, and also we are aware
of your issues with 47 kind of being the gateway
to the city and making that look nice for the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
11
city, so there will be extensive berming,
extensive landscaping, and then inside the
landscaping and berming there will be a security
fence, which will be made out of steel or wrought
iron or something like that. It won't be a chain
link fence. We don't propose any barbed wire.
It will be a nice looking fence, but you won't be
able to see much of it because of the landscaping
and berming.
One issue that I think bears some
discussion and recognition tonight is the height
of the buildings. We are planning the actual
building height to be at 55 feet; however, some
of the rooftop units may go up to 78 feet, and I
know that's contrary to the ordinance that you
will be considering tonight, but, you know, we
did work on this for a substantial amount of time
before we got that ordinance, so we would be
asking for consideration, and that ordinance has
a 1500 -- or, excuse me, a 1500 radius where you
can't have the building over 70 feet, and if you
can see those kind of dotted lines on there, I
don't know who has got the cursor, but there is
some dotted line -- yeah. That's the 1500 foot
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
12
line, so all the buildings would not be within
that 1500 foot line, but several of them would
be, so we just want to make sure that we pointed
that out to you.
Mr. Funkhouser, we listened to your
concerns at the EDC meeting. There will be no
vinyl around the tops of the buildings to hide
the units that are up there, those will all be
masonry, and there will also be sound barriers on
there to protect the area residents from any
sounds.
All the buildings will be made from
precast -- May we go to the next slide? Okay. I
sort of got ahead of myself. We talked about the
setbacks, landscape berms.
These are the elevations. The
brown -- This isn't the greatest one, and we will
have a better one for you when we get to the
public hearing at the Planning and Zoning
Commission, but the brown is intended to kind of
represent the berming that could be in front of
the building. If you would go to the next slide,
please.
And, you know, the buildings are
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
13
intended to be -- you know, we think of these big
tilled up or masonry buildings that are
associated with industrial parks. You know, the
nice thing about this is the logistics centers
that you see being built in many communities,
while they are tilt-up buildings and they have
some glass and some nice painting around them,
what you mostly see are trucks.
You see trucks around the whole
outside of the building and you see truck docks
along at least one side of the building and
sometimes cross docks on both sides.
This data center campus won't
operate like a logistics building; there will be
virtually no truck traffic in and out of there.
You will have some deliveries obviously that come
in, but once the construction is finished, you're
not going to see the truck traffic or the
intensity of traffic that would be associated
with a logistics building.
And I think Bart did a pretty good
job of pointing out the economic benefits of a
project of this nature, and we think it's a
really good place for the city to be in because
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
14
you do get the benefit of the economics of the
utility taxes, of the property taxes for all the
taxing districts, but you don't have the burden
of the truck traffic, which we have seen in so
many communities.
So these buildings will be a mixture
of precast, some metal, some glass. We are still
working with the city on the elevations with city
staff, but it will generally have the appearance
of a large office building, and, again, no truck
bays, nothing like that. Let's go to the next
slide, please. Is that it? No.
Okay. It's just another view.
Again, the brown is kind of the berming. This is
taken from -- it's a rendering from some distance
back. I apologize, unfortunately I don't know
what the distance is on that, but it's taken
obviously from a considerable distance back, and
we will, again, refine some of these before our
presentation to the Planning and Zoning
Commission next month.
Again, the fiscal impacts will be --
will be substantial. The berming, the
landscaping, will -- and the nature of the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
15
buildings, the aesthetics of the buildings, will
help to make it as compatible with the
surrounding areas as possible.
To the north it's mostly farmland
right now; I know there are some residences
scattered around both on Galena Road and on Base
Line Road. We will pay particular attention
around those residences.
For the folks in Equestrian Estates ,
we will pay particular attention to the berming
and the landscaping along the western area, and
for the folks over in Bristol Bay, our closest
building is about 1500 feet from the nearest
residential structure and buffered by Route 47 as
well.
So what we have before the Council
tonight is an annexation agreement that we are
still discussing with your staff. Essentially we
are asking for the annexation of the 300 plus or
minus acres. We are asking for the property to
be rezoned.
Currently the property, which is not
annexed, is zoned County A -1 , Agricultural 1 , and
the property that is already annexed is a
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
16
combination of R -2 , R -3 and B -3 I believe within
the -- within the city limits.
So we are asking for the property of
these 300 acres to be rezoned to the M -2 District
and that we could receive a preliminary planned
unit development approval so that we can move
further along in this process.
Once we have this annexation
agreement and the planned unit development
agreement approved, hopefully we can get to that
point; if we do, then we will begin working on a
number of other agreements which will implement
the planned unit development ordinance and also
the annexation agreement in terms of what
roadways need to be upgraded and to what extent
do they need to be upgraded , what sewer,
utilities, do we need here, and community
benefits, what things can we provide that may be
on top of everything else to assist the community
and make Yorkville a better place to live.
Those agreements I am sure will
include a number of fees that the city will be
requesting from us.
So that concludes our presentation.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
17
Obviously we are happy to answer any questions
from the Council or the public. I rely on Matt
to help me out if I get stuck, but we are here,
we are here to answer questions, and we really
appreciate the public process that the City of
Yorkville has including all the people, and I
hope that our community meetings were helpful
also.
MAYOR PURCELL: Mr. Funkhouser?
ALDERMAN FUNKHOUSER: Are we taking
Council discussion first or comment?
MAYOR PURCELL: Up to you.
ALDERMAN FUNKHOUSER: All right. I know
this is not part of the annexation agreement, but
it's part of the PUD, I know you guys are
resisting the height restriction on the
1500 feet. That is a point that we will stand
to. I think that's important for us.
The other one, on the annexation
agreement, Section 2 -B is the uses of the site.
It has the reduced list of approved uses for it.
I thought based on the conversation we had that
that was being changed to data center only.
MR. SILVERMAN: Yeah. We have asked the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
18
city to take that out, and for the benefit of the
public, basically it's what happens if this is
not a data center, and Matt's willing to commit
that this is essentially going to be a data
center or whatever the city wants it to be.
We don't need those extra uses in
there, and we are working with your staff,
Councilman, on some language that will accomplish
that goal so that --
ALDERMAN FUNKHOUSER: Okay.
MR. SILVERMAN: -- say we don't build
out by getting near the term of the agreement,
you know, you can just rezone it to residential
or whatever you want to do with it.
ALDERMAN FUNKHOUSER: Okay. Good.
That's what I wanted to confirm. Appreciate it.
MAYOR PURCELL: Anything else?
MR. SILVERMAN: On the annexation
specifically, that's it.
MS. WILLRETT: There's been a request to
speak in the microphone. People on Zoom cannot
hear the questions that are asked.
ALDERMAN FUNKHOUSER: Oh, sorry. We
have some mics that are off.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
19
MAYOR PURCELL: Did I see Mr. Koch's
hand?
ALDERMAN KOCH: Yeah.
MAYOR PURCELL: Please?
ALDERMAN KOCH: Please.
MAYOR PURCELL: Go ahead, guys.
ALDERMAN KOCH: Can you put the drawing
that shows the layout?
MR. OLSON: Yeah. You want like the
overhead-type thing?
ALDERMAN KOCH: The drawing that showed
the buildings from like the --
MR. SILVERMAN: The concept plan?
ALDERMAN KOCH: Yeah. Back further. So
I see these other substation boxes. What are
those actually?
MR. SILVERMAN: Those will be ComEd
facilities that ComEd will actually come in and
build on the property.
ALDERMAN KOCH: So it will come into the
main substation, and then how does it get to
those customer substations? Is that power
lines?
MR. SILVERMAN: We are pretty close to
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
20
the power lines coming through right there, the
power lines cut diagonally through. I think just
a tad east of the area we are going to annex
there is a corridor, you can see on the ComEd
corridor, so the power will jump off of there I
would assume. I don't pretend to be an expert on
that.
And then there is also another one a
little bit to the right that they will run lines
over to.
ALDERMAN KOCH: Yeah, so I seen those
two and I was wondering what the difference is
between a regular ComEd substation and these.
That's my --
MR. SILVERMAN: Matt, do you know?
MR. McCARRON: Yes.
MR. SILVERMAN: Why don't you come over
to the microphone and pick it up?
MR. McCARRON: Yeah, so -- excuse me.
MS. NOBLE: Speak into the mic.
MR. McCARRON: Yeah, so one of them is a
utility switchyard.
MAYOR PURCELL: Matt, can you state your
name?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
21
MATT McCARRON,
testified before the City Council as follows:
MR. McCARRON: I 'm sorry. I am Matt
McCarron. I represent Project Cardinal, Pioneer
Development.
MAYOR PURCELL: Thank you.
MR. McCARRON: So one of them is a
utility switchyard, so typically that's built by
ComEd, and it's going to be taking 345 k V feeds,
so similar to the existing power lines today, and
from there it's brought to a utility switchyard
because the project is tentatively using so much
electricity, it has to be stepped down again to
the customer substations, so it drops to down to
a lower voltage before it's actually utilized by
the data center shells.
ALDERMAN KOCH: And are those above
ground utilities or do you bury those?
MR. McCARRON: It's up to ComEd's
discretion.
ALDERMAN KOCH: Okay.
MS. WILLRETT: Just real quick, if
everybody could speak directly into the
microphone. Everybody on Zoom cannot hear you.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
22
ALDERMAN KOCH: And the other question
regarding the elevation and the little difference
there, are these -- are you able to -- have you
ever thought about like -- These are ground
level, right, the buildings?
MR. McCARRON: Correct, yes.
ALDERMAN KOCH: Could you set them down
a little bit to offset that elevation issue?
MR. McCARRON: There is going to be some
grading done on-site, but no, we wouldn't be
really like going down underground.
ALDERMAN KOCH: I didn't know if you
could drop it down when you build them, just for
my knowledge.
MR. McCARRON: Yeah, no one has ever
asked me that question before, but we can circle
back with the engineers, but typically we do not
do that.
MAYOR PURCELL: Other Council members?
Mr. Soling.
ALDERMAN SOLING: In regards to your
discharge of water, has there been studies done
with what kind of impact you would have on the
local sanitary districts?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
23
MR. McCARRON: Yes, so there has been
preliminary stormwater sanitary done. There is
not going to be any adverse impact given that we
are using, as Bart mentioned in his presentation,
roughly less water than what a multi-family
community would be on a per-acre basis.
ALDERMAN SOLING: So no glycol, no heavy
metals, no --
MR. McCARRON: No, no, no. There's not
going to be any discharge of any chemicals
whatsoever. So typically, like glycol as you
mentioned, is used for like immersion tanks for
cooling purposes, but that would not be
discharged. That runs in a closed loop system
and is recycled.
ALDERMAN SOLING: Thank you.
MAYOR PURCELL: Other questions from
Aldermen? Mr. Funkhouser, do you have others?
Of course you do.
ALDERMAN FUNKHOUSER: I have plenty of
questions and comments, most are not related to
just the annexation specifically, which I know
will vet out as we go through the process of the
development agreement because that's where most
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
24
of this would come in.
The rooftop units, will they end up
being on the roof or will they be interior to the
building ultimately with the technological
changes that we're seeing? That's one that I
think eliminates the issue I have with the height
of the buildings.
The perimeter ten-foot buffer that
we're getting -- or, I 'm sorry, easement we're
getting for the trails, ten foot is being
provided. Is the developer going to be providing
a trail with the roadway improvements?
These are the kind of questions I
would like to have clarified as we're going
forward towards the agreement.
I know we've talked about the
process of starting from the west, working to the
east; obviously there is some county residents
out there that are adjacent to that, so when we
say we're trying to keep it away from the
residents, we're keeping it away from the city
residents, but that doesn't actually apply to the
county residents, so I want to address that. I
know you guys have your phasing and your
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
25
planning.
Fencing around the property, I did
hear that there was going to be no chain link,
that's good, I appreciate that.
I wanted to clarify that the
utilities, which are substations, are those being
held to the city standard or is that going to be
independent and something that ComEd has their
own oversight where they can say we're just going
to do a 10-foot chain link fence? If you could
look to a clarification on something of that for
me, I appreciate that.
There will be a litany of others,
but those are just a couple of the general
comments that I had as I am reviewing the
documents that we've been provided so far.
MAYOR PURCELL: Any other Aldermen?
(No response.)
MAYOR PURCELL: I have a couple
questions. First was for Krysti, and I know
you've answered this, but I forget the answer.
Is the annexation separate from the
zoning or will they go concurrently?
MS. NOBLE: So they will be separate
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
26
documents, but they will be reviewed and voted
upon concurrently.
MAYOR PURCELL: Okay. But they are
separate documents. Okay.
Then some thoughts, and as
Mr. Funkhouser stated, some of these items are
not going to be fleshed out tonight, but figure
you should hear them, something I just thought of
here tonight.
What if it's not built out in
whatever you're expecting, 10, 20 years, would
you consider donating the remainder of land to
the city?
The next thing is a big concern, and
I know Bart's expressed -- initially has
expressed and shared with you some of our
thoughts on impacts to the community, et cetera.
And, Matt, I don't know where you
live, Dave I know you are real familiar with this
area. Property taxes are a huge concern. We
have a burgeoning school population. The school
is going to need several hundred million dollars
most likely for buildings.
I 'd like you to consider upfronting,
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
27
writing a check to the school district for that.
And then also the HVAC, I know Bart
has told me, I trust him, he does an amazing job,
they're learning or we're learning that some of
these data centers put their HVAC on the ground
in a courtyard. Maybe that's what you guys do
somewhere else, I don't know, but I would like
you to consider that, too.
So those are my thoughts for
tonight. I can't tell you all m y other thoughts,
that is my prerogative to add them whenever I 'd
like, but just want to get those out there right
now publicly, okay? Appreciate it.
Any other aldermen have questions?
(No response.)
MAYOR PURCELL: So now I 'm going to open
it up to public comments, so you'll have to
remind me, Bart, Kathy, Jori, Chris even, we're
going to allow public comments from the folks
here, but I know we have some questions from
people on Zoomland --
MR. OLSON: Yeah.
MAYOR PURCELL: -- and they may have
questions, too, so, Bart, how would you like to
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
28
handle it?
MR. OLSON: I think maybe everybody in
the room maybe can speak and then I can kind of
go through and then recite the questions in Zoom
and then answer them as I can, or the developer
can answer them as they can.
MAYOR PURCELL: Sounds good. Let's open
it up for public comment. Again, we just ask
that you state your name for the record. You
don't have to state your address or anything,
just state your name. And let's go.
BERNIE WEILER,
testified before the City Council as follows:
MR. WEILER: Once again, my name is
Bernie Weiler. I am a partner of the firm of
Mickey, Wilson, Weiler, Renzi, Lenert & Julian,
and I represent a number of the homeowners who
live directly across Ashe Road from -- to the
west of this development.
One of the things that I want to
indicate is that there have been significant
discussions with regard to this and we are happy
to see that the development department has been
very contentious with regard to the study of the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
29
impact that these data centers have on the
community, and we have also had -- the developer
and its attorney have been very gracious in
meeting with the residents and discussing the
impact that this has, and I can see from our
first meeting a few weeks ago until now that a
number of those concerns have already been
addressed with regard to how the development is
going to be staged with regard to center in
versus perimeter out, and also the addressing of
the setback of the 7 0 -foot buildings and also the
consideration of perhaps putting the rooftop
units on the ground.
So there have been some productive
discussions, but I think there needs to be --
before we get into the details of an annexation
agreement, these things need to be further
addressed.
One of the things that we need to
consider is that the plan is to dedicate 3 ,000
acres of essentially contiguous property or very
close to contiguous property to a single use.
These uses are not a typical
development use in which it contributes to the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
30
communication of one portion of your community to
the other, these are closed to the public access,
and when you look at -- you know, one of the
comments is there is going to be more trees than
there are with regard to the agricultural use.
You have to consider that in a
typical development, that's where a community
obtains its reforestation, because as you are
taking farmland, you are developing it into
developments that have interior landscaping that
create a greater forestation canopy, and so if
you look at this development, you see a very,
very thin belt of -- and even though you look at
it as screening, it does not achieve the interior
forestation that you would have in other
developments, so I think that needs to be
addressed, and I think that question came up
at -- one of your aldermen had indicated that to
be a concern at the -- at the presentation that
was done at the previous development committee
meeting.
Once again the question came up, and
I have talked to Dave about this and he had
addressed this, the annexation agreement as
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
31
currently drafted has as a default, if it's not a
data center, some uses that would automatically
apply.
That creates a conundrum when we do
go and address the zoning issue, is that now you
are actually not responding to a zoning question,
you are responding to what amounts to a planning
question, okay?
So that -- you know, so the question
is if it's not going to be a data center, is it
going to be car dealerships and big box stores,
which are part of the consideration in the
current agreement.
So I think there is a lot of things
that have been -- there has been a lot of
productive questions that have been addressed and
I think there's been a lot of productive
responses to some concerns, but I don't think
that we are at the point where we have an
annexation agreement that everyone can understand
what's going to happen and what this is going to
look like. Okay?
So, you know, we would like to see a
schedule in which the community could have a
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
32
better understanding of what this is going to
look like.
With regard to the noise issue, it's
one thing to calculate the decibels, it's another
thing to analyze noise at a constant -- at a
constant frequency over a long period of time, so
even though a humming might not be -- reach a
decibel level, it can also be deleterious to
people who are around it, so we want to be able
to address that as well. Some of our people are
very concerned about that.
The other issue is that with regard
to the sanitary district, the question I don't
think was answered with -- was answered on the
basis of stormwater, but if we have all of this
water use, where is that water going?
Is it going to be recycled or is it
going to -- is that going to be discharged as
stormwater or is it going to go into the sanitary
sewer system, so -- you know, as you are using
this water for cooling purposes.
So there are a number of -- there
are a number of issues that we would like to see
addressed. We would like -- the developers have
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
33
graciously agreed to meet with our homeowners
again to talk about these -- these issues, and,
you know, one of our other concerns is that even
though there are significant setbacks, those
setbacks are consumed -- this is where all of the
detention is, so that the setbacks are looking
over flat water as opposed to variegated, you
know, landscaping, so your green space is not on
the exterior of the building, it's on the
interior of the site. So those are the things
that we would like to continue to discuss.
We are encouraged by the
responsiveness to the questions that we've had.
As I have indicated, many of those questions have
been addressed between the meeting three weeks
ago and today, so we are encouraged by the
concern that the development commission has --
the development department has had to the
concerns of the residents and their responses to
it, so, you know, we look forward to further
discussion on that.
MAYOR PURCELL: Thank you for your
comments. Appreciate it.
Who else would like to speak? Just
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
34
state your name.
JAMIE DAMITZ,
testified before the City Council as follows:
MS. DAMITZ: My name is Jamie Damitz and
I live in the Bristol Bay subdivision. We were
able to attend the meeting via Zoom with --
sorry, remind me of your name.
MR. McCARRON: Matt .
MS. DAMITZ: Matt . He did a great job
explaining what the property will look like and
what it will have for the community.
I just have a question with how much
power it's going to be using. Have these
buildings ever been used -- I know you can't
supply all your power with solar, but would solar
offset the amount of power that's being required?
MR. McCARRON: Do you want me to --
MAYOR PURCELL: Please, yeah. Go up
there.
MR. McCARRON: I will just stay up
there.
MAYOR PURCELL: That way we can catch it
on the record for the court reporter.
MR. McCARRON: Yes, so we are working on
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
35
what the cogen component is going to be, so there
is nothing been definitive yet, but potentially
there could be solar that is offsetting any power
usage, and over the course of probably like the
next year or so we will be more clear on it.
MS. DAMITZ: Okay. And then in the
meeting that you did with Bristol Bay residents
on Zoom you said that the landscaping and berming
I think would be completed before any buildings
were up. Is that correct?
MR. McCARRON: Yeah. So the first thing
with these developments, typically you do site
grading, so we are going to be utilizing as much
dirt as possible, and if we have to get more
dirt, we are going to do that to basically have
the berms, and then there would be vegetation
that's planned along the berm work to make as
dense an area as possible before the bulk of the
construction work begins.
MS. DAMITZ: And then the Mayor already
brought up this next point, our school district
already is in kind of a crisis with being
over-populated and not having enough buildings,
but having funding prior to seeing any positive
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
36
income for the city would help to alleviate that.
There is currently a creek called
Rob Roy Creek that runs on 47. Has there been
any decision about what happens with that when
this is built? Does that remain?
MAYOR PURCELL: It will remain. I don't
think they have talked about changing the course
at all.
MR. McCARRON: Yeah, we are not touching
or disturbing Rob Roy Creek at all.
In regards to school upgrades or
improvements, we are planning on tackling that
once the project is fully entitled, so basically
once we have an answer from ComEd, I think we can
get more into the details on that.
MAYOR PURCELL: And just a side note,
the Rob Roy Creek, that drainage district log
goes back like a hundred years. That's really
kind of -- somebody is shaking their head, yeah,
that -- for them to change that is like an act of
God. It really is.
MS. DAMITZ: All right. And then my
last one was from the meeting that we had on
Zoom. There is supposed to be nature trails that
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
37
are accessible to the public on their grounds,
and we possibly talked about there being some
sort of passageway or walkway connecting Bristol
Bay to those paths.
With the security fencing that's
going up around the buildings, that wouldn't
impact access to the trails, correct?
MR. McCARRON: So in regards to the
walking trail, that would not be disturbed. So
the actual security fencing is like pretty
substantial. Again, so like the first shell on
the eastern border along Illinois 47, I think
it's about 700 or 800 feet, yeah, so the actual
security fencing goes around the building, so
it's not going around like after the landscaping
buffer.
And then in regards to the trail and
access point for Bristol Bay, we have actually
already talked about that with our engineers. We
are going to have to talk with IDOT since it's an
IDOT road, but we are definitely open to that,
and as of today, like we are thinking about since
they are making an upgraded bridge tentatively on
the corner of Galena and 47, of having an
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
38
entrance there, so there would be a sidewalk on
the eastern edge of Illinois 47, cutting down,
and then a pedestrian crosswalk across the
street.
MR. OLSON: And then just to clarify.
Matt, you said the fence is inset. Is it this?
MR. McCARRON: Correct, yes. That is
the fence.
MR. OLSON: So it kind of hugs the
building pad line as opposed to being way out
here where the trail would be.
MS. DAMITZ: Thank you.
MAYOR PURCELL: Matt, I have a couple
questions, and again, I may be out on leads, more
leads than we need to get to, but have you ever
stocked any of those ponds for fishing?
ALDERMAN KOCH: I was thinking -- I was
thinking the same thing.
MR. McCARRON: Given the amount of
water, I think that sounds like a good idea.
MAYOR PURCELL: Excellent. Bass? I
heard they were tasty.
Next question, and you mentioned
this, or David did, how many buildings again are
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
39
you looking at?
MR. McCARRON: There are 14 buildings.
MAYOR PURCELL: 14 now, okay. And at
full build-out -- and I get it, things change --
but today, if you build out the 14 buildings,
what do you estimate the value of that total
project would be for the community?
MR. McCARRON: The total value of the
project itself?
MAYOR PURCELL: Yes.
MR. McCARRON: We are going to keep that
confidential.
MAYOR PURCELL: Okay. Is it like more
or less than like a Chicago Bears stadium?
MR. McCARRON: Yes, it would be more
than a stadium.
MAYOR PURCELL: Okay. Just checking.
Thank you. Okay.
Other comments from the public?
Please step forward, state your name.
DAVID HOLTZMAN,
testified before the City Council as follows:
MR. HOLTZMAN: So my name is David
Holtzman. I am from Bristol Bay.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
40
As I 've heard different
presentations, I 've heard different statements on
where we are starting at. From the city's
perspective, we were starting west and going
east, and then when Mr. Silverman was speaking,
he said most likely, and then I 've heard from
another person that they're starting from the
center and working their way out.
I would like to know which one of
these things is where we are starting the
building at. Are we starting in the center or
are we starting at the west or is it a most
likely?
Because I don't feel like I have a
real clear picture of where we are starting this
project at, because I 've heard west, we are
starting in the west and working our way east,
and I 've heard most likely.
So that makes me feel very
uncomfortable with where we are starting this
project at. I would just like a definitive
answer on where we are starting.
MAYOR PURCELL: So I will be upfront
with you, you are not going to get that
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
41
definitive answer tonight. The city and staff,
we have expressed our preference, but there is no
development agreement yet, so we do not have a
specific answer to that question.
MR. HOLTZMAN: Okay. Thank you.
MAYOR PURCELL: Sure. Other questions
or comments?
KEITH LANDOVITZ,
testified before the City Council as follows:
MR. LANDOVITZ: Good evening. Keith
Landovitz, 275 Ashe Road. My wife and I live
across the road due west of the subject property.
First, I just want to reiterate a
couple of Mr. Weiler's acknowledgments. There
was a meeting, which I understand was quite
productive, or some number of meetings, with
different sets of the nearby residents.
I appreciate that. My wife and I
were not able to a ttend the first meeting due to
a personal scheduling conflict, but I anticipate
that those conversations will be ongoing.
I had a favorable report from my
neighbors of the first conversation, so I 'm --
that's -- that to me is a good start.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
42
I also acknowledge and commend the
city's officials for their care in learning about
best practices for this type of use and trying to
implement those in Yorkville to make this a world
class exemplar of this type of use.
So with that said, most of my
concerns strictly speaking are probably PUD
details and, therefore, inapposite to the instant
matter, so I will reserve kind of detailed
comments about those for the appropriate
hearings.
I have one concern directly about
the annexation agreement. I say had because it
may be moot in light of Alderman Funkhouser's
question and Mr. Silverman's responsive comments.
I am concerned about the alternative
uses that the draft version of the annexation
agreement contemplates. Those uses and my
appreciation of them are quite different to what
I might call modern manufacturing, industrial
uses, of which data center use is I believe
noticeably low impact.
Those other contemplated uses are
more, again, to my appreciation, commercial uses,
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
43
which have much greater potential for generating
traditional types of nuisance.
So, again, I am hoping, and it
sounds like we are all agreed, that it's going to
be data center or nothing, and I hope that that
will be the case.
I have two further comments which
are about things directly. Again, most of my
concerns will be addressed in due course through
the meetings with the developer and through
hearing, PUD hearings, but it seems to me that
the contemplated annexation -- of course, an
agreement is for the purpose of something being
annexed, so I think it's relevant.
The contemplated annexation has a
couple of important implications to which I want
now to call attention. First, I note that the
concept plan, the site concept plan, does not
depict two existing residential driveways on Ashe
Road, so I do have a concern about what's
depicted, and in general a concern about traffic
on Ashe Road.
Obviously if the property that's the
subject of this hearing were not annexed, it
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
44
would change the feasible transportation plan for
the site, so I do hope that the annexation
notwithstanding entrance and egress on Ashe Road
will not be part of the final plan and that Ashe
Road will continue to be a corridor for
residential access.
I should note in that regard, I
neglected to say earlier, my wife and I , our
property is not part of the Estates at Legacy
Farm residential subdivision, we are immediately
to the south of that, but we are not part of the
subdivision and our access to Ashe Road is not
from the subdivision roads, from their entrance
or exit.
Second, and this -- others have
alluded to this, the concern about building from
the west versus building from the center of the
proposed project site, obviously from the west
means something very different if the subject
property is annexed because that means from the
west it is much closer to my residence than it
would otherwise be.
I am concerned, Mr. Olson's
presentation made reference to mitigating impact
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
45
or nuisance to citizens of Yorkville. I do voice
an equal protection concern about that.
I hope that all -- in terms of
mitigating nuisance, all people in the vicinity
of the development are considered equally
regardless of the jurisdiction in which they
live, and certainly I acknowledge that the
meetings with the developers have been agnostic,
too, and have been structured in no way to favor
Yorkville residents versus residents of other
jurisdictions, but that remains a concern for me
in terms of how the site will be developed, and,
again, I advocate for an approach that will
develop from the center out as being most
equitable to all who live in the vicinity.
So thank you very much. I
anticipate further good conversations with the
developer. So thank you.
MAYOR PURCELL: Thank you. Others?
JACK SCHLUETER,
testified before the City Council as follows:
MR. SCHLUETER: Hello. My name is Jack
Schlueter. I am a resident of 73 Ford Drive on
the south side of town. I am also a licensed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
46
professional engineer with like about ten years
of industrial capital project experience, so I am
very familiar with industry and manufacturing
like this in general.
So under this proposal the
manufacturing center would be the first thing you
see when you enter Yorkville coming from the
north, so I guess our sign can say welcome to
Yorkville, home of high tech data centers .
And I think that could be a good or
bad thing, it's just a question of is this what
we want Yorkville to be when it grows up.
I believe manufacturing can be good
for our community. I reviewed the proposal and
I -- you know, I couldn't find an estimate for
how many permanent jobs or how many temporary
construction jobs it's expected to create, but
like you mentioned earlier, Bart, I know there
will be some, it's a data center, so -- but there
is not as many as a larger build-out, but -- and
also tax revenue generation obviously you touched
on earlier, but annexing this land and proceeding
with this proposal would also be a fairly
significant land use change that deviates from
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
47
the 2016 community vision and land use strategy.
So going ahead with this proposal
and additional data center proposals and
industrial proposals on that side of town likely
extends that North Eldamain development corridor,
which is currently now the north side of the
railroad tracks and Faxon -- or yeah, north side
of the railroad tracks and Faxon and Eldamain up
to the lettuce plant at Corneils, it was sort of
the previous bucket for industrial land use
inside Yorkville.
So when you stick the -- this
development further north on Eldamain up at the
corner of Base Line by Ashe, you basically
squeeze out any other non-industrial development
between this existing -- the existing industrial
corridor and the future development, or this
proposed development by this project.
And, again, that might be good for
some people, bad for some people, but I wouldn't
want to live or run in a business like -- live in
a place or run a business squeezed in between two
industrial parks, so you're committing to making
that whole corridor industrial essentially, and
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
48
it starts to be a significant amount of land
slated for industrial use in our city.
So just a couple general questions
for the Council and for I think for the community
at-large that I am considering are do we want
that much manufacturing in Yorkville and is M -2
zoning really a vision for all that land?
If we're going to change the planned
use from what it currently is today, is this the
best thing we can do for the land and for our
community, and is there opportunity cost in
locking in that land and committing it to
industrial use or is there something else we
could do with it that could maybe make our
community better.
And, you know, just kind of boils
down to, again, i s that block of land as an
industrial use what we want Yorkville to be when
it grows up.
Thank you.
MAYOR PURCELL: Thank you very much.
Other comments?
MAGDALENA EMMERT,
testified before the City Council as follows:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
49
MS. EMMERT: Hi. My name is Magdalena
Emmert. I am a resident of Bristol Bay, and I
definitely see the benefit, the economic
benefits, that a project like this could bring to
our town, especially if it's going to help our
schools where we're having a problem with our
population. So I do have a couple of questions.
Thank you for -- obviously, living
so close to the development, noise and light
pollution are definitely a concern for me and for
our family and I know for the residents, so I am
glad to hear that you guys have already
considered those issues.
Now, a couple of things that I have
not heard is, first, actually the neighbor right
across the street from me drives by a data center
every day and she says that every time that she
drives by and she is on the phone, the phone --
the phone call drops, and as soon as she passes,
it's all fine.
So a question is for you guys, can
you speak of whether a large scale data center
like this could impact cell service, wifi or
other wireless connectivity near the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
50
neighborhoods, and are there any known issues
related to electromagnetic interference or signal
disruption that you are aware of. That's the
first question.
The second is actually -- My husband
could not be here tonight, but he has a question
about just security. He says given the scale of
the facility and the role the data centers can
play in national or corporate infrastructure, are
there any considerations or potential security or
terrorism-related risks?
What kind of physical and
cybersecurity protections will be in place and
how will those measures ensure the safety of the
surrounding community?
Also, is the facility considered a
potential target under the national security
guidelines?
Those were the questions, so, that's
it.
MAYOR PURCELL: Thank you. Any thoughts
on those tonight? Matthew.
MR. McCARRON: So in regards to E MF
interference, we are not envisioning there being
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
51
any problems. We already did a preliminary study
related to that and nothing popped up that would
affect cell signal or anything of that nature.
In regards to potential terrorism
activity, I know that is an ongoing concern given
that this is going to be digital infrastructure
that's like the backbone basically for the United
States.
I have heard murmurings that there
could be a Homeland Security office opening out
here to alleviate some of those concerns, and we
are having, if the project is entitled as
envisioned, significant security aspects to make
sure the facility is safe and to basically, you
know, thwart any negative -- or any negative
things potentially happening, and also working
with the great Yorkville Police Department.
MR. OLSON: A couple comments on
security and terrorism concerns. So the CyrusOne
facility that's off of Eola and 88, city staff
toured that last year. You know, in addition to
having, you know, fencing around the entire
thing, you know, in order to even get in, you
have to have an appointment, they don't accept
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
52
walk-ins.
There is double-gated entrances, so
they'll actually like, you know, scan your car
for explosives before you go in, and then, you
know, everything obviously is secure even once
you get inside.
Some months ago as we were talking
to the Loudoun County, Virginia staff, they had
mentioned that the Department of Homeland
Security and probably the FBI would eventually
reach out to us to kind of just talk through
different issues as it relates to terrorism
concerns or building security and anything else,
so we then proactively reached out to the
Department of Homeland Security, had a meeting
with them six months ago probably.
CHIEF JENSEN: Yes.
MR. OLSON: And their main concern is
physical building site security, you know,
infrastructure concerns, so they didn't have
anything that they wanted us to do immediately,
but, you know, we are familiar with the contacts
there.
They said that they would be happy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
53
to actually like review building plans, and then
after it's constructed to kind of conduct
assessments on the building from that side, and
then they put us in touch with the Chicago FBI
office that deals with cybersecurity issues, and
so we are in touch with the head of that just in
case anything comes up.
So they said because we are still in
the planning phase there isn't anything that we
need to do at this time, but, you know, as things
land and start to get constructed that they then
might have some, you know, briefings for us at
that point.
MAYOR PURCELL: Thank you, Bart. Other
questions or comments from anyone here?
(No response.)
MAYOR PURCELL: Bart, you received
several comments on Zoom?
MR. OLSON: Yes. I will just go back
through them and I will read the ones that have
already been typed in for the people that are on
Zoom, and then if you want to unmute at the end
of it, I will call and then, you know, people can
unmute and then speak.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
54
So first comment is just a
compliment for the Mayor about the impact fee and
school districts, so not really a question.
And then there is a question from
April. Last night it was stated building eight
first, which is in the middle of the property,
but tonight twice west to east.
So I think this gets to the question
that was posed in the room and the Mayor
articulated, you know, in general we would prefer
that the buildings be constructed -- in general
the staff feels it would be a benefit for the
buildings to be constructed as far away from as
many residences as possible, then moving closer
to residents towards the end of it.
And so, you know, to I think another
commenter's point, there are some residents on
the west side, there are some residents on the
east side, so we will take that into account, and
there is different things that we will need to
talk through with construction noise and phasing,
and probably the sound engineer would need to
weigh in.
A concept I think that was posed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
55
post-meeting, last EDC meeting that we had on
this a month and a half ago, was that if you
construct buildings like on the west end first,
it may actually buffer properties to the west, or
if you start on the east end and then go the
other way, it might actually buffer noise from
further construction on the interior on the
farther end of the site, and so that's something
that we would have to take into account.
So, you know, I think that's open
for conversation, appreciate the feedback. It's
something we will take into account. It still
has to be negotiated or committed between City
Council and the developer when that gets into,
you know, the PUD phase.
And then can we reasonably assume
that $68,000,000 estimated revenue when totally
completed in approximately ten years completion,
that $68,000,000 could be divided over the
ten years fairly evenly.
The slides that I mentioned, the
utility tax numbers provided by the developers
and then the property tax estimates are actually
annual numbers, so you don't have to divide that
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
56
by ten, that's recurring revenue theoretically,
and so that would be the total take when the
developer is built out and then fully using the
site.
A couple comments about, you know,
noise and sound here, and then are there any
security concerns and will there be any
anticipated impact on the police and fire
department, will the fire department need to
purchase any special equipment for this facility.
The fire department has been
involved in our staff level plan council
meetings. They are, you know, part of the
negotiation process. We have talked to them
about how they would build, you know, future fire
stations, identifying land for future fire
stations.
There could be an opportunity where
multiple developers in the area actually donate
either money or land or both or equipment to the
fire department.
But what has been, you know, I guess
reiterated to us is that the amount of tax
revenue that could come in could theoretically
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
57
offset their construction costs, where they may
be able to do a referendum or, you know, just
build and then, you know, pay for that over time
with ongoing property tax revenue. So that's
something that's an ongoing conversation and, you
know, they've got a seat at the table.
I will keep going up. Who does this
developer represent and who is their partners?
So right now Project Cardinal is an LLC, I think
it's based out of Wyoming.
Matt McCarron is here as the
developer representative, and I don't know if
there is any, you know, discussion about users or
investors, or if any of that can be disclosed at
this time.
MR. McCARRON: We are still keeping that
confidential.
MR. OLSON: Okay. So the answer is that
is still confidential at this time.
What will happen with noise
pollution at Bristol Bay, what actions will be
done. There was a slide in the presentation that
talks through the city has comprehensive lighting
codes, and I am speaking very simply, you know,
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
58
light is not supposed to spill over from the
property line under -- onto other properties.
That's not to say that you won't be
able to see it from hundreds of feet away or
maybe even a mile away, as you can most
developments, but we have generally a pretty
modern lighting code, and that will actually be
proven out through a photometric plan that will
be submitted from the developer to the city staff
to make sure that it meets city code and then
approved as part of, you know, the overall PUD
plan for the city.
And then how have the developers
responded Yorkville's requests on the noise
issues. So I will talk specifically about
Project Cardinal because we've had a couple
meetings with them.
I think their initial opinion is
that they will be able to meet our city code for
noise without issue. That will have to be proven
out by land use plan, sound engineering analysis,
placement of chillers, all those other things,
but their distance from most of their buildings
to residential areas is greater than a lot of the
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
59
other data center developments in town, and so
that will be I think a key component of future
City Council approvals as it goes forward.
Does the developer plan to reach out
to the area Building and Construction Trades
Council?
MR. McCARRON: Absolutely. That's
preliminary right now.
MR. OLSON: The answer from the
developer is absolutely, it's preliminary right
now.
Is there anything else you wanted to
share on any of those other questions?
MR. McCARRON: I don't think so
specifically, but one thing I did want to touch
on that I know Dave has talked about and it's
been brought up on a couple of questions, we are
not intending or going to be developing the
property for any other use case besides a data
center campus, so the annexation agreement draft
has already been updated as such, so there is not
going to be any auto manufacturing plants. It's
literally a data center campus or we are not
going to be developing it.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
60
MR. OLSON: At this point we can open it
up to Zoom questions?
MAYOR PURCELL: Please. Please.
MR. OLSON: If anybody on Zoom wants to
unmute, they can, and then speak, or you can type
it in and then I will read it out.
Doesn't look like it.
MAYOR PURCELL: Okay. Council, any
further questions?
(No response.)
MAYOR PURCELL: One last shot, anyone
here have any further questions? Okay.
MR. HOLTZ: I just have one.
MAYOR PURCELL: If you can just step to
the microphone, please. Yes, ask away.
MITCH HOLTZ,
testified before the City Council as follows:
MR. HOLTZ: Yeah. My name is Mitch
Holtz. I live in Yorkville as well.
I just wanted to ask if anyone who
is a part of the decision-making process on
behalf of the City of Yorkville, would any
conflicts of interest related to these projects
be disclosed to the public?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
61
MS. ORR: Yes.
MR. HOLTZ: I assume the answer is yes,
but --
MS. ORR: Yes.
MAYOR PURCELL: Our attorney says yes.
MS. ORR: Yes. We will be sure.
MS. WILLRETT: There is one more
question on Zoom.
MAYOR PURCELL: There is, another
question just popped up.
MR. OLSON: Thank you. If the
development is not fully realized, can part of it
be sold to other developers for other uses not
data centers.
So, and this gets into the
annexation agreement has a list of other uses in
there, and so in other developments, in other
data center developments that we have talked
through that haven't had land uses and don't have
users, we have said we are rezoning it for a data
center, but if it doesn't become a data center,
it can become a bread factory or an auto
manufacturing plant or, you know, whatever those
other uses are, and this developer has actually
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
62
rebutted that and specifically asked for it to be
data center users or nothing, so that is a
concept that we will have to effectuate in a
future development agreement or annexation
agreement clause going forward.
So the concept there would be if we
locked that into place in the development
agreement that the only way that it could become
another use would be for it to be sold to
somebody else and then for the City Council to
approve it through a normal land use process.
MS. ORR: And public hearing.
MR. OLSON: And public hearing.
MAYOR PURCELL: Do these buildings ever
get sold between different users in the industry?
MR. McCARRON: No.
MAYOR PURCELL: No? Okay.
ALDERMAN SOLING: I have one more thing
I would like to add.
MAYOR PURCELL: I was just thinking
about a transfer tax.
ALDERMAN SOLING: So furthering on the
attorney's question about discharge of sanitary,
my understanding is it basically would just be
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
63
like domestic waste, same as it would be for a
subdivision is all you would be discharging then,
so for the local sanitary district, there is no
impact on organic loadings or any of that -- any
of that. Is that safe to assume?
MR. McCARRON: Correct.
ALDERMAN SOLING: Does that answer your
question?
UNIDENTIFIED AUDIENCE MEMBER: Yes.
MAYOR PURCELL: Mr. Funkhouser?
ALDERMAN FUNKHOUSER: One item that I
just would like to have clarified, I have heard a
couple comments on, so there was a question about
the trails, and I want to be clear on what the
intent is here, that the trails that we are
discussing are perimeter to the site, but would
not be internal to the site. So that's the first
part, that that would be the case.
And then there is a couple comments
on some open space and what we have, so I believe
the site shows 41 percent open, so it's pervious,
which is 425 acres.
Aside from the water and the
buffers, that is all going to be generally
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
64
prairie grass, correct?
MR. McCARRON: Yeah, so the trail would
tentatively run the perimeter of the site, so it
would be outside of the berm work I think as
intended and asked.
It could tentatively run, you know,
in and out of the berm work, but it's really
going to be up to you guys, but it's going to be
an undulating berm, so that could be kind of
complicated.
And then as it relates to the
prairie grass, so -- and that's really coming
from your feedback, too, at the unofficial EDC
meeting, but our landscape designer has pushed
forward some changes to have natural prairie
grass elements, so it's not just going to be
grass, because really a lot of that acreage, too,
is owned by ComEd, so we are not technically
allowed to touch it, the ComEd transmission
corridor, but we are trying to basically like
envision something that's similar to the Meig
Field development in Chicago that has like
natural prairie elements and like undulating
hills basically.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
65
ALDERMAN FUNKHOUSER: So to be clear, no
trails interior because, one, it's ComEd, ComEd,
unless they have rights, typically doesn't want
anybody on it, and you have a couple drainage
corridors running through the center of the site
to the basins, so you have barriers there.
MR. McCARRON: Correct. Yeah, there
will be no trail on the interior of the property.
MAYOR PURCELL: Any other questions?
MR. OLSON: There is one more on Zoom.
MAYOR PURCELL: Oh. Go ahead, please.
MR. OLSON: Question for the developer
from Zoom. Is there an anticipated life span of
the data center? Can they become obsolete in a
relatively short time?
MR. McCARRON: No. These powered shells
are being designed for typically a 50 to 75-year
life span, so once you technically have a power
feed, a transmission feed, they are going to be
used for data centers.
The interior equipment, so actually
inside the buildings, like the actual racks that
house the GPU s or TPU s , typically are shrinking
their form factor over time, so basically once
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
66
you build the shell, whether or not it's , you
know, fully consumed by equipment at max capacity
with, you know, more shallow aisles or in the
future more open space, the building is still
utilized.
MAYOR PURCELL: Actually a good question
that was a follow-up to that, do you have some
kind of decommissioning plan? I mean, not you
personally, but the company.
MR. McCARRON: I probably won't be
around in 75 years, but we can work on --
MAYOR PURCELL: I don't plan on running
again.
MR. McCARRON: But who knows, though,
with artificial intelligence, maybe we will all
be here, we will have the same philosophy, but we
can work on a rough decommissioning plan with our
engineers.
MAYOR PURCELL: Okay. We require that
of some, and I thought probably not unfair to
ask, so thank you.
Mr. Koch.
ALDERMAN KOCH: Just thought of
something. So we know how the power would come
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
67
in. How does the data come into these data
centers?
MR. McCARRON: Yeah, so Yorkville and
the greater Chicago region is blessed with
excellent fiber capacity, so it was over-built
before the dot com crash in the late '90s , early
2000s , so there is plentiful fiber running
through Aurora. I think our site itself has
three or four different dark fiber access points,
so that's how it runs to the site.
ALDERMAN KOCH: So it's already there.
MR. McCARRON: It is already there,
yeah. We are not going to be trenching in fiber.
MAYOR PURCELL: Ken, you know, the old
AT&T center out by Plano, they're going to tap
into that from like 197 2 or whatever that was.
I 'm just kidding.
MR. OLSON: And I have then one last
question on Zoom.
MAYOR PURCELL: One last question on
Zoom.
MR. OLSON: Can we clarify when exactly
is the next publicly accessible meeting regarding
the development and is it available on Zoom?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
68
So for Project Cardinal the next
meeting will be --
MS. ORR: Tomorrow.
MR. OLSON: -- tomorrow, Planning and
Zoning Commission public hearing for rezoning,
special use PUD and preliminary PUD plan.
That meeting, though -- and the
public hearing will be opened and continued until
the Wednesday, July 9 th Planning and Zoning
Commission meeting, so you can attend tomorrow
night.
MAYOR PURCELL: What time?
MR. OLSON: 7 :00 p .m . tomorrow.
MAYOR PURCELL: 7 :00 p .m .?
MS. NOBLE: In this room.
MR. OLSON: 7 :00 p .m . on July 9 th, same
room. There will be a different Zoom link
available on the meeting agenda and packet page
on the City website, you know, so you can attend
and comment if you want to.
The developer is not expected to be
present or do a presentation until that July 9 th
meeting.
MAYOR PURCELL: And we won't be here.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
69
Krysti will be here.
MS. NOBLE: I will be here.
MAYOR PURCELL: Two nights in a row,
Krysti. We love you, Krysti.
Any other final questions?
(No response.)
MAYOR PURCELL: Okay. At 9 :0 6 , I will
close the public hearing for Project Cardinal
data center annexation.
(Which were all the proceedings had
in the public hearing, concluding
at 9 :06 p .m .)
---o 0 o ---
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
70
STATE OF ILLINOIS )
) SS:
COUNTY OF LASALLE )
I , CHRISTINE M . VITOSH, a Certified
Shorthand Reporter of the State of Illinois, do
hereby certify:
That the foregoing public hearing
transcript, Pages 1 through 70, was reported
stenographically by me by means of machine
shorthand, was simultaneously reduced to
typewriting via computer-aided transcription
under my personal direction, and constitutes a
true record of the testimony given and the
proceedings had;
That the said public hearing was taken
before me at the time and place specified;
That I am not a relative or employee or
attorney or counsel, nor a relative or employee
of such attorney or counsel for any of the
parties hereto, nor interested directly or
indirectly in the outcome of this action.
I further certify that my certificate
attached hereto applies to the original
transcript and copies thereof signed and
certified under my hand only. I assume no
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
71
responsibility for the accuracy of any reproduced
copies not made under my control or direction.
IN WITNESS WHEREOF, I do hereunto set my
hand at Leland, Illinois, this 24th day of June,
2025.
/s / Christine M . Vitosh
CHRISTINE M . VITOSH,
Illinois C .S .R . Certificate
No. 084-02883
$
$68,000,000 [2] -
55:17, 55:19
'
'90s [1] - 67:6
/
/s [1] - 71:8
0
084-002883 [1] - 3:24
084-02883 [1] - 71:10
1
1 [2] - 15:23, 70:7
1,000 [3] - 8:2, 8:8, 9:8
1,040 [1] - 8:3
10 [2] - 1:20, 26:11
10-foot [1] - 25:10
100 [1] - 3:8
14 [4] - 8:9, 39:2, 39:3,
39:5
140 [1] - 3:13
1500 [6] - 11:20,
11:24, 12:2, 15:13,
17:17
17,000,000 [1] - 8:10
18 [1] - 4:5
1804 [1] - 3:3
1972 [1] - 67:16
2
2-B [1] - 17:20
20 [1] - 26:11
2000s [1] - 67:7
2016 [1] - 47:1
2025 [2] - 1:20, 71:5
21 [1] - 8:3
24th [1] - 71:4
275 [1] - 41:11
3
3,000 [1] - 29:20
300 [4] - 7:23, 9:5,
15:19, 16:4
34 [1] - 4:6
345 [1] - 21:9
350 [1] - 3:3
39 [1] - 4:7
4
41 [2] - 4:8, 63:21
425 [1] - 63:22
45 [1] - 4:9
47 [8] - 6:22, 9:2,
10:23, 15:14, 36:3,
37:12, 37:24, 38:2
48 [1] - 4:10
5
5 [1] - 4:3
50 [1] - 65:17
500 [1] - 10:17
55 [1] - 11:13
6
60 [1] - 4:11
60435 [1] - 3:8
60554 [1] - 3:13
60563 [1] - 3:4
630 [2] - 3:4, 3:14
651 [1] - 1:16
682-0085 [1] - 3:4
7
70 [2] - 11:21, 70:7
70-foot [1] - 29:11
700 [1] - 37:13
73 [1] - 45:23
730-9500 [1] - 3:9
75 [1] - 66:11
75-year [1] - 65:17
78 [1] - 11:14
7:00 [4] - 1:21, 68:13,
68:14, 68:16
7:59 [1] - 5:3
8
800 [1] - 37:13
801-9699 [1] - 3:14
815 [1] - 3:9
822 [1] - 3:8
88 [1] - 51:20
9
9 [1] - 4:4
9:06 [2] - 69:7, 69:12
9th [3] - 68:9, 68:16,
68:22
A
A-1 [1] - 15:23
able [8] - 11:8, 22:3,
32:9, 34:6, 41:19,
57:2, 58:4, 58:19
absolutely [2] - 59:7,
59:10
accept [1] - 51:24
access [6] - 30:2,
37:7, 37:18, 44:6,
44:12, 67:9
accessible [2] - 37:1,
67:23
accomplish [1] - 18:8
account [3] - 54:19,
55:9, 55:12
accuracy [1] - 71:1
achieve [1] - 30:14
acknowledge [2] -
42:1, 45:7
acknowledgments [1]
- 41:14
acre [1] - 23:6
acreage [1] - 64:17
acres [9] - 7:23, 8:3,
8:8, 9:5, 9:8, 15:20,
16:4, 29:21, 63:22
act [2] - 9:7, 36:20
action [1] - 70:20
actions [1] - 57:21
activity [1] - 51:5
actual [4] - 11:12,
37:10, 37:13, 65:22
add [3] - 5:11, 27:11,
62:19
addition [1] - 51:21
additional [1] - 47:3
address [4] - 24:23,
28:10, 31:5, 32:10
addressed [8] - 29:8,
29:18, 30:17, 30:24,
31:16, 32:24, 33:15,
43:9
addressing [1] - 29:10
adjacent [1] - 24:19
Administrator [2] -
2:11, 2:14
adverse [1] - 23:3
advocate [1] - 45:13
aesthetics [1] - 15:1
affect [1] - 51:3
agenda [2] - 5:12,
68:18
agnostic [1] - 45:8
ago [5] - 29:6, 33:16,
52:7, 52:16, 55:2
agreed [2] - 33:1, 43:4
Agreement [1] - 5:9
agreement [26] - 5:8,
5:10, 7:9, 7:24,
15:17, 16:9, 16:10,
16:14, 17:14, 17:20,
18:12, 23:24, 24:15,
29:17, 30:24, 31:13,
31:20, 41:3, 42:13,
42:18, 43:13, 59:20,
61:16, 62:4, 62:5,
62:8
agreements [2] -
16:12, 16:21
Agricultural [1] -
15:23
agricultural [1] - 30:5
ahead [4] - 12:14,
19:6, 47:2, 65:11
aided [1] - 70:10
aisles [1] - 66:3
Alderman [8] - 2:3,
2:4, 2:5, 2:6, 2:7,
2:8, 2:9, 42:14
ALDERMAN [29] -
17:10, 17:13, 18:10,
18:15, 18:23, 19:3,
19:5, 19:7, 19:11,
19:14, 19:20, 20:11,
21:17, 21:21, 22:1,
22:7, 22:12, 22:21,
23:7, 23:16, 23:20,
38:17, 62:18, 62:22,
63:7, 63:11, 65:1,
66:23, 67:11
Aldermen [2] - 23:18,
25:17
aldermen [2] - 27:14,
30:18
alleviate [2] - 36:1,
51:11
allow [2] - 9:6, 27:19
allowed [1] - 64:19
alluded [1] - 44:16
ALSO [1] - 2:10
alternative [1] - 42:16
amazing [1] - 27:3
amount [5] - 11:17,
34:16, 38:19, 48:1,
56:23
amounts [1] - 31:7
analysis [1] - 58:21
analyze [1] - 32:5
annex [1] - 20:3
annexation [27] - 5:7,
5:10, 7:9, 7:18, 7:24,
9:5, 15:17, 15:19,
16:8, 16:14, 17:14,
17:19, 18:18, 23:22,
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
1
25:22, 29:16, 30:24,
31:20, 42:13, 42:17,
43:12, 43:15, 44:2,
59:20, 61:16, 62:4,
69:9
Annexation [1] - 5:8
annexed [7] - 7:20,
8:5, 15:23, 15:24,
43:14, 43:24, 44:20
annexing [1] - 46:22
annual [1] - 55:24
answer [16] - 7:2, 7:3,
7:16, 17:1, 17:4,
25:21, 28:5, 28:6,
36:14, 40:22, 41:1,
41:4, 57:18, 59:9,
61:2, 63:7
answered [3] - 25:21,
32:14
answers [1] - 7:4
anticipate [2] - 41:20,
45:17
anticipated [2] - 56:8,
65:13
apologize [1] - 14:16
appearance [1] - 14:9
APPEARANCES [1] -
3:1
appeared [3] - 3:5,
3:10, 3:15
applies [1] - 70:22
apply [2] - 24:22, 31:3
appointment [1] -
51:24
appreciate [6] - 17:5,
25:4, 25:12, 33:23,
41:18, 55:11
Appreciate [2] - 18:16,
27:13
appreciation [2] -
42:19, 42:24
approach [1] - 45:13
approaches [1] - 10:9
appropriate [1] -
42:10
approval [1] - 16:6
approvals [1] - 59:3
approve [1] - 62:11
approved [3] - 16:10,
17:21, 58:11
April [1] - 54:5
Arden [1] - 2:6
area [8] - 10:7, 12:10,
15:11, 20:3, 26:20,
35:18, 56:19, 59:5
areas [2] - 15:3, 58:24
articulated [1] - 54:10
artificial [1] - 66:15
Ashe [9] - 9:3, 28:18,
41:11, 43:19, 43:22,
44:3, 44:4, 44:12,
47:14
aside [1] - 63:23
aspects [1] - 51:13
assessments [1] -
53:3
assist [1] - 16:19
Assistant [1] - 2:13
associated [2] - 13:3,
13:19
assume [5] - 20:6,
55:16, 61:2, 63:5,
70:24
AT&T [1] - 67:15
at-large [1] - 48:5
attached [1] - 70:22
attend [4] - 34:6,
41:19, 68:10, 68:19
attention [3] - 15:7,
15:10, 43:17
attorney [5] - 6:13,
29:3, 61:5, 70:17,
70:18
attorney's [1] - 62:23
AUDIENCE [1] - 63:9
Aurora [1] - 67:8
auto [2] - 59:22, 61:22
automatically [1] -
31:2
available [2] - 67:24,
68:18
aware [2] - 10:22, 50:3
B
B-3 [1] - 16:1
backbone [1] - 51:7
bad [2] - 46:11, 47:20
barbed [1] - 11:6
Barksdale [1] - 2:20
Barksdale-Noble [1] -
2:20
barriers [2] - 12:9,
65:6
Bart [10] - 2:11, 10:15,
13:21, 23:4, 27:2,
27:18, 27:24, 46:18,
53:14, 53:17
Bart's [1] - 26:15
Base [3] - 9:4, 15:6,
47:14
based [2] - 17:22,
57:10
basins [1] - 65:6
basis [2] - 23:6, 32:15
bass [1] - 38:21
Bay [9] - 7:1, 15:12,
34:5, 35:7, 37:4,
37:18, 39:24, 49:2,
57:21
bays [1] - 14:11
bears [1] - 11:10
Bears [1] - 39:14
become [4] - 61:21,
61:22, 62:8, 65:14
begin [1] - 16:11
begins [1] - 35:19
behalf [4] - 3:5, 3:10,
3:15, 60:22
BEHLAND [1] - 5:9
Behland [1] - 2:12
belt [1] - 30:13
benefit [4] - 14:1,
18:1, 49:3, 54:12
benefits [3] - 13:22,
16:18, 49:4
berm [4] - 35:17, 64:4,
64:7, 64:9
berming [9] - 10:19,
11:1, 11:3, 11:9,
12:21, 14:14, 14:23,
15:10, 35:8
berms [3] - 10:21,
12:15, 35:16
BERNARD [1] - 3:12
Bernie [1] - 28:15
BERNIE [2] - 4:5,
28:12
best [2] - 42:3, 48:10
better [4] - 12:18,
16:20, 32:1, 48:15
between [6] - 20:13,
33:15, 47:16, 47:22,
55:13, 62:15
big [3] - 13:1, 26:14,
31:11
bit [2] - 20:9, 22:8
blessed [1] - 67:4
block [1] - 48:17
blue [1] - 7:19
board [1] - 7:8
boils [1] - 48:16
border [1] - 37:12
bordered [1] - 9:2
Boulevard [2] - 3:3,
10:7
box [1] - 31:11
boxes [1] - 19:15
brad [1] - 2:22
bread [1] - 61:22
bridge [1] - 37:23
briefings [1] - 53:12
bring [2] - 8:22, 49:4
Bristol [9] - 7:1, 15:12,
34:5, 35:7, 37:3,
37:18, 39:24, 49:2,
57:21
brought [3] - 21:11,
35:21, 59:17
brown [3] - 12:17,
12:20, 14:14
bucket [1] - 47:10
buffer [4] - 24:8,
37:16, 55:4, 55:6
buffered [1] - 15:14
buffers [1] - 63:24
build [10] - 9:17,
18:11, 19:19, 22:13,
39:4, 39:5, 46:20,
56:15, 57:3, 66:1
build-out [3] - 9:17,
39:4, 46:20
Building [1] - 59:5
building [24] - 9:10,
10:18, 11:13, 11:21,
12:22, 13:10, 13:11,
13:14, 13:20, 14:10,
15:13, 24:4, 33:9,
37:14, 38:10, 40:11,
44:16, 44:17, 52:13,
52:19, 53:1, 53:3,
54:5, 66:4
buildings [31] - 8:9,
9:12, 9:13, 11:12,
12:1, 12:7, 12:12,
12:24, 13:2, 13:6,
14:6, 15:1, 19:12,
22:5, 24:7, 26:23,
29:11, 34:14, 35:9,
35:23, 37:6, 38:24,
39:2, 39:5, 54:11,
54:13, 55:3, 58:23,
62:14, 65:22
built [10] - 9:9, 9:12,
9:13, 10:4, 13:5,
21:8, 26:10, 36:5,
56:3, 67:5
bulk [1] - 35:18
burden [1] - 14:3
burgeoning [1] -
26:21
bury [1] - 21:18
business [2] - 47:21,
47:22
BY [4] - 3:3, 3:7, 3:12,
3:23
C
C.S.R [2] - 3:24, 71:9
calculate [1] - 32:4
cam [1] - 8:17
campus [6] - 8:13,
8:17, 9:7, 13:13,
59:20, 59:23
cannot [2] - 18:21,
21:24
canopy [1] - 30:11
capacity [2] - 66:2,
67:5
capital [1] - 46:2
car [2] - 31:11, 52:3
Cardinal [13] - 3:10,
3:15, 5:6, 6:17, 7:20,
8:1, 8:7, 8:23, 21:4,
57:9, 58:16, 68:1,
69:8
care [1] - 42:2
case [5] - 10:12, 43:6,
53:7, 59:19, 63:18
CASTALDO [1] - 3:2
catch [1] - 34:22
cell [2] - 49:23, 51:3
center [32] - 9:8, 9:17,
13:13, 17:23, 18:3,
18:5, 21:16, 29:9,
31:2, 31:10, 40:8,
40:11, 42:21, 43:5,
44:17, 45:14, 46:6,
46:19, 47:3, 49:16,
49:22, 59:1, 59:20,
59:23, 61:18, 61:21,
62:2, 65:5, 65:14,
67:15, 69:9
Center [1] - 5:7
centers [9] - 8:11,
13:4, 27:5, 29:1,
46:9, 50:8, 61:14,
65:20, 67:2
certainly [3] - 7:4,
7:15, 45:7
Certificate [1] - 71:9
certificate [1] - 70:21
Certified [1] - 70:3
certified [1] - 70:24
certify [2] - 70:5,
70:21
cetera [1] - 26:17
chain [3] - 11:5, 25:3,
25:10
change [6] - 8:15,
36:20, 39:4, 44:1,
46:24, 48:8
changed [1] - 17:23
changes [2] - 24:5,
64:15
changing [1] - 36:7
check [1] - 27:1
checking [1] - 39:17
chemicals [1] - 23:10
Chicago [4] - 39:14,
53:4, 64:22, 67:4
CHIEF [1] - 52:17
Chief [1] - 2:17
chillers [1] - 58:22
Chris [2] - 2:7, 27:18
Christine [2] - 3:23,
71:8
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
2
CHRISTINE [2] - 70:3,
71:9
circle [1] - 22:16
citizens [1] - 45:1
CITY [2] - 1:6, 1:9
city [26] - 6:18, 7:5,
7:10, 7:20, 10:14,
10:24, 11:1, 13:24,
14:8, 16:2, 16:22,
18:1, 18:5, 24:21,
25:7, 26:13, 36:1,
41:1, 48:2, 51:20,
57:23, 58:9, 58:10,
58:12, 58:19
City [20] - 2:11, 2:12,
2:13, 2:22, 3:5, 6:10,
17:5, 21:2, 28:13,
34:3, 39:22, 41:9,
45:21, 48:24, 55:13,
59:3, 60:17, 60:22,
62:10, 68:19
city's [2] - 40:3, 42:2
clarification [1] -
25:11
clarified [2] - 24:14,
63:12
clarify [3] - 25:5, 38:5,
67:22
class [1] - 42:5
clause [1] - 62:5
clear [4] - 35:5, 40:15,
63:14, 65:1
Clerk [1] - 2:12
climb [1] - 9:19
close [4] - 19:24,
29:22, 49:9, 69:8
closed [2] - 23:14,
30:2
closer [2] - 44:21,
54:14
closest [1] - 15:12
code [3] - 58:7, 58:10,
58:19
codes [1] - 57:24
cogen [1] - 35:1
com [1] - 67:6
combination [1] - 16:1
ComEd [15] - 8:19,
9:20, 10:3, 19:17,
19:18, 20:4, 20:13,
21:9, 25:8, 36:14,
64:18, 64:19, 65:2
ComEd's [2] - 9:22,
21:19
coming [5] - 6:1, 6:20,
20:1, 46:7, 64:12
commencing [1] - 5:3
commend [1] - 42:1
comment [4] - 17:11,
28:8, 54:1, 68:20
commenter's [1] -
54:17
comments [18] -
23:21, 25:15, 27:17,
27:19, 30:4, 33:23,
39:19, 41:7, 42:10,
42:15, 43:7, 48:22,
51:18, 53:15, 53:18,
56:5, 63:13, 63:19
commercial [1] -
42:24
commission [1] -
33:17
Commission [6] - 7:6,
10:6, 12:20, 14:21,
68:5, 68:10
commit [2] - 9:14,
18:3
committed [1] - 55:13
committee [1] - 30:20
committing [2] -
47:23, 48:12
communicate [1] - 7:4
communication [1] -
30:1
communities [2] -
13:5, 14:5
community [18] -
6:21, 16:17, 16:19,
17:7, 23:6, 26:17,
29:2, 30:1, 30:7,
31:24, 34:11, 39:7,
46:14, 47:1, 48:4,
48:11, 48:15, 50:15
Community [1] - 2:20
Company [1] - 6:16
company [2] - 3:10,
66:9
compatible [1] - 15:2
completed [2] - 35:9,
55:18
completion [1] - 55:18
complicated [1] -
64:10
compliment [1] - 54:2
component [2] - 35:1,
59:2
comprehensive [1] -
57:23
computer [1] - 70:10
computer-aided [1] -
70:10
concentrate [1] -
10:20
concept [7] - 8:6,
19:13, 43:18, 54:24,
62:3, 62:6
concern [13] - 26:14,
26:20, 30:19, 33:17,
42:12, 43:20, 43:21,
44:16, 45:2, 45:11,
49:10, 51:5, 52:18
concerned [3] - 32:11,
42:16, 44:23
concerns [12] - 12:6,
29:7, 31:18, 33:3,
33:19, 42:7, 43:9,
51:11, 51:19, 52:13,
52:20, 56:7
concludes [1] - 16:24
concluding [1] - 69:11
concurrently [2] -
25:23, 26:2
conduct [1] - 53:2
confident [1] - 9:20
confidential [3] -
39:12, 57:17, 57:19
confirm [1] - 18:16
conflict [1] - 41:20
conflicts [1] - 60:23
connecting [1] - 37:3
connectivity [1] -
49:24
consider [5] - 26:12,
26:24, 27:8, 29:20,
30:6
considerable [1] -
14:18
consideration [3] -
11:19, 29:12, 31:12
considerations [1] -
50:10
considered [3] - 45:5,
49:13, 50:16
considering [2] -
11:16, 48:5
consisting [1] - 8:3
consolidated [3] -
8:17, 9:7
constant [2] - 32:5,
32:6
constitutes [1] - 70:11
construct [1] - 55:3
constructed [4] -
53:2, 53:11, 54:11,
54:13
Construction [1] -
59:5
construction [7] -
9:18, 13:17, 35:19,
46:17, 54:21, 55:7,
57:1
consumed [2] - 33:5,
66:2
consumption [1] -
10:10
contacts [1] - 52:22
contemplated [3] -
42:23, 43:12, 43:15
contemplates [1] -
42:18
contentious [1] -
28:24
contiguous [2] -
29:21, 29:22
continue [2] - 33:11,
44:5
continued [1] - 68:8
contrary [1] - 11:15
contributes [1] -
29:24
control [1] - 71:2
conundrum [1] - 31:4
conversation [4] -
17:22, 41:23, 55:11,
57:5
conversations [2] -
41:21, 45:17
cooling [2] - 23:13,
32:21
cooperation [1] - 7:12
copies [2] - 70:23,
71:2
Corneils [1] - 47:9
corner [2] - 37:24,
47:14
corporate [1] - 50:9
correct [8] - 5:7, 22:6,
35:10, 37:7, 38:7,
63:6, 64:1, 65:7
corridor [7] - 20:4,
20:5, 44:5, 47:5,
47:17, 47:24, 64:20
corridors [1] - 65:5
cost [1] - 48:11
costs [1] - 57:1
Council [21] - 6:10,
6:12, 9:6, 15:16,
17:2, 17:11, 21:2,
22:19, 28:13, 34:3,
39:22, 41:9, 45:21,
48:4, 48:24, 55:14,
59:3, 59:6, 60:8,
60:17, 62:10
COUNCIL [1] - 1:9
council [1] - 56:12
Councilman [1] - 18:8
counsel [2] - 70:17,
70:18
County [2] - 15:23,
52:8
county [2] - 24:18,
24:23
COUNTY [2] - 1:7,
70:2
couple [16] - 6:21,
25:14, 25:19, 38:13,
41:14, 43:16, 48:3,
49:7, 49:14, 51:18,
56:5, 58:16, 59:17,
63:13, 63:19, 65:4
course [5] - 23:19,
35:4, 36:7, 43:9,
43:12
court [1] - 34:23
courtyard [1] - 27:6
Craig [1] - 2:5
crash [1] - 67:6
create [2] - 30:11,
46:17
creates [1] - 31:4
creek [1] - 36:2
Creek [3] - 36:3,
36:10, 36:17
crisis [1] - 35:22
cross [1] - 13:12
CROSS [1] - 3:7
Cross [1] - 6:14
crosswalk [1] - 38:3
current [1] - 31:13
cursor [1] - 11:23
customer [2] - 19:22,
21:14
cut [1] - 20:2
cutting [1] - 38:2
cybersecurity [2] -
50:13, 53:5
CyrusOne [1] - 51:19
D
Damitz [1] - 34:4
DAMITZ [8] - 4:6, 34:2,
34:4, 34:9, 35:6,
35:20, 36:22, 38:12
Dan [1] - 2:4
dark [1] - 67:9
Data [1] - 5:6
data [32] - 8:11, 9:8,
13:13, 17:23, 18:3,
18:4, 21:16, 27:5,
29:1, 31:2, 31:10,
42:21, 43:5, 46:9,
46:19, 47:3, 49:16,
49:22, 50:8, 59:1,
59:19, 59:23, 61:14,
61:18, 61:20, 61:21,
62:2, 65:14, 65:20,
67:1, 69:9
Dave [3] - 26:19,
30:23, 59:16
David [4] - 6:2, 6:13,
38:24, 39:23
DAVID [5] - 3:7, 4:3,
4:7, 6:9, 39:21
dealerships [1] -
31:11
deals [1] - 53:5
decibel [1] - 32:8
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
3
decibels [1] - 32:4
decision [2] - 36:4,
60:21
decision-making [1] -
60:21
decommissioning [2]
- 66:8, 66:17
dedicate [1] - 29:20
default [1] - 31:1
definitely [3] - 37:21,
49:3, 49:10
definitive [3] - 35:2,
40:21, 41:1
deleterious [1] - 32:8
deliveries [1] - 13:16
dense [1] - 35:18
Department [3] -
51:17, 52:9, 52:15
department [6] -
28:23, 33:18, 56:9,
56:11, 56:21
depict [1] - 43:19
depicted [1] - 43:21
designed [1] - 65:17
designer [1] - 64:14
detailed [1] - 42:9
details [3] - 29:16,
36:15, 42:8
detention [1] - 33:6
develop [1] - 45:14
developed [1] - 45:12
developer [17] - 5:16,
10:13, 24:11, 28:5,
29:2, 43:10, 45:18,
55:14, 56:3, 57:8,
57:12, 58:9, 59:4,
59:10, 61:24, 65:12,
68:21
developers [6] -
32:24, 45:8, 55:22,
56:19, 58:13, 61:13
developing [3] - 30:9,
59:18, 59:24
Development [4] -
2:21, 6:16, 10:6,
21:5
development [29] -
3:10, 3:15, 6:17,
16:6, 16:9, 16:13,
23:24, 28:19, 28:23,
29:8, 29:24, 30:7,
30:12, 30:20, 33:17,
33:18, 41:3, 45:5,
47:5, 47:13, 47:15,
47:17, 47:18, 49:9,
61:12, 62:4, 62:7,
64:22, 67:24
developments [7] -
30:10, 30:16, 35:12,
58:6, 59:1, 61:17,
61:18
deviates [1] - 46:24
Dhuse [1] - 2:16
diagonally [1] - 20:2
difference [2] - 20:12,
22:2
different [10] - 40:1,
40:2, 41:17, 42:19,
44:19, 52:12, 54:20,
62:15, 67:9, 68:17
digital [1] - 51:6
DiNOLFO [1] - 3:2
direction [2] - 70:11,
71:2
directly [5] - 21:23,
28:18, 42:12, 43:8,
70:19
Director [4] - 2:15,
2:16, 2:19, 2:21
dirt [2] - 35:14, 35:15
discharge [3] - 22:22,
23:10, 62:23
discharged [2] -
23:14, 32:18
discharging [1] - 63:2
disclosed [2] - 57:14,
60:24
discretion [1] - 21:20
discuss [1] - 33:11
discussing [3] -
15:18, 29:4, 63:16
discussion [4] -
11:11, 17:11, 33:21,
57:13
discussions [2] -
28:22, 29:15
disruption [1] - 50:3
distance [4] - 14:15,
14:17, 14:18, 58:23
district [5] - 27:1,
32:13, 35:21, 36:17,
63:3
District [1] - 16:4
districts [3] - 14:3,
22:24, 54:3
disturbed [1] - 37:9
disturbing [1] - 36:10
divide [1] - 55:24
divided [1] - 55:19
docks [2] - 13:10,
13:12
documents [3] -
25:16, 26:1, 26:4
dollars [1] - 26:22
domestic [1] - 63:1
donate [1] - 56:19
donating [1] - 26:12
done [5] - 22:10,
22:22, 23:2, 30:20,
57:22
dot [1] - 67:6
dotted [2] - 11:22,
11:24
double [1] - 52:2
double-gated [1] -
52:2
down [7] - 21:13,
21:14, 22:7, 22:11,
22:13, 38:2, 48:17
draft [3] - 7:9, 42:17,
59:20
drafted [1] - 31:1
drainage [2] - 36:17,
65:4
drawing [2] - 19:7,
19:11
Drive [3] - 3:8, 3:13,
45:23
driven [1] - 10:2
drives [2] - 49:16,
49:18
driveways [1] - 43:19
drop [1] - 22:13
drops [2] - 21:14,
49:19
due [3] - 41:12, 41:19,
43:9
E
early [1] - 67:6
easement [1] - 24:9
east [9] - 9:2, 10:1,
20:3, 24:18, 40:5,
40:17, 54:7, 54:19,
55:5
eastern [2] - 37:12,
38:2
economic [2] - 13:22,
49:3
Economic [1] - 10:6
economics [1] - 14:1
EDC [3] - 12:6, 55:1,
64:13
edge [1] - 38:2
effectuate [1] - 62:3
egress [1] - 44:3
eight [1] - 54:5
either [2] - 10:13,
56:20
Eldamain [3] - 47:5,
47:8, 47:13
electricity [1] - 21:13
electromagnetic [1] -
50:2
elements [2] - 64:16,
64:23
elevation [2] - 22:2,
22:8
elevations [2] - 12:16,
14:8
eliminates [1] - 24:6
EMF [1] - 50:23
EMMERT [3] - 4:10,
48:23, 49:1
Emmert [1] - 49:2
employee [2] - 70:16,
70:17
encouraged [2] -
33:12, 33:16
end [8] - 8:14, 9:13,
24:2, 53:22, 54:15,
55:3, 55:5, 55:8
engineer [2] - 46:1,
54:22
Engineer [1] - 2:22
engineering [1] -
58:21
engineers [3] - 22:17,
37:19, 66:18
ensure [1] - 50:14
enter [1] - 46:7
entire [2] - 10:16,
51:22
entitled [2] - 36:13,
51:12
entrance [3] - 38:1,
44:3, 44:13
entrances [1] - 52:2
envision [1] - 64:21
envisioned [1] - 51:13
envisioning [1] -
50:24
Eola [1] - 51:20
equal [1] - 45:2
equally [1] - 45:5
Equestrian [1] - 15:9
equipment [4] - 56:10,
56:20, 65:21, 66:2
equitable [1] - 45:15
Eric [1] - 2:16
Erin [1] - 2:13
especially [1] - 49:5
essentially [4] - 15:18,
18:4, 29:21, 47:24
Estates [2] - 15:9,
44:9
estimate [2] - 39:6,
46:15
estimated [1] - 55:17
estimates [1] - 55:23
et [1] - 26:17
Evans [1] - 2:18
evening [1] - 41:10
evenly [1] - 55:20
eventually [1] - 52:10
exactly [1] - 67:22
excellent [2] - 38:21,
67:5
excuse [4] - 8:9, 8:23,
11:20, 20:19
exemplar [1] - 42:5
existing [5] - 10:18,
21:10, 43:19, 47:16
exit [1] - 44:14
expected [2] - 46:17,
68:21
expecting [1] - 26:11
experience [1] - 46:2
expert [1] - 20:6
explaining [1] - 34:10
explosives [1] - 52:4
expressed [3] - 26:15,
26:16, 41:2
extends [1] - 47:5
extensive [2] - 11:1,
11:2
extent [1] - 16:15
exterior [1] - 33:9
extra [1] - 18:6
F
facilities [2] - 10:4,
19:18
facility [6] - 8:18, 50:8,
50:16, 51:14, 51:20,
56:10
fact [1] - 10:2
factor [1] - 65:24
factory [1] - 61:22
fairly [2] - 46:23, 55:20
familiar [3] - 26:19,
46:3, 52:22
family [2] - 23:5, 49:11
far [2] - 25:16, 54:13
farm [1] - 10:8
Farm [1] - 44:10
farmland [2] - 15:4,
30:9
favor [1] - 45:9
favorable [1] - 41:22
Faxon [2] - 47:7, 47:8
FBI [2] - 52:10, 53:4
feasible [1] - 44:1
fee [1] - 54:2
feed [2] - 65:19
feedback [2] - 55:11,
64:13
feeds [1] - 21:9
fees [1] - 16:22
feet [10] - 7:15, 8:11,
10:17, 11:13, 11:14,
11:21, 15:13, 17:17,
37:13, 58:4
fence [6] - 11:4, 11:6,
11:7, 25:10, 38:6,
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
4
38:8
fencing [5] - 25:2,
37:5, 37:10, 37:14,
51:22
few [1] - 29:6
fiber [4] - 67:5, 67:7,
67:9, 67:13
Field [1] - 64:22
FIELD [1] - 3:3
figure [2] - 5:24, 26:7
final [2] - 44:4, 69:5
Finance [1] - 2:15
fine [2] - 6:3, 49:20
finished [1] - 13:17
fire [7] - 7:15, 56:8,
56:9, 56:11, 56:15,
56:16, 56:21
firm [3] - 6:13, 8:22,
28:15
first [17] - 5:14, 17:11,
25:20, 29:6, 35:11,
37:11, 41:13, 41:19,
41:23, 43:17, 46:6,
49:15, 50:4, 54:1,
54:6, 55:3, 63:17
fiscal [1] - 14:22
fishing [1] - 38:16
flat [1] - 33:7
fleshed [1] - 26:7
folks [5] - 6:22, 7:1,
15:9, 15:12, 27:19
follow [1] - 66:7
follow-up [1] - 66:7
following [1] - 5:1
follows [10] - 5:4,
6:10, 21:2, 28:13,
34:3, 39:22, 41:9,
45:21, 48:24, 60:17
foot [4] - 11:24, 12:2,
24:8, 24:10
footprint [1] - 8:1
Ford [1] - 45:23
foregoing [1] - 70:6
forestation [2] -
30:11, 30:15
forget [1] - 25:21
forgot [1] - 5:11
form [2] - 7:9, 65:24
forward [6] - 24:15,
33:20, 39:20, 59:3,
62:5, 64:15
four [1] - 67:9
Fredrickson [1] - 2:15
frequency [1] - 32:6
front [2] - 5:20, 12:21
full [1] - 39:4
fully [4] - 36:13, 56:3,
61:12, 66:2
funding [1] - 35:24
FUNKHOUSER [8] -
17:10, 17:13, 18:10,
18:15, 18:23, 23:20,
63:11, 65:1
Funkhouser [6] - 2:7,
12:5, 17:9, 23:18,
26:6, 63:10
Funkhouser's [1] -
42:14
furthering [1] - 62:22
future [7] - 10:14,
47:17, 56:15, 56:16,
59:2, 62:4, 66:4
G
Galena [4] - 9:3, 10:7,
15:6, 37:24
gated [1] - 52:2
gateway [1] - 10:23
general [6] - 25:14,
43:21, 46:4, 48:3,
54:10, 54:11
generally [3] - 14:9,
58:6, 63:24
generating [1] - 43:1
generation [1] - 46:21
given [6] - 10:9, 23:3,
38:19, 50:7, 51:5,
70:12
glad [1] - 49:12
glass [2] - 13:7, 14:7
glow [1] - 6:1
glycol [2] - 23:7, 23:11
goal [1] - 18:9
God [2] - 5:20, 36:21
GPUs [1] - 65:23
gracious [1] - 29:3
graciously [1] - 33:1
grading [2] - 22:10,
35:13
grass [4] - 64:1,
64:12, 64:16, 64:17
great [2] - 34:9, 51:17
greater [4] - 30:11,
43:1, 58:24, 67:4
greatest [1] - 12:17
green [1] - 33:8
ground [4] - 21:18,
22:4, 27:5, 29:13
grounds [1] - 37:1
Grove [1] - 3:13
grows [2] - 46:12,
48:19
guess [3] - 5:19, 46:8,
56:22
guidelines [1] - 50:18
guys [7] - 17:15, 19:6,
24:24, 27:6, 49:12,
49:21, 64:8
H
half [1] - 55:2
hand [3] - 19:2, 70:24,
71:4
handle [1] - 28:1
handsome [1] - 5:24
happy [3] - 17:1,
28:22, 52:24
HASENBALG [1] - 3:2
head [2] - 36:19, 53:6
hear [5] - 18:22,
21:24, 25:3, 26:8,
49:12
heard [9] - 38:22,
40:1, 40:2, 40:6,
40:16, 40:18, 49:15,
51:9, 63:12
hearing [15] - 5:3, 5:6,
5:13, 7:7, 12:19,
43:11, 43:24, 62:12,
62:13, 68:5, 68:8,
69:8, 69:11, 70:6,
70:14
HEARING [1] - 1:10
hearings [2] - 42:11,
43:11
heavy [1] - 23:7
height [4] - 11:11,
11:13, 17:16, 24:6
held [1] - 25:7
hello [1] - 45:22
help [5] - 7:17, 15:2,
17:3, 36:1, 49:5
helpful [1] - 17:7
hereby [1] - 70:5
hereto [2] - 70:19,
70:22
hereunto [1] - 71:3
hi [1] - 49:1
hide [1] - 12:7
high [1] - 46:9
higher [1] - 10:21
hills [1] - 64:24
holding [1] - 7:15
HOLTZ [5] - 4:11,
60:13, 60:16, 60:18,
61:2
Holtz [1] - 60:19
Holtzman [1] - 39:24
HOLTZMAN [4] - 4:7,
39:21, 39:23, 41:5
home [1] - 46:9
Homeland [3] - 51:10,
52:9, 52:15
homeowners [3] -
3:15, 28:17, 33:1
hope [5] - 8:16, 17:7,
43:5, 44:2, 45:3
hopefully [2] - 7:2,
16:10
hoping [1] - 43:3
house [1] - 65:23
huge [1] - 26:20
hugs [1] - 38:9
humming [1] - 32:7
hundred [2] - 26:22,
36:18
hundreds [1] - 58:4
hurdles [2] - 9:19,
9:21
husband [1] - 50:5
HVAC [2] - 27:2, 27:5
Hyett [1] - 2:9
I
idea [1] - 38:20
identifying [1] - 56:16
IDOT [2] - 37:20,
37:21
ILLINOIS [2] - 1:7,
70:1
Illinois [10] - 1:17, 3:4,
3:8, 3:13, 3:24,
37:12, 38:2, 70:4,
71:4, 71:9
immediately [2] -
44:10, 52:21
immersion [1] - 23:12
impact [12] - 10:22,
22:23, 23:3, 29:1,
29:5, 37:7, 42:22,
44:24, 49:23, 54:2,
56:8, 63:4
impacts [2] - 14:22,
26:17
implement [2] - 16:12,
42:4
implications [1] -
43:16
important [2] - 17:18,
43:16
improvements [2] -
24:12, 36:12
IN [1] - 71:3
in-person [1] - 2:1
inapposite [1] - 42:8
include [1] - 16:22
including [1] - 17:6
income [1] - 36:1
independent [1] - 25:8
indicate [1] - 28:21
indicated [2] - 30:18,
33:14
indirectly [1] - 70:20
industrial [12] - 13:3,
42:20, 46:2, 47:4,
47:10, 47:15, 47:16,
47:23, 47:24, 48:2,
48:13, 48:18
industry [2] - 46:3,
62:15
Infantry [1] - 3:8
infrastructure [3] -
50:9, 51:6, 52:20
initial [1] - 58:18
inset [1] - 38:6
inside [4] - 11:2,
47:11, 52:6, 65:22
instant [1] - 42:8
integrated [1] - 8:12
intelligence [1] -
66:15
intended [4] - 8:12,
12:20, 13:1, 64:5
intending [1] - 59:18
intensity [1] - 13:19
intent [2] - 9:11, 63:15
interest [1] - 60:23
interested [1] - 70:19
interference [2] - 50:2,
50:24
interior [8] - 24:3,
30:10, 30:14, 33:10,
55:7, 65:2, 65:8,
65:21
internal [1] - 63:17
intro [1] - 5:17
investors [1] - 57:14
involved [1] - 56:12
iron [1] - 11:5
issue [7] - 11:10, 22:8,
24:6, 31:5, 32:3,
32:12, 58:20
issues [8] - 10:23,
32:23, 33:2, 49:13,
50:1, 52:12, 53:5,
58:15
item [1] - 63:11
items [1] - 26:6
itself [2] - 39:9, 67:8
J
JACK [2] - 4:9, 45:20
Jack [1] - 45:22
James [1] - 2:17
Jamie [1] - 34:4
JAMIE [2] - 4:6, 34:2
JENSEN [1] - 52:17
Jensen [1] - 2:17
job [3] - 13:22, 27:3,
34:9
jobs [2] - 46:16, 46:17
Joe [1] - 2:6
John [1] - 2:2
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
5
Joliet [2] - 3:8, 6:15
Jori [2] - 2:12, 27:18
Julian [1] - 28:16
JULIEN [1] - 3:12
July [3] - 68:9, 68:16,
68:22
jump [1] - 20:5
June [2] - 1:20, 71:4
jurisdiction [1] - 45:6
jurisdictions [1] -
45:11
K
KATHLEEN [1] - 3:3
Kathy [1] - 27:18
keep [3] - 24:20,
39:11, 57:7
keeping [2] - 24:21,
57:16
KEITH [2] - 4:8, 41:8
Keith [1] - 41:10
Ken [2] - 2:3, 67:14
KENDALL [1] - 1:7
key [1] - 59:2
kidding [1] - 67:17
kind [18] - 5:17, 10:23,
11:22, 12:20, 14:14,
22:23, 24:13, 28:3,
35:22, 36:19, 38:9,
42:9, 48:16, 50:12,
52:11, 53:2, 64:9,
66:8
knowledge [1] - 22:14
known [1] - 50:1
knows [1] - 66:14
KOCH [15] - 19:3,
19:5, 19:7, 19:11,
19:14, 19:20, 20:11,
21:17, 21:21, 22:1,
22:7, 22:12, 38:17,
66:23, 67:11
Koch [2] - 2:3, 66:22
Koch's [1] - 19:1
Krysti [5] - 2:20,
25:20, 69:1, 69:4
kV [1] - 21:9
L
land [16] - 26:12,
46:22, 46:24, 47:1,
47:10, 48:1, 48:7,
48:10, 48:12, 48:17,
53:11, 56:16, 56:20,
58:21, 61:19, 62:11
Landovitz [1] - 41:11
LANDOVITZ [3] - 4:8,
41:8, 41:10
landscape [2] - 12:15,
64:14
landscaping [11] -
10:19, 10:21, 11:2,
11:3, 11:8, 14:24,
15:11, 30:10, 33:8,
35:8, 37:15
language [1] - 18:8
large [3] - 14:10, 48:5,
49:22
larger [1] - 46:20
LASALLE [1] - 70:2
last [8] - 6:24, 36:23,
51:21, 54:5, 55:1,
60:11, 67:18, 67:20
late [1] - 67:6
law [1] - 6:13
layout [1] - 19:8
leads [2] - 38:14,
38:15
leaning [1] - 5:21
learning [3] - 27:4,
42:2
least [2] - 10:17, 13:11
left [1] - 5:11
Legacy [1] - 44:9
Leland [1] - 71:4
Lenert [1] - 28:16
LENERT [1] - 3:11
less [2] - 23:5, 39:14
lettuce [1] - 47:9
level [3] - 22:5, 32:8,
56:12
License [1] - 3:24
licensed [1] - 45:24
life [2] - 65:13, 65:18
light [3] - 42:14, 49:9,
58:1
lighting [2] - 57:23,
58:7
likely [7] - 9:10, 9:24,
26:23, 40:6, 40:13,
40:18, 47:4
limits [2] - 7:21, 16:2
Line [3] - 9:4, 15:7,
47:14
line [5] - 11:24, 12:1,
12:2, 38:10, 58:2
lines [7] - 10:3, 11:22,
19:23, 20:1, 20:2,
20:9, 21:10
link [4] - 11:6, 25:3,
25:10, 68:17
list [2] - 17:21, 61:16
listened [1] - 12:5
litany [1] - 25:13
literally [1] - 59:23
live [10] - 16:20, 26:19,
28:18, 34:5, 41:11,
45:7, 45:15, 47:21,
60:19
living [1] - 49:8
LLC [2] - 3:7, 57:9
loadings [1] - 63:4
local [2] - 22:24, 63:3
locked [1] - 62:7
locking [1] - 48:12
log [1] - 36:17
logistics [3] - 13:4,
13:14, 13:20
look [10] - 10:24,
25:11, 30:3, 30:12,
30:13, 31:22, 32:2,
33:20, 34:10, 60:7
looking [3] - 11:7,
33:6, 39:1
loop [1] - 23:14
Loudoun [1] - 52:8
love [1] - 69:4
low [1] - 42:22
lower [1] - 21:15
LTD [1] - 3:2
M
M-2 [2] - 16:4, 48:6
machine [1] - 70:8
MAGDALENA [2] -
4:10, 48:23
Magdalena [1] - 49:1
Mahoney [1] - 6:14
MAHONEY [1] - 3:7
main [2] - 19:21, 52:18
manufacturing [7] -
42:20, 46:3, 46:6,
46:13, 48:6, 59:22,
61:23
Marek [1] - 2:8
masonry [2] - 12:9,
13:2
matt [2] - 34:8, 34:9
MATT [2] - 4:4, 21:1
Matt [10] - 2:8, 6:23,
17:2, 20:15, 20:23,
21:3, 26:18, 38:6,
38:13, 57:11
Matt's [1] - 18:3
matter [1] - 42:9
Matthew [1] - 50:22
max [1] - 66:2
Mayor [7] - 2:2, 5:22,
6:11, 9:6, 35:20,
54:2, 54:9
MAYOR [63] - 5:5,
5:10, 5:19, 5:23, 6:4,
6:6, 6:8, 17:9, 17:12,
18:17, 19:1, 19:4,
19:6, 20:23, 21:6,
22:19, 23:17, 25:17,
25:19, 26:3, 27:16,
27:23, 28:7, 33:22,
34:18, 34:22, 36:6,
36:16, 38:13, 38:21,
39:3, 39:10, 39:13,
39:17, 40:23, 41:6,
45:19, 48:21, 50:21,
53:14, 53:17, 60:3,
60:8, 60:11, 60:14,
61:5, 61:9, 62:14,
62:17, 62:20, 63:10,
65:9, 65:11, 66:6,
66:12, 66:19, 67:14,
67:20, 68:12, 68:14,
68:24, 69:3, 69:7
McCarron [42] - 4:4,
6:23, 20:16, 20:19,
20:21, 21:1, 21:3,
21:4, 21:7, 21:19,
22:6, 22:9, 22:15,
23:1, 23:9, 34:8,
34:17, 34:20, 34:24,
35:11, 36:9, 37:8,
38:7, 38:19, 39:2,
39:8, 39:11, 39:15,
50:23, 57:11, 57:16,
59:7, 59:14, 62:16,
63:6, 64:2, 65:7,
65:16, 66:10, 66:14,
67:3, 67:12
mean [1] - 66:8
means [3] - 44:19,
44:20, 70:8
measures [1] - 50:14
meet [2] - 33:1, 58:19
meeting [22] - 6:24,
10:6, 12:6, 29:4,
29:6, 30:21, 33:15,
34:6, 35:7, 36:23,
41:15, 41:19, 52:15,
55:1, 64:14, 67:23,
68:2, 68:7, 68:10,
68:18, 68:23
MEETING [1] - 1:9
meetings [7] - 6:21,
17:7, 41:16, 43:10,
45:8, 56:13, 58:17
meets [1] - 58:10
Meig [1] - 64:21
MEMBER [1] - 63:9
members [4] - 6:11,
6:12, 9:6, 22:19
mentioned [9] - 8:7,
9:19, 10:15, 23:4,
23:12, 38:23, 46:18,
52:9, 55:21
met [1] - 6:20
metal [1] - 14:7
metals [1] - 23:8
mic [1] - 20:20
Mickey [1] - 28:16
MICKEY [1] - 3:11
microphone [4] -
18:21, 20:18, 21:24,
60:15
mics [1] - 18:24
middle [1] - 54:6
might [5] - 32:7,
42:20, 47:19, 53:12,
55:6
mile [1] - 58:5
million [1] - 26:22
minus [2] - 9:17,
15:20
Mitch [1] - 60:18
MITCH [2] - 4:11,
60:16
mitigating [2] - 44:24,
45:4
mixture [1] - 14:6
modern [2] - 42:20,
58:7
money [1] - 56:20
month [2] - 14:21,
55:2
months [2] - 52:7,
52:16
moot [1] - 42:14
Morris [1] - 6:15
most [13] - 9:10, 9:24,
23:21, 23:24, 26:23,
40:6, 40:12, 40:18,
42:6, 43:8, 45:14,
58:5, 58:23
mostly [3] - 10:2, 13:8,
15:4
move [1] - 16:6
moving [1] - 54:14
MR [82] - 3:7, 3:12,
5:16, 5:22, 6:3, 6:5,
6:7, 6:11, 17:24,
18:11, 18:18, 19:9,
19:13, 19:17, 19:24,
20:15, 20:16, 20:17,
20:19, 20:21, 21:3,
21:7, 21:19, 22:6,
22:9, 22:15, 23:1,
23:9, 27:22, 28:2,
28:14, 34:8, 34:17,
34:20, 34:24, 35:11,
36:9, 37:8, 38:5,
38:7, 38:9, 38:19,
39:2, 39:8, 39:11,
39:15, 39:23, 41:5,
41:10, 45:22, 50:23,
51:18, 52:18, 53:19,
57:16, 57:18, 59:7,
59:9, 59:14, 60:1,
60:4, 60:13, 60:18,
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
6
61:2, 61:11, 62:13,
62:16, 63:6, 64:2,
65:7, 65:10, 65:12,
65:16, 66:10, 66:14,
67:3, 67:12, 67:18,
67:22, 68:4, 68:13,
68:16
MS [22] - 3:3, 5:8, 5:9,
18:20, 20:20, 21:22,
25:24, 34:4, 34:9,
35:6, 35:20, 36:22,
38:12, 49:1, 61:1,
61:4, 61:6, 61:7,
62:12, 68:3, 68:15,
69:2
multi [1] - 23:5
multi-family [1] - 23:5
multiple [2] - 9:9,
56:19
Municipal [1] - 3:13
murmurings [1] - 51:9
N
name [13] - 6:12,
20:24, 28:9, 28:11,
28:14, 34:1, 34:4,
34:7, 39:20, 39:23,
45:22, 49:1, 60:18
Naper [1] - 3:3
Naperville [1] - 3:4
national [2] - 50:9,
50:17
nationally [1] - 8:22
natural [2] - 64:15,
64:23
nature [4] - 13:23,
14:24, 36:24, 51:3
near [3] - 3:15, 18:12,
49:24
nearby [1] - 41:17
nearest [1] - 15:13
necessary [1] - 10:12
need [12] - 16:15,
16:16, 16:17, 18:6,
26:22, 29:17, 29:19,
38:15, 53:10, 54:20,
54:22, 56:9
needed [1] - 10:13
needs [2] - 29:15,
30:16
negative [2] - 51:15
neglected [1] - 44:8
negotiated [1] - 55:13
negotiation [1] - 56:14
neighbor [1] - 49:15
neighborhoods [1] -
50:1
neighbors [1] - 41:23
new [3] - 8:19, 10:9
next [10] - 12:13,
12:22, 14:11, 14:21,
26:14, 35:5, 35:21,
38:23, 67:23, 68:1
nice [4] - 10:24, 11:7,
13:4, 13:7
night [2] - 54:5, 68:11
nights [1] - 69:3
Noble [1] - 2:20
NOBLE [5] - 5:8,
20:20, 25:24, 68:15,
69:2
noise [9] - 32:3, 32:5,
49:9, 54:21, 55:6,
56:6, 57:20, 58:14,
58:20
non [1] - 47:15
non-industrial [1] -
47:15
normal [1] - 62:11
North [2] - 3:3, 47:5
north [6] - 9:4, 15:4,
46:8, 47:6, 47:7,
47:13
note [3] - 36:16,
43:17, 44:7
nothing [5] - 14:11,
35:2, 43:5, 51:2,
62:2
noticeably [1] - 42:22
notwithstanding [1] -
44:3
nuisance [3] - 43:2,
45:1, 45:4
number [7] - 16:12,
16:22, 28:17, 29:7,
32:22, 32:23, 41:16
numbers [2] - 55:22,
55:24
O
obsolete [1] - 65:14
obtains [1] - 30:8
obviously [9] - 13:16,
14:18, 17:1, 24:18,
43:23, 44:18, 46:21,
49:8, 52:5
OF [3] - 1:6, 70:1, 70:2
office [3] - 14:10,
51:10, 53:5
offices [1] - 6:14
officials [1] - 42:2
offset [3] - 22:8,
34:16, 57:1
offsetting [1] - 35:3
old [1] - 67:14
Olson [3] - 2:11, 8:7,
9:18
OLSON [22] - 5:16,
19:9, 27:22, 28:2,
38:5, 38:9, 51:18,
52:18, 53:19, 57:18,
59:9, 60:1, 60:4,
61:11, 62:13, 65:10,
65:12, 67:18, 67:22,
68:4, 68:13, 68:16
Olson's [1] - 44:23
on-site [1] - 22:10
once [9] - 13:17, 16:8,
28:14, 30:22, 36:13,
36:14, 52:5, 65:18,
65:24
one [38] - 6:22, 8:14,
8:16, 8:17, 8:18, 9:7,
9:10, 11:10, 12:17,
12:18, 13:11, 17:19,
20:8, 20:21, 21:7,
22:15, 24:5, 28:20,
29:19, 30:1, 30:3,
30:18, 32:4, 33:3,
36:23, 40:9, 42:12,
59:15, 60:11, 60:13,
61:7, 62:18, 63:11,
65:2, 65:10, 67:18,
67:20
ones [1] - 53:20
ongoing [4] - 41:21,
51:5, 57:4, 57:5
open [9] - 5:13, 27:16,
28:7, 37:21, 55:10,
60:1, 63:20, 63:21,
66:4
opened [1] - 68:8
opening [2] - 5:5,
51:10
operate [1] - 13:14
opinion [1] - 58:18
opportunity [2] -
48:11, 56:18
opposed [2] - 33:7,
38:10
order [1] - 51:23
ordinance [4] - 11:15,
11:18, 11:19, 16:13
organic [1] - 63:4
original [1] - 70:22
ORR [6] - 3:3, 61:1,
61:4, 61:6, 62:12,
68:3
Oswego [1] - 6:15
otherwise [1] - 44:22
OTTOSEN [1] - 3:2
outcome [1] - 70:20
outside [2] - 13:10,
64:4
over-built [1] - 67:5
over-populated [1] -
35:23
overall [1] - 58:11
overhead [1] - 19:10
overhead-type [1] -
19:10
oversight [1] - 25:9
own [1] - 25:9
owned [1] - 64:18
P
P.C [1] - 3:12
p.m [6] - 1:21, 5:3,
68:13, 68:14, 68:16,
69:12
packet [1] - 68:18
pad [1] - 38:10
page [2] - 4:2, 68:18
Pages [1] - 70:7
painting [1] - 13:7
parcels [2] - 8:3, 8:4
parks [2] - 13:3, 47:23
Parks [1] - 2:18
part [11] - 17:14,
17:15, 31:12, 44:4,
44:9, 44:11, 56:13,
58:11, 60:21, 61:12,
63:18
particular [2] - 15:7,
15:10
parties [1] - 70:19
partner [2] - 8:21,
28:15
partners [2] - 9:20,
57:8
passageway [1] - 37:3
passes [1] - 49:19
paths [1] - 37:4
pay [3] - 15:7, 15:10,
57:3
pedestrian [1] - 38:3
people [9] - 17:6,
27:21, 32:9, 32:10,
45:4, 47:20, 53:21,
53:23
People [1] - 18:21
per [1] - 23:6
per-acre [1] - 23:6
percent [1] - 63:21
perhaps [1] - 29:12
perimeter [4] - 24:8,
29:10, 63:16, 64:3
period [1] - 32:6
permanent [1] - 46:16
person [2] - 2:1, 40:7
personal [2] - 41:20,
70:11
personally [1] - 66:9
perspective [1] - 40:4
pervious [1] - 63:21
petitioner [1] - 5:15
phase [3] - 9:10, 53:9,
55:15
phases [1] - 9:9
phasing [2] - 24:24,
54:21
philosophy [1] - 66:16
phone [3] - 49:18,
49:19
photometric [1] - 58:8
physical [2] - 50:12,
52:19
pick [1] - 20:18
picture [1] - 40:15
Pioneer [5] - 5:6, 6:16,
6:24, 8:21, 21:4
place [6] - 13:24,
16:20, 47:22, 50:13,
62:7, 70:15
placement [1] - 58:22
plan [16] - 8:6, 19:13,
29:20, 43:18, 44:1,
44:4, 56:12, 58:8,
58:12, 58:21, 59:4,
66:8, 66:12, 66:17,
68:6
planned [5] - 16:5,
16:9, 16:13, 35:17,
48:8
planning [5] - 11:12,
25:1, 31:7, 36:12,
53:9
Planning [5] - 7:6,
12:19, 14:20, 68:4,
68:9
Plano [1] - 67:15
plans [2] - 10:20, 53:1
plant [2] - 47:9, 61:23
plants [1] - 59:22
play [1] - 50:9
pleasure [1] - 7:13
plentiful [1] - 67:7
plenty [1] - 23:20
Plocher [1] - 2:6
plus [2] - 9:16, 15:19
point [9] - 10:14,
16:11, 17:17, 31:19,
35:21, 37:18, 53:13,
54:17, 60:1
Pointe [1] - 1:16
pointed [1] - 12:3
pointing [1] - 13:22
points [1] - 67:9
police [1] - 56:8
Police [2] - 2:17,
51:17
pollution [2] - 49:10,
57:21
ponds [1] - 38:16
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
7
popped [2] - 51:2,
61:10
populated [1] - 35:23
population [2] - 26:21,
49:7
portion [3] - 7:19,
10:5, 30:1
posed [2] - 54:9,
54:24
positive [1] - 35:24
possible [4] - 15:3,
35:14, 35:18, 54:14
possibly [1] - 37:2
post [1] - 55:1
post-meeting [1] -
55:1
potential [4] - 43:1,
50:10, 50:17, 51:4
potentially [2] - 35:2,
51:16
power [13] - 9:22,
10:3, 19:22, 20:1,
20:2, 20:5, 21:10,
34:13, 34:15, 34:16,
35:3, 65:18, 66:24
powered [2] - 8:18,
65:16
practices [1] - 42:3
prairie [4] - 64:1,
64:12, 64:15, 64:23
Prairie [1] - 1:16
precast [2] - 12:13,
14:7
prefer [1] - 54:10
preference [1] - 41:2
preliminary [6] - 16:5,
23:2, 51:1, 59:8,
59:10, 68:6
prerogative [1] - 27:11
PRESENT [2] - 2:1,
2:10
present [1] - 68:22
presentation [7] -
14:20, 16:24, 23:4,
30:19, 44:24, 57:22,
68:22
presentations [1] -
40:2
pretend [1] - 20:6
pretty [4] - 13:21,
19:24, 37:10, 58:6
previous [2] - 30:20,
47:10
proactively [1] - 52:14
problem [1] - 49:6
problems [1] - 51:1
proceed [1] - 10:1
proceeding [1] - 46:22
proceedings [3] - 5:2,
69:10, 70:13
process [8] - 7:17,
16:7, 17:5, 23:23,
24:17, 56:14, 60:21,
62:11
productive [4] - 29:14,
31:16, 31:17, 41:16
professional [1] - 46:1
project [19] - 8:14, 9:1,
9:15, 9:22, 9:24,
10:11, 10:16, 13:23,
21:12, 36:13, 39:7,
39:9, 40:16, 40:21,
44:18, 46:2, 47:18,
49:4, 51:12
Project [14] - 3:10,
3:15, 5:6, 6:17, 7:19,
8:1, 8:6, 8:22, 8:23,
21:4, 57:9, 58:16,
68:1, 69:8
projecting [1] - 9:16
projects [2] - 9:8,
60:23
properties [2] - 55:4,
58:2
property [21] - 14:2,
15:20, 15:22, 15:24,
16:3, 19:19, 25:2,
26:20, 29:21, 29:22,
34:10, 41:12, 43:23,
44:9, 44:20, 54:6,
55:23, 57:4, 58:2,
59:19, 65:8
proposal [4] - 46:5,
46:14, 46:23, 47:2
proposals [2] - 47:3,
47:4
propose [1] - 11:6
proposed [2] - 44:18,
47:18
protect [1] - 12:10
protection [1] - 45:2
protections [1] -
50:13
proven [2] - 58:8,
58:20
provide [1] - 16:18
provided [3] - 24:11,
25:16, 55:22
providing [1] - 24:11
PUBLIC [1] - 1:10
public [24] - 5:2, 5:5,
5:13, 6:12, 7:7,
12:19, 17:2, 17:5,
18:2, 27:17, 27:19,
28:8, 30:2, 37:1,
39:19, 60:24, 62:12,
62:13, 68:5, 68:8,
69:8, 69:11, 70:6,
70:14
Public [1] - 2:16
publicly [2] - 27:13,
67:23
PUD [7] - 17:15, 42:7,
43:11, 55:15, 58:11,
68:6
Purcell [1] - 2:2
PURCELL [63] - 5:5,
5:10, 5:19, 5:23, 6:4,
6:6, 6:8, 17:9, 17:12,
18:17, 19:1, 19:4,
19:6, 20:23, 21:6,
22:19, 23:17, 25:17,
25:19, 26:3, 27:16,
27:23, 28:7, 33:22,
34:18, 34:22, 36:6,
36:16, 38:13, 38:21,
39:3, 39:10, 39:13,
39:17, 40:23, 41:6,
45:19, 48:21, 50:21,
53:14, 53:17, 60:3,
60:8, 60:11, 60:14,
61:5, 61:9, 62:14,
62:17, 62:20, 63:10,
65:9, 65:11, 66:6,
66:12, 66:19, 67:14,
67:20, 68:12, 68:14,
68:24, 69:3, 69:7
purchase [1] - 56:10
purpose [1] - 43:13
purposes [2] - 23:13,
32:21
pushed [1] - 64:14
put [3] - 19:7, 27:5,
53:4
putting [1] - 29:12
Q
questions [29] - 7:2,
7:16, 17:1, 17:4,
18:22, 23:17, 23:21,
24:13, 25:20, 27:14,
27:20, 27:24, 28:4,
31:16, 33:13, 33:14,
38:14, 41:6, 48:3,
49:7, 50:19, 53:15,
59:13, 59:17, 60:2,
60:9, 60:12, 65:9,
69:5
quick [1] - 21:22
quite [2] - 41:15,
42:19
R
R-2 [1] - 16:1
R-3 [1] - 16:1
racks [1] - 65:22
radius [1] - 11:20
railroad [2] - 47:7,
47:8
rather [1] - 9:12
reach [3] - 32:7,
52:11, 59:4
reached [1] - 52:14
read [2] - 53:20, 60:6
ready [1] - 6:7
real [3] - 21:22, 26:19,
40:15
realized [1] - 61:12
really [10] - 13:24,
17:4, 22:11, 36:18,
36:21, 48:7, 54:3,
64:7, 64:12, 64:17
reasonably [1] - 55:16
rebutted [1] - 62:1
receive [1] - 16:5
received [1] - 53:17
recite [1] - 28:4
recognition [1] -
11:11
recognized [1] - 8:22
record [3] - 28:9,
34:23, 70:12
Recreation [1] - 2:18
recurring [1] - 56:1
recycled [2] - 23:15,
32:17
red [2] - 7:22, 8:4
reduced [2] - 17:21,
70:9
reference [1] - 44:24
referendum [1] - 57:2
refine [1] - 14:19
reforestation [1] -
30:8
regard [8] - 28:22,
28:24, 29:8, 29:9,
30:5, 32:3, 32:12,
44:7
regarding [2] - 22:2,
67:23
regardless [1] - 45:6
regards [6] - 22:21,
36:11, 37:8, 37:17,
50:23, 51:4
region [1] - 67:4
regular [1] - 20:13
reiterate [1] - 41:13
reiterated [1] - 56:23
related [5] - 23:21,
50:2, 50:11, 51:2,
60:23
relates [2] - 52:12,
64:11
relative [2] - 70:16,
70:17
relatively [1] - 65:15
relevant [1] - 43:14
rely [1] - 17:2
remain [2] - 36:5, 36:6
remainder [1] - 26:12
remains [1] - 45:11
remind [2] - 27:18,
34:7
rendering [1] - 14:15
RENZI [1] - 3:11
Renzi [1] - 28:16
report [1] - 41:22
REPORTED [1] - 3:23
reported [1] - 70:7
reporter [1] - 34:23
Reporter [1] - 70:4
represent [5] - 6:16,
12:21, 21:4, 28:17,
57:8
representative [1] -
57:12
representing [1] -
6:23
reproduced [1] - 71:1
request [1] - 18:20
requesting [1] - 16:23
requests [1] - 58:14
require [1] - 66:19
required [1] - 34:16
reserve [1] - 42:9
reserved [1] - 10:12
residence [1] - 44:21
residences [3] - 15:5,
15:8, 54:14
resident [2] - 45:23,
49:2
residential [8] - 10:18,
10:22, 15:14, 18:13,
43:19, 44:6, 44:10,
58:24
residents [15] - 12:10,
24:18, 24:21, 24:22,
24:23, 29:4, 33:19,
35:7, 41:17, 45:10,
49:11, 54:15, 54:17,
54:18
resisting [1] - 17:16
responded [1] - 58:14
responding [2] - 31:6,
31:7
response [5] - 25:18,
27:15, 53:16, 60:10,
69:6
responses [2] - 31:18,
33:19
responsibility [1] -
71:1
responsive [2] - 7:14,
42:15
responsiveness [1] -
33:13
restriction [1] - 17:16
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
8
revenue [5] - 46:21,
55:17, 56:1, 56:24,
57:4
review [1] - 53:1
reviewed [2] - 26:1,
46:14
reviewing [1] - 25:15
rezone [1] - 18:13
rezoned [2] - 15:21,
16:4
rezoning [2] - 61:20,
68:5
rights [1] - 65:3
risks [1] - 50:11
Road [12] - 9:3, 9:4,
15:6, 15:7, 28:18,
41:11, 43:20, 43:22,
44:3, 44:5, 44:12
road [2] - 37:21, 41:12
roads [1] - 44:13
roadway [1] - 24:12
roadways [1] - 16:15
Rob [4] - 2:15, 36:3,
36:10, 36:17
role [1] - 50:8
roof [1] - 24:3
rooftop [3] - 11:14,
24:2, 29:12
room [4] - 28:3, 54:9,
68:15, 68:17
rough [1] - 66:17
roughly [1] - 23:5
Route [2] - 9:2, 15:14
row [1] - 69:3
Roy [3] - 36:3, 36:10,
36:17
run [5] - 20:9, 47:21,
47:22, 64:3, 64:6
running [3] - 65:5,
66:12, 67:7
runs [3] - 23:14, 36:3,
67:10
Rusty [1] - 2:9
S
safe [2] - 51:14, 63:5
safety [1] - 50:14
Sanderson [1] - 2:22
sanitary [6] - 22:24,
23:2, 32:13, 32:19,
62:23, 63:3
scale [2] - 49:22, 50:7
scan [1] - 52:3
scattered [1] - 15:6
schedule [1] - 31:24
scheduling [1] - 41:20
SCHLUETER [3] - 4:9,
45:20, 45:22
Schlueter [1] - 45:23
school [6] - 26:21,
27:1, 35:21, 36:11,
54:3
schools [1] - 49:6
screen [1] - 5:23
screening [1] - 30:14
seat [1] - 57:6
second [2] - 44:15,
50:5
Section [1] - 17:20
secure [1] - 52:5
security [12] - 11:3,
37:5, 37:10, 37:14,
50:7, 50:10, 50:17,
51:13, 51:19, 52:13,
52:19, 56:7
Security [3] - 51:10,
52:10, 52:15
see [22] - 6:4, 6:5,
7:19, 9:1, 11:8,
11:22, 13:5, 13:8,
13:9, 13:10, 13:18,
19:1, 19:15, 20:4,
28:23, 29:5, 30:12,
31:23, 32:23, 46:7,
49:3, 58:4
seeing [2] - 24:5,
35:24
separate [3] - 25:22,
25:24, 26:4
service [1] - 49:23
set [3] - 10:17, 22:7,
71:3
setback [1] - 29:11
setbacks [5] - 10:16,
12:15, 33:4, 33:5,
33:6
sets [1] - 41:17
seven [3] - 5:16, 8:4,
8:8
several [7] - 3:15,
6:20, 8:15, 9:19,
12:2, 26:22, 53:18
sewer [2] - 16:16,
32:20
shaking [1] - 36:19
shallow [1] - 66:3
share [1] - 59:13
shared [1] - 26:16
shell [2] - 37:11, 66:1
shells [2] - 21:16,
65:16
short [1] - 65:15
Shorthand [1] - 70:4
shorthand [1] - 70:9
shot [1] - 60:11
showed [1] - 19:11
shown [1] - 10:8
shows [2] - 19:8,
63:21
shrinking [1] - 65:23
side [11] - 6:22, 10:1,
13:11, 36:16, 45:24,
47:4, 47:6, 47:7,
53:3, 54:18, 54:19
sides [1] - 13:12
sidewalk [1] - 38:1
sign [1] - 46:8
signal [2] - 50:2, 51:3
signed [1] - 70:23
significant [5] - 28:21,
33:4, 46:24, 48:1,
51:13
SILVERMAN [17] -
3:7, 3:7, 4:3, 5:22,
6:3, 6:5, 6:7, 6:9,
6:11, 17:24, 18:11,
18:18, 19:13, 19:17,
19:24, 20:15, 20:17
Silverman [3] - 6:13,
6:14, 40:5
Silverman's [1] -
42:15
similar [2] - 21:10,
64:21
simply [1] - 57:24
simultaneously [1] -
70:9
single [1] - 29:22
site [20] - 8:10, 9:14,
17:20, 22:10, 33:10,
35:12, 43:18, 44:2,
44:18, 45:12, 52:19,
55:8, 56:4, 63:16,
63:17, 63:21, 64:3,
65:5, 67:8, 67:10
six [1] - 52:16
slated [1] - 48:2
slide [4] - 12:13,
12:22, 14:12, 57:22
slides [2] - 5:17, 55:21
solar [3] - 34:15, 35:3
sold [3] - 61:13, 62:9,
62:15
Soling [2] - 2:5, 22:20
SOLING [6] - 22:21,
23:7, 23:16, 62:18,
62:22, 63:7
sometimes [1] - 13:12
somewhere [1] - 27:7
soon [1] - 49:19
sorry [4] - 18:23, 21:3,
24:9, 34:7
sort [3] - 12:14, 37:3,
47:9
sound [4] - 12:9,
54:22, 56:6, 58:21
sounds [4] - 12:11,
28:7, 38:20, 43:4
South [1] - 3:13
south [4] - 9:2, 10:7,
44:11, 45:24
space [3] - 33:8,
63:20, 66:4
span [2] - 65:13, 65:18
speaking [3] - 40:5,
42:7, 57:24
special [2] - 56:10,
68:6
specific [1] - 41:4
specifically [5] -
18:19, 23:22, 58:15,
59:15, 62:1
specified [1] - 70:15
speculation [1] - 9:12
spill [1] - 58:1
square [1] - 8:10
squeeze [1] - 47:15
squeezed [1] - 47:22
SS [1] - 70:1
stadium [2] - 39:14,
39:16
staff [11] - 7:10, 7:14,
14:9, 15:18, 18:7,
41:1, 51:20, 52:8,
54:12, 56:12, 58:9
staged [1] - 29:9
stand [1] - 17:17
standard [1] - 25:7
start [5] - 5:14, 9:24,
41:24, 53:11, 55:5
starting [11] - 24:17,
40:3, 40:4, 40:7,
40:10, 40:11, 40:12,
40:15, 40:17, 40:20,
40:22
starts [1] - 48:1
STATE [1] - 70:1
state [6] - 20:23, 28:9,
28:10, 28:11, 34:1,
39:20
State [1] - 70:4
statements [1] - 40:2
States [1] - 51:8
stations [2] - 56:16,
56:17
stay [1] - 34:20
steel [1] - 11:4
stenographically [1] -
70:8
step [2] - 39:20, 60:14
stepped [1] - 21:13
stick [1] - 47:12
still [8] - 7:10, 14:7,
15:18, 53:8, 55:12,
57:16, 57:19, 66:4
stocked [1] - 38:16
stores [1] - 31:11
stormwater [3] - 23:2,
32:15, 32:19
strategy [1] - 47:1
street [2] - 38:4, 49:16
strictly [1] - 42:7
structure [1] - 15:14
structured [1] - 45:9
stuck [1] - 17:3
studies [1] - 22:22
study [2] - 28:24, 51:1
subdivision [6] - 7:1,
34:5, 44:10, 44:12,
44:13, 63:2
subject [4] - 7:23,
41:12, 43:24, 44:19
submitted [1] - 58:9
substantial [4] -
10:16, 11:17, 14:23,
37:11
substation [3] - 19:15,
19:21, 20:13
substations [4] - 8:20,
19:22, 21:14, 25:6
Sugar [1] - 3:13
Suite [2] - 3:3, 3:8
supply [1] - 34:15
supposed [2] - 36:24,
58:1
surrounding [2] -
15:3, 50:15
switchyard [4] - 8:19,
20:22, 21:8, 21:11
system [2] - 23:14,
32:20
T
table [1] - 57:6
tackling [1] - 36:12
tad [1] - 20:3
talks [1] - 57:23
tank [1] - 10:8
tanks [2] - 10:11,
23:12
tap [1] - 67:15
target [1] - 50:17
tasty [1] - 38:22
tax [6] - 46:21, 55:22,
55:23, 56:23, 57:4,
62:21
taxes [3] - 14:2, 26:20
taxing [1] - 14:3
tech [1] - 46:9
technically [2] - 64:18,
65:18
technological [1] -
24:4
temporary [1] - 46:16
ten [8] - 9:16, 24:8,
24:10, 46:1, 55:18,
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
9
55:20, 56:1
ten-foot [1] - 24:8
ten-year [1] - 9:16
tentatively [4] - 21:12,
37:23, 64:3, 64:6
term [1] - 18:12
terms [3] - 16:14,
45:3, 45:12
terrorism [4] - 50:11,
51:4, 51:19, 52:12
terrorism-related [1] -
50:11
testified [9] - 6:10,
21:2, 28:13, 34:3,
39:22, 41:9, 45:21,
48:24, 60:17
testimony [1] - 70:12
theoretically [2] -
56:1, 56:24
therefore [1] - 42:8
thereof [1] - 70:23
they've [1] - 57:6
thin [1] - 30:13
thinking [4] - 37:22,
38:17, 38:18, 62:20
thoughts [5] - 26:5,
26:17, 27:9, 27:10,
50:21
thousand [1] - 8:2
three [2] - 33:15, 67:9
thwart [1] - 51:15
tilled [1] - 13:2
tilt [1] - 13:6
tilt-up [1] - 13:6
Tim [1] - 2:18
today [5] - 21:10,
33:16, 37:22, 39:5,
48:9
Tomorrow [1] - 68:3
tomorrow [3] - 68:4,
68:10, 68:13
tonight [14] - 6:15,
7:3, 7:9, 7:24, 11:11,
11:16, 15:17, 26:7,
26:9, 27:10, 41:1,
50:6, 50:22, 54:7
top [1] - 16:19
tops [1] - 12:7
total [5] - 8:1, 9:17,
39:6, 39:8, 56:2
totally [1] - 55:17
touch [4] - 53:4, 53:6,
59:15, 64:19
touched [1] - 46:21
touching [1] - 36:9
toured [1] - 51:21
towards [2] - 24:15,
54:15
town [4] - 45:24, 47:4,
49:5, 59:1
TPUs [1] - 65:23
tracks [2] - 47:7, 47:8
Trades [1] - 59:5
traditional [1] - 43:2
traffic [5] - 13:15,
13:18, 13:19, 14:4,
43:21
trail [6] - 24:12, 37:9,
37:17, 38:11, 64:2,
65:8
trails [6] - 24:10,
36:24, 37:7, 63:14,
63:15, 65:2
transcript [2] - 70:7,
70:23
transcription [1] -
70:10
transfer [1] - 62:21
Transier [1] - 2:4
transmission [2] -
64:19, 65:19
transportation [1] -
44:1
trees [1] - 30:4
trenching [1] - 67:13
truck [6] - 5:12, 13:10,
13:15, 13:18, 14:4,
14:10
trucks [2] - 13:8, 13:9
true [1] - 70:12
trust [1] - 27:3
trying [3] - 24:20,
42:3, 64:20
Tuesday [1] - 1:20
twice [1] - 54:7
two [6] - 8:19, 20:12,
43:7, 43:19, 47:22,
69:3
type [4] - 19:10, 42:3,
42:5, 60:5
typed [1] - 53:21
types [1] - 43:2
typewriting [1] - 70:10
typical [2] - 29:23,
30:7
typically [7] - 21:8,
22:17, 23:11, 35:12,
65:3, 65:17, 65:23
U
ultimately [1] - 24:4
uncomfortable [1] -
40:20
under [6] - 46:5,
50:17, 58:2, 70:11,
70:24, 71:2
underground [1] -
22:11
undulating [2] - 64:9,
64:23
unfair [1] - 66:20
unfortunately [1] -
14:16
UNIDENTIFIED [1] -
63:9
unit [3] - 16:6, 16:9,
16:13
UNITED [1] - 1:6
United [2] - 3:5, 51:7
units [4] - 11:14, 12:8,
24:2, 29:13
unless [1] - 65:3
unmute [3] - 53:22,
53:24, 60:5
unofficial [1] - 64:13
up [30] - 9:15, 11:14,
12:8, 13:2, 13:6,
17:12, 20:18, 21:19,
24:2, 27:17, 28:8,
30:17, 30:22, 34:18,
34:20, 35:10, 35:21,
37:6, 46:12, 47:8,
47:13, 48:19, 51:2,
53:7, 57:7, 59:17,
60:2, 61:10, 64:8,
66:7
updated [1] - 59:21
upfront [1] - 40:23
upfronting [1] - 26:24
upgraded [3] - 16:15,
16:16, 37:23
upgrades [1] - 36:11
usage [1] - 35:4
user [3] - 8:14, 8:16,
9:13
users [6] - 8:15,
10:22, 57:13, 61:20,
62:2, 62:15
uses [14] - 17:20,
17:21, 18:6, 29:23,
31:2, 42:17, 42:18,
42:21, 42:23, 42:24,
61:13, 61:16, 61:19,
61:24
utilities [3] - 16:17,
21:18, 25:6
utility [6] - 8:19, 14:2,
20:22, 21:8, 21:11,
55:22
utilized [2] - 21:15,
66:5
utilizing [1] - 35:13
V
value [2] - 39:6, 39:8
variegated [1] - 33:7
vegetation [1] - 35:16
version [1] - 42:17
versus [3] - 29:10,
44:17, 45:10
vet [1] - 23:23
via [3] - 2:1, 34:6,
70:10
vicinity [2] - 45:4,
45:15
view [1] - 14:13
vinyl [1] - 12:7
Virginia [1] - 52:8
virtually [1] - 13:15
vision [2] - 47:1, 48:7
Vitosh [2] - 3:23, 71:8
VITOSH [2] - 70:3,
71:9
voice [1] - 45:1
voltage [1] - 21:15
voted [1] - 26:1
W
walk [1] - 52:1
walk-ins [1] - 52:1
walking [1] - 37:9
walkway [1] - 37:3
wants [3] - 5:14, 18:5,
60:4
waste [1] - 63:1
water [11] - 10:8,
10:10, 10:11, 22:22,
23:5, 32:16, 32:21,
33:7, 38:20, 63:23
website [1] - 68:19
Wednesday [1] - 68:9
week [1] - 6:24
weeks [2] - 29:6,
33:15
weigh [1] - 54:23
WEILER [5] - 3:11,
3:12, 4:5, 28:12,
28:14
Weiler [2] - 28:15,
28:16
Weiler's [1] - 41:14
welcome [1] - 46:8
west [17] - 6:22, 9:3,
10:1, 24:17, 28:19,
40:4, 40:12, 40:16,
40:17, 41:12, 44:17,
44:18, 44:21, 54:7,
54:18, 55:3, 55:4
western [1] - 15:11
whatsoever [1] -
23:11
WHEREOF [1] - 71:3
WHEREUPON [1] -
5:1
Vitosh Reporting Service
815.993.2832 cms.vitosh@gmail.com
City Council - Public Hearing - June 10, 2025
10
whole [3] - 5:21, 13:9,
47:24
wife [3] - 41:11, 41:18,
44:8
wifi [1] - 49:23
willing [2] - 9:14, 18:3
Willrett [1] - 2:13
WILLRETT [3] - 18:20,
21:22, 61:7
WILSON [1] - 3:11
Wilson [1] - 28:16
wire [1] - 11:6
wireless [1] - 49:24
WITNESS [2] - 4:2,
71:3
wondering [1] - 20:12
word [1] - 5:11
Works [1] - 2:16
world [1] - 42:4
writing [1] - 27:1
wrought [1] - 11:4
Wyoming [1] - 57:10
Y
year [3] - 9:16, 35:5,
51:21
years [7] - 9:16, 26:11,
36:18, 46:1, 55:18,
55:20, 66:11
YORKVILLE [1] - 1:6
Yorkville [20] - 1:17,
3:6, 6:18, 8:23, 8:24,
16:20, 17:6, 42:4,
45:1, 45:10, 46:7,
46:9, 46:12, 47:11,
48:6, 48:18, 51:17,
60:19, 60:22, 67:3
Yorkville's [1] - 58:14
Z
zoned [1] - 15:23
zoning [4] - 25:23,
31:5, 31:6, 48:7
Zoning [5] - 7:6,
12:19, 14:20, 68:5,
68:9
Zoom [18] - 2:1, 18:21,
21:24, 28:4, 34:6,
35:8, 36:24, 53:18,
53:22, 60:2, 60:4,
61:8, 65:10, 65:13,
67:19, 67:21, 67:24,
68:17
Zoomland [1] - 27:21
United City of YorkvilleData Center DevelopmentsInformational Presentation and Status UpdateJune 10, 2025
What has changed since May 6thpresentation?•Anything with a yellow bulletpoint/highlight is new information•Clarification on the purpose of upcoming meetings, and public notices required by state statute•Updated maps of data center properties•Updated project renderings of Project Cardinal•Non-guaranteed property tax and utility tax estimates created by staff and the Project Cardinal developer•The impact of the Meta DeKalb data centers on DeKalb area property taxes•Status of City Council discussion on potential revenues and resident impact•Clarification on evaporative cooling vs. air cooling and water use•ComEd’s summer energy price increases•“I live 400 yards from Mark Zuckerberg’s massive data center” video response
Overview•The Basics•What is a data center?•Why are data centers needed?•Why Yorkville?•The Specifics•Overview of current projects•Electrical Utility Tax Revenue•Property Tax Revenue•Resident Concerns, with assistance from Loudoun County, Virginia•Power Supply and Electrical Rates•Aesthetics of power lines•Noise•Proximity to existing homes•Water Use•Construction Issues•Cost of Infrastructure Improvements
The Basics•What is a data center?•At its simplest, a data center is a physical facility that organizations use to house their critical applications and data. A data center's design is based on a network of computing and storage resources that enable the delivery of shared applications and data. The key components of a data center design include routers, switches, firewalls, storage systems, servers, and application-delivery controllers.•Source -https://www.cisco.com/c/en/us/solutions/data-center-virtualization/what-is-a-data-center.html
Project Steel renderingMarch 31, 2025
Cyrus One renderingMay 2024
Project Cardinal renderingsMay 16, 2025
The Basics•Why are data centers needed?Data centers are essential for several reasons, as they provide the infrastructure needed to store, process, and manage data on a large scale. Here's why they're important:1. Data Storage and Management: Data centers house vast amounts of data from businesses, organizations, and individuals. With the growing amount of data generated daily (from emails, transactions, social media, IoT devices, etc.), data centers are necessary to store and organize this data securely and efficiently.2. Reliability and Redundancy: Data centers are designed with backup systems (e.g., power generators, uninterruptible power supplies) and redundancy features (e.g., duplicate servers, network connections) to ensure high availability and prevent data loss. This helps ensure that services like cloud computing, online services, and websites remain accessible even if a failure occurs.3. High-Performance Computing: For businesses that require heavy computing power (e.g., AI, machine learning, and big data processing), data centers provide the hardware, software, and infrastructure to support these operations at scale.4. Security: Data centers are equipped with physical and digital security measures to protect sensitive data. These include surveillance, firewalls, encryption, and strict access controls to prevent unauthorized access or data breaches.5. Cloud Services: Many modern services, such as cloud computing (e.g., AWS, Microsoft Azure, Google Cloud), rely on data centers to deliver computing resources over the internet. These data centers provide the backbone for everything from hosting websites and applications to enabling virtual storage and computing for users worldwide.6. Scalability: Data centers allow companies to scale their infrastructure as needed. Whether adding more storage, processing power, or bandwidth, data centers offer a flexible environment to accommodate growing demands without the need for businesses to invest inbuilding their own infrastructure.7. Cost Efficiency: By centralizing infrastructure in data centers, companies can reduce the costs associated with building and maintaining their own IT facilities. Additionally, data centers often provide economies of scale, which allows companies to share resources and reduce operational costs.•In essence, data centers are vital for supporting the vast array of digital services and applications that modern businesses and consumers rely on every day. They ensure that data is stored safely, processed quickly, and delivered reliably to users across the globe.
The BasicsThe source of information on the prior slide:Chatgpt.com
The Basics•Why are data centers needed?•Major worldwide investment in artificial intelligence (AI) with the hopes of eventually creating artificial general intelligence (AGI)•Everything is a computer, creating data which needs to be stored
The Basics•Why Yorkville? According to industry sources:•Data centers are running into power supply limitations in other states and Illinois is well positioned for future energy supply growth•Yorkville has thousands of acres of undeveloped land around one of the larger ComEd substations in the region•Open land in and around the substation allows easy expansion•Yorkville has a proposed HVDC converter facility called SooGreen, adjacent to the ComEd substation•SooGreen will provide more than 2 gigawatts of power, roughly the capacity of a nuclear power plant in the size of a modest utility building•Illinois has a Data Center Investment Program, providing state level incentives that are competitive throughout the Country
The Basics•Why should we allow them in Yorkville?•They are high tax revenue generating developments that have minimal impact on municipal and school district services •While job creation is often less in quantity than similar sized manufacturing developments, the jobs created are often higher paying than the median wage for full time employee in the same county
The Specifics
The Specifics
The Specifics
The Specifics
The Specifics
The Specifics
The Specifics•Overview of current projects•Project Cardinal / Pioneer Development•On tonight’s City Council agenda for public hearing for the annexation agreement•Public notice is required in the newspaper and the City website by state law•No resident mailers are required•Developer is present at tonight’s meeting and will make a presentation and answer questions from the public and the City Council•Public hearing is expected to be closed at the end of all comments and questions
The Specifics•Overview of current projects•Project Cardinal / Pioneer Development•On Wednesday, June 11 Planning and Zoning Commission (PZC) agenda for public hearing on the rezoning, special use/PUD, and preliminary PUD plan•Public notice is required in the newspaper, on the City website, and residents within 500 feet of the development will receive a direct mailer about the public hearing•Direct mailers to residents are required to be sent between 15 and 30 days from the hearing•Direct mailers were sent in mid-to-late May•Required June 3 Economic Development Committee (EDC) meeting was cancelled due to lack of quorum (aldermen had family conflicts or work emergencies the day of the meeting)•EDC meeting must occur prior to PZC vote on the rezoning, special use / PUD, and preliminary PUD plan•Results in PZC hearing delay as outlined in the next bulletpoint•PZC hearing will be opened at the June 11thPZC meeting and continued to the July 9thPZC meeting•Developer will not be present at the meeting and will not present information about the project on June 11. PZC members and staff maylisten to resident comments and questions (discretion of the chairman).•Developer will be present at July 9thPZC meeting and will make a full presentation and answer questions from the public and the PZC members.
The Specifics•Overview of current projects•Project Steel / Prologis•On the June 24thCity Council agenda for public hearing for the annexation agreement•Public notice is required in the newspaper and the City website by state law•No resident mailers are required•Developer is expected to be present at the June 24thmeeting and will make a presentation and answer questions from the public and the City Council•Public hearing is expected to be closed at the end of all comments and questions
The Specifics•Overview of current projects•Project Steel / Prologis•On Wednesday, July 9 Planning and Zoning Commission (PZC) agenda for public hearing on the rezoning, special use/PUD, and preliminary PUD plan•Public notice is required in the newspaper, on the City website, and residents within 500 feet of the development will receive a direct mailer about the public hearing•Direct mailers to residents are required to be sent between 15 and 30 days from the hearing•Developer is expected to be present at the July 9 meeting and will make a presentation and answer questions from the public and the Planning and Zoning Commission•PZC public hearing is expected to be closed at the end of all comments and questions
The Specifics•Electrical Utility Taxes•Data centers use power, which is taxed by the community on a per kilowatt hour basis and the tax revenue benefits Yorkville property tax owners•City Code Section 3-2-4-B.c.•Each Cyrus One data center will generate between $500,000 and $1,000,000 annually in electrical utility taxes•There are 9 buildings of around 333,333 square feet per building in Cyrus One•At full build out, we expect the Cyrus One development to generate between $4,500,000 and $9,000,000 annually in utility taxes •$1.50 to $3.00 in utility taxes per square foot
The Specifics•Electrical Utility Taxes•Early staff and developer high-end, non-guaranteed utility tax estimates for Project Cardinal is that each data center building could generate as much as $7.3m annually, for a total annual revenue to the City of around $100m annually at full build out•Developer has cautioned that these figures are before any possible state or local incentives•City has not agreed to any incentives at this time•The entire City currently generates $750,000 annually in utility taxes•The City’s general fund budget (core operations) is ~$26,000,000 in FY 26
The Specifics•Property Taxes•Data Centers pay normal property taxes, despite generating no school students•META Data Centers in DeKalb with 3 buildings of around 1m square feet per building and 3m square feet total is currently faced with a post-local-incentive tax bill of ~$31,000,000•Pre-incentive•The META property tax bill would be ~$68,000,000•As an illustration, the Yorkville School District is 71% of the property tax bill and would receive ~$48,000,000 if the META project was in Yorkville•As a comparison, all Yorkville School District taxpayers pay $80,000,000 in property taxes annually•META in DeKalb = 227 acres of data centers housing ~3,000,000 square feet•Cyrus One in Yorkville City but Plano School District = 230 acres of data centers housing ~3,000,000 square feet
The Specifics•Property TaxesProject NameCountyGeneral LocationAcreageBuildingsTotal Building Square FeetEAVAnnual Tax BillProject Cardinal Yorkville Kendall 47 and Galena, Yorkville IL 1048 14 buildings @ 1.2m sf each 17,000,000 TBD 62,040,000$ Project Steel Yorkville Kendall Eldamain and Galena, Yorkville IL 557 18 buildings @ 379,000 sf each 6,822,000 TBD TBDCyrus One Yorkville Kendall Eldamain and Corneils, Yorkville IL 230 9 buildings @ 333,000 sf each 3,000,000 TBD TBDMETA DeKalb* DeKalb Gurler Rd and Peace Rd, DeKalb, IL 227 3 Buildings @ 1m sf each 3,000,000 531,000,000$ 68,000,000$ Equinix Elk Grove Village Cook Lund and Busse, Elk Grove Village IL 8 150,000 sf 150,000 37,000,000$ 8,000,000$ Cyrus One Aurora DuPage Eola and Diehl, Aurora IL 41 1 bldg @ 466k sf, 1 bldg @ 170k sf 636,000 19,000,000$ 1,400,000$ CenterSquare Lisle DuPage Yeader and Western, Lisle IL 15 363,000 sf 363,000 10,100,000$ 734,000$ Element Wood Dale DuPage Edgewood and Balm, Wood Dale IL 5 100,000 sf 100,000 3,000,000$ 216,000$ Databridge Aurora DuPage Meridien Parkway, Aurora IL 5 80,000 sf 80,000 1,800,000$ 140,000$ * Project has a 55% property tax abatement. Figures shown are gross (i.e. before the incentive is applied)
The Specifics•DeKalb Meta Data Centers, DeKalb Property Tax Bill Impact•Yorkville tax rate reduction•Kendall County bill tax rate reduction relative to DeKalbTax Year DeKalb Tax Rate per $100 EAV% ChangeDeKalb Sample EAV% Change Taxes$ Change% ChangeCumulative Change2019 11.7346 $95,343 $11,1882020 11.4993 ‐2% $99,488 4% $11,440 $252 2% 2%2021 11.0639 ‐4% $101,197 2% $11,196‐$244‐2% 0%2022 10.1116 ‐9% $108,293 7% $10,950‐$246‐2%‐2%2023 9.4128 ‐7% $119,185 10% $11,219 $269 2% 0%2024 7.9669 ‐15% $136,575 15% $10,881‐$338‐3%‐3%Year DeKalb Tax Rate per $100 EAV% ChangeDeKalb Sample EAV% Change Taxes$ Change% ChangeCumulative Change2019 11.7346 $95,343 $11,1882020 11.4993 ‐2% $99,157 4% $11,402 $214 2% 2%2021 11.0639 ‐4% $103,123 4% $11,409 $7 0% 2%2022 10.1116 ‐9% $107,248 4% $10,844‐$565‐5%‐3%2023 9.4128 ‐7% $111,538 4% $10,499‐$346‐3%‐6%2024 7.9669 ‐15% $115,999 4% $9,242‐$1,257‐12%‐18%
The Specifics•DeKalb Meta Data Centers, DeKalb Property Tax Bill Impact•Yorkville tax rate reduction•Kendall County bill tax rate reduction relative to DeKalbYear Yorkville Tax Rate per $100 EAV% ChangeYorkville Sample EAV% Change Taxes$ Change% ChangeCumulative Change2019 10.0575 $80,767 $8,1232020 9.8485 ‐2% $83,370 3% $8,211 $88 1% 1%2021 9.7175 ‐1% $86,284 3% $8,385 $174 2% 3%2022 9.4879 ‐2% $92,811 8% $8,806 $421 5% 8%2023 8.9056 ‐6% $102,840 11% $9,158 $353 4% 12%2024 8.1217 ‐9% $112,526 9% $9,139‐$19 0% 12%Year Yorkville Tax Rate per $100 EAV% ChangeYorkville Sample EAV% Change Taxes$ Change% ChangeCumulative Change2019 10.0575 $80,767 $8,1232020 9.8485 ‐2% $83,998 4% $8,273 $149 2% 2%2021 9.7175 ‐1% $87,358 4% $8,489 $216 3% 4%2022 9.4879 ‐2% $90,852 4% $8,620 $131 2% 6%2023 8.9056 ‐6% $94,486 4% $8,415‐$205‐2% 4%2024 8.1217 ‐9% $98,265 4% $7,981‐$434‐5%‐2%
The Specifics•DeKalb Meta Data Centers, DeKalb Property Tax Bill Impact•Yorkville tax rate reduction•Kendall County bill tax rate reduction relative to DeKalbTax Year United City of Yorkville Tax Rate per $100 EAV% ChangeYorkville Sample EAV% Change Taxes $ Change% ChangeCumulative Change2011 0.7046 $69,534 $4902012 0.7490 6% $61,886‐11% $464‐$26‐5%‐5%2013 0.7738 3% $57,559‐7% $445‐$18‐4%‐9%2014 0.7581 ‐2% $57,559 0% $436‐$9‐2%‐11%2015 0.7361 ‐3% $60,269 5% $444 $7 2%‐10%2016 0.6795 ‐8% $65,726 9% $447 $3 1%‐9%2017 0.6471 ‐5% $71,001 8% $459 $13 3%‐6%2018 0.6242 ‐4% $76,720 8% $479 $19 4%‐2%2019 0.6029 ‐3% $80,767 5% $487 $8 2% 0%2020 0.5880 ‐2% $83,370 3% $490 $3 1% 0%2021 0.5710 ‐3% $86,284 3% $493 $2 1% 1%2022 0.5377 ‐6% $92,811 8% $499 $6 1% 2%2023 0.4921 ‐8% $102,840 11% $506 $7 1% 4%2024 0.4415 ‐10% $112,526 9% $497‐$9‐2% 2%
The Specifics•DeKalb Meta Data Centers, DeKalb Property Tax Bill Impact•Yorkville tax rate reduction•Kendall County bill tax rate reduction relative to DeKalbTax Year United City of Yorkville Tax Rate per $100 EAV% ChangeYorkville Sample EAV% Change Taxes $ Change% ChangeCumulative Change2011 0.7046 $70,000 $4932012 0.7490 6% $72,800 4% $545 $52 11% 11%2013 0.7738 3% $75,712 4% $586$41 7% 18%20140.7581 ‐2% $78,740 4% $597 $11 2% 20%2015 0.7361 ‐3% $81,890 4% $603 $6 1% 21%20160.6795 ‐8% $85,166 4% $579‐$24‐4% 17%2017 0.6471 ‐5% $88,572 4% $573‐$6‐1% 16%20180.6242 ‐4% $92,115 4% $575 $2 0% 16%2019 0.6029 ‐3% $95,800 4% $578 $3 0% 17%2020 0.5880 ‐2% $99,632 4% $586 $8 1% 18%2021 0.5710 ‐3% $103,617 4% $592 $6 1% 19%2022 0.5377 ‐6% $107,762 4% $579‐$12‐2% 17%2023 0.4921 ‐8% $112,072 4% $552‐$28‐5% 12%2024 0.4415 ‐10% $116,555 4% $515‐$37‐7% 6%
The Specifics•Caveats to the prior slides•In Illinois, you cannot eliminate property taxes on residents and keep them on data centers (tax rate must be applied to all property, and amounts paid depend on value of property)•Yorkville could take the windfall from data center revenues and reduce other tax burdens like the food and beverage tax or water rates accompanying the Lake Michigan project, which has an annual debt burden of more than $10m in future years•Reiterating, data center buildings will be built 1-2 at a time for each development, with some developments taking 20 years to build out•Will AI investments continue at current pace, if no AI companies are making money?
The Specifics•How would the revenue impact residents?•DeKalb has shown property tax reductions – in 2-3 years, ~3% to 18% of the entire property tax bill has been reduced•Reduce non-home rule sales taxes? Total annual revenue is $4.3m•Free garbage service? Total annual cost is $2m•Eliminate Road Infrastructure Fee? Total annual revenue is $1m•Reduce water rates? Total annual water sales is currently $8m, but will increase to $16m annually in 2030 due to Lake Michigan water source project•Eliminate City sewer maintenance fees? Total annual revenue is $2m•Downtown Riverwalk? ~$10m one time cost•Bike paths to and from every subdivision in town? No cost estimate•New regional and neighborhood parks? No cost estimate
The Specifics•Resident concerns, according to Loudoun County, Virginia staff•Lack of power supply for new development (ComEd issue in Illinois)•Noise of data centers•Multiple generators per building, used when power goes out in the area and semi-regular testing•Chillers and other mechanical equipment outside of the building has tonal noise during normal operations, and can have non-tonal noise when a chiller or other piece of rooftop equipment goes bad•Aesthetic complaints of new power lines•Loudoun County is heavily developed, and has data center buildings squeezing into vacant land next to residential homes
The Specifics•How will Yorkville address expected resident concerns?•Power supply issues are entirely handled by ComEd – City has no say or oversight•Aesthetic/power line issues are likely to be a non-factor – the City already has high tension and high-capacity power lines near Baseline and Route 47 heading west through the Project Cardinal site, and then south to the ComEd substation near Bright Farms and Cyrus One•ComEd staff have opined that any future power lines in the region would be in the existing ComEd easement footprint, or if not in the existing easements, would be a lower intensity / lower capacity line than what we currently see
The Specifics•How will Yorkville address expected resident concerns?•Noise•The City has engaged a national engineering firm (Soundscape Engineering) that specializes in acoustics, noise, and vibration control, and has worked on data center projects•Soundscape Engineering is providing guidance on the project before the City Council considers it•Distance restrictions to residential homes•Site specific recommendations on how each project is oriented•Best to put generators and chillers on the ground on the opposite side of a building from residents or on the rooftop with mufflers, screening, and other mitigating equipment, if necessary•Assistance with ongoing monitoring of a project during development•Post-development sound reports
The Specifics•How will Yorkville address expected resident concerns?•Noise•The City has a comprehensive noise ordinance that protects public health•Daytime noise must be kept under 60 dbA(normal conversational voice) and nighttime noise must be kept under 50 dbA(home refrigerator noise)•There are 10 dbApenalties to those limits for tonal noise (i.e. limit of 50 dbAdaytime / 40 dbAnighttime)•City is requiring each data center development to adhere to those standards, and model it prior to a City Council final vote•Route 47 noise•IDOT conducted a noise study between 2011 and 2019 that studied impact of expanding Route 47 to four lanes•Study showed then-current sound levels were between 56 and 68 dbAfor noise receptors stationed between 82 feet and 509 feet away from Route 47•Study projected that sound levels in 2040, post roadway expansion, would be between 50 dbAand 70 dbA
The Specifics•Other concerns•Proximity of buildings to residential subdivisions•City Council guidelines that:•No building shall be closer than ~500 feet to the nearest residential subdivision property line•No building shall exceed ~70 feet in height within 1,500 feet of the nearest subdivision property line•There shall be a 100-foot-wide landscaped buffer adjacent to neighborhoods, with some areas also receiving an 8’ tall berm within that buffer•Enhanced building facades that will be viewable from public rights of way or neighborhoods
The Specifics•Other concerns•Water use•No evaporative coolingdata centers•Minooka’s proposed Equinix Data Center on 340 acres is proposing to be an evaporative cooling data center with daily usage around 3 million gallons on average•Yorkville’s entire daily water usage is currently between 2 – 2.5 million gallons a day•Yorkville’s Cyrus One data center project on 230 acres is an “air cooled” data center certified for 750,000 gallons per day, but exact usage is expected to be around 90,000 gallons per day•Cyrus One has their own commitments to sustainable water use, including a “net positive water strategy”•Yorkville is strictly limiting water allocation to Project Cardinal and Project Steel, resulting in daily water use that will be LESS THAN a normal subdivision on the same properties•Project Cardinal is currently planning to use closed loop air chillers, which have a much lower sound profile than other chillers and can be installed fully indoors
The Specifics•Other concerns•Water use•Cyrus One, expected around 90,000 gallons per day (393 gallons per acre)•Project Steel / Prologis, expected around 130,000 gallons per day (236 gallons per acre)•Project Cardinal, expected around 350,000 gallons per day (333gallons per acre)•Typical Residential Subdivision•Houses per acre – 2.8•People per household - 2.9•Gallons per person per day - 75Gallons Per Acre Per Day -609
The Specifics•Other concerns•Construction phasing•Data Centers are massive developments, fueled by interest in data storage and AI, but what happens if that all changes?•Yorkville is recommending Project Steel and Project Cardinal to build as far away from Yorkville residential neighborhoods as possible, first, and then allowing them to build closest to neighborhoods last•This will have the impact of protecting developable land near neighborhoods for as long as possible, in case data center interest wanes in the future•This will mitigate construction noise and issues from existing neighborhoods for as long as possible
The Specifics•Other concerns•Cost of infrastructure improvements•Water and sewer•Yorkville mandated the Cyrus One development to pay for all costs of water and sewer infrastructure extensions before the infrastructure projects were started•Estimated cost at the time of development approval was $11m, exact costs came in around $8m•Yorkville is requiring all other data centers to pay for the cost of water and sewer infrastructure extensions up front•Roadways•Yorkville will require a traffic study complete with construction traffic plan and permanent access plan•Plans will be reviewed by Kendall County and the State (IDOT), as needed•Yorkville has general development rules that require developments to improve all roadways adjacent to the development, according to the traffic generated from the development•Roadway work might be mandated before construction begins, or may be phased
The Specifics•Other concerns•Cost of infrastructure improvements•Electrical system upgrades•ComEd segregates commercial/industrial rate payers from residential, so all system improvements should be borne by the developers themselves, or built into a commercial/industrial rate •Power generation concerns (not ComEd) are spread out among 13 states in the PJM Interconnection organization, so the Yorkville area power generation costs may be spread out among the country•Tax revenues will still be locally captured•ComEd summer energy supply rate increase is expected hit residential bills by an average of a 10% increase, representing an additional ~$10 per month per household•Onestated reason for the price increase is increased demand, from data center users among other users•Tax revenues will still be locally captured and expected to exceed any electrical bill increase
The Specifics•Other concerns•https://www.youtube.com/watch?app=desktop&v=DGjj7wDYaiI •Concern in video – data centers will harm private water wells•Yorkville is in the process of moving to a Lake Michigan water source in 2028 (away from current deep aquifer wells), so it is unlikely any data centers will be operational in Yorkville while we’re still using our current deep aquifer sources.•Concern in video – data center developer utilized blasting on site•Not allowed in Yorkville, and likely not needed due to soil conditions•Concern in video – decimation of existing trees and tree cover•Site is currently farmland with almost no trees. Yorkville is requiring a fully landscaped perimeter with an 8’ tall berm. Any buildings viewable from public right of way (through the berms and the landscaping) will have increased façade standards.
The Specifics•Other concerns•https://www.youtube.com/watch?app=desktop&v=DGjj7wDYaiI •Concern in video – light pollution at night•City has a comprehensive ordinance restricting light spillover from developments. City will review a photometric (light) plan prior to construction. •Concern in video – Georgia power bills are increasing due to data centers•Illinois and ComEd are requiring upfront studies to secure power supplies. Data centers will be expected to pay for the electrical system improvements upfront, or they will have a reasonably certain guarantee that they’ll offset the costs of the improvements through rate increases that will apply to industrial and commercial users only. Finally, any increased supply costs that impact residents will be offset by utility taxes and property taxes paid to local governments, with benefits expected for local taxpayers.•Concern in video – nighttime construction•City prohibits construction between 7pm and 7am and all day on Sunday. We have not had any complaints from neighbors to our current residential and commercial (Costco) development projects in town. •Concern in video – Fayetteville City Council’s approval process•Yorkville City Council has asked the staff to address resident concerns and questions as they come up. We have a project page for each development on our website here - https://www.yorkville.il.us/.../Project-Cardinal-Data... and here - https://www.yorkville.il.us/.../Project-Steel-Data-Center.... Plans for each development and a tentative schedule of meeting dates is included there for your use.
How can you participate?•Multiple projects will have multiple meetings over the next few months – all will be open to the public and some will be dedicated public hearings as required by Illinois laws•Project Cardinal -https://www.yorkville.il.us/906/Project-Cardinal-Data-Center-Campus-Anne•Project Steel -https://www.yorkville.il.us/905/Project-Steel-Data-Center-Campus-Annex-R
How can you participate?•Contact staff with any questions •Bart Olson, City Administrator – bolson@yorkville.il.us•Krysti Barksdale-Noble, Community Development Director – knoble@yorkville.il.us•Elected officials contact information -https://www.yorkville.il.us/320/City-Council •Come to a meeting in person or remotely and speak under Citizen Comments•Don’t want to come to a meeting? You can provide written comment that the City Clerk will enter into the public record for each meeting by emailing Jori Behland at jbehland@yorkville.il.us
June 10, 2025
Overview ƔLocationƔParcel AnnexationƔIntegrationƔPhasing
Site Design, Buffers, and Visual ImpactƔSetbacksƔLandscaped BermsƔPrairie BuffersƔPrecast ScreeningƔBuilding HeightƔVisual Impact
United City of YorkvilleWater Rate Presentation - Five Year PlanJune 10, 2025
Overview•Quick overview of Lake Michigan project status•Changes since this was discussed in 2022•Project costs and timing•Five year plan assumptions in the FY 26 Budget•Five year rate schedule proposal•Brief discussion of other alternatives analyzed but not recommended
Lake Michigan Project Status•City Council has chosen to transition to Lake Michigan water source, via DuPage Water Commission (DWC) and City of Chicago•City has a Lake Michigan water allocation permit from IDNR•City has spent ~$23m in the past couple years to plan and design the system
Lake Michigan Project Status•Construction will start in earnest in 2026, all the way from the south end of Naperville to Oswego, Montgomery, and Yorkville•First drop of Lake Michigan water in Yorkville is expected to be available in 2028
Lake Michigan Project Status•First construction bid package will be reviewed by DWC this Fall, providing the first opportunity to compare project cost estimates to actual construction costs•Current Project Cost Estimates for DWC Transmission Main Only:•~$307m for Oswego, Yorkville, and Montgomery•~$124m for Yorkville•Cost estimates do not include watermain replacement and other local projects•Project is being paid for by ~$25m in normal municipal bonds, ~$28m in low interest state loans, and ~$120m in federal WIFIA loans
What has changed with cost estimates?•Construction inflation has outpaced historical averages•The City was mandated to replace all 10.7 miles of watermain in town that were constructed before 1980, at an estimated cost of ~$26m•Originally assumed wholesale water rate has been impacted by Chicago mayoral changes and negotiations between the DuPage Water Commission, Grand Prairie Water Commission (Joliet), and Chicago
Timing of Project Expenditures•Constr$0$20,000,000$40,000,000$60,000,000$80,000,000$100,000,000$120,000,0002023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050Debt Service CostTransfer to Building and GroundsDWC Buy‐in CostPurchased Water Cost from DWCCapital ImprovementsO&M and AdminNote: $35M Line of Credit repayment in FY2028 is not included.
Timing of Project Expenditures•Constr$0$5,000,000$10,000,000$15,000,000$20,000,000$25,000,000$30,000,0002023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050Additional Expenses ‐Debt Service, Transfer to Building & Grounds, DWC Buy‐in Cost, & Purchased Water CostDebt Service CostTransfer to Building and GroundsDWC Buy‐in CostPurchased Water Cost from DWCNote: $35M Line of Credit Repayment in FY2028 is not included.
Budget Assumptions - Water Revenue•FY 23 Actual - $3,900,000•FY 24 Actual - $4,400,000•FY 25 Projected - $5,600,000•FY 26 Budgeted - $7,000,000 (~25%)•FY 27 Budgeted - $8,800,000 (~25%)•FY 28 Budgeted - $10,600,000 (~20%)•FY 29 Budgeted - $12,700,000 (~20%)•FY 30 Budgeted - $15,200,000 (~20%)
Five Year Water Rate Plan, Matching Budget•All water rates shown are bi-monthly minimum fees plus the Water Infrastructure Fee for the first 350 cubic feet used, then a volumetric fee for every 100 cubic feet used•FY 25 Actual - $49.50 minimum fee + $5.80 volumetric•FY 26 Budgeted - $58.27 minimum fee + $7.28 volumetric•FY 27 Budgeted - $68.97 minimum fee + $9.10 volumetric•FY 28 Budgeted - $79.67 minimum fee + $10.92 volumetric•FY 29 Budgeted - $92.45 minimum fee + $13.10 volumetric•FY 30 Budgeted - $107.73 minimum fee + $15.72 volumetric
Five Year Water Rate Plan, Matching Budget•Current Utility Bill Photo Needed, will overlay graphics indicating which section we’re talking aboutYESNOT IMPACTEDYESNONONOT IMPACTEDNOT IMPACTEDNOT IMPACTEDNOT IMPACTED
Bill estimates shown on next slide!•All fees listed are bi-monthly minimum fees, rolling the water infrastructure fee into the minimum fee•Proposed plan keeps the first 350 cubic feet used as free to the user (i.e. rolled into the minimum fee)•Any water used past 350 cubic feet in a billing cycle is billed at the volumetric rate listed per 100 cubic feet•Calculations are given on a billing cycle basis, annualized basis over the five-year proposal, and total paid over the five-year proposal
Bill estimates shown on next slide!•Minimum residential user•Homes who use less than 350 cubic feet in a billing cycle•Roughly 11% of all users•Average residential user•Homes who use between 351 cubic feet and 1000 cubic feet in a billing cycle•Roughly 41% of all users•High residential user•Homes who use between 1001 cubic feet and 1600 cubic feet in a billing cycle•Roughly 24% of all users•Average Yorkville restaurant•The average Yorkville restaurant uses 10,000 cubic feet in a billing cycle•Large commercial user•The largest commercial water users in town use 70,000 cubic feet in a billing cycle
Five Year Water Rate Plan, Matching BudgetFiscal Year Base Rate Plus Infrastructure Fee Rate per 100 cubic feet Minimum Residential User Bill % Increase Average Residential User Bill % Increase High Residential User Bill % Increase Average Yorkville Restaurant's Bill % Increase Large Commercial User Bill % Increase 25 (Previous) $49.50 $5.80 50$ 87$ 0.0% 122$ 609$ 4,089$ 26 (Current) $58.27 $7.28 58$ 17.7% 106$ 21.1% 149$ 22.4% 761$ 24.9% 5,129$ 25.4%27 $68.97 $9.10 69$ 18.4% 128$ 21.3% 183$ 22.4% 947$ 24.5% 6,407$ 24.9%28 $79.67 $10.92 80$ 15.5% 151$ 17.6% 216$ 18.3% 1,133$ 19.7% 7,685$ 20.0%29 $92.45 $13.10 92$ 16.0% 178$ 17.9% 256$ 18.5% 1,357$ 19.7% 9,217$ 19.9%30 $107.73 $15.72 108$ 16.5% 210$ 18.2% 304$ 18.7% 1,625$ 19.8% 11,057$ 20.0%$926$4,631$6,987$34,936$47,394$236,968$489$2,443Average Annual Bill5 Year Total Paid$1,330$6,652 Bi‐Monthly Figures Proposed Water Rates and Bill Impacts
Items to note – Five Year Water Rate Plan•Rates for FY 26 are based on an assumed City Council approval in June 2025, for the billing cycle that begins July 1st. •If approval is delayed, each successive billing cycle missed costs ~$300,000 in lost revenue that must be planned around
Items to note – Five Year Water Rate Plan•We are showing a five-year water rate plan, but WIFIA will require a 40-year water plan•40-year plan is extremely unrealistic due to variance in community growth projections and WIFIA reserve standards
Items to note – Five Year Water Rate Plan•City Council will be able to review and revise the rates every year at time of budget•Best guess from City staff is that the five-year water rate plan will not change much in that timeframe, given WIFIA bond payments hitting in full in 2033•Possible positive factors for residents•Capital payments from large commercial users and data centers?•Bid prices for Lake Michigan water source project beat engineer’s estimates•Conservative contingency amounts assumed throughout •When Joliet connects to Lake Michigan in ~2030, City should receive a more favorable wholesale rate than current assumptions
Other rate plans considered by staff•City staff spent weeks looking at as many as seven different rate structures. Final recommendation made to keep things most simple and in-line with what the City Council has done in the past.•Lower base rate, higher volumetric rate•Minimally benefits minimal, average, and high residential users•Maximally hurts all restaurants and large commercial users•Higher base rate, lower volumetric rate•Maximally hurts minimal and average residential users•Benefits restaurant and large commercial users•Eliminate or phase out the 350 cubic foot free allocation•Maximally hurts minimal and average residential users•Minimally benefits restaurants and large commercial users
Next Steps•Discussion and Feedback by City Council - June 10, 2025•Up for consideration by City Council - June 24, 2025ORUp for consideration by City Council, - July 2025with revenue impacts
Questions?Bart OlsonCity Administrator630-553-8537 officebolson@yorkville.il.us