Software Platform Feature Usage Tracking and Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software platforms lack effective tracking and comparison of feature usage across different entities, making it difficult for system administrators to determine proper utilization and identify abnormalities, as well as generate meaningful metrics for customization and recommendations.

Innovation Solution

A server computer system that tracks interactions, preprocesses data, and generates displays for comparing metrics between entities, allowing for the identification of underutilized features and providing recommendations for improvement by aggregating and computing metrics across similar entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If configurable software platforms are deployed to meet diverse customer needs, then flexibility and adaptability improve, but the ability to track and compare feature usage across different entities deteriorates

Engineering Contradiction:
Improvesoftware platform configurabilityVSAvoidfeature usage data availability
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary system comprising tracking scripts embedded in the software platform and a server computer that mediates between the configurable software platform and the analysis requirements. These tracking components intercept and record feature usage data from multiple entities, transforming untracked individual usage into aggregated comparable data without restricting platform configurability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If detailed tracking of feature usage is implemented, then measurement precision improves, but device complexity and implementation difficulty increase

Engineering Contradiction:
Improvefeature usage tracking accuracyVSAvoidtracking system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts the tracking functionality into separate, modular tracking scripts that are embedded within the software platform but operate independently. These scripts capture specific interaction data (clicks, views, submissions) and transmit it to an external server, separating the tracking complexity from the core software platform while maintaining precise measurement capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If feature usage data is collected from multiple entities, then the ability to identify abnormalities and provide recommendations improves, but data processing requirements and computational resources increase

Engineering Contradiction:
Improveabnormality detection accuracyVSAvoidcomputational processing power
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The patent implements preliminary action by pre-processing and aggregating feature usage data on the server side before detailed analysis is required. The server computer receives raw interaction data, processes it into standardized formats, and maintains organized datasets that can be efficiently queried for abnormality detection and recommendation generation, reducing computational burden during actual analysis operations.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10949229B1Tracking interactions with a software platform and identifying underutilization of software platform features in a specific deployment
Publication Date: 2021.03.16 COUPA SOFTWARE INC
  • US10949229B1 patent drawing
  • US10949229B1 patent drawing
  • US10949229B1 patent drawing

AI summary

Techniques for tracking software platform utilization by a plurality of entities are described herein. In an embodiment, a management computer system stores first entity data defining a first entity and associating the first entity with a plurality of first accounts, the first entity having access to the management computer system programmed which provides options for performing a plurality of tasks. The management computer system tracks a first plurality of interactions with the management computer system that are performed by each of the plurality of first accounts. The management computer system stores first interaction data defining one or more aspects of interaction with the management computer system that are performed by each of the plurality of first accounts. The management computer system stores second entity data defining a plurality of second entities and associating each of the plurality of second entities with a plurality of second accounts. The management computer system tracks a second plurality of interactions with the management computer system that are performed by each of the plurality of second accounts. The management computer system stores second interaction data defining the one or more aspects of interaction with the management computer system performed by each of the plurality of second accounts. The management computer system computes one or more first metrics for the first entity based, at least in part, on the tracked first interaction data. The management computer system computes one or more second metrics for the plurality of second entities based, at least in part, on the tracked second interaction data. The management computer system generates a display comprising a comparison between the one or more first metrics for the first entity and the one or more second metrics for the plurality of second entities.