AVEVA MES Cloud integration 8.0 release notes
- Last UpdatedFeb 23, 2026
- 6 minute read
This version of AVEVA™ Manufacturing Execution System (MES) Cloud integration supports MES 2020 and MES 2023. It includes new capabilities for publishing MES genealogy and inventory transactions.
This Readme contains important information about MES Cloud integration (Version 8.0) and documents the system requirements, licensing, and user documentation.
The Readme file from this release of MES Cloud integration is posted to the Product Hub page of the Knowledge and Support Center. Once on the Product Hub page, you can use the filter to list the MES Cloud integration documents, which includes the Readme file.
About this release
MES Cloud integration includes the following components for extracting on-premises MES data and publishing it to CONNECT data services:
AVEVA Events to CONNECT agent
The AVEVA Events to CONNECT agent provides the connectivity to CONNECT data services and enables the publishing of MES events from the MES Curation Service. The AVEVA MES Cloud integration solution must be used with this component. AVEVA Events to CONNECT is included as a separate install and configuration.
MES Curation Service
The MES Staging Curation service is a Windows service that provides two main functions:
-
Extracting (curating) data from the MES database and storing it in a staging schema. This release of the MES Staging Curation Service supports publishing of MES genealogy and inventory events from item_cons, job_events, job_route, lot, sublot, item_inv, item_transfer, storage_ent_transfer, receipt, receipt_lot, shipment, shipment_lot, po, po_line, so, and so_line. All necessary context information such as customer are also included.
-
Providing a Web API interface for the AVEVA Events to CONNECT agent. The agent periodically requests event data from the MES Curation service including context information. When data is available, it is sent to CONNECT data services event storage.
CONNECT visualization
Within the AVEVA Cloud Platform, the visualization of the published data is through pre-built widgets. New widgets to visualize the additional published data will be released incrementally in the future.
System requirements
The system requirements describe the hardware, software, and operating system requirements to install the MES Cloud integration software.
For the most current compatibility information, see the Technology Matrix page.
Hardware requirements
The hardware requirements that are described are based on the minimal requirements for running MES Cloud integration components. Additional minimum hardware might be required based on the version of Windows being used on a node (see Minimum Hardware Requirements for Supported Windows Version).
Database server
The following hardware is recommended:
-
Computer with dual core processor with 2 GHz or faster clock speed, or single core processor with 3 GHz or faster clock speed. Multi-core processor recommended for optimal performance.
-
8 GB or more of RAM recommended, 4 GB of RAM minimum.
-
300-GB Disk with RAID support for data. The amount of disk space necessary depends on the frequency of data collected (number of work orders, operations, production quantities, etc.) and the amount of data kept online in the production database.
-
Depending on complexity and size of the database server, 30 GB or more of available disk space is recommended. The database hard disk space should be enough to support the storage and performance requirements for your particular deployment.
Minimum hardware requirements for supported Windows version
All supported Windows operating system versions require 64-bit CPUs.
See your specific Microsoft operating system hardware requirements for additional details.
Software requirements
The following AVEVA and other third-party prerequisite software is required to install MES Cloud integration:
-
Microsoft .NET Framework 4.8
-
Microsoft .NET Core 8
Note: If the required release of .NET Core is not present prior to installing MES Cloud integration, you will be prompted to install it during the MES Cloud integration installation.
-
MES 2020 or MES 2023 (including any patches)
Note: Refer to the MES Installation Guide (Version 6.2) for detailed MES 2020 installation requirements or the MES Installation Guide (Version 7.0) for detailed MES 2023 installation requirements. For information on implementing MES Cloud integration for MES 2023 R2, refer to the MES 2023 R2 Installation Guide (v23.1).
-
AVEVA Events to CONNECT agent
Note: Refer to the AVEVA Events to CONNECT Installation Documentation for detailed AVEVA Events to CONNECT installation requirements.
Database requirements
The following Microsoft SQL Server versions are supported for MES Cloud integration:
|
Microsoft SQL Server version |
Type |
Service pack level |
|
|
2017 |
64-bit |
Express, Standard, or Enterprise Edition |
N/A |
|
2019 |
64-bit |
Express, Standard, or Enterprise Edition |
N/A |
|
2022 |
64-bit |
Express, Standard, or Enterprise Edition |
N/A |
When you are considering database requirements, note the following details:
-
Although MES 2020 supports SQL 2014 and SQL 2016 and MES 2023 supports SQL 2016 SP3, the MES Staging Curation Service makes use of functions only available in SQL 2017 and later.
-
During configuration, the MES database will have Read Committed Snapshot enabled.
Operating system requirements
The following table lists the operating systems that are supported and can be installed on computers that run MES Cloud integration.
|
Operating systems |
Type |
Version |
|---|---|---|
|
Windows Server 2012 R2 |
Standard or Datacenter |
none |
|
Windows Server 2016 |
Standard or Datacenter |
none |
|
Windows Server 2019 |
Standard or Datacenter |
none |
|
Windows Server 2022 |
Standard or Datacenter |
none |
|
Windows Server 2025 |
Standard or Datacenter |
none |
|
Windows Server |
Core |
1803/1903 |
|
Windows 8.1 |
Professional or Enterprise |
none |
|
Windows 10 |
Professional or Enterprise |
1607 (Anniversary Update) or later for .NET 4.7.2 |
|
Windows 11 |
Professional or Enterprise |
none |
Product compatibility
For this release, MES Cloud integration is compatible with MES 2020 and MES 2023. If using MES 2023 R2, install MES Cloud integration with the MES 2023 R2 installation.
MES Cloud integration must be installed on a node with the MES Middleware already installed.
All other AVEVA software components that are compatible with the installed version of MES can co-exist on the same node.
Resolved issues
The following table lists the resolved issues for this release of MES Cloud integration.
|
ID |
Description |
|---|---|
|
na |
Continuously updated event records (e.g., item production being updated every 30 seconds) do not get sent to CONNECT until the updates stop. This is addressed with the new TypesToUpdateFrequently setting in the appsettings.json file. |
Known issues
The following table lists the known issues for this release of MES Cloud integration.
|
ID |
Description |
|---|---|
|
IMS 2353035 |
For entities with shifts that have the MES Curator Service running, if the start time of an active shift is moved into the past in MES 2020, the current shift on the entity is never closed in CONNECT data services. |
|
IMS 3039808 |
Even though the installation allows the user to select a custom installation folder, MES Cloud integration installs to the same folder where MES 2020 is installed. |
|
na |
The visualization widgets rely on the entity standard item to determine the asset's unit of measure (UOM). The UOM is then used for UOM conversions. This setting is available in the MES Web Portal and is added to MES Client in MES 2023 R2. |
|
na |
Deletes are reported to CONNECT data services first followed by updates to data and new data. If the frequency for data curation for a type is different from the frequency of data requests from the AVEVA Events to CONNECT agent it is possible that a record that is inserted (curated), then deleted (curated), and then requested will remain in CONNECT data services. |
|
na |
When configuring MES components using the Configurator, a runtime error may occur if multiple components depend on different versions of the System.Text.Json assembly. Specifically, if a component using a newer version is loaded first, it locks that version into the process. Subsequent components that rely on an older version will fail with a missing method implementation error (e.g., DisposeAsync not found). This is due to .NET’s restriction of loading only one version of an assembly per process. Note that this issue is more likely to occur when AVEVA Events to CONNECT is installed before PCS. If this error occurs, restart the Configurator and configure the components that depend on older versions of the assembly first. |
|
na |
Important: The AVEVA Events to CONNECT agent is currently only supported on systems configured with the English (United States) culture setting (en-US). Systems using non-English culture settings (e.g., fr-FR, de-DE, ja-JP) may experience issues such as:
To ensure proper functionality, please verify that your system’s Language and Region settings are configured to use English (United States) prior to installation and operation of the agent. |
Documentation
The following documentation is available for MES Cloud integration:
-
MES Cloud integration online help (https://docs.aveva.com)
-
MES Cloud integration Installation Guide
-
MES Cloud integration Readme