Process Control System GUI Isolation via Distributed Runtime

Solution Overview

Problem

Current industrial control systems face challenges in integrating user interfaces from different applications without risking the stability of core control functions, as flaws in integrated code components can cause the entire user interface to crash or malfunction.

Innovation Solution

A method and system where a graphical user interface is displayed by a client application in a separate computing environment, with graphic representations of control objects sent via an intermediate service to integrate with the core system's interface without executing any code components from the integrated applications, using a technique similar to Remote Desktop for remote viewing and sharing pixel information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If user interface components from different applications are plugged in to provide integrated user interface, then user interface integration is achieved, but system reliability deteriorates because code components from integrated applications execute in the same environment as core control system components

Engineering Contradiction:

Improveuser interface integrationVSAvoidsystem stability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system is divided into two separate execution environments: a first computer processing environment for the control system client application and core control functions, and a second computer processing environment for hosting integrated application code components. This segmentation isolates potentially flawed integrated application code from core control system components, preventing crashes while maintaining UI integration capabilities.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

A distributed run-time system acts as an intermediary between the two separate processing environments. It enables communication and coordination between the control system client application in the first environment and the integrated application code components in the second environment, allowing seamless user interface integration without direct code execution in the same space.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If code components from integrated applications are executed in the same environment as core control system components, then seamless integration is achieved, but the risk of system crash increases due to potential flaws in integrated code

Engineering Contradiction:

Improveseamless integrationVSAvoidsystem stability

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system is divided into two separate execution environments: a first computer processing environment for the control system client application and core control functions, and a second computer processing environment for hosting integrated application code components. This segmentation isolates potentially flawed integrated application code from core control system components, preventing crashes while maintaining UI integration capabilities.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system provides access to integrated application code components through the distributed run-time system without requiring them to be physically copied or installed in the core control system environment. The components are accessed remotely across network connections, maintaining operational seamlessness while enforcing environmental separation for safety.

Inventive Principle:

Principle #26Copying

3Reliability

If separate computing environments are used for integrated applications, then system stability is improved by isolating non-core application execution, but interface integration complexity increases

Engineering Contradiction:

Improvecore control function stabilityVSAvoidinterface integration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The distributed run-time system provides universal functionality for hosting and managing multiple integrated application code components across different processing environments. It offers standardized interfaces and communication protocols that simplify integration despite the underlying environmental separation, reducing the perceived complexity for users.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

A distributed run-time system acts as an intermediary between the two separate processing environments. It enables communication and coordination between the control system client application in the first environment and the integrated application code components in the second environment, allowing seamless user interface integration without direct code execution in the same space.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10606616B2Method for control in a process control system implemented in part by one or more computer implemented run-time processes

Publication Date: 2020.03.31 ABB (SCHWEIZ) AG

AI summary

A method for control in a process control system, where a graphical user interface of said process control system is arranged with graphic representations of one or more control objects for monitoring and/or control of a process or an equipment. The control system GUI is displayed by a control system client application on a computer or workstation. In addition, one or more applications for monitoring and/or controlling at least one said control object are run in a computing process environment separate from said process control system. No code components execute in the same processing space as that running the GUI for the process control system. Any flaw or error in the extended applications cannot affect the control system program controlling an industrial process in real-time. A control system and a computer program are also disclosed.