As I recall, "inhibiting" an alarm means that the operator won't be bothered with an alarm horn or the need to acknowledge the alarm in the Alarm Manager, but the alarm will still be duly reported to the Alarm Manager and recorded by the historian. "Disabling" an alarm will not report the alarm to the operator display, the alarm manager, or the historian. In effect, disabling an alarm causes it not to exist. -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Monte J Hansford Sent: Thursday, December 14, 2006 11:43 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] alarm inhibiting vs. alarm disabling - process summary reporter Hi, I'm a relatively new Foxboro user, and I'm trying to customize a=20 report of inhibited alarms using the Process Summary Reporter and a little=20 shell script. I am a little confused about the difference between=20 'inhibiting' and 'disabling' alarms, which are two separate entries in=20 PSR. 'Alarms disabled' isn't described in the manual (B0193DG-E). Am I right in thinking that 'disabling' refers to inhibiting alarms from=20 the block detail page, as opposed to inhibiting via the ICC? When a=20 block's alarms are disabled, do they become 'inhibited' upon upload to the=20 workfile? Monte J. Hansford MeadWestvaco, Kraft Division Process Control & IS Group ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service._______________________________________________________________ This electronic message contains information from MeadWestvaco Corporation or subsidiary companies, which may be confidential, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify MeadWestvaco immediately at postmaster@xxxxxxxxxxxxxxxxx _______________________________________________________________________ =20 =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html =20 foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 ***************************************************************************= ************************** This email and any files transmitted with it are confidential and intended = solely for the=20 use of the individual or entity to whom they are addressed. If you are not = the intended=20 recipient or the person responsible for delivering the email to the intende= d recipient, be=20 advised that you have received this email in error that any use, disseminat= ion,=20 forwarding, printing, or copying of this email is strictly prohibited. If = you have received=20 this email in error please notify the sender immediately. Please note that = we reserve=20 the right to monitor and read any emails sent and received by the Company i= n=20 accordance with and to the extent permitted by applicable legal rules. ***************************************************************************= ************************** _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave