High-Level Rule Management for Complex Operational Changes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing rule management systems face significant overhead in identifying, modifying, and testing multiple rules when implementing changes, especially in complex operational systems with frequent changes or high consistency requirements.

Innovation Solution

The introduction of high-level rules that modify the effects of multiple rules by combining or replacing their actions, allowing users to specify criteria and actions through a rule management interface, with a processor executing these rules efficiently and minimizing conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple individual rules are modified to implement a change, then the operational system can accommodate complex and granular requirements, but the time and effort required to identify, modify, and test each rule increases significantly

Engineering Contradiction:
Improveability to manage granular requirementsVSAvoidtime to identify, modify and test rules
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges multiple individual rules into a single high-level rule that combines their conditions and effects. When a high-level rule is created, it automatically identifies and integrates the logic from multiple existing rules (Rm) that share common conditions, allowing the system to implement changes across multiple rules through a single modification point rather than editing each rule individually

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The high-level rule serves multiple functions simultaneously: it acts as a parent rule that can be executed directly, while also serving as a template that automatically generates or modifies multiple child rules (Rm). This universal structure allows a single high-level rule to manage granular requirements across multiple operational contexts without requiring separate rule definitions for each scenario

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

2Reliability

If multiple rules are modified to implement a change, then the system can maintain consistency across different operational requirements, but the testing overhead and potential for errors increase

Engineering Contradiction:
Improveconsistency of decisionsVSAvoidcomplexity of rule modification process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by automatically identifying which rules (Rm) should be modified when a high-level rule is created. The rule management system pre-processes the change by matching the high-level rule conditions against existing rules, determining the scope of modification before actual changes are made, and preparing the necessary test cases in advance

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the rule management system monitors the execution and performance of high-level rules and their generated child rules. When inconsistencies or errors are detected in rule modifications, the system provides feedback to automatically adjust the rules or alert operators, ensuring consistency across operational requirements while reducing manual testing overhead

Inventive Principle:
Principle #23Feedback

3Ease of operation

If individual rules are executed separately, then each rule can be precisely controlled, but the overhead of managing and executing multiple rules increases

Engineering Contradiction:
Improvecontrol over individual rulesVSAvoidefficiency of rule execution
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent introduces a hierarchical dimension to rule management by creating high-level rules that operate above the individual rule level. This additional layer allows the system to execute rules in batches or groups based on the high-level rule structure, maintaining precise control over individual rules while enabling efficient bulk execution when multiple rules share common high-level conditions

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

Data Source

PatentUS11651241B2System and method for specifying rules for operational systems
Publication Date: 2023.05.16 MASTERCARD INT INC
  • US11651241B2 patent drawing
  • US11651241B2 patent drawing
  • US11651241B2 patent drawing

AI summary

A method of controlling an operational system by a rules management system comprising a processor and a memory, and a computing apparatus comprising a processor and a memory are provided. The processor is programmed to execute rules from a rules repository stored on a memory in response to a request. The computing apparatus further comprises a high rules repository storing one or more high level rules, wherein each high level rule, when executed by the processor, modifies the effect of execution of one or more rules Rm in the rules repository; and a high rules conditions module that when executed by the processor identifies and executes the high level rules that apply to the request.