Remote Customization Module for Business Logic Engines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current business engine customization methods, such as altering core code, are prone to errors, time-consuming, and introduce security risks, especially when integrating third-party suppliers, leading to potential failures and delays in providing bespoke functionality to clients.

Innovation Solution

A remote customization module that communicates with a business logic engine to process and generate response data without requiring core code recoding, using a communication interface and logic element to interrogate applications, thereby providing bespoke functionality efficiently and securely, with minimal data transfer and reduced risk of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If core code is altered to customize business engine functionality, then bespoke functionality is achieved, but code reliability deteriorates due to increased error risk

Engineering Contradiction:
Improvebespoke functionalityVSAvoidcode reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system segments customization functionality from the core business engine code by introducing a separate customization layer that interfaces with the engine through defined protocols. This allows bespoke functionality to be added without modifying the core code, thereby maintaining code reliability while achieving adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary customization interface is introduced between the user and the core business engine. This intermediary layer handles customizations and translates them into engine-compatible operations, preventing direct modification of core code while still enabling bespoke functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If core code is altered to meet client requirements, then client-specific functionality is achieved, but development time increases due to strict version control

Engineering Contradiction:
Improveclient-specific functionalityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-defining a standardized customization interface and framework before client-specific requirements are implemented. This preliminary structure enables rapid deployment of client-specific functionality without requiring time-consuming code modifications and reintegration processes.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If third party supplier databases are integrated to extend functionality, then service versatility is improved, but security risks increase due to data transfer requirements

Engineering Contradiction:
Improveservice versatilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

An intermediary data exchange layer is introduced between the business engine and third-party supplier databases. This intermediary implements security protocols, data validation, and controlled access mechanisms, allowing service versatility through third-party integration while mitigating security risks through structured data transfer controls.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7913264B2Remote customisation module and system comprising said module
Publication Date: 2011.03.22 AMADEUS SAS
  • US7913264B2 patent drawing
  • US7913264B2 patent drawing

AI summary

A remote customisation module for a logic engine, running upon a server remote from said logic engine, comprises a communication interface arranged to communicate with the logic engine and with an application running upon said server. The module also comprises a logic element arranged to receive an incoming request for data from the logic engine via the communication interface. The logic element is arranged to interrogate the application in order to extract data required to fulfill said request. The logic element is also arranged to process said extracted data to generate response data and to pass said response data to the logic engine.