• Not Answered

Recipe List

I am starting work on a VERY simple batch system.  I have a question on the operator interface with either Operate or Live.  To avoid possible confusion at 2:00 in the morning, I would like to be able filter the Recipe List such that when an operator is going to create a batch, a particular operator graphic can only see selected Recipes.  Since I am very early in the development process, the organization of my batch system is not cast in stone.  Right now, all my phases reside in a single Unit Module.  Is there a way to do this sort of filtering in either Operate or DeltaV Live?

Thank you in advance for any suggestions.

Kent

• 9 May 2020 1:34 PM
• Cancel

4 Replies

• chip.burge

  

  • 15 May 2020 5:51 PM

  Definitely yes for DeltaV operate: by Batch ID, Area, Process Cell, and Unit. I don't have personal experience with the batch list in DV Live but I'd assume similar functionality is there. Here's the relevant instructions for the DeltaV Operate batch list view:
  
  Set List Filtering
  1 Select the Filter Based On: option to allow filtering.
  2 Specify the source type; for example, Batch IDs, Plant Areas, Process Cells, Units, Unassociated Prompts, or Phases.
  Note What is displayed as a filter changes based on the object. For example, Unassociated Prompts is only available on the Batch Prompts object.
  
  3 Enter the name of the source for the selected option (Batch IDs for example). You can enter up to ten (10) source names in the fields (one per field). You can use the % symbol as a wildcard. For example, %PhaseName returns any phase from any unit (instead of specifying the unit name).

  • Cancel
• Kent

  

  • 15 May 2020 6:10 PM

  Thanks for the input.  If I use %PHaseName, will it give me a list of recipes that use that phase?

   

   

  • Cancel
• chip.burge

  

  • 15 May 2020 6:27 PM

  In reply to Kent:

  Sorry I think I misread your question initially. The information in my last post is for filtering the batch list view for already running batches. If you want to filter which recipes a specific operator can add you'd have to accomplish that at the security level. You could assign the BATCH_ADD function to a user defined lock and give operators different keys based on an area. Since all of your recipes are being run on the same unit I'm not sure if this helps you either. Are you trying to differentiate between say a cleaning recipe vs. a make product recipe? There are a lot of ways to make an omelette in DeltaV even if it's not the first way you think of

  • Cancel
• Kent

  

  • 15 May 2020 6:40 PM

  In reply to chip.burge:

  These are both very small pieces of equipment and I hate to put them in different units because that means that I'd need 2 licenses rather than 1. I'd like to have each piece of equipment have its recipes accessed from separate operator graphics. I'm trying to avoid confusion in the middle of the night and grab a recipe for the wrong equipment. I try to make it very hard for my operators to do things wrong and easy to do it right.

  • Cancel