Fault-Tolerant Case Creation Framework for Automated Event Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Case Management Systems require manual code development for each case creation, leading to inefficiencies and errors, as they lack automated fault tolerance and effective error handling for creating cases across multiple applications triggered by external events.

Innovation Solution

A fault-tolerant system that receives application-specific inputs, monitors external events, and automatically creates cases by invoking associated codes, with retry mechanisms and error reporting, eliminating the need for manual code development for each application and enhancing error handling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual code development is used for each case creation in conventional Case Management Systems, then developers can create cases for multiple applications, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improvecase creation efficiencyVSAvoidtime for case creation
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service case creation by automatically monitoring external events and creating cases without requiring manual code development. The framework autonomously extracts case properties, creates instances, and manages the case creation process, eliminating the need for developers to manually create code for each case while maintaining high productivity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-configuring case properties, intake information, and triggering parameters in a repository before external events occur. When events are detected, the framework retrieves pre-prepared case definitions and automatically creates cases, significantly reducing the time required for case creation compared to manual code development.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual monitoring and error tracking is performed for each case creation, then developers can identify and remediate errors, but the process becomes complex and time-consuming

Engineering Contradiction:
Improveerror handling capabilityVSAvoiderror tracking complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements automated feedback mechanisms that monitor case creation processes, detect errors, and trigger remedial actions. The framework continuously tracks the status of case creation, identifies failures, and automatically retries or notifies users based on predefined error handling rules, reducing the complexity of error tracking while maintaining high reliability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system prepares error handling strategies in advance by configuring retry counts, remediation steps, and notification preferences before case creation attempts. When errors occur, the framework executes pre-planned error handling procedures, eliminating the need for complex real-time error tracking and reducing operational complexity while ensuring reliable error management.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Productivity

If automated case creation is implemented across multiple applications, then efficiency is improved, but fault tolerance and error handling mechanisms are needed

Engineering Contradiction:
Improveautomation efficiencyVSAvoidfault tolerance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The automated case creation framework incorporates continuous feedback loops that monitor the success of case creation across multiple applications. When failures occur, the system automatically retries case creation up to a configured number of times and notifies users of persistent errors, ensuring fault tolerance while maintaining high automation efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system configures fault tolerance parameters in advance, including retry counts, remediation steps, and notification preferences, before automated case creation begins. This preliminary preparation ensures that the system can handle failures reliably across multiple applications without compromising automation efficiency, as error handling procedures are already in place.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Adaptability or versatility

If developers explicitly create code for each case, then case creation can be customized for different applications, but the process becomes non-trivial and time-consuming

Engineering Contradiction:
Improvecase creation customizationVSAvoidcase creation process simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The framework provides a universal case creation mechanism that works across multiple applications without requiring separate code development for each case. The system retrieves case properties and intake information from a centralized repository and automatically creates cases for different applications using the same framework, maintaining adaptability while greatly simplifying the case creation process.

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

Solution Approach 2:

The system enables self-service case creation by automatically monitoring external events, extracting case properties, and creating cases without requiring developers to write custom code for each application. The framework adapts to different applications by retrieving application-specific case definitions from the repository, maintaining versatility while eliminating the complexity of manual code development.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10437711B1Framework for fault tolerant case creation
Publication Date: 2019.10.08 BANK OF AMERICA CORP
  • US10437711B1 patent drawing
  • US10437711B1 patent drawing
  • US10437711B1 patent drawing

AI summary

Embodiments of the present invention provide a system for fault tolerant case creation. The system is typically configured for receiving an application specific input associated with an application from a user via a user portal, storing the application specific input in a repository, accessing the repository to determine a plurality of predefined triggering parameters, identifying occurrence of first external event, creating an instance of the first external event, adding the first external event and the associated instance in a queue as a first entry, de-queuing the first entry, invoking one or more codes for creating a first case for the first external event and the associated instance, identifying that the creation of the first case by the one or more codes is successful, and generating a report comprising information associated with the successful creation of the first case.