A method for constructing a civil aircraft digital manufacturing platform architecture supporting elastic expansion and a platform

Abstract

This invention relates to a method and platform for constructing a digital manufacturing platform architecture for civil aircraft that supports flexible scalability. The method includes the following steps: constructing a two-layer, separate platform architecture, including a domain-side application unit and a platform support layer; and establishing a domain component collaboration mechanism based on event flow-driven and workflow-based collaboration within the domain-side application unit. This invention effectively solves the technical problems of existing civil aircraft manufacturing information systems when dealing with multi-model mixed-line production, capacity fluctuations, and cross-departmental collaboration, such as poor system architecture scalability, high module coupling, low resource utilization, poor functional component reusability, weak intelligent decision-making capabilities, and low deployment efficiency. It also addresses the problems of existing civil aircraft manufacturing information platforms being unable to adapt to manufacturing environments with multiple models operating in parallel and frequent process changes, and weak data isolation and cross-system linkage. This invention possesses highly efficient flexible scalability, good decoupling, and real-time collaborative performance.

Description

Technical Field

[0001] This invention relates to the field of digital manufacturing technology for civil aircraft, and specifically to a method and platform for constructing a digital manufacturing platform architecture for civil aircraft that supports flexible expansion. Background Technology

[0002] In the field of civil aircraft manufacturing, existing information systems mainly include Manufacturing Execution System (MES), Advanced Planning and Scheduling System (APS), Enterprise Resource Planning System (ERP), and Warehouse Management System (WMS). These systems generally adopt a closed architecture in practical applications, with high coupling between functional modules, severe data isolation, and difficulty in achieving cross-system linkage and information sharing.

[0003] Traditional MES and related systems, due to their closed architecture, suffer from independent functions, fragmented data, and information silos between different departments and workshops, resulting in low overall efficiency and difficulty in meeting the needs of unified management and collaborative optimization. Secondly, these systems often rely heavily on customized development to meet diverse business requirements, such as integrating ERP or WMS functions into the MES system, leading to excessively high development, deployment, and upgrade costs, and failing to adapt to the needs of rapid enterprise iteration and transformation.

[0004] Regarding service-unit architecture, existing technologies assemble functional components through layered design, but their configuration relies on static templates and lacks runtime dynamic adjustment capabilities. When faced with sudden high-load tasks such as aircraft assembly, the system cannot quickly expand resources according to actual needs, leading to task backlog and response delays. Furthermore, existing solutions do not fully consider the unique constraints of civil aircraft manufacturing, such as frequently changing process routes in single-piece, small-batch production models, stringent airworthiness traceability requirements, and complex scheduling needs for massive quantities of parts. These existing solutions are insufficiently adaptable to the aerospace manufacturing environment with heterogeneous equipment protocols and significantly different business logics, making it difficult to achieve real-time collaboration between the equipment layer and the process layer.

[0005] Current industrial internet platforms focus more on cross-industry data fusion and system integration, but in practical applications, they still face heterogeneous adaptation challenges caused by differences in equipment protocols and business logic. These platforms suffer from insufficient data reusability in complex manufacturing scenarios and lack dynamic scheduling capabilities at the equipment and process layers. Particularly in critical scenarios such as logistics management triggered by changes in work order status, existing systems lack efficient event-driven mechanisms, leading to frequent disconnects between material delivery and production progress.

[0006] Furthermore, traditional architectures lag behind in responding to dynamic adjustments in assembly processes, and there is a time difference between the execution of process instructions and resource coordination, which cannot meet the stringent requirements of civil aircraft manufacturing for real-time performance, collaboration, and flexibility. If a tight coupling design is adopted between the platform support layer and the domain side, it will lead to difficulties in independently deploying components, and the technical infrastructure services will struggle to support the rapid iteration of business functions.

[0007] In summary, considering the characteristics of civil aircraft manufacturing, existing meta-modeling and visualization platforms are still unable to quickly capture and respond to process changes when dealing with frequent adjustments in assembly procedures and changes in key links. This results in delayed execution of process instructions and untimely resource coordination. Under the conditions of massive parts and complex processes involved in large aircraft manufacturing, existing systems have significant shortcomings in terms of flexible processing capabilities, dynamic scheduling mechanisms, and component reusability, making it difficult to meet actual needs.

[0008] With the comprehensive digitalization of civil aircraft manufacturing, production management and control platforms have become a crucial foundation for process orchestration and resource collaboration. However, existing systems suffer from lengthy data acquisition and distribution links, limited module expansion, and susceptibility to response delays under load fluctuations. They are ill-suited for single-piece, small-batch production and frequently changing process scenarios, while also needing to balance airworthiness traceability and high-level data security. Although domestic and international efforts have driven the evolution from monolithic to service-unit architectures, common implementations still suffer from low access efficiency, fragmented user experience, and long cross-domain collaboration links in highly coupled aerospace manufacturing processes and heterogeneous terminal environments, making it difficult to support real-time linkage and flexible orchestration across multiple roles and scenarios.

[0009] Therefore, existing solutions generally have shortcomings in terms of elastic scaling, event-driven dynamic scheduling, and cross-scenario consistency, making it difficult to meet the dual requirements of stability and agility in the digital manufacturing of civil aircraft. To address these issues, existing technologies urgently need improvement. Summary of the Invention

[0010] In view of the above-mentioned deficiencies of the prior art, the first aspect of the present invention provides a method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion, comprising the following steps:

[0011] Construct a two-tiered, separate platform architecture, including domain-side application units and a platform support layer;

[0012] The platform support layer is configured to provide technical infrastructure services that support independent deployment and elastic scaling of domain components through containerized deployment, service registration and discovery, master data management, process configuration, workflow engine and event flow bus.

[0013] The domain-side application unit is built on top of the platform support layer; wherein, the domain-side application unit includes multiple domain components for realizing process design, production operation, quality operation, logistics operation and equipment operation functions respectively;

[0014] Within the domain-side application unit, a domain component collaboration mechanism based on event flow-driven and workflow collaboration is established. This mechanism utilizes an event flow bus to enable cross-domain component event publishing and subscription, and a workflow engine to orchestrate and execute business processes. A production operations domain component and a logistics management domain component are established, and a subscription relationship is established between the logistics management domain component and the work order status events published by the production operations domain component, in order to trigger logistics management actions based on events.

[0015] Each domain component on the domain side achieves decoupling from the platform support layer and collaboration between components by calling the standardized service interfaces provided by the platform support layer.

[0016] In the construction method of the civil aircraft digital manufacturing platform architecture that supports elastic scaling as described above, the following steps may be optionally included:

[0017] Step S1: Construct the domain-side application unit and platform support layer;

[0018] Specifically, the domain-side application unit is configured to carry core manufacturing domain capabilities, including at least process planning, production operation, quality operation, logistics management, and equipment maintenance; the platform support layer is configured to provide technical infrastructure services, including at least component encapsulation, service registration and discovery, master data management, process configuration, workflow engine, and event flow bus; the workflow engine is used to realize the dynamic orchestration and execution of business processes, support the configuration and process governance of multi-level tasks, and manage workflow instances in full-fledged parallel production scenarios; the event flow bus is used to realize the event publishing, subscription, and distribution of cross-domain components, support asynchronous communication and state linkage, and event routing and load balancing in full-fledged parallel production scenarios; and the decoupling of the domain-side and the platform support layer is achieved through standardized service interfaces to ensure elastic scalability in full-fledged parallel production scenarios;

[0019] Step S2: Construct the process planning domain component;

[0020] Specifically, the process planning domain component service unit is divided into a manufacturing digital prototype sub-component and a process intelligent generation sub-component; the manufacturing digital prototype sub-component is configured to decompose the product's three-dimensional structure into process unit structures based on a three-dimensional model analysis engine; and the process intelligent generation sub-component is configured to generate corresponding process document content based on the process model.

[0021] Step S3: Build production operations domain components;

[0022] Specifically, the production operation domain component service unit is divided into sub-components for planning management, intelligent scheduling, task scheduling, and work order control, and logical connections are established between these sub-components to achieve distributed scheduling and control. The planning management sub-component formulates a multi-level production planning system based on production orders and resource constraints. The intelligent scheduling sub-component dynamically generates production scheduling schemes by comprehensively considering multi-dimensional constraints, including at least equipment capacity, personnel allocation, and process routes. The task scheduling sub-component decomposes the scheduling scheme into specific work tasks and distributes them to the corresponding production workstations. The work order control sub-component tracks and manages the execution process of production instructions throughout the entire process to ensure the controllability and traceability of the production process.

[0023] Step S4: Construct the quality operation domain component;

[0024] Specifically, the quality operation domain component service unit is divided into quality inspection, quality collaboration, and personnel qualification management sub-components to establish loosely coupled collaborative control functions. The quality inspection sub-component has a built-in ASR (Acceptance Sampling Rule) feature library to automatically match sampling schemes according to part categories, and integrates NDT (Non-Destructive Testing) and PCLR (Process Control Laboratory) test sheet templates to standardize testing content and judgment criteria. At the same time, it is configured to support multi-level approval, version management, and report export functions for quality assurance records. The quality collaboration sub-component is established based on event-triggered cross-departmental collaborative workflows. When a quality anomaly is reported in the production or inspection process, the system initiates a processing flow that includes problem definition, cause analysis, corrective action formulation, and effect verification. The personnel qualification management sub-component is used to maintain personnel skill files and business authorization matrices, providing permission verification and compliance assurance for quality-related business operations.

[0025] Step S5: Construct the logistics management domain component;

[0026] Specifically, core logistics functions, including at least material distribution and line-side replenishment, are integrated into a unified logistics management domain component. This component is configured to trigger corresponding logistics management actions by subscribing to work order status change events published by the production operations domain component. Upon receiving a work order initiation event, the logistics management domain component automatically parses the corresponding work order's material requirements list and generates a material preparation task. Real-time data interaction with the inventory management system ensures material distribution. The logistics management domain component monitors line-side inventory based on a safety stock threshold and automatically triggers replenishment reminders and delivery processes when inventory levels fall below a preset threshold.

[0027] Step S6: Build the device operation and maintenance domain component;

[0028] Specifically, the equipment operation and maintenance domain component service unit is divided into sub-components for equipment file management, equipment repair, equipment maintenance, equipment operation, and equipment use. These sub-modules are configured to share a unified equipment master data model to support integrated management throughout the entire lifecycle. The equipment file management sub-component is used to establish and maintain equipment master data files containing basic equipment information, technical parameters, and installation location. The equipment repair management sub-component supports electronic process management from fault reporting to repair completion, including fault information collection, automatic dispatch of repair tasks, repair process tracking, and repair result recording. The equipment maintenance management sub-component automatically generates preventative maintenance plans based on key indicators such as equipment operating time and usage frequency, and tracks their execution.

[0029] Step S7: Construct the technical infrastructure services for the platform support layer;

[0030] Specifically, containerized deployment, service registration and discovery, unified master data management and process configuration, workflow engine and event flow bus enable independent deployment, dynamic scaling and scaling, and process adjustment capabilities for each domain component in the domain-side application unit. The workflow engine provides dynamic orchestration and execution capabilities for business processes, supporting multi-level task configuration, process governance, and workflow instance management in full-fledged parallel scenarios. The event flow bus provides cross-domain component event publishing, subscription, and distribution capabilities, supporting asynchronous communication, state linkage, and event routing and load balancing in full-fledged parallel production scenarios. Containerized deployment and service registration and discovery enable load-based elastic scaling, supporting dynamic resource scheduling and automatic instance scaling in full-fledged parallel production scenarios.

[0031] In the construction method of the civil aircraft digital manufacturing platform architecture that supports elastic expansion as described above, optionally, in step S1, the domain-side application unit and the platform support layer interact with each other through two communication protocols: synchronous call and event channel.

[0032] For synchronous business scenarios that require real-time response, the RESTful API direct call method is adopted; for asynchronous business scenarios that allow delayed processing, the message queue publish and subscribe method is adopted.

[0033] In the construction method of the civil aircraft digital manufacturing platform architecture that supports flexible expansion as described above, optionally, in step S2, the manufacturing digital prototype sub-component constructs the three-dimensional model analysis engine based on MBD technology to automatically identify the assembly features, constraint relationships and process requirements in the product three-dimensional geometric model transmitted from the design system, and automatically decomposes the product structure into a process unit tree structure based on preset manufacturing process rules; the three-dimensional model analysis engine has a built-in allocation integrity check algorithm, which automatically triggers an integrity alarm and generates a missing parts list when it detects that there are parts in the product structure that are not covered by any process unit;

[0034] The intelligent process generation sub-component has a built-in process content generation engine assisted by a large language model. It automatically generates standardized process document content based on the input part features and process requirements by using deep learning to understand the structured features and process logic of historical process documents.

[0035] In the construction method of the civil aircraft digital manufacturing platform architecture that supports elastic expansion as described above, optionally, in step S3, the intelligent scheduling sub-component has a built-in constraint satisfaction algorithm, which simultaneously considers multiple conflicting optimization objectives, including at least production efficiency, resource utilization and delivery time, under a multi-objective optimization framework, and generates a scheduling scheme close to the global optimum through a heuristic search strategy; and the task scheduling sub-component dynamically reallocates production tasks in response to equipment failure or personnel change events.

[0036] In the construction method of the civil aircraft digital manufacturing platform architecture that supports flexible expansion as described above, optionally, in step S4, the ASR automatic matching algorithm executed by the quality inspection subcomponent performs similarity calculation based on the geometric features, material properties and quality requirements of the parts in a multi-dimensional feature vector to select an inspection scheme from the sampling rule base; the event triggering mechanism of the quality collaboration subcomponent supports multi-level quality problem classification and processing, and automatically determines the processing priority and responsible department according to the severity and scope of the quality problem.

[0037] In the aforementioned method for constructing a civil aircraft digital manufacturing platform architecture that supports elastic scaling, optionally, in step S7, the containerized deployment relies on the workload abstraction and declarative release objects of the container orchestration platform to realize the declarative deployment, upgrade, and health management of domain components, and supports rolling updates, version rollback, and health detection; the service registration and discovery supports the elastic scaling of instances, dynamically adding or removing instances based on service pressure and incorporating or removing them from traffic distribution and coordinating with load balancing strategies; the unified management of master data ensures data consistency through version control and broadcast mechanisms, and automatically sends notifications to relevant domain components to refresh local caches when master data changes; the process configuration supports drag-and-drop definition of business processes and approval rules through a visual process modeler, and converts them into executable process configurations for the process engine to run.

[0038] To achieve the above objectives, a second aspect of the present invention provides a civil aircraft digital manufacturing platform that supports flexible expansion, wherein the platform is constructed using a construction method for a civil aircraft digital manufacturing platform architecture that supports flexible expansion as described in any of the embodiments of the first aspect above, and the platform adopts a two-layer architecture in which the domain-side application unit and the platform support layer are separated.

[0039] The platform support layer includes:

[0040] The containerized deployment module is used to encapsulate, deploy, and orchestrate the components of domain-side application units.

[0041] The service registration and discovery module is used to maintain service registration information of domain components and realize dynamic addressing of service instances;

[0042] The master data management module is used to maintain a unified data model for equipment, materials, personnel, and processes, and to perform data version control and change synchronization.

[0043] The process configuration module is used to visually model business processes, and the process engine executes the process model.

[0044] The workflow engine module is used to dynamically orchestrate and execute business processes, supporting multi-level task configuration, process governance, and workflow instance management in full-scale parallel scenarios.

[0045] The event flow bus module is used to implement event publishing, subscription and distribution for cross-domain components, and supports event routing and load balancing in asynchronous communication, state linkage and full-fledged parallel production scenarios;

[0046] The domain-side application unit is built on top of the platform support layer and includes multiple domain components implemented in a service unit manner. Each domain component includes at least:

[0047] The process planning domain component is used to complete process planning and document output, including sub-components for manufacturing digital prototypes and generating process documents;

[0048] The production operations domain component is used for plan decomposition, scheduling and issuance, as well as work order execution status tracking, and includes sub-components for plan management, intelligent scheduling, task scheduling and work order control;

[0049] The Quality Operations Domain component is used for quality inspection, anomaly closure, and personnel qualification management, and includes sub-components for quality inspection, quality collaboration, and personnel qualification management.

[0050] Logistics management domain components are used for material distribution and lineside replenishment;

[0051] Equipment operation and maintenance domain components are used for equipment file, repair, maintenance, operation and usage management;

[0052] The logistics management domain component establishes an event subscription relationship with the production operation domain component, and triggers material preparation and delivery operations based on the work order status events published by the production operation domain component.

[0053] Each domain component of the domain-side application unit calls the services provided by the platform support layer through standardized service interfaces to achieve decoupling and collaboration between the domain-side application unit and the platform support layer, as well as between domain components.

[0054] To achieve the above objectives, a third aspect of the present invention provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when running the program, implements a method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion as described in any of the preceding first aspects.

[0055] To achieve the above objectives, a fourth aspect of the present invention provides a computer-readable storage medium storing computer-executable instructions or a computer program, which, when executed by a processor, implements a method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion as described in any of the first aspects above.

[0056] This invention provides a method and platform for constructing a civil aircraft digital manufacturing platform architecture that supports elastic scaling. Specifically designed for the business characteristics of civil aircraft manufacturing, the platform is divided into a basic technology component library and a business application component library. The former encapsulates common capabilities such as user authentication, master data management, process configuration, and container orchestration, while the latter encapsulates specialized functions such as process planning, production operation, quality control, logistics management, and equipment maintenance. The two are decoupled through a unified interface and service registration mechanism, achieving high component reusability, independent evolution, and dynamic expansion. This architecture, through containerized deployment, service discovery, elastic scaling, and configuration-based management mechanisms, ensures efficient response and stable operation in scenarios involving parallel production of multiple models and complex process changes.

[0057] In summary, this invention, by constructing a two-layer, separate architecture and an event-driven collaborative mechanism, enables domain components to be deployed independently and expanded elastically. This effectively solves the technical problems of existing civil aircraft manufacturing information systems when dealing with multi-model mixed-line production, capacity fluctuations, and cross-departmental collaboration, such as poor system architecture scalability, high module coupling, low resource utilization, poor functional component reusability, weak intelligent decision-making capabilities, and low deployment efficiency. It also addresses the problems of existing civil aircraft manufacturing information platforms being unable to adapt to manufacturing environments with multiple models operating in parallel and frequent process changes, and weak data isolation and cross-system linkage. The invention possesses highly efficient elastic expansion capabilities, good decoupling, and real-time collaborative performance.

[0058] The following will further explain the concept, specific structure, and technical effects of the present invention in conjunction with the accompanying drawings, so as to fully understand the purpose, features, and effects of the present invention. Attached Figure Description

[0059] Figure 1 This is a flowchart illustrating an embodiment of a method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion, provided by the present invention.

[0060] Figure 2 This is a schematic diagram of the architecture of an embodiment of the civil aircraft digital manufacturing platform supporting flexible expansion of the present invention, which constructs an operation and control system covering the entire civil aircraft manufacturing process in the domain-side application unit.

[0061] Figure 3 This is a schematic diagram of an embodiment of the civil aircraft digital manufacturing platform supporting flexible expansion of the present invention, which adopts a layered architecture at the software level.

[0062] Figure 4 This is a schematic diagram of the architecture of an embodiment of the civil aircraft digital manufacturing platform supporting flexible expansion of the present invention, which adopts a multi-layered technical system at the technical implementation level.

[0063] Figure 5 This is a schematic diagram of the architecture of the independent domain-side component of the civil aircraft digital manufacturing platform supported by the present invention, which is designed to further realize modularity and flexible expansion. Detailed Implementation

[0064] To make the technical means, inventive features, objectives, and effects of the invention readily understandable, the invention is further illustrated below with reference to specific figures. However, the invention is not limited to the embodiments described below.

[0065] It should be noted that the structures, proportions, sizes, etc., illustrated in the accompanying drawings of this specification are only used to complement the content disclosed in the specification for those skilled in the art to understand and read, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0066] Terms such as “comprising” and “including” indicate that, in addition to the components that are directly and explicitly stated in the specification and claims, the technical solution of the present invention does not exclude the presence of other components that are not directly or explicitly stated.

[0067] Furthermore, the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0068] In the digital manufacturing platform for civil aircraft, the closed architecture and highly coupled functional modules result in data silos across different systems, hindering effective data sharing. This architecture lacks elastic scalability, making it difficult to dynamically adjust resources when facing single-piece, small-batch production demands. Furthermore, the absence of event-driven collaboration mechanisms prevents domain components from responding to state changes in real time, impacting the overall system's data synchronization timeliness, business function scalability, and system responsiveness. Specifically, functional coupling increases customized development costs, data silos impede unified management of core data such as process, equipment, and logistics, and the lack of elastic scalability prevents the system from automatically adjusting resource allocation in unexpected task scenarios.

[0069] For example, in the assembly process of large civil aircraft, when the process design department adjusts the assembly procedure of a key component, the production operations system updates the work order status. However, due to data isolation in the existing system, the logistics system cannot obtain this change information in a timely manner, resulting in the failure to update the material delivery plan synchronously. In this scenario, the problems of functional coupling and data silos directly manifest as a disconnect between logistics management actions and production rhythm, leading to reduced resource scheduling efficiency. Furthermore, due to the lack of a dynamic event-driven mechanism, the logistics management domain components cannot trigger delivery actions in real time based on changes in work order status, causing assembly lines to wait for materials, which in turn affects the continuity of the overall production cycle.

[0070] If these issues are not addressed, it will lead to increased resource idleness during the manufacturing process, disrupted production rhythms, and an inability to meet the stringent requirements for data real-time performance and consistency in airworthiness traceability. In the complex and ever-changing civil aircraft manufacturing environment, the system struggles to adapt to frequent process adjustments, resulting in decreased overall operational efficiency. Consequently, the demand for customized development continues to rise, system upgrade and maintenance costs increase significantly, hindering the advancement of digital transformation and failing to meet the basic requirements for system collaboration and flexibility across multiple roles and scenarios.

[0071] In response, this application proposes a method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible scaling, which may include the following steps:

[0072] Construct a two-tiered, separate platform architecture, including domain-side application units and a platform support layer.

[0073] The platform support layer is configured to provide technical infrastructure services that support independent deployment and elastic scaling of domain components through containerized deployment, service registration and discovery, master data management, and process configuration.

[0074] Build domain-side application units on top of the platform support layer.

[0075] In this step, the domain side can contain multiple service unitized components for implementing domain components for process planning, production operation, quality operation, logistics management, and equipment operation and maintenance functions.

[0076] Establish an event-driven domain component collaboration mechanism within the domain.

[0077] In this step, a production operations domain component and a logistics management domain component are established, and a subscription relationship is established between the logistics management domain component and the work order status events published by the production operations domain component, so as to trigger logistics management actions based on the events; each domain component on the domain side achieves decoupling from the platform support layer and collaboration between components by calling the standardized service interface provided by the platform support layer.

[0078] This technical solution decouples business logic from technical infrastructure through a two-layer separation architecture, enabling domain components to be deployed independently and scale elastically. Simultaneously, the event-driven collaboration mechanism eliminates response latency caused by synchronous calls in traditional systems, and the standardized service interface calling method avoids direct dependencies between components. Therefore, this architecture effectively solves the problems of high functional coupling and data silos caused by the closed system architecture in the civil aircraft digital manufacturing platform. It achieves dynamic scaling capabilities for domain components and ensures real-time collaboration across component business processes, thereby meeting the elastic scaling and dynamic scheduling requirements of single-piece, small-batch production in civil aircraft manufacturing scenarios.

[0079] Furthermore, the specific implementation details of this platform architecture and its various domain components are as follows:

[0080] In such Figure 1 In the illustrated embodiment, the method for constructing the digital manufacturing platform architecture for civil aircraft may specifically include the following steps:

[0081] Step S1: Construct the domain side and platform support layer.

[0082] In step S1, the domain-side application unit is configured to carry core manufacturing business functions such as process planning, production operation, quality management, logistics management, and equipment maintenance. The platform support layer is configured to provide technical infrastructure services such as component encapsulation, service registration and discovery, master data management, process configuration, workflow engine, and event flow bus. The workflow engine is used to dynamically orchestrate and execute business processes, supporting multi-level task configuration and process governance, as well as workflow instance management in full-fledged parallel scenarios. The event flow bus is used to implement event publishing, subscription, and distribution across domain components, supporting asynchronous communication and state linkage, as well as event routing and load balancing in full-fledged parallel production scenarios, and decoupling the domain side from the platform support layer through standardized service interfaces.

[0083] In an optional embodiment, the domain-side application unit and the platform support layer can interact with each other through two communication protocols: synchronous calls and event channels. Specifically, for synchronous business scenarios requiring real-time responses, a direct RESTful API call method is used; for asynchronous business scenarios allowing for delayed processing, a publish-subscribe message queue method is used.

[0084] RESTful APIs, which are representational state transfer interfaces based on the HTTP protocol, can be implemented using JSON or XML data formats. Their purpose is to provide a real-time, synchronous data exchange mechanism to ensure immediate response to critical business operations. Specifically, the solution in this application dynamically selects the communication protocol based on the real-time characteristics of the business scenario, enabling the platform to accurately adapt to differentiated needs. For synchronous business scenarios requiring real-time response, a direct call to the RESTful API is used, based on the HTTP request-response model to achieve instant data exchange, ensuring that critical operations such as production and operation are completed within milliseconds. For asynchronous business scenarios that allow for delayed processing, a publish-subscribe approach using message queues is adopted, achieving decoupled communication through an event-driven mechanism and smoothly handling high-concurrency requests using a message buffer pool. This dual-mode communication mechanism allows domain-side application units and the platform support layer to meet real-time requirements while avoiding resource congestion during data interaction, effectively resolving the contradiction between response speed and processing capacity that a single communication mode cannot simultaneously address.

[0085] Through the above solution, this application can avoid response delays in synchronous business scenarios and resource blockages in asynchronous business scenarios, significantly improve the resource scheduling efficiency of the civil aircraft digital manufacturing platform in dealing with flexible production, meet the stringent requirements of airworthiness traceability for real-time data, and support the elastic expansion needs of delayed operations such as logistics replenishment.

[0086] Step S2: Construct the process planning domain component;

[0087] In step S2, the process planning domain component service unitizes the manufacturing digital prototype sub-component and the process intelligence generation sub-component. Service unitization refers to breaking down business functions into independent, separately deployable, and scalable service units, which can be implemented using distributed service frameworks such as Spring Cloud or Dubbo, aiming to improve the system's flexibility and maintainability.

[0088] The configuration and manufacturing digital prototype sub-component uses a 3D model analysis engine to decompose the product's 3D structure into process unit structures. The configuration and intelligent process generation sub-component generates corresponding process documentation based on the process model. The 3D model analysis engine is a software module used to automatically identify process-related information in the product's 3D geometric model. It can perform model analysis based on the CAD system's native API or common 3D data exchange standards such as STEP, aiming to reduce manual intervention and ensure the accuracy of process decomposition.

[0089] In an optional embodiment, the digital prototype manufacturing sub-component constructs a 3D model parsing engine based on MBD (Model-Based Definition) technology to automatically identify assembly features, constraints, and process requirements in the 3D geometric model of the product imported from the design system. Based on preset manufacturing process rules, it automatically decomposes the product structure into a tree-like structure of process units. Simultaneously, the 3D model parsing engine incorporates an allocation integrity check algorithm. When a part not covered by any process unit is detected in the product structure, an integrity alarm is automatically triggered, and a list of missing parts is generated. The intelligent process generation sub-component incorporates a large language model-assisted process content generation engine. Through deep learning of the structured features and process logic of historical process documents, it automatically generates standardized process document content based on the input part features and process requirements. This achieves intelligent assistance in the process design process, forming a closed-loop process from model parsing to document generation, ensuring the systematic nature and maintainability of process data.

[0090] The allocation integrity check algorithm can be understood as a set of logical rules for verifying the integrity of process unit coverage. It can be implemented using graph traversal algorithms or set coverage algorithms, aiming to monitor the part coverage status in real time and prevent production interruption risks caused by omissions in process design. The large language model-assisted process content generation engine is specifically an intelligent system that uses natural language processing technology to generate process documents. It can be implemented using a neural network model with a Transformer architecture, aiming to understand the implicit rules and patterns in historical data and avoid the rigidity problem of static rule generation.

[0091] Through the above-described scheme, this application introduces a three-dimensional model analysis and constraint mechanism into the process planning process, realizing the evolution from traditional two-dimensional process definition to a process generation method based on three-dimensional digital models. This method ensures the completeness of process unit decomposition and the adaptability of process document generation, effectively avoiding the risk of production interruption due to omissions in process design, significantly improving the response speed and document quality of process design, and meeting the manufacturing needs of multi-process collaboration and complex assembly scenarios.

[0092] Step S3: Build production operations domain components.

[0093] In step S3, the production operations domain component service unit is modularized into sub-components for planning management, intelligent scheduling, task scheduling, and work order control, and logical connections are established between these sub-components to achieve distributed scheduling and control. The planning management sub-component formulates a multi-level production planning system based on production orders and resource constraints. The intelligent scheduling sub-component dynamically generates production scheduling schemes by comprehensively considering multi-dimensional constraints such as equipment capacity, personnel allocation, and process routes. The task scheduling sub-component decomposes the scheduling scheme into specific work tasks and distributes them to the corresponding production workstations. The work order control sub-component tracks and manages the execution process of production instructions throughout the entire process to ensure the controllability and traceability of the production process.

[0094] In an optional embodiment, the intelligent scheduling subcomponent incorporates a constraint satisfaction algorithm that simultaneously considers multiple conflicting optimization objectives such as production efficiency, resource utilization, and delivery time within a multi-objective optimization framework. It then generates a near-globally optimal scheduling solution through a heuristic search strategy. Furthermore, the task scheduling subcomponent dynamically reallocates production tasks in response to equipment failures or personnel changes.

[0095] In practical applications, constraint satisfaction algorithms refer to computational methods for handling complex constraints. They can be implemented using generalized methods such as backtracking search, constraint propagation, or local search to ensure that scheduling solutions meet all hard constraints, aiming to avoid infeasibility due to insufficient constraint handling. Multi-objective optimization frameworks can be understood as mathematical structures capable of handling multiple conflicting optimization objectives simultaneously. They can be implemented using weighted summation, Pareto optimal solution sets, or goal programming, aiming to dynamically trade off between different optimization objectives. Heuristic search strategies specifically refer to mechanisms that use empirical rules to guide solution space exploration. They can be implemented using generalized methods such as simulated annealing, genetic algorithms, or tabu search, aiming to efficiently approximate the global optimum. Response mechanisms for equipment failures or personnel changes refer to triggering mechanisms for real-time detection of anomalies in the production site. They can be implemented using event listeners, message queues, or status monitoring, aiming to promptly detect changes in the production environment. Dynamic reallocation of production tasks refers to the method of adjusting task allocation based on the current resource status. It can be implemented using generalized methods such as rule-based allocation, real-time optimization algorithms, or priority scheduling, with the aim of ensuring the continuity of the production process.

[0096] Through the above technical solutions, this application effectively solves the problems of multi-objective scheduling conflicts and rigid scheduling in civil aircraft manufacturing. The intelligent scheduling sub-component, through a multi-objective optimization framework and heuristic search strategy, achieves a comprehensive balance between production efficiency, resource utilization, and delivery time while meeting the complex constraints of aerospace manufacturing, avoiding the overall benefit imbalance caused by single-objective optimization. The task scheduling sub-component, through an event-driven dynamic reallocation mechanism, responds in real time to emergencies such as equipment failures or personnel changes, ensuring the continuity of the production process in a highly complex manufacturing environment, significantly improving resource utilization efficiency and production collaboration capabilities, thereby meeting the stringent requirements of flexible scheduling and real-time response in civil aircraft manufacturing with single-piece, small-batch, and multi-variable processes.

[0097] Step S4: Build the quality operation domain component.

[0098] In step S4, the quality operation domain component service is unitized into quality inspection, quality collaboration, and personnel qualification management sub-components to establish loosely coupled collaborative control functions. The quality inspection sub-component has a built-in ASR feature library to automatically match sampling plans based on part categories and integrates NDT and PCLR test sheet templates to standardize inspection content and judgment criteria. It is also configured to support multi-level approval, version management, and report export functions for Quality Assurance Records (QARs). The quality collaboration sub-component is established based on an event-triggered cross-departmental collaborative workflow. When an inspection detects a quality anomaly, a closed-loop processing flow including problem definition, root cause analysis, corrective action formulation, and effectiveness verification is automatically initiated. The personnel qualification management sub-component is used to maintain personnel skill files and business authorization matrices, providing permission verification and compliance assurance for quality-related business operations.

[0099] The ASR feature library refers to a database storing automatic sampling rules. It can use rule-based matching algorithms or statistical methods to automatically select sampling schemes, aiming to improve the efficiency and consistency of quality inspection. In practical applications, event-triggered cross-departmental collaborative workflows refer to automated business processes implemented based on message middleware. These can use message queue technologies such as RabbitMQ or Kafka to implement event publishing and subscription, aiming to accelerate the closed-loop processing of quality issues.

[0100] In an optional embodiment, the ASR automatic matching algorithm executed by the quality inspection subcomponent can perform similarity calculations based on the geometric features, material properties, and multi-dimensional feature vectors of quality requirements of the parts to select inspection schemes from the sampling rule base. The event triggering mechanism of the quality collaboration subcomponent supports multi-level quality problem classification and processing, and automatically determines the processing priority and responsible department according to the severity and scope of the quality problem.

[0101] The ASR (Automatic Sampling Response) matching algorithm is a dynamic sampling rule selection mechanism based on multi-dimensional feature vectors. It utilizes feature vector extraction and similarity measurement techniques to comprehensively capture attributes such as the physical structure, material properties, and quality indicators of parts, avoiding matching biases caused by relying solely on part categories. The multi-level quality problem classification processing of the quality collaboration sub-component involves classifying quality problems into different levels according to preset standards. This can be achieved using a quantitative evaluation model, aiming to optimize problem handling paths and eliminate the subjectivity of manual intervention. Automatically determining processing priorities and responsible departments means the system dynamically assigns processing entities based on the problem's impact dimension. This can be achieved using weight calculation and responsibility matrix mapping techniques, ensuring that critical issues are prioritized and the responsible entities are accurately identified.

[0102] Specifically, the proposed solution uses a quality inspection sub-component to transform the geometric features, material properties, and quality requirements of parts into multi-dimensional feature vectors. These vectors are then matched with rules in a sampling rule base to dynamically select suitable inspection schemes. Simultaneously, when a quality anomaly is detected, the quality collaboration sub-component automatically assesses the severity and scope of the problem, triggering appropriate processing flows and assigning responsibility to relevant departments, forming a complete chain from problem discovery to closed-loop processing. This mechanism enables the system to achieve precise sampling by comprehensively considering the multi-dimensional attributes of parts, avoiding rigid inspection standards. Furthermore, by quantitatively analyzing the dimensions of problem impact, it ensures priority scheduling and clear accountability for critical quality issues, thereby optimizing cross-departmental collaboration efficiency.

[0103] Step S5: Build the logistics management domain component.

[0104] In step S5, core logistics functions such as material distribution and line-side replenishment are integrated into a unified logistics management domain component. This component is configured to trigger corresponding logistics management actions by subscribing to work order status change events published by the production operations domain component. When the logistics management domain component subscribes to a work order initiation event, it automatically parses the corresponding work order's material requirements list and generates a material preparation task. Real-time data interaction with the inventory management system ensures material distribution. The logistics management domain component monitors line-side inventory based on a safety stock threshold and automatically triggers replenishment reminders and delivery processes when inventory levels fall below a preset threshold.

[0105] When the production scheduling module issues a work order initiation event, the logistics management domain component automatically parses the material requirements list for that work order and generates the corresponding material preparation task. Through real-time data interaction with the inventory management system, it ensures the timely delivery of the required materials. The line-side inventory management function is based on a safety stock threshold monitoring mechanism. When the line-side inventory level is detected to be lower than a preset threshold, it automatically triggers replenishment reminders and emergency delivery processes to ensure the continuity of production operations.

[0106] Step S6: Build the device operation and maintenance domain component.

[0107] In step S6, the equipment operation and maintenance domain component service is unitized into sub-components for equipment file management, equipment repair, equipment maintenance, equipment operation, and equipment usage. These sub-modules are configured to share a unified equipment master data model to support integrated management throughout the entire lifecycle. The equipment file management sub-component is used to establish and maintain equipment master data files containing basic equipment information, technical parameters, and installation location. The equipment repair management sub-component supports electronic workflow management from fault reporting to repair completion, including fault information collection, automatic dispatch of repair tasks, repair process tracking, and repair result recording. The equipment maintenance management sub-component automatically generates preventative maintenance plans based on key indicators such as equipment operating time and usage frequency, and tracks their execution.

[0108] In this embodiment, the equipment file management submodule establishes and maintains equipment master data files containing key information such as basic equipment information, technical parameters, and installation location, providing a unified data foundation for other equipment management functions. The equipment maintenance management submodule supports fully electronic workflow management from fault reporting to maintenance completion, including functions such as fault information collection, automatic dispatch of maintenance tasks, maintenance process tracking, and maintenance result recording. The equipment maintenance management submodule automatically generates preventative maintenance plans based on key indicators such as equipment operating time and usage frequency and tracks their execution.

[0109] Step S7: Construct the technical infrastructure services for the platform support layer.

[0110] In step S7, containerized deployment, service registration and discovery, unified master data management, process configuration, workflow engine, and event flow bus are used to achieve independent deployment, dynamic scaling, and process adjustment capabilities for each domain component in the domain-side application unit. Containerized deployment refers to packaging the application and its dependencies into lightweight runtime units, which are then scheduled and orchestrated by the orchestration engine to support rapid deployment and elastic scaling.

[0111] In optional embodiments, containerized deployment relies on the workload and release abstraction of the orchestration platform to achieve declarative deployment and lifecycle management of domain components, and supports batch replacement, version rollback, and health detection. Service registration and discovery dynamically adjusts the number of service instances based on service load and coordinates with traffic distribution strategies. Unified master data management ensures data consistency through data version control and change notification mechanisms. When master data changes, notifications are automatically sent to relevant domain components to update their local caches. Process configuration provides a visual process designer, supporting drag-and-drop operations to define business processes and approval rules, and automatically converts them into executable process engines for execution. The workflow engine provides dynamic orchestration and execution capabilities for business processes, supporting multi-level task configuration, process governance, and workflow instance management in full-fledged parallel scenarios. The workflow engine enables cross-domain component business process orchestration and execution, ensuring process collaboration and status linkage in full-fledged parallel production scenarios. The event flow bus provides cross-domain component event publishing, subscription and distribution capabilities, supports asynchronous communication, status linkage and event routing and load balancing in full-fledged parallel production scenarios, and enables event-driven collaboration of cross-domain components through the event flow bus, ensuring real-time status synchronization and dynamic resource scheduling in full-fledged parallel production scenarios.

[0112] Containerized deployment ensures consistent runtime environments by automatically managing resource allocation and state synchronization through standardized images and declarative configuration. Service registration and discovery enables automatic addressing and collaborative scaling based on registry directory maintenance and service naming resolution. Unified master data management focuses on centralized governance and change traceability of critical master data, combined with message channels to trigger component cache refresh. Process configurability manages processes and permission rules in a visual configuration manner, enabling flexible adjustments to business rules without modifying program code.

[0113] The above mechanism forms a closed-loop capability of "deployment scheduling - service addressing - data consistency - process governance": container orchestration provides elastic resources and state self-healing, registration and discovery ensure service addressing and horizontal scaling, master data governance ensures cross-domain consistency, and process configuration supports rapid changes in business orchestration, providing a stable and agile technical foundation for complex manufacturing scenarios.

[0114] Specifically, the solution in this application forms an organically collaborative technical system by systematically defining the specific implementation steps of domain components and platform support layers. The two-layer architecture constructed in step S1 decouples the domain-side application unit and the platform support layer through standardized service interfaces, laying the foundation for the independent operation of subsequent components. In step S2, the service unit decomposition of the process planning domain component enables the manufacturing digital prototype sub-component to parse the 3D model and decompose the process unit, while the intelligent process generation sub-component can generate standardized process documents based on the process model. This collaborative mechanism establishes a unified link from numerical model analysis to process document generation, ensuring the standardization and consistency of the process planning process. In step S3, after the sub-components of the production operation domain component establish logical connections, the planning management sub-component generates a multi-level planning system, the intelligent scheduling sub-component dynamically optimizes the scheduling scheme under multi-dimensional constraints, the task scheduling sub-component decomposes the scheme into specific work tasks, the work order control sub-component tracks the status throughout the process, and the task scheduling sub-component dynamically reallocates tasks in response to equipment failures or personnel changes, forming a closed-loop scheduling mechanism. In step S4, the sub-components of the quality operation domain component achieve linkage through event-driven mechanisms. The quality inspection sub-component automatically matches sampling schemes and standardizes the testing process, the quality collaboration sub-component triggers cross-departmental processing upon receiving anomalies, and the personnel qualification management sub-component provides permission verification, jointly ensuring the timeliness and consistency of quality control. Compliance; In step S5, the logistics management domain component automatically triggers material preparation and delivery actions by subscribing to work order status events published by the production operations domain component, and achieves line-side replenishment based on inventory threshold monitoring, ensuring that logistics response is synchronized with production rhythm; In step S6, the sub-modules of the equipment operation and maintenance domain component share a unified master data model, the equipment file management sub-component maintains basic data, the equipment repair management sub-component realizes full-process electronic management of faults, and the equipment maintenance management sub-component generates preventive maintenance plans based on key indicators, forming a full lifecycle management chain; In step S7, the platform support layer achieves independent lifecycle management of components through containerized deployment, service registration and discovery dynamically adjusts the number of instances according to load, unified master data management ensures data consistency, and process configuration supports flexible adjustment of business rules, jointly providing elastic infrastructure for upper-layer domain components. Each step is closely connected through an event-driven mechanism and standardized interfaces, enabling domain components to operate independently and link efficiently, thereby achieving flexible resource scheduling and rapid system response in complex manufacturing scenarios.

[0115] The above steps are tightly integrated through an event-driven mechanism and standardized interfaces, enabling domain-side application units to operate independently and collaborate efficiently, achieving resource scheduling and system response in complex manufacturing scenarios. The platform introduces a unified workflow and event flow management mechanism in its overall architecture. By capturing, orchestrating, and distributing business events, it achieves process collaboration and state linkage between cross-domain components. The workflow engine supports dynamic configuration and process orchestration of multi-level tasks, while the event flow bus is responsible for asynchronous communication and subscription distribution of key events. Relying on containerized deployment and service orchestration technologies, the platform can elastically scale and automatically extend instances according to business load, ensuring stable operation and real-time response capabilities in high-concurrency and complex collaborative scenarios. Thus, the platform forms an application operation architecture centered on event flow-driven, workflow collaboration, and elastic scaling, providing unified support for the digital and intelligent operation of the entire civil aircraft manufacturing process.

[0116] Through the above solutions, this application solves the problems of difficult independent deployment and insufficient dynamic collaboration of components in civil aircraft manufacturing. It realizes the logical association and dynamic redistribution between sub-components of production and operation components, ensuring that tasks can be quickly reassigned when equipment fails. The logistics component enables more timely material delivery response through a clear event subscription mechanism. The quality component establishes a closed-loop processing flow to accelerate the resolution of quality problems. The equipment component adopts a unified master data model to improve the efficiency of full life cycle management, thereby meeting the real-time and system resilience requirements of single-piece and small-batch production.

[0117] To achieve the above objectives, the present invention also provides a civil aircraft digital manufacturing platform that supports flexible expansion, which adopts a two-layer architecture that separates the domain-side application unit from the platform support layer.

[0118] The platform support layer may include:

[0119] The containerized deployment module can encapsulate, deploy, and orchestrate the components of domain-side application units based on Docker and Kubernetes;

[0120] The service registration and discovery module can maintain service registration information for domain components based on Nacos and enable dynamic addressing of service instances.

[0121] The master data management module is used to maintain a unified data model for equipment, materials, personnel, and processes, and to perform data version control and change synchronization.

[0122] The process configuration module is used to visually model business processes, and the process engine executes the process model.

[0123] The workflow engine module is used to dynamically orchestrate and execute business processes, supporting multi-level task configuration, process governance, and workflow instance management in full-scale parallel scenarios.

[0124] The event flow bus module is used to implement event publishing, subscription and distribution for cross-domain components, and supports event routing and load balancing in asynchronous communication, state linkage and full-fledged parallel production scenarios.

[0125] Domain-side application units are built on top of the platform support layer and include multiple domain components in a service-unitized operational form. Specifically, these domain components may include:

[0126] The process planning domain component is used to complete process planning and document output, including sub-components for manufacturing digital prototypes and generating process documents.

[0127] The production operations domain component is used for plan decomposition, scheduling and issuance, as well as work order execution status tracking. It includes sub-components for plan management, intelligent scheduling, task scheduling and work order control.

[0128] The Quality Operations Domain component is used for quality inspection, anomaly closure, and personnel qualification management, and includes sub-components for quality inspection, quality collaboration, and personnel qualification management.

[0129] Logistics management domain components are used for material distribution and lineside replenishment.

[0130] Equipment maintenance domain components are used for equipment file, repair, maintenance, operation and usage management.

[0131] The logistics management domain component establishes an event subscription relationship with the production and operation domain component, and triggers material preparation and delivery operations based on the work order status events published by the production and operation domain component.

[0132] Each domain component of the domain-side application unit calls the services provided by the platform support layer through standardized service interfaces to achieve decoupling and collaboration between the domain-side application unit and the platform support layer, as well as between domain components.

[0133] Specifically, in optional embodiments, such as Figure 2 As shown, the platform (system) of this invention constructs an operation and control system covering the entire process of civil aircraft manufacturing in the domain-side application unit, forming five domains: process planning domain (process document and version management, issuing process routes and resource constraints to the production domain), production operation domain (plan decomposition, work order generation and modification, assembly scheduling and takt control, realizing closed-loop production drive), logistics management domain (demand calculation, distribution and line-side inventory), quality operation domain (incoming material / process / delivery inspection, non-conformity handling, deviation tracing and statistical analysis), and equipment operation and maintenance domain (ledger, status monitoring, inspection and maintenance). These five domains are built upon a unified data management capability, completing the collection, aggregation and management of multi-source data from equipment, parts, personnel and environment, and achieving virtual-real mapping through digital twins.

[0134] like Figure 3As shown, this platform adopts a two-tier architecture at the software level, separating domain-side application units from the platform support layer (software technology foundation). The bottom layer is a unified platform support layer, providing technical infrastructure services (general modules / basic capability components). Based on this, the platform support layer integrates core service capabilities such as containerized deployment, service registration and discovery, master data management, and process configuration, ensuring independent deployment, elastic scaling, and stable operation of domain components. Simultaneously, the platform supports multiple data access methods, including on-site industrial data acquisition, document acquisition, and API acquisition, and combined with a digital twin engine and visualization capabilities, achieves unified presentation of multi-source data.

[0135] like Figure 4 As shown, this platform adopts a multi-layered system that emphasizes both layering and decoupling in its technical implementation: the interaction layer uses a component-based front-end technology stack to build the interface and manage state; the service layer completes domain services and orchestration around the mature Java ecosystem; and the data layer introduces relational, key-value, and document-based storage to support heterogeneous data. In terms of traffic governance, routing, rate limiting, and circuit breaking are achieved through reverse proxy and gateway collaboration, and observability components are used to complete logging, metrics, and link tracing. On the security side, unified identity authentication, fine-grained authorization, and end-to-end auditing are provided to ensure controllable and compliant operation.

[0136] like Figure 5 As shown, to further achieve service unitization and elastic scaling, this platform has designed independent service unitization components for core capabilities such as users, processes, objects, and messages. Taking the user service component (user component) as an example, it is divided into a platform layer (infrastructure layer), a capability layer (service layer), and a presentation layer (interface layer) from bottom to top. The presentation layer builds the front-end interface based on the front-end technology stack (ReactJS and TypeScript technology stack), providing unified login and user interaction; the capability layer encapsulates logic processing and database interaction based on the back-end framework (SpringBoot and SpringCloud); the platform layer is supported by databases, caches, a registry center, and container orchestration platforms (MySQL, Redis, Nacos, Kubernetes, etc.). In this way, the platform can achieve high cohesion, low coupling (decoupling), and flexible scaling with a service unitization architecture.

[0137] The specific implementation methods have been described in detail above and will not be repeated here.

[0138] As described above, this invention achieves complete decoupling between business functions and technical infrastructure, enabling the civil aircraft digital manufacturing platform to expand business functions on demand without changing the underlying technical architecture. Regarding the reusability and independence of domain-side components, a service-unitized component encapsulation mechanism breaks down complex manufacturing business functions into independent service components with single responsibilities and clear boundaries. Each component possesses complete business processing capabilities and standardized service interfaces. Complete functional decoupling is achieved between the core manufacturing domain capabilities of process planning, production operation, quality operation, logistics management, and equipment maintenance. Upgrading, maintaining, or failing any module will not affect the normal operation of other modules. The platform system supports on-demand combination and rapid adaptation to different aircraft models or process changes, reducing upgrade and maintenance costs. Simultaneously, through standard interfaces and event-driven mechanisms, the platform enables real-time collaboration between modules, avoiding data transmission delays and low cross-module collaboration efficiency in traditional systems, thereby ensuring the continuity and consistency of the manufacturing process.

[0139] To achieve the above objectives, the present invention also provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor runs the program, it can implement the steps of the method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion as described in any of the foregoing embodiments.

[0140] Processors and memory can be configured separately or integrated together, for example, integrated on a system-on-chip (SOC) in a terminal device.

[0141] To achieve the above objectives, the present invention also provides a computer-readable storage medium storing computer-executable instructions or computer programs, wherein when the computer-executable instructions or computer programs are processed and executed, the method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion as described above is implemented.

[0142] The computer-readable storage medium is, for example, memory. Memory can be volatile or non-volatile, or it can include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DRRAM).

[0143] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0144] The preferred embodiments of the present invention have been described in detail above. It should be understood that those skilled in the art can make numerous modifications and variations based on the concept of the present invention without creative effort. Therefore, all technical solutions that can be obtained by those skilled in the art based on the concept of the present invention through logical analysis, reasoning, or limited experimentation on the basis of existing technology should be within the scope of protection defined by the claims.

Claims

1. A method for constructing a civil aircraft digital manufacturing platform architecture supporting elastic expansion, characterized in that, Includes the following steps: Construct a two-tiered, separate platform architecture, including domain-side application units and a platform support layer; The platform support layer is configured to provide technical infrastructure services that support independent deployment and elastic scaling of domain components through containerized deployment, service registration and discovery, master data management, process configuration, workflow engine and event flow bus. The domain-side application unit is built on top of the platform support layer; wherein, the domain-side application unit includes multiple domain components for realizing process planning, production operation, quality operation, logistics management and equipment operation and maintenance functions respectively; A domain component collaboration mechanism based on event flow and workflow collaboration is established within the domain-side application unit. This mechanism utilizes an event flow bus to enable cross-domain component event publishing and subscription, and a workflow engine to orchestrate and execute business processes. A production operations domain component and a logistics management domain component are established, and a subscription relationship is established between the logistics management domain component and the work order status events published by the production operations domain component, thereby triggering logistics management actions based on event flow. Each domain component on the domain side achieves decoupling from the platform support layer and collaboration between components by calling the standardized service interfaces provided by the platform support layer; Specifically, the steps include the following: Step S1: Construct the domain-side application unit and platform support layer; Specifically, the domain-side application unit is configured to carry core manufacturing domain capabilities, including at least process planning, production operation, quality operation, logistics management, and equipment maintenance; the platform support layer is configured to provide technical infrastructure services, including at least component encapsulation, service registration and discovery, master data management, process configuration, workflow engine, and event flow bus; the workflow engine is used to realize the dynamic orchestration and execution of business processes, support the configuration and process governance of multi-level tasks, and manage workflow instances in full-fledged parallel production scenarios; the event flow bus is used to realize the event publishing, subscription, and distribution of cross-domain components, support asynchronous communication and state linkage, and event routing and load balancing in full-fledged parallel production scenarios; and the decoupling of the domain-side and the platform support layer is achieved through standardized service interfaces to ensure elastic scalability in full-fledged parallel production scenarios; Step S2: Construct the process planning domain component; Specifically, the process planning domain component service unit is divided into a manufacturing digital prototype sub-component and a process intelligent generation sub-component; the manufacturing digital prototype sub-component is configured to decompose the product's three-dimensional structure into process unit structures based on a three-dimensional model analysis engine; and the process intelligent generation sub-component is configured to generate corresponding process document content based on the process model. Step S3: Build production operations domain components; Specifically, the production operation domain component service unit is divided into sub-components for planning management, intelligent scheduling, task scheduling, and work order control, and logical connections are established between these sub-components to achieve distributed scheduling and control. The planning management sub-component formulates a multi-level production planning system based on production orders and resource constraints. The intelligent scheduling sub-component dynamically generates production scheduling schemes by comprehensively considering multi-dimensional constraints, including at least equipment capacity, personnel allocation, and process routes. The task scheduling sub-component decomposes the scheduling scheme into specific work tasks and distributes them to the corresponding production workstations. The work order control sub-component tracks and manages the execution process of production instructions throughout the entire process to ensure the controllability and traceability of the production process. Step S4: Construct the quality operation domain component; Specifically, the quality operation domain component service unit is divided into quality inspection, quality collaboration, and personnel qualification management sub-components to establish loosely coupled collaborative control functions. The quality inspection sub-component has a built-in ASR feature library to automatically match sampling plans according to part categories, and integrates NDT and PCLR test sheet templates to standardize inspection content and judgment criteria. At the same time, it is configured to support multi-level approval, version management, and report export functions for quality assurance records. The quality collaboration sub-component establishes an event-triggered cross-departmental collaborative workflow. When a quality anomaly is reported in the production or inspection process, the system initiates a processing flow that includes problem definition, cause analysis, corrective action formulation, and effect verification. The personnel qualification management sub-component is used to maintain personnel skill files and business authorization matrices, providing permission verification and compliance assurance for quality-related business operations. Step S5: Construct the logistics management domain component; Specifically, core logistics functions, including at least material distribution and line-side replenishment, are integrated into a unified logistics management domain component. This component is configured to trigger corresponding logistics management actions by subscribing to work order status change events published by the production operations domain component. Upon receiving a work order initiation event, the logistics management domain component automatically parses the corresponding work order's material requirements list and generates a material preparation task. Real-time data interaction with the inventory management system ensures material distribution. The logistics management domain component monitors line-side inventory based on a safety stock threshold and automatically triggers replenishment reminders and delivery processes when inventory levels fall below a preset threshold. Step S6: Build the device operation and maintenance domain component; Specifically, the equipment operation and maintenance domain component service unit is divided into sub-components for equipment file management, equipment repair, equipment maintenance, equipment operation, and equipment use. These sub-components are configured to share a unified equipment master data model to support integrated management throughout the entire lifecycle. The equipment file management sub-component is used to establish and maintain equipment master data files containing basic equipment information, technical parameters, and installation location. The equipment repair management sub-component supports electronic process management from fault reporting to repair completion, including fault information collection, automatic dispatch of repair tasks, repair process tracking, and repair result recording. The equipment maintenance management sub-component automatically generates preventative maintenance plans based on key indicators such as equipment operating time and usage frequency, and tracks their execution. Step S7: Construct the technical infrastructure services for the platform support layer; Specifically, containerized deployment, service registration and discovery, unified master data management, process configuration, workflow engine, and event flow bus enable independent deployment, dynamic scaling, and process adjustment capabilities for each domain-side component within the domain-side application unit. The workflow engine provides dynamic orchestration and execution capabilities for business processes, supporting multi-level task configuration, process governance, and workflow instance management in full-fledged parallel scenarios. The event flow bus provides cross-domain component event publishing, subscription, and distribution capabilities, supporting asynchronous communication, state linkage, and event routing and load balancing in full-fledged parallel production scenarios. Containerized deployment and service registration and discovery enable load-based elastic scaling, supporting dynamic resource scheduling and automatic instance scaling in full-fledged parallel production scenarios.

2. The construction method of the civil aircraft digital manufacturing platform architecture supporting elastic expansion according to claim 1, characterized in that, In step S1, the domain-side application unit and the platform support layer interact with each other through two communication protocols: synchronous call and event channel. For synchronous business scenarios that require real-time response, the RESTful API direct call method is adopted; for asynchronous business scenarios that allow delayed processing, the message queue publish and subscribe method is adopted.

3. The construction method of the civil aircraft digital manufacturing platform architecture supporting elastic expansion according to claim 1, characterized in that, In step S2, the manufacturing digital prototype sub-component constructs the three-dimensional model analysis engine based on MBD technology to automatically identify the assembly features, constraint relationships and process requirements in the three-dimensional geometric model of the product transmitted from the design system, and automatically decomposes the product structure into a process unit tree structure based on preset manufacturing process rules. The 3D model parsing engine has a built-in allocation integrity check algorithm. When it detects that there are parts in the product structure that are not covered by any process unit, it automatically triggers an integrity alarm and generates a list of missing parts. The intelligent process generation sub-component has a built-in process content generation engine assisted by a large language model. It automatically generates standardized process document content based on the structured features and process logic of historical process documents and the input part features and process requirements.

4. The construction method of the civil aircraft digital manufacturing platform architecture supporting elastic expansion according to claim 1, characterized in that, In step S3, the intelligent scheduling subcomponent has a built-in constraint satisfaction algorithm that simultaneously considers multiple conflicting optimization objectives, including at least production efficiency, resource utilization, and delivery time, within a multi-objective optimization framework. It also generates a scheduling scheme that is close to the global optimum through a heuristic search strategy. Furthermore, the task scheduling subcomponent dynamically reallocates production tasks in response to equipment failures or personnel changes.

5. The method for constructing a civil aircraft digital manufacturing platform architecture supporting flexible expansion according to claim 1, characterized in that, In step S4, the ASR automatic matching algorithm executed by the quality inspection sub-component performs similarity calculations based on the geometric features, material properties, and multi-dimensional feature vectors of quality requirements of the parts in order to select an inspection scheme from the sampling rule base. The event triggering mechanism of the quality collaboration sub-component supports multi-level quality problem classification and handling, and automatically determines the handling priority and responsible department based on the severity and scope of the quality problem.

6. The construction method of the civil aircraft digital manufacturing platform architecture supporting elastic expansion according to claim 1, characterized in that, In step S7, the containerized deployment relies on the workload control and declarative release objects of the container orchestration object platform to realize the declarative deployment, upgrade, and health management of domain components, and supports rolling updates, version rollback, and health detection; the service registration and discovery supports the elastic scaling of instances, dynamically adding or removing instances based on service pressure and including or removing them from traffic distribution and coordinating with load balancing strategies; the unified management of master data ensures data consistency through data version control and change broadcasting mechanisms, and automatically sends notifications to relevant domain components to refresh local caches when master data changes; The process configuration supports drag-and-drop definition of business processes and approval rules through a visual process modeler, and converts them into executable process configurations for the process engine to run.

7. A digital manufacturing platform for civil aircraft supporting elastic extension, characterized in that, The platform is constructed using the construction method of the civil aircraft digital manufacturing platform architecture supporting elastic expansion as described in any one of claims 1 to 6, wherein the platform adopts a two-layer architecture that separates the domain-side application unit from the platform support layer. The platform support layer includes: The containerized deployment module is used to encapsulate, deploy, and orchestrate the components of domain-side application units. The service registration and discovery module is used to maintain service registration information of domain components and realize dynamic addressing of service instances; The master data management module is used to maintain a unified data model for equipment, materials, personnel, and processes, and to perform data version control and change synchronization. The process configuration module is used to visually model business processes, and the process engine executes the process model. The workflow engine module is used to dynamically orchestrate and execute business processes, supporting multi-level task configuration, process governance, and workflow instance management in full-scale parallel scenarios. The event flow bus module is used to implement event publishing, subscription and distribution for cross-domain components, and supports event routing and load balancing in asynchronous communication, state linkage and full-fledged parallel production scenarios; The domain-side application unit is built on top of the platform support layer and includes multiple domain components in a service-unitized operational form. Each domain component includes at least: The process planning domain component is used to complete process planning and document output, including the manufacturing digital prototype and process intelligent generation sub-components; The production operations domain component is used for plan decomposition, scheduling and issuance, as well as work order execution status tracking, and includes sub-components for plan management, intelligent scheduling, task scheduling and work order control; The Quality Operations Domain component is used for quality inspection, anomaly closure, and personnel qualification management, and includes sub-components for quality inspection, quality collaboration, and personnel qualification management. Logistics management domain components are used for material distribution and lineside replenishment; Equipment operation and maintenance domain components are used for equipment file, repair, maintenance, operation and usage management; The logistics management domain component establishes an event subscription relationship with the production operation domain component, and triggers material preparation and delivery operations based on the work order status events published by the production operation domain component. Each domain component of the domain-side application unit calls the services provided by the platform support layer through standardized service interfaces to achieve decoupling and collaboration between the domain-side application unit and the platform support layer, as well as between domain components.

8. A terminal device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor runs the program, it implements the method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions or computer programs, which, when processed and executed by a processor, implement the method for constructing a civil aircraft digital manufacturing platform architecture that supports flexible expansion as described in any one of claims 1 to 6.

Images