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

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. =3D



  Enlighten us, are there situations where this would be both useful and
  Supported ?


  =3D

  Regards,


  Scott =3D


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

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