# US 2026/0064244 A1 · Merge menu directed inspections from multiple borescope inspections into a single inspection and report

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

- Number: US 2026/0064244 A1
- Document ID: US20260064244A1
- Status: Published application
- Kind: A1
- Application number: 19/380,223
- Filed: 2025-11-05
- Published: 2026-03-05
- Earliest claimed: 2022-12-12
- Applicants: Baker Hughes Holdings LLC
- Inventors: Dennis Lavin; Bryan Maule; Abigail Geaslin; Matthew Joseph Ryan
- Web page: https://patentgrep.com/patent/US20260064244A1

## CPC

- G06F 3/0482: Interaction with lists of selectable items, e.g. menus
- G02B 23/2484: {Arrangements in relation to a camera or imaging device (processing or control of video signals generated by an endoscope H04N23/60, H04N23/70)}
- G06F 3/0484: for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
- G01N 2021/9542: {using a probe}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G02B: OPTICAL ELEMENTS, SYSTEMS OR APPARATUS
- G01N: INVESTIGATING OR ANALYSING MATERIALS BY DETERMINING THEIR CHEMICAL OR PHYSICAL PROPERTIES (measuring or testing apparatus or processes other than immunoassay, involving enzymes or microorganisms C12M, C12Q)

## Abstract

In one aspect a system and method for merging inspections from multiple borescope inspections into a single inspection and report include receiving, within a graphical user interface (GUI) of a borescope device, a selection of a first inspection file including first data characterizing a first inspection of an asset, receiving, within the GUI, a selection of a second inspection file including second data characterizing a second inspection of the asset, determining that the first inspection file and the second inspection file may be compatible to be merged and generating, automatically, a merged inspection file the merged inspection file that includes the first data and the second data.

## Claims

### Claim 1

A method comprising:
receiving, by at least one processor of a computing device, 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, by the at least one processor, 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, by the at least one processor, that the first inspection file and the second inspection file are compatible to be merged; and
generating a merged inspection file comprising the first data and the second data.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, within a graphical user interface (GUI) of the computing system, a selection of a merge button; and
prompting, within the GUI, a user to select the first inspection file and the second inspection file.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
comparing, by the at least one processor, a first inspection identifier of the first inspection file to a second inspection identifier of the second inspection file; and
generating the merged inspection file responsive to determining that the first inspection identifier is compatible with the second inspection identifier.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
providing an error notification to a graphical user interface (GUI) of the computing system responsive to determining that the first inspection identifier is not compatible with the second inspection identifier.

### Claim 5 (depends on 3)

The method of claim 3, further comprising:
automatically naming the merged inspection file based on the first inspection identifier and the second inspection identifier.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
generating a merged inspection folder, wherein the merged inspection folder comprises the merged inspection file, and
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
wherein 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, and
wherein the merged inspection folder further comprises the one or more first files and the one or more second files, and 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.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
determining that 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
modifying the title of at least one of the one or more first files and the one or more second files to resolve the one or more naming conflicts.

### Claim 8 (depends on 6)

The method of claim 6, further comprising:
generating a merged inspection report, wherein the merged inspection report includes at least one of an image file, a video file, or a text-based file comprising the contents of the merged inspection folder; and
providing the merged inspection report to a user.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
receiving, by the at least one processor, 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.

### Claim 10 (depends on 1)

The method of claim 1, wherein at least one of the first machine-readable inspection file and the second machine-readable inspection file are received via an external drive communicatively coupled to the computing system.

### Claim 11

A system comprising:
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 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 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 file comprising the first data and the second data.

### Claim 12 (depends on 11)

The inspection system of claim 11, further comprising a graphical user interface (GUI), wherein the at least one data 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.

### Claim 13 (depends on 11)

The inspection system of claim 11, wherein the at least one data processor is further configured to perform operations comprising:
comparing a first inspection identifier of the first inspection file to a second inspection identifier of the second inspection file; and
generating the merged inspection file responsive to determining that the first inspection identifier is compatible with the second inspection identifier.

### Claim 14 (depends on 13)

The inspection system of claim 13, further comprising a graphical user interface (GUI), wherein the at least one data processor is further configured to perform operations comprising:
providing an error notification to the GUI responsive to determining that the first inspection identifier is not compatible with the second inspection identifier

### Claim 15 (depends on 13)

The inspection system of claim 13, wherein the at least one data processor is further configured to perform operations comprising:
automatically naming the merged inspection file based on the first inspection identifier and the second inspection identifier

### Claim 16 (depends on 11)

The inspection system of claim 11, wherein the at least one data processor is further configured to perform operations comprising:
generating a merged inspection folder, wherein the merged inspection folder comprises the merged inspection file, and
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
wherein 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, and
wherein the merged inspection folder further comprises the one or more first files and the one or more second files, and 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.

### Claim 17 (depends on 16)

The inspection system of claim 16, wherein the at least one data processor is further configured to perform operations comprising:
determining that 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
modifying the title of at least one of the one or more first files and the one or more second files to resolve the one or more naming conflicts.

### Claim 18 (depends on 16)

The inspection system of claim 16, wherein the processor is further configured to perform operations comprising:
generating a merged inspection report, wherein the merged inspection report includes at least one of an image file, a video file, or a text-based file comprising the contents of the merged inspection folder; and
providing the merged inspection report to a user.

### Claim 19 (depends on 11)

The inspection system of claim 11, 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.

### Claim 20 (depends on 11)

The inspection system of claim 11, wherein at least one of the first machine-readable inspection file and the second machine-readable inspection file are received via an external drive communicatively coupled to the at least one processor and the memory.
