IP Library › Granted Patent US 12670174

Granted Patent B1

US 12670174 · App. 19/044,069 · Granted Jun 30, 2026

ETL clustering for reduction of data bloat

Inventors: Kyle Niksa (Columbus, OH); Ryan Brink (Columbus, OH); Shaun Rankin (Columbus, OH)

Assignee: The Huntington National Bank

G06F16/254 G06F16/9024

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 12670174
App. No.: 19/044,069
Granted: Jun 30, 2026
Kind: B1

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

Metadata mapped to units of execution executed by components of a computing infrastructure and data created and/or used by the units of execution may be collected. The metadata may be consolidated and analyzed to identify units of execution mapped to similar or replicative data instances. Instances of potential data bloat mapped to at least a subset of the identified units of execution may be determined. Execution composites may be developed that may include specifications of at least the subset of the identified units of execution. A bloat reduction interface may be generated. The bloat reduction interface may be configured to represent at least the subset of identified units of execution and the instances of potential data bloat mapped to at least the subset of the identified units of execution and to facilitate bloat reduction actions with respect to units of execution of the subset of identified units of execution.

Claims (52)

1 . A system for automatically performing one or more bloat reduction operations to remediate replicative data instances, the system comprising:

one or more processing devices and memory communicatively coupled with and readable by the one or more processing devices, the memory comprising processor-readable instructions which, when executed by the one or more processing devices, cause the system to perform operations comprising:

analyzing metadata to identify units of execution mapped to similar or replicative data instances;

developing specifications of at least a subset of the identified units of execution;

based at least in part on the identified units of execution mapped to similar or replicative data instances, determining one or more instances of potential data bloat mapped to at least a subset of the identified units of execution;

consequent to the determining the one or more instances of potential data bloat, developing execution composites as a function of data created and/or used by the subset of the identified units of execution, wherein each execution composites comprises a mapping of one or more users to at least one of the identified units of execution and storage locations and/or host identifiers mapped to the at least one of the identified units of execution;

based at least in part on the execution composites, determining one or more users associated with the subset of the identified units of execution;

generating and transmitting one or more communications indicative of the determined one or more instances of potential data bloat mapped to at least the subset of identified units of execution, wherein:

the one or more communications comprise a service request populated based at least in part on one or more of the execution composites and directed to the determined one or more users associated with the identified units of execution, and

the service request comprises a link to a user interface that graphically represents the determined one or more instances of potential data bloat and that comprises one or more interface elements that are user-selectable to initiate one or more bloat reduction actions with respect to at least the subset of identified units of execution; and

responsive to a user selection of an interface element, automatically performing a bloat reduction action by reconfiguring, deleting, or deactivating at least one unit of execution of the subset of identified units of execution.

2 . The system as recited in claim 1 , wherein the one or more communications comprise a graphical indication of data relationships of the subset of identified units of execution.

3 . The system as recited in claim 1 , wherein the one or more communications comprise a graphical indication of how the one or more instances of potential data bloat emerged in a computing infrastructure.

4 . The system as recited in claim 1 , wherein the one or more bloat reduction actions comprise reconfiguring, deleting, or deactivating one or more units of execution of the subset of identified units of execution.

5 . The system as recited in claim 1 , wherein the user interface graphically indicates how the one or more instances of potential data bloat emerged in a computing infrastructure.

6 . The system as recited in claim 1 , wherein the user interface is configured to represent at least the subset of identified units of execution and the one or more instances of potential data bloat mapped to at least the subset of the identified units of execution.

7 . The system as recited in claim 1 , wherein the metadata corresponds to consolidated metadata, and the operations further comprise:

collecting metadata mapped to units of execution executed by one or more components of a computing infrastructure and data created and/or used by the units of execution; and

consolidating the metadata into one or more data repositories.

8 . One or more non-transitory, processor-readable media having processor-readable instructions thereon which, when executed by one or more processing devices, cause a system to perform operations for automatically performing one or more bloat reduction operations to remediate replicative data instances, the operations comprising:

analyzing metadata to identify units of execution mapped to similar or replicative data instances;

developing specifications of at least a subset of the identified units of execution;

based at least in part on the execution composites, determining one or more users associated with the subset of the identified units of execution;

9 . The one or more non-transitory, processor-readable media as recited in claim 8 , wherein the one or more communications comprise a graphical indication of data relationships of the subset of identified units of execution.

10 . The one or more non-transitory, processor-readable media as recited in claim 8 , wherein the one or more communications comprise a graphical indication of how the one or more instances of potential data bloat emerged in a computing infrastructure.

11 . The one or more non-transitory, processor-readable media as recited in claim 8 , wherein the one or more bloat reduction actions comprise reconfiguring, deleting, or deactivating one or more units of execution of the subset of identified units of execution.

12 . The one or more non-transitory, processor-readable media as recited in claim 8 , wherein the user interface graphically indicates how the one or more instances of potential data bloat emerged in a computing infrastructure.

13 . The one or more non-transitory, processor-readable media as recited in claim 8 , wherein the user interface is configured to represent at least the subset of identified units of execution and the one or more instances of potential data bloat mapped to at least the subset of the identified units of execution.

14 . The one or more non-transitory, processor-readable media as recited in claim 8 , wherein the metadata corresponds to consolidated metadata, and the operations further comprise:

collecting metadata mapped to units of execution executed by one or more components of a computing infrastructure and data created and/or used by the units of execution; and

consolidating the metadata into one or more data repositories.

15 . A method for automatically performing one or more bloat reduction operations to remediate replicative data instances, the method comprising:

analyzing metadata to identify units of execution mapped to similar or replicative data instances;

developing specifications of at least a subset of the identified units of execution;

based at least in part on the execution composites, determining one or more users associated with the subset of the identified units of execution;

16 . The method as recited in claim 15 , wherein the one or more communications comprise a graphical indication of data relationships of the subset of identified units of execution.

17 . The method as recited in claim 15 , wherein the one or more communications comprise a graphical indication of how the one or more instances of potential data bloat emerged in a computing infrastructure.

18 . The method as recited in claim 15 , wherein the one or more bloat reduction actions comprise reconfiguring, deleting, or deactivating one or more units of execution of the subset of identified units of execution.

19 . The method as recited in claim 15 , wherein the user interface graphically indicates how the one or more instances of potential data bloat emerged in a computing infrastructure.

20 . The method as recited in claim 15 , wherein the user interface is configured to represent at least the subset of identified units of execution and the one or more instances of potential data bloat mapped to at least the subset of the identified units of execution.