Methods for verifying and validating structural nonconformities and abnormalities

Abstract

This provides a method for verifying and validating structural non-conformities and abnormalities. [Solution] Disclosed are anomaly artifacts and related methods for generating and using anomaly artifacts to support structural anomaly inspection activities. Anomaly artifacts include anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information, which are integrated into a single structured reference usable during anomaly inspection activities. Anomaly location information may include map-based location information mapped to a digital representation of the structure, which may be subdivided into zones such that anomalies are represented by zone-specific anomaly artifacts.

Description

Technical Field

[0001] Cross-Reference to Related Applications This application claims the benefit of priority from U.S. Provisional Patent Application No. 63 / 765,175, filed on February 28, 2025, which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates generally to documenting nonconformity anomalies in structures, and more specifically to nonconformity anomaly artifacts and associated methods.

Background Art

[0003] Management of nonconformity (NC) anomalies in large or complex structures such as aircraft, rockets, microchips, and other assemblies can present significant challenges due to the volume, distribution, and complexity of anomalies. Conventional anomaly communication systems, such as quality management systems (QMS), often store anomaly data in fragmented, disjointed, or cumbersome formats, and lack an integrated format that organizes anomaly information in a manner suitable for efficient inspection preparation and performance. Anomaly data is often distributed across multiple data sources (e.g., databases, spreadsheets, reports), requiring inspectors to manually compile and interpret data before performing an inspection. This fragmented approach increases the risk of oversights, extends inspection preparation time, and complicates anomaly resolution efforts. In addition, inspections are often performed at a whole-item level rather than a local (e.g., zone-specific) level, making it difficult and costly to efficiently verify large or complex anomalies in an organized manner.

Summary of Invention

[0004] The subject matter of this application was developed in accordance with the latest technology, in particular in response to the shortcomings associated with conventional anomaly communication and documentation methods that have not yet been fully resolved by currently available technologies. Accordingly, the subject matter of this application was developed to provide non-conforming anomaly artifacts and related methods for generating and using them, which overcome at least some of the aforementioned shortcomings of the prior art.

[0005] The following is a non-exhaustive list of examples of subject matter disclosed herein that may or may not be claimed.

[0006] This specification discloses a method for generating anomaly artifacts to support structural anomaly inspection activities. The method includes the steps of: aggregating anomaly data from one or more anomaly data sources to generate structured anomaly data about anomalies; generating anomaly artifacts about anomalies as a single reference usable during anomaly inspection activities based on the structured anomaly data; and storing and selectively updating the anomaly artifacts in an anomaly management system to maintain an accurate current representation of the anomaly. The anomaly artifacts include anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information. The aforementioned subject matter of this paragraph characterizes Example 1 of this disclosure.

[0007] The step of generating an anomaly artifact further includes the step of capturing the anomaly artifact using a predetermined artifact template having a standardized configuration of anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information. The subject matter described above in this paragraph characterizes Example 2 of the present disclosure, which also includes the subject matter of Example 1 described above.

[0008] Anomaly location information includes map-based localization information mapped to a digital representation of the structure to indicate the spatial location of anomalies within the structure, the digital representation of the structure being subdivided into multiple zones, and the anomaly artifact being associated with at least one of the multiple zones based on the anomaly location information. The subject matter described above in this paragraph characterizes Example 3 of the present disclosure, which also includes the subject matter described in Example 1 or 2 above.

[0009] When an anomaly extends to several of several zones, the method further includes the step of generating zone-specific anomaly artifacts of the anomaly, each zone-specific anomaly artifact corresponding to one of the several zones. The subject matter described above in this paragraph characterizes Example 4 of the present disclosure, which also includes the subject matter of Example 3 described above.

[0010] The step of generating anomalous artifacts includes the step of automatically generating anomalous artifacts based on structured anomalous data. The subject matter described above in this paragraph characterizes Example 5 of the present disclosure, which also includes the subject matter of any one of Examples 1-4 above.

[0011] The step of generating an anomalous artifact includes the step of manually generating an anomalous artifact based on structured anomalous data. The subject matter described above in this paragraph characterizes Example 6 of the present disclosure, which also includes the subject matter of any one of Examples 1-4 above.

[0012] The step of generating an anomalous artifact further includes a step of including at least one of the following: at least one image associated with the anomalous artifact, a severity level of the anomalous artifact, a classification of the anomalous artifact, or anomalous metadata associated with the anomalous artifact. The subject matter described herein is characteristic of Example 7 of the present disclosure, which also includes the subject matter of any one of Examples 1-6 above.

[0013] The step of selectively updating anomaly artifacts includes at least one of the following steps: updating anomaly description information, updating anomaly check information, or updating anomaly location information. The subject matter described above in this paragraph characterizes Example 8 of the present disclosure, which also includes the subject matter described in any one of Examples 1-7 above.

[0014] The method further includes the step of structuring anomaly artifacts to have interoperability between multiple anomaly management systems in order to support inspection-related activities across different inspection contexts, wherein the anomaly management system is one of the multiple anomaly management systems. The subject matter described above in this paragraph characterizes Example 9 of the present disclosure, which also includes the subject matter of any one of Examples 1 to 8 above.

[0015] A method for using anomaly artifacts to support structural anomaly inspection activities is further disclosed herein. The method includes the steps of: aggregating anomaly data from one or more anomaly data sources to generate structured anomaly data about anomalies; generating anomaly artifacts about anomalies as a single reference usable during anomaly inspection activities based on the structured anomaly data; and storing and selectively updating the anomaly artifacts in an anomaly management system to maintain an accurate current representation of the anomaly. The method also includes the steps of: mapping anomaly location information of an anomaly artifact to a digital representation of the structure in order to provide the spatial context of the anomaly; and providing the anomaly artifacts to at least one user to support anomaly inspection activities. The anomaly artifacts include anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information. The aforementioned subject matter of this paragraph characterizes Example 10 of the present disclosure.

[0016] The step of mapping anomalous location information includes the step of including the mapped location information within the anomalous artifact. The subject matter described above in this paragraph characterizes Example 11 of the present disclosure, which also includes the subject matter described in Example 10 above.

[0017] The digital representation of the structure is subdivided into multiple zones, and the step of mapping anomalous location information further includes the step of associating the anomalous artifact with at least one of the multiple zones. The subject matter described above in this paragraph characterizes Example 12 of the present disclosure, which also includes the subject matter described in either Example 10 or 11 above.

[0018] When an anomaly extends to several of several zones, the method further includes the step of generating several zone-specific anomaly artifacts of the anomaly, each zone-specific anomaly artifact corresponding to one of the several zones. The subject matter described above in this paragraph characterizes Example 13 of the present disclosure, which also includes the subject matter of Example 12 above.

