Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Composable and Model Driven MES

Understand the Operator console

  • Last UpdatedOct 15, 2025
  • 3 minute read

The Operator console is created based on the AVEVA Task Driven User Interface (TDUI) approach. It provides automatically generated tasks for the shop floor operator to execute for the selected equipment the operator is working on (for example, a machine, vessel, unit, or production line).

A user receives context-related access to status information, tasks, and functions that are relevant to the role and activity they are executing. This enables them to execute use case-based production activities on the equipment—without needing to leave their console. This approach minimizes mouse clicks and navigation efforts, enabling intuitive and efficient access to all relevant information and use cases essential for daily production operations. Configurable context in this case may include what task is executed, the user's certification, what material is currently being produced, what equipment or line the user is operating, and other custom criteria.

The Composable MES Operator console showing the Produce use case details.

The Operator console is composed of the following elements:

Header

The Operator console header is the top section of the interface that provides essential, real-time context for the operator’s current work environment. It includes:

  • Equipment selection: A dropdown menu that allows the operator to choose the equipment (e.g., machine, line, vessel) they are working on. Selecting equipment dynamically updates the console with relevant data and tasks for that equipment.

  • Equipment status: A visual indicator showing whether the selected equipment is currently running or in downtime. Operators can also manually trigger or end downtime events directly from this field.

  • Configurable content area: A flexible space that can display context-related information based on the specific configuration of the MES solution. This might include production metrics, job progress indicators, or other role-specific data.

  • Optional tabs: Additional tabs can be configured based on the needs of the operation or the specific MES solution. These may include:

    • Job or work order management: For viewing or managing job-related data.

    • Performance dashboards: To display KPIs or production metrics.

    • Material handling: For use cases like material reception or kitting.

    • Supervisory functions: Limited access to management tools typically used in the Supervisory console.

      These optional tabs are defined during the solution configuration phase and can be tailored to match the operator’s role and responsibilities.

For more information, see Operator console header.

Task list

The task list that organizes access to different MES functions and use cases. This list is designed to streamline the operator’s workflow by grouping relevant tools and information in one place. This is a core component of the Operator console and is always present. It displays a list of active tasks for the selected equipment. Each task is linked to a specific use case, allowing the operator to take immediate action—such as starting a job, assigning downtime, or entering quality data.

For more information, see Operator console Task tab.

Use case details area

The use case detail area is the interactive section of the Operator console where operators execute tasks linked to specific MES use cases.

This configuration is managed through a central configuration table, ensuring that the operator sees only the most relevant and actionable content for their current task.

The use case detail area supports a wide range of MES activities—from simple job actions like start job or complete Job to more complex workflows such as material reception or quality checks.

For more information on the console, see Operator console use case details area.

For more information on the AVEVA standard available use cases, see the related Composable MES use case documentation.

TitleResults for “How to create a CRG?”Also Available in