What is OPC UA?
OPC is short for “Open Platform Communications”. UA stands for “Unified Architecture”. OPC UA is an interoperability standard that was developed specifically for secure and reliable data exchange with Industry 4.0 and IoT applications. OPC UA offers considerable advantages for these applications, enabling platform-independent, secure, and scalable communication between industrial devices and systems. OPC UA standardizes data formats and protocols at the interface between various components and offers comprehensive security functions to protect communication.
These are the benefits:
Platform independence:
OPC UA offers platform-independent, standardized communication between different systems, regardless of manufacturer or technical environment.
Security:
OPC UA provides encryption, authentication and authorization to ensure that data remains confidential and can only be read by authorized persons or systems. Users can therefore be sure that their data is protected.
Flexibility and scalability:
OPC UA supports a wide variety of transport protocols, from TCP/IP to HTTPS and MQTT. This means that the OPC UA interface can be used in many different applications and devices to ensure that the data arrives where it is needed. OPC UA systems can also be flexibly expanded to meet new requirements, either by adding new devices or by adapting to growing data volumes.
Standardization:
OPC UA was developed and is maintained by the OPC Foundation to ensure an interoperable communication standard. To cover industry-specific requirements, the OPC Foundation works with members on the development of Companion Specifications that go beyond the basic standard. These Specifications ensure consistency and compatibility and facilitate the use of OPC UA and the integration of a wide range of system components in industrial scenarios.
How does the OPC UA communication work?
OPC UA communication works on the basis of a client-server or publisher-subscriber model (pub/sub model) and uses a serviceoriented architecture (SOA).
Client-server model:
The OPC UA server provides data that can be retrieved and updated by OPC UA clients. Communication takes place via defined services such as reading, writing, subscribing to data changes and alarms. This means that clients can always access current data and react to changes, which ensures reliable and timely data communication.
Publisher-subscriber model:
The publisher sends data to one or more subscribers. The subscribers receive data from the publisher. This model is particularly suitable for scenarios in which data needs to be distributed to multiple recipients in real time.
How can OPC UA be used for data integration with Industry 4.0 and IoT applications?
There are several typical scenarios and project situations in which OPC UA is used at the interface between OT and IT:
1. Modernization of legacy systems through OPC UA integration
Many machines and devices in legacy systems do not have a standardized OPC UA interface and use older communication protocols or proprietary interfaces instead. In modernization projects, it is often necessary to integrate these machines and devices into innovative solutions via OPC UA to take advantage of Industry 4.0 and IoT applications and ensure effective data integration.
2. Efficient connection and integration of OPC UA servers in modern facilities
In modern systems, many devices are already equipped with integrated OPC UA servers. The challenge here is to connect the applications efficiently, easily and securely to a large number of data sources. In addition, there is often a need to allow applications to access data from OPC UA servers via standard protocols commonly used in the IT world, such as MQTT.
3. Standardization and integration through Companion Specifications and OPC UA information models
In modern facilities, there is a growing need for the use of Companion Specifications or OPC UA Information Models. They standardize interfaces for devices, machines and systems, including semantic information, and facilitate their integration into innovative IoT solutions, for example via “Unified Name Spaces” (UNS).
Adapting OPC UA solutions to individual operating processes and infrastructures
All the requirements and application scenarios can usually be covered with standard products that support OPC UA and minimize project-specific integration efforts.
However, because users differ in terms of organization, operational processes, and existing infrastructure, the optimal choice for adapting an OPC UA-based data integration solution to a specific organization may vary. Depending on the circumstances, Docker-based software solutions, Windows-based software solutions, or hardware solutions may be the most suitable option.
Softing OPC UA expertise and portfolio
Softing OPC UA expertise and portfolio With our extensive experience in OPC technology and close collaboration with the OPC Foundation, we are the ideal partner for your OPC data integration needs. Whether for legacy systems or new installations, and whether supporting traditional operations or IT-driven and automated processes, Softing offers tailored end-user products for OPC UA-based data integration.
In addition to these end-user products, Softing Industrial develops and markets Software Development Kits (SDKs) for project-specific development of OPC UA client and server components. These SDKs can be used for both device and software applications. We are are also utilizing these SDKs in the development of our OPC UA-based end-user products. The synergies created by this approach benefit both the users of our end-user products and the users of the SDKs.
Complementing our standard products, we offer a comprehensive training and service program to provide our customers with the best possible support.
Softing products for OPC UA data integration
Windows-based OPC servers and middleware – serve as software interfaces for exchanging data between different systems and devices. The OPC servers collect data from different devices and make it available in a standardized format, while OPC middleware facilitates data forwarding and processing between different systems.
Product: dataFEED OPC Suite
Integration platforms for data aggregation – collect, combine and consolidate vast data volumes from different sources. This allows users to control data at a single point and manage it easily and securely.
Products: Secure Integration Server, edge Aggregator
Docker-based OPC UA software solutions – run as containers and offer a flexible and scalable way to use OPC UA functionalities.
Products: edge Aggregator, edgeConnectors, edgePlugs, smartLink SW-HT, smartLink SW-PN
OPC UA Software Development Kits (SDKs) – provide the necessary tools and libraries to develop applications that can act as OPC UA clients or servers. These applications collect, process and forward data from various devices and controllers.
Products: OPC UA SDKs
Hardware gateways for network access parallel to the controller – are ideal for expanding existing systems. They provide additional communication options via OPC UA without affecting the operation of the control system.
Products: smartLink gateways
Hardware gateways for direct access to controller data – are suited for applications that require tight integration and direct access to controller information.
Products: edgeGate, ua Gates, eATM Manager Control Logix
