Of the contracted MW, how much is expected by the lease date — and how much of the printed pile can we actually name on the wire?
→Large load
Contracted MW is not delivered MW.
A lease is a claim. A printed load book is a pile. Named megawatts are footprints on a wire. Atlas holds them in separate columns, so a campus is not treated as live capacity and a metro is not treated as a published book.
Decision loop · Large load
Objectives
Contracted MW is not delivered MW.
A lease is a claim. A printed load book is a pile. Named megawatts are footprints on a wire. Atlas holds them in separate columns, so a campus is not treated as live capacity and a metro is not treated as a published book.
Objectives0/3
The lease MW, the P50 MW, the P90 MW. Nothing blended to make the book look full.
What the utility printed stays at book grain. Named is footprints Atlas can attach to a node. The rest is unknown.
A node is the POI or the corridor. Who else is asking for that wire is part of the path, not a footnote.
Audiences
Who the run has to hold.
Each seat sees a different cut of the same physical graph. The construct does not change. The capital question does.
Audiences0/3
What they printed. One row per utility or ISO. Not a US total. Not a metro number.
The wire. Asks sit here. Scores do not.
An LLC joined to a place. Unknown-owner rows stay unknown — that unknown is the warning.
Questions
Test the behavior the decision is meant to change.
Every follow-up runs against the same population, without survey exhaustion, so iteration moves at the speed of the decision.
Questions 0/3
Core metric
MW × Date × Probability
Illustrative
A decision run against the book.
A capacity desk was sizing a compute book to contracted megawatts before asking what had shown up at the meter, who else was asking for the same wire, and how much of the printed pile was still unknown.
Across the capital stack the same graph.
Infrastructure investors
Infrastructure capital is underwritten on schedules, contracts, engineering assumptions, and expected capacity. Atlas reconstructs those assumptions as an observable physical state — then returns a distribution only where the record supports one. You take a recommendation into IC, not a brochure score.
Lenders
Debt repayment depends on physical infrastructure delivering the capacity assumed in the financing case. Atlas reconstructs the delivery path — the node, the other asks on that wire, the upgrade they share — and carries physical delay through debt service and downside scenarios under the covenants you attach.
Insurance
Construction and operational risk often starts with physical dependencies that can be observed before a loss occurs. Atlas provides an independent view of project progress, critical dependencies, and delivery uncertainty — stated clocks beside observed clearance, shared gates named as shared.
Developers
Your project schedule is a network of dependencies. Atlas names the node each site sits on, who else is asking for that wire, and which constraint should take the next dollar — so development capital is sequenced against the bind, not the deck narrative.
Large load
A lease is a claim. A printed load book is a pile. Named megawatts are footprints on a wire. Atlas holds them in separate columns, so a campus is not treated as live capacity and a metro is not treated as a published book.
Built for infrastructure investors, lenders, insurers, developers, and large-load buyers who cannot treat a sponsor date as a base case.