The DeltaV Batch Executive

The DeltaV Batch Executive consists of the Batch  Manager service, the Batch Runtime Server, and the individual batch runner applications. One instance of a batch runner is created for every running batch. Each batch runner is responsible for taking the batch through all its states and for communicating to the Batch Manager for equipment arbitration and any other inter-runner or client-based communications. The Batch Manager is responsible for managing the batch runners. It also sends information from the runners to clients (such as the Batch Operator Interface and Campaign Manager Server) that require run-time data.

In the tutorial, we will configure the Batch Executive on the same workstation on which we are doing configuration and operation. However, optimal performance of the Batch Executive is achieved by installing the Batch Executive on its own Application Station. Consult your Emerson representative before installing a Batch Executive on a workstation other than an Application Station.

Options you need to configure when enabling the Batch Executive are:

Remove files older than (days) - sets the maximum number of days for which batch event records are stored in the .evt file.

Restart Behavior - sets the method for restarting the Batch Executive. Choices are:

• Query User - allows the user to select between Warm & Cold Restarts or Cancel the operation.
• Warm Restart - returns the Batch Executive to its last known state. Control recipes, manually controlled phases, and arbitration functions are returned to the state that existed prior to termination of the Batch Executive. The warm boot method is only used to recover batches and data after an unexpected loss of the Batch Executive.
• Cold Restart - starts Batch Executive with an empty batch list and with no resources allocated to the operator.

Hold propagation limit - sets the level to which a Hold propagates. The choices are Phase, UOP (operation), UPC (unit procedure), and BPC (procedure).

Allow manual phase history to be combined with other batch history - enables the ability to combine a manual phase's history with another batch's history (for example, with the 'parent' batch). When you start the manual phase you are given the option to select a batch (by batch ID) with which the manual phase history will be combined. You can also opt to not combine histories at this point.