Re: [foxboro] IACC versus ICC
- From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 17:45:51 -0500
The support of existing systems in the IEE is an on-going effort.
Delivery of that support is sometime away; hence, my recommendation of
IACC.
Today, IEE does not exceed IACC for back documentation (FoxCAE remains
the best at that). However, it is an area that is being worked.
LOOPID is the key used by FoxCAE, IACC, and IEE to group imported blocks
into control strategies. If you use it for "free text", the grouping
will not be terribly useful on import into any of these configurators.
Does this help?
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 Goldie, Shaun S
Sent: Thursday, January 04, 2007 4:19 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC versus ICC
Hmmmm this is turning into a very interesting thread
Thanks Alex for your extended effort with the configurator comparisons
I hadn't considered IEE didn't realise it had progressed so far
? How will IEE support hybrid 6.5.x/7.x/8.x systems that include modules
only supported by sysDef
=3D09eg MB+ integrators and COM15 gateways
The suggestion for me to migrate to FCP's using ICC then change to IEE
at a later date looks inviting
? will IEE be any better at back engineering than IACC
? What are the rules for the loopID field when importing a saveAll into
IACC/foxCAE/IEE using the loop ID grouping
We have only used loop ID as free text but it seems the starting point
to improve changing configurators
Shaun
NZ Steel
=3D0A=3D0ANOTICE - This message and any attached files may contain
informatio=3D
n that is confidential and intended only for use by the intended
recipien=3D
t. If you are not the intended recipient or the person responsible for
de=3D
livering the message to the intended recipient, be advised that you have
=3D
received this message in error and that any dissemination, copying or
use=3D
of this message or attachment is strictly forbidden, as is the
disclosur=3D
e of the information therein. If you have received this message in error
=3D
please notify the sender immediately and delete the message.
=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:
