Industrial IoT and Business Operations · Study deck

OPC UA: Companion Models and Implementation

A secure OPC UA connection can exchange data, but two machines still need shared meanings for assets, states, and measurements.

Ada is your guide for this deck.

iiot

Ada, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Explain: Year 2-3: Lower annual maintenance can drive positive ROI if the model, gateway, and certificate lifecycle are actually easier to operate than the custom alternative.
Explain: Real-world factors not modeled: outage windows, validation effort, vendor support, license terms, cybersecurity review, and the cost of maintaining namespace and certificate ownership over time.
Explain: The site-specific extension is where local meaning enters, and it is the step that quietly breaks integration when nobody writes it down.
Explain: SCADA systems consume that model as clients, while operations platforms receive wider event streams through MQTT publish-subscribe.

Major section

Companion Specifications

The base node model is generic.

The companion layer adds the domain types a machine shares with its peers.
The site-specific extension is where local meaning enters, and it is the step that quietly breaks integration when nobody writes it down.
The last two boxes are the fix.
Conformance evidence records the model version and the tests that passed.

Companion specifications reduce custom semantics only when teams record model versions, tests, local extensions, and the client contract that downstream systems rely on.

Major section

Implementation Considerations

Full feature support.

Publishing interval: How often server checks for changes (100 ms-5s typical).
Sampling interval: How often server reads underlying value (can be faster than publishing).
Queue size: How many changes to buffer between publications.
Lifetime count: How many publishing intervals before subscription expires.

Major section

OPC-UA in Practice

Native industrial protocols carry the fastest local signals into edge gateways, which can expose aggregated data as OPC UA servers.

SCADA systems consume that model as clients, while operations platforms receive wider event streams through MQTT publish-subscribe.
Enterprise applications reach analytics through REST APIs rather than entering the control loop.
PLC runs embedded OPC-UA server.

OPC-UA often sits between real-time OT systems and operations or enterprise consumers, so each ISA-95 level needs an explicit interaction pattern and boundary rule.

Major section

OPC-UA in Practice (continued)

The pattern changes with the job at each boundary.

OPC UA supplies structured plant meaning across OT layers, but it does not make cloud or enterprise software the owner of deterministic control.
Edge gateway subscribes to PLC data.
Gateway publishes to MQTT broker.
Cloud platform consumes MQTT messages.

Major section

Understanding the ROI

Year 2-3: Lower annual maintenance can drive positive ROI if the model, gateway, and certificate lifecycle are actually easier to operate than the custom alternative.

Real-world factors not modeled: outage windows, validation effort, vendor support, license terms, cybersecurity review, and the cost of maintaining namespace and certificate ownership over time.
Scenario: A beverage company operates a bottling line with native PROFINET PLCs, EtherCAT motion equipment, inspection cameras, and legacy Modbus RTU conveyor controllers.
Year 4-5: Savings may accelerate when standardized onboarding reduces the effort needed to add new equipment.

Major section

Summary

OPC-UA has emerged as the definitive standard for industrial interoperability.

Built-in Security: Unlike legacy protocols (Modbus, PROFIBUS) that have no native security, OPC-UA provides layered defense: application certificates, message signing and encryption, multiple user authentication methods, and audit logging that supports controlled operations.
Dual Communication Patterns: Client-server mode supports SCADA and HMI use cases that need direct request-response interaction.
PubSub supports decoupled messaging through standardized transport mappings such as UDP, Ethernet, and MQTT for use cases including analytics and monitoring.

Deck summary

Key takeaways

The base node model is generic.

Full feature support.
Native industrial protocols carry the fastest local signals into edge gateways, which can expose aggregated data as OPC UA servers.
The pattern changes with the job at each boundary.
Year 2-3: Lower annual maintenance can drive positive ROI if the model, gateway, and certificate lifecycle are actually easier to operate than the custom alternative.

Retrieval practice

Recall check 1 of 4

Ada says: answer from memory, then check your reasoning.

Q1A packaging line needs shared machine states and production counters across vendors. Which companion model should the team examine first?

AEUROMAP for plastics machinery interfaces and states.

BPackML for packaging machine states and counts.

CMTConnect for machine tool status and production counts.

DRaw vendor tags without a shared companion model.

Show answer

Answer: B PackML defines packaging state and counter meaning for this domain.

Retrieval practice

Recall check 2 of 4

Ada says: answer from memory, then check your reasoning.

Q2An OPC UA historian misses notifications during short production bursts. A trace shows the server produces the changes, but the subscriber queue overflows before the historian processes them. It subscribes to 2,000 variables across 20 PLCs at a 100 ms publishing interval. What is the best first tuning step?

AReplace all PLCs with faster controllers before checking subscription settings.

BSwitch to raw Modbus TCP and lose subscriptions, security, and semantic context.

CIncrease subscription queues and add dead-band filtering for noisy variables.

DReduce the publishing interval to 10ms and increase peak traffic further.

Show answer

Answer: C A larger queue can absorb bounded bursts, and dead-band filtering can reduce unnecessary change notifications.

Retrieval practice

Recall check 3 of 4

Ada says: answer from memory, then check your reasoning.

Q3A manufacturing company has 15-year-old Modbus RTU sensors, newer PROFINET PLCs, and wants to connect everything to a cloud analytics platform. Which OPC-UA integration pattern should they use?

AReplace all legacy equipment with native OPC-UA devices before adding analytics.

BBridge Modbus directly into MQTT and keep PROFINET separate from the analytics model.

CInstall full OPC-UA servers on each legacy serial sensor instead of using gateways.

DUse gateways to expose Modbus and PROFINET in one OPC-UA namespace, then publish cloud streams over MQTT.

Show answer

Answer: D This is exactly the Legacy Integration pattern (Pattern 3) combined with PLC to Cloud (Pattern 1).

Retrieval practice

Recall check 4 of 4

Ada says: answer from memory, then check your reasoning.

Q4What exposes OPC UA node relationships within a server information model?

ADiscover endpoints

BSecure channel

CSession activate

DBrowse model

Show answer

Answer: D Browsing exposes the server information model and node relationships.

Q5Complete the OPC-UA route gate so bad-quality values and unapproved writes do not cross the integration boundary:

Aself.writable_nodes = set(writable_nodes)

Bself.writable_nodes = []

Cself.writable_nodes = None

Dself.writable_nodes = writable_nodes.pop()

Show answer

Answer: A The gate preserves OPC-UA evidence rules: poor-quality samples are held, writes require an approved node list, and cloud consumers receive read-only events instead of direct control access.

Print reference

Answers 1 of 2

Answer key.

B · PackML defines packaging state and counter meaning for this domain.
C · A larger queue can absorb bounded bursts, and dead-band filtering can reduce unnecessary change notifications.
D · This is exactly the Legacy Integration pattern (Pattern 3) combined with PLC to Cloud (Pattern 1).
D · Browsing exposes the server information model and node relationships.

Print reference

Answers 2 of 2

Answer key.

A · The gate preserves OPC-UA evidence rules: poor-quality samples are held, writes require an approved node list, and cloud consumers receive read-only events instead of direct control access.