Setup guide

OSx Migration Cookbook August 30, 2006
9 – Tags
Alarming
Alarm
suppression
DBA sets the alarmability of a tag based on the install.tag file used
to import it into PCS 7. Tags that are configured for alarming in
OSx (but NOT Tistar) have RBE ids assigned to them. In the
install.tag format RBE ids are optional and DBA can accept
install.tag files with and without RBE ids. Files originating from
APT, Tistar, and the OSx 4.1.2, 4.1.1 or 4.1.0/4.1.0A HMI do not
have RBE ids. Files that originate from the 4.1.2A HMI or via the
PAS R&D Data Extraction Services do (except Tistar which does
not implement RBE).
When DBA sees an install.tag file that does not contain any RBE
ids, it makes the assumption that all tags are alarmable. That means
you will have to manually edit the newly imported tags to turn off
alarmability on those tags you do not want to be alarmable to avoid
nuisance alarms.
When DBA sees an install.tag file with RBE ids, it configures those
tags that have RBE ids as alarmable. All other tags are not so
configured. If you want tags that were not alarmed in OSx to be
alarmable in PCS 7 then you will have to manually edit those tags
in DBA.
When setting PCS 7 tags to be alarmable DBA uses defaults for
priorities and levels that may not match how these were set in OSx.
If those are not as they were in OSx or as you want them, you will
need to manually edit each incorrect alarm tag in DBA.
OSx has an alarm suppression feature where the value in one tag
can suppress an alarm in another. This allows for the automated
suppression of nuisance alarms. PCS 7 does not have this feature.
You can turn off a tag’s alarmability at runtime temporarily but that
is a manual operation. OSx alarm suppression could be mimicked
by the use of a PCS 7 action which when a tag reaches a certain
value, turns off the alarmability on another tag. You would also
have to provide for a condition that then turned that alarmability
back on.
24