Step Execution
- Last UpdatedOct 15, 2025
- 1 minute read
The Step Execution use case brings together a focused set of MES functionalities to support operators in managing and executing production steps efficiently. It is designed to streamline the execution process by providing a task-driven interface that enables clear visibility and control over each step within a job sequence.
The Step Execution use case enables the operator to view step details, start, suspend, or complete steps.
This use case is integrated with the Job Execution use case. Step tasks are automatically generated when a job is RUNNING and disappear when the job is SUSPENDED. Steps are executed in a predefined sequence, and a job can only be marked as COMPLETED once all associated steps are completed.
The Step Execution use case is typically integrated into the Operator console to be accessible from the Task list.
Note: This documentation describes the predefined AVEVA standard Step Execution use case (version 1.02) without considering any additional customization.
This Step Execution use case requires the installation of the following MES module:
-
Job Management Module (JM)