Re: [foxboro] One more question...
- From: "Deathos, Matthew" <matthew.deathos@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 4 Jan 2007 15:01:09 -0500
To follow-up on Alex's response,
Yes, an IACC database can contain multiple CP databases up to roughly the
12,000 block limit.
Further the IACC server can can contain multiple IACC databases with each IACC
database containing 1 or more CP databases.
Each IACC database is editable by one user at a time as Alex mentioned. This
makes the decision on how you divide up your CP databases into IACC databases
important of course. In most cases we recommend a 1 to 1 relationship between
IACC database and CP databases to alleviate this concurrency issue and conform
with the current limits established by ICC and FoxCAE.
(Couldn't help throwing in my two cents...)
Regards,
Matt DeAthos
IA Series Product Manager and former IACC project team member.
________________________________
From: foxboro-bounce@xxxxxxxxxxxxx on behalf of Johnson, Alex P (IPS)
Sent: Thu 1/4/2007 2:43 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] One more question...
In IACC, a database may hold one or more CP database.
IACC is an ICC replacement. It exceeds the ICC in every respect
including the size of the database. It's most commonly perceived
limitations are:
1) Its database architecture supports only 12,000 objects in a database
(about 3 CPs maximum)
2) Only one person may edit a database at a time.
Relative to the ICC, #2 is no different especially if the database is
limited to one CP as you suggest.
Thus, IACC is a very good ICC replacement though by no means is it the
ultimate configuration tool. We hope that IEE will grow to be as great
an improvement over IACC as IACC is over the ICC.
Note: FoxCAE users like their tool combined with ICC, but it has reached
a mature state and does not handle some of the new features, e.g., FF
device configuration.
Make sense?
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 Brazell, Troy L Jr
Sent: Thursday, January 04, 2007 12:12 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] One more question...
Question .....
Can two databases co-exist within the IACC?
In other words can the CP's have there own database?
Thanks
Troy
**************************
Troy Brazell
DCP Midstream
ISA CCST
Sr. Process Control Analyst
Office 405-263-4130
Cell 405-301-2994
tlbrazell@xxxxxxxxxxxxxxxx
**************************
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Thursday, January 04, 2007 11:53 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] One more question...
As in all decisions, there are trade-offs.
IEE supports only V8.2 and later and only equipment that was preferred
in that release (so not 100-Series I/O). It also lacks FV integration
which can be a big time saver for new projects.
IACC supports from V6.4 and later and all station types. It has FV
integration.
Both IEE and IACC have similar configuration tool sets though IEE is
much better looking.
If the project is grassroots new, IEE is the better control
configuration tool.
If the project has any older equipment or could benefit from FV
integration, IACC is the better choice.
Does that help?
(I really should learn to avoid short answers. :))
Regards,
=3D3D20
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 Jeremy Milum
Sent: Thursday, January 04, 2007 10:14 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] One more question...
On 1/4/07, Johnson, Alex P (IPS) <alex.johnson@xxxxxxxxxxxxxxxx> wrote:
> I strongly recommend that you get and use IACC. This configurator is
> much more modern than the much, much older ICC. It supports graphic
loop
> templates and integration with FoxView among other features.
IACC and not IEE?
=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:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave
=3D3D20
Confidentiality Notice: =3D3D0AThe information contained in this =3D
electronic
m=3D3D
essage and any attachment(s) to this message are intended for the
exclusi=3D3D
ve use of the recipient(s) and may contain confidential, privileged or
pr=3D3D
oprietary information. If you are not the intended recipient, please
noti=3D3D
fy the sender immediately, delete all copies of this message and any
atta=3D3D
chment(s). Any other use of the E-Mail by you is prohibited.=3D3D0A
=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
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
-- File: winmail.dat
_______________________________________________________________________
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:
