Analytics Engine Segmentation for CMS Resource Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content management systems (CMS) face challenges in efficiently managing and analyzing data related to content items, which can lead to reduced performance and barriers in user interaction when generating multi-dimensional reports and analytics.

Innovation Solution

A computer-implemented method that involves receiving data associated with the use of content items in a CMS, measuring the use of CMS resources, assigning usage metrics, and generating a database schema to optimize resource usage and facilitate efficient access to content items.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If analytics are performed by the CMS itself, then comprehensive business intelligence is achieved, but CMS performance deteriorates due to processor-intensive operations

Engineering Contradiction:
Improvebusiness intelligenceVSAvoidCMS performance
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The system segments the analytics function from the CMS by introducing a separate analytics engine. The CMS generates events and transmits them to the analytics engine, which performs processor-intensive analytics operations. This segmentation allows the CMS to maintain optimal performance while the analytics engine comprehensively processes business intelligence requirements.

Inventive Principle:
Principle #1Segmentation

2Productivity

If an analytics engine is separated from the CMS, then CMS performance is improved, but user interaction between CMS and analytics becomes barriered

Engineering Contradiction:
ImproveCMS performanceVSAvoiduser interaction
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system merges the CMS and analytics engine into a unified user interface environment. Both the CMS interface and analytics reports are accessible through the same client device and interface paradigm, allowing users to interact with both systems seamlessly without switching applications or learning different interaction models.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system introduces an event data warehouse and standardized event protocols as intermediaries between the CMS and analytics engine. Events generated by the CMS are transmitted through this intermediary layer to the analytics engine, enabling smooth data flow and interaction while maintaining system separation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If multi-dimensional reports are generated, then comprehensive analytics are achieved, but resource consumption increases

Engineering Contradiction:
Improveanalytics comprehensivenessVSAvoidprocessor resources
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary action by pre-processing and storing event data in an event data warehouse in the same time zone as the CMS. Events are normalized and organized beforehand, allowing the analytics engine to efficiently generate multi-dimensional reports without performing intensive real-time processing, thus reducing overall processor resource consumption.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12242434B2Reducing reliance on content management system resources in a content management system
Publication Date: 2025.03.04 HYLAND UK OPERATIONS LTD
  • US12242434B2 patent drawing
  • US12242434B2 patent drawing
  • US12242434B2 patent drawing

AI summary

An analytics engine is described that can receive data associated with use of a content item in a content management system and measure a use of content management system resources required to maintain the content item. Values of a usage metric can be assigned to the content item based on the received data associated with the use of the content item. A database schema can be generated by the analytics engine that is configured to reduce the use of content management system resources required to maintain the content item. The database schema can be provided to the content management system for implementation in a database associated with the content management system.