Re: [foxboro] FXBAIS vs PI OPC Interface

Alex,

This is the Fxbais model that is referred to in the other emails.  What
about the statements that OSIsoft is dropping support for this option?
We are using a p91 2003 server here does the windows version of PiAPI
run on the sever?  How does the security work between the windows
machine and the mill information network?  Our IT folks like OPC
communications, what can I do to convince them other wise?  Is there a
copy of Invensys and OSIsoft recommendation on letterhead from either or
both vendors?

Thanks for the help.

Jeff Miller
Smart Papers Holdings LLC
Hamilton Ohio

FYI:  The Fxbais version of the OSIsoft connection has worked well here
for years with little to no trouble.  Most of the issues are related to
network problems or 2nd ether net ports.


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Tuesday, June 24, 2008 11:26 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FXBAIS vs PI OPC Interface

Julie Zeilenga of OSIsoft and I recently put this following together to
describe our preferred approach to the integration of I/A Series systems
and OSIsoft's PI Historian.


****************************

The standard interface between an OSIsoft PI System and a Foxboro I/A
Series control system is the OSIsoft Foxboro I/A 51 and 70 Series
Interface to the PI System; PI Part Number PI-IN-FX-IA-NTI. The
interface comes standard with the PI API which is used for communication
to the PI Server and which also contains the program which buffers data
to the PI Interface node if there is a break in communication with the
PI Server. This software is sold and maintained by OSIsoft. Support for
the development of the interface is provided to OSIsoft by IPS on a
mutually agreeable basis. =3D


In general, one loads the OSIsoft Foxboro Interface and the PI API on an
I/A Series AW that connects to a network that leads to the PI Host
computer. The AW must have installed on it the latest FoxAPI software
from IPS since the interface uses the FoxAPI to connect to process data
within the I/A Series system.

From this AW, the OSIsoft Foxboro Interface may collect data from any
I/A Series data source. Generally, however, such data collection is
limited to a specific process unit. Many sites have multiple OSIsoft
Foxboro Interfaces, each one communicating to its own process unit.
There are a number of reasons for this approach, but the three most
important are:

1)       A copy of the OSIsoft Foxboro Interface per process unit allows
the plant to simplify its maintenance and upgrade planning since each
interface is responsible for data collection for that unit.

2)       A single AW can acquire data from approximately 64,000 tags.
This number is more than adequate for most units, but is too small for a
large plant.

3)       Since the OSIsoft Foxboro interface runs on the I/A Series AW
and collects data from that station only, no data are lost if there is a
break in communication between that I/A Series AW and other I/A AWs on
the process control network.

The installation of the PI API on the AW allows the user to benefit from
its 'store and forward' mechanism in the event of a network failure
between the OSIsoft Foxboro Interface and the PI Server. Data will
continue to be buffered to disk (2 Gig limit) until communication is
re-established with the PI Server. At that time, data will be sent to
the PI Server from the PI Interface node in first in/first out order.
Version 1.6.x of the PI API on Windows can also now be configured to
buffer data to multiple PI Servers. Buffering data to multiple PI
Servers is a central component of OSIsoft's High Availability (HA)
strategy. The OSIsoft Foxboro interface also supports failover; each
member of the failover pair will run on its own AW.

Alternative approaches are possible, but add more layers of software.

******************

I hope this helps.


Regards,
 =3D

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 =3D


-----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,
-- =3D

Aymen LAZAAR


 =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=3D3D=
77.

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).


=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:             http://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:             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: