[00:00] In this lesson, we will explore the ability to configure multiple alarms on a single Ignition tag. Here in my designer I have a level OPC tag that tells me the level in liters of one of the tanks on my plant floor. I will be configuring multiple alarms on this tag so let's double click on it to bring up its editor. I will scroll down to the alarming section where I will click on this little pencil to bring up the alarming configuration window. First, I want to configure a high level alarm so let's do that. I will click on the plus sign to add my alarm. I will name the alarm high level. I will give it a critical priority. And for my alarm notes, I want to include something to give operators a bit of information as to how to resolve this problem. So I will say, tank level is high, open overflow valve.

[01:05] I will then set its mode to be above setpoint. And for my setpoint value, I will just give it the static value of 900. If my tank's level does go above 900 liters, my alarming condition will be met and this alarm will become active. I am done with this alarm's configuration so I will press the plus sign once more to add my second alarm. This alarm will be named low level, its priority will remain low, and for the alarm notes I will just say, tank level is low, open filler valve. For my mode I will have it be below setpoint. And for my setpoint value I will have it be the static value of 50, meaning that if my tanks level falls below 50 liters, this low priority alarm will become active. Now let's imagine for a second that the network connection between my Ignition server and my PLC were to fail.

[02:06] My OPC tag here representing my tank level will no longer be able to fetch a value from the PLC and therefore its value will become bad quality. If this were to happen, we want users to be warned. So we will configure an alarm that watches this tag's quality. I will press the plus sign once more to add my third alarm and I will name it tank level quality and give it a priority of critical as well. For my mode, I will use the bad quality mode. This simply means that if my tag's value were to go bad quality, my alarm condition will be met and this alarm will become active. This is a good way to notify users of possible PLC connection issues or configuration issues. That's it. Once I'm done configuring my alarms, I can press commit and then press okay to save all my configuration changes. Ignition's ability to configure multiple alarms on a single tag makes it easy to account for multiple alarm conditions on a single tag.