Method, device, medium and equipment for constructing aircraft manufacturing multi-process requirement model

Abstract

This application discloses a method, apparatus, medium, and equipment for constructing a multi-process requirement model for aircraft manufacturing, relating to the field of digital technology in aircraft manufacturing. This application determines the model architecture by matching the target project. The entire business process revolves around the defined manufacturing dimensions to technically expand the requirements, forming a multi-process professional requirement model for aircraft manufacturing based on manufacturing concerns. This supports the design of multi-process professional requirements required for aircraft manufacturing engineering. Under the selected dimensions, the collaborative relationship interfaces of different process specialties are defined, realizing the expression of the model's node network relationships. Finally, the content design of manufacturing non-functional requirement indicators is carried out, constructing a model guided by non-functional requirements. This achieves digital management of manufacturing requirement process design to support the implementation of aircraft manufacturing engineering, reduce reliance on process technicians, and effectively improve aircraft manufacturing efficiency.

Description

Technical Field

[0001] This application relates to the field of digital technology in aircraft manufacturing, specifically to a method, apparatus, medium, and equipment for constructing a multi-process requirement model for aircraft manufacturing. Background Technology

[0002] Modern large aircraft are typical complex aviation products. In their manufacturing process, process design needs to understand product requirements and adapt process methods. More importantly, it needs to translate the efficiency, quality, and cost requirements of manufacturing into requirements for realizing complex products. That is, to carry out manufacturability design around the production realization of complex products, complete the analysis of the rationality, feasibility, and affordability of manufacturability, and finally form a manufacturing process requirement model. Based on the manufacturing process requirement model, the manufacturing process can be monitored and controlled.

[0003] Existing methods are primarily used for designing and analyzing demand models for complex aerospace products, but lack directly applicable methods and technologies for the manufacturing process of such products. Currently, the process design process in aircraft manufacturing engineering mainly relies on project experience, using offline communication and face-to-face discussions to plan process requirements and design technical indicators for various process disciplines. This heavily depends on the individual capabilities of process engineers, impacting the efficiency of aircraft manufacturing. Summary of the Invention

[0004] The main objective of this application is to provide a method, apparatus, medium, and equipment for constructing a multi-process requirement model for aircraft manufacturing, aiming to solve the problem in the prior art that there is a lack of directly usable process requirement models in the aircraft manufacturing process.

[0005] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:

[0006] In a first aspect, embodiments of this application provide a method for constructing a multi-process requirement model for aircraft manufacturing, comprising the following steps:

[0007] Match the target project to determine the target architecture dimension of the model;

[0008] The technical aspects of the requirements are elaborated around the target architecture.

[0009] Define the interface for the collaborative relationship between the first process discipline and the second process discipline based on the dimensions of the target architecture and the technology expansion.

[0010] Based on the dimensions of target architecture and technology development, design the content of manufacturing non-functional requirement indicators and construct the target manufacturing process requirement model.

[0011] In one possible implementation of the first aspect, the interface for the collaborative relationship between the first process discipline and the second process discipline is defined according to the dimensions of the target architecture and the technology expansion, including:

[0012] Based on the dimensions of the target architecture and the technology expansion, obtain the first identifier and the second identifier;

[0013] Based on the first identifier and the second identifier, a structured expression of the interface between the first process specialty and the second process specialty is used to define the interface for the collaborative relationship between the first process specialty and the second process specialty.

[0014] In one possible implementation of the first aspect, before defining the interface for the collaborative relationship between the first and second process specialties based on the target architecture dimension and the technology unfolding dimension, the method further includes:

[0015] Based on the requirements of the target project, determine the interface relationships; these relationships include one-to-many and many-to-many relationships.

[0016] Based on the dimensions of target architecture and technology deployment, the interface definition for the collaborative relationship between the first process discipline and the second process discipline is as follows:

[0017] Based on the dimensions of target architecture and technology development, the interface for collaboration between the first process discipline and the second process discipline is defined using interface relationships.

[0018] In one possible implementation of the first aspect, the target architecture dimension of the model is determined by matching based on the target project, including:

[0019] Based on the target project, determine the target architectural dimensions of the model by matching the manufacturing strategy or focus.

[0020] In one possible implementation of the first aspect, after designing the content of manufacturing non-functional requirement indicators based on the target architecture dimension and the technology expansion dimension, and constructing the target manufacturing process requirement model, the method further includes:

[0021] Determine whether the non-functional manufacturing requirements in the target manufacturing process requirement model need to be verified. If the determination is that verification is required, verification is carried out according to the verification plan tasks. The verification plan tasks include calculation tasks, analysis tasks, simulation tasks, and prototype tasks.

[0022] In one possible implementation of the first aspect, after designing the content of manufacturing non-functional requirement indicators based on the target architecture dimension and the technology expansion dimension, and constructing the target manufacturing process requirement model, the method further includes:

[0023] Reuse based on the target manufacturing process requirement model.

[0024] In one possible implementation of the first aspect, reuse is performed based on the target manufacturing process requirements model, including:

[0025] Based on the target manufacturing process requirement model, obtain the requirement model results and related clue relationship results, and publish them;

[0026] Based on the target manufacturing process requirement model, model reuse, workflow reuse, digital clue analysis, and clue-based management are achieved through template generation and digital clue generation.

[0027] Secondly, embodiments of this application provide an apparatus for constructing a multi-process requirement model for aircraft manufacturing, comprising:

[0028] The architecture design module of the manufacturing process requirements model is used to match the target project and determine the target architecture dimensions of the model.

[0029] The manufacturing process requirements decomposition and allocation module is used to technically elaborate on requirements around the target architecture dimension.

[0030] The manufacturing process requirement interface definition module is used to define the collaborative relationship interface between the first process discipline and the second process discipline based on the target architecture dimension and the technology expansion dimension.

[0031] The Manufacturing Process Requirements Content Design Module is used to design the content of non-functional manufacturing requirements indicators based on the target architecture dimension and the technology expansion dimension, and to build the target manufacturing process requirements model.

[0032] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when loaded and executed by a processor, implements the aircraft manufacturing multi-process requirement model construction method provided in any of the first aspects above.

[0033] Fourthly, embodiments of this application provide an electronic device, including a processor and a memory, wherein,

[0034] Memory is used to store computer programs;

[0035] The processor is used to load and execute computer programs to enable electronic devices to perform the aircraft manufacturing multi-process requirement model construction method provided in any of the first aspects above.

[0036] Compared with the prior art, the beneficial effects of this application are:

[0037] This application proposes a method, apparatus, medium, and equipment for constructing a multi-process requirement model for aircraft manufacturing. The method includes: matching with target projects to determine the target architecture dimension of the model; technically expanding the requirements around the target architecture dimension; defining the collaborative relationship interface between a first process specialty and a second process specialty based on the target architecture dimension and the dimensions of the technical expansion; and designing the content of manufacturing non-functional requirement indicators based on the target architecture dimension and the dimensions of the technical expansion, thereby constructing a target manufacturing process requirement model. This application determines the model architecture by matching with target projects. The entire business process revolves around the determined manufacturing dimensions to technically expand the requirements, forming a multi-process professional requirement model for aircraft manufacturing based on manufacturing focus. This supports the design of multi-process professional requirements required for aircraft manufacturing engineering. Under the selected dimension, the collaborative relationship interface of different process specialties is defined, realizing the expression of the model's node network relationship. Finally, the content of manufacturing non-functional requirement indicators is designed, constructing a non-functional requirement-oriented model. This enables digital management of manufacturing requirement process design to support the implementation of aircraft manufacturing engineering, reduce reliance on process technicians, and effectively improve aircraft manufacturing efficiency. Attached Figure Description

[0038] Figure 1 This is a schematic diagram of the electronic device structure of the hardware operating environment involved in the embodiments of this application;

[0039] Figure 2 A flowchart illustrating the method for constructing a multi-process requirement model for aircraft manufacturing provided in this application embodiment;

[0040] Figure 3 A flowchart illustrating step 01 in one implementation of the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment;

[0041] Figure 4 This is a schematic diagram illustrating the technical development of step 02 in the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment under a distributed architecture implementation.

[0042] Figure 5 A schematic diagram illustrating the technical development of step 02 in the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment under a federated architecture implementation.

[0043] Figure 6 A flowchart illustrating step 03 in one implementation of the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment;

[0044] Figure 7 A flowchart illustrating step 04 in one implementation of the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment;

[0045] Figure 8 A flowchart illustrating step 05 in one implementation of the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment;

[0046] Figure 9 A flowchart illustrating step 06 in one implementation of the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment;

[0047] Figure 10 A schematic diagram illustrating the overall characteristics of the target manufacturing process requirement model in the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment;

[0048] Figure 11 A flowchart illustrating one implementation of the aircraft manufacturing multi-process requirement model construction method provided in this application embodiment;

[0049] Figure 12 A schematic diagram of the modules of the aircraft manufacturing multi-process requirement model construction device provided in the embodiments of this application;

[0050] The diagram is labeled as follows: 101-Processor, 102-Communication bus, 103-Network interface, 104-User interface, 105-Memory. Detailed Implementation

[0051] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0052] See attached document Figure 1 , attached Figure 1This is a schematic diagram of the electronic device structure of the hardware operating environment involved in the embodiments of this application. The electronic device may include: a processor 101, such as a central processing unit (CPU), a communication bus 102, a user interface 104, a network interface 103, and a memory 105. The communication bus 102 is used to realize the connection and communication between these components. The user interface 104 may include a display screen and an input unit such as a keyboard. Optionally, the user interface 104 may also include a standard wired interface and a wireless interface. The network interface 103 may optionally include a standard wired interface and a wireless interface (such as a Wi-Fi interface). The memory 105 may be a storage device independent of the aforementioned processor 101. The memory 105 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM), such as at least one disk storage device. The processor 101 may be a general-purpose processor, including a central processing unit, a network processor, etc., or it may be a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component.

[0053] Those skilled in the art will understand that the appendix Figure 1 The structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0054] As attached Figure 1 As shown, the memory 105, which serves as a storage medium, may include an operating system, a network communication module, a user interface module, and a device for constructing multi-process requirements models for aircraft manufacturing.

[0055] In the appendix Figure 1 In the electronic device shown, the network interface 103 is mainly used for data communication with the network server; the user interface 104 is mainly used for data interaction with the user; the processor 101 and the memory 105 in this application can be set in the electronic device. The electronic device calls the aircraft manufacturing multi-process requirement model construction device stored in the memory 105 through the processor 101 and executes the aircraft manufacturing multi-process requirement model construction method provided in the embodiment of this application.

[0056] Modern large aircraft are typical complex aerospace products. Their manufacturing process requires, on the one hand, understanding product requirements and adapting manufacturing methods; on the other hand, and more importantly, translating manufacturing efficiency, quality, and cost requirements into requirements for realizing the complex product. This involves conducting manufacturability design around the production realization of the complex product, completing analyses of the rationality, feasibility, and affordability of manufacturability, and ultimately forming a manufacturing process requirements model. Based on this model, the manufacturing process can be monitored and controlled. Current technologies for solving complex products and systems mainly include traditional systems engineering, model-based systems engineering (MBSE) methods and tools, and software systems. The following three types of methods are primarily used in the requirements design of product objects:

[0057] Functional decomposition method: Primarily uses data flow diagrams to represent key product functions, resource and interface relationships, especially information and control flows. Key model elements include: functions, flows, and data storage. Information modeling method: Primarily uses object-relationship diagrams to represent the organization of resources and information. Key model elements include: objects, relationships, candidates, selections, and constraints. Behavioral analysis method: Primarily uses transformation diagrams to represent the behavior of an object system when objective variables such as time, state, and environment change, as well as the associated specific scenarios that lead to these changes. Key model elements include: states, scenarios, transformation types, and behaviors.

[0058] The methods described above are primarily used for designing and analyzing requirement models for complex products. However, they lack directly applicable methods and technologies for the manufacturing process of complex products. Currently, the process design process in aircraft manufacturing engineering mainly employs project experience-based methods, using offline communication and face-to-face discussions to plan process requirements and design technical indicators for various process disciplines. This approach has the following main drawbacks:

[0059] Traditional demand models focus on functional descriptions, decomposing and designing requirements based on the product system as input and along the Product Breakdown Structure (PBS). They largely lack descriptions of non-functional requirements, such as manufacturing efficiency, quality, and cost. There is also a lack of methods and technologies for constructing such manufacturing demand models.

[0060] In manufacturing engineering, the design of manufacturing process requirements is located at the end of the product development lifecycle. Experience-based manufacturing requirements design often focuses more on non-functional requirements, and may ignore or fail to identify and realize the key requirements from the product itself, resulting in product characteristic assurance quality risks in the manufacturing of complex products.

[0061] There is also a great deal of collaboration among multiple process disciplines in the manufacturing process. However, the collaboration of process requirement design cannot be explicitly expressed and controlled based on personal experience and face-to-face communication.

[0062] Traditional manufacturing process requirements are characterized by "multi-source heterogeneity," making it difficult to digitize and make explicit the management of requirements, making them difficult to reuse, and making it impossible to find control points in the manufacturing process according to the focus of attention.

[0063] Currently, in terms of information system platforms for requirements design, whether it's dedicated requirements management software like IBM DOORS and Dassault Systèmes Reqtify, or the requirements design modules within mainstream product lifecycle management software, the mainstream technology used to construct product design requirements models is primarily the aforementioned functional decomposition method. After obtaining the product design requirements model architecture after functional decomposition, some interrelationships and logical behavioral information are integrated to ultimately form a requirements model covering the product design. These software platforms and tools are designed for the verification of design requirements for complex products, rather than manufacturing feasibility. In particular, they do not include manufacturing requirements that focus on non-functional aspects such as manufacturing efficiency, manufacturing cost, and manufacturing quality, nor do they involve the control of manufacturing process requirements or the generation of attention reports.

[0064] In addition, the design of aircraft manufacturing process requirements has traditionally relied heavily on the professional skills and qualities of individual process technicians. The results of these individual process requirement designs are generally recorded in a discrete, multi-carrier, and different format, scattered in various physical, paper, and digital documents, making it difficult to transfer and trace the knowledge of aircraft manufacturing process requirements.

[0065] To address this, this application provides a solution: the model architecture is determined by matching the target project, and the entire business process revolves around the defined manufacturing dimensions to develop the technical requirements, forming a multi-process professional requirement model for aircraft manufacturing based on manufacturing concerns. This supports the design of multi-process professional requirements required for aircraft manufacturing engineering. Under the selected dimensions, the collaborative relationship interfaces of different process professionals are defined to realize the expression of the node network relationship of the model. Finally, the content design of non-functional manufacturing requirement indicators is carried out to build a non-functional requirement-oriented model, realize the digital management of manufacturing requirement process design, support the implementation of aircraft manufacturing engineering, reduce the dependence on process technicians, and effectively improve aircraft manufacturing efficiency.

[0066] See attached document Figure 2 Based on the hardware device described in the foregoing embodiments, embodiments of this application provide a method for constructing a multi-process requirement model for aircraft manufacturing, comprising the following steps:

[0067] Step 01: Match the target project to determine the target architecture dimension of the model.

[0068] In the specific implementation process, matching is performed based on the target project, selecting manufacturing strategies or priorities, and designing different types of demand model architectures. That is: matching is performed based on the target project to determine the target architecture dimensions of the model, including: matching manufacturing strategies or priorities based on the target project to determine the target architecture dimensions of the model.

[0069] The architecture can be integrated into various forms, such as discrete architecture, distributed architecture, and federated architecture, depending on the manufacturing strategy and focus requirements, forming an overall organizational structure. The appropriate architecture can be selected based on specific needs, such as: a demand model architecture for low-cost manufacturing (exemplary designation: R1), a demand architecture for rapid development (exemplary designation: R2), or a demand architecture for mass production (exemplary designation: R3), etc.

[0070] Specifically: as shown in the appendix Figure 3 This is a flowchart illustrating step 01 in one implementation. The input is "Aircraft Manufacturing Strategy and Focus," providing options 1 through n. In this example, these include "Option 1: Low-Cost Manufacturing R1," "Option 2: Rapid Development R2," and "Option 3: Mass Production R3." As shown in the example, when "Option 1: Low-Cost Manufacturing R1" is selected, a "Distributed Architecture" template is pushed to the user for further architecture design based on the pre-defined architecture matched to this manufacturing strategy / focus. When "Option 3: Mass Production R3" is selected, a "Federated Architecture" template is pushed to the user for further architecture design based on the pre-defined architecture matched to this manufacturing strategy / focus. In step 01, the architecture allows users to expand, copy, merge, and tailor the architecture according to the needs of the manufacturing strategy and focus. At this point, the associated matching architecture better aligns with the compositional logic of the aircraft manufacturing strategy and focus. For example, the distributed architecture pre-matched for low-cost manufacturing R1 reflects the characteristics of mutual constraints, mutual influence, and comprehensive balance among different cost nodes, reflecting the inherent characteristics of aircraft manufacturing technology costs.

[0071] Step 02: Conduct a technical breakdown of the requirements around the target architecture dimension.

[0072] In the specific implementation process, the manufacturing process requirements are decomposed and allocated. For a selected target architecture, the technical requirements are developed around the architecture, such as the main aircraft manufacturing process technology development (exemplary identifier: D1), the aircraft manufacturing subcontracting technology development (exemplary identifier: D2), and the aircraft manufacturing quality technology development (exemplary identifier: D3), etc.

[0073] Specifically, as shown in the attached document Figure 4This diagram illustrates the technology deployment in step 02 under a distributed architecture implementation. The required architecture at this point is a distributed architecture matched to "Low-Cost Manufacturing R1". First, the technology deployment form of the architecture nodes is determined. As shown in the diagram, when "Option 1: Aircraft Main Manufacturing Process Technology Deployment D1" is selected, the node "Labor Cost" expresses the labor cost requirements for low-cost aircraft manufacturing in the main manufacturing process of "parts manufacturing, component assembly, aircraft integration, and test flight". Similarly, when "Option 2: Aircraft Manufacturing Subcontracting Technology Deployment D2" is selected, the node "Labor Cost" expresses the labor cost requirements for low-cost aircraft manufacturing in the aircraft manufacturing subcontracting processes of "fuselage subcontracting, wing subcontracting, electromechanical subcontracting, avionics subcontracting, and power subcontracting". (See attached diagram) Figure 5 This is a schematic diagram illustrating the technical deployment of step 02 under a federated architecture implementation. The implementation methods of this example are similar to those in the appendix. Figure 4 Similar to the example shown, the only difference is the output of step 01, which illustrates the same usage of the implementation method.

[0074] It should be noted that when selecting technology deployment options, individual nodes within the demand architecture can choose either the same option or different options, as shown in the attached diagram. Figure 4 As shown, you can select "Option 2: Aircraft Manufacturing Subcontracting Technology Deployment D2" for both the "Labor Cost" and "Supporting Cost" nodes; select "Option 2: Aircraft Manufacturing Subcontracting Technology Deployment D2" for the "Labor Cost" node, and select "Option 1: Aircraft Main Manufacturing Process Technology Deployment D1" for the "Supporting Cost" node.

[0075] Step 03: Define the interface for the collaboration between the first process discipline and the second process discipline based on the target architecture dimension and the technology expansion dimension.

[0076] In the specific implementation process, for the selected dimensions already determined in the aforementioned steps, the interface for the collaborative relationship between the first and second process specialties is defined. The different collaborations and coordination among multiple aircraft manufacturing process specialties need to be expressed using a node network relationship. The node definition includes the input-output relationship at the node and the rich text editable field information attributes of the node itself. An example is given where the first process specialty is process specialty A and the second process specialty is process specialty B.

[0077] When the selected dimension is under the low-cost manufacturing demand model architecture (exemplarily labeled: R1) and unfolded according to the aircraft main manufacturing process technology (exemplarily labeled: D1), the output interface of process A is defined as "A-R1D1-P1", and the input interface of process B, which collaborates with it, is defined as "B-R1D1-P1", indicating that process A outputs its requirements to process B, and so on. When the selected dimension is under the mass production manufacturing demand model architecture (exemplarily labeled: R3) and unfolded according to the aircraft manufacturing subcontracting technology (exemplarily labeled: D2), the input interface of process A is defined as "A-R3D2-P2", and the output interface of process B, which collaborates with it, is defined as "B-R3D2-P2", indicating that process B outputs its requirements to process A, and so on, and vice versa. That is, based on the target architecture dimension and the technology unfolding dimension, the interface definition of the collaboration relationship between the first process and the second process is performed, including:

[0078] Based on the dimensions of the target architecture and the technology expansion, obtain the first identifier and the second identifier;

[0079] Based on the first identifier and the second identifier, a structured expression of the interface between the first process specialty and the second process specialty is used to define the interface for the collaborative relationship between the first process specialty and the second process specialty.

[0080] In the specific implementation process, as shown in the appendix Figure 6 This is a flowchart illustrating step 03 in one implementation. Values ​​are used to define the manufacturing process professional requirement node labels, such as "R1D1-Labor Cost" and "R1D1-Supporting Cost," representing the "Labor Cost under Low-Cost Manufacturing, Developed According to Aircraft Main Manufacturing Process Technology" node and the "Supporting Cost under Low-Cost Manufacturing, Developed According to Aircraft Main Manufacturing Process Technology," respectively. Each sub-node under the "R1D1-Labor Cost" node inherits the pre-configured name from step 02. A collaborative interface is defined for the sub-node "Part Manufacturing A" under "R1D1-Labor Cost," distinguishing the collaborative interaction interfaces under the same requirement node (label) from those under different requirement nodes (labels). (See attached...) Figure 6 As shown in the right-hand diagram: Interfaces "A-R1D1-P1" and "B-R1D1-P1" represent collaborative interactions under the same "labor cost," indicating a demand collaboration relationship between "labor cost of manufacturing part A" and "labor cost of assembling component B." Interfaces "A-R1D1-P2," "A-R1D1-P3," "A-R1D1-P4," "B-R1D1-P2," "B-R1D1-P3," and "B-R1D1-P4" represent collaborative interactions under different nodes (tags) "labor cost" and "supporting costs," indicating a key demand collaboration across categories.

[0081] The input and output types of the interface are not expressed by name, but are defined only as node attributes. In this process of defining multi-disciplinary interfaces in manufacturing, one-to-many and many-to-many interface relationships are allowed according to the needs of the target project. That is, before defining the collaborative interface between the first and second process disciplines based on the target architecture and technical expansion dimensions, the method also includes:

[0082] Based on the requirements of the target project, determine the interface relationships; these relationships include one-to-many and many-to-many relationships.

[0083] Based on the dimensions of target architecture and technology deployment, the interface definition for the collaborative relationship between the first process discipline and the second process discipline is as follows:

[0084] Based on the dimensions of target architecture and technology development, the interface for collaboration between the first process discipline and the second process discipline is defined using interface relationships.

[0085] Step 04: Based on the target architecture dimension and the technology expansion dimension, design the content of manufacturing non-functional requirement indicators and construct the target manufacturing process requirement model.

[0086] In the specific implementation process, a requirement content design function for a single aircraft manufacturing process specialty is provided to complete the design of the manufacturing non-functional requirement indicators for the dimensions already determined in steps 01 and 02. For example, when the selected dimension is under the low-cost manufacturing requirement model architecture (exemplarily identified as: R1) and unfolded according to the aircraft main manufacturing process technology (exemplarily identified as: D1), the description model content in the aforementioned A process specialty output node "A-R1D1-P1" is: "Under an object cost of 10,000 yuan, metal bonding process is adopted" output to the B process specialty node "B-R1D1-P1", whose description model content is: "Metal bonding process is adopted, and the bonding surface of a single part is not painted." (See attached) Figure 7 This is a flowchart illustrating step 04 in one implementation, using the interaction and collaboration of "R1D1 - Labor Cost" between the two demand nodes "Part Manufacturing A" and "Component Equipment B" as an example:

[0087] Since "Low-cost manufacturing R1" has already been selected in step 01 and "Aircraft main manufacturing process technology deployment" has already been selected in step 02, and the specific requirement under the time cost requirement is "Minimize aircraft main manufacturing time," then in "Part Manufacturing A" under "R1D1-Time Cost," the non-functional requirement is defined as "Metal bonding process should be adopted, index S1, to reduce component assembly time." In "Component Assembly B" under "R1D1-Time Cost," the non-functional requirement is defined as "Total component assembly time, index S3." The above two specific design requirements are collaboratively transmitted through the interfaces "A-R1D1-P1" and "B-R1D1-P1."

[0088] Similarly, in the coordination of labor cost requirements and supporting cost requirements, as shown in the example, a non-functional requirement is defined in "Part Manufacturing A" under "R1D1-Labor Cost": "Part manufacturing labor time should not exceed indicator S2, and the supplier is responsible for supporting." This requirement is output through interface "A-R1D1-P2" to interface "A-R1D1-P3" and connected to "Part Manufacturing A" under "R1D1-Supporting Cost". That is, the supporting cost is controlled by the indicator requirement of part manufacturing labor cost, and the supplier completes the supporting of parts, thereby reducing the part manufacturing labor cost of the aircraft's main manufacturer.

[0089] In this embodiment, the model architecture is determined by matching the target project. The entire business process revolves around the determined manufacturing dimension to develop the technical requirements, forming a multi-process professional requirement model for aircraft manufacturing based on manufacturing focus. This supports the design of multi-process professional requirements required for aircraft manufacturing engineering. Under the selected dimension, the collaborative relationship interface of different process professionals is defined to realize the expression of the node network relationship of the model. Finally, the content design of non-functional manufacturing requirement indicators is carried out to build a non-functional requirement-oriented model, realize the digital management of manufacturing requirement process design, support the implementation of aircraft manufacturing engineering, reduce the dependence on process technicians, and effectively improve aircraft manufacturing efficiency.

[0090] In one embodiment, after designing the content of manufacturing non-functional requirement indicators based on the target architecture dimension and the technology expansion dimension, and constructing the target manufacturing process requirement model, the method further includes step 05: manufacturing process requirement verification management; specifically:

[0091] Determine whether the non-functional manufacturing requirements in the target manufacturing process requirement model need to be verified. If the determination is that verification is required, verification is carried out according to the verification plan tasks. The verification plan tasks include calculation tasks, analysis tasks, simulation tasks, and prototype tasks.

[0092] In the specific implementation process, for the indicator requirements in the model content design results of step 04, a judgment is made as to whether the indicator needs to be verified. If indicator verification is required, the verification plan task method is selected, then the process requirement verification task begins. Finally, a judgment is made as to whether the indicator verification has been completed. (See attached document) Figure 8 This is a flowchart of step 05 under one implementation. Based on the result of the design definition of non-functional requirements in step 04, the entry "Metal bonding process should be adopted, indicator S1, to reduce component assembly time" is used to introduce "Indicator S1". A judgment is made on whether "Indicator S1" needs to be verified. If "No" is selected, proceed directly to the next step. If "Yes" is selected, proceed to the selection of verification method or technology.

[0093] Select at least one verification method or technique from the options "Computational Method (or Technique)," "Analytical Method (or Technique)," "Simulation Method (or Technique)," and "Prototype Method (or Technique)." After selection, proceed to the next step. Create the corresponding verification task based on the selection result. For example, if "Simulation Method (or Technique)" is selected, a "Simulation Verification Task" is created; if "Prototype Method (or Technique)" is selected, a "Prototype Verification Task" is created.

[0094] Check if all verification tasks are completed. If you select "Yes", proceed to the next step; if you select "No", return to the previous step 04, that is, return to step 04 to modify "Indicator S1" in the requirement model.

[0095] In one embodiment, after designing the content of manufacturing non-functional requirement indicators according to the target architecture dimension and the technology expansion dimension, and constructing the target manufacturing process requirement model, the method further includes: Step 06: Reusing the target manufacturing process requirement model.

[0096] In the specific implementation process, the results of the model construction, including the demand model results and the results of the related clue relationships, are published. The related clue relationships of the manufacturing process demand model are the actual work process connections from steps 01 to 05, and the network relationships of model nodes, specifically including the input-output association mapping datasets of various aircraft manufacturing process professional requirements. The reuse of the target manufacturing process demand model includes model publication, model reuse, work process reuse, digital clue analysis, and clue-based management. Specifically, the reuse of the target manufacturing process demand model includes:

[0097] Based on the target manufacturing process requirement model, obtain the requirement model results and related clue relationship results, and publish them;

[0098] Based on the target manufacturing process requirement model, model reuse, workflow reuse, digital clue analysis, and clue-based management are achieved through template generation and digital clue generation.

[0099] In the specific implementation process, as shown in the appendix Figure 9 The flowchart for step 06 is shown in one embodiment. After completing step 05, "Aircraft Manufacturing Process Requirements Model Result" and "Work Process Record of Steps 01 to 05" can be generated respectively, and their specific elements are shown in the figure.

[0100] The template generation includes an "Aircraft Manufacturing Process Requirements Model Template" and "Work Process Templates for Steps 01 to 05". For example, see attached... Figure 9 The dashed lines represent the sources of these templates for generating specific element information from existing "Aircraft Manufacturing Process Requirements Model Results" and "Work Process Records from Steps 01 to 05". Digital clue generation includes "Model Content Component Association Information," "Work Process Clues," and "Modeling Process Clues." An example is attached... Figure 9 Examples of digital clue information generated from these clues are provided, including: "the relationship between indicators S1, S2, and S3," "the workflow from manufacturing strategy / attention to model results," and "modeling process clues (e.g., architecture, nodes, indicators, and validation relationship information)." Similarly, examples are attached. Figure 9 The dotted lines represent the source of these digital clues from the specific elements in the existing "Aircraft Manufacturing Process Requirements Model Results" and "Work Process Records from Step 01 to Step 05".

[0101] Step 06 for reusing manufacturing process requirements models mainly includes model release, model reuse, workflow reuse, digital clue analysis, and clue-based management. (See appendix...) Figure 9 The text exemplifies the functions of these modules, such as "publishing the results of the aircraft manufacturing process requirements model", "publishing model R1D1 and reusing it as a new model RnDn", "reusing the first work process as the nth work process", "analysis of the emphasis of manufacturing strategy / focus", and "control of key tasks and completion status during the work process".

[0102] Using the manufacturing strategy and focus on "mass production" as the initial input, this paper describes several characteristics of the design results of the multi-process professional requirements model for aircraft manufacturing, as shown in the appendix. Figure 10 The diagram shows its overall features, with the features and the functional modules of the virtual device corresponding to the method of this application from which the features originate. Specifically:

[0103] Feature “Federal Architecture” selection: Architecture design module derived from the manufacturing process requirements model, i.e., the functional module of the virtual device that executes step 01.

[0104] Feature “Aircraft Manufacturing Subcontracting Technology Deployment” selection: from the Manufacturing Process Requirements Decomposition and Allocation module, which is also the functional module of the virtual device executing step 02.

[0105] The interface definition relationship between the nodes of each requirement model is characterized to realize the collaboration of multiple professional requirements: it comes from the interface definition module of manufacturing process requirements, that is, the functional module of the virtual device that executes step 03.

[0106] Feature “Non-functional requirements design for a single aircraft manufacturing process”: from the manufacturing process requirements content design module, that is, the functional module of the virtual device that executes step 04.

[0107] The feature "Verification task of content indicators" comes from the manufacturing process requirement verification management module, which is also the functional module of the virtual device that executes step 05.

[0108] The feature “different colored blocks represent different levels of control over manufacturing strategies / attention based on clues” comes from the manufacturing process requirement model reuse module, which is the functional module of the virtual device that executes step 06.

[0109] According to the appendix Figure 11 Further explanation of this application is attached. Figure 11 Here is a flowchart illustrating one implementation of the method described in this application:

[0110] First, a manufacturing process requirement model architecture is designed. Instead of relying on traditional requirement model construction methods, it uses non-functional expansion centered around manufacturing concerns to integrate multiple different requirement architectures, and provides a model construction method oriented towards non-functional requirements such as manufacturing efficiency, manufacturing cost, and manufacturing quality.

[0111] Secondly, the manufacturing process requirements are decomposed and allocated. Instead of relying on the functional decomposition and expansion methods of traditional product requirements, the non-functional expansion of manufacturing requirements is emphasized. The technology expansion can be flexibly carried out in the form of tree structure, correlation, center radiation, etc.

[0112] The manufacturing process requirement interface is defined to form a digital thread network of manufacturing process requirements. This not only satisfies the definition of collaborative relationships among multiple different process disciplines, but also supports the model customization and reuse in subsequent project applications. It solves the problem of "multi-source heterogeneity" of traditional manufacturing requirement carriers, especially the problems of unstructured and unclear associations.

[0113] Then, the manufacturing process requirements are designed. Based on the predefined semantic format, the content definition of the manufacturing process requirements is completed at the input and output nodes of the requirements model. Key manufacturing technology element indicators are identified and associated by keywords to support retrieval and rapid reuse in the digital clue model.

[0114] Finally, after the manufacturing process requirements verification management is passed, the manufacturing process requirements model can be reused; if the verification management fails, the process requirements design steps are returned to for redefinition. This achieves a digital closed-loop control effect for manufacturing process requirements design and verification. On the one hand, only manufacturing process requirements models that have passed verification can be released; on the other hand, detailed information on verification evidence, such as calculation processes, simulation processes, analysis processes, and sample reports, can be quickly found through reverse tracing of process indicators in the manufacturing requirements, avoiding the arbitrary release of immature process indicators.

[0115] This application provides a complete closed-loop coverage of requirements capture, decomposition, allocation, and verification for the manufacturing of complex aerospace products, including aircraft, ensuring the complete acceptance of process requirements design and the reasonable allocation of process indicators. It constructs a multi-process professional requirements model for aircraft manufacturing using an architecture that matches manufacturing strategies and a specific technology decomposition method. This solves the problem of traditional methods that decompose product design requirements around the product's own functions, relying on the Product Breakdown Structure (PBS) to construct product requirements models. It also addresses the issue of unusable requirements model design results caused by non-functional requirements such as manufacturing efficiency, cost, and quality in aircraft manufacturing processes. Based on predefined results from multiple manufacturing process specialties and mapping key technical elements around work processes and content descriptions, it realizes the transmission, inspection, and information extraction of inputs and outputs in manufacturing process requirements, enabling digital management of manufacturing requirements process design to support the implementation of aircraft manufacturing engineering.

[0116] See attached document Figure 12 Based on the same inventive concept as in the foregoing embodiments, this application also provides an apparatus for constructing a multi-process requirement model for aircraft manufacturing, comprising:

[0117] The architecture design module of the manufacturing process requirements model is used to match the target project and determine the target architecture dimensions of the model.

[0118] The manufacturing process requirements decomposition and allocation module is used to technically elaborate on requirements around the target architecture dimension.

[0119] The manufacturing process requirement interface definition module is used to define the collaborative relationship interface between the first process discipline and the second process discipline based on the target architecture dimension and the technology expansion dimension.

[0120] The Manufacturing Process Requirements Content Design Module is used to design the content of non-functional manufacturing requirements indicators based on the target architecture dimension and the technology expansion dimension, and to build the target manufacturing process requirements model.

[0121] In one embodiment, the apparatus further includes:

[0122] The Manufacturing Process Requirements Verification Management module is used for manufacturing process requirements verification management.

[0123] The manufacturing process requirement model reuse module is used to reuse the target manufacturing process requirement model.

[0124] Those skilled in the art should understand that the division of the various modules in the embodiments is merely a logical functional division. In actual applications, they can be fully or partially integrated into one or more actual carriers. These modules can be implemented entirely in software through processing unit calls, entirely in hardware, or a combination of software and hardware. It should be noted that each module in the aircraft manufacturing multi-process requirement model construction device in this embodiment corresponds one-to-one with each step in the aircraft manufacturing multi-process requirement model construction method in the aforementioned embodiments. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned aircraft manufacturing multi-process requirement model construction method, which will not be repeated here.

[0125] Based on the same inventive concept as in the foregoing embodiments, embodiments of this application also provide a computer-readable storage medium storing a computer program. When the computer program is loaded and executed by a processor, it implements the aircraft manufacturing multi-process requirement model construction method provided in the embodiments of this application.

[0126] Based on the same inventive concept as in the foregoing embodiments, embodiments of this application also provide an electronic device, including a processor and a memory, wherein,

[0127] Memory is used to store computer programs;

[0128] The processor is used to load and execute computer programs to enable electronic devices to perform the aircraft manufacturing multi-process requirement model construction method provided in the embodiments of this application.

[0129] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a device including one or any combination of the above-mentioned memories. The computer may be a variety of computing devices, including smart terminals and servers.

[0130] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0131] As an example, executable instructions may, but do not necessarily, correspond to files in the file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborative files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0132] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.

[0133] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0134] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0135] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory / random access memory, magnetic disk, optical disk) and includes several instructions to cause a multimedia terminal device (which may be a mobile phone, computer, television receiver, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0136] In summary, this application provides a method, apparatus, medium, and equipment for constructing a multi-process requirement model for aircraft manufacturing. The method includes: matching with target projects to determine the target architecture dimension of the model; technically expanding the requirements around the target architecture dimension; defining the collaborative relationship interface between a first process specialty and a second process specialty based on the target architecture dimension and the dimensions of the technical expansion; and designing the content of manufacturing non-functional requirement indicators based on the target architecture dimension and the dimensions of the technical expansion, thereby constructing a target manufacturing process requirement model. This application determines the model architecture by matching with target projects. The entire business process revolves around the determined manufacturing dimensions to technically expand the requirements, forming a multi-process professional requirement model for aircraft manufacturing based on manufacturing focus. This supports the design of multi-process professional requirements required for aircraft manufacturing engineering. Under the selected dimension, the collaborative relationship interface of different process specialties is defined, realizing the expression of the model's node network relationship. Finally, the content of manufacturing non-functional requirement indicators is designed, constructing a non-functional requirement-oriented model. This enables digital management of manufacturing requirement process design to support the implementation of aircraft manufacturing engineering, reduce reliance on process technicians, and effectively improve aircraft manufacturing efficiency.

[0137] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for constructing a multi-process requirement model for aircraft manufacturing, characterized in that, Includes the following steps: Match the target project to determine the target architecture dimension of the model; The process of matching based on the target project to determine the target architecture dimension of the model includes: Based on the target project, determine the target architectural dimensions of the model by matching the manufacturing strategy or focus. The technical aspects of the requirements are elaborated around the target architecture dimension. Based on the target architecture dimension and the technology expansion dimension, define the interface for the collaborative relationship between the first process discipline and the second process discipline; Based on the target architecture dimension and the technology expansion dimension, the content design of manufacturing non-functional requirement indicators is carried out to construct a target manufacturing process requirement model; wherein, the manufacturing non-functional requirement indicators are used for control in the corresponding technology expansion.

2. The method for constructing a multi-process requirement model for aircraft manufacturing according to claim 1, characterized in that, The definition of the collaborative relationship interface between the first process discipline and the second process discipline based on the target architecture dimension and the technology expansion dimension includes: Based on the target architecture dimension and the technology expansion dimension, a first identifier and a second identifier are obtained; Based on the first identifier and the second identifier, a structured representation of the interface between the first process specialty and the second process specialty is made to define the interface for the collaborative relationship between the first process specialty and the second process specialty.

3. The method for constructing a multi-process requirement model for aircraft manufacturing according to claim 1, characterized in that, Before defining the collaborative relationship interface between the first process discipline and the second process discipline based on the target architecture dimension and the technology expansion dimension, the method further includes: Based on the requirements of the target project, determine the interface relationships; wherein, the interface relationships include one-to-many relationships and many-to-many relationships; The definition of the collaborative relationship interface between the first process discipline and the second process discipline based on the target architecture dimension and the technology expansion dimension includes: Based on the target architecture dimension and the technology expansion dimension, the interface definition for the collaboration relationship between the first process discipline and the second process discipline is based on the interface relationship.

4. The method for constructing a multi-process requirement model for aircraft manufacturing according to claim 1, characterized in that, After designing the content of manufacturing non-functional requirement indicators based on the target architecture dimension and the technology expansion dimension, and constructing the target manufacturing process requirement model, the method further includes: The non-functional manufacturing requirements in the target manufacturing process requirement model are assessed to determine whether verification is required. If verification is required, verification is performed according to the verification plan tasks. The verification plan tasks include calculation tasks, analysis tasks, simulation tasks, and prototype tasks.

5. The method for constructing a multi-process requirement model for aircraft manufacturing according to claim 1, characterized in that, After designing the content of manufacturing non-functional requirement indicators based on the target architecture dimension and the technology expansion dimension, and constructing the target manufacturing process requirement model, the method further includes: The model can be reused based on the target manufacturing process requirements.

6. The method for constructing a multi-process requirement model for aircraft manufacturing according to claim 5, characterized in that, The reuse based on the target manufacturing process requirement model includes: Based on the target manufacturing process requirement model, obtain the requirement model results and related clue relationship results, and publish them. Based on the target manufacturing process requirement model, model reuse, workflow reuse, digital clue analysis, and clue-based management are performed through template generation and digital clue generation.

7. A device for constructing a multi-process requirement model for aircraft manufacturing, characterized in that, include: The architecture design module of the manufacturing process requirements model is used to match the target project and determine the target architecture dimensions of the model. The process of matching based on the target project to determine the target architecture dimension of the model includes: Based on the target project, determine the target architectural dimensions of the model by matching the manufacturing strategy or focus. The manufacturing process requirements decomposition and allocation module is used to technically expand the requirements around the target architecture dimension. The manufacturing process requirement interface definition module is used to define the collaborative relationship interface between the first process specialty and the second process specialty based on the target architecture dimension and the technology expansion dimension. The manufacturing process requirements content design module is used to design the content of manufacturing non-functional requirements indicators based on the target architecture dimension and the technology expansion dimension, and to construct a target manufacturing process requirements model; wherein, the manufacturing non-functional requirements indicators are used for control in the corresponding technology expansion.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is loaded and executed by the processor, it implements the method for constructing a multi-process requirement model for aircraft manufacturing as described in any one of claims 1-6.

9. An electronic device, characterized in that, Including processor and memory, among which, The memory is used to store computer programs; The processor is used to load and execute the computer program so that the electronic device performs the aircraft manufacturing multi-process requirement model construction method as described in any one of claims 1-6.

Images