Strategy Maintenance System for Enterprise Bandwidth Conservation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large enterprises, such as financial institutions, face inefficiencies in managing and communicating strategies with third-party entities, leading to bandwidth and memory consumption issues due to frequent changes and testing requirements.

Innovation Solution

A strategy-maintenance system that stores and executes templates on a local machine, allowing enterprises to create, edit, and manage strategies internally before sending them to third-party entities, thereby reducing the need for continuous communication and testing by the third-party.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If strategies are frequently updated and communicated to third-party entities, then the enterprise can maintain up-to-date strategies, but bandwidth and memory consumption increase

Engineering Contradiction:
Improvestrategy currencyVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by storing strategies locally and executing them before communication to third-party entities. This allows the enterprise to maintain current strategies without continuously transmitting updates, as the local cache serves as a preliminary reservoir of up-to-date information that reduces the need for frequent communications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention implements local quality by maintaining a local cache of strategies and templates within the enterprise environment. This local repository allows selective communication of only necessary updates to third-party entities, rather than transmitting entire strategy sets, thereby reducing bandwidth consumption while maintaining strategy currency.

Inventive Principle:
Principle #3Local quality

2Reliability

If strategies are frequently updated and communicated to third-party entities, then the enterprise can maintain up-to-date strategies, but memory consumption increases

Engineering Contradiction:
Improvestrategy currencyVSAvoidmemory consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system segments strategy management into distinct components: local storage of templates and strategies, local execution capabilities, and selective communication mechanisms. This segmentation allows the enterprise to maintain strategy currency by storing only essential template definitions locally rather than complete strategy instances, reducing memory consumption while preserving the ability to generate updated strategies as needed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

By preliminarily storing template definitions and strategy structures locally rather than complete strategy data, the system reduces memory requirements. The local cache contains only the essential framework information needed to reconstruct or update strategies, rather than storing full strategy objects, thereby maintaining strategy currency with reduced memory consumption.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If third-party entities create, edit, and manage strategies, then strategy management is outsourced, but control and testing capability are reduced

Engineering Contradiction:
Improveoutsourced managementVSAvoidtesting capability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system enables self-service by providing the enterprise with local strategy execution capabilities and template management tools. The enterprise can independently create, edit, and test strategies using locally stored templates before communicating them to third-party entities. This self-service approach maintains outsourcing benefits while preserving full testing and control capabilities within the enterprise environment.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The invention implements preliminary action by allowing the enterprise to fully develop and test strategies locally using stored templates before transmitting them to third-party entities. This preliminary development and testing phase ensures strategy reliability is verified in advance, maintaining control and testing capability while still benefiting from outsourced management of the actual strategy communication and implementation.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If third-party entities test strategies, then external validation is obtained, but bandwidth and memory are consumed for each test iteration

Engineering Contradiction:
Improvestrategy validationVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary validation by enabling local strategy execution and testing capabilities within the enterprise environment. Strategies can be tested and validated locally before being communicated to third-party entities, obtaining necessary validation without requiring repeated transmissions for each test iteration. This preliminary validation approach maintains reliability while significantly reducing bandwidth consumption.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention implements local quality by providing local strategy execution capabilities that allow validation to occur within the enterprise environment rather than requiring external testing for each iteration. This local validation capability reduces the need for continuous communication with third-party entities for testing purposes, thereby reducing bandwidth consumption while maintaining strategy validation quality.

Inventive Principle:
Principle #3Local quality

5Reliability

If third-party entities test strategies, then external validation is obtained, but memory and processing resources are consumed

Engineering Contradiction:
Improvestrategy validationVSAvoidmemory consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system performs preliminary validation locally by storing strategy templates and execution capabilities within the enterprise environment. This allows strategies to be validated and tested using local resources before being communicated to third-party entities, obtaining necessary validation without requiring third-party memory resources for each test iteration. This preliminary validation approach maintains reliability while reducing overall memory consumption.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention segments the validation process into local template storage and execution capabilities, separating the heavy lifting of strategy validation from third-party entities. By maintaining local execution capabilities, the enterprise can perform validation using its own resources, reducing the memory and processing burden on third-party systems while maintaining validation reliability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9720651B2Strategy maintenance system
Publication Date: 2017.08.01 BANK OF AMERICA CORP
  • US9720651B2 patent drawing
  • US9720651B2 patent drawing
  • US9720651B2 patent drawing

AI summary

A strategy-maintenance system comprises a memory, an interface, and a processor. The system is operable to store a plurality of templates. A template comprises a statement that facilitates writing one or more strategies. The system may further communicate to a first computer the plurality of templates for presentation on a first graphical user interface. The system also receives a first selection of at least one of the plurality of templates for a strategy. The strategy is operable to calculate a key value based on at least one of the plurality of templates. The system finally executes the strategy to calculate the key value and communicates the strategy for execution on a remote machine.