Knowledge Management for Data Lineage Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies lack effective tools for identifying and managing potential issues associated with changes to applications and server configurations, leading to unreliable monitoring and potential performance or security issues due to misalignments in data lineage.

Innovation Solution

A knowledge management system that tracks the lineage of application code and server configurations, using predefined data lineage criteria to detect misalignments and prevent changes until approved by an administrator, while updating criteria based on historical data for improved analytics and insights.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a knowledge management system with data lineage tracking is implemented, then reliability of change management is improved, but device complexity increases

Engineering Contradiction:
Improvereliability of change managementVSAvoidcomplexity of monitoring system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary validation of requested changes against stored data lineage criteria before implementation. The processor compares the requested change against predefined ranges of values for server and application configuration data, identifying potential misalignments before they cause problems. This proactive approach improves reliability by preventing erroneous changes while the automated preliminary checking manages complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system provides feedback to administrators through alerts that include indications of detected misalignments and requests for confirmation. This feedback loop allows the system to automatically monitor changes while involving human judgment only when misalignments are detected, improving reliability through automated monitoring and managing complexity by reducing manual review needs.

Inventive Principle:
Principle #23Feedback

2Productivity

If automated misalignment detection is implemented, then productivity of change management is improved, but device complexity increases

Engineering Contradiction:
Improveproductivity of change managementVSAvoidcomplexity of knowledge management system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system performs self-service by automatically monitoring its own data lineage and detecting misalignments in requested changes without requiring manual intervention for each change. The processor autonomously compares changes against stored criteria and generates alerts when misalignments are detected, improving productivity by eliminating manual monitoring while managing complexity through automated self-validation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary automated validation of requested changes against data lineage criteria before implementation. This automated preliminary checking improves productivity by quickly identifying potential issues that would otherwise require manual review, while the systematic approach to automated validation manages the complexity of the monitoring process.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If data lineage criteria are maintained and updated, then measurement precision of change validation is improved, but loss of time for maintenance increases

Engineering Contradiction:
Improveprecision of change validationVSAvoidtime for criteria maintenance
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system maintains precise data lineage criteria through automated feedback loops that track actual configurations and update criteria accordingly. The system monitors implemented changes and uses this feedback to refine and update the stored data lineage criteria, improving measurement precision for future validations while automating the maintenance process to reduce time investment.

Inventive Principle:
Principle #23Feedback

4Reliability

If comprehensive monitoring of changes is implemented, then reliability is improved, but loss of time for administration increases

Engineering Contradiction:
Improvereliability of system configurationVSAvoidtime for administrator review
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements comprehensive automated monitoring of all changes against data lineage criteria, but only requires administrator time when misalignments are detected. The processor automatically validates routine changes without human intervention, improving reliability through continuous monitoring while reducing administrator time investment by involving humans only when necessary to resolve detected issues.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11349957B2Automatic knowledge management for data lineage tracking
Publication Date: 2022.05.31 BANK OF AMERICA CORP
  • US11349957B2 patent drawing
  • US11349957B2 patent drawing
  • US11349957B2 patent drawing

AI summary

A memory record of a knowledge management tool stores data lineage criteria. A processor of the knowledge management tool receives a request to change one or more of a configuration of a server, a code of a hosted application, and a configuration of the hosted application. The processor determines whether a misalignment is detected associated with the requested change being outside at least one of the predefined ranges of values for server configuration data and application configuration data of the data lineage criteria. If the misalignment is not detected, the requested change is allowed to be implemented in one or both of the server and the hosted application. If the misalignment is detected, an alert is provided to an administrator device. If a response to the alert indicates to implement the requested change, implementation of the requested change is allowed. Otherwise, implementation of the requested change is prevented.