AVEVA Manufacturing Execution System 2023 R2 (Version 23.1)

Last revision: Wednesday, October 29, 2025

In This Document

About these release notes

About this release

System requirements

Product compatibility

Licensing

Upgrade from a previous version to MES 2023 R2

Resolved issues

Known issues

Security information and guidance

MES documentation

About these release notes

These release notes contain important information about AVEVA™ Manufacturing Execution System (MES) 2023 R2 (version 23.1). The release notes document the system requirements, known issues, resolved issues, and changes, if any, to the MES user documentation.

Readme files from previous releases of MES are 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 documents, which include the Readme files.

About this release

The MES 2023 R2 release includes multiple significant changes as listed below. The version number has been updated from 7.0 to 23.1 to align with other AVEVA product versions. However, this release is an incremental update to MES 2023.

Upon release, MES 2023 R2 is compatible with System Platform 2023 R2 SP1 Patch 2, Work Tasks 2023 R2, Recipe Manager 2023 R2, and other current releases. See the compatibility information on the Technology Matrix page for further updates.

MES Cloud integration

The ability to install MES Cloud Integration as a feature of MES 2023 R2 has been added.

MES Data Editor and MES Supervisor are removed

This release of AVEVA MES no longer includes the Data Editor or Supervisor components:

Supply Chain Connector tables and functionality have been removed. Do not upgrade if you use Supply Chain Connector.
Entity Usage Editor and Labor Usage Editor .Net controls from Data Editor have been removed. Remaining Data Editor .Net controls remain in the product.
Corresponding privileges and system parameters have been removed.

MES Client

Selecting an error message in the error list in MES Client opens the corresponding editor and navigate to the row with the error.
When selecting the parent (entities) node in Entity editor of MES Client, the properties pane shows a summary of acquired licenses and configured entities with corresponding capabilities.
Entity spares and standard item for entities (OEE Exec property) are added.
The grouping of system parameters is updated to remove references to the Data Editor and Supervisor groups and create a new Configuration group. The system parameters for defining processes are moved from the General group to the new Configuration group. In addition, any remaining Data Editor or Supervisor parameters are moved to appropriate groups.
The grouping of system privileges are updated to remove references to the Data Editor. In addition, the Configurator group is renamed to Configuration. Any remaining Data Editor privileges are moved to the Supervisor or Operator group.
The Quality sample generation system parameter is added for calendar frequency.
All users in a group can be assigned to a certification.
When MES Cloud Integration is installed, there is a new editor for configuring CONNECT Types.
The archive, purge, and restore stored procedures are updated to handle larger data volumes.

MES database

Identity columns are modified to start with one (1) instead of zero (0) for new installations (no change to any data in an upgrade). The only exception to this is the SPC rule ID.
The logic in create work order from process is updated to set start and required quantity from reject percentage (%).
The row_id for cert_audit_log.ref_row_id is updated to long integer.

MES Stateless API

A new JobExec.CreateWOFromProcess overload that includes work order (WO) spare fields is added.
New async methods for Sample.FinalizeSampleDataAsync, Sample.GenerateSampleAsync, Sample.RecordSampleDataAsync, Result.RecordResultDataAsync, Result.RecordSampleCharacteristicDataAsync are added.
A new WO.update overload that includes production schedule ID parameter is added.
A new JobExec.CertSignoff overload to support Datalog row IDs as long integer.
Updated methods or new overloads for DataLog to support row ID as long integer.
New method JobRoute.GetByKey.
New overload Language.GetAll adds the ability to filter by context.

Web API

The UtilEvent model (Mes.WebApi.Models.V3.Util.UtilEvent) - raw_reas_cd datatype is changed from integer to string.
The Web API GET calls are updated to use last_edit_at >= Date.
New Web API v3/util/allowableReasons to get limited list of reasons based on a raw reason code.

Stateful API

New overload JobExec.PopupReduceProdDlg for reducing serial numbers.

Sample Recording Object

Sample Recording Object (SRO) is enhanced to include the without response mode and rejected messages primitive to support using MS Message Queue for storing messages locally when disconnected from the MES Middleware.

Security

The MES Middleware endpoints (sync, async, message queue, and event broker) are updated to require a valid user making the call.
The MES Middleware Proxy is configured to register with AVEVA Identity Manager (AIM).
All MES Client components are updated to provide security token when communicating with the MES Middleware.
Support for redundant System Management Servers (AIM single sign-on redundancy) is added.
Issues with PCS monthly certificate renewal are addressed.
OS User security is enabled in the default install.

Note: This is the last MES release that will include native security

Updated documentation

Significant content updates to the MES user documentation are summarized below.

MES Client User Guide and Help

Content now includes the new and updated modules for the changes in this release.

MES Database Reference Guide

Document is included as part of the installation. Includes new and updated tables for this release.

MES Installation Guide and Help

Includes changes to the installation, upgrading, and configuration.

MES Middleware and Cloud integration User Guide

Renamed document. Updates to include details about the MES Curator service.

MES Stateless API Reference Help

Updates to include API changes described above in 'MES Stateless API'.

MES Supervisor User Guide

Deprecated.

MES Data Editor User Guide

Deprecated.

MES Deployment Guide

Content now includes instructions for deploying MES Cloud integration.

MES Virtual Environment Implementation Guide

Deprecated. Content added to the MES Deployment Guide.

MES Web API V3 Reference

Updates to include API changes described above in 'MES Web API V3'.

MES Operator User Guide and Help

Updates to describe the new and updated modules in this release.

MES SRO User Guide

Updates that describe without response mode.

MES .NET Controls User Guide

Updates to describe the labor control.

System requirements

This section describes the hardware, software, and operating system requirements to install the MES 2023 R2 software.

For the most current compatibility information, see the Technology Matrix page.

Hardware requirements

The following are the recommended hardware requirements for nodes on which MES 2023 R2 components will be installed.

The hardware requirements that are described in the following topics are based on the minimal requirements for running MES 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 versions).

Middleware or database server

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.

MES web application server

Computer with 2 GHz or faster processor clock speed.
8 GB or more of RAM recommended, 4 GB of RAM minimum.

Minimum hardware requirements for supported Windows versions

All supported Windows operating system versions require 64-bit CPUs.

See your specific Microsoft operating system hardware requirements for additional details.

Software requirements

This section lists the AVEVA and other third-party software requirements to install MES 2023 R2:

Microsoft .NET Framework 4.8 is required for all components. If it is not already installed, the MES installation process will prompt you to install it.
Microsoft .NET Core 8.0.10 is required for all components. Later versions of Microsoft .NET Core can coexist on the same system, but MES requires .NET Core 8.0.10.
If installing MES Web Portal, the following are required:
- Microsoft Internet Information Services 7.5.
- Microsoft Web Deploy tool.
- MES Web Portal is compatible with version 13.0.1 of newtonsoft.json.dll.
If installing MES application objects, the following are required:
- The Entity Model Builder feature requires System Platform Integrated Development Environment (System Platform IDE).
- The MES Objects require Microsoft Message Queue for their asynchronous calls.

Web browsers supported for MES Web Portal client

The MES Web Portal client has been validated with the following web browsers, using the web browser versions that were available at the time of the MES 2023 R2 release:

Chrome
Edge Chromium
Firefox

It is expected that the MES Web Portal client will operate properly with subsequent releases of Chrome, Edge, and Firefox browsers. However, if any MES Web Portal features do not function due to changes in a new release of Chrome, Edge, or Firefox, customers will be notified by a Technical Alert when we are made aware of the issue.

Note: Videos in the MES Web Portal help will not run in standard Firefox. To run demo videos in Firefox, you must have an MP4-capable video player such as Windows Media Player installed on both the server and client machines or have a third-party MP4 plug-in installed in Firefox.

Database requirements

Supported Microsoft SQL Server versions


Microsoft SQL Server Version		Type
2017	64-bit	Express, Standard, or Enterprise Edition
2019	64-bit	Express, Standard, or Enterprise Edition
2022	64-bit	Express, Standard, or Enterprise Edition

Requirements

The MES 2023 R2 release requires SQL Server 2017 or later as it makes use of SQL functionality added in that release.
SQL Server should be configured for TCP/IP for local connections. SQL Server should also be configured for TCP/IP for remote connections if servers that require access to the MES database, such as the MES middleware server or the Reports server, are on remote machines. SQL Server must be installed using a case-insensitive collation.
Microsoft Distributed Transaction Coordinator and IIS 6.0 or later.
MES Database using multiple languages requires AL32UTF8 Unicode character set installed on your server.

Recommendations

For proper database maintenance, use a SQL Enterprise version due to the availability of online indexing capability.

Operating system requirements

The following table lists the operating systems that are supported and can be installed on computers that run MES 2023 R2.


Operating Systems		Type	Version	MES Features
Operating Systems		Type	Version	Client Components	Database	Middleware	MES Web Portal Service	Reports Components
Windows Server 2019	64-bit	Standard or Datacenter	none	Yes	Yes	Yes	Yes	Yes
Windows Server 2022	64-bit	Standard or Datacenter	none	Yes	Yes	Yes	Yes	Yes
Windows Server 2025	64-bit	Standard or Datacenter	none	Yes	Yes	Yes	Yes	Yes
Windows Server	64-bit	Core	1803/1903	No	No	No	No	No
Windows 11	64-bit	Professional or Enterprise	none	Yes	Yes ¹	Yes ¹	No	Yes

¹ Indicates that it is supported for sales and demo purposes only, not for production systems.

Support for virtual environments and high availability

The MES 2023 R2 software can be run in virtual environments to support High Availability for Live Migration and Failover. Implementing High Availability can be performed using VMware technology or Microsoft Hyper-V technology.

For information about implementing MES in a virtual environment, see the System Platform in a Virtualized Environment Implementation Guide and the MES Deployment Guide.

For specific information on VMware product compatibility, see the VMWare Compatibility Guide at https://compatibilityguide.broadcom.com.

Support for non-English versions of operating systems

The MES 2023 R2 software runs on the following non-English operating systems:

French
German
Japanese
Simplified Chinese
Russian
Spanish

The corresponding language versions of Microsoft SQL server are used, where applicable.

MES firewall exceptions list and firewall ports

The firewall ports and exception list specific to MES applications are created during the MES DB/MW Communication component configuration.

The default HTTPS, HTTP, and SQL Server firewall ports that are required by MES applications are opened by default on Windows or by installing SQL Server. The default HTTP and HTTPS port numbers that MES uses are listed in the following table.


Application / Service	Component	Port				Changeable
Application / Service	Component	HTTP	HTTPS	TCP	NET. MSMQ	HTTP	HTTPS	TCP	NET. MSMQ
FactMES. Server.Host (MW Service Host executable)	MW sync endpoint	80	443	8099	N/A	Y	Y	N	N/A
	MW async endpoint	N/A	N/A	NA	1801	N/A	N/A	N/A	N
	Event broker	80	N/A	N/A	N/A	Y	N/A	N/A	N/A
	MES middleware web API	N/A	443¹	N/A	N/A	N/A	Y	N/A	N/A
	MES Curation Web API	N/A	443¹	N/A	N/A	N/A	Y	N/A	N/A
Client applications	MES middleware proxy	80	443	N/A	N/A	Y	Y	N/A	N/A
Internet Information Service (IIS)	MES Web Portal	N/A	443	N/A	N/A	N/A	Y	N/A	N/A
System Management Server (SMS)	AVEVA Identity Management (AIM)	80	443	N/A	N/A	Y	Y	N/A	N/A

¹ MES shares the port with SMS for the MES Web API and MES Curation Web API.

For a list of the firewall ports used by other AVEVA products with which MES works, refer to their documentation:

License Server and Manager: Enterprise Licensing Guide
System Platform: System Platform Readme and Application Server User Guide
Work Tasks: Work Tasks Administrator Guide
BI Gateway: BI Gateway Installation Guide and BI Gateway Web Configuration Guide

For SQL Server and similar third-party products, refer to the appropriate product documentation.

Product compatibility

MES 2023 R2 is compatible and can co-exist with the following products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

For the most current compatibility information, see the Technology Matrix page.

Component	Version	Compatibility	Co-existence
Application Server	2020, 2020 R2	N	N
System Platform	2023, 2023 R2, 2023 R2 SP1, 2023 R2 SP1 Patch 1	N	N
System Platform	2023 R2 SP1 Patch 2	Y	Y
Platform Common Services (PCS)¹	8.1.2, 8.1.3, 8.1.4, 8.1.5	Y	Y
Operations Management Interface (OMI)	2023 R2 SP1 Patch 2	Y	Y
InTouch^®	2023 R2 SP1 Patch 2	Y	Y
Historian Server	2023 R2 SP1 Patch 2	N/A	Y
Historian Client	2023 R2 SP1 Patch 2	N/A	Y
Batch Management	2023	N/A	N
Batch Management	2023 R2	N/A	Y
BI Gateway	2021 SP 1²	Y	Y
Enterprise Integration	2023 R2	Y	Y
Recipe Management	2020, 2020 U1, 2023	N/A	N
Recipe Management	2023 R2	N/A	Y
Work Tasks	2020, 2020 U1, 2020 U2, 2023, 2023 SP1	N	N
Work Tasks	2023 R2	Y	Y
Work Tasks Connector/Extension for MES	7.0³	N	N
Work Tasks Connector/Extension for MES	7.1⁴	Y	Y

¹This version of MES installs PCS version 8.1.5 and PCS SDK 4.1.5.

²The version of BI Gateway supported by MES has different OS and SQL Server version support. Check the Technology Matrix page for the latest updates to BI Gateway OS and SQL Server support^..

³This version of Work Tasks Connector/Extension for MES works with MES 2023 and Work Tasks 2023.

⁴This version of Work Tasks Connector/Extension works with MES 2023 R2 and Work Tasks 2023 R2.

Note: MES 2023 R2 does not support the Connected Experience option in System Platform products that automatically logs the CONNECT user into the application.

Licensing

The 2007 Microsoft Office Fluent User Interface is subject to protection under U.S. and international intellectual property laws and is used by MES under license from Microsoft.

Quinn-Curtis SPC Chart Control:

The use of the QCSPCChart and QCChart2D WPF, .NET, and JavaScript controls require the purchase of an Advanced Dev Studio or MES Quality license.

Upgrade from a previous version to MES 2023 R2

Upgrading from the following MES versions is supported:

4.0 (all service packs and patches)
4.5 (including P1)
5.0 (including SP1 and R2)
5.3
6.0 (including R2)
6.2
7.0

To upgrade from an earlier version, you must first uninstall the previous version and then install the new version.

Database migration

If an existing database has custom indexes or keys that reference MES core tables, the database migration will fail. Prior to upgrading, drop any custom indexes and keys. They can be added back after the database migration is complete.
The MES Database Setup component in the post-install Configurator application supports migration of databases from version 4.0 and later. To migrate from versions earlier than 4.0, you must first update the database to version 4.0. Custom modifications to any version of the MES database might not be supported by the utility and might prevent migration.
The MES database upgrade from versions prior to 6.0 will take significantly longer than previous upgrades as the utilization data must be migrated to the new schema. Databases with multiple millions of records in the Util_Log, Job_Util_Log_Link, and Item_Prod tables will take on the order of hours to migrate. Prior to migration, the post-install Configurator application will provide a rough estimate of the time required.
The current database structure has views that include the same columns as the tables prior to MES version 6.0 so that legacy queries will not break. However, the data will be slightly different as there are no longer extra records during shift changes.
Starting with MES 2020 (version 6.2), an additional link table is included and the views are updated to use this new table. The migration populates this new link table, so migrations from 6.0 and 6.1 to version 7.0 also take significant time.
Migration of MES 2020 or earlier versions will move all Data_Log_16 and Data_log_48 table data to the Data_Log table. If you previously ran the optional scripts from MES 2020 to copy the data to this new table, then you should delete the duplicate data from the Data_log_16 and Data_log_48 tables prior to upgrading so that there isn't duplicate data in the Data_Log table after migration.
Migration of MES 2020 or earlier versions will not include any shift exception definitions as the approach for defining these has changed. Migration of shift schedules should be reviewed in close detail. You should determine whether or not a better approach exists with the new functionality added in MES 2023 for shift patterns with effectivity dates and entity-specific shift exceptions.
Migration of MES 2023 or earlier versions will require that no other connections are active against the MES database as the migration enables read committed snapshot isolation on the database.

