What is OPC

What Is OPC? OPC Meaning, Specifications and Servers Explained

What is OPC? OPC (Open Platform Communications) is a vendor-neutral set of standards for exchanging industrial data. An OPC server reads data from devices such as programmable logic controllers (PLCs) in their own protocol. It then publishes that data as standard OPC tags that any OPC client can read, whatever the vendor.

Diagram of an OPC server reading PLCs, DCS, RTUs and meters and serving SCADA, HMI, historian and MES clients
Figure 1. An OPC server reads each device in its native protocol and publishes standard OPC tags that any client can use.

Before OPC, every pairing of a device and an application needed its own driver. With ten device types and five applications, that could mean dozens of drivers to build and maintain. OPC replaces them with one standard interface: each device gets one server, and every client speaks OPC.

What does OPC mean? OPC originally stood for “OLE for Process Control”, because the first specification, released in 1996, was built on Microsoft’s OLE and COM technology. In 2011 the OPC Foundation renamed it Open Platform Communications, since OPC no longer depends on Windows. Today the name covers two generations:

  • OPC Classic: the original Windows-based specifications. The main three are Data Access (DA), Historical Data Access (HDA) and Alarms & Events (A&E).
  • OPC UA (Unified Architecture): the platform-independent successor, with built-in security and a single information model. It is published as the international standard IEC 62541.

This guide explains how OPC fits into a plant’s architecture, what each specification does, how OPC Classic and OPC UA compare, how to migrate between them, and how to choose the right OPC server.

How OPC works in a plant

How OPC works: the client-server model

OPC uses a client-server model. The server connects to the control system and holds the data. Clients connect to the server to read values, write setpoints or subscribe to changes. One server can serve many clients at once, and one client can connect to many servers.

Where OPC sits in a plant’s architecture

Most plants organise their systems in levels, often described with the Purdue model. OPC servers usually sit at the supervisory level (Level 2). From there they connect down to the controllers and up to the applications that use the data.

Purdue model diagram showing OPC DA, HDA and A&E servers between plant controllers and business systems
Figure 2. OPC servers run at the supervisory level and feed SCADA, historians and business systems above them.

In a typical OPC Classic deployment:

  1. Level 1, control. PLCs, distributed control systems (DCS) and remote terminal units (RTUs) run the process. They speak their own protocols, such as Modbus.
  2. Level 2, supervisory. An OPC DA server reads live values from the controllers and feeds the SCADA (supervisory control and data acquisition) system and HMI (human-machine interface) screens. An OPC A&E server forwards alarms and events to the same operators.
  3. Level 3, operations. A historian collects values from the OPC DA server and stores them. An OPC HDA server gives other applications access to that history.
  4. Level 4, business. Manufacturing execution systems (MES), reporting tools and enterprise resource planning (ERP) systems use the data. They usually reach it through an industrial DMZ (demilitarised zone) that separates the plant (OT) network from the business (IT) network.

OPC Classic specifications and the DCOM problem

The OPC Classic specifications

OPC Classic splits industrial data into three types, with one specification for each:

Specification Data it carries Typical client
OPC DA (Data Access) Real-time values, each with a quality flag and timestamp SCADA, HMI, historian
OPC HDA (Historical Data Access) Stored time-series data and aggregates such as averages Reporting and analysis tools
OPC A&E (Alarms & Events) Alarm conditions, acknowledgements and event notifications Alarm management, operator consoles

Two more specifications, XML-DA and Data eXchange (DX), also exist but are rarely used today.

The DCOM problem

OPC Classic is built on Microsoft COM. When client and server run on different machines, they communicate through DCOM (Distributed Component Object Model). DCOM causes three recurring problems in plants:

  • Windows only. Both machines must run Windows.
  • Hard to secure. It depends on matching Windows accounts and security settings on both machines.
  • Firewall-unfriendly. It uses dynamically assigned ports, so firewalls either block it or are opened wider than security teams accept.
Diagram comparing DCOM blocked at a firewall with OPCNet Broker tunneling OPC Classic data across it
Figure 3. OPC tunneling removes DCOM from the network path, so OPC Classic data can cross firewalls securely.

OPC tunneling solves this without changing the OPC servers or clients. A broker runs next to each side and talks to the local OPC application over COM. Between the two machines, the data travels through a DCOM-free tunnel. OPCNet Broker DA HDA AE works this way for DA, HDA and A&E. For a deeper look, read What is DCOM?

Download OPCNet Broker® 

OPC UA and how it compares with OPC Classic

What OPC UA changes

The OPC Foundation designed OPC UA to remove OPC Classic’s dependence on Windows and DCOM. Three changes matter most in an architecture:

  • One server instead of three. Live values, history, alarms and methods share one information model, so a single OPC UA server can expose all of them.
  • Security built into the protocol. Certificates, encryption and user authentication are part of OPC UA itself, not borrowed from Windows settings.
  • Runs anywhere. OPC UA servers and clients run on Windows, Linux, embedded devices and cloud platforms, and connect over standard network transports.

For the full picture, read What is OPC UA? and our guide to OPC UA security.

OPC Classic vs OPC UA at a glance

