Multi-Layered Ingestion Script Generation to Reduce Runtime Errors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current script generation procedures for transferring information from regional databases to central repositories are time-consuming, resource-intensive, and prone to runtime errors due to manual generation and debugging, especially when large amounts of data need to be transferred quickly.

Innovation Solution

A multi-layered ingestion program automatically generates scripts for each stage of the information transfer process, including a first layer for identifying information, a second layer for deploying a schedule management program, and a third layer for synchronizing with a central repository, reducing manual input and errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual script generation is used to transfer information from regional databases to central repositories, then flexibility in script customization is improved, but runtime errors increase and productivity decreases

Engineering Contradiction:
Improvescript customizationVSAvoidruntime errors
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs self-service by automatically generating ingestion scripts without requiring manual user intervention. The script generation engine autonomously creates, configures, and deploys scripts based on database schemas and transfer requirements, eliminating human error while maintaining adaptability through automated customization capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-generating and validating scripts before actual data transfer operations. The script generation engine creates scripts in advance, performs syntax validation and dependency checks, and prepares them for deployment, ensuring error-free execution during the actual data ingestion process.

Inventive Principle:
Principle #10Preliminary action

2Quantity of substance

If multiple scripts are manually generated for different data subsets, then information transfer completeness is improved, but time consumption increases

Engineering Contradiction:
Improveinformation transfer volumeVSAvoidscript generation time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The script generation engine provides universality by serving multiple functions: it generates scripts for different data subsets, configures transfer parameters, validates syntax, manages dependencies, and deploys scripts automatically. This multi-functional approach handles large volumes of information transfer across multiple databases without requiring separate manual script generation for each case.

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

Solution Approach 2:

The system ensures continuity of useful action by automating the entire script generation and deployment pipeline. Once initiated, the engine continuously generates scripts for different data subsets, validates them, and deploys them without interruption, enabling uninterrupted information transfer operations across multiple regional databases to the central repository.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If manual script debugging is performed to reduce runtime errors, then script reliability is improved, but resource expenditure increases

Engineering Contradiction:
Improvescript execution accuracyVSAvoiddebugging resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary validation and error checking during script generation before deployment. The engine checks syntax, validates database connections, verifies data type compatibility, and tests script logic in advance, ensuring high reliability without requiring additional manual debugging resources during production operations.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If automated script generation is implemented, then productivity is improved, but system complexity increases

Engineering Contradiction:
Improveinformation transfer speedVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the automated script generation functionality into distinct modular components: a schema analysis module that parses database structures, a script generation engine that creates transfer scripts, a validation module that checks syntax and logic, and a deployment module that executes scripts. This modular architecture enables high productivity while managing system complexity through organized, reusable components.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12386855B2Automatic script generation using a multi-layered ingestion program to reduce runtime errors
Publication Date: 2025.08.12 BANK OF AMERICA CORP
  • US12386855B2 patent drawing
  • US12386855B2 patent drawing
  • US12386855B2 patent drawing

AI summary

Aspects of the disclosure relate to automatic script generation using a multi-layered ingestion program. An automatic ingestion platform may generate the program. The platform may receive a request to ingest information. The platform may automatically generate a plurality of executable scripts using the program. The plurality of scripts may include at least one script corresponding to a first layer of the program and a plurality of scripts corresponding to a second layer of the program. The platform may identify a subset of information to be ingested based on executing a script corresponding to the first layer. The platform may execute the scripts corresponding to the second layer. Executing the scripts corresponding to the second layer may cause the platform to deploy a schedule management program and transfer the subset of information to a third layer. The platform may cause synchronization of a central information repository with the third layer.