Rule Engine Logic Architecture for Power System Control

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing power system control systems are difficult to modify due to cumbersome coding techniques, limiting flexibility in adding or modifying logic functions.

Innovation Solution

A method and system that utilize a rule engine logic architecture, where data assets are associated with rule engine logic identifiers in configuration files, allowing easy modification by running specific rule engines and sending results to displays, along with confidence values if applicable, to control power systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional coding techniques are used to add or modify logic functions, then the control system can perform logic operations, but the system becomes difficult to modify and requires cumbersome coding techniques

Engineering Contradiction:

Improveflexibility to add or modify logic functionsVSAvoidcomplexity of modifying control system logic

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The control system logic is segmented into separate, independently configurable rule engines that can be selectively activated. Each rule engine operates as a discrete unit that processes specific data assets according to predefined logic, allowing individual rules to be added, modified, or removed without affecting the entire system. This segmentation enables flexible modification of logic functions while maintaining system stability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system employs dynamic configuration files that allow logic functions to be modified at runtime without requiring system reconfiguration or recompilation. The configuration files store mappings between data assets and rule engines, enabling users to dynamically add, remove, or modify logic rules by simply updating configuration parameters rather than rewriting code, thus achieving easy adaptability.

Inventive Principle:

Principle #15Dynamics

2Ease of operation

If configuration files are used to associate data assets with rule engine logic identifiers, then modification becomes easier, but the system requires additional configuration management overhead

Engineering Contradiction:

Improveease of modifying logic functionsVSAvoidcomplexity of configuration file management

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system automatically processes configuration files to establish associations between data assets and rule engines without requiring manual intervention for each rule configuration. The configuration management system self-updates and self-validates rule associations, reducing the operational overhead for users while maintaining ease of modification through standardized configuration formats.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS8280834B2Systems and methods involving rule engines

Publication Date: 2012.10.02 GE INFRASTRUCTURE TECH LLC

AI summary

A method for monitoring a system includes receiving a first data asset from the system, receiving a configuration file, determining whether the configuration file includes the first data asset and an associated first rule engine logic identifier, and running a first rule engine associated with the first rule engine logic identifier responsive to determining that the configuration file includes the first data asset and the associated first rule engine logic identifier. The method also includes sending the first data asset to the first rule engine, receiving a first result from the first rule engine, and sending the first result to a display for presentation to a user.