Re: [foxboro] FXBAIS vs PI OPC Interface

We are successfully using fxbais on Version 8.3 MESH P91s as well as
Nodebus Version 6.12 AW51Es. We use the command line startup for fxbais,
rather than the PI preferred Interface GUI, as the new Windows Server
2003 PI Interface GUI requires a Foxboro quick-fix applied to FoxAPI to
allow the PI Interface GUI to start as a service, which can break other
applications using Foxapi on this P91.

Use of the foxapi fxbais approach is no better than OPC at preventing
the PI Server being able to access any and all MESH tags with any
configured delta. All changes to PI access are made on the PI Server
without any apparent indication on the Foxboro. This can be particularly
important on a loaded system. Although I have no OPC experience, I
suspect either OPC or fxbais would load your control system exactly the
same. I have heard negative things about using OPC, but have not been
personally involved and as such cannot judge.

We use Foxboro's Isolation Station product which only allows PI access
to tags configured on the Isolation Station. This eliminates the ability
of someone on the PI Server configuring too many or the wrong tags
automatically tied back into your control system. The Isolation Station
is also read only from the MESH, which prevents a PI write tag from
operating your control system.

Jack Easley



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of dave.g.williams@xxxxxxxxx
Sent: Tuesday, June 24, 2008 8:54 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface

We are using both types on different systems.  Our strategy is to move =3D
all our systems to the OPC connection.  Our advise from OSI was that he
=3D
FXBAIS connection was regarded as legacy and would eventually be =3D
withdrawn. =3D20

Other than some issues, which are detailed in a helpful hint, we have =3D
had no significant problems with the FXBAIS solution.

The issues with OPC connection are potentially many and various.  Mainly
=3D
the fact that OPC is client driven and therefore potentially can have =3D
unlimited data calls with uncontrollable deltas.  You design must do =3D
something to regulate this state of affairs.  Both Matrikon and Invensys
=3D
offer suitable servers, ensure the latest QF are installed if you use =3D
AIM*OPC.  One of the main differences is the way access and data delta =3D
control is implemented.  Although there are other differences that may =3D
influence you choice depending on the data you wish to collect.

If you go down the OPC route you can download a 30 day trial of the =3D
Matrikon server.  I'm sure your Invensys account manager can arrange =3D
something similar for AIM*OPC. =3D20



Dave Williams
Snr Power and Control Engineer
Tel: +44(0)151350 4480 Fax: 4566=3D20
Mobile Tel: +44 (0)7799 657836
mailto:dave.g.williams@xxxxxxxxx
__________________________________________________
> Shell UK Oil Products Limited
> Registered in England
> Registered number: 3625633
> Registered office: Shell Centre, London SE1 7NA
> Internet: http://www.shell.com/uk


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Aymen LAZAAR
Sent: 24 June 2008 14:30
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  =3D
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 =3D
solution
in terms of reliability, efficiency, performance and availability.

Please do not hesitate to share your feedback and thanks in advance.

Regards,
--=3D20
Aymen LAZAAR


=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:             http://www.freelists.org/list/foxboro
to subscribe:         =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe:      =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=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
 
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 email message, including any attachments, =0A=
contains or may contain confidential information intended only for the =0A=
addressee. If you are not an intended recipient of this message, be =0A=
advised that any reading, dissemination, forwarding, printing, copying=0A=
or other use of this message or its attachments is strictly prohibited. If=
=0A=
you have received this message in error, please notify the sender =0A=
immediately by reply message and delete this email message and any=0A=
attachments from your system. 
 
 
_______________________________________________________________________
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: