Exclusionary source filter on Alarm List object

[rlao]

Is it possible to exclude sources based on a wildcard string in the Alarm List? Mainly looking to exclude multiple FAT sections in our database from showing up on operator alarm lists. They are all named the same so I can build the wildcard string pretty easily but there's seemingly no way to apply a NOT clause to it.

The closest I can find from the filter wildcard list is the '!' wildcard but that apparently only works on single characters and only for starting characters of a source string.

[AndrewScott]

It isn't possible to filter an alarm list in this way, the OPC AE standard doesn't provide a way to do this.

However, you could simply change the security on the objects you wish to exclude so that the operators don't have the "View Alarms" permission and then they won't see any alarms for these objects, see View Alarms.

[rlao]

Hi Andrew,

Yes this is what we have been doing in the past.

The issue is our FAT sites are templated and a few of those templated objects have specific access privileges that don't inherit from parent. So those specific alarms still come through to the operators even though we removed view alarm privileges at the parent site instance level.

Technically, I could fix it by doing a property override on the security of those specific objects and then manually fudging it on individual FAT instances when they get built, but then we would have to remember to revert them back to original when they get moved to the production section. So I was hoping there was a more elegant way to go about this.