enzwa lab · conduit · agentic data-centre delivery

Two energisation dates for the same campus.

Conduit models an 80MW build as eight linked orders with real lead times. Move one of them and the model re-solves the whole schedule. This page runs the plan as signed down the left, and the same build after the transformer slipped down the right. They start on one line and never meet again.

A tool for showing how one late order moves the day a data centre can switch on.

The problem

A large data centre is a chain of orders, and some of them, like the high-voltage transformer, take years to arrive. A normal schedule records a delay only once somebody reports it, and by then the room to recover has gone.

What it does

Conduit models the whole build as linked orders with real lead times. Move one and it re-plans the entire programme in front of you, including the date the site starts earning.

A high-voltage substation and a receding line of transmission pylons compressed by a long lens into a single plane, with a low grey industrial shell behind.
the constraint moved from the rack to the substation
01the divergence

One order moves. Everything after it moves with it.

Both columns below start from the same June 2026 date and the same eight orders. On the right, the transformer OEM pushes its delivery slot by sixteen weeks. That is the only change made to the model.

The planas signed
wk 000Day zero

Delphi North. 80MW, 24,000 GPUs, a two billion dollar campus. Eight orders on the critical path.

wk 000 · 053Grid interconnect

Fifty-three weeks to a firm energisation date. It runs alone: nothing in the chain overlaps it.

wk 006 · 091HV transformer

Eighty-four weeks, single source, ordered in week six. That is the earliest the design releases it.

wk 006No slack

The order already sits as early as the design allows. There is nothing left to pull forward.

wk 077 · 150Power train and fit-out

Switchgear, UPS, cooling, white space, GPUs. Each overlaps what precedes it, and the plan already counts that overlap.

wk 150 · 157Commissioning

Seven weeks of integrated systems test, then energisation.

wk 157Energised Jun 2029

The campus starts earning.

9.7 weeks
carried
The worldone order moves
wk 000Day zero

The same site, the same eight orders, the same start. Nothing has moved yet.

wk 000 · 053Grid interconnect

The utility holds its date. The queue position stands.

wk 000 · 101HV transformer

The OEM moves the slot sixteen weeks. This is the only change on the page.

wk 000What comes back

Ordering on day one returns six of the sixteen weeks. There is no earlier than day one, so ten are carried.

wk 086 · 159Power train and fit-out

All five finish ten weeks late. Their overlap was spent in the plan, long before the slip arrived.

wk 159 · 166Commissioning

The same seven weeks of test, ten weeks later.

wk 166Energised Aug 2029

Same building, same order book, ten weeks of nothing.

0 20 40 60 80 100 120 140 160 THE PLAN · ENERGISED WEEK 157 Grid interconnect HV transformer MV switchgear UPS & power Liquid cooling White space GPU servers Commissioning THE WORLD · ENERGISED WEEK 166 Grid interconnect HV transformer MV switchgear UPS & power Liquid cooling White space GPU servers Commissioning JUN 2029 AUG 2029 9.7 wk weeks from a June 2026 start

both programmes to scale · swipe to read the full 172 weeks

02where it lands

Where the delay happens decides what it costs.

Conduit lets the chain break anywhere. The same sixteen weeks are worth different amounts at different points, because each order carries a different share of overlap against the one in front of it. The outline bar is the delay injected. The solid bar is what arrives at the energisation date.

DISRUPTION INJECTED (OUTLINE) · AT THE END (SOLID) 0 5 10 15 20 Interconnection study delayed 20 wk 20 wk HV transformer slips 16 wk 9.7 wk Cooling vendor defaults 12 wk 3.6 wk GPU allocation pulled forward 10 wk 5 wk weeks

computed from Conduit’s chain, speed-to-power objective · swipe for the full scale

disruptioninjectedat the endwhy
Interconnection study delayed20 wk20 wkThe utility node runs alone. Nothing overlaps it, so it passes through whole.
HV transformer slips16 wk9.7 wkSix weeks come back by ordering on day one, and day one is the floor.
Cooling vendor defaults12 wk3.6 wkCooling runs largely in parallel, so most of the delay disappears into the overlap.
GPU allocation pulled forward10 wk early5 wk earlierGood news travels at half speed. Half of it is absorbed by the same overlap.
03the two with no float

The nodes that absorb nothing are the ones the market is worst at.

Grid interconnection and the high-voltage transformer are the two orders that pass a delay through untouched. They are also the two with the longest queues in the real market.

A single large high-voltage power transformer standing alone on a concrete pad, radiator fins down its flanks and porcelain bushings on top, the substation lattice flattened behind it.
the forty million dollar object that sets the date
the real constrainttodaycontext
Large power transformer, 100 MVA and above, US delivery128 to 143 weeks7 to 14 months before 2020
Medium-voltage switchgear, 15 kV52 to 80 weeksmanufacturers sold out into 2028
Interconnection request to commercial operation, medianover 5 yearsaround 2,060 GW queued across 8,200 projects

Power infrastructure is 40 to 50% of what a data centre costs to build, and the queue figures come from Lawrence Berkeley National Laboratory’s Queued Up, 2026 edition, covering projects to the end of 2025. A shell with no energisation date is a finished asset earning nothing.

A long low windowless data-centre shell, freshly finished and completely dark, with empty external plant bases along an empty apron.
finished, and with no energisation date
04what the model does with it

The orchestrator prices the trade rather than arguing it.

A static schedule records a slip once somebody reports it. Conduit holds every dependency as a node with its lead time, supplier and risk, takes live signals from grid, vendors, transit and site, cascades a change downstream the moment it arrives, and proposes the recovery. Where it is authorised, it executes the re-route. Set what the build should optimise for and every routing decision and lead-time buffer re-weights to match.

objectiveenergisedplan confidencesingle points of failure
Speed to powerJune 202980%3
De-risk supply chainJanuary 203093%1
Minimise costMarch 203074%4

Resilience costs seven months and removes two single points of failure. Cost discipline costs nine months and adds one. The three columns are the same eight orders under three weightings, and the model will run any of them in front of the people who have to choose.

05open it

Break the chain yourself.

Conduit runs in the browser. Set the objective, fire a disruption, and watch the orchestrator cascade it and re-plan the energisation date. Every date on this page was knowable the day the OEM moved the slot, two and a half years before anyone on site would have felt it.

Open the control room →
Transmission lines running to the horizon, compressed by a long lens into a stack of near-parallel horizontal bands that never converge.
parallel to the horizon