[0019] The step of providing an anomaly artifact to at least one user includes presenting anomaly location information to guide at least one user to a specific zone among a plurality of zones of a digital representation corresponding to a region of the structure in which the anomaly is located. The subject matter described above in this paragraph characterizes Example 14 of the present disclosure, which also includes the subject matter described in Example 13 above.

[0020] Anomaly artifacts for supporting structural anomaly inspection activities are further disclosed herein. Anomaly artifacts include anomaly identification information, which includes a unique anomaly identifier for the anomaly; anomaly description information, which describes the anomaly; anomaly inspection information, which defines one or more actions taken to inspect the anomaly; and anomaly location information, which indicates where the anomaly is located within the structure. The anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information are integrated into a single reference available during anomaly inspection activities. The aforementioned subject matter of this paragraph characterizes Example 15 of the present disclosure.

[0021] An anomaly artifact further includes at least one image associated with the anomaly, the at least one image showing the anomaly or the region of the structure in which the anomaly is located. The subject matter described above in this paragraph characterizes Example 16 of the present disclosure, which also includes the subject matter described in Example 15 above.

[0022] An anomalous artifact further includes metadata associated with the anomalous artifact, the metadata including at least one of the following: revision status, creation timestamp, modification timestamp, or user identifier associated with the modification. The subject matter described herein is used to characterize Example 17 of the present disclosure, which also includes the subject matter described in either Example 15 or 16 above.

[0023] Anomaly location information includes map-based location information mapped to a digital representation of the structure to indicate the spatial location of anomalies within the structure. The subject matter described above in this paragraph characterizes Example 18 of the present disclosure, which also includes the subject matter described in any one of Examples 15–17 above.

[0024] The digital representation of the structure is subdivided into multiple zones, and the anomaly location information associates the anomaly with at least one of the multiple zones. The subject matter described above in this paragraph characterizes Example 19 of the present disclosure, which also includes the subject matter described in Example 18 above.

[0025] When an anomaly affects several of multiple zones, the anomaly artifact is generated as one of several zone-specific anomaly artifacts, each zone-specific anomaly artifact corresponding to one of those zones. The subject matter described above in this paragraph characterizes Example 20 of the present disclosure, which also includes the subject matter described in Example 19 above.

[0026] The described features, structures, advantages, and / or characteristics of the subject matter of the present disclosure may be combined in any suitable manner in one or more examples and / or implementations. In the following description, numerous specific details are provided to give a thorough understanding of examples of the subject matter of the present disclosure. Those skilled in the art will recognize that the subject matter of the present disclosure may be practiced without one or more of the specific features, details, components, materials, and / or methods of a particular example or implementation. In other examples, additional features and advantages may be recognized in particular examples and / or implementations that may not be present in all examples or implementations. Further, in some instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the subject matter of the present disclosure. The features and advantages of the subject matter of the present disclosure will become more fully apparent from the following description and the appended claims, or may be learned by practice of the subject matter set forth below.

[0027] In order that the advantages of the subject matter may be more readily understood, a more particular description of the subject matter briefly described above is provided by reference to specific examples illustrated in the accompanying drawings. It should be understood that these drawings, which are not necessarily drawn to scale, depict only certain examples of the subject matter, and therefore should not be considered as limiting the scope thereof. The subject matter will be described and explained with additional specificity and detail through the use of the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] [Figure 1] Fig. 1 is a schematic flow diagram of a method for generating an anomaly artifact to support inspection activities for structural anomalies in accordance with one or more examples of the present disclosure. [Figure 2] Fig. 2 is a schematic flow diagram illustrating aggregation of anomaly data, generation of an anomaly artifact, and storage of the anomaly artifact in accordance with one or more examples of the present disclosure. [Figure 3A] Fig. 3 is a schematic block diagram illustrating an anomaly artifact in accordance with one or more examples of the present disclosure. [Figure 3B]This is a schematic representative diagram showing an example of an anomaly artifact into which anomaly-related information has been incorporated, based on one or more examples of the present disclosure. [Figure 4] This is a schematic representative diagram of a digital representation of a structure, illustrating the map-based localization of anomalies, as shown in one or more examples of the present disclosure. [Figure 5A] This is a schematic representative diagram of a digital representation of a structure subdivided into multiple zones, illustrating the association between anomalies and zones, as shown in one or more examples of the present disclosure. [Figure 5B] This is a schematic representative diagram of the digital representation of Figure 5A, illustrating the subdivision of an anomaly spanning multiple zones into multiple zone-specific anomaly artifacts, as shown in one or more examples of the present disclosure. [Figure 6] This is a schematic flowchart illustrating how anomaly artifacts are used to support structural anomaly inspection activities, as illustrated by one or more examples of the present disclosure. [Modes for carrying out the invention]

[0029] Throughout this specification, any reference to “one example,” “one example,” or similar wording means that the particular features, structure, or characteristic described in relation to the example is included in at least one example of this disclosure. Throughout this specification, any occurrence of the phrases “one example,” “one example,” and similar wording may, though not necessarily, all refer to the same example. Similarly, the use of the term “implementation” means an implementation having a particular feature, structure, or characteristic described in relation to one or more examples of this disclosure, although an implementation may be associated with one or more examples if there is no clear correlation indicating otherwise.

[0030] This specification discloses nonconforming anomaly artifacts and related methods for generating and using them. As used herein, a nonconforming (NC) anomaly refers to a deviation from a given design, manufacture, or operating specification, including, but not limited to, defects, malfunctions, and other conditions affecting the performance, integrity, reliability, or appearance of a structure. NC anomalies, hereafter referred to as “anomalies,” may arise from manufacturing inconsistencies, material degradation, assembly errors, environmental damage, operating stresses, fatigue, or other factors that cause a component or system to fall outside acceptable tolerances. Anomalies can vary in size and severity, ranging from small surface defects to large structural anomalies requiring extensive corrective action.

[0031] The disclosed anomaly artifacts and methods provide an improved approach to organizing, contextualizing, and communicating anomaly-related information by treating the anomaly artifact itself as a primary inspection support object. The anomaly artifact functions as an integrated and structured reference that aggregates anomaly information from one or more data sources (e.g., a quality management system (QMS)) into a single, standalone artifact usable during inspection activities such as anomaly verification. In a standardized configuration, the anomaly artifact carries anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information, thereby reducing reliance on users (e.g., inspectors) to manually reconcile information dispersed across multiple systems or documents. In this way, the anomaly artifact can function as a foundational reference for anomaly inspection activities and can be used consistently across different systems or operating conditions, including QMS and non-QMS environments, while maintaining traceability of anomaly-related information.

[0032] In some examples, anomalous artifacts are further enhanced by map-based localization, where anomalous location information is mapped to a digital representation of the structure to provide spatial context. The digital representation can be subdivided into a given zone, allowing for a local representation of the anomaly and, in some cases, the subdivision of a single anomaly into multiple zone-specific anomalous artifacts.

[0033] The disclosed anomalous artifacts and associated methods may be beneficial for large and / or complex structures and assemblies, such as aircraft, ships, industrial equipment, or large infrastructure components, where anomalous information is often geographically dispersed and / or operationally complex. By providing a standardized artifact-centric approach that integrates anomalous information and, in some cases, combines it with its spatial context, the disclosed subject matter may reduce inspection preparation effort, improve coordination across distributed teams and systems, and support more efficient and localized inspection activities.

[0034] Referring to Figure 1, one embodiment illustrates a method 100 for generating anomaly artifacts to support inspection activities for structural anomalies. Method 100 focuses on collecting, organizing, and integrating anomaly-related information into a single reference usable during inspection activities. As used herein, “inspection activity” means one or more organization-defined activities performed in relation to an anomaly in order to evaluate, assess, document, and / or resolve the anomaly to a structure. Inspection activities may include, for example, confirming the identification of an anomaly, confirming the identification of an anomaly, confirming the location of the anomaly on the structure, inspecting the anomaly to determine whether the reported condition is present or absent, collecting observations or measurements, documenting inspection results, determining or recording actions to be taken regarding the anomaly (e.g., current acceptance, rework, repair, replacement, postponement), implementing or adjusting corrective actions associated with the anomaly, documenting the completion of corrective actions, and confirming or verifying that corrective actions have been completed and / or the anomaly has been resolved. The scope, sequence, and content of inspection activities may vary depending on organizational practices, regulatory or contractual requirements, the purpose of the inspection, or the context in which it applies. In some examples, the inspection activity may be limited to determining whether an abnormal condition exists or not at a particular location (e.g., presence verification). In other examples, the inspection activity may include additional inspections, actions, corrective actions, and / or verification steps performed before, during, or after corrective actions. The inspection activity is supported, but not limited to, the behavior defined by the abnormal inspection information contained within the abnormal artifact (see, for example, Figure 3A).

[0035] Anomaly artifacts are intended to be used throughout the entire anomaly inspection lifecycle, including during verification and corrective action activities, until the anomaly is corrected or otherwise resolved. The disclosed method does not perform inspection or corrective action, but instead prepares and maintains anomaly-related information in a way that supports such activities.

[0036] Method 100 is applicable to a wide range of structures, including but not limited to aircraft, ships, industrial machinery, microchips, and large-scale infrastructure components. Such structures are often complex, geographically dispersed, and comprise numerous interconnected parts or subsystems. In large and / or complex structures, anomaly-related information is often generated by multiple organizations, tools, or processes, resulting in fragmented information across the system that is difficult to interpret in a unified manner. For example, anomaly-related information may be generated during manufacturing, assembly, inspection, maintenance, or repair activities, and may originate from multiple organizations, systems, or processes operating across different locations in the structure. As a result, anomaly-related information can frequently be fragmented across different systems and formats, making it difficult to interpret in a unified, spatially meaningful manner.

[0037] As shown in the figures herein, Method 100 is described using an aircraft as an exemplary structure to illustrate how anomaly information can be aggregated, organized, and contextualized for inspection preparation and use. However, the disclosed subject matter is not limited to aircraft, and the same technique may be applied to other types of structures with similar complexity or inspection needs. Method 100 addresses these challenges by generating an artifact-centric representation of anomaly information that can be used consistently across inspection contexts without requiring inspectors or other users to manually reconcile information from different sources.

[0038] Referring generally to Figure 1, and more specifically to Figure 2, Method 100 includes the step in block 102 of aggregating anomaly data from one or more anomaly data sources 120. Anomaly data sources 120 refer to any system, platform, or repository that stores anomaly-related information, including but not limited to quality management systems (QMS), manufacturing execution systems, inspection records, maintenance databases, reports, and document-based tracking tools. Often, anomaly data in such sources may be scattered across multiple records or formats and may lack a standardized configuration suitable for direct inspection use. In addition, in some cases, anomaly data sources 120 may be associated with different organizations, facilities, or networks associated with the manufacturing, inspection, maintenance, or repair of structures.

[0039] Aggregation involves collecting, compiling, and organizing anomaly-related information from one or more anomaly data sources 120 to generate structured anomaly data 122. The structured anomaly data 122 represents a normalized and standardized dataset derived from the aggregated anomaly data and may include, for example, anomaly identifiers, anomaly descriptions, severity indices, images, location-related information, and inspection-related guidance. In some examples, aggregation may further include selecting or filtering anomaly-related information relevant to a particular anomaly to prepare the information for consolidation into a single anomaly artifact. By aggregating anomaly data into structured anomaly data 122, Method 100 centralizes anomaly information and prepares it for use in generating a consolidated anomaly artifact, reducing the need for manual data adjustment and improving the overall consistency of inspection preparation activities. In some examples, aggregation in block 102 is performed per anomaly so that structured anomaly data 122 is generated for a particular anomaly and used to generate a corresponding anomaly artifact. In other examples, anomaly data from one or more anomaly data sources 120 is aggregated collectively and then organized or split to generate structured anomaly data 122 corresponding to individual anomalies.

[0040] Method 100 further includes the step in block 104 of generating an anomaly artifact 124 related to an anomaly based on structured anomaly data 122. The anomaly artifact 124 is generated as a structured standalone reference that consolidates anomaly-related information into a single reference usable during an anomaly inspection activity. The anomaly artifact 124 is derived from the structured anomaly data 122 and formatted to organize the anomaly information in a standardized, accessible way suitable for inspection preparation and use, rather than as a raw data record. In other words, the anomaly artifact 124 consolidates anomaly-related information that could otherwise be scattered across multiple systems or records into a single reference associated with a particular anomaly, thereby reducing the need for inspectors or other users to manually reconcile anomaly information from different sources before or during inspection activities. In some examples, the anomaly artifact 124 and the structured anomaly data 122 may contain overlapping information, but the anomaly artifact 124 presents the information in a form optimized for inspection preparation and communication.

[0041] In some examples, anomaly artifacts 124 are automatically generated based on structured anomaly data 122. Automatic generation is performed by an anomaly management system 126 using predetermined rules, templates, or processing logic, and the anomaly artifacts 124 may incorporate relevant anomaly-related information. In other examples, anomaly artifacts 124 are manually generated, with personnel reviewing the structured anomaly data 122 and inputting or organizing the anomaly-related information into the anomaly artifacts 124. In yet another example, automatic and manual generation may be combined so that the automatically generated anomaly artifacts 124 are reviewed, supplemented, or refined by personnel before use.

[0042] In some examples, the method includes the step of creating or configuring an artifact template for a specific application or inspection context. The artifact template may be configured based on application-specific requirements, anomaly types, or user needs by selecting sections to include, adjusting the layout of sections, or adjusting the protrusion of sections within the template. After the artifact template is configured for a specific application or inspection context, it is treated as a given artifact template for generating anomaly artifacts, such that anomaly-related information from structured anomaly data 122 is incorporated into anomaly artifacts 124 in a standardized configuration defined by the given artifact template.

[0043] In some examples, a given artifact template includes reserved fields, optional sections, or expandable regions that allow for the inclusion of additional anomaly-related information while maintaining a standardized configuration. In one non-exclusive example, a given artifact template employs a multi-region layout (e.g., four regions or a "four squares" arrangement) where different regions are designated for different categories of anomaly-related information.

[0044] Method 100 further includes the step in block 106 of storing and selectively updating anomaly artifacts 124 in an anomaly management system 126 in order to maintain an accurate current representation of the anomaly. That is, anomaly artifacts 124 are stored in an anomaly management system 126, which may have a digital platform, database, or repository configured to maintain anomaly artifacts and associated information. The anomaly management system 126 may assist in storing, retrieving, and selectively updating anomaly artifacts 124 so that each anomaly artifact reflects the most up-to-date available anomaly-related information as inspection activities progress. In this way, anomaly artifacts 124 provide an accurate current representation of the anomaly by incorporating updates resulting from inspection activities, changes in the description or location of the anomaly, or completion of corrective actions, while avoiding reliance on outdated or superseded information. In some examples, anomaly artifacts 124 may be exported or stored in offline formats, such as printed documents or locally managed digital files, for use in environments with limited network access or where physical documents are required. In such cases, the information recorded during the inspection activity may be subsequently incorporated into a digital version of the anomaly artifact 124, so that the anomaly artifact 124 maintained in the anomaly management system 126 reflects the current accurate representation of the anomaly, when connectivity is available.

[0045] In some examples, selectively updating the anomalous artifact 124 includes updating one or more parts of the anomalous artifact, such as updating the anomalous description information, updating the anomalous inspection information, or updating the anomalous location information, as additional information becomes available during the inspection activity. In this way, the anomalous artifact 124 is maintained as a single reference that is updated over time, rather than being replaced by multiple fragmented records.

[0046] Referring to Figures 3A and 3B, an anomaly artifact 124 is shown. Figure 3A shows a conceptual diagram of the anomaly artifact 124. Figure 3B shows a non-restrictive example of an anomaly artifact 124 having a defined format and incorporating anomaly-related information. As described above, the anomaly artifact 124 is a structured standalone reference that is generated for a specific anomaly and configured to integrate anomaly-related information into a single reference usable during inspection activities. Unlike raw anomaly data records, the anomaly artifact 124 is formatted to support inspection activities by presenting related information in an organized and accessible manner. The anomaly artifact 124 includes anomaly identification information 128, anomaly description information 130, anomaly inspection information 132, and anomaly location information 134. By integrating these categories of information into a single artifact, the anomaly artifact 124 reduces reliance on multiple systems or documents and supports efficient inspection activities. In some examples, the anomaly artifact 124 is generated, maintained, and presented by one or more computing systems that execute instructions configured to organize and present the anomaly-related information described herein.

[0047] In contrast to reports generated from raw anomaly records, database entries, or anomaly data sources, anomaly artifacts 124 are dedicated inspection references configured to organize and present anomaly-related information in a way that directly supports inspection activities. Anomaly artifacts are not merely storage containers for anomaly data, but structured representations designed to aggregate, contextualize, and communicate anomaly information as a unified reference during inspection. Anomaly artifacts 124 are configured to be usable across different inspection contexts, including manufacturing, inspection, maintenance, and repair environments, without requiring users to reconstruct anomaly information from multiple systems. This portability enables consistent inspection practices across organizations, facilities, and operational phases. A separate anomaly artifact 124 is generated for each individual anomaly, and the anomaly-related information for each anomaly is maintained as a different, independently usable reference during inspection activities.

[0048] Anomaly identification information 128 uniquely identifies an anomaly and may include, for example, a different alphanumeric code, serial number, reference number, or other designation that enables clear identification of the anomaly. Anomaly identification information 128 enables the association of all anomaly-related information within the anomaly artifact 124, supporting anomaly traceability across systems, records, and inspection activities, thereby reducing confusion and redundancy. In some examples, anomaly identification information 128 is captured from the anomaly data source during the aggregation of anomaly data and incorporated into the anomaly artifact 124. In other examples, anomaly identification information 128 is assigned automatically or manually in the anomaly management system 126. In some examples, anomaly identification information 128 is not intended to be modified after the initial creation of the anomaly artifact 124 to avoid confusion with other anomalies.

[0049] Anomaly description information 130 includes information that describes an anomaly and provides context to support the recognition and understanding of the anomaly during inspection activities. For example, anomaly description information 130 may include a text description, classification, severity index, or other descriptive information that characterizes the nature of the anomaly or the observed conditions associated with the anomaly. Anomaly description information 130 provides context to support the understanding of the anomaly during inspection activities. As shown in Figure 3B, anomaly description information 130 may include, for example, a text description 136 that describes the anomaly, a severity level 138 that indicates the relative importance or priority of the anomaly, and an anomaly classification 140 that identifies the type or category of the anomaly. These examples are provided for illustrative purposes only, and anomaly description information 130 is not limited to the categories shown. In other examples, anomaly description information 130 may include additional or alternative descriptive fields appropriate to a particular application, structure, or inspection context.

[0050] Anomaly inspection information 132 defines one or more actions to be performed during an anomaly inspection activity. Anomaly inspection information 132 may specify inspection steps, observation requirements, measurements to be taken, equipment to be used, or response selections to complete the inspection activity. For example, in some inspection contexts, the inspection activity may include verifying whether a reported condition exists or does not exist at a specified anomaly location (e.g., verification). In other inspection contexts, the inspection activity may include verifying that one or more corrective actions have been taken and that the anomaly condition has been addressed by applicable requirements. Thus, anomaly inspection information 132 may include actions to verify the completion, existence, or effectiveness of corrective actions associated with the anomaly. By including anomaly inspection information 132 within the anomaly artifact 124, the user is provided with clear and actionable guidance tailored to the applicable inspection context without the need to refer to separate documents.

[0051] Anomaly location information 134 indicates where an anomaly is located within the structure. Anomaly location information 134 may include text location identifiers mapped to a digital representation of the structure, component references, coordinate-based information, or map-based location information, as will be described in more detail below. Anomaly location information 134 may provide spatial context to help users locate anomalies during inspection activities.

[0052] In some examples, the anomalous location information 134 contained in the anomalous artifact 124 includes map-based localization information mapped to a digital representation of the structure. The map-based localization information indicates the spatial location of the anomaly within the structure and provides a visual context to assist the user in locating the anomaly during inspection activities. The digital representation may correspond to a model, diagram, or other representation of the structure that allows the anomalous location to be presented in relation to the surrounding structural features. Further details regarding exemplary mapping techniques and zone-based representations are described below with reference to subsequent figures.

[0053] In some examples, the anomaly artifact 124 further includes at least one image 142 associated with the anomaly, as shown in Figure 3B. The at least one image 142 may depict the anomaly itself or the area of ​​the structure in which the anomaly is located. For example, the image may include a photograph, annotated image, diagram, or other visual representation captured during a manufacturing, inspection, maintenance, or inspection activity. Including one or more images within the anomaly artifact 124 provides a visual context that helps the user recognize the anomaly and understand its physical characteristics during inspection, without the need to refer to a separate image repository or document. In some examples, at least one image forms part or all of the anomaly description information 130 by visually characterizing the anomaly or observed condition. In other examples, at least one image forms part of the anomaly location information 134 by visually indicating where the anomaly is located within the structure. In this way, the anomaly artifact 124 can visually convey descriptive or location-related information in addition to, or instead of, a textual representation.

[0054] An anomaly artifact 124 may further include metadata associated with the anomaly artifact. This metadata may include, for example, a revision status 144, a creation timestamp, a modification timestamp, or a user identifier associated with the modification of the anomaly artifact 124. Such metadata facilitates traceability of changes made to the anomaly artifact over time and assists the user in determining the current state of the anomaly artifact during inspection activities. In particular, the revision status 144 indicates whether the anomaly artifact reflects an initial, updated, or alternative version of the anomaly-related information. The revision status 144 may be updated when the anomaly-related information changes, such as when additional inspection results are recorded, the anomaly description is refined, the anomaly location information is clarified, or corrective action information is incorporated. By presenting the revision status 144 within the anomaly artifact 124, users can easily determine during inspection whether they are working with the latest version of the anomaly artifact, thereby reducing the risk of relying on outdated or incomplete anomaly information.

[0055] In some cases, anomaly artifacts 124 are structured for interoperability across multiple anomaly management systems. Rather than being limited to a single system or platform, anomaly artifacts 124 are formatted as a self-contained and standardized reference that can be exchanged, accessed, or utilized across different anomaly management systems and inspection contexts. This interoperability allows anomaly artifacts to be generated in one system and used in other systems associated with manufacturing, inspection, maintenance, repair, or supplier work, while maintaining the organization and content of anomaly-related information. By structuring anomaly artifacts 124 for interoperability, inspection activities can be supported across different organizations, facilities, or network environments without users having to manually reconcile anomaly information from different systems.

[0056] In some examples, the anomaly location information 134 contained in the anomaly artifact 124 includes map-based localization information mapped to a digital representation of the structure. Referring to Figure 4, an exemplary digital representation 150 of a structure is shown. As used herein, a digital representation 150 of a structure refers to a map-based or spatial representation that depicts a structure and assists in localizing anomalies relative to the physical features of the structure. In the illustrated example, the digital representation 150 depicts an aircraft 151. The aircraft 151 includes an anomaly 148 associated with the structure, shown at a specific location on the digital representation 150, and the anomaly artifact 124 is associated with anomaly 148. The digital representation 150 may be generated from a computer-aided design (CAD) model, an engineering dataset, an inspection record, or other data source that describes the structure. By mapping the anomaly location information to the digital representation 150, the spatial context of the anomaly 148 is provided, allowing the user to understand where the anomaly is located relative to the overall structure and surrounding structural features during inspection activities. Digital representations may include two-dimensional or three-dimensional visual maps, cross-sectional views, surface maps, or other spatial representations suitable for identifying anomalies within a structure.

[0057] In some examples, the digital representation 150 or a related portion thereof is included within the anomaly artifact 124 as part of the anomaly location information. In other examples, the anomaly artifact 124 includes location information encoded in a structured form, such as a text descriptor, tabular entries, or charted location data, which is derived from map-based localization and conveys the spatial location of the anomaly relative to the structure without embedding the complete digital representation.

[0058] In some examples, as shown in Figure 4, the digital representation 150 of the structure is maintained as a single, undivided representation. In other examples, as shown in Figures 5A and 5B, the digital representation 150 of the structure is subdivided into multiple zones 152, each zone representing a defined portion of the structure for the purpose of anomaly location and inspection. The multiple zones 152 may be defined based on structural features, manufacturing or assembly areas, inspection access considerations, or other application-specific criteria. In some examples, the digital representation 150 includes hierarchical divisions such as zones and subzones to facilitate a more granular organization of anomaly location information. An anomaly artifact 124 is associated with at least one of the multiple zones 152 based on the anomaly location information within the digital representation 150.

[0059] By subdividing the digital representation 150 into zones, it becomes possible to represent anomaly locations not only at the overall structural level but also for specific parts of the structure. This zoned organization supports more targeted inspection activities by allowing users to focus on the relevant areas of the structure associated with a particular anomaly. In large or complex structures such as aircraft, the zoned association of anomaly artifacts can improve clarity, reduce ambiguity in anomaly location, and facilitate coordination among users responsible for inspection activities in different areas of the structure.

[0060] As shown in Figure 5A, the multiple zones 152 of the digital representation 150 include a first zone 152A, a second zone 152B, a third zone 152C, a fourth zone 152D, and additional unlabeled zones for clarity. In this example, the anomaly location information indicates that the anomaly 148 is located within the second zone 152B, so that the corresponding anomaly artifact 124 is associated with the second zone 152B. In other examples, the anomaly may extend to multiple zones of the digital representation 150. In such cases, when the anomaly extends to multiple zones, the anomaly is subdivided into multiple zone-specific anomaly artifacts.

[0061] When an anomaly extends across multiple zones within the digital representation 150, the anomaly artifact 124 is generated as one of several zone-specific anomaly artifacts. That is, each zone-specific anomaly artifact corresponds to a specific zone and contains anomaly-related information associated with the portion of the anomaly located within that zone. For example, as shown in Figure 5B, an anomaly extending across the second zone 152B and the third zone 152C is split into two anomalies, the first anomaly 148A and the second anomaly 148B, each further represented by several zone-specific anomaly artifacts 124-1 and 124-2, respectively. Each zone-specific anomaly artifact supports local inspection activities within its corresponding zone but remains associated with the same underlying anomaly.

[0062] Referring to Figure 6, a method 200 for supporting structural anomaly inspection activities is shown. Method 200 includes, in block 202, a step of aggregating anomaly data from one or more anomaly data sources 120 to generate structured anomaly data 122 about the anomaly. This aggregation step may be performed in the same manner as described above with respect to block 102 of Method 100. In some examples, aggregation is performed specifically to assist in preparing anomaly artifacts for use in inspection activities. In block 204, Method 200 includes a step of generating anomaly artifacts 124 about the anomaly based on the structured anomaly data. The anomaly artifact 124 is generated as a single reference usable during inspection activities and includes, as described above, anomaly identification information 128, anomaly description information 130, anomaly inspection information 132, and anomaly location information 134. The generation of the anomaly artifact 124 makes it possible to present anomaly-related information in a form suitable for use by one or more users during inspection activities.

[0063] Method 200 further includes the step in block 206 of storing and selectively updating the anomaly artifact in the anomaly management system 126 in order to maintain an accurate current representation of the anomaly. As inspection activities progress, information associated with the anomaly artifact, such as updates to the anomaly description information 130, anomaly inspection information 132, or anomaly location information 134, may be selectively updated. This allows the anomaly artifact 124 to reflect the latest available information without changing the anomaly identification information.

[0064] In block 208, method 200 includes the step of mapping anomalous location information 134 of an anomalous artifact 124 to a digital representation 150 of the structure in order to provide a spatial context of the anomalous artifact. The mapping associates the anomalous artifact with a location on the digital representation 150, enabling the user to understand where the anomalous artifact is located relative to the physical features of the structure. In some examples, the mapped location information derived from the digital representation 150 is included directly within the anomalous artifact 124, so that the anomalous artifact presents the spatial location information without requiring the user to access the digital representation separately. In other examples, the anomalous artifact 124 includes a reference, link, or identifier that associates the anomalous artifact with the mapped location on the digital representation 150, while still providing sufficient anomalous location information within the anomalous artifact to support inspection activities.

[0065] In some examples, the digital representation 150 is subdivided into multiple zones 152, and the anomalous artifact 124 is associated with at least one of the zones based on the mapped anomalous location information, as described above.

[0066] In block 210, method 200 includes the step of providing an anomaly artifact 124 to at least one user to support anomaly inspection activities. The step of providing the anomaly artifact 124 may include the step of presenting the anomaly artifact 124 via a user interface, the step of exporting the anomaly artifact 124 to a portable format, or otherwise making the anomaly artifact 124 accessible to the user. By providing the anomaly artifact 124 as a single, integrated reference, method 200 enables the user to perform inspection activities using anomaly-related information without relying on multiple separate systems or documents. The anomaly artifact 124 serves as the primary reference used by personnel throughout the inspection activity, and the information necessary to identify, locate, inspect, and evaluate the anomaly and support corrective actions is obtained directly from the anomaly artifact without requiring access to multiple underlying systems or records. In some examples, the anomaly artifact 124 is used to support inspection activities from initial identification of the anomaly to corrective actions and resolution of the anomaly.

[0067] In some examples, the methods and techniques described herein are implemented, in whole or in part, by one or more computing devices. Such computing devices may include one or more processors, memory devices, storage devices, and communication interfaces, and may execute software instructions, firmware, or logic configured to perform the operations described. In some examples, functions associated with the aggregation of anomalous data, the generation of anomalous artifacts, the mapping of anomalous locations, the storage and updating of anomalous artifacts, and the presentation of anomalous artifacts to the user are performed by one or more software modules or logical components running on one or more computing devices. The operations described may be performed automatically, semi-automatically, or in combination with user input, depending on the implementation and testing circumstances.

[0068] In summary, the disclosed anomaly artifacts and associated methods provide an artifact-centric approach to anomaly inspection activities in which anomaly-related information is integrated into a single structured reference usable throughout the inspection lifecycle. By integrating anomaly identification information, descriptive information, inspection information, and location information, including map-based localization linked to a digital representation of the structure, the anomaly artifacts serve as the primary reference for personnel performing inspection activities. The disclosed techniques further support the fragmentation of anomalies into zone-specific anomaly artifacts for more targeted inspection within defined areas of the structure, while maintaining traceability, revision control, and interoperability across systems. This approach reduces reliance on different records and systems, improves the efficiency and consistency of inspection activities, and is particularly well suited to large or complex structures where accurate localization and coordinated inspection are critical.

[0069] In the above description, specific terms such as “up,” “down,” “upper side,” “lower side,” “horizontal,” “vertical,” “left,” “right,” “upward,” and “downward” may be used. These terms are used to clarify the description when dealing with relative relationships where applicable. However, these terms are not intended to imply absolute relationships, positions, and / or orientations. For example, the “upper side” of an object can become the “lower side” by simply inverting that object. Nevertheless, this is still the same object. Furthermore, the terms “include,” “equip,” and “possess,” and their variations, mean “include, but not limited to,” unless otherwise explicitly specified. An enumerated list of items does not mean that any or all of the items are mutually exclusive and / or mutually inclusive, unless otherwise explicitly specified. The terms “a,” “an,” and “the” also mean “one or more,” unless otherwise explicitly specified. Furthermore, the term “plural” can be defined as “at least two.” Furthermore, unless otherwise specified, as defined in this disclosure, certain features do not necessarily represent all of the features of the entire set or class of features.

[0070] The terms “approximately” or “substantially” are defined in some embodiments as meaning within + / - 5% of a given value, but in additional embodiments, any disclosure of “approximately” may be further narrowed and asserted to mean within + / - 4% of a given value, within + / - 3% of a given value, within + / - 2% of a given value, within + / - 1% of a given value, or the exact given value. Furthermore, if at least two values ​​of a variable are disclosed, such disclosure is specifically intended to include a range between the two values, whether they are disclosed in relation to separate embodiments or examples, and specifically intended to include a range less than or equal to at least the smaller of the two values ​​and / or the larger of the two values. Additionally, if at least three values ​​of a variable are disclosed, such disclosure is specifically intended to include a range between any two of the values, whether they are disclosed in relation to separate embodiments or examples, and specifically intended to include a range less than or equal to at least value A and / or value B, where A may be any value of the disclosed values ​​other than the disclosed maximum value, and B may be any value of the disclosed values ​​other than the disclosed minimum value.

[0071] Additionally, examples herein of one element being "joined" to another may include direct and indirect joins. A direct join can be defined as one element being joined to another and having some kind of contact. An indirect join can be defined as a join between two elements that do not directly touch each other but have one or more additional elements between the joined elements. Furthermore, as used herein, fixing one element to another may include direct and indirect fixings. Additionally, as used herein, "adjacent" does not necessarily indicate contact. For example, one element may be adjacent to another element without touching it.

[0072] As used in this disclosure, the phrase “at least one of” when used with a list of items means that one or more different combinations of items on the list may be used, or only one of the items on the list may be required. An item may be a specific object, thing, or category. In other words, “at least one of” means that any combination or any number of items on the list may be used, but not all items on the list may be required. For example, “at least one of item A, item B, and item C” may mean item A, item A and item B, item B, item A, item B, and item C, or item B and item C. In some cases, “at least one of item A, item B, and item C” may mean, for example, two item A, one item B, and ten item C, four item B and seven item C, or any other suitable combination, for example, but not limited to these.

[0073] Unless otherwise stated, terms such as "first," "second," etc., are used merely as labels in this disclosure and are not intended to impose any order, position, or hierarchical requirements on the items they refer to. Furthermore, the designation of, for example, an item as "second" does not require or exclude the existence of, for example, an item as "first" or an item numbered lower than "first," and / or an item as "third" or an item numbered higher than "third."

[0074] Where used herein, a system, apparatus, structure, article, element, component, or hardware “configured to perform” a specified function is not only capable of performing the specified function after further modification, but can actually perform the specified function without any modification. In other words, a system, apparatus, structure, article, element, component, or hardware “configured to perform” a specified function is specifically selected, created, implemented, used, programmed, and / or designed to perform the specified function. Where used herein, “configured to” refers to an existing characteristic of the system, apparatus, structure, article, element, component, or hardware that enables it to perform the specified function without further modification. In addition to or instead of this, for the purposes of this disclosure, a system, apparatus, structure, article, element, component, or hardware described as “configured to perform” a particular function may also be described as “adapted” and / or “operable” to perform that function.

[0075] The schematic flowcharts included herein are generally described as logical flowcharts. Therefore, the illustrated order and labeled steps represent one example of the presented method. Other steps and methods may be considered equivalent in function, logic, or effect to one or more steps, or parts thereof, of the illustrated method. Additionally, the formatting and symbols used are provided to illustrate the logical steps of the method and are not intended to limit the scope of the method. Various arrow and line types may be used in the flowcharts, but these are not intended to limit the scope of the corresponding method. In fact, some arrows or other connectors may be used to indicate only the logical flow of the method. For example, arrows may indicate unspecified duration wait or monitoring periods between enumerated steps of the illustrated method. Additionally, the order in which a particular method is performed may or may not strictly adhere to the order of the corresponding steps shown.

[0076] Many of the functional units described herein are labeled as modules to further emphasize the independence of their implementation forms. For example, modules may be implemented as hardware circuits including custom large-scale integrated circuits (VLSIs) or off-the-shelf semiconductors such as gate arrays, logic chips, transistors, or other individual components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays ("FPGAs"), programmable array logic, or programmable logic devices.

[0077] Modules may be implemented in software for execution on various types of processors. A module of identified program code may, for example, contain one or more physical or logical blocks of computer instructions, which may be organized as, for example, objects, procedures, or functions. Nevertheless, the executable files of identified modules do not need to be physically located together and may contain separate instructions stored in different locations that, when logically combined, constitute the module and achieve the purposes described for that module.

[0078] In fact, a module of program code may be a single instruction or many instructions, and may be distributed across several different code segments, different programs, and several memory devices. Similarly, operational data may be identified and illustrated within a module as herein, embodied in any suitable form, and organized within any suitable type of data structure. Operational data may be collected as a single dataset, or distributed in different locations, including different storage devices, and may exist at least partially simply as electrical signals on a system or network. If a module or part of a module is implemented in software, the program code may be stored and / or propagated on one or more computer-readable media.

[0079] A computer program product may include a computer-readable storage medium (or multiple mediums) having computer-readable program instructions that cause a processor to execute an aspect of the present invention.

[0080] Computer-readable storage media can be tangible devices capable of holding and storing instructions used by instruction execution devices. Computer-readable storage media may be, but are not limited to, electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination thereof. More specific examples of computer-readable storage media include portable computer disks, hard disks, random access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM") or flash memory, static random access memory ("SRAM"), portable compact disk read-only memory ("CD-ROM"), digital multi-application disks ("DVD"), memory sticks, floppy disks, perforated cards, and mechanically encoded devices such as grooved raised structures with instructions stored in the groove structure itself, or any suitable combination thereof. The computer-readable storage medium used in this application should not be interpreted as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., an optical pulse passing through an optical fiber cable), or a transient signal itself such as an electrical signal transmitted by a wire.

[0081] The computer-readable program instructions described in this application can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface of each computing / processing device receives computer-readable program instructions from the network and transfers the computer-readable program instructions for storage in a computer-readable storage medium within each computing / processing device.

[0082] The computer-readable program instructions for performing the operation of the present invention may be assembler instructions, instruction set architecture ("ISA") instructions, machine instructions, machine-specific instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages, and may be either source code or object code including object-oriented programming languages ​​such as Smalltalk or C++, or may be conventional procedural programming languages ​​such as C or similar programming languages. The entire computer-readable program instruction may be executed on the user's computer, or only a portion of the instruction may be executed on the user's computer, or the instruction may be executed as a standalone software package, or a portion of the instruction may be executed on the user's computer and a remote computer, or the entire instruction may be executed on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or this connection may be to an external computer (for example, via the Internet using an Internet Service Provider). In some embodiments, to carry out aspects of the present invention, electronic circuits including, for example, programmable logic circuits, field-programmable gate arrays ("FPGAs") and programmable logic arrays ("PLAs") may be used to execute computer-readable program instructions by utilizing state information of computer-readable program instructions and customizing them for the electronic circuits.

[0083] Aspects of the present invention will be described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It will be understood that each block in the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0084] These computer-readable program instructions may be provided to a general-purpose computer, a dedicated computer, or a processor of another programmable data processing device to manufacture a machine such that instructions executed via the processor of a computer or other programmable data processing device create means for implementing functions / operations specified in one or more blocks of a flowchart and / or block diagram. These computer-readable program instructions may also be stored on a computer-readable storage medium on which the instructions are stored, which can cause a computer, a programmable data processing device, and / or other device to function in a particular way such that the storage medium on which the instructions are stored constitutes a manufactured article containing instructions that implements a mode of function / operation specified in one or more blocks of a flowchart and / or block diagram.

[0085] Computer-readable program instructions can also be loaded into a computer, other programmable data processing device, or other device so that a series of operational steps are executed by the computer, other programmable device, or other device to realize a process performed by a computer, other programmable device, or other device, so that the functions / operations shown in one or more blocks of a flowchart and / or block diagram are performed by instructions executed by the computer, other programmable device, or other device, so that a process performed by a computer is realized.

