Product element quality tracing method and device based on fault code and electronic equipment

Abstract

The invention provides a product component quality tracing method and device based on a fault code and electronic equipment, and relates to the technical field of information management.The scheme comprises the steps that an equipment fault code and equipment basic information in a fault work order are obtained, and when the fault rate corresponding to the equipment fault code reaches the target fault rate, the equipment fault code is determined to be the target fault rate; and determining a target element corresponding to the target fault code and the equipment basic information and a target batch corresponding to the target element based on a quality causal map, thereby realizing active positioning of the batch to which the product element having the fault belongs, and preventing the product element of the batch from being continuously used in the monitored equipment.

Description

Technical Field

[0001] This invention relates to the field of information management technology, and specifically to a method, apparatus, and electronic device for tracing the quality of components in a product based on fault codes. Background Technology

[0002] In manufacturing, product quality issues (especially those caused by fluctuations in supplier components or specific process parameters) are often discovered after the production and sales stages have commenced. Problems are only passively identified through after-sales repairs and customer complaints after a large number of potentially defective products have already entered the market, by which time they have often become part of a batch quality incident.

[0003] The supply chain system of modern manufacturing is becoming increasingly complex. The product lifecycle involves multiple stages, from suppliers, incoming material inspection, production, warehousing and logistics to after-sales service, generating massive amounts of heterogeneous data. These data sources include, but are not limited to: batch information provided by suppliers, incoming material inspection data, process parameters in the production process (MES system), the correspondence between product unique identifiers (SN) and batches, and after-sales repair work orders and quality inspection reports of returned parts. How to effectively utilize this multi-source, heterogeneous, and long-chain data to achieve end-to-end traceability and proactive early warning of product quality is a significant technical challenge currently facing the field of quality management in manufacturing.

[0004] The existing traceability of non-conforming products is mostly "positive" and based on the known non-conforming product number (SN). This traceability method is based on the company already knowing that a certain product is non-conforming. When the company is not clear whether a certain product is non-conforming, it is difficult to take the initiative to trace it. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a method, apparatus and electronic device for tracing the quality of product components based on fault codes, so as to realize the proactive tracing of non-conforming components in the monitored equipment based on the fault codes of the equipment faults, so as to determine the batch to which the non-conforming components belong.

[0006] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0007] A component quality traceability method for products based on fault codes includes:

[0008] Retrieve the equipment fault codes and basic equipment information from the fault work order;

[0009] The number of target fault codes is counted from the acquired equipment fault codes, wherein the target fault codes are fault codes whose fault cause is a component failure;

[0010] Based on the number of the target fault codes obtained from statistics, it is determined whether the failure rate corresponding to the target fault codes has reached the target failure rate;

[0011] When the target failure rate is reached, the target component corresponding to the target fault code and the basic equipment information is determined based on the quality cause-effect graph, as well as the target batch corresponding to the target component. The quality cause-effect graph includes at least the basic equipment information of each monitored device, the product batch of each component in the monitored device, and the target component corresponding to each fault code.

[0012] Optionally, in the above-mentioned component quality traceability method for products based on fault codes, the quality cause-effect graph also includes the process parameters corresponding to the components of each product batch, and the method further includes:

[0013] Based on the quality cause-effect graph, the process parameters corresponding to the target component are determined and denoted as defective process parameters.

[0014] Optionally, in the above-mentioned component quality traceability method for products based on fault codes, obtaining the equipment fault code and basic equipment information from the fault work order includes:

[0015] Obtain fault work orders for the monitored equipment in the target area, and obtain the equipment fault codes and basic equipment information from the fault work orders.

[0016] Optionally, in the above-mentioned component quality traceability method for products based on fault codes, after determining the target component corresponding to the target fault code and the basic equipment information, and the target batch corresponding to the target component based on the quality cause-effect graph, the method further includes:

[0017] Product quality testing is performed on the target components of the target batch;

[0018] When the test results indicate that the target component of the target batch is a non-conforming component, the basic equipment information of the target component of the target batch is determined based on the quality cause-effect graph. The basic equipment information includes at least the type of the monitored equipment and the production batch of the monitored equipment.

[0019] When the test results show that the target component of the target batch is a qualified component, the target component corresponding to the target fault code and the basic equipment information is re-determined based on the quality cause-effect graph, as well as the target batch corresponding to the target component, and product quality testing is performed on the target component of the re-determined target batch.

[0020] Optionally, in the above-mentioned component quality traceability method for products based on fault codes, re-determining the target component corresponding to the target fault code and the basic equipment information based on the quality cause-effect graph, and the target batch corresponding to the target component, includes:

[0021] Based on the priority order from high to low, the target components corresponding to the target fault codes and equipment basic information, as well as the target batches corresponding to the target components, are re-determined based on the quality cause-effect graph.

[0022] Optionally, in the above-mentioned component quality traceability method for products based on fault codes, when the test results show that the target component of the target batch is a non-conforming component, the method further includes: determining the monitored device based on the quality cause-effect graph, wherein the monitored device is a product that applies the target component of the target batch, and the quality cause-effect graph also includes the monitored device applied to each batch of target components.

[0023] Optionally, in the above-mentioned component quality traceability method for products based on fault codes, the quality cause-effect graph also includes the supplier corresponding to each batch of target components. When the test results indicate that the target components in the target batch are non-conforming components, it further includes:

[0024] The supplier of the target component for the target batch is determined based on the quality cause-effect graph.

[0025] Optionally, in the above-mentioned component quality traceability method for products based on fault codes, obtaining the equipment fault code and basic equipment information from the fault work order includes:

[0026] Based on a preset frequency, the device fault codes and basic device information in the fault work orders corresponding to each type of monitored device are sequentially traversed. The monitored devices include at least one of air conditioners, refrigerators, and washing machines.

[0027] A component quality traceability device for products based on fault codes, comprising:

[0028] The data extraction module is used to obtain equipment fault codes and basic equipment information from fault work orders;

[0029] The fault code statistics module is used to count target fault codes from the acquired fault codes;

[0030] An anomaly detection module is used to determine whether the failure rate corresponding to the target fault code has reached the target failure rate;

[0031] The fault tracing module is used to determine the target component corresponding to the target fault code and the basic equipment information, as well as the target batch corresponding to the target component, based on the quality cause-effect graph when the fault rate reaches the target fault rate. The quality cause-effect graph includes at least the basic equipment information of each monitored device, the product batch of each component in the monitored device, and the target component corresponding to each fault code.

[0032] An electronic device, comprising:

[0033] At least one processing device and a storage device connected to the processing device, wherein:

[0034] The storage device is used to store computer programs;

[0035] The processing device is used to execute the computer program so that the electronic device can implement any of the above-described fault code-based product component quality traceability methods.

[0036] Based on the above technical solution, the solution provided by the embodiments of the present invention extracts equipment fault codes and basic equipment information from fault work orders. When the failure rate corresponding to the equipment fault code reaches the target failure rate, the target component corresponding to the target fault code and the basic equipment information, as well as the target batch corresponding to the target component, are determined based on the quality cause-effect graph. Thus, the batch to which the faulty product component belongs is actively located to prevent the product components of that batch from continuing to be used in the equipment. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0038] Figure 1 A flowchart illustrating the component quality traceability method for products based on fault codes provided in this application embodiment;

[0039] Figure 2 This is a schematic diagram of the component quality traceability device for products based on fault codes, provided in an embodiment of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0041] This application proposes a component quality traceability method for products based on fault codes. By tracing faulty components in a product and the corresponding batch of the component through fault codes, non-conforming components can be identified, thereby ensuring the quality of the manufactured products.

[0042] Before implementing this method, a quality causal graph needs to be constructed in advance. This graph is a knowledge graph that can reflect the causal relationship of the entire chain from component suppliers to after-sales service. By dynamically detecting abnormal paths in the graph, early warning of batch quality risks can be achieved, and reverse location and handling strategies can be automatically generated.

[0043] When constructing the quality causal graph, multi-dimensional data collection is required through data sources, which include, but are not limited to:

[0044] Incoming material inspection data includes incoming material quality inspection records, supplier name, supplier batch number, inspection items, inspection results, and judgment thresholds.

[0045] Process parameter data: sourced from the Manufacturing Execution System (MES), including the product's process route, information on the equipment and tooling used in production, and the actual values ​​and timestamps of key process parameters (such as temperature, pressure, and torque).

[0046] SN-Batch Association Data: Records the correspondence between the product's unique identifier (SN) and the batch, type, production batch, and production time of the key components used.

[0047] After-sales work order data: sourced from customer relationship management (CRM) or after-sales service systems, including the region, time, product serial number, description of the fault phenomenon recorded by the user or repair personnel (such as "not cooling" or "loud noise"), standardized fault codes finally diagnosed by the system (such as "E6 - communication fault"), specific repair operations (such as replacing parts), and information on the replaced old parts, etc.

[0048] Repaired parts quality inspection data: Secondary quality inspection is carried out on failed parts returned from after-sales channels, and their failure modes and quality inspection results are recorded.

[0049] Data governance: Due to the diverse sources of data, rigorous governance is required to ensure data consistency and reliability. Key governance tasks include:

[0050] Unified entity and field mapping: Define globally unique entity identification rules. For example, associate "supplier batch number" with "component", then associate "component" with "product SN", and finally associate "product SN" with "after-sales work order" to form a primary key mapping rule that runs throughout the process. Here, the component is the element used in the monitored equipment.

[0051] Conflict resolution and data cleaning: Handling dirty data, such as batch merging / splitting, duplicate serial numbers, inconsistent time windows, etc., with preset processing rules (such as prioritizing timestamps, weighting based on data source credibility, etc.).

[0052] Data credibility score: Assign credibility scores to data from different sources and at different times. These scores are used for weighted calculations in subsequent analyses to improve the accuracy of the results.

[0053] By capturing and organizing data from the aforementioned data sources, we can construct the node data and edge (relationship) definitions for each component in the product within the quality causal graph.

[0054] The node data represents the core entities in the quality traceability process, and the node data may include:

[0055] Components: For example, "XX model capacitor".

[0056] Supplier: For example, "Company A".

[0057] Supplier batch: For example, "Company A - Batch 202310".

[0058] Component manufacturing process: For example, "reflow soldering process".

[0059] Process parameters: For example, "reflow soldering temperature -245℃".

[0060] Type: For example, "MP25024476".

[0061] Product SN: The product's unique serial number.

[0062] Fault codes: For example, "E6 - Communication failure".

[0063] Repair outcome: For example, "Replace the motherboard".

[0064] Regional / environmental factors: for example, "South China" or "high humidity environment".

[0065] An edge is defined to represent the semantic relationship between nodes, and it can have attributes (such as timestamps, counts, etc.) to record the context of the relationship. The main edge types include:

[0066] Supply (supplier → supplier batch) is used to characterize all batches of components supplied by a supplier;

[0067] Includes (supplier batch → component), used to identify which component corresponds to each supplier batch;

[0068] Assembled in (component → product SN), used to identify the SN number of the product to which each component is applied.

[0069] It belongs to (Product SN → Type), which is used to identify which types of applications the product is used on.

[0070] Experience (Product SN → Process) is used to characterize the production process of the product;

[0071] The parameters are (process → process parameters), which are used to characterize the process parameters under this process;

[0072] The "Fault Occurrence (Product SN → Fault Code)" field is used to identify which fault codes correspond to each product when a fault occurs.

[0073] The maintenance action is (fault code → maintenance result), which is used to characterize how the fault was resolved during the after-sales maintenance process.

[0074] Located in (Product SN → Region / Environmental Factors), it is used to characterize the region where the product SN is located and the environmental parameters of that region.

[0075] Semantic Constraints: To ensure the logical rigor of the graph, semantic constraints need to be incorporated during modeling. For example: Time Consistency: The timestamp of any production-related event (such as process parameter records) must be earlier than the time of the after-sales failure corresponding to the product's serial number. Topological Consistency: Ensure that the path from "supplier" to "after-sales failure" conforms to the assembly and flow relationships in the physical world.

