This document contains important information about AVEVA™ System Platform 2020, formerly Wonderware. This version of System Platform includes a number of security enhancements and new features for the component products of System Platform.
Important: Support for 32-bit operating systems and 32-bit SQL Server versions is discontinued in this release of System Platform. System Platform 2020 is only compatible with 64-bit operating systems and SQL Server versions. If you have a 32-bit version of SQL Server, you must uninstall it before installing System Platform. System Platform will check that an installed SQL version is compatible prior to installation, and will display an error message if the installed SQL Server version is not compatible for any reason (not only for 32-bit versions). For information about moving from 32-bit to 64-bit SQL Server, refer to Issue 1249251 under Install/Uninstall and Galaxy Migration Issues. For general information about SQL Server requirements, see SQL Server Notes.
In This Document
AVEVA Application Server 2020
AVEVA Communication Drivers Pack 2020
AVEVA Enterprise License Manager
AVEVA Enterprise License Server
AVEVA Enterprise Licensing Platform
AVEVA Historian 2020
AVEVA Historian Client 2020
AVEVA InTouch HMI 2020
AVEVA InTouch Access Anywhere Server 2020
AVEVA InTouch Access Anywhere Secure Gateway 2020
Platform Common Services 4.4.1
System Monitor Agent Install Manager 2020
System Monitor Manager 2020
Changelog: System Platform 2020
Add support for FLEX (subscription) licensing
Improve design-time performance for Object Wizards and Symbol Wizards
Improve propagation performance for changes made to Area objects
64-bit operating system required for all System Platform components
64-bit SQL Server required for Application Server, Historian, InTouch HMI, and InTouch OMI
Improve Galaxy Repository startup speed (aaGR process)
OI Core, OI Gateway, and OI Sim components are combined into the AVEVA Communication Drivers Pack
Allow import and use of WinForm controls in InTouch OMI ViewApps
Add InTouch OMI and InTouch HMI support for AVEVA Connect (cloud portal)
Add responsive option to InTouch OMI Layout Editor
Add methods for retrieving lists of named credentials in InTouch OMI apps
Add support for binding graphic custom properties in an InTouch OMI layout
Add HideContent method for InTouch OMI graphic and layout scripting
Add support for InTouch OMI Layout scripting
Add event scripting for InTouch OMI apps
Improvements to ContentPresenter app (InTouch OMI)
Add support for out-of-sequence data via multiple channels to AVEVA Telemetry Server
Allow OPC-UA clients to see Galaxy run-time data
Allow externally detected alarms to link to another attribute via a Boolean attribute (Historian improvement)
Add support for Historian LIKE/NOT LIKE functions in Application Server
Provide clear messages to allow customers to easily troubleshoot deployment issues
Miscellaneous bug fixes
Incorporate InTouch HMI and Application Server hot fixes
Supported System Platform Versions for Product Upgrade
You can upgrade directly to System Platform 2020 from the following versions:
Note that all existing products must be upgraded to the same version.
Supported System Platform Versions for Migration
You can migrate user-created content (for example, .cab files, .aaPKG files, Historian databases, etc.,) to System Platform 2020, as long as the content was created in one of the following product versions:
System Platform 2020 continues to utilize the server-based licensing subsystem introduced in System Platform 2017. This new licensing subsystem provides centralized license management, and replaces the file-based licensing system that was used in prior releases. Licenses must be activated before use.
If you are upgrading from Windows Server 2014 R2 SP1 (with or without patches), you must first install and configure a license server node, and activate the licenses to ensure continuous plant operation. The license server is typically installed on the Galaxy Repository node, but you can use a dedicated license server. See the "License Installation and Activation" section of the System Platform Installation Guide (SP_Install_Guide.pdf), located at the root of the DVD.
Start Menu and Shortcut Changes
Some Start menu folders and some of the System Platform shortcuts they contain have been renamed. Commonly used applications, such as the Change Network Account utility, Configurator, and System Platform Management Console, are now located under the AVEVA Start menu folder. These were under the Wonderware Utilities folder in prior releases.
System Platform 2020 Name
Wonderware System Platform
AVEVA System Platform
Sentinel System Monitor
AVEVA System Monitor
ArchestrA Service Bus Portal
Common Services Portal
AVEVA Enterprise License Manager
Enterprise License Manager
System Monitor Application
Readme Files for Other Products in this Release
To access individual product Readme files, insert the System Platform installation DVD and navigate to the applicable folder under the InstallFiles directory. Review the known and resolved issues contained in each Readme file for the component products updated for this release:
Location on Installation DVD
Application Server 2020
InTouch HMI 2020
Historian Server 2020
Historian Client 2020
InTouch Access Anywhere 2020
This information is applicable to a small subset of highly secured environments, in which operating systems and supporting networks have been configured to enable TLS 1.2 and where TLS 1.0 and 1.1 have been purposefully disabled. In these rare instances, some additional configuration is required to ensure that System Platform will work as expected.
System Platform 2020 includes various measures to strengthen security, including the ability to leverage TLS (transport layer security) 1.2, provided that TLS 1.2 it has been enabled and configured in the host operating system.
In some cases, you may have to enable TLS 1.2 support by applying Microsoft updates and by making several manual edits to the system registry. The tasks of applying all Microsoft updates and editing the system registry must be completed before you install System Platform 2020. These instructions also apply to any other software products that support TLS 1.2. Follow the instructions listed below.
If you are required to enable TLS 1.2 and disable TLS 1.0 and TLS 1.1:
For important information about this product release, go to the AVEVA Global Customer Support (GCS) website. Information on the GCS website includes product requirements, compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.
Two important new features, the requirement for 64-bit operating systems and SQL Server versions (where needed) and the Flex licensing option, apply across all System Platform 2020 products.
Additional new product-specific features are outlined below.
64-bit Operating System and SQL Server Now Required
With the release of System Platform 2020, a 64-bit operating system and SQL Server version are now required for all System Platform core products: Application Server, InTouch OMI, InTouch HMI, and the Historian. Running in a 64-bit environment provides a common environment for all products, and ensure that you get the best performance from your System Platform installation. For information about moving from 32-bit to 64-bit SQL Server, refer to Issue 1249251 under Install/Uninstall and Galaxy Migration Issues.
Flex Licensing Option
You can now choose between a perpetual license model and the new Flex-licensing subscription option for Application Server. Flex licensing lets you easily acquire and assign licenses to platforms, much more easily and affordably than what was possible with legacy perpetual licensing. Flex licenses are based on AppEngine assignments, rather than having to calculate I/O counts and other system parameters to determine final licensing costs. Other benefits include better cash flow management and a simplified business process.
A number of enhancements to improve performance have been implemented for this release of System Platform.
Credential Management for InTouch OMI ViewApps
InTouch OMI ViewApps can use security credentials created in Application Server to gain access to third-party data where Windows OS credentials are not recognized, and/or to provide a method to automatically load a particular data set for specified users. Credential Management is described under "Security" in both the Application Server User Guide and the System Platform 2020 Help.
Support for Additional .NET Controls InTouch OMI ViewApps
InTouch OMI now lets you import, configure, and use .NET WinForm controls in a ViewApp (.NET WPF controls were already supported). See "Importing ArchestrA Apps" in the System Platform 2020 Help for more information.
Responsive Layouts for InTouch OMI ViewApps
The Layout Editor has a new option for creating responsive layouts. This allows the ViewApp to dynamically move and resize content in response to the screen size on which it is being viewed. See "About Responsive Layouts" in the System Platform 2020 Help for more information.
Script Support for InTouch OMI Layouts
Using the same foundation as scripting for Industrial Graphics (formerly ArchestrA Graphics), layout scripting lets you customize run time behaviors for layout content as well as the layout container by adding scripts. As part of layout support, graphic custom properties can be overridden within the layout. A new namespace, "MyContent," is available for addressing content within a single ViewApp, in addition to the MyViewApp global namespace. See "Layout Scripts" in the System Platform 2020 Help for more information.
Event Scripting for InTouch OMI Layouts
You can add event-based scripts to InTouch OMI layouts when the layout include apps that expose public properties, for example "MouseDown." See "Add an Event Handler Script" in the System Platform 2020 Help for more information.
HideContent() Scripting Function and API Call
The HideContent() scripting function and API call can be used in conjunction with ShowContent(), which was introduced in System Platform 2017 Update 2. ShowContent() lets you place symbols or layouts into specific panes within an InTouch OMI layout, either through scripting or programmatically, and now HideContent() provides the additional functionality for more complete control of the content you wish to make available to users at run time. See the Application Server Scripting Guide for more information.
InTouch OMI App Enhancements
The MapApp and Content Presenter App have been enhanced with new features and improved functionality. These apps are described in the System Platform 2020 Help.
Browse Application Server Run-Time Data with OPC UA Clients
AVEVA Application Server now includes OPC UA server functionality. This lets you browse the namespace in a deployed galaxy, and connect to, subscribe to, and retrieve galaxy data, without the need for a gateway or other protocol translation mechanism. See "Configuring and Using the OPC UA Server" in the Application Server User Guide for more information.
AVEVA Connect for Sharing Graphics
AVEVA Connect is a cloud-based resource that lets you easily create and share graphics between locations, galaxies, and applications. See "AVEVA Connect" in the Application Server User Guide for more information.
AVEVA Telemetry Server Enhancements
The Telemetry Server now supports handling data that arrives out-of-sequence via multiple channels. See "Telemetry Server Data References" in the Application Server User Guide for more information.
Visualize Externally-Detected Alarms
Alarm conditions that have been detected within a PLC can now be visualized in, for example, the Historical Trend App or the Alarm App. To accomplish this, the ability to configure a Boolean attribute within the Object Editor as an alarm input for a State Alarm has been added. This allows the trend tools to properly visualize alarms that have been detected externally. See "Using the State Alarm Feature" in the Application Server User Guide for more information.
InTouch HMI 2020 includes a number of new features, hot fixes, and provides support for the latest versions of Microsoft products. Refer to the GCS Technology Matrix for the list of supported Microsoft products. The following section summarizes the major features introduced in this release.
64-bit Operating System and SQL Server Now Required
With the release of System Platform 2020, a 64-bit operating system and SQL Server version are now required for all System Platform core products: Application Server, InTouch OMI, InTouch HMI, and the Historian. Running in a 64-bit environment provides a common environment for all products, and ensure that you get the best performance from your System Platform installation.
Flex Licensing Option
You can now choose between a perpetual license model and new subscription option for InTouch HMI. Subscription (Flex) licensing lets you easily acquire licenses, much more easily and affordably than what was possible with legacy perpetual licensing. For more information, see the Application Management and Extension Guide.
New and Improved InTouch HMI Application Manager
The new InTouch HMI Application Manager presents with a modern user interface with simplified workflow tasks and easier access to features.
Integration with AVEVA Connect
You can upload, download and manage Industrial Graphics in AVEVA Connect via the Graphic Toolbox.
In this release we have introduced the framework of using HTML5 widgets within InTouch HMI. The Carousel widget from the graphic toolbox will allow you to configure and view a HTML5 widget in WindowViewer and Web Client.
Standalone Applications with Support for Industrial Graphics
The new standalone application now supports Industrial Graphics.
Other Major InTouch HMI Features
There are many improvements to the Web Client:
Web Client now available as a Mobile App
The Web Client interface is now available as a Mobile App. For more information see the Viewing Application Graphics in a Web Browser guide.
Using the Historical Trend Control from the Drawing toolbar you can configure the IndustrialSQL Server History Provider (Historian Server), to visualize historical trend data. This functionality requires the storage of database credentials in local files. To prevent unauthorized access to Historian and other SQL databases, we recommend using the ArchestrA Trend Client, with a Windows Integrated or Windows Account authentication mode.
Multi-Tier Replication Support
The Historian supports multi-tier replication. Data originating at tier 1 can be replicated to tier 2, then again to tier 3, and so on. Replication from tier 1 to tier two can be simple or summary replication. Replication beyond tier 2 is simple replication.
Support for AVEVA Flex Licensing
Enhanced Excel add-in
Support for tag selection using search, tag metadata in headings, wide/narrow output formatting, flexible column selection, and native formats for numbers/dates.
AVEVA Historian Client Web (previously known as Historian Insight) supports white labeling for OEMs
Trend automatically sets scale precision
Added auto precision option (enabled by default) to tag trend options. When enabled, the number of decimal places is set automatically based on the value range.
Trend XY plot "start/end" marker changes
Added options to show end markers only, show start markers only, not show any markers or time labels, and to change start/end marker sizes.
Dashboards can be accessed by URL, so they can be shared
Support for AVEVA Flex Licensing
Web Help - Browser-based User Assistance
Web help components have been delivered in this release. Web help opens in the default browser on your local computer. Help displayed in a browser allows more dynamic and searchable user assistance including standard web browser navigation and tutorial videos.
Typically, help content is installed on your local machine as part of the documentation library, and displays in your browser without requiring an Internet connection. To open the help, use one of the following methods (depending on the editor/UI you are using):
Browser Requirements and Recommendations
Internet Explorer is recommended. You can also view web help Firefox. If you use Firefox, you may need to install and use an IE rendering extension (for example, IE Tab) to ensure that video content is shown.
Browser Permissions for Displaying Web Help
Each browser and Windows operating system combination has its own security permissions. Using Internet Explorer (version 8, 10, or 11) as an example, you may see a dialog requesting you to "Allow blocked content" each time you invoke the web help. This dialog is triggered by the presence in the help system of JavaScript components that control internal navigation and topic display elements such as pop-up or in-place-expanding display blocks that contain text and graphical images. The text and image content is itself non-active.
You can accept each occurrence of this dialog, or you can set the following option in Internet Explorer, depending on your IT security requirements: In Internet Options, click the Advanced tab, then navigate to the Security section. Enable the "Allow active content to run in files on My Computer." Permissions and security settings will vary depending on your specific browser.
Playback of Tutorial Videos
The web help may contain a number of brief tutorial videos. To play these videos, you must have Microsoft Media Player installed on your local machine. In Windows Server operating systems, you must enable the "Desktop Experience" feature using Server Manager.
Internet Explorer (or IE-rendering in other browsers) may be required for viewing video content. If using a browser other than Internet Explorer without IE rendering enabled, videos may not be visible.
InTouch OMI SDK Web Help
When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.
When you install the Application Server IDE, the InTouch OMI SDK is automatically installed, and a link to the InTouch OMI SDK Web Help is added to the Windows start menu. The browser requirements and recommendations that apply to System Platform Web Help also apply to the SDK help.