If you do work with I/NET and Emergin and have an issue with the Alarms not getting cleared after it goes back to normal, this information might be helpful to you.
I/NET Seven Site
I/NET and Emergin and have an issue with the Alarms not getting cleared after it goes back to normal
- Paging via snpp (corporate paging server) and SMTP (e-mail).
- Paging on alarms generated from DA points, as well as analog points that are out of range and giving the value at the time of the alarm.
- Escalating pages through to a list of people at certain times and canceling via "Return to normal" or "Alarm Acknowledged". This pages those on the list who have been paged the first time that the message has been cancelled.
Canceling alarms with specific cancellation keys. Within Emergin Alarms Messenger - each alarm has the opportunity to define a certain cancellation key. However the software scans all cancellation keys to see if it meets the criteria to cancel, NOT THE SPECIFIC ONE.
2 alerts with specific keys - AHU1 Fan Alrm & AHU2 Fan Alrm
1 general cancellation key for "Return to Normal"
1 general cancellation key for "Alarm Ack"
AHU1 Fan Alrm alert is assigned the cancellation key for "Return to Normal"
AHU2 Fan Alrm alert is assigned the cancellation key for "Alarm Ack"
Execution Working as Planned:
AHU1 Fan Alrm goes into alarm and sends pages. AHU1 Fan Alrm returns to normal and cancellation page sent to all previously paged.
Execution not working with specific cancellation:
AHU1 Fan Alrm goes into alarm and sends pages. AHU1 Fan Alrm is acknowledged in INET and sends a cancellation page to all previously paged. Then the point returns to normal and nothing pages.
***Because the "Alarm Ack" was setup for AHU2, it was lumped in the cancellation list with "Return to Normal." Therefore the first condition cancels - not the one specifically assigned.
EMERGIN WORKS AS FOLLOWS: Emergin lumps ALL Cancellation together. Any alert is cancelled with the FIRST cancellation tag it matches - NOT the specific one assigned in the alert.