Hello guys.
Is there any way I can give an alarm a second acknowledgement?
My client wants to akcnowledge an alarm when it becomes active, shelve it and acknowledge again once it's resolved. Is this possible. If not I'm thinking about doing some kind of copy of the alarm into a DB and just write the second acknowledgement there.
What's your opinion?
Many thanks
Im not following. Most alarms dont clear, even if acknowledged, unless resolved. And what about alarms that self resolve and only require a single acknowledgment? Take for example a motor failed to start alarm. Motor output on, timer, no motor feedback, latch start fault, motor logic stops. As soon as that fault is acknowledged it goes away until next motor start attempt. Motor disconnect alarm...disconnect off, motor disc alarm. Shelve it, time expires, disc off, alarm reappears...second ack isnt going to clear it. While its shelved, the disconnect is turned on, timer expires, alarm reappears, alarm acknowledged and clears.
Im trying to visualize the scenario youre describing and coming up blank.
Ok.
I don't want the alarm to clear once it has been acknowledged.
The scenario is the following. I'm monitoring the temperature of equipments and if the temperature falls out of a certain range, an alarm is triggered.
Because of audits, a justification for the recently triggered alarm must be provided (using acknowledgment notes). Once the alarm is solved, another justification for the alarm resolution must be provided to justify why or how it has been solved (e.g. 1st ack: Cold air leak, 2nd ack: Door seal replaced).
I know the second ack falls a bit out of the concept of alarm, so any ideas are welcome 
Many thanks
Sounds maybe more like something to handle in a separate table that shows only cleared alarms and lets users select an alarm to attach a note to with a dedicated interface for it. You might want to alert operstors that there are cleared alarms waiting to have notes added
That's what I was thinking in doing if there was no option to give the second ack. Thanks
What is generating the alarm? If a PLC, i would do the logic in the PLC. 1st alarm is one tag. When the PLC sees that alarm ack, it sets a second bit as another alarm that must be seperately acknowledged. Similar to the seperate table idea above, but the PLC or controller is managing it, and all ignition does is use the standard alarm techniques.
It isn't a PLC.
But I'll use one value on Associated Data in the alarm configuration for that tag and then query that entry and write to it. This way I can keep all alarm related things on the alarm instance itself and display them using Alarm Journal Table