OOUAMiddleware – Industrial OPC UA Middleware Platform

A semantic-model-driven industrial OPC UA platform for integration, execution and archiving.

OOUAMiddleware architecture showing OPC UA Configuration Studio, CoreServer, industrial connectivity through VPI, data persistence through VFI, and OPC UA client applications.

What is OOUAMiddleware?

OOUAMiddleware is a model-driven industrial integration platform built on the OPC UA standard (IEC 62541).
It combines OOUA Configuration Studio, an engineering environment for configuring and instantiating OPC UA information models, with OOUA CoreServer, a native C/C++ runtime that loads and executes these models.
Multiple OPC UA information models can coexist within the same AddressSpace, preserving their types, namespaces and relationships.
Modular Virtual Protocol Interfaces (VPIs) connect heterogeneous industrial systems and data sources, while Virtual File Interfaces (VFIs) provide integration with data persistence and historical storage solutions.
This architecture separates information modeling, industrial connectivity and data persistence, enabling the same OPC UA information model to be used with simulated or connected industrial systems.

OOUAMiddleware projects are prepared using OOUA Configuration Studio, which supports OPC UA information model instantiation and the configuration of industrial connectivity and persistence interfaces before runtime execution.

OOUAMiddleware functional architecture showing OOUA Configuration Studio for OPC UA information model configuration and deployment, OOUA CoreServer for runtime execution, Virtual Protocol Interfaces (VPI) for industrial connectivity, and Virtual File Interfaces (VFI) for data persistence and historization. The platform exposes structured OPC UA information to SCADA, MES, analytics, digital twins and AI agents.

For a broader definition of the role, scope and architectural purpose of this software category, see OPC UA Middleware.

A working example of the platform is available through the OOUAMiddleware ProductionCell demo, which illustrates a model-driven runtime execution, a modular connectivity and an industrial OPC UA behavior in practice.

How OOUAMiddleware Works

OOUAMiddleware separates industrial system modeling, runtime execution, protocol connectivity and data persistence.

OOUA Configuration Studio is used to configure and instantiate OPC UA information models and prepare deployment configurations. OOUA CoreServer loads these models and exposes their instantiated AddressSpace through OPC UA services.

Virtual Protocol Interfaces (VPI) connect industrial systems and external protocols to the runtime. Virtual File Interfaces (VFI) connect persistence backends used to store operational and historical data.

This separation allows industrial connectivity and storage implementations to evolve without requiring application code generation for each OPC UA information model.

Designed for Complex Industrial Environments

  • Multi-protocol integration
  • IT/OT convergence
  • Long lifecycle industrial systems
  • High availability requirements
OPC UA middleware platform – NodeSet-driven domain modeling and industrial runtime

Core Capabilities of the Platform

  • OPC UA Server & Client Stack
  • Modular Connectivity Drivers
  • Dynamic AddressSpace from NodeSet XML
  • Redundancy mechanisms
  • Structured Information Modeling
  • Companion Specification integration
  • Flexible Archiving (SQL, Parquet, Binary)
  • Extensible Plug-in Architecture

Platform Architecture Overview

OOUAMiddleware is built around structured OPC UA information models that define the semantic structure of the system. These models are created using official Companion Specifications or a dedicated industrial modeling methodology.
The semantic layer drives the runtime core, industrial connectors and archiving modules. Its execution model relies on runtime interpretation of NodeSet-based models rather than generated code. This architectural differentiator is described in OpenOpcUa Runtime Model Architecture. For the system-level view of component separation, runtime orchestration and extension mechanisms, see OPC UA Middleware Architecture.

Industrial Protocol Integration

OOUAMiddleware is designed to integrate heterogeneous industrial data sources through a modular driver architecture. Data acquisition is handled by dedicated collection modules, allowing protocols to be added, updated or replaced without impacting the OPC UA core runtime or the information modeling layer.
The platform can act as an industrial data concentrator, mapping field-level data into structured OPC UA information models and exposing it through a consistent semantic interface.
Typical industrial integration scenarios include:

  • PLC and field device acquisition through modular protocol drivers
  • OPC UA aggregation and gateway architectures
  • OPC Classic wrapping for legacy environments
  • Incremental modernization where protocols coexist during migration phases