Note: You can only perform a database Restore from an archive that was created with the version of MES that you are currently running. Restores using an archive from a previous version of MES are not supported and might fail.

For more information on upgrading, see the MES Installation Guide and online help.

Resolved issues

This section describes important resolved issues in MES 2023 R2, listed by their Change Request number.

IMS	Description
Bug 2150752	Connection errors continue to be logged every few seconds when MES Middleware is down and MES Objects are undeployed. These end when MES Middleware is restarted or the engine is undeployed.
Bug 2400345	In MES Operator, when setting the production lot on the Production tab, the storage location is different than configured in the bill of material (BOM).
Bug 3853535	Cannot split utilization events when an entity is under a site with different time zone than the middleware.
ENH 2883623	MES Client update to define entity spares.
ENH 2930113	MES Client update to assign certifications to all users within a user group.
ENH 3022630	Add Spare 1-4 fields in MES stateless API JobExec.CreateWOfromProcess.
ENH 3024753	MES Client update to define an entity standard item in OEE settings.
ENH 3491728	WO.Update does not have production schedule ID parameter.
IMS 1809089	Related to HF L00152505: sp_BOM_Item_Oper_Link_Chk improvements when there are many BOM versions and items linked to a process.
IMS 1932592	Easily monitor entity actual vs licensed usage counts.
IMS 1972207	MES Client throws misleading error when there is a mismatch between the collation of the MES database (MESDB) and SQL Server.
IMS 2147744	MES Web API for Utilization Grid does not populate some fields such as raw_reas_cd, failure, spares, and categories.
IMS 2156935	Reducing item consumption to zero should not remove record until enterprise resource planning (ERP) quantity is also reduced to zero
IMS 2175840	Continuation of IMS 2147744: Changing raw_reas_cd does not get recorded in database.
IMS 2178106	System Platform (SP) IDE 2023 becomes sluggish and unresponsive when creating many instances of MES Operations Capability Object (OCO) with the Production Event Module (PEM) enabled and when running Entity Model builder. Fixed in SP 2023 Patch 1.
IMS 2220865	Request to add @P_job_start_utc as parameter to standard sp_U_Job_Exec_StartJob_Qty.
IMS 2297972	Shift exceptions that span more than one shift are not returned correctly in either shift_to_go or the API. Fixed in MES 7.0.
IMS 2307214	QualityCharacteristicDetail report displays OOC incorrectly depending on filter applied.
IMS 2322933	Related to HF 2156935: Using sp_U_Item_prod to set quantity to zero leaves job.qty_prod unchanged.
IMS 2327370	Web API call to custom stored procedure (SP) replaces date parameter with null.
IMS 2369254	MES Client is very slow in navigating jobs within a work order (WO).
IMS 2409234	Showing statistical process control (SPC) Spec limits on the SPC Chart rounds spec limits to whole number and shows lines in range chart.
IMS 2410622	MES Client option to view route map does not show quantity information.
IMS 2424223	Migration from MES 4.5 to 6.2 generates datatype conversion error on job_event.value1 if it includes text in migration from 5.3 to 6.0 script.
IMS 2425425	Error: last_edit_comment must be no longer than 254 characters.
IMS 2426422	The sublotNo and fgSublotNo parameters in EnProd.ItemCons.GetConsByFilter are not used.
IMS 2481090	Cannot split an inventory record into two separate sublots.
IMS 2493235	Related to HF IMS 577706: Undeploy/deploy of OCO causes rolling counters to improperly increment.
IMS 2495361	Continuation of HF 1882057: vw_prod_events is slow.
IMS 2501996	Related to IMS 2297972: Long duration shift exceptions starting in the past are not reflected in shift_to_go.
IMS 2517204	Duplicate key error when setting the produced item for a cloned process.
IMS 2536303	With system parameter set to apply late production counts to last job that ran on entity, these counts cannot later be reduced with AddProdPostExec.
IMS 2543087	Cloning a work order with split jobs incorrectly sets required quantity.
IMS 2559371	Spare Fields from Storage_Exec are trimmed to 80 characters when copied to Storage_Ent_Transfer.
IMS 2599781	With hundreds of User Groups MES Client is slow to load the User Groups and Users editor.
IMS 2601979	Continuation of HF 1882057: vw_prod_events is slow.
IMS 2608313	MES Client crash when opening editors with specifications where OS decimal separator is different from data in database (e.g. spec is saved as 4.5 and OS has comma decimal separator).
IMS 2722854	Related to IMS 2501996: Slowness in Daily task causes shift changes to be missed (recorded as shift 0).
IMS 2724236	Qty_per_parent_item field in Job_bom is always Zero for BOM position 0 (produced item).
IMS 2813964	In time zones with non-zero minute offsets from UTC (e.g. India), AddProdPostExec is incorrectly setting _local minutes to zero (_UTC times are correctly set with minutes as zero).
IMS 2855449	Inserting a new BOM item in a process is timing out.
IMS 2860376	Identical Job Execs parameter overwritten when using an OCO and UCO at different hierarchical levels.
IMS 2868190	HF 2608313 for 6.2: MES Client crash when opening editors with specifications where OS decimal separator is different from data in database (for example, spec is saved as 4.5 and OS has comma decimal separator).
IMS 2872468	Cannot edit a process if checked out user has different case than logged in user. MES Client is case-insensitive, but the process check is case sensitive.
IMS 2880973	MES Web API 3 - Job Start and Job End API does not consider the act_start_time_utc / act_end_time_utc parameter but always updates the current time.
IMS 2888756	HF IMS 2147744 and 2175840 for MES 7.0: Changing raw_reas_cd does not get recorded in database.
IMS 2897804	When splitting inventory without specifying a new unit of measure (UOM), the new inserted row is not setting the UOM.
IMS 2899695	Cloning a WO having Job_Bom_Subst records results in 'Violation of Primary Key'.
IMS 2922157	Running APR with dense data in a single hour gives error: 'Error executing DBMaint XML Command for Job [Archive_Purge_Job_Monthly] Table [WO]: Execution Timeout Expired'.
IMS 2931309	Prod.ItemProd.UpdateSpecific incorrectly updates item_inv table by the new quantity instead of the difference between the new and old quantity.
IMS 2957544	QM Spec Characteristic Targets and Limits are restricted to 4 decimals instead of using characteristic's number of decimals.
IMS 2970304	NoLock hint missing on Ent table trigger (tg_ent_aft_upd).
IMS 2973474	Regional settings causes DirectAccess Web API decimal separator issues when using a specific user account for the MES middleware.
IMS 2984264	Cloning a job from a WO times out and throws MES Client 'Unexpected Error'.
IMS 2999694	aaStorageExec.Addinv method doesn't insert spare3 and spare6 for 2 of the 3 overloads.
IMS 3001197	Unable to split utilization event in MDM Job Management form.
IMS 3018141	MES stored procedures that update/insert MES attributes in tables use dynamic SQL statements limited to 4000 characters.
IMS 3030791	OCO Download specs command is stuck in downloading when trying to end one job and start a new job.
IMS 3037051	Continuation of IMS 2855449: Inserting a new BOM item in a process is timing out.
IMS 3061128	Performance enhancements for ending long running jobs (job_hour_history updates) and get bottleneck entities lines with many entities.
IMS 3065230	When security mode set to OS User, handle leak and lsass.exe memory leak.
IMS 3189520	Qty_per_parent_item field in Job_bom is always zero for BOM position 0 (Produced Item) when no BOM versions are defined.
IMS 3238578	MES Middleware will not start after monthly renewal of certificate in PCS.
IMS 3242898	Intermittent failure of MES WebAPI V3_Prod_Jobs_Start due to selecting available job position.
IMS 3258410	MES Stateless API call from ASPX page in Work Tasks (64-bit) fails with error: 'Access to the registry key 'HKEY_LOCAL_MACHINE\Software\Wonderware\MES\MWClientCfg' is denied.'.
IMS 3261306	Job_attr row_id column is defined as 32-bit integer and customer will soon exceed the maximum value for row_id. Updated row_id of all attribute tables to BigInt (64-bit).
IMS 3267555	With multiple entities at an operation and a high precision decimal is used for for the 'Initial Production % Required' setting, the WO required quantity and the final operation quantity are miscalculated.
IMS 3340073	Adding an item to produce to a process times out.
IMS 3356616	IMS 2493235 for MES 6.2 Patch 2: Undeploy/deploy of OCO causes rolling counters to improperly increment.
IMS 3357981	Job starting and required quantities not calculated correctly for create WO from process based on reject quantity percentage.
IMS 3381278	Minutely task to kill stale sessions generates error on notes column about not supporting NULL.
IMS 3403627	Utilization by Entity report includes wrong data when duplicate shift data exists. Need to filter out aaObsolete records in vwShifts view.
IMS 3410429	Starting a job clears out future samples and doesn't recreate them for calendar / shift samples on multi-job exec entity.
IMS 3415035	Create work order from process times out with large number of BOMs.
IMS 3432079	Continuation of IMS 3242898: MES WebAPI V3_Prod_Jobs_End deadlock issue.
IMS 3445781	MES Client becomes unresponsive when clicking 'Expand all' on the produced item with complex BOMs in 'Configure Operation Output'.
IMS 3451110	MES Client system parameter for 'Cut-off time in days to limit the number of samples…' cannot be edited.
IMS 3477928	Error Parameter @expiry_date was supplied multiple times when calling sp_u_item_prod to update sublot.
IMS 3480578	MES Client and IDE does not show all Util reasons / groups when more than 5,000 are defined.
IMS 3495481	SP_U_Labor_Exec_CloseLabEvents incorrectly calculates UTC time from provided event time.
IMS 3510946	QM Specs from MES Client does not show all characteristics when no filter applied and more than 5,000 are defined.
IMS 3513771	sp_I_Item_Inv_Add incorrectly adds inventory when item UOM conversion is defined with the same to_uom and from_uom.
IMS 3514150	Related to HF 2294559 and IMS 1679737 Shift Change process timing out - slow sp_U_Ent_DoAutoShiftChanges with additional stored procedure updates
IMS 3618710	MES Client timeout creating new BOM Version with many other BOM versions (even with HF 2482803).
IMS 3629927	Execution time of sp_BOM_Item_Oper_link_chk grows exponentially based on the number of existing BOM versions and when new BOM version has preferred version set.
IMS 3671851	GetByKey method missing from MES Stateless API JobRoute Class.
IMS 3692427	UCO with hundreds of Raw Reason Codes slow to check in.
IMS 3724464	PEM in error status (-101) after rebooting the machine with a deployed OCO.
IMS 3744365	During database upgrade provide warning if BOM version effectivity dates are out of range.
IMS 3749610	Related to IMS 3037051: Executing sp_BOM_Item_Oper_link hundreds of times in transaction control timing out.
IMS 3767082	IMS 3065230 for MES 6.1: When security mode set to OS User, handle leak and lsass.exe memory leak.
IMS 3768303	The job generated by PEM function is always in "Ready" Status.
IMS 3773869	IMS 3065230 for MES 7.0: When security mode set to OS User, handle leak and lsass.exe memory leak.
IMS 3787903	Cannot restore an archive with wo and lot as the assigned_lot file is missing header rows.
IMS 3798240	MES Client does not restrict editing of Job States, File Extensions, or Labor Categories/Departments based on user privileges.
IMS 3877903	Cannot restore an archive with wo and lot as the assigned_lot file is missing header rows.
IMS 3900260	Middleware proxy connection issues with customized port and firewall (Cannot block port 80).
IMS 3915223	Very slow login after changing security settings in MS AD.
IMS 3933863	aaMES.EnProd.aaStorageExec.AddInv() fromEntId parameter value not populating in item_transfer.
IMS 4230122	Related to IMS 3510946: MES Web Portal not showing all util reasons, items, etc when more than 5,000 are defined.
L00143414	Launching of the Operator following a fresh install fails with an error dialog that states "Unable to load DLL 'PEGRP32C.DLL'. This is an intermittent issue that can be resolved by rebooting the machine after installation. Reboot is now required after installation.
L00144202	After failover, selecting an OCO object with PEM enabled in the Object Viewer logs a bunch of error messages from the BaseRuntimeComponentServer component when reading a PEM extended attribute's data type property.
L00153087	SampleViewer .NET control does not honor RequireEntityLogOn property when used in an InTouch Frame window. Fixed in InTouch.
L00154309	Modifying a deployed OCO or SRO that adds or removes an object generated attribute causes errors to be logged every scan (object reference not set) even though the object still functions correctly. Request AOT HF L00154664 for System Platform 2023.
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

This section describes important known issues in MES 2023 R2, and in System Platform that affect MES.

System Platform 2020 and MES 2020 upgrade issues

If you are upgrading to MES 2023 R2 from a system running MES 2020 with System Platform (SP) 2020, a direct upgrade from SP 2020 to SP 2023 R2 SP1 Patch 2 will prevent successful migration of your MES SP Galaxy (Known issue: 3878221).

To upgrade a system setup that implements MES 2020 and SP 2020 to MES 2023 R2 and SP 2023 R2 SP1 Patch 2, do the following:

Upgrade SP 2020 to SP 2020 R2 SP1; do not launch or connect to the SP IDE.
Upgrade SP 2020 R2 SP1 to SP 2023 R2 SP1 Patch 2; do not launch or connect to the System Platform IDE.
Upgrade MES 2020 to MES 2023 R2.
Configure MES components, as required.
Restart the machine.
Launch the SP IDE, and open the SP Galaxy you wish to migrate.
When prompted, select Yes to proceed with Galaxy migration.

System Platform 2020 R2 SP1 and MES 2020 Patch 2 upgrade issues

If there are issues when upgrading from System Platform 2020 R2 SP1 Patch 2 and MES 2020 Patch 2 , first ensure that you follow the correct sequence to upgrade your system:

Upgrade System Platform to 2023 R2 SP1 Patch 2; do not connect to the System Platform IDE.
Upgrade MES to 2023 R2.
Start the System Platform IDE to migrate the galaxy.
Follow MES steps in the MES Installation Guide or help to import updated MES .NET Controls, application objects, and scripts.
Following completion of the upgrade, perform a reboot.

If there is still an issue with deploying the objects or View app with errors related to the ArchestrA.Visualization components, try restarting the AVEVA Service Manager service.

Regarding IMS 2075532 (Unable to deploy the remote Windows platform once System Platform 2020 R2 SP1 is upgraded to System Platform 2023): If, during deployment, an error stating that the remote node's user ID or password doesn't match the GR node, try re-registering the transport component on the remote node as described below:

In a command prompt, go to C:\Program Files (x86)\ArchestrA\Framework\Bin.
Run aaDCOMTransport.exe /REGSERVER.

MES BI Gateway Reports: Detection of utilization event deletion or modification

The MES BI Gateway Reports model cannot detect utilization event deletion or duration modification. The BI Gateway service is dependent upon a detection method for notification of changes to records. The MES model uses the last_edit_at field in the MES database for its detection method. When a utilization event is deleted by modifying an existing event's duration or inserting a new event to cover an existing event, there is no option to notify the BI Gateway Service. Similarly, if an event's duration is changed but not its start time, the last_edit_at column is not modified since the duration is not stored in the new Util_History table, resulting in no notification to the BI Gateway Service. There is no workaround for this issue.

Known issues for MES

The following table lists the known open change requests for MES, listed by their change request number.

ID	Description
Bug 3837303	If either AVEVA Historian or AVEVA OPC UA SERVER is selected as the SSL Certificate, the MES Web Portal component cannot be successfully configured. To configure the MES Web Portal component, select either the ASB certificate or a custom (FQDN) certificate.
Bug 3767661	Uninstalling the last AVEVA product from Control Panel does not remove the suite level GUID causing a reinstall to show the modify/repair option. To address this issue, use setup.exe to uninstall AVEVA products.
IMS 2173510	When MES is installed in a system with System Platform, running the MES Repair operation will cause you to be prompted to specify the location of the installation media. Use the Browse button to navigate to and select the MES setup.exe file in the MES installation software.
IMS 2517970	No records are purged from Lot table if expiry_date is NULL.
IMS 3882730	Random duplicate calendar frequency samples.
IMS 3933505	MES Web Portal shows "Error Occurred" in the UI but no error at the back end and needs page refresh to see the update.
IMS 4105744	Create Work Order from Process has inconsistency in job and work order quantities when quantity has 2 decimals and item configured for 1 decimal (API called with x.43 yields wo.reqd_qty = X.4 while job.reqd_qty = X.5).
L00131983	Trying to start a job on more than one machine causes an error inserting into the Prod_Rate_History table on very specific scenarios.
L00132902	If multiple items to be produced in a process have a common sub-item to be produced in BOM #1 and BOM #2, then every time that common sub-item is marked as "Set as Produced Item" on BOM #1 for an operation, the same sub-item will be marked as produced on that operation for BOM #2.
L00135404	With the OS language set to Russian, the Entity OEE targets set in MES Client will generate a validation error but still save correctly.
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.

Known issues for System Platform and common components that affect MES

The following table lists the known issues for System Platform that affect MES, listed by their identifier.

ID	Description
Bug 3703022	If you repair MES from the Windows Control Panel Add or Remove Programs (ARP) dialog, the Operations Control Management Console (OCMC) log viewer is also repaired. During this repair, the registry permissions are removed and not replaced. After the repair, the registry values appear without the required permissions, and MES messages no longer display in the log viewer. To address this issue, do one of the following when repairing MES: Perform MES repairs using Setup.exe. If you repair MES using the ARP dialog, also repair the OCMC log viewer.
Bug 3878221	If you are upgrading from MES 2020 with System Platform (SP) 2020 to MES 2023 R2, a direct upgrade from SP 2020 to SP 2023 R2 SP1 Patch 2 will prevent successful migration of MES SP Galaxies. To address this issue, upgrade to SP 2020 R2 SP1 from SP 2020 first, and then from SP 2020 R2 SP1 to SP 2023 R2 SP1 Patch 2. Next, upgrade MES 2020 to MES 2023 R2, configuring applicable MES components. Finally, restart the machine and launch the SP IDE. Open the galaxy, and confirm that you want to migrate the SP Galaxy when prompted.
Bug 3923466	When installing MES 2023 R2 on a system that has System Platform 2023 R2 SP1 Patch 2 and Platform Common Services (PCS) (version 8.1.2), the MES installer will behave as though the MES install is an upgrade and not a new installation. As a result, the MES installation Select Roles dialog will not be displayed. To address this issue, continue with the MES installation, using the Features and Components dialog to manually select the specific MES components to install.
Bug 4300311	For systems where System Platform (SP) 2023 R2 SP1 Patch 3 is installed, the silent configuration will log 'missing assembly' errors similar to the following and subsequently fail. Could not load file or assembly 'file:///C:\Program Files (x86)\Wonderware\MES\ConfiguratorPlugins\ PCS.Extensions.Configuration.Registry.dll' or one of its dependencies. The system cannot find the file specified. To address this issue, complete the following procedure before performing the silent configuration: Back up the configurator.exe.config file from the C:\Program Files (x86)\Common Files\ArchestrA location¹. Copy the provided version of the configurator.exe.config file from C:\Program Files (x86)\Common Files\ArchestrA\MESConfigBackup¹ to the location noted in step 1. Proceed with the silent configuration. Once configuration is successfully completed, restore the backed up configurator.exe.config file to the location noted in step 1. ¹If the Program Files(x86) is installed to a non-default drive, make sure to use the correct drive/path.
Bug 4300331	For systems where System Platform (SP) 2023 R2 SP1 Patch 3 is installed, the MES uninstallation will log 'missing assembly' errors similar to the following. Could not load file or assembly 'file:///C:\Program Files (x86)\Wonderware\MES\ConfiguratorPlugins\ PCS.Extensions.Configuration.Registry.dll' or one of its dependencies. The system cannot find the file specified. To address this issue, complete the following procedure before performing the uninstallation: Back up the configurator.exe.config file from the C:\Program Files (x86)\Common Files\ArchestrA location¹. Copy the provided version of the configurator.exe.config file from C:\Program Files (x86)\Common Files\ArchestrA\MESConfigBackup¹ to the location noted in step 1. Proceed with the uninstallation. Once uninstallation is successfully completed, restore the backed up configurator.exe.config file to the location noted in step 1. ¹If the Program Files(x86) is installed to a non-default drive, make sure to use the correct drive/path.
IMS 3527443	In SP 2023 R2 SP1, Entity Model Builder fails to create an entity with a long name (up to 128 characters) when the first 80 characters match another already exported object. The MES entity name limit is 80 characters. Work around is to ensure the first 80 characters are unique.
IMS 3926774	During failover, if PEM status is in BUSY state, then it will be stuck in BUSY state on secondary node until a redeploy.
IMS 3983816	UCO Editor is slow with 90K utilization reasons.
L00138837	AppEngine can crash due to the calls made to the FactMES API dlls even when using try/catch. Specific to Nullable data types. Will not be fixed in System Platform, so recommendation is to continue using the wrapped MES API DLLs in System Platform scripting.
L00158082	Importing of the MES folder for OMI can generate a warning during the import and log a message that it was unable to find referenced file system.windows.forms. Instead of importing the folder, MES 2023 includes an MESOMIControls.aapkg file that does not generate any warnings.

