Emerson Exchange 365

• Not Answered

Duplicate Batch ID

Is it possible to prevent the use of a duplicate batch ID or prompt to alert operators before entering a duplicate batch ID

David Siler

• 27 Jun 2017 7:48 PM
• Cancel

3 Replies

• Matt Stoner

  

  • 28 Jun 2017 1:24 PM

  The system won't allow duplicate Batch IDs "active" (seen in the Batch List) at the same time but there isn't a way to prevent someone from entering the same Batch ID that has previously run and been removed from the Batch List unfortunately.
  
  If you would like to see this changed/enhanced, requests can be made on the User Driven Enhancement Program (UDEP) website - www.userideas-emerson.com/

  • Cancel
• Steve Linehan

  

  • 29 Jun 2017 11:49 AM

  We did some like this a while ago. We had an onchange command that was triggered by a phase by writing to a parameter in the database which was linked to a change event on the graphics. The phase was the startup phase that ran before all others in batch to set stable conditions before start and a bunch of other housekeeping stuff.
  This ran a script that opened a file on \\PROPLUS\DVDATA\BATCHSTOR\List.csv.
  This file checked for the existance of the batch name and if found returned "Used" or "Not Used" to a second parameter. Based on that we could prompt the operator to verify he wanted to proceed as the batch name was already used.
  If answer was yes we appended the batch ID to the CSV file. If No we aborted.
  We needed a few more parameters to store the update station as the command would fire everywhere. Basically write update station name to another parameter. (Many workstations write). Then after 5 sec update other parameter from the phase to fire second event. This checks to see if current workstation is master and if so proceed to check the Batch ID and if necessary update file. Dont use delay in script as this can interfere with graphic execution.
  Not a completely robust solution but works if you can guarentee and least one graphics session open.

  • Cancel
• gamella

  

  • 29 Jun 2017 12:23 PM

  First, I think this duplicate batchid prevention must be restricted to a period of time to the past (days, weeks, moths, etc...). Having to check against any batchid used anytime in plant's life will require a potentially "infinite" list of batchid's stored somewhere.
  
  It will be possible to implement custom campaign manager interface inside DeltaV Operate to create and launch batches. As this custom interface will be written using VBA, i see two options to check if batchid was already used in some batch
  1- If Batch Historian is present, VBA code may perform an SQL query against Batch Historian to retrieve batchid's stored on current database (autoarchiving time span defined will define period of time in the past to check for repeated batch id). Then custom interface will check if proposed batchid is repeated or not, and warn operator.
  2- If Batch Historian is NOT present, this custom interface should update a persistent list of used batchid's on batch creation attempt and check against that list to validate if batchid requested was used previously or not. The problem is where/how to store used batch id data. Text files could not be a good solution because a single file stored on a selected workstation could be accesed from several operator stations, raising file locking issues. I will suggest use of event chronicle SQL database. Custom interface will write ito a control module the new batch id (if validated as not repeated) and this module will write a LOGEVENT into chronicle database. In this way the custom interface may retrive a list of used batch ids by SQL query on event chronicle database (period defined to keep chronicle database events defore exporting/deleting will define period of time in the past to check for repeated batch id).
  
  However, this is costly/risky solution and it is a fact that creating batches from standard batch operator interface without repeated batchid checking will still be possible.

  • Cancel