Unified Metadata Repository for Search and Analytics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for business data management require separate tools for operational and analytical modalities, leading to inefficiencies in search, query, reporting, and analytics, as they lack a unified metadata model to facilitate model-based operations across these domains.
Innovation Solution
The introduction of a metadata repository architecture that includes business object view and multi-dimensional analytical view metadata models, allowing for model-based access and reuse across search, query, reporting, and analytics, eliminating the need for separate abstraction layers and enabling integration of various metadata models through a common meta-metadata model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If separate tools are used for operational and analytical modalities, then each modality can be optimized independently, but the system complexity increases and efficiency decreases due to lack of integration
Solution Approach 1:
The patent merges operational and analytical modalities into a single unified system that uses a common metadata model for both transactional operations and analytical operations. This eliminates the need for separate tools and abstraction layers, reducing system complexity while improving efficiency through integrated access to business objects.
Solution Approach 2:
The unified metadata model serves multiple functions simultaneously - it supports both operational modality (transactional operations on business objects) and analytical modality (search, query, reporting, and analytics). This multi-functionality eliminates the need for separate specialized tools while maintaining optimization for both modalities.
2Ease of manufacture
If separate abstraction layers are used for operational and analytical modalities, then each modality can be independently optimized, but the development complexity and time increase
Solution Approach 1:
The patent combines the operational and analytical abstraction layers into a single unified metadata model that both modalities can access directly. This eliminates the need to develop and maintain separate abstraction layers, reducing development complexity and accelerating the creation of queries and reports.
Solution Approach 2:
The unified metadata model provides universal access for both operational and analytical operations, serving as a single interface for developing queries, reports, and analytics. This eliminates the need for separate development processes and tools, improving ease of manufacture while reducing time loss.
3Reliability
If multiple specialized tools are used for different business modalities, then each tool can be optimized for its specific purpose, but the overall system efficiency decreases due to integration overhead
Solution Approach 1:
The patent merges operational and analytical operations into a single system using a unified metadata model, eliminating integration overhead between separate tools. This maintains reliability through consistent data access while improving overall system efficiency by removing the performance penalties associated with tool integration.
Data Source
AI summary
A system includes first metadata defining a business object object model, and second metadata defining a first object model to define a query on the business object object model. The first object model is an instance of a business object view metadata model, and the business object object model is an instance of a business object metadata model. In some aspects, a request is received to retrieve a result element associated with a query on a business object, the business object comprising an instance of a business object object model, and the business object is instantiated based on first metadata defining the business object object model. An instance of a business object view object model is instantiated based on second metadata defining the business object view object model, the instance of the business object view object model defining the query on the business object.