Plant management system Connect to 800xa 5.1 FP4
Can you please suggest a solution for connection of DCS system to thirparty Plant management system through OPC Server.
1. secuity of the system
2. Loading of the 800xa server
Can you please suggest a solution used is other sites, or if you have something. 27000 Tags need to be transffered to the thirparty systems ( Infy90+PLC Connect +AC800M )
800xa Application server + Matricon OPC Funnel server + Firewall ( is this option ) ?
Do we have any other better solution which will not efffet the running 800xa DCS.
A "Plant Management System" can mean many things. What sort of data do you want to collect ?
One thing to be very aware of is that collecting 27000 tags through OPC is a LOT. And yes, if you get this wrong it could seriously affect the operation of the system.
Do you need "real time" information - ie current values, or "near real-time values" ie as long as the data is within the last minute or so then everything is fine ?
In 99% of cases near real-time is perfectly OK and in this case I would strongly recommend an OPC HISTORY ( OPC-HDA ) interface that collects data from the Basic History services on your connectivity server. We have done this on several sites to Third Party systems like historians and Plant Performance Assesment systems ( specifically OSI-PI and Expertune Plant Triage ) and it works very well.
An OPC-HDA interface collects data that is already being collected by the history services, so it adds no additional load to the controllers. It is also much easier to configure the third pary interface by using Bulk Data Manager to get a list of Logged History points. However, it is important to ensure your Basic History server can handle the expected Disk IO load.
I typically dont like using additional third party OPC Clients like Matrikon between ABB systems and another Vendor. This makes troubleshooting much more difficult. But of course sometimes you have no choice. I would suggest you look for other viable options to compare to the Matrikon solution before making a final choice. Systems like OSI-PI do not require this anyway as they have their own solutions for passing data through firewalls etc.
The rule simply becomes - if you have a Trend on 800xA, then you configure a point in PI to collect that data.
Because the OPC History service is redundant, your OSI PI interface can be shut down and restarted and it will recover ALL of the missing data from the 800xA history. This means you do not need a redundant interface from PI.
Note that OSI will probably try to sell you the OPC-DA interface. You need to specifically ask for the OPC-HDA interface. They should be the same price.
Otherwise, if you are using PLC connect and want to avoid connecting to 800xA completely, you would use the OPC-DA server. I cannot give you any advice (good or bad) about this without knowing more details of your PLC's
DCS system installed in upgraded to 800xa 5.1 FP4 , and Plantmanagement system is sam as old. Exisitng connection in OPC-DA.
Controllers connected to 800xa system in AC800M, Infy 90 and PLC Connect signals from thirdparty systems. At the moment seperate PPB system is passing the information to plant management system (Only infy90 data's) , After upgrade of 800xa customer want to move all the other datas from AC800M and PLC connect to the same link.
As DCS system , if we are forced to use the OPC-DA due to the existing system configuration. What is the best way to reduce the imapct on the system performance.
Honestly, I would tell the customer he needs to buy a new OPC-HDA interface.
Otherwise, theres not much point asking how you can reduce the communications load of 27000 OPC Subscription points interfaced to a PI system. I'm assuming that you're already collecting most of this data for the 800xA historian. It seems pointless to collect it twice. You need to be especially carefull of collecting OPC data from older systems like the Infi 90
Like I said, the HDA interface is more reliable, is easier to configure, and does not require redundancy. Its all round a much better solution.