Re: [foxboro] Grouping for compounds

Using the process unit as the driver for grouping also allows code to be 
developed once and deployed many times to common units.
That is if you have several identical units, you can develop the code for 
unit1, and then copy the entire contents of unit1 to unit2 and not have to make 
all the connection changes.


Ken Moore
Celanese
Enoree, SC 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of Jeff Hurt
Sent: Wednesday, September 24, 2008 11:46 AM
To: foxboro@xxxxxxxxxxxxx
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: