Federated Database Aggregating Business Service Context

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional Business Service Management (BSM) tools fail to provide a comprehensive view of the status or health of IT systems due to data dispersion across various applications, limiting user understanding as they can only access data specific to their application.

Innovation Solution

A method and system that enables a mobile computing device to request and display an aggregated business service context from a database, incorporating information from multiple applications, using a federated database to aggregate data and present a unified view of business service performance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional BSM tools are used to manage IT services, then each application can access its own data, but the user cannot obtain a comprehensive view of the business service status because data is dispersed across multiple applications

Engineering Contradiction:
Improvecomprehensive view of business service statusVSAvoiddata dispersion across multiple applications
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a federated database that consolidates data from multiple independent applications (email server, Help-Desk, system resource monitoring) into a unified structure. This allows the mobile device to retrieve comprehensive business service context in a single query, eliminating information loss while maintaining the independence of source applications.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The federated database acts as an intermediary layer between the mobile device and multiple source applications. It aggregates data from diverse applications without requiring changes to the applications themselves, providing a unified view while preserving the existing application architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a mobile device requests business service context from a federated database, then the user receives aggregated information from multiple applications, but the data retrieval and aggregation process becomes more complex

Engineering Contradiction:
Improveaccess to unified business service informationVSAvoidfederated database aggregation mechanism
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the data aggregation complexity from the mobile device and relocates it to the federated database server. The mobile device only needs to send simple context requests and receive aggregated results, while the complex aggregation logic resides on the server side where it belongs.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If traditional BSM applications are used, then the system maintains simple data access patterns, but the user productivity is reduced due to limited visibility of business service health

Engineering Contradiction:
Improveuser productivity in incident managementVSAvoidvisibility of business service health
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent adds a new dimension to data access by enabling mobile devices to query the federated database. This creates a new information channel that delivers comprehensive business service context to users anywhere in the organization, not just at traditional desktop locations, thereby improving productivity through better visibility.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS9412084B2Service context
Publication Date: 2016.08.09 BMC HELIX INC
  • US9412084B2 patent drawing
  • US9412084B2 patent drawing
  • US9412084B2 patent drawing

AI summary

According to one general aspect, a method may include displaying a user interface associated with the application. The user interface may provide a selection of a business service that is implemented within an Information Technology (IT) environment by at least one server and at least one business application executing on the at least one server. The method may include requesting a service status for the business service based on the selection, and receiving a database result regarding the business service from a database server. The database result may include performance information associated with the business service. The method may include displaying the service status as a user interface element viewable within the user interface of the application. The service status may provide the performance information that has been received within the database result.