[0076] Of course, when constructing the quality causal graph, users can reasonably adjust the data content contained in the quality causal graph according to their own needs.

[0077] Based on the aforementioned quality cause-effect graph, this application provides a component quality traceability method for products based on fault codes. (See [link to relevant documentation]). Figure 1 The method may include:

[0078] Step S101: Obtain the equipment fault code and basic equipment information from the fault work order in the after-sales system.

[0079] To better serve users, a Customer Relationship Management (CRM) or After-Sales Service (ESS) system needs to be built. This system can provide after-sales repair services. After the repair is completed, the repair personnel need to fill out a fault work order and upload it to the CRM or ESS system. The fault work order should at least record the fault code (e.g., E6 fault) of the monitored equipment being repaired, as well as the basic equipment information. The basic equipment information may include the equipment type (e.g., air conditioner, refrigerator, and the specific model of the air conditioner or refrigerator), serial number, etc. Based on the equipment type, the correspondence between the fault code and the faulty component can be determined. The serial number can be used to determine the relevant information of each component that makes up the monitored equipment. The relevant information may include data such as batch, type, production batch, and production time, and may also include the supplier of the component and the supplier batch.

[0080] Step S102: Count the number of target fault codes from the acquired device fault codes.

[0081] In this embodiment, the target fault code for which quantity statistics are required is one whose fault is caused by a component failure. When the target fault code appears, it indicates that a component failure has occurred in the monitored device.

[0082] After obtaining the fault work order, the target fault codes to be counted are identified from the fault codes filled in each fault work order. The number of occurrences of each target fault code is counted. Alternatively, each fault code can be traversed sequentially from a pre-configured fault code set, and the traversed fault codes can be used as target fault codes. The traversed target fault codes are then traced and analyzed. In this case, only the occurrence count of the target fault code needs to be counted.

[0083] Step S103: Based on the number of the target fault codes obtained from statistics, determine whether the failure rate corresponding to the target fault codes has reached the target failure rate.

[0084] In this scheme, the failure rate can refer to the failure rate of equipment sold in a certain region that has the corresponding failure code, or it can be the failure rate of all equipment sold that has the corresponding failure code. The failure rate can be calculated as the number of times the target failure code appears / the number of monitored equipment sold.

[0085] Once the failure rate corresponding to the target fault code is determined, it is compared with the target failure rate. If the failure rate of the monitored equipment exceeds the target failure rate, it indicates that there may be substandard components in the monitored equipment, requiring component quality traceability to prevent the continued use of substandard components. When the failure rate does not reach the target failure rate, the process continues to iterate through the next target fault code, checking whether the failure rate corresponding to that target fault code reaches the target failure rate, until all target fault codes of the monitored equipment have been traversed.

[0086] Step S104: When the target failure rate is reached, the target component corresponding to the target fault code and the basic equipment information, and the target batch (supplier batch) corresponding to the target component are determined based on the quality cause-effect graph. The quality cause-effect graph includes at least the basic equipment information of each monitored device, the product batch of each component in the monitored device, and the target component corresponding to each fault code.

[0087] When a device malfunctions, a fault code related to the malfunction will be displayed. This fault code indicates which component in the monitored device has failed. The component may include the parts mentioned earlier. When the failure rate of the target fault code reaches the target failure rate, the target component corresponding to the target malfunction is determined by the correspondence between the fault codes of the monitored device and the faulty components recorded in the quality cause-effect graph. The batch, type, production batch, and production time of each component used in this type of monitored device are determined by the relationship (product SN (SN of the monitored device) - batch association data) determined in the quality cause-effect graph. Based on this, the batch, type, production batch, and production time of the target component are determined. If the target component that failed is directly supplied by a supplier, the supplier and target batch (supplier batch) corresponding to the target component can be determined by the quality cause-effect graph. This target batch is the batch to which the target component that failed belongs.

[0088] In this solution, the fault codes and basic information of the equipment are extracted from the fault work orders corresponding to the monitored equipment. The number of target fault codes in the fault codes is counted. When the failure rate corresponding to the target fault code reaches the target failure rate, the target component corresponding to the target fault code and the basic information of the equipment, as well as the target batch corresponding to the target component, are determined based on the quality cause-effect graph. In this way, the batch to which the faulty component belongs is located, so as to prevent the product components of that batch from continuing to be used in the monitored equipment.

[0089] Furthermore, if the target component is manufactured by the company producing the monitored equipment, the target production batch, target production process, target process parameters, and raw material supplier batch can be located based on the quality cause-effect diagram and the equipment's basic information. This prevents components from that target production batch from continuing to be used in the monitored equipment. Simultaneously, production testing personnel can test the target component's production process, process parameters, and raw materials to determine whether the problem lies in the process or the raw materials, thereby identifying the root cause of the target component's non-conformity. When the faulty target component was obtained by the company producing the monitored equipment through assembling parts supplied by a supplier, it is necessary to further determine the target component's production batch, the suppliers and batches of each component used to assemble the target component, based on the quality cause-effect diagram. This allows staff to inspect the specific components causing the target component's non-conformity and their corresponding supplier batches, preventing the continued use of components from that supplier batch in product manufacturing.

[0090] In this embodiment, after the target batch of the target component is determined, the production process and process parameters of the target component supplied by the supplier for the target batch can also be obtained based on the quality causal graph. When it is determined that the quality of the target component is unqualified due to the production process and process parameters, the production process and process parameters are marked to prevent the subsequent use of target components produced based on the process and process parameters.

[0091] In this embodiment, to reduce data processing volume, detection can be performed only in typical regions with high equipment sales volume. These typical regions are designated as target regions. In this case, obtaining the equipment fault codes and basic equipment information from the fault work orders can include: obtaining the fault work orders of the monitored equipment in the target regions, and then obtaining the equipment fault codes and basic equipment information from these work orders. The target regions are pre-marked regions with the highest sales volume of the monitored equipment. Because the sales volume of monitored equipment in these regions is the largest, the statistical data obtained from them is more accurate and reliable, with smaller errors.

[0092] In this embodiment, there can be multiple target components that can cause the monitored device to display a target fault code. A specific problem with any of these target components will cause the monitored device to malfunction and display the target fault code. Therefore, after identifying the target component and its corresponding target batch, it is also necessary to determine whether the fault is caused by that target component. Thus, the solution further includes: performing product quality testing on the target components of the target batch. When the test results show that the target components of the target batch are unqualified, it indicates that the equipment fault is caused by that target component. Based on the quality cause-effect graph, the basic information of all monitored devices using the target components of the target batch is determined. The basic equipment information includes at least the type of monitored device and the production batch of the monitored device, so that the user can locate which devices use the target components of the target batch and resolve the equipment fault in a timely manner. When the test results show that the target components of the target batch are qualified, the target fault code (one fault code can correspond to multiple target components) is re-determined using the quality cause-effect graph (one fault code can correspond to multiple target components) and the basic equipment information to determine the target component and its corresponding target batch. Product quality testing is then performed on the re-determined target components of the target batch until the target component and target batch causing the equipment fault are identified. Once the target batch of the target component is identified, the process, process parameters, and raw materials of the target component in the target batch are tested to determine the root cause of the target component's non-conformity. Alternatively, the batch to which each component of the target component in the target batch belongs is determined, and the components in that batch are tested to determine which component caused the quality problem of the target component, as well as the process and process parameters of that component.

[0093] In this embodiment, the failure of multiple target components may cause the monitored device to experience the same fault. Therefore, the same fault code can correspond to multiple different components. To facilitate the rapid screening of the target component that has failed, this application can pre-prioritize these multiple components corresponding to the same fault code based on prior data. The higher the priority, the greater the probability that the component will cause the monitored device to experience the fault; the lower the priority, the smaller the probability that the component will cause the monitored device to experience the fault. The component with the highest priority is selected as the target component. At this time, re-determining the target fault code and the target component and the target batch corresponding to the target component based on the quality causal graph includes: re-determining the target component and the target batch corresponding to the target fault code and the device basic information based on the quality causal graph in descending order of priority. That is, among the multiple target components corresponding to the target fault code, the remaining target component with the highest priority is selected as the target component for this fault analysis, and the batch corresponding to the target component is recorded as the target batch.

