Data Uniformity Framework for Cross-System Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex organizational system landscapes, archiving and deletion of personal or sensitive data across multiple connected software systems are typically performed individually, leading to software systems being out of sync, introducing errors, and requiring time-consuming syncing efforts, which complicates compliance with regulations like GDPR.

Innovation Solution

A data uniformity framework module that captures and logs key information about data processing actions in a primary system, allowing connected systems to access and replicate these actions, ensuring data is handled uniformly and reducing the need for redundant efforts in compliance with regulations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If archiving and deletion actions are performed individually in each connected system, then each system can independently manage its data, but the systems become out of sync and require time-consuming syncing efforts

Engineering Contradiction:
ImproveIndependent data management capabilityVSAvoidTime for syncing systems
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent introduces a notification log as an intermediary component that centralizes archiving and deletion actions. When data is archived or deleted in one system, the action is logged in the notification log, which then notifies other connected systems. This mediator approach eliminates the need for manual syncing while maintaining independent data management, as systems automatically receive and process notifications about data changes in other systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If archiving and deletion actions are performed individually in each connected system, then each system has full control over its data processing, but errors are introduced by executing actions multiple times

Engineering Contradiction:
ImproveSystem autonomy in data processingVSAvoidData consistency across systems
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The notification log implements a feedback mechanism where systems report their data processing actions to a centralized log, which then provides feedback notifications to other systems. This feedback loop ensures that when one system archives or deletes data, other systems receive notification and can update their records accordingly, preventing duplicate actions and maintaining data consistency while preserving system autonomy.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If manual syncing of all connected software systems is performed, then data uniformity can be achieved, but the process becomes time-consuming and complex

Engineering Contradiction:
ImproveData uniformity across systemsVSAvoidComplexity of syncing process
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The notification log performs preliminary actions by pre-processing and logging all archiving and deletion actions in a centralized manner before they need to be propagated to other systems. This preliminary logging and notification mechanism eliminates the need for complex manual syncing processes, as systems automatically receive pre-processed notifications about data changes, ensuring data uniformity with minimal complexity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11455294B2Information lifecycle management notification framework
Publication Date: 2022.09.27 SAP SE
  • US11455294B2 patent drawing
  • US11455294B2 patent drawing
  • US11455294B2 patent drawing

AI summary

According to some embodiments, systems and methods are provided, comprising a data uniformity framework module; a data uniformity framework processor in communication with the data uniformity framework module and operative to execute processor-executable process steps to cause the system to: receive an indication that an action event was executed at a primary application; extract one or one or more key data elements affected by the execution of the action event; log the extracted one or more key data elements in a notification log; receive a request from a secondary application for the logged data; transmit the logged data to the secondary application; and manipulate secondary application data that corresponds to the logged data to replace the secondary application data with the logged data. Numerous other aspects are provided.