Obsolescence rarely announces itself. It appears as a quote that comes back no-bid, a control card that can only be sourced from brokers, a vendor acquisition that ends a support line, or a procurement specification that references standards two editions out of date. Individually these are annoyances. Collectively they are a reliability exposure with a compounding interest rate.
Make obsolescence visible before it is urgent
An obsolescence program starts with an unglamorous census: which components, platforms, and services the operation depends on, which of them are no longer manufactured or supported, and what the realistic sourcing path is for each. The output is a risk register with dates — end of support, last-time-buy windows, broker-only thresholds — that lets replacement be scheduled into outages and budgets instead of erupting between them.
Modernize against the operating need, not the catalog
Modernization decisions go wrong in both directions: sites that replace working equipment because a newer platform exists, and sites that nurse unsupportable systems years past the point where a failure is recoverable. The discipline is the same as any engineering decision — define what the operation actually requires (capability, reliability, support horizon, integration), and evaluate candidates against that requirement. A modernization justified by the risk register funds itself; one justified by a brochure rarely does.
Procurement specifications for the industry you operate in now
Specifications age as fast as equipment. Documents that still call for withdrawn standards, obsolete coatings, discontinued instrument protocols, or materials the supply chain no longer stocks force suppliers to either take exception or quote fiction. A periodic specification review — current code editions, current material availability, current vendor landscape, lessons from recent failures — is one of the cheapest reliability investments available, because every future purchase inherits it.
- Maintain a living obsolescence register with support dates and sourcing paths
- Tie last-time-buy and modernization decisions to outage and budget cycles
- Review procurement specifications against current standards and the actual supply chain
- Capture equipment knowledge before the people who hold it retire with it
Sites do not fail because equipment aged. They fail because the aging was nobody’s program.