Skip to main content
← All insights

OPC-UA Edge Architecture Patterns for Industrial Data Collection

Architectural patterns for deploying OPC-UA edge gateways to collect, process, and forward industrial data efficiently and reliably.

North Peak Engineering5 min read

OPC-UA provides a standardized way to access industrial data from PLCs, SCADA systems, and other automation equipment. Deploying OPC-UA edge gateways enables efficient data collection, local processing, and reliable forwarding to analytics platforms or cloud systems.

Edge Gateway Architecture

A typical OPC-UA edge gateway architecture includes:

  1. OPC-UA client: Connects to OPC-UA servers on industrial equipment to read data points.

  2. Local processing: Performs data validation, aggregation, or filtering before forwarding.

  3. Data buffering: Stores data locally to handle network interruptions or upstream system unavailability.

  4. Forwarding service: Sends processed data to analytics platforms, databases, or cloud systems via MQTT, REST APIs, or other protocols.

This architecture provides resilience against network issues and enables local processing that reduces upstream data volume.

Connection Management

Reliable OPC-UA connections require:

  • Connection pooling: Reuse connections to multiple OPC-UA servers rather than creating new connections for each read operation.

  • Automatic reconnection: Implement retry logic with exponential backoff to handle temporary network or server issues.

  • Subscription management: Use OPC-UA subscriptions for efficient data collection rather than polling individual data points.

  • Security configuration: Configure appropriate security policies (e.g., Basic128Rsa15, Basic256) and certificate management.

Test connection reliability under various network conditions and server load scenarios.

Data Collection Patterns

Choose collection patterns based on data characteristics:

  • Polling: Read data points at fixed intervals (e.g., every second) for systems that don't support subscriptions.

  • Subscriptions: Use OPC-UA subscriptions for efficient collection of changing values with configurable sampling rates and deadband filters.

  • Event-based: Subscribe to OPC-UA events (e.g., alarms, state changes) for event-driven data collection.

  • On-demand: Read specific data points only when requested, useful for diagnostic or configuration operations.

Combine patterns as needed: subscriptions for high-frequency data, polling for low-frequency points, and events for alarms.

Local Processing and Filtering

Perform local processing to reduce data volume and improve efficiency:

  • Deadband filtering: Only forward data when values change beyond a threshold, reducing unnecessary data transmission.

  • Aggregation: Calculate averages, min/max, or other statistics over time windows before forwarding.

  • Data validation: Check data quality (e.g., range checks, rate-of-change limits) and flag or filter invalid values.

  • Compression: Compress time-series data before transmission to reduce bandwidth requirements.

Local processing reduces upstream system load and network bandwidth while maintaining data quality.

Buffering and Resilience

Implement buffering to handle network interruptions:

  • Local storage: Store data in local databases (e.g., SQLite, InfluxDB) or files when upstream systems are unavailable.

  • Queue management: Use message queues (e.g., MQTT with QoS levels) to ensure reliable delivery with retry mechanisms.

  • Backfill procedures: Automatically backfill missing data when connectivity is restored.

  • Storage limits: Implement storage limits and rotation policies to prevent local storage from filling completely.

Test buffering behavior during network interruptions and system restarts to ensure data integrity.

Security Considerations

Secure edge gateways appropriately:

  • Network segmentation: Place edge gateways in appropriate network zones with restricted access to production systems.

  • Certificate management: Use proper certificate management for OPC-UA connections and secure data transmission.

  • Access controls: Implement appropriate authentication and authorization for gateway configuration and data access.

  • Encryption: Encrypt data in transit and at rest as required by security policies.

Follow industrial cybersecurity best practices (e.g., IEC 62443) for edge gateway deployment.

Monitoring and Diagnostics

Implement monitoring for edge gateway health:

  • Connection status: Monitor OPC-UA connection status and alert on disconnections.

  • Data collection rates: Track data collection rates to identify issues with OPC-UA servers or network problems.

  • Processing performance: Monitor local processing performance and queue depths to identify bottlenecks.

  • Storage utilization: Monitor local storage usage to prevent capacity issues.

Use monitoring data to proactively identify and resolve issues before they impact data collection.

Deployment Patterns

Common deployment patterns include:

  • Single gateway per production line: One gateway collects data from all equipment on a production line.

  • Distributed gateways: Multiple gateways collect data from different areas, with centralized aggregation.

  • Redundant gateways: Deploy redundant gateways for critical data collection to ensure availability.

Choose deployment patterns based on network topology, data volume, and availability requirements.

Performance Optimization

Optimize gateway performance:

  • Efficient data point selection: Only collect data points that are needed for analytics or monitoring.

  • Batch operations: Batch multiple read operations to reduce OPC-UA server load.

  • Connection reuse: Reuse OPC-UA connections rather than creating new connections for each operation.

  • Resource management: Monitor and manage CPU, memory, and network resources to prevent performance degradation.

Benchmark gateway performance under expected data collection loads to ensure adequate capacity.

Integration with Analytics Platforms

Integrate edge gateways with analytics platforms:

  • MQTT: Use MQTT for lightweight, efficient data transmission to analytics platforms.

  • REST APIs: Use REST APIs for structured data transmission and integration with web-based analytics systems.

  • Time-series databases: Forward data directly to time-series databases (e.g., InfluxDB, TimescaleDB) for efficient storage and querying.

  • Message formats: Use consistent message formats (e.g., JSON, Protocol Buffers) for easy integration with downstream systems.

Design integration points to be flexible and support multiple downstream systems as requirements evolve.

OPC-UA edge gateways provide a reliable foundation for industrial data collection. By following established architectural patterns and implementing appropriate resilience, security, and monitoring, you can deploy systems that efficiently collect and forward industrial data for analytics and operational intelligence.

Discuss a deployment

Want to apply this on your line?

Explore how we can deliver similar results for your operation — starting with a technical conversation.

Book a technical call