Hierarchical Data Structure Synchronization Across Enterprise Hierarchies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise data management systems struggle to maintain consistency across multiple hierarchal data structures, leading to conflicts and inefficiencies when changes are made to one structure without corresponding modifications in others.

Innovation Solution

A system applies a set of rules and a machine learning model to modify hierarchal data structures, ensuring consistency by determining necessary modifications in related structures based on user inputs and historical data patterns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If enterprise data management systems allow different entities to access enterprise data using different applications, then data accessibility and versatility are improved, but maintaining consistency across multiple hierarchal data structures becomes complex and error-prone

Engineering Contradiction:
Improvedata accessibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the hierarchal data structure into multiple independent hierarchies (e.g., organizational hierarchy, cost center hierarchy, project hierarchy) that can be modified independently. Each hierarchy is treated as a separate entity that can be updated without requiring simultaneous updates to all other hierarchies, thus reducing system complexity while maintaining versatility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by proactively identifying and applying required modifications to dependent hierarchies before conflicts arise. When a change is detected in one hierarchal data structure, the system automatically determines and executes necessary modifications in related structures in advance, preventing consistency errors before they occur.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system proactively modifies multiple hierarchal data structures to maintain consistency, then data consistency is improved, but the risk of creating conflicts and errors increases

Engineering Contradiction:
Improvedata consistencyVSAvoidconflict risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent implements feedback mechanisms where the system continuously monitors hierarchal data structures for changes and automatically triggers corrective modifications in dependent hierarchies. This closed-loop feedback system detects inconsistencies and resolves them proactively, maintaining data consistency while minimizing conflict risk through automated control.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system introduces an intermediary layer (the data processing system) that mediates between different hierarchal data structures. This intermediary automatically determines and executes required modifications, acting as a buffer that prevents direct conflicts between hierarchies while ensuring consistency through controlled, rule-based transformations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If manual synchronization of hierarchal data structures is performed, then system complexity is reduced, but time consumption and productivity are worsened

Engineering Contradiction:
Improvesystem complexityVSAvoidsynchronization time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent enables the hierarchal data structures to self-synchronize through automated rule-based modifications. When a change occurs in one hierarchy, the system automatically determines and applies necessary modifications to dependent hierarchies without requiring manual intervention, thus eliminating time loss while keeping system complexity manageable through predefined rules.

Inventive Principle:
Principle #25Self-service

4Productivity

If automated rule-based modification is applied to hierarchal data structures, then productivity and synchronization efficiency are improved, but the complexity of managing and applying rules increases

Engineering Contradiction:
Improvesynchronization efficiencyVSAvoidrule management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal rule-based framework that handles multiple types of hierarchal data structure modifications through a single standardized mechanism. The same rule engine and modification logic are applied across different hierarchy types (organizational, cost center, project), reducing rule management complexity by providing a multi-functional, unified approach rather than separate rules for each hierarchy type.

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

Data Source

PatentUS12475095B2Hierarchal data structure modification
Publication Date: 2025.11.18 ORACLE INT CORP
  • US12475095B2 patent drawing
  • US12475095B2 patent drawing
  • US12475095B2 patent drawing

AI summary

Techniques for modifying hierarchal-structured data of one hierarchal data structure based on a modification to another hierarchal data structure are disclosed. A system determines that a modification has been made, or is requested to be made, to a particular hierarchal data structure. The system analyzes a set of rules to determine whether the modification of the hierarchal data structure triggers another modification to an additional hierarchal data structure. The additional hierarchal data structure includes different nodes, or nodes arranged in a different hierarchal structure, than the particular hierarchal data structure. The system modifies the additional hierarchal data structure based on the rule. The modification of the additional hierarchal data structure is different than the modification to the particular hierarchal data structure.