Grid Interconnection

Projects typically submit an interconnection request, enter study phases, receive cost estimates for upgrades, negotiate agreements, and complete required construction before full service.

Large loads may need substation upgrades, transmission upgrades, distribution reinforcement, protection equipment, and utility coordination.

Interconnection agreements determine who pays for upgrades, when capacity is available, what operational limits apply, and what happens if costs or timelines change.

Tenant contracts may allocate delay risk between data-center owner, power provider, and customer.

Is interconnection approved, studied, under construction, or merely requested?

What upgrades are required, who pays, and what is the critical path?

Is the project exposed to queue delays, curtailment, or conditional service limits?

Track request acceptance, study deposits, feasibility or system studies, facilities design, executed agreement, equipment procurement, construction, commissioning, and energization. Each stage can change scope and required security.

Transformer lead times, substation work, transmission upgrades, land rights, and restudies can increase both schedule and capital needs after initial estimates.

Distinguish firm from interruptible service, initial from ultimate megawatts, and contracted demand from actual deliverability at required reliability. Review ramp limits, curtailment, backup requirements, and power-quality obligations.

Financing milestones should follow funded upgrades and enforceable capacity, with contingency for delay and tenant credits.

For Grid Interconnection, bridge physical capacity to billable revenue. Start with contracted or announced units, then deduct capacity not yet delivered, powered, cooled, networked, commissioned, accepted by customers, or available after redundancy and maintenance requirements.

Build a monthly schedule for installed capacity, usable capacity, committed capacity, billed capacity, and collected revenue. This prevents double-counting the same GPU, rack, or megawatt across marketing pipeline, financing collateral, and customer backlog.

Separate high-margin infrastructure revenue from pass-through power, setup fees, burst usage, credits, taxes, and reimbursed costs. Revenue quality depends on margin, duration, collectability, and renewal probability, not only gross contract value.

Review the exact contracting party, guarantor, minimum commitment, ramp schedule, delivery conditions, service levels, termination rights, cure periods, force majeure, assignment rights, deposits, and lender step-in rights.

Customer quality matters because AI demand can be volatile. Underwrite concentration, funding runway, payment history, use case, workload portability, and whether the customer can switch to hyperscalers or newer hardware.

Supplier diligence should cover title transfer, liens, serial-number evidence, warranty, replacement rights, export controls, delivery delay remedies, and whether a reseller actually controls the inventory it promises.

AI compute economics are constrained by power price, power availability, cooling design, rack density, network fabric, facility uptime, maintenance, software orchestration, spare parts, and labor. A GPU fleet can be technically installed but commercially weak if one of these constraints binds.

Stress power-price increases, curtailment, delayed interconnection, transformer lead times, cooling retrofits, customer credits, lower utilization, and hardware failures. Compare gross utilization with contribution margin after power and operating costs.

For financing, match customer contract tenor and hardware useful life to debt amortization. A long loan against short-lived or rapidly repricing hardware can leave residual-value risk with the lender or vehicle.

Track hardware by cohort: model, purchase date, installed cost, memory profile, networking, warranty, utilization, average realized rate, power draw, and expected resale or redeployment value.

Monitor competitive GPU pricing, new chip launches, customer workload shifts, inference versus training mix, cloud spot pricing, and resale market depth. A unit that still functions can become economically stale before physical failure.

Warning signs include revenue booked before acceptance, unclear ownership of hardware, repeated delivery delays, rising service credits, power constraints, low realized utilization, customer nonpayment, and capex needs that are not reflected in the financing model.