Flow RTU Enablement Framework for Independent Software Releases

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current flow computer software and RTU software are monolithic, requiring full updates and releases for even minor changes, leading to unintended consequences and extensive testing, and necessitating custom host software for communication and visualization.

Innovation Solution

A modular software architecture for flow computers with a partitioned enablement framework that manages multiple application instances independently, allowing individual updates and licensing, and supports component add-ons with a common framework for resource management and communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If monolithic software architecture is used, then system integration is simplified, but software updates require full releases causing unintended consequences and extensive testing

Engineering Contradiction:
Improvesoftware architecture complexityVSAvoidsoftware update reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The software is divided into separate application instances (e.g., flow calculation application, data management application, user interface application) that can be independently updated. Each application instance operates as a distinct module with its own memory space and execution context, allowing granular updates without requiring full system re-release and extensive regression testing.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If monolithic software architecture is used, then resource management is centralized, but resource utilization efficiency decreases

Engineering Contradiction:
Improveresource management complexityVSAvoidsoftware development productivity
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

Computational resources are allocated to separate application instances based on their specific needs. Each instance can be independently scaled, started, or stopped, improving overall resource utilization efficiency and enabling parallel development and deployment of different software components.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If custom host software is required for communication and visualization, then system functionality is enhanced, but system complexity and maintenance burden increase

Engineering Contradiction:
Improvecommunication and visualization capabilityVSAvoidsoftware synchronization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The flow computer is designed with standardized communication interfaces and protocols that can be accessed by multiple different host systems and visualization tools. This universal interface approach eliminates the need for custom host software development while maintaining enhanced communication and visualization capabilities across different platforms.

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

Data Source

PatentUS20260079689A1Flow Computer Remote Terminal Unit with Modular Software Architecture
Publication Date: 2026.03.19 ABB (SCHWEIZ) AG
  • US20260079689A1 patent drawing
  • US20260079689A1 patent drawing
  • US20260079689A1 patent drawing

AI summary

A method includes executing, by a flow remote terminal unit (RTU) management system, a plurality of application instances that manage one or more industrial operations at an industrial facility; and receiving, from one or more input devices at the industrial facility and by an enablement framework of the RTU management system, input device information associated with the one or more industrial operations. The enablement framework manages the plurality of applications instances being executed by the flow RTU management system, and the enablement framework is partitioned separately in memory from the plurality of application instances. The method also includes determining, based on using a dispatcher of the enablement framework, one or more application instances, from the plurality of application instances, that utilize the input device information; and providing, by the dispatcher of the enablement framework, the input device information to the determined one or more application instances.