Re: [foxboro] CP60 Alarm Message
- From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 19 Mar 2008 08:28:17 -0400
It is permissible to use both Compound alarm groups and Station block
alarm groups for any given block.
Of course, any single alarm can be reported to one group, but different
alarms in the same block may go to different groups of either type.
Regards,
=
Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (voice)
713 329 1600 (switchboard)
713 329 1700 (fax)
alex.johnson@xxxxxxxxxxxxxxxx
=
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin_Fitzgerrell@xxxxxxx
Sent: Wednesday, March 19, 2008 12:49 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CP60 Alarm Message
Scott,
I'm still not clear on whether you're saying the use of both compound
and station level alarming must be avoided, I don't see anything
documented about this as a limitiation. Can you clarify?
Yes, there are good reasons for using both station block and compound
group devices at the same time.
The station block devices and groups let you define 16 alarm
destinations and 5 groups. There is/was an issue with one of the
station groups (group 8 I think) where it would be overwritten with
seemingly random data (fixed in 6.4 or one of the 6.5 control releases I
think). If you have a CP dedicated to a single operating group, that is
probably enough groups and devices. If your CP spans 2 or 3 plant areas
you may end up with:
Group 4 - alarms go to control room 1 workstations, printer log 1 and
historian
Group 5 - alarms go to control room 2 workstations, printer log 2 and
historian
Group 6 - alarms go to control rooms 1 and 2 workstations, printer logs
1 and 2, and historian(s)
Group 7 - alarms go to historian only
Group 8 - not used because of random overwrite problem
Another good use for a station group would be to send Bad I/O alarms to
a separate printer log for E&I.
Sometimes I want to configure an alarm to use the alarm detection
features but not actually send the alarm message anywhere. I could use
a valid group and inhibit it, but my preference is to pick group 3 and
send all of these types of alarms there. =3D20
Sometimes I have one group or piece of equipment that needs to alarm to
a different location, probably because it's managed by a different
operating unit and ended up on this CP because it's the only one that
had I/O anywhere nearby. My preference is to put equipment like this in
it's own compound and set up compound level alarming.
CPs for control of common utilities introduce their own set of problems
- sometimes there is equipment that should alarm to many or all control
rooms or groups of operators, so the 16 devices available to groups 4-8
is handy. Other groups of equipment should only alarm to one control
room, or one group of operators in a common control room, but there may
be many groups of this kind of equipment with different alarm
destinations for each group, so the compound alarm groups 1-3 are best
for those.
Regards,
Kevin FitzGerrell
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Landry, Scott
Sent: Wednesday, March 19, 2008 9:56 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CP60 Alarm Message
Kevin,
I've always done alarm destinations either with the station block or
Compound group device not both at the same time. =3D3D
Enlighten us, are there situations where this would be both useful and
Supported ?
=3D3D
Regards,
Scott =3D3D
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin_Fitzgerrell@xxxxxxx
Sent: Tuesday, March 18, 2008 7:48 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CP60 Alarm Message
Scott,
Could you elaborate on the station block and compounds both being
configured? I hadn't noted this being a prohibited configuration
before.
Regards
Kevin FitzGerrell
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Landry, Scott
Sent: Wednesday, March 19, 2008 9:44 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] CP60 Alarm Message
Check this first
Is devmon.cfg the same on a potential masters and slaves ?
Is the devmon executable compatible with all potential masters and
slaves?
Also check that the station block and compounds have not both been
=3D3D3D3D
configed for Alarm Destinations.
Regards,
Scott of the living
=
=
_______________________________________________________________________
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=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
* 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 legal=
ly privileged. This email is from the Invensys Process Systems business uni=
t of Invensys plc which is a company registered in England and Wales with i=
ts registered office at Portland House, Bressenden Place, London, SW1E 5BF =
(Registered number 166023). For a list of European legal entities within t=
he Invensys Process Systems business group, please click here http://www.in=
vensys.com/legal/default.asp?top_nav_id=3D77&nav_id=3D80&prev_id=3D77.
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 Help=
desk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx T=
his e-mail and any attachments thereto may be subject to the terms of any a=
greements 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
Other related posts:
