Skip to main content
Version: 5.6

Edge Device Architecture

This chapter describes the architectural recommendations for deploying the OPC Router on edge devices. These recommendations are specifically intended for companies that wish to use a distributed architecture in which data processing and integration take place at the edge of the network.

Definition and Characteristics of Edge Devices​

Edge devices are specialized hardware devices deployed at the edge of a network to process and store data locally. This reduces latency and bandwidth usage, as only relevant data is forwarded to central systems.

Typical Characteristics​

  • Local data processing and integration
  • Low latency
  • Reduced bandwidth usage
  • High availability and reliability
  • Easy scalability

Typical Application Examples​

Production Monitoring​

An edge device deployed in a production facility to collect and process data from machines and sensors in real time.

Condition Monitoring​

An edge device that collects data from various sensors and devices in a warehouse or facility to monitor the condition of the equipment and predict maintenance needs.

Minimum Hardware and Software Requirements​

Hardware Requirements​

  • Edge device or high-performance embedded PC
  • Sufficient CPU capacity (at least 4 cores)
  • CPU with AVX2 support
  • At least 4 GB RAM
  • SSD with sufficient capacity for data processing and storage

Software Requirements​

  • Operating system: Linux or Windows IoT
  • OPC Router software with the necessary plug-ins for communication with existing machines and devices
  • Network infrastructure: LAN or Wi-Fi with sufficient bandwidth and stability

Implementation on Edge Devices​

Docker Container: The OPC Router can be run in a Docker container on the edge device. This provides portability and isolation of the application, as well as easy management and updates.

Installation and Configuration​

  • Docker Installation: Ensure that Docker is installed on the edge device.
  • Docker Compose: Use Docker Compose to configure and orchestrate the OPC Router and the required plug-ins as containers.
  • Configuration: Customize the configuration of the OPC Router and the plug-ins to meet the specific requirements of the environment.

Sample Configuration​

  • Docker Compose File:
version: '3'
services:
  opc-router:
    image: opc-router:<major>.<minor>
    container_name: opc-router
    ports:
      - "8080:8080"
    volumes:
      - ./config:/config
      - ./data:/data

Management of Edge Devices​

Portainer​

You can use Portainer to simplify the management of Docker containers on edge devices. Portainer provides a user-friendly web interface for managing and monitoring containers.

Deployment Templates:​

Create and use deployment templates to quickly and consistently deploy the OPC Router on multiple edge devices.

Documentation and Resources:​

Deploy the OPC Router Portainer App Template

Deploy OPC Router Portainer Edge Template

Configurable Environment Variables

Integration with Industrial Platforms​

Siemens Industrial Edge​

Use Siemens Industrial Edge to integrate the OPC Router into an industrial edge platform specifically designed for use in production environments.

Azure IoT Edge:​

Use Azure IoT Edge to integrate the OPC Router into the Azure cloud and benefit from the extensive IoT services and features of the Azure platform.

Documentation and Resources:​

Siemens Industrial Edge

Azure IoT Edge Marketplace

Security Considerations​

Security is also an important aspect for edge devices. The following measures should be considered:

  • Network security: Implement firewalls and network segmentation to prevent unauthorized access.
  • Data encryption: Where possible, data transmission between machines and OPC Router instances should be encrypted. However, older systems used in industry often do not support this. In such cases, it is recommended to implement physical separation or segmentation via VLANs. The OPC Router system can be deployed across multiple networks so that web management is accessible from "outside." For OPC Router management, HTTPS should always be configured and strong passwords used.

Use HTTPS

Use HTTPS (Windows)

  • User Access Control: Set up user accounts and roles to control access to the OPC Router instance and the data. Each user should have their own account, or there should be an integration with, for example, Azure EntraID / Active Directory.

Integrate Microsoft Entra ID/Azure AD

User Management

Backups and Updates​

Regular Backups:​

  • Automated Backups: Implementation of automated backups of the OPC Router configuration and databases on the edge devices.
  • External Storage Locations: Save backups to external storage locations, e.g., in the cloud or on external hard drives.

Regular Updates:​

  • Software Updates: Keep the OPC Router and all used plug-ins on the edge devices up to date.
  • Easy Updates in Container Environments: In Docker environments, updates can be performed by simply updating the image tag in the Compose file and re-running the Compose command. Alternatively, a new container can be created with the updated version, which continues to use the volume containing the data from the previous version.

Summary​

Using edge devices with the OPC Router offers a flexible and efficient solution for local data processing and integration. By utilizing Docker containers and management tools such as Portainer, companies can easily scale and manage their edge device architecture. Taking security aspects into account protects data and systems. Regular backups ensure data security. Regular updates ensure the continuous performance and security of the entire system.