Service Context Aggregation for Dispersed IT Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional Business Service Management (BSM) tools lack the ability to provide a comprehensive view of IT service health due to data dispersion across various applications, limiting user understanding of IT service status and performance.

Innovation Solution

A method and system that utilize a partially virtual database to aggregate information from multiple applications, generating a unified business service context for display, enabling users to access and visualize the status and performance of business services across different applications through a graphical user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional BSM tools are used to monitor IT services, then each application can access its own data, but the system lacks a comprehensive view of overall service health because data is dispersed across multiple applications

Engineering Contradiction:
Improvecomprehensive view of service healthVSAvoiddata dispersion across applications
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements a service context mechanism that merges data from multiple disparate applications (email server, Help-Desk, system monitoring) into a unified contextual view. The service context aggregator collects information from different data sources and combines them into a single comprehensive service context that can be displayed together in one application interface.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The service context acts as an intermediary layer between the underlying data sources and the user interface. It mediates the access to dispersed data by creating a unified data structure that represents the overall service health, allowing applications to access comprehensive information without direct access to all underlying data sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If applications access only their own data, then data security and application independence are maintained, but users cannot access information from other applications to understand overall service status

Engineering Contradiction:
Improveuser access to service informationVSAvoidaccess to multi-application data
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent segments the data access architecture into distinct layers: individual application data sources, a service context aggregation layer, and a presentation layer. This segmentation allows each application to maintain its data independently while enabling the aggregation layer to combine这些数据 into a unified view accessible to users through controlled interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service context mechanism provides universal access to service information across different applications. A single service context can be accessed and displayed by multiple different applications (Help-Desk, monitoring tools, management consoles), allowing any application to provide a comprehensive service view without each application needing to implement its own data collection logic.

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

3Reliability

If data is collected from multiple applications, then a complete service view can be achieved, but the system complexity and data integration difficulty increase

Engineering Contradiction:
Improveaccuracy of service status informationVSAvoiddata integration architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service context mechanism is designed to be self-populating through automated data collection from registered data sources. Applications automatically publish their data to the service context aggregator, which automatically processes and stores the information. This self-service approach reduces the need for manual data integration configuration and minimizes the complexity of data collection while maintaining high reliability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8745040B2Service context
Publication Date: 2014.06.03 BMC HELIX INC
  • US8745040B2 patent drawing
  • US8745040B2 patent drawing
  • US8745040B2 patent drawing

AI summary

According to one general aspect, a method of using an application may include receiving a request, from a user, to display at least a portion of a business service context regarding a business service. The method may also include receiving, from a database, an aggregated database result regarding the business service. The aggregated database result may include the requested business service context. The business service context may include information from a plurality of other applications. The method may further include displaying a graphical user interface element that displays at least a portion of the information included by the business service context.