DC Escalation Calculator escalate your own base cost by the DC Build index — and see exactly which packages moved it

This escalates your number. We publish an input-price index (2018-01=100), not a turnkey $/MW quote — so the base cost is yours to supply, and the calculator applies the ratio between two months of the DC Build index, and optionally carries a rate you choose past the last print. Because the index is a fixed-weight Laspeyres aggregate, it is linear in its components: each row's contribution is weight × (component index change) ÷ the headline's base index — not the component's own base index (see the note above the bridge table). In the underlying numbers, the contributions sum to the headline escalation with no residual — but each row in the table is rounded to 2 decimal places for display, so the printed rows can land a few hundredths of a point away from the headline. The TOTAL row under the table adds up what's printed; Headline shows the real figure — the difference between them is that rounding, nothing more. Every month here is sampled on its last daily-grid day, not the first — "base month 2024-03" means 2024-03-31 — except the window's end, which stops at the index's latest observation (2026-10-02) and is therefore a partial month. Escalation is national — state parity multipliers on /datacenter are level multipliers (cost relative to the national average), not escalation rates; your base cost for a real site already embeds its location, so applying them here would count location twice. The measured leg above is history: it stops at the index's last print, and nothing past that print is asserted. The deliver by leg is not a forecast either — it carries forward a rate you choose from regimes that have actually occurred (the long-run average, the post-2008 downturn, the last three years, the latest twelve months, or the 2021–23 spike), each shown with the exact window it was measured over. Those windows measure to the last month every Build component actually reports a full print for — not to the partial month noted above — because only 2 of the 12 components (Copper wire & cable and Aluminum mill shapes, 8.5% of the index's weight) have moved since then; anchoring a rate on a 2-component move would misstate it as a basket-wide one. We do not predict which regime will obtain, and we publish no central path. The realized band underneath the table is a count of what happened across overlapping historical windows of the same length as yours, reported alongside the number of independent draws behind it — a small number, over a sample containing one downturn and one spike, best read as a range of precedents rather than a probability. Component sources and weights are documented on /datacenter. Index choice. The default is the live DC Build grid, whose trailing month carries a futures-proxy tail for copper and aluminium until the next PPI replaces it — so its latest month restates. Official prints only is the same Laspeyres basket on the agencies' own prints: every month is complete, and a month once published moves only when BLS revises its print. That is the basis to cite in a price-adjustment clause; its monthly series downloads as CSV on /datacenter. P80. The P80 line is the 80th percentile of the same realized windows as the band: carried over your forward leg, it is the allowance that would have covered four in five of the historical windows of your length — with the same small-sample caveat.