# US 2022/0027382 A1 · Data conversion bulk validation automated framework

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0027382 A1
- Document ID: US20220027382A1
- Status: Published application
- Kind: A1
- Application number: 16/937,187
- Filed: 2020-07-23
- Published: 2022-01-27
- Earliest claimed: 2020-07-23
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Howard Bagg; Mathangi Pichai; Justin Charles Taylor
- Web page: https://patentgrep.com/patent/US20220027382A1

## CPC

- G06F 16/258: {Data format conversion from or to a database}
- G06F 16/284: {Relational databases}
- G06F 40/151: Transformation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments of the invention are directed to systems, methods, and computer program products for automating bulk data conversion processes of one or more database management systems. Data conversion projects of focus may comprise conversion of a large bulk of data with a wide range in order of magnitude. The system is designed and driven by the present constraints of large data conversion and is based on principles of reviewability, minimization of manual review and development work, persistence of data stores for data result comparison, process optimization for downstream review and certification, timely execution, and allowance for concurrent development by multiple systems and resources.

## Claims

### Claim 1

A system for automation of bulk data conversion, the system comprising:
at least one memory device with computer-readable program code stored thereon;
at least one communication device;
at least one processing device operatively coupled to the at least one memory device and the at least one communication device, wherein executing the computer-readable program code is configured to cause the at least one processing device to:
receive a request from a user via a user device to initiate a conversion project;
generate and store a conversion project data file for the conversion project on a shared datastore, wherein the shared datastore comprises a datastore accessible via remote access over a network;
receive source data for conversion;
generate a relational database conversion template based on the received source data;
execute the relational database conversion template to generate a peer review data package;
upload the peer review data package to the shared datastore;
grant access to the peer review data package to one or more peer users;
revise the relational database conversion template based on input received from the one or more peer users;
execute a revised relational database conversion template to generate a converted data package; and
upload the converted data package for access by one or more downstream users.

### Claim 2 (depends on 1)

The system of claim 1, wherein generating the relational database conversion template further comprises generating a pre-populated relational database management conversion script based on one or more fields contained in the source data.

### Claim 3 (depends on 1)

The system of claim 1, wherein the source data further comprises data to be converted, a definition document defining one or more data fields or conversion rules, and a data conversion validation file.

### Claim 4 (depends on 1)

The system of claim 1, wherein the peer review data package further comprises a shadow table, wherein the shadow table displays a system version of sourced versus converted data and a summary of discrepancies between source data and converted data.

### Claim 5 (depends on 1)

The system of claim 1, wherein the converted data package further comprises a spreadsheet file summarizing the bulk data conversion.

### Claim 6 (depends on 1)

The system of claim 1, wherein the converted data package further comprises a spreadsheet file with one or more hyperlinks to relational database management conversion code and one or more data definitions.

### Claim 7 (depends on 1)

The system of claim 1, wherein the shared datastore is continuously updated to reflect the status of the conversion project.

### Claim 8

A computer program product for automation of bulk data conversion, the computer program product comprising a non-transitory computer-readable storage medium having computer-executable instructions to:
receive a request from a user via a user device to initiate a conversion project;
generate and store a conversion project data file for the conversion project on a shared datastore, wherein the shared datastore comprises a datastore accessible via remote access over a network;
receive source data for conversion;
generate a relational database conversion template based on the received source data;
execute the relational database conversion template to generate a peer review data package;
upload the peer review data package to the shared datastore;
grant access to the peer review data package to one or more peer users;
revise the relational database conversion template based on input received from the one or more peer users;
execute a revised relational database conversion template to generate a converted data package; and
upload the converted data package for access by one or more downstream users.

### Claim 9 (depends on 8)

The computer program product of claim 8, wherein generating the relational database conversion template further comprises generating a pre-populated relational database management conversion script based on one or more fields contained in the source data.

### Claim 10 (depends on 8)

The computer program product of claim 8, wherein the source data further comprises data to be converted, a definition document defining one or more data fields or conversion rules, and a data conversion validation file.

### Claim 11 (depends on 8)

The computer program product of claim 8, wherein the peer review data package further comprises a shadow table, wherein the shadow table displays a system version of sourced versus converted data and a summary of discrepancies between source data and converted data.

### Claim 12 (depends on 8)

The computer program product of claim 8, wherein the converted data package further comprises a spreadsheet file summarizing the bulk data conversion.

### Claim 13 (depends on 8)

The computer program product of claim 8, wherein the converted data package further comprises a spreadsheet file with one or more hyperlinks to relational database management conversion code and one or more data definitions.

### Claim 14 (depends on 8)

The computer program product of claim 8, wherein the shared datastore is continuously updated to reflect the status of the conversion project.

### Claim 15

A computer implemented method for automation of bulk data conversion, the computer implemented method comprising:
providing a computing system comprising a computer processing device and a non-transitory computer readable medium, where the non-transitory computer readable medium comprises configured computer program instruction code, such that when said instruction code is operated by said computer processing device, said computer processing device performs the following operations:
receiving a request from a user via a user device to initiate a conversion project;
generating and store a conversion project data file for the conversion project on a shared datastore, wherein the shared datastore comprises a datastore accessible via remote access over a network;
receiving source data for conversion;
generating a relational database conversion template based on the received source data;
executing the relational database conversion template to generate a peer review data package;
uploading the peer review data package to the shared datastore;
granting access to the peer review data package to one or more peer users;
revising the relational database conversion template based on input received from the one or more peer users;
executing a revised relational database conversion template to generate a converted data package; and
uploading the converted data package for access by one or more downstream users.

### Claim 16 (depends on 15)

The computer implemented method of claim 15, wherein generating the relational database conversion template further comprises generating a pre-populated relational database management conversion script based on one or more fields contained in the source data.

### Claim 17 (depends on 15)

The computer implemented method of claim 15, wherein the source data further comprises data to be converted, a definition document defining one or more data fields or conversion rules, and a data conversion validation file.

### Claim 18 (depends on 15)

The computer implemented method of claim 15, wherein the peer review data package further comprises a shadow table, wherein the shadow table displays a system version of sourced versus converted data and a summary of discrepancies between source data and converted data.

### Claim 19 (depends on 15)

The computer implemented method of claim 15, wherein the converted data package further comprises a spreadsheet file with one or more hyperlinks to relational database management conversion code and one or more data definitions.

### Claim 20 (depends on 15)

The computer implemented method of claim 15, wherein the shared datastore is continuously updated to reflect the status of the conversion project.
