Re: [foxboro] IACC Product and Integration with existing I/A tool s

Q: Can IACC be used for modification/support of existing (I/A Version 6.3)
CP and INT30 databases?

A: No. IACC restrictions include:

a) V6.4 and later systems
b) A subset of all existing controllers. Notable among the missing are CP10s
and some, but not all 'A-style' CPs and Gateways. 

The list of supported equipment can be found in the IACC User Notes. The
V1.1 User Notes are in my possession and I can send them to you. However, I
know that they are out of date and that new stations have been added. 


Q: If a V6.3 CP database is "sucked" into IACC, changes made, and the =
result pushed back into the CP, can ICC still be used for that compound =
(or block) or is this a one way street (conversion)?

First, IACC does not suck. :)

Second, as mentioned above, it does not support V6.3.

However, there are parts of your question that still applies. I'll restate
them:
   Q: Can IACC and ICC share ownership of the same control station?
   A: No. Once IACC is used for a control station, it must own it forever
      more. This makes sense when you realize that any other operation would

      require determination of which version of the database is the "right"
      one.

   Q: Can IACC and ICC co-exist on the same system
   A: Yes. There is a configuration file that determines on a control
      station by control station basis which configurator may be used.


Q: If a whole CP database was built (and downloaded) using IACC, must IACC
be used for ALL subsequent changes to that database or can ICC be used for
daily support (block by block basis)?

A: Once IACC is used on a control station, it must be used forever more. Be
aware that the IACC does support single parameter changes just as the ICC
does.


Q: If sequence blocks are configured with IACC, can ICC be used to make
changes to these blocks (picking on these separately as blocks built with
SFC could not be changed with ICC Text editor so wondering if same issue was
here)?

A: Once the IACC owns a station, the ICC may not be used to change it.


Regards,
 
Alex Johnson
Invensys Process Systems
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Dehler, Glenn SCAN--
Sent: Wednesday, February 02, 2005 12:50 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] IACC Product and Integration with existing I/A tools

Greetings ... and thank-you all for the interesting and informative =
discussion on IACC.

I have a couple of questions that perhaps those knowledgeable in IACC =
could provide some insight.

Scenario:
Say you have an existing plant running I/A.  There are plans to expand =
the plant resulting in integration of new I/A equipment (Version 8) with =
the installed base (Version 6.3).  This new project is considering the =
use of IACC for generation of the loops.  When the project gets =
integrated, the IACC tool will arrive at the plant. =20

1) Can IACC be used for modification/support of existing (I/A Version =
6.3) CP and INT30 databases?

2) If a V6.3 CP database is "sucked" into IACC, changes made, and the =
result pushed back into the CP, can ICC still be used for that compound =
(or block) or is this a one way street (conversion)?

3) If a whole CP database was built (and downloaded) using IACC, must =
IACC be used for ALL subsequent changes to that database or can ICC be =
used for daily support (block by block basis)?

4) If sequence blocks are configured with IACC, can ICC be used to make =
changes to these blocks (picking on these spearately as blocks built =
with SFC could not be changed with ICC Text editor so wondering if same =
issue was here)?

What I am trying to avoid is having multiple tools that need to be used =
for daily support of a I/A System (FoxCAE, ICC, IACC).

In advance, thank-you for sharing. =20


Glenn Dehler

Shell Research Center
3655 36 Street NW    T2L 1Y8
Calgary, Alberta          Canada
Tel: +1(403) 284-6710    Fax: +1(403) 284-6662
Email: glenn.dehler@xxxxxxxxx
Internet: http://www.shell.ca

 
 
_______________________________________________________________________
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:             http://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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: