Re: [foxboro] IACC versus ICC
- From: "Marchal, Andre L." <AMarchal@xxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 10 Jan 2007 10:38:29 -0700
Thanks Tim & Howard. There is quite a bit of information there!
What I was hoping to get is a tag list from a configuration in IACC. We =
have not kept the taglist up to date in IACC, so I was hoping to be able =
to generate one from the configuration, the way FoxCAE can do it.
I just wished that Foxboro had not decided to stop development on FoxCAE =
before a new tool is available with "equivalent/better" features as =
FoxCAE. IACC is very powerful to configure large projects, but not so =
great for maintenance (I hope I learn to appreciate its features with =
time... I am new to this).
Andre
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Lowell, Timothy
Sent: Friday, January 05, 2007 9:06 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC versus ICC
Andre,
There is a workaround for the RIN/ROUT blocks in FoxCAE. I'll refer you
Howard Cossitt's e-mail to the list in reference to this problem.
//www.freelists.org/archives/foxboro/06-2006/msg00078.html
Tim Lowell
Control Systems Engineer
Tesoro Corporation
(office) 210-283-2929
(mobile) 210-253-0225
tlowell@xxxxxxxxxxx
=3D20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Marchal, Andre L.
Sent: Friday, January 05, 2007 9:58 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC versus ICC
Alex,
I agree with the statement made that the backdocumentation capabities of
=3D3D
IACC are lower than IACC. I ended up loading our CPs configured in IACC
=3D3D
on FoxCAE (for information only). I particularly like to follow block =
=3D
=3D3D
connections, even between CSDs.
However, going to 8.x, the RIN, ROUT blocks are not fully supported by =
=3D
=3D3D
FoxCAE. So, the taglist generated in FoxCAE lacks most of our analog =
=3D
=3D3D
I/Os. And there is no equivalent function in IACC. So, we are back to
=3D3D
maintaining the I/O list on a separate document. Did I miss anything or
=3D3D
did we lose this feature?
Andr=3D3DE9
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Johnson, Alex P (IPS)
Sent: Thursday, January 04, 2007 3:46 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IACC versus ICC
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,
=3D3D3D20
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
=3D3D3D3D09eg 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
=3D3D3D3D0A=3D3D3D3D0ANOTICE - This message and any attached files may =
=3D
contain
informatio=3D3D3D3D
n that is confidential and intended only for use by the intended
recipien=3D3D3D3D
t. If you are not the intended recipient or the person responsible for
de=3D3D3D3D
livering the message to the intended recipient, be advised that you have
=3D3D3D3D
received this message in error and that any dissemination, copying or
use=3D3D3D3D
of this message or attachment is strictly forbidden, as is the
disclosur=3D3D3D3D
e of the information therein. If you have received this message in error
=3D3D3D3D
please notify the sender immediately and delete the message.
=3D3D3D20
=3D3D3D20
_______________________________________________________________________
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
=3D3D3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Djoin
to unsubscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Dleave
=3D3D3D20
Confidentiality Notice: =3D3D3D0AThe information contained in this =3D3D
electronic m=3D3D3D
essage and any attachment(s) to this message are intended for the =3D3D
exclusi=3D3D3D
ve use of the recipient(s) and may contain confidential, privileged or =
=3D
=3D3D
pr=3D3D3D
oprietary information. If you are not the intended recipient, please =
=3D3D
noti=3D3D3D
fy the sender immediately, delete all copies of this message and any =
=3D3D
atta=3D3D3D
chment(s). Any other use of the E-Mail by you is prohibited.=3D3D3D0A
=3D3D20
=3D3D20
_______________________________________________________________________
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
=3D3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin
to unsubscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave
=3D3D20
=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
_______________________________________________________________________
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:
