Interconnection Queue

Projects enter queues for feasibility studies, system impact studies, facilities studies, and interconnection agreements. Withdrawals by earlier projects can force restudies and change cost allocations.

Congested regions may have multi-year delays and substantial network upgrade costs.

Queue uncertainty affects project start dates, tenant delivery commitments, capex budgets, power prices, and financing milestones.

For data-center platforms, a portfolio of queue positions can be valuable, but only if conversion probability and upgrade costs are realistic.

What is the project's queue position and study status?

Are required upgrades identified and funded?

Have nearby queue withdrawals or cluster studies changed timing or cost estimates?

Separate submitted requests from validated applications, completed studies, accepted upgrade costs, executed agreements, construction-ready projects, and energized capacity. Require evidence for deposits, site control, equipment orders, and utility milestones.

Apply stage-specific conversion probabilities rather than assigning equal value to every megawatt in a developer pipeline.

Projects are electrically interdependent. An earlier withdrawal can change power flows, network upgrades, and cost allocation for remaining requests, triggering restudy and delay.

Review cluster assumptions, financial-security deadlines, withdrawal penalties, shared-upgrade dependencies, and sensitivity to neighboring projects that the sponsor cannot control.

For Interconnection Queue, 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.