Skip to content
Hakan KaracaENGINEERING JOURNAL
PLC & SCADAEki 8, 20263 min read

OPC UA Between PLC and MES: Information Model, Security and Failure Modes

OPC UA'nın çalışma mantığını, güvenliğini ve PLC ile MES arasında kullanımını anlatan teknik rehber.

OPC UA is more than a way to read a tag; its value depends on modelling meaning and operating the interface responsibly.

OPC Unified Architecture (OPC UA) is a platform-independent industrial communication framework that supports structured information exchange, discovery, security mechanisms and a model of the information being exposed. In a PLC-to-MES integration, that means the consumer can receive more context than a raw memory address—provided the server’s information model is designed and maintained with that context in mind.

Start with data meaning

Before configuring subscriptions, decide which process values and events the MES actually needs. A measurement should carry an agreed type and engineering unit; a state should have a defined enumeration; quality information should not be discarded; and timestamps must have a known interpretation. If downstream software must rely on a vendor-specific tag name and a separate spreadsheet to decode it, the integration is technically connected but semantically fragile.

Read, subscribe or call a method?

Periodic reads can be adequate for slowly changing values. Subscriptions reduce unnecessary polling and allow change notifications within configured sampling and publishing constraints. Methods may be appropriate for defined service operations, but remote writes and method calls need stronger governance than read-only telemetry. The client should know which nodes are read-only, which writes are permitted, what acknowledgement looks like and how authorization is enforced.

Security is part of the deployment

Review endpoint configuration, certificates, trust lists, user authentication, authorization, security policies and network reachability. Do not use an unauthenticated or unrestricted endpoint just because the system is on an internal network. Certificates expire, machines are replaced and trust stores drift; certificate lifecycle must therefore be part of operations, not a commissioning footnote.

Engineer the failure path

A robust consumer distinguishes an actual value from a stale or bad-quality value. It detects connection loss, retries with bounded backoff, re-establishes subscriptions, and marks data as unavailable until quality is restored. It should also handle server restarts, namespace changes, revised data types and the difference between a missed state update and a missed event.

For event-based business records, OPC UA subscriptions alone do not automatically provide end-to-end business exactly-once delivery. If an event must survive a client outage, investigate the server’s history/event capabilities and combine them with sequence identifiers, persistent buffering or a reconciliation process appropriate to the platform.

Commissioning checklist

  1. Confirm the information model, units and ownership of each node.
  2. Test supported security modes and certificate renewal/replacement.
  3. Interrupt the connection and observe client state, alarms and reconnection.
  4. Restart the server and verify subscriptions and namespace handling.
  5. Inject bad-quality or stale data and confirm the MES does not treat it as fresh.
  6. Test authorised writes separately from normal read-only collection.
  7. Document endpoint configuration, identity, firewall flow and recovery ownership.

Official reference: OPC Foundation’s OPC UA overview. Specific capabilities depend on product, version and profile, so verify the implementation documentation for the actual devices and software.

References and further reading

  1. OPC Foundation — OPC UA Overview
  2. NIST SP 800-82 Rev. 3 — Operational Technology Security