Containerized Automation Firmware for Local OT Network Analytics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Industrial automation systems face limitations in control operations and bandwidth usage within operational technology (OT) networks, particularly when communicating with information technology (IT) networks, leading to inefficient data processing and analysis.

Innovation Solution

Implementing software containers in industrial automation systems to replace existing components, enhance functionality, and improve communication by allowing data processing and control operations within the OT network, enabling devices to perform analytics that typically require cloud computing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Difficulty of detecting and measuring

If data is communicated between OT network and IT network for analysis, then data analysis capability is improved, but bandwidth consumption increases

Engineering Contradiction:
Improvedata analysis capabilityVSAvoidbandwidth consumption
Core Design Contradiction:
Difficulty of detecting and measuringVSQuantity of substance

Solution Approach 1:

A software container is introduced as an intermediary component that runs directly on the automation controller within the OT network. This container provides data analysis capabilities locally, eliminating the need to transmit large amounts of raw data to external IT network resources. The container acts as a mediator between the controller's data processing needs and analytical capabilities, performing computations in-place and returning only essential results, thereby maintaining analysis capability while minimizing bandwidth consumption.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If software container is executed on automation controller, then device functionality is improved, but device complexity increases

Engineering Contradiction:
Improvedevice functionalityVSAvoiddevice complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The automation controller's software architecture is segmented into distinct modular components: the base controller functionality and the software container. The container is further divided into isolated execution environments that can be independently deployed, configured, and managed. This segmentation allows new functionalities to be added via containers without modifying or complicating the core controller architecture, maintaining clarity and manageability while enhancing device versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A container runtime environment serves as an intermediary layer between the controller hardware and the containerized software applications. This intermediary manages the execution, resource allocation, and lifecycle of containers, shielding the underlying hardware complexity from users and allowing diverse applications to run on standardized infrastructure without directly increasing controller complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of time

If control operations are performed locally on automation device, then response time is improved, but control capability is limited

Engineering Contradiction:
Improveresponse timeVSAvoidcontrol capability
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The software container provides a universal platform that can execute multiple different control algorithms and analytics workloads within a single runtime environment. By containerizing control capabilities, the system gains access to a broader range of control strategies and data processing functions that would otherwise require separate dedicated hardware or software systems. This multi-functionality is achieved without compromising local execution speed, as containers run directly on the controller's processing units.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12147217B2Automation device firmware as a service via a container implementation
Publication Date: 2024.11.19 ROCKWELL AUTOMATION TECH INC
  • US12147217B2 patent drawing
  • US12147217B2 patent drawing
  • US12147217B2 patent drawing

AI summary

An industrial automation device includes processing circuitry and a non-transitory computer-readable medium that includes instructions that, when executed by the processing circuitry of the industrial automation device, cause the processing circuitry to execute a software container and receive, at the software container, data from one or more industrial automation devices communicatively coupled to the industrial automation device. The instructions, when executed, also cause the processor to determine, using the software container, one or more control operations for the industrial automation device or the one or more industrial automation devices based on the data. Furthermore, the instructions, when executed, cause the processor to cause the industrial automation device to perform the one or more control operations or send the one or more control operations to the one or more industrial automation devices.