Centralized Predictive Model Management System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In organizations, multiple teams duplicate efforts in designing and generating predictive models, lack collaboration, and have inconsistent and resource-intensive model retraining processes, making it difficult to manage and determine which models are effective.

Innovation Solution

A centralized model maintenance system that allows teams to share and build upon each other's work, automatically retrain models, and manage model versions, reducing duplication and improving model performance by providing a centralized view of model performance and version history.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple teams independently design and generate predictive models, then each team can develop models tailored to their specific needs, but this results in duplicated effort and wasted resources

Engineering Contradiction:
Improvemodel customizationVSAvoidmodel generation efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges model development efforts across multiple teams by implementing a centralized model registry and version control system. Teams share a common infrastructure for model training, evaluation, and deployment, allowing them to leverage each other's work while maintaining the ability to customize models for specific needs. This resolves the contradiction by combining resources to improve efficiency while preserving adaptability through configurable model parameters and team-specific customization options.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system provides universal model development capabilities that serve multiple teams simultaneously. A single model architecture and training pipeline can be used across different teams, with the ability to adapt to various specific requirements through configuration rather than separate implementation. This universal platform improves overall productivity while maintaining the versatility needed for different team-specific applications.

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

2Reliability

If teams retrain models independently and ad hoc, then models can be updated when needed, but this leads to inconsistent retraining timing and excessive computational resource consumption

Engineering Contradiction:
Improvemodel accuracyVSAvoidcomputational resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system implements periodic, scheduled model retraining based on centralized criteria rather than ad hoc independent retraining by each team. A coordination mechanism monitors data drift and performance degradation across all teams' models, triggering retraining only when necessary and at optimized intervals. This periodic approach maintains model reliability while significantly reducing unnecessary computational resource consumption compared to continuous or frequent independent retraining.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system employs feedback loops that monitor model performance and data characteristics across all teams, using this information to intelligently determine when retraining is necessary. The feedback mechanism aggregates performance metrics from multiple teams and triggers centralized retraining decisions, ensuring models remain accurate while avoiding redundant retraining computations. This feedback-driven approach optimizes the balance between model reliability and resource efficiency.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If teams develop models independently without collaboration, then each team maintains full control over their model development, but management cannot determine which models are effective or how to improve underperforming teams

Engineering Contradiction:
Improveteam autonomyVSAvoidmodel performance visibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system introduces a centralized model registry and performance tracking system as an intermediary between independent teams and organizational management. This intermediary collects, standardizes, and makes visible performance data from all teams' models while preserving team autonomy in model development. Management gains visibility into model effectiveness and team performance through this intermediary layer without micromanaging individual teams, thus maintaining ease of operation while reducing information loss.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments model development and performance tracking into independent, modular components that can be independently managed by each team while being aggregated for organizational visibility. Each team maintains autonomous control over their specific model development processes, while the segmented performance metrics are collected and presented in a centralized dashboard. This segmentation preserves team autonomy while enabling management to identify effective models and support underperforming teams.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10387799B2Centralized management of predictive models
Publication Date: 2019.08.20 ACCENTURE GLOBAL SOLUTIONS LTD
  • US10387799B2 patent drawing
  • US10387799B2 patent drawing
  • US10387799B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for centralized management of predictive models. One of the methods includes receiving a plurality of model versions from respective teams within the organization. Each received model version is processed to generate a respective predictive model corresponding to the model version, including identifying one or more collections of training data specified by the model version, identifying one or more training engines specified by the model version, training, by the identified one or more training engines, a predictive model using the identified one or more collections of training data, computing one or more performance metrics for the predictive model, and associating the one or more performance metrics for the predictive model with the corresponding model version in the version repository.