OPC-UA — Industrial Data Communication Standard

OPC-UA (OPC Unified Architecture) is the modern, platform-independent, secure data communication standard for industrial automation. It replaces the legacy OPC Classic (DCOM-based) with a vendor-neutral, cross-platform protocol that supports both client-server and publish-subscribe communication, with built-in security (authentication, encryption) and a rich information model.

Why companies use it

·Enables integration between PLCs, SCADA, MES, ERP, and cloud platforms from different vendors without proprietary drivers
·Platform-independent — OPC-UA runs on Windows, Linux, and embedded systems, unlike legacy OPC Classic which required Windows DCOM
·Built-in security (X.509 certificates, AES encryption) makes OPC-UA suitable for networks that require ICS cybersecurity compliance
·The OPC-UA information model enables semantic data sharing — instead of just tag values, it transmits structured data with context

What hiring managers look for

·OPC-UA is the backbone of Industry 4.0 and smart factory data infrastructure — automation engineers must understand it
·Experience implementing OPC-UA servers on PLCs or edge devices and OPC-UA clients in SCADA or MES is directly practical
·Understanding OPC-UA security modes (None, Sign, Sign & Encrypt) and certificate management is required for ICS security roles
·Knowledge of OPC-UA over TSN (Time Sensitive Networking) for deterministic real-time communication shows leading-edge awareness

Typical interview questions

What are the main differences between OPC Classic (DA, HDA, A&E) and OPC-UA?

How does OPC-UA implement security and what are the three security modes?

What is an OPC-UA Information Model and why is it useful for smart manufacturing?

How would you connect a Siemens S7 PLC, an SAP MES system, and a cloud analytics platform using OPC-UA?

What is OPC-UA PubSub and how does it differ from the client-server model?

Common mistakes

·Using OPC-UA in "None" security mode on a production network — this transmits all data in plaintext and provides no authentication
·Confusing OPC-UA with MQTT — both carry industrial data but MQTT is a lightweight publish-subscribe protocol without OPC-UA's information model or security model
·Not managing OPC-UA certificate expiry — expired certificates cause silent communication failures that are hard to diagnose
·Over-designing the OPC-UA address space — an overly complex information model makes client integration difficult; start with a flat structure and add hierarchy when needed
·Assuming OPC-UA is real-time — standard OPC-UA has latency of tens of milliseconds; for deterministic real-time control, OPC-UA TSN or a dedicated fieldbus is needed

Real engineering example

A precision machining factory wanted to implement overall equipment effectiveness (OEE) dashboards for their 22 CNC machines from three different vendors. Each machine had a different proprietary communication protocol. Deploying OPC-UA server adapters on each machine type (Siemens Sinumerik, Fanuc FOCAS, Heidenhain) standardised the data interface. A single OPC-UA client in the SCADA historian then aggregated all 22 machines into one data model. OEE dashboards were delivered in 6 weeks rather than the 6-month estimate for proprietary integration.

Topics covered

OPC-UAindustrial communicationSCADAIndustry 4.0smart factoryICSautomation

Related interview guides

Mechatronics Engineer →Manufacturing Engineer →Software Engineer →Embedded Software Engineer →

More in Automation

PLC Programming — Industrial Control Logic5 min SCADA — Supervisory Control and Data Acquisition5 min HMI — Human-Machine Interface Design4 min Industrial Robots — Kinematics and Programming6 min Motion Control — Servo Drives and Control Theory6 min

Preparing for an interview?

Browse our role-specific interview guides written by engineers who know what hiring managers at ASML, NXP, and Philips look for.

Browse Interview Guides →