Hardware Refresh, Depreciation Strategy, Decommissioning & ITAD

Refresh is where the depreciation debate from Chapter 1.8 stops being a line on a pro-forma and becomes a loading dock full of two-generations-old accelerators that are simultaneously a security liability, an environmental obligation, and — if you handle them right — a meaningful slice of recovered capital. Every earlier chapter in Part 14 keeps the asset alive; this one decides when to retire it, and what to do with the retired hardware. One question runs through the whole chapter, the same one that runs through AI-infrastructure finance: is a retired GPU an asset that cascades to a lower-value workload and earns its way to the book-life, or a depreciating liability you need off your floor before it costs more to keep than it is worth? The answer is workload- and site-specific, and getting it wrong in either direction is expensive.

This is refresh as execution, deliberately distinct from refresh as economics. The canonical home for the contested 2–3-year-bear-case-vs-4–6-year-estimate argument, the residual-value evidence, and the training-to-inference cascade as a depreciation defense is Chapter 1.8 — we do not re-litigate it here. What this chapter owns is the operational consequence: the refresh-trigger decision, the decommissioning-and-sanitization workflow, the ITAD/resale channel and the circular economy it feeds, and the migration discipline that keeps the factory earning while you swap its engines. The decommissioning of the facility itself — generators, BESS, coolant, the slab — is a separate lifecycle stage in Chapter 14.10; here we retire IT, not concrete.

There is no single refresh clock. There are four, they fire at different times, and the one you let dominate quietly sets your residual-value outcome. Most operators inherit a default ("refresh on the book schedule") without realizing it is a choice with downstream cost.

Calendar trigger. Refresh when the depreciation schedule says the asset is fully written down. Simple, auditable, and the implicit default for anyone who let accounting set the cadence. Its failure mode is that the silicon does not obey the ledger: a part can be economically dead two years before its book life ends, or perfectly productive two years after.

Efficiency trigger. Refresh when the next generation's perf-per-watt makes the incumbent uneconomic to run against the power it consumes. This is the trigger that matters most in a power-bound world: when megawatts are the scarce input, the question is not "does this GPU still work" but "is this the highest-value use of this megawatt." A Hopper-class rack drawing ~40 kW that a Blackwell rack at ~130 kW or a Rubin-class rack beyond that can out-earn per kW is a refresh candidate even if it is fault-free, because the opportunity cost is measured in stranded interconnection capacity you cannot get back. → density trajectory in Chapter 14.7.

Failure-rate trigger. Refresh when the fleet slice crosses the wear-out knee of the bathtub curve and the annualized failure rate plus RMA logistics cost more in lost goodput than redeployment is worth. The spares and RMA machinery in Chapter 14.6 is what tells you where that knee is; refresh is the exit when sparing a generation stops paying.

Density-ramp trigger. Refresh to capture the revenue-per-MW step of a new generation — the same density-ramp logic that Chapter 1.1 treats as a scoping decision, now executed mid-life. This only works if the irreversible substrate (floor loading, water, electrical headroom) was reserved for it; a hall scoped for 40 kW air cannot absorb a 130 kW liquid generation, and the refresh becomes a rebuild.

The retired-asset workload cascade is the mechanism that, if it holds, stretches economic life toward book life — and refresh is where the cascade is either executed or revealed to be a story. A part retired from the current liquid-cooled tier does not have to leave the building. Frontier pre-training, test-time scaling, and agentic inference can all occupy that current tier; retired parts can move only to workloads whose performance and power envelopes they still meet — such as smaller post-training or fine-tuning, latency-relaxed enterprise inference, batch, or internal work — and earn revenue there. Each step down relaxes the requirement the part can no longer meet (top-end perf-per-watt, the largest scale-up domain) and exploits what it still does well (raw memory bandwidth, adequate FLOPS for a smaller model).

The catch is that the cascade is finite and power-gated. There is only so much lower-tier demand, and in a power-bound site every cascaded part is occupying a megawatt that a newer part could use more profitably. So the real refresh decision per part is a three-way: redeploy it down the cascade (if you have the lower-tier demand and the megawatt is not the binding constraint), resell it into the secondary market (if the residual price beats the cascade value net of the power it would consume), or retire/shred it (if security obligations forbid resale or the part is genuinely uneconomic to run). The cascade defense of the long book life is only honest if a real, liquid resale market exists to absorb the parts that do not cascade internally — which is exactly the secondary-market-depth question flagged as load-bearing in Chapter 1.8.

