Re: [foxboro] FXBAIS vs PI OPC Interface
- From: "Kubbenga, Otto" <otto.kubbenga@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 26 Jun 2008 09:32:50 -0400
Hi,
To provide tag security when using PI, the AIM OPC Server provides you
this functionality. With the OPC server you may specify the usage of
aliasing. An alias is mapped to the real OPC Item (=3D DCS tag) within the
opc server.
Next you may set the option "only connect to aliases", which allows the
OSI PI OPC client only to connect to the pre-defined aliases (no other
parameter can be read or written).
Then, for each alias you can specify the 'read-only' option.
So, for any external application that are connected through the AIM OPC
server, you can specify which tags are allowed, and which ones can be
writable.
Further more about Aim OPC Server, is that I just recently validated it
for a customer using MESH. Running it on a W2K3 system, it could handle
6000 updates per second. It was too much to handle for PI. But when PI
was polling each minute, it was able to handle it.
However, a disadvantage of OPC is the DCOM configuration, which is a
certain pain. Of course tunnellers are available, or e.g. install AIM
OPC Server on system where PI OPC Client is running also resolves the
problem.
And yes it is absolutely true that OPC has much more complexity then
FXBAIS. =
Though, using the AIM OPC server, it is a standard interface for all
kinds of external applications. In the past there were some issues with
Aim OPC. With the latest AIM V.3.3 (April 2008) Aim OPC server became
very reliable. =
Hope this helps the conversation.
Otto Kubbenga
Invensys Systems N.V.
T: +31 (0)35 54 84 146 F: +31 (0)35 54 84 185 M: +31 (0)6 30 45 02 07
=
=
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Theobald, Martin
Sent: Wednesday, June 25, 2008 6:57 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface
For systems that allow OSI PI (or even OPC DA/HDA Clients) to write back
to the I/A Series, what options are there for limiting which
Compound:Block.Parameters that can be written to?
Regards,
Martin Theobald
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: 24 June 2008 19:05
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface
Re: Read-only and FoxAPI (and AIM*API for that matter)
It is possible to configure read-only access using FoxAPI. This
configuration is done in the /opt/fox/ais/bin/an_init.tcp file on the
machine running the netFoxAPI Server (an_server).
If this is set, it does not matter what PI is configured to do, the data
will not be written.
For AIM*API, the file is /opt/aim/bin/an_init.tcp.
Regards,
=3D3D
Alex Johnson
Invensys Process Systems
10900 Equity Drive
Houston, TX 77041
713 329 8472 (voice)
713 329 1600 (switchboard)
713 329 1944 (fax)
alex.johnson@xxxxxxxxxxxxxxxx
http://ips.invensys.com =3D3D
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Toecker, Michael
Sent: Tuesday, June 24, 2008 12:58 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface
Dear Aymen Lazaar,
Don't forget to secure this connection as well, as security is also a
contributing factor to reliability, efficiency, performance, and
availability. =3D3D3D20
Ensure that there is a clear demarcation between your process network
(both the nodebus/mesh and the other interfaces on your Foxboro systems)
and your business network. Typically, this involves the installation,
configuration and maintenance of a firewall between the two networks.
Additionally, make sure you make use of the access control features in
FXBAIS and PI to restrict the ability of remote users to make changes to
data points. Most of the installations I've seen simply use a
"read-only" type of configuration for points coming out of the Foxboro
system into a process intelligence system, but that might vary depending
on your requirements.
Good luck!
Sincerely,
=3D3D3D20
Michael Toecker
Burns and McDonnell Engineering
Control System Security Group
mtoecker@xxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Aymen LAZAAR
Sent: Tuesday, June 24, 2008 8:30 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FXBAIS vs PI OPC Interface
Dear list,
We are evaluating the use of FXBAIS and PI OPC Interface as a software
solution to interface our DCS System (Foxboro I/A system - MESH and
Nodebus
Networks) to OSIsoft PI (based on Real Time data).
In order to choose the right option we may go for, we would like to
understand the advantages and limitations of each of the two options and
what are the considerations to look at before deciding on the best
solution in terms of reliability, efficiency, performance and
availability.
Please do not hesitate to share your feedback and thanks in advance.
Regards,
--=3D3D3D20
Aymen LAZAAR
=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: http://www.freelists.org/list/foxboro
to subscribe: =3D3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Djoin
to unsubscribe: =3D3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Dleave
=3D3D3D20
=3D3D
=3D3D
_______________________________________________________________________
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
=3D3D
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave
=3D3D
* Confidentiality Notice:
This e-mail and any associated files are intended solely for the
individual=3D3D or entity to whom they are addressed. Please do not copy
it or use it for =3D3D any purposes, or disclose its contents to any other
person. Further, this e=3D3D -mail and any associated files may be
confidential and further may be legal=3D3D ly privileged. This email is
from the Invensys Process Systems business uni=3D3D t of Invensys plc
which is a company registered in England and Wales with i=3D3D ts
registered office at Portland House, Bressenden Place, London, SW1E 5BF
=3D3D (Registered number 166023). For a list of European legal entities
within t=3D3D he Invensys Process Systems business group, please click
here http://www.in=3D3D
vensys.com/legal/default.asp?top_nav_id=3D3D3D77&nav_id=3D3D3D80&prev_id=3D=
3D3
D77=3D
.
If you have received this e-mail in error, you are on notice of its
status.=3D3D Please notify us immediately by reply e-mail and then delete
this message =3D3D from your system. Thank you for your co-operation. You
may contact our Help=3D3D desk on +44 (0)20 7821 3859 / 2105 or email
inet.hqhelpdesk@xxxxxxxxxxxxx T=3D3D his e-mail and any attachments
thereto may be subject to the terms of any a=3D3D greements between
Invensys (and/or its subsidiaries and affiliates) and the=3D3D recipient
(and/or its subsidiaries and affiliates).
=3D
=3D
_______________________________________________________________________
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
=3D
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D
* Confidentiality Notice:
This e-mail and any associated files are intended solely for the
individual=3D or entity to whom they are addressed. Please do not copy it
or use it for =3D any purposes, or disclose its contents to any other
person. Further, this e=3D -mail and any associated files may be
confidential and further may be legal=3D ly privileged. This email is from
the Invensys Process Systems business uni=3D t of Invensys plc which is a
company registered in England and Wales with i=3D ts registered office at
Portland House, Bressenden Place, London, SW1E 5BF =3D (Registered number
166023). For a list of European legal entities within t=3D he Invensys
Process Systems business group, please click here http://www.in=3D
vensys.com/legal/default.asp?top_nav_id=3D3D77&nav_id=3D3D80&prev_id=3D3D77=
.
If you have received this e-mail in error, you are on notice of its
status.=3D Please notify us immediately by reply e-mail and then delete
this message =3D from your system. Thank you for your co-operation. You
may contact our Help=3D desk on +44 (0)20 7821 3859 / 2105 or email
inet.hqhelpdesk@xxxxxxxxxxxxx T=3D his e-mail and any attachments thereto
may be subject to the terms of any a=3D greements between Invensys (and/or
its subsidiaries and affiliates) and the=3D recipient (and/or its
subsidiaries and affiliates).
=
=
_______________________________________________________________________
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=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual=
or entity to whom they are addressed. Please do not copy it or use it for =
any purposes, or disclose its contents to any other person. Further, this e=
-mail and any associated files may be confidential and further may be legal=
ly privileged. This email is from the Invensys Process Systems business uni=
t of Invensys plc which is a company registered in England and Wales with i=
ts registered office at Portland House, Bressenden Place, London, SW1E 5BF =
(Registered number 166023). For a list of European legal entities within t=
he Invensys Process Systems business group, please click here http://www.in=
vensys.com/legal/default.asp?top_nav_id=3D77&nav_id=3D80&prev_id=3D77.
If you have received this e-mail in error, you are on notice of its status.=
Please notify us immediately by reply e-mail and then delete this message =
from your system. Thank you for your co-operation. You may contact our Help=
desk on +44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx T=
his e-mail and any attachments thereto may be subject to the terms of any a=
greements between Invensys (and/or its subsidiaries and affiliates) and the=
recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
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
- References:
- [foxboro] FXBAIS vs PI OPC Interface
- From: Aymen LAZAAR
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Toecker, Michael
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Johnson, Alex P (IPS)
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Theobald, Martin
Other related posts:
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- » Re: [foxboro] FXBAIS vs PI OPC Interface
- [foxboro] FXBAIS vs PI OPC Interface
- From: Aymen LAZAAR
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Toecker, Michael
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Johnson, Alex P (IPS)
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Theobald, Martin