Why old PLCs become a problem
Many Alberta plants, water systems and buildings still run on PLCs installed decades ago. They often work perfectly, right up until a power supply or CPU fails and the replacement part is discontinued, sold only on the used market, or weeks away.
The issue is rarely the logic. It is the hardware lifecycle: manufacturers move product lines from active to mature to discontinued, and support and spares dry up over time. Older programming software may also only run on old laptops and operating systems, which become hard to keep and hard to secure.
Signs it is time to plan
- The manufacturer has announced the hardware as discontinued or end of support.
- You are buying spares from surplus dealers, or cannot find them at all.
- Only one laptop, or one person, can connect to the PLC.
- There is no recent program backup, or nobody is sure which version is running.
- The HMI runs on an unsupported operating system.
- You want features the old system cannot provide, like remote monitoring or data logging.
None of these means you must replace everything this year. They mean you should have a plan, a budget and enough spares to bridge the gap until you can act on your own schedule.
A useful exercise is to ask: if the CPU failed tonight, how long would we be down, and what would that cost? If the honest answer is "days, and a lot", migration belongs in next year's capital plan, and critical spares belong on the shelf now.
Start with an audit and a backup
Before anyone talks about new hardware, capture what you have:
- Upload and save the current program from the running PLC, plus the HMI application.
- Build or verify the I/O list against the drawings and the actual wiring.
- Record network connections to drives, other controllers, SCADA and the BAS.
- Write down how operators actually use the system, including workarounds nobody documented.
This work is useful even if migration is years away. It reduces risk today and makes the eventual project faster and more accurate.
Choosing an approach
There are several ways to move to current hardware, and the right one depends on how much downtime you can accept, the condition of the panels and field wiring, and the budget.
| Approach | Good fit when | Trade-offs |
|---|---|---|
| Full replacement | Panels are old or crowded, wiring is poor, or the process is changing | Longest outage, most thorough result |
| Wiring conversion | Panels and field wiring are sound and downtime is precious | Depends on conversion products existing for your hardware |
| Remote I/O first, CPU later | You need to spread the cost and outage over several windows | Temporary hybrid systems need careful testing |
| Phased by area | Large sites with separable process areas | Two systems must coexist and communicate for a while |
Program conversion tools can translate much of the old logic to a new platform, but the result always needs review. Old programs often contain workarounds, unused code and timing assumptions that do not carry over cleanly.
Keeping the cutover short
The goal is to do almost everything before the shutdown. A good plan includes a factory acceptance test (FAT) of the new panel and program, simulated against the I/O list; a detailed cutover procedure with a rollback plan; and pre-built panels, cables and labels ready on site.
During the outage, the crew lands or connects the field wiring and runs loop checks on every point before restart. Operators should be involved in testing and trained on the new screens before the process goes back online.
Hold on to the removed hardware and the last program backup until the new system has run through a full season. In Alberta that means at least one winter for anything weather-related.
What to ask for in the contract
- Unlocked, commented program files and HMI application, delivered to the owner
- As-built drawings and an updated I/O list
- FAT and site acceptance test (SAT) records
- Signed loop check sheets
- Operator training and a short plain-language functional description
- Passwords and licence details in the owner's name
Our controls migration team handles audits, design, panel builds through our control panels service, and cutover. See PLC basics for owners if you are new to the terminology.
Common questions
Can we migrate without any shutdown at all?
Sometimes, with redundant equipment or a process that can run in manual for a period. More often the aim is a short, planned outage at a time that suits you.
Will the new system look and work the same for operators?
It can, if that is the goal. Many owners take the chance to improve screens and alarms, but changes should be agreed with operators before the cutover.
Do we need an engineer?
It depends on the scope. Changes to safety functions, hazardous location equipment or process design typically need engineering review. Simple like-for-like hardware swaps may not, but permits and your own policies still apply.
How far ahead should we plan?
Ideally as soon as your hardware is announced as discontinued. Long-lead items like panels and some I/O can take months, and the best shutdown windows are usually booked well in advance.
Codes and permit rules change and every building is different. For work on your system, talk to a licensed electrician and your local permit authority.