Nested Software Configuration Hierarchy for Industrial Control Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for managing executable program files in industrial control systems do not allow for modifications, application of options and variants, or configuration management, leading to limitations in relationship and versioning of software algorithms.

Innovation Solution

A computer-implemented system and method that provides a development environment for creating a nested hierarchy of software configurations, enabling the management of discrete control algorithms based on real equipment characteristics, with features like version traceability, relationship management, and automatic generation of configuration hierarchies in downloadable output files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional techniques are used to manage executable program files, then the system structure remains simple, but the ability to modify, apply options and variants, and manage configurations is lost

Engineering Contradiction:
Improveability to modify and reconfigure softwareVSAvoidsoftware management system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the monolithic algorithm into discrete, modular components that can be independently configured and managed. Each algorithm component can be separately versioned, modified, and applied to different equipment configurations, enabling flexible software management without requiring complete system reconfiguration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a nested hierarchy structure where algorithms are organized within configurations, which are organized within equipment models. This nested structure allows for hierarchical configuration management where lower-level components can be independently modified while maintaining relationships with parent structures.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If a monolithic algorithm structure is used, then the system is easier to implement, but relationship management and versioning capabilities are eliminated

Engineering Contradiction:
Improvesoftware version control and traceabilityVSAvoidconfiguration management structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent pre-defines hierarchical structures, relationships, and versioning frameworks before algorithm development. Configuration templates and equipment models are established in advance, allowing algorithms to be automatically assigned to appropriate configurations and versions without requiring complex runtime decision-making.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system automatically tracks and records relationships between algorithms, configurations, and equipment versions. When modifications are made to algorithms or configurations, the system provides feedback by updating version records and maintaining traceability links, enabling reliable version control and change management.

Inventive Principle:
Principle #23Feedback

3Productivity

If manual configuration management is used, then system complexity is lower, but programming errors increase and time-to-market increases

Engineering Contradiction:
Improvesoftware development speedVSAvoidconfiguration management ease
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system automatically manages configuration assignments, algorithm selections, and versioning based on equipment characteristics and predefined templates. The configuration management process is self-service oriented, where the system automatically tracks changes, maintains relationships, and generates downloadable outputs without requiring extensive manual intervention.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent enables dynamic parameter changes in configurations and algorithms without requiring manual reconfiguration of the entire system. Parameters such as equipment characteristics, operational requirements, and performance specifications can be automatically adjusted, and the system generates updated configurations and downloadable outputs accordingly.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8689184B2Apparatus, system, and method for managing industrial software configurations
Publication Date: 2014.04.01 PROCTER & GAMBLE CO
  • US8689184B2 patent drawing
  • US8689184B2 patent drawing
  • US8689184B2 patent drawing

AI summary

An apparatus, system, and computer-implemented method of managing a software program. The computer comprises a processor, a memory, and an input/output interface for receiving and transmitting information to and from the processor, the computer providing a development environment for developing a set of instructions executable by a system. The processor receives a first program containing information in machine-readable form. The information represents a first set of instructions executable by the system. A configuration is created for the system based on the received information. The processor generates a second program containing a second set of instructions executable by the system based on the configuration. The second set of instructions corresponds to at least one algorithm assembled in a nested hierarchy.