In the process industry and in energy production the backbone of the automation is often a distributed control system (DCS) such as Valmet DNA or ABB 800xA. The system has history and reporting tools of its own, yet the data is often wanted elsewhere as well: in reports, energy monitoring and analysis. OPC UA is the standard route for that.
OPC UA in a distributed control system
Both Valmet and ABB offer OPC UA connectivity for their current systems. Its availability, features and licensing, however, depend on the system version and the options purchased, and they differ from plant to plant. The first step is therefore always a question to the system supplier, not an assumption.
This article does not describe either manufacturer's products in detail and is no substitute for their documentation. Compatibility comes through the OPC UA standard, not through a certified integration.
What to ask the system supplier
- Does our system have an OPC UA server, which version, and is it licensed and running?
- Which measurements are visible in the server's address space, and how are they named?
- Does the server offer alarms and events through Alarms & Conditions?
- Does it offer history through history reads (Historical Access), and over how long a period?
- Which security policies does the server support, and how is a client's certificate approved?
- Which network is the server in, and what is the recommended way to bring the connection there through the firewall?
Network and accounts: read, do not open a door
The control system network is isolated for a reason. Build the OPC UA connection so that it can only be used for reading:
- One direction: the firewall opens a connection from the reading server to the OPC UA server's port, not the other way round.
- A dedicated account: its own user account for the reading system, with read rights only to the nodes it needs.
- Encryption: an encrypted connection and a strong security policy such as Basic256Sha256 in production.
- A separate server: the reading system on a server of its own, not on the control system's machines.
At many plants the OPC UA server sits in a zone between the control system network and the office network. That is a decision for the plant and the supplier together.
The first connection
The connection can first be tested with a general OPC UA test tool such as UaExpert: does the session open, are the measurements visible and do the values come through? Once that works, the reading system is connected with the same details.
DataPortia™ alongside the DCS
DataPortia joins the system's OPC UA server as a client only. It writes nothing to the control system, acknowledges no alarms and changes no setpoints.
- Measurements: measurement points are picked from the server's node tree and stored in a time-series database on the plant's own server.
- Alarms: if the server offers Alarms & Conditions events, they are stored with the timestamp the server gave.
- History: if the server offers history reads, past periods can be imported over the same connection, and only the missing periods are read.
- Backup server: if the system has a redundant OPC UA server, the connection can be given a backup server.
- Reports: scheduled PDF, CSV and Excel reports, trends, dashboards and alarm analyses from the same data.
The OPC UA roles are explained in OPC UA client vs. server, and the difference between a historian and reporting in Process historian or reporting system? Industry examples are on the process industry and power generation pages.
Try DataPortia for 30 days against your own control system's OPC UA server: the trial includes every feature except the HA add-on and commits you to nothing.