Upgrade path

The upgrade path to get to the version you want may include upgrading to other versions first.

When you perform an online upgrade to the latest version, the Accept encrypted and non-encrypted connections (mixed mode) setting is on by default on the configurator's Encryption page. You can clear this option prior to performing the upgrade if you want to use unencrypted communications. You can also configure your system to use encryption after the upgrade process is complete.

Upgrade path requirements based on method

Offline upgrade: upgrade your project directly into the latest version from v7.20 SR1 and after.
Online upgrade: runtime and historical data are migrated and upgraded, you need to follow an upgrade path that depends on your starting version.

Upgrade path requirements and notes based on version

v8.0 or later: When doing an online upgrade, check that any pre-7.20 Alarm Save files are removed from the latest project folders. For example, <project_cluster>_ALMSAVE.DAT and <project_cluster>_ALMINDEXSAVE.DAT.
v7.30 or v7.30 SR1: Restore your project to v7.40. Compile and run your project to restore and convert your historic alarm data. If the existing project uses the ES_StartAdvOneLine() function, instead use PLS_StartAdvOneLine available in all Power Operation versions since v7.30.
v7.20 SR1 and earlier: Upgrade to v7.20 SR1. Compile and run your project to restore and convert your historic alarm data. After v7.20, the dynamic one-line animation engine and related genies are different, so updates may need to be made to a v7.20 project you are upgrading to ensure correct operation of the dynamic one-line animation in the project.

Upgrade path requirements based on Advanced Reporting and Dashboards

Advanced Reporting and Dashboards Module v2022 must be used with Power Operation 2022 R1.
An upgrade might be required for the Advanced Reporting and Dashboards software (Power Monitoring Expert).
Versions of Power Operation and Power Monitoring Expert must be the same.