Why Put a Data Center Here?
I understand why In-N-Out picked its location on Keystone Avenue here in Reno. Hungry people drive past it, and some of them stop. I have occasionally contributed to that business model.
The reasoning behind putting a data center nearby was less obvious to me.
Looking at the surrounding businesses, traffic, and neighborhood, I wondered why that particular location made sense. Could a site farther along Second Street offer much the same advantages with fewer complications?
There may be an excellent answer. But finding it requires understanding something about the facility that isn’t apparent from the street.
That seems to be a recurring problem with data centers. The people building them understand why they want to be there. The people passing by—or living nearby—may be working with considerably less information.
First, What Kind of Data Center?
My initial reaction treated data centers as though they were essentially interchangeable: large buildings full of computers that need substantial electricity and some way to keep everything cool.
That description doesn’t get us very far.
CENTRA describes its project at 265 Keystone, called RNO2, as a purpose-built interconnection data center. It is intended to connect telecommunications networks, content services, and cloud providers, while also supporting computing workloads, including AI. CENTRA’s project announcement
In ordinary language, an interconnection facility gives different networks a place to connect directly and exchange information. It can also house customers’ computing equipment. The emphasis on connections helps explain why its location matters.
Think of a transportation interchange, except the traffic is information and nobody needs to stop for a hamburger.
this kind of facility, access to existing communications routes can be an important consideration. Cheap land somewhere out of town may not be much of a bargain if getting the necessary connections there becomes expensive or difficult.
I can understand that reasoning. It answers part of my question.
Why This Particular Corner?
Understanding the general area still leaves the question of the particular parcel.
Could another property nearby provide suitable connections? Would it require extensive digging or new electrical infrastructure? Was the necessary land unavailable? Would another site introduce problems that aren’t obvious to someone driving past?
I don’t know.
I have searched for an explanation of whether nearby alternatives were considered and why they might have been passed over. So far, I haven’t found one.
That does not mean nobody considered them. A company’s internal comparisons, property negotiations, and engineering decisions may never appear in an easily accessible public document.
It also doesn’t establish that my suggested stretch of Second Street would work. Looking less busy from the road is hardly a complete engineering study. My windshield is useful, but it has limitations as a planning instrument.
Still, the question seems reasonable: What makes this location preferable to another nearby location?
An explanation could help residents understand which requirements are essential, which are matters of cost, and where there might have been room for a different choice.
The Public Discussion Changed
There is another complication. A project can take years to move from an initial idea to construction. Public attitudes can change while the engineering and financing proceed.
A September Pew Research Center report documents a substantial change between January and late July or early August of this year. The share of Americans saying data centers are mostly bad for nearby residents’ quality of life rose from 30 percent to 49 percent. Negative views of their effects on home energy costs rose from 38 percent to 50 percent. Pew Research Center
Those figures don’t tell us what caused the change. They also don’t establish what Reno residents thought when the Keystone property was selected.
But they do suggest that a developer may now be addressing a much more questioning audience.
The people asking questions today may not have followed an earlier planning discussion. Some may have known little about data centers until recently. Others may have begun wondering about them when the subject shifted from distant computing facilities to electricity bills and buildings in their own communities.
Earlier approval doesn’t make those later questions disappear.
What Happens Outside the Building?
The explanation also needs to reach beyond the equipment inside.
If I lived beside a proposed facility, I would want to know what I would hear, what I would see, and what would happen during construction and normal operation.
How will cooling equipment sound at night? Where will backup generators be placed, and when will they be tested? What water does this particular design require? What electrical improvements are necessary, and who pays for them?
Those are questions, not a list of things I have established are wrong with Keystone.
We should be equally careful about traffic. A data center’s construction period and its normal operating life are different situations. A building can contain expensive equipment without having hundreds of employees arriving every morning.
My concern about an already busy location should therefore lead to questions about actual deliveries, access, construction activity, and daily operations. It should not become an assumption that the finished facility will create another drive-through queue.
The answers need to describe this project. A reassuring example from a different facility—or an alarming example from somewhere else—may tell us little about what neighbors here should expect.
What Comes Back to the Community?
Then there is the benefit side.
A developer can reasonably explain how the facility serves customers and earns money. Residents can reasonably ask how hosting it benefits their community.
Will it improve connections available to local businesses? Make useful services easier to obtain? Produce meaningful local tax revenue? Support other investment?
Some benefits may be indirect, and some may take time. That does not make them imaginary. But they need to be explained with the same care used to describe the building’s technical capabilities.
“Economic development” covers a great deal of territory. I would like to know which part of the economy is expected to develop, who will participate, and how confident anyone is about the projections.
Construction jobs and permanent jobs are different. Investment in equipment and revenue available for public services are different. A useful explanation should help us keep them straight.
I am interested in the opportunities. I would simply appreciate being able to follow the reasoning from the building to the benefit.
Approval and Understanding Are Different Accomplishments
I don’t have a complete account of the neighborhood outreach for this project, so I am not going to claim the developer failed to communicate.
But the broader distinction matters.
A planning presentation must address technical and legal requirements. A neighborhood explanation must help people understand what is being proposed and what it means for them.
Information can be publicly available without being readily understandable. A planning file may explain the engineering perfectly and still leave a neighbor wondering what the building will mean for their daily life.
That effort should also include listening. Residents may identify a practical problem that looks minor on a site drawing but matters considerably from a kitchen window. Where changes are possible, the discussion should happen early enough to influence them. Where choices are already fixed, the developer should explain the constraints honestly.
A polished brochure won’t settle everything. Clear commitments about noise, resource use, construction, and responsibility would be more useful.
I Would Like to Understand the Choice
I use the services these facilities support. I am interested in what better computing and communications can make possible for businesses and individuals. I would like our region to participate in that growth.
I also think it is reasonable to ask why a particular building belongs in a particular place.
Information can be publicly available without being readily understandable. A planning file may explain the engineering perfectly and still leave a neighbor wondering what the building will mean for their daily life.
Perhaps Keystone is the best practical location. Perhaps another nearby site would introduce difficulties I haven’t considered. I would welcome an explanation that helps me understand the choice.
I can find the hamburger menu without much research. Understanding the new neighbor should not require quite so much homework.
What explanation or commitment would matter most to you if a data center were proposed near your home?
