Hai Will this help. When alarms are inhibited 1. With INHOPT 0 & 2 alarms are detected by CP alarm outputs are set . If interlocks are written based on these output they will work.Only messages are suppressed to target devices 2. With INHOPT 1 & 3 alarms are not detected by CP alarm outputs are not set. If interlocks are written based on these output they will not work. Manimala.S Invensys India Pvt. Ltd, Do you want to Know More and Act Faster ? Join Us ... IPS Asia Pacific Users Group Conference 2007 23 - 26 January 2007 (JW Marriott Hotel, Kuala Lumpur Malaysia) For more details, visit www.ips-ap.com.sg/UGC2007 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Johnson, Alex P (IPS) Sent: Thursday, December 14, 2006 10:53 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] alarm inhibiting vs. alarm disabling - process summary reporter If you disable an alarm, the blocks behavior is identical to that of a block for which the alarm was not configured. That is, disabling causes the block to stop alarm detection AND notification. If you inhibit an alarm, the block no longer notifies the rest of the system of detected alarms of that type. The "rest of the system" refers to the alarm destinations specified by the alarm's alarm group parameter. These destinations are specified block's compound's GRxDVy parameters or the alarm groups in the SYSTEM block. Note: I said the behavior is identical, but there is a difference. In both cases, a message is sent to the alarm destinations telling them that the alarm is disabled or inhibited. That's how the CAD knows to change its display. Regards, =20 Alex Johnson Invensys Systems, Inc. 10900 Equity Drive Houston, TX 77041 713.329.8472 (voice) 713.329.1700 (fax) 713.329.1600 (switchboard) alex.johnson@xxxxxxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Monte J Hansford Sent: Thursday, December 14, 2006 10: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 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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave =20 Confidentiality Notice: =0AThe information contained in this electronic m= essage and any attachment(s) to this message are intended for the exclusi= ve use of the recipient(s) and may contain confidential, privileged or pr= oprietary information. If you are not the intended recipient, please noti= fy the sender immediately, delete all copies of this message and any atta= chment(s). Any other use of the E-Mail by you is prohibited.=0A _______________________________________________________________________ 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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave Confidentiality Notice: The information contained in this electronic message and any attachment(s) to this message are intended for the exclusive use of the recipient(s) and may contain confidential, privileged or proprietary information. If you are not the intended recipient, please notify the sender immediately, delete all copies of this message and any attachment(s). Any other use of the E-Mail by you is prohibited. Confidentiality Notice: The information contained in this electronic message and any attachment(s) to this message are intended for the exclusive use of the recipient(s) and may contain confidential, privileged or proprietary information. If you are not the intended recipient, please notify the sender immediately, delete all copies of this message and any attachment(s). Any other use of the E-Mail by you is prohibited. -- No attachments (even text) are allowed -- -- Type: image/gif -- File: image002.gif -- Desc: image002.gif _______________________________________________________________________ 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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave