Cascading Data Impact Visualization for Cloud Lineage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating to cloud computing environments complicates tracking data flow across multiple linked data resources, making it challenging to assess and manage the impact of data changes, which can lead to unnecessary downtime and resource loss due to unanticipated failures in downstream data resources.

Innovation Solution

A cascading data impact visualization tool that consolidates data lineage documents to provide a graphical view of interrelationships between data resources, allowing users to identify and communicate the impact of changes, ensuring informed decision-making and efficient updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data resources are migrated to cloud computing environments with multiple linked data resources, then computing resources and flexibility are improved, but tracking data flow and assessing impact of data changes becomes more difficult

Engineering Contradiction:
Improvecloud computing flexibilityVSAvoiddata flow tracking difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces a data lineage document as an intermediary mechanism that captures and stores information about data flow relationships between cloud resources. This mediator enables users to track data flow paths and assess impact without needing to directly monitor complex inter-resource connections, thus resolving the contradiction between cloud flexibility and data flow tracking difficulty

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system creates a virtual copy of the data flow relationships through data lineage documents, which replicate the actual data flow paths in a manageable format. This copying approach allows users to analyze and visualize data relationships without interfering with the actual cloud infrastructure, solving the tracking difficulty while preserving cloud adaptability

Inventive Principle:
Principle #26Copying

2Productivity

If data changes are implemented without impact analysis, then development speed is improved, but downstream data resource failures increase causing downtime and resource loss

Engineering Contradiction:
Improvedevelopment speedVSAvoiddownstream data resource reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary impact analysis by querying data lineage documents before data changes are applied. This advance action identifies all downstream resources that would be affected by a proposed change, allowing developers to plan and coordinate updates proactively, thus preventing failures while maintaining development speed

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback about the impact of data changes by retrieving and analyzing data lineage information that shows which downstream resources depend on the changed data. This feedback mechanism enables developers to adjust their changes based on identified impacts, ensuring reliability without sacrificing productivity

Inventive Principle:
Principle #23Feedback

3Measurement precision

If comprehensive data flow tracking is implemented across all data resources, then impact assessment accuracy is improved, but system complexity and time required for analysis increase

Engineering Contradiction:
Improveimpact assessment accuracyVSAvoiddata flow tracking system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts only the essential data flow relationship information from the complex cloud infrastructure and stores it in simplified data lineage documents. This extraction approach retains the accuracy needed for impact assessment while removing unnecessary complexity, allowing precise analysis without overwhelming system complexity

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments the comprehensive data flow tracking into discrete data lineage documents that can be individually queried and analyzed. This segmentation allows the system to maintain high measurement precision for impact assessment while reducing overall system complexity by organizing information into manageable, isolated units

Inventive Principle:
Principle #1Segmentation

4Ease of operation

If data lineage information is consolidated and visualized, then communication of impact to stakeholders is improved, but processing time and computational resources increase

Engineering Contradiction:
Improveimpact communication efficiencyVSAvoidprocessing time for impact analysis
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent performs preliminary consolidation of data lineage information from multiple sources into unified documents before impact analysis is needed. This advance preparation reduces processing time during actual impact assessment by having the data ready in an optimized format, thus improving communication efficiency without significant time loss

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system merges scattered data flow information from multiple cloud resources into consolidated data lineage documents. This combining approach improves ease of operation by providing a unified view of impacts while managing processing time through efficient aggregation methods that prevent redundant computations

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12118016B2Cascading data impact visualization tool
Publication Date: 2024.10.15 CAPITAL ONE SERVICES LLC
  • US12118016B2 patent drawing
  • US12118016B2 patent drawing
  • US12118016B2 patent drawing

AI summary

Methods and systems described herein may retrieve a data lineage associated with a first computing system comprising a plurality of services and data elements. The data lineage may indicate a plurality of interrelationships between the plurality of services and data elements. Based on the data lineage, a visualization of the first computing system may be generated. Based on the one or more interrelationships between a first data element and the plurality of services and data elements, one or more services and data elements affected by the change to the first data element may be identified. Based on the one or more services and data elements affected by the change to the first data element, the visualization of the first computing system to indicate the impact to the first computing system.