Decommissioning an IT asset at scale is a chain-of-custody discipline, not a teardown. The workflow is roughly invariant across operators, and skipping a step is how a retired GPU becomes a data-breach headline or a stranded-capital line. The sequence: de-provision (drain workloads, remove from the scheduler and fabric, update the CMDB/DCIM asset record); power down and physically extract (de-cable, drain liquid loops on DLC racks, palletize); sanitize all data-bearing media using the approved NIST SP 800-88 Rev. 2 method, then verify execution, validate the result and retain a serial-linked certificate per asset; account and tag every serial through a chain-of-custody manifest; route each part to redeploy, resale, or destruction; and document the disposition for audit, environmental compliance, and — increasingly — embodied-carbon and Scope 3 reporting. The asset-record discipline is the spine of all of it: an untracked serial is an unsanitized serial and an unrecoverable dollar.

IT Asset Disposition is the industrialized channel that turns a retired part into either recovered capital or certified e-waste. The 2026 reality is that the compressed refresh cadence — accelerator generations now landing on a roughly annual rhythm (GB200 → GB300 → VR200 → Rubin Ultra Kyber) against the legacy 5–7-year enterprise cycle — can expand secondary-market supply when owners actually retire equipment, creating opportunities for smaller inference buyers and price risk when that supply outruns qualified demand; product launches alone do not establish those retirements. The lifecycle-economics lever that practitioners actually pull is resale velocity: obtain dated executable bids per SKU and track realized value net of fees, freight, sanitization cost, warranty state, and export eligibility as each new generation resets the market. An expiring executable bid can make a dock delay expensive; deliberate holding wins when retained contribution or rollback/repair option value exceeds carrying cost and the sale alternative.

Vendor selection is a compliance decision with teeth. The certifications that matter — R2v3 and e-Stewards for responsible recycling and chain-of-custody, ISO 14001 for environmental management, and increasingly NAID AAA for data destruction — help qualify the provider and its audited scope; the per-serial custody record, verified execution, validation decision and disposition receipt prove what happened to a particular asset. A provider certificate alone does not prove that the part was sanitized or destroyed rather than quietly resold. Skip certified ITAD and the downside is concrete: a tracked serial surfacing on the secondary market with recoverable tenant data on it, or an e-waste-dumping liability under tightening jurisdictional rules. The circular-economy framing — refurbish, reuse, recover materials, certified-destroy only as last resort — is also where refresh meets the embodied-carbon argument: a part kept in service one more cascade rung is embodied carbon you do not have to re-manufacture. → embodied carbon and circularity in Chapter 15.6.

On a live campus, refresh is a migration — one that must protect goodput and the power envelope while it happens, rather than fitting into a single maintenance window. The cost the swap strands is revenue: every megawatt taken offline to receive the new generation is a megawatt not earning against a depreciation clock that is still running. The dominant pattern is therefore rolling, hall-by-hall (or row-by-row) migration: drain and de-provision one fault domain, swap it, re-commission it, and only then move to the next — so the cluster never loses more than one domain's worth of capacity, and the new generation is validated against the live workload before the old generation is fully retired. The alternative — a forklift cut-over of a whole hall at once — is faster on paper but strands the entire hall's revenue during the transition and concentrates commissioning risk into a single window, which is exactly the high-risk density-step-up that re-commissioning discipline exists to de-risk.

The power envelope is the constraint that makes this delicate. A denser successor generation does not just need more total megawatts; during the overlap window you may be running both generations, and the facility power and cooling plant must absorb the transient. The migration plan and the capacity/power plan are therefore the same plan: the order in which you swap halls is dictated by where you have stranded power headroom to land the denser part, and a refresh executed without that headroom reserved becomes a rebuild of the power chain, not a swap of the silicon. The re-commissioning required to accept the new density step follows the changed thermal, structural, power and control dependencies, and it is owned by the continuous/re-commissioning discipline in Chapter 14.14. → capacity and power management in Chapter 14.7; risk-based density-step retesting is treated in Chapter 14.14.

Trace. Cascade value = internal contribution + later net sale − incremental migration/holding cost = about $9k per asset from the declared inputs. Sell-now value is about $10k, so select sale after the custody, eligibility and sanitization gates: about $1k more per asset and immediate release of the old asset’s power and service burden. Do not count the original purchase price again; it is sunk for this short disposition comparison.

Flip. Solve contribution + later net sale − incremental cost = sell-now value: contribution must exceed about $4k over the three-month horizon for cascade to win, with all other assumptions fixed. A support or purge-validation failure overrides the financial ranking and returns the asset to HOLD or an approved destruction path. Method: incremental cash comparison, with NIST SP 800-88 Rev. 2 governing media-specific verification and validation. Chapter 1.8 owns buy/rent and earning-life economics; this chapter owns executing the selected cascade or disposition with a serial-linked receipt.