Re: [foxboro] Grouping for compounds

I have seen worse ...

Like the site where someone thought it would be a great idea to have all
the blocks in Compounds sorted alphabetically - by block type ... as in
AIN, AOUT, CALC, PID .. etc. !

We found out when they complained of slow loop response...

Regards,

Barry Heap

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Corey R Clingo
Sent: Thursday, 25 September 2008 2:29 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Grouping for compounds

This was done back in 2003 on a project in one of my plants.  1 compound

for analog, 1 for discrete, and one for CALC-ish blocks (!).

IMHO, it's a drag.


We don't have the alarm destination issues, as the 3 compounds all refer

to the same section of the plant.  But the switching back and forth 
between compounds in Select, and having to use full pathnames on every 
connection between different block types, is enough to convince me not
to 
do it again (we still have DM in this plant, so no tree views as in 
FoxSelect).


The fact that the blocks aren't in loop alphabetical order (except where

loop processing dictates otherwise), as is my personal standard
practice, 
further exacerbates the problems.


Corey Clingo
BASF Corporation






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
 


* 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 legally 
privileged. This email is from the Invensys Process Systems business unit of 
Invensys plc which is a company registered in England and Wales with its 
registered office at Portland House, Bressenden Place, London, SW1E 5BF 
(Registered number 166023).  For a list of European legal entities within the 
Invensys Process Systems business group, please click here 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.

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 Helpdesk on 
+44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail 
and any attachments thereto may be subject to the terms of any agreements 
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:             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: