The present disclosure relates to a damage assessment system, and more specifically, to methods and systems for assessing allowable damage limits for a structure.
Maintenance programs intended to maintain structures in good operating condition may sometimes become complex and burdensome. By way of example, in operating airplanes in North America, Europe, Japan, Australia and in other regulatory jurisdictions which may have a bilateral agreement with the FAA (U.S. Federal Aviation Administration), airlines may need to manage a significant amount of complex and overlapping maintenance requirements set out by the FAA. Compliance with FAA and other requirements by an airline may be required to qualify an airplane for continued airworthiness.
As an aircraft ages or as repairs to the structure age, evaluation may be performed to verify the health of the structure and to confirm that the structure has sufficient remaining strength for continued operations. Structural damage data needs to be interpreted in order to assess the health of a structure. Some known maintenance programs require that personnel interpret this data. Errors can arise due to manual collection and interpretation of the data, leading to errors in assessment of the health of a structure. Variability exists when data of structural components is interpreted manually. For any given structural inspection task, the probability of detection can be affected by several factors such as the skill and experience of the inspector; accessibility to the structure; and exposure of the inspection surface.
Moreover, some known programs for assessing allowable damage limits include field personnel looking up data in structural repair manuals. The assessment, however, can require that the personnel sift through large amounts of data to attempt to locate critical allowance data which is time consuming and inefficient. To successfully manage such a maintenance program, structural and maintenance personnel may need to have a comprehensive and detailed understanding of all the requirements of the maintenance program and of the 3D (three-dimensional) physical locations on structure where the requirements may apply. A program to systematically locate, identify, quantify and/or assess structure damage would enhance better utilization of maintenance programs.
In one aspect, a computer-implemented method of assessing a damage of a structure is provided. The computer-implemented method includes receiving damage information into a user interface device and quantifying at least one parameter of the damage. The computer-implemented method further includes performing a structural analysis to determine a damage allowability based on the at least one parameter. The computer-implemented method displays an output result of the structural analysis from the user interface device.
In another aspect, a system to assess an allowable damage limit for a damage of a structure is provided. The system includes a compliance system having a database of structural information relating to the structure. A computer enabled user interface device is coupled to the compliance system. The computer enabled user interface device includes a processor configured to access the structural information and display a location of the damage based on the structural information. The processor is configured to quantify at least one parameter of the damage. The processor is further configured to perform a structural analysis to determine a damage allowability based on the at least one parameter and display a maintenance instruction based on the damage allowability.
In a further aspect, a computer-implemented method of performing maintenance on a damage of a structure is provided. The computer-implemented method includes locating a damage area; accessing the damage area; and receiving damage information by a user interface device. The computer-implemented method further includes quantifying at least one parameter of the damage and performing a structural analysis to determine a damage allowability based on the at least one parameter. The computer-implemented method includes displaying maintenance instructions based on the structural analysis from the user interface device and includes performing a maintenance response on the damage.
The embodiments described herein relate to a damage assessment system and methods of operating the system. More particularly, the embodiments relate to a system for locating and identifying damage areas and quantifying and assessing structural damage present in the damage areas. Moreover, the embodiments are utilized in a variety of environments such as, but not limited to, military, civil, building, industrial, rail, shipping, aerodynamic and consumer environments. The embodiments described herein facilitate locating, quantifying and analyzing damage to reduce maintenance time and downtime of structures. A user interface device facilitates electronic damage assessment and recordation of repair procedures applied to the damage. In one application, the damage assessment system described herein is utilized for damage applied to the vehicle. It should be understood that the description and figures that utilize vehicles are exemplary only.
Management system 18 may be implemented by or embodied in a central processing unit 22. Management system 18 is configured to facilitate mapping, in 3D coordinates, areas, zones and specific locations of damage 12 on and/or within structure 14. Compliance management system 18 includes a structure database 24 such as, but not limited to, toolbox and/or knowledge tree databases having information relating to specific locations of damage of structure 14. Moreover, management system 18 includes a damage analyzer 26 that is configured to perform a structural analysis to determined damage allowability of damage 12. In the exemplary embodiment, structure database 24 includes a query of questions 78 relating to structure locations. Moreover, compliance management system 18 includes a program to generate questions 78 relating to structure locations based on inputs 28 provided by user interface device 16. Management system 18 includes data functional blocks 30. Data functional blocks 30 include a requirements data functional block 32, a tasks data functional block 34, an information data functional block 36, a records data functional block 38 and other data functional blocks 40.
In the exemplary embodiment, user interface device 16 is computer enabled having a central processing unit 42, a screen 44, an input device 46, such as for example a keyboard, and a database 48. As used herein, the term central processing unit is not limited to integrated circuits referred to in the art as a computer, but broadly refers to a microcontroller, a microcomputer, a programmable logic controller (PLC), an application specific integrated circuit, and other programmable circuits, and these terms are used interchangeably herein. In the embodiments described herein, memory may include, but is not limited to, a computer-readable medium, such as a random access memory (RAM), and a computer-readable non-volatile medium, such as flash memory. Alternatively, a floppy disk, a compact disc-read only memory (CD-ROM), a magneto-optical disk (MOD), and/or a digital versatile disc (DVD) may also be used. Also, in the embodiments described herein, additional input channels may include, without limitation, computer peripherals associated with an operator interface, such as a mouse and a keyboard. Alternatively, other computer peripherals may also be used that may include, without limitation, a scanner. Furthermore, in the exemplary embodiment, additional output channels may include, without limitation, an operator interface monitor. In the exemplary embodiment, central processing unit includes mobile communication and computing device such as, but not limited to, a cell phone, a personal digital assistant, and a computer laptop. User interface device 16 may be implemented using any appropriate combination of software and/or hardware configured for wired and/or wireless communication.
Moreover, in the exemplary embodiment, processes are illustrated as a collection of blocks in logical flow graphs, which represent a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components and data structures that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the process. Processes may be performed, at least in part, by user interface device 16.
In the exemplary embodiment, allowable damage limit assessment 62 is selected via user interface device 16 at block 340. At block 350, a list of damage types 64, such as but not limited to, gouges and lightning strikes, is displayed by user interface device 16. A determination is made to select damage type 64. In the illustrative example, “gouge” is selected and highlighted by user interface device 16.
At block 440, damage area 50 is displayed by user interface device 16. More particularly, block 450 graphically illustrates damage area 50. In the exemplary embodiment, block 450 graphically illustrates in 3D representative damage areas 50. Alternatively, block 450 can display textual descriptions for damage area 50. In the exemplary embodiment, 3D graphical representation of damage area 50 is provided to user interface device 16 by compliance management system 18. Alternatively 3D graphical representation of damage area 50 may be stored in database 48 of user interface device 16. At block 460, a list of damaged areas 50 is displayed by user interface device 16. In the exemplary embodiment, damage areas 50 are defined by graphics correlating to areas of structure 14. In the illustrative example, damage areas 50 are defined by indicia 67 such as “S-21R” as representing a particular string of structure 14. Alternatively, any type of indicia 67, such as graphical fonts, photographs and videos, can be used to identify damage area 50. Moreover, at block 460, more than one damage area 50 can be selected by user interface device 16 if damage extends into more than one area.
At block 620, quantifiable information 73, relating to parameter 74, is inputted into user interface device 16. More particularly, at block 6301, 6302 and 6303, specific entries 76 for quantifiable information 73 are displayed by user interface device 16. In an illustrative example, a measured dimension for damage length L (for example 1.85 in) is inputted at block 6301; a measured dimension for damage width W (for example 0.20 in) is inputted at block 6302 and a measured dimension for damage depth D (for example 0.037 in) is inputted at block 6303.
As parameters 74 are inputted at block 620, user interface device 16 is configured to display at least one question 78 relating to damage parameters 74 at block 640. Block 640 displays questions 78 with a “Yes” answer selection and a “No” answer selection. In the exemplary embodiment, questions 78 further define aspects of damage 12 as related to structure 14. At block 640, answers are inputted into user interface device 16 by selecting appropriate “Yes” answer or “No” answer.
At block 650, a determination is made to document damage 12. More particularly, damage 12 is documented by a procedure such as, but not limited to, photographing damage, video recording damage and/or electronically imputing a text description of damage. At block 660, instructions for damage documentation, such as how to photograph damage 12, are displayed by user interface device 16.
At block 750, a determination is made that damage 12 is not within allowable damage limit 80. A maintenance response 82 is displayed by user interface device 16 at block 760 based on the determination. More particularly, user interface device 16 displays that structure 14 is to be removed from service as maintenance response 82.
At block 770, a determination is made that damage 12 is within allowable damage limits 80. Maintenance response 82 is displayed by user interface device 16 at block 780. More particularly, user interface device 16 displays that structure 14 is to be repaired at block 780. In the exemplary embodiment, user interface device 16 displays a repair instruction 781 such as, but not limited to, that a temporary seal is to be applied to damage 12 at block 790. A record of temporary seal is recorded by user interface device 16 at block 792. More particularly, record of temporary repair at damage area 50 is coupled to database 48 to further document a permanent seal is to be made prior to predetermined number of life cycles of structure 14. Alternatively, at block 794, user interface device 16 displays that a permanent seal is to be applied to damage 12 as maintenance response 82.
Method 1200 includes identifying and selecting 1214 structure type 58 from a list of displayed structure types 58. A maintenance action 60, that is relative to selected structure type 58, is selected 1216 and damage type 64 is selected 1218. Method 1200 includes accessing damage 1220. More particularly, damage 12 is exposed 1222 by removing any component and/or finish that inhibits access to damage 12. In the exemplary method 1200, damage area 50 and more particularly damage zones 68 are selected 1224.
After damage area 50 and damage zone 68 are selected 1224, user interface device 16 receives 1226 damage information. In the illustrative method, damage information relates to information such as, but not limited to, structure type 58, damage type 64, damage area 50 and damage zone 68. Method 1200 includes displaying 1228 structural information based on receiving damage information. At least one parameter 74 of damage 12 is quantified 1230. More particularly, quantifying 1230 at least one parameter 74 includes measuring 1232 dimensions of damage 12. In the exemplary method 1200, at least one parameter 74 and damage 12 are electronically documented 1234 by user interface device 16.
Method 1200 includes performing 1236 a structural analysis to determine damage allowability 81 based on at least one parameter 74. More particularly, at least one question 78 relative to the at least one parameter 74 is displayed 1238. Moreover, method 1200 includes assessing 1240 the at least one question 78 and assessing 1242 allowable damage limits 80 based on answering the at least one question 78. In the exemplary method 1200, allowable damage limit 80 is compared 1244 to the at least one parameter 74.
Method 1200 includes displaying 1246 output result of the structural analysis from user interface device 16. More particularly, a maintenance response 82 is displayed 1248 based on the structural analysis and allowable damage limit 80. Method 1200 includes performing 1250 maintenance response 82 on damage 12.
Embodiments of the disclosure may be described in the context of an illustrative vehicle manufacturing and service process 1300 as shown in
Each of the processes of method 1300 may be performed or carried out by a system integrator, a third party, and/or an operator (e.g., a customer). For the purposes of this description, a system integrator may include without limitation any number of vehicle manufacturers and major-system subcontractors; a third party may include without limitation any number of venders, subcontractors, and suppliers; and an operator may be an airline, leasing company, military entity, service organization, and so on.
The various techniques embodied herein may be employed during any one or more of the stages of the production and service method 1300. For example, one or more of embodiments of fleet maintenance application, may be utilized while vehicle 1400 is in-service 1312 and/or at the maintenance and service 1314.
As shown in
Although the aircraft 1500 shown in
The embodiments described herein systematically locate and identify damage areas and quantify and assess structural damage present in damage areas. The embodiments successfully manage a maintenance program to provide structural and maintenance personnel a comprehensive and detailed program of all the requirements of the maintenance program and of the 3D physical locations on structure where the requirements may apply. The embodiments described herein provide a program to systematically locate, identify, quantify and/or assess structure damage to facilitate enhancing better utilization of maintenance programs. The embodiments include the hand-held user interface device that provides a structured method to efficiently locate, document and repair damage for convenient access by personnel within a program to enhance better utilization of maintenance information and to improved collaboration across a maintenance program.
The embodiment described herein may include, an automotive vehicle, an aircraft vehicle, or a civil engineering structure. For example, if the assessment system is deployed in a civil application, the damage may be located underneath a bridge or to a beam in a building. The assessment system may be used to monitor health of the structure to determine whether, for example, the structure is in danger of buckling or collapsing.
Exemplary embodiments of systems and methods for a damage assessment system are described above in detail. The systems and methods are not limited to the specific embodiments described herein, but rather, components of systems and/or steps of the method may be utilized independently and separately from other components and/or steps described herein. Each component and each method step may also be used in combination with other components and/or method steps. Although specific features of various embodiments may be shown in some drawings and not in others, this is for convenience only. Any feature of a drawing may be referenced and/or claimed in combination with any feature of any other drawing.
This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.