A data processing method, system, medium and device for a composite product

Abstract

The embodiment of the application provides a kind of composite product data processing method, system, medium and equipment, method includes: through the material master data in product life cycle management unit in integration center, through enterprise resource planning unit, the target manufacturing process of order is inquired, through manufacturing execution unit production and generates report work data, through integration center, the ratio of material consumption weight and theoretical consumption weight is sent to enterprise resource planning unit as consumption deviation coefficient, through integration center, based on solidification effective period, corner material recycling is judged, and through enterprise resource planning unit, according to consumption deviation coefficient, the standard consumption quota in material list is updated, and according to report work data, inventory and cost are updated, realize the whole process data processing of composite product from order, corner material recycling and material list quota correction, improve data consistency and data processing efficiency.

Description

Technical Field

[0001] This application belongs to the field of data processing technology, and in particular relates to a data processing method, system, medium and equipment for composite material products. Background Technology

[0002] In the field of digital manufacturing, product data processing typically relies on independently deployed systems such as Product Lifecycle Management (PLM), Enterprise Resource Planning (ERP), Manufacturing Execution System (MES), and Warehouse Management System (WMS). These systems respectively manage product design data, production planning data, shop floor execution data, and material warehousing data, forming a digital chain from R&D to delivery.

[0003] However, in practice, each system operates independently, exchanging data through point-to-point interfaces or manual import / export methods. Product data is stored in a fragmented manner across different systems, lacking unified data standards, coding specifications, and business flow rules, resulting in low efficiency in cross-system data processing throughout the entire process from order to delivery. Summary of the Invention

[0004] This application provides a data processing method, system, medium, and device for composite material products, which can realize the entire process of data processing for composite material products from order processing, scrap recycling, and bill of materials quota correction, thereby improving data consistency and data processing efficiency.

[0005] In a first aspect, embodiments of this application provide a data processing method for composite material products, applied to an integrated information system. The integrated information system includes an integration platform, and a product lifecycle management unit, an enterprise resource planning unit, a manufacturing execution unit, and a warehouse management unit that are communicatively connected to the integration platform via pluggable adapters. The pluggable adapters are configured with standard interface templates corresponding to the respective units, including: The integrated platform synchronizes the material master data of the product lifecycle management unit to each unit. The material master data includes the material's solidification expiration date, the product's manufacturing process, and the bill of materials. The enterprise resource planning unit responds to the order by querying the target manufacturing process and target bill of materials corresponding to the ordered product from the material master data, and then forwards them to the manufacturing execution unit through the integration platform. The manufacturing execution unit produces the ordered products according to the target manufacturing process and generates work report data, which includes the finished product quantity, material consumption weight, and scrap weight of the ordered products. The integrated platform receives the work report data and determines the theoretical consumption weight based on the finished product quantity and the standard consumption quota in the target bill of materials; the ratio of the material consumption weight to the theoretical consumption weight is used as the consumption deviation coefficient and sent to the enterprise resource planning unit. The integrated platform queries the target curing validity period of scrap materials from the material master data; if the current date has not exceeded the target curing validity period, the weight of the scrap materials is sent to the warehouse management unit for recycling; after recycling is completed, the work report data is sent to the enterprise resource planning unit. The enterprise resource planning unit updates the standard consumption quotas of materials in the target bill of materials based on the consumption deviation coefficient, and updates the inventory and cost of the ordered products based on the work report data.

[0006] In one feasible implementation, the material master data includes temperature and humidity thresholds for the manufacturing process; the step of producing the ordered product according to the target manufacturing process by the manufacturing execution unit and generating work report data includes: The manufacturing execution unit obtains the current temperature and humidity; if the current temperature and humidity are not greater than the target temperature and humidity threshold corresponding to the target manufacturing process, the order product is produced according to the target manufacturing process and work report data is generated. When the current temperature and humidity exceed the target temperature and humidity threshold, the manufacturing execution unit locks the start permission of the target manufacturing process and generates a temperature and humidity warning message to prompt the user to adjust the current temperature and humidity.

[0007] In one feasible implementation, before producing the ordered product according to the target manufacturing process via the manufacturing execution unit, the method further includes: The integrated platform performs an expiration date check on the target material based on the current date and the curing expiration date of the target material required for the ordered product. Upon successful inspection, the integrated platform generates a material release instruction and sends it to the manufacturing execution unit. If the inspection fails, the integrated platform generates an expiration warning for the target material and sends it to the user. The process of producing the ordered product according to the target manufacturing process through the manufacturing execution unit includes: The manufacturing execution unit responds to the material release instruction and produces the ordered product according to the target manufacturing process.

[0008] In one feasible implementation, the material master data further includes a material code for uniquely identifying each type of material; Sending the weight of the scrap material to the warehouse management unit for recycling includes: The integrated platform determines the weight of each specification of scrap material based on the weight of the scrap material and the preset specification classification rules, and generates a material code for each specification of scrap material. The warehousing management unit allocates recycling locations based on the material code and weight of each specification of scrap material, and records the warehousing registration data after recycling the scrap material according to the recycling location. The step of updating the inventory and cost of the ordered products based on the reported work data includes: The integration platform forwards the warehouse registration data and the work reporting data to the enterprise resource planning unit. The enterprise resource planning unit updates the inventory and cost of the ordered products based on the inbound registration data and the work report data.

[0009] In one feasible implementation, the material master data of the product lifecycle management unit is synchronized to each unit through the integration platform, including: The product lifecycle management unit initiates an engineering change request to the integration platform, and the engineering change request carries the material sub-data to be synchronized. In response to the engineering change request, the integrated platform generates an engineering change notification. The engineering change notification is used to synchronize the material sub-data to the enterprise resource planning unit, the manufacturing execution unit, and the warehouse management unit through field mapping.

[0010] In one feasible implementation, before initiating an engineering change request to the integration platform through the product lifecycle management unit, the method further includes: The integration platform performs cross-comparison of message queue logs and / or timestamps for each of the enterprise resource planning unit, manufacturing execution unit, and warehouse management unit according to a preset fallback scanning cycle, based on the material master data in the product lifecycle management unit, to determine the list of units to be synchronized. The integration platform sends the list to be synchronized to the product lifecycle management unit. The step of initiating an engineering change request to the integration platform through the product lifecycle management unit includes: When the material master data changes or the list to be synchronized is received, the product lifecycle management unit determines the material sub-data to be synchronized. The product lifecycle management unit initiates the engineering change request to the integration platform based on the material sub-data.

[0011] In one feasible implementation, after the enterprise resource planning unit responds to an order by querying the target manufacturing process and target bill of materials corresponding to the ordered product from the material master data, and forwarding them to the manufacturing execution unit via the integration platform, the method further includes: The integrated platform detects abnormal events during the production process of the ordered products. These abnormal events include at least one of the following: temperature and humidity exceeding the standard and locking, material expiration, failure to verify the expiration date of scrap materials, and failure to synchronize engineering changes. The integrated platform determines the abnormal alarm level of the abnormal event based on the preset mapping relationship between event type and alarm level. Each alarm level corresponds to a preset notification method and response action, and the response action includes at least one of retry, locking, data isolation and user permission freezing. The integrated platform pushes abnormal alarm information to the user according to the notification method corresponding to the abnormal alarm level, and triggers the response action corresponding to the abnormal alarm level.

[0012] Secondly, embodiments of this application provide a data processing system for composite material products. The integrated information system includes an integration platform, and a product lifecycle management unit, an enterprise resource planning unit, a manufacturing execution unit, and a warehouse management unit that are communicatively connected to the integration platform via pluggable adapters. The pluggable adapters are configured with standard interface templates corresponding to the respective units, including: The product lifecycle management unit is used to upload material master data to the integration platform. The material master data includes the material's expiration date, the product's manufacturing process, and the bill of materials. The enterprise resource planning unit is used to respond to orders by querying the target manufacturing process and target bill of materials corresponding to the ordered product from the material master data and sending them to the integration platform; receiving the consumption deviation coefficient sent by the integration platform and updating the standard consumption quota of the materials in the target bill of materials according to the consumption deviation coefficient; and receiving the work report data sent by the integration platform and updating the inventory and cost of the ordered product according to the work report data. The manufacturing execution unit is used to produce the ordered products according to the target manufacturing process and generate work report data, which includes the finished product quantity, material consumption weight, and scrap weight of the ordered products; and to send the work report data to the integration platform. The warehouse management unit is used to receive the weight of the scrap materials sent by the integrated platform, and to recycle the scrap materials according to the weight of the scrap materials; The integrated platform is used to synchronize the material master data to each unit; forward the target manufacturing process and the target bill of materials to the manufacturing execution unit; receive the work report data and determine the theoretical consumption weight based on the finished product quantity and the standard consumption quota in the target bill of materials; send the ratio of the material consumption weight to the theoretical consumption weight as the consumption deviation coefficient to the enterprise resource planning unit; query the target solidification validity period of scrap materials from the material master data; if the current date has not exceeded the target solidification validity period, send the weight of the scrap materials to the warehouse management unit; and after recycling is completed, send the work report data to the enterprise resource planning unit.

[0013] Thirdly, embodiments of this application provide a data processing device for composite material products. The device includes a processor and a memory storing computer program instructions. The processor reads and executes the computer program instructions to implement any of the above-described data processing methods for composite material products.

[0014] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement any of the above-described data processing methods for composite material products.

[0015] Fifthly, embodiments of this application provide a computer program product, wherein when the instructions in the computer program product are executed by the processor of an electronic device, the electronic device performs any of the above-described data processing methods for composite material products.

[0016] This application discloses a data processing method, system, medium, and device for composite material products. It integrates and synchronizes material master data (including curing validity period, manufacturing process, and temperature and humidity thresholds) within the product lifecycle management unit via an integrated platform. It queries the target manufacturing process of an order through an enterprise resource planning (ERP) unit, generates production data including scrap weight through a manufacturing execution (MEP) unit, calculates theoretical consumption weight based on finished product quantity and standard consumption quotas via the integrated platform, and sends the ratio of material consumption weight to theoretical consumption weight as a consumption deviation coefficient to the ERP unit. It also determines scrap recycling based on the curing validity period via the integrated platform, and updates the standard consumption quotas in the bill of materials (BOM) based on the consumption deviation coefficients and updates inventory and costs based on the production data via the ERP unit. This achieves end-to-end data processing for composite material products, from order processing and scrap recycling to BOM quota correction, improving data consistency and processing efficiency. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic flowchart of a data processing method for composite material products provided in an embodiment of this application; Figure 2 This is a schematic diagram of the structure of the integrated information system provided in the embodiments of this application; Figure 3 This is a schematic diagram of the structure of a data processing device for composite material products provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a data processing device for composite material products provided in an embodiment of this application. Detailed Implementation

[0019] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0020] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0021] In the field of digital manufacturing, product data processing typically relies on independently deployed systems such as Product Lifecycle Management (PLM), Enterprise Resource Planning (ERP), Manufacturing Execution System (MES), and Warehouse Management System (WMS). These systems respectively manage product design data, production planning data, shop floor execution data, and material warehousing data, forming a digital chain from R&D to delivery.

[0022] However, in practice, each system operates independently, exchanging data through point-to-point interfaces or manual import / export methods. Product data is stored in a fragmented manner across different systems, lacking unified data standards, coding specifications, and business flow rules, resulting in low efficiency in cross-system data processing throughout the entire process from order to delivery.

[0023] To address the problems in the prior art, embodiments of this application provide a data processing method, apparatus, device, and computer storage medium for composite material products.

[0024] In practical applications, the execution subject of the data processing method for composite material products in this application embodiment can be a terminal device, such as a desktop computer or laptop computer, or a remote device similar to a server. Of course, the execution subject in this application embodiment can also be a software entity, such as a client or software program installed on a terminal device. The specific type of execution subject corresponding to the technical solution provided in this application embodiment is not strictly limited here, and can be flexibly selected according to the actual application scenario and actual needs.

[0025] The following describes specific embodiments of a data processing method, apparatus, medium, and equipment for composite material products provided in this application. First, a data processing method for composite material products is introduced.

[0026] Figure 1 A flowchart illustrating a data processing method for a composite material product according to an embodiment of this application is shown. Figure 1 As shown, this method is applied to an integrated information system, which includes an integration platform, a product lifecycle management unit, an enterprise resource planning unit, a manufacturing execution unit, and a warehouse management unit. The product lifecycle management unit, enterprise resource planning unit, manufacturing execution unit, and warehouse management unit communicate with the integration platform through pluggable adapters pre-configured with corresponding standard interface templates. The data processing procedure for this composite material product includes steps S100 to S105: S100: The material master data of the product lifecycle management unit is synchronized to each unit through the integrated platform. The material master data includes the material's solidification validity period, the product's manufacturing process, and the bill of materials.

[0027] In one or more embodiments of this application, in order to enable subsequent production execution and scrap recycling to make decisions and controls based on the time validity and environmental sensitivity of materials, in this step, this application uses the product lifecycle management unit as the sole source of material master data, and distributes it uniformly to the enterprise resource planning unit, manufacturing execution unit and warehouse management unit through an integrated platform to ensure that each unit operates under a unified data standard.

[0028] Specifically, this application can pre-build an integration platform and pre-construct a unified master data governance module within it. This module defines a unified material coding standard, a fixed expiration date format, manufacturing process numbering rules, and a data structure for temperature and humidity thresholds. After the product lifecycle management unit publishes the material master data, the integration platform can obtain the material master data from the product lifecycle unit through active retrieval or passive reception, and then convert the material master data into a format recognizable by each unit according to preset field mapping rules before distributing it accordingly.

[0029] It should be noted that the integration platform includes an access adaptation layer, a data standard layer, a business orchestration layer, and an application service layer. The access adaptation layer connects the various units and has built-in pluggable adapters supporting multiple access methods such as WebService, API, middleware library, and MQ message queue, and pre-configures standard interface templates for each unit. The data standard layer defines and maintains master data standards such as material codes, BOMs, and process routes to achieve unified data governance and consistent data distribution. The business orchestration layer defines end-to-end business processes across systems to achieve automatic collaboration between units. The application service layer provides unified business capability interfaces and services such as monitoring, alarms, and access control. This application uses PLM as the R&D source, ERP as the planning hub, MES as the production execution hub, and WMS as the warehouse logistics endpoint, achieving consistent material master data, seamless process flow, event-driven operations, and real-time linkage across the four units through the integration platform.

[0030] This application does not limit the specific content of the material master data, which can be set according to actual needs. For example, the material master data may also include a material code (such as a material type batch number) to uniquely identify each type of material, a formula ratio version, temperature and humidity thresholds for the manufacturing process, temperature and humidity thresholds for the storage environment, and classification rules for scrap specifications. To address the physical characteristic of composite material raw materials having a curing shelf life, and the requirement that the manufacturing process of composite material products is sensitive to the temperature and humidity of the production environment, in one or more embodiments of this application, two fields, curing shelf life and temperature and humidity thresholds, may be added to the material master data. The temperature and humidity thresholds include upper temperature limits and upper humidity limits, as follows: First, when uploading product manufacturing operations, the Product Lifecycle Management (PLM) unit writes the required temperature and humidity thresholds for each manufacturing process as an additional attribute into the material master data. For example, the temperature and humidity thresholds for the thermosetting curing process are 25℃ / 60%RH. Second, after receiving the material master data, the integration platform stores it in its database and maintains data version consistency among the Enterprise Resource Planning (ERP) unit, Manufacturing Execution (MEP) unit, and Warehouse Management (WMM) unit. Finally, when the ERP unit queries the target manufacturing process based on the order, the corresponding temperature and humidity thresholds for each target manufacturing process are also returned along with the target manufacturing process, so that the MEP unit can use them for environmental comparison before starting operations.

[0031] S101: In response to the order, the Enterprise Resource Planning (ERP) unit queries the target manufacturing process and target bill of materials corresponding to the ordered product from the material master data, and forwards them to the Manufacturing Execution (MEP) unit via the integration platform.

[0032] In one or more embodiments of this application, in order to determine the start-up conditions based on accurate manufacturing processes and production environment temperature and humidity thresholds during subsequent production execution, in this step, this application uses the Enterprise Resource Planning (ERP) unit as the order response hub, utilizes its synchronized material master data to automatically query the target manufacturing process corresponding to the order product and its corresponding target temperature and humidity thresholds, and forwards them to the Manufacturing Execution Unit through the integration platform to realize the automated transmission from order to production instructions.

[0033] Specifically, after receiving a user's order, the Enterprise Resource Planning (ERP) unit searches the locally synchronized material master data based on the material code corresponding to the ordered product to match the target manufacturing process and target bill of materials for that product. The ERP unit encapsulates the query results, including the identifier of the target manufacturing process, the sequence of the target manufacturing process, the operation parameters, and the target bill of materials, and sends them to the integration platform. The business orchestration layer of the integration platform then forwards them to the Manufacturing Execution Unit (MEP).

[0034] It should be noted that this application does not limit the specific method by which the Enterprise Resource Planning (ERP) unit queries material master data. The method can be set according to actual needs, such as through API calls, database queries, or message queue request and response modes. This application also does not limit the specific form of the order; the order can be a sales order, a production order, or an internal transfer order, etc. To ensure that the Manufacturing Execution Unit (MLU) can obtain complete environmental assessment data before commencing operations, in one or more embodiments of this application, when the ERP unit queries material master data, it needs to obtain the target temperature and humidity thresholds for each target manufacturing process in the entire product manufacturing process, as follows: First, the Enterprise Resource Planning (ERP) unit parses basic information from the order, such as product material code, order quantity, and delivery date, and locates the corresponding product manufacturing operation in the material master data based on the product material code. Second, the ERP unit extracts the complete target manufacturing process and the associated target temperature and humidity thresholds for each target manufacturing process from the product manufacturing operation. For target manufacturing processes without explicitly set temperature and humidity thresholds, preset general thresholds can be used by default, or no production environment determination can be made. Finally, the ERP unit assembles the product material code, order quantity, target manufacturing process, and target temperature and humidity thresholds for each target manufacturing process into a manufacturing instruction and sends it to the integration platform. The integration platform's business orchestration layer can forward this manufacturing instruction to the corresponding manufacturing execution unit according to preset routing rules.

[0035] S102: The manufacturing execution unit produces the ordered product according to the target manufacturing process and generates work report data, which includes the finished product quantity, material consumption weight, and scrap weight of the ordered product.

[0036] In one or more embodiments of this application, in order to enable subsequent scrap recycling and cost updates to be processed based on accurate material consumption data and recyclable resource data, in this step, this application uses a manufacturing execution unit to produce the order products according to the target manufacturing process, and automatically generates work report data containing the quantity of finished products, the weight of material consumption and the weight of scrap after production is completed, thereby realizing closed-loop control of production execution and production environment linkage.

[0037] Specifically, this application involves producing ordered products in the manufacturing execution unit according to the target manufacturing process, and recording the material consumption weight of each target manufacturing process, the quantity of finished products in the order, and the weight of scrap generated in the trimming and finishing processes, and summarizing them to form structured work reporting data.

[0038] It should be noted that this application does not limit the specific format of the reporting data; JSON, XML, or a custom data structure can be used. When the material master data includes temperature and humidity thresholds for manufacturing processes, in order to ensure that the manufacturing processes of composite material products start under preset environmental conditions during production and to avoid product quality abnormalities due to excessive environmental temperature and humidity, in one or more embodiments of this application, a data interface with a temperature and humidity sensor of the production environment is pre-configured in the manufacturing execution unit. Before starting the target manufacturing process, the manufacturing execution unit reads the current temperature and humidity values ​​of the production environment in real time through this data interface and compares the current temperature and humidity with the target temperature and humidity thresholds forwarded by the integration platform. If the current temperature and humidity do not exceed the thresholds, production is allowed to start and proceed according to the target manufacturing process; conversely, if any parameter of the current temperature and humidity exceeds the target temperature and humidity thresholds, the start permission for that process is locked, and a temperature and humidity warning message is generated and sent to the user to prompt the user to adjust the current temperature and humidity of the production environment.

[0039] In this embodiment, the present application does not limit the specific method by which the manufacturing execution unit obtains the current temperature and humidity. It can be set according to the actual deployment of the production environment, such as a temperature and humidity sensor connected via an RS485 bus, a PLC acquisition point accessed via an industrial Ethernet network, or sensor data uploaded via a wireless IoT gateway. To address the recyclable nature of scrap materials during composite material product production and the management requirement that scrap materials have the same curing shelf life as the raw materials used in production, in one or more embodiments of this application, when the manufacturing execution unit generates work report data, it separately counts the scrap materials and records their association with the corresponding raw materials, as follows: First, during production, the Manufacturing Execution Unit (MExecution Unit) calculates the weight of scrap generated by each manufacturing process that produces scrap (such as trimming and finishing) using weighing equipment at the end of the manufacturing process or a preset standard loss rate. Second, the MExecution Unit associates the scrap weight with the material codes of the raw materials used in this production run. The scrap inherits the fixed shelf life attribute of the raw materials, meaning its shelf life is the same as the remaining shelf life of the raw materials. Finally, the MExecution Unit writes the finished product quantity, the material consumption weight of each raw material, the scrap weight, and the associated material codes into the work report data, which is then forwarded to the Enterprise Resource Planning (ERP) and Warehouse Management (WMM) units via the integration platform for further processing.

[0040] To avoid using expired raw materials before putting them into production and to ensure product quality and the subsequent recycling value of scrap materials, in one or more embodiments of this application, before producing the order products according to the target manufacturing process, the application needs to perform a pre-shipment expiration inspection on the target materials through an integrated platform. If the inspection passes, a material shipment instruction is generated, and then the manufacturing execution unit responds to the material shipment instruction to produce the order products according to the target manufacturing process, as follows: First, the integration platform verifies the expiration date of the target material based on the current date and its fixed expiration date. This application does not limit the specific representation of the fixed expiration date; it can be set according to actual needs, such as representing it as an absolute date after which it expires, or as a relative number of days valid within N days of warehousing. For example, the integration platform obtains the fixed expiration date and the warehousing date of the target material from the material master data, calculates the difference between the current date and the warehousing date, and compares this difference with the fixed expiration date to determine whether the material is still within its validity period.

[0041] Secondly, the integrated platform generates a material release instruction and sends it to the manufacturing execution unit after the inspection is passed. For example, if the difference between the current date and the receipt date does not exceed the fixed validity period, the inspection is passed; if the difference exceeds the fixed validity period, the inspection fails.

[0042] Finally, the integrated platform generates an expiration warning for the target material if the inspection fails, and sends it to the user. This expiration warning includes, but is not limited to, information such as material code, material name, current inventory batch number, date of receipt, expiration date in days, and expiration date in days. This allows users to promptly handle expired materials, performing operations such as scrapping, returning, or downgrading their use, preventing waste materials from accidentally entering the production process.

[0043] S103: Receive the work report data through the integrated platform, and determine the theoretical consumption weight based on the finished product quantity and the standard consumption quota in the target bill of materials; send the ratio of the material consumption weight to the theoretical consumption weight as the consumption deviation coefficient to the enterprise resource planning unit.

[0044] S104: Query the target curing validity period of the scrap material from the material master data through the integrated platform; if the current date has not exceeded the target curing validity period, send the weight of the scrap material to the warehouse management unit for recycling; after recycling is completed, send the work report data to the enterprise resource planning unit.

