Automated Message File Generation and Validation Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing process of creating and transmitting message files is tedious and error-prone, often failing to validate messages against industry standards, leading to difficulties in communication between message-sending and receiving entities.

Innovation Solution

A system architecture framework that includes a message generator to create message files from spreadsheet data, a transmitter to send these files to a UNIX-based server, a shell script for handshaking and initiating transmission, an output retriever to retrieve files, a validation appliance to ensure message accuracy, and a report generator to document the process, all of which can operate independently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If message files are created manually by copying and pasting data into user interfaces, then the process is simple to implement, but it is tedious and error-prone with high human error factor

Engineering Contradiction:
Improveease of implementationVSAvoiderror rate
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system enables self-service automation where the message generator automatically reads spreadsheet data and creates message files without human intervention. The validation appliance then automatically validates these messages against industry standards, eliminating the need for manual copying and pasting while ensuring accuracy through automated validation rules.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical manual process of copying and pasting data with an automated electronic system. The message generator uses software automation to read spreadsheet data and generate message files programmatically, while the validation appliance uses automated validation logic to check compliance, substituting human manual operations with automated computational processes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Device complexity

If manual message creation process is used, then the system complexity is low, but the process is unable to determine or validate messages to ensure industry standards compliance

Engineering Contradiction:
Improvesystem complexityVSAvoidvalidation accuracy
Core Design Contradiction:
Device complexityVSManufacturing precision

Solution Approach 1:

The system segments the message creation and validation process into distinct modular components: the message generator that creates message files from spreadsheet data, and the validation appliance that separately validates these messages against industry standards. This segmentation allows each component to be optimized independently while maintaining overall system manageability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The validation appliance acts as an intermediary between message creation and message transmission. It receives generated message files, validates them against industry standards, and only allows compliant messages to proceed. This intermediary layer ensures validation accuracy without requiring complete system redesign, adding verification capability while maintaining process flow.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If automated message generation system is implemented, then validation accuracy and industry standards compliance are ensured, but the device complexity and system architecture increase

Engineering Contradiction:
Improvevalidation accuracyVSAvoidsystem architecture
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The validation appliance is designed as a universal component that can validate multiple types of message files against various industry standards. It provides multi-functional validation capabilities that can handle different message formats and standards requirements, reducing the need for separate validation systems for each message type and thereby managing complexity through consolidation.

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

Solution Approach 2:

The system implements feedback through the validation appliance that provides validation results back to the message generation process. When messages fail validation, the system can identify and correct errors before transmission. This feedback mechanism ensures high validation accuracy while managing complexity through iterative improvement rather than requiring perfect initial design.

Inventive Principle:
Principle #23Feedback

4Device complexity

If manual message transmission process is used, then the setup is simple, but it causes difficulties in communication between message-sending and receiving entities due to undetected errors

Engineering Contradiction:
Improvesetup simplicityVSAvoidcommunication reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The validation appliance performs preliminary validation of message files before they are transmitted to receiving entities. By checking messages against industry standards in advance and correcting errors before transmission, the system ensures communication reliability without requiring complex real-time communication protocols or post-transmission error handling mechanisms.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10817661B2System architecture framework
Publication Date: 2020.10.27 BANK OF AMERICA CORP
  • US10817661B2 patent drawing
  • US10817661B2 patent drawing
  • US10817661B2 patent drawing

AI summary

Methods for operating a system architecture framework are provided. Methods may include receiving a spreadsheet file. Methods may include creating a plurality of message files at a message generator. Each message file may correspond to a single row of data included in the spreadsheet file. Methods may include transmitting the plurality of message files to a UNIX-based server. Methods may include handshaking using a shell script located on the UNIX-based server, between the server and the message generator. Methods may include transmitting an instruction to the message generator to initiate message transmission from the message generator to the server. The instruction may be triggered in response to the shell script determining that the message generator has completed message generation. Methods may include performing a validation test on each of the message files. The validation test may compare each message file to the corresponding row in the spreadsheet file.