Corey. If by "operator action messages get garbled" you mean that the first two characters of a number of the (AIM* table) fields are lost then this is the subject of CAR 1008305 - the problem probably lies with the Current Alarm Display and not the historian. A QF has been available and has been rolled into I/A ver. 8.4.2 . Further information is available via the Global Client Support website http://support.ips.invensys.com . Regards, Martin Theobald -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Corey R Clingo Sent: 30 January 2009 18:07 To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Best Alarm Package for Ver 8 MESH We have PlantStateSuite from PAS here, and I find that the situation is just the opposite. The PAS principals come from a Honeywell background, and PAS software reflects that by trying to make everything look like Honeywell. While much of the philosophy between TDC and I/A is common, some is not, and the terminology is different; this has already caused some confusion with people doing alarm management activities here. Another issue is that PSS does not understand the concept of alarm destinations, so you might have data showing up in your alarm reports than never emits a peep at an operator console. I had to write some custom scripts here to collect and filter the alarm data before sending it to the PAS alarm server to get around that. That said, we are getting some value out of it (as we probably would with any alarm management tool). The UI in the client looks nice, but is surprisingly unintuitive for infrequent users; however, we mostly work from canned reports anyway. The I/A collection interface actually works better than the TDC one (!), so I personally can't complain too much there. We do have an issue on our one v8 system where operator action messages get garbled, but we've determined that that is a problem with the AIM*ODBC driver, which PSS uses for collection on that system. It's not my plant so I don't know if they ever resolved it. I have never used Matrikon alarm management, so I don't know about them. But TiPS' package looked functional if not necessarily pretty, and they've been doing I/A for a long time. Also, PSS is definitely a "full blown alarm management package" that is quite complex. Corey Clingo BASF Corporation "Jenckes, Jim R." <JJenckes@xxxxxxxxxxx> Sent by: foxboro-bounce@xxxxxxxxxxxxx 01/30/2009 10:44 AM Please respond to foxboro@xxxxxxxxxxxxx To <foxboro@xxxxxxxxxxxxx> cc Subject Re: [foxboro] Best Alarm Package for Ver 8 MESH We are presently using Matrikon, but have heard the of another company that may be better integrated into the I/A world. You might want to check these folks out PAS. Check out this link http://news.thomasnet.com/fullstory/478442 for some info. There also is a website www.pas.com, but I had trouble getting to it. Jim Jenckes, CCST Process Controls Specialist Tesoro Alaska Co. 907-776-3865 -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Jack.Easley@xxxxxxxxxxxx Sent: Saturday, January 24, 2009 9:56 AM To: foxboro@xxxxxxxxxxxxx Cc: Clifford.Adams@xxxxxxxxxxxx Subject: [foxboro] Best Alarm Package for Ver 8 MESH Group, I am looking for recommendations for the best 3rd party package to deal with alarm and alarm message extraction from the AIM Historian. I know Tips has been around a long time, but have heard yeas and nays about it. I've also heard FoxRay is pretty good. Ideally, I'd like to hear from someone with experience with several of these options to determine the best. The only thing we are looking for is a simple Windows AIM alarm/alarm message extraction application that is easy to search and create simple reports on an infrequent basis. We don't really need a full blown alarm management package that is overly complicated. Thanks in advance, Jack Easley Sr. I&C Technician Luminant Power, Martin Lake Plant Phone 903.836.6241 jack.easley@xxxxxxxxxxxx _______________________________________________________________________ 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: 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_id=77&nav_id=80&prev_id=77. 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