My daughter wanted the following for her 16th birthday (last year): 1) A car 2) A trip to France 3) A pony She got: 1) A 1990 Toyota Camry Stationwagon with about 120K miles on it 2) An exchange trip with classes 8 hours a day for three weeks to Nice 3) A 1/2 lease on a horse at her barn that requires her to be there 3 days a week taking care of the hay burner. There are several morals to the story: 1) Be careful what you pray for, you may get it. Pray for strength=20 and you'll get opportunities that test your strength and build it. 2) Project requirement definition is very important. 3) Things often sound better (more glamourous) than they are:=20 "I got a car, a pony, and a trip to France for my 16th birthday!" Merry Christmas. I've got shopping to do. 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 Lowell, Timothy Sent: Wednesday, December 20, 2006 10:49 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] alarm inhibiting vs. alarm disabling - process summary reporter Me! Going beyond that, I'd like to see a comprehensive alarm management mechanism incorporating flood suppression, grouping, and other techniques, built in to all I/A blocks that are capable of generating alarms, so that we don't have to roll our own with scripts that are difficult to develop and maintain. =3D20 I also want a 60" Plasma TV with a surround sound system for Christmas. And a pony. Tim Lowell Control Systems Engineer Tesoro Corporation (office) 210-283-2929 (mobile) 210-253-0225 tlowell@xxxxxxxxxxx =3D20 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Corey R Clingo Sent: Wednesday, December 20, 2006 10:40 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] alarm inhibiting vs. alarm disabling - process summary reporter Hmmm....sounds familiar :) So let's take a poll: who would like to see connectable alarm destination=3D20 group (*GP) parameters? Corey Clingo BASF Corporation "Armour, Alan" <aarmour@xxxxxxxxxxxxx>=3D20 Sent by: foxboro-bounce@xxxxxxxxxxxxx 12/19/2006 04:14 PM Please respond to foxboro@xxxxxxxxxxxxx To <foxboro@xxxxxxxxxxxxx> cc Subject Re: [foxboro] alarm inhibiting vs. alarm disabling - process summary=3D20 reporter Good one Michael, The annoying thing that I find is that as soon as you use INHIB or INHALM to configure logically driven alarm suppresion the block automatically appears as "inhibited" on the inhibited alarms report. What I have done is to use INHALM for logically supressing alarms, so that the operators can still overide the logical inhibits by using INHIB. I have walked away from the Foxboro inhibited alarms reports and used a script which looks for INHIB =3D3D3D1, and combined =3D with another script which extracts alarm inhibiting actions from the operator action logs. This gives me a time stamp of when an alarm was operator inhibited. The other annoying thing is as part of my overall alarm philosopy I want to reduce alarm traffic to the operator during abnormal situations. There is important data which can be used in post event analysis which would be lost if a blanket inhibit of non immediately important alarms are suppressed, so I have a desire to divert many alarms to an "historian only" alarm group. This would be easy to do if the alarm group paramaters on any block which produces alarms was connectable, but....(hope Alex is looking!). At the moment what I am doing is run two blocks, one for the operators, and one for historian, and use block names which are as close as possible to each other. regards, Alan =3D3D20 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Kessler Sent: Wednesday, 20 December 2006 12:22 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] alarm inhibiting vs. alarm disabling - process summary reporter > 2. You can send a HEX pattern to the AIN's INHALM parameter. =3D Again=3D3D20 > this =3D3D3D parameter is connectable and settable, so any display =3D or=3D3D20 > program can set =3D3D3D the hex pattern if there is no connection. =3D For=3D3D20 > example a pattern 0x0003 =3D3D3D will inhibit HIGH and LOW alarms. > You can also toggle the HEX bits individually from block detail in Select. For example, to inhibit only the HI alarm, 1. Call up block detail for the AIN. 2. Click Alarms 3. From Select pick the HIABS parameter. 4. Click Toggle A black INHIBITED should appear indicating that the HEX bit to disable HIABS has been set. mk =3D3D20 =3D3D20 ______________________________________________________________________ =3D20 =3D20 _______________________________________________________________________ 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 =3D20 foxboro mailing list: http://www.freelists.org/list/foxboro to subscribe: =3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin to unsubscribe: =3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave =3D20 =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 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: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave