Conceptual equipment illustration.
A SCADA upgrade needs to preserve the operating functions and records the plant relies on, not simply display the old screens on new software. Inventory the platform, communications and retained data first. Then establish the supported upgrade path and a cutover test for the selected versions.
For machine retrofit and modernization, the SCADA change must be coordinated with controllers and the operating procedure.
Configuration and Runtime History Are Separate Assets
An engineering backup can contain screens, tags and scripts without containing the runtime archives. Siemens’ WinCC upgrade guidance makes this distinction: its Project Duplicator “Save as” route does not transfer runtime data, while a complete operator-station archive includes the relevant databases.
That is a specific WinCC example. For the actual platform, identify the backup and restore route for each asset:
| Asset | Cutover evidence |
|---|---|
| Engineering project | Restored screens, tags, recipes and scripts |
| Runtime history | Historical values can be queried over the required period |
| Alarm records | Prior events and current alarm behaviour are distinguishable |
| Users and permissions | Expected roles work without unintended access |
| External interfaces | The destination receives the correct data and status |
The HMI and SCADA integration scope covers those operating interfaces. Do not treat a successful screen import as a complete migration.
Test the Version Combination
Confirm compatibility of operating system, database, SCADA software, drivers and connected controller versions. Some products require intermediate upgrade steps. Use the manufacturer’s documented path for the installed release, including any intermediate migrations.
Check time zones and timestamps when querying migrated archives. A correct-looking value shifted to the wrong time can make a process event appear to have happened on another shift.
Coordinate controller changes with the PLC migration scope so that tag names, addresses and update behaviour remain consistent.
Rehearse the Cutover and Return Path
Restore into the proposed environment and test representative functions before the production change. Include unavailable controller communications, a missing database and alarm acknowledgement. Establish who determines when the system is ready to control or monitor the live process.
Keep the previous configuration and the rollback conditions explicit. A rollback also needs to explain what happens to records created after cutover; discarding or duplicating them changes the historical dataset.
Review access and network interfaces with the industrial cybersecurity guide. Contact Motionwell to discuss the operating functions and archives that the upgrade needs to preserve.