Skip to main content

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 Features​

  • 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​

The system requirements in the “Docker Systems” section are decisive—that section also specifies which processor architectures the two images support (x86_64 with AVX2 or ARM64). For edge devices, the following also applies:

  • Edge device or high-performance embedded PC
  • Sufficient CPU capacity (at least 4 cores)
  • At least 4 GB of RAM—this is the recommended amount for the runtime image with integrated MongoDB. The 8 GB specified for the smaller solutions applies to a native Windows installation.
  • 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:
services:
  opc-router:
    image: opcrouter/runtime:latest
    container_name: opc-router
    restart: unless-stopped
    ports:
      - "8080:8080"
    environment:
      - OR_I_ACCEPT_EULA=true
      - INITIAL_USERNAME=<username>
      - INITIAL_PASSWORD=<password>
    volumes:
      - opcrouter-data:/data
      - opcrouter-logs:/var/log/opcrouter
volumes:
  opcrouter-data:
  opcrouter-logs:

For more examples and an explanation of the environment variables, see Docker Compose and Configurable Environment Variables.

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​

Network security, data encryption, and user access control apply to edge devices as before; they are described in the section on small-scale solutions.

Unlike a device in a data center, however, an edge device is often freely accessible in the hall. This results in two issues that centrally located instances do not have:

  • Physical Access: Whoever has the device in their hands also has access to its storage media. Secure the storage media with encryption and restrict access to the installation site; an unencrypted volume exposes project data and stored credentials.
  • **Device Loss: Plan for device failure or loss as a normal occurrence. Since the engineering configuration is backed up at a central location, a replacement device can be set up and the backup restored. Additionally, revoke the credentials and certificates that were stored on the lost device.

Backup and Updates​

For backups and updates, follow the procedure for small-scale solutions. On an edge device, this applies to the device’s configuration and databases, as well as the container’s image tag; store the backups in a central location, not on the device itself.

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.