A coding lifecycle control method for aircraft business objects

Abstract

This invention relates to the field of information technology in the aviation industry, specifically to a method for controlling the lifecycle of codes for aircraft business objects during aircraft development. How to effectively control the lifecycle of business object codes—both to recycle recyclable codes to save coding resources and to avoid situations where a single code represents multiple objects—is a problem that needs to be considered. This invention provides a method for controlling the lifecycle of codes for aircraft business objects based on the business system in which the code corresponds, the business status of the business object, and the status of the code in the coding management system. This solves the problem in aircraft development where coding resources may not be actually used after being acquired, leading to resource waste and potentially insufficient coding resources for business objects. This method achieves closed-loop control and effective utilization of coding resources, effectively supporting the unique coding of each business object and the application of that coding during the aircraft development process.

Description

Technical Field

[0001] This invention relates to the field of information technology in the aviation industry, specifically to a coding lifecycle control method for aircraft business objects in aircraft development. Background Technology

[0002] Aircraft are a very complex product, containing tens of thousands of parts, which can be divided into self-made parts, standard parts, finished products, etc. They also include many technical standards, technical specifications, technical reports, test reports and other documents that support the development process, as well as various change processes and change documents for user technical status management. All these business objects need to be coded, and it is necessary to ensure that each item has a unique code.

[0003] During aircraft development, companies typically define coding rules for various business objects. Aircraft designers can manually number these objects according to these rules and use them in the business systems. Companies with a high level of IT infrastructure build coding management systems to achieve structured management of business object coding rules. These systems are integrated with various business systems, allowing aircraft designers to directly generate and apply codes for business objects within these systems. The codes obtained by aircraft designers are stored in the current business system along with the business object. However, as business objects are issued or related business processes are integrated, the business object and its code are transferred from the current system to another, and then to yet another. For example, the code for an aircraft's 3D digital model is initially stored in the design-related PDM system. As development progresses, it is subsequently transferred to manufacturing-related CAPP, ERP, MES, and other business systems. With business objects and their codes being stored and transferred across multiple business systems, controlling the lifecycle of business object codes—both to recycle recyclable codes to save coding resources and to avoid situations where a single code represents multiple objects—is a crucial issue that IT personnel in the aviation industry need to consider. Summary of the Invention

[0004] The purpose of this invention is to provide a coding lifecycle control method for aircraft business objects. This method establishes coding lifecycle control rules based on the lifecycle status of the business object and the business system in which the business object is located, thereby achieving closed-loop control of the coding lifecycle.

[0005] This invention proposes a coding lifecycle control method for aircraft business objects, which includes the following steps:

[0006] Step 1: Establish a unified coding management system;

[0007] Step 2: Establish a business system for aircraft business objects;

[0008] Step 3: If a code retrieval request is sent from the business system to the code management system, a temporary code for the business object will be generated in the code management system.

[0009] Step 4: Confirm the temporary code of the business object in the code management system, then generate the formal code of the business object in the code management system and store it in the code management system;

[0010] Step 5: Create a business object in the business system and store the generated business object's formal code as the business object code;

[0011] Step Six: If a new business object needs to be created in the existing business system, return to Step Three; if a new business system needs to be created, return to Step Two; if an existing business object code needs to be deleted, the status of the business object needs to be determined. If the business object has been deployed to other business systems, it cannot be deleted or modified; if the business object has not been deployed to other business systems, it can be deleted, and the corresponding formal business object code stored in the code management system must also be deleted.

[0012] Advantageously, in step three, the last few digits of the temporary code for the business object are serial numbers, generated sequentially in chronological order and never repeated.

[0013] Advantageously, in step three, the coding rule corresponding to the business object is selected in the coding management system, and a temporary code for the business object is generated in the coding management system by inputting or selecting the rule instance field.

[0014] Advantageously, after generating the temporary code for the business object in step four, if the coding request is cancelled, the temporary code for the business object is also cancelled and does not occupy coding resources.

[0015] Advantageously, in step four, once the formal code of a business object is stored in the code management system, the formal code of the business object can be deleted to release the occupied code resources; if the formal code of a business object already stored in the code management system is not used, it can be reused.

[0016] Advantageously, the formal code of the business object generated in step four may be the same as or different from the temporary code of the business object.

[0017] Advantageously, in step five, once the business object code is stored in the business system, the business object code serves as the unique identifier of the business object within the business system and cannot be altered.

[0018] Advantageously, regularly check the formal codes of business objects in the code management system. If there are formal codes of business objects that are not used by the business system, they can be used or deleted.

[0019] Beneficial Effects: This invention provides a control method for the lifecycle of aircraft business object codes, based on the business system in which the corresponding business object resides, the business status of the business object, and the status of the code in the code management system. This solves the problem in aircraft development where code resources may not be actually used after being acquired, leading to resource waste and potentially insufficient code resources for business objects. This method achieves closed-loop control and effective utilization of code resources, effectively supporting the unique coding of each business object and the application of those codes during aircraft development. Attached Figure Description

[0020] Figure 1 This is a schematic diagram illustrating the generation of temporary codes in a coding management system, as provided in an embodiment of the present invention.

[0021] Figure 2 This is a schematic diagram illustrating the generation of business object codes in a business system, as provided in an embodiment of the present invention.

[0022] Figure 3 This is a schematic diagram illustrating the creation of a business object and storage of its encoding in a business system, as provided in an embodiment of the present invention.

[0023] Figure 4 This is a schematic diagram illustrating the transfer of a business object between two business systems, provided as an embodiment of the present invention.

[0024] Figure 5 This is an example of a coding lifecycle control logic provided in an embodiment of the present invention. Detailed Implementation

[0025] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0026] Figure 1 This indicates that the coding management system and business system 1 have been integrated. Coding requests in business system 1 will connect to the coding management system. When an aircraft designer intends to create business object 1 in business system 1 and clicks the "Retrieve Coding" button, a request is sent to the coding management system. In the coding management system, the aircraft designer specifies coding rule 1 and further sets the values ​​of field 1 and field 2 to obtain the code XXXYYY003. This code is a temporary code for the business object, and 003 is the serial number. Before the aircraft designer clicks the "Confirm" button in the coding management system, this code remains temporary and is not stored in the coding management system. Clicking the "Cancel" button in the coding management system abandons the coding request, and the occupied coding resources XXX, YYY, and 003 are released.

[0027] Figure 2 This is a schematic diagram illustrating the generation of a business object code in a business system according to an embodiment of the present invention. An aircraft designer clicks the confirmation button in the code management system, officially generating the business object code. However, since multiple aircraft designers are simultaneously requesting code generation, the final code obtained according to the request sequence is XXXYYY005. This code is immediately stored in the code management system and simultaneously displayed in business system 1. If the aircraft designer clicks the cancel button in business system 1, the code is only stored in the code management system, and the aircraft designer can delete the code to release the occupied resources. If the aircraft designer creates a new business object corresponding to the coding rule in business system 1 again, the code can be used directly without needing to retrieve the code again.

[0028] Figure 3 This is a schematic diagram illustrating the creation of a business object and storage of its code in a business system, as provided in an embodiment of the present invention. An aircraft designer clicks the "OK" button in business system 1, and the business system completes the creation of business object 1, storing the business object code XXXYYY005 in business system 1. The business object's business status is now "modifiable." At this point, the aircraft designer can delete the business object from business system 1, and the business object code is also deleted from business system 1 simultaneously. Furthermore, the aircraft designer can delete the code corresponding to the business object in the code management system to release the occupied resources.

[0029] Figure 4 This is a schematic diagram illustrating the transfer of a business object between two business systems according to an embodiment of the present invention. Due to the needs of aircraft development, business object 1 is transferred from business system 1 to business system 2 as the development process progresses. In business system 1, the business state of business object 1 is set to frozen. In business system 2, business object 1 is received and created, and its code is also stored in business system 2, with the business object's state set to modifiable. At this time, business object 1 can be deleted in business system 2, and the corresponding business object code is also deleted from business system 2. However, since business object 1 is already stored in business system 1 and is in a frozen business state, this deletion cannot release the resources occupied by the code.

[0030] Figure 5This invention provides an example of code lifecycle control logic. When a temporary code is generated in the code management system, the aircraft designer can abandon the current code request to release the occupied code resources. When a code has been stored in the code management system and become a formal code, if the code only exists in the code management system and has not yet been stored in business system 1, the code can be deleted to release the occupied resources. If the business object corresponding to the code has been stored in business system 1 and its business status is modifiable, the business object can be deleted, and further, the code in the code management system can be deleted to release the code resources. If the business object corresponding to the code has been stored in business system 1 and its business status is frozen, this indicates that the business object has been transferred to another business system, and neither the business object nor the corresponding code is allowed to be deleted.

[0031] The above description is merely a specific embodiment of the present invention, providing a detailed description of the invention. Parts not covered herein are conventional techniques. However, the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. The scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A coding lifecycle control method for aircraft business objects, characterized in that, The method includes the following steps: Step 1: Establish a unified coding management system; Step 2: Establish a business system for aircraft business objects; Step 3: If a code retrieval request is sent from the business system to the code management system, a temporary code for the business object will be generated in the code management system. Step 4: Confirm the temporary code for the business object in the coding management system. Then, generate the official code for the business object in the coding management system and store it there. If the coding application request is cancelled after the temporary code is generated, the temporary code will also be cancelled and will not occupy coding resources. Once the official code for the business object is stored in the coding management system, it can be deleted to release the occupied coding resources. An unused official code for a business object stored in the coding management system can be reused. Regularly check the official codes for business objects in the coding management system; if there are unused official codes, they can be used or deleted. Step 5: Create a business object in the business system and store the generated business object's official code as the business object code; once the business object code is stored in the business system, it serves as the unique identifier of the business object in the business system and cannot be modified. Step Six: If a new business object needs to be created in the existing business system, return to Step Three; if a new business system needs to be created, return to Step Two; if an existing business object code needs to be deleted, the status of the business object needs to be determined. If the business object has been deployed to other business systems, it cannot be deleted or modified; if the business object has not been deployed to other business systems, it can be deleted, and the corresponding formal business object code stored in the code management system must also be deleted.

2. The coding lifecycle control method according to claim 1, characterized in that: In step three, the last few digits of the temporary code for the business object are serial numbers, generated sequentially in chronological order and never repeated.

3. The coding lifecycle control method according to claim 1, characterized in that: In step three, select the coding rule corresponding to the business object in the coding management system, and generate a temporary code for the business object in the coding management system by inputting or selecting the rule instance field.

4. The coding lifecycle control method according to claim 1, characterized in that: The formal code of the business object generated in step four may be the same as or different from the temporary code of the business object.

Images