Master Reference Data Set Identifier Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data integration systems face challenges in reconciling and managing a unified view of data entities across multiple applications and data sources, often requiring significant changes to existing systems and processes, which can be costly and disruptive, and may lead to data loss or resistance from business users due to the need for standardized identifiers.

Innovation Solution

A user interface allows users to specify attributes for a master reference data set and identify enterprise-specific identifiers (ESIDs) that can be used to access and update data in an enterprise data storage, maintaining both current and historical values of these identifiers to enable flexible data management and integration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single unifying identifier is standardized across all source systems, then data integration and sharing is achieved, but significant changes to existing systems and business processes are required

Engineering Contradiction:

Improvedata integrationVSAvoidsystem changes

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (data integration system) that sits between the legacy systems and the unified data view. This intermediary handles the complexity of mapping multiple legacy identifiers to a unified identifier without requiring changes to the legacy systems themselves, thus achieving data integration while minimizing system disruption

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the identifier management function into separate components: legacy identifier preservation in source systems, intermediary mapping in the integration system, and unified identifier presentation in the data mart. This segmentation allows each layer to operate independently with its own identifier scheme

Inventive Principle:

Principle #1Segmentation

2Reliability

If pervasive changes are made across the enterprise to implement standardized identifiers, then data standardization is achieved, but data loss may occur in legacy data silos

Engineering Contradiction:

Improvedata standardizationVSAvoiddata loss

Core Design Contradiction:

ReliabilityVSLoss of substance

Solution Approach 1:

The patent performs preliminary actions by extracting and preserving legacy identifier values before any potential loss occurs. The system captures the original legacy identifiers and stores them in the data mart alongside the unified identifier, ensuring that historical data remains accessible even as systems evolve

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent creates copies of legacy data and identifiers in the data mart environment. These copies preserve the original legacy identifier values while allowing the source systems to undergo standardization changes, thus preventing data loss through replication rather than modification

Inventive Principle:

Principle #26Copying

3Reliability

If a unified identifier is imposed on business users, then data integration is achieved, but user resistance increases due to unfamiliarity with the identifier

Engineering Contradiction:

Improvedata integrationVSAvoiduser acceptance

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent applies local quality by allowing different identifier types in different contexts: business users continue to interact with familiar legacy identifiers in their local applications, while the unified identifier is used only in the integrated data mart environment where it provides analytical value without disrupting local workflows

Inventive Principle:

Principle #3Local quality

4Reliability

If extensive customization and coding are performed across applications to support standardized identifiers, then data model standardization is achieved, but development time and cost increase

Engineering Contradiction:

Improvedata model standardizationVSAvoidcustomization time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent positions the data integration system as an intermediary that handles all customization and mapping logic centrally, eliminating the need for extensive coding in each application. The intermediary layer absorbs the development effort through configuration rather than customization, significantly reducing implementation time

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS8271477B2Methods and systems for accessing data

Publication Date: 2012.09.18 INFORMATICA CORP

AI summary

Some embodiments of the invention provide a user interface that allows a user to specify one or more attributes that should be included in a master reference data set, and identify which of these attributes should serve as enterprise specified identifiers that can be used to identify the particular master reference data set in an enterprise data storage. Some embodiments of the invention provide a method that allows the master reference data set to be accessed and updated in the data storage through the use of the enterprise specified identifiers.