Andon Execution

The Andon Execution use case brings together a set of real-time communication tools to support operators in requesting and managing help during production. It’s designed to streamline issue escalation and resolution by enabling structured, bi-directional communication between the person raising an issue (the requestor) and the person assigned to resolve it (the receiver).

The Andon Execution use case enables the operator to:

• Raise Andon requests for production, maintenance, safety, quality, or general issues.

• Define issue details and location using guided dropdowns.

• Track the status of raised Andons (e.g., NEW, ACKNOWLEDGED, RESOLVED, NOT RESOLVED).

• View and respond to feedback through dedicated buttons and history logs.

• Close the communication loop by marking issues as resolved or requesting further action.

The Raise Andon task (one part of the Andon Execution use case) belongs to the Command task type in the Operator console. In contrast to other typical task types like job tasks, quality tasks, or downtime tasks, the Command task type is used on demand when required by the operator. Available command tasks are accessible in the task list by filtering the list for the Command task type.

Note: This documentation describes the predefined AVEVA standard Andon Execution use case (version 1.02) without considering any additional customization.

This Andon Execution use case requires the installation of the following MES module:

• Andon Module (AM)