Upgrading to System Platform 2020

Upgrading to System Platform 2020

AVEVA Wonderware System Platform 2020 was released for download April 27th 2020 in the Knowledge and Support Center.

The following is a guide through the upgrade from System Platform 2017 Update 3 to System Platform 2020.

Remember to backup all data before performing a upgrade.

Supported System Platform Versions for Product Upgrade. You can upgrade directly to System Platform 2020 from the following versions:

  • System Platform 2017 Update 3 SP1
  • System Platform 2017 Update 3
  • System Platform 2017 Update 2
  • System Platform 2017 Update 1
  • System Platform 2017
  • System Platform 2014 R2 SP1 with Patch 01 and/or Patch 02
  • System Platform 2014 R2 SP1

The setup scans the system for existing installations and give a list of the programs currently installed that will be affected by this upgrade.

My already installed System Platform 2017 with Application Server 2017 Update 3 SP1 17.3.100

As seen in the next screenshot, adding or removing components is not possible in the upgrade. Uninstall programs before or after the upgrade to remove features.

Down in the left corner there is a button called “View Install Guide” and it has a few interesting bulletins you need to pay attention to. Here are examples from the “Upgrading System Platform”chapter.

Previous versions that can be upgrade directly to System Platform 2020

One of the big changes is the new flex licensing system which works with universal credits that can be spend on all kinds of previously licensed products. So instead of buying specific licenses you can now move your license credits back and forth between which features you need.

Flex licensing is now a thing

The AVEVA System Monitor Manager is not installed automatically during the upgrade and it is necessary to use the modify work flow to add it after the upgrade is finished.

You have to install AVEVA System Monitor Manager manually

All running instances of ArchestrA IDE or other programs that connects to the System Platform have to be closed.

A list pf programs that needs to be closed is supplied

On step 8 you are reminded to make a backup of your data through the SMC Galaxy Database Manager, you can use this guide on how to backup your galaxy.

Always backup.

All deployed objects will stop to work once the ArchestrA services are stopped. It is also important to check the status of your deployed objects after the upgrade is complete.

The communication drivers for the OI Server is upgraded before everything else.

All ArchestrA, Historian and System Platform services have to be stopped and that is easily done by pressing the “Stop Services” button down in the left corner.

Stop all services before installation.

The pre-installation steps are all completed and the old System Platform is ready to be upgraded.

Ready to upgrade

All prerequisites are now installed first, then the program updates and last the configuration steps. The installation / upgrade takes around 45 minutes, so there is time for a cup of coffee.

Installation progress bar

When you return from the well-derserved coffee break, you will see this window, unless something goes wrong. It is now time to configure System Platform 2020.

Installation complete

It should not be required to change any settings if you are upgrading from System Platform 2017 Update 3. I did not have to change anything, but I did press the “Test Connection” button for all the options to test connectivity.

Configuration of license, historian and system monitor

The new System Monitor Manager even responds with connection successful. Everything is good and ready to go!

All connections tested

It is necessary to restart the system in order to get all the rights services to start up properly. Reboot the server.

Reboot the server, let us hope the server is not running any important tasks in other systems

Upon opening the System Platform IDE or ArchestrA IDE, you can select your previsouly existing galaxies but you will get a popup telling you that the galaxy is from a older version and needs to be migrated.

Migration of galaxy from 2017 to 2020

The migration is done by a automated galaxy .cab file backup which is then migrated to the new version and it restores the galaxy database from the migrated .cab file.

Galaxy migration part 1
Galaxy migration part 2

The whole galaxy migration process can be followed in the SMC Log Viewer as seen below.

SMC Log Viewer content from the galaxy migration process

The migrated galaxy can now be connect to through the ArchestrA IDE and from the About splash in Help we can see that the Build date is April 7th 2020, 20 days before it was released to customers. Version 20.0.000 and 5750.1213.3853.1

Galaxy migrated to System Platform 2020 and connected to in ArchestrA IDE

System Platform 2020 is now installed and migration of the galaxy is done.


Discover more from SCADA, PLC and Automation Engineering

Subscribe to get the latest posts sent to your email.

Leave a Reply

Your email address will not be published. Required fields are marked *