The Controller Still Works. That Is the Problem.
A PLC installed twenty years ago is very likely still running the line it was bought for. Programmable controllers are extraordinarily reliable, and that reliability is exactly why obsolescence catches plants out. Nothing has gone wrong, so nothing is planned. Then a processor fails, the replacement is no longer made, the only spare on the market is second hand at several times the old price, and a migration that should have taken a planned week is attempted in a panic.
Two of the most widely installed controller families in Australian food and beverage plants have reached that point. This guide sets out where they stand and how to plan a migration on your own terms.
Where the Common Platforms Stand
Siemens S7-300 and ET 200M. Siemens has been phasing out this family in stages. The phase designated P.M400 ran to September 2025. From 1 October 2025 the family moved to the stage designated P.M410, under which more than 267 assemblies became available as spare parts only, with significant increases in spare part prices. The migration path Siemens provides is from the S7-300 processor to the S7-1500, from ET 200M remote input and output stations to ET 200MP, and for analogue peripherals to ET 200SP.
Allen-Bradley SLC 500. Rockwell Automation announced a discontinued date of 31 March 2024 for all remaining SLC 500 controllers. The migration path is to the CompactLogix and ControlLogix families, and support is available for the legacy networks used with SLC 500 systems, including DH+, DH485 and Remote I/O, so that a transition can be phased.
Both platforms were the standard choice for packaged machinery for many years. If your plant has fillers, labellers, palletisers or process skids that have been in service for a decade or more, it may well have one or both.
What Obsolete Actually Means
Manufacturers do not switch products off overnight. A platform typically moves from active sale, to a mature stage where it is still sold but not recommended for new designs, to spare parts only, and finally to no support. The stages are announced years ahead.
The risk changes at each one. While a product is on active sale a failure is an inconvenience. At the spare parts only stage, prices rise and lead times become unpredictable. After support ends, you depend on your own stock, on the second hand market and on the shrinking number of people who know the platform.
The hardware is only part of it. Programming software for old platforms may not run on current operating systems. The engineers who wrote and understand the code retire. HMIs, drives and networks connected to the controller age at the same time.
Five Risks of Waiting
A long outage. If a processor fails with no spare, the line is down until one is found.
Rising costs. Spare part prices increase as supply shrinks.
Questionable parts. Second hand and grey market components come with no history and no warranty.
Lost knowledge. The longer a system runs untouched, the fewer people understand it and the less likely its documentation matches what is installed.
No choice of timing. A forced migration happens when the hardware fails, not when production can spare the line.
Start With an Inventory
You cannot plan for what you have not listed. For every controller on site, record the platform and model, the firmware version, the input and output modules, the networks it uses, the HMI and drives connected to it, the software and version needed to program it, where the current program backup is and when it was last verified, and what spares you hold.
Plants are routinely surprised by this exercise. It turns up controllers nobody knew were there, backups that do not match the running program and software licences that have lapsed.
Rank by Risk
Not everything needs migrating at once. Score each controller on two questions: how likely is a failure to be unrecoverable, and how much does that machine matter?
A controller on the main filler with no spare processor and no verified backup goes to the top of the list. A controller on a secondary conveyor with two spares on the shelf can wait. The ranking gives you a migration sequence and a case for the budget.
Buy Time Sensibly
For controllers that are not first in line, a bridging strategy reduces risk while the migration is planned. Buy critical spares now, from the manufacturer, while they are still supplied. Take and verify a backup of every program, and store copies off site. Keep a computer with the programming software in working order. Hardware removed in the first migrations can be kept as spares for the systems still waiting.
Bridging is a way to control the timetable. It is not a substitute for migrating.
Choosing a Migration Approach
Phased, input and output first or processor first. Both major manufacturers offer ways to replace part of a system while keeping the rest. A new processor can be connected to existing input and output racks through adaptors or legacy networks, or the reverse. This spreads cost and limits each outage, at the price of running a hybrid system for a period.
Like for like conversion. The program is converted to the new platform using the manufacturer’s tools and then corrected by hand. It is the fastest route and it preserves familiar behaviour. It also carries forward twenty years of patches and workarounds, and converted code is often hard to read.
Rewrite. The control is written afresh on the new platform to current standards. It takes longer and needs a clear description of what the machine is supposed to do. The result is cleaner, better documented and makes use of what the new hardware can do, such as better diagnostics.
The right choice depends on the machine. A simple conveyor system converts well. A complex filler with years of accumulated modifications is often better rewritten.
What Else Changes
A controller migration rarely stays confined to the controller. Old HMIs often cannot communicate with a new processor and need replacing. Networks may need to move to industrial Ethernet. Drives and instruments on legacy networks need gateways or replacement. Safety functions need to be assessed, and a migration is a natural moment to bring machine safety up to current expectations.
Scope these at the start. The projects that overrun are the ones that discovered the HMI problem during commissioning.
Testing and Cutover
The outage is the expensive part, so everything possible is done before it. The new program is tested against a simulation of the machine. The new panel or backplane is assembled and tested in the workshop. Every input and output is mapped and checked against the drawings. A cutover plan sets out each step, who does it and how long it takes.
Cutover is scheduled into a planned shutdown. Old hardware is removed in a way that allows it to be reinstated if something goes badly wrong. Each input and output is checked at the device. The machine is run dry, then with water or empty containers, then with product. Someone who knows the new system stays on site through the first production shifts.
Afterwards the drawings are updated, the program is backed up, the maintenance team is trained and the spares list is rewritten.
Where BevTech Fits
BevTech is a family owned engineering business in Richlands, Brisbane, with more than 25 years in beverage and FMCG manufacturing. We work on both Allen Bradley and Siemens platforms, and we have delivered new control systems on the current Siemens generation, including an S7-1500 controlling glycol refrigeration for beer tank temperatures and an S7-1200 running a hot water rinse process on a can seamer. Our automation engineers, industrial electricians and TUV certified functional safety engineers plan and carry out migrations together, with electrical drawings produced in house and cutovers scheduled into shutdowns.
If you have controllers on your site that are no longer made, use the contact form at bevtech.com.au/contact and we can start with the inventory.
Product lifecycle dates in this article are those published by the manufacturers, current as at October 2026. Confirm the status of your specific part numbers with the manufacturer or its distributor.











