Enterprise Concept Dictionary Segmentation for Definition Consistency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprises face challenges in maintaining consistent concept definitions across multiple business units operating in different domains, leading to redundant and inconsistent definitions if each unit creates its own definitions independently.

Innovation Solution

A computer-implemented method and system for managing an electronic enterprise concept dictionary, which includes a master dictionary with concept entries and identifiers, and local dictionaries that link to the master dictionary for consistent definitions, ensuring that all units use a common identifier and definition for shared concepts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If each business unit creates its own concept definitions independently, then each unit can have customized definitions for its domain, but redundant and inconsistent definitions result across the enterprise

Engineering Contradiction:

Improvedomain-specific customizationVSAvoiddefinition consistency

Core Design Contradiction:

Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The system segments the enterprise concept dictionary into a master dictionary (centralized) and local dictionaries (decentralized). Each business unit maintains a local dictionary for domain-specific concepts, while the master dictionary stores enterprise-wide concepts. This segmentation allows customization at the local level while maintaining consistency at the enterprise level through the centralized master dictionary.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system merges the master dictionary and local dictionaries into a unified enterprise concept dictionary. The local dictionaries inherit from and are synchronized with the master dictionary, combining the benefits of centralized control (consistency) and decentralized customization (adaptability) into a single integrated system.

Inventive Principle:

Principle #5Merging (Combining)

2Manufacturing precision

If a centralized master dictionary is maintained for all concepts, then definition consistency is improved, but the complexity of managing and updating definitions across multiple units increases

Engineering Contradiction:

Improvedefinition consistencyVSAvoiddictionary management complexity

Core Design Contradiction:

Manufacturing precisionVSDevice complexity

Solution Approach 1:

The system divides the management responsibility into two segments: the master dictionary is managed centrally for enterprise-wide concepts, while local dictionaries are managed independently by each business unit for domain-specific concepts. This segmentation reduces the complexity of centralized management by allowing autonomous local management where appropriate.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system establishes the master dictionary structure and concept definitions in advance, before local dictionaries are created. This preliminary action provides a ready-made framework that local dictionaries can inherit from, reducing the complexity of creating and maintaining definitions from scratch at each local level.

Inventive Principle:

Principle #10Preliminary action

3Ease of manufacture

If local dictionaries are created without linking to the master dictionary, then local customization is easier, but redundancy and inconsistency increase across the enterprise

Engineering Contradiction:

Improvelocal dictionary creation easeVSAvoiddefinition redundancy

Core Design Contradiction:

Ease of manufactureVSLoss of information

Solution Approach 1:

The master dictionary serves multiple functions: it stores enterprise-wide concepts, provides a template for local dictionaries, and acts as a reference for consistency. Local dictionaries can be created easily by inheriting from the master dictionary, while the master dictionary prevents redundancy through centralized concept management.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Local dictionaries are created by copying the structure and concepts from the master dictionary. This copying mechanism allows easy local customization while maintaining consistency with the enterprise-wide standards defined in the master dictionary, preventing redundancy through systematic inheritance.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS9442915B2Semantic application logging and analytics

Publication Date: 2016.09.13 BANK OF AMERICA CORP

AI summary

A system for managing dictionaries, such as an application dictionary and a domain dictionary, and for adding entries to a data log is described herein. The system may, in response to a determination that an event occurs at an application, determine that the application uses a first concept name from the application dictionary to describe the event. An entry for the event may be added to a data log for the application. The entry may also include the first concept name from the application dictionary. A mapping of the first concept name from the application dictionary to a second concept name from the domain dictionary may be generated. In some aspects, the data log may be sent to a data log analysis system capable of accessing the domain dictionary.