How to notify operator about a failure in an Operation?

Hi Everyone,

We have the Hold Propagation Limit in the Batch Executive set to UOP (Operation). Now, if we are running a procedure and an operation within goes to Hold, the operator does not get an indication. In BOI it is only visible if you drill down to the Operation level. Also on the displays in DeltaV Operate, the PCSD standard RecipeInfo dynamo does not indicate anything. It shows the operation name, but it does not show that it is in an abnormal state. We also can potentially have parallel operations running on one unit, so this dynamo is not that useful.

Any best practices on how to make the operator aware?

  • I would suggest using the P1/P2 parameters to check for failure in some unit support module. If RX-777-xxx/P1/BSTATUS = HOLDING or HELD or RXxxx/P2/xxxxx etc. This will give you an aggretated status of all "phases" status and tell you if one is failed. If you have an operation in hold you should have at least one phase in hold.

    You can typically use the Phase Name or P1/P2 to test phase conditions. P1 is the first phase to load and P2 is the next phase etc. Alternatly a dynamo can be created but not sure if graphics can test for P1 etc. You should be able to test the graphics option easily.

    You can test for a failed phase and then figure out which phase is failed. Use Unit/P6/Phasename or something like that to flag to the operator that a phase has failed.

    Hope this gives you some ideas.
  • I am also looking at Phase Alarms now. I think they might be a good solution, and would not need the custom module you suggested. They become active when the failure monitor is triggered, which is essentially when the phase goes to Hold. I found some options in BOL which I cannot find in DeltaV:

    The following additional properties, which control the behavior of phase alarms in the unit module, are configured in the unit phase table for each phase:
    Enable failure alarms on this unit phase - Is a Boolean property. If False, then the values of the other alarm-related properties do not matter. Defaults to True.
    Phase alarm name - Is the name that will appear in the alarm details field in the alarm banner when this unit phase has a failure. Must pass the standard parameter name checks (characters, length, no name space collisions, and so on). Defaults to the unit phase name. If the phase class name is changed, the phase alarm name does not change. It remains the same as the original unit phase name.

    Does anyone know where these could be set? Also, how to manage the fact that I would want the alarm to be automatically acknowledged when the operator restarts from Hold? I would not want the operator to have to do 2 things: restart and acknowledge.
  • In reply to István Orbán:

    The options for the phase alarms are set on the Unit Instance that the phases are assigned. You will need to update them on each of the unit instances for the changes you want to configure.

    The automatic acknowledgement would be set on the priority of the alarm you use on the phase alarms. The system will clear the alarm itself when restarted but the auto acknowledge of New and/or Inactive alarms are a function of the alarm priority so you may need to create an alarm priority to use for the functionality you want.