Create New Alarm Priority/Class

[nlev80]

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?

[Kevin.Herron]

Alarm priorities are fixed, unfortunately.

The design of Ignition’s alarm system was influenced by The Alarm Management Handbook, 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.

[desaitvisha]

@Kevin.Herron

design of Ignition’s alarm system was influenced by The Alarm Management Handbook , 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'

[jlandwerlen]

@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.

[Kevin.Herron]

The priority levels and the names are fixed.

[Zach_Smith]

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?

[Kevin.Herron]

@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

Numerically represented 0-4 in various places. Pipeline - Filter on Alarm Priority | Ignition User Manual

[Guilherme_Avelar]

@Kevin.Herron is there some way (scripts or custom properties) to rename the priorities?

[justinedwards.jle]

@Guilherme_Avelar

is there some way [...] to rename the priorities

Not directly. Enums 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.

[Guilherme_Avelar]

Can you please share one way to manipulate the way an alarm priority is displayed?

[justinedwards.jle]

What module are you using?

Custom alarm status/journal viewer in Vision?

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…

[Guilherme_Avelar]

I'm using Alarm Journal Table and Alarm Status Table.

[pturmel]

Those are components, not modules. Are you using the Perspective module or the Vision module?

[Guilherme_Avelar]

Vision