Content Bucket Manager for Financial Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Institutions face challenges in maintaining consistency in treating customers fairly due to unique circumstances surrounding each customer or account, leading to inconsistencies in procedures and data management across different employees and sources.

Innovation Solution

A method and system for standardizing stored content objects through prepopulating storage areas with content buckets, allowing authorized users to fill and manage these buckets, and automatically renaming content objects for consistent naming across storage areas, while enabling customization for different industries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If institutions allow employees to manage customer data independently with different preferences, then employee flexibility and autonomy are improved, but data consistency and uniformity deteriorate

Engineering Contradiction:
Improveemployee flexibilityVSAvoiddata consistency
Core Design Contradiction:
Ease of operationVSStability of the object's composition

Solution Approach 1:

The system segments data management into standardized templates that define specific content buckets for different data types. Each template prescribes the structure and organization of data, allowing employees to work independently while maintaining consistency through predefined segments rather than free-form management.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the parameters of data storage by imposing standardized schemas, required fields, and content bucket structures. This transforms unrestricted data entry into constrained data population within defined parameters, ensuring uniformity while allowing employee autonomy in filling the structured templates.

Inventive Principle:
Principle #35Parameter changes

2Stability of the object's composition

If institutions implement standardized procedures for customer treatment, then treatment consistency is improved, but adaptability to unique customer circumstances deteriorates

Engineering Contradiction:
Improvetreatment consistencyVSAvoidcustomer-specific flexibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system implements dynamic templates that can be customized for different customer types, products, and scenarios. While the overall structure remains standardized for consistency, the content buckets and required fields can be dynamically adjusted to accommodate unique customer circumstances, merging standardization with adaptability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The template system serves multiple functions: it enforces standardized data collection for consistency while simultaneously providing flexible customization capabilities for different customer situations. The same framework universally applies to all customers but can be adapted to specific needs through configurable parameters and optional content buckets.

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

3Quantity of substance

If institutions collect detailed information from multiple sources, then data completeness is improved, but data organization and review difficulty increase

Engineering Contradiction:
Improvedata completenessVSAvoiddata organization
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The system segments incoming data from multiple sources into predefined content buckets within templates. Each bucket is designed to receive specific types of information, automatically organizing diverse data into structured categories. This segmentation maintains data completeness while reducing organizational complexity through systematic classification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The template system acts as an intermediary layer between raw data from multiple sources and the final organized record. Data flows through the template structure which mediates the organization process, automatically placing information in appropriate buckets and applying standardized formatting, thereby simplifying the review process while maintaining completeness.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Measurement precision

If institutions manually organize and review customer data, then data accuracy can be maintained, but time consumption and processing efficiency deteriorate

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary organization and validation of data as it enters the templates, automatically checking for required fields, proper formatting, and consistency rules. This preliminary action catches errors early in the process, maintaining data accuracy while reducing the time needed for later manual review and correction.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The template system provides self-service data validation and organization capabilities, automatically verifying data accuracy through built-in rules and constraints. This reduces the need for manual accuracy checks while maintaining high standards, allowing employees to focus on higher-value tasks rather than repetitive verification.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8762376B2Financial-service structured content manager
Publication Date: 2014.06.24 NCINO
  • US8762376B2 patent drawing
  • US8762376B2 patent drawing
  • US8762376B2 patent drawing

AI summary

A financial-service system that manages content objects includes a chronicles platform with a chronicle associated with a loan request. A content manager determines a set of content objects to be associated with the chronicle and generates a bucket for each content object of the set of content objects. Each bucket is associated with a name and is configured to receive an associated content object. The chronicle is populated with the generated buckets. An interface that detects a user action and that thereafter receives or generates a content object, which is detected by the content manager and associated with a bucket. The content manager causes the bucket to receive the content object and presents representations of the buckets to a user. Representations of one or more buckets that have received a content object differ from representations of one or more other buckets that have not received a content object.