Get started with the Step Execution use case

The Step Execution use case extends the Job Execution workflow by enabling operators to manage individual production steps within a job, offering a focused interface that supports step-level visibility, control, and execution.

Integration with the Job Execution use case

The Step Execution use case is closely integrated with the Job Execution use case. When a job enters the RUNNING state and has steps configured, the system automatically generates corresponding step tasks. These tasks appear in the Operator Console’s task list and are executed in the predefined sequence established during the job’s process definition.

Step configuration occurs during the work order setup phase, and each step is triggered automatically once the preceding step is marked as COMPLETED. If the job is SUSPENDED, the associated step tasks temporarily disappear and reappear when the job resumes. A job can only be marked as COMPLETED once all its required steps have been successfully executed.

Step Execution use case access

Launch the Step Execution use case UI by selecting a step task from the Operator console’s task list. This opens the dedicated Step Execution use case detail, which includes all the necessary functions for managing the selected step within a job. This use case consists of an integrated Step Execution Panel and an integrated use case detail area to launch the use case details linked to the step execution panel buttons.

Note: The example above shows the full content of the Step Execution use case detail which will be shown in the Operator console related use case detail area.

This use case detail consists of a use case specific panel bar and a use case specific use case detail area that launch linked use case details. The configuration of these context related panel buttons is similar to the workflow for configuring the panels for tab-related use cases like Job Management, Work Order Management, or Performance Management.

The Step Execution use case consists of:

Step execution panel: Provides panel buttons (e.g., Start, Complete, View Details) that are dynamically enabled or disabled based on the current status of the selected job. By default, these buttons link to predefined AVEVA standard use case details or can be configured to trigger processes via workflows. The link itself can be dependent on configured context. The use case details can be replaced by modified use case details depending on customer requirements.

For more information, see Execute step use case details.

Step use case details: The use case detail area is the interactive section for the user to execute MES use cases linked to the relevant panel buttons. The link between the panel button and the use case are configured based on several contextual factors such as:

• The current status of the production process

• The material being produced

• The specific equipment selected

• The role and identity of the operator

• Other custom context

  For more information, see Execute step use case details.

For detailed instructions on how to access the Step Execution use case from the Operator console, see Navigate the Step Execution use case.