General steps for configuring a batch system

Although it is likely that these steps will be done in a different order when configuring an actual batch application, the following is a general outline of the steps needed for configuring aDeltaV Batch system.

1. In the DeltaV Explorer hierarchy, create the Plant Area under System Configuration/Control Strategies. Areas let you organize process cells and modules in a way that is meaningful for your application.
2. Create the process cell class in the Advanced Definitions Library in DeltaV Explorer, and drag the class into the Plant Area to create the Process Cell. The process cell must be defined before unit modules can be assigned to it.
3. Create the Control Module Classes for each device and control element. Configure the logic in Control Studio. 
4. Create the Equipment Module Classes. Create the named sets for command-driven and state-driven algorithm types. Add the appropriate control module classes. Configure the control logic for the equipment module class in Control Studio. 
5. Create Unit Classes and, if needed, define unit parameters. Add equipment module classes and control module classes to the unit classes as needed.
6. Create the Phase Classes in the Advanced Definitions Library with batch input and report parameters as needed. These parameters are used to download values to the phase logic or report actual process values, respectively.
7. Using Control Studio, configure the Phase Logic for the phase classes. The phase logic is written in the form of sequential function charts that step through the actions to be performed during each phase.
8. Using DeltaV Explorer, assign the Phase Classes to the unit classes. Note that more than one phase class can be assigned to a single unit class. (For example, a blender unit class might have separate phases assigned for charging ingredients, agitating, heating, and discharging the contents.)
9. Create the Unit Modules by dragging a unit class to the appropriate process cell in the DeltaV Explorer. Unit modules are instances of a unit class; they inherit their phase logic from the assigned phase class or classes. The resulting unit module contains instances of the control module and equipment module classes contained in the unit class as well as a list of the module aliases. 
10. If necessary, create additional control modules and equipment modules that are outside of the unit modules. 
11. Select the Unit Phases to be included in download of the unit module. Only those phases that are assigned to the unit class and specifically marked as controller type will be available when the unit module is run.
12. Resolve Alias Names for non-class-based items by specifying the actual parameter reference paths to be used for each alias. For class-based modules, assign device tags to function blocks as needed. 
13. Specify Unit Parameter values for any unit parameters that you defined for the unit class (UM_BLEND_500, for example, might have a volume of 1000 gallons and be made of stainless steel). Change any other configurable parameters as needed for the individual module instances.
14. Assign unit modules (and contained control modules and equipment modules) to the controller (or workstation for simulation). 
15. Configure unit phase type (Disabled, Controller, or External Phase).
16. Assign the area to the Batch Executive.
17. Assign the area to the Alarms and Events subsystem.  (This is necessary to be able to change any parameter setpoints on the current workstation.)
18. Configure the Batch Recipes.
19. Assign the recipes to the Batch Executive.