Re: [foxboro] IACC versus ICC
- From: "Lowell, Timothy" <TLowell@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 07:53:04 -0600
Shaun,
You may also want to consider that the new InFusion product line from
Invensys includes the InFusion Engineering Environment (IEE), which will
eventually supersede IACC as the configuration tool of choice for the
I/A system. As I understand it, and please, all you Invensys folks jump
in and correct me if I am wrong, but IACC is essentially on the same
track as FoxCAE, supported indefinitely but not being further developed.
IEE requires v.8.2 or higher, so depending on when you expect to upgrade
to that version, this may be of interest to you. Certainly, many of the
skills learned using IACC would be transferable to IEE, but it is a
different product with a different interface, and you may want to jump
right into IEE without first going to IACC.
Tim Lowell
Control Systems Engineer
Tesoro Corporation
(office) 210-283-2929
(mobile) 210-253-0225
tlowell@xxxxxxxxxxx
=20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of cleddon@xxxxxxx
Sent: Wednesday, January 03, 2007 10:14 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC versus ICC
If this is your first attempt at IACC and you are not familiar with
programs such as FoxCAE and you are converting online, I would probably
recommend that you go ahead and run the scripts on the code you already
have. The automation of the conversion through SED and AWK combined with
the other command line tools will be significantly quicker than learning
and correctly implementing IACC. =20
=20
I am not aware of your system configuration but if you are going to
FCP's then 8.X is somewhere in the mix and an AWXP will hosting the
processors with a Mesh network is in the background. If this is all
new, then you don't need the added complexity of IACC to divert you from
the end goal of getting online and stable. =20
=20
After the implementation of the ICC solution, take your time and
experiment with IACC and regenerate the same blocks in IACC to get
experience with the program. You can generate the CSD's and link the
blocks to build a second set of compounds to compare with the first.
The real strength of IACC is realized in a production environment where
you don't have any legacy code to work from but you have hundreds or
thousands of blocks to generate and a well defined set of primitives to
reference. The exercise of learning IACC is considerable but IACC can
be very useful after you have learned all of the tricks.
=20
Of course I am assuming you don't have a lot of time available before
the new code needs to be operational (less than a month). If so, and
you are planning to go IACC for all future mods you may be able to pull
it off. I was assuming about 2 weeks for the code conversion and
installation using ICC.
=20
Hopefully your system includes a test bed for offline code development
and testing since the new 8.X systems no longer support virtual CPs.
=20
CDLeddon
Invensys Foxboro Atlanta
770-331-4303=20
=20
=20
-----Original Message-----
From: Shaun.Goldie@xxxxxxxxxxxxxxxxxx
To: foxboro@xxxxxxxxxxxxx
Sent: Wed, 3 Jan 2007 9:12 PM
Subject: [foxboro] IACC versus ICC
=3D20
Hi there
I am about to embark on collapsing a CP30A and Modbus Plus Gateway into
a FCP270
Does anybody have a justification for staying with ICC (or not)
At NZS we don't use FoxCAE but I figured that the above job justifies
going to IACC
Normally we would use ICCdrvr scripts and they work well especially as
this job is online and progressive compound by compound
ON the surface introducing IACC is the biggest risk on this job and
creates plenty of opportunity for stuffups
There is no doubt the IACC visualisation of the configuration is the
standard expected these days but with ICC/scripts we have the power
Shaun
NZ Steel
_______________________________________________________________________
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:
