[foxboro] Need help

We intend to install a real-time database historian such as IP21/PI  and 
potentially, an MVC and an intelligent tuning application on a FOX I/A with an 
already installed AIM license.
 
Here are the Options we are considering, and please tell us whether it is 
feasible:
 
1.  Use an AW70  with the OPC I/O Gate.
Such box will read data from the FOX I/O blocks and transfers it to the 
Historian( PI or IP21), which means the historian should have an OPC server as 
well.
If this is doable (transferring data from the FOX I/A to the historian using 
AW70),  we will then interface the future MVC (most likely DMC) to the OPC 
sever of the historian where the AW70 OPC client will read the setpoints from 
and transfers them to the FOX I/O blocks.
 
Considering an AIM license already exists, what are the consideration we need 
to take concerning the CP loads by adding the AW70  which will serve as the 
gateway for the future Historian?  
What do you think about this approach?  Is it feasible?
 
Based on your experience how long would it take to install the AW70, the relate 
software and the required configuration?
 
2.  Install the OPC server for AIM on top of the AIM server.
 
We presume a simple PC is suitable.  Or is there a standard Foxboro hardware we 
need to recommend? If yes why?
We presume the OPC server of AIM comes with an AIMnet  API that connects to the 
AIM-API over TCP-IP.
 
In he future, if we decide to go for the MVC we will write points to the OPC 
server of AIM.  
 
Such configuration will not create any overload on the DCS network CP load as 
we will be using AIM as a shield or buffer zone.  Is it correct?
 
However, the issue comes from the fact, what if AIM fails?  Then we will stop 
any communications to all applications. 
 
We have a single point of failure.
 
 
3.  Install the OPC server of Matrikon.
 
This could be attractive.  However we would need to understand of the DCS load.
At the same time, our experience with Matrikon and many customers confirm the 
same, their support is very poor and products are buggy.  In addition, it takes 
them too long to fix anything and get back to customers.
 
The idea of buying a solution from Foxboro is more attractive to us.  Foxboro 
has a good reputation.
 
4.  Install the Native FOX I/A bridge of the Historian such as PI.
 
This could be an attractive solution as if the network fails, both Historian we 
will buffer the data.  Do you have any comments on this?
 
Later on, what will happen if we add an MVC?
 
Also, if we had applications to fine loop controllers for example, we will just 
add an OPC server to the historian.
 
What do you think?
 
Best Regards,
Mark David
Joint Gas
Costa Rica

                
---------------------------------
Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !
Créez votre Yahoo! Mail

Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !

 
 
_______________________________________________________________________
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: