Manufacturing configuration and design configuration difference management and control method and system

Abstract

The invention belongs to the technical field of airplane digital manufacturing, and discloses a control method for driving the difference between manufacturing configuration and design configuration, which comprises the following steps of: controlling EBOM data, product digitization and signature tasks and process files for implementing design change in PDM, establishing a data control tool platform, integrating the data control tool platform with the PDM, and establishing a data management and control tool platform; importing complete design configuration state EBOM data into a data management and control tool platform, and creating a data initial engineering configuration baseline; the EO is generated, and EO monitoring tasks are generated and pushed to a data management and control tool platform one by one; the EO monitoring task completely inherits design state data and implemented process state data; through the unique part number and father-child level three-generation relation, the part number position is accurately positioned, the design configuration state EBOM data is automatically updated, and the design state is kept to be the latest state. Through the unique part number and father-child level three-generation relation, the part number position is accurately positioned, and the EBOM data is automatically updated.

Description

Technical Field

[0001] This invention belongs to the field of aircraft digital manufacturing technology, and relates to a manufacturing design difference management platform based on the implementation schedule of design changes, specifically a method and system for managing differences between manufacturing configuration and design configuration. Background Technology

[0002] Modern aircraft manufacturing is a complex and massive systems engineering project. Especially during the development phase, aircraft manufacturing engineering changes are frequent. The completeness of the implementation of design changes in the physical aircraft, as well as the completion of process documents, are direct factors in assessing the manufacturing conformity of the aircraft's physical configuration. Aircraft manufacturing involves different suppliers. When comparing the differences between the manufactured configuration and the design configuration, in addition to the physical implementation at the main assembly stage, it is necessary to integrate all the configuration records of components manufactured by each supplier into the individual aircraft differences, down to each component, to indicate the overall configuration's technical status. The result of the comparison between the manufactured configuration and the design configuration is the final data set demonstrating manufacturing conformity by the manufacturing unit. It is also the main input basis for designers to assess the differences between the manufactured and design configurations, determining the accuracy of the aircraft's physical condition assessment, whether the current physical configuration can meet the requirements of various important tasks such as aircraft transfer, flight testing, experimentation, and certification, and even affecting flight safety. The timeliness of the input documents directly affects the progress of transfer, flight testing, experimentation, and certification, increasing development costs.

[0003] Currently, despite the development of digital management of product data, the applicant has identified the following main problems in comparing the differences between manufacturing configuration and design configuration: 1. Efficiency issues with manual sorting: Currently, the discrepancies between the physical configuration and the design configuration are sorted manually. This requires coordinating the implementation of design changes, ensuring the completion of process documents on-site, etc. The amount of data is enormous, the sorting cycle is long, and there are human identification errors and inaccurate comparisons of differences, which affects the normal implementation of tests and flight tests, and may even pose safety hazards.

[0004] 2. There are cases where different test subject configuration range lists involve the same DS, and different personnel compile different difference technical reports on the same day. This results in inconsistent difference results for the same part, leading to inaccurate configuration difference assessments. Repeated verification and modification of the difference situation are required, which delays the progress of the test task.

[0005] 3. Problem of scattered multi-source data: Manufacturing configuration and design configuration involve data from multiple stages, such as engineering drawings, digital models, progress of design change implementation, progress of process document preparation, and completion status of on-site process document implementation. This data is usually scattered in different management systems (such as PDM, MES, etc.), making it difficult to form a unified data source and lacking a full-process control platform.

[0006] 4. Information lag problem: The implementation progress of design changes is not tracked properly, the feedback on the closure of on-site instructions is not timely, and there are cases where the physical implementation has been carried out, but the statistical data feedback has not been executed. This leads to discrepancies between the comparison results and the actual installation status of the aircraft, which makes it impossible to carry out tests or test flights normally. Summary of the Invention

[0007] To address the aforementioned issues, this invention provides a method and system for controlling the differences between manufacturing and design configurations. Based on a system management platform, it achieves data sharing and integration, enabling global data control. It monitors progress through design changes and the completion status of process documents, and automatically generates a difference table between the manufacturing and design configurations using the data platform. This significantly improves the accuracy and timeliness of manufacturing configuration difference comparisons, reduces the workload of manual comparisons, and thus enhances control efficiency. The method and system possess strong systematicity and integration.

[0008] The technical solution of the present invention is as follows: A method for managing the discrepancy between manufacturing configuration and design configuration includes: managing EBOM data, product model review and approval tasks, and process documents for implementing design changes in the PDM; establishing a data management tool platform; integrating the data management tool platform with the PDM; importing complete design configuration status EBOM data into the data management tool platform; creating an initial engineering configuration baseline; and generating EO monitoring tasks after EO approval and pushing them one by one to the data management tool platform, while maintaining and tracking the implementation status of EOs. The EO monitoring task fully inherits the design status data and the implemented process status data; After the EO monitoring task is imported into the data management tool platform, the part number is accurately located by the unique process document part number and the parent-child three-generation relationship, and the design configuration status EBOM data is automatically updated to keep the design status up-to-date.

[0009] Furthermore, the process document preparation and approval tasks also include the initial preparation of referenced design models, implementation of recall letters, implementation of fault reports, and implementation of non-conforming product review reports. After the process document is approved, it is automatically pushed to the data management tool platform to monitor the progress of the implementation document preparation. The data management tool platform can read the associated design models of the process document and the component drawing numbers and version information of the process document. After EO approval, the data management tool platform will synchronize and update the process documentation information in real time. The data management tool platform has a query window dashboard that can query and quickly identify the progress of each EO or process document by EO number and process document number.

[0010] Furthermore, the data management tool platform has an MBOM data import and storage function window. After the MBOM data is imported, it directly indexes and locates the unique part number based on the three-level parent-child part number relationship, updates the physical installation status, process documents, and difference descriptions, and serves as background data, which is not displayed in the progress management window; the data management tool platform does not restrict the process document format.

[0011] Furthermore, the data management tool platform references component information from process documents or implements EO process data, overlays and accumulates statistical data on physical and design status, and automatically calculates and compares differences, that is, compares the consistency between the version of the installed physical drawing number and the version of the design drawing number, and edits configuration difference descriptions based on the differences; it also formulates manufacturing configuration and design configuration difference management templates in the data management tool platform, establishes configuration difference description entries and principles, and automatically generates manufacturing configuration and design configuration difference tables; finally, it exports the latest manufacturing configuration and design configuration difference table.

[0012] Furthermore, the drawing number and version information of EBOM and EO are linked to the design configuration status information in the manufacturing configuration vs. design configuration difference table. The drawing number and version information referenced or implemented in the process documents are linked to the physical installation status information in the manufacturing configuration vs. design configuration difference table. During the process document information overlay calculation, duplicate instructions are automatically merged. The process instructions in the process document column of the manufacturing configuration vs. design configuration difference table are a collection of all historical instructions. If an instruction is invalidated, the data management tool platform automatically identifies whether there is an invalidation instruction in the process document column. After identifying an invalidation instruction, the corresponding table is automatically cleared. At the same time, based on the component version implemented in the instruction, the physical status information is automatically revoked, and the instruction number is added to the remarks.

[0013] Furthermore, the differences between the manufacturing configuration and the design configuration can be categorized into three types: no difference, version difference, and retention. No difference means the design configuration state is consistent with the actual installed state. Version difference means the design configuration state is inconsistent with the actual installed state, with the actual version being lower than the design configuration version. Changes due to version differences do not require implementation; this type of difference indicates a version difference and requires a difference assessment. Retention is divided into assembly retention and implementation retention. Assembly retention refers to components not being installed, while implementation retention refers to parts being installed but with design changes that have not been fully implemented. Other types include design changes requiring disassembly, but the actual device has not yet been disassembled.

[0014] Furthermore, EBOM data is managed in a modular fashion. A DS is a management module, and DS represents a configuration model. Each DS contains a different number of finished products, parts, components, and R models under its EBOM relationship. The module status of instruction consumption in implementing DS is divided into initial instruction reference with the drawing number consistent with the design status or implementation of design changes. Therefore, the logic for generating the manufacturing configuration and design configuration difference table is to sort out the correspondence between the initial implementation instructions of all process documents and DS, components, and R models, and then overlay and statistically analyze the correspondence between subsequent process documents implementing design changes, implementing recall letters, implementing fault tickets, implementing non-conforming product review tickets, and other types of instructions.

[0015] Furthermore, the instructions refer to or implement DS, the version of the physical installation drawing number is consistent with the version of the design drawing number, all related instructions have been closed, the physical installation drawing number and version and process documents have been updated, and the difference description is that there is no difference; If the DS is referenced or implemented in the instruction, and the version of the physical drawing number is inconsistent with the version of the design drawing number, and the EO implementation is not required if the physical version is lower than the design version, the physical installation status and process documents remain unchanged, and the difference should be described as version difference. If the DS is referenced or implemented in the instruction, and the version of the physical installation drawing number is inconsistent with the version of the design drawing number, and the EO with the physical version being lower than the design version, it needs to be implemented. If the instruction is not closed, the physical installation status and process documents will not be updated. The difference should be explained by writing "implementation" and retained. If the instruction references or implements DS, the version of the physical installation drawing number is consistent with the version of the design drawing number, the instruction is not closed, the physical installation status and process documents are not updated, the physical status information is empty, and the difference is explained as assembly retention; The instruction references or implements DS, the physical installation status already exists, the version of the physical installation drawing number and the version of the design drawing number are consistent, and the difference is described as no difference.

[0016] A control system for driving the difference between manufacturing configuration and design configuration, running the aforementioned control method for driving the difference between manufacturing configuration and design configuration, includes a data control tool platform, which is integrated with PDM and MES. The data control tool platform has an EBOM data import module, an MBOM data import module, an EO monitoring module, a process document structured management module, and a control template for the difference between manufacturing configuration and design configuration.

[0017] The beneficial effects of this invention are as follows: 1. On the one hand, this invention can change the structural relationship through EO, accurately locate the part number position through the unique part number and the parent-child three-generation relationship, and automatically update the EBOM data.

[0018] 2. The present invention, through the implementation progress control of design changes and the implementation progress control of process documents in relation to design data and execution status, can monitor the implementation progress and completion status of process documents in real time, and can query and download the incomplete list, which can be used as a basis for identifying the physical configuration status.

[0019] 3. The present invention can integrate design change data, process documents and physical completion data, automatically compare and output the differences between the manufacturing configuration and the design configuration, effectively solve the problem of diversified data sources, and reduce the problems of long manual comparison cycle and inaccuracy. It can output a list of differences between the manufacturing configuration and the design configuration according to the required option list. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of this invention, the drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this invention and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained from these drawings without creative effort.

[0021] Figure 1 This is a diagram showing the data transmission and sharing relationships within the platform integration of this invention.

[0022] Figure 2 This is a list of incomplete items in the design changes and process documents of this invention.

[0023] Figure 3 This is a template diagram comparing the differences between the design configuration and the manufacturing configuration of this invention.

[0024] Figure 4 This is a diagram illustrating the differences between the design configuration and the manufacturing configuration of this invention.

[0025] Figure 5 This is a diagram showing the input source of the design configuration state data and physical configuration state data of this invention. Detailed Implementation

[0026] This section describes embodiments of the present invention, used to explain and illustrate the technical solutions of the present invention. Unless otherwise specified, the embodiments and features described herein can be combined with each other.

[0027] In the description of this invention, it should be understood that the terms "center," "longitudinal," "lateral," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating directions or positional relationships, are given in the accompanying drawings and are used only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or device referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implying the number of indicated technical features. Thus, features defined with "first," "second," etc., may explicitly or implicitly include more than one of those features. In the description of this invention, unless otherwise stated, "a plurality of" means two or more.

[0028] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integrated connections; they can refer to mechanical connections or point connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0029] Example 1: A method for managing the discrepancy between manufacturing configuration and design configuration includes: managing EBOM data, product model review and approval tasks, and process documents for implementing design changes in the PDM; establishing a data management tool platform; integrating the data management tool platform with the PDM; importing complete design configuration status EBOM data into the data management tool platform; creating an initial engineering configuration baseline; and generating EO monitoring tasks after EO approval and pushing them one by one to the data management tool platform, while maintaining and tracking the implementation status of EOs. The EO monitoring task fully inherits the design status data and the implemented process status data; After the EO monitoring task is imported into the data management tool platform, the part number is accurately located through the unique part number and the parent-child three-generation relationship, and the design configuration status EBOM data is automatically updated to keep the design status up-to-date.

[0030] The process document preparation and approval task also includes the initial preparation of referenced design models, implementation of recall letters, implementation of fault reports, and implementation of non-conforming product review reports. After the process document is approved, it is automatically pushed to the data management tool platform to monitor the progress of the implementation document preparation. The data management tool platform can read the associated design models of the process document and the component drawing numbers and version information of the process document. After EO approval, the data management tool platform will synchronize and update the process documentation information in real time. The data management tool platform has a query window dashboard that can query and quickly identify the progress of each EO or process document by EO number and process document number.

[0031] The data management tool platform has an MBOM data import and storage function window. After the MBOM data is imported, it directly indexes and locates the unique part number based on the three-level parent-child part number relationship, updates the physical installation status, process documents, and difference descriptions, and serves as background data, which is not displayed in the progress management window. The data management tool platform does not restrict the process document format.

[0032] The data management tool platform references component information from process documents or implements EO process data, overlays and accumulates statistics on physical and design status, and automatically calculates and compares differences, that is, compares the consistency between the version of the installed physical drawing number and the version of the design drawing number, and edits configuration difference descriptions based on the differences; it also formulates manufacturing configuration and design configuration difference management templates in the data management tool platform, establishes configuration difference description entries and principles, and automatically generates manufacturing configuration and design configuration difference tables; finally, it exports the latest manufacturing configuration and design configuration difference table.

[0033] The drawing number and version information of EBOM and EO are linked to the design configuration status information in the manufacturing configuration vs. design configuration difference table. The drawing number and version information referenced or implemented in the process documents are linked to the physical installation status information in the manufacturing configuration vs. design configuration difference table. During the process document information overlay calculation, duplicate instructions are automatically merged. The process instructions in the process document column of the manufacturing configuration vs. design configuration difference table are a collection of all historical instructions. If an instruction is invalidated, the data management tool platform automatically identifies whether there is an invalidation instruction in the process document column. After identifying an invalidation instruction, the corresponding table is automatically cleared. At the same time, based on the component version implemented in the instruction, the physical status information is automatically revoked, and the instruction number is added to the remarks.

[0034] Differences between the manufacturing configuration and the design configuration can be categorized into three types: no difference, version difference, and retention. No difference means the design configuration matches the actual installed configuration. Version difference means the design configuration differs from the actual installed configuration, with the actual version being lower than the design version. Changes due to version differences do not require implementation; this type of difference indicates a version difference and requires a difference assessment. Retention is further divided into assembly retention and implementation retention. Assembly retention refers to components not being installed, while implementation retention refers to parts being installed but with design changes that have not been fully implemented. Other types include design changes requiring disassembly, but the actual device has not yet been disassembled.

[0035] EBOM data is managed in a modular fashion. A DS is a management module, and DS is a configuration model. Each DS contains a different number of finished products, parts, components, and R models under its EBOM relationship. The module status of instruction consumption in the DS is divided into the initial compilation of instruction reference and the drawing number consistent with the design status or the implementation of its design changes. Therefore, the logic for generating the manufacturing configuration and design configuration difference table is to sort out the correspondence between the initial implementation instructions of all process documents and DS, components, and R models, and then overlay and statistically analyze the correspondence of subsequent process documents implementing design changes, recall letters, fault tickets, non-conforming product review tickets, and other types of instructions.

[0036] The instructions reference or implement DS, the version of the physical installation drawing number is consistent with the version of the design drawing number, all related instructions have been closed, the physical installation drawing number and version and process documents have been updated, and the difference description is no difference; If the DS is referenced or implemented in the instruction, and the version of the physical drawing number is inconsistent with the version of the design drawing number, and the EO implementation is not required if the physical version is lower than the design version, the physical installation status and process documents remain unchanged, and the difference should be described as version difference. If the DS is referenced or implemented in the instruction, and the version of the physical installation drawing number is inconsistent with the version of the design drawing number, and the EO with the physical version being lower than the design version, it needs to be implemented. If the instruction is not closed, the physical installation status and process documents will not be updated. The difference should be explained by writing "implementation" and retained. If the instruction references or implements DS, the version of the physical installation drawing number is consistent with the version of the design drawing number, the instruction is not closed, the physical installation status and process documents are not updated, the physical status information is empty, and the difference is explained as assembly retention; The instruction references or implements DS, the physical installation status already exists, the version of the physical installation drawing number and the version of the design drawing number are consistent, and the difference is described as no difference.

[0037] A control system for driving the difference between manufacturing configuration and design configuration, running the aforementioned control method for driving the difference between manufacturing configuration and design configuration, includes a data control tool platform, which is integrated with PDM and MES. The data control tool platform has an EBOM data import module, an MBOM data import module, an EO monitoring module, a process document structured management module, and a control template for the difference between manufacturing configuration and design configuration.

[0038] Example 2: A method for globally automated management and control of the implementation schedule of design changes and the differences between manufacturing configuration and design configuration, comprising: S1. In the Process Coordination Platform (PDM), manage EBOM data, product model review and approval tasks, and process document preparation and approval tasks for implementing design changes. Establish a data management tool platform integrated with the Process Coordination Platform (PDM), import complete design configuration EBOM data into the data management tool platform, and create an initial engineering configuration baseline. Design changes that occur after the EBOM is imported, after the Design Change (EO) is approved, generate EO monitoring tasks that are automatically pushed to the data management tool platform to update the EBOM data and track the implementation of the EO.

[0039] After S2.EO approval, an EO monitoring task is generated. The EO monitoring task fully inherits the design status data and the implemented process status data, including detailed change content, structural change relationship before and after the change, drawing number before and after the change, version before and after the change, work-in-process handling opinions, change method, division of labor for process implementation, process review and approval opinions, and status of related process documents for implementation and modification.

[0040] After the S3.EO monitoring task is imported into the data management platform, the part number of the component to which the EO belongs is accurately located through the unique part number and the parent-child three-generation relationship. The design configuration status EBOM data is automatically updated, including design status drawings, version, quantity and other information, to keep the design status up-to-date.

[0041] The method for globally automated management of differences between manufacturing configuration and design configuration based on design change implementation schedule also includes: S4. In addition to implementing design changes, process documents also include types such as initial compilation of referenced design models, implementation of recall letters, implementation of fault reports, and implementation of non-conforming product review reports. After approval, process documents are automatically pushed to the data management tool platform to monitor the progress of document compilation. The process documents are managed in a structured manner, and information such as the design models associated with the process documents and the component drawing numbers and versions associated with the process documents can be read.

[0042] After EO approval, the process documentation preparation for EO implementation requires a period of time. The process documentation information associated with EO that is directly transmitted to the data management tool platform through the platform integration data is incomplete. After the subsequent process documentation preparation is completed, the data management tool platform will also update the process documentation information in real time.

[0043] The data management tool platform establishes a query window dashboard, which allows users to quickly identify the progress of each EO or process document by querying the EO number and process document number.

[0044] S5. The process collaboration platform is integrated with the MES platform. After the process documents are approved, they are imported into the MES platform to track, record and manage the progress of the implementation and completion of the process documents.

[0045] S6. The data management tool platform is integrated with the physical installation record MES platform. After the process document is completed, it will be automatically fed back to the data management tool platform, and the process document status will be "completed".

[0046] The implementation schedule control of the aforementioned design changes also includes: S7. The data management tool platform establishes a query window dashboard, allowing users to quickly identify the implementation progress status of each EO or process document by querying by EO number and process document number. It can also export a list of incomplete EOs and process documents.

[0047] Furthermore, S4 specifically includes: S8. Some components are outsourced to suppliers for production. These components are delivered with a supplier-provided MBOM (Model-Based Manufacturing Organization), which details the differences between the manufactured and designed configurations. The data management platform has enabled an MBOM data import and storage function. After importing this type of data, it directly indexes and locates the unique part number based on the three-level parent-child part number relationship, updating the physical installation status, process documents, and difference descriptions. This data is stored in the background and is not displayed in the progress management window. The data management platform does not restrict the format of process documents.

[0048] Furthermore, S9. Based on the data from steps S1-S7, a configuration difference comparison is performed. The data management tool platform uses component information referenced in the process documents or implements EO process data, overlays and accumulates statistical data on physical and design states, and automatically calculates and compares the differences, that is, compares the consistency between the version of the installed physical drawing number and the version of the design drawing number, and edits the configuration difference description according to the differences.

[0049] Furthermore, S9 specifically includes: Develop a template for managing differences between manufacturing and design configurations, and establish principles and definitions for comparing configuration differences. The system will automatically perform comparisons between manufacturing and design configurations.

[0050] Differences between the manufacturing configuration and the design configuration can be categorized into three types: no difference, version difference, and retention. No difference means the design configuration matches the physical assembly configuration. Version difference means the design configuration differs from the physical assembly, with the physical version being lower than the design version. Changes due to version differences do not require implementation; this type of difference indicates a version discrepancy and requires a difference assessment. Retention includes assembly retention and implementation retention. Assembly retention refers to components not being installed, while implementation retention refers to parts being installed but not fully implemented due to design changes or malfunctions. Other types include design changes requiring disassembly, but the physical assembly has not yet been disassembled.

[0051] EBOM data is managed modularly, with each DS (Design Module) representing a component model. Each DS's EBOM contains varying numbers of finished products, parts, components, and R models. Instruction consumption across DS modules is categorized into initial instruction references to drawing numbers consistent with the design status or implementation of design changes. Therefore, the logic for generating the difference comparison table involves identifying the correspondence between the initial implementation instructions in all process documents and the corresponding DS, components, and R models. This is then overlaid with statistics to determine the correspondence between subsequent process documents implementing design changes, recall letters, fault reports, and non-conforming product review reports.

[0052] The instructions reference or implement DS (components), the version of the physical assembly drawing number is consistent with the version of the design drawing number, all related instructions have been closed, the physical assembly drawing number and version and process documents have been updated, and the difference description is no difference.

[0053] If the instruction references or implements DS (components), and the version of the physical assembly drawing number is inconsistent with the version of the design drawing number, and the EO implementation is lower than the design version, then no implementation is required. The physical assembly status and process documents remain unchanged. The difference should be described as a version difference, for example: "Version difference: AB, changes." "Version difference: 051A-051B, changes."

[0054] If the instruction references or implements DS (components), and the version of the physical installation drawing number is inconsistent with the version of the design drawing number, or if the EO (Equipment Entity) version is lower than the design version, it must be implemented. If the instruction is not closed, the physical installation status and process documents will not be updated. The difference should be explained by writing "implementation" to retain it.

[0055] The instruction references or implements DS (components), the version of the physical assembly drawing number is consistent with the version of the design drawing number, the instruction is not closed, the physical assembly status and process documents are not updated, the physical status information is empty, and the difference is explained as assembly retention.

[0056] The instruction references or implements the DS (component), the physical installation status already exists, the version of the physical installation drawing number and the version of the design drawing number are consistent, and the difference description is "no difference". When a new instruction references or implements the DS's EO, and the instruction is not closed, this type does not change the difference description status. This type may exist because disassembly has not yet been implemented or the modification of the relevant part has not been executed. For disassembly not implemented, the aircraft status remains unchanged or there is no difference; for part modification not executed, the retained content is reflected in the corresponding component of the implementation.

[0057] S10. Update the design configuration data and the actual manufacturing configuration data, and fill in the difference description.

[0058] The drawing numbers and versions of EBOM and EO are linked to the design configuration status information in the configuration difference table. The drawing numbers and versions referenced or implemented in the process documents are linked to the physical installation status information in the configuration difference table. During the overlay calculation of process document information, duplicate instructions are automatically merged. The process instructions in the process document column of the difference table are a collection of all historical instructions.

[0059] The physical assembly diagram number and version will only change after the command is closed; otherwise, the physical assembly status will remain unchanged from the previous state.

[0060] If a new instruction is invalidated, the system will automatically identify whether the instruction exists in the process document column. If an invalid instruction is detected, the table will be automatically cleared. At the same time, based on the component version implemented in the instruction, the physical status information and difference description will be automatically revoked, that is, the physical status updated by the instruction will be revoked, and the instruction number will be added to the remarks to facilitate the verification of the physical status.

[0061] S11. Finally, an option difference report can be automatically generated based on the required DS range, and the latest manufacturing configuration and design configuration difference table can be exported.

[0062] Secondly, the present invention also provides a system management platform that applies the above-mentioned global automated control method for manufacturing configuration and design configuration differences driven by the implementation schedule of design changes.

[0063] Example 3: like Figure 1 As shown, the present invention provides a globally automated management method for differences between manufacturing configuration and design configuration driven by the implementation schedule of design changes. This method is based on a system management platform and includes the following steps: Step S1. In the process coordination platform PDM, manage EBOM data, product model review and approval tasks, and process document preparation and approval tasks to implement design changes. Establish a data management tool platform integrated with the process coordination platform PDM, import complete EBOM and historical EO data into the data management tool platform, and create the initial engineering configuration baseline for the data.

[0064] S1-1: Integration of the Process Coordination Platform (PDM) and the Data Management Tool Platform; Data Transfer Methods Visible Figure 1 Specifically, for a particular model for which drawings have already been released, the design configuration needs to be frozen (for models not yet released, freezing is not necessary; data transfer can begin directly from the first digital model release). The complete design configuration data EBOM and historical EOs are then transferred and imported into the data management tool platform. An engineering configuration data baseline is created on the data management tool platform to lay the foundation for subsequent data maintenance.

[0065] S1-2: After the data is successfully imported, the design configuration data will be unfrozen. Any new data or EO data thereafter will be automatically transferred to the data management tool platform after approval in the process coordination platform.

[0066] Step S2. After importing the complete EBOM data, any design changes (hereinafter referred to as EOs) that occur will be automatically pushed to the data management tool platform to update the design configuration status EBOM data after the EO is approved. The implementation status of the EO will also be maintained and tracked.

[0067] Once the EO is approved, an EO monitoring task is generated. The EO monitoring task fully inherits the design status data and the information of the implemented process documents, including detailed change content, structural changes before and after the change, drawing numbers before and after the change, versions before and after the change, work-in-process handling opinions, change methods, division of labor for process implementation, process review and approval opinions, and information on related process documents.

[0068] Step S3. After importing the EO data, based on the unique part number and the parent-child three-generation relationship, the part number position of the component to which the EO belongs is accurately located, and the design configuration status EBOM data is automatically updated, including design status drawings, version, quantity and other information, to keep the design status up-to-date.

[0069] S3-1: Aircraft configurations may have borrowed parts, such as wings, nacelles, and other symmetrical structures. There may be identical structural parts on the left and right sides of the aircraft, but they belong to different components. Therefore, when managing and associating data, it is necessary to identify the parent and grandparent of the parts.

[0070] S3-2: In addition, based on the structured management of EO monitoring tasks, the EO has its own path, which makes it easier to identify the location of parts and components.

[0071] Step 4. In addition to implementing the EO (Engineer Entity), process documents also include the initial compilation of referenced design models, implementation of recall letters, implementation of fault reports, and implementation of non-conforming product review reports. The implementation process of process documents is updated and pushed to the data management tool platform to monitor the progress of document compilation. The process documents are managed in a structured manner, allowing for the reading of design models associated with the process documents and information such as component drawing numbers and versions.

[0072] After S4-1.EO approval, the process document preparation for implementing the EO requires a period of time. The process document information associated with the EO that is directly transmitted to the data management tool platform through the platform integration data is incomplete. After the subsequent process document preparation is completed, the data management tool platform will also update the process document information in real time.

[0073] S4-2. The data management tool platform establishes a query window dashboard, which allows users to quickly identify the progress of each EO or process document by querying the EO number and process document number.

[0074] Step S5. Integrate the process collaboration platform with the MES platform. After the process documents are approved, import them into the MES platform to track, record, and manage the implementation and completion progress of the process documents.

[0075] Step S6. The data management tool platform is integrated with the physical installation record MES platform. After the process document is completed, it will be automatically linked to the data management tool platform, and the process document status will be "completed".

[0076] The data management platform establishes a query dashboard, allowing users to quickly identify the completion status of each process document by searching for the EO number and process document number. It can also export a list of incomplete EOs and process documents. See [link / reference]. Figure 2 .

[0077] Step S7. Some components are outsourced to suppliers for production. When these components are delivered, they come with a supplier-provided MBOM (Model-Based Manufacturing Organization), which details the differences between the manufacturing configuration and the design configuration. The data management tool platform enables the MBOM data import and storage function. After importing this type of data, it directly indexes and locates the unique part number based on the three-level parent-child part number relationship, updates the physical installation status, process documents, and difference descriptions, and stores this as background data, not displayed in the progress management window. The data management tool platform does not restrict the format of process documents.

[0078] Step S8. Based on the data from steps S1-S7, perform configuration difference comparison. The data management tool platform uses component information referenced in process documents or implements EO process data, overlays and accumulates statistical data on physical and design states, and automatically calculates and compares differences, that is, compares the consistency between the version of the installed physical drawing number and the version of the design drawing number, and edits configuration difference descriptions based on the differences.

[0079] S8-1. Develop a template for managing differences between manufacturing and design configurations, and establish principles and definitions for comparing configuration differences. (See below) Figure 3 and Figure 4 The system automatically compares the differences between the manufacturing configuration and the design configuration.

[0080] S8-2. Differences between the manufactured configuration and the design configuration can be categorized into three types: no difference, version difference, and retention. No difference means the design configuration matches the physical assembly configuration. Version difference means the design configuration differs from the physical assembly, with the physical version being lower than the design version. Changes due to version differences do not require implementation; this type of difference indicates a version difference and requires a difference assessment. Retention includes assembly retention and implementation retention. Assembly retention refers to components not being installed, while implementation retention refers to parts being installed but not fully implemented due to design changes or malfunctions. Other types include design changes requiring disassembly, but the physical assembly has not yet been disassembled.

[0081] S8-3. EBOM data is managed modularly. Each DS (Designated Component) is a management module, and each DS contains a different number of finished products, parts, components, and R models under its EBOM relationship. The implementation of instructions within the DS module is categorized into initial instruction references to drawing numbers consistent with the design status or implementation of design changes. Therefore, the logic for generating the difference comparison table involves identifying the correspondence between the initial implementation instructions in all process documents and the DS, components, and R models, and then overlaying and statistically analyzing the correspondence between subsequent process documents implementing design changes, recall letters, fault reports, non-conforming product review reports, and other types of instructions.

[0082] The instructions reference or implement DS (components), the version of the physical assembly drawing number is consistent with the version of the design drawing number, all related instructions have been closed, the physical assembly drawing number and version and process documents have been updated, and the difference description is no difference.

[0083] If the instruction references or implements DS (components), and the version of the physical assembly drawing number is inconsistent with the version of the design drawing number, and the EO implementation is lower than the design version, then no implementation is required. The physical assembly status and process documents remain unchanged. The difference should be described as a version difference, for example: "Version difference: AB, changes." "Version difference: 051A-051B, changes."

[0084] If the instruction references or implements DS (components), and the version of the physical installation drawing number is inconsistent with the version of the design drawing number, or if the EO (Equipment Entity) version is lower than the design version, it must be implemented. If the instruction is not closed, the physical installation status and process documents will not be updated. The difference should be explained by writing "implementation" to retain it.

[0085] The instruction references or implements DS (components), the version of the physical assembly drawing number is consistent with the version of the design drawing number, the instruction is not closed, the physical assembly status and process documents are not updated, the physical status information is empty, and the difference is explained as assembly retention.

[0086] The instruction references or implements the DS (component), the physical installation status already exists, the version of the physical installation drawing number and the version of the design drawing number are consistent, and the difference description is "no difference". When a new instruction references or implements the DS's EO, and the instruction is not closed, this type does not change the difference description status. This type may exist because disassembly has not yet been implemented or the modification of the relevant part has not been executed. For disassembly not implemented, the aircraft status remains unchanged or there is no difference; for part modification not executed, the retained content is reflected in the corresponding component of the implementation.

[0087] Step S9. Update the design configuration data and the physical manufacturing configuration data, and fill in the difference description.

[0088] The drawing numbers and versions of S9-1.EBOM and EO are linked to the design configuration status information in the configuration difference table. The drawing numbers and versions referenced or implemented in the process documents are linked to the physical installation status information in the configuration difference table. (See...) Figure 5 During the overlay and calculation of process document information, duplicate instructions are automatically merged. The process instructions in the process document column of the difference table are a collection of all historical instructions.

[0089] S9-2. After the command is closed, the physical installation drawing number and version will be changed; otherwise, the physical installation status will remain unchanged.

[0090] S9-3. When a new instruction is invalidated, the system will automatically identify whether the instruction exists in the process document column. If an invalidated instruction is detected, the table will be automatically cleared. At the same time, based on the component version implemented in the instruction, the physical status information and difference description will be automatically revoked, that is, the physical status updated by the instruction will be revoked, and the instruction number will be added to the remarks to facilitate the verification of the physical status.

[0091] Step S10. Finally, an option difference report can be automatically generated based on the required DS range, and the latest manufacturing configuration and design configuration difference table can be exported.

[0092] The above-disclosed embodiments are merely preferred embodiments of the present invention and should not be construed as limiting the scope of the invention. Therefore, any equivalent variations made in accordance with the claims of the present invention shall still fall within the scope of the invention.

Claims

1. A method for controlling the difference between manufacturing configuration and design configuration, characterized in that, include: In PDM, manage EBOM data, product model approval tasks, and process documents for implementing design changes. Establish a data management tool platform, integrate the data management tool platform with PDM, and import complete design configuration status EBOM data into the data management tool platform to create an initial engineering configuration baseline. For subsequent EOs, after EO approval, generate EO monitoring tasks and push them to the data management tool platform one by one, and maintain and track the implementation status of EOs. The EO monitoring task fully inherits the design status data and the implemented process status data; After the EO monitoring task is imported into the data management tool platform, the process document part number is accurately located through the unique process document part number and the parent-child three-generation relationship, and the design configuration status EBOM data is automatically updated to keep the design status up-to-date.

2. The method for controlling the difference between the manufacturing configuration and the design configuration according to claim 1, characterized in that, The process document preparation and approval task also includes the initial preparation of referenced design models, implementation of recall letters, implementation of fault reports, and implementation of non-conforming product review reports. After the process document is approved, it is automatically pushed to the data management tool platform to monitor the progress of the implementation document preparation. The data management tool platform can read the associated design models of the process document and the component drawing numbers and version information of the process document. After EO approval, the data management tool platform will synchronize and update the process documentation information in real time. The data management tool platform has a query window dashboard that can query and quickly identify the progress of each EO or process document by EO number and process document number.

3. The method for controlling the difference between the manufacturing configuration and the design configuration according to claim 2, characterized in that, The data management tool platform has an MBOM data import and storage function window. After the MBOM data is imported, it directly indexes and locates the unique part number according to the three-level parent-child part number relationship, updates the physical installation status, process documents and difference descriptions, and serves as background data, which is not displayed in the progress management window. The data management tool platform does not restrict the format of process documents.

4. The method for controlling the difference between the manufacturing configuration and the design configuration according to claim 2, characterized in that, The data management tool platform references component information from process documents or implements EO process data, overlays and accumulates statistics on physical and design status, and automatically calculates and compares differences, that is, compares the consistency between the version of the installed physical drawing number and the version of the design drawing number, and edits configuration difference descriptions based on the differences; it also formulates manufacturing configuration and design configuration difference management templates in the data management tool platform, establishes configuration difference description entries and principles, and automatically generates manufacturing configuration and design configuration difference tables; finally, it exports the latest manufacturing configuration and design configuration difference table.

5. The method for controlling the difference between the manufacturing configuration and the design configuration according to claim 4, characterized in that, The drawing number and version information of EBOM and EO are linked to the design configuration status information in the manufacturing configuration vs. design configuration difference table. The drawing number and version information referenced or implemented in the process documents are linked to the physical installation status information in the manufacturing configuration vs. design configuration difference table. During the process document information overlay calculation, duplicate instructions are automatically merged. The process instructions in the process document column of the manufacturing configuration vs. design configuration difference table are a collection of all historical instructions. If an instruction is invalidated, the data management tool platform automatically identifies whether there is an invalidation instruction in the process document column. After identifying an invalidation instruction, the corresponding table is automatically cleared. At the same time, based on the component version implemented in the instruction, the physical status information is automatically revoked, and the instruction number is added to the remarks.

6. The method for controlling the difference between the manufacturing configuration and the design configuration according to claim 4, characterized in that, Differences between the manufacturing configuration and the design configuration can be categorized into three types: no difference, version difference, and retention. No difference means the design configuration matches the actual installed configuration. Version difference means the design configuration differs from the actual installed configuration, with the actual version being lower than the design version. Changes due to version differences do not require implementation; this type of difference indicates a version difference and requires a difference assessment. Retention is further divided into assembly retention and implementation retention. Assembly retention refers to components not being installed, while implementation retention refers to parts being installed but with design changes that have not been fully implemented. Other types include design changes requiring disassembly, but the actual device has not yet been disassembled.

7. The method for controlling the difference between the manufacturing configuration and the design configuration according to claim 1, characterized in that, EBOM data is managed in a modular fashion. A DS is a management module, and DS is a configuration model. Each DS contains a different number of finished products, parts, components, and R models under its EBOM relationship. The module status of instruction consumption in the DS is divided into the initial compilation of instruction reference and the drawing number consistent with the design status or the implementation of its design changes. Therefore, the logic for generating the manufacturing configuration and design configuration difference table is to sort out the correspondence between the initial implementation instructions of all process documents and DS, components, and R models, and then overlay and statistically analyze the correspondence of subsequent process documents implementing design changes, recall letters, fault tickets, non-conforming product review tickets, and other types of instructions.

8. The method for controlling the difference between the manufacturing configuration and the design configuration according to claim 7, characterized in that, The instructions reference or implement DS, the version of the physical installation drawing number is consistent with the version of the design drawing number, all related instructions have been closed, the physical installation drawing number and version and process documents have been updated, and the difference description is no difference; If the DS is referenced or implemented in the instruction, and the version of the physical drawing number is inconsistent with the version of the design drawing number, and the EO implementation is not required if the physical version is lower than the design version, the physical installation status and process documents remain unchanged, and the difference should be described as version difference. If the DS is referenced or implemented in the instruction, and the version of the physical installation drawing number is inconsistent with the version of the design drawing number, and the EO with the physical version being lower than the design version, it needs to be implemented. If the instruction is not closed, the physical installation status and process documents will not be updated. The difference should be explained by writing "implementation" and retained. If the instruction references or implements DS, the version of the physical installation drawing number is consistent with the version of the design drawing number, the instruction is not closed, the physical installation status and process documents are not updated, the physical status information is empty, and the difference is explained as assembly retention; The instruction references or implements DS, the physical installation status already exists, the version of the physical installation drawing number and the version of the design drawing number are consistent, and the difference is described as no difference.

9. A control system for driving differences between manufacturing configuration and design configuration, comprising a control method for driving differences between manufacturing configuration and design configuration as described in any one of claims 1-8, characterized in that... This includes a data management tool platform that integrates with both PDM and MES. The data management tool platform includes modules for EBOM data import, MBOM data import, EO monitoring, structured management of process documents, and templates for managing differences between manufacturing configuration and design configuration.

Images