# Create New Alarm Priority/Class **URL:** \ **Category:** Ignition\ **Created:** [September 16, 2020, 9:28am UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736 "2020-09-16T09:28:37Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![nlev80](https://avatars.discourse-cdn.com/v4/letter/n/d78d45/32.png) [@nlev80](https://forum.inductiveautomation.com/u/nlev80)\ **Post date:** [September 16, 2020, 9:28am UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/1 "2020-09-16T09:28:37Z")
Hi all, I’ve been looking into Ignition as a potential SCADA solution for our future projects and came across smth that I can not figure out. In process industries it is very common to follow IEC 62682 (Alarm Management) standard. Long story short, it means that every project can and should define what alarms classes it want to use. Hence my question: is it possible to add new alarm priorities to the ones already defined in Ignition (Diagnostic/Low/Medium/High/Critical)? Or is it possible to edit/rename the pre-defined ones? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [September 16, 2020, 12:48pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/2 "2020-09-16T12:48:30Z")
Alarm priorities are fixed, unfortunately. The design of Ignition’s alarm system was influenced by [The Alarm Management Handbook](https://www.amazon.com/Alarm-Management-Handbook-Bill-Hollifield/dp/0977896927), one of the results being the use of a fixed number of priorities (Critical, P1, P2, P3, P4). We just tweaked the names a bit. ---
**Author:** ![desaitvisha](https://avatars.discourse-cdn.com/v4/letter/d/59ef9b/32.png) [@desaitvisha](https://forum.inductiveautomation.com/u/desaitvisha)\ **Post date:** [April 26, 2021, 11:39pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/3 "2021-04-26T23:39:13Z")
> [@Kevin.Herron](#): > > design of Ignition’s alarm system was influenced by [The Alarm Management Handbook](https://www.amazon.com/Alarm-Management-Handbook-Bill-Hollifield/dp/0977896927), one of the results being the use of a fixed number of priorities (Critical, P1, P2, P3, P4). We just tweaked the names a bit. Can we change the names of the existing priorities? e.g. 'Low' priority to be names as 'Warning' ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [April 26, 2021, 11:46pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/4 "2021-04-26T23:46:46Z")
> [@Kevin.Herron](#): > > Alarm priorities are fixed, unfortunately. I think he already answered, sorry, didn't mean for you to post here, just to get your answer here. My bad for being confusing. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 26, 2021, 11:49pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/5 "2021-04-26T23:49:26Z")
The priority levels _and the names_ are fixed. ---
**Author:** ![Zach\_Smith](https://avatars.discourse-cdn.com/v4/letter/z/e47c2d/32.png) [@Zach\_Smith](https://forum.inductiveautomation.com/u/Zach_Smith)\ **Post date:** [June 25, 2024, 8:31pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/6 "2024-06-25T20:31:24Z")
Kevin, Can you elaborate on your alarm structure? In your response from Sep 2020, you state that alarms are (Critical, P1, P2, P3, P4), but in actuality the numbers appear to be reversed P4 is critical, P1 is low. I'm also only seeing 4 total priorities, not 5. Can you please explain these differences? Lastly, how does this ensure API 1165 is met? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [June 25, 2024, 8:40pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/7 "2024-06-25T20:40:31Z")
> [@Zach\_Smith](#): > > In your response from Sep 2020, you state that alarms are (Critical, P1, P2, P3, P4), but in actuality the numbers appear to be reversed P4 is critical, P1 is low The book I referenced uses these priorities. Ignition uses 5 as recommended, but we named them less ambiguously: - Diagnostic - Low - Medium - High - Critical ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/a/fad734de3dcfcc9905969f7e0a720a8faa486b56.png) Numerically represented 0-4 in various places. [Pipeline - Filter on Alarm Priority | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/alarm-notification/alarm-notification-pipelines/pipeline-filter-on-alarm-priority) ---
**Author:** ![Guilherme\_Avelar](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@Guilherme\_Avelar](https://forum.inductiveautomation.com/u/Guilherme_Avelar)\ **Post date:** [July 9, 2024, 2:11am UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/8 "2024-07-09T02:11:51Z")
@Kevin.Herron is there some way (scripts or custom properties) to rename the priorities? ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [July 10, 2024, 12:48am UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/9 "2024-07-10T00:48:23Z")
> [@Guilherme\_Avelar](#): > > is there some way [...] to rename the priorities Not directly. [Enums](https://docs.oracle.com/javase/8/docs/api/java/lang/Enum.html) are used for this sort of thing, so they're not editable. > [@Guilherme\_Avelar](#): > > (scripts or custom properties) There are plenty of ways to manipulate how an alarm priority is displayed to the user, but none of them will change what they are under the hood. ---
**Author:** ![Guilherme\_Avelar](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@Guilherme\_Avelar](https://forum.inductiveautomation.com/u/Guilherme_Avelar)\ **Post date:** [July 10, 2024, 1:21pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/10 "2024-07-10T13:21:52Z")
Can you please share one way to manipulate the way an alarm priority is displayed? ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [July 10, 2024, 1:51pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/11 "2024-07-10T13:51:43Z")
What module are you using? > [@Custom alarm status/journal viewer in Vision?](https://forum.inductiveautomation.com/t/custom-alarm-status-journal-viewer-in-vision/67637/2): > > Personally, I probably wouldn't do this. At first, I will admit that I shared your view of the various unmalleable enum classes that comprise much of the data in the Alarm Status Table, and I found the complexity of that component to be a little off putting, but the more I work with it, the more impressed I am. The tool is quite comprehensive, and I can tell that a lot of high quality reasoning went into its design. It's actually quite a bit more flexible than it at first seems. However, if you… ---
**Author:** ![Guilherme\_Avelar](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@Guilherme\_Avelar](https://forum.inductiveautomation.com/u/Guilherme_Avelar)\ **Post date:** [July 10, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/12 "2024-07-10T15:02:30Z")
I'm using Alarm Journal Table and Alarm Status Table. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 10, 2024, 3:03pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/13 "2024-07-10T15:03:39Z")
Those are components, not modules. Are you using the Perspective module or the Vision module? ---
**Author:** ![Guilherme\_Avelar](https://avatars.discourse-cdn.com/v4/letter/g/c67d28/32.png) [@Guilherme\_Avelar](https://forum.inductiveautomation.com/u/Guilherme_Avelar)\ **Post date:** [July 10, 2024, 4:02pm UTC](https://forum.inductiveautomation.com/t/create-new-alarm-priority-class/38736/14 "2024-07-10T16:02:21Z")
Vision