• Not Answered

Batch Executive

Hi all,

Today I try to download some upgrade not related to Batch. Then after the some download on a stream, I try to ask the operator to run the stream. From BOI (Batch Operator Interface) they create new batch ID and so on. But after they done usual run then they set the mode to O-AUTO, the batch sequence was not load onto the Control Module to create the Batch Parameter and so on. Is there any tips on how to make sure it is Batch is correctly load from BOI.

Sorry I'm new in DeltaV program.

p/s: Now suddenly OK by itself, can I know what are the problem related.

8 Replies

  • When there is a problem with a recipe, it won't load in BOI. The state will say 'load_failed'. Right clicking the batch will give information on the failure.
    Recipe studio has a verify recipe option. This will check if all the SFC logic is valid and other things.
    Also when a recipe loads in BOI, the mode is o-auto by default, so I don't understand why an operator must change it. Unless ASC is used.

    Your question is too unclear to properly answer. More information is needed first.

  • In reply to Robert Rijnders:

    I'm sorry coz I'm not too familiar with the program.

    This what I've before it happen.
    1 - Operation stop production ( Stop by Area)
    2 - Then I download control module for the valve that I have edited.
    3 - After download verify the status.
    4 - Ask operation to run the production by Batch
    5 - As usual they will create a batch through BOI
    6 - Suppose Phase Class already running but none was running.
    7 - Thats all I know ( Then after few hours the Phase class run by itself ), is there any stuck or problem with BOI or Phase Class?

    Sorry for the unclear question.
  • In reply to Raimi:

    Your description leads me to suspect arbitration issues. The unit phase did not start immediately because the unit or the unit phase was owned by another batch or by the operator. Either the batch finished, releasing the unit, or your operators released the phase. A picture is worth a thousand words, so in the future it will be helpful to attach a picture of your issue.
  • In reply to Raimi:

    Agree on the arbitration issue. A not well known fact is that when a recipe is aborted (or stopped), the unit module and aborted phases remain acquired by this recipe. Only when the recipe is removed from the batch list, the equipment is released. (Unless the no. of owners is increased.)
    So if this occurs a next time, check the arbitration page in BOI to make sure the resource (phase) is available.
  • In reply to Robert Rijnders:

    Is there a fix for this or is this just a bug?
  • In reply to Jeison:

    Above is not a bug, so no fix required. It is intended behavior that e.g a unit that is acquired and allowing only one owner, can not be used (acquired) by another recipe.
  • In reply to Alfred Pol:

    I understand that. However, from time to time some of our operator are experiencing 'stuck' phases in which nothing happens eventually.
    Forcing the transistion does not work anymore as well as not being able to remove the acquired operation in the arbitration list.
    The only solution that they have is to manually remove the batch and reload it again, then jump to the operation you stopped at. This includes a lot of manual operation so care is needed.
    Is there a way to prevent this from happening?

    I suspect that this happens when they force an operation at the operation level instead of the phases level. Correct me if I am wrong.
  • In reply to Jeison:

    Sounds more like a problem in the batch design? I've done projects where it is sometimes inevitable in the process that an operation needs a phase that is still acquired by another operation. But after this operation is done with the phase, the other operation would run without problems. In general it is possible to design a batch structure without any acquiring problems.

    About the DeltaV batch system. When a phase is in a acquiring state, the following transition can't be forced. Nor can you use 'active step change' to release the phase. Another limitation in the system is that only 10 unit phases can run simultaneously on 1 unit-module. (If 11 or more are configured the phases will also remain in acquiring until a path is activated with 10 or less parallel phases.)

    I think in your case the operators need to check at a phase level why it isn't completing. So really check the transition conditions, first on the operation level and second on the phase level. Forcing transitions is always a bad thing imo. Also aborting recipes shouldn't be necessary in normal production.