Database Integration Mechanism for Enterprise System Consolidation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprises face challenges in integrating databases from different management systems due to varying data and process types, parameters, APIs, and access authorities, leading to increased storage and management resources needed for multiple systems.

Innovation Solution

An integration mechanism that compares artifacts between databases using semantic analysis, modifies APIs and processes based on access authorities, and integrates process roles to create a unified database access point, reducing complexity and resource requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple independent management systems are adopted for different operation purposes, then the functionality and versatility of the enterprise system is improved, but the storage resources and management resources required increase significantly

Engineering Contradiction:
ImprovefunctionalityVSAvoidstorage resources
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple independent database systems into a unified database system. Different management systems (document management, income and expenditure management, working hour management, patent management) that previously maintained separate databases are integrated into a single database, eliminating data redundancy and reducing storage resources while preserving all functional capabilities.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified database system is designed to serve multiple management functions simultaneously. A single database structure supports various management systems through standardized interfaces and processes, allowing one system to perform multiple functions that previously required separate specialized systems.

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

2Adaptability or versatility

If multiple independent management systems are adopted for different operation purposes, then the functionality and versatility of the enterprise system is improved, but the management resources required increase significantly

Engineering Contradiction:
ImprovefunctionalityVSAvoidmanagement resources
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines multiple independent management systems into a unified system with shared database, processes, and interfaces. This merging reduces the complexity of managing multiple separate systems while maintaining all necessary functional capabilities through integration.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements homogeneous data structures, standardized interfaces, and unified processes across previously disparate management systems. By making the system components consistent and uniform, the complexity of managing diverse systems is reduced while preserving functional versatility.

Inventive Principle:
Principle #33Homogeneity

3Quantity of substance

If databases of different management systems are integrated to access the same database, then storage resources and management resources are reduced, but the complexity of integrating different data types, parameters, APIs, and access authorities increases

Engineering Contradiction:
Improvestorage resourcesVSAvoidintegration complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent performs preliminary actions by pre-defining standardized data structures, uniform interfaces, and standardized processes before integration. Artifact templates and process role templates are established in advance, which simplifies the actual integration process by providing a common framework that all systems must follow.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces intermediary elements such as artifact templates, process role templates, and standardized interfaces that mediate between different data types, parameters, and access authorities. These intermediaries translate and harmonize differences between systems, reducing integration complexity while enabling resource consolidation.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Quantity of substance

If databases of different management systems are integrated to access the same database, then storage resources and management resources are reduced, but the complexity of modifying APIs and processes according to different access authorities increases

Engineering Contradiction:
Improvestorage resourcesVSAvoidAPI and process modification complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent applies local quality by allowing different access authorities and process configurations for different users and systems within the unified database. Each process role and user account can have customized access permissions and interface configurations tailored to their specific needs, while still operating within the unified system framework.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent performs preliminary configuration of access authorities, process roles, and artifact templates before actual data integration. By pre-establishing the access control framework and standardized interfaces, the complexity of modifying APIs and processes during integration is significantly reduced.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10133769B2Integration device and integration method thereof
Publication Date: 2018.11.20 INSTITUTE FOR INFORMATION INDUSTRY
  • US10133769B2 patent drawing
  • US10133769B2 patent drawing
  • US10133769B2 patent drawing

AI summary

An integration device and an integration method thereof are provided. The integration device executes an artifact integration procedure to integrate the artifacts in a first database and the artifacts in the second database. Based on the access authority of each process role in the first database and the access authority of each process role added from the second database into the first database, the integration device further modifies a plurality of application programming interfaces associated with the integrated artifacts and modifies a plurality of processes according to the modified application programming interfaces. In addition, the integration device further executes a process role integration procedure to integrate the process roles of the first database and the process roles added from the second database into the first database.