Re: [foxboro] Grouping for compounds

Jeff,
IMHO...

I have seen it all in my 28+ years of Foxboro's use of the
Compound:Block concept as a Foxboro employee, as an end user, and as a
3rd party provider; yes, this concept was used before the IA System in
the Spectrum world.  I have been forced to work with Compounds by Block
types, by Loops names, by FBMs, by physical areas, and many others.  My
recommendations would be to divide your process areas/units into logical
Compound names; hopefully with about -/+ 200 blocks each.  It will be
the most flexible and efficient method.  The reasons are too numerous to
mention and can only be realized once you have made the mistake of doing
it a different way.  Think of the most basic of control loops (the PID)
in 3 different compounds?  Or a Compound of AINs with alarms that need
to go to 20 different areas/workstations/historians/printers with only 8
groups of 8 devices to work with?

Just my 2 cents...


Joseph M. Riccardi 
DCS Services - Industrial Process Control 
  
North-Central Office (OH, PA, MI, IN, WV area) 
South-East Office (FL, GA, AL, SC, NC area) 

Joe@xxxxxxxxxxxxx 

"To give real service you must add something that cannot be bought or
measured with money; and that is sincerity and integrity." - Donald A.
Adams


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