Security information and guidance

AVEVA is committed to releasing secure products. This section is intended to provide relevant security-related information to guide your installation or upgrade decision.

AVEVA proactively discloses aggregate information about the number and severity of security vulnerabilities addressed in each release. The table below provides an overview of security issues mitigated and their relative severity based on standard scoring.

Security vulnerabilities mitigated

The following vulnerabilities were identified for mitigation in this release.

Component

Version

CVE or Reference

CVSS

Mitigation

IdentityServer3.AccessTokenValidation

2.14.0

CVE-2017-12677

6.1

MES uses IdentityServer in its Web API, however MES Web API does not serve pages, therefore the product is not directly exposed to this vulnerability.

Microsoft Web Deploy

3.5

CVE-2025-53772

8.8

Prior to installing MES, complete the following:

Download Web Deploy v4.0 (Version 10.0.2001, published August 13, 2025) from the official Microsoft download site. The installer filename is webdeploy_amd64_en-US.msi.
If you have an earlier version of Web Deploy installed, uninstall it.
After removing the previous version, install Web Deploy v4.0.
Once Web Deploy v4.0 has been installed, proceed with the MES installation.

MES documentation

The MES 2023 R2 documentation set includes the following:

ReadMe

Information about software and hardware requirements, known issues, licensing, and documentation.

MES Deployment Guide

Guidance on deploying a MES solution.

MES Installation Guide and online help

Information about installing MES applications.

MES Client User Guide and online help

Information about customizing and maintaining the plant floor information.

MES Dynamic Routing User Guide

Information required to set up dynamic routing of operations through a process defined in MES.

MES .NET Controls Developer Guide

Information about the properties and methods of the MES .NET controls for use in custom applications and System Platform graphics.

MES Application Object (OCO, UCO, SRO) Help

Information about run-time behavior, configuration, and run-time attributes of UCO, OCO, and SRO application objects. This help is accessed from the Object Editor Help menu in the System Platform IDE.

Operation Capability Object (OCO) User Guide

Information about installing, configuring, and using the Operations Capability Object to track production transactions against equipment.

Sample Recording Object (SRO) User Guide

Information about installing, configuring, and using the Sample Recording Object to collect and store values for samples.

Utilization Capability Object (UCO) User Guide

Provides information about installing, configuring, and using the Utilization Capability Object to collect equipment performance data.

MES Entity Model Builder User Guide

Information about creating entities from the System Platform equipment model.

MES Database Reference Guide

Information about the MES database tables and relationships.

MES Stateless API Reference online help

Information about using the Stateless API within the System Platform IDE to develop and customize System Platform scripts.

MES Stateful API Reference online help

Information about using the Stateful API within the System Platform IDE to develop and customize System Platform scripts.

MES Web API V1 Reference online help

Information about using the MES Web API V1 to develop custom applications.

MES Web API V3 Reference online help

Information about using the MES Web API V3 to develop custom applications.

MES Operator User Guide and online help

Information about executing production processes at the plant floor using the Operator application.

MES Web Portal User Guide and online help

Information about using the web browser-based MES Web Portal to customize and maintain the MES system and execute jobs at the plant floor.

MES Middleware and Cloud Integration User Guide

Information about how to configure the MES middleware and what regularly scheduled tasks it performs in the MES system. In addition, the guide provides information about how to use middleware extensibility hooks to perform custom actions before or after a specific middleware event is executed. Also, the guide provides information about the MES curator service configuration and tasks it performs.

MES BI Gateway Reports User Guide

Information about running and viewing MES BI Gateway Reports.

The MES 2023 R2 product library includes a set of Portable Document Files (PDFs) located in the Docs folder in the MES installation folder. You need Adobe Reader installed on your computer to view the MES documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site.

After installing Adobe Reader, double-click a PDF file to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.

The MES installation instructions are located in the root folder of the MES installation folder as a PDF file and an online help file. You can view these instructions by clicking Help as you start the MES installation procedure.