Run-Type Integration Flows for Object Validation and Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating applications with different logical entities, such as PLM systems, is challenging due to structural and content differences, requiring extensive custom coding and domain knowledge, especially for object type-specific functions like validation and migration.
Innovation Solution
Implementing 'run types' that define sequences of processing steps for inbound and outbound messages, including validation, migration, and execution run types, to ensure consistent handling of object instance data across systems, using models of mappings between object types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom coding is used to implement object type-specific integration functions, then integration functionality can be achieved, but development complexity and time increase significantly
Solution Approach 1:
The patent implements a universal integration framework that handles multiple object types (material objects, BOM objects, etc.) through a common architecture. The framework provides standardized interfaces and reusable components that can be applied across different object types, eliminating the need for separate custom coding for each object type while maintaining object type-specific functionality through configuration and mapping.
2Reliability
If extensive custom coding is performed for validation and migration, then proper data handling is achieved, but development time and resource requirements increase
Solution Approach 1:
The patent implements validation and migration functionalities as pre-built components within the integration framework. These components are designed and tested in advance, allowing them to be reused across different integration scenarios. The framework includes pre-configured validation rules, data transformation templates, and migration scripts that can be applied immediately, eliminating the need for time-consuming custom development while ensuring data handling accuracy.
3Manufacturing precision
If domain knowledge is required for proper integration implementation, then integration quality improves, but accessibility and ease of implementation decrease
Solution Approach 1:
The patent introduces an integration framework that acts as an intermediary layer between different PLM systems and object types. This framework encapsulates complex domain knowledge and integration logic within its components and services, allowing users to implement integrations without requiring deep domain expertise. The framework provides abstractions that hide complexity while maintaining integration quality through standardized processes and best practices built into the framework itself.
4Adaptability or versatility
If separate handling is implemented for each object type, then object type-specific requirements are met, but system complexity increases
Solution Approach 1:
The patent segments the integration system into modular components, each responsible for specific object type handling. The framework uses object type-specific adapters, validators, and transformers that can be independently configured and maintained. This segmentation allows the system to handle different object types with their specific requirements while maintaining overall system simplicity through modular architecture, where each segment can be developed and understood in isolation.
Data Source
AI summary
Systems and methods include reception of a first object instance of a first object type from a second system and, in response to receipt of the first object instance, determination of a plurality of run types associated with the first object type, the plurality of run types including a first validation run type, a first migration run type and a first execution run type, execution of the respective plurality of tasks of the first validation run type, execution, if no errors occurred during execution of the first validation run type, of the respective plurality of tasks of the first migration run type, and execution of the respective plurality of tasks of the first execution run type to integrate the first object instance of the first object type into one or more object instances of one or more object types of the system.