Legacy SCADA to WinCC Unified Migration
Old SCADA nodes on unsupported operating systems are the quietest risk in a plant and the hardest to justify replacing — until IT disconnects them or the machine dies. We migrate tags, screens, alarms, history and reports onto a supportable platform, without losing what the plant has recorded.
Discuss a SCADA Migration WhatsApp Our EngineersWhen a SCADA Becomes the Risk
The symptoms are consistent: the SCADA runs on an operating system that no longer receives patches, IT wants it off the network, the licence dongle is irreplaceable, the project file exists in one version on one machine, and nobody can add a tag without calling the person who built it. The plant runs fine — until the PC fails, and then production is blind.
Migration is not only a version upgrade. It is the opportunity to fix the alarm flood, the screen hierarchy nobody navigates and the reports that are typed into a spreadsheet every morning because the SCADA cannot produce them.
What the Migration Covers
Tag database rebuild against the PLC, with naming brought to a standard. Screen hierarchy redesigned for how the plant is actually operated, not how it was drawn. Alarm rationalisation — priorities, grouping, suppression during start-up and shutdown — so alarms mean something again. Historian and archive migration so the plant keeps its history. Reports and shift logs. Redundancy where the process justifies it. User access, roles and audit trail. Client, panel and mobile views where they earn their place.
Keeping the History
Plant history is worth keeping and is usually the part of the migration that gets dropped for time. We export the existing archives, map the tags to the new structure and load them, so trends cross the migration date instead of restarting at it. Where the legacy system stores data in a closed format, we say so at survey stage rather than discovering it during the cutover.
Running It Without Stopping the Plant
A SCADA migration is friendlier than a PLC migration: the new system can usually be built and run in parallel, reading the same PLCs, while the old one stays in service. Operators use both during a proving period, and the old node is retired only after a full production cycle on the new one. Where the PLC also has to change, we sequence the two so that neither is commissioned blind.
After the Migration
Annual maintenance, programme backup and version control, Siemens spares supply, and remote PLC and SCADA troubleshooting so that most faults are diagnosed before an engineer travels. ATMAN Group is a project, service and spare-parts provider; we are not an authorised Siemens channel.
Discuss a SCADA Migration
Tell us the SCADA in use, its version, the PLCs behind it and roughly how many tags, and we will come back with a method and an indicative budget.
Frequently Asked Questions
Can WinCC Unified read PLCs that are not Siemens?
Yes, through standard protocols and OPC UA, so a SCADA migration does not force a PLC migration. Plants often migrate the SCADA first and the PLCs later, in that order, for exactly this reason.
Will we lose our historical data?
Not normally. We export the archives, map them to the new tag structure and load them so trends run across the migration date. Where the legacy system stores data in a closed format we tell you at survey stage.
Can the old and new SCADA run in parallel?
Yes, and we prefer it. The new system is built and proved against the live plant while the old one stays in service, and the old node is retired only after a full production cycle on the new one.
Do you handle redundancy and remote clients?
Yes. Server redundancy where the process justifies it, plus web and panel clients with role-based access, are part of the scope where you want them.
Do you work on makes other than Siemens?
Yes. Siemens is our core platform and our deepest expertise — S7-1200 and S7-1500, legacy S7-300 and S7-400, TIA Portal, STEP 7, WinCC and WinCC Unified. We also program, modify, troubleshoot and upgrade Allen-Bradley, Mitsubishi, Delta and other major makes, and we handle migration from any make to Siemens or within the same make.
Do you supply the panels as well?
Yes. Panel engineering, supply and commissioning are part of our scope — control philosophy, GA and wiring drawings, component selection, testing and site commissioning — so the panel, the programme and the field instrumentation are answerable to one team.