[0086] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of the apparatus, system, method, and computer program product according to various embodiments of the present invention. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code containing one or more executable instructions of program code for performing a specified logical function.

[0087] While various types of arrows and lines may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiment. In fact, some arrows or other connectors may be used to show only the logical flow of the shown embodiment. For example, an arrow may indicate an unspecified duration of waiting or monitoring period between enumerated steps of the illustrated embodiment. It should also be noted that each block in a block diagram and / or flowchart, as well as combinations of blocks in a block diagram and / or flowchart, may be implemented by a dedicated hardware-based system or a combination of dedicated hardware and program code that performs a specified function or operation.

[0088] The subject matter of the present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The examples described should be considered in all respects only as illustrative and not restrictive. All modifications within the meaning and equivalence of the claims shall be included within that scope. [Explanation of Symbols]

[0089] 120 data sources 122 Structured Anomaly Data 124, 124-1, 124-2 Abnormal Artifacts 126 Anomaly Management System 128 Identification Information 130 Descriptive Information 132 Inspection Information 134 Location information 136 Text description of an anomaly 138 Severity Level 140 Anomaly classification 142 At least one image 144 Revision Status 148, 148A, 148B Abnormal 150 Digital Expressions 151 Aircraft Zones 152, 152A, 152B, 152C, and 152D

Claims

1. A method for generating anomaly artifacts to support structural anomaly inspection activities, the method being: To generate structured anomaly data relating to the aforementioned anomaly, the steps include aggregating anomaly data from one or more anomaly data sources, Steps include generating an anomaly artifact relating to the anomaly as a single reference usable during an anomaly inspection activity, based on the structured anomaly data, wherein the anomaly artifact includes anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information; In order to maintain the current accurate representation of the anomaly, the anomaly management system stores the anomaly artifact and selectively updates it. Methods that include...

2. The method according to claim 1, wherein the step of generating the anomalous artifact further includes the step of capturing the anomalous artifact using a predetermined artifact template having a standardized configuration of the anomalous identification information, the anomalous description information, the anomalous inspection information, and the anomalous location information.

3. The anomaly location information includes map-based location information mapped to a digital representation of the structure to indicate the spatial location of the anomaly within the structure. The digital representation of the structure is subdivided into multiple zones, The method according to claim 1, wherein the anomalous artifact is associated with at least one of the plurality of zones based on the anomalous location information.

4. The method according to claim 3, wherein, when the anomaly extends to some of the multiple zones, the method further includes the step of generating multiple zone-specific anomaly artifacts of the anomaly, each zone-specific anomaly artifact corresponding to one of the multiple zones.

5. The method according to claim 1, wherein the step of generating the anomalous artifact includes the step of automatically generating the anomalous artifact based on the structured anomalous data.

6. The method according to claim 1, wherein the step of generating the anomalous artifact includes the step of manually generating the anomalous artifact based on the structured anomalous data.

7. The step of generating the aforementioned anomalous artifact is At least one image associated with the aforementioned anomaly, Severity level of the anomaly, Classification of abnormalities, or The anomalous metadata associated with the aforementioned anomalous artifact The method according to claim 1, further comprising the step of including at least one of the following.

8. The step of selectively updating the aforementioned anomalous artifact is The steps include updating the aforementioned abnormal description information, The steps include updating the aforementioned abnormality inspection information, The steps include updating the abnormal location information and The method according to claim 1, comprising at least one of the following.

9. The method according to claim 1, further comprising the step of constructing the anomaly artifact for interoperability across multiple anomaly management systems, wherein the anomaly management system is one of the multiple anomaly management systems to support inspection-related activities across different inspection contexts.

10. A method for using anomaly artifacts to support structural anomaly inspection activities, the method being: To generate structured anomaly data relating to the aforementioned anomaly, the steps include aggregating anomaly data from one or more anomaly data sources, Steps include generating an anomaly artifact relating to the anomaly as a single reference usable during an anomaly inspection activity, based on the structured anomaly data, wherein the anomaly artifact includes anomaly identification information, anomaly description information, anomaly inspection information, and anomaly location information; To maintain the current accurate representation of the aforementioned anomaly, the anomaly management system is used to store and selectively update the anomaly artifact. To provide the spatial context of the anomaly, the steps include mapping the anomaly location information of the anomaly artifact to a digital representation of the structure, To support the inspection activity for the aforementioned anomaly, the steps include providing the anomaly artifact to at least one user. Methods that include...

11. The method according to claim 10, wherein the step of mapping the abnormal location information includes the step of including the mapped location information within the abnormal artifact.

12. The digital representation of the structure is subdivided into multiple zones, The method according to claim 10, wherein the step of mapping the anomalous location information further includes the step of associating the anomalous artifact with at least one of the plurality of zones.

13. The method according to claim 12, wherein when the anomaly extends to some of the multiple zones, the method further includes the step of generating a multiple zone-specific anomaly artifact of the anomaly, each zone-specific anomaly artifact corresponding to one of the multiple zones.

14. The method according to claim 13, wherein the step of providing the anomalous artifact to at least one user includes presenting the anomalous location information to guide the at least one user to a specific zone among the plurality of zones of the digital representation corresponding to the region of the structure in which the anomalous artifact is located.

15. An anomaly artifact for supporting inspection activities for structural anomalies, wherein the anomaly artifact is, Anomaly identification information including a unique anomaly identifier relating to the anomaly, Anomaly description information describing the aforementioned anomaly, Anomaly inspection information defining one or more actions to be performed to inspect the aforementioned anomaly, Anomaly location information indicating where the anomaly is located within the structure, Includes, An anomaly artifact in which the anomaly identification information, the anomaly description information, the anomaly inspection information, and the anomaly location information are integrated into a single reference usable during the anomaly inspection activity.

16. The anomaly artifact according to claim 15, further comprising at least one image associated with the anomaly, wherein the at least one image shows the anomaly or a region of the structure in which the anomaly is located.

17. The anomalous artifact according to claim 15, further comprising metadata associated with the anomalous artifact, wherein the metadata includes at least one of a revision status, a creation timestamp, a modification timestamp, or a user identifier associated with the modification.

18. The anomaly artifact according to claim 15, wherein the anomaly location information includes map-based localization information mapped to a digital representation of the structure in order to indicate the spatial location of the anomaly within the structure.

19. The digital representation of the structure is subdivided into multiple zones, The abnormal location information associates the abnormality with at least one of the plurality of zones. The anomalous artifact described in claim 18.

20. The anomaly artifact according to claim 19, wherein when the anomaly extends to some of the multiple zones, the anomaly artifact is generated as one of the multiple zone-specific anomaly artifacts, and each zone-specific anomaly artifact corresponds to one of the multiple zones.

Images