- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-12-11 09:17 PM . Last Modified: 2023-05-02 11:50 PM
Historic Overactive Alarms
Hi Schneider Support,
Do the "Historic Overactive" alarms (configured from ViewX | Root | Edit Properties | Historian Tab | Overactive section) get shown in the alarm banner to all users that have "View Alarm" security permissions to the $Root folder?
Ideally, we would like to show the "Historic Overactive" alarms only to the people that have responsibility for specific plants or parts of the database tree (ie: that are members of specific user groups). Is this possible, or once a user has "View Alarm" security permissions to the $Root folder they therefore see all areas (including some parts of the database tree that they are not interested in)?
Hope you can clarify.
Cheers
- Labels:
-
ViewX
Link copied. Please paste this link to share this article on your social media post.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-12-12 02:26 AM
Historic overactive alarms are text alarms. The source of a text alarm is the whole system, rather than a particular object in the database, and as such the root group security settings apply to text alarms.
You could restrict access to overactive alarms by allocating the overactive alarms to an 'area of interest' that only the required users have access to. Alternatively, you could allocate them to a particular severity that only the required users have access to (using default alarm filter).
Andrew Scott, R&D Principal Technologist, AVEVA
Link copied. Please paste this link to share this article on your social media post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-12-12 02:26 AM
Historic overactive alarms are text alarms. The source of a text alarm is the whole system, rather than a particular object in the database, and as such the root group security settings apply to text alarms.
You could restrict access to overactive alarms by allocating the overactive alarms to an 'area of interest' that only the required users have access to. Alternatively, you could allocate them to a particular severity that only the required users have access to (using default alarm filter).
Andrew Scott, R&D Principal Technologist, AVEVA
Link copied. Please paste this link to share this article on your social media post.