Asset Decommissioning and Salvage Runbook¶
Procedural runbook — instantiates Defensible Boundary Retreat
Retires, salvages, or safely quarantines what is left behind and books the surviving obligations, so the abandoned position stops silently consuming resources or leaking liability.
Retreat is only half-finished when the people and functions have moved; the old position is still there, full of assets and obligations that do not disappear because attention did. Asset Decommissioning and Salvage Runbook is the step-by-step procedure for winding that down. Its defining move is to treat the vacated position as worked inventory rather than dead weight: every asset is triaged into salvage-and-reuse, sale, safe disposal, or quarantine, and every surviving obligation — a lease, a warranty, an environmental liability, a decommissioning bond — is written into a register with an owner and an end date. It governs what remains behind, not the move of the living functions and not the fate of displaced people; those are its siblings' work.
Example¶
A utility is retiring a decommissioned coal-fired power station after its generation has been shifted elsewhere. Walking away is not an option: the site holds tens of millions of dollars of salvageable copper, steel, and turbine components, plus coal-ash ponds and fuel-handling systems that are an active environmental liability. The runbook works the site methodically. High-value recoverables are catalogued and routed to reuse or sale first — the generator step-up transformers to a sister plant, the copper windings and structural steel to scrap markets — funding part of the teardown. Hazardous systems are isolated and disposed of to code, in an order that keeps the site safe as it empties.
What cannot be resolved at teardown goes into the residual-obligation register: the capped ash pond with a 30-year groundwater-monitoring commitment, the land-remediation bond that must stay posted until the site is certified clean, the demolition contractor's warranty. Each line gets a named owner and a review date, so the "closed" plant does not quietly reappear years later as an un-owned liability nobody budgeted for. The old position stops costing money and starts, where possible, returning some.
How it works¶
- Triage before you touch. Every asset is first classified — reuse, resell, recycle, dispose, or quarantine-in-place — so teardown follows a value-and-safety order rather than whatever is easiest to reach.
- Salvage funds the retreat. Recoverable value is harvested early and deliberately, offsetting decommissioning cost and reducing the stranded-asset write-off the retreat would otherwise book.
- Sequence for safety as the site empties. Hazardous and load-bearing systems are retired in a dependency order that keeps the shrinking site safe to work in, not left for last.
- Every survivor gets an owner and an expiry. Obligations that outlive the teardown — monitoring, bonds, warranties, latent liabilities — are entered in a register with an accountable owner and a review date, so nothing becomes invisible simply because the position is "closed."
Tuning parameters¶
- Salvage-depth threshold — how much recoverable value justifies the labor to extract it. Aggressive salvage maximizes recovery but slows teardown and can expose workers to more hazard; light salvage is fast but writes off more.
- Disposal standard — minimum-compliance versus best-practice remediation. Higher standards cut latent liability and reputational risk but cost more up front.
- Quarantine vs. full removal — cap-and-monitor a hazard in place, or fully remove it. In-place quarantine is cheaper now but leaves a long-tail obligation on the register.
- Register granularity — one line per obligation class or itemized per asset. Fine granularity prevents orphaned liabilities but is heavier to maintain.
- Obligation review cadence — how often the residual register is revisited. Frequent review catches lapsing bonds and monitoring gaps but is standing overhead.
When it helps, and when it misleads¶
Its strength is that it stops the archetype's zombie legacy position — the vacated site, system, or contract that keeps consuming budget, attention, and risk long after everyone believes it is closed — and it recovers value that would otherwise be written off as stranded. Sound practice mirrors the accounting discipline of an asset retirement obligation: the liability of eventually retiring a long-lived asset is recognized and funded up front rather than sprung as a surprise at the end.[n1]
It misleads when salvage economics quietly override safety or obligation, or when the register is treated as paperwork. The classic misuse is burden displacement: the assets worth money are stripped and sold, while the un-monetizable liabilities — the contaminated ground, the monitoring commitment, the un-transferred lease — are left off the register to become someone else's problem, often a future maintainer or the receiving community. A runbook optimized only for recovery becomes a mechanism for externalizing harm. The guarding discipline is to book every surviving obligation with an owner and funding before declaring the position closed, and to treat the register, not the scrap check, as the definition of "done."
How it implements the components¶
Asset Decommissioning and Salvage Runbook realizes the left-behind machinery of the archetype — what happens to the vacated position:
salvage_and_reuse_plan— it triages, harvests, and routes recoverable assets to reuse, resale, recycling, or safe disposal, turning stranded value into offset and reducing the write-off.residual_obligation_register— it records every liability that outlives the teardown — leases, bonds, warranties, monitoring commitments — with an accountable owner and an expiry, so the closed position cannot silently keep costing or leaking.
It does not sequence the move of the still-living functions (transition_pathway — see Phased Relocation Plan) or protect the people displaced by the retreat (Retreat Compensation and Continuity Package); its obligations are to assets and liabilities, not to persons.
Related¶
- Instantiates: Defensible Boundary Retreat — this runbook is the residual-management core that closes out the old position cleanly.
- Consumes: Phased Relocation Plan sequences the withdrawal that frees each asset for decommissioning; the runbook acts on a position only once its live functions have moved off it.
- Sibling mechanisms: Managed Retreat Trigger Review · Receiving Boundary Readiness Assessment · Phased Relocation Plan · Retreat Compensation and Continuity Package · Hold-vs-Retreat Scenario Stress Test · Old-Position Sunset Clause · New Boundary Stabilization Review
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Retires, salvages, or safely quarantines what is left behind and books the surviving obligations, so the abandoned position stops silently consuming resources or leaking liability, making its operative form an enacted repeatable sequence of actions, handoffs, or states.
Independent corroboration: The frozen evidence defines Asset Decommissioning and Salvage Runbook as 'Retires, salvages, or safely quarantines what is left behind and books the surviving obligations, so the abandoned position stops silently consuming resources or leaking liability', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Asset lifecycle and decommissioning engineering provide ordered shutdown, salvage, isolation, disposal, and long-horizon site obligations.
Related originating lineages:
- Accounting & Auditing — Asset-retirement obligations book future wind-down costs and owners.
- Environmental Science & Climate Studies — Remediation and monitoring obligations persist after closure.
- Logistics & Supply Chain Management — Reverse logistics routes reusable and saleable components.
Review resolution: Decommissioning engineering is the agreed primary. Asset-retirement accounting, remediation obligations, and reverse logistics materially shape the runbook's residual-liability and salvage routes; organizational management is generic execution context rather than a distinct origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] An asset retirement obligation is an accounting liability for the future cost of retiring a long-lived asset — decommissioning a plant, capping a well, remediating a site — recognized and funded over the asset's life rather than deferred to its end. It is the financial embodiment of "book the wind-down cost before it surprises you." ↩