Dynamic Contextual Pivot Grid Analytics for Enterprise Reporting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for generating and customizing analytic reports in enterprise environments are slow, costly, and lack flexibility, requiring specialized technical knowledge and often fail to implement uniform security features, leading to inconsistent data security and control.

Innovation Solution

A method that allows end users to create, customize, and configure analytic reports by receiving configuration information to generate database queries, construct analytic templates, and publish them for access, incorporating context information like user roles and security settings to ensure secure and timely data retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional developer-created reports are used, then data security policies can be implemented, but the system lacks flexibility and requires specialized technical knowledge

Engineering Contradiction:
Improvereport customization flexibilityVSAvoidtechnical knowledge requirement
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a report template system as an intermediary between developers and end users. Pre-configured templates with embedded security policies serve as the mediator, allowing users to generate secure reports without needing to understand the underlying complexity. The template engine automatically applies security rules based on user roles and context information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables end users to create and customize their own reports through a user-friendly interface without requiring developer intervention. Users can select from pre-configured templates, modify parameters, and generate reports independently. The system automatically handles security policy application, query generation, and report distribution based on user selections and context information.

Inventive Principle:
Principle #25Self-service

2Reliability

If custom reports are created by developers, then security features can be implemented, but the report-creation process is slow and costly

Engineering Contradiction:
Improvedata security consistencyVSAvoidreport creation speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Security policies, query structures, and report templates are pre-configured by developers before deployment. These templates contain embedded security rules, data source connections, and formatting specifications. When users generate reports, they simply select from these pre-prepared templates and provide specific parameters, eliminating the need for developers to create each report from scratch while maintaining security consistency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system allows users to customize reports by changing parameters within pre-configured templates. Users can modify date ranges, filters, groupings, and other report parameters without altering the underlying security structure or query logic. This enables rapid report generation with different data slices while maintaining consistent security policies across all reports.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If developers create reports, then specialized skills are utilized, but administrators lack awareness of sought report features

Engineering Contradiction:
Improvereport feature accuracyVSAvoiduser requirements understanding
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The system incorporates feedback mechanisms where users can provide input about their reporting needs through the interface. The system responds by presenting relevant templates and customization options based on user selections and context information. This iterative feedback loop ensures that generated reports accurately reflect user requirements while maintaining security policies, eliminating the communication gap between administrators and developers.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If disparate analytic reports are created by different developers, then various report features can be achieved, but uniform security features are not implemented

Engineering Contradiction:
Improvereport feature varietyVSAvoidsecurity policy uniformity
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent implements a universal template system where all reports are generated from a common set of pre-configured templates that embed consistent security policies. These multi-functional templates can serve different reporting needs by accepting various parameters and context information, while uniformly applying security rules based on user roles and organizational policies. This ensures that all reports, regardless of type or creator, adhere to the same security standards.

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

Solution Approach 2:

The system applies security policies at the appropriate local level based on user roles, data sensitivity, and report context. Different security rules are applied to different data elements and report sections according to their specific requirements, while maintaining overall policy consistency. Context information about the user and their permissions determines which security rules are applied to each report.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10642990B2Generation of dynamic contextual pivot grid analytics
Publication Date: 2020.05.05 ORACLE INT CORP
  • US10642990B2 patent drawing
  • US10642990B2 patent drawing
  • US10642990B2 patent drawing

AI summary

A system and method for facilitating timely end user creation, customization, and/or configuration of analytic reports in a computing environment, such as an enterprise-computing environment. An example method includes receiving configuration information characterizing one or more User Interface (UI) features to be incorporated into an analytic report; employing the configuration information to generate one or more database queries to selectively retrieve data from the database; using the configuration information and the one or more database queries to construct an analytic template; and publishing the analytic template so that the analytic template is accessible to one or more end users of the computing environment. In a more specific embodiment, the computing environment includes an enterprise-computing environment, and the one or more users include enterprise personnel. The configuration information, which may include user job role information, includes instructions for collecting context information to control user accessibility to the analytic template and data associated therewith in accordance with the context information.