Re: [foxboro] Grouping for compounds

I highly suggest that where applicable, that control blocks associated 
with the controls for a piece of equipment (like a distillation column, a 
batch kettle, etc.) be grouped within the same COMPOUND.  Where practical, 
blocks that are part of the same control strategy should be in the same 
COMPOUND.  Doing so will effect the block processing order, the ease of 
configuring the block and monitoring the block in FoxSelect, and numerous 
other reasons.  I believe Modbus gateways will require that Booleans be 
grouped in a COMPOUND separate from reals, but unless there are 
requirements to do so, don't separate Compounds by block type.

Neil Martin
Huntsman Performance Chemicals
Conroe & Dayton , TX. 
Conroe ph) 936-760-6205
Dayton ph)  936-257-4212
pager) 936-522-0052



Jeff Hurt <thehurtman@xxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
09/24/2008 10:46 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
[foxboro] Grouping for compounds






We are in the design phase for a new Foxboro I/A project.  For our 
compounds, we were considering having one compound for each type of block 
(AIN, COUT, etc).  It seems that this is a break from the norm, grouping 
by system.  Any thoughts as to why grouping by block type would be a bad 
idea?
 
Thanks,
Jeff
 
 
_______________________________________________________________________
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: