Glossary · OPC Unified Architecture

OPC UA

OPC UA is an industrial communication standard that carries names, units and structure along with the values, addressing the limits of protocols that transmit numbers alone.

How it connects

  1. Equipment server

    Expose equipment data

  2. Information model

    Values, meaning and structure

  3. Client

    Read through a standard interface

Definition

Definition

OPC UA is an industrial communication standard that carries names, units and structure along with the values, addressing the limits of protocols that transmit numbers alone.

In more detail

Protocols like Modbus transmit values only; what a value means had to be looked up in documentation. OPC UA carries meaning with the data — name, unit, data type and position within the equipment model.

Security is part of the specification. Authentication, encryption and access control are standard features rather than bolt-on infrastructure.

The trade-off is weight. Older equipment often does not support it, and where it does, an optional module may be required. Real plants therefore run a mixture of OPC UA, Modbus and dry contacts, which is exactly why a layer that absorbs the difference is needed.

How it is used on the floor

  • Take structured data directly from relatively recent equipment.
  • Use the information model to reduce tag mapping work.
  • Meet security requirements between control and upper networks with standard features.

OPC UA versus classic OPC (OPC DA)

Classic OPC depended on Windows COM/DCOM, making firewall traversal and portability difficult. OPC UA was redesigned to run independently of the operating system. The name carries over; the architecture does not.

Related terms

Terms that make more sense read together.

Related products

What IYULAB provides in this area.

Quick Answers

OPC UA — frequently asked

Questions that come up when evaluating OPC UA.

How do we know whether our equipment supports OPC UA?

Check the specification sheet or ask the vendor. Even where supported, a separate licence or module is sometimes required.

Is data collection difficult without OPC UA?

No. Modbus or dry contacts work too. OPC UA reduces mapping effort; it is not a prerequisite.

Should we standardise the whole plant on OPC UA?

Rarely practical and rarely necessary. If the collection layer absorbs protocol differences, upstream systems never need to know.

How would this apply to your plant?

A look at your equipment and current workflow is usually enough to scope it.

Talk to an engineer
KR KO