Process Plant Graphic Object Overrides for Phased Change Propagation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current process control systems face challenges in efficiently configuring and managing process plants due to the limitations of class-based configuration systems, which lead to increased complexity, productivity losses, and difficulties in updating control strategies and graphic displays, especially when dealing with numerous similar equipment and display elements.

Innovation Solution

The implementation of flexible object techniques allows for more variation among instances made from a class object without forcing instances to be removed from the class, enabling phased distribution of changes and incremental verification, thereby improving the usability of class-based configuration systems in running plants.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If class-based configuration systems are used to manage process plants, then standardization and reusability are improved, but device complexity and difficulty in managing variations increase

Engineering Contradiction:
Improvereusability of class objectsVSAvoidcomplexity of managing class variations
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the configuration system into multiple hierarchical levels (class objects, instances, and overrides). Each level handles specific aspects of configuration, allowing variations to be managed at the instance level through selective overrides rather than creating entirely separate class objects. This segmentation reduces the proliferation of class objects while maintaining the ability to handle variations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a temporal dimension to class-instance relationships by introducing version control and phased distribution mechanisms. Changes can be propagated incrementally across instances over time rather than all at once, allowing for verification and rollback capabilities. This transforms the traditional single-dimension class-instance model into a multi-dimensional system that includes time and state management.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Stability of the object's composition

If changes are propagated to all instances from a class object, then consistency is improved, but productivity is reduced due to inability to perform incremental updates

Engineering Contradiction:
Improveconsistency of class instancesVSAvoidspeed of implementing changes
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The patent introduces dynamic control over the propagation process, allowing the system to adapt the distribution of changes based on verification results and operational requirements. Instances can be updated in phases, with the ability to pause, verify, and rollback if needed. This dynamic approach replaces the static all-or-nothing update model, enabling both consistency and productivity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements preliminary testing and verification mechanisms before full propagation. Changes can be tested on a subset of instances first, and only after successful verification are they propagated to remaining instances. This preliminary action ensures consistency while maintaining productivity through risk mitigation and incremental deployment.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If instances are removed from the class to allow variations, then flexibility is improved, but loss of time occurs due to inability to propagate future updates

Engineering Contradiction:
Improveflexibility of instance variationsVSAvoidtime lost in manual updates
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies local quality by allowing each instance to have selective overrides of specific properties while maintaining inheritance for other properties. This means variations are applied locally at the property level rather than globally at the instance level. Instances can have customized properties where needed while still receiving automatic updates for non-customized properties, maintaining both flexibility and automatic update propagation.

Inventive Principle:
Principle #3Local quality

4Adaptability or versatility

If multiple class objects are created to handle variations, then adaptability is improved, but device complexity increases due to proliferation of classes

Engineering Contradiction:
Improveability to handle equipment variationsVSAvoidnumber of class objects to manage
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent makes the class object universal by enabling it to serve as the parent for multiple instances with different variations. Instead of creating specialized class objects for each variation, a single class object can accommodate diverse instances through the override mechanism. This multi-functionality reduces the number of class objects needed while maintaining the ability to handle all variations.

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

Data Source

PatentUS11599251B2Derived and linked definitions with override
Publication Date: 2023.03.07 FISHER ROSEMOUNT SYST INC
  • US11599251B2 patent drawing
  • US11599251B2 patent drawing
  • US11599251B2 patent drawing

AI summary

Flexible graphic element objects in a process plant are configurable both in a run-time operating environment in which a process is being controlled and in a configuration environment. An instantiated flexible graphic element object may be a display view or may be another graphic element included on a display view. A graphic element object may be linked to and/or derived from another graphic element object, and changes to a particular graphic element object may be propagated to its derivations, e.g., according to a distribution policy. Changes to definitions corresponding to a particular graphic element object (e.g., to the definition of a graphic element attribute such as a shape, animation, event handler or property) may be overridden or modified in another object derived from the particular graphic element object. The modified derived object may be renamed and saved separately from the particular graphic element object.