OPC UA (Open Platform Communications Unified Architecture) is a vendor-neutral industrial communication standard that lets PLCs (programmable logic controllers), machines and software from different manufacturers exchange data securely and with its meaning intact. Alongside a value such as "40", it carries the machine, sensor, unit and limits, which is why it has become the common language of SCADA, MES (manufacturing execution system) and ERP integration.
Key takeaways
- OPC UA is a vendor- and platform-independent industrial communication standard, released by the OPC Foundation in 2008.
- Data travels inside a browsable information model, together with its unit, limits and timestamp.
- Security is built into the standard: X.509 certificates, message signing and encryption, provided they are configured correctly.
- OPC UA, Modbus and MQTT are not rivals; most factories run all three in different layers.
- A rollout starts with a pilot on one line and one use case; the real work is designing the information model.
What problem does OPC UA solve on the factory floor?
On a typical shop floor, a fifteen-year-old injection moulding machine runs next to last year's CNC and PLCs from three different vendors. Each has its own protocol and addressing scheme. On one, the oil temperature lives in "holding register 40001"; on another, it is "DB10.DBW4", and only the technician who commissioned the machine knows which is which.
The symptoms are familiar. SCADA screens are remapped for every new machine, production counts are collected by hand, and the ERP figure never quite matches the line. Each new report means another driver or script, until the point-to-point links become a tangle nobody fully understands.
OPC UA replaces the tangle with one rule: every machine publishes its data through a standard server interface, and every application reads it through the same client interface. According to the OPC Foundation's OPC UA overview, the standard was released in 2008. As of 2026, many modern PLCs and machine controllers can act as an OPC UA server without extra hardware.
What does a missing common language between machines cost?
When machines share no common language, the first casualty is visibility. If the start, cause and duration of a stoppage are not recorded automatically, problems surface at the end of the shift or, worse, in a customer complaint.
Siemens' The True Cost of Downtime 2024 report found that large plants average 25 unplanned downtime incidents a month and lose 27 hours a month to them.
The same Siemens report found that nine out of ten respondents already do some form of condition monitoring. Collecting data is no longer a differentiator; what separates plants is how quickly and consistently that data reaches decision-making systems.
The second casualty is data quality. Writing in MIT Sloan Management Review in 2017, data quality expert Thomas C. Redman estimated the cost of bad data at 15% to 25% of revenue for most companies. Hand-keyed production counts, mixed-up units and timestamps from unsynchronised clocks are exactly what that looks like on a factory floor.
The third casualty is security. The Verizon 2026 Data Breach Investigations Report found ransomware in 48% of all breaches. Machines exposed to the office network over legacy protocols with no encryption or authentication carry that risk straight onto the production line, as we explain in OT security for SCADA. The full architecture that OPC UA sits in is explained layer by layer in what is IIoT.
How does OPC UA work? Four core concepts
Four concepts are enough to understand how OPC UA works:
- Servers and clients: An OPC UA server on the machine or PLC exposes data; SCADA, MES or a gateway connects as a client to read it and, where permitted, write to it. Endpoints typically start with
opc.tcp://. - Address space and information model: Data is not a flat list of addresses but a browsable tree of objects. A node such as "Line 2 > Press 3 > Hydraulics > Oil Temperature" carries its value, engineering unit, limits and timestamp together.
- Subscriptions: Instead of polling every second, a client says "tell me when this changes". Sampling intervals and deadbands keep network traffic under control.
- Security: Applications identify each other with X.509 certificates; messages can be signed, or signed and encrypted, and users authenticate with a username and password or a certificate.
Much of the real value of the OPC UA information model comes from companion specifications, industry templates built on top of OPC UA. EUROMAP 77 for injection moulding machines and the OPC UA for Machine Tools model popularised by the umati initiative are two examples. Two machines from different vendors that implement the same model expose the same data under the same names and structure, so integration stops being reinvented for every project.
OPC UA also defines a publish/subscribe (PubSub) model, so data can be pushed to many receivers at once over UDP or MQTT, a pattern common in edge computing for manufacturing.
What is the difference between OPC UA, OPC Classic, Modbus and MQTT?
The quickest way to place OPC UA is to set it beside the alternatives you are most likely to meet on site:
| Criterion | OPC UA | OPC Classic (DA) | Modbus TCP | MQTT |
|---|---|---|---|---|
| Data model | Rich, hierarchical, typed | Flat tag list | Numbered registers | Free-form topics and payloads |
| Platform | OS-independent | Tied to Windows and DCOM | Independent | Independent |
| Built-in security | Certificates, signing, encryption | Depends on DCOM settings | None in the classic protocol (a TLS extension exists but is rare on site) | TLS and auth via the broker |
| Units and meaning | Travel with the data | Limited | Not included; read from manuals | Left to the application |
| Typical use | Machine–SCADA–MES integration | Legacy OPC servers | Simple devices and meters | Lightweight site-to-cloud messaging |
This comparison is not about crowning a winner but putting each protocol in the right layer. Modbus RTU and TCP remain the practical way to read a simple energy meter, and MQTT for industrial IoT excels at moving data from many remote points to the cloud. OPC UA earns its place at the machine–software boundary, where meaning and security matter; most sites run all three, with a gateway translating.
For machines with no PLC, current sensors, counters and add-on I/O modules make data readable first; see our guide to retrofitting legacy machines.
How do you roll out OPC UA in a factory? A 7-step framework
An OPC UA project is really a redesign of your data model. This sequence keeps risk and rework down:
- Build an inventory. Record each machine's PLC make, model, firmware, current protocol and network connection in one table, and separate devices with an embedded OPC UA server from those that need a gateway.
- Pick one use case. Rather than "connect everything", choose a single question: understanding stoppage causes, calculating OEE or tracking energy use.
- Design the information model. Agree tag names, units, hierarchy and any relevant companion specification. Skip this and OPC UA becomes little more than a renamed register list.
- Set the security policy up front. Certificate management, sign-and-encrypt mode, user roles and OT network segmentation are settled before go-live. "We'll secure it later" tends to become permanent.
- Pilot on one line. Measure subscription rates, deadbands and network load on one or two machines, and validate the data on a SCADA screen and in a report.
- Connect storage and integration. Write values to a time-series database, link counts and orders to the MES, and pass summaries to the ERP.
- Write the operating rules. Document the certificate renewal schedule, the template for adding new machines and the change approval process.
Use these checks at each stage of an OPC UA rollout:
| Checkpoint | Question to ask |
|---|---|
| Inventory | Which machines have an embedded OPC UA server, and which need a gateway? |
| Information model | Do machines of the same type share the same tag structure? |
| Security | Is the "None" security mode disabled, and who owns certificate renewal? |
| Performance | Were sampling rates chosen for the use case, or on a "faster is better" basis? |
| Integration | Do the MES and ERP use the same name with the same meaning? |
How Digital Bridge delivers OPC UA integration
At Digital Bridge, we start every OPC UA project with discovery and requirements analysis. As part of our free on-site assessment for Industry 4.0 projects, we map the PLC landscape, existing protocols and network topology, and agree with the production team which data is needed for which decision. The outcome is a written proposal setting out scope, phases and cost.
In the pilot we connect one or two critical machines over OPC UA and bring the data into SCADA and HMI screens. We connect to Siemens, Allen-Bradley, Mitsubishi, Schneider and other brands over Modbus, OPC-UA, Profibus and Ethernet, so a mixed machine park is not a barrier to getting started. With the custom SCADA we build, the source code belongs to the customer and there are no additional licence fees; we weigh that option against off-the-shelf platforms in commercial vs custom SCADA.
Once the OPC UA pilot proves its value, we connect the data to production management. Our MES production management solution integrates with SAP, bespoke ERPs and Logo and Mikro (ERP packages widely used in Türkiye), so counts, stoppages and quality data from OPC UA are tied to work orders. The difference between the two layers is covered in MES vs ERP.
Linking the wider software estate is the job of our system integrations service. OPC UA standardises the language on the shop floor, but talking to office systems usually needs an API integration as well. For multi-site businesses, we feed the data into a remote monitoring platform so every site appears on one screen, and the same data can later drive predictive maintenance.
Where should an OPC UA project start?
Moving to OPC UA does not mean rebuilding the whole plant at once. One line where stoppages hurt most, one clear question and a well-designed information model is enough to produce the data that shapes your next steps. For wider prioritisation, see our Industry 4.0 roadmap for SMEs and the full set of Industry 4.0 articles.
To assess how ready your machines are for OPC UA, get in touch with our team. During the site assessment we build the inventory with you and propose a concrete scope for the first pilot.