What is AVEVA MES? Modules, integrations and alternatives
AVEVA MES is a manufacturing execution system from AVEVA, the industrial software company whose portfolio includes the former Wonderware products. It manages production execution, material tracking, quality and performance on the shop floor and integrates with AVEVA System Platform and enterprise ERP.
Also known as: Wonderware MES, AVEVA Manufacturing Execution System, AVEVA MES Operations
AVEVA MES descends from the Wonderware MES line and is sold within AVEVA's industrial software portfolio, alongside products such as System Platform for supervisory control and a historian for process data. Older documentation and job postings still refer to it as Wonderware MES, which is useful to know when searching for support material and skilled resources.
The product addresses the layer between ERP and the control systems. It receives production orders, dispatches work, tracks material and equipment states, captures quality results, and reports performance measures such as OEE and downtime. It is commonly used in discrete and batch-oriented manufacturing, including food and beverage, consumer goods and automotive suppliers.
Because it shares an ecosystem with System Platform and the AVEVA historian, it is most natural where those are already the SCADA and data layer. Plants on different SCADA vendors can still use it but should plan more integration work. As with any MES, much of the value depends on process design and data discipline rather than the software alone.
Modules and capabilities
Operations management
Manages production orders, dispatch and execution of operations across lines and work centers.
Performance and OEE
Calculates availability, performance and quality measures and tracks downtime and loss reasons.
Quality management
Captures in-process checks and results and supports holds and nonconformance handling.
Material and genealogy tracking
Tracks lots and consumption for traceability and recall support.
Equipment and resource tracking
Maintains equipment states and resource availability from shop floor signals.
Integration to ERP
Exchanges orders, confirmations, and material movements with enterprise systems.
Integrations and data access
SCADA and data layer
Integrates with AVEVA System Platform and the AVEVA historian for equipment signals and process data.
ERP
Connects to ERP such as SAP and Oracle for order download and confirmation, typically via messaging or web service interfaces built during implementation.
Databases
Data resides in a relational database, which supports reporting and external analytics when access is permitted.
Industrial protocols
Equipment data is generally reached through the SCADA layer using OPC and driver-based connectivity.
Standards
Aligned with ISA-95 concepts for the boundary between enterprise and control systems.
Strengths
- Natural fit with System Platform and historian in AVEVA-based plants.
- Solid OEE, downtime and performance tracking capability.
- Configurable without writing custom code for every change.
- Established partner and integrator ecosystem from the Wonderware era.
Limitations
- Naming and packaging changes over time can make documentation and version identification confusing.
- Heavily Windows and on-premise oriented compared with newer cloud-native MES products.
- Implementation requires specialist skills and careful process design.
- Plants on other SCADA ecosystems face extra integration effort.
Where AI helps AVEVA MES users
- - Explaining OEE movements by combining downtime codes, shift data and order context in plain language.
- - Natural-language lookup of lot genealogy and quality results for investigations.
- - Summarising shift performance and recurring loss reasons for supervisors.
- - Matching MES confirmations against ERP orders to find discrepancies.
- - Private retrieval over SOPs and maintenance notes so operators get grounded answers on site.
Evaluating AVEVA MES? Check these
- Identify exactly which AVEVA MES modules and version are proposed, and their support lifecycle.
- Confirm how the MES will use your existing SCADA and historian rather than duplicating them.
- Define master data ownership between ERP and MES before design starts.
- Check ERP interface templates and who maintains them post go-live.
- Validate performance under your expected event volume with a pilot line.
- Review regulated-industry validation support if relevant.
Common alternatives: Siemens Opcenter Execution, Rockwell FactoryTalk ProductionCentre, Critical Manufacturing MES, DELMIA Apriso, Tulip, Ignition.
Frequently asked questions
Is AVEVA MES the same as Wonderware MES?
AVEVA MES descends from the Wonderware MES product line. After Wonderware software was brought into the AVEVA brand, the MES products were renamed. Older manuals, training and support content may still use the Wonderware name, so search both when looking for documentation or experienced consultants.
What does AVEVA MES do?
It executes production between ERP and the control layer. It dispatches orders, tracks material and equipment states, captures quality data, and reports performance such as OEE and downtime. Results and consumption flow back to ERP, and equipment signals typically arrive through System Platform or comparable connectivity.
Does it require AVEVA System Platform?
It is designed to work closely with System Platform and the historian, and that combination is the most natural. It is not meant to be an isolated tool, but plants using other SCADA can still connect equipment data. Expect additional integration effort if you are not on the AVEVA stack.
Which ERP systems can it connect to?
It is commonly integrated with SAP, Oracle and other ERP through messaging or web service interfaces. These integrations are generally built during implementation, so confirm available templates, the owner of ongoing maintenance and how master data such as routings and materials will be synchronised.
Can AI work with AVEVA MES data?
Yes, usually through read-only access to its relational database or reporting interfaces, feeding a private query layer. Practical cases include OEE explanations, genealogy lookups and ERP reconciliation. Writing back should require human approval and respect existing roles, validation needs and audit trails.
Running AVEVA MES?
We add AI, chat, automation and integrations to the systems manufacturers already run, on-prem if needed.
Get a free assessment