Re: [foxboro] New (Soon to be) Foxboro IA User
- From: "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 5 Jun 2002 09:42:15 -0400
I would add
Learn and use FoxCAE to implement your control schemes and perform back
documentation.
Regards,
Alex Johnson
Invensys
10707 Haddington
Houston, TX 77063
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx <mailto:ajohnson@xxxxxxxxxxx>
Come to the Invensys Showcase: http://www.invensysshowcase.com/
<http://www.invensysshowcase.com/>
-----Original Message-----
From: Jriccardi@xxxxxxx [SMTP:Jriccardi@xxxxxxx]
Sent: Wednesday, June 05, 2002 8:36 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] New (Soon to be) Foxboro IA User
As the original inquiry was from a new IA System user looking for
Do's/Don'ts
(although some of the suggestions below are not necessarily limited
to the IA
System) ...
The use of the Station Block's alarming groups will require
strategic
distribution (i.e., process units, etc.) of the Compounds:Blocks
among the
CPs/ABs.
Thoroughly document your requirements, specifications, plant
standards, etc.
IA System changes are cumbersome.
Preconfigure standard/common control loops; test the complicated
ones.
Do not proceed with configuration until the database (Tag #,
Description,
Range, etc.) is 100% accurate. If not, subsequent changes (even if
minor)
can be a nightmare, as they typically impact multiple blocks,
displays, etc.
and must be implemented manually (utilities are no help).
A major cost savings can be realized by using common Tag/Block names
(with
different Compound names) for duplicate/similar process units; even
if this
requires the use of a prefix/suffix (i.e., A/B/C/..., or 1/2/3/...,
etc.).
If there is flexibility with the Tag naming convention, there are a
number of
methods/utilities (FoxCAE, FoxAPI, etc.) that can be used to
replicate
Compounds/Blocks to save on configuration costs; especially when
changes are
required in the future.
Do not modify the standard faceplates, as they may be overwritten on
subsequent version upgrades. Use custom overlays, etc.
Use a 3rd party software package to test 100% of the I/O and the
control
strategies before installation and startup.
I'm sure there are many others ...
Good luck.
Joseph M. Riccardi
www.eRiccardi.com
(440)-458-4411 Business
(440)-725-4025 Cell
Joe@xxxxxxxxxxxxx eMail
In a message dated 6/4/2002 8:14:57 PM Eastern Standard Time,
pbruley@xxxxxxxxxxx writes:
> Subj:Re: [foxboro] New (Soon to be) Foxboro IA User
> Date:6/4/2002 8:14:57 PM Eastern Standard Time
> From:<A HREF="mailto:pbruley@xxxxxxxxxxx";>pbruley@xxxxxxxxxxx</A>
> Reply-to:<A
HREF="mailto:foxboro@xxxxxxxxxxxxx";>foxboro@xxxxxxxxxxxxx</A>
> To:<A
HREF="mailto:foxboro@xxxxxxxxxxxxx";>foxboro@xxxxxxxxxxxxx</A>, <A
HREF="mailto:bwingard@xxxxxxxxxx";>bwingard@xxxxxxxxxx</A>
> Sent from the Internet
>
>
>
>
> Don't use Alarming Groups 1,2 or 3
>
> Make use of Alarming Groups 4 thru 8 as they are all controlled
through the
> "Station" block and make life much easier to implement changes in
future.
>
> ----------
> From: Bob Wingard
> Sent: Friday, May 31, 2002 8:51 PM
> To: FoxboroList
> Subject: [foxboro] New (Soon to be) Foxboro IA User
>
> Hello List,
>
> This is great, I wish there was a list like this for our
current
> system.
>
> We have decided to replace our brand H DCS with a Foxboro
IA
> system. I am looking for Do's Don'ts etc. for IA. Specifically
things that
> you would have done differently or not at all when you purchased
your
> system. I have already learned a great deal from looking at the
archive (60
> ohm input impedance and HART).
>
> System will install in December.
>
> System configuration is starting to firm up and the system
will look
> something like this:
> 3 CP60ft Approx. 900 I/O - 200 series FBM's
> 3 AB I30ft Approx. 3000 discrete points
> 2 AW70A
> 1 AW70C Server
> 10 WP70s all dual screen
>
> Thanks,
>
> Bob Wingard
> Process Control Engineer
> Inland Paperboard and Packaging
> Orange, Texas
> (409) 746-7525
_______________________________________________________________________
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:
//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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
