OPC UA Information Modeling: A Complete Guide for Manufacturing Data Integration

How semantic data standards enable standardized machine-to-system communication in industrial environments

If you've spent any time working with industrial data, you're familiar with a common challenge. Data from machines arrives as measurements, but understanding what those measurements represent requires additional context. A tag labeled "TAG_001" might be a temperature reading, a pressure value, or something else entirely. The engineering units, location, and relationship to other data points are often documented separately, if at all.

This challenge affects integration projects, analytics initiatives, and system connections across manufacturing facilities. Engineers spend significant time manually mapping data points and creating custom integration code for each new machine or system addition.

Information modeling provides a solution to this problem, and it represents a fundamental shift in how industrial systems share data. Jouni Aro, CTO of Prosys OPC with over 20 years of experience in OPC technology development, explains that information modeling moves beyond simple data delivery to create true understanding between systems.

‍

‍

What is Information Modeling and How Does It Work

‍

Think about how industrial data has traditionally worked. Your sensors and PLCs generate measurements, and those measurements get tagged with names that made sense to whoever programmed the system five years ago. When you need to connect a new system or build an analytics application, someone has to figure out what all those tags mean, document them, and map them to the new system's expectations.

Information modeling flips this approach. Instead of delivering raw measurements that require outside knowledge to interpret, it packages data with its context built in. You don't just get a number—you get a temperature measurement, in Celsius, from the bearing on motor three of production line two, along with its engineering units, normal operating range, and relationship to other measurements.

This shift matters because it removes the interpretation burden from every downstream system. Your MES doesn't need a custom integration guide. Your analytics platform doesn't need a data dictionary maintained by hand. The data describes itself.

But information modeling goes further. It models entire machines, production lines, and processes in a standardized way. When a robot is modeled using a standard information model, every robot from every vendor presents the same structure—same data points, same commands, same status information. This standardization enables reusable integration approaches across equipment from different manufacturers.

‍

How OPC UA Information Modeling Enables Standardized Machine Integration

‍

Industry 4.0 has always talked about plug-and-produce—the idea that you could add new equipment to your factory and have it automatically integrate with your existing systems. The physical connection has never been the hard part. It's the information systems that create the bottleneck.

OPC UA information modeling addresses this challenge by standardizing interfaces at the semantic level, creating a common language for machines to describe themselves. A machine tool from Vendor A and one from Vendor B both use the same language, expose the same data structure, and can be integrated using the same approach.

The standardization happens through companion specifications—industry-specific information models developed by the OPC Foundation in collaboration with industry organizations. Companion specifications exist for robotics, machine tools, AutoID systems, and many other device categories.

These specifications define what information a device type should provide, independent of the manufacturer. For example, a robot must expose its joint positions, speed, program status, and error codes in a standardized way. Manufacturers can add proprietary data on top of this standardized core, but the base interface remains consistent across vendors.

This means your integration code becomes reusable. Your monitoring dashboards work across vendors. Your analytics models can be applied to similar equipment regardless of who made it. The manual mapping work that used to take weeks for each new device can be largely eliminated.

‍

Understanding OPC UA Companion Specifications and Their Role

‍

Manufacturing equipment varies significantly between vendors and applications, which creates challenges for standardization. The key is finding the right balance between standardization and flexibility.

Companion specifications handle this through a layered approach. The base layer defines what every device of a certain type must provide—the common denominator that enables basic integration. Then vendors can extend the model with their specific capabilities and features.

Take the robotics specification as an example. Every industrial robot needs to report basic status, accept motion commands, and expose safety information. That's the standardized core. But a collaborative robot might add force sensing data, while a high-speed pick-and-place robot adds specific trajectory planning parameters.

The specification work itself is collaborative, bringing together vendors, end users, and automation experts. This ensures the standards reflect real-world needs rather than theoretical ideals. It also means the process takes time—sometimes years—to get right. But the payoff is standards that actually work in production environments.

For anyone implementing OPC UA, the companion specifications are where you start. They provide tested, validated information models that solve common integration challenges. You're not building from scratch. You're building on the collective experience of the industry.

‍

The OPC Foundation Cloud Library: A Central Repository for Information Models

‍

When devices use standardized information models, organizations need a way to access and manage those model definitions. Where do the models reside? How does a system identify which model a new device is using? How can integrators access the definitions they need?

The OPC Foundation's solution is the Cloud Library—a centralized, public repository for information models. Think of it as a global catalog where manufacturers can publish their device models and integrators can discover and download what they need.

This creates an automated discovery mechanism. When you connect to a device, it identifies which information models it implements. Client systems can automatically retrieve those models from the Cloud Library if they are not already available locally. This reduces manual configuration requirements and eliminates the need to track down proprietary documentation.

The Cloud Library also provides tooling for browsing and searching models, understanding dependencies between models, and even generating code stubs for different programming languages. It transforms information models from abstract specifications into practical, usable resources.

For system integrators and automation engineers, this approach improves efficiency in several ways. Engineers can explore what data a device provides before procurement. They can verify that a vendor's implementation matches the standard specification. They can build integration code that works across similar devices from different manufacturers.

The Cloud Library is relatively new, and adoption continues to grow as more vendors publish their information models and more integrators incorporate the repository into their workflows. Information models are transitioning from being scattered across vendor documentation to being centrally discoverable and accessible.

‍

OPC UA PubSub and Information Modeling in Cloud and Edge Applications

‍

Traditional OPC UA uses a client-server architecture, which works well inside the factory where you have stable network connections. But modern manufacturing needs data to flow to the cloud for analytics, and down to the field level for control. This is where OPC UA PubSub comes in.

PubSub extends OPC UA in both directions. To the cloud, it enables efficient data delivery to analytics platforms and business systems without maintaining constant connections. To the field, it supports deterministic, real-time control applications. The interesting part is that it does this while preserving the information modeling capability that makes OPC UA valuable.

Under the hood, OPC UA PubSub often uses MQTT—a proven, efficient messaging protocol. But it adds the semantic layer that MQTT alone does not provide. Data is published with its information model intact, so subscribers automatically understand what they are receiving.

This enables what is often called the "information bus" concept—a factory architecture where hundreds of systems publish their data to a common bus, all using standardized information models. Any new system can subscribe to the data it needs without custom integration work. An MES system can automatically consume data from a new machine. Analytics platforms can discover and ingest process data as needed.

The PubSub specifications continue to evolve, with ongoing work to better incorporate information models into the communication architecture. Real-world deployments are growing as the specifications mature. OPC UA is expanding from a point-to-point protocol to a platform for standardized data exchange across entire factories and supply chains.

‍

Practical Takeaways for Manufacturing Organizations

‍

If you're responsible for factory data infrastructure or digital transformation, what should you do with this information?

Start with the companion specifications relevant to your equipment. Don't try to create custom information models from scratch. Use the standards that exist. If you're working with robotics, machine tools, packaging equipment, or AutoID systems, there are specifications ready to use. They solve problems you'll encounter anyway, and they enable future flexibility.

Consider the Cloud Library in your architecture planning. If you're building new applications or upgrading existing ones, design them to leverage centralized information model repositories. This reduces maintenance burden and enables automatic integration with new devices.

Evaluate your equipment vendors on their OPC UA information modeling support. Not all OPC UA implementations are equal. Vendors who fully implement the relevant companion specifications will integrate more easily and deliver more value. Make this part of your procurement criteria.

Think beyond point-to-point integration. If you're still connecting every system directly to every other system, you're building complexity that will become unmaintainable. Start planning for a more scalable architecture using concepts like the information bus.

Invest in building information modeling expertise on your team. Understanding how to work with information models, extend them appropriately, and leverage them in applications provides operational advantages in system integration and data utilization.

‍

Implementing OPC UA Information Modeling in Your Manufacturing Operation

‍

Industrial automation has focused for decades on moving data between systems—connecting sensors to PLCs, PLCs to SCADA systems, and SCADA to MES. The industry has developed strong capabilities in connectivity, but each connection typically requires custom integration work.

Information modeling represents a shift from connectivity to semantic understanding. When data includes its context and meaning, systems can integrate without custom code for each connection. New equipment can be added with reduced engineering effort. Analytics can be applied across similar assets from different vendors.

The necessary standards, tools, and specifications are available today. Manufacturing organizations are implementing OPC UA information modeling in production environments, typically starting with specific use cases and expanding based on results. The technology has moved from specification to practical implementation.

As manufacturing operations become more data-intensive and automated, the ability to integrate new systems efficiently and extract value from data across the enterprise affects operational performance. Information modeling provides the semantic foundation needed for these capabilities. OPC UA, with its comprehensive information modeling framework, offers manufacturing organizations a path to more flexible, scalable data infrastructure.

‍