A large data center campus behaves less like a single building and more like an industrial district. Power, water, wastewater, drainage, roads, fiber and emergency services cross tenants and phases. The owner does not need to own every utility, but someone must integrate every service into one operating and funding plan.
The campus problem
Illustrative scenario, not a claimed client result.
A campus master plan includes several tenants, on-site generation, a new substation, water storage, wastewater treatment, fiber routes and dedicated emergency-response facilities. Each package has a sponsor, but the interfaces do not share one phase plan. Solar occupies future pad space, the water plant depends on power not included in the electrical balance, and regional infrastructure assumes contributions from tenants that are not yet committed.
Shared systems create value and common-mode exposure
Central assets can reduce duplication and support later phases. They also create dependencies that no individual building package owns. A water plant depends on electrical service, generation may depend on gas and water, and emergency access may share a corridor with construction traffic.
Ownership and operation should be chosen separately. A utility may operate an owner-funded extension. A district may finance an authorized regional asset. A third party may own generation under an offtake contract. Campus ownership adds control and also staffing, compliance, maintenance and replacement duties.
The Texas context
Large loads have defined ERCOT integration processes, while water and wastewater projects follow separate provider, planning and permitting pathways. TCEQ states that wastewater and certain stormwater discharges require applicable authorization. TWDB's state planning process evaluates future supply needs and sponsoring entities at regional scale. A campus therefore cannot treat power, water, discharge and land as interchangeable private commodities. Each system has its own authority, operator and delivery evidence.
Build a campus service balance before assigning the assets
Create one schedule of demand, quality, availability, reserve and recovery for every essential service. Follow power into pumps and treatment, water into cooling and generation, and discharge through permitted routes. Then test drought, fuel interruption, a late tenant and loss of one shared corridor.
Sitebraid would coordinate the integrated campus basis across providers, public partners, technical teams, operators and tenants. The owner receives a phased system plan whose contracts, land and acceptance evidence agree with the services the campus must provide.
Solutions and their tradeoffs
Provider-led core services
Keep major utilities external where dependable service is available on workable terms.
Conditions to resolve: Confirm capacity, extension scope, operating standards and the owner contribution.
Hybrid campus utility system
Own selected shared assets while utilities and specialists provide others.
Conditions to resolve: Create a single operating authority and prevent gaps between package warranties.
Regional partnership
Co-fund infrastructure that serves the campus and documented public demand.
Conditions to resolve: Separate required mitigation from incremental regional benefit and fund operations over the asset life.
Choose ownership service by service
Swipe or scroll to compare all columns.
| Structure | When it can fit | Exposure to retain |
|---|---|---|
| Utility-owned | Provider can fund, deliver and operate the required service | Schedule, extension payments and service conditions |
| District or public partner | Authorized entity can finance or operate defined regional assets | Approvals, revenue sufficiency and ongoing governance |
| Campus-owned | Control and dedicated performance justify owner capital and operating responsibility | Staffing, compliance, lifecycle replacement and tenant recovery |
| Third-party owned | A specialist can finance against supportable service contracts | Credit, performance, step-in, termination and replacement service |
This is the development problem behind our infrastructure budget gap challenge. Our Campus readiness capability explains the scope Sitebraid can take on.
Our approach: from the decision to delivery
Build one campus service basis covering energy and power, fuel, raw and treated water, cooling, wastewater, stormwater, fiber, roads, security and emergency response. For each service, record demand, quality, availability, storage, backup, operator, owner, approval, construction package, funding source and tenant allocation. Reconcile common corridors and common-mode dependencies. Test whether proposed heat reuse has an actual nearby customer, delivery route and contract rather than counting theoretical heat as a community benefit.
Set service targets by phase
Define the first tenant's accepted service and the reserve needed for later phases. Use consistent demand units and design conditions across technical and commercial workstreams.
Resolve the system interfaces
Reconcile power for pumps and treatment, water for cooling and generation, corridors for utilities and access, and emergency operation across systems. Identify failures that can disable several services at once.
Allocate capital and operations separately
An entity can fund an asset without being the right long-term operator. Establish ownership, control, maintenance, compliance, customer allocation and replacement funding for each layer.
Deliver a coordinated phase
Sitebraid joins provider commitments, technical packages, public agreements, tenant requirements and acceptance evidence in one campus schedule. The specialists retain their regulated duties. The owner receives a system that can operate, not merely a collection of completed assets.
How we protect the decision
Do not market self-sufficiency as isolation from public systems or oversight. Do not count the same reserve for tenant continuity, grid support and future expansion. Keep regional benefits tied to accepted service, beneficiaries, operating responsibility and funding. Test drought, fuel loss, wastewater interruption, tenant delay and common-mode failure.
The result the owner should require
Every required service has a supported phase capacity, accountable operator, funded capital route, lifecycle responsibility and tested interface with the other campus systems. The owner knows which dependencies remain external and what happens when one service or tenant does not arrive as planned.
How to measure progress
- Service capacity and reserve reconciled by phase.
- Shared assets without an identified operator or lifecycle budget.
- Common-mode failures affecting multiple campus services.
- Capital supported by committed tenants versus speculative expansion.
The decision to take forward
Define self-sustaining as accountable service delivery, not independence from public systems. Own only the assets whose control justifies the lifecycle responsibility, and keep funding and operations visible when future tenants do not arrive.
Continue with Finance the campus in layers. Make the obligations work together. to examine the connected decision.