Skip to content

Case study, modelled

Silicon on the dock

The racks are here. The power is not.

Modelled

Three of four racks waiting for power start earning inside the same 2,800 kW interim envelope, recovering 48 rack-weeks at a 16-week gap, modelled.

Twenty-four racks are on site and a 2,800 kW interim envelope lights 20 of them. With the runtime the same envelope holds 23 racks on the conservative reading and all 24 on the stated basis, modelled. At a 16-week gap the conservative reading recovers 48 rack-weeks of earning.

Who it is for

A neocloud or GPU cloud operator with a part-energised site. The change-control and security reviewer holds the veto, and the finance function signs the move from a capitalised project line to an expensed one.

GPU cloud and neocloud

The basis

A modelled scenario

This is modelled. Every rack count, week and pound on this page is arithmetic over declared inputs you can change. One number is ours, and it is measured: up to 21% less GPU die power on NVIDIA H100 NVL over 48 hours. Managed and baseline arms ran under an equal cap, read from NVML. Die power is a lower bound on wall power. The rack in this model is a different NVIDIA architecture and stays modelled until a baseline run on it. A three-week validation on your own racks makes the figure yours.

Key figures

Every figure, what kind of figure it is, and its basis.

One figure is measured. The derived figures come from the same run. Everything else is modelled on the inputs below.

  • Less GPU die power

    measured

    Up to 21%

    NVIDIA H100 NVL, one continuous 48-hour window, six managed accelerators against a baseline arm under an equal cap, NVML die power.

  • Tokens per watt

    derived

    Up to +22%

    From NVML die power and vLLM serving throughput on the same run. The same tokens for less energy.

  • Throughput change in the run

    derived

    0%

    Same 48-hour run, Balanced mode, throughput and P99 latency held.

  • Reduction at the rack, conservative reading

    modelled

    About 15%

    21% applied to the 72% accelerator share, cascade factor one.

  • Reduction at the rack, stated basis

    modelled

    21%

    The die figure read as a floor on wall watts, a physics argument.

  • Managed rack draw

    modelled

    About 119 kW conservative; about 111 kW stated basis

    140 kW less each reduction.

  • Racks the 2,800 kW envelope holds

    modelled

    20 without the runtime; 23 conservative; 24 stated basis

    Envelope over rack draw, rounded down. The stated basis gives 25, capped at the 24 delivered.

  • Racks that stop waiting

    modelled

    3 to 4, which is 216 to 288 accelerators

    The fourth rack appears only on the stated basis or above an accelerator share of about 79%.

  • Share of the delivered fleet earning now

    modelled

    About 83% without the runtime; about 96% to 100% with it

    20, 23 or 24 racks of 24.

  • Dock-to-live removed from every delivered rack

    modelled

    2 weeks at a 16-week gap; 1 week at 8 weeks; about 3 weeks at 26 weeks

    3 of 24 racks multiplied by the gap, conservative reading.

  • Rack-weeks recovered, conservative reading

    modelled

    24, 48 and 78 at gaps of 8, 16 and 26 weeks

    3 racks multiplied by the gap.

  • Forgone contribution per waiting rack per day

    modelled

    About GBP 2,500 to GBP 20,000; anchor about GBP 9,300

    72 accelerators at published third-party hourly figures, utilisation 50% to 90%. The anchor is one rack-scale figure at 70%.

  • Gross value of the recovered weeks at a 16-week gap

    modelled

    About GBP 3 million at the anchor, inside about GBP 850,000 to GBP 7 million

    3 racks for 112 days is 336 rack-days, conservative reading. List figures, before realised revenue and running costs.

  • Gross value at the anchor, 8 and 26-week gaps

    modelled

    About GBP 1,600,000 and about GBP 5 million

    168 and 546 rack-days at the anchor.

  • More work inside the same envelope

    modelled

    About 15% conservative; 20% stated basis

    23 or 24 racks working against 20. Rack-count arithmetic, not a tokens-per-watt figure.

  • Reserve inside the envelope with 23 managed racks

    modelled

    67 kW, about 2%

    23 racks at about 119 kW draw about 2,733 kW against 2,800 kW.

  • Headroom at full energisation, 3,500 kW

    modelled

    1 rack without the runtime; 5 to 7 racks with it, beyond the 24 delivered

    25, 29 or 31 racks held. Hardware somebody still has to buy; count it once.

  • Cost of adding 560 kW of envelope

    modelled

    About GBP 5 million one-off

    The GBP 9,500,000 per MW of project capital assumed in the Ofgem July 2026 connections consultation.

  • Capital held under the proposed connection commitment

    modelled

    About GBP 133,000 to GBP 399,000 until energisation

    The range proposed in the Ofgem Curate consultation of 29 July 2026, applied to 560 kW.

  • Fleet earning now at ten times the scale

    modelled

    About 98%, with 35 of 40 waiting racks lit

    240 racks inside 28,000 kW, conservative reading. The whole-rack remainder shrinks with scale.

Declared inputs

What the arithmetic runs on.

Each input is stated with its basis. Change any of them and the figures above move with it.

  • Rack type

    NVIDIA GB300 NVL72: rack-scale, liquid-cooled, 72 accelerators and 36 Grace CPUs in one NVLink domain

    NVIDIA published configuration. Reader-supplied for any other rack.

  • Accelerators per rack

    72

    Same published configuration.

  • Rack draw at the rack input, nominal

    140 kW

    Published OEM specifications give 132 to 142 kW nominal. Reader-supplied.

  • Rack peak

    About 155 kW

    Same specifications. It decides the answer if the envelope is a plant rating.

  • Busway provisioning for transients

    About 192 kW

    Same specifications. It decides the answer if the envelope is a busway rating.

  • Accelerator share of rack draw

    72%, about 101 kW of the 140 kW

    Derived from the same specifications. Reader-supplied, and the largest lever in the model.

  • Upstream cascade factor

    1, no credit upstream of the die

    Default. You can change it.

  • Racks delivered and on site

    24, holding 1,728 accelerators

    Reader-supplied.

  • Envelope energised today

    2,800 kW of IT load at the rack input

    Reader-supplied, with its plane and whether it is contractual, metered or a plant rating.

  • Envelope at full energisation

    3,500 kW

    Reader-supplied. Used only for the headroom after energisation.

  • Gap to full energisation

    Illustrated at 8, 16 and 26 weeks

    Your own schedule.

  • Coefficient at the die

    21%

    Measured on NVIDIA H100 NVL. Fixed, not an input.

  • Operating mode

    Balanced

    The mode the coefficient was measured in, with throughput and P99 latency held.

  • Utilisation of newly lit racks

    70%, with the band run at 50%, 70% and 90%

    Assumed. The 50% end of the band allows for racks that take time to fill; your own ramp replaces it.

  • Rental anchor

    One published rack-scale figure; a band across four published lists

    Third-party lists read at source on 20 August 2026, converted to GBP at that day's reference exchange.

The working

The situation

Accelerators arrive on a date the buyer does not set. Power arrives later still. When the first lands ahead of the second, the operator holds a paid-for asset consuming its own earning window. Depreciation waits for the in-service date, so the loss shows on nobody's report. The earning window is fixed at the far end, so the gap costs days from the highest-earning part of the asset's life. Operators count that gap as dock-to-live, and this page counts in the same unit.

The fleet and the envelope

Twenty-four rack-scale, liquid-cooled racks are on site, 1,728 accelerators in all. Each is NVIDIA's published GB300 NVL72 configuration: 72 accelerators and 36 Grace CPUs in one NVLink domain. Nominal draw at the rack input is 140 kW, from published OEM specifications of 132 to 142 kW, with a peak of about 155 kW. The accelerators account for about 101 kW of that, a 72% share. That share is your field to set, and the largest lever in the model.

The envelope energised today is 2,800 kW of IT load at the rack input; the full envelope, when it lands, is 3,500 kW. Unmanaged, the fleet draws 3,360 kW, so the shortfall is 560 kW. The gap to full energisation is yours to supply and is illustrated at 8, 16 and 26 weeks. Our coefficient was measured on H100 NVL, so the GB300 rack stays modelled until a baseline run on it: one engine, calibrated per architecture.

From the die to the rack

Our coefficient sits at the accelerator die and your constraint sits at the rack input. The reduction at your rack is our die figure multiplied by your accelerator share. The upstream cascade factor stays at one, giving our own physics argument no credit. The conservative reading applies 21% to the 72% share: about 15% at the rack, a managed rack drawing about 119 kW instead of 140 kW. The stated basis reads the die figure as a floor on wall watts: 21% at the rack, about 111 kW. Both are modelled and neither travels alone.

