Template Node Detection for Cross-Application Data Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual data synchronization between disparate data hierarchies in different applications is cumbersome, leading to poor alignment, data divergence, and inaccurate decision-making due to inconsistent data mappings, especially when data hierarchies change frequently or in response to events like mergers or acquisitions.

Innovation Solution

A data management system uses rules-driven or AI-driven processes to identify template records for updating connections between data hierarchies, leveraging ancestor information and vector embeddings to find best-matching records, and applies these updates to target dimensions while considering roll-up structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual data synchronization is performed between different applications, then data can be updated across applications, but the process becomes cumbersome and time-consuming, especially when data hierarchies change frequently

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service data synchronization by automatically detecting template nodes in target hierarchies that match source nodes, eliminating the need for manual intervention. The automated detection process compares data structures, identifies matching templates based on hierarchy and attributes, and propagates updates automatically, allowing the system to serve itself without human effort while maintaining data consistency across applications.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-establishing template node mappings between source and target data hierarchies. When data changes occur in the source application, the system has already prepared the template relationships, enabling rapid automatic propagation of updates to target applications without requiring real-time manual configuration or analysis of data structure changes.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual data mapping is established between applications, then data can be synchronized, but significant manual labor is required from subject matter experts and the process must be repeated when data hierarchies change

Engineering Contradiction:
Improvedata alignmentVSAvoidmanual configuration effort
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system replaces manual expert configuration with self-service automated detection. The system autonomously analyzes data hierarchies, identifies template nodes based on structural and attribute matching, and establishes mappings without human intervention. This eliminates the need for subject matter experts to manually configure data mappings and repeat the process when hierarchies change.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements dynamic template node detection that automatically adapts when data hierarchies change. Instead of static manual mappings that require reconfiguration, the system continuously monitors and detects new or changed template relationships based on current data structures, allowing the mapping configuration to evolve dynamically with the applications.

Inventive Principle:
Principle #15Dynamics

3Productivity

If data synchronization is performed using traditional methods, then updates can be propagated, but data divergence occurs due to inconsistent data mapping across applications

Engineering Contradiction:
Improveupdate propagation speedVSAvoiddata consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system introduces template nodes as intermediaries between source and target data hierarchies. These template nodes serve as standardized mapping references that ensure consistent data propagation. By using template nodes as mediators, the system maintains reliable data consistency across applications while enabling fast update propagation, as the template relationships provide a clear mapping path without requiring complex real-time transformation logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If frequent data hierarchy changes occur due to organizational events like mergers or acquisitions, then the organization can adapt to new challenges, but data mappings become outdated and require continuous manual updates

Engineering Contradiction:
Improveorganizational flexibilityVSAvoidmapping maintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system implements dynamic template node detection that automatically adapts to organizational changes. When data hierarchies change due to mergers, acquisitions, or other organizational events, the system continuously monitors the data structures, detects new template relationships, and updates mappings automatically. This allows the organization to maintain flexibility and adapt to new challenges while eliminating the time-consuming manual maintenance of data mappings.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12353436B1Rules driven application synchronization by automatically detecting different template nodes for different synchronization targets
Publication Date: 2025.07.08 ORACLE INT CORP
  • US12353436B1 patent drawing
  • US12353436B1 patent drawing
  • US12353436B1 patent drawing

AI summary

A data management system receives updates to records of a source dimension. Some records of the source dimension reference target dimensions. The data management system identifies template records from existing records in the source dimension for modeling changes to connections with the target dimensions based on the updated records in the source dimension. The template records are discovered using rules-driven processes, AI-driven processes, or a serial or parallel hybrid processes including rules and AI. These processes use ancestor information from the updated records to find best-matching template records. The rules-driven processes additionally rely on matching fields, and the AI-driven processes additionally rely on vector embeddings and optionally clustering. Updates are made to the target records in the target dimensions, including any roll-up structures indicated for data propagation, identified using the template records, and downstream applications using the target records may consume the updates.