Composite View Materialization in Master Data Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Master Data Management (MDM) systems face challenges in combining and updating data from multiple sources efficiently, with physical MDM systems lacking source-level updating capabilities and virtual MDM systems being slow and unsuitable for omni-channel architectures.

Innovation Solution

A method and system that create a composite view by determining composite view rules to combine data from multiple sources, physically materializing the view while preserving and updating source records, allowing for efficient data management with the speed of physical MDM systems and the updating capabilities of virtual MDM systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If physical MDM systems are used to achieve fast data retrieval and consistent master data, then data access speed is improved, but source-level updating capability is lost

Engineering Contradiction:
Improvedata access speedVSAvoidsource-level updating capability
Core Design Contradiction:
SpeedVSEase of operation

Solution Approach 1:

The system segments data storage into two distinct layers: source records are preserved in their original form in source systems, while a separate entity layer is created in the MDM system that combines data from multiple sources. This segmentation allows source records to remain updateable while providing fast access to the consolidated entity view.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The entity acts as an intermediary between source records and the master data view. The entity combines data from multiple source records and presents a unified view for fast retrieval, while changes can still be propagated back to source systems through the entity layer, thus mediating between speed and update capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If virtual MDM systems are used to maintain source records intact and updatable, then source-level updating capability is improved, but data retrieval speed deteriorates

Engineering Contradiction:
Improvesource-level updating capabilityVSAvoiddata retrieval speed
Core Design Contradiction:
Ease of operationVSSpeed

Solution Approach 1:

The system performs preliminary action by pre-computing and storing the composite entity view in the MDM system. This entity consolidates data from multiple sources in advance, so when data is requested, the system can retrieve the pre-computed entity view quickly without having to compute it in real-time from source records.

Inventive Principle:
Principle #10Preliminary action

3Stability of the object's composition

If physical MDM systems collapse merge source records into entities, then data consistency is improved, but ability to undo merging deteriorates

Engineering Contradiction:
Improvedata consistencyVSAvoidability to undo merging
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system creates a copy of source record data in the entity layer rather than permanently merging and deleting source records. The entity contains the consolidated view, but source records remain intact in source systems. This copying approach allows the system to maintain data consistency through the entity while preserving the ability to access and effectively 'undo' the merging by referring back to original source records.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11822543B2Composite views in a master data management system
Publication Date: 2023.11.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11822543B2 patent drawing
  • US11822543B2 patent drawing
  • US11822543B2 patent drawing

AI summary

A computer-implemented method includes determining, by a computer device, composite view rules for combining first data from a first data record and second data from a second data record to create a composite view of an entity in a master data management system; receiving, by the computer device, the first data; receiving, by the computer device, the second data; creating, by the computer device, the composite view from the first data and the second data based on the composite view rules; physically materializing the composite view on a storage device; preserving, by the computer device, the first data record; and preserving, by the computer device, the second data record.