Re: [foxboro] AW: LINE PRINTER REPLACEMENT

No whip.  Will a Taser work?  But our new one is, well, new, so I guess I 
will cut her some slack :)


If I got AIM*, I likely would use it for the system historians as well.  I 
envision running two on-platform instances, and probably one off-platform 
one that collected data from the two on-platform ones; that third one 
would then feed data to our site process historian, any 3rd-party alarm 
management software, process/loop diagnostic software, whatever the 
initiative-du-jour came up with, in hopes that system load would stay 
relatively constant.  If the off-platform box gets buried (not likely, 
given the power of current PC hardware) we say a eulogy and buy a bigger 
one.  And we would have a readily-available "backup" source of data if the 
site server(s) got hosed.


In truth, I really haven't checked the pricing.  My comment referred to a 
conversation in passing I had with our old account manager.  I'm sure if I 
formally asked for a quote on AIM* I could get it.  I just wasn't looking 
at that time; the legacy historians met our needs (still do, really, for 
on-system stuff).


Corey Clingo
BASF Corporation






"Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
12/14/2006 09:54 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
Re: [foxboro] AW: LINE PRINTER REPLACEMENT






A regional sales manager once told me that Account Reps are best managed
with a whip. Do you have one? :)

FYI. AIM*Historian is licensed on a per real-time point monitored basis.
Gathering and logging messages does not require real-time points so you
may buy the smallest license. I find it difficult to believe that the
price of AIM*Historian will be the hang up for alarm analysis since you
can load one "somewhere" to get just the alarms of interest.


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 Corey R Clingo
Sent: Thursday, December 14, 2006 9:48 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AW: LINE PRINTER REPLACEMENT

Yes, I am interested in a database approach as well, and want to play=20
around with Postgres.  Grep and Ctrl-F in Notepad work pretty well for=20
forensics, but are getting a little winded when doing heavy-duty alarm=20
analysis.  Something to keep me off the mean streets of Lake Jackson, TX

during my upcoming time off I suppose.


I guess I also need to ask my new account manager about AIM*, as a
general=20
data store/supply to external systems.  My old one tried to sell it to
me,=20
and I asked him to "make me an offer I can't refuse", but I never heard=20
anything...


Corey Clingo
BASF Corporation






"Jeremy Milum" <jmilum@xxxxxxxxx>=20
Sent by: foxboro-bounce@xxxxxxxxxxxxx
12/13/2006 09:26 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
Re: [foxboro] AW: LINE PRINTER REPLACEMENT






On 12/13/06, Corey R Clingo <corey.clingo@xxxxxxxx> wrote:
> Personally, I use the sLumberjack (tm) alarm logger -- "we log your=20
alarms
> while you sleep"  (that would be two legacy historians and some shell
> scripts  :)

sounds like my solution except I have sLumberJack+ (i added a
PostgreSQL database as a backend to hold all the alarms for archiving
and analysis)

I will of course send you the royalties for the use of the name ;)



=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
 
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

Other related posts: