Thanks Terry, I think we'll probably not go to the alarm printers, but I may look at driving an external horn or light from within the logic. The flashing button I can live with - we have a long way to go for alarm management, the ops would think something was wrong if the button was not flashing. Cheers, Kevin On Mon, Feb 16, 2009 at 12:28 AM, Doucet, Terrence < tdoucet@xxxxxxxxxxxxxxxxxx> wrote: > Kevin, > > A method that I have seen used is a combination of CAD filtering (for > display) and Alarm Printer per Alarm area. The noise of the dot-matrix > printer is used to alert the operator of a new alarm. Certainly not the > greatest scheme and if the Operator leaves the CRT area briefly, he must > check the CAD when he returns. CAD is used to ACK. > > Not a critical process and fairly slow reaction times, so this worked OK. > Flashing button is an annoinance. > > Terry > > > ________________________________ > > From: foxboro-bounce@xxxxxxxxxxxxx on behalf of Kevin Fitzgerrell > Sent: Sat 2/14/2009 8:49 PM > To: foxboro@xxxxxxxxxxxxx > Subject: Re: [foxboro] P92 Quad KVM Extension > > > > Thanks Alex! > I'd gotten a presentation before MM was released and I'm not sure the > presenter was entirely clear on what it would and would not do. > > Looks like it's CAD filtering for me then. > > Cheers, > > Kevin > > On Sun, Feb 15, 2009 at 4:56 AM, Johnson, Alex P (IPS) < > alex.johnson@xxxxxxxxxxxxxxxx> wrote: > > > Kevin, > > > > Re: For the smaller control stations where I don't have a central > > control room I'm going to try the V8.x alarm management software and > > direct alarms to specific displays (at least that's the plan). > > > > > > Kevin, the Message Manager doesn't do what you think it does. > > > > The MM subscribes to the messages from the CPs and relays them to a > > large number of destinations, but there is only one such destination per > > WP/AW. > > > > That is, the messages received by a process whose name I forget and are > > stored in the Alarm Manager's database. This this database is shared by > > all Alarm Managers in the WP. > > > > > > CP WP > > CP ==> MM ==> WP > > CP WP > > > > > > In the WP: > > > > AM > > Msg -> <rcvProc> -> MsgDB -> AlmSrvrTask -> AM > > AM > > > > So, he MM can't do what you are saying, it can't send the message to a > > DM (or its associated AM instance). They go into the message database > > and are served up by the Alarm Server Task (ast) from that pool to each > > AM. > > > > > > The only option is to apply filters to the CAD display. > > > > Regards, > > > > Alex Johnson > > Invensys Process Systems > > 10900 Equity Drive > > Houston, TX 77041 > > 713 329 8472 (desk) > > 713 329 1600 (operator) > > 713 329 1944 (SSC Fax) > > 713 329 1700 (Central Fax) > > alex.johnson@xxxxxxxxxxxxxxxx > > > > > > > > * Confidentiality Notice: > > This e-mail and any associated files are intended solely for the > individual > > or entity to whom they are addressed. Please do not copy it or use it for > > any purposes, or disclose its contents to any other person. Further, this > > e-mail and any associated files may be confidential and further may be > > legally privileged. This email is from the Invensys Process Systems > business > > unit of Invensys plc which is a company registered in England and Wales > with > > its registered office at Portland House, Bressenden Place, London, SW1E > 5BF > > (Registered number 166023). For a list of European legal entities within > > the Invensys Process Systems business group, please click here > > http://www.invensys.com/legal/default.asp?top_nav_idw&nav_id?&prev_idw > > . > > > > If you have received this e-mail in error, you are on notice of its > status. > > Please notify us immediately by reply e-mail and then delete this message > > from your system. Thank you for your co-operation. You may contact our > > Helpdesk on +44 (0)20 7821 3859 / 2105 or email > > inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto > may > > be subject to the terms of any agreements between Invensys (and/or its > > subsidiaries and affiliates) and the recipient (and/or its subsidiaries > and > > affiliates). > > > > > > > > > > _______________________________________________________________________ > > 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 > > > > > > > > > _______________________________________________________________________ > 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 > > > > > > > _______________________________________________________________________ > 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 > > _______________________________________________________________________ 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