Supported and commonly used protocol modules include Modbus, Siemens S7 and EtherNet/IP, as well as OPC UA and legacy OPC Classic integration. OOUAMiddleware supports OPC UA Publish-Subscribe communication in accordance with IEC 62541-14 through its MQTT Publisher and MQTT Subscriber Virtual Protocol Interfaces (VPIs). Additional drivers can be implemented following the same modular principles, preserving long-term maintainability and strict IEC 62541 alignment. In heterogeneous industrial environments, protocol integration also raises deployment and exposure questions. A structured middleware layer helps preserve controlled boundaries between field connectivity, semantic modeling and enterprise-facing interfaces. For a broader security-oriented perspective, see Secure Deployment of Industrial Communication Protocols

Flexible Industrial Data Storage

OOUAMiddleware provides flexible and modular data storage mechanisms adapted to diverse industrial architectures.
Historic and operational data can be persisted using different storage backends depending on performance, traceability and analytics requirements. Supported storage options include relational SQL databases, structured file exports (CSV), native binary formats and high-efficiency columnar formats such as Apache Parquet for large-scale analytics environments.
The storage layer is fully decoupled from the runtime core. This separation allows organizations to evolve their data strategies — including integration with data lakes or cloud-based systems — without modifying the semantic information model or the OPC UA server layer.
OOUAMiddleware also supports OPC UA Historical Access, ensuring standardized access to archived industrial data in compliance with IEC 62541.

Deployment and Usage Model

Industrial deployment, commissioning and first-level support are provided by OOUA integration partners. 4CE Industry develops and maintains the platform and provides partner training, remote Level 2 technical support and separately scoped engineering services.

Key Characteristics of OOUAMiddleware

  • Model-driven runtime: loads OPC UA information models and instantiated AddressSpaces from NodeSet XML without generating application code for each model.
  • Multiple information models: supports the coexistence of multiple OPC UA information models within a single AddressSpace.
  • Industrial connectivity: uses modular VPIs to connect industrial controllers, OPC UA systems and other supported protocols.
  • Data persistence: integrates databases and file-based storage through VFIs, with OPC UA Historical Access for standardized access to archived data.
  • Runtime services: implements OPC UA services including subscriptions, Methods, Events and Alarms & Conditions.
  • Deployment flexibility: separates information models, connectivity and persistence from the core runtime.

Typical industrial scenarios

  • Industrial Data Integration Layer
    Integrating PLCs, machines and field systems into a unified OPC UA architecture.
  • OPC Classic Migration Gateway
    Replacing legacy OPC Classic infrastructures with modern OPC UA systems.
  • Industrial Data Historization Platform
    Collecting, structuring and archiving industrial process data.
  • Model-Driven OPC UA Architecture
    Implementing structured OPC UA information models across industrial systems.
  • Industrial Edge Integration
    Connecting machines to MES, cloud platforms or analytics pipelines.

Discuss Your Industrial OPC UA Architecture

Industrial OPC UA deployments require more than protocol connectivity.
They demand structured information modeling, architectural consistency and long-term interoperability aligned with IEC 62541 principles.
Whether you are defining a new domain-specific information model, integrating Companion Specifications or designing a multi-system OPC UA architecture, a structured technical discussion ensures that modeling decisions and runtime behavior remain aligned.
Operational support, architectural guidance and structured technical sponsorship programs related to OOUAMiddleware are provided through 4CE Industry.

From OPC UA Middleware Concepts to Industrial Deployment

OOUAMiddleware implements these integration principles through a configurable industrial runtime. Continue with the platform documentation, explore the model-driven architecture or evaluate the ProductionCell demonstration.

OOUAMiddleware

Explore the industrial platform and its technical capabilities.

Architecture

Examine the separation between models, runtime and integration modules.

Runtime Model

Understand how NodeSet types and instances are loaded at runtime.

Information Modeling

Explore the structure and semantics of OPC UA information models.

Download & Evaluate

Request access to the ProductionCell demonstration package.