[0045] In one or more embodiments of this application, in order to recycle only scrap materials with reuse value and dynamically adjust the standard consumption quota in the bill of materials according to actual production consumption in subsequent inventory updates and cost allocation, and to avoid including expired scrap materials in the recycling process, resulting in invalid warehousing and incorrect cost accounting, in steps S103 and S104, this application determines the standard consumption quota for dynamically adjusting the bill of materials and performs a pre-verification of the solidified validity period of scrap materials through an integrated platform.

[0046] Specifically, after receiving the work report data from the Manufacturing Execution Unit (MAU) in the integrated platform, this application analyzes the scrap weight, the material code of the associated raw material, the quantity of finished products, and the material consumption weight. Based on the quantity of finished products and the standard consumption quota in the target bill of materials, the integrated platform determines the theoretical consumption weight and then uses the ratio of the material consumption weight to the theoretical consumption weight as a consumption deviation coefficient, sending it to the Enterprise Resource Planning (ERP) unit. Based on the material code of the raw material, the integrated platform retrieves the target solidification expiration date corresponding to the scrap from the material master data and obtains the raw material's warehousing date. The integrated platform calculates the difference between the current date and the warehousing date and compares this difference with the solidification expiration date; if the difference does not exceed the expiration date, the scrap is determined to have reuse value, and the scrap weight and associated raw material material code are sent to the warehouse management unit; if the difference exceeds the expiration date, the scrap is determined to be expired, the recycling request is intercepted, and an expiration warning is triggered. After the warehouse management unit completes the registration of scrap material return to the warehouse, it sends a recycling completion message back to the integration platform. After receiving the recycling completion message, the integration platform sends the work report data reported by the manufacturing execution unit to the enterprise resource planning unit.

[0047] It should be noted that the consumption deviation coefficient reflects the actual consumption characteristics of materials under the current production environment. When the consumption deviation coefficient is greater than 1, it indicates that the actual consumption is higher than the theoretical quota; when the consumption deviation coefficient is less than 1, it indicates that the actual consumption is lower than the theoretical quota; when the consumption deviation coefficient is equal to 1, it indicates that the actual consumption is consistent with the theoretical quota. When the enterprise resource planning unit subsequently receives an order using the same material, the integration platform can query the historical consumption deviation coefficient corresponding to that material, and then send the historical consumption deviation coefficient to the enterprise resource planning unit. The enterprise resource planning unit multiplies it by the standard consumption quota in the bill of materials to obtain the corrected theoretical consumption weight, which is used for cost budgeting and material procurement planning. In this application, the specific triggering time for validity period verification is not limited. Verification can be performed in real time when the work report data is received, or it can be verified again before the warehouse management unit executes recycling to ensure data accuracy. In order to address the scenario where composite material scraps have different recycling values ​​due to different specifications and sizes, in one or more embodiments of this application, after the integration platform receives the work report data and before triggering the warehouse management unit to recycle, a process for scrap specification classification and recoding is added, as follows: First, the integration platform determines the weight of each specification of scrap material based on its weight and preset specification classification rules, and generates a material code for each specification. This application does not limit the specific content of the specification classification rules; they can be set according to actual needs, such as classifying materials larger than 20cm as large pieces, 5-20cm as small pieces, and less than 5cm as scraps. For example, the integration platform initiates a request to the main data unified governance module to generate an independent material code for each specification of scrap material, such as CF-SCRAP-LARGE-001 for large pieces and CF-SCRAP-SMALL-001 for small pieces, and associates the scrap material with the curing shelf life of the raw material, meaning the curing shelf life of the scrap material is consistent with the remaining shelf life of the raw material.

[0048] Secondly, the warehouse management unit allocates recycling locations based on the material code and weight of each type of scrap material. After recycling the scrap material according to the designated location, the unit records the entry registration data. For example, the warehouse management unit assigns high-value recycling location A-01 to large pieces (CF-SCRAP-LARGE-001), crushing location B-03 to small pieces (CF-SCRAP-SMALL-001), and waste material location C-99 to scrap (CF-SCRAP-WASTE-001). Forklift operators or AGVs can then transport the scrap material to the designated location according to the recycling location guide. The warehouse management unit scans the material code to complete the entry registration and updates the scrap material inventory ledger.

[0049] Finally, the integrated platform forwards the warehouse entry registration data and work reporting data to the enterprise resource planning unit, so that the enterprise resource planning unit can update the inventory and cost of the ordered products based on the warehouse entry registration data and work reporting data.

[0050] S105: The enterprise resource planning unit updates the standard consumption quotas of materials in the target bill of materials according to the consumption deviation coefficient, and updates the inventory and cost of the ordered products according to the reported work data. In one or more embodiments of this application, in order to automatically complete data accounting after the scrap recycling is completed and realize closed-loop collaboration between production execution and data accounting, in this step, this application forwards the consumption deviation coefficient and work report data to the enterprise resource planning unit through the integration platform. The enterprise resource planning unit updates the standard consumption quota, finished product inventory and order cost of the order products according to the work report data, avoiding the delay and errors of manual entry.

[0051] Specifically, the Enterprise Resource Planning (ERP) unit parses the reported work data and receives the consumption deviation coefficient; based on the consumption deviation coefficient, the ERP unit updates the standard consumption quota, such as multiplying the standard consumption quota of the corresponding material in the target bill of materials by the consumption deviation coefficient to obtain the updated standard consumption quota; the ERP unit increases the finished goods inventory ledger based on the quantity of finished products, deducts raw material inventory based on the weight of materials consumed, and calculates the cost deduction amount based on the weight of scrap and the preset recycling value, thereby adjusting the production cost of the order.

[0052] For example, the enterprise resource planning unit updates the finished goods inventory based on the quantity of finished products in the work report data. Based on the weight and recycling value of scrap materials in the inventory registration data, such as large pieces having higher recycling value, small pieces having lower value, and scrap having no recycling value, the scrap recycling revenue is deducted from the product cost to achieve cost allocation. For example, if 5kg of large pieces are calculated at a recycling value of 50 yuan per kilogram, totaling 250 yuan, 2kg of small pieces are calculated at 20 yuan per kilogram, totaling 40 yuan, and 1kg of scrap has no recycling value, then 290 yuan is deducted from the product cost, so the product cost is adjusted from the original 10,000 yuan to 9,710 yuan.

[0053] It should be noted that this application does not restrict the specific methods by which enterprise resource planning units update inventory and costs. These methods can be set according to the actual data accounting system, such as using the moving average method, the first-in-first-out method, or the standard cost method.

[0054] In the data processing method for the aforementioned composite material products, this application reverse-corrects the standard consumption quotas in the enterprise resource planning unit using actual consumption data from the manufacturing execution unit, achieving dynamic self-optimization of quotas that fluctuate with batches; by verifying the curing validity period before scrap recycling through an integrated platform, invalid recycling of expired materials is avoided; and by using a plug-in adapter architecture design in the integrated platform, the coupling between systems and integration and maintenance costs are reduced. These three elements work together to solve the problems of static quotas, lack of timely data support for recycling decisions, and data silos between systems in composite material manufacturing, improving data consistency and cross-system collaboration efficiency.

[0055] Furthermore, in order to automatically synchronize the changed material sub-data to each unit when the curing shelf life, temperature and humidity thresholds, or manufacturing process of composite material products changes, and to avoid production misuse of old parameters or invalidation of scrap recycling rules due to data inconsistency, in one or more embodiments of this application, this application may also add a process for linking engineering changes, as follows: Specifically, the product lifecycle management unit initiates an engineering change request to the integration platform, which carries the material sub-data to be synchronized. The integration platform responds to the engineering change request by generating an engineering change notification, which is used to synchronize the material sub-data to the enterprise resource planning unit, manufacturing execution unit, and warehouse management unit through field mapping.

[0056] It should be noted that the engineering change request carries the material sub-data to be synchronized and the corresponding operation type (such as add, update, or delete). This application does not restrict the specific triggering method for engineering change requests; it can be set according to actual business needs, such as being manually initiated by a user in the product lifecycle management unit, or automatically triggered by the integration platform when a material master data version change is detected. This application also does not restrict the synchronization method for engineering change notifications; it can use message queue broadcasting, API interface-based sequential issuance, or database trigger-based synchronization, etc.

