Skip to main content
Version: 5.3

Edge device architecture

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

Definition and characteristics of edge devices

Edge devices are specialized hardware devices that are used at the periphery of a network to process and store data locally. This reduces latency and bandwidth usage by only forwarding relevant data to central systems.

Typical characteristics

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

Typical application examples

Example 1: Production monitoring An edge device used in a production plant to collect and process data from machines and sensors in real time.

Example 2: Condition monitoring An edge device that collects data from various sensors and devices in a warehouse or plant to monitor the condition of the equipment and predict maintenance needs.

Minimum hardware and software requirements

Hardware requirements

  • Edge device or powerful embedded PC
  • Sufficient CPU capacity (at least 4 cores)
  • 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 required plug-ins for communication with the existing machines and devices
  • Network infrastructure: LAN or WLAN 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: Make sure 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 the specific requirements of the environment.

Example 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

Use Portainer to simplify the management of Docker containers on the 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 to multiple edge devices.

Documentation and Resources:

OPC Router Portainer App Template deployment

OPC Router Portainer Edge Template deployment

Configurable environment variables

Integration with industrial platforms

Siemens Industrial Edge:

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

Azure IoT Edge:

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

Documentation and Resources:

Siemens Industrial Edge

Security aspects

Security is an important aspect even in small use cases. The following measures should be taken into account:

  • Network security: Implement firewalls and network segmentation to prevent unauthorized access.
  • Data encryption: If possible, data transmission between the machines and the OPC Router instance 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 present in multiple networks so that the web management can be accessed from the “outside”. HTTPS should always be configured for OPC Router management and secure passwords should be used.

Use HTTPS (Docker

Use HTTPS (Windows

  • User access control: Setting up user accounts and roles to control access to the OPC Router instance and the data. Each user should have their own user, or there should be a connection to e.g. Azure EntraID / Active Directory.

Connect Microsoft Entra ID/AzureAD

User management

Backup and updates

Regular backups:

  • Automated backups: Implementing automated backups of the OPC Router configuration and databases on the edge devices.
  • External storage locations: Storing backups in external storage locations, e.g. in the cloud or on external hard disks.

Regular updates:

  • Software updates: Keep the OPC Router and all plug-ins used 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 and restarting the container.

Summary

Using edge devices with the OPC Router provides a flexible and efficient solution for local data processing and integration. By using Docker containers and management tools such as Portainer, companies can easily scale and manage their edge architecture. Taking into account security aspects and regular backups and updates also ensures that data and systems are protected and that the entire system continues to perform and remain secure.