How should a plant manage obsolete PLC and control system spare parts?
A spare PLC module is not useful merely because it is on a shelf. Firmware, hardware revisions, licensing, configuration files and communication compatibility can determine whether the part restores the process. Obsolescence management should connect the storeroom, controls engineers, cybersecurity and capital planning.
Start with the installed base
List controllers, I/O cards, network equipment, drives, HMIs and associated power supplies by asset, manufacturer, exact part number and hardware or firmware revision. Identify which equipment is in service, which is a spare, which has vendor support and which has a verified repair route. Confirm that the CMMS bill of materials matches what is physically installed.
Classify consequence and recoverability
A discontinued display for a noncritical local panel may have a workable alternative. A proprietary controller on a single production train may present an extended outage risk. Assess failure consequence, installed population, commonality, lead time, availability of tested substitutes and the time needed to restore the application and communications. Do not use issue history alone to justify removing a rare critical spare.
Qualify a spare before relying on it
- Identity: exact catalog number, revision, serial number and ownership.
- Condition: preservation, environmental storage, packaging and battery status where applicable.
- Compatibility: approved hardware, firmware, rack, network and software dependencies.
- Recovery: backed up configuration, licenses, credentials held securely and a documented restore method.
- Test: a controlled bench test or other approved acceptance evidence when feasible.
- Supply: reputable supplier, traceability, repair warranty and counterfeit risk screening.
Build a migration trigger, not a panic purchase
Set triggers such as end of OEM repair support, repeated unavailability of verified spares, security exposure without an approved mitigation, or a required operating change that the legacy system cannot support. Compare holding a qualified spare with staged migration, including engineering, downtime, validation, training and documentation costs. Use management of change where applicable, and do not substitute an untested module during a breakdown.
Example: an obsolete I/O card
A plant has three nominally identical I/O cards. A technician discovers that only one matches the installed rack firmware and the other two were purchased under an old revision. The team quarantines the incompatible cards, confirms the correct replacement, tests recovery in a safe environment and updates the equipment BOM. This converts apparent inventory into a verified recovery capability.
Keep ownership clear
Assign controls engineering responsibility for compatibility, the storeroom for preservation and inventory accuracy, and maintenance leadership for recovery priorities. Review high risk items at least during annual asset strategy and capital planning. Record decisions against the asset so the next team does not repeat the research.
Explore KANE consulting
Discuss practical maintenance and reliability improvements for your facility.
Request a consultation →Related answers: critical spare parts selection · equipment bom cmms
Technical references
DOE Operations and Maintenance Best Practices · NIST Roadmap for Digital Thread Supply Chain Resilience