Cloud Master Data Management System for Automated Trading Partner Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business process integration systems require manual configuration and customization for specific trading partners, which is time-consuming and expensive, as they are typically generic software applications installed on-premise and customized locally without automated on-demand creation of customized software applications.
Innovation Solution
A cloud-based Master Data Management (MDM) system that enables automated mapping and synchronization of data across multiple applications and systems, using a multi-tenant architecture with a graphical user interface for system integration, allowing for real-time data exchange and configuration without human intervention, and providing a customizable software application creation capability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual configuration and customization is used for specific trading partners, then the system can be tailored to specific needs, but the process becomes time-consuming and expensive
Solution Approach 1:
The patent implements pre-configured templates and standardized data models that are prepared in advance for common trading partner scenarios. These templates contain pre-defined mapping rules, data structures, and integration patterns that can be quickly deployed without manual configuration, thereby reducing configuration time while maintaining adaptability through template selection and parameter customization.
Solution Approach 2:
The patent enables replication of successful trading partner configurations through template copying and cloning mechanisms. Once a trading partner integration is configured and validated, its configuration can be copied and adapted for similar trading partners, significantly reducing the time and effort required for new configurations while maintaining consistency and quality across multiple integrations.
2Adaptability or versatility
If manual configuration and customization is used for specific trading partners, then the system can be tailored to specific needs, but the cost increases
Solution Approach 1:
The patent implements a universal configuration framework with standardized data models, mapping templates, and integration patterns that can serve multiple trading partner scenarios. This multi-functional approach allows a single set of configurable components to handle diverse trading partner requirements, reducing the need for custom development and lowering implementation costs while maintaining adaptability through parameter customization.
Solution Approach 2:
The patent enables customization through parameter adjustment rather than structural modification. Trading partner-specific configurations are achieved by changing parameters within standardized templates (such as data field mappings, communication protocols, and validation rules) rather than requiring custom code development, thereby reducing implementation costs while maintaining adaptability to specific needs.
3Reliability
If generic software applications are installed on-premise, then the system is stable and secure, but automated on-demand creation of customized software applications is not available
Solution Approach 1:
The patent introduces a cloud-based configuration service as an intermediary between the on-premise trading partner integration system and the customization requirements. This intermediary service provides automated template selection, configuration generation, and validation, enabling on-demand creation of customized integrations while the actual data processing and storage remain on-premise, thereby maintaining system stability and security while adding automation capability.
Solution Approach 2:
The patent separates the configuration and customization functions from the core trading partner integration system by moving them to a cloud-based dimension. This dimensional separation allows automated on-demand customization to occur in the cloud while the on-premise system maintains its stable, secure operation, effectively adding automation capability without compromising the reliability of the core system.
Data Source
AI summary
A host enterprise includes a local data store, a data registry, and an interface process module. The data registry establishes storage of a data record at the local data store or at a data store located remotely from the host enterprise. The data registry maintains links identifying a relationship between the data record and a first source record maintained at a first source enterprise between the data record and a second source record maintained at a second source enterprise. The interface process module determines that a value at the data record has been updated and provides the updated value to the first source enterprise using an Internet protocol.