The Area Model defines the physical equipment and the batch components to be used by batch recipes. There are several configuration changes that alter the Area Model (see below). When an Area Model change is made, the Batch Executive does not have to be stopped and restarted; however, the Batch Executive needs to be downloaded (either a complete download or equipment only) for the changes to take effect.
The following are considered Area Model changes:
-
Adding, deleting, or modifying a process cell
-
Adding, deleting, or modifying a unit module (including downstream units)
-
Adding, deleting, or modifying a phase class (altering composite logic within the phase does not impact the Area Model)
-
Changing the "Phase Type" or "Simulate" properties for a Unit Phase or a Phase Logic Module (PLM)
-
Changing the associations between areas and process cells, between process cells and units/unit modules, units and phase logic modules, and unit modules and unit phases
-
Changing area assignments to the Batch Executive
-
Changes to unit aliases in equipment trains and equipment train classes
-
Changes to unit selection policies
-
Adding or deleting equipment trains
When the Batch Executive is processing a download the following functions are not available through the Batch Operator Interface, Campaign Manager or the DeltaV Operate Batch control:
-
Adding a batch to the batch list.
-
Creating a manual phase batch.
-
Creating a campaign.
-
Releasing a batch via the Campaign Manager.
For changes made to the controller (for example, unit module assignments) to be effective with new batches added to the Batch List, the changes, that is the changed unit modules, must be downloaded to the controller. The Batch Executive must also be downloaded (equipment download at a minimum). When downloading both the controller and the Batch Executive, download the controller first, then the Batch Executive. To be able to select new equipment for recipes already on the batch list, you must resynchronized the recipe after downloading the controller and Batch Executive.
If you have already downloaded the Batch Executive and then change the unit module's controller assignment, you will have to make a change to the Area Model as well and re-download the Batch Executive for the Batch Executive to be current.
Changes to recipes do not impact recipes already on the Batch List. A snapshot of the recipe and equipment configuration is stored by the batch runner when the batch is added to the Batch List.New batches will use the modified recipe.
The following recipe changes can take effect after a download without restarting the Batch Executive.
-
Recipes may be added or deleted or modified (provided that you have not added new input or report parameters to any phase classes that are referenced in the recipe).
-
Creating, altering, or deleting formulas
-
Creating, altering, or deleting operations
-
Creating, altering, or deleting unit procedures
-
Creating, altering, or deleting procedures
-
Modifying what equipment trains the procedure uses
CAUTION!Downloading a modified recipe used as a base recipe in a campaign requires you to resync the campaign's (or its constituent batches') recipes.
The following changes should not be downloaded while a recipe is running or on the batch list. Doing so can cause undesirable results.
-
Deleting process cells or units that are being used by batches currently in the Batch List
-
Renaming equipment, phase classes, unit class parameters, or phase class parameters
-
Modifying unit class or phase class parameters
-
Changing equipment arbitration ID's
-
Adding or deleting phase class input or report parameters
If you make changes online, such as adding or deleting a phase parameter, while recipes are running that involve those parameters, your phase logic must be able to handle those kinds of changes. For example, if a recipe gets to a phase where a parameter has been deleted, there may be a mismatch. (The Batch Executive knows of the parameter, but the controller is not aware of it.) In this case an operator prompt will appear notifying you of the mismatch and asking for confirmation of whether to continue. On the other hand, if you add a phase parameter and download the phase, the Batch Executive will not be aware of it, but the controller will be. Your phase/recipe logic must be able to handle this kind of mismatch.
CAUTION!Never download a phase logic module (PLM) that is being used by an active batch as this will cause all phases that are being executed on the phase logic module to be terminated. The unexpected termination of a phase will cause the recipe that was executing the phase to fail.