OPC Classic OPC UA
Specifications Separate DA, HDA and A&E One unified architecture (IEC 62541)
Transport Microsoft COM and DCOM Binary TCP, HTTPS and publish-subscribe, including MQTT
Operating systems Windows only Windows, Linux, embedded and cloud
Security Depends on Windows DCOM settings Built in: certificates, encryption, user authentication
Data model Flat tags, one specification per data type Rich information model for data, history, alarms and methods
Firewalls Hard to route (dynamic ports) Firewall-friendly: one configurable endpoint
Best fit today Stable, isolated plant-floor systems New projects, cross-platform, Industrial Internet of Things (IIoT) and cloud integration

Migrating from OPC Classic to OPC UA

When should you move to OPC UA?

OPC Classic remains a sound choice for stable, isolated systems that already work. Moving to OPC UA makes sense when you need:

  • Linux, embedded or cloud deployments
  • Secure connections across networks or sites, without DCOM
  • Integration with IIoT and enterprise platforms

Migrate one side at a time

Most plants can’t replace every OPC server and client at once. A bridge lets each side move on its own schedule.

Diagram of OPC UA Wrapper and OPC UA Proxy bridging OPC Classic and OPC UA clients and servers
Figure 4. Bridge OPC Classic and OPC UA in either direction without replacing working servers or clients.
  • OPC UA Wrapper exposes an existing OPC Classic server as an OPC UA server. New OPC UA clients can then read it without the Classic server changing.
  • OPC UA Proxy works the other way. It lets existing OPC Classic clients read from OPC UA servers, so legacy applications keep working when new equipment arrives.

For a step-by-step plan, read our OPC Classic to OPC UA migration guide.

Download OPC UA Wrapper

Which OPC server do I need?

The right OPC server depends on where your data lives and which clients need it. Start from the problem you’re solving:

Decision tree matching OPC connectivity needs to Integration Objects OPC servers, bridges, toolkits and free tools
Figure 5. Start from the connectivity problem you need to solve to find the right OPC server or tool.

 

Product

What it does

OPC Server for Modbus Gives SCADA and HMI clients one OPC connection to all your Modbus devices
OPC Server for Databases Brings relational database data into OPC Classic control systems
OPC UA Server for Databases Exposes relational database data as live OPC UA tags
OPC Server for SNMP Brings network device monitoring into SCADA
OPC UA Wrapper / OPC UA Proxy Bridge OPC Classic and OPC UA in either direction (Figure 4)
OPCNet Broker DA HDA AE DCOM-free OPC tunneling between machines (Figure 3)
OPC Easy Archiver Keeps a complete historical record of your OPC data
OPC UA Universal Server Combines several industrial protocols into one secure OPC UA endpoint. Delivered as a configurable server within SIOTH® Data Flow
OPC UA Server Toolkit, OPC UA Client Toolkit, OPC .NET Client Toolkit For software developers building their own OPC servers or clients in .NET

Discover all our OPC Products

Testing first? Six of our OPC tools are free to download, with no time limit:

Beyond a single OPC server

When one OPC server is no longer enough

Each OPC product solves one connectivity problem. The architecture changes when a second problem arrives: another protocol, another site, a historian to federate, or plant data that IT and cloud teams need. Adding one more converter, tunnel and bridge each time leads to a web of point-to-point links that is hard to secure and maintain.

SIOTH® replaces that web with one integration layer. You configure Data Flows between any source and destination instead of installing separate point products.

Architecture diagram of SIOTH connecting OPC and OT sources to IT and cloud systems through one Unified Namespace
Figure 6. SIOTH® connects every OPC and OT source once and serves IT and cloud systems through one Unified Namespace.
  • Data Flow connects to OPC Classic, OPC UA and 100+ OT protocols, converts between them, and buffers data when links drop.
  • OPC UA Universal Server and MQTT Universal Broker are configurable servers within Data Flow. They publish every connected source through one secure OPC UA endpoint or one MQTT broker.
  • Data Model organises all of it into one Unified Namespace (UNS), with ISA-95 compatible asset models.
  • Security is built into the architecture: a protocol break between OT and IT, TLS encryption and role-based access control (RBAC). SIOTH is IEC 62443-aligned.

Download SIOTH®

Frequently asked questions

An OPC server is software that connects to industrial devices or systems in their native protocol and presents the data as standard OPC tags. Any OPC client can then read the data without a device-specific driver.

OPC DA is the original Windows-only, DCOM-based specification for real-time data. OPC UA is its platform-independent successor, with built-in security and one model for live data, history and alarms.

OPC HDA gives clients access to stored time-series data, such as trends and aggregates, for reporting and analysis.

Yes. Many plants still run OPC DA, HDA and A&E servers. They often bridge them to OPC UA with a wrapper, or tunnel them across networks, instead of replacing them.

Use OPC tunneling. A broker on each side talks to the local OPC application and carries the data between machines without DCOM, as shown in Figure 3.

Yes. Our OPC product line covers OPC Classic servers, OPC UA servers, wrappers and proxies between the two, tunneling, archiving, developer toolkits and free test tools.

Related Posts