Client components

The client components can run on non-server nodes and interact with the server components on the server nodes.

MES Client

MES Client is used to configure almost all aspects of the MES system, and interact with operational information. You can:

• Configure system utilization states, reason groups, and reason codes

• Configure users, user groups, privileges, entity access, and user certifications

• Configure languages

• Configure physical entities

• Configure shift patterns and schedules and assign them to entities

• Set up system-wide values such as job states, document types, defaults for file extensions, labor departments, and labor categories

• Configure General Parameters

• Configure items, BOMs, operations, and processes

• Configure archive, purge, and restore (APR) jobs for database maintenance

• Configure quality specifications, sample plans, and characteristics

• Create and manage work orders and jobs

• Set up data collection

• Store customer information and processing sales orders

For more information, refer to the MES Client documentation.

Application Objects

The Application Objects components include:

• The Operations Capability Object (OCO), which extends the System Platform IDE equipment model to trigger production events and log associated production data in the MES database.

• The Utilization Capability Object (UCO), which extends the System Platform IDE equipment model to monitor machine performance.

• The Sample Recording Object (SRO), which extends the System Platform IDE equipment model to monitor quality samples for an entity.

For more information about these objects, see Application objects.

Entity Model Builder

Entity Model Builder is a System Platform IDE extension. Therefore, the System Platform IDE must be installed before attempting to install Entity Model Builder.

You can use Entity Model Builder to perform the following tasks:

• Creating entities from your System Platform equipment model that use the UCO for configuring utilization/OEE support, the OCO for configuring production related entity support, and/or the SRO for capturing quality data.

• Exporting the existing System Platform users and roles to MES to create corresponding MES users and groups.

If you install Entity Model Builder, you must also install the MES Application Objects component and import at least one of these objects into a System Platform galaxy. Running Entity Model Builder without having an MES application object installed and imported is not a supported scenario.

For more information, refer to the MES Entity Model Builder documentation.

Operator

You can use MES Operator to control processes as an operator on the factory floor, such as:

• Executing jobs

• Claiming produced quantities and reporting consumption

• Entering data for steps, specifications, and the data logger

• Capturing machine utilization and labor data

For more information, refer to the MES Operator documentation.

.NET controls

The .NET controls are part of the client components’ user interface. You can use these controls as building blocks for System Platform graphical interfaces and Operations Management Interfaces (OMI).

When the .NET Controls component is installed, the .NET control files and the MESControls.aaPKG file are installed in the <MES program files path>\Wonderware\MES\Controls folder. The MESControls.aaPKG file, which contains all of the DLLs, can be imported into the System Platform IDE. The MES\MES OMI Controls folder can be imported as an OMI app or the MESOMIControls.aaPKG file can be imported.

Middleware proxy

The MES middleware proxy is required by client components installed on remote nodes to access the MES middleware service. These include, for example, nodes that have an application object (that is, a OCO, UCO, or SRO) deployed on them.