[0057] To achieve the locking of old version data and the smooth switching of new version data during engineering change processes, and to avoid data inconsistencies or production chaos during change execution, in one or more embodiments of this application, a version locking and switching strategy is added before the engineering change notification is synchronized, as follows: First, an engineering change request is initiated to the integration platform through the product lifecycle management unit. The engineering change request includes the change type, the material sub-data to be changed, and the change activation strategy. The change type includes, but is not limited to, modification of the curing expiration date, adjustment of temperature and humidity thresholds, addition or deletion of manufacturing processes, etc. The change activation strategy includes, but is not limited to, immediate activation, activation on a specified date, or activation after old inventory is exhausted.

[0058] Secondly, the integration platform responds to engineering change requests and performs version locking operations according to the change effectiveness policy. If the change is to take effect immediately, a locking instruction is issued to each unit to prohibit the continued use of the old version data and enable the new version data. If the change is to take effect on a specified date, the changed data is temporarily stored and the switch is automatically executed after the specified time point is reached. If the change is to take effect after the old inventory is exhausted, the usage of the old version materials in each unit is monitored and the switch is automatically executed after all materials are consumed.

[0059] Finally, by generating engineering change notifications through the integration platform, the changed material sub-data is converted into a format recognizable by each unit through field mapping, synchronized to the enterprise resource planning unit, manufacturing execution unit, and warehouse management unit, and a change log is recorded.

[0060] For example, in the production scenario of carbon fiber composite components, the Product Lifecycle Management (PLM) unit changes the curing validity period of a certain raw material from 30 days to 45 days and sets it to take effect immediately. The PLM unit initiates an engineering change request to the integration platform, carrying the raw material code CF-PRE-01, the new curing validity period of 45 days, and the effective policy of immediate effect. After responding to the engineering change request, the integration platform issues a lock command to the Enterprise Resource Planning (ERP) unit, Manufacturing Execution (M&A) unit, and Warehouse Management (WMM) unit, prohibiting the continued use of the old validity period (30 days). After each unit confirms the lock, the integration platform synchronizes the new curing validity period of 45 days to each unit through field mapping and updates the material master data version number.

[0061] Before initiating an engineering change request to the integration platform through the product lifecycle management unit, in order to proactively detect data inconsistencies between units and automatically trigger engineering changes for resynchronization when message loss, network failure, or system anomalies occur in the event-driven synchronization mechanism, thus ensuring data consistency across multiple systems, in one or more embodiments of this application, a timed fallback scan and proactive change triggering process may be added, as follows: First, by integrating the middle platform, for each unit in each enterprise resource planning unit, manufacturing execution unit, and warehouse management unit, according to the preset bottom-line scanning cycle, and based on the material master data in the product lifecycle management unit, the message queue logs and / or timestamps are cross-compared to determine the list of units to be synchronized.

[0062] Secondly, the list to be synchronized is sent to the product lifecycle management unit through the integration platform, so that the product lifecycle management unit can determine the material sub-data to be synchronized when the material master data changes or when the list to be synchronized is received.

[0063] Finally, the product lifecycle management unit initiates an engineering change request to the integration platform based on the material sub-data.

[0064] It should be noted that this application does not limit the specific size of the fallback scanning cycle, which can be set according to actual needs. For example, it can be set according to the business's sensitivity to data consistency; core data can be scanned once every 1 minute, and non-core data can be scanned once every 10 minutes. Message queue log comparison refers to the integration platform comparing the sent change event records in the message queue with the response receipt records returned by each unit, marking data entries in states such as sent, no response, timed out without confirmation, and lost message. Timestamp cross-comparison refers to the integration platform cross-comparing the last timestamp of the update of the same business object (such as material code, BOM version, fixed validity period) in each unit. If the time difference exceeds a preset threshold, it is determined that the data is inconsistent. This application does not limit the choice of synchronization method, which can be set according to the actual scenario requirements. For example, when all systems are online and stable, interfaces are working smoothly, and the MQ service is functioning correctly, event-driven real-time synchronization can be enabled only, while timed backup can be disabled. Event-driven synchronization can achieve second-level linkage without the need for backup, thus saving system resources. When a system is shut down for maintenance, an interface crashes, or the MQ message queue service fails, causing an interruption in the event-driven link, event-driven real-time synchronization should be paused, while timed backup can be used for periodic incremental synchronization to ensure eventual data consistency. During nighttime shifts or off-peak periods such as holidays, timed backup can be used only for periodic data consistency checks. When a new system is initially integrated into the integration platform or a project is in the initialization and deployment phase, basic material master data, historical BOMs, and process data need to be synchronized in batches. In this case, only timed backup can be enabled for incremental or initialization synchronization, without temporarily enabling event-driven synchronization. The system can be switched to dual-mechanism operation after the basic data synchronization is complete. Of course, to more comprehensively identify data inconsistency issues, this application can set up data asynchrony identification methods such as business end-to-end closed-loop status verification and abnormal alarm ledger linkage identification. The business end-to-end closed-loop status verification refers to verifying the continuity of upstream and downstream business statuses according to the business chain rules of R&D, planning, production, and warehousing. The anomaly alarm ledger linkage identification refers to reusing records of abnormal data, format mismatches, verification failures, and unauthorized calls intercepted by the data mapping and conversion engine, automatically categorizing unprocessed anomaly entries into the suspected synchronization pool. For example, when the enterprise resource planning unit has issued a manufacturing operation, but the manufacturing execution unit has no corresponding execution record, or the warehousing management unit has no completion and warehousing linkage record, the manufacturing operation is directly marked as suspected synchronization data at a link breakpoint and included in the synchronization list. When the data mapping and conversion engine intercepts a material master data synchronization request due to field type mismatch, the data is marked as having a format anomaly, and its material code is included in the synchronization list, awaiting user correction of the format before re-triggering synchronization.

[0065] After the Enterprise Resource Planning (ERP) unit responds to an order by querying the target manufacturing process and target bill of materials corresponding to the ordered product from the material master data, and then forwards them to the Manufacturing Execution (MEP) unit via the integration platform, in order to promptly detect and handle various abnormal events during the production process of the ordered product and avoid wider business interruptions or data errors due to the spread of abnormalities, in one or more embodiments of this application, an abnormal event detection and alarm handling process may be added, as follows: First, the platform detects abnormal events during the production process of ordered products. Abnormal events include at least one of the following: temperature and humidity exceeding the standard and locking, material expiration, failure to verify the expiration date of scrap materials, and failure to synchronize engineering changes.

[0066] Secondly, the integration platform determines the abnormal alarm level of abnormal events based on the preset mapping relationship between event types and alarm levels. Each alarm level corresponds to a preset notification method and response action, and the response action includes at least one of retry, locking, data isolation, and user permission freezing.

[0067] Finally, the integration platform pushes abnormal alarm information to users according to the notification method corresponding to the abnormal alarm level, and triggers the response action corresponding to the abnormal alarm level.

[0068] It should be noted that this application does not limit the specific mapping relationship between event types and alarm levels. These can be set according to actual business needs. For example, anomalies that may cause production interruptions or quality problems, such as temperature and humidity exceeding limits, material expiration, and engineering change synchronization failures, can be set to the emergency level. Anomalies that do not affect the main production process, such as failure to verify the expiration date of scrap materials, can be set to the important level. Temporary interface timeouts can be set to the normal level. This application also does not limit the specific form of notification; pop-ups, SMS, emails, or one or more combinations thereof can be used. Furthermore, this application allows setting timeout thresholds for different systems and business scenarios, such as PLM R&D changes, ERP work order issuance, MES production reporting, and WMS inventory management. For example, the R&D BOM synchronization threshold can be short, the production work order synchronization threshold can be medium, and the warehouse inventory data synchronization threshold can be appropriately relaxed. Of course, the threshold is not fixed and can be dynamically and adaptively adjusted: monitor the response latency of each interface, the frequency of business changes, the data concurrency and server load; increase the timeout threshold during peak business periods, when interface responses are slow or data is backlogged, to avoid false alarms of a large number of timeouts; decrease the timeout threshold during off-peak business periods and when the system is idle and running smoothly, to improve the real-time requirements of data synchronization.

