DeltaV Batch configuration applications

DeltaV Explorer is used to define classes (for process cells, units, equipment modules, control modules, and phases) in the Batch Library. It is also used to create areas, process cells, unit modules, equipment modules, and control modules. Phase classes can be created in the DeltaV Explorer and the logic written in Control Studio. Recipes can also be created in DeltaV Explorer and the recipe logic written in Recipe Studio.

In batch applications, Control Studio is used to configure the phase logic. Each phase class contains a pre-configured state transition diagram. The configuration engineer defines the logic or the five active states (running, stopping, aborting restarting, and holding) and for failure monitoring. This is done by creating a sequential function chart (SFC) for each active state and a function block diagram for failure monitoring. Control Studio is also used to create the logic for control modules (typically in the form of command-driven or state-driven algorithms). Several algorithm types are available for defining the logic for control modules and equipment modules.

Recipe Studio is used to create and modify the recipes in the batch process, specifically, the procedures, unit procedures, and operations. This is done by creating a PFC (Procedural Function Chart) that consists of steps, transitions, and a termination. Recipe Studio provides graphical configuration tools similar to those in Control Studio.

Recipe Simulator allows you to test recipe configurations before phase implementation. It runs through procedural logic without executing the real phases. You can model and test your equipment configuration, equipment arbitration, phase interactions, and recipes without affecting any real-time processes.

Batch Executive is the application that executes recipes in DeltaV Batch applications. It manages the procedural logic, coordinates phase communications, and allocates equipment. It downloads phase parameters to the phase logic and uploads report data from the phase logic. It sends recipe and phase status information to the Batch Operator Interface. The Batch Executive also collects and records batch events in recipe journal files that may be viewed at the Batch Operator Interface and used by the Batch Historian to build its database.

The Batch Operator Interface is the graphical interface used by the operator to perform most batch-related functions. Using the Batch Operator Interface, an operator can create and schedule batches for execution, manage batch equipment, modify batch execution online, and view event journal information—all from one interface. The operator can switch back and forth between the operator environment and the Batch Operator Interface.

Operators interact with the process control system through one of these operator applications, which are the primary interfaces used to monitor and control the process equipment.

The Batch Historian provides automated collection of recipe execution data from the DeltaV Batch Executive journal files and process management event data from the DeltaV Event Chronicle. Operators can view the data using the Batch History View application.