Understanding the difference between zoning authorization, development agreements, and final project approval.
When a major development is proposed in a community, residents understandably have questions. What is being built? Where will it be located? Who approved it? What impact could it have on surrounding neighborhoods? And perhaps most importantly, has the project already received all the approvals necessary to move forward?
These are reasonable questions, and they deserve clear, factual answers.
In Glenn Heights, conversations surrounding a proposed data center have generated considerable interest in the development itself, the decisions made by the City Council, and the steps that remain in the municipal approval process.
Before we examine issues such as water consumption, electricity demand, environmental considerations, traffic, economic development, and neighborhood impacts, we must first establish a common understanding of what has actually been approved and what remains subject to further review.
That is the purpose of Chapter 1.
This educational series is not intended to persuade residents to support or oppose the proposed development. It is designed to provide information, explain the process, distinguish established facts from unanswered questions, and encourage informed community participation.
AMF Mission Critical has proposed developing a data center on property located along Uhl Road, across from an existing Oncor electrical switch station.
A data center is a specialized facility designed to house computer servers, data-storage systems, networking equipment, and the infrastructure necessary to support their operation. Data centers help power many of the digital services people use every day, including online banking, healthcare information systems, educational platforms, cloud storage, communications, and business applications.
However, not all data centers are the same. Facilities can differ significantly in their purpose, physical size, computing equipment, electricity requirements, cooling systems, staffing, and operational characteristics.
AMF Mission Critical has represented to the City that the proposed Glenn Heights facility would operate as a cloud data center.
That description is important, but it does not eliminate the need to evaluate the facility's specific design, infrastructure requirements, and potential impacts.
The developer has also informed the City that its development concept has changed. An earlier proposal contemplated nine buildings during the first phase of development. The developer subsequently indicated that its revised Phase One plan calls for one building.
These changes illustrate why residents should distinguish between preliminary development concepts and the detailed plans ultimately submitted for municipal review.
The final design, building dimensions, equipment configuration, infrastructure requirements, and other development characteristics must be evaluated through the applicable review process.
Before the 2024 rezoning, the property was designated as a residential Planned Development under Ordinance O-734-02, with provisions for single-family residential uses.
That zoning established a different development framework from the one now authorized.
Zoning is the legal mechanism through which municipalities regulate how property may be used and developed. Depending on the applicable zoning district and regulations, it may establish permitted land uses, building setbacks, height limitations, landscaping requirements, screening, and other development standards.
A zoning designation does not necessarily mean a particular development will be constructed. It establishes the legal framework governing potential development.
Consequently, changing the zoning of a property is a significant municipal decision, but it is not necessarily the final approval required before construction.
On October 15, 2024, the Glenn Heights City Council adopted Ordinance O-15-24, rezoning property at 1118 Uhl Road from residential Planned Development PD-16B to Planned Development PD-30, with an industrial base zoning designation.
The ordinance established a development framework allowing a data center and electrical substation, subject to the adopted Planned Development regulations.
The ordinance also adopted development regulations and a concept plan.
This was a zoning approval. It was not approval of a final construction-ready site plan.
That distinction is fundamental.
The zoning action established the types of uses authorized on the property and the applicable development framework. It did not, by itself, complete every review or authorization required for construction.
The City Council also approved a Chapter 380 Economic Development Agreement involving AMF Mission Critical.
An economic development agreement is a separate legal instrument through which a municipality and a developer may establish certain economic development arrangements, obligations, incentives, or commitments.
Such an agreement should be evaluated according to its actual written terms. Its existence should not be confused with approval of every physical or operational detail of a proposed development.
This is one of the most important distinctions in the entire discussion.
The 2024 zoning decision was preceded by several months of discussions, submissions, public notices, and municipal review.
The documented timeline includes the following milestones:
This timeline demonstrates that the rezoning proceeded through a formal municipal process involving staff review, public notice, public hearings, Planning and Zoning Commission consideration, and City Council action.
It also demonstrates why the public record matters. Understanding when decisions occurred, what materials were considered, and which actions were formally approved helps residents evaluate the process based on documented information.
Economic considerations are another important part of understanding the proposed development.
The City's community tour materials reported that the property had an approximate market value of $3 million, with an agricultural valuation adjustment or exemption of approximately $2.976 million, resulting in an approximate taxable value of $24,000.
For the 2025 tax year, collected in 2026, those materials reported total property taxes of $557.30, of which approximately $135.07 went to the City of Glenn Heights.
These figures provide context regarding the property's tax status before development.
A completed commercial or industrial development could substantially change the property's taxable value. However, any future tax revenue would depend on actual investment, taxable valuation, applicable exemptions or agreements, tax rates, and other relevant factors.
Projected economic benefits should not be presented as guaranteed revenue.
The developer has discussed potential community and infrastructure benefits associated with the proposed project, including improvements to Uhl Road, a contribution toward Heritage Park, and a hike-and-bike trail.
Those representations should be evaluated against the executed economic development agreement and other applicable documents to determine which commitments are legally established, what conditions apply, and how compliance would be monitored.
We will examine economic development, community benefits, and accountability in greater detail in later chapters.
A zoning approval does not answer every question about the eventual operation of a development. For example, residents may reasonably want to know:
These questions are not evidence that a development will necessarily create a particular problem. Nor should they be dismissed simply because the property has already been rezoned.
They are legitimate subjects for project-specific review.
Some questions can be answered through existing ordinances, agreements, engineering documents, or established technical standards. Others may require additional information from the developer, utility providers, professional studies, or future submissions.
Where project-specific information has not been established, the responsible approach is to acknowledge that uncertainty rather than substitute assumptions for facts.
The adopted Planned Development zoning remains an important part of the project's legal framework. However, the proposal must continue through the applicable development-review process before construction can proceed.
Depending on the final plans and governing requirements, that process may involve detailed site-plan review, platting, infrastructure and engineering review, permitting, and consideration by the Planning and Zoning Commission or City Council where required.
Residents should also understand that not every subsequent administrative approval necessarily requires a new public hearing or City Council vote. The applicable ordinance, regulations, and type of application determine the review and approval process.
For that reason, it is important to identify the specific decisions that remain, the officials or bodies responsible for those decisions, and the opportunities for public participation associated with each step.
The public should be able to distinguish between what has already been decided, what remains under review, and what information is still needed.
Land-use decisions can influence a community for decades. They can affect infrastructure, public services, neighborhood development, economic opportunities, and the physical character of a city.
That is why understanding the process matters just as much as understanding the proposed development itself.
Residents do not have to share the same opinion about data centers to agree that public decisions should be informed by accurate information, transparent procedures, and careful consideration of community impacts.
Some residents may view the proposal as an economic development opportunity. Others may have concerns about electricity, water, the environment, property values, or neighborhood compatibility. Still others may be gathering information before forming an opinion.
Each perspective deserves an opportunity to be heard and considered within the applicable public process.
The purpose of this educational initiative is not to resolve those differences by telling residents what conclusion to reach. It is to help ensure that the conversation begins with a shared understanding of the facts.
The Glenn Heights City Council approved a rezoning through Ordinance O-15-24 on October 15, 2024, establishing Planned Development PD-30 and allowing a data center and electrical substation under the adopted development regulations.
The City also approved an economic development agreement involving AMF Mission Critical.
Those actions did not, by themselves, constitute approval of every detailed construction plan or operational characteristic of the proposed facility.
Additional development requirements and applicable approvals must be addressed through the City's established processes.
As this educational series continues, we will examine the issues residents have raised, including water, electricity, environmental considerations, traffic, economic impact, property values, and community accountability.
Our objective remains consistent: to provide factual information, explain the process, encourage meaningful questions, and support informed public participation.
Education does not require agreement. Transparency does not require consensus. And public engagement should never be confused with public persuasion.
Answering community questions, separating established facts from assumptions, and identifying what we still need to know.
When a major development is proposed in a community, questions are not only expected; they are an essential part of informed public participation.
In Glenn Heights, residents have raised important questions about the proposed data center along Uhl Road. Some want to understand what a data center actually does. Others are concerned about electricity reliability, property values, noise, environmental impacts, infrastructure, and whether the development will produce meaningful benefits for our community.
These questions reflect the legitimate interests of residents who care about their homes, neighborhoods, families, and the future of Glenn Heights.
As Mayor, I believe residents deserve more than general assurances or technical explanations that are difficult to understand. They deserve factual information presented clearly, an explanation of what has been verified, and an acknowledgment of what remains unknown.
That is why Chapter 2 addresses six of the most frequently discussed questions surrounding the proposed development.
Our objective is not to convince residents that data centers are inherently beneficial or harmful. It is to provide a foundation for informed discussion while recognizing that the impacts of any particular facility depend on its design, location, infrastructure, operations, and applicable development requirements.
A data center is a specialized building or group of buildings designed to house computer servers, networking equipment, data-storage systems, and the supporting infrastructure needed to operate them.
Although many people have never visited a data center, most of us interact with services supported by these facilities every day.
When you access online banking, participate in a virtual meeting, store photographs in the cloud, use navigation software, stream entertainment, or access digital records, the information may be processed, transmitted, or stored through equipment housed in data centers.
Businesses, hospitals, school districts, government agencies, financial institutions, and technology companies also rely on data centers to support their operations.
However, not all data centers perform the same functions or have the same operational requirements.
Some facilities primarily support cloud computing and data storage. Others support enterprise technology operations, telecommunications, high-performance computing, artificial intelligence, or specialized computing activities.
Different workloads can create different requirements for electricity, cooling, equipment, infrastructure, and staffing. Even facilities serving similar purposes can vary significantly in their physical and operational characteristics.
What has the developer told Glenn Heights?
AMF Mission Critical has represented to the City that the proposed development would operate as a cloud data center.
Cloud data centers support the storage, management, processing, and delivery of digital information and cloud-based services.
The developer has also indicated that the proposed first phase has changed from an earlier concept involving nine buildings to a revised concept involving one building.
This is an important distinction because the development should be evaluated based on the specific plans ultimately submitted for review, rather than assumptions based on earlier concepts or unrelated facilities.
It is also important to understand that describing a facility as a cloud data center does not, by itself, establish every computing workload that may operate within it. Cloud infrastructure can support a variety of digital applications.
What remains important to establish?
Residents should have access to project-specific information concerning the final building design, proposed equipment, electricity requirements, cooling technology, operating characteristics, and other relevant details as those materials become available.
The appropriate question is not simply whether data centers are good or bad.
It is whether the specific development proposed for Glenn Heights can meet applicable requirements and how its potential impacts and benefits will be evaluated.
For many residents, their home represents their largest financial investment. Questions about property values are therefore both understandable and important.
The relationship between nearby development and residential property values is complex.
Property values are influenced by numerous factors, including location, housing supply and demand, interest rates, school districts, neighborhood conditions, property maintenance,
accessibility, public infrastructure, surrounding land uses, and broader economic conditions.
The presence of a commercial or industrial development may also influence buyer perceptions, particularly when concerns exist about building appearance, noise, traffic, lighting, or proximity to residential neighborhoods.
However, there is no reliable basis for stating that every data center increases property values or that every data center decreases them.
The potential effect depends on the characteristics of the individual facility and its relationship to surrounding properties.
What factors should residents consider?
Several project-specific considerations may be relevant:
A professional property-value analysis would need to consider these factors and use appropriate comparable properties and market evidence.
What does this mean for Glenn Heights?
The proposed facility's actual relationship to surrounding neighborhoods should be evaluated using the final development plans, applicable zoning requirements, and relevant technical information.
It would be premature to promise residents that their property values will increase. It would be equally premature to declare that property values will necessarily decline.
Both conclusions require evidence.
Residents should also understand that property values and property taxes are related but distinct issues. An increase in the taxable value of a commercial property does not automatically determine what will happen to the market value or tax bill of a nearby home.
We will examine these distinctions in greater detail in Chapter 8: Property Values & Neighborhood Impact.
Electricity is one of the most frequently discussed issues surrounding data center development.
Data centers require electricity to operate servers, networking equipment, cooling systems, security systems, and other supporting infrastructure.
Depending on their size, equipment, computing workloads, and operating requirements, some facilities can have substantial electricity demand.
That demand raises legitimate questions about grid capacity, infrastructure investment, reliability, and how new large electrical loads are evaluated.
How does the electrical grid work?
Does a data center automatically cause power outages?
No. The presence of a data center does not, by itself, establish that nearby homes will experience outages. At the same time, it would be inappropriate to guarantee that a proposed facility could never contribute to electrical system challenges.
Grid reliability depends on several interacting factors, including generation availability, transmission capacity, distribution infrastructure, weather conditions, equipment performance, system planning, and overall electricity demand.
A large new customer can create additional infrastructure requirements, and those requirements should be evaluated through the appropriate utility and grid-planning processes.
What about the proposed Glenn Heights location?
The proposed site is located along Uhl Road, across from an existing Oncor electrical switch station. That location is relevant to discussions about electrical infrastructure, but proximity to an existing electrical facility does not automatically establish that sufficient capacity is available or that no additional infrastructure will be needed.
Those conclusions require project-specific utility information.
What questions deserve answers?
Residents may reasonably ask:
A meaningful evaluation should rely on information from the developer, utility providers, applicable regulatory authorities, and technical studies.
The key distinction is that a data center's electricity demand is a legitimate planning issue, but an assertion that it will necessarily cause residential power outages is not an established fact without supporting evidence.
We will explore these issues further in Chapter 4: Electricity & The Power Grid.
Noise is another important consideration, particularly when a proposed development is located near residential property.
Data centers can contain equipment that produces sound during normal operations or under specific operating conditions.
Potential sources include cooling equipment, ventilation systems, transformers, mechanical systems, and backup generators.
The amount of sound produced depends on the equipment selected, its location, the facility's design, operating conditions, and measures used to reduce noise.
Are all data centers equally noisy?
No. Noise characteristics can differ substantially between facilities. Some equipment operates continuously, while other equipment may operate periodically for testing, maintenance, or emergency backup purposes.
A facility with equipment located inside an enclosed structure may have different sound characteristics from one with substantial equipment installed outdoors.
Similarly, the distance between equipment and surrounding properties can influence the sound experienced by nearby residents.
How is noise evaluated?
Noise is commonly measured in decibels, and environmental noise assessments may use A-weighted decibels, expressed as dBA, to approximate the sensitivity of human hearing.
However, a single decibel measurement does not tell the entire story.
The time of day, duration, frequency characteristics, background sound levels, and whether noise contains prominent tones can influence how it is perceived. For example, a sound that is relatively unobtrusive during a busy afternoon may be more noticeable during quiet nighttime hours.
A meaningful noise evaluation may therefore consider expected equipment operation, surrounding land uses, measurement locations, applicable standards, and potential mitigation.
What can be done to address noise?
Depending on the facility and applicable requirements, potential measures may include equipment enclosures, sound barriers, setbacks, screening structures, equipment placement, and operational controls.
These measures should be evaluated according to the actual design rather than assumed to be effective in every situation.
What about Glenn Heights?
The proposed facility's final equipment configuration and project-specific noise characteristics should be reviewed as additional plans and technical information become available.
The community's educational visit to an operating cloud data center in Richardson provided an opportunity to observe conditions at one existing facility.
However, that visit should not be interpreted as proof that the proposed Glenn Heights development would produce identical sound levels.
Different facilities can have different equipment, layouts, surroundings, and operating conditions.
The appropriate objective is to identify potential noise sources, understand applicable requirements, and evaluate credible project-specific information before drawing conclusions.
Location is one of the most important considerations in evaluating any proposed development.
Data centers often require access to substantial electrical infrastructure, telecommunications connectivity, suitable land, transportation access, and other services.
Developers may also consider property availability, zoning, construction feasibility, proximity to infrastructure, customer requirements, and long-term operational needs.
These considerations can influence site selection, but the relative importance of each factor varies by project.
What do we know about the Glenn Heights location?
The proposed development is located along Uhl Road, across from an existing Oncor electrical switch station. Before the rezoning, the property was designated for residential Planned Development uses.
On October 15, 2024, the Glenn Heights City Council adopted Ordinance O-15-24, establishing Planned Development PD-30 with an industrial base zoning designation allowing a data center and electrical substation, subject to the ordinance's regulations. That action changed the development framework governing the property.
Does the presence of an electrical switch station explain the entire site-selection decision?
Not necessarily. Proximity to electrical infrastructure may be relevant to a developer's evaluation, but it does not independently establish the developer's complete rationale or demonstrate that every necessary utility connection or upgrade is already available.
Only the developer and appropriate infrastructure providers can substantiate the specific considerations that informed the selection.
Why does surrounding land use matter?
A property's suitability for a proposed use involves more than whether the use is legally permitted. The surrounding environment may include homes, roadways, utilities, drainage features, natural areas, and other developments.
Questions about compatibility may involve building height, screening, access, noise, lighting, stormwater management, landscaping, and the placement of mechanical equipment.
Those matters should be evaluated against the adopted Planned Development regulations and the detailed plans submitted through the applicable review process.
What about the original residential zoning?
The property's previous residential designation is part of the documented history of the site.
Residents may reasonably consider that history when evaluating the change in authorized land use. However, the adoption of the new Planned Development zoning means the current legal framework must be understood as well.
Understanding why a location may be attractive to a developer is not the same as concluding that every aspect of the proposed development is appropriate or inappropriate.
Those are separate questions requiring different kinds of information.
Economic development is often discussed in terms of investment, tax revenue, infrastructure improvements, employment, and potential community benefits. Data center projects may involve substantial capital investment in land, buildings, electrical infrastructure, computing equipment, and related systems. Depending on applicable property-tax treatment, ownership arrangements, valuation, exemptions, and agreements, that investment may affect the local tax base.
However, the financial impact of a development cannot be determined simply by citing its projected construction cost.
What has been discussed for Glenn Heights?
The developer has identified several potential benefits associated with the proposed project, including:
These are relevant considerations, but they must be evaluated carefully.
A proposed benefit, a developer representation, and a legally enforceable commitment are not necessarily the same thing.
The executed economic development agreement and any related official documents should be consulted to establish which obligations have been formally adopted, what conditions apply, when performance is required, and what remedies may exist if commitments are not fulfilled.
What about jobs?
Data center development may create construction-related employment opportunities during the building phase. Once operational, however, data centers can require relatively small permanent workforces compared with other types of commercial or industrial facilities of similar physical size or capital value. Permanent positions may involve information technology, electrical systems, mechanical operations, maintenance, security, facilities management, and other specialized functions. The number and types of jobs depend on the specific facility and its operating model.
Residents should distinguish between temporary construction employment, permanent on-site positions, indirect economic activity, and any workforce development commitments formally associated with the project.
What about property taxes?
The City's educational materials reported that, before development, the property had an approximate market value of $3 million and an approximate taxable value of $24,000 after its agricultural valuation treatment.
These figures provide a baseline for understanding the property's existing tax contribution.
Future taxable value and revenue would depend on the actual development, applicable appraisal and taxation rules, tax rates, exemptions, and any relevant agreements. A projected increase in taxable value should not be presented as guaranteed revenue before the relevant conditions are established.
How should community benefits be evaluated?
The important questions include:
A development's economic value should be evaluated alongside its infrastructure requirements, potential costs, and long-term obligations.
Community benefits deserve both recognition and accountability.
We will examine these issues more thoroughly in Chapter 7: Jobs, Workforce & Economic Impact and Chapter 9: Community Benefits & Accountability.
One of the challenges of discussing a proposed development is that not every answer is available at the same stage of the process. Some information is established through adopted ordinances, executed agreements, public meeting records, or existing technical standards.
Other information may come from statements made by developers, consultants, or utility providers. Still other questions cannot be fully evaluated until detailed engineering plans, technical studies, or other project-specific materials are submitted.
These categories should not be treated as interchangeable.
A verified fact is supported by an identifiable, reliable source.
A developer representation is information provided by the project proponent that may require supporting documentation or further evaluation.
A projection is an estimate based on assumptions that may change.
An unanswered question identifies information that has not yet been established or made available.
Acknowledging these distinctions is not an expression of support or opposition. It is part of responsible public communication. Residents should not be expected to accept assumptions as facts. Likewise, the absence of complete information should not automatically be treated as proof of a particular negative outcome. Our responsibility is to identify what is known, explain what remains uncertain, and continue asking appropriate questions as the process moves forward.
Community engagement does not end when a zoning ordinance is adopted.
Residents can continue to review available public documents, attend applicable public meetings, submit questions, communicate with elected representatives, and participate in hearings when the governing process provides for them.
It is also important to recognize that different stages of development may involve different decision-makers and procedures.
Some matters may require Planning and Zoning Commission consideration or City Council action. Others may be reviewed administratively under applicable regulations.
Not every subsequent development decision necessarily requires a new public hearing.
Understanding which approvals remain and how those approvals are handled helps residents direct their questions to the appropriate stage of the process.
Residents also have an important role in identifying local conditions that may warrant consideration, including neighborhood access, drainage concerns, existing traffic patterns, nearby homes, and other community characteristics.
Meaningful public engagement is strengthened when residents have access to understandable information and clear explanations of how their input fits into the decision-making process.
The proposed Glenn Heights data center raises questions that deserve thoughtful, evidence-based answers. Some questions concern how data centers operate generally. Others concern the particular characteristics of the proposed development along Uhl Road.
Those are not always the same questions, and they should not be answered as though every data center is identical. The City Council's 2024 rezoning established a legal development framework, but that action alone did not establish every final design or operational detail of the proposed facility.
As additional project-specific information becomes available, it should be evaluated against applicable requirements and communicated clearly to the public.
Throughout this educational series, we will continue exploring the issues residents have raised while distinguishing documented facts from estimates, representations, and unanswered questions. Residents may ultimately reach different conclusions about the proposed development. That is their right.
Our responsibility is to support a process in which those conclusions can be informed by accurate information, transparency, and meaningful opportunities for participation.
Education does not require agreement. Transparency does not require consensus. And public engagement should never be confused with public persuasion.
Understanding water consumption, cooling technology, infrastructure capacity, and the proposed Glenn Heights data center.
Water is essential to our daily lives. We depend on it for drinking, cooking, bathing, sanitation, public safety, recreation, and the operation of businesses and public facilities. It is also a critical resource for economic development and the long-term sustainability of our communities.
As Glenn Heights continues to grow, responsible water management remains an important municipal responsibility. Residents reasonably expect the City to consider existing water needs, future population growth, infrastructure capacity, and the potential demands associated with new development.
That responsibility becomes particularly important when discussing facilities such as data centers, which can have significantly different water requirements depending on their cooling technology and operational design.
Across the country, concerns have been raised about the amount of water certain data centers consume. Those concerns deserve serious consideration. However, it is equally important to understand that not every data center uses the same cooling system, and not every facility requires the same amount of water.
Some data centers rely on systems that consume substantial quantities of water through evaporation. Others use technologies that recirculate water or rely primarily on air-based cooling methods.
Understanding these differences is essential to evaluating the proposed development in Glenn Heights.
Our objective in this chapter is to explain how data centers use water, examine the cooling system described by the developer, and identify the information necessary to evaluate the potential impact on our community.
Data centers house servers and other electronic equipment that generate heat while operating.
When computer processors perform calculations, store information, and transmit data, they consume electricity. Much of that electrical energy ultimately becomes heat.
If the heat is not properly managed, equipment can overheat, lose efficiency, experience performance problems, or sustain damage.
For this reason, data centers require cooling systems designed to maintain appropriate operating temperatures and protect sensitive equipment.
Cooling is not optional. It is a fundamental part of data center operations.
However, cooling does not always require large quantities of continuously consumed water.
The amount of water needed depends on several factors, including the type of cooling system, the facility's computing equipment, its operating load, local weather conditions, and how the cooling infrastructure is designed. A facility's size alone does not establish its water consumption.
Two data centers with similar building dimensions may have very different water requirements because they use different cooling technologies.
To understand water consumption, we must first understand the major differences between common cooling approaches.
Evaporative Cooling
Evaporative cooling systems use the evaporation of water to remove heat. As water evaporates, it carries heat away from the cooling system. This can be an effective method of cooling, but the evaporated water must be replaced.
Depending on the system, additional water may also be discharged to control mineral concentrations and maintain equipment performance. Because water is consumed through evaporation and other operational processes, facilities using these systems may require a continuing supply of replacement water. The amount consumed can vary substantially based on equipment, climate, operating conditions, and system design.
Air-Based Cooling
Some data centers use systems that transfer heat to outdoor air through mechanical equipment.
These systems may use little or no water for the primary heat-rejection process, depending on their design.
However, they can have different electricity requirements, particularly during periods of high outdoor temperatures.
This illustrates an important consideration: reducing water consumption may involve tradeoffs involving energy demand, equipment selection, or operating efficiency.
Closed-Loop Liquid Cooling
Closed-loop cooling systems circulate a liquid through a contained system to absorb and transport heat.
Instead of continuously discharging the circulating liquid after each cooling cycle, the system reuses it.
The heated liquid transfers its heat through equipment such as heat exchangers before circulating again.
This can substantially reduce the need for replacement water within the closed circulation loop.
However, a critical distinction must be made.
A closed-loop cooling system does not automatically mean that the entire facility uses no water.
The circulating liquid may operate in a closed system while another part of the facility uses water for heat rejection. For example, a closed internal loop can transfer heat to an evaporative cooling tower. Alternatively, heat may be rejected primarily through dry cooling equipment.
The complete cooling design, rather than the term closed-loop alone, determines the facility's overall water requirements.
AMF Mission Critical has represented to the City that the proposed Glenn Heights cloud data center would use a closed-loop cooling system.
According to the developer's explanation, water would circulate through the cooling system rather than being continuously consumed and replaced.
The developer has further indicated that the circulating water is anticipated to require replacement approximately once every ten years. This representation is significant because it describes a cooling approach that differs from facilities relying on continuous evaporative water consumption. However, the ten-year replacement interval should be understood as a developer representation concerning the proposed system—not as an independently verified measurement of total facility water consumption. The replacement interval does not, by itself, establish the volume of water initially required to fill the system, the amount of water needed for periodic maintenance, whether supplemental water will be necessary, or how the facility will ultimately reject heat. Those details depend on the engineering design and operating characteristics of the system.
What does this mean for residents?
It means that the proposed facility should not automatically be assigned the water-consumption figures associated with other data centers that use different cooling technologies.
It also means that the developer's description should be supported by appropriate technical information before conclusions are drawn about the facility's actual water requirements.
Both distinctions are important.
In addition to describing a closed-loop cooling system, the developer has represented that routine water consumption at the proposed Glenn Heights facility would primarily involve landscape irrigation and restroom facilities for a relatively small number of permanent employees.
This is consistent with the fact that some data centers operate with relatively limited permanent on-site staffing compared with other commercial or industrial developments.
However, staffing levels alone do not determine a facility's total water demand. Water may also be needed for initial system filling, equipment maintenance, cleaning, testing, construction activities, or other operational purposes, depending on the final design.
The distinction between routine daily consumption and occasional or temporary water requirements is important.
A facility may have relatively low daily consumption while still requiring a larger volume of water during initial commissioning or specific maintenance activities.
For that reason, a complete water-demand evaluation should consider:
The most meaningful question is not simply whether a data center uses water. It is how much water the proposed facility would require, when that water would be needed, and whether the necessary infrastructure can reliably serve that demand.
These three terms are often used interchangeably in public discussions, but they describe different activities.
Water withdrawal refers to water taken from a source, such as a municipal water system, groundwater supply, or surface-water source.
Not all withdrawn water is necessarily consumed.
Water consumption generally refers to water that is not returned to the same source or system in a manner that makes it immediately available for reuse, such as water lost through evaporation.
A facility's water consumption may therefore differ from the total amount of water it withdraws.
Water recirculation means water is reused within a system rather than being discarded after a single use.
A closed-loop system can recirculate the same liquid many times. However, recirculation does not necessarily eliminate all water withdrawal or consumption elsewhere in the facility.
These distinctions matter when comparing water-use figures. For example, a statement that a cooling system recirculates water does not establish the facility's total annual water consumption. Similarly, a large volume of water circulating inside a cooling system should not automatically be interpreted as an equivalent volume of new water being withdrawn from the municipal supply each day.
Accurate comparisons require consistent definitions and reliable measurements.
This is one of the most important questions residents can ask.
Municipal water systems must be planned and operated to serve existing customers while accounting for future growth, emergency needs, infrastructure limitations, and applicable regulatory requirements. The addition of any substantial water customer can require an evaluation of available supply and distribution capacity. However, the impact of a proposed development cannot be determined solely by its classification as a data center. The evaluation must consider the facility's actual anticipated demand and the capacity of the water system serving it.
For Glenn Heights, relevant considerations include whether the proposed facility would require municipal potable water, the volume and timing of that demand, the location and capacity of existing water lines, and whether additional infrastructure improvements would be necessary.
The City must also continue considering the needs of residents, businesses, schools, public facilities, and future development.
There is no basis for concluding that the proposed facility will necessarily reduce residential water availability without evaluating its actual demand and the City's available capacity.
Likewise, there should be no unconditional assurance that a proposed development will have no effect on the water system before the relevant information has been established.
The responsible approach is to evaluate the projected demand, verify infrastructure capacity, and identify any necessary improvements.
Water infrastructure is an essential part of municipal planning, regardless of whether a particular data center is developed.
As communities grow, they must evaluate water storage, distribution capacity, system pressure, fire protection, aging infrastructure, and the ability to meet peak demand.
Water towers and other elevated storage facilities help maintain system pressure and provide stored water to support normal operations and periods of increased demand.
However, water storage capacity and available water supply are not the same thing.
A water tower stores water and helps manage pressure and distribution. It does not independently create a new source of water.
Likewise, improvements to a water distribution system do not necessarily establish that sufficient long-term water supply exists for every potential future development. Glenn Heights' water infrastructure planning, including its water tower project, should be understood in the broader context of current service needs, future growth, system reliability, and applicable engineering requirements.
Any claim that a particular infrastructure project is necessary because of the proposed data center—or that it guarantees sufficient capacity for the data center—should be supported by documented engineering and planning information.
The City must consider its water infrastructure responsibilities comprehensively, with the needs of residents and the community remaining central to those decisions.
Water conservation is an important consideration for both public and private development.
Texas communities regularly confront questions involving population growth, drought conditions, changing weather patterns, water supply planning, and long-term resource management.
These concerns make it important to evaluate how major developments use water and whether opportunities exist to reduce unnecessary consumption.
For data centers, conservation strategies may include efficient cooling technology, water recirculation, monitoring systems, equipment optimization, and appropriate landscape design.
Depending on the facility and available infrastructure, some developments may also evaluate alternative water sources or reclaimed water. However, the suitability of any conservation strategy depends on the actual system design, local conditions, applicable regulations, and technical feasibility.
A proposed facility should not be described as environmentally sustainable solely because it uses a particular cooling technology. A broader assessment may consider total water consumption, electricity demand, energy efficiency, wastewater generation, equipment operation, and other relevant environmental factors.
Responsible resource management requires examining the complete operational picture rather than relying on a single technical feature.
One way to evaluate water consumption is through actual metered usage. Water meters can document the amount of water delivered to a facility over a particular period. Before construction, however, projected demand generally must be evaluated using engineering calculations, equipment specifications, and operating assumptions.
Once a facility becomes operational, actual consumption can be compared with those projections.
Some data center operators also use water-efficiency measurements to evaluate their operations.
One commonly discussed measure is Water Usage Effectiveness, or WUE, which relates annual site water consumption to the energy consumed by the facility's information technology equipment. This measure can be useful when comparing facilities, but it must be interpreted carefully. A WUE figure may depend on the boundaries of the measurement, the facility's operating conditions, and the methodology used. It should not replace direct reporting of actual water consumption.
For residents, understandable information may include average daily use, annual consumption, peak demand, and any unusual or seasonal requirements.
Where legally and operationally appropriate, clear reporting can help the public understand whether actual usage aligns with the assumptions presented during development review.
Based on the developer's representations, the proposed Glenn Heights facility is expected to use closed-loop cooling, with routine water use primarily associated with irrigation and restrooms.
Those statements provide a starting point, but additional project-specific information would allow a more complete evaluation.
Questions worth addressing include:
These questions are not accusations or predictions of negative impacts.
They are appropriate due-diligence questions for evaluating a proposed development and communicating its potential infrastructure requirements to the public.
Public confidence is strengthened when residents can distinguish between general industry information, project-specific representations, independently verified data, and questions that remain unanswered.
For the proposed Glenn Heights facility, the developer's description of a closed-loop cooling system is relevant information.
It should neither be dismissed without consideration nor accepted as a complete assessment of water demand without appropriate supporting documentation. The same standard should apply to claims made in favor of or against the development.
If someone states that the facility will consume enormous quantities of water, that claim should be supported by information relevant to the actual proposed cooling system.
If someone states that the facility will use virtually no water, that claim should also be supported by a complete accounting of anticipated consumption.
The goal is not to select the most reassuring or alarming statement. The goal is to establish what the evidence supports.
Residents deserve that level of care when discussing a resource as essential as water.
Water is a vital community resource, and its responsible management must remain a priority as Glenn Heights continues to grow.
Data centers require cooling, but their water consumption can vary substantially depending on the technologies they use.
AMF Mission Critical has represented that the proposed Glenn Heights cloud data center would use a closed-loop cooling system, with the circulating water anticipated to require replacement approximately once every ten years.
The developer has also represented that routine water consumption would primarily involve landscape irrigation and restroom facilities for a relatively small permanent workforce.
These statements are important, but they do not, by themselves, establish the facility's total water requirements or the capacity of the municipal system to serve those requirements.
Those matters should be evaluated using appropriate engineering information, utility planning, and the final development design.
As we continue this educational series, our commitment remains the same: to provide factual information, explain the issues clearly, identify unanswered questions, and encourage informed community participation.
Water is too important for assumptions, exaggerations, or unsupported assurances.
Residents deserve facts. Our infrastructure deserves responsible planning. And our community deserves transparency.
Understanding how data centers use electricity, how Texas manages its power grid, and what residents should know about the proposed Glenn Heights facility.
Electricity is essential to nearly every aspect of modern life. It powers our homes, schools, hospitals, businesses, public safety systems, water infrastructure, and the technology we depend on every day.
For residents, reliable electricity is not simply a matter of convenience. It is a matter of public safety, economic stability, and quality of life. That is why questions about electricity consumption and grid reliability deserve careful attention when discussing large developments such as data centers. Across Texas and throughout the country, the rapid expansion of data centers has generated conversations about electricity demand, infrastructure capacity, utility costs, and the ability of existing power systems to accommodate additional large customers.
These are legitimate concerns, particularly in a state where residents have experienced the consequences of severe weather, widespread power outages, and challenges involving electrical infrastructure.
However, it is important to distinguish between the electricity demands of data centers generally and the specific requirements of the facility proposed for Glenn Heights.
Not all data centers consume the same amount of electricity. Their power requirements depend on their size, computing equipment, operational purpose, cooling technology, and the amount of computing activity occurring within the facility.
In this chapter, we will examine how data centers use electricity, explain the organizations responsible for managing and delivering power in Texas, and identify the information necessary to evaluate the proposed development. Our purpose remains unchanged: to provide facts, explain the process, and encourage informed community participation.
Data centers contain specialized computing equipment designed to process, store, and transmit digital information. Unlike many commercial buildings, where electricity demand may decrease significantly after business hours, data centers often operate around the clock.
Their equipment may support essential digital services that customers expect to remain available at all times. Electricity is used for several purposes.
Servers perform the calculations and processing necessary to support digital applications, cloud services, information storage, and other computing functions.
The electricity required depends on the number and type of servers, their processing capabilities, and how heavily they are being used.
Computing equipment generates heat while operating.
Cooling systems remove that heat to maintain appropriate equipment temperatures and prevent overheating.
Depending on the design, cooling equipment may represent a substantial portion of a facility's electricity demand.
Data centers also require electricity to operate equipment that connects servers, manages digital communications, and stores information.
Lighting, monitoring equipment, fire protection systems, access controls, and other building systems also require electricity.
Many data centers incorporate equipment designed to maintain operations during electrical disturbances or outages. This may include batteries, uninterruptible power supplies, backup generators, and other supporting systems.
The combined demand of these systems can make data centers significant electrical customers.
However, the amount of electricity required by one facility cannot be reliably determined simply by looking at its building size or identifying it as a data center. Project-specific information is necessary.
Electricity discussions often involve technical terms that can be confusing.
Understanding a few basic measurements can make these conversations much easier.
A kilowatt is a unit of electrical power equal to 1,000 watts.
It describes the rate at which electricity is being used or supplied at a particular moment.
A megawatt equals 1,000 kilowatts, or one million watts.
Large electrical facilities and major commercial or industrial customers frequently describe their power requirements in megawatts.
A kilowatt-hour measures energy consumption over time.
For example, equipment using one kilowatt of power continuously for one hour consumes one kilowatt-hour of electricity.
A megawatt-hour equals 1,000 kilowatt-hours.
This measurement is commonly used when discussing larger quantities of electrical energy.
Why does the distinction matter?
A facility's maximum electrical demand is not necessarily the same as its actual electricity consumption throughout the year. For example, a facility with a maximum demand of 50 megawatts would consume approximately 438,000 megawatt-hours annually if it operated at that full demand continuously for an entire 365-day year. Actual consumption could be lower depending on operating conditions.
This is a mathematical illustration, not an estimate of the proposed Glenn Heights facility's electrical demand.
When evaluating a proposed development, it is important to distinguish between its requested maximum electrical capacity, anticipated operating demand, and projected annual electricity consumption. Each provides different information.
Understanding the Texas electrical system requires recognizing that several different organizations have distinct responsibilities.
Electricity generation, grid management, transmission, distribution, and retail service are related, but they are not the same function.
ERCOT operates the bulk electric grid serving most of Texas and manages the wholesale electricity market within its region.
ERCOT is responsible for coordinating electricity supply and demand across the grid, maintaining system reliability within its responsibilities, and managing various grid-planning and operational processes.
ERCOT does not function as the local electric utility that repairs every neighborhood power line.
The Public Utility Commission of Texas regulates important aspects of the state's electric industry.
Its responsibilities include oversight of regulated utilities and various rules affecting electric service, infrastructure, and market operations.
Oncor is the transmission and distribution utility serving Glenn Heights.
Its infrastructure delivers electricity through transmission and distribution facilities to customers within its service territory.
Oncor's responsibilities include operating and maintaining its delivery infrastructure, addressing outages involving that infrastructure, and planning applicable system improvements.
Electricity is produced by generating facilities using various energy sources, including natural gas, wind, solar, nuclear energy, and other technologies.
In competitive retail areas of Texas, customers generally purchase electricity through retail electric providers. These companies sell electricity plans and bill customers for their service, while transmission and distribution utilities deliver the electricity.
Why is this important?
When residents ask whether a proposed data center will affect electricity reliability, the answer may involve several different organizations. A municipality does not independently control ERCOT's grid operations, the construction of every transmission facility, or the generation resources available across Texas. However, municipalities can seek relevant information, coordinate with appropriate entities, and evaluate development matters within their legal authority.
AMF Mission Critical has proposed developing a cloud data center along Uhl Road, across from an existing Oncor electrical switch station. The developer has informed the City that the current Phase One concept involves one building rather than the nine buildings contemplated in an earlier development concept. The proposed location near existing electrical infrastructure is relevant to discussions about the facility's potential utility connections. However, proximity to an electrical switch station does not automatically establish that sufficient capacity exists to serve the proposed facility. It also does not establish that the project can connect without additional infrastructure improvements. Those questions require evaluation by the appropriate utility providers and other responsible entities.
At the time of the City's educational discussions, a verified project-specific maximum electrical demand figure had not been established in the information available for this series. Therefore, it would be inappropriate to assign the proposed Glenn Heights facility a particular megawatt requirement based on the electrical demands of unrelated data centers. The facility's anticipated electricity demand should be evaluated using the actual equipment specifications, development plans, operating assumptions, and utility information associated with the project.
This is one of the most important questions residents have raised and the concern is understandable. Electricity reliability affects everything from household comfort and food preservation to medical equipment, public safety, and business operations.
Residents want to know whether adding a large electrical customer could increase the likelihood of outages.
The presence of a data center does not automatically mean that nearby homes will experience power outages. However, it would also be inappropriate to guarantee that a proposed facility could never contribute to electrical system challenges.
Electricity reliability depends on numerous factors, including:
A large new electrical load may require studies, system upgrades, or other arrangements before it can be reliably served. The important question is whether the proposed demand has been appropriately evaluated and whether the necessary infrastructure and operational requirements can be satisfied. A data center's potential impact on electricity reliability should be determined through project-specific utility and grid analysis, not assumptions based solely on the type of development.
Residents sometimes ask whether electricity supplied to a data center means less electricity will be available for their homes. This question deserves a clear explanation. Electricity is delivered through an interconnected system rather than being assigned from a fixed neighborhood supply that remains unchanged regardless of demand.
When a large new customer seeks service, the utility and other responsible entities must evaluate the infrastructure and system requirements associated with that demand. Depending on the circumstances, additional transmission facilities, substations, equipment upgrades, or other improvements may be necessary.
A properly planned connection may be designed to accommodate the new customer while maintaining applicable reliability requirements. However, the broader electric system must also have sufficient resources to serve total demand. This is why large-load growth is a significant issue for utilities, grid operators, and state regulators.
The relevant question is not whether a data center simply takes electricity away from nearby homes. It is whether the electrical system can reliably accommodate the additional demand and what improvements may be required.
For Glenn Heights, that assessment should be based on the proposed facility's actual electrical requirements and information from the responsible utility and grid entities.
Electricity costs are another legitimate concern. Residents should understand that their electricity bills may include several components, depending on their retail service arrangement.
These can include charges associated with electricity generation, retail service, transmission, distribution, and other applicable costs.
Large increases in electricity demand can influence the broader electricity market and create a need for additional infrastructure investment. Those changes may affect costs, but the relationship between one proposed development and an individual household's electric bill is not straightforward. For example, electricity prices may be influenced by fuel costs, generation availability, weather, market conditions, transmission investments, regulatory decisions, and the terms of a customer's retail electricity plan.
Likewise, the cost of constructing new electrical infrastructure may be allocated according to applicable tariffs, agreements, and regulatory requirements. Some costs may be assigned directly to the requesting customer, while other costs may be recovered more broadly under applicable rules.
It would be inaccurate to state that the proposed Glenn Heights data center will automatically increase every resident's electric bill by a specific amount.
It would also be premature to guarantee that no costs associated with serving new large electrical loads could ever affect other customers. Those conclusions require information about the project's electrical service arrangements, infrastructure requirements, applicable cost-allocation rules, and broader market conditions. Residents deserve an explanation of who pays for any required improvements and how those costs are determined.
Data centers often provide services that customers expect to remain available continuously.
For that reason, many facilities are designed with multiple layers of electrical protection.
These may include:
UPS systems can provide temporary electrical power when the primary supply is interrupted.
They help protect equipment and may allow time for backup systems to activate or for operations to be safely managed.
Batteries may be used as part of a UPS system or other power-management infrastructure.
Their capacity and operating purpose depend on the facility's design.
Some data centers use generators to supply electricity during utility outages.
These generators may operate on diesel, natural gas, or other fuels, depending on the equipment selected.
Some facilities incorporate multiple electrical pathways or other design features intended to reduce the likelihood that a single equipment failure will interrupt operations.
However, backup systems are not all designed the same way.
Their capabilities depend on equipment specifications, fuel availability, maintenance, operating conditions, and the facility's overall design.
An important distinction: Backup generators do not necessarily mean that a data center can operate independently of the electrical grid indefinitely. The duration and capability of backup operations depend on the actual equipment and available resources. For the proposed Glenn Heights facility, the final backup-power configuration should be evaluated when project-specific information becomes available.
Backup generators introduce considerations beyond electrical reliability. Depending on their type and operation, generators can produce noise and air emissions. Their potential impacts depend on several factors, including equipment size, fuel type, exhaust controls, operating duration, testing schedules, placement, and applicable regulatory requirements. Generators may operate during emergencies, maintenance, or periodic testing. The frequency and duration of these activities can influence their effects on surrounding properties.
Questions worth addressing include whether backup generators are proposed, how many would be installed, what fuel they would use, where they would be located, and what noise or emissions requirements would apply. The existence of backup generators should not automatically be interpreted as evidence of unacceptable environmental impacts. Likewise, their potential effects should not be dismissed without reviewing the actual equipment and operating plans.
Texas residents understand the importance of electrical reliability during extreme weather.
Severe winter conditions, prolonged summer heat, storms, and other events can place significant demands on electrical infrastructure.
During periods of extreme heat, electricity demand often increases as homes and businesses use more air conditioning. Winter weather can also create substantial demand while affecting generation facilities, fuel systems, transmission infrastructure, and other equipment.
Data centers may operate continuously during these periods, although their actual demand and ability to adjust operations depend on the facility. Texas has continued to develop rules, planning processes, and operational measures addressing grid reliability and large electrical loads.
However, the existence of these measures does not eliminate every risk associated with severe weather or rapid demand growth.
The appropriate question is how the proposed facility's electrical requirements would be evaluated under normal conditions and during periods of system stress.
This may involve utility studies, applicable interconnection requirements, emergency operating procedures, and other technical considerations. Residents should also understand that a data center's backup-power system is generally intended to protect the facility's own operations.
It should not be assumed to provide emergency electricity to surrounding neighborhoods unless a specific arrangement establishes that capability.
Yes. Cooling technology can influence both water use and electricity demand.As discussed in Chapter 3: Water, AMF Mission Critical has represented that the proposed Glenn Heights facility would use a closed-loop cooling system. The developer has indicated that the circulating cooling water is anticipated to require replacement approximately once every ten years.
This representation is relevant to the discussion of water consumption. However, the cooling system's electricity requirements must be evaluated separately. A system designed to reduce water consumption may use fans, pumps, compressors, heat exchangers, or other equipment that requires electricity.
Different cooling technologies involve different operating characteristics and potential tradeoffs.
For example, dry cooling systems can reduce evaporative water consumption but may require additional electrical energy under certain conditions.
Other systems may use water evaporation to reject heat more efficiently under particular environmental conditions.
Lower water consumption does not automatically mean lower electricity consumption, and higher electricity consumption does not automatically establish that a cooling system is inefficient.
A meaningful evaluation requires examining the complete system and the conditions under which it will operate. This is why the proposed facility's final cooling design is relevant to both water and electricity discussions.
One commonly used measurement in the data center industry is Power Usage Effectiveness, or PUE. PUE compares the total energy consumed by a data center with the energy used by its information technology equipment.
The calculation is:
PUE = Total Facility Energy ÷ IT Equipment Energy
For example, a PUE of 1.20 means that for every unit of energy used by the computing equipment, the facility consumes an additional 0.20 units for cooling, power distribution, lighting, and other supporting systems.
A PUE closer to 1.0 generally indicates that a smaller share of total facility energy is being used for supporting infrastructure. However, PUE has limitations. It does not directly measure the total amount of electricity a facility consumes, the carbon intensity of its electricity supply, or its overall environmental impact. A very large data center with an efficient PUE can still consume substantially more electricity than a smaller facility with a less efficient PUE. PUE also does not establish whether the electrical grid has sufficient capacity to serve the facility.
Energy efficiency and total electricity demand are related, but they are not interchangeable.
Both should be considered when evaluating a proposed development.
When a large development requires additional electrical infrastructure, questions naturally arise about who is responsible for the cost.
Potential improvements may include utility connections, transformers, substations, transmission facilities, distribution equipment, or other system upgrades. The allocation of these costs depends on applicable utility tariffs, regulatory requirements, agreements, and the specific nature of the improvements. Some costs may be assigned to the developer or requesting customer. Other costs may be allocated through regulated utility mechanisms, depending on the circumstances and governing rules.
It would therefore be inaccurate to assume that the City of Glenn Heights must automatically pay for all infrastructure improvements associated with the proposed facility. It would be equally inappropriate to assume that every infrastructure cost must be paid exclusively by the developer.
The actual financial responsibilities should be established through the relevant utility arrangements and applicable regulatory framework.
Residents may reasonably ask whether new electrical infrastructure would require municipal financial participation, affect local public property, or create other obligations for the City.
Those questions should be answered through documented agreements and applicable requirements rather than speculation.
The proposed Glenn Heights facility should be evaluated using reliable, project-specific electrical information.
Questions that deserve consideration include:
These questions do not presume that the proposed facility will create an electrical reliability problem. They also do not presume that the facility can be served without additional infrastructure or operational considerations. They identify information necessary for a responsible evaluation.
Electricity infrastructure involves technical systems, regulatory requirements, and decisions that extend beyond the authority of any single municipality. For this reason, responsible planning requires coordination among developers, utility providers, grid operators, regulators, and local governments within their respective areas of responsibility.
Residents should understand which organizations make particular decisions and what information is available to support those decisions. The developer can provide information about anticipated electrical demand, equipment, operating requirements, and project design.
Oncor and other responsible utility entities can address matters within their authority concerning electrical service and infrastructure.
ERCOT and state regulators address broader grid operations, planning, and applicable regulatory requirements.
The City of Glenn Heights remains responsible for carrying out its municipal duties under applicable laws and development regulations.
No single participant should be expected to answer every question outside its area of responsibility. At the same time, residents should not be left without clear explanations simply because an issue involves multiple organizations.
Public education is most effective when responsibilities are clearly identified, technical information is explained in understandable terms, and unanswered questions are acknowledged.
Data centers require electricity to operate computing equipment, cooling systems, networking infrastructure, and supporting facilities. Some data centers are substantial electrical customers, but their actual demand varies according to their size, equipment, workloads, and operating characteristics. AMF Mission Critical has proposed a cloud data center along Uhl Road, across from an existing Oncor electrical switch station.
That location is relevant to the project's electrical infrastructure considerations, but it does not independently establish the capacity available to serve the facility or the improvements that may be required.
A verified project-specific maximum electrical demand figure has not been established in the information available for this educational chapter.
Therefore, claims that the proposed facility will necessarily cause residential outages, increase household electricity bills by a particular amount, or require specific infrastructure improvements should not be presented as established facts without supporting evidence.
Likewise, assurances that the facility will have no effect on electrical infrastructure or broader system costs require appropriate support.
The responsible approach is to examine the actual electrical requirements, obtain information from the appropriate utility and regulatory entities, and communicate verified findings to residents.
Electricity reliability is too important for unsupported assumptions or blanket assurances.
As Glenn Heights continues to evaluate development opportunities, residents deserve factual information about how proposed projects may interact with essential infrastructure.
Our commitment remains consistent: to explain what is known, identify what remains unanswered, and encourage informed public participation.
Reliable infrastructure requires responsible planning. Responsible planning requires accurate information. And accurate information is essential to public trust.
Understanding Land, Habitat & Environmental Impact
As we continue our Understanding Data Centers: Facts. Process. Community. educational series, Chapter 5 focuses on an area several residents have asked about: the environment and wildlife.
Development changes land. That is true whether the project is residential, commercial, industrial, or something else. The important questions are: What is there today? What could be disturbed? What protections apply? What can be preserved or restored? And what safeguards should be incorporated into the final development plan?
Those are fair questions, and they deserve factual answers. 🌳
One question I've received is: How much land and wildlife habitat will be disturbed?
You can't responsibly answer that simply by looking at the property's total acreage. The actual disturbance depends on the final site plan, building footprint, roads, utilities, drainage infrastructure, setbacks, preserved areas, landscaping, and other improvements.
And remember, a final site plan for the proposed Glenn Heights data center has not yet been approved by the City Council.
That distinction matters.
Before I characterize how much habitat would actually be lost or altered, I want to see the detailed plans and understand the existing environmental conditions on the property. The EPA notes that land development can affect wildlife habitat, water quality, and watershed function, among other environmental resources. US EPA
What happens to the trees and vegetation already on the property?
Some vegetation may have to be removed wherever buildings, roads, utilities, and other infrastructure are constructed. But that does not mean every tree or natural feature necessarily has to disappear.
This is where the detailed site plan becomes important.
I want us to understand what existing vegetation can reasonably be preserved, what the applicable landscaping and screening requirements are, and where native or appropriate vegetation could be incorporated into the development.
Texas Parks and Wildlife specifically provides guidance to municipalities and developers regarding natural-resource management, site assessment, habitat restoration, native landscaping and sustainable development planning.
Could development affect wildlife?
Yes. Any substantial change in land use can affect wildlife by altering habitat, vegetation, food sources, movement patterns, light levels, and human activity.
But the nature and magnitude of that impact are site-specific. I don't want to speculate about which species may be present on this particular property or what impact construction could have on them without appropriate information.
The Texas Parks and Wildlife Department has an Environmental Review Team specifically tasked with helping identify, evaluate, and address potential impacts of development projects on natural resources of conservation concern. Its work includes commercial construction and urban infrastructure.
That gives us another avenue to explore as we continue asking questions about this proposal.
Environmental concerns aren't limited to how much water a facility uses. We also need to talk about what happens when it rains.
Development generally creates more impervious surface through roofs, roads, and pavement. Those surfaces can increase stormwater runoff and affect erosion, water quality, and surrounding habitat if they are not properly managed.
Texas regulates stormwater associated with construction. Under the current TCEQ Construction General Permit, projects disturbing one acre or more, including qualifying portions of a larger common plan of development, are generally subject to construction-stormwater requirements. Operators subject to the permit must develop and implement a Stormwater Pollution Prevention Plan (SWP3) containing measures designed to control pollutants in runoff.
For our project, I want residents to eventually be able to see and understand the proposed drainage and stormwater strategy rather than simply being told that drainage has been "addressed."
Environmental compatibility also includes what happens at the edge of the property.
Lighting, mechanical equipment, generators, landscaping, screening, setbacks and the placement of buildings can all influence how a development interacts with surrounding properties and wildlife.
This is why I've continued emphasizing buffering, landscaping and screening throughout our discussions.
The question isn't whether a development will be invisible. It won't be. The question is whether thoughtful site design can reduce its effects on surrounding properties and the environment, and whether those protections are clearly established before final approval.
Finally: What environmental studies, permits or reviews will be required?
There isn't one universal "data center environmental permit." Requirements depend upon the particular site, construction activity, equipment, environmental conditions, and other project-specific factors.
For example, construction stormwater requirements are administered through TCEQ, while TPWD can provide recommendations concerning potential impacts to fish, wildlife, and natural resources. Other federal, state, or local requirements may apply depending upon what is ultimately proposed and what resources are identified on the property.
So I'm not going to tell you today that every environmental question has been answered. It hasn't.
What I can tell you is that these are exactly the kinds of questions we should continue asking as the project moves from a conceptual proposal toward the detailed plans that would be required for further City review.
And when those plans come forward, I believe residents deserve the opportunity to understand not only what is being built, but also how the land, drainage, vegetation, wildlife, neighboring properties, and surrounding environment have been considered.
That's what this educational series is about.
Not telling you what to think. Giving you factual information with which to think. 💙💛
Planning Today for a Safer, Stronger Tomorrow
As we continue our Understanding Data Centers: Facts. Process. Community. series, Chapter 6 tackles another question I have heard repeatedly:
What would a data center mean for traffic, our roads, and the people who already travel them every day?
This conversation is especially important for Glenn Heights. We already know our community faces transportation challenges. So when we consider any major development, it is reasonable to ask not simply, “Will it create traffic?” but “How much? What kind? For how long? Where will it travel? And what infrastructure will be in place to accommodate it?”
Those are the questions that matter. 🚦
Let's start by separating construction traffic from permanent operational traffic, because they are not the same.
If the proposed data center moves forward, construction would create a temporary period of increased activity associated with workers, contractors, heavy equipment, construction materials, and deliveries.
How many trucks? How frequently? What hours? Which routes?
I don't have verified project-specific answers to all of those questions today, and I'm not going to manufacture numbers simply to fill in the blanks.
Those details should become clearer as Adetailed site plan, construction phasing, and related engineering information.
What I do believe is important is identifying the anticipated construction routes before construction begins, particularly where heavy vehicles could interact with residential traffic, school traffic, pedestrians, or already-congested corridors.
Once construction is finished, the traffic picture changes considerably.
A cloud data center does not function like a grocery store, restaurant, apartment complex, or traditional office building where large numbers of customers, residents, or employees continuously enter and leave throughout the day.
The developer has indicated that the proposed facility would have a relatively small permanent workforce, which is one reason we expect normal operational traffic to be substantially different from the temporary construction period.
But again, “less traffic” is not a traffic study.
Before making a definitive project-specific statement, I want to see the anticipated employee counts, shift patterns, service vehicles, deliveries, and projected daily trips associated with the final plan.
Then comes the bigger question:
Can our roads handle it?
That requires more than looking at a map. A meaningful transportation analysis considers existing traffic conditions, roadway capacity, intersections, turning movements, access points, peak travel periods, and the additional trips a proposed development generates. And in Glenn Heights, that analysis cannot occur in a vacuum.
We already have transportation pressures in portions of our city, and we are dealing with growth and major transportation projects throughout the region. Any traffic analysis should begin with the conditions residents are experiencing today, then determine what additional impact the proposed development could create. That is the information I want to see.
Construction will inevitably cause some disruption. The objective should be to manage it rather than pretend it won't exist.
That can include designated construction routes, delivery scheduling, work hours, signage, temporary traffic controls, construction staging, communication with residents, and coordination when work affects public roadways.
For projects involving the state highway system, TxDOT's traffic-control framework specifically calls for planning that moves motorists, pedestrians, bicyclists, and transit through or around work zones safely and efficiently while minimizing hazards and unnecessary delay.
That planning principle is important here too:
Construction should not be allowed to simply happen around the community. It should be planned around the community.
This is also where the proposed Uhl Road improvements become particularly important.
Road infrastructure associated with development should not be viewed only as a way to get vehicles into and out of the development. We should be asking whether those improvements also strengthen the transportation network for the people who already live here.
As this proposal advances through the development-review process, I want clear answers regarding:
Where will the primary entrance be? How will trucks enter and exit? What improvements will be made to Uhl Road? Will turn lanes or other improvements be necessary? How will construction interact with nearby transportation projects? And which improvements are the developer's responsibility?
TxDOT's own design guidance recognizes that construction planning may need to account for impacts extending beyond the immediate work zone and into the surrounding transportation network. Texas Department of Transportation
And finally, traffic isn't just about cars. It is about people.
Residents trying to get home. Parents taking children to school. School buses. DART riders. Police, fire, and EMS. Pedestrians. Businesses receiving deliveries. And families simply trying to move through their community.
That is why I am particularly interested in how construction traffic would be scheduled and routed, how residents would be notified about significant disruptions, and how emergency access would be protected.
TxDOT's temporary traffic-control guidance emphasizes maintaining mobility and safety through construction areas and preserving access while work is underway.
Those are reasonable expectations for our community as well.
Will construction create additional traffic? Yes.
I don't think it serves residents to pretend otherwise.
Will that temporary construction traffic be the same as the long-term traffic generated once the facility is operational? No. Those are two different phases and should be evaluated separately.
And do we currently have every project-specific traffic number necessary to quantify either one?
No.
That is precisely why detailed plans, engineering analysis, and continued review matter.
Based on the information available today, I believe the appropriate approach is to identify the impacts, require appropriate infrastructure, establish a construction-management strategy, protect existing residents, and hold everyone involved accountable for the commitments ultimately made.
Throughout this series, I've tried to be very intentional about one thing: where we have answers, I will share them. Where we don't, I will say that too.
Because transparency doesn't mean pretending every question already has an answer.
It means continuing to ask until we get one. 💙💛
Opportunity Today. A Stronger Tomorrow.
As we continue our Understanding Data Centers: Facts. Process. Community. series, Chapter 7 moves into one of the most important questions surrounding any major development:
What does this actually mean economically for Glenn Heights and the people who live here?
When we talk about economic development, it is easy to focus on a large investment number or the phrase “job creation.” But I believe residents deserve to understand what kinds of jobs are created, how long those jobs last, what opportunities may exist for local workers and businesses, what revenue may be generated, and what measurable value the community receives in return.
So, let's break it down. 💼
The first employment impact would occur during construction.
A project of this nature can require workers across numerous skilled trades and specialties, including electricians, plumbers, HVAC technicians, equipment operators, concrete workers, engineers, construction managers, security professionals, and other contractors.
But there is an important distinction:
Construction jobs are temporary jobs associated with building the facility. They should not be represented as permanent employment.
For the proposed Glenn Heights project, I do not yet have a verified project-specific construction workforce number or final construction schedule. As those details become available, I want to know not only how many construction jobs may be created, but also what opportunities may exist for local contractors, subcontractors, and skilled tradespeople.
Then there are the jobs that remain after construction.
Cloud data centers are highly automated facilities. They generally do not employ as many permanent workers as you might find in a large office complex, manufacturing facility, or major retail development.
Permanent positions can include information technology professionals, network and systems technicians, facilities and electrical personnel, security, operations specialists and management.
The developer has indicated that the proposed Glenn Heights facility would have a relatively small permanent workforce.
That needs to be said plainly.
Economic development should never be evaluated by inflating a temporary construction workforce and presenting it as though those workers will remain at the facility indefinitely.
But the workforce conversation shouldn't end with the number of permanent employees.
One of the questions I am particularly interested in is:
Can we create a pathway that allows residents, especially our young people, to compete for the jobs that do exist?
Data centers require technical skills. That creates an opportunity to explore partnerships involving our school districts, community colleges, universities, workforce organizations, and the private sector.
Those partnerships could potentially include career exposure, internships, certifications, apprenticeships, technical training, and other pathways into information technology, electrical systems, HVAC, cybersecurity, facilities management, and related careers.
Those opportunities are not automatic, and I don't want to suggest that agreements exist where they do not.
But I believe they're conversations worth having. Because attracting investment is one thing.
Connecting that investment to our people is another.
Jobs are only one part of economic impact.
A major private investment can also affect the City's tax base and generate property-tax revenue. Construction and ongoing operations may create additional economic activity through purchases of goods and services.
For Glenn Heights, that matters because additional revenue can help support the services residents rely upon, including public safety, infrastructure, parks and other municipal priorities.
However, gross investment and community benefit are not the same measurement.
Any economic-development agreement, incentive, or public commitment should be evaluated alongside the revenue and other benefits the community is expected to receive. That is the equation residents deserve to see.
Another question we should be asking is:
How much of the economic activity can stay local?
A facility may require contractors, landscaping, maintenance, security, food services, equipment, supplies, and numerous other goods and services throughout construction and operation.
I want to explore whether qualified Glenn Heights and Best Southwest businesses can compete for those opportunities.
Again, I am deliberately saying “opportunity,” not “guarantee.”
Unless a specific local contracting or procurement commitment is established, I will not represent it as one.
But when major investment comes into our community, I believe asking how local businesses can participate is entirely appropriate.
And this may be the most important section of Chapter 7.
How should Glenn Heights measure whether this project is ultimately a good economic deal for the community?
Not simply by the size of the building.
Not simply by the announced investment.
And certainly not simply by counting construction jobs and permanent jobs together.
We should look at the entire picture: private investment, net tax revenue, infrastructure improvements, developer obligations, incentives, employment, workforce opportunities, local business participation and other tangible community benefits.
In this particular proposal, discussions have included $15M Uhl Road improvements, a $1 million contribution toward Heritage Park, a public hike-and-bike trail, and additional property-tax revenue.
Those items matter.
But as I have said throughout this series, I want residents to understand the details, the responsibilities attached to them, and ultimately what is delivered.
A data center should not be sold to a community simply by saying:
“It will create jobs.”
That statement alone doesn't tell us enough.
We should ask:
How many are temporary? How many are permanent? What kinds of jobs are they? What skills do they require? Can our residents prepare for them? Can our businesses participate? What revenue will the City actually receive? What infrastructure will be provided? What incentives or obligations are involved? And what does Glenn Heights receive over the life of the project?
Some of those answers are available today. Others still require additional project-specific information.
And I will continue making that distinction.
Because economic development should not simply be about bringing investment into a city.
It should ensure that investment creates meaningful, lasting value for the community that welcomes it. 💙💛
Real Questions. Facts. A Stronger Tomorrow.
As we continue our Understanding Data Centers: Facts. Process. Community. series, Chapter 8 addresses one of the most personal questions residents have raised:
“What could this mean for the value of my home?”
I understand why that question matters. For many families, a home is their largest financial investment. It is also where they raise their children, build memories, retire, and establish roots in a community. So when a significant development is proposed nearby, residents have every right to ask what effect it could have on their property and quality of life.
But this is also an area where we need to be especially careful about making broad claims.
I am not going to tell residents that a data center will automatically increase surrounding property values. I am also not going to tell residents that it will automatically decrease them.
Neither conclusion should be presented as fact without evidence. Let's look at why. 🏠
Property values are influenced by many factors, not one. Location, housing supply and demand, interest rates, neighborhood conditions, schools, public safety, infrastructure, amenities, comparable sales, surrounding land uses and broader economic conditions can all influence what buyers are willing to pay for a home. That means isolating the effect of one nearby development can be complicated.
This is particularly important when discussing data centers because these facilities vary substantially in their size, design, location, surrounding land uses, setbacks, landscaping, mechanical systems and proximity to residential neighborhoods.
So when someone says, “Data centers destroy property values,” my next question is:
What data are we using, and how comparable is that data to the project being proposed in Glenn Heights?
The same standard applies to anyone claiming the opposite.
Distance matters, but proximity alone doesn't tell us everything.
Two homes could theoretically be the same distance from two different developments and experience very different conditions depending on what exists between them.
Those details matter and this is why I believe any discussion about property values should be tied to the actual site plan and actual conditions surrounding the Glenn Heights proposal, rather than assumptions based solely on the words “data center.”
This is one reason I have repeatedly emphasized landscaping, screening and buffering. These aren't simply cosmetic issues. The way a development transitions into its surroundings can affect how neighboring properties experience it.
Trees, landscaping, setbacks, fencing, berms, architectural treatments and the placement of buildings and equipment can help reduce visual impacts and create separation between different land uses.
But saying that buffering can help is different from saying that adequate buffering will exist.
I want to see it on the detailed plans.
Those are legitimate questions.
Then we have noise, lighting and building appearance. These are quality-of-life issues, but they can also become part of how prospective buyers perceive a neighborhood. A data center can contain mechanical equipment associated with cooling, electrical systems and backup power. Exterior lighting and the physical scale of the building can also affect how a facility interacts with surrounding properties.
That does not automatically tell us what residents near the proposed Glenn Heights facility would experience.
Before drawing conclusions, I want project-specific information regarding the location of major equipment, anticipated noise, lighting design, building orientation, setbacks and the measures proposed to reduce impacts at the property boundary.
And this conversation is bigger than an appraisal number. Residents care about the character of their neighborhoods. They care about traffic, noise, lighting, safety, drainage, road conditions, green space, the appearance of nearby development, and whether they continue to enjoy the community they chose to call home. Those concerns should not be dismissed simply because they cannot always be reduced to a dollar amount.
At the same time, concern should not automatically be converted into a prediction of harm.
Our responsibility is to examine the conditions that could affect quality of life and determine what can reasonably be addressed through planning, design, infrastructure and development standards.
This is where I believe our conversation about property values needs to become more disciplined. Rather than asking only:
“Do data centers hurt property values?”
Let's ask better questions.
And perhaps most importantly:
What does the actual Glenn Heights site plan propose?
That is how we move from speculation toward meaningful analysis.
I know some residents are concerned that this proposed development could negatively affect their property values.
I hear that concern. Acknowledging a concern and declaring an outcome are two different things. Based on the information available today, I do not believe we have sufficient project-specific evidence to responsibly tell residents that their home values will either rise or fall because of this proposed data center.
And I would be uncomfortable with anyone presenting either prediction as a certainty.
What we can do is examine the factors that could influence neighborhood impact.
That has been the purpose of this entire series. Not to minimize concerns. Not to manufacture concerns. Not to tell residents what conclusion they should reach. But to separate what we know from what we don't know, and give our community factual information with which to make informed decisions.
As we continue our Understanding Data Centers: Facts. Process. Community. series, Chapter 9 brings us to a question I believe every community should ask when considering a major development:
If this project moves forward, what does Glenn Heights receive in return, and how do we make sure those commitments are actually delivered?
Economic development should be a partnership.
A project may create private investment and generate revenue, but when a community is asked to accommodate a major development, residents deserve to understand the entire value proposition. Not just what is being proposed.
What is being committed to. Who is responsible for delivering it. When it must be delivered. And how we will know it happened.
Let's talk about it.
One of the most significant potential community benefits associated with the proposed development is Uhl Road. The project discussions have included reconstruction and improvements to Uhl Road, infrastructure that would serve the development but could also provide a broader benefit to our community. That distinction matters. I have consistently said that when development creates or increases an infrastructure need, existing taxpayers should not automatically be expected to carry that burden.
We should understand:
The details matter just as much as the promise.
Another benefit discussed in connection with the proposed project is a $1 million contribution toward Heritage Park. There has also been discussion of a public hike-and-bike trail associated with the development. Those are meaningful potential community investments.
But here again, I want us to move beyond simply saying, “We're getting a million dollars for the park.” Residents should ultimately understand when the contribution becomes due, how it may be used, what triggers the obligation, and how it fits into the City's larger vision for Heritage Park.
The same applies to the trail. Where will it go? How will the public access it? Who constructs it? Who maintains it? How does it connect with our broader pedestrian and trail network?
A community benefit becomes much more meaningful when residents can see exactly how it improves their quality of life.
Then there is tax revenue.
A major private development can substantially change the taxable value of property that may currently generate comparatively little revenue. That potential matters because property-tax revenue helps fund municipal operations and services. But here's where I want to be particularly careful. Market value, taxable value, projected revenue and actual revenue are not interchangeable terms. Neither is the total tax bill on a property the same thing as the amount ultimately received by the City of Glenn Heights.
And if incentives or economic-development agreements are involved, those must also be considered when evaluating the net fiscal benefit to the City. So rather than focusing on the largest number that can be placed on a presentation slide, I want us asking:
And over time:
That's the number that matters.
As we discussed in Chapter 7, community benefit can also extend beyond taxes and infrastructure. Construction and ongoing operations can create opportunities for contractors, suppliers, maintenance providers, landscapers, security companies and other businesses.
I believe it is appropriate to ask whether qualified Glenn Heights and Best Southwest businesses can compete for those opportunities. But I want to repeat an important distinction:
An opportunity is not the same thing as a commitment.
Unless local procurement, contracting or participation requirements are specifically established, we should not represent them to residents as guaranteed benefits.
Instead, we should identify where opportunities exist and explore how our local businesses can be positioned to compete for them.
This may be the most important distinction in this entire chapter:
A proposed community benefit and an enforceable obligation are not necessarily the same thing.
A presentation can say something is planned.
A conversation can say something is intended.
A rendering can show something beautiful.
But accountability requires us to ask:
What does the agreement actually require?
The City has entered into an economic development agreement with AMF Mission Critical. As this project progresses, the relevant agreements and development requirements are where commitments, responsibilities, performance standards, triggers and timelines become especially important.
For each major community benefit, I want residents to be able to answer four basic questions:
What is required? Who is responsible? When is it due? What happens if it isn't delivered?
That is how we move from a promise to accountability.
And accountability doesn't stop when an agreement is signed.
If this project moves forward, I believe significant commitments should be tracked.
Residents shouldn't have to remember something that was said at a meeting three years earlier and wonder: “Whatever happened to that?”
There should be a way to determine whether the obligation has been completed, remains pending, has changed pursuant to an agreement, or has not yet been triggered. Transparency shouldn't end when construction begins. In many ways, that's when accountability becomes most important.
I support economic development that produces measurable value for the people who already call Glenn Heights home.
That doesn't mean every benefit has to arrive in the same form.
Some may be financial.
Some may be infrastructure.
Some may improve recreation or connectivity.
Some may expand the tax base.
Some may create opportunities for businesses and workers.
But whatever the benefit is, we should be able to identify it, measure it and, where it is an enforceable commitment, track whether it was delivered.
Because ribbon cuttings are easy. Announcements are easy. Renderings are easy.
Accountability is making sure the community ultimately receives what was actually promised.
That is the standard I believe our residents deserve. And it is the same standard I will continue applying as we move through this process.
Facts. Process. Community. And yes, accountability.
Clear Steps. Informed Decisions. A Stronger Tomorrow.
Over the past several chapters, we have talked about water, electricity, the environment, traffic, jobs, property values, community benefits, and many of the questions residents have raised about the proposed AMF Mission Critical cloud data center.
For this final chapter, I want to bring the conversation back to something just as important:
The process. There has been some confusion about what the Glenn Heights City Council approved in 2024 and what that approval means today. So let's start with the most important point:
The City Council approved a zoning change. The City Council did NOT approve a final data center site plan.
Those are two very different things. And understanding that distinction is essential to understanding what happens next.
In 2024, the Glenn Heights City Council approved Ordinance O-15-24, changing the zoning applicable to the property associated with the proposed development. That zoning action established the land-use framework under which the property could be developed.
But zoning approval is not the same thing as approving the final design and construction of a particular building. It does not mean that every building, driveway, drainage feature, landscape plan, utility connection, access point, or other detail shown in later concepts has already received final City approval. That is why you have heard me repeatedly make the distinction between:
“The property was rezoned” and “The final site plan was approved.”
The first occurred. The second has not.
As detailed plans are developed, the City's development-review process becomes increasingly important.
Planning & Zoning helps evaluate development proposals against applicable zoning and development requirements and makes recommendations where required by the City's process.
That review gives us an opportunity to move beyond concepts and renderings and examine the details.
Those details matter because a concept tells us what someone wants to build. A detailed plan tells us how they propose to build it.
This is where many of the questions we've explored throughout this series come together. A project of this scale involves multiple layers of review, potentially including detailed site planning, civil engineering, drainage, utilities, infrastructure, building and fire requirements, permitting, and other applicable development standards. Some matters may involve the City.
Others may involve utilities or county, regional, state, or federal entities depending on the particular issue. And some requirements will not become relevant until particular stages of development.
That is why I have been careful throughout this series not to tell residents that every question has already been answered. They haven't.
There are things we know. There are things we are continuing to learn.
And there are things that cannot be definitively answered until the developer submits the detailed information necessary for the next stage of review.
That's not avoiding the question. That's how the development process works.
Residents have also asked:
“When do we get a say?”
Public participation does not have to begin and end with one Council meeting.
It includes following agendas, reviewing publicly available materials, attending meetings, submitting comments, asking questions, participating in public hearings when required, and communicating with your elected representatives. And I want that participation to be informed participation. That is one of the primary reasons I created this series. Whether you ultimately support this project, oppose it, or remain undecided, I would rather you reach that conclusion after examining information than after reading a rumor on social media. Your questions matter.
And as additional project-specific information becomes available through the City's process, our questions should become increasingly specific too.
Another important part of the process is understanding what the City can and cannot require.
Municipal decisions don't occur in a vacuum.
Part of responsible governance is knowing the difference.
My commitment is to continue asking our professional staff and legal counsel those questions when necessary so that decisions are based not only on what we might want to do, but also on what we are legally authorized and obligated to do.
There isn't one single moment when a project like this goes from “proposed” to “built.”
There are steps.
That is why I will continue watching the process closely. And as meaningful milestones occur, I will continue sharing information with our residents.
When we started this series, my goal was never to convince you to support a data center. It was never to convince you to oppose one either. My goal was much simpler:
Give our community more information.
Over ten chapters, we've asked hard questions.
💧 What about our water?
⚡ What about electricity and the power grid?
🌿 What about the environment and wildlife?
🚧 What about traffic and construction?
💼 What about jobs and economic impact?
🏡 What about property values and our neighborhoods?
🤝 What benefits could our community receive, and how do we hold everyone accountable?
🏛️ And finally, what has actually been approved and what still has to happen?
I have never believed that transparency requires having every answer immediately.
Transparency requires being willing to tell people what you know, what you don't know, and what you're doing to find out.
That is what I have tried to do throughout these ten chapters.
And although this is the end of the Understanding Data Centers series, it is certainly not the end of the conversation. As new information becomes available, as plans move through the process, and as additional questions arise, I will continue communicating with you.
Because an informed community doesn't require everyone to agree. It requires everyone to have access to the information necessary to reach an informed conclusion of their own.
And perhaps that is the most important takeaway from this entire series:
Understanding Data Centers: Facts. Process. Community.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.