Re: [foxboro] A&E interface Specification
- From: "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 30 Jul 2004 16:25:34 -0400
AIM*AMI (Alarm and Message Interface) is a tool for examining the alarm and
message (process alarms, sequence block messages, SOE, OAJ, and SymMon msgs)
in the AIM*Historian.
For Alarm Analysis we recommend that you work with our Alarm Analysis team
in Houston. They have tools to examine your alarm situation and make
recommendations on how to adjust your system to respond intelligently.
Contact Dave Gaertner at
713.722.2700
dgaertne@xxxxxxxxxxx
for more information.
With regard to creating an alarm filter, that is possible. FoxPage/Event
Driven Scripts is an alarm filter that checks incoming alarms and takes
action on them.
However, the work is non-trivial.
Regards,
Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (operator)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
For the latest information on ArchestrA, go to
http://www.invensys.com/Archestra.html.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Jaime Claramunt R. (Inforsa)
Sent: Friday, July 30, 2004 1:08 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] A&E interface Specification
I'm interested too...
operation guys allways ask for "every" alarm available...and this results in
too much events to present and handle, besides "heavy" logics to
discriminate special conditions when to alarm when don't...
thanks
regards
Jaime Claramunt
INFORSA Paper Mill
-----Mensaje original-----
De: Wiggins, Bryan [mailto:Bryan.Wiggins@xxxxxxxxxxxxxx]
Enviado el: Viernes, 30 de Julio de 2004 13:44
Para: foxboro@xxxxxxxxxxxxx
Asunto: Re: [foxboro] A&E interface Specification
Hi Jim could you elaborate on the practice call "Alarm Rationalization" =
for myself and others who may not be familiar?
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Pan, Jim
Sent: Friday, July 30, 2004 11:37 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] A&E interface Specification
I would recommend that you go through a practice called "Alarm
Rationalization" to eliminate nuisance alarms on your I/A system. So =
what's
left in the Alarm Manager display are "valid" alarms.
Jim Pan
Lifetime Learning
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Tjidde Boers
Sent: Friday, July 30, 2004 7:24 AM
To: 'foxboro@xxxxxxxxxxxxx'
Cc: (MailTest) Hidde Schouten
Subject: [foxboro] A&E interface Specification
Dear all,
=20
We currently need an Alarm interface with an IA DCS application. The =
plan is
that we read all alarms from the IA system and send only the valid alarm
back to the IA system (Alarm filter). I understand that the AIM*AT OPC
server does not support the A&E specification, so I'm now looking for an
alternative interface. Can anybody help us in locating a good =
alternative? I
found a "AIM*AT Alarm & Message interface" in our AIM API Admin tool. =
Could
this provide OPC like A&E functionality? If so how can I find the
specification for this interface
=20
Tjidde Boers
=20
MAGION Industrial Software Solutions bv
Phone: +31 (0)70 444 2770
Fax: +31 (0)70 444 2082
Mobile: +31 (0)655 894 628
E-mail: <mailto:t.boers@xxxxxxxxx> t.boers@xxxxxxxxx
=20
Notice of Confidentiality
This transmission is intended for the named addressee only. It contains
information which may be confidential and which may also be privileged.
Unless you are the named addressee (or authorised to receive it for the
addressee) you may not copy or use it, or disclose it to anyone else. If =
you
have received this transmission in error please notify the sender
immediately.
=20
=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
=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
_______________________________________________________________________
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
_______________________________________________________________________
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
_______________________________________________________________________
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: