Re: [foxboro] IACC versus ICC
- From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 11:28:00 -0500
Re: IACC seems to be only an interim product between the ICC and the IEE
As I said at the User's Group meeting, ALL products are interim
products.=20
We are committed to maximizing the retention of your Intellectual and
Physical Assets over time, but we are not going to commit to
consistently enhancing any particular product.
To that end, the IEE can import IACC templates and control blocks.
Re: IACC future development
It is true that new feature development for IACC will be minimized, but
there are no formal plans at this point to put it in the Mature state,
i.e., stop enhancement.=20
That may occur at some point, but it has not yet occurred.
Re: IEE
The IEE - today - cannot do everything that the IACC can do. In
particular, it is limited to newer equipment. That is, equipment and
software that is in the Preferred state as of V8.2.
The following provides a brief comparison among ICC, FoxCAE, IACC, and
IEE:
Number of databases per system
=09ICC: 1/CP =20
=09FoxCAE: =20
IACC: 1 / CP =20
IEE: 1 =20
Comments: IEE does not support by unit modularity for
configuration.
That is there is exactly one IEE server per system. IACC
allows multiple servers per system, i.e., by unit
modularity.
Number of controllers per database
=09ICC: 1 =20
=09FoxCAE:
=09IACC: 1-3 =20
=09IEE: All =20
=09Comments: IACC does not support putting everything in one
database so
peer-to-peer connections may need to be entered by hand.
IEE
does not have this limitation. ICC always requires by
hand
connection specification.
Number of users per database =20
=09ICC: 1 =20
=09FoxCAE: =20
=09IACC: 1 =20
=09IEE: Many - limited by performance
=20
System Definition Support Built-in
=09IEE: N =20
=09FoxCAE: N
=09IACC: Y (V6.4 and up)
=09IEE: Y (V8.2 and up)
Control Scheme Templates =20
=09ICC: N =20
FoxCAE: Y =20
=09IACC: Y =20
=09IEE: Y =20
Graphical generation of control schemes =20
=09ICC: N =20
=09FoxCAE: N =20
=09IACC: Y =20
=09IEE: Y =20
Animated Loop Drawings =20
=09ICC: N =20
=09FoxCAE: N =20
=09IACC: Y
IEE: Y =20
HMI Building Integrated =20
ICC: N =20
FoxCAE: N =20
IACC: Y =20
=09IEE: N (On the roadmap for InFusion View, FoxView is TBD)
Device Templates =20
ICC: N =20
FoxCAE: N =20
IACC: Y =20
=09IEE: Phase 2
FDT Support for FF =20
=09ICC: N =20
FoxCAE: N =20
IACC: Y in IACC V2.2 =20
IEE: Phase 2
FDT Support for HART/FoxCom
=09ICC: N =20
FoxCAE: N =20
=09IACC: N
=09IEE: N =20
=09Comment: In all cases, FDM (PACTware) for HART and FoxCom is
used
InFusion Application Environment Support
=09ICC: N =20
=09FoxCAE: N =20
=09IACC: N
=09IEE: Y =20
Scriptable Operation/Open database
=09IEE: Y (ICC Driver Task)
=09FoxCAE: Y (FoxPro Database)
=09IACC: N =20
=09IEE: Phase 2 (SQL Server used, but objects and object
attributes
are not necessarily accessible and the schema is not
not published for external acces. Tools will be added to
provide access to the data
Workfile support:
=09IEE: Y
=09FoxCAE: Y (also keeps a separate database)
=09IACC: Y (also keeps a separate database)
=09IEE: N (Everything stored in SQL Server)
Regards,
=20
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Hicks, Gaylon F
Sent: Thursday, January 04, 2007 9:01 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC versus ICC
Hi Shaun,
One thing to consider with the IACC is the upcoming InFusion Engineering
Environment (IEE), which (personal opinions only loosely based on facts
to follow) appears to be future direction for I/A, and the IACC seems to
be only an interim product between the ICC and the IEE at this point in
time.
Based on what I saw at the Users Conference this year, and conversations
with unnamed sources, we are going to completely skip the IACC here at
our plant. We plan on sticking with the ICC for now, even on a new 8.2
system we are installing, and will likely go straight to the IEE when we
upgrade in the future. From what we saw in Dallas the IEE looks pretty
cool. The only gripe I have about the IEE based on very limited
knowledge is that it isn't certain that the ICCdrvr tasks will work
anymore. =3D20
Any dispute out there that the IACC is (almost) a dead end product at
this point in time? Anybody out there knowledgeable of the inner
workings of the IEE that would care to explain how checkpoint files,
work files, etc., are being handled (or not) in the IEE? =3D20
Anybody noticed that I (really) like parentheses?
Thanks,
Gaylon Hicks
TVA - Browns Ferry NP
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Goldie, Shaun S
Sent: Wednesday, January 03, 2007 8:13 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] IACC versus ICC
=3D3D20
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
=3D3D0A=3D3D0ANOTICE - This message and any attached files may contain
informatio=3D3D
n that is confidential and intended only for use by the intended
recipien=3D3D
t. If you are not the intended recipient or the person responsible for
de=3D3D
livering the message to the intended recipient, be advised that you have
=3D3D
received this message in error and that any dissemination, copying or
use=3D3D
of this message or attachment is strictly forbidden, as is the
disclosur=3D3D
e of the information therein. If you have received this message in error
=3D3D
please notify the sender immediately and delete the message.
=3D20
=3D20
_______________________________________________________________________
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
=3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
Confidentiality Notice: =0AThe information contained in this electronic m=
essage and any attachment(s) to this message are intended for the exclusi=
ve use of the recipient(s) and may contain confidential, privileged or pr=
oprietary information. If you are not the intended recipient, please noti=
fy the sender immediately, delete all copies of this message and any atta=
chment(s). Any other use of the E-Mail by you is prohibited.=0A
_______________________________________________________________________
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:
