Dynamic Report Mapping for IT Service Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data processing systems face challenges in report definition reusability and migration due to embedded database connection information, requiring manual updates and redeployment when database schemas change, and necessitating core reporting team involvement for new views.

Innovation Solution

A computer-implemented method for dynamically creating report mapping relationships at runtime, using a generalized report definition without database-specific properties to abstract data connections, allowing for dynamic data acquisition and report generation without manual code updates or redeployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If database connection information and schema are embedded in report definitions, then report generation is straightforward, but report definition reusability deteriorates when database schema changes

Engineering Contradiction:

Improvereport generation simplicityVSAvoidreport definition reusability

Core Design Contradiction:

Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The system segments the reporting architecture into distinct layers: report definitions (presentational layer), mapping relationships (translation layer), and database schemas (data layer). This segmentation allows report definitions to remain unchanged while adapting to database schema changes through dynamic mapping updates.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces mapping relationships as an intermediary layer between report definitions and database schemas. This mediator dynamically translates generalized data source descriptions into database-specific queries, enabling report definitions to remain reusable while adapting to different database schemas without direct embedding.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If mapping relationships are statically defined in back-end code, then data retrieval connections are stable, but system flexibility deteriorates when schema changes occur

Engineering Contradiction:

Improvedata retrieval stabilityVSAvoidsystem flexibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent transforms static mapping relationships defined in back-end code into dynamic mapping relationships that are created and updated at runtime. This allows the system to maintain stable data retrieval while adapting flexibly to schema changes without requiring code modifications or redeployment.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system enables self-service for mapping updates by allowing runtime creation and modification of mapping relationships without requiring core reporting team involvement. Developers can independently update mappings to reflect schema changes, maintaining reliability while improving adaptability.

Inventive Principle:

Principle #25Self-service

3Measurement precision

If report definitions contain database-specific properties, then data access is precise, but portability deteriorates across different reporting products

Engineering Contradiction:

Improvedata access precisionVSAvoidreport definition portability

Core Design Contradiction:

Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent creates universal report definitions using a standardized schema (e.g., XML-based format) that can port across different reporting products and database systems. The mapping relationships serve as adapters that maintain precise data access while enabling the same report definition to work with different databases and reporting tools.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Ease of operation

If manual updates are required for schema changes, then control over reporting is maintained, but productivity deteriorates due to redeployment requirements

Engineering Contradiction:

Improvereporting controlVSAvoidreport update efficiency

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The system enables automated self-service for handling schema changes. When the database schema changes, the mapping relationships can be dynamically updated at runtime without requiring manual code updates or system redeployment, maintaining operational control while dramatically improving update efficiency.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS8712965B2Dynamic report mapping apparatus to physical data source when creating report definitions for information technology service management reporting for peruse of report definition transparency and reuse

Publication Date: 2014.04.29 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A computer implemented method, data processing system, and computer program product for dynamically creating report mapping relationships at runtime within an information technology infrastructure. When report definition comprising a generalized description of desired data without any database-specific properties is generated, a relationship mapping definition based on the generalized description in the report definition is created, wherein the relationship mapping definition comprises data connection information for accessing the data sources containing the desired data. The relationship mapping definition is then used to initiate a connection to the data sources. Once the desired data has been acquired from the data sources, a report may then be created using the acquired data.