Cloud Master Data Management System for Automated Partner Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business process integration systems require manual configuration and customization for each trading partner, which is time-consuming and expensive, and lack efficient methods for maintaining consistency across multiple information sources.
Innovation Solution
A cloud-based Master Data Management (MDM) system that uses a multi-tenant architecture to manage and synchronize data across multiple applications, enabling automated data mapping and harmonization through a graphical user interface, allowing for real-time updates and configuration without human intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual configuration and customization is performed for each trading partner, then data integration accuracy is improved, but time consumption and cost increase
Solution Approach 1:
The patent pre-configures standard data mapping templates and integration patterns for common trading partner scenarios before actual data exchange occurs. These pre-established templates include predefined field mappings, data transformation rules, and validation schemas that can be quickly activated without manual configuration, thereby maintaining integration accuracy while dramatically reducing setup time.
Solution Approach 2:
The system creates reusable templates and patterns from successful data integration configurations. Once a trading partner integration is successfully established, its mapping rules and transformation logic are copied and adapted for similar partners, eliminating the need to manually reconfigure each partnership from scratch while preserving data accuracy through proven patterns.
2Manufacturing precision
If manual configuration and customization is performed for each trading partner, then data integration accuracy is improved, but cost increases
Solution Approach 1:
The patent implements a universal data mapping framework that handles multiple trading partner scenarios through a single configurable system. The same infrastructure and tools can be applied across different partners and data types, eliminating the need for separate custom development for each integration while maintaining accuracy through consistent, validated mapping rules.
Solution Approach 2:
The system uses parameterized configuration files and templates that can be adjusted through simple parameter changes rather than code modification. This allows the same core integration logic to serve multiple purposes with different partners by changing configuration parameters such as field names, data formats, and transformation rules, thereby reducing development and maintenance costs while preserving integration accuracy.
3Productivity
If automated data mapping is implemented, then productivity is improved, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary layer consisting of standardized data transformation templates and mapping rules that sit between the source and target systems. This intermediary framework automates the complex mapping logic while presenting a simplified interface to users, thereby improving productivity through automation without exposing the full complexity of the transformation engine to end users or system operators.
Data Source
AI summary
A source record from an enterprise is received at a registry at a master data management system at a host enterprise. The enterprise is located remotely from the host enterprise. The source record has a source identifier. A data record is generated based on the source record and the data record has a first registry identifier. The data record is stored at a data store. The registry maintains a link identifying a relationship between the registry identifier and the source identifier. A reference engine determines a value of an attribute of a field of the source record identifies a second source record, and determines whether the registry includes a second registry identifier associated with a second data record generated based on the second source record. The reference engine sets an indicator identifying the data record if the registry does not include the second registry identifier, and clears the indicator if the registry does include the second registry identifier.