Re: [foxboro] FXBAIS vs PI OPC Interface
- From: "tjvandew@xxxxxxxxx" <tjvandew@xxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 25 Jun 2008 07:01:54 -1000
Mike or Marty,
Is TrendView actually retrieving data from the OSI PI data store or
does it use Aim* historian data for the trends? If it is using the OSI
PI data store then it has to be retrieving it across the MESH or through
a 2nd Ethernet network. If that is what you are doing then additional
security considerations must have already been addressed to allow every
Fox IA workstation on the MESH to access the PI data store. If that is
enabled then it seems one could just load OSI PI's Process Book
application on the Foxboro Workstation and get the trending capability
from there. Also, is the TrendView application approved for loading on
the Foxboro workstation on the MESH? Is OSI PI Process Book approved by
Foxboro for loading on a P91 or P92 Windows Workstation?
I am really hoping that TrendView is actually pulling historical
data from AIM* that resides on the MESH and that Foxboro has adopted
this application as a viable Trending package. What about it Alex? The
default trending windows that Foxboro provides from within the DM and
Foxview windows is really pretty pitiful by today's standards. There
has been little noticeable improvement since the inception of Fox IA in
the late 80's. Four trend lines per trend is pretty restrictive also.
I am confident that Infusion View's Trending package is much better even
though I haven't seen it. It has to be. I am interested in additional
information about Trend View.
Cheers,
Tom VandeWater
Control Conversions Inc.
Kapolei, Hawaii
Wilson, Mike J. wrote:
> Hi Aymen,
>
> Since you have OSI PI and windows Foxboro IA, I thought I would mention
> a product we recently installed called Trendview built by DCS
> Applications. =
>
>
> Basically the product is windows program that uses OSI PI ActiveX
> interface. The trending window works just like Processbook, can have up
> to 16 trend windows with as many pens in each as Processbook allows, the
> ability for operators to save there own trends, and many other nice
> features. The big advantage to using it is the ability to load trends
> from Foxboro allowing it to be used as the operator trend package.
> Basically we added right click menus to the Foxboro objects, allowing
> the operator to select a motor, transmitter, etc on the Foxview and load
> the correct C:B.P into the Trendview window. It makes it real easy to
> build trends quickly for troubleshooting.
>
> We recently installed it at a major paper mill which uses a lot of OSI
> PI.
> They usually keep a PC next to the Fox IA operator stations for calling
> up Processbook. Now they don't need the PC, and the operators can have
> the trend directly on the Foxview operator stations. We also set up a
> larger monitor connected to the WP's, and keep the Trenview app on that
> monitor.
>
> If you would like more information, you can send them at
> marty@xxxxxxxxxxxxxxxxxxxx
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Aymen LAZAAR
> Sent: Tuesday, June 24, 2008 9: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,
> -- =
>
> Aymen LAZAAR
>
>
> =
>
> =
>
> _______________________________________________________________________
> 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
>
>
>
_______________________________________________________________________
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
- Follow-Ups:
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Johnson, Alex P (IPS)
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Wilson, Mike J.
- References:
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Wilson, Mike J.
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
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Johnson, Alex P (IPS)
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Wilson, Mike J.
- Re: [foxboro] FXBAIS vs PI OPC Interface
- From: Wilson, Mike J.