Granted Patent B2

US 12,535,937 · App. 18/528,401 · Granted Jan 27, 2026

Inventors: Dennis Lavin (Syracuse, NY); Bryan Maule (Camillus, NY); Abigail Geaslin (Camillus, NY); Matthew Joseph Ryan (Syracuse, NY)

Assignee: Baker Hughes Holdings LLC

G06F3/0482G02B23/2484

Abstract

Claims (54)

1 . A method comprising:

receiving, within a graphical user interface (GUI) of a borescope device, a selection of a first machine-readable inspection file comprising first data characterizing a first inspection template having one or more nodes corresponding to one or more first inspection points of a first inspection of an asset;

receiving, within the GUI, a selection of a second machine-readable inspection file comprising second data characterizing a second inspection template having one or more nodes corresponding to one or more second inspection points of a second inspection of the asset;

determining that the first inspection file and the second inspection file are compatible to be merged; and

generating a merged inspection folder, wherein the merged inspection folder comprises a, automatically, a merged inspection file, wherein the merged inspection file comprises comprising the first data and the second data.

2 . The method of claim 1 , further comprising:

receiving, within the GUI, a selection of a merge button; and

prompting, within the GUI, a user to select the first inspection file and the second inspection file.

3 . The method of claim 1 , further comprising:

determining whether the first inspection template matches the second inspection template;

generating the merged inspection file responsive to determining that the first inspection template matches the second inspection template; and

providing an error notification to the GUI responsive to determining that the first inspection template does not match the second inspection template.

4 . The method of claim 1 , wherein the first inspection file is stored within a first inspection folder comprising the first inspection file and one or more first files, each of the one or more files corresponding one of the one or more first inspection points, and the second inspection file is stored within a second inspection folder comprising the second inspection file and one or more second files, each of the one or more second files corresponding to one of the one or more second inspection points, the method further comprising:

generating a merged inspection folder, and wherein the merged inspection folder further comprises a merged inspection file, the one or more first files and the one or more second files.

5 . The method of claim 4 , wherein the one or more first files and the one or more second files comprise at least one of an image file, a video file and a text file.

6 . The method of claim 4 , further comprising:

determining whether one or more naming conflicts exist between a title of the one or more first files and a title of the one or more second files; and

responsive to determining that a naming conflict exists between the title of one or more of the first files and the title of the one or more of the second files, modifying the title of at least one of the one or more first files and the one or more second files to resolve the conflict.

7 . The method of claim 4 , wherein the first inspection folder further comprises a first inspection ID and the second inspection folder further comprises a second inspection ID, the method further comprising:

automatically naming the merged inspection folder based on the first inspection ID and the second inspection ID.

8 . The method of claim 4 , further comprising:

generating a merged inspection report, wherein the merged inspection report is a text-based file comprising the contents of the merged inspection folder; and

providing the merged inspection report to a user.

9 . The method of claim 1 , further comprising:

receiving, within the GUI, a selection of a third inspection file comprising third data characterizing a third inspection of the asset; and

determining that the third inspection file is compatible to be merged with the first inspection file and the second inspection file, wherein the merged inspection file further comprises the third data.

10 . A inspection system comprising:

a user interface display (UI); and

a computing system communicatively coupled to the UI and including at least one data processor and a memory storing instructions which, when executed by the at least one processor, cause the at least one processor to perform operations comprising:

receiving, within a graphical user interface (GUI) of the UI, a selection of a first machine-readable inspection file comprising first data characterizing a first inspection template having one or more nodes corresponding to one or more first inspection points of a first inspection of an asset;

receiving, within the GUI, a selection of a second machine-readable inspection file comprising second data characterizing a second inspection template having one or more nodes corresponding to one or more second inspection points of a second inspection of the asset;

determining that the first inspection file and the second inspection file are compatible to be merged; and

generating a merged inspection folder, wherein the merged inspection folder comprises a merged inspection file, wherein the merged inspection file comprises comprising the first data and the second data.

11 . The inspection system of claim 10 , wherein the processor is further configured to perform operations comprising:

receiving, within the GUI, a selection of a merge button; and

prompting, within the GUI, a user to select the first inspection file and the second inspection file.

12 . The inspection system of claim 10 , wherein the processor is further configured to perform operations comprising:

determining whether the first inspection template matches the second inspection template;

generating the merged inspection file responsive to determining that the first inspection template matches the second inspection template; and

providing an error notification to the GUI responsive to determining that the first inspection template does not match the second inspection template.

13 . The inspection system of claim 10 , wherein the first inspection file is stored within the memory in a first inspection folder comprising the first inspection file and one or more first files, each of the one or more files corresponding one of the one or more first inspection points, and the second inspection file is stored within the memory in a second inspection folder comprising the second inspection file and one or more second files, each of the one or more second files corresponding to one of the one or more second inspection points, and the processor is further configured to perform operations comprising:

generating a merged inspection folder, wherein the merged inspection folder further comprises a merged inspection file, the one or more first files and the one or more second files.

14 . The inspection system of claim 13 , wherein the one or more first files and the one or more second files comprise at least one of an image file, a video file and a text file.

15 . The inspection system of claim 13 , wherein the processor is further configured to perform operations comprising:

determining whether one or more naming conflicts exist between a title of the one or more first files and a title of the one or more second files; and

responsive to determining that a naming conflict exists between the title of one or more of the first files and the title of the one or more of the second files, modifying the title of at least one of the one or more first files and the one or more second files to resolve the conflict.

16 . The inspection system of claim 13 , wherein the first inspection folder further comprises a first inspection ID and the second inspection folder further comprises a second inspection ID, and the processor is further configured to perform operations comprising:

automatically naming the merged inspection folder based on the first inspection ID and the second inspection ID.

17 . The inspection system of claim 13 , wherein the processor is further configured to perform operations comprising:

generating a merged inspection report, wherein the merged inspection report is a text-based file comprising the contents of the merged inspection folder; and

providing the merged inspection report to a user.

18 . The inspection system of claim 10 , wherein the processor is further configured to perform operations comprising:

receiving, within the GUI, a selection of a third inspection file comprising third data characterizing a third inspection of the asset; and

determining that the third inspection file is compatible to be merged with the first inspection file and the second inspection file, wherein the merged inspection file further comprises the third data.

Assignments (2)

Continuity (2)

References Cited (16)