System 800xA + IEC61850 (CET OPC Server) integrated with PI PIMS
System Version 800xA 5.0.2;
IEC61850 (ABB Relays: REx615 and REx630);
CET OPC Server;
I have five CET OPC Servers with redundancy in my plant, as you should know, 800xA gets all infos from those OPCs.
Can I send data to PI PIMS direct from 800xA or I have to make an OPC - OPC communication (i.e.: CET OPC Server is read by OPC Surrogate or KepServer)
If I have to communicate between OPC Servers, how can I centralize all OPC Servers in one server and then this server communicate with PI PIMS?
It is very hard to handle with many CETs communicating direct with PI PIMS.
Voted best answer
All communication from 800xA to third party client has to be done via OPCSurrogate.
You can, but you should not, access ABB internal OPC Servers like AC800M OPC server or IEC61850 OPC severs from a third party client.
OPCSurrogate accesses all internal OPC servers and makes data available to outside clients, therefore you dont need to access five IEC61850 OPC servers from PI.
Using PI with an OPC connection (a PI-OPC Interface) doubles the number of OPC subscriptions to your controllers. This is a bad thing.
Instead, I recommend that you use a PI-HDA interface which connects to the Basic History Service running in your connectivity servers. Any and every tag that has a trend collection in 800xA can then be passed to PI without requiring an OPC connection.
The list of PI tags can then easily be created by using BDM to get a list of all history logs in the system.
The PI-HDA interface can also back fill history if there is a problem and the interface fails for any reason.
The cost for a PI-HDA interface is the same as for a PI-OPC interface. You should easily be able to exchange licenses with OSI. Also, because the server can recover history in the event of failure, a redundant interface is not really required.