# Alarm Tag That Points to Other Tags **URL:** \ **Category:** Ignition\ **Tags:** scripting, perspective\ **Created:** [October 16, 2025, 5:03pm UTC](https://forum.inductiveautomation.com/t/alarm-tag-that-points-to-other-tags/111527 "2025-10-16T17:03:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![rowens](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rowens/32/79407_2.png) [@rowens](https://forum.inductiveautomation.com/u/rowens)\ **Post date:** [October 16, 2025, 5:03pm UTC](https://forum.inductiveautomation.com/t/alarm-tag-that-points-to-other-tags/111527/1 "2025-10-16T17:03:06Z")
Hello, Is there a way to make an alarm tag that points to x number of tags and will alarm if any or all of those tags meet the condition? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/f/6f35dd5926ceca36a5b49f92afc34f8612a19549.png) For example these two tags are set up the same way alarm wise and I have about one hundred more tags that will be set up the same way as these two I am looking for a way to save some time instead of setting up hundreds of tags with the same alarm structure. Is there a way to copy and paste the alarm setting in perspective? Anything helps, let me know if I need to clarify. Thank you ---
**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\ **Post date:** [October 16, 2025, 5:35pm UTC](https://forum.inductiveautomation.com/t/alarm-tag-that-points-to-other-tags/111527/2 "2025-10-16T17:35:06Z")
Create a UDT with parameters. Preset the alarm instance with the common attributes. For those attributes that are unique to each tag, use the defined parameters with {} substitution. As an example, I have a valve UDT with the normal 4 alarms (open, close, both, neither feedbacks). The parameter is the valve ID string. The alarm is “{ID} Open Alarm”. Then, create your tag instances of type UDT and simply change the parameter for each instance. ---
**Author:** ![rowens](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rowens/32/79407_2.png) [@rowens](https://forum.inductiveautomation.com/u/rowens)\ **Post date:** [October 16, 2025, 6:36pm UTC](https://forum.inductiveautomation.com/t/alarm-tag-that-points-to-other-tags/111527/3 "2025-10-16T18:36:12Z")
I’ll have to try that out. I am experimenting with the script console and see if I can set up the historian and alarm tags all the same way ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [October 16, 2025, 9:32pm UTC](https://forum.inductiveautomation.com/t/alarm-tag-that-points-to-other-tags/111527/4 "2025-10-16T21:32:06Z")
Definitely a UDT makes sense here. I set my alarms up differently though. I set the: - Name: the alarm name, no context. Eg Failed to Start - Label: the equipment name and equip id. Eg Acid Dosing Pump [CRWDP001] - Display path: the plant area. Eg Crushers West This way you can provide as much or as little context as you need in different places. Eg Equipment faceplates: Name only Plant area alarm view: Label and Name only Site alarm view: All three Note also, you can change the texts 'Label' and 'Disaply Path' with the translation manager to something more appropriate like Device and Area ---
**Author:** ![rowens](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/rowens/32/79407_2.png) [@rowens](https://forum.inductiveautomation.com/u/rowens)\ **Post date:** [October 16, 2025, 10:21pm UTC](https://forum.inductiveautomation.com/t/alarm-tag-that-points-to-other-tags/111527/5 "2025-10-16T22:21:50Z")
I’ll have to try that out. Thanks