[0094] Furthermore, after the target component test is completed, if all target components corresponding to the target fault code are found to be qualified components, then the cause of the equipment failure may be due to the environment of the area where the monitored equipment is located. In this case, the environmental parameters of the area where the monitored equipment is located can be obtained from the quality cause-effect graph. Under these environmental parameters, environmental tests can be performed on each target component corresponding to the target fault code to determine the target component that failed under these environmental parameters, as well as the relevant information such as the target batch, process and process parameters corresponding to the target component.

[0095] In this embodiment, after the test results indicate that the target component in the target batch is a non-conforming component, the method further includes: determining the monitored equipment based on the quality cause-effect graph. The monitored equipment is the product that uses the target component from the target batch, and the quality cause-effect graph also includes the monitored equipment used by each batch of target components. This allows identification of monitored equipment that has already used the target component, and then the potential failure risk of these monitored equipment can be resolved by replacing the components in these monitored equipment.

[0096] Furthermore, in this embodiment, when a target component is determined to be a non-conforming component, the supplier of the target component in the target batch can be determined based on the quality cause-effect graph. This allows for downgrading of the supplier and reducing the corresponding products supplied by that supplier.

[0097] In this embodiment, the method can be used to monitor the fault status of multiple monitored devices, that is, to obtain the device fault codes and basic device information in the fault work orders, including: sequentially traversing the device fault codes and basic device information in the fault work orders corresponding to various types of monitored devices based on a preset frequency. The monitored devices refer to the product equipment manufactured by the company, such as refrigerators and air conditioners.

[0098] This embodiment discloses a component quality traceability device for products based on fault codes. For the specific working content of each unit in the device, please refer to the content of the above method embodiment.

[0099] The component quality traceability device for products based on fault codes provided in the embodiments of the present invention will be described below. The component quality traceability device for products based on fault codes described below can be referred to in correspondence with the component quality traceability method for products based on fault codes described above.

[0100] See Figure 2 The product quality traceability device includes:

[0101] The data extraction module 10, which corresponds to step S101 in the above method, is used to obtain the equipment fault code and basic equipment information in the fault work order.

[0102] The fault code statistics module 20, which corresponds to step S102 in the above method, is used to count the number of target fault codes from the acquired equipment fault codes, wherein the fault corresponding to the target fault code is caused by a component failure.

[0103] The anomaly judgment module 30, which corresponds to step S103 in the above method, is used to determine whether the failure rate corresponding to the target fault code has reached the target failure rate based on the number of the target fault codes obtained by statistics.

[0104] The fault tracing module 40, which corresponds to step S104 in the above method, is used to determine the target component corresponding to the target fault code and the basic equipment information, and the target batch corresponding to the target component, based on the quality cause-effect graph when the fault rate reaches the target fault rate. The quality cause-effect graph includes at least the basic equipment information of each monitored device, the product batch of each component in the monitored device, and the target component corresponding to each fault code.

[0105] Corresponding to the above method, this application also provides an electronic device, which includes: at least one processing device and a storage device connected to the processing device, wherein: the storage device is used to store a computer program; the processing device is used to execute the computer program so that the electronic device can implement the component quality traceability method for products based on fault codes as described in any one of the above.

[0106] For ease of description, the above system is described by dividing it into various modules based on their functions. Of course, in implementing this invention, the functions of each module can be implemented in one or more software and / or hardware components.

[0107] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0108] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0109] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0110] It should also be noted that, in this document, relational terms such as "first" and "second" are used only 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 one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0111] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A component quality traceability method for products based on fault codes, characterized in that, include: Retrieve the equipment fault codes and basic equipment information from the fault work order; The number of target fault codes is counted from the acquired equipment fault codes, and the fault corresponding to the target fault code is caused by component failure; Based on the number of the target fault codes obtained from statistics, it is determined whether the failure rate corresponding to the target fault codes has reached the target failure rate; When the target failure rate is reached, the target component corresponding to the target fault code and the basic equipment information is determined based on the quality cause-effect graph, as well as the target batch corresponding to the target component. The quality cause-effect graph includes at least the basic equipment information of each monitored device, the product batch of each component in the monitored device, and the target component corresponding to each fault code.

