Automatic synchronization of borescope data

Abstract

A first data set is received by a non-destructive testing device (NDT device) from a remote system. A second data set is received by the NDT device from a sensor on the NDT device. In response to receiving the second data set, the first data set and the second data set are synchronized by comparing the first data set and the second data set to create a synchronized data set, identifying differences between the first data set and the second data set, and providing a data set that includes elements of both the first data set and the second data set. The synchronization occurs automatically during the inspection. The synchronization occurs between the NDT device and the remote system such that the synchronized data set exists on both the NDT device and the remote system.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority under 35 U.S.C. § 119 to U.S. Provisional Patent Application No. 63 / 370,052, entitled "Automated Borescope Data Upload," filed August 1, 2022, which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates to automating the synchronization of data from testing equipment. [Background technology]

[0003] During a borescope inspection, a large amount of data is captured and generated. This includes images and corresponding 3D data, measurements, human- or computer-generated annotations and displays, menu-driven inspection (MDI) metadata, and other metadata related to the inspection. In typical operation, such data is stored on the borescope or on a memory card within the borescope. The data is then transferred to a personal computer or server after the borescope completes its inspection operation and returns from the inspection site. Summary of the Invention

[0004] The present disclosure relates to automating the synchronization of borescope data.

[0005] An exemplary implementation of the subject matter described within this disclosure is a method having the following features: A first data set is received by a non-destructive testing device (NDT device) from a remote system; A second data set is received by the NDT device from a sensor on the NDT device; In response to receiving the second data set, the first data set and the second data set are synchronized by comparing the first data set and the second data set to create a synchronized data set, identifying differences between the first data set and the second data set, and providing a data set that includes elements of both the first data set and the second data set; The synchronization occurs automatically during the inspection; The synchronization occurs between the NDT device and the remote system such that the synchronized data set exists on both the NDT device and the remote system.

[0006] The disclosed methods may be implemented in various ways, such as in a system including at least one data processor and non-transitory memory storing instructions for the processor to perform aspects of the method. Alternatively or additionally, the methods may be contained in non-transitory computer-readable memory storing the methods as instructions that, when executed by at least one data processor forming part of at least one computing system, cause the at least one data processor to perform operations of the method.

[0007] Aspects of the example method that may be included with the example method alone or in combination with other aspects include the following: the NDT device is a first NDT device, and the synchronized dataset is a first synchronized dataset. The method further includes the following features: the first dataset is received by a second NDT device from a remote system; a third dataset is received by the second NDT device from a sensor on the NDT device; and in response to receiving the third dataset, the first dataset, the second dataset, and the third dataset are synchronized between the first NDT device, the second NDT device, and the remote system to automatically create a second synchronized dataset during the inspection, such that a second set of synchronized datasets exists at the first NDT device, the second NDT device, and the remote system.

[0008] Aspects of the example method that may be included with the example method alone or in combination with other aspects include the following: Synchronizing the first data set and the second data set includes providing, by the NDT device, the second data set to the remote system, the second data set characterizing the information content of the NDT device.

[0009] Aspects of the example method that may be included with the example method alone or in combination with other aspects include the following: Receiving a first data set from a remote system includes providing the first data set characterizing the test template from the remote system to the NDT device.

[0010] Aspects of the exemplary method that may be included with the exemplary method alone or in combination with other aspects include the following: Receiving data from a sensor includes performing a test.

[0011] Aspects of the exemplary method that may be included with the exemplary method alone or in combination with other aspects include the following: The synchronized dataset includes images or videos, metadata, annotations made by the inspector, and / or measurements.

[0012] Aspects of the exemplary method that may be included with the exemplary method alone or in combination with other aspects include the following: The synchronized data includes a specified file nomenclature. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a flow diagram of an exemplary method that may be used according to aspects of the present disclosure. [Figure 2] FIG. 1 is a block diagram of an example communication that may be used by aspects of the present disclosure. [Figure 3] FIG. 2 is a block diagram of an exemplary controller. [Figure 4] FIG. 1 is a diagram of a borescope. DETAILED DESCRIPTION OF THE INVENTION

[0014] Certain embodiments will now be described to provide a thorough understanding of the principles of the structure, function, manufacture, and use of the devices and methods disclosed herein. One or more examples of these embodiments are illustrated in the accompanying drawings. Those skilled in the art will understand that the devices and methods explicitly described herein and illustrated in the accompanying drawings are non-limiting embodiments, and that the scope of the invention is defined only by the claims. Features illustrated or described in connection with one embodiment may be combined with features of other embodiments. Such modifications and variations are intended to be within the scope of the present invention.

[0015] Furthermore, in this disclosure, like-named components of embodiments generally have similar characteristics, and therefore, every feature of each like-named component within a particular embodiment is not necessarily described in full detail. Additionally, to the extent that linear or circular dimensions are used in describing the disclosed systems, devices, and methods, such dimensions are not intended to limit the types of shapes that may be used with such systems, devices, and methods. Those skilled in the art will recognize that the equivalents of such linear and circular dimensions can be readily determined for any geometric shape. The size and shape of the systems and devices and their components may depend, at least, on the anatomical structure of the subject with whom the systems and devices are to be used, the size and shape of the components with which the systems and devices are to be used, and the method and procedure with which the systems and devices are to be used.

[0016] Backing up and synchronizing data on non-destructive testing (NDT) devices, such as borescope data from a borescope, is currently a manual process. This can be done by using a graphic user interface (GUI) to navigate to the data to be synchronized and then uploading the data to a remote server or copying the data to a larger external drive. This is time-consuming, inefficient, and prone to human error. Large amounts of data are captured and generated during NDT inspections. Such data can include images and corresponding 3D data, measurements, human- or computer-generated annotations, menu-driven inspection (MDI) metadata, and other metadata related to the inspection.

[0017] This disclosure describes how this large amount of data from one or more NDT devices may be continuously synchronized automatically to a remote system without requiring user input. Data from the NDT devices is synchronized to the remote system. The data may include measurement images (images and corresponding 3D data). Alternatively or additionally, the data may include annotations and representations generated from human input and / or image processing algorithms, as well as information needed to create, modify, or delete the annotations and representations. Alternatively or additionally, the data may include MDI templates, images, reports, and MDI inspections, including all information needed to resume the MDI inspection. Alternatively or additionally, the software uploads other videos and images stored on the device.

[0018] 1 is a flow diagram of an example method 100 that may be used according to aspects of the present disclosure. At 102, a first data set is received by a non-destructive testing (NDT) device from a remote system. Communication between various components described within the present disclosure is illustrated in FIG. 2. Receiving the first data set from the remote system may include providing the first data set characterizing the inspection template from the remote system to the NDT device. The remote system may take many forms, such as a remote server, a cloud server, a remote hard drive, or any device with non-transitory memory / storage capable of communicating with the NDT device from a remote location.

[0019] At 104, a second data set is received by the NDT device from a sensor on the NDT device. Receiving such data from the sensor may occur, for example, when performing an inspection with the NDT device. An example of such an NDT device is illustrated and described with respect to FIG.

[0020] At 106, upon receiving the second data set, the first data set and the second data set are synchronized to create a synchronized data set. To accomplish this, the first data set and the second data set are compared, and any differences between the first data set and the second data set are identified. A data set including elements of both the first data set and the second data set is then provided. Such synchronization occurs automatically during the inspection. The synchronization occurs between the NDT device and the remote system, such that a synchronized data set exists on both the NDT device and the remote system. While synchronization between a single NDT device and the remote system has been described above, additional NDT devices may be synchronized with the remote system and / or with each other, as described below. In some implementations, synchronizing the data first data set and the second data set includes providing, by the NDT device, a second data set from the NDT device to the remote system, the second data set characterizing the information content of the NDT device. The resulting synchronized data set may include the inspection template, images or videos, metadata, annotations made by the inspector, and / or measurements. Alternatively or additionally, the synchronized data may include a designated file naming scheme, which may include information such as date, location, NDT device used, or other identifying information. Alternatively or additionally, metadata may be used to store such information.

[0021] 2 is a block diagram of an example communication that may be used by aspects of the present disclosure. A first data set 252 is transmitted from a remote system 200 to an NDT device 202. When an inspection begins, a second data set 254 is received by the NDT device 202 from an NDT device sensor 204. The first data set 252 and the second data set 254 are then synchronized to create a synchronized data set 256 that is exchanged between the remote system 200 and the NDT device 202. This process is repeated during the inspection operation as more data is acquired by the sensor 204.

[0022] In some embodiments, a second NDT device 206 is used together with the first NDT device 202 during an inspection operation. In such an example, a first data set 253 is received by the second NDT device 206 from the remote system 200. The first data set 253 received by the second NDT device 206 may be identical to, similar to, or different from the first data set 252 received by the first NDT device 202. For example, the first data set 253 received by the second NDT device 206 may include a template for a different inspection route or the same template for the same inspection route as received by the first NDT device 202. As the inspection operation progresses, a third data set 258 is received by the second NDT device 206 from a sensor 208 on the second NDT device 206. In response to receiving the third data set 258, the first data set (252, 253), the second data set 254, and the third data set 258 may be synchronized to create a second synchronized data set 260. This second synchronized data set 260 is then automatically synchronized between the first NDT device 202, the second NDT device 206, and the remote system 200 such that the second set of synchronized data sets 260 is present in the first NDT device 202, the second NDT device 206, and the remote system 200. Such synchronization occurs automatically during testing.

[0023] FIG. 3 illustrates an example controller 300 that may be used in conjunction with some aspects of the present subject matter, for example, as a controller for NDT device 202. In some implementations, the controller may perform all or a portion of method 100 described throughout this disclosure. Controller 300 may, among other things, monitor system parameters and send signals to actuate and / or adjust various operating parameters of such system. As shown in FIG. 3 , controller 300 may include one or more processors 350 and a non-transitory computer-readable memory storage device (e.g., memory 352) that includes instructions that cause processor 118 to perform operations. Processor 118 is coupled to an input / output (I / O) interface 354 for sending and receiving communications to and from components of the system, including, for example, sensor 109 and / or remote system 200. In some implementations, I / O interface 354 may include a wireless communication device. In certain examples, the controller 300 may additionally communicate status with, and send actuation and / or control signals to, one or more of the various system components of the system (e.g., including the light source or actuation system of the NDT device 202) and other sensors that provide signals to the system (e.g., pressure sensors, temperature sensors, vibration sensors, and other types of sensors).

[0024] The controller 300 may be implemented with various levels of autonomy. For example, in some examples, the controller 300 may determine that the dataset on the NDT device 202 differs from the dataset on the remote system 200, prompt the operator of the NDT device 202, and synchronize the data based on input from the operator. Alternatively or additionally, the controller 300 may determine that the dataset on the NDT device 202 differs from the dataset on the remote system 200 and then synchronize the data without input from the operator. The controller may also alert the operator if other conditions are met. For example, in examples where the memory of the controller 300 is determined to be at or above a specified threshold (e.g., 90%), the controller 300 may alert the operator and / or stop the automatic synchronization operation without input from the operator.

[0025] 4 is a diagram illustrating an exemplary NDT device in the form of a borescope 400. The borescope 400 may include a control unit 402 and an inspection tube 403. The inspection tube 403 may include a conduit section 404, a bendable and actuable articulating portion or section 406, and an inspection head 408. In one embodiment, the sections 404, 406, and 408 may have different lengths and may be integral with or detachable from one another. As shown, the conduit section 404 is suitable for insertion into a variety of different targets, such as inside turbomachinery, equipment, pipes, conduits, underwater locations, curves, bends, inside or outside aircraft systems, etc.

[0026] The borescope 400 may include a probe driver 409 coupled to the conduit section 404. The probe driver 409 may include an actuator (not shown) configured to translate and / or rotate one or more of the sections 404, 406, 408 (e.g., to facilitate insertion of the inspection head 408 into a target). Additionally or alternatively, the orientation / position of portions of the inspection head 408 (e.g., a camera, a light source, etc.) may be changed to obtain an inspection area image (e.g., an RGB image, an IR image, etc.). The control unit 402 may include a control unit housing 410, the controller 300, a directional input 414, and a screen 416. As previously described, the controller 300 may include a processor 350 and a readable memory 352 containing computer-readable instructions that can be executed by the processor 350 to operate the borescope 400. The computer-readable instructions may include an inspection plan based on which the borescope 400 or portions thereof (e.g., the conduit section 404, the bendable articulation section 406, and the inspection head 408) may be translated / rotated (e.g., by the probe driver 409). In some implementations, the operation of the probe driver 409 may be based on control signals (e.g., generated by the controller 300 based on user input, such as via a GUI display space of the inspection plan / screen 416 or a computing device).

[0027] The controller 300 may be communicatively coupled to the control unit 402 via one or more cables 421. The controller 300 may also be disposed within the control unit housing 410 or may be disposed external to the control unit housing 410. In some implementations, the directional input 414 may be configured to receive user input (e.g., directional control) to the control unit 402 for operating the borescope 400. The screen 416 may display visual information being received by a camera (including a light sensor) disposed on the inspection head 408, thereby allowing a user to better guide the borescope 400 using the directional input 414. The directional input 414 and the screen 416 may be communicatively coupled to the controller 300 via one or more cables 421, which may be a wired connection or a wireless signal such as Wi-Fi or Bluetooth. In one implementation, inspection data and / or notifications (e.g., notifications based on the inspection data as described above) may be presented on the screen 416. Further details regarding controller 300 are provided later in this disclosure.

[0028] The conduit section 404 may include a tubular housing 422 having a proximal end 424 and a distal end 426. The tubular housing 422 may be a flexible member along its entire length, or may be rigid at the proximal end 424 and more flexible along the length of the conduit section 404 toward the distal end 426. In certain embodiments, the tubular housing 422 may be formed from a non-porous material to prevent contaminants from entering the borescope 400 through the conduit section 404.

[0029] The control unit 402 may be disposed at a proximal end 424 of the tubular housing 422, while the bendable articulation section 406 may be disposed at a distal end of the tubular housing 422. The bendable articulation section 406 may include a bendable neck 428 and a washer 130. The bendable neck 428 may be disposed at the distal end 426 of the tubular housing 422 and may move 360° in the YZ plane. The bendable neck 428 may be encased in a non-porous material to prevent contaminants from entering the borescope 400 through the bendable articulation section 406.

[0030] The inspection head 408 may include a light source 434 (e.g., an LED or a fiber optic bundle with a light at its proximal end), a camera 436 (or multiple cameras, such as a visible light camera, an IR camera, etc.), and one or more sensors 204, which may be configured to collect data about the surrounding environment. The camera 436 of the borescope 400 may present images and videos suitable for inspection on the screen 416 of the control unit 402. The light source 434 may be used to provide illumination when the inspection head 408 is disposed in low-light or no-light locations. The sensors 204 may record data including temperature data, distance data, separation data (e.g., the distance between a rotating element and a stationary element), flow rate data, etc.

[0031] In certain embodiments, the borescope 400 includes one or more interchangeable inspection heads 408. The inspection heads 408 may include tips with different optical properties, such as focal length, stereoscopic vision, three-dimensional (3D) phase view, shadow view, etc. Additionally or alternatively, the inspection head 408 may include removable and interchangeable portions of the inspection head 408. As such, the head section 408, the bendable neck 428, and the conduit section 404 may be provided with a variety of diameters, ranging from approximately 1 millimeter to 10 millimeters or more.

[0032] During use, the bendable articulation section 406 and the probe driver 409 may be controlled, for example, by control inputs (e.g., relative control gestures, physical manipulation devices) from the directional input 414 and / or by control signals generated by the controller 300. The directional input may be a joystick, D-pad, touchpad, trackball, optical sensor, or touchscreen on the screen 416. The directional input 414 may also be a similar device located outside the control unit housing 410 and connected by wired or wireless means. In particular, a single set of control inputs may be used to control the bendable articulation section 406 and / or the probe driver 409. The bendable articulation section 406 may be steered, or "bend," in various dimensions, while the conduit section 404 may be translated and / or rotated using any combination of actuators and wires located within the control unit 402 to adjust the orientation (e.g., alignment) of the inspection head 408. In some implementations, the control / direction inputs 414 may be generated by a controller based on a test plan.

[0033] The actuators may be electrically, pneumatically, or ultrasonically operated motors or solenoids, shaped alloys, electroactive polymers, dielectric elastomers, polymer muscle materials, or other materials. For example, the bendable articulation section 406 and probe driver 409 may enable movement of the inspection head 408 in the XY, XZ, and / or YZ planes. Indeed, the directional input 414 may be used to implement control operations suitable for positioning the inspection head 408 at various angles, such as the angle α shown. In this manner, the inspection head 408 may be positioned for visual inspection of a desired location.

[0034] Once the inspection head 408 is in the desired position, the camera 436 may operate, for example, to capture still or continuous visual images, which may be displayed on a screen 416 of the control unit 402 and recorded by the borescope 400. In an embodiment, the screen 416 may be a multi-touch touchscreen that uses capacitive, resistive, infrared grid, or the like technology to detect the touch of a stylus and / or one or more human fingers. Additionally or alternatively, the captured visual images may be synchronized with the remote system 200 for later reference.

[0035] In some embodiments, the source code may be human-readable code that may be written in a programming language such as Python, C++, etc. In some embodiments, the computer-executable code may be machine-readable code that may be generated by compiling one or more source codes. The computer-executable code may be executed by an operating system (e.g., Linux, Windows, Mac, etc.) of a computing device or distributed computing system. For example, the computer-executable code may include data needed to create a runtime environment (e.g., binary machine code) that may be executed by a processor of a computing system or distributed computing system.

[0036] Other embodiments are within the scope and spirit of the disclosed subject matter. For example, the methods for generating integrated data sets described herein may be used in facilities with complex machines having multiple operating parameters. The use of the words "optimize" / "optimizing" in this application may mean "improve" / "improving."

[0037] Specific embodiments will now be described to provide a thorough understanding of the principles of the structure, function, manufacture, and use of the systems, devices, and methods disclosed herein. One or more examples of these embodiments are illustrated in the accompanying drawings. Those skilled in the art will understand that the systems, devices, and methods explicitly described herein and illustrated in the accompanying drawings are non-limiting exemplary embodiments, and that the scope of the present invention is defined solely by the claims. Features illustrated or described in connection with one exemplary embodiment may be combined with features of other embodiments. Such modifications and variations are intended to be included within the scope of the present invention. Furthermore, in this disclosure, like-named components of embodiments generally have similar features, and therefore, each feature of each like-named component within a particular embodiment has not necessarily been fully described in detail.

[0038] The subject matter described herein may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, or in combinations thereof, including the structural means disclosed herein and their structural equivalents. The subject matter described herein may also be implemented as one or more computer program products, such as one or more computer programs tangibly embodied in an information carrier (e.g., in a machine-readable storage device) or embodied in a propagated signal, for execution by or to control the operation of a data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). Computer programs (also known as programs, software, software applications, or code) can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, such as as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program can be stored as a portion of a file that holds other programs or data, in a single file dedicated to the program, or in multiple coordinated files (e.g., files storing one or more modules, subprograms, or portions of code). A computer program can be deployed to be executed on one computer, on multiple computers at one site, or distributed across multiple sites and interconnected by a communications network.

[0039] The processes and logic flows described herein, including method steps of the subject matter described herein, may be performed by one or more programmable processors executing one or more computer programs to perform functions of the subject matter described herein by operating on input data and generating output. The processes and logic flows may also be performed by special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit), and apparatus of the subject matter described herein may be implemented as such special purpose logic circuitry.

[0040] Processors suitable for executing a computer program include, by way of example, both general-purpose and special-purpose microprocessors, and any one or more processors of any kind of digital computer. Typically, a processor will receive instructions and data from a read-only memory or a random-access memory, or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices, such as magnetic, magneto-optical, or optical disks, for storing data, or be operatively coupled to receive data from, transfer data to, or both. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including, by way of example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and optical disks (e.g., CD and DVD disks). The processor and memory may be supplemented by, or incorporated in, special-purpose logic circuitry.

[0041] To provide for interaction with a user, the subject matter described herein may be implemented on a computer having a display device, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user, as well as a keyboard and pointing device (e.g., a mouse or trackball) by which the user may provide input to the computer. Other types of devices may also be used to provide interaction with a user. For example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user may be received in any form, including acoustic, speech, or tactile input.

[0042] The techniques described herein may be implemented using one or more modules. As used herein, the term “module” refers to computing software, firmware, hardware, and / or various combinations thereof. However, at a minimum, a module should not be interpreted as software not implemented on hardware, firmware, or a non-transitory processor-readable, recordable storage medium (i.e., the module is not software itself). Indeed, a “module” should always be interpreted to include at least some physical non-transitory hardware, such as a processor or part of a computer. Two different modules may share the same physical hardware (e.g., two different modules may use the same processor and network interface). The modules described herein can be combined, integrated, separated, and / or replicated to support various applications. Also, functions described herein as being performed by a particular module may be performed by one or more other modules and / or by one or more other devices instead of, or in addition to, the functions performed by the particular module. Furthermore, modules may be implemented across multiple devices and / or other components, local or remote from each other. Additionally, modules can be moved from one device and added to another device and / or incorporated into both devices.

[0043] The subject matter described herein may be implemented in a computing system that includes back-end components (e.g., data servers), middleware components (e.g., application servers), or front-end components (e.g., client computers having graphical user interfaces or web interfaces through which users can interact with embodiments of the subject matter described herein), or any combination of such back-end, middleware, and front-end components. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), e.g., the Internet.

[0044] As used herein throughout the specification and claims, approximation may be applied to modify any quantitative expression that can be permissibly varied without resulting in a change in the basic function to which it relates. Thus, values modified by terms such as "about" and "substantially" are not limited to the exact value specified. In at least some instances, approximation may correspond to the precision of the instrument used to measure the value. Range limitations may be combined and / or interchanged herein throughout the specification and claims, but such ranges are identified and include all subranges contained therein unless the context or language dictates otherwise.

Claims

1. 1. A method comprising: receiving, by a non-destructive testing (NDT) device, a first data set from a remote system; receiving, by the NDT device, a second data set from a sensor on the NDT device; responsive to receiving the second data set, synchronizing the first data set and the second data set by comparing the first data set and the second data set to create a synchronized data set, identifying differences between the first data set and the second data set, and providing a data set including elements of both the first data set and the second data set, wherein the synchronization occurs automatically during an inspection, and wherein the synchronization occurs between the NDT device and the remote system, and wherein the synchronized data set exists in both the NDT device and the remote system; A method comprising:

2. the NDT device is a first NDT device, the synchronized dataset is a first synchronized dataset, and the method comprises: receiving the first data set from the remote system by a second NDT device; receiving, by the second NDT device, a third data set from a sensor on the NDT device; In response to receiving the third data set, synchronizing the first data set, the second data set, and the third data set between the first NDT device, the second NDT device, and the remote system to automatically create a second synchronized data set during the inspection, such that the second set of synchronized data sets exists at the first NDT device, the second NDT device, and the remote system; The method of claim 1 further comprising:

3. Synchronizing the first data set and the second data set includes: The method of claim 1 , comprising providing, by the NDT device, the second data set characterizing the information content of the NDT device to the remote system.

4. receiving the first data set from the remote system; The method of claim 1 , comprising providing the first data set characterizing an inspection template to the NDT device from the remote system.

5. receiving data from the sensor; The method of claim 1 , further comprising performing a test.

6. the synchronized data set is Images or videos, metadata, Annotations made by the inspector, or The method of claim 1 , comprising measurements.

7. The method of claim 1 , wherein the synchronized data includes a specified file naming convention.

8. 1. A system comprising: at least one data processor; a non-transitory memory storing instructions that, when executed by the at least one data processor, cause the at least one data processor to perform operations, the operations including: receiving a first data set from a remote system by a non-destructive testing (NDT) device; receiving, by the NDT device, a second data set from a sensor on the NDT device; responsive to receiving the second data set, synchronizing the first data set and the second data set by comparing the first data set and the second data set to create a synchronized data set, identifying differences between the first data set and the second data set, and providing a data set that includes elements of both the first data set and the second data set, wherein the synchronization occurs automatically during an inspection, and wherein the synchronization occurs between the NDT device and the remote system, such that the synchronized data set exists on both the NDT device and the remote system; Including, the system.

9. the NDT device is a first NDT device, the synchronized data set is a first synchronized data set, and the operation comprises: receiving the first data set from the remote system by a second NDT device; receiving, by the second NDT device, a third data set from a sensor on the NDT device; In response to receiving the third data set, synchronizing the first data set, the second data set, and the third data set between the first NDT device, the second NDT device, and the remote system to automatically create a second synchronized data set during the inspection, such that the second set of synchronized data sets exists at the first NDT device, the second NDT device, and the remote system; The system of claim 8 further comprising:

10. Synchronizing the first data set and the second data set includes: The system of claim 8 , including providing, by the NDT device, the second data set characterizing the information content of the NDT device to the remote system.

11. receiving the first data set from the remote system; The system of claim 8 , further comprising providing the first data set characterizing an inspection template to the NDT device from the remote system.

12. receiving data from the sensor; The system of claim 8 , further comprising: performing a test.

13. the synchronized data set is Images or videos, metadata, Annotations made by the inspector, or The system of claim 8 including measurements.

14. The system of claim 8 , wherein the synchronized data includes a specified file naming convention.

15. A non-transitory computer-readable memory storing instructions that, when executed by at least one data processor forming part of at least one computing system, cause the at least one data processor to perform operations, the operations including: receiving a first data set from a remote system by a non-destructive testing (NDT) device; receiving, by the NDT device, a second data set from a sensor on the NDT device; responsive to receiving the second data set, synchronizing the first data set and the second data set by comparing the first data set and the second data set to create a synchronized data set, identifying differences between the first data set and the second data set, and providing a data set including elements of both the first data set and the second data set, wherein the synchronization occurs automatically during an inspection, and wherein the synchronization occurs between the NDT device and the remote system, such that the synchronized data set exists on both the NDT device and the remote system; a non-transitory computer readable memory including:

16. the NDT device is a first NDT device, the synchronized data set is a first synchronized data set, and the operation comprises: receiving the first data set from the remote system by a second NDT device; receiving, by the second NDT device, a third data set from a sensor on the NDT device; In response to receiving the third data set, synchronizing the first data set, the second data set, and the third data set between the first NDT device, the second NDT device, and the remote system to automatically create a second synchronized data set during the inspection, such that the second set of synchronized data sets exists at the first NDT device, the second NDT device, and the remote system; 16. The non-transitory computer-readable memory of claim 15, further comprising:

17. Synchronizing the first data set and the second data set includes: The non-transitory computer-readable memory of claim 15 , further comprising providing, by the NDT device, the second data set characterizing information content of the NDT device to the remote system.

18. receiving the first data set from the remote system; The non-transitory computer-readable memory of claim 15 , further comprising providing the first data set characterizing an inspection template from the remote system to the NDT device.

19. the synchronized data set is Images or videos, metadata, Annotations made by the inspector, or 16. The non-transitory computer-readable memory of claim 15, comprising measurements.

20. 16. The non-transitory computer-readable memory of claim 15, wherein the synchronized data includes a specified file nomenclature.

Images