# How to alarm management

**URL:** <https://forum.inductiveautomation.com/t/how-to-alarm-management/22871>\
**Category:** General Discussion\
**Tags:** ignition79\
**Created:** [February 26, 2019, 9:51am UTC](https://forum.inductiveautomation.com/t/how-to-alarm-management/22871 "2019-02-26T09:51:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![c.bertulli](https://avatars.discourse-cdn.com/v4/letter/c/f19dbf/32.png) [@c.bertulli](https://forum.inductiveautomation.com/u/c.bertulli)\
**Post date:** [February 26, 2019, 9:51am UTC](https://forum.inductiveautomation.com/t/how-to-alarm-management/22871/1 "2019-02-26T09:51:41Z")

</div>

Hi All,

I’m looking for new strategies for alarm management. Thanks in advance to those who will answer 🙂

The following is the way I currently use:  
One string ( coming from the PLC ) for every alarm, then as alarming properties I have:  
As **label** ( which is the property the user visualize inside the Alarm Table ) the tag itself, this allows the PLC guy to build the alarm string dynamically from the PLC.  
As **mode** on condition  
As **condition** `if ({[.]String_0} != '', 1, 0)` where String\_0 is the tag itself.

I made a script that creates the tags and their alarm properties, so this method will take me 5 minutes to create any amount of tags.

My concern is that in this way, the net traffic load will slow down communication.