A campus can have an active utility application, a promising supply discussion and an electrical design that still cannot support a tenant opening date. These are pieces of a delivery route, not interchangeable evidence that power is ready. When a date slips, the owner's first task is to identify which dependency moved and which commitments still rely on the old assumption.
The campus problem
Illustrative scenario, not a claimed client result.
An owner controls a Texas site and has progressed a large-load request. The operator wants an initial data hall before the ultimate campus build-out. Civil procurement is approaching, but the utility correspondence, electrical design and tenant schedule use different load assumptions. The assignment is to establish and execute a power pathway for an agreed operating phase, rather than keep every package moving against an unsupported date.
Separate system availability from service at the tenant boundary
The route runs through several handoffs: the system study position, provider facilities, land and easements, customer-owned electrical works, equipment delivery, protection settings and commissioning. A positive result at one handoff does not close the others. For example, equipment on site cannot compensate for an unresolved right of way, and completed civil work does not establish permission to energize. Track each dependency by evidence, responsible party and the date it must close to protect the tenant schedule.
Load definitions matter at every handoff. An IT-load promise is not the same as facility demand at the point of interconnection. Cooling and other supporting systems consume power, and their demand changes with design and operating conditions. The responsible engineers must reconcile those values. The commercial team then needs to use the same basis when discussing staged service, minimum commitments and the capacity available to additional tenants.
The Texas context
ERCOT’s Large Load Integration materials include project-information requirements, a Load Commissioning Plan and documentation used to evaluate project eligibility. This creates a practical owner-side question: does the campus plan match the submitted electrical and commissioning assumptions? The applicable process and project status must be confirmed with the interconnecting utility.
The commitment ledger must reconcile to the load model
Separate provider-supported capacity, tenant-reserved demand, operating reserve and the next tranche still conditional on works. For each tranche, identify who signs and funds the service obligation, when security is due and whether the tenant payment starts before or after availability. The site can have a technically plausible energization route and an unfunded period between equipment release and rent commencement. Bring that gap to the owner before procurement, not after a revised utility invoice.
Recover a slipping date without replacing one unsupported promise with another
If the delayed dependency is a shared upgrade, a smaller initial ramp may be worth testing. If it is a site-specific easement, an alternative route may matter more than a different energy supplier. If the gap is lengthy, bridge generation becomes a separate development project with fuel, permits, operating costs and transition work. Identifying the actual cause prevents the owner from buying a response that does not change the controlling date.
Sitebraid would align the utility-supported schedule with equipment releases and the tenant's minimum useful opening configuration. We would compare the capital required to accelerate, the cost of accepting a later date and the obligations created by temporary supply. The recommended route should state what is available first, what remains conditional and who absorbs a further delay. If no route supports the promised date, the owner needs that conclusion before the next binding tenant commitment, not after another procurement release.
Solutions and their tradeoffs
Phase the grid connection
A smaller opening phase meets the operator brief and the utility can support the proposed sequence.
Conditions to resolve: Written provider position, accepted design basis and the cost of later expansion.
Develop a bridge-power option
The operator can accept the operating model and a separate generation project is feasible.
Conditions to resolve: Fuel, air authorization, operating responsibilities and transition scope before equipment commitment.
Change the date or site
Neither route supports an acceptable commercial outcome.
Conditions to resolve: Revised investment case including sunk cost, cancellation exposure and alternative-site timing.
A recovery schedule must move the controlling date
Hypothetical earliest completion months from a common decision date. All durations and dependencies require project-specific confirmation. This is not an ERCOT or utility schedule.
Swipe or scroll to compare all columns.
| Prerequisite | Current completion | Recovery implication |
|---|---|---|
| Customer electrical works and tests | Month 12 | Finishing in month 10 does not advance service if another prerequisite controls. |
| Utility works, including route rights | Month 18 | Rights and construction must both support this date. |
| Required equipment delivery and installation | Month 16 | Acceleration matters only if utility works also move. |
| All prerequisite packages ready | Latest of 12, 18 and 16: month 18 | With an assumed two-month final acceptance sequence, earliest service is month 20. |
| Utility works accelerated to month 14 | Equipment now controls at month 16 | Earliest service becomes month 18, not month 16; a month-17 tenant date remains unsupported. |
This is the development problem behind our power date slipping challenge. Our Power & energization capability explains the scope Sitebraid can take on.
Putting the analysis to work
We would reconcile the site-control documents, utility correspondence, study submissions, electrical models, load commissioning plan, one-line diagrams, equipment reservations and operator brief. The electrical team must distinguish IT load from total facility demand and identify the phase-by-phase ramp. Every capacity and date should have a source, an owner and a status: requested, studied, committed or achieved. A commercial target must not silently become an engineering assumption.
How Sitebraid would support this decision
Establish the real constraint
Bring the utility and project electrical engineer into a working session on the same phase definition. Separate missing studies or information from network upgrades, site-side construction and commissioning prerequisites. Assign each open item to the party that can actually close it.
Convert the route into buildable work
Map land rights, substation works, protection, metering, access and customer-side systems into defined packages. Confirm equipment specifications before orders, establish the interface between utility and owner construction, and obtain the relevant approvals through the responsible teams.
Sequence spending around evidence
Connect utility milestones and equipment delivery to the civil and building schedule. Present the owner with explicit release points for procurement and works. Identify which early activities preserve options and which create stranded cost if energization moves.
Complete the phase and verify it meets requirements
Track construction dependencies through inspections, testing and operator turnover. Resolve interface issues with the responsible parties. Treat permission to energize, actual energization and accepted IT capacity as separate milestones, with different evidence and decision makers.
How we protect the decision
The owner retains approval of capital commitments, changes to the operating brief and acceptance of schedule exposure. We would maintain a power-dependency register and a critical-path forecast with named actions and evidence dates. If a utility milestone moves, the response is a revised construction and commercial decision, not an unchanged opening date on a dashboard.
The result the owner should require
For a power-readiness engagement, completion could mean the agreed provider arrangements, design prerequisites and funded infrastructure packages are in place. For a delivery engagement, it would extend to the specific completed and accepted works. The contract must identify the endpoint. Neither a study submission nor an equipment order should earn a fee intended for delivered capacity.
How to measure progress
- Capacity supported by written evidence for the first phase, separately from ultimate IT MW.
- Unresolved critical-path prerequisites and their accountable parties.
- Capital exposed before the next external dependency is resolved.
- Accepted energization and turnover evidence against the agreed milestone.
The decision to take forward
Manage power as a sequence of accepted delivery conditions. Use the current provider record to set the plan, then connect it to the customer's works, tenant ramp and funding. An earlier date is useful only when the physical and contractual route can support it.
Continue with Bridge power is a development project, not a generator order. to examine the connected decision.