independent data handling in 800xa for third party opc connections
In our plant we have now have 2 opc connections (seen below) connected through 1 redundant server. On 1 redundant network, we call the industry network.
Now we want to add 1 more OPC connection from a third party. This connection is our fire alarming system which also can be connected through OPC. For this te be a valid and certified connection, the connection needs to be autonomous from other networks e.g. office networks, internet, etc.
Now industry-network is separated from all other networks. And the networking from and to the fire alarming system can be configured separate 1 on 1, which is good. But the industry network and fire-alarming system will come together on the same redundant server, but will be communicate through different OPC configurations:
The fire-alarm system will have completely customized objects and structure in 800xa. But in the end will be all be available on 800xa. How does 800xa keep the data for different third party OPC separate from one another and is ABB able guarantee that? Is this written down somewhere?
I wasn't able to find anything to cover this, hope you can help!
Now we want to add 1 more OPC connection from a third party. This connection is our fire alarming system which also can be connected through OPC. For this te be a valid and certified connection, the connection needs to be autonomous from other networks e.g. office networks, internet, etc.
Now industry-network is separated from all other networks. And the networking from and to the fire alarming system can be configured separate 1 on 1, which is good. But the industry network and fire-alarming system will come together on the same redundant server, but will be communicate through different OPC configurations:
- Harmony OPC Connect for DCS
- PLC-Connect OPC through kepWare for PLC's
- And adding to that, a fire-alarm OPC through Bosch OPC FPA5000 for the fire-alarm system.
The fire-alarm system will have completely customized objects and structure in 800xa. But in the end will be all be available on 800xa. How does 800xa keep the data for different third party OPC separate from one another and is ABB able guarantee that? Is this written down somewhere?
I wasn't able to find anything to cover this, hope you can help!
Asked 1 month ago
Voted best answer
1
Q: "How does 800xa keep the data for different third party OPC separate from one another?"
A: "Each 3rd Party OPC Network may have its own dedicated OPC DA Connector service provider, or two if redundant"
The person configuring the system may opt to host these connectors on a dedicated server or set of servers having a dedicated network connected. Due to this the data will be kept separated from other data until a client (e.g. a historian or PG2 graphic) connects and subscribe. Once a client connect, data will travel from the server to the client over the common client/server network.
A: "Each 3rd Party OPC Network may have its own dedicated OPC DA Connector service provider, or two if redundant"
The person configuring the system may opt to host these connectors on a dedicated server or set of servers having a dedicated network connected. Due to this the data will be kept separated from other data until a client (e.g. a historian or PG2 graphic) connects and subscribe. Once a client connect, data will travel from the server to the client over the common client/server network.
Add new comment