AVEVA MES Cloud integration 8.1.0 release notes
- Last UpdatedFeb 23, 2026
- 8 minute read
About this release
MES Cloud integration (Version 8.1.0) 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. The MES Staging Curation Service supports publishing of MES events from util_history, job_history, job_hour_history, shift_history, wo, job, job_bom, item_prod, 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, so_line, sample, result, sample_char_link (containing sample_char_rule_link records), and bottleneck_history. All necessary context information such as entity, items, utilization reasons, characteristics, QM specifications, and production lines are also included.
For detailed information on the CONNECT data services types supported by this release of MES Cloud integration, see the tables below.
-
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.
CONNECT data services types supported by MES in this release
The following table lists the types in CONNECT data services supported by MES in this release. The last two columns contain the supported actions for the types listed.
|
CONNECT data services Type Id |
MES Table |
Upserts |
Deletes |
|---|---|---|---|
|
Asset |
ent |
Yes |
Yes |
|
MESCustomer |
cust |
Yes |
Yes |
|
MESEquipmentUtilizationHistory |
util_history |
Yes |
Yes |
|
MESEquipmentUtilizationReason |
util_reas |
Yes |
Yes |
|
MESEquipmentUtilizationReasonGroup |
util_reas_grp |
Yes |
Yes |
|
MESEquipmentUtilizationState |
util_state |
Yes |
Yes |
|
MESJobHourlyResponse |
job_hour_history |
Yes |
No |
|
MESJobOrder |
job |
Yes |
Yes |
|
MESJobOrderRoute |
job_route |
Yes |
Yes |
|
MESJobOrderStateHistory |
job_event |
Yes |
No |
|
MESJobResponse |
job_history |
Yes |
No |
|
MESJobResponseState |
job_state |
Yes |
Yes |
|
MESLocation |
site |
Yes |
Yes |
|
MESMaterialClass |
item_class |
Yes |
Yes |
|
MESMaterialConsumedActual |
item_cons |
Yes |
Yes |
|
MESMaterialConsumedActualProperty |
job_event |
Yes |
No |
|
MESMaterialDefinition |
Item |
Yes |
Yes |
|
MESMaterialGrade |
item_grade |
Yes |
Yes |
|
MESMaterialInventory |
item_inv |
Yes |
Yes |
|
MESMaterialInventoryTransfer |
item_transfer |
Yes |
No |
|
MESMaterialLot |
lot |
Yes |
Yes |
|
MESMaterialLotStatus |
item_state |
Yes |
Yes |
|
MESMaterialOrderLine1 |
po_line_so_line |
Yes |
Yes |
|
MESMaterialOrderMovement2 |
receipt_lot_shipment_lot |
Yes |
Yes |
|
MESMaterialProducedActual |
item_prod |
Yes |
Yes |
|
MESMaterialProducedActualProperty |
job_event |
Yes |
No |
|
MESMaterialReason |
item_reas |
Yes |
Yes |
|
MESMaterialReasonGroup |
item_reas_grp |
Yes |
Yes |
|
MESMaterialSublot |
sublot |
Yes |
Yes |
|
MESOperationsMaterialBill |
job_bom |
Yes |
Yes |
|
MESPerson |
user_name |
Yes |
Yes |
|
MESProductionLine |
line |
Yes |
Yes |
|
MESProductionLineAsset |
line_ent_link |
Yes |
Yes |
|
MESProductionLineBottleneckHistory |
bottleneck_history |
Yes |
No |
|
MESQASPCRule |
spc_rule |
Yes |
No |
|
MESQASPCStatistic |
stats |
Yes |
No |
|
MESQATestCategory |
category |
Yes |
Yes |
|
MESQATestSample |
sample |
Yes |
Yes |
|
MESQATestSampleCharacteristic |
sample_char_link |
Yes |
Yes |
|
MESQATestSampleCharacteristicResult |
result |
Yes |
Yes |
|
MESQATestSpecification |
qm_spec |
Yes |
Yes |
|
MESQATestSpecificationCharacteristic |
qm_spec_char_link |
Yes |
Yes |
|
MESShiftDefinition |
shift |
Yes |
Yes |
|
MESShiftHistory |
shift_history |
Yes |
No |
|
MESStorageLocationMovement |
storage_ent_transfer |
Yes |
Yes |
|
MESTrait |
ent |
Yes |
Yes |
|
MESUnitOfMeasureConversion |
uom_conv |
Yes |
Yes |
|
MESUnitOfMeasureDefinition |
uom |
Yes |
Yes |
|
MESWorkRequest |
wo |
Yes |
Yes |
1po_line_so_line pulls data from the tables po, po_line, so, so_line.
2receipt_lot_shipment_lot pulls data from the tables receipt, receipt_lot, shipment, shipment_lot.
CONNECT data services types with entity capabilities in this release
The following table lists the CONNECT data services types supported by MES that have entity capabilities. Types with entity capabilities have AssetSupportedType set in the Asset Framework for this release.
If an entity capability is removed after the entity has been created in CONNECT data services, the MESTrait will be removed, but the AssetSupportedType will remain to cover scenarios where event data was already published related to the capability.
|
CONNECT data services Type Id |
Description |
|---|---|
|
MESEquipmentUtilizationHistory |
Entities in MES that can capture utilization data will be returned as part of this Type Id. |
|
MESJobHourlyResponse |
Entities in MES that can track OEE will be returned as part of this Type Id. |
|
MESJobResponse |
Entities in MES that can run jobs will be returned as part of this Type Id. |
|
MESJobOrderStateHistory |
Entities in MES that can run jobs will be returned as part of this Type Id. |
|
MESMaterialConsumedActual |
Entities in MES that can run jobs will be returned as part of this Type Id. |
|
MESMaterialConsumedActualProperty |
Entities in MES that can run jobs will be returned as part of this Type Id. |
|
MESMaterialInventory |
Entities in MES that can store will be returned as part of this Type Id. |
|
MESMaterialInventoryTransfer |
Entities in MES that can store will be returned as part of this Type Id. |
|
MESMaterialProducedActual |
Entities in MES that can run jobs will be returned as part of this Type Id. |
|
MESMaterialProducedActualProperty |
Entities in MES that can run jobs will be returned as part of this Type Id. |
|
MESQATestSample |
Entities in MES that can capture quality will be returned as part of this Type Id. |
|
MESQATestSampleCharacteristic |
Entities in MES that can capture quality will be returned as part of this Type Id. |
|
MESQATestSampleCharacteristicResult |
Entities in MES that can capture quality will be returned as part of this Type Id. |
|
MESShiftHistory |
Entities in MES that can change shifts will be returned as part of this Type Id. |
|
MESStorageLocationMovement |
Entities in MES that can store will be returned as part of this Type Id. |
|
MESTrait |
All entities in MES will be part of this Type Id. |
New features and enhancements
This release of MES Cloud integration includes the following new features and enhancements:
-
Adds support for the publishing of MES Quality events and reference types.
-
Adds support for the publishing of MES Production Line events and reference types.
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 2023 or MES 2023 R2 (including any patches)
Note: Refer to the MES Installation Guide (Version 7.0) for detailed MES 2023 installation requirements. Refer to the MES Installation Guide (Version 23.1) for detailed MES 2023 R2 installation requirements.
-
AVEVA Events to CONNECT agent
Note: Refer to the AVEVA Events to CONNECT Installation Documentation for detailed AVEVA Events to CONNECT installation requirements.
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 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 10 |
Professional or Enterprise |
1607 (Anniversary Update) or later for .NET 4.7.2 |
|
Windows 11 |
Professional or Enterprise |
none |
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 |
In addition:
-
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.
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.
Product compatibility
For this release, MES Cloud integration is compatible with MES 2023 and MES 2023 R2.
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.
For the most current compatibility information, see the Technology Matrix page.
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 3039808 |
Even though the installation allows the user to select a custom installation folder, MES Cloud integration installs to the same folder where MES 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:
|
|
na |
When configuring the AVEVA Events to CONNECT agent to publish history-only data from MES to CONNECT, the data is temporarily stored in the buffer folder configured for the agent. If there is a large amount of historical data to backfill, the size of the buffer will need to be increased to ensure all the data is transferred. The Events to CONNECT agent does not log an error when overwriting buffer files resulting in some data not being published. |