[0069] Furthermore, to identify and intercept anomalies at the data source, this application incorporates dedicated data verification rules within the data mapping and transformation engine of the integrated platform. These rules are used for real-time verification of data flowing across systems, including but not limited to automatic early warning of near-expiration raw materials, interception of warehousing for exceeding temperature and humidity limits, verification of formula ratio tampering, and prohibition of production of expired raw materials. These verification rules are applied throughout the entire process, including material master data synchronization, material outbound, production execution, and scrap recycling, automatically intercepting illegal data and issuing cross-system alarms. Anomalies detected by the verification rules are sent to the aforementioned anomaly detection and alarm handling process, where they are pushed and automatically responded to according to preset alarm levels. To achieve classified management and automated handling of anomalies and reduce manual intervention costs, in one or more embodiments of this application, differentiated response actions are configured for different types of anomalies, as follows: First, for emergency-level anomalies such as process locking due to excessive temperature and humidity, or outbound interception due to expired materials, the integration platform automatically triggers real-time pop-ups, SMS, and email notifications to users and executes automatic response actions. For example, when temperature and humidity exceed the limits, relevant process permissions are locked; when materials expire, outbound instructions are intercepted and the batch of materials is frozen. Second, for critical-level anomalies such as failed expiration verification of scrap materials or inconsistent BOM versions, the integration platform triggers pop-ups and email notifications and executes automatic response actions. For example, when scrap material verification fails, the batch's recycling request is intercepted; when BOM versions are inconsistent, engineering change synchronization is triggered. Finally, for ordinary-level anomalies such as single interface call timeouts or non-core field synchronization delays, the integration platform only records the event in the backend ledger without proactively pushing alarms and executes automatic response actions. For example, if an interface times out, it automatically retryes three times; if it still fails, it is escalated to a critical-level anomaly.

[0070] In step S100, the standard interface template in the access adaptation layer is not fixed. The integrated information system supports automatic learning, autonomous iteration, and continuous optimization of the preset standard interface template from historical successful interface calls and data mapping interaction records, as follows: First, the interaction mapping records are retained. This application pre-builds a multi-system adaptation access module in the integration platform. After completing the interface calls, field mappings, format conversions, and protocol adaptations from PLM, ERP, MES, and WMS to the target system (such as PLM), this multi-system adaptation access module records all the essential information of this successful interaction, including but not limited to the interface field correspondence, format conversion rules, unit conversion logic, adaptation protocol type, business scenario tags (such as recipe synchronization, work order issuance, inventory write-back, engineering change), and synchronization result status.

[0071] Secondly, historical mapping data is categorized and classified. This application stores all historical success records and interface adaptation records into a pre-defined template knowledge base, and classifies and archives them according to unit type, business scenario, and unit version to form a learnable sample library.

[0072] Secondly, the rule engine uses clustering to extract commonalities. Utilizing the built-in rule validation and calculation capabilities of the data mapping and transformation engine, historical mapping records of units with the same scenario and type are clustered to extract high-frequency fixed field mapping relationships, optimal format conversion logic, preferred adaptation protocols, and common field matching priorities.

[0073] Then, the standard interface template is automatically iterated and optimized. Based on the common rules extracted by clustering, the original pre-set standard interface template is automatically optimized, such as adding high-frequency custom adaptation fields, solidifying the optimal format and conversion rules, eliminating inefficient adaptation protocols, simplifying redundant interface fields, and adjusting the automatic matching weight of fields, thereby completing the optimization of the standard interface template.

[0074] Next, gray-scale adaptation and closed-loop verification are implemented. The optimized standard interface template can be applied in a gray-scale manner to plug-and-play access systems of the same type, and the data synchronization success rate, the number of abnormal alarms, and the mapping error rate are monitored in real time. If the adaptation stability is improved and the number of abnormalities is reduced, the global standard interface template is officially updated and solidified; if adaptation anomalies occur, the old template is rolled back, and interaction records are re-collected and optimized.

[0075] Finally, template versions are globally synchronized. The optimized standard interface template is incorporated into version control and automatically synchronized to the plug-and-play adapters of all systems across the entire domain as the project changes, achieving unified iteration and synchronous updates of interface templates across multiple systems.

[0076] In this embodiment, based on actual business scenarios and system interaction history, this application iteratively optimizes the mapping accuracy and adaptation efficiency of pluggable adapters, reduces manual maintenance costs, and avoids integration interruptions caused by interface changes.

[0077] Furthermore, to ensure the security, traceability, and reliability of cross-system data interaction, this application also provides a permission security and end-to-end traceability mechanism in one or more embodiments, as follows: First, unified identity authentication and role-based hierarchical authorization are implemented. This application establishes a unified identity center within an integrated platform, and based on a pre-established identity association and role-permission mapping table for individual users across multiple systems (PLM, ERP, MES, WMS), it binds and maps a user's unique primary account to roles in each system. The permission logic is hierarchically authorized based on job position, matching the user's operable menus, data viewing scope, and API call permissions across different systems based on the identity association and role-permission mapping table.

[0078] Secondly, the entire process is traceable and the logs are tamper-proof. For each cross-system operation, data interaction, or engineering change during execution, the integration platform generates a globally unique and non-repeatable business tracking ID, spanning the entire PLM, ERP, MES, and WMS process, serving as the unique traceability identifier for the entire chain. It automatically captures the operation user, operation time, source system, target system, operation content, field values ​​before and after changes, interface call parameters, and permission information to form a structured raw log. A hash algorithm is used to calculate the hash of the complete log plaintext, generating a unique hash fingerprint for the log and embedding it in the log fields. Each log header carries the hash value of the previous log, forming a chained association; breaking any one of these links will cause the entire chain to fail. After log generation, the log is directly written to an isolated log database or file storage area that is not editable and only allows appending, disabling ordinary users' modification, deletion, and overwrite permissions, supporting only audit queries. During audit tracing, the log plaintext is recalculated for hashing. If the calculated hash matches the log's built-in hash and the chained hashes match, the log is considered complete and tamper-proof. If the calculated hash does not match the log's built-in hash or the chained hashes do not match, the log is considered tampered with or the data is abnormal, triggering an audit alarm.

[0079] Based on the aforementioned data processing method for composite material products, this application also provides a specific embodiment of an integrated information system.

[0080] like Figure 2 As shown, Figure 2 This is a schematic diagram of the structure of an integrated information system provided in an embodiment of this application. The integrated information system 200 includes an integration platform 201, and a product lifecycle management unit 202, an enterprise resource planning unit 203, a manufacturing execution unit 204, and a warehouse management unit 205 that are communicatively connected to the integration platform via plug-in adapters. The plug-in adapters are configured with standard interface templates for the corresponding units.

[0081] The product lifecycle management unit 202 is used to upload material master data to the integration platform. The material master data includes the material's solidification validity period, the product's manufacturing process, and the bill of materials. The enterprise resource planning unit 203 is used to respond to an order by querying the target manufacturing process and target bill of materials corresponding to the ordered product from the material master data and sending them to the integration platform; receiving the consumption deviation coefficient sent by the integration platform and updating the standard consumption quota of the materials in the target bill of materials according to the consumption deviation coefficient; and receiving the work report data sent by the integration platform and updating the inventory and cost of the ordered product according to the work report data. The manufacturing execution unit 204 is used to produce the ordered product according to the target manufacturing process and generate work report data, which includes the finished product quantity, material consumption weight, and scrap weight of the ordered product; and send the work report data to the integration platform. The warehouse management unit 205 is used to receive the weight of the scrap material sent by the integrated platform and to recycle the scrap material according to the weight. The integrated platform 201 is used to synchronize the material master data to each unit; forward the target manufacturing process and the target bill of materials to the manufacturing execution unit; receive the work report data and determine the theoretical consumption weight based on the finished product quantity and the standard consumption quota in the target bill of materials; send the ratio of the material consumption weight to the theoretical consumption weight as the consumption deviation coefficient to the enterprise resource planning unit; query the target solidification validity period of scrap materials from the material master data; if the current date has not exceeded the target solidification validity period, send the weight of the scrap materials to the warehouse management unit; and after recycling is completed, send the work report data to the enterprise resource planning unit.

[0082] Based on the aforementioned data processing method for composite material products, this application also provides a specific embodiment of a data processing apparatus for composite material products.

[0083] like Figure 3 As shown, Figure 3 This is a schematic diagram of a data processing device for composite material products provided in an embodiment of this application. The device 300 is applied to an integrated information system, which includes an integration platform and product lifecycle management units, enterprise resource planning units, manufacturing execution units, and warehouse management units that are communicatively connected to the integration platform via pluggable adapters. The pluggable adapters are configured with standard interface templates corresponding to the respective units. The device includes a data unification module 301, an order response module 302, a production detection module 303, a work reporting module 304, a recycling module 305, and an update module 306.

[0084] The data unification module 301 is used to synchronize the material master data of the product lifecycle management unit to each unit through the integration platform. The material master data includes the solidification validity period of the material, the manufacturing process of the product, and the bill of materials. Order response module 302 is used to respond to orders through the enterprise resource planning unit, query the target manufacturing process and target bill of materials corresponding to the order product from the material master data, and forward them to the manufacturing execution unit through the integration platform; The production inspection module 303 is used to produce the order product according to the target manufacturing process through the manufacturing execution unit and generate work report data, which includes the finished product quantity, material consumption weight and scrap weight of the order product; The work reporting module 304 is used to receive the work reporting data through the integrated platform, and determine the theoretical consumption weight based on the finished product quantity and the standard consumption quota in the target bill of materials; and send the ratio of the material consumption weight to the theoretical consumption weight as the consumption deviation coefficient to the enterprise resource planning unit. The recycling module 305 is used to query the target curing validity period of scrap materials from the material master data through the integrated platform; if the current date has not exceeded the target curing validity period, the weight of the scrap materials is sent to the warehouse management unit for recycling; after recycling is completed, the work report data is sent to the enterprise resource planning unit. The update module 306 is used to update the standard consumption quota of materials in the target bill of materials according to the consumption deviation coefficient through the enterprise resource planning unit, and to update the inventory and cost of the order products according to the work report data.

[0085] In one feasible implementation, the production detection module is specifically used to: obtain the current temperature and humidity thresholds of the manufacturing process from the material master data; acquire the current temperature and humidity through the manufacturing execution unit; produce the ordered product and generate work report data according to the target manufacturing process when the current temperature and humidity are not greater than the target temperature and humidity threshold corresponding to the target manufacturing process; and, when the current temperature and humidity are greater than the target temperature and humidity threshold, lock the start permission of the target manufacturing process and generate temperature and humidity warning information through the manufacturing execution unit, wherein the temperature and humidity warning information is used to prompt the user to adjust the current temperature and humidity.

[0086] In one feasible implementation, the production inspection module is specifically used to perform an expiration inspection on the target material based on the current date and the solidification expiration date of the target material required for the ordered product through the integrated platform; if the inspection passes, the integrated platform generates a material release instruction and sends it to the manufacturing execution unit; if the inspection fails, the integrated platform generates an expiration warning message for the target material and sends it to the user; the step of the manufacturing execution unit producing the ordered product according to the target manufacturing process includes: the manufacturing execution unit responding to the material release instruction and producing the ordered product according to the target manufacturing process.

[0087] In one feasible implementation, the recycling module is specifically used for the material master data, which also includes a material code for uniquely identifying each type of material; the integrated platform determines the weight of each specification of scrap material based on the weight of the scrap material and preset specification classification rules, and generates a material code for each specification of scrap material; the warehouse management unit allocates recycling storage locations based on the material code and weight of each specification of scrap material, and records the warehousing registration data after recycling the scrap material according to the recycling storage location; the integrated platform forwards the warehousing registration data and the work report data to the enterprise resource planning unit; and the enterprise resource planning unit updates the inventory and cost of the ordered products based on the warehousing registration data and the work report data.

[0088] In one feasible implementation, the data unification module is specifically used to initiate an engineering change request to the integration platform through the product lifecycle management unit. The engineering change request carries material sub-data to be synchronized. In response to the engineering change request, the integration platform generates an engineering change notification. The engineering change notification is used to synchronize the material sub-data to the enterprise resource planning unit, the manufacturing execution unit, and the warehouse management unit through field mapping.

[0089] In one feasible implementation, the data unification module is specifically used to, before initiating an engineering change request to the integration platform through the product lifecycle management unit, perform a message queue log and / or timestamp cross-comparison for each of the enterprise resource planning unit, manufacturing execution unit, and warehouse management unit according to a preset fallback scanning cycle, using the material master data in the product lifecycle management unit as a benchmark, to determine the list of units to be synchronized; send the list of units to be synchronized to the product lifecycle management unit through the integration platform; when the material master data changes or the list of units to be synchronized is received, determine the material sub-data to be synchronized; and initiate the engineering change request to the integration platform through the product lifecycle management unit based on the material sub-data.

[0090] In one feasible implementation, the order response module is specifically used to respond to an order through the enterprise resource planning unit, query the target manufacturing process and target temperature and humidity threshold corresponding to the ordered product from the material master data, and forward this to the manufacturing execution unit via the integration platform. Then, the integration platform detects abnormal events during the production process of the ordered product. These abnormal events include at least one of the following event types: temperature and humidity exceeding limits (locking), material expiration, failure to verify the expiration date of scrap materials, and failure to synchronize engineering changes. The integration platform determines the abnormal alarm level of each abnormal event based on a preset mapping relationship between event types and alarm levels. Each alarm level corresponds to a preset notification method and response action. The response action includes at least one of retry, locking, data isolation, and user permission freezing. The integration platform pushes abnormal alarm information to the user according to the notification method corresponding to the abnormal alarm level and triggers the response action corresponding to the abnormal alarm level.

[0091] Figure 4 A schematic diagram of the hardware structure of a data processing device for composite material products provided in an embodiment of this application is shown.

[0092] A data processing device for a composite material product may include a processor 401 and a memory 402 storing computer program instructions.

[0093] Specifically, the processor 401 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0094] Memory 402 may include mass storage for data or instructions. For example, and not limitingly, memory 402 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. In one embodiment, memory 402 may include removable or non-removable (or fixed) media, or memory 402 may be non-volatile solid-state memory. Memory 402 may be internal or external to the integrated gateway disaster recovery device.

[0095] In one embodiment, memory 402 may be read-only memory (ROM). In one embodiment, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0096] Memory 402 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the data processing method for a composite material product according to one aspect of this application.

[0097] The processor 401 reads and executes computer program instructions stored in the memory 402 to achieve... Figure 1 Data processing method for composite material products in the illustrated embodiment.

[0098] In one example, a data processing device for a composite material product may further include a communication interface 403 and a bus 404. Wherein, as Figure 4 As shown, the processor 401, memory 402, and communication interface 403 are connected through bus 404 and complete communication with each other.

[0099] The communication interface 403 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0100] Bus 404 includes hardware, software, or both, that couples components of a data processing device for a composite product together. For example, and not as a limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 404 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.

[0101] Furthermore, in conjunction with the data processing method for composite material products in the above embodiments, this application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the data processing methods for composite material products in the above embodiments.

[0102] This application also provides a computer program product, including a computer program that, when executed by a processor, implements a data processing method for any of the composite material products described in the above embodiments.

[0103] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0104] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0105] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0106] The aspects of this application have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by dedicated hardware performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0107] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A data processing method for composite material products, characterized in that, This is applied to an integrated information system, which includes an integration platform and product lifecycle management units, enterprise resource planning units, manufacturing execution units, and warehouse management units that are communicatively connected to the integration platform via pluggable adapters. The pluggable adapters are configured with standard interface templates for the corresponding units. The manufacturing execution unit is pre-configured with a data interface for a temperature and humidity sensor in the production environment, including: The integrated platform synchronizes the material master data of the product lifecycle management unit to each unit. The material master data includes the curing validity period of the material, the manufacturing process of the product, the temperature and humidity threshold of the manufacturing process, and the bill of materials. The enterprise resource planning unit responds to the order by querying the target manufacturing process corresponding to the order product, the target temperature and humidity threshold for each target manufacturing process, and the target bill of materials from the material master data, and then forwards it to the manufacturing execution unit through the integration platform. The manufacturing execution unit obtains the current temperature and humidity through the data interface; if the current temperature and humidity are not greater than the target temperature and humidity threshold, the unit produces the ordered product according to the target manufacturing process and generates work report data, which includes the finished product quantity, material consumption weight, and scrap weight of the ordered product; if the current temperature and humidity are greater than the target temperature and humidity threshold, the unit locks the start permission of the target manufacturing process and generates temperature and humidity warning information, which is used to prompt the user to adjust the current temperature and humidity. The integrated platform receives the work report data and determines the theoretical consumption weight based on the finished product quantity and the standard consumption quota in the target bill of materials; the ratio of the material consumption weight to the theoretical consumption weight is used as the consumption deviation coefficient and sent to the enterprise resource planning unit. The integrated platform queries the target curing validity period of scrap materials from the material master data; if the current date has not exceeded the target curing validity period, the weight of the scrap materials is sent to the warehouse management unit for recycling; after recycling is completed, the work report data is sent to the enterprise resource planning unit. The enterprise resource planning unit updates the standard consumption quotas of materials in the target bill of materials based on the consumption deviation coefficient, and updates the inventory and cost of the ordered products based on the work report data.

2. The method according to claim 1, characterized in that, Before producing the ordered product according to the target manufacturing process via the manufacturing execution unit, the method further includes: The integrated platform performs an expiration date check on the target material based on the current date and the curing expiration date of the target material required for the ordered product. Upon successful inspection, the integrated platform generates a material release instruction and sends it to the manufacturing execution unit. If the inspection fails, the integrated platform generates an expiration warning for the target material and sends it to the user. The process of producing the ordered product according to the target manufacturing process through the manufacturing execution unit includes: The manufacturing execution unit responds to the material release instruction and produces the ordered product according to the target manufacturing process.

3. The method according to claim 1, characterized in that, The material master data also includes a material code used to uniquely identify each type of material; Sending the weight of the scrap material to the warehouse management unit for recycling includes: The integrated platform determines the weight of each specification of scrap material based on the weight of the scrap material and the preset specification classification rules, and generates a material code for each specification of scrap material. The warehousing management unit allocates recycling locations based on the material code and weight of each specification of scrap material, and records the warehousing registration data after recycling the scrap material according to the recycling location. The step of updating the inventory and cost of the ordered products based on the reported work data includes: The integration platform forwards the warehouse registration data and the work reporting data to the enterprise resource planning unit. The enterprise resource planning unit updates the inventory and cost of the ordered products based on the inbound registration data and the work report data.

4. The method according to claim 1, characterized in that, The integrated platform synchronizes the material master data of the product lifecycle management unit to each unit, including: The product lifecycle management unit initiates an engineering change request to the integration platform, and the engineering change request carries the material sub-data to be synchronized. In response to the engineering change request, the integrated platform generates an engineering change notification. The engineering change notification is used to synchronize the material sub-data to the enterprise resource planning unit, the manufacturing execution unit, and the warehouse management unit through field mapping.

5. The method according to claim 4, characterized in that, Before initiating an engineering change request to the integration platform through the product lifecycle management unit, the method further includes: The integration platform performs cross-comparison of message queue logs and / or timestamps for each of the enterprise resource planning unit, manufacturing execution unit, and warehouse management unit according to a preset fallback scanning cycle, based on the material master data in the product lifecycle management unit, to determine the list of units to be synchronized. The integration platform sends the list to be synchronized to the product lifecycle management unit. The step of initiating an engineering change request to the integration platform through the product lifecycle management unit includes: When the material master data changes or the list to be synchronized is received, the product lifecycle management unit determines the material sub-data to be synchronized. The product lifecycle management unit initiates the engineering change request to the integration platform based on the material sub-data.

6. The method according to any one of claims 1 to 5, characterized in that, After responding to an order through the Enterprise Resource Planning (ERP) unit, querying the target manufacturing process and target bill of materials corresponding to the ordered product from the material master data, and forwarding them to the Manufacturing Execution (MEP) unit via the integration platform, the method further includes: The integrated platform detects abnormal events during the production process of the ordered products. These abnormal events include at least one of the following: temperature and humidity exceeding the standard and locking, material expiration, failure to verify the expiration date of scrap materials, and failure to synchronize engineering changes. The integrated platform determines the abnormal alarm level of the abnormal event based on the preset mapping relationship between event type and alarm level. Each alarm level corresponds to a preset notification method and response action, and the response action includes at least one of retry, locking, data isolation and user permission freezing. The integrated platform pushes abnormal alarm information to the user according to the notification method corresponding to the abnormal alarm level, and triggers the response action corresponding to the abnormal alarm level.

7. An integrated information system, characterized in that, The integrated information system includes an integration platform, and product lifecycle management unit, enterprise resource planning unit, manufacturing execution unit, and warehouse management unit that are communicatively connected to the integration platform via pluggable adapters. The pluggable adapters are configured with standard interface templates for the corresponding units. The manufacturing execution unit is pre-configured with a data interface for a temperature and humidity sensor in the production environment, including: The product lifecycle management unit is used to upload material master data to the integration platform. The material master data includes the material's curing validity period, the product's manufacturing process, the temperature and humidity thresholds of the manufacturing process, and the bill of materials. The enterprise resource planning unit is used to respond to orders by querying the target manufacturing process corresponding to the ordered product, the target temperature and humidity threshold for each target manufacturing process, and the target bill of materials from the material master data, and sending them to the integration platform; receiving the consumption deviation coefficient sent by the integration platform, and updating the standard consumption quota of materials in the target bill of materials according to the consumption deviation coefficient; receiving the work report data sent by the integration platform, and updating the inventory and cost of the ordered product according to the work report data; The manufacturing execution unit is configured to acquire the current temperature and humidity based on the data interface; if the current temperature and humidity are not greater than the target temperature and humidity threshold, produce the ordered product according to the target manufacturing process and generate work report data, the work report data including the finished product quantity, material consumption weight, and scrap weight of the ordered product; if the current temperature and humidity are greater than the target temperature and humidity threshold, lock the start permission of the target manufacturing process and generate temperature and humidity warning information, the temperature and humidity warning information being used to prompt the user to adjust the current temperature and humidity; and send the work report data to the integration platform. The warehouse management unit is used to receive the weight of the scrap materials sent by the integrated platform, and to recycle the scrap materials according to the weight of the scrap materials; The integrated platform is used to synchronize the material master data to each unit; forward the target manufacturing process and the target bill of materials to the manufacturing execution unit; receive the work report data and determine the theoretical consumption weight based on the finished product quantity and the standard consumption quota in the target bill of materials; send the ratio of the material consumption weight to the theoretical consumption weight as the consumption deviation coefficient to the enterprise resource planning unit; query the target solidification validity period of scrap materials from the material master data; if the current date has not exceeded the target solidification validity period, send the weight of the scrap materials to the warehouse management unit; and after recycling is completed, send the work report data to the enterprise resource planning unit.

8. An electronic device, characterized in that, The electronic device includes: a processor and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the data processing method for composite material products as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the data processing method for composite material products as described in any one of claims 1-6.

Images