Content Object Integration in ERP Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing ERP systems require content objects to be separately structured, formatted, and included in a central repository, leading to inefficiencies for developers and additional shipment and installation complexities due to the need for multiple channels and distinct repository systems.
Innovation Solution
Content objects are incorporated directly into application systems, allowing for single-channel shipping and installation, with a publishing mechanism to facilitate communication between systems, supporting both central repository and point-to-point data sharing, enabling seamless data exchange without relying on a central repository.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If content objects are stored in a central repository, then data sharing between applications is enabled, but developer complexity and installation complexity increase
Solution Approach 1:
The patent extracts content objects from the central repository requirement and embeds them directly within application components. This allows applications to contain their own content objects locally, eliminating the need for separate repository storage and reducing system structural complexity while maintaining data sharing capabilities through direct application-to-application communication.
Solution Approach 2:
The patent segments the ERP system into independent application components, each with its own embedded content objects. This segmentation allows each application to be self-contained and deployable independently, reducing the complexity of centralized repository management while enabling data sharing through standardized interfaces between segmented components.
2Ease of operation
If content objects are embedded in applications, then installation complexity is reduced, but data sharing between applications may be affected
Solution Approach 1:
The patent introduces an intermediary mechanism in the form of standardized data interfaces and protocols that enable embedded content objects in different applications to communicate and share data. This intermediary layer maintains data sharing capability while allowing applications to remain self-contained with locally embedded content objects.
3Reliability
If separate shipment channels are used for applications and content objects, then repository integrity is maintained, but shipment and installation time increase
Solution Approach 1:
The patent merges content objects with their parent application components into single deployable units. This combination eliminates the need for separate shipment channels for content objects, allowing everything to be installed together in a single operation, thereby reducing installation time while maintaining system integrity through the self-contained nature of each application component.
Data Source
AI summary
Content objects may be incorporated as metadata in application systems in the same programming environment used to create the rest of the application. Although content objects may be included as part of the application systems, in some instances a central repository storing content object information from each application system may be used to facilitate communication and data sharing between applications. Alternatively, point-to-point communications between applications may also be supported so that applications may share content object data without relying on the central repository. Some embodiments may support both central repository communications and point-to-point communications between applications. Determinations may be made to identify the type of connectivity supported in different circumstances.