Party Object Conversion System for Dynamic Type Changes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems require the creation of a new party object when a party changes type or classification, leading to redundant data acquisition and processing, and fail to identify necessary start-up points within ongoing processes.

Innovation Solution

A dynamic and automated conversion system that uses party-type and classification rules to determine which data and processes to retain, delete, or add to the existing party object, allowing for conversion without creating a new object, and identifies start-up points within ongoing processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a new party object is created when party type changes, then the party object structure matches the new party type, but redundant data acquisition and processing occurs

Engineering Contradiction:

Improveparty object structure accuracyVSAvoiddata acquisition efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by identifying and retaining applicable data and processes from the existing party object before conversion. The conversion application analyzes the existing object, determines what data and processes are relevant to the new party type, and preserves these elements before completing the conversion, thereby avoiding redundant data acquisition

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system discards only the data and processes that are not applicable to the new party type while recovering and retaining the applicable ones. The conversion application selectively removes obsolete elements and keeps relevant data, processes, and relationships, thus eliminating redundancy while maintaining necessary information

Inventive Principle:

Principle #34Discarding and recovering

2Reliability

If a new party object is created when party type changes, then the party object is optimized for the new party type, but processing time and resources increase

Engineering Contradiction:

Improveparty object applicabilityVSAvoidconversion processing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary analysis to identify the new party type requirements and determine which existing data and processes should be retained before executing the full conversion. This preliminary assessment reduces the overall processing time by pre-identifying what needs to be converted versus what can be preserved

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system changes parameters by modifying the existing party object's type classification and associated attributes rather than creating a completely new object. The conversion application updates the party object's parameters to reflect the new party type while maintaining continuity, thereby reducing processing time and resource consumption

Inventive Principle:

Principle #35Parameter changes

3Ease of manufacture

If the existing party object is deleted and a new one created, then the process is simple to implement, but common data and processes are redundantly processed

Engineering Contradiction:

Improveconversion process simplicityVSAvoidcomputational resource consumption

Core Design Contradiction:

Ease of manufactureVSLoss of energy

Solution Approach 1:

The system merges the conversion process with the existing party object rather than treating them as separate operations. The conversion application integrates the analysis, retention, and transformation steps into a unified process that operates on the existing object, simplifying implementation while avoiding redundant processing of common data and processes

Inventive Principle:

Principle #5Merging (Combining)

4Productivity

If party object conversion is performed, then redundant data acquisition is eliminated, but system complexity increases

Engineering Contradiction:

Improvedata processing efficiencyVSAvoidconversion system complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a conversion application as an intermediary between the existing party object and the final converted object. This intermediary component handles the complex logic of analyzing, retaining, and transforming data and processes, thereby eliminating redundant operations while managing system complexity through a dedicated intermediate layer

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS11126637B2System for dynamic conversion of party objects

Publication Date: 2021.09.21 BANK OF AMERICA CORP

AI summary

A system for dynamic and automated conversion of party objects based on a change in party type and/or party classification. Party-type and/or party-classification specific rules are relied on to determine which data and processes to include in the converted party object. As such, the converted party object provides for (i) retaining data and processes that are common to both party types and/or classifications, (ii) disabling or otherwise deleting data and processes not associated with the new party type and/or classification, and (iii) adding new data, data entry fields and processes for data and processes associated with the new party type and/or classification that were not associated with the previous party type.