How much of the fleet earns now

Without the runtime the 2,800 kW envelope holds 20 racks, 1,440 accelerators, exactly full with no headroom. On the conservative reading it holds 23 racks, 1,656 accelerators. On the stated basis it holds 25, capped at the 24 delivered. Three of the four waiting racks stop waiting on the conservative reading, 216 accelerators, and the fourth does not. On the stated basis all four do, 288 accelerators. The share of the fleet earning now moves from about 83% to about 96%, or to 100%, modelled. Plan against three racks; the fourth is what the validation is for.

Weeks, not watts

Every rack that stops waiting does so for the whole gap, so the recovered quantity is rack-weeks. What falls is fleet-average dock-to-live. At a 16-week gap, four racks wait without the runtime and one waits with it. Two weeks of dock-to-live come off every delivered rack and 48 rack-weeks come back, modelled. At 8 weeks the figures are one week and 24 rack-weeks; at 26 weeks, about three weeks and 78.

The connection date, the equipment delivery and the commissioning schedule stay exactly where they were. What moves is the date each admitted rack starts earning. It moves by software installation rather than by construction.

What the recovered weeks are worth

Every money input here is a third party's published figure, read at source on 20 August 2026. Across four published lists and utilisations of 50% to 90%, a waiting rack forgoes about GBP 2,500 to GBP 20,000 of contribution a day. At one published rack-scale figure and 70% utilisation, the anchor is about GBP 9,300. Three recovered racks over a 16-week gap is 336 rack-days: about GBP 3 million at the anchor, inside about GBP 850,000 to GBP 7 million, modelled.

The band is gross value at published list figures. To make it your figure, replace list with your realised revenue per accelerator-hour, take off the running cost of the newly lit racks (close to zero where the envelope is already contracted), and add any contractual remedies avoided on pre-sold capacity. Leave the depreciation charge out: the revenue is what would have paid it.

The alternatives, costed where they can be

Adding 560 kW of envelope is measured in months at best. The Ofgem July 2026 connections consultation assumes GBP 9,500,000 per MW of project capital. On that basis the work is about GBP 5 million one-off, modelled. The connection commitment proposed in the same consultation would hold about GBP 133,000 to GBP 399,000 of capital until energisation. None of it acts inside the gap. Temporary or behind-the-meter generation adds an envelope rather than changing what the work needs, so it composes with a runtime. Splitting across sites forks the clock, since each fragment arrives with its own energisation date. Slipping the date onto a customer moves the loss and can carry contractual remedies.

The bill, the reserve and the standing condition

The energy bill does not fall. Before, 20 racks draw 2,800 kW inside a 2,800 kW envelope. After, 23 racks draw about 2,733 kW, so the site draws about the same and does about 15% more work, modelled. The run gave up to +22% tokens per watt, derived, with throughput unchanged. That ratio is the same tokens for less energy; the extra output here is rack-count arithmetic. At full energisation the 3,500 kW envelope holds 29 to 31 managed racks against 25 unmanaged, 5 to 7 beyond the 24 delivered, modelled, counted once.

Racks energised by virtue of the reduction depend on it. Remove the software and the site is back over its limit, with a reserve of 67 kW against three racks of unmanaged draw. The runtime fails open to full performance on a component fault, which protects the workload and returns the racks to full draw, so the site plans for that event. The mitigation lives at the site: reserved headroom, an agreed curtailment right, or a commitment set far enough below the modelled figure to absorb a total failure.

What would change it

What moves the result, and how to check it on your own fleet.

The provisioning basis of the envelope moves the result most. If your 2,800 kW is a contractual or metered demand figure over a settlement interval, a sustained reduction relieves it and the arithmetic holds. If it is a transformer, breaker or busway rating, that plant is sized for peak and a sustained reduction does not relieve it. The document that sets the limit tells you which, so bring it. Then read your accelerator share from your rack specification or a metered rack. The answer stays at 23 racks for any share between about 62% and 79%. Last, the time-value figures assume accelerators that run until superseded, when the earning window is fixed at the far end. If yours run until they fail, those figures fall by about an order of magnitude, so say which when you bring your numbers.

Your own numbers

The same arithmetic, on your site.

Bring your interim envelope and the document that sets it, the racks on your dock and the date the rest of the power lands. We will run this arithmetic on your numbers and scope the validation that makes the figure yours.