Get started with AVEVA Model Driven MES

In the Manufacturing Execution System (MES) model-driven application content approach, a MOM/MES solution is vertically integrated with two sets of models:

• An MES model, composed of procedure-centric workflow templates in Work Tasks

• If capturing automated data and events, a real-time model, composed of equipment-centric templates in System Platform

These two models work together to provide overall monitoring and control of manufacturing operations and processes.

The model-driven approach simplifies the development of MOM/MES solutions by:

• Shifting development focus from scripting/programming to configuring/modeling.

• Separating MES business logic from automation scripting, and making that business logic easier to read, maintain, and document.

• Developing operational process-oriented workflows that can coordinate equipment, systems, and people across the enterprise.

• Making it easier to understand and address variability across sites in the enterprise by expressing the MES business logic in visual, self-documented workflows.

• Providing change management capabilities that pulls all UI and business logic into application packages that can be versioned and transferred across sites.

• Providing a robust and extensible platform to develop modern enterprise solutions based on a HTML5 web UI.

It’s also important to understand the following points about a MES model-driven application content:

• The model-driven content is not a product. Rather, it is a new way to develop and deliver MOM/MES solutions, based on existing mature standard products.

• The model-driven content does not replace System Platform. System Platform is still the foundation of the AVEVA plant floor integration layer, including services such as device integration, alarms, historian, and so on.

• The model-driven content is not a real-time HMI. Some customers will only need Work Tasks Enterprise Console to implement a solution. However, for customers that need a real-time HMI, the solution will require a hybrid approach that is some combination of System Platform and Work Tasks.