Legacy PLC migration in Australia is usually driven by support risk before it is driven by performance. A line can still be running, but spare parts may be thin, software access may depend on one old laptop, and recovery options may be getting narrower.
The best time to plan is while the site still has options on timing, staging, and cutover.
Signs it is time to start planning
Spare parts are getting thin
If a failed CPU or I/O card is now hard to source, the site is already exposed.
The software is fragile
One old laptop and one engineer who still knows the job is not a support strategy.
The plant needs new data or visibility
Older platforms often struggle once the site wants better reporting, alarms, or integration.
What to decide early
| Option | Best fit |
|---|---|
| Full replacement | Old hardware, old network, and poor supportability |
| Processor swap with retained I/O | Tight outages and healthy existing field side |
| Staged migration | Multi-line plants that cannot stop everything at once |
What to verify before the first shutdown
Migration checklist
- Physical I/O and comms paths checked on site.
- Third-party interfaces identified and tested in FAT scope.
- Cutover run sheet written with rollback rules.
- Post-start support locked in before the outage begins.
What this means
If one hardware failure would now create a sourcing or support problem, it is worth starting the migration plan before the site is forced into an outage. The cleaner jobs are usually the ones planned while there is still time to stage them.