Re: [foxboro] Block Equivalents List

Jack,

The block equivalent tables and associated guidelines have lots of shortcomings.
 For what they are worth:

Maximum block equivalents
CP10     300
CP30    1000
CP30B   1000
CP40    2000
CP40B   2000
CP50    3000
CP60    4000

CP:
All blocks count as one (including ECBs) except the following:
CALC - 3 block equivalents
DPIDA - 2 block equivalents
PIDE - 2 block equivalents
PIDX - 2 block equivalents
PIDXE - 2 block equivalents
PIDA - 2 block equivalents
PLB - 2 block equivalents
ECB8 - 3 block equivalents
MON - 4 block equivalents
EXC - 6 block equivalents*
DEP - 6 block equivalents*
IND - 6 block equivalents*
* Add one block equivalent for each additional 25 lines of logic.

My notes also indicate that each alarm indication is 1 block equivalent.

Regards,

Kevin FitzGerrell
Carter Holt Harvey, Ltd.
+64 27 460 9994

Quoting "Jack.Easley@xxxxxxx" <Jack.Easley@xxxxxxx>:

> Does anyone have a handy-dandy list of I/O Loading block equivalents
> for
> the most common Foxboro blocks they are willing to share? I know
> Foxboro
> 
> has spreadsheets available for this, and that other factors affect
> CP/GW
> 
> loading, but I could use a better grasp of block equivalents to quickly
> 
> check loading problems.
> 
> 
> 
> A list of other CP/GW loading factors such as peer-2-peer, display,
> 
> historian, and PI connections and how one calculates (rsom, sipc, etc)
> 
> how significantly they affect CP/GW loading would be useful to most of
> 
> us also.
> 
> 
> 
>  
> 
> 
> 
> Appreciate it ...
> 
> 
> 
> Jack Easley
> 
> 
> 
>  
> 
> 
> 
>  
> 
> 
> 
> 
> 
> Confidentiality Notice: This email message, including any attachments, 
> 
> contains or may contain confidential information intended only for the 
> 
> addressee. If you are not an intended recipient of this message, be 
> 
> advised that any reading, dissemination, forwarding, printing, copying
> 
> or other use of this message or its attachments is strictly prohibited.
> If
> 
> you have received this message in error, please notify the sender 
> 
> immediately by reply message and delete this email message and any
> 
> attachments from your system.
> 
> 
>  
>  
> ______________________________________________________________________
> _
> 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: