Interconnection is a pricing problem, not an engineering one
Connection queues clear on economics, not merit. The engineers solve the study. The investors price the risk. A note on what that means for how investors should screen their pipelines.
Every conversation about interconnection queues eventually lands on engineering language. Reactive power. Short-circuit ratio at point of connection. Fault-level headroom. Load-flow base cases. The vocabulary is technical and it is the right vocabulary for the study.
But the vocabulary for the investment question is different. The question an investor has to answer is not whether the project can connect. It is what the project will connect for, when, and with what residual risk.
Three framings that drift
The engineer's question
Can the project meet the grid code at the declared point of connection, under the ISO's set of base-case dispatches, with reasonable mitigation plant?
The developer's question
What mitigation plant is the ISO going to require, what does that cost, and how does the capex delta move our competitive position in the queue?
The investor's question
Given the capex delta, the ISO's process for re-studying neighbours, and the expected behaviour of competing entrants, what is the probability-weighted date this project commissions, and what is the curtailment profile once it does?
All three are valid. But they are not the same question, and confusing them at the screening stage is expensive. An investor screening pipeline on the engineer's framing will routinely pay A$150k to A$500k for IE reports on projects whose price signal tells you the investment answer already.
Read the capacity curve, then the study
The single most information-dense data source in an interconnection queue is not the study pack. It is the queue position, the capacity cleared in recent comparable projects, and the pattern of re-scopes the ISO has forced on earlier entrants. Those three inputs tell you the price the market is willing to pay for connection risk on this node. The study then tells you whether the specific project is at or around that price, or an outlier.
An outlier in the cheap direction is an opportunity. An outlier in the expensive direction is a cost signal the ISO has already priced in, and the project is going to wear.
Our red-flag engine treats connection-queue information as a pricing signal first and a technical signal second. It is a small framing shift. It materially changes which projects a client's pipeline flags as investable.