A stopped production line rarely gives you time to research a discontinued controller family. When a CPU fails, the priority is to identify the exact unit, confirm what will work in the existing rack and get a replacement moving quickly. That is how to source legacy PLC CPUs without turning a single failed component into extended downtime.
Legacy PLC procurement is not simply a matter of matching a manufacturer name. A Siemens, Allen-Bradley, Mitsubishi, Schneider or Omron CPU may have several near-identical variants with different memory, communications, firmware, power requirements or supported I/O. The part number is the starting point, but it should be checked against the installed system before an order is placed.
Start with the exact CPU part number
The label on the installed CPU is the most useful piece of information in the sourcing process. Record the complete manufacturer part number, including every suffix, revision and series marking. A missing suffix can mean the difference between a direct replacement and a unit that will not communicate with the existing rack, remote I/O or programming software.
Take clear photographs of the front label, side label, rack position and connected communications ports before removing the failed part where possible. Also record the processor family, power supply reference, rack or base unit part number, installed I/O modules and any communications cards. This gives purchasing and engineering teams enough detail to assess alternatives if the exact CPU is unavailable.
For example, an Allen-Bradley processor may share a family name with another model but differ in memory capacity, network support or chassis compatibility. Similarly, a Siemens CPU reference may need its full order number and hardware version checked. Do not rely on an abbreviated description from an old maintenance spreadsheet if the physical label is available.
Confirm compatibility before you buy
A legacy CPU can look correct and still create problems at commissioning. Compatibility must cover the physical installation as well as the application running on the processor.
First, verify that the replacement fits the existing rack or base, uses the correct power arrangement and supports every connected I/O and communications module. Next, confirm that its firmware can run the backup program and works with the programming package available at site. In some cases, a newer revision is suitable; in others, a revision change can require software updates, conversion work or a planned shutdown.
The most common checks are straightforward:
- Exact manufacturer part number, suffix and hardware revision
- Rack, base unit, backplane and power supply compatibility
- Memory specification and installed memory card or battery requirements
- Network interfaces, protocol support and communications module compatibility
- Firmware level, programming software and application backup compatibility
Decide whether new and sealed or refurbished is right
Availability often determines the best route for a legacy part. New and sealed stock can be preferable for critical spares, particularly where a plant policy requires unused components or where the CPU includes consumable items that deteriorate with age. However, sealed does not automatically mean recently manufactured. It may be long-held surplus stock, so condition, packaging and storage history still matter.
Refurbished CPUs are often the practical option for discontinued families. They can reduce cost and make an otherwise unavailable replacement obtainable quickly. The key question is how the condition has been assessed. A procurement team should ask whether the unit has been inspected, tested and checked for physical damage, and whether it is supplied with the accessories required for installation.
There is no universal answer. For a line with a single point of failure and no spare processor, the fastest tested match may be the right decision. For a planned overhaul, you may have time to source a new and sealed unit or assess a wider controls upgrade. Treat the condition label as a purchasing fact, not a vague marketing term: new and sealed, used, and refurbished should be clearly distinguished.
Source from a supplier that works by part number
Legacy automation purchasing works best when the enquiry is specific. Provide the full part number, required quantity, condition preference and deadline. State whether you need a direct replacement only or would consider a compatible revision after technical confirmation.
An independent multi-brand supplier can be particularly useful when OEM channels have declared a product obsolete, lead times are uncertain or the requirement covers several control platforms. Automation Planet UK LTD sources PLC hardware across major OEM ecosystems and lists equipment by part number, helping maintenance and procurement teams move from identification to availability checks quickly.
Ask direct questions before placing an order. Is the item physically in stock? Is it new and sealed or refurbished? Has the exact unit been tested where applicable? What is the dispatch timing? Are photos of the actual item available for older or high-value references? Clear answers matter more than broad claims about availability.
Be equally careful with marketplace listings that use stock images or generic family descriptions. A low price is not useful if the supplier cannot verify the full reference, cannot state the item condition or cannot confirm when it will leave their facility. For a failed production asset, certainty usually has more value than a small saving.
Build a controlled substitution process
When the original CPU cannot be found, engineering may consider a substitution. This is not a procurement-only decision. A replacement from the same family can still need a different rack, revised wiring, new programming software or program conversion. Moving to a current platform may be sensible, but it is a migration project rather than an emergency swap.
Set a clear threshold for escalation. A same-part-number replacement with confirmed condition can normally follow the standard breakdown process. A revision change should be reviewed against the existing application and hardware. A different CPU family should trigger a documented engineering assessment covering programme conversion, I/O compatibility, networks, safety functions, validation and commissioning time.
This distinction prevents a common mistake: buying a technically capable modern controller during an outage, then discovering that the line cannot return to service without substantial re-engineering.
Use the failure to improve your spares position
Once the immediate replacement is secured, review whether the failed CPU should become a stocked spare requirement. The right level of stock depends on failure history, production impact, sourcing difficulty and the number of machines using the same platform. A processor that is cheap but available only from the secondary market may deserve more attention than a higher-value current product with dependable manufacturer supply.
Keep a controlled spares register with exact part numbers, installed locations, tested backup files, firmware information and the location of any memory cards, batteries or cables. Review it after changes to the machine. A part-number record that was accurate five years ago may no longer reflect a modified control panel.
Surplus stock can also help fund the programme. Unused automation modules, CPUs and drives held after upgrades may have value to another plant still running that platform. Selling excess inventory through a specialist buyer clears storage while returning hard-to-find equipment to the market.
Keep the replacement process ready for the next fault
The fastest legacy CPU purchase is usually the one prepared before the fault occurs. Keep full references in the asset record, maintain current programme backups, define acceptable condition options and know which parts require engineering sign-off. When the next processor fails, your team can focus on restoring production rather than trying to identify a controller from a faded label under pressure.