Asset Management Catalog Integration for Data Structure Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current asset management systems struggle with integrating structural and semantic information into a unified catalog, leading to inconsistencies and difficulties in managing and querying data across disparate storage assets.

Innovation Solution

The system determines structure data from schema data applicable to data stored in a data storage asset, generates data entries based on this structure data, and integrates them into an asset management catalog, along with associating them with the underlying data. Additionally, semantic metadata is determined and integrated into the catalog using terms and annotations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data structures are designed and governed independently for each storage asset, then each group or sub entity can manage its own data structure, but the data structures become inconsistent across different storage assets and are difficult to query uniformly

Engineering Contradiction:
Improveindependent data structure managementVSAvoiddata structure consistency
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by creating a unified asset management catalog that serves multiple storage assets with different data structures. The catalog uses standardized labels and metadata schemas that can represent data from various sources uniformly, allowing a single system to handle diverse data structures without requiring separate management approaches for each asset.

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

Solution Approach 2:

The asset management catalog acts as an intermediary layer between disparate storage assets and query interfaces. It translates various data structures into a common representation through standardized labels and metadata, enabling uniform querying without requiring changes to the underlying storage assets or their independent data structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If labels in the asset management catalog are predefined or simple names, then the catalog implementation is simple, but the labels lack self-defining meaning and require external information to be understood

Engineering Contradiction:
Improvecatalog implementation simplicityVSAvoidlabel semantics
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent applies the nested doll principle by creating hierarchical metadata structures where labels are nested within broader contexts. Labels are not standalone simple names but are embedded within metadata schemas, ontologies, and classification hierarchies that provide their meaning. This allows labels to remain simple for catalog implementation while gaining rich semantic meaning through their nested context.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent applies preliminary action by pre-defining metadata schemas, ontologies, and label hierarchies before catalog implementation. These preliminary structures establish the semantic framework that gives meaning to labels, so that when labels are created, their meaning is already determined by their position within the pre-established metadata framework rather than requiring external interpretation.

Inventive Principle:
Principle #10Preliminary action

3Duration of action of moving object

If data structures evolve and change independently in different storage assets, then each asset can adapt to its specific needs, but querying and managing data across assets becomes increasingly difficult

Engineering Contradiction:
Improvedata structure evolution capabilityVSAvoidcross-asset data querying
Core Design Contradiction:
Duration of action of moving objectVSEase of operation

Solution Approach 1:

The patent applies dynamics by creating a flexible metadata framework that can adapt to evolving data structures. The asset management catalog uses dynamic label schemas and metadata models that can accommodate changes in data structures without requiring rigid predefined formats. This allows storage assets to evolve their data structures independently while the catalog dynamically adjusts to represent the new structures through updated metadata.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If similar information is stored in different storage assets with differing data structures and access mechanisms, then each asset can optimize for its specific use case, but unified management and access become complex

Engineering Contradiction:
Improveasset-specific optimizationVSAvoidunified management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing the asset management catalog to handle multiple types of storage assets with different data structures and access mechanisms through a single unified interface. The standardized labels and metadata schemas can represent similar information from diverse sources uniformly, allowing the system to manage assets specifically optimized for their use cases while providing unified access through the common catalog framework.

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

Data Source

PatentUS12204501B2Integration of structural information into an asset management catalog
Publication Date: 2025.01.21 DELL PROD LP
  • US12204501B2 patent drawing
  • US12204501B2 patent drawing
  • US12204501B2 patent drawing

AI summary

Integration of structural information into an asset management catalog (e.g., using a computerized tool), is enabled. For example, a system can comprise a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising: based on schema data applicable to data stored in a data storage asset, determining structure data representative of a structure of the data stored in the data storage asset, in response to determining the structure data, generating a data entry, applicable to the structure data, to be added to an asset management catalog associated with the data storage asset, and in response to generating the data entry, associating the data entry with the data stored in the data storage asset.