Definable Action System for Business Intelligence Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing business intelligence systems face challenges in integrating heterogeneous processes, workflows, services, and data sources, requiring complex technical knowledge and making it difficult for users to interact effectively, especially in determining actions based on reports and information.

Innovation Solution

A system comprising an action manager, repository, data association manager, and implementation engine that generates and manages action definitions, allowing users to select and invoke actions based on metadata, data transformations, and conditional rules, enabling consistent and secure interaction with external targets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If complex code is written to interface with multiple systems, then system integration capability is improved, but device complexity and ease of operation deteriorate

Engineering Contradiction:
Improvesystem integration capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer (the system architecture with defined interfaces and data models) that mediates between heterogeneous source systems and target systems. This intermediary layer handles the complexity of integration internally, allowing users to interact with simple, standardized interfaces while the system manages the complex mappings and transformations behind the scenes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal integration framework that can handle multiple different source systems and target systems through a common set of interfaces and data models. This universal architecture allows the same system to integrate with various heterogeneous systems without requiring custom code for each integration scenario, thereby reducing overall complexity.

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

2Manufacturing precision

If detailed technical knowledge is required for system integration, then integration precision is improved, but ease of operation deteriorates

Engineering Contradiction:
Improveintegration precisionVSAvoiduser accessibility
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent enables self-service integration by providing users with standardized, self-describing interfaces and data models that guide the integration process. Users can configure integrations using predefined templates and metadata-driven approaches without requiring deep technical knowledge, while the system automatically handles the complex mapping and transformation logic to maintain integration precision.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-defining data models, interfaces, and integration patterns before actual system integration is needed. These pre-configured elements serve as reusable templates that users can select and customize, eliminating the need for users to understand complex integration details while ensuring precise and consistent integration outcomes.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If custom code is written for each integration scenario, then adaptability is improved, but productivity and loss of time deteriorate

Engineering Contradiction:
Improveintegration flexibilityVSAvoidintegration speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent performs preliminary action by pre-configuring integration templates, data models, and transformation rules that can be reused across multiple integration scenarios. Instead of writing custom code for each scenario, users can select from pre-built templates and customize them as needed, dramatically reducing integration time while maintaining the ability to adapt to different scenarios through configuration rather than coding.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables copying of integration patterns and configurations across different scenarios. Once an integration is configured using the standardized framework, it can be copied and reused for similar integrations, eliminating the need to rewrite code and significantly improving productivity while maintaining adaptability through parameter customization.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If integration solutions are customized for each scenario, then adaptability is improved, but ease of repair and reusability deteriorate

Engineering Contradiction:
Improvescenario-specific customizationVSAvoidsolution reusability
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

The patent segments the integration solution into modular, independently configurable components such as source system adapters, target system adapters, data models, and transformation rules. This segmentation allows each component to be developed, tested, and maintained independently, improving reusability across scenarios while maintaining adaptability through modular configuration. Problems can be isolated and repaired in individual segments without affecting the entire integration.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8543527B2Method and system for implementing definable actions
Publication Date: 2013.09.24 ORACLE INT CORP
  • US8543527B2 patent drawing
  • US8543527B2 patent drawing
  • US8543527B2 patent drawing

AI summary

A method and system is provided for use in business intelligence and reporting. The method and system are able to implement one or more definable actions when presented with data. The data may be produced by a business intelligence application. The actions may relate to activities performed by a user or an agent. The system comprises an action manager, a repository, a data association manager and an implementation engine. In one embodiment a data mining engine is provided. The system enables the availability of an action in response to the execution of analytic queries to be determined based on a relationship defined by the data association manager. If an action is available, an action definition is used to invoke a target in response to selection of the action by an entity, the invocation of the target including propagating data produced by an analytic engine into the target based on metadata to perform the action.