Part installation position coding database construction method and application

Abstract

The invention relates to the technical field of aircraft part management, and particularly discloses a method for creating a part installation position coding database based on a single mechanism type, and the method comprises the following steps: creating an initial configuration-based part position coding database; the position code database comprises position codes of the parts and a part feature data set associated with position code mapping; the part feature data set comprises at least three kinds of part feature data; the position code is unique and represents the position of one part; obtaining feature data of target aircraft parts, and performing traversal comparison on the feature data of the target aircraft parts and a part feature data set in the position coding database of the parts on the basis of a multi-stage comparison decision strategy; if it is judged that comparison and matching are successful, the records of the position coding database are kept unchanged; and if the comparison matching fails, updating the data in the position coding library.

Description

Technical Field

[0001] This invention relates to the field of aircraft component management technology, and more specifically, to a method for creating a component location coding database based on a single-structure model. Background Technology

[0002] To further enhance safety management and ensure the continued airworthiness of aircraft, the Civil Aviation Administration of China (CAAC) requires aircraft operators (primarily airlines) to implement mandatory and refined management of aircraft operation and maintenance. This refined management primarily manifests in the entire lifecycle of aircraft, from components to the complete aircraft, from manufacturing to disposal.

[0003] (1) Records of the installation location and operating time of components on different aircraft;

[0004] (2) Records of parts being transferred, modified, and repaired between aircraft operators, parts dealers, and parts repairers.

[0005] With the development of the industry and the gradual improvement of civil aviation safety regulations, aircraft safety management and control has become increasingly detailed and continuously improved. Existing aircraft maintenance information management systems are finding it difficult to conduct refined management and control of parts throughout their entire lifecycle.

[0006] Aircraft components frequently require replacement or swapping due to malfunctions, performance degradation, reaching the end of their service life, or needing repair. When installing and positioning time-limited components on an aircraft, it's crucial to consider not only their location but also the corresponding aircraft configuration. Even for the same type of time-limited component installed in the same location, differences in aircraft configuration can lead to variations in their lifespan, increasing the difficulty of managing them compared to ordinary components. For example, while both the Airbus A319 and A320 aircraft are equipped with the same landing gear, their different weights result in different landing gear lifespans.

[0007] For large airlines with a large fleet and complex aircraft configurations, the management of time-related components is extremely difficult. Relying entirely on manual management is prone to errors, leading to loss of control and affecting aircraft safety.

[0008] Furthermore, aircraft manufacturers currently assign identification numbers to some components (FIN for Airbus, LIN for COMAC). However, on the same aircraft, there may be components installed in different locations but with the same identification number. When these components need to be replaced, if the location of the part to be replaced is identified and located solely by its identification number, it is easy to confuse it with other components installed in different locations on the aircraft but with the same identification number, making it difficult to accurately indicate the location of the part to be replaced.

[0009] The same component may have the same identification number, but the installation location may be different on different aircraft configurations (for example, the slide pre-position warning light may be installed in a different location on an A320 aircraft than on an A321 aircraft). If the staff only locates the component based on the identification number but does not accurately identify the aircraft configuration, it will be impossible to quickly and accurately locate the installation location of the component on different aircraft.

[0010] Within a certain area of ​​the same aircraft, there are multiple identical components (such as multiple identical relays installed on the cockpit electrical integration mounting panel). The installation locations of these components are complex and difficult to describe. The staff's descriptions of their locations are rather arbitrary, with different people giving different descriptions. One staff member may describe the location of a replaced part, but others may not be able to understand it accurately.

[0011] Due to the complexity of the aforementioned aircraft parts, current aircraft maintenance information management systems are highly susceptible to errors in the control and management of these parts. Summary of the Invention

[0012] One aspect of this application is to provide a method for creating a component installation location coding database based on a single aircraft configuration. This database stores precise positioning information of components, which can efficiently and accurately locate the installation position of components on aircraft with different configurations, facilitating standardized aircraft maintenance and management.

[0013] To achieve the above objectives, the present invention adopts the following solution:

[0014] The method for creating a component installation location coding database based on a single mechanism type includes the following steps:

[0015] Create an initial configuration-based component location coding database; the location coding database includes component location codes and component feature datasets associated with the location code mappings; the component feature datasets contain at least three types of component feature data; the location code is unique and represents the location of a component;

[0016] Component feature data includes: component name, component part number, component configuration, component identification number, and component region number;

[0017] Acquire the feature data of the target aircraft parts and compare it with the feature dataset of the parts in the location coding database based on a multi-level comparison decision strategy; if the comparison is successful, keep the record in the location coding database unchanged; if the comparison fails, update the record in the location coding database.

[0018] The multi-level comparison decision strategy includes a first multi-level comparison decision strategy and / or a second comparison decision strategy; the first multi-level comparison rule is used when the acquired target aircraft component feature data includes a component identification number; the second multi-level comparison rule is used when the acquired target aircraft component feature data does not include a component identification number.

[0019] The first multi-level comparison decision strategy is to compare components based on component identification number, component area number, aircraft configuration, component part number, and component name.

[0020] The second multi-level comparison decision strategy is a traversal comparison based on component identification number, component name, component area number, and aircraft configuration.

[0021] As one specific implementation scheme, if the comparison and matching are determined to be unsuccessful, updating the records in the location coding database includes at least one of the following update methods:

[0022] Update Method 1: If the location code for the component is not found in the location code database, then create the location code for the component in the location code database;

[0023] Update Method 2: If the feature dataset of the component in the location coding database is missing feature data, then update the feature data of the component in the location coding database;

[0024] In the first multi-level comparison decision strategy, in response to the failure of comparison matching of one feature data or at least two feature data combinations among the component identification number, component area number, and component configuration, the result of the judgment that the location code of the component is not found in the location code database is output.

[0025] In the second multi-level comparison decision strategy, in response to the failure of comparison matching of one feature data or at least two feature data combinations among the component name, component part number, component area number, and component configuration, the output result is that the location code of the component is not found in the location code database.

[0026] As a specific implementation scheme, a set of possible component names and a set of possible component part numbers of the target aircraft are obtained; the set of possible component names and the set of possible component part numbers respectively include at least one possible component name and at least one possible component part number of the component.

[0027] In the second multi-level comparison decision strategy, the possible component names and possible component part numbers are compared and matched with the component feature dataset in the location coding database as component names and component part numbers.

[0028] As a specific implementation scheme, in the second multi-level comparison decision strategy, when the comparison and matching of one feature data or at least two feature data combinations among the component name, component part number, component area number, and component configuration is successful, but the unique mapping relationship between the location code and the component still cannot be output, a decision node with the location view as the comparison parameter is added. The unique mapping relationship is confirmed through the location view of the component. When the comparison and matching of this decision node fails, the judgment result that the location code of the component does not exist in the location code database is output.

[0029] As a specific implementation plan, in the first multi-level comparison decision strategy, the comparison parameters of each decision node are, in order, the combination features of the component identification number, the component area number, the component configuration, the component part number, and the component name;

[0030] If the output result of any decision node fails to match, the result of the failed comparison with the first multi-level comparison decision strategy is output, and the location coding database is updated; otherwise, the result of the successful comparison with the first multi-level comparison decision strategy is output, and the location coding database is not updated.

[0031] The method for creating a component installation location coding database based on a single mechanism type according to claim 3 is characterized in that, in the second multi-level comparison decision strategy, the part number comparison is used as the comparison parameter of the first decision node. In response to the comparison matching result of the first decision node, a second decision node Y is generated if the matching is successful, and a second decision node N is generated if the matching fails.

[0032] The second decision node Y uses the combination of component part number, component name, and component area number as the comparison parameters for this decision node.

[0033] The second decision node N uses the combination of possible component part number, component name and component area number as the comparison parameters of this decision node;

[0034] In response to the comparison and matching result of the second decision node Y, if the comparison and matching is successful, the result of successful comparison and matching with the second multi-level comparison and decision strategy is output, and the database is not updated; in response to the comparison and matching result of the second decision node Y, if the comparison and matching fails, the result of failed comparison and matching with the second multi-level comparison and decision strategy is output, and the database is updated.

[0035] In response to the comparison and matching result of the second decision node N, if the comparison and matching is successful, a third decision node is generated; if the comparison and matching fails, the result of the failure to compare and match with the second multi-level comparison decision strategy is output, and the database is updated.

[0036] The third decision node uses the configuration of the component as the comparison parameter. In response to the comparison and matching result of the third decision node, if the comparison and matching is successful, it outputs the result of the successful comparison and matching with the second multi-level comparison and decision strategy, without updating the database; if the comparison and matching fails, it outputs the result of the failed comparison and matching with the second multi-level comparison and decision strategy, and updates the database.

[0037] The method for creating a component installation location coding database based on a single mechanism type according to claim 3 is characterized in that the possible component name set and the possible component part number set are updated to the location coding database.

[0038] As one specific implementation, the location coding database also includes a location view mapped to the location codes of the components.

[0039] As a specific implementation plan, the decision-making process based on the first multi-level comparative decision-making strategy is as follows:

[0040] Step Y1: Read the delivery data of the target aircraft. The delivery data includes the identification number and area code of the target aircraft's parts.

[0041] Step Y2: Based on the mapping relationship between position codes and component feature data in the position code database, determine whether the position code database stores component data for the target aircraft configuration; if yes, proceed to step Y3; if no, proceed to step Y4.

[0042] Step Y3: Based on the installed component data, traverse and compare the component data under this aircraft type in the position coding database to determine whether the position coding in the position coding database maps and associates with the complete installed component data; if yes, then do not update the position coding database; if no, then add the missing installed component data into the position coding database to update the position coding database.

[0043] Step Y4: Create a new location code in the location code database, map the assembled parts data to the location code to form parts data, and find the possible part numbers and names of the parts corresponding to the location codes based on the assembled parts data and technical documents and add them to the parts data in the location code database.

[0044] As a specific implementation scheme, the specific process of determining whether the location coding database stores component data for the target aircraft configuration in step Y2 is as follows:

[0045] Step Y21: Compare the combination of component identification number and area number in the component data with the combination of area number and identification number in the location coding database to determine if there is any data that can be successfully compared. If yes, proceed to step Y22; otherwise, proceed to step Y23.

[0046] Step Y22: Based on the mapping relationship between all position codes and configuration expressions corresponding to the successfully compared combination data, a set of configuration expressions is formed. The target aircraft configuration is compared with each configuration expression in the set of configuration expressions. If the comparison is successful, it is determined that the position code database stores the component data under the target aircraft configuration; if the comparison fails, it is determined that the position code database does not store the component data under the target aircraft configuration.

[0047] Step Y23: Based on the identification number of the component in the assembly component data, perform a comparison search in the location coding database to determine if it is found. If it is found, proceed to step Y24; otherwise, determine that the location coding database does not store component data for the target aircraft type.

[0048] Step Y24: Based on the mapping relationship between all position codes and configuration expressions corresponding to the found identification number, a set of configuration expressions is formed. The target aircraft configuration is compared with each configuration expression in the set of configuration expressions. If the comparison is successful, it is determined that the position code database stores the component data of the target aircraft configuration; if the comparison fails, it is determined that the position code database does not store the component data of the target aircraft configuration.

[0049] As a specific implementation plan, the decision-making process based on the second-level multi-level comparative decision-making strategy is as follows:

[0050] Step N1: Based on the part number of the assembled parts, traverse and compare the location coding database to determine if a matching part number is found; if yes, proceed to step N2; if no, proceed to step N3.

[0051] Step N2: Compare the combination of part number, name, and area code in the assembled parts data with the combination of part number and name in the location coding database to determine if there is a matching combination in the location coding database; if yes, do not update the database; if no, proceed to step N21.

[0052] Step N21: Create a new location code in the location code database, map the installed component data to the location code to form component data, and find the possible part numbers and names of the components corresponding to the location codes based on the installed component data and technical data and add them to the component data in the location code database to complete the database update.

[0053] Step N3: Based on the part number of the assembled component, obtain all possible part numbers that can be interchanged with it, and compare and search the possible part numbers in the location coding database to determine whether a matching part number can be found; if yes, proceed to step N4; if no, proceed to step N5.

[0054] Step N4: Combine the assembled parts and all possible matching part numbers found in the location coding database to form a part number dataset. Then, find the location code corresponding to each part number in the part number dataset in the location coding database to form a location code set. Add all the part numbers in the part number dataset to the part number corresponding to each location code in the location code set to form a new part number dataset in the location coding database.

[0055] The system compares the component name, part number, and region number of the assembled components with the component name, part number, and region number in the location coding database to determine if there is a corresponding configuration in the location coding database that matches the target aircraft configuration. If yes, proceed to step N41; otherwise, proceed to step N42.

[0056] Step N41: Based on the installed component data, traverse and compare the component data under this aircraft type in the position coding database to determine whether the position coding in the position coding database maps and associates with the complete installed component data; if yes, then do not update the position coding database; if no, then add the missing installed component data into the position coding database to update the position coding database.

[0057] Step N42: Create a new location code in the location coding data, and traverse and compare the component data of the aircraft type in the location coding database according to the installed component data. Fill the missing installed component feature data into the mapped and associated location code to complete the database update.

[0058] As a specific implementation scheme, step N4 also includes the following processes:

[0059] Step N4.1: Compare the combination of component name, component number, and area number of the assembled component with the component name, component number, and area number in the location code database. If no matching combination is found, compare the combination of component number and area number of the assembled component with the component number and area number in the location code database.

[0060] Step N4.2: In the position coding database, retrieve the configuration expression corresponding to the position code of the successfully compared combination data, and perform a conformity comparison between the configuration of the target aircraft and the configuration expression.

[0061] As one specific implementation scheme, in the specific implementation process of step N4:

[0062] When the combined data consisting of the component name, component number, and area number of the installed components and the aircraft configuration data can be successfully compared in the location coding database, the location coding database already fully includes the installed component data, and there is no need to update the location coding database.

[0063] When the combined data consisting of the part number and area code of the installed components can be successfully compared with the aircraft configuration data in the location coding database, the following processing is required:

[0064] In the location coding database, the location codes corresponding to the successfully compared part numbers and area numbers form a location coding set. At this time, the location view of the part number on the target aircraft is obtained by querying the aircraft technical data, and this view is compared with the component installation position location views corresponding to all successfully compared part numbers and area numbers in the location coding set. The coordinates of the component installation position station code shown are traversed and compared. If they are consistent, the name description of the component is added to the location coding database. If they are not consistent, step N4.3 is executed.

[0065] Step N4.3: Create a new location code in the location code database and map all part numbers in the new part number dataset, the part names obtained from technical data, and the configuration expression corresponding to the installation position view of the part on the target aircraft to the location code.

[0066] The purpose of a component location coding database based on a single mechanism type is for building digital models of aircraft, specifically implemented as follows:

[0067] After importing and reading the target aircraft delivery data, the target aircraft is matched in the location coding database. If the match is successful, a location code is assigned to each component of the target aircraft, and a digital model of the aircraft is visualized by using the location view associated with the location code. If the corresponding target aircraft cannot be matched in the location coding database, the location coding database is updated based on the target aircraft's delivery data.

[0068] A component installation location coding database storage device stores a location coding database created based on the method for creating a component installation location coding database of the single-structure type described above.

[0069] An execution device for a method of creating a component installation location coding database, comprising a memory and a processor, to implement the aforementioned creation method;

[0070] Memory is used to store location-coded databases and computer programs or instructions that are executed on a processor.

[0071] The aforementioned computer program or instructions are loaded and executed by the processor to implement the aforementioned method for creating a location-encoded database based on a single-structure model.

[0072] The technical solution of this application has at least the following advantages and beneficial effects:

[0073] 1. In this invention, there is a unique association between aircraft components and their installation locations based on the aircraft configuration. However, current aircraft maintenance information management systems lack standardized installation location definitions for aircraft components based on their configuration, which easily leads to errors in component management. This invention constructs a component location coding database, assigning a location code to each component. This enables the efficient and accurate representation of the installation location of each component.

[0074] 2. In this invention, the established location code is associated with the location diagram, which enables the quick indexing and display of the possible installation location of the component on the aircraft after the specified component is found in the database. The staff only needs to select the installation location on the view to quickly and accurately locate the component installation position, which provides convenience for aircraft maintenance management, improves work efficiency and accuracy, and avoids the problem of component positioning difficulties caused by inaccurate expression or misunderstanding by the staff in the past.

[0075] 3. The configuration of an aircraft determines the types, quantities, and locations of its components. Differences in aircraft configurations lead to significant variations in the types, quantities, and locations of components. Therefore, a single aircraft model cannot be simply used as a representative of all aircraft models; each model requires specific analysis and creation based on its unique configuration. In this invention, components are coded according to their individual configurations, ensuring that each component can be quickly and accurately located. This enables configuration-based reliability data acquisition and allows for more granular reliability data analysis.

[0076] 4. This database can be updated in real time based on the delivery data of the target aircraft to ensure the completeness of the data, and it has accurate comparison and identification methods for both parts with and without identification numbers, thus making it more widely applicable.

[0077] 5. When aircraft manufacturers deliver aircraft data, they often treat the digital model as core technology and a secret, and do not provide it to aircraft operators. This results in cumbersome component inspection during maintenance, requiring staff to spend a significant amount of time consulting technical documents. However, based on the component location coding database of this invention, visualized digital modeling of components can be completed conveniently and quickly.

[0078] 6. This invention locates the installation position of each component based on its configuration, enabling refined reliability data collection and analysis based on configuration and positioning, thus overcoming the shortcomings of traditional aircraft maintenance information management systems in reliability data collection and analysis. Attached Figure Description

[0079] Figure 1 This is a configuration representation of the Airbus A320 family of aircraft.

[0080] Figure 2 A partial illustration showing the markings for different configurations of the Airbus A320 family of aircraft during modification.

[0081] Figure 3 Diagram illustrating the relationship between aircraft configuration and position coding;

[0082] Figure 4 The relationship between flight configuration, configuration expression, and position encoding;

[0083] Figure 5 A diagram illustrating the relationship between component mounting location codes and aircraft configuration.

[0084] Figure 6 A diagram illustrating the fields of a location-encoded database;

[0085] Figure 7 This is a system flowchart of the present invention;

[0086] Figure 8 This is a flowchart illustrating the process of using the identification number as a decision node in this invention.

[0087] Figure 9 This is a flowchart of the first multi-level comparative decision-making strategy;

[0088] Figure 10 This is a flowchart illustrating the response when the output of the first decision node in the second multi-level comparison decision strategy is negative.

[0089] Figure 11 This is a flowchart illustrating the process when the output of the first decision node in the second multi-level comparison decision strategy is "yes".

[0090] Figure 12 for Figure 11 The diagram illustrates the process of using the combination of name, part number, and region number as decision nodes and responding with a negative output. Detailed Implementation

[0091] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the present invention will be briefly introduced below in conjunction with the accompanying drawings and descriptions of the embodiments or the prior art. Obviously, the following description of the structure of the accompanying drawings is only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. It should be noted that the description of these embodiments is for the purpose of helping to understand the present invention, but does not constitute a limitation of the present invention.

[0092] It should be understood that although the terms first, second, etc., may be used herein to describe various modules, these modules should not be limited by these terms. These terms are only used to distinguish one module from another. For example, a first module may be referred to as a second module, and similarly, a second module may be referred to as a first module, without departing from the scope of the exemplary embodiments of the invention.

[0093] It should be understood that the term "and / or" that may appear in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, B exists alone, and A and B exist simultaneously. The term " / and" that may appear in this document describes another relationship between related objects, indicating that two relationships can exist. For example, A / and B can mean: A exists alone, and A and B exist alone. In addition, the character " / " that may appear in this document generally indicates that the related objects before and after it are in an "or" relationship.

[0094] To facilitate understanding of the embodiments, the applicant provides a description of the prior art as follows:

[0095] In practice, aircraft manufacturers provide technical documentation for the aircraft they manufacture, including but not limited to: AMM manuals, IPC manuals, CMM manuals, etc. Once an aircraft is produced and delivered, a delivery list will be provided.

[0096] The technical data of an aircraft can be obtained from its configuration data, which includes the aircraft type, engine type, MOD list, SB list, etc.

[0097] Aircraft configuration can be represented by configuration combination expressions, which represent a combination of one or more configuration expressions. Configuration expressions are divided into basic expressions and state expressions. The aircraft type and engine model are the basic expressions for aircraft configuration. Taking the MOD number as an example, the MOD number is a numerical code representing a certain modification state. The POST mark before the MOD indicates that the aircraft has performed the modification corresponding to that MOD number; the PRE mark before the MOD indicates that the aircraft has not performed the modification corresponding to that MOD number; the MOD number + POST / PRE mark is the state expression of the aircraft configuration, such as... Figure 1 The figure shows some configuration expressions of the Airbus A320 family of aircraft. Based on the determination of multiple configuration expressions, the configuration combination expression of the aircraft can be obtained, and thus the configuration of the aircraft can be determined.

[0098] Each aircraft has corresponding configuration data, including the aircraft type, engine type, and MOD (Modification of Designations) list. The MOD list displays all modifications performed on the aircraft during the manufacturing phase, expressed in the form of a MOD list. The MOD list includes the aircraft type, serial number, MOD number, and specific details corresponding to the MOD number, such as:

[0099] MOD number "161035" indicates that the aircraft was equipped with auxiliary central fuel tank number 1.

[0100] MOD number "161036" indicates that the aircraft was equipped with auxiliary central fuel tank number 2.

[0101] MOD number "161037" indicates that the aircraft was equipped with auxiliary central fuel tank number 4.1.

[0102] If the configuration delivery list for an aircraft contains MOD number "161035", then it is "POST-161035", indicating that the aircraft is equipped with auxiliary center fuel tank No. 1. Similarly, if the configuration delivery list for an aircraft does not contain "161036", then it is "PRE-161036", indicating that the aircraft is not equipped with auxiliary center fuel tank No. 2. If the configuration delivery list for an aircraft does not contain "161037", then it is "PRE-161037", indicating that the aircraft is not equipped with auxiliary center fuel tank No. 4.1.

[0103] Based on this, different combinations of configuration expressions characterize different flight configurations.

[0104] The delivery list provided by the aircraft manufacturer refers to the list of characteristic data of the parts installed on the aircraft, which is delivered to the aircraft operator (such as an airline). Each line of the delivery list represents a part, and the information includes the aircraft type (Type), MSN (Manufacturing Serial Number), Owner, Zone (Airbus encodes aircraft zone numbers, each zone number representing a region of the aircraft body), Description, Identification Number (FIN for Airbus, LIN for COMAC, hereinafter referred to as Identification Number), Part Number (i.e., the part type), and Serial Number.

[0105] In some cases, certain components do not have identification numbers.

[0106] To facilitate understanding of this invention, this application provides explanations of important technical terms and concepts:

[0107] Component Name - Description of Components: In aircraft technical data, there may be multiple names for a component at a certain installation location.

[0108] Part number - describes the part model. In the aircraft's technical data, for a part number of a part at a certain installation location, the relationship between the part number and the part name is: one name corresponds to at least one part number.

[0109] Part identification numbers (MINs) are used to functionally / logically identify parts installed in a specific location. Therefore, it is possible for multiple identical MINs to exist in different locations on the same aircraft, meaning that multiple parts on an aircraft may perform completely identical functions. In other words, multiple parts located in different locations correspond to one MIN.

[0110] Parts Zone Number - In the aircraft parts installation and delivery list, parts with identification numbers are marked with a ZONE number to indicate their regional location.

[0111] MOD number - various numerical codes, indicating a certain modification status (the modification reflects the installation status of a certain component in a certain location). If the MOD number can be found in the MOD list of an aircraft, it means that the aircraft has performed the modification (that is, the component indicated by the MOD number was installed at the installation location indicated by the MOD number); a MOD number may refer to a single location where a single component is installed or multiple locations where the component is installed.

[0112] MOD Status - This indicates whether the modification has been performed. The MOD status is the most basic configuration expression, and different configurations of the aircraft have performed different modifications.

[0113] Aircraft configuration – the layout and number of aircraft components are entirely determined by the aircraft configuration. Different configurations or combinations of configurations map to different component installation layouts and quantities. Therefore, an aircraft configuration is represented by a set of configuration expressions consisting of multiple configuration expressions.

[0114] Location coding – a concept introduced in this invention, refers to assigning a location code to the installation location of an aircraft component. One location code may correspond to multiple component part numbers and multiple component names. One location code may correspond to multiple aircraft configurations (i.e., different aircraft configurations may all have this installation location).

[0115] Example 1

[0116] The first aspect of this embodiment provides a method for creating a component position coding database based on a single mechanism type, the implementation of which includes the following process:

[0117] Step 1: Create an initial configuration-based component location coding database;

[0118] Step 2: Obtain the feature data of the target aircraft parts and compare it with the feature dataset of the parts in the location coding database based on a multi-level comparison decision strategy; if the comparison is successful, keep the record in the location coding database unchanged; if the comparison fails, update the record in the location coding database.

[0119] In this embodiment, the data on the delivered components for the target aircraft includes the following data with a mapping relationship: component name, component number, component identification number, component area number, and aircraft type to which the component belongs.

[0120] In this embodiment, the component location coding database includes component data, which includes the following mapping relationships: location code, component name, component part number, component identification number, component area number, and aircraft type to which the component belongs. Since some components lack identification numbers / area numbers, their component identification numbers / area numbers are empty values ​​in the component location coding database.

[0121] Furthermore, for aircraft, factors such as model compatibility, system differences, varying internal standards, and component development and updates mean that component names and part numbers may not be unique. Therefore, in the component location coding database, component names include a set of possible names, and component part numbers include a set of possible part numbers. That is, from aircraft technical data, it can be known that a component can be replaced by components with other part numbers, and different part numbers may correspond to different names.

[0122] As for the data of the installed components, it is already in the actual installation stage. Therefore, at this time, the part number and name of the component are unique.

[0123] To facilitate a clearer understanding of the descriptions below, this embodiment defines component name, component part number, component identification number, component region number, and the aircraft type to which the component belongs as component feature data. Therefore, in this invention, the component location coding database includes location codes and component feature data mapped to those location codes.

[0124] Specifically, the component location coding database has the following characteristics:

[0125] (1) Each positional encoding pair can correspond to multiple configuration expressions;

[0126] (2) Each location code corresponds to multiple component part numbers (possible part number set) that can be installed at that location;

[0127] (3) Each location code corresponds to multiple component names (possible name set) that can be installed at that location;

[0128] (4) Each location code corresponds to the component identification number located at that location;

[0129] (5) Each location code corresponds to the aircraft area code to which the location belongs.

[0130] Furthermore, to more intuitively display the location view of the component, each location code is mapped to a location code station view, showing the specific location of the component on the aircraft.

[0131] In some embodiments, a successful comparison in process two indicates that the component location coding database has already stored all component data for that aircraft configuration. Therefore, in process two, each component of the target aircraft can be assigned a location code based on the component location coding database. Furthermore, since the location codes in the location coding database are mapped to location views, a digital model of the target aircraft can be established after a complete comparison of the data in the component location coding database with the target aircraft.

[0132] Furthermore, in process two, the multi-level comparison decision strategy includes a first multi-level comparison decision strategy and / or a second comparison decision strategy; when the acquired target aircraft component feature data includes a component identification number, the first multi-level comparison rule is adopted; when the acquired target aircraft component feature data does not include a component identification number, the second multi-level comparison rule is adopted.

[0133] The first multi-level comparison decision strategy is to compare components based on component identification number, component area number, aircraft configuration, component part number, and component name.

[0134] The second multi-level comparison decision strategy is a traversal comparison based on component identification number, component name, component area number, and aircraft configuration.

[0135] Example 2

[0136] The implementation of process one is as follows:

[0137] Step A1: Establish the mapping relationship between flight configuration, configuration expression, and position encoding. The implementation of this step is as follows:

[0138] Step A11: Obtain all modification statuses included in a series of aircraft;

[0139] Step A12: Mark the aircraft of each configuration under this series of aircraft to indicate whether the above-mentioned modification status has been performed;

[0140] refer to Figure 2 As shown, this represents a partial effect of the markings indicating the aircraft modification status for each configuration within the series of aircraft.

[0141] Step A13: Based on the configuration determination formula obtained from the aircraft technical data, determine the configuration of the aircraft by considering the obtained aircraft type, engine, and modification status. The aircraft configuration is represented by the field corresponding to the configuration combination expression.

[0142] Step A14: Obtain all configuration expressions corresponding to the aircraft configuration;

[0143] Step A15: Establish the position codes of the components corresponding to the configuration expressions; and establish the configuration expressions corresponding to the position codes; the position codes reflect the installation positions of the components on the aircraft;

[0144] The application logic of this step in practical application scenarios is as follows: Figure 3 As shown in Table 1.

[0145] from Figure 3 As can be seen, the A321 series configuration aircraft all include four coding positions: PC-A320S-00001, PC-A320S-00002, PC-A320S-00003, and PC-A320S-00004. Therefore, the correspondence between aircraft configuration and position coding is shown in Table 1.

[0146] The position codes PC-A320S-00005 and PC-A320S-00006 are only found on aircraft with the A321-PRE-FLEX configuration.

[0147] The four position codes PC-A320S-00007, PC-A320S-00008, PC-A320S-00009, and PC-A320S-00010 are only found on aircraft in the A321-POST-FLEX configuration. Therefore, once the aircraft configuration is identified, it's known which position codes (i.e., which component installation locations) the aircraft should have. Figure 4 As shown.

[0148] Table 1: Relationship between component location codes and aircraft configuration representation

[0149] Location coding Configurational expression PC-A320S-00001 A321 PC-A320S-00002 A321 PC-A320S-00003 A321 PC-A320S-00004 A321 PC-A320S-00005 A321-PRE-FLEX PC-A320S-00006 A321-PRE-FLEX PC-A320S-00007 A321-POST-FLEX PC-A320S-00008 A321-POST-FLEX PC-A320S-00009 A321-POST-FLEX PC-A320S-00010 A321-POST-FLEX

[0150] Step A16: Obtain all position codes (i.e., component installation positions) corresponding to the aircraft configuration.

[0151] Step A17: Establish the mapping relationship between flight configuration, configuration expression, and position code. Figure 5 As shown.

[0152] When the delivery list of the target aircraft is searched / compared by the computer with the indicated location codes and their configuration mapping relationship database, the computer can determine which parts of the aircraft are installed in the database.

[0153] Step A2: Associate the aircraft component feature data with the component location codes to form an initial configuration-based component location code database.

[0154] like Figure 6 The image shows a schematic diagram of a specific location coding database. The location coding database includes fields such as identification number (…). Figure 6 The information includes the FIN number, possible name, possible part number, location code, area number, configuration, and Chinese name of the location.

[0155] Each location code on the aircraft is unique. The component installed at the location corresponding to this location code may have multiple names, multiple part numbers, and belong to multiple aircraft types. Therefore, the location code database uses possible names and possible part numbers as fields.

[0156] When an aircraft leaves the factory, the characteristic data of the components installed on the aircraft are delivered to the aircraft operator in the form of a list (i.e., a delivery list). The delivery list includes the aircraft model corresponding to the component, the MSN (Sequence Number), the owner, the area code of the aircraft where the component is located, the component name, the component identification number, the component part number, and the component serial number. Some components do not have an area code or identification number.

[0157] Since aircraft parts are divided into two types—those with identification numbers and area codes, and those without identification numbers and area codes—the implementation of step A2 is divided into method B and method C, as detailed below:

[0158] (1) Method B, which does not have an identification number or area code, is as follows:

[0159] Step B1: Obtain the target component based on the delivery data;

[0160] Step B2: Obtain the positions of the components within the aircraft configuration based on the aircraft configuration;

[0161] Step B3: Obtain the component feature data corresponding to the target location code based on the aircraft technical data;

[0162] Step B4: Assign a location code to the target component so that the location code is associated with the component feature data in step B3.

[0163] It should be noted that aircraft technical data provides relatively comprehensive information. By consulting the aircraft technical data, one can find all the part numbers of all components installed at a certain component's installation location, as well as the possible names of the components corresponding to those part numbers.

[0164] Finally, through step B4 above, a mapping relationship was established between location code, aircraft configuration, component name (possible name set), and component part number (possible part number set).

[0165] (2) Method C, which includes an identification number and a region number, is as follows:

[0166] Currently, the aircraft delivery manifest includes area codes to indicate the location of parts with identification numbers.

[0167] An identification number represents the function / logic of a component installed at a specific location on an aircraft; therefore, the identification number possesses a "location attribute." Due to variations in aircraft configurations, the installation layout and quantity of components with identification numbers will also differ. The specific implementation of the method includes:

[0168] Step C1: Based on the target component identification number, search for the component feature data corresponding to the component identification number in all delivery lists, and establish the association between the target component identification number and the component name, component part number and aircraft identification number;

[0169] In this step, the aircraft identification number refers to the aircraft's registration number and / or the aircraft's manufacturing serial number (MSN), which is a unique identifier for the aircraft.

[0170] Step C2: Based on the aircraft technical manual, obtain the name and part number of the component to be installed at the location indicated by the target component identification number;

[0171] Step C3: Locate the MOD number corresponding to the part name of the target part identification number in the MOD list of the aircraft with the corresponding aircraft identification number;

[0172] Step C4: Assign position codes to components and map the position codes to component feature data using configuration expressions based on MOD numbers.

[0173] Example 3

[0174] In this invention, the implementation of process two is the core focus. The configuration-based initial position coding database enables the following: after importing and reading the target aircraft delivery list, if a match can be found in the component position coding database, position codes can be assigned to each component of the target aircraft. This allows for the visualization and creation of a digital model of the aircraft through position views associated with the position codes. However, if no match is found in the database, it indicates that the database lacks data for that target aircraft, necessitating an update to the position coding database based on the target aircraft's delivery data.

[0175] Based on this, in the above embodiments, the first step involves building an initial location coding database. This initial database can be a blank database, meaning that all fields in the component location coding database, including the mapping relationship location code, component name, component part number, aircraft configuration, aircraft model, component identification number, and component area number, are empty. The component location coding database is then populated and updated by importing the target aircraft delivery list.

[0176] The implementation of process two is explained in detail below:

[0177] like Figure 8 As shown, since not all parts in the delivery list of the target aircraft have identification numbers, the implementation of Process Two requires first using the identification number as a comparison parameter to form decision nodes, and then adopting different processing methods based on whether the part has an identification number. Specifically, the implementation of Process Two includes the following steps:

[0178] The delivery list of the target aircraft is read, and it is determined whether each aircraft component data has a corresponding identification number. If so, the first multi-level comparison decision strategy is executed; otherwise, the second comparison decision strategy is executed. The delivery list includes the aircraft configuration data and the data of each installed component.

[0179] like Figure 9 As shown, the decision-making process of the first multi-level comparison decision strategy is as follows:

[0180] Step Y1: Read the delivery data of the target aircraft. The delivery data includes the identification number and area code of the target aircraft's parts.

[0181] Step Y2: Based on the mapping relationship between position codes and component feature data in the position code database, determine whether the position code database stores component data for the target aircraft configuration; if yes, proceed to step Y3; if no, proceed to step Y4.

[0182] Step Y3: Based on the installed component data, traverse and compare the component data under this aircraft type in the position coding database to determine whether the position coding in the position coding database maps and associates with the complete installed component data; if yes, then do not update the position coding database; if no, then add the missing installed component data into the position coding database to update the position coding database.

[0183] In step Y3, if the mapping relationship between the installed component data and the location code cannot be accurately confirmed through the installed component data, the accurate association mapping between the installed component data and the location code is performed by consulting the aircraft technical data.

[0184] Step Y4: Create a new location code in the location code database, map the assembled parts data to the location code to form parts data, and find the possible part numbers and names of the parts corresponding to the location codes based on the assembled parts data and technical documents and add them to the parts data in the location code database.

[0185] Furthermore, in step Y2, the specific implementation process for determining whether the location coding database stores component data for the target aircraft configuration is as follows:

[0186] Step Y21: Compare the combination of component identification number and area number in the component data with the combination of area number and identification number in the location coding database to determine if there is any data that can be successfully compared. If yes, proceed to step Y22; otherwise, proceed to step Y23.

[0187] Step Y22: Based on the mapping relationship between all position codes and configuration expressions corresponding to the successfully compared combination data, a set of configuration expressions is formed. The target aircraft configuration is compared with each configuration expression in the set of configuration expressions. If the comparison is successful, it is determined that the position code database stores the component data under the target aircraft configuration; if the comparison fails, it is determined that the position code database does not store the component data under the target aircraft configuration.

[0188] Step Y23: Based on the identification number of the component in the assembly component data, perform a comparison search in the location coding database to determine if it is found. If it is found, proceed to step Y24; otherwise, determine that the location coding database does not store component data for the target aircraft type.

[0189] Step Y24: Based on the mapping relationship between all position codes and configuration expressions corresponding to the found identification number, a set of configuration expressions is formed. The target aircraft configuration is compared with each configuration expression in the set of configuration expressions. If the comparison is successful, it is determined that the position code database stores the component data of the target aircraft configuration. If the comparison fails, it is determined that the position code database does not store the component data of the target aircraft configuration.

[0190] like Figure 10-12 As shown, the decision-making process of the second multi-level comparison decision strategy is as follows:

[0191] Step N1: Based on the part number of the assembled parts, traverse and compare the location coding database to determine if a matching part number is found; if yes, proceed to step N2; if no, proceed to step N3.

[0192] Step N2: Compare the combination of part number, name, and area code in the assembled parts data with the combination of part number and name in the location coding database to determine if there is a matching combination in the location coding database; if yes, do not update the database; if no, proceed to step N21.

[0193] Step N21: Create a new location code in the location code database, map the assembled parts data to the location codes to form parts data, and based on the assembled parts data and technical documents, find the possible part numbers and names of the parts corresponding to the location codes and add them to the parts data in the location code database to complete the database update.

[0194] Step N3: Based on the part number of the assembled component, obtain all possible part numbers that can be interchanged with it, and compare and search the possible part numbers in the location coding database to determine whether a matching part number can be found; if yes, proceed to step N4; if no, proceed to step N5.

[0195] Step N4: Combine the assembled parts and all possible matching part numbers found in the location coding database to form a part number dataset. Then, find the location code corresponding to each part number in the part number dataset in the location coding database to form a location code set. Add all the part numbers in the part number dataset to the part number corresponding to each location code in the location code set to form a new part number dataset in the location coding database.

[0196] The system compares the component name, part number, and region number of the assembled components with the component name, part number, and region number in the location coding database to determine if there is a corresponding configuration in the location coding database that matches the target aircraft configuration. If yes, proceed to step N41; otherwise, proceed to step N42.

[0197] Step N41: Based on the installed component data, traverse and compare the component data under this aircraft type in the position coding database to determine whether the position coding in the position coding database maps and associates with the complete installed component data; if yes, then do not update the position coding database; if no, then add the missing installed component data into the position coding database to update the position coding database.

[0198] Step N42: Create a new location code in the location coding data, and traverse and compare the component data of the aircraft type in the location coding database according to the installed component data. Fill the missing installed component feature data into the mapped and associated location code to complete the database update.

[0199] Furthermore, in aircraft manufacturing and maintenance, a component part number typically corresponds to a specific component name. This correspondence is to ensure the uniqueness and traceability of components. However, in some cases, a component part number may correspond to multiple component names, such as when a component is multi-purpose or when multiple sub-components in a modular design share the same part number. Therefore, the implementation of step N4 also includes the following processes:

[0200] Step N4.1: Compare the combination of component name, component number, and area number of the assembled component with the component name, component number, and area number in the location code database. If no matching combination is found, compare the combination of component number and area number of the assembled component with the component number and area number in the location code database.

[0201] Step N4.2: In the position coding database, retrieve the configuration expression corresponding to the position code of the successfully compared combination data, and perform a conformity comparison between the configuration of the target aircraft and the configuration expression.

[0202] It is worth noting that in the specific implementation of step N4:

[0203] 1. When the combined data consisting of the component name, component number, and area number of the installed component and the aircraft configuration data can be successfully compared in the location coding database, the location coding database already fully includes the installed component data, and there is no need to update the location coding database.

[0204] 2. Since the part numbers in the location coding database being compared at this time are a [new part number dataset], if the combined data consisting only of the part number and area code of the installed parts and the aircraft configuration data can be successfully compared with the location coding database, then further confirmation is needed to verify the accuracy of the location coding;

[0205] In the location coding database, the location codes corresponding to the successfully compared part numbers and area numbers form a location coding set. At this time, the location view of the part number on the target aircraft is obtained by querying the aircraft technical data, and this view is compared with the location views of the component installation positions corresponding to all successfully compared [part numbers and area numbers] in the location coding set. The coordinates of the shown component installation position station codes are traversed and compared. If they are consistent, the name description of the component is added to the location coding database. If they are not consistent, step N4.3 is executed.

[0206] Step N4.3: Create a new location code in the location code database and map all part numbers in the new part number dataset, the part names obtained from technical data, and the configuration expression corresponding to the installation position view of the part on the target aircraft to the location code.

[0207] The second aspect of this embodiment provides the use of a component position coding database based on a single mechanism type for building digital models of aircraft, specifically implemented as follows:

[0208] After importing and reading the target aircraft delivery data, the target aircraft is matched in the location coding database. If the match is successful, a location code is assigned to each component of the target aircraft, and a digital model of the aircraft is visualized by using the location view associated with the location code. If the corresponding target aircraft cannot be matched in the location coding database, the location coding database is updated based on the target aircraft's delivery data.

[0209] The third aspect of this embodiment provides a storage device based on a single-structure type position coding database for storing a position coding database created based on the above-described method for creating a single-structure type component installation position coding database.

[0210] In this embodiment, the storage device can be a local server, cloud server, floppy disk, optical disk, hard disk, flash memory, USB flash drive, and / or Memory Stick.

[0211] The fourth aspect of this embodiment provides an execution device for a method of creating a component installation location coding database based on a single mechanism type, so as to implement the above-described creation method;

[0212] Memory is used to store location-coded databases and computer programs or instructions that are executed on a processor.

[0213] The aforementioned computer program or instructions are loaded and executed by the processor to implement the aforementioned method for creating a location-encoded database based on a single-structure model.

[0214] In other possible embodiments, the memory is divided into external memory and internal memory. The external memory stores the location coding database, while the internal memory stores the computer programs or instructions executed on the processor.

[0215] In this embodiment, the external storage can be a local server, cloud server, floppy disk, optical disk, hard disk, flash memory, USB flash drive, and / or Memory Stick; the internal storage can be random access memory (RAM), read-only memory (ROM), flash memory, first-in-first-out (FIFO) memory, and / or first-in-last-out (FILO) memory, etc. Specifically, the processor can include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor can be implemented using at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), or PLA (Programmable Logic Array). The processor can also include a main processor and a coprocessor. The main processor, also known as the CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state.

[0216] In some embodiments, the processor may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. For example, the processor may not be limited to microprocessors of the STM32F105 series, reduced instruction set computer (RISC) microprocessors, x86 architecture processors, or processors with integrated embedded neural network processing units (NPUs). The execution device may also include, but is not limited to, a power module, a display screen, and other necessary components.

[0217] The working process, working details and technical effects of the electronic device provided in this embodiment can be found in the first aspect of the embodiment, and will not be repeated here.

[0218] The various embodiments of the present invention have now been described in detail. To avoid obscuring the concept of the invention, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions of this invention based on the above description, and the scope of the invention is defined by the appended claims.

Claims

1. A method for creating a component installation location coding database, characterized in that, Its implementation includes the following processes: Create an initial configuration-based component location coding database; the location coding database includes component location codes and component feature datasets associated with the location code mappings; the component feature datasets contain at least three types of component feature data; The location code is unique and represents the installation location of a component; Component feature data includes: component name, component part number, location code configuration, component identification number, and component region number; component identification refers to the component's functional / logical identification number. Acquire the feature data of the target aircraft parts and compare it with the feature dataset of the parts in the location coding database based on a multi-level comparison decision strategy; if the comparison is successful, keep the record in the location coding database unchanged; if the comparison fails, update the data in the location coding database. The multi-level comparison decision strategy includes a first multi-level comparison decision strategy and / or a second multi-level comparison decision strategy; when the acquired target aircraft component feature data includes component identification numbers, the first multi-level comparison rule is used; when the acquired target aircraft component feature data does not include component identification numbers, the second multi-level comparison rule is used. The first multi-level comparison decision strategy is to compare components based on component identification number, component area number, aircraft configuration, component part number, and component name. The second multi-level comparison decision strategy is to compare components based on their names, part numbers, region numbers, and aircraft configurations.

2. The method for creating a component installation location coding database according to claim 1, characterized in that, If the comparison fails, the location encoding database is updated using at least one of the following methods: Update Method 1: If the location code of the component is not in the location code database, create the location code of the component in the location code database and add the component feature dataset associated with the location code. Update Method 2: If the feature dataset of the component in the location coding database is missing feature data, then update the feature data associated with the location coding mapping of the component in the location coding database; In the first multi-level comparison decision strategy, in response to the failure of comparison matching of one feature data or at least two feature data combinations in the component identification number, component area number, and configuration, the result of the judgment that the location code of the component is not found in the location code database is output. In the second multi-level comparison decision strategy, in response to the failure of comparison matching of one feature data or at least two feature data combinations among the component name, component part number, component area number, and component configuration, the output result is that the location code of the component is not found in the location code database.

3. The method for creating a component installation location coding database according to claim 2, characterized in that, Obtain the set of possible component names and the set of possible component part numbers for the target aircraft; the set of possible component names and the set of possible component part numbers each include at least one possible component name and at least one possible component part number for that component. In the second multi-level comparison decision strategy, the possible component names and possible component part numbers are compared and matched with the component feature dataset in the location coding database as component names and component part numbers.

4. The method for creating a component installation location coding database according to claim 3, characterized in that, In the second multi-level comparison decision strategy, when the comparison and matching of one feature data or at least two feature data combinations among the component name, component part number, component area number, and component configuration is successful, but the unique mapping relationship between the location code and the component still cannot be output, a decision node with the location view as the comparison parameter is added. The unique mapping relationship is confirmed through the location view of the component. When the comparison and matching of this decision node fails, the judgment result that the location code of the component does not exist in the location code database is output.

5. The method for creating a component installation location coding database according to claim 1, characterized in that, In the first multi-level comparison decision strategy, the comparison parameters of each decision node are, in order, the combination features of the component identification number and the component area number, the configuration to which the component belongs, the component part number, and the component name; If the output result of any decision node fails to match, the result of the failed comparison with the first multi-level comparison decision strategy is output, and the location coding database is updated; otherwise, the result of the successful comparison with the first multi-level comparison decision strategy is output, and the location coding database is not updated.

6. The method for creating a component installation location coding database according to claim 3, characterized in that, In the second multi-level comparison decision strategy, the combination of component name and part number is compared as the comparison parameter of the first decision node. In response to the comparison matching result of the first decision node, a successful match generates the second decision node Y, and a failed match generates the second decision node N. The second decision node Y uses the combination of component part number, component name, and component area number as the comparison parameters for this decision node. The second decision node N uses the combination of possible component part number, component name and component area number as the comparison parameters of this decision node; In response to the comparison and matching result of the second decision node Y, if the comparison and matching is successful, the result of successful comparison and matching with the second multi-level comparison and decision strategy is output, and the database is not updated; in response to the comparison and matching result of the second decision node Y, if the comparison and matching fails, the result of failed comparison and matching with the second multi-level comparison and decision strategy is output, and the database is updated. In response to the comparison and matching result of the second decision node N, if the comparison and matching is successful, a third decision node is generated; if the comparison and matching fails, the result of the failure to compare and match with the second multi-level comparison decision strategy is output, and the database is updated. The third decision node uses the configuration of the component as the comparison parameter. In response to the comparison and matching result of the third decision node, if the comparison and matching is successful, it outputs the result of the successful comparison and matching with the second multi-level comparison and decision strategy, without updating the database; if the comparison and matching fails, it outputs the result of the failed comparison and matching with the second multi-level comparison and decision strategy, and updates the database.

7. The method for creating a component installation location coding database according to claim 3, characterized in that, The possible component name set and possible component part number set are updated to the location coding database.

8. The method for creating a component installation position coding database based on a single-structure model according to claim 1, characterized in that, The location coding database also includes location views that map the location codes of components.

9. The method for creating a component installation location coding database according to claim 1, characterized in that, The decision-making process based on the first-level multi-comparison decision-making strategy is as follows: Step Y1: Read the delivery data of the target aircraft. The delivery data includes the identification number and area code of the target aircraft's parts. Step Y2: Based on the mapping relationship between position codes and component feature data in the position code database, determine whether the position code database stores component data for the target aircraft configuration; if yes, proceed to step Y3; if no, proceed to step Y4. Step Y3: Based on the installed component data, traverse and compare the component data under this aircraft type in the position coding database to determine whether the position coding in the position coding database maps and associates with the complete installed component data; if yes, then do not update the position coding database; if no, then add the missing installed component data into the position coding database to update the position coding database. Step Y4: Create a new location code in the location code database, map the assembled parts data to the location code to form parts data, and find the possible part numbers and names of the parts corresponding to the location codes based on the assembled parts data and technical documents and add them to the parts data in the location code database.

10. The method for creating a component installation location coding database according to claim 9, characterized in that, In step Y2, the specific implementation process for determining whether the location coding database stores component data for the target aircraft configuration is as follows: Step Y21: Compare the combination of component identification number and area number in the component data with the combination of area number and identification number in the location coding database to determine if there is any data that can be successfully compared. If yes, proceed to step Y22; otherwise, proceed to step Y23. Step Y22: Based on the mapping relationship between all position codes and configuration expressions corresponding to the successfully compared combination data, a set of configuration expressions is formed. The target aircraft configuration is compared with each configuration expression in the set of configuration expressions. If the comparison is successful, it is determined that the position code database stores the component data under the target aircraft configuration; if the comparison fails, it is determined that the position code database does not store the component data under the target aircraft configuration. Step Y23: Based on the identification number of the component in the assembly component data, perform a comparison search in the location coding database to determine if it is found. If it is found, proceed to step Y24; otherwise, determine that the location coding database does not store component data for the target aircraft type. Step Y24: Based on the mapping relationship between all position codes and configuration expressions corresponding to the found identification number, a set of configuration expressions is formed. The target aircraft configuration is compared with each configuration expression in the set of configuration expressions. If the comparison is successful, it is determined that the position code database stores the component data of the target aircraft configuration. If the comparison fails, it is determined that the position code database does not store the component data of the target aircraft configuration.

11. The method for creating a component installation location coding database according to claim 1, characterized in that, The decision-making process based on the second-level multi-comparison decision-making strategy is as follows: Step N1: Based on the part number of the assembled parts, traverse and compare the location coding database to determine if a matching part number is found; if yes, proceed to step N2; if no, proceed to step N3. Step N2: Compare the combination of part number, name, and area code in the assembled parts data with the combination of part number and name in the location coding database to determine if there is a matching combination in the location coding database; if yes, do not update the database; if no, proceed to step N21. Step N21: Create a new location code in the location code database, map the installed component data to the location code to form component data, and find the possible part numbers and names of the components corresponding to the location codes based on the installed component data and technical data and add them to the component data in the location code database to complete the database update. Step N3: Based on the part number of the assembled parts, obtain all possible part numbers that can be interchanged with it, and compare and search the possible part numbers in the location coding database to determine whether a matching part number can be found; if so, proceed to step N4. If not, proceed to step N5; Step N4: Combine the assembled parts and all possible matching part numbers found in the location coding database to form a part number dataset. Then, find the location code corresponding to each part number in the part number dataset in the location coding database to form a location code set. Add all the part numbers in the part number dataset to the part number corresponding to each location code in the location code set to form a new part number dataset in the location coding database. The system compares the component name, part number, and region number of the assembled components with the component name, part number, and region number in the location coding database to determine if there is a corresponding configuration in the location coding database that matches the target aircraft configuration. If yes, proceed to step N41; otherwise, proceed to step N42. Step N41: Based on the installed component data, traverse and compare the component data under this aircraft type in the position coding database to determine whether the position coding in the position coding database maps and associates with the complete installed component data; if yes, then do not update the position coding database; if no, then add the missing installed component data into the position coding database to update the position coding database. Step N42: Create a new location code in the location coding data, and traverse and compare the component data of the aircraft type in the location coding database according to the installed component data. Fill the missing installed component feature data into the mapped and associated location code to complete the database update.

12. The method for creating a component installation location coding database according to claim 11, characterized in that, The implementation of step N4 also includes the following processes: Step N4.1: Compare the combination of component name, component number, and area number of the assembled component with the component name, component number, and area number in the location code database. If no matching combination is found, compare the combination of component number and area number of the assembled component with the component number and area number in the location code database. Step N4.2: In the position coding database, retrieve the configuration expression corresponding to the position code of the successfully compared combination data, and perform a conformity comparison between the configuration of the target aircraft and the configuration expression.

13. The method for creating a component installation location coding database according to claim 12, characterized in that, In the specific implementation of step N4: When the combined data consisting of the component name, component number, and area number of the installed components and the aircraft configuration data can be successfully compared in the location coding database, the location coding database already fully includes the installed component data, and there is no need to update the location coding database. When the combined data consisting of the part number and area code of the installed components can be successfully compared with the aircraft configuration data in the location coding database, the following processing is required: In the location coding database, the location codes corresponding to the successfully compared parts and area numbers form a location coding set. At this time, the location view of the part number on the target aircraft is obtained by querying the aircraft technical data, and this view is compared with the component installation location views corresponding to all successfully compared parts and area numbers in the location coding set. The coordinates of the component installation position code are traversed and compared. If they are consistent, the name description of the component is added to the location coding database. If they are not consistent, step N4.3 is executed. Step N4.3: Create a new location code in the location code database and map all part numbers in the new part number dataset, the part names obtained from technical data, and the configuration expression corresponding to the installation position view of the part on the target aircraft to the location code.

14. The application of a component location coding database, characterized in that, The digital modeling of the aircraft is specifically implemented as follows: After importing and reading the target aircraft delivery data, the target aircraft is matched in the location coding database. If the match is successful, a location code is assigned to each component of the target aircraft. Thus, a digital model of the aircraft is visualized and built through the location view associated with the location code. If the target aircraft cannot be matched in the location coding database, the location coding database is updated based on the delivery data of the target aircraft.

15. A component installation location coding database storage device, characterized in that, The system stores a component installation location coding database created based on the method for creating a component installation location coding database according to any one of claims 1-7.

16. An execution device for a method of creating a component installation location coding database, for implementing the creation method according to any one of claims 1-13, characterized in that, Including memory and processor; Memory is used to store location-coded databases and computer programs or instructions that are executed on a processor. The aforementioned computer program or instructions are loaded and executed by the processor to implement the aforementioned method for creating a location-encoded database based on a single-structure model.

Images