The field relates to configuration maintenance. More precisely, the field relates to remotely comparing a maintenance configuration with an allowable configuration of a composite physical object.
Highly regulated companies, for example Aerospace and Defense (A&D) and utilities industries need to comply with as-allowed asset structures to run their daily businesses. Since the as-maintained structures are changed frequently during maintenance, staying compliant with the as-allowed structures is a hard and cost intensive business for such companies.
As-maintained and as-allowed structures are well established and used objects in the industries. An as-maintained configuration also referred to as maintenance configuration is a configuration that consists of information how a complex composite object such as an aircraft, an engine or a power generator is maintained. An as-allowed configuration also referred to as allowable configuration is provided usually by the manufacturer of the composite object or the owner of the composite object. In some industries, the allowable configuration is approved by a regulating authority, for example the National Transportation Security Board (NTSB) for A&D in the United States. An allowable configuration usually consists of the parts allowed to be used as replacement parts for the composite object, as well as parts interdependence. The structure of a composite object defines its configuration. The configuration is the current asset structure and comprising parts. For an aircraft or an engine, the information for the structure and the parts are typically provided by the manufacturer of the asset in a parts catalogue or a parts list. According to the asset, information may also be provided for the functional location of the parts and their consistency. The configuration check of an as-maintained with an as-allowed configuration is done in the industries but on a paper based process or by using dedicated software applications. Either the paper based approach or using a dedicated software application has many disadvantages.
Various embodiments of systems and methods of remote comparison of a maintenance configuration with an allowable configuration are described herein. In one embodiment, the method includes receiving an operator identification from an operator of a composite object at a remote server and receiving data representing the first configuration from the operator of the composite object at the remote server. The method also includes comparing the first configuration with the second configuration of the composite object within the remote server and determining a deviation between the first configuration and the second configuration of the composite object. The method further includes presenting result data to the operator, the result data comprising the determined deviation.
In other embodiments, the system for remotely comparing a maintenance configuration to an allowable configuration of a composite object includes at least one processor for executing program code and memory, and a remote server. The system also includes a receiving module within the remote server to receive an operator identification and data representing the maintenance configuration from an operator of the composite object. The system further includes a processing module within the remote server to compare the maintenance configuration with the allowable configuration and to determine a deviation between the maintenance configuration and the allowable configuration of the composite object and a reporting module to present result data to the operator, the result data comprising the determined deviation.
These and other benefits and features of embodiments of the invention will be apparent upon consideration of the following detailed description of preferred embodiments thereof, presented in connection with the following drawings.
The claims set forth the embodiments of the invention with particularity. The invention is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. The embodiments of the invention, together with its advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings.
Embodiments of techniques for systems and methods of remote comparison of a maintenance configuration with an allowable configuration are described herein. In the following description, numerous specific details are set forth to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
Reference throughout this specification to “one embodiment”, “this embodiment” and similar phrases, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of these phrases in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Further, at block 230, the first configuration is compared to a second configuration of the composite object within the remote server. In one embodiment, the second configuration is an allowable configuration of the composite object. In one embodiment, the comparison, as described in block 230, includes extracting the second configuration from a repository, the second configuration indexed by the operator identification received at block 220 and comparing elements of the first configuration to corresponding elements of the second configuration. In one embodiment, the repository with the second configuration is contained within the remote server such as repository 135 within the remote server 130.
Turning back to
Then, at block 250, result data is presented to the operator of the composite object. The result data comprises the determined deviation at block 240. In one embodiment, the result data is sent to the operator through a report.
The remote server 305 further includes a receiving module 360 to receive an operator identification and data representing the maintenance configuration from the operator 340 of the composite object 350.
The remote server 305 also includes a processing module to compare the maintenance configuration with the allowable configuration and to determine a deviation between the maintenance configuration and the allowable configuration of the composite object 350. In one embodiment, the processing module 370 is operable to extract the allowable configuration from a repository 380, the allowable configuration indexed by the operator identification. In one embodiment, the repository 380 is contained in a database within the remote server 305.
In one embodiment, the processing module 370 is operable to compare elements of the maintenance configuration to corresponding elements of the allowable configuration.
In one embodiment, the processing module 370 is operable to determine inconsistencies between elements of the maintenance configuration and corresponding elements of the allowable configuration.
The remote server 305 further includes a reporting module 390 to present result data to the operator 340, the result data comprising the determined deviation by the processing module 370. In one embodiment, the reporting module provides the result data to the operator 340 in a report.
In one embodiment, the method, as described in
Some embodiments of the invention may include the above-described methods being written as one or more software components. These components, and the functionality associated with each, may be used by client, server, distributed, or peer computer systems. These components may be written in a computer language corresponding to one or more programming languages such as, functional, declarative, procedural, object-oriented, lower level languages and the like. They may be linked to other components via various application programming interfaces and then compiled into one complete application for a server or a client. Alternatively, the components maybe implemented in server and client applications. Further, these components may be linked together via various distributed programming protocols. Some example embodiments of the invention may include remote procedure calls being used to implement one or more of these components across a distributed programming environment. For example, a logic level may reside on a first computer system that is remotely located from a second computer system containing an interface level (e.g., a graphical user interface). These first and second computer systems can be configured in a server-client, peer-to-peer, or some other configuration. The clients can vary in complexity from mobile and handheld devices, to thin clients and on to thick clients or even other servers.
The above-illustrated software components are tangibly stored on a computer readable storage medium as instructions. The term “computer readable storage medium” should be taken to include a single medium or multiple media that stores one or more sets of instructions. The term “computer readable storage medium” should be taken to include any physical article that is capable of undergoing a set of physical changes to physically store, encode, or otherwise carry a set of instructions for execution by a computer system which causes the computer system to perform any of the methods or process steps described, represented, or illustrated herein. Examples of computer readable storage media include, but are not limited to: magnetic media, such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs, DVDs and holographic devices; magneto-optical media; and hardware devices that are specially configured to store and execute, such as application-specific integrated circuits (“ASICs”), programmable logic devices (“PLDs”) and ROM and RAM devices. Examples of computer readable instructions include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter. For example, an embodiment of the invention may be implemented using Java, C++, or other object-oriented programming language and development tools. Another embodiment of the invention may be implemented in hard-wired circuitry in place of, or in combination with machine readable software instructions.
A data source is an information resource. Data sources include sources of data that enable data storage and retrieval. Data sources may include databases, such as, relational, transactional, hierarchical, multi-dimensional (e.g., OLAP), object oriented databases, and the like. Further data sources include tabular data (e.g., spreadsheets, delimited text files), data tagged with a markup language (e.g., XML data), transactional data, unstructured data (e.g., text files, screen scrapings), hierarchical data (e.g., data in a file system, XML data), files, a plurality of reports, and any other data source accessible through an established protocol, such as, Open DataBase Connectivity (ODBC), produced by an underlying software system (e.g., ERP system), and the like. Data sources may also include a data source where the data is not tangibly stored or otherwise ephemeral such as data streams, broadcast data, and the like. These data sources can include associated data foundations, semantic layers, management systems, security systems and so on.
In the above description, numerous specific details are set forth to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however that the invention can be practiced without one or more of the specific details or with other methods, components, techniques, etc. In other instances, well-known operations or structures are not shown or described in details to avoid obscuring aspects of the invention.
Although the processes illustrated and described herein include series of steps, it will be appreciated that the different embodiments of the present invention are not limited by the illustrated ordering of steps, as some steps may occur in different orders, some concurrently with other steps apart from that shown and described herein. In addition, not all illustrated steps may be required to implement a methodology in accordance with the present invention. Moreover, it will be appreciated that the processes may be implemented in association with the apparatus and systems illustrated and described herein as well as in association with other systems not illustrated.
The above descriptions and illustrations of embodiments of the invention, including what is described in the Abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. These modifications can be made to the invention in light of the above detailed description. Rather, the scope of the invention is to be determined by the following claims, which are to be interpreted in accordance with established doctrines of claim construction.