Operational Information Provider for ESOA Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex Enterprise Service Oriented Architecture (ESOA) systems, managing and accessing operational data from multiple, disparate locations with different formats and interfaces is challenging, leading to increased complexity and inefficiency in developing reporting applications.

Innovation Solution

Implementing operational information providers that offer a standardized interface for optimized data and metadata retrieval, allowing front-end applications to access real-time operational data from back-end units through consumer services and metadata-based descriptions, transforming data formats and providing unified access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If individual applications access operational data from multiple disparate locations with different formats and interfaces, then each application can retrieve the data it needs, but the system complexity increases and management becomes difficult

Engineering Contradiction:
Improvedata access flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an operational information provider as an intermediary layer between applications and operational data. This provider implements a standardized interface that applications use to access operational data, eliminating the need for applications to directly interact with multiple disparate data sources. The intermediary translates standardized application requests into appropriate data retrieval operations, thereby reducing system complexity while maintaining data access flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The operational information provider implements a universal standardized interface that can access multiple types of operational data from different sources through a single unified access point. This universal interface handles various data formats and retrieval methods internally, allowing applications to access diverse operational data without needing to know the specific details of each data source, thus reducing complexity while maintaining versatility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If applications recalculate operational data individually, then each application ensures data accuracy, but redundant calculations increase processing time and reduce efficiency

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The operational information provider performs preliminary data retrieval and validation operations centrally before distributing data to applications. By pre-fetching and validating operational data at the provider level, the system ensures data accuracy is maintained while avoiding redundant calculations in each application. The provider prepares data in advance according to standardized formats, reducing processing time for individual applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple data retrieval and calculation operations into a single centralized operational information provider. Instead of each application independently retrieving and calculating operational data, the provider consolidates these operations, performing them once and serving multiple applications. This merging maintains data accuracy through centralized control while significantly improving processing efficiency by eliminating redundant calculations.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of manufacture

If operational data is stored in a data warehouse, then static data can be accessed directly, but operational information that changes constantly cannot be stored and must be obtained through business processes

Engineering Contradiction:
Improvedata access simplicityVSAvoiddata type coverage
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The operational information provider implements a universal access mechanism that handles both static data warehouse data and dynamic operational data through a single interface. For static data, the provider retrieves from the data warehouse directly; for dynamic operational data, the provider obtains from business processes. This universal approach maintains ease of access for both data types while expanding the scope of data coverage to include both static and operational information.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The provider acts as an intermediary that transparently handles different data source types. Applications interact with the provider using the same standardized interface regardless of whether the data comes from the data warehouse or business processes. The intermediary manages the complexity of determining data freshness, retrieval methods, and format transformations, thereby maintaining access simplicity while covering diverse data types.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8549035B2Operational information providers
Publication Date: 2013.10.01 SAP SE
  • US8549035B2 patent drawing
  • US8549035B2 patent drawing
  • US8549035B2 patent drawing

AI summary

In a computer program product, system and method for retrieving operational data, a front-end unit generates a query for operational data. In an embodiment, in response to the generation of the query, an operational information provider is sent to a back-end unit to retrieve real-time operational data from the back-end unit using a retrieval method specified in the operational information provider. The retrieved operational data, including the real-time operational data is received by the front-end unit from the back-end unit.