CAPABILITIES / DEFINED DEVELOPMENT SCOPE
A power commitment the campus can deliver.
We turn the gap between a utility position and a tenant operating date into a defined development scope. The work connects usable capacity, service conditions, infrastructure, equipment releases and tenant obligations. It does not replace the utility study or the engineer's design.
Engage us when the project has several plausible power routes but no defensible basis for choosing one, or when an agreed route is no longer supported by the facts. The first task is to identify which commitment must change before additional capital is exposed.
01 / ENGAGEMENT ENDPOINTS
These are distinct scopes, not an automatic three-stage contract. The engagement defines the selected endpoint, deliverables, authority and acceptance criteria.
You receive A phase-by-phase capacity and commitment model, route comparison and recommended investment sequence.
Acceptance The owner can select a route knowing which capacity is supported, what remains conditional and what a delayed phase costs.
You receive An integrated release package joining provider conditions, land rights, funded works and approved procurement dependencies.
Acceptance Each release has the required technical and commercial approvals. An unresolved condition is held or accepted explicitly by the authorized owner.
You receive Closure of the agreed utility, site-side and operator interfaces, with the responsible teams' test and permission records.
Acceptance The agreed operating load and conditions are accepted by the operator; open expansion obligations remain separately identified.
02 / WORK PRODUCTS
ILLUSTRATIVE DECISION / NOT A CLIENT RESULT
Illustrative decision: the provider supports an initial load below the tenant's requested opening requirement. We would reject treating the ultimate campus allocation as opening-day capacity. A smaller opening is viable only if the tenant accepts it and the engineers establish the operating configuration. Bridge generation stays out of the base case until fuel, air authorization, connection and funding are supported. If neither route closes, the recommendation is a revised commitment, not an accelerated equipment order.
03 / TEXAS EXECUTION
Reviewed September 10, 2026. These are development interfaces, not project-specific legal opinions. Counsel and qualified specialists confirm applicability and current requirements.
For affected projects, ERCOT's September 3, 2026 notice describes conditional Batch Zero classification, not unconditional eligibility. We obtain the provider's project-specific conditions and build their closure into the commitment schedule.
ERCOT September 3, 2026 conditional-classification noticeWith utility counsel, we reconcile the large-load framework with currently effective provider terms and project agreements. A statewide policy summary is not a quote for this campus. Generation alternatives require their own air and operating review.
Texas Utilities Code §37.0561Sitebraid owns the integrated development comparison, dependency closure and agreed release evidence. The owner chooses the commercial risk; the utility controls its service position; engineers and commissioning specialists retain design, protection, testing and certification duties.
Before engagement, agree the responsible lead, access to provider discussions, document authority and acceptance endpoint. Relevant experience can be discussed confidentially; this is a proposed service scope, not evidence of completed power delivery.