Effectiveness change management method and system based on auxiliary identifier, and medium

Abstract

The invention relates to the technical state management field, and relates to an auxiliary identification-based validity change management method and system, and a medium, and the method comprises the steps: 1, under a product node, dividing an LRU by taking a CI as a unit, and determining a configuration number and an initial product auxiliary identification number; 2, defining a technical state change object and a change mode; 3, when the technical states of the CI and the LRU on the lower layer of the CI are changed, determining an auxiliary identification number of the CI; 4, configuring a product composition state; two types of auxiliary identification codes and an identification code evolution rule based on a replacement mode are adopted, when the technical state of the aviation product is changed through a product data management system, the system automatically calculates and changes the validity identification of the product LRU by identifying whether the replacement mode is a one-way replacement mode or a two-way replacement mode, and meanwhile, when a new state product structure tree is constructed, a new state product structure tree is constructed. According to the method, a product manager can be helped to quickly judge the replacement relation between the LRUs in different technical states through the identification codes, and the change history of the technical states is improved while the replacement relation between the LRUs in the different technical states is judged; and the problems that the validity identifier is difficult to understand and the management is complicated when the aviation products are managed by using the traditional batch validity are also solved.

Description

Technical Field

[0001] The present invention relates to the field of technical status management, and more particularly to a technical status management for aviation airborne products, and specifically to a method, system and medium for validity change management based on auxiliary identification. Background Art

[0002] Technical status control is an engineering management technology and method, and its goal is to ensure that the requirements of users for product functions, physical characteristics, etc. are reflected in design and production, and ultimately to achieve user requirements. Among them, the validity identification plays a role of clearly and accurately recording the technical status of the product in technical status management.

[0003] When technical status managers control the technical status of aviation products in the product data management system, they need the system to quickly and clearly construct product structure trees of different configurations and technical statuses. The traditional validity based on batch batches is not applicable to aviation airborne products. The technical status of aviation airborne products is not based on flight batches or batch batches, and designers are concerned about the replacement relationship between different technical status LRU. Directly using the validity defined based on batch batches will face the problem that the identification is difficult to understand.

[0004] How to identify aviation products through new validity, control the technical status of aviation products, and quickly identify the replacement relationship between LRU has become a problem that technical status managers and product managers need to consider. Summary of the Invention

[0005] The technical problem solved by the present invention: A method, system and medium for validity change management based on auxiliary identification are proposed to solve the problem that the identification is difficult to understand when directly using the validity defined based on batch batches in the prior art; aiming at the problems existing in the prior art, the object of the present invention is to propose a method, system and medium for validity change management based on auxiliary identification. This method uses two types of auxiliary identification codes and an identification code evolution rule based on the replacement method. Through the product data management system, when the technical status of an aviation product changes, the system automatically calculates and changes the validity identification of the product LRU by identifying whether it is a one-way or two-way replacement method, and at the same time, when constructing the product structure tree of the new state, uses pointers to point to the nodes of the original state product tree and the new version nodes. This method has a clear process and a fast product tree construction speed, which can help product managers quickly judge the replacement relationship between LRU of different technical statuses through the identification code, and at the same time, when recording the technical status change history, it also solves the problems of difficult-to-understand validity identification and complex management when using traditional batch batch validity to manage aviation products.

[0006] Technical Solution of the Present Invention

[0007] A method for managing the validity change based on auxiliary identification includes the following steps:

[0008] Step 1: Under the product node, divide the LRU by CI as the unit, and determine the configuration model number and the initial product auxiliary identification number, where CI is the configuration item and LRU is the field replacement unit;

[0009] Step 2: Define the technical status change object and the change method;

[0010] Step 3: When the technical status of the CI and its lower-level LRU changes, determine the auxiliary identification number of the CI;

[0011] Step 4: Configure the product composition status.

[0012] Furthermore, in Step 1, when dividing the LRU by CI as the unit, each CI under the product corresponds to an LRU one by one. In the product data management system, assign the configuration model number and the main code M of the auxiliary identification code to each CI node 主 and the secondary code M of the auxiliary identification code 副 , the initial M 主 and M 副 are both empty, and then, according to whether there is coexistence of multiple validity states in the LRU and the category of technical status change, perform the assignment and change of each CI node.

[0013] Furthermore, the specific process of performing the assignment and change of each CI node is as follows: If the initial value of the CI node is empty, assign a non-empty main code M of the auxiliary identification code and the secondary code M of the auxiliary identification code to the CI node 主 and the secondary code M of the auxiliary identification code 副 , if the value of the CI node is non-empty, change the main code M of the auxiliary identification code and the secondary code M of the auxiliary identification code of the CI node 主 and the secondary code M of the auxiliary identification code 副 .

[0014] Furthermore, Step 2 is specifically as follows: The engineering and technical personnel initiate a change application related to the technical status on the product structure tree editing page in the product data management system. This change application needs to clearly define the CI node and number to be modified, as well as the change method, that is, the engineering and technical personnel take the LRU as the unit, judge whether the LRU node generates multiple states, and then select whether this change is a version change or a validity change in the change application creation form. If the change method is a validity change, it is also necessary to select whether this change is a one-way replacement or a two-way replacement.

[0015] Furthermore, Step 3 is based on the change application in Step 2. The product data management system identifies the CI node under the corresponding product node, reads the change method data in the change application, and takes the LRU as the unit to perform relevant judgments and operations.

[0016] Further, perform relevant judgments and operations, including:

[0017] c. If there is no coexistence of multiple states in the LRU, then replace the version of the original LRU, and the model number, main code, and secondary code of the auxiliary identification code remain unchanged;

[0018] d. If there are multiple states in the LRU, then generate a new configuration LRU and a new version of the CI, and judge the auxiliary identification code M 主 and the secondary code M of the auxiliary identification code 副 of the value, and determine the subsequent changes according to the following rules;

[0019] a) If the auxiliary identification codes M 主 and M 副 are empty and it is a one-way change, then set M 主 to A, set M 副 to 1, and A represents the value assigned to M 主 ;

[0020] b) If the auxiliary identification codes M 主 and M 副 are empty and it is a two-way change, then set M 主 to X, set M 副 to 1, and X represents the value assigned to M 主 ;

[0021] c) If the auxiliary identification codes M 主 and M 副 are not empty and it is a one-way change, then shift the value of M 主 one place forward in the alphabet, and set M 副 to 1;

[0022] d) If the auxiliary identification codes M 主 and M 副 are not empty and it is a two-way change, then increment the value of M 副 by one.

[0023] Further, in c), when the auxiliary identification code M 主 is shifted forward in the alphabet, the three letters I, O, and X should be skipped. When the current auxiliary identification code M 主 is Z, the value after shifting forward in the alphabet is AA.

[0024] Further, step 4: Configure the product composition status, including:

[0025] After the technical status of each LRU under the product changes, the product data management system counts the changes of each LRU, lists the product tree obtained by the effective permutation and combination of different LRU nodes, that is, it is recorded that there are N LRU under the product, and the i-th LRU contains k i coexisting technical statuses, then the product effectiveness is a total of species;

[0026] When the product data management system generates different state product trees through permutation and combination, it does not generate instance nodes separately at the LRU nodes of each tree, but points to the actual version of the LRU node through a pointer;

[0027] The product supervisor selects the actually valid product tree, and the validity combinations of the LRU contained in the product tree are all different. At this time, the product validity is used to identify the product tree, that is, the product tree is identified by two Arabic numerals: starting from 01 and increasing sequentially.

[0028] A validity change management system based on auxiliary identification, comprising:

[0029] Initial determination unit: configured to divide the LRU in units of CI under the product node, and determine the configuration model number and the initial product auxiliary identification number, where CI is the configuration item and LRU is the field replacement unit;

[0030] Definition unit: configured to define the technical state change object and the change method;

[0031] Auxiliary identification number determination unit: configured to determine the auxiliary identification number of the CI when the technical state of the CI and its lower-level LRU changes;

[0032] Configuration unit: configured to configure the product composition state.

[0033] A computer storage medium stores computer-executable instructions, and the computer-executable instructions are used to execute the foregoing validity change management method based on auxiliary identification.

[0034] Beneficial effects

[0035] The present invention proposes a validity change management method, system and medium based on auxiliary identification, which can quickly judge their replacement relationships according to the validity identifications of different states of the CI: if the main code M of the auxiliary identification 主 is the same, they can be interchanged bidirectionally. If the main code M of the auxiliary identification 主 is different, the state with a later alphabetical order can be unidirectionally replaced by the state with a higher alphabetical order. At the same time, the main code of the auxiliary identification code of the CI node also records the number of times of unidirectional replacement of this node. At the same time, when the product data management system points to the actual version of the LRU node through a pointer to construct product structure trees with different validities, this method and generating instances for the CI nodes under each tree, which requires storing the method of information containing instance node information, only needs to store the node information in the original product structure tree and the information of subsequent new versions. The total number of stored nodes is

[0036] Through the product data management system, all possible product validities can be configured and filtered based on the CI validity at the product node. When there are a large number of CI nodes under a product, the conventional method based on batch lot status management is relatively complex. By means of the combination based on the validity of CI nodes, the development information is extracted, which enhances the intensity of status control and helps to improve the efficiency of management work. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 It is a flowchart for calculating the auxiliary identification code of the present invention;

[0038] Figure 2 It is an evolution example diagram provided by an embodiment of the present invention;

[0039] Figure 3a It is a schematic diagram showing that there are multiple statuses for multiple CI nodes under a product provided by an embodiment of the present invention;

[0040] Figure 3b It is a schematic diagram for configuring product validity provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] The features and illustrative embodiments of various aspects of the present invention will be described in detail below. In the following detailed description, many specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is only intended to provide a better understanding of the present invention by showing examples of the present invention. The present invention is in no way limited to any specific settings and methods set forth below, but covers any improvements, substitutions, and modifications of structures, methods, and devices without departing from the spirit of the present invention. Well-known structures and technologies are not shown in the drawings and the following description to avoid unnecessarily obscuring the present invention.

[0042] It should be noted that, without conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other, and the various embodiments may refer to and cite each other. The present invention will be described in detail below with reference to the drawings and in combination with the embodiments.

[0043] An embodiment of the present invention is: to provide a method for managing validity change based on auxiliary identification,

[0044] including the following steps:

[0045] Step 1: Under the product node, divide the LRU by CI, determine the configuration model number and the initial product auxiliary identification number, where CI is the configuration item and LRU is the field replaceable unit; in Step 1, the product manager divides the LRU by CI, and the CI and LRU under each product correspond one by one. The configuration model number, the main code M of the auxiliary identification code are assigned to each CI node in the product data management system. 主 And the secondary code M of the auxiliary identification code 副 , the initial M 主 And M 副 Are both empty, and then according to whether there is coexistence of multiple validity states in the LRU and the situation of the technical state change category, the assignment and change of each CI node are carried out.

[0046] Among them, the specific process of assigning and changing each CI node is as follows: if the initial value of the CI node is empty, then assign a non-empty main code M of the auxiliary identification code and the secondary code M of the auxiliary identification code to the CI node 主 And the secondary code M of the auxiliary identification code 副 , if the value of the CI node is non-empty, change the main code M of the auxiliary identification code and the secondary code M of the auxiliary identification code of the CI node 主 And the secondary code M of the auxiliary identification code 副 .

[0047] Step 2: Define the technical state change object and the change method;

[0048] The engineering and technical personnel initiate a technical state-related change application on the product structure tree editing page in the product data management system for the CI node under the product node. This change application needs to clearly define the CI node and number to be modified, as well as the change method, that is, the engineering and technical personnel take the LRU as the unit, judge whether the LRU node generates multiple states, and then select whether this change is a version change or a change of validity in the change application creation form. If the change method is a change of validity, it is also necessary to select whether this change is a one-way replacement or a two-way replacement.

[0049] Step 3: When the technical state of the CI and its lower-level LRU changes, determine the auxiliary identification number of the CI;

[0050] Step 3 is based on the change application in Step 2. The product data management system identifies the CI node under the corresponding product node, reads the change method data in the change application, and takes the LRU as the unit to perform relevant judgments and operations.

[0051] Furthermore, the relevant judgments and operations include:

[0052] a. If there is no coexistence of multiple states in the LRU, then reissue the original LRU, and the configuration model number, the main code and the secondary code of the auxiliary identification code remain unchanged;

[0053] b. If the LRU has multiple states, generate a new configuration of the LRU and a new version of the CI, and judge the auxiliary identification code M 主 and the auxiliary identification code secondary code M 副 value, and determine subsequent changes according to the following rules;

[0054] a) If the auxiliary identification code M 主 and M 副 are empty and it is a one-way change, set M 主 to A, set M 副 to 1, and A represents the value given to M 主 ;

[0055] b) If the auxiliary identification code M 主 and M 副 are empty and it is a two-way change, set M 主 to X, set M 副 to 1, and X represents the value given to M 主 ;

[0056] c) If the auxiliary identification code M 主 and M 副 are not empty and it is a one-way change, shift the value of M 主 one position forward in the alphabet, and set M 副 to 1; among them, when the auxiliary identification code M 主 is shifted forward in the alphabet, the three letters I, O, and X should be skipped. When the current auxiliary identification code M 主 is Z, the value after shifting forward in the alphabet is AA.

[0057] d) If the auxiliary identification code M 主 and M 副 are not empty and it is a two-way change, add 1 to the value of M 副 .

[0058] Step 4: Configure the product composition status, including:

[0059] After the technical status of each LRU under the product changes, the product data management system counts the changes of each LRU, lists the product tree obtained by the valid permutation and combination of different LRU nodes, that is, it is recorded that there are N LRU under the product, and the i-th LRU contains k i coexisting technical statuses, then there are a total of kinds of product validities;

[0060] When the product data management system generates different state product trees through permutation and combination, it does not generate instance nodes separately at the LRU nodes of each tree, but points to the actual version of the LRU node through a pointer;

[0061] The product manager selects an actually valid product tree. The validity combinations of LRUs contained in the product tree are different. At this time, the product validity is used to identify the product tree, that is, the product tree is identified with two Arabic numerals: starting from 01 and increasing in sequence.

[0062] The second embodiment of the present invention is:

[0063] Figure 3a The following is a schematic diagram of a product structure model applicable to the present invention provided in an embodiment of the present invention. Figure 3a As shown in the figure, the product structure numbered ZP1001 contains three CI nodes: ZP10011010-000-000, ZP10011020-000-000 and ZP10011030-000-000. After dividing the LRU into CI units, each CI node corresponds to a unique LRU, and the structure models are ZP10011010-001-001, ZP10011020-001-003 and ZP10011030-001-001.

[0064] Figure 1 This is a flowchart for calculating the auxiliary identification code of the present invention. When an engineer initiates a change request for LRU-1 and LRU-2 in the product data management system and it is approved, the technical status of the two nodes changes. According to the rules, due to the coexistence of multiple states, new configurations will be generated for both, and the corresponding CI nodes will be upgraded. Therefore, based on CI-1 and LRU1, CI-1 version B and LRU-1 with configuration model ZP10011010-001-002 will be generated. Based on CI-2 and LRU2, CI-2 version C and LRU2 with configuration model ZP10011010-001-004 will be generated.

[0065] Figure 2 This is the data chain of validity identification changes when the validity of the initial status product changes. When the initial status product undergoes unidirectional replacement and bidirectional replacement alternately, the main code and sub-code in the product's validity identification will continue to change. The system can automatically determine the replacement relationship between different product statuses based on the validity main code. Product statuses with the same main code can be bidirectionally replaced. For product statuses with different main codes, the status at the end of the alphabet can be unidirectionally replaced by the status at the front of the alphabet (the status with the main code X is an exception, because it is the value of the main code when the initial status product undergoes bidirectional replacement).

[0066] Since the auxiliary identification code of LRU-1 was empty before the technical state change, the auxiliary identification code of the newly generated LRU-2 through unidirectional replacement is A1. Since the auxiliary identification code of LRU-2 was A2 before the technical state change, the auxiliary identification code of the newly generated LRU-2 through bidirectional replacement is A3. The validity of its corresponding CI nodes is 0001A1 and 0001A3 respectively. At this time, under the ZP1001 product, there are two LRUs with two coexisting technical states.

[0067] Figure 3b This is a schematic diagram for configuring the validity of a product provided by an embodiment of the present invention. Since LRU-1 contains two coexisting technical states, LRU-2 contains two coexisting technical states, and LRU-3 contains one technical state, therefore, theoretically, the technical states of this product total types. Use two Arabic numerals to identify and sort them in the order of natural numbers, and obtain the product technical state situation of the ZP1001 product when the technical states of the included LRUs change as shown in Figure 3b . By observing Figure 3b , it can be seen that the initial state of the product ZP1001 has a total of 3 CI nodes. After the validity changes, 2 new version CI nodes are added. Therefore, there are 5 different CI nodes. When the product data management system generates a product structure tree with multiple validities, pointers are directly used to point to the above 5 different CI nodes, and no new CI nodes are generated for each validity. The latter will generate nodes, which is 3 times that of the method of the present invention.

[0068] Therefore, the present invention can quickly judge their replacement relationships according to the validity identifications of different states of the CI: if the main code M of the auxiliary identification 主 is the same, they can be interchanged bidirectionally; if the main code M of the auxiliary identification 主 is different, the state with a later alphabetical order can unidirectionally replace the earlier state. At the same time, the main code of the auxiliary identification code of the CI node also records the number of times of unidirectional replacement of this node. At the same time, when the product data management system points to the actual version of the LRU node through a pointer to construct a product structure tree with different validities, this method and generating instances for the CI nodes under each tree require storing nodes with instance node information during the generation process. Compared with this, only the node information in the original product structure tree and the information of subsequent new versions need to be stored, and the total number of stored nodes is

[0069] Through the product data management system, all possible product validities can be configured and filtered based on the CI validity at the product node. When there are a large number of CI nodes under a product, the conventional method based on batch lot technical status management is relatively complex. By means of the combination based on the validity of CI nodes, the development information is extracted, which enhances the intensity of technical status control and helps improve the efficiency of management work.

[0070] The third embodiment of the present invention provides a validity change management system based on auxiliary identification, which is applied to the method described above and includes:

[0071] Initial determination unit: configured to divide the LRU in units of CI under the product node, determine the model number and the initial product auxiliary identification number, where CI is the configuration item and LRU is the field replacement unit;

[0072] Definition unit: configured to define the technical status change object and the change method;

[0073] Auxiliary identification number determination unit: configured to determine the auxiliary identification number of the CI when the technical status of the CI and its lower-level LRU changes;

[0074] Configuration unit: configured to configure the product composition status.

[0075] The fourth embodiment of the present invention further provides a computer storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are used to execute the foregoing validity change management method based on auxiliary identification.

[0076] The present invention quickly judges their replacement relationship according to the validity identification of different states of the CI: if the main code M of the auxiliary identification 主 is the same, they can be interchanged bidirectionally. If the main code M of the auxiliary identification 主 is different, the state with a later alphabetical order can be unidirectionally replaced by the state with a previous one. At the same time, the main code of the auxiliary identification code of the CI node also records the number of times of unidirectional replacement of this node. At the same time, when the product data management system points to the actual version of the LRU node through a pointer and constructs a product structure tree with different validities, compared with the method of generating instances for each CI node under each tree, which requires storing the information of the instance nodes during the generation process, only the node information in the original product structure tree and the information of the subsequent new versions need to be stored, and the total number of stored nodes is

[0077] Through the product data management system, all possible product validities can be configured and filtered based on the CI validity at the product node. When the number of CI nodes under the product is large, the conventional management method based on the technical status of batch batches is relatively complex. By means of the combination based on the validity of CI nodes, the development information is extracted, which enhances the intensity of technical status control and helps to improve the efficiency of management work.

[0078] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or substitutions within the technical scope disclosed by the present invention, and these modifications or substitutions should all be covered within the protection scope of the present invention.

Claims

1. A method for effective change management based on auxiliary identification, characterized in that, It includes the following steps: Step 1: Under the product node, divide the LRU by CI, and determine the configuration model number and the initial product auxiliary identification number, where CI is the configuration item and LRU is the field replaceable unit; Step 2: Define the object of technical state change and the change method; Step 3: When the technical state of the CI and its lower-level LRU changes, determine the auxiliary identification number of the CI; Step 4: Configure the product composition status.

2. The method for managing the validity change based on the auxiliary identifier according to claim 1, wherein In Step 1, the LRU is divided by CI, and each CI corresponds to an LRU under each product. In the product data management system, each CI node is assigned a configuration model number, the main code M of the auxiliary identification code 主 and the secondary code M of the auxiliary identification code 副 , with the initial M 主 and M 副 both being empty. Then, according to whether there are multiple validity states coexisting in the LRU and the category of the change in the technical state, each CI node is assigned and changed.

3. The method for managing the validity change based on auxiliary identification according to claim 2, wherein The specific process of assigning and changing each CI node is as follows: If the initial value of the CI node is empty, assign the non-empty main code M of the auxiliary identification code to the CI node 主 and the secondary code M of the auxiliary identification code 副 , if the value of the CI node is non-empty, change the main code M of the auxiliary identification code of the CI node 主 and the secondary code M of the auxiliary identification code 副 .

4. The method for managing the validity change based on the auxiliary identifier according to claim 3, wherein Specifically, in Step 2: The engineering and technical personnel initiate a change application related to the technical state on the product structure tree editing page in the product data management system for the CI node under the product node. This change application needs to clearly define the CI node and number to be modified, as well as the change method. That is, the engineering and technical personnel take the LRU as the unit and judge whether the LRU node has multiple states. Then, in the change application creation form, select whether this change is a version change or a change in validity. If the change method is a change in validity, it is also necessary to select whether this change is a one-way replacement or a two-way replacement.

5. The method for managing the validity change based on the auxiliary identifier according to claim 4, wherein Step 3 is based on the change application in Step 2. The product data management system identifies the CI node under the corresponding product node, reads the change method data in the change application, and takes the LRU as the unit to perform relevant judgments and operations.

6. The method for managing the validity change based on the auxiliary identifier according to claim 5, wherein Performing relevant judgments and operations includes: a. If there is no coexistence of multiple states in the LRU, then change the version of the original LRU, and the configuration model number, the main code and the secondary code of the auxiliary identification code remain unchanged; b. If the LRU has multiple states, generate a new configuration of the LRU and a new version of the CI, and judge the auxiliary identification code M 主 and the auxiliary identification code secondary code M 副 value, and determine the subsequent changes according to the following rules; a) If the auxiliary identification code M 主 , M 副 is empty and it is a one-way change, then set M 主 to A, set M 副 to 1, where A represents the value assigned to M 主 ; b) If the auxiliary identification code M 主 , M 副 is empty and it is a two-way change, then set M 主 to X, set M 副 to 1, where X represents the value assigned to M 主 ; c) If the auxiliary identification code M 主 , M 副 is not empty and is a one-way change, then shift the value of M 主 one position forward in the alphabet and set M 副 to 1; d) If the auxiliary identification code M 主 , M 副 is not empty and is a two-way change, then increment the value of M 副 by one.

7. The method for managing the validity change based on the auxiliary identifier according to claim 6, wherein c), the auxiliary identification code M 主 When sequentially following the alphabet, the three letters I, O, and X should be skipped. When the current auxiliary identification code M 主 is Z, the value after sequential following of the alphabet is AA.

8. The method for managing the validity change based on the auxiliary identifier according to claim 7, wherein Step 4: Configure the product composition status, including: After the technical state of each LRU under the product changes, the product data management system counts the changes of each LRU and lists the product tree obtained by the valid permutation and combination of different LRU nodes. That is, it is recorded that there are N LRUs under the product, and the i-th LRU contains k i coexisting technical states, then there are a total of kinds of product validities; When the product data management system generates different state product trees through permutation and combination, it does not separately generate instance nodes at the LRU nodes of each tree, but points to the actual version of the LRU node through a pointer; The product supervisor selects the actually valid product tree. The validity combinations of the LRU included in the product tree are all different. At this time, use the product validity to identify the product tree, that is, identify the product tree with two Arabic numerals: starting from 01 and increasing sequentially.

9. A validity change management system based on auxiliary identification, which is applied to the method described in claim 8, and is characterized in that, It includes: Initial determination unit: Configured to divide the LRU by CI under the product node, and determine the configuration model number and the initial product auxiliary identification number, where CI is the configuration item and LRU is the field replaceable unit; Definition unit: Configured to define the object of technical state change and the change method; Auxiliary identification number determination unit: Configured to determine the auxiliary identification number of the CI when the technical state of the CI and its lower-level LRU changes; Configuration unit: Configured to configure the product composition status.

10. A computer storage medium storing computer-executable instructions, characterized in that: The computer-executable instructions are used to execute the validity change management method based on the auxiliary identification according to any one of the preceding claims 1 to 8.

Images