• Not Answered

About LOG alarms and showing them in DV analyze

Hello everyone,

My system is DV 11.3.1 with DV analyze 2.0

Our site is working on creating a solution for nuisance alarms that should not be alarms in the first place due to the very long time required to have a relevant consequence or solution, but that are still important enough as to desire to have them reported somewhere where they can be easily acknowledged and solved by personnel on a different group, and not the console operator (which, as said, can't or shouldn't do anything about these alarms within their shift).

At this point you guys probably have noticed that what we desire is pretty much having a working mechanism to receive what ISA 18.2 defines as alerts.

I was thinking that this may be a good case for exploiting the functionality of the default LOG (P3) alarms, which as explained in the Books Online are not really managed as alarms by the system, but that create events registering every time that the limits associated to them are exceeded. I hoped that we could simply set all alarms that fall in the category described in the previous paragraph as LOG (P3) alarms and then just have shift operators print the Log events report from Delta V analyze once per shift, so I configured a couple of LOG alarms and set them in such a way that the variables associated to them surpassed the limits to verify that the corresponding records were created in the system event log. The expected events regarding the log alarms used for this little test seemed to be working properly (I could confirm that every time that the LOG alarms were triggered a corresponding event was created), but then my problem is that they are not being shown as log alarms in Delta V analyze. I've check the corresponding time frames and there's nothing. In fact, there's nothing at all in the Log alarm section in DV Analyze, which by itself doesn't surprise me because as far as I know there are no other LOG alarms on the system except those just created by me, but for some reason this section of DV Analyze is not showing the Log alarms that I've recently created and triggered on purpose.

I would appreciate any direction you can give on this matter. DV Analyze is working fine in collecting all other "normal" alarms. There's something that I must be doing or understanding wrong about Log alarms, even though I've checked everything many times. If you think that there's another way to fulfill our need with this matter, other than what I've thought, I will be also glad to listen. If there's any further info that you need to be able to help, please let me know.

Many thanks!

3 Replies

  • I'm not familiar with DeltaV Analyze, but if you look in the Event Journal, you'll see that the LOG alarms are logged as "EVENT" instead of "ALARM", see the Event Type column. Maybe you could use a new alarm priority where you set it to "Auto-Acknowledge new alarms"? They would still be visible, but would not require acknowledgement.
  • In reply to István Orbán:

    István,

    Thanks. I am aware of that. Log alarms do show as EVENT in the event journal.

    A new alarm priority other than LOG will not work for us, even with the auto-acknowledge feature enable, because they will be managed by the system as an alarm: they will appear in the alarm banner, they will count as an alarm in alarm statistics made by DV Analyze, they will show in the alarm summary and they will possible make the HORN sound (though I think this last one can be disabled)....All of these implications being undesirable to us for these cases where what we need is an alert that is outside the alarm system.

    Thanks for your reply anyway.
  • In reply to DXSANCH:

    Note that the alarm banner and alarm summary have filter options such that if you used alarm priority 4, auto acknowledge with no horn. You would address your concerns. In analyze you could manage your reports based this priority and the assigned category. You can then also create a dedicated summary by filtering on priority 4.

    I agree that an alert level category would be nice so that the alarm system is separate from alerts or notifications.

    The best we have is to leverage the 12 alarm priorities, which you typically only use three or four. That leaves multiple priorities acting as alerts that can be displayed in dedicated summaries.

    Andre Dicaire