sitebraid.

SITEBRAID REFERENCE / TEXAS CAMPUS DELIVERY

Texas Data Center Campus Infrastructure Responsibility Matrix

A practical owner-side matrix for assigning control, funding, approval, construction, operation and acceptance across shared Texas data center campus infrastructure.

A multi-tenant data center campus can have a complete design and still lack a deliverable infrastructure plan. The common failure is not an empty scope. It is a scope whose verbs belong to different parties: a provider approves, an owner funds, a contractor builds, an operator accepts and a tenant depends on the result.

This matrix is a starting point for assigning those responsibilities before commitments collide. It does not prescribe one ownership model. Texas utility territories, municipal structures, districts, site conditions and contracts differ. The owner should replace every provisional entry with project-specific evidence from the responsible authority, provider, designer, operator and counsel.

Campus infrastructure responsibility matrix

Use each row as a coordination prompt. The final project record should name the responsible entity, source document, date, conditions and next acceptance event.

Swipe or scroll to compare all columns.

SystemTypical control or authorityLikely funding questionDelivery and acceptance record
Electric service and substationThe serving utility, cooperative or municipal system controls its service process. ERCOT requirements can apply through the interconnecting provider for qualifying large loads.Who funds dedicated and shared electrical works, deposits, security and minimum obligations before each tenant ramps?Provider-supported service scope and schedule; executed agreements; accepted design and equipment milestones; commissioning and energization records.
On-site generation and microgridThe owner, generator, operator, provider and applicable regulators divide authority according to the selected configuration. A private location does not remove interconnection, permitting or operating requirements.Who funds fuel, interconnection, standby service, controls, maintenance and the downside if permanent service arrives early or late?Approved operating boundary; permits; protection and controls basis; fuel and maintenance contracts; tested transition and emergency procedures.
Water supply, storage and treatmentThe certificated provider, municipality, district or other authorized supplier controls the applicable service route. CCN territory alone does not establish physical capacity.Who pays for source, transmission, storage, treatment and oversizing that later phases or other users may need?Provider commitment; supported demand and quality basis; funded improvement scope; easements; permits; testing and accepted service date.
Wastewater and dischargeThe relevant provider and environmental authorities control service and discharge permissions. Cooling choices determine the quantity and quality case.Who funds off-site conveyance or treatment upgrades, and who carries cost if tenant water assumptions change?Accepted discharge basis; provider capacity confirmation; permit path; funded works; connection and operating acceptance.
Drainage and flood-management worksLocal development authorities and responsible drainage entities govern the applicable criteria. The owner controls the integrated site response within its rights.Which works serve the first phase, preserve later phases or provide a wider regional benefit, and how is each portion recovered?Approved studies and plans; land and easement control; construction acceptance; inspection and long-term maintenance assignment.
Roads, access and emergency responseCities, counties, TxDOT or other road authorities control affected public routes. Emergency-service providers define response requirements with the campus operator.Who funds turn lanes, road upgrades, controlled access, facilities, equipment, staffing and recurring service?Approved access and traffic plan; right-of-way; construction acceptance; emergency operating plan; funded staffing and service commitments.
Fiber routes and campus entriesCarriers control their networks; the owner controls campus corridors and entry arrangements within its property rights. Two commercial providers may still share one physical route.Who funds diverse laterals, ducts, meet-me facilities and protected corridors for future tenants?Route evidence; easements and access rights; physical-diversity review; tested service; operating and repair responsibilities.
Shared corridors and utility infrastructureThe owner coordinates land, tenant, provider and operator rights. Individual utilities or districts may own and operate specific assets.Which party carries early shared capital, how is later use charged and what happens if later tenants never arrive?Integrated corridor plan; ownership schedule; access and easement record; interface register; accepted phase handoffs and lifecycle responsibilities.
Entitlements and public commitmentsThe applicable city, county, district and other authorities control their approvals. Counsel should establish the project-specific route and obligations.Which infrastructure or community commitments are conditions of approval, sponsor investments or recoverable shared works?Adopted approvals and agreements; service and mitigation commitments; accountable owners; funding; dates; reporting and closure evidence.
Tenant interfaces and campus operationsThe owner and operator coordinate shared systems, while tenant agreements define rights and obligations subject to the actual service structure.How are reserves, minimum commitments, expansion rights, operating costs and shared-asset repayment allocated between tenants and sponsor?Reconciled capacity and commitments ledger; interface agreements; change control; operating acceptance; current campus basis after each phase.

Six rules for using the matrix

Assign verbs, not labels

For every system, name who specifies, approves, funds, designs, constructs, owns, operates, maintains and accepts. Writing only utility, city or developer hides the handoffs that decide schedule.

Separate territory from service

A boundary or service territory identifies a potential authority or provider. It does not prove capacity, funding, land rights, approvals or a usable delivery date.

Separate ownership from operation

An owner-funded asset may be utility-operated. A district-financed improvement may serve several users. Campus ownership increases control and also creates staffing, compliance, maintenance and replacement duties.

Allocate cost by phase and cause

Distinguish first-phase requirements, shared campus capacity, future options and wider regional benefits. Do not treat speculative later tenants or existing residents as an unexplained backstop.

Define acceptance before release

A completed construction package is not necessarily usable service. Identify the evidence required by the provider, authority, operator and affected tenant before releasing capital.

Update after every commitment

A new tenant date, load, cooling basis or public commitment should update the responsibility matrix before the next contract, procurement release or development representation.

Sources and scope

  1. ERCOT large-load integration

    Large-load project information and commissioning context.

  2. Texas Water Code, Chapter 13

    Water and sewer utility regulation and certificates of convenience and necessity.

  3. TCEQ water districts guidance

    Texas water-district creation, powers and oversight context.

  4. Texas Local Government Code, Chapter 43

    Municipal annexation and service-plan context.

  5. TxDOT access management resources

    State-highway access-management context.

  6. FCC broadband data collection

    A public broadband-availability starting point, not proof of route diversity or deliverable service.

This reference is Sitebraid’s owner-side coordination framework. It is not legal, engineering, utility or regulatory advice and does not establish site-specific service, authority, capacity, cost or schedule. The linked public sources were reviewed September 10, 2026. Project teams should confirm current requirements with the responsible entities and qualified advisors.

Questions or corrections? Email [email protected].