2. The component quality traceability method for products based on fault codes according to claim 1, characterized in that, The quality cause-and-effect graph also includes the process parameters corresponding to the components of each product batch, and the method further includes: Based on the quality cause-effect graph, the process parameters corresponding to the target component are determined and denoted as defective process parameters.

3. The component quality traceability method for products based on fault codes according to claim 1, characterized in that, The process of obtaining the equipment fault code and basic equipment information from the fault work order includes: Obtain fault work orders for the monitored equipment in the target area, and obtain the equipment fault codes and basic equipment information from the fault work orders.

4. The component quality traceability method for products based on fault codes according to claim 1, characterized in that, After determining the target component corresponding to the target fault code and the basic equipment information based on the quality cause-effect graph, and the target batch corresponding to the target component, the method further includes: Product quality testing is performed on the target components of the target batch; When the test results indicate that the target component of the target batch is a non-conforming component, the basic equipment information of the target component of the target batch is determined based on the quality cause-effect graph. The basic equipment information includes at least the type of the monitored equipment and the production batch of the monitored equipment. When the test results show that the target component of the target batch is a qualified component, the target component corresponding to the target fault code and the basic equipment information is re-determined based on the quality cause-effect graph, as well as the target batch corresponding to the target component, and product quality testing is performed on the target component of the re-determined target batch.

5. The component quality traceability method for products based on fault codes according to claim 4, characterized in that, Based on the quality cause-effect graph, the target components corresponding to the target fault codes and basic equipment information are identified, and the target batches corresponding to the target components include: Based on the priority order from high to low, the target components corresponding to the target fault codes and equipment basic information, as well as the target batches corresponding to the target components, are re-determined based on the quality cause-effect graph.

6. The component quality traceability method for products based on fault codes according to claim 4, characterized in that, When the test results indicate that the target component of the target batch is a non-conforming component, the method further includes: determining the monitored equipment based on the quality cause-effect graph, wherein the monitored equipment is the product that applies the target component of the target batch, and the quality cause-effect graph also includes the monitored equipment applied to each batch of target components.

7. The component quality traceability method for products based on fault codes according to claim 4, characterized in that, The quality cause-and-effect graph also includes the suppliers corresponding to the target components in each batch. When the test results indicate that the target components in the target batch are non-conforming components, it also includes: The supplier of the target component for the target batch is determined based on the quality cause-effect graph.

8. The component quality traceability method for products based on fault codes according to claim 1, characterized in that, Retrieve the equipment fault codes and basic equipment information from the fault work order, including: Based on a preset frequency, the device fault codes and basic device information in the fault work orders corresponding to each type of monitored device are sequentially traversed. The monitored devices include at least one of air conditioners, refrigerators, and washing machines.

9. A component quality traceability device for products based on fault codes, characterized in that, include: The data extraction module is used to obtain equipment fault codes and basic equipment information from fault work orders; The fault code statistics module is used to count the number of target fault codes from the acquired equipment fault codes, wherein the target fault codes are fault codes whose fault causes are component failures. The anomaly detection module is used to determine whether the failure rate corresponding to the target fault code has reached the target failure rate based on the number of the target fault codes obtained by statistics. The fault tracing module is used to determine the target component corresponding to the target fault code and the basic equipment information, as well as the target batch corresponding to the target component, based on the quality cause-effect graph when the fault rate reaches the target fault rate. The quality cause-effect graph includes at least the basic equipment information of each monitored device, the product batch of each component in the monitored device, and the target component corresponding to each fault code.

10. An electronic device, characterized in that, include: At least one processing device and a storage device connected to the processing device, wherein: The storage device is used to store computer programs; The processing device is used to execute the computer program to enable the electronic device to implement the component quality traceability method for products based on fault codes as described in any one of claims 1 to 8.

Images