Installation and upgrade considerations

The Asset Strategy Optimization installation package (zip-file) needs to be downloaded first. The link will be provided by customer support.

The multi-user installation is complex and is usually carried out in close collaboration between your IT organization and an Asset Strategy Optimization consultant.

Once installed, several configuration settings will need to be performed in the application itself, which requires a license key from AVEVA. This will be provided by customer support. To avoid waiting times, we advise to coordinate this step with our customer support team, so they can provide the license key promptly.

Note: You may want to consider installing the AppLocker application to avoid a vulnerability. Consult Appendix B – AppLocker to learn more.

- Asset Strategy Optimization uses third party assemblies. Some of these are not signed. Please compare the list in Appendix D against your company policy before using our application.

Upgrade considerations

Following are some points that you must consider before upgrading to Asset Strategy Optimization 9.3 and later versions.

• If you have any RCAs that needs to be imported in Asset Strategy Optimization 9.1 or earlier releases, then you must first import the pending RCA models before upgrading to this version.

Data privacy with Microsoft Edge WebView2

AVEVA Asset Strategy Optimization is bundled with AVEVA Platform Common Services (PCS) 8.2.1. The Platform Common Services (PCS) 8.2.1 software makes use of Microsoft Edge WebView2. AVEVA has not disabled Microsoft Defender SmartScreen as part of use of Microsoft Edge WebView2 in this release.

The Microsoft Defender SmartScreen feature collects and transmits user information to Microsoft, as detailed in Microsoft’s statement on Data and Privacy in WebView2 and the Microsoft Edge Privacy Whitepaper.

Customers can disable the Microsoft Defender SmartScreen feature before installing Asset Strategy Optimization. Instructions for disabling this feature are available in the support documentation for Microsoft Edge.