How to Modernise a Legacy Control System Without Stopping Production

Signs it is time to migrate

• The manufacturer has discontinued the controllers or spare parts are only available second-hand.
• Programming tools no longer run on supported operating systems.
• Unplanned stoppages are rising and troubleshooting depends on one or two people.
• You cannot connect to modern systems for data collection, remote support or Industry 4.0 analytics.
• Safety or cyber security requirements can no longer be met with the existing equipment.

Phase 1: Audit and document what exists

Start with a thorough audit: I/O lists, electrical drawings, existing programs, interlocks, network topology and how operators really use the system. Documentation is often out of date, so verify against the plant. Capture the hidden logic, such as workarounds and manual overrides, because the new system must either preserve or consciously replace them.

This is where independent engineering pays off. On the Tata Steel project in the Netherlands, a comprehensive automation solution had to be integrated with an existing production line, and the first phase was system analysis and design. Read the full Tata Steel automation implementation case study.

Phase 2: Choose a migration strategy

There are three common approaches:

• Rip and replace: swap the whole system during a planned shutdown. Fastest, but highest risk, and only practical for small or modular plants.
• Phased migration: replace one area, line or unit at a time, with the old and new systems co-existing through gateways. Best balance for most plants.
• Wrap and extend: keep the legacy controllers for now, but add modern I/O gateways, HMIs and SCADA on top to gain visibility while you plan the replacement.

Protocol gateways and managed industrial networks make co-existence possible, and distributed I/O reduces the amount of re-cabling needed in the field.

Phase 3: Design, build and test offline

Develop and test the new control logic away from the live plant wherever possible. Simulation and emulation let engineers exercise sequences and alarm responses before they touch real equipment. Then run a Factory Acceptance Test (FAT) with the customer, using the actual hardware, to prove the system against the functional specification.

A good example is our work for Atlas Copco's Oil-Free Air division, where a new test control system replaced legacy SCADA-only control with deterministic PLC orchestration. See the Atlas Copco PLC automation project for how the architecture was approached.

Phase 4: Commission in stages and run in parallel

Cutover should be rehearsed. Where possible, run the new system in shadow mode, reading the same inputs and comparing its outputs to the old system before it takes control. Schedule switchovers during planned low-demand windows, and prepare a rollback procedure that everyone understands.

Site Acceptance Testing (SAT) then confirms the system on site under real conditions. Our oil refinery process automation upgrade is an example of control and safety systems delivered without disruption to live operations, which is the standard we apply to every migration.

Phase 5: Train, hand over and support

A migration is not finished at cutover. Operators and maintenance staff need training, documentation must be current, and the first weeks need close support to resolve teething issues. Our training and certification and maintenance and support services exist for this reason, so the knowledge stays with your people.

Budgeting and scheduling a migration

The cost of a migration is driven by I/O count, the amount of logic to rewrite, the number of screens, cabinet and cabling changes, and the testing and commissioning effort. Shutdown windows are usually the scarcest resource: schedule them first, then build the project plan backwards from them. Allow contingency for surprises found during the audit, because older plants nearly always contain undocumented modifications.

Managing risk during cutover

• Prepare a detailed cutover plan with step-by-step actions, owners and time estimates.
• Rehearse in the workshop or in simulation before touching the live plant.
• Agree go and no-go criteria in advance, with a tested rollback procedure.
• Keep experienced operators and maintenance staff involved from the start.
• Have engineers and key spares on site during the first days of operation.

Documentation and handover deliverables

A good migration leaves the plant better documented than it was. Expect updated electrical drawings, I/O lists, network diagrams, functional descriptions, tested backups of programs and configurations, and operator and maintenance manuals. Our project management approach tracks these deliverables from the first phase through final handover.

Common mistakes to avoid

• Copying old logic line by line instead of redesigning it for modern capabilities.
• Skipping the audit and discovering undocumented interlocks during commissioning.
• Underestimating cabling, power and panel-modification work.
• Ignoring cyber security until after go-live; see our guide to OT cyber security and IEC 62443.
• Having no single owner for the project, which is why we offer dedicated project management.

If you are weighing up an upgrade, start by reading how PLC, DCS and SCADA differ, then talk to our engineers about the right migration path for your plant.

Frequently asked questions

How long does a control system migration take?

It depends on size and complexity. A single machine can be migrated in weeks, while a multi-unit plant is typically phased over months. A thorough audit and design phase usually determines how smoothly the rest goes.

Can we migrate without any shutdown?

Often most of the work can be done online, but the final cutover of each section usually needs a short planned stop. Phased migration and parallel running keep those stops short.

Should we keep the same PLC brand?

Not necessarily. Staying with one vendor can reduce re-training, but migration is also a chance to standardise on platforms with better support, connectivity and lifecycle. Evaluate availability, skills and total cost.