Emerson Exchange 365

• Not Answered

Automatically Increment Batch ID When New Batch is Created

Hi all,

We have a unique situation at our plant in which we have two separate trains of equipment that have a unique batch recipe that runs on each.  As both of these trains make the same end result product, their batches  are named the same except for the number of the batch at the end.  One train uses even numbers and the other uses odd.  We have issues (happening more often here lately due to new recruits) in which the operator incidentally skips the next batch number and creates the one after.  For example, if the next batch were suppose to be 129, the operator skips this and creates batch 131 which throws production off when they go to do material balances, etc.  Is there any way in which you can have the field prepopulated with the next batch ID when the operator goes to create the batch?  One step further, is would there be a way to make this work with the even and odd numbering scheme we are currently using? If there is no way to prepopulate this field, is there a way to restrict the batch ID that is entered to where we would only let them enter the next number?

Thanks and any help is much appreciated!

• #BatchID #DeltaVBatch #Batch

dsturg

• 2 Mar 2017 4:15 PM
• Cancel

2 Replies

• dvarghese

  

  • 2 Mar 2017 4:23 PM

  Campaign manager is one solution.

  • Cancel
• Michael Moody

  

  • 2 Mar 2017 4:50 PM

  First, just to confirm - you referring to the Batch ID field in the dialog used to create a new batch? I don't think there is an easy way to limit what goes into that field as it is a text field (as best as I remember).
  
  As mentioned, Campaign Manager can add incremental numbers to a Prefix, but I'm not sure about limiting to even or odd. Is there a reason you wish to distinguish by even / odd? If using the reactor vessel number in the Batch ID followed by a sequential number would work, then Campaign Manager could easily handle this. Of course, this assumes you are making multiple batches of the same product in the form of a campaign.
  
  If you need additional flexibility beyond the standard Campaign Manager, there is a "Campaign Manager SOA Web Service" available. This even allows external programs to dictate batch details (Batch ID, product, formula, etc.) I have never used it, but it might be an option. Please look at the following link for info:
  www2.emersonprocess.com/.../DV_PDS_CampaignManager.pdf
  
  Just a note, Campaign Manager is included with Professional Batch. If you do not have it already, you may and may not want to pay the additional license fees just for batch numbering.
  
  If none of those options are feasible, you could create a "Batch ID" parameter. This is simply a parameter in a Control Module. I used something similar on a project where they only wanted to use an integer for Batch Numbering. When a batch was created, it was given a name for Batch ID, but this was ignored by operators. The first operation / phase passed a flag to a CM that a new batch started. A parameter in the CM held the next available batch number. This number was then dumped into the batch ID for the new batch and then incremented for the next vessel. In our case, we used the same parameter to hold the next available batch ID for four separate reactors. You could easily dedicate a separate CM for each and increment by 2 vs. 1. One CM would hold only odd and the other even IDs. Just realize that while this Batch ID can be displayed on the screen, trended in the Historian, and included on Batch Reports, it is decoupled from the Batch ID that is used for Batch History View and Journal.

  • Cancel