A quality problem analysis method and device based on node health degree pre-checking

Abstract

The application belongs to the technical field of household appliance production quality analysis, and provides a quality problem analysis method and device based on node health degree pre-inspection. The node health degree pre-inspection is performed on the key stage nodes by intervening in the project topology network before the project starts, and then the health degree of the project topology network is pre-inspected, so as to identify potential weak links before the project starts, repair the problem nodes in advance, effectively avoid the quality risks caused by process defects or lagging quality analysis, and improve the project operation stability and project pass rate.

Description

Technical Field

[0001] This application belongs to the field of home appliance production quality analysis technology, and in particular relates to a quality problem analysis method and device based on node health pre-inspection. Background Technology

[0002] In the manufacturing process of home appliances, products need to undergo processing on multiple production lines and pass through multiple quality inspection stages before leaving the factory. Each processing or inspection stage on these production lines operates independently. If a problem arises, operators can adjust the affected processing or inspection point to ensure the production line meets the quality requirements of the home appliances. However, in this isolated operation model, the operators' adjustments do not incorporate a process of tracing the underlying causes of the problem, making it difficult to resolve the root cause of the issue.

[0003] To improve the adaptability of production lines to various problems, a project topology network can be established based on the causal relationships between various nodes in the production line. In this way, when problems arise during the production of home appliances, the quality problem analysis system or device can trace and locate the problem based on the causal relationships provided by the project topology network.

[0004] However, this approach requires determining whether there are any abnormalities in the production of home appliances based on production data only after production has begun. Therefore, even if the project topology can be optimized to improve subsequent quality analysis processes by identifying the root cause of quality problems when production quality issues arise, the appliances with quality problems will still have to be scrapped, resulting in a significant waste of resources. Summary of the Invention

[0005] This application provides a method and apparatus for analyzing quality problems based on node health pre-inspection, in order to solve the problem that the lack of quality inspection of the project topology network before the start of the production stage of home appliances leads to a significant lag in the detection of production faults, which in turn wastes a lot of production resources.

[0006] In a first aspect, embodiments of this application provide a quality problem analysis method based on node health pre-detection, including:

[0007] Upon detecting a project change event, obtain the target project identifier; the target project identifier is used to characterize the project to be implemented.

[0008] The corresponding project topology network is determined based on the target project identifier; the project topology network includes multiple nodes; the nodes are used to represent the key business corresponding to the project to be implemented;

[0009] Obtain the node information and time decay coefficient corresponding to each node; where, the node information includes the node failure occurrence time and node failure level when the node is of different node types; the time decay coefficient and the node failure occurrence time are used to determine the time decay weight; the time decay coefficient is used as the base of the time decay weight, and the time decay factor is used as the exponent of the time decay weight, and the time decay factor is the difference between the system time and the node failure occurrence time.

[0010] The difference between the baseline value and the first accumulated value is used to obtain the network score corresponding to the project topology network; the first accumulated value is the sum of the products of the node failure level of each node and the corresponding time decay weight.

[0011] If the network score is greater than or equal to the target network score threshold, the project to be implemented is started, and the implementation process of the project to be implemented is monitored based on the project topology network.

[0012] If the network score is less than the target network score threshold, network adjustment information is generated; the network adjustment information is used to adjust the execution strategy of each node in the project topology network.

[0013] In some feasible embodiments, node types include source nodes and handle nodes; node faults include source node faults and handle node faults; node information includes the occurrence time and level of the first node fault when the node is a source node, and the occurrence time and level of the second node fault when the node is a handle node; the node information also includes the number of first node faults that cause source node faults when the node is a source node, and the number of second node faults that cause handle node faults when the node is a handle node.

[0014] Before calculating the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network, the following steps are also included:

[0015] Based on the difference between the system time and the time of each first node failure, determine the first time decay factor corresponding to each source node failure when the node is the source node; and based on the difference between the system time and the time of each second node failure, determine the second time decay factor corresponding to each handle node failure when the node is the handle node.

[0016] Based on the time decay coefficient and the first time decay factor, determine the first time decay weight corresponding to each source node failure when the node is the source node; and based on the time decay coefficient and the second time decay factor, determine the second time decay weight corresponding to each handle node failure when the node is the handle node; wherein, the base of the first time decay weight is the time decay coefficient, and the exponent of the first time decay weight is the first time decay factor; the base of the second time decay weight is the time decay coefficient, and the exponent of the second time decay weight is the second time decay factor.

[0017] The source risk score is obtained by summing the sub-source risk scores of each node when it is the source node; where each sub-source risk score is the sum of the products of the first node failure level and the first time decay weight when the node is the source node.

[0018] The sub-gatekeeping risk scores of each node when it is used as a gatekeeping point are summed to obtain the gatekeeping risk score; where each sub-gatekeeping risk score is the sum of the product of the second node failure level and the second time decay weight when the node is used as a gatekeeping point for each time a gatekeeping point failure occurs.

[0019] Calculate the sum of the source risk score and the gate control risk score to obtain the first cumulative value.

[0020] In some feasible embodiments, the sum of the source risk score and the gate control risk score is calculated to obtain a first accumulated value, specifically including:

[0021] The corresponding source risk score coefficient and gate control risk score coefficient are determined based on the target project identifier; the sum of the source risk score coefficient and the gate control risk score coefficient is 1.

[0022] Calculate the first product of the source risk score and the source risk score coefficient, and calculate the second product of the gate control risk score and the gate control risk score coefficient;

[0023] Calculate the sum of the first and second products to obtain the first accumulated value.

[0024] In some feasible embodiments, if the network score is greater than or equal to a target network score threshold, the project to be implemented is initiated, and after monitoring the implementation process of the project based on the project topology network, the process further includes:

[0025] When problems occur in the implementation process of a project to be implemented, identify the faulty node of the project to be implemented and the node type corresponding to the faulty node when the fault occurs.

[0026] If the faulty node corresponds to the source node when the fault occurs, the source risk score coefficient is increased by a preset step size, and the gate control risk score coefficient is decreased by a preset step size.

[0027] If the faulty node corresponds to a key node type when the fault occurs, the source risk score coefficient is reduced by a preset step size, and the control risk score coefficient is increased by a preset step size.

[0028] In some feasible embodiments, the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network, specifically including:

[0029] Calculate the sum of the sub-source risk score and the sub-gatekeeping risk score corresponding to the node, and determine the first score of the node;

[0030] Calculate the difference between the baseline value and the first score corresponding to the node to obtain the second score corresponding to the node;

[0031] If the second score corresponding to each node is greater than or equal to the score threshold, then the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network.

[0032] In some feasible embodiments, the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network, specifically including:

[0033] Get the number of first node failures that cause source node failures when each node is a source node, and the number of second node failures that cause handle node failures when each node is a handle node.

[0034] If the number of failures of the first node and the number of failures of the second node corresponding to a node are both less than the node failure threshold, then the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network.

[0035] In some feasible embodiments, after obtaining the target project identifier upon detecting a project change event, the method further includes:

[0036] Obtain the project level mapping table; the project level mapping table includes the mapping relationship between project identifiers and project levels;

[0037] Based on the project level mapping table, determine the target project level corresponding to the target project identifier;

[0038] Based on the correspondence between project level and network score threshold, determine the target network score threshold corresponding to the target project level.

[0039] Secondly, embodiments of this application also provide a quality problem analysis device based on node health pre-detection, including: a display component and a controller;

[0040] The controller is configured as follows:

[0041] Upon detecting a project change event, obtain the target project identifier; the target project identifier is used to characterize the project to be implemented.

[0042] The corresponding project topology network is determined based on the target project identifier; the project topology network includes multiple nodes; the nodes are used to represent the key business corresponding to the project to be implemented;

[0043] Obtain the node information and time decay coefficient corresponding to each node; where, the node information includes the node failure occurrence time and node failure level when the node is of different node types; the time decay coefficient and the node failure occurrence time are used to determine the time decay weight; the time decay coefficient is used as the base of the time decay weight, and the time decay factor is used as the exponent of the time decay weight, and the time decay factor is the difference between the system time and the node failure occurrence time.

[0044] The difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network; the first accumulated value is the sum of the products of the node fault level of each node and the corresponding time decay weight.

[0045] If the network score is greater than or equal to the target network score threshold, the project to be implemented is started, and the implementation process of the project to be implemented is monitored based on the project topology network.

[0046] If the network score is less than the target network score threshold, network adjustment information is generated, and the display component is controlled to display the network adjustment information; the network adjustment information is used to adjust the execution strategy of each node in the project topology network.

[0047] In some feasible embodiments, node types include source nodes and handle nodes; node faults include source node faults and handle node faults; node information includes the occurrence time and level of the first node fault when the node is a source node, and the occurrence time and level of the second node fault when the node is a handle node; the node information also includes the number of first node faults that cause source node faults when the node is a source node, and the number of second node faults that cause handle node faults when the node is a handle node.

[0048] Before the controller calculates the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network, it is also configured as follows:

[0049] Based on the difference between the system time and the time of each first node failure, determine the first time decay factor corresponding to each source node failure when the node is the source node; and based on the difference between the system time and the time of each second node failure, determine the second time decay factor corresponding to each handle node failure when the node is the handle node.

[0050] Based on the time decay coefficient and the first time decay factor, determine the first time decay weight corresponding to each source node failure when the node is the source node; and based on the time decay coefficient and the second time decay factor, determine the second time decay weight corresponding to each handle node failure when the node is the handle node; wherein, the base of the first time decay weight is the time decay coefficient, and the exponent of the first time decay weight is the first time decay factor; the base of the second time decay weight is the time decay coefficient, and the exponent of the second time decay weight is the second time decay factor.

[0051] The source risk score is obtained by summing the sub-source risk scores of each node when it is the source node; where each sub-source risk score is the sum of the products of the first node failure level and the first time decay weight when the node is the source node.

[0052] The sub-gatekeeping risk scores of each node when it is used as a gatekeeping point are summed to obtain the gatekeeping risk score; where each sub-gatekeeping risk score is the sum of the product of the second node failure level and the second time decay weight when the node is used as a gatekeeping point for each time a gatekeeping point failure occurs.

[0053] Calculate the sum of the source risk score and the gate control risk score to obtain the first cumulative value.

[0054] In some feasible embodiments, the controller calculates the sum of the source risk score and the gate control risk score to obtain a first accumulated value, which is specifically configured as follows:

[0055] The corresponding source risk score coefficient and gate control risk score coefficient are determined based on the target project identifier; the sum of the source risk score coefficient and the gate control risk score coefficient is 1.

[0056] Calculate the first product of the source risk score and the source risk score coefficient, and calculate the second product of the gate control risk score and the gate control risk score coefficient;

[0057] Calculate the sum of the first and second products to obtain the first accumulated value.

[0058] As can be seen from the above, the embodiments of this application provide a quality problem analysis method and apparatus based on node health pre-inspection. By intervening in the project topology network before the project starts, health pre-inspection is performed on nodes in key stages, thereby pre-inspecting the health of the project topology network. This allows for the identification of potential weak links before the project starts and the early repair of problematic nodes, which can effectively avoid quality risks caused by process defects or delayed quality analysis, and improve the stability of project operation and the project pass rate. Attached Figure Description

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

[0060] Figure 1 This application provides a method for analyzing quality problems based on node health pre-inspection in some embodiments;

[0061] Figure 2 A schematic diagram of node information provided for some embodiments of this application;

[0062] Figure 3 A flowchart illustrating the calculation of a first accumulated value for some embodiments of this application;

[0063] Figure 4 A flowchart illustrating the calculation of a second first accumulated value provided in some embodiments of this application;

[0064] Figure 5 A flowchart illustrating the adjustment of source risk score coefficients and gate control risk score coefficients provided for some embodiments of this application;

[0065] Figure 6 A flowchart of a first single-node health assessment method provided for some embodiments of this application;

[0066] Figure 7 A second single-node health assessment flowchart provided for some embodiments of this application;

[0067] Figure 8 A flowchart for obtaining a target network score threshold is provided for some embodiments of this application;

[0068] Figure 9 This is a schematic diagram illustrating the interaction between a display component and a controller provided in some embodiments of this application. Detailed Implementation

[0069] The embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described below do not represent all embodiments consistent with this application. They are merely examples of systems and methods consistent with some aspects of this application as detailed in the claims.

[0070] In the process of manufacturing home appliances, from the first trial production to stable mass production, it usually requires multiple stages of ramp-up production. That is, the production process is divided into multiple stages. Only after the production capacity and quality of each stage are stable can a complete production line be formed to produce new home appliances.

[0071] A complete production line comprises various production nodes, each corresponding to a key business process, such as requirement definition, chip selection, BOM (Bill of Material) release, and automated testing. To effectively monitor each node in the production line and to effectively repair any production failures, a project topology network can be constructed based on multiple production nodes across multiple production lines. This network records the causal relationships between the nodes, allowing for monitoring of the production process during home appliance manufacturing based on real-time production data. In the event of production failures, the cause can be traced based on the failure type and the project topology network.

[0072] In tracing the root causes of failures, root cause analysis can be used to identify the specific reasons for the problem. Each node in the project topology network can have two types: source nodes and handle nodes. Source nodes are those that cause the failure, representing the cause in the causal chain. Handle nodes are those nodes in the causal chain that should have detected, intercepted, or mitigated the failure but failed to do so. Thus, root cause analysis allows for tracing the root cause of production failures and modifying the rules and strategies of source and handle nodes, thereby optimizing the project topology network. The optimized project topology network can then be used in subsequent production processes to effectively monitor appliance production based on adjustments to node strategies and rules, thereby improving product yield.

[0073] However, the root cause analysis approach is a form of delayed feedback compared to the start-up of the production process. Although it can optimize the nodes in the project topology network, its lag makes it difficult to correct problems in a timely manner during the production process, thus leading to the waste of production resources in the current production process.

[0074] Furthermore, the lag inherent in this root cause analysis approach not only affects the normal operation of the production line where the fault occurs, but also further impacts the normal operation of multiple related production lines. Even if related production lines can operate normally after a fault has been identified but not immediately corrected, it remains difficult to produce home appliances that meet production requirements, thus wasting production resources and increasing the risk of equipment malfunctions.

[0075] Figure 1 This application provides a method for analyzing quality problems based on node health pre-inspection in some embodiments.

[0076] To solve the above problems, such as Figure 1 As shown, some embodiments of this application provide a quality problem analysis method based on node health pre-detection, including:

[0077] S100: Obtain the target project identifier when a project change event is detected.

[0078] The target project identifier is used to characterize the project to be implemented.

[0079] In some embodiments, terminal devices associated with a production line can receive various messages from each production line and determine the production progress based on the received messages. These terminal devices can be locally deployed. In subsequent embodiments, the terminal devices will be described as the implementing entities of a quality problem analysis method based on node health pre-inspection.

[0080] In addition, terminal devices can also communicate with mobile terminals based on various types of Internet networks. The mobile terminals can be projection devices, etc. In this way, operators who are not on-site can also remotely participate in the adjustment process of the project topology network through mobile terminals.

[0081] In some embodiments, a project change event indicates that a new production project has been received on the production line. Different projects have different production processes, and therefore, different projects have different project topologies. Thus, terminal devices can distinguish different projects using different project identifiers, and accurately invoke the corresponding project topology.

[0082] In some examples, the television production process includes key operations such as requirements definition, chip selection, BOM publication, and automated testing. The terminal device can detect corresponding project change events based on user-issued new project change instructions and control the production line to temporarily halt operation in order to perform the node health assessment process described in subsequent embodiments. That is, upon detecting a project change event, the node health assessment process is executed first, and then the production line is controlled to start.

[0083] S101: Determine the corresponding project topology network based on the target project identifier.

[0084] The project topology network includes multiple nodes, which represent the key business processes corresponding to the project to be implemented.

[0085] In some embodiments, the television production process includes key business processes such as demand definition, chip selection, BOM release, and automated testing. Then, in the project topology network construction phase, nodes in the project topology network can be formed based on key business processes such as demand definition, chip selection, BOM release, and automated testing, and edges in the project topology network can be formed based on the causal relationships between the nodes, thereby completing the construction of the project topology network.

[0086] It is understandable that the project topology network is pre-built, and there is a mapping relationship between the project topology network and the project identifier. The mapping relationship between the project topology network and the project identifier can be stored in a mapping table. After the terminal device determines the target project identifier, it can determine and call the project topology network corresponding to the target project identifier according to the mapping relationship stored in the mapping table.

[0087] The project's topology network includes multiple nodes, each corresponding to a key business function in the production process. Different nodes have different functions, and consequently, each node corresponds to different execution rules or strategies. During production, different nodes perform their functions according to their respective execution rules or strategies, thereby maintaining the normal operation of the production line.

[0088] In some embodiments, when the terminal device determines the project topology network from local or cloud storage, it can also simultaneously obtain the execution rules or strategies corresponding to each node in the project topology network, as well as the node information corresponding to each node. Furthermore, the terminal device can pre-evaluate the production process based on various node information before production begins, i.e., a health assessment of the project topology network. It can then promptly adjust the rules and strategies corresponding to the nodes, i.e., perform the first policy adjustment on the project topology network in the local or cloud storage to update the policy.

[0089] The local or cloud storage system updates the project topology network policy and sends the updated policy to the production line. Specifically, the updated policy can be sent to each node in the production line. At this point, the terminal device can send a project start message to the production line, and the production line officially begins production of the new project. The production line executes the production tasks corresponding to each node according to the updated policy. During production, each node in the production line can provide fault information in real time. The production line sends this fault information to the terminal device, which then performs a second policy adjustment on the local or cloud-based project topology network based on the fault information.

[0090] S102: Obtain the node information and time decay coefficient corresponding to each node.

[0091] The node information includes the occurrence time and level of each node failure, depending on the node type. The time decay coefficient and the node failure occurrence time are used to determine the time decay weight. The time decay coefficient serves as the base of the time decay weight, and the time decay factor serves as the exponent. The time decay factor is the difference between the system time and the node failure occurrence time.

[0092] In some embodiments, node information can be stored in a database. The storage format of node information in the database can be a multi-level storage method. The first level can be the node identifier of the node, the second level can be the node type of the node, and the third level can be the node failure time and node failure level when the node is of different node types.

[0093] In some embodiments, the node information of a node may further include the number of node failures that occur when the node is of different node types.

[0094] In some embodiments, the node failure level is used to characterize the importance of a node failure. The higher the node failure level, the greater the importance of the node failure, that is, the greater the impact on the node health and the greater the impact on the health of the project topology network.

[0095] In some embodiments, the time decay coefficient is a pre-set empirical value, which can be denoted as λ. Incorporating the time decay coefficient into the network score calculation process allows for the integration of the impact of historical failures on current production into quality problem analysis methods based on node health pre-detection.

[0096] In some embodiments, the time decay coefficient and the node failure occurrence time can be used to determine the time decay weight. The time decay coefficient can be used as the base of the time decay weight, the difference between the system time and the node failure occurrence time can be used as the time decay factor, and the time decay factor can be used as the exponent of the time decay weight. This adds a time dimension when calculating the network score, improving the effectiveness and adaptability of the network score.

[0097] In some examples, the time decay factor can be less than 1, such as 0.9, so that the impact of historical failures on the current production line will decrease as the difference between the system time and the time of the node failure increases.

[0098] It is understandable that the execution rules or strategies of each node in the production line are constantly being optimized. Therefore, most historical failures are unlikely to affect the operation of the current production line. Thus, by increasing the time decay coefficient, the impact of historical failures on the current production line can be effectively avoided, thereby improving the fit between the network score and the actual production situation and effectively assessing the health of the project's topology network.

[0099] S103: Calculate the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network.

[0100] The first accumulated value is the sum of the products of the node fault level and the corresponding time decay weight of each node.

[0101] In some embodiments, node failures include source node failures and node breakpoint failures.

[0102] In one embodiment, the baseline value is a network performance reference value set based on production experience. This baseline value is determined by comprehensively considering the normal operation of each node in the project topology network and the impact of potential minor faults on overall network performance. The closer the network score of the project topology network is to the baseline value, the higher the health level of the project topology network and the lower the probability of problems. Conversely, the lower the health level of the project topology network, the higher the probability of problems. In some examples, the baseline value can be 100 points.

[0103] In some embodiments, the node failure level is related to the node type at the time of failure. The node failure level may include a first node failure level and a second node failure level. The time decay weight includes a first time decay weight corresponding to the first node failure level and a second time decay weight corresponding to the second node failure level. Specifically, the first node failure level is the node failure level each time a source node failure occurs when the node is a source node; the second node failure level is the node failure level each time a handle node failure occurs when the node is a handle node. Thus, by calculating the cumulative value of the product of the first node failure level and the first time decay weight for each node, and calculating the cumulative value of the product of the second node failure level and the second time decay weight for each node, and summing these two cumulative values, a first cumulative value can be obtained.

[0104] S104: If the network score is greater than or equal to the target network score threshold, start the project to be implemented and monitor the implementation process of the project based on the project topology network.

[0105] In some embodiments, the target network score threshold is preset, whereby the target network score threshold characterizes a health assessment scale for the project topology network. A higher target network score threshold indicates a more stringent health assessment scale for the project topology network. The terminal device can determine the corresponding target network score threshold after identifying the target project identifier and compare the network score with the target network score threshold.

[0106] In some examples, if the terminal device calculates the network score of the project topology network to be 75 points and the target network score threshold is 70 points, then the terminal device determines that the current project topology network can be used for the production of the project to be implemented, and then sends the instruction to start production to the production lines related to each node in the project topology network.

[0107] S105: If the network score is less than the target network score threshold, generate network adjustment information.

[0108] Among them, network adjustment information is used to adjust the execution strategies of each node in the project topology network.

[0109] In some embodiments, network adjustment information is information generated by the terminal device based on the network score of the project topology network. It can be used to adjust the execution strategies of each node in the project topology network, thereby optimizing the project topology network before production begins. This is to avoid the production monitoring strategy corresponding to the project topology network lagging behind production failures during actual production, which would lead to a waste of production resources.

[0110] In this way, by adding a project topology network health assessment step before production starts, the terminal equipment effectively intercepts potential process breakpoints, moving the risk handling window forward to the project planning stage. This effectively avoids production risks and significantly reduces the probability of rework and downtime due to process defects. Furthermore, the terminal equipment retains its original delayed node repair strategy; even in the event of production problems, it can dynamically adjust node execution strategies based on real-time fault feedback, thus forming a closed-loop governance mechanism of "pre-assessment - in-process monitoring - post-optimization." This effectively solves the problem of significant delays in production fault detection due to the lack of quality inspection of the project topology network before the start of the home appliance production stage, leading to a waste of substantial production resources.

[0111] Figure 2 This is a schematic diagram of node information provided for some embodiments of this application.

[0112] like Figure 2 As shown, each node contains attributes for node type and node information. The node type includes source node and endpoint node. The node information includes the node failure time, the number of node failures, and the node failure level.

[0113] In some embodiments, the node information includes the occurrence time and level of a first node failure when the node acts as a source node, and the occurrence time and level of a second node failure when the node acts as a control node, each time a control node failure occurs. The node information also includes the number of first node failures when the node acts as a source node, and the number of second node failures when the node acts as a control node. The node information can be stored according to node type, allowing the terminal device to retrieve the corresponding node information based on the node type.

[0114] Figure 3 A flowchart illustrating the calculation of a first accumulated value provided in some embodiments of this application.

[0115] like Figure 3 As shown, before calculating the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network, the following steps are also included:

[0116] S300: Based on the difference between the system time and the time of each first node failure, determine the first time decay factor corresponding to each source node failure when the node is the source node; and based on the difference between the system time and the time of each second node failure, determine the second time decay factor corresponding to each handle node failure when the node is the handle node.

[0117] The first node failure occurrence time is the actual time when a node acts as the source node, and each time a source node failure occurs. The second node failure occurrence time is the actual time when a node acts as the control node, and each time a control node failure occurs. The system time is the current assessment initiation time. A first time attenuation factor is determined based on the difference between the first node failure occurrence time and the system time, and a second time attenuation factor is determined based on the difference between the second node failure occurrence time and the system time. The first and second time attenuation factors can be denoted as t1 and t2, respectively. The first and second time attenuation factors t1 and t2 can be normalized to units such as days, weeks, and months to ensure that failures more recent in time have a greater impact on health.

[0118] In some examples, the terminal device retrieves node information from the database and determines that the first node failure time of the "missing specification" source node is May 15th. Combined with the current system time of July 15th, and with the month as the normalization unit, the first time decay factor t1 is determined to be 2.

[0119] S301: Based on the time decay coefficient and the first time decay factor, determine the first time decay weight corresponding to each source node failure when the node is the source node; and based on the time decay coefficient and the second time decay factor, determine the second time decay weight corresponding to each handle node failure when the node is the handle node.

[0120] In this context, the base of the first time decay weight is the time decay coefficient, and the exponent of the first time decay weight is the first time decay factor. Similarly, the base of the second time decay weight is the time decay coefficient, and the exponent of the second time decay weight is the second time decay factor.

[0121] In some embodiments, the first time decay weight and the second time decay weight refer to the risk weights corresponding to nodes participating in the fault as different node types, respectively. The first time decay weight and the second time decay weight are denoted as follows: and The calculation formula is as follows: , ,in, The time decay coefficient, As the first time decay factor, This is the second time decay factor.

[0122] S302: Accumulate the sub-source risk scores of each node when it is a source node to obtain the source risk score.

[0123] The risk score for each sub-source is the product of the first node failure level and the first time decay weight when a node acts as a source node and causes a source node failure each time.

[0124] The source risk score represents the quantified risk accumulated by a node when it participates in a failure as a source node, denoted as [missing information]. The calculation formula is as follows:

[0125] ;

[0126] in, This refers to the severity score of the p-th node as the source node of the i-th failure. The severity score corresponds to the node failure level, and h is the number of source nodes, 1≤p≤h. The time decay coefficient, This refers to the first-time decay weight corresponding to the p-th source node as the source node failure in the i-th instance. This refers to the first time decay factor of the i-th source node failure of the p-th source node; Let Sa be the sub-source risk score of the p-th source node, and let i be the source risk score. Here, i represents the number of source node failures, 1 ≤ i ≤ n, and n represents the total number of times the p-th node, as a source node, causes source node failures.

[0127] S303: Accumulate the sub-gatekeeping risk scores of each node when it is used as a gatekeeping point to obtain the gatekeeping risk score.

[0128] In this context, the risk score for each sub-gatekeeper is the product of the second node fault level and the second time decay weight when the node is used as a gatekeeper node and each time a gatekeeper node failure occurs.

[0129] The risk score characterizing node is used as a quantitative value of the risk accumulated when a key point participates in a failure, denoted as Sk, and its calculation formula is as follows:

[0130] ;

[0131] in, This refers to the severity score of the q-th node as the j-th joint point failure score, where the severity score corresponds to the node failure level, and o is the number of joint points, 1≤q≤o; This refers to the second time decay weight corresponding to the q-th key point being used as the j-th key point failure. This refers to the second time decay factor of the j-th failure of the q-th joint. Let q be the sub-gatekeeping risk score for the q-th key point. To control the risk score. Where j represents the number of times the key node fails, 1≤j≤m, and m represents the total number of times the q-th node causes a key node failure.

[0132] S304: Calculate the sum of the source risk score and the gate control risk score to obtain the first cumulative value.

[0133] In some embodiments, the terminal device sums the source risk score and the gate control risk score to obtain a first accumulated value. Then, the terminal device subtracts the preset benchmark value from the first accumulated value to finally determine the network score of the project topology network.

[0134] In some examples, the formula for calculating the network score is:

[0135] ;

[0136] Where H is the network score. This is the first accumulated value. Terminal devices can assess the health of the project's network topology based on the network score, combined with the target network score threshold; 100 is a pre-set baseline value.

[0137] Understandably, in actual production, the proportions of source risk score and gate control risk score in the network score can be adjusted by further considering the actual impact of source risk and gate control risk on production, so as to more accurately reflect their differentiated contributions to process stability.

[0138] Figure 4 A flowchart illustrating the calculation of a second first accumulated value provided in some embodiments of this application.

[0139] like Figure 4 As shown, the sum of the source risk score and the gatekeeping risk score is calculated to obtain the first accumulated value, which specifically includes:

[0140] S400: Determine the corresponding source risk score coefficient and gate control risk score coefficient based on the target project identifier.

[0141] The sum of the source risk score coefficient and the gatekeeping risk score coefficient is 1.

[0142] The source risk score coefficient and the gate control risk score coefficient can be denoted as α and β, respectively. Both the source risk score coefficient and the gate control risk score coefficient can be preset fixed values. Terminal equipment can obtain different combinations of risk score coefficients depending on the project.

[0143] In some embodiments, different types of projects correspond to different risk characteristics. If the project to be implemented focuses on source control, the source risk score coefficient α can be set to a higher value, such as 0.7, and the gate control risk score coefficient β is 0.3.

[0144] In other embodiments, where the project to be implemented emphasizes gatekeeping effectiveness, the gatekeeping risk score coefficient β can be set to a higher value, such as 0.75, in which case the source risk score coefficient α is 0.25.

[0145] S401: Calculate the first product of the source risk score and the source risk score coefficient, and calculate the second product of the gate control risk score and the gate control risk score coefficient.

[0146] For example, the first product is ,in, As the source of risk score, The source risk score coefficient; the second product is ,in, To control risk scores, To control the risk score coefficient.

[0147] S402: Calculate the sum of the first product and the second product to obtain the first accumulated value.

[0148] For example, the first accumulated value = .

[0149] In some embodiments, the terminal device may use the following formula to calculate the network score of the project topology network:

[0150] ;

[0151] In this way, by introducing source risk score coefficients and gate control risk score coefficients, terminal devices can determine the health assessment focus of the project topology network based on the project characteristics of the project to be implemented, thereby dynamically calibrating the health assessment process.

[0152] Figure 5 The flowchart illustrates the adjustment process of the source risk score coefficient and the gate control risk score coefficient for some embodiments of this application.

[0153] like Figure 5 As shown, if the network score is greater than or equal to the target network score threshold, the project to be implemented is initiated. Based on the project topology network, the implementation process of the project to be implemented is monitored, and the process also includes:

[0154] S500: In the event of a problem in the implementation process of a project to be implemented, identify the faulty node of the project to be implemented and the node type corresponding to the faulty node when the fault occurs.

[0155] In some embodiments, if the terminal device's network score is greater than or equal to a target network score threshold, it can determine that the project to be implemented can be executed according to the existing rules in the project topology network, i.e., the project can be started. Each node runs autonomously according to its corresponding execution strategy. During operation, the terminal device can collect the operating data of each node in real time, automatically identify abnormal fluctuations, and locate faulty nodes. If a faulty node is located, the terminal device can trace the cause of the fault based on root cause analysis methods, thereby finding the node type corresponding to the fault.

[0156] Understandably, based on the root cause analysis method, the terminal equipment, combined with the project topology network, can first reverse-engineer the source node, and then, having identified the source node, forward-engineer the control node. The terminal equipment can dynamically fine-tune the source risk score coefficient or control risk score coefficient based on the finally determined cause of the failure, in order to correct the node according to the actual operating conditions.

[0157] S501: If the node type corresponding to the faulty node is the source node when the fault occurs, the source risk score coefficient is increased by a preset step size, and the gate control risk score coefficient is decreased by a preset step size.

[0158] In some embodiments, after the terminal device determines that the faulty node is the source node, it is determined that the cause of the production failure is that the vulnerability of the source node itself has not been effectively contained. At this time, it is necessary to strengthen the source control weight. Therefore, the source risk score coefficient α can be increased in a preset step size (such as 0.05), and the control risk score coefficient β is decreased in a synchronous and equal amount to ensure that α+β=1.

[0159] S502: If the node type corresponding to the faulty node is a key node when the fault occurs, the source risk score coefficient is reduced by a preset step size, and the control risk score coefficient is increased by a preset step size.

[0160] In other embodiments, after the terminal device determines that the fault node is the key point, it indicates that the problem has not been effectively intercepted. The root cause is that the gatekeeping mechanism has failed. At this time, it is necessary to increase the gatekeeping risk score coefficient β to strengthen the process interception capability. Therefore, the terminal device increases the gatekeeping risk score coefficient β by a preset step size (such as 0.05) and decreases the source risk score coefficient α by the same amount to ensure that α+β=1.

[0161] In this way, the terminal equipment can continuously calibrate the health assessment strategy before production starts based on real-time feedback, so that the dynamic ratio of the source risk score coefficient α and the control risk score coefficient β always matches the actual risk distribution of the current production line.

[0162] The health assessment strategy for the project topology network can be optimized through a delayed feedback loop. Terminal devices can further optimize the health assessment strategy to improve the accuracy of the analysis of the project topology network health.

[0163] Figure 6 A flowchart of a first single-node health assessment provided for some embodiments of this application.

[0164] like Figure 6 As shown, the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network, specifically including:

[0165] S600: Calculate the sum of the sub-source risk score and the sub-gatekeeping risk score corresponding to the node, and determine the first score of the node.

[0166] In some embodiments, after calculating the sub-source risk score and sub-gatekeeping risk score of any node, the terminal device can calculate the first score of that node. This value directly represents the comprehensive risk exposure level of that node in the dual dimensions of "problem generation" and "problem interception". The higher the value, the more dense the historical problems of that node and the weaker its prevention and control capabilities.

[0167] S601: Calculate the difference between the baseline value and the first score corresponding to the node to obtain the second score corresponding to the node.

[0168] As is understandable, each node has a corresponding node identifier, so the terminal device can calculate the second score, or node score, for each node one by one according to the node identifier. It then determines whether to proceed with subsequent network score calculations based on the health status of each node.

[0169] S602: If the second score corresponding to each node is greater than or equal to the score threshold, calculate the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network.

[0170] In some examples, the baseline value for a node is set to 100 points, the threshold value to 75 points, the risk score for a node's sub-source is 3 points, and the risk score for a node's sub-handle is 15 points. Therefore, the first score for a node is the sum of the sub-source risk score and the sub-handle risk score, which is 18 points. Correspondingly, the second score for a node is the difference between the baseline value and the first score, which is 82 points. Thus, if the second score is greater than the node's threshold value, it indicates that the node's health meets the standard, and the step of calculating the network score for the project topology network can continue. It should be noted that the step of calculating the network score for the project topology network only continues when the second score for all nodes in the project topology network is greater than the node's threshold value, to ensure that the implementation process of the project is not affected by the risk of individual nodes.

[0171] In some embodiments, the project topology network includes chip selection nodes and chip design nodes. In this project topology network, chip selection nodes and chip design nodes can act as both source nodes and control nodes; that is, chip selection nodes and chip design nodes can be specific examples of either source nodes or control nodes. The terminal device calculates a first score of 26 points for a certain chip selection node, and a second score of 74 points. Combined with a score threshold of 70 points for chip selection nodes, this indicates that the chip selection node's health meets the standard.

[0172] Furthermore, the terminal device calculates the first score of chip design node DES-001 as 18 points, and the second score as 82 points. Combined with the chip design node's score threshold of 75 points, this indicates that the chip design node's health also meets the standard. Then, with both nodes meeting the health standard, the terminal device continues to calculate the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network.

[0173] In this way, by screening node health layer by layer and comparing it with thresholds, the terminal device ensures that network-level aggregation calculation is only initiated when all critical nodes meet the baseline requirements, thereby preventing local risks from being diluted by global indicators. This effectively avoids the problem of local risks being masked by global averaging, leading to failures due to the neglect of local risks in actual production.

[0174] In some embodiments, if the second score of at least one node is less than a score threshold, a first node adjustment strategy is generated for the first target node; the first target node is the node whose second score is less than the score threshold, and the first node adjustment strategy is used to adjust the execution strategy of the first target node. In this case, it is not necessary to calculate the network score of the project topology network.

[0175] In some other embodiments, the project topology network includes requirement definition nodes and chip selection nodes. In this project topology network, requirement definition nodes and chip selection nodes can serve as both source nodes and handle nodes; that is, requirement definition nodes and chip selection nodes can be either specific examples of source nodes or specific examples of handle nodes.

[0176] The terminal device can compute the second score corresponding to the requirement definition node and the chip selection node in parallel, and compare it with the score threshold.

[0177] In some examples, the second score of the requirement definition node is 68, which is lower than its score threshold of 70. The terminal device then generates an adjustment strategy for the requirement definition node. After the adjustment strategy for the requirement definition node is completed, the terminal device recalculates the second score of the requirement definition node. Only if the second score is greater than or equal to the score threshold will the network score of the project topology network be calculated.

[0178] In some examples, after calculating the second score corresponding to the requirement definition node and the chip selection node, the terminal device can determine the corresponding heat map based on the second score and display the heat map to the operator through a display component such as a display or projection component, so that the operator can quickly determine the health status of each node in the project topology network.

[0179] Understandably, even when the second scores at both the demand definition node and the chip selection node meet the requirements, the terminal equipment can still receive real-time node adjustment commands from operators during the heatmap display phase. This allows operators to proactively adjust nodes that show potential fluctuations despite meeting the second scores, thus preventing risk accumulation. Furthermore, by incorporating operators' experience across various project scenarios, the terminal equipment can improve production stability and ultimately increase the yield rate of home appliance products.

[0180] In this way, the pre-inspection of the project topology network by the terminal equipment before the project starts is divided into two phases. The first phase focuses on node-level health screening, identifying and addressing low-scoring nodes in a closed-loop manner. The second phase initiates a network-level aggregation assessment after all nodes meet the standards. Single-node health assessment can effectively prevent network-level aggregation assessment from masking local vulnerabilities under the appearance of overall stability, while network-level aggregation assessment can identify cross-node coupling risks from a global perspective. Therefore, the terminal equipment can perform dual verification of the project topology network before the project starts, ensuring that there are neither single points of vulnerability nor systemic coupling risks, thereby improving the stability and reliability of project execution.

[0181] In some implementations, embodiments of this application can also determine whether a node is healthy based on whether the number of node failures exceeds a node failure threshold.

[0182] Figure 7 A second single-node health assessment flowchart is provided for some embodiments of this application.

[0183] like Figure 7 As shown, the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network, specifically including:

[0184] S700: Obtain the number of first node failures that cause source node failures when each node is a source node, and the number of second node failures that cause handle node failures when each node is a handle node.

[0185] S701: If the number of failures of the first node and the number of failures of the second node corresponding to the node are both less than the node failure number threshold, then calculate the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network.

[0186] In some embodiments, the terminal device analyzes the health of nodes based on the number of node failures for each node type. The threshold for the number of node failures can differ for different node types. For example, the threshold for source nodes could be set to 3 failures per quarter, while the threshold for key nodes could be set to 1 failure per quarter, reflecting the varying sensitivities to stability at different stages.

[0187] In some embodiments, the project topology network includes requirement definition nodes and verification test nodes. In this project topology network, requirement definition nodes and verification test nodes can act as either source nodes or handle nodes; that is, they can be specific examples of either source nodes or handle nodes. When the requirement definition node is a source node and the verification test node is a handle node, if the terminal device obtains a node failure count of 2 times / quarter for the requirement definition node, which is below the threshold of 3 times / quarter, then the node is determined to be currently healthy. Simultaneously, if the verification test node's failure count is 0 times / quarter, which is also below the threshold of 1 time / quarter, then the node is determined to be healthy. Furthermore, the terminal device determines that all nodes are currently healthy and can proceed to the network score calculation process for the project topology network.

[0188] This approach saves computational resources compared to determining a node's health based on its score, making it particularly suitable for resource-constrained edge devices or high-frequency iteration development scenarios.

[0189] In some embodiments, if the number of failures of at least one of the first node failure count and the second node failure count corresponding to a node is greater than or equal to a node failure count threshold, a second node adjustment strategy for the second target node is generated; the second target node is a node whose number of failures of at least one of the first node failure count and the second node failure count is greater than or equal to a node failure count threshold, and the second node adjustment strategy is used to adjust the execution strategy of the second target node.

[0190] In some embodiments, if the terminal device detects that the number of times the verification test node fails reaches 2 times per quarter, exceeding the threshold of 1 time per quarter, an adjustment strategy for that node will be generated.

[0191] In this way, the terminal device can immediately trigger local optimization instead of recalculating the entire network if any node is unhealthy. This not only ensures multi-stage verification of the project's topology network, but also significantly improves response efficiency.

[0192] It should be noted that different network score thresholds and node score thresholds (i.e., the score thresholds mentioned earlier) can be preset for different project levels. For example, if project A is a key project, the target network score threshold can be set higher, such as 85 points, to fully ensure the delivery quality of project A. On the other hand, if project B is a general project, the target network score threshold can be set lower, such as 70 points, to balance quality monitoring and resource consumption.

[0193] Figure 8 This is a flowchart illustrating the process of obtaining a network score threshold for some embodiments of this application.

[0194] like Figure 8 As shown, after obtaining the target project identifier upon detecting a project change event, the process also includes:

[0195] S800: Get the project level mapping table.

[0196] The project level mapping table includes the mapping relationship between project identifiers and project levels.

[0197] S801: Determine the target project level corresponding to the target project identifier based on the project level mapping table.

[0198] S802: Determine the target network score threshold corresponding to the target project level based on the correspondence between each project level and the network score threshold.

[0199] In some embodiments, the project level mapping table includes a mapping relationship between project identifiers and project levels. Project levels can be classified according to the importance of quality control or the production implementation stage of the home appliance production project. After obtaining the target project identifier used to characterize the project to be implemented, the terminal device can look up the target project identifier in the project level mapping table and determine the project level that has a mapping relationship with the target project identifier as the target project level.

[0200] There is a pre-set correspondence between project level and network score threshold. Based on this, after determining the target project level, the target network score threshold corresponding to the target project level can be dynamically matched.

[0201] In some examples, if the target project identifier “PRJ-2026-001” corresponds to the target project level “key project level” in the project level mapping table, then the target network score threshold of 85 points will be automatically matched and enabled.

[0202] In some other examples, if the target project identifier “PRJ-2026-002” corresponds to the target project level “Exploratory Project Level” in the project level mapping table, then the network score threshold of 65 points will be automatically matched and enabled.

[0203] This dynamic target network threshold matching mechanism not only adapts to project differences but also fits well with scenarios involving the parallel processing of multiple projects. Understandably, the terminal device can simultaneously monitor multiple projects to be implemented, and then, based on the target project identifier of each project, match its unique target network score threshold in real time, and independently assess the health of the project's topology network.

[0204] During the health assessment of the project's topology network, terminal equipment can combine the total failure frequency of all nodes to determine the failure trend, and then combine the failure trend to determine whether historical failures show accelerated deterioration or periodic recurrence characteristics, so as to adjust the time decay coefficient.

[0205] In some embodiments, the node information of each node in the project topology network has a corresponding recording period. The recording period includes a first period and a second period. In this embodiment, the current statistical period corresponding to the system time of the project to be implemented is the first period, and the historical statistical period corresponding to the current statistical period (e.g., its previous statistical period) is the second period. The statistical lengths of the first and second periods are the same. In practical applications, the historical statistical period can also be a third period, a fourth period, etc., with a longer time interval, to form trend analysis based on multiple periods, so as to improve the adjustment law of the time decay coefficient.

[0206] In some embodiments, the failure of a node as a source node has a greater impact on the health of the project topology network. Therefore, the failure trend can be determined by combining the failure frequency corresponding to the node as a source node, and then the time decay coefficient and the target network score threshold can be adjusted according to the failure trend. Furthermore, in this embodiment, the target source node (e.g., the requirement definition node) with the greatest impact on the project topology network can be selected as the node for measuring the failure trend.

[0207] In some embodiments, the terminal device pre-divides the recording period, such as a first period and a second period, with each period having the same statistical length. The terminal device acquires the number of third node failures occurring in the first period when the node is the source node, and the number of fourth node failures occurring in the second period when the node is the source node, and calculates the ratio of the number of third node failures to that in the first period to determine a first occurrence frequency. It also calculates the ratio of the number of fourth node failures to that in the second period to determine a second occurrence frequency.

[0208] In some examples, both the first and second periods can be set to 10 days. The terminal device can obtain the number of node failures generated in the first and second periods, and then calculate the first and second occurrence frequencies of the target source node (the requirement-defined node). By comparing the first and second occurrence frequencies, the terminal device can determine the magnitude of frequency changes and thus determine the failure trend.

[0209] For example, the frequency change amplitude = (first occurrence frequency - second occurrence frequency) ÷ second occurrence frequency × 100%.

[0210] In some examples, when the frequency change exceeds 30%, the terminal device determines that the failure trend of the demand-defined node is a worsening trend. Alternatively, if the terminal device determines that the node's failure trend is a worsening trend when the first occurrence frequency is greater than or equal to the second occurrence frequency, the terminal device can reduce the time decay coefficient from 0.95 to 0.85 to enhance the weight of recent failure records, making the health score more sensitive to the current risk.

[0211] In other examples, the adjustment step size of the time decay coefficient is positively correlated with the frequency change amplitude. For example, for every 10% increase in the frequency change amplitude, the step size is increased by 0.02 to ensure that the adjustment accuracy matches the trend strength. For instance, when the frequency change amplitude of the terminal device increases by 40%, the step size is increased to 0.08, and the coefficient is directly adjusted from 0.95 to 0.87.

[0212] In other examples, the frequency change is -30%, and the terminal device determines that the failure trend of the demand definition node is an improving trend. Alternatively, if the first occurrence frequency is less than the second occurrence frequency, the terminal device determines that the failure trend of the demand definition node is an improving trend and increases the time decay factor from 0.9 to 0.95 to enhance the weight of historical data.

[0213] In this way, the terminal device can adjust the time decay coefficient by combining the failure trend of nodes in the project topology network when they are source nodes, so that the network score of the project topology network can more robustly reflect long-term stability.

[0214] In some embodiments, the terminal device may adjust the target network score threshold based on the failure occurrence trend when a node is the source node. An increasing failure trend when a node is the source node indicates a need for a more stringent health assessment of the project topology network in the near future. A decreasing failure trend when a node is the source node indicates that the health assessment of the project topology network can be appropriately relaxed to balance the health assessment scale of the project topology network with the production quality of the project to be implemented.

[0215] In some embodiments, when the first occurrence frequency is greater than or equal to the second occurrence frequency, the terminal device raises the target network score threshold from 80 to 85 to tighten the warning triggering conditions. In this way, in scenarios where faults occur frequently and node health deteriorates, the sensitivity of risk identification is enhanced by increasing the target network score threshold.

[0216] In other embodiments, when the first occurrence frequency is less than the second occurrence frequency, the terminal device lowers the target network score threshold from 80 points to 75 points to reduce the warning threshold. In this way, when the number of faults decreases and the health of nodes shows an improving trend, the warning conditions are relaxed, the warning sensitivity and operational efficiency are balanced, and excessive warnings are avoided from interfering with the normal process.

[0217] This dynamic adjustment mechanism for the target network score threshold can flexibly adjust the threshold by combining fault occurrence trends with project stage characteristics, thereby enabling more accurate pre-inspection of the project topology network to match the risk prevention and control needs of each stage. This application also provides a quality problem analysis device based on node health pre-inspection.

[0218] The device includes a controller and a display component. The display component can be a projection component, capable of synchronously projecting heatmaps of each node in the process topology network to visually present the health distribution through heatmaps of different colors. It can also synchronously project network adjustment strategies, node adjustment strategies, and corresponding implementation suggestions, such as "reducing the approval process between nodes A and B" or "enabling a dual-person review mechanism for node C."

[0219] In this way, based on the interactive capabilities provided by the device, operators can clearly know the current health status of each node, the cause of the abnormality, and the recommended intervention path, so that operators can implement intervention measures in a timely manner.

[0220] The controller is configured as follows:

[0221] Upon detecting a project change event, obtain the target project identifier; the target project identifier is used to characterize the project to be implemented.

[0222] The corresponding project topology network is determined based on the target project identifier; the project topology network includes multiple nodes; the nodes are used to represent the key business corresponding to the project to be implemented;

[0223] Obtain the node information and time decay coefficient corresponding to each node; where, the node information includes the node failure occurrence time and node failure level for each node failure when the node is of different node types; the time decay coefficient and node failure occurrence time are used to determine the time decay weight; the time decay coefficient is the base of the time decay weight, and the time decay factor is the exponent of the time decay weight, which is the difference between the system time and the node failure occurrence time.

[0224] The difference between the baseline value and the first accumulated value is used to obtain the network score corresponding to the project topology network; the first accumulated value is the sum of the products of the node failure level of each node and the corresponding time decay weight.

[0225] If the network score is greater than or equal to the target network score threshold, the project to be implemented is started, and the implementation process of the project to be implemented is monitored based on the project topology network.

[0226] If the network score is less than the target network score threshold, network adjustment information is generated; the network adjustment information is used to adjust the execution strategy of each node in the project topology network.

[0227] In some embodiments, the node type includes a source node and a handle node; node faults include source node faults and handle node faults; node information includes the occurrence time and level of a first node fault when the node is a source node, and the occurrence time and level of a second node fault when the node is a handle node; the node information also includes the number of first node faults that cause source node faults when the node is a source node, and the number of second node faults that cause handle node faults when the node is a handle node.

[0228] Before the controller calculates the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network, it is also configured as follows:

[0229] Based on the difference between the system time and the time of each first node failure, determine the first time decay factor corresponding to each source node failure when the node is the source node; and based on the difference between the system time and the time of each second node failure, determine the second time decay factor corresponding to each handle node failure when the node is the handle node.

[0230] Based on the time decay coefficient and the first time decay factor, determine the first time decay weight corresponding to each source node failure when the node is the source node; and based on the time decay coefficient and the second time decay factor, determine the second time decay weight corresponding to each handle node failure when the node is the handle node; wherein, the base of the first time decay weight is the time decay coefficient, and the exponent of the first time decay weight is the first time decay factor; the base of the second time decay weight is the time decay coefficient, and the exponent of the second time decay weight is the second time decay factor.

[0231] The source risk score is obtained by summing the sub-source risk scores of each node when it is the source node; where each sub-source risk score is the sum of the products of the first node failure level and the first time decay weight when the node is the source node.

[0232] The sub-gatekeeping risk scores of each node when it is used as a gatekeeping point are summed to obtain the gatekeeping risk score; where each sub-gatekeeping risk score is the sum of the product of the second node failure level and the second time decay weight when the node is used as a gatekeeping point for each time a gatekeeping point failure occurs.

[0233] Calculate the sum of the source risk score and the gate control risk score to obtain the first cumulative value.

[0234] In some embodiments, the controller calculates the sum of the source risk score and the gate control risk score to obtain a first accumulated value, which is specifically configured as follows:

[0235] The corresponding source risk score coefficient and gate control risk score coefficient are determined based on the target project identifier; the sum of the source risk score coefficient and the gate control risk score coefficient is 1.

[0236] Calculate the first product of the source risk score and the source risk score coefficient, and calculate the second product of the gate control risk score and the gate control risk score coefficient;

[0237] Calculate the sum of the first and second products to obtain the first accumulated value.

[0238] Figure 9 This is a schematic diagram illustrating the interaction between a display component and a controller provided in some embodiments of this application.

[0239] like Figure 9 As shown, in some embodiments, a manufacturing execution system, a bill of materials system, and an information management system operate on the production line. The controller can receive various types of information from the production line and detects a project change event when it receives a notification message that a new project is about to enter production. After detecting the project change event, the controller can perform a pre-inspection of the project topology network corresponding to the project to be implemented, either in the cloud or locally. During the pre-inspection process, the controller can control the display component to display the node health status. The node health status is specifically presented as a node score bar chart. The node score bar chart is used to display the second score of each node in the project topology network calculated during the pre-inspection, so as to show the operator the health status of each node in the current project topology network through the display.

[0240] Users observe the second scores of nodes A, B, C, D, E, F, and G through the display component and compare them with the node score thresholds. If the user determines that node B clearly does not meet the requirements, they can interact with the display component / controller to instruct the controller to modify the execution strategy for node B. This optimizes the corresponding project topology network before the project is put into production, enabling predictive project topology network maintenance and improving the health of the project topology network. Only after adjusting the execution strategy for node B does the controller send a start message to each system in the production line, enabling each production node in the production line to execute critical business operations based on the modified project topology network.

[0241] In some examples, when the controller receives an instruction from the user to adjust the execution strategy of node B, it can control the display component to display the specific adjustment strategy for the user to choose from, or display prompts to inform the user of what aspects have been adjusted.

[0242] The display component can be either a monitor or a projection component. The display component can be connected to the controller via the Internet, allowing operators to optimize the production process of the project in a remote environment by carrying a similar projection component.

[0243] Integrating a display component into the quality problem analysis device visualizes the project topology network optimization process, allowing users to understand and monitor the process. This enables users to add empirical values ​​in real time during adjustments, resulting in higher efficiency and quality of project topology network optimization. This also improves the effectiveness of pre-inspection and optimization of the project topology network during the pre-inspection phase, ensuring the smooth implementation of projects. It effectively solves the problem of wasted production resources due to monitoring lag caused by relying solely on the project topology network for monitoring during production.

[0244] Similar parts between the embodiments provided in this application can be referred to mutually. The specific implementation methods provided above are only a few examples under the overall concept of this application and do not constitute a limitation on the scope of protection of this application. For those skilled in the art, any other implementation methods extended from the solution of this application without creative effort shall fall within the scope of protection of this application.

Claims

1. A quality problem analysis method based on node health pre-inspection, characterized in that, include: Upon detecting a project change event, the target project identifier is obtained; wherein, the target project identifier is used to characterize the project to be implemented; A corresponding project topology network is determined based on the target project identifier; wherein, the project topology network includes multiple nodes; the nodes are used to represent the key business corresponding to the project to be implemented; Obtain node information and time decay coefficients corresponding to each node; wherein, the node information includes the node failure occurrence time and node failure level for each node failure when the node is of different node types; the time decay coefficient and the node failure occurrence time are used to determine the time decay weight; the time decay coefficient serves as the base of the time decay weight, and the time decay factor serves as the exponent of the time decay weight, wherein the time decay factor is the difference between the system time and the node failure occurrence time; the time decay coefficient is obtained by integrating the impact of historical failures on current production; The difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network; the first accumulated value is the sum of the products of the node fault level of each node and the corresponding time decay weight; the baseline value is set according to the normal execution status of each node in the project topology network and the impact of minor faults on the network performance of the project topology network. If the network score is greater than or equal to the target network score threshold, the project to be implemented is started, and the implementation process of the project to be implemented is monitored based on the project topology network. If the network score is less than the target network score threshold, network adjustment information is generated; the network adjustment information is used to adjust the execution strategy of each node in the project topology network.

2. The quality problem analysis method based on node health pre-inspection according to claim 1, characterized in that, The node types include source nodes and handle nodes; the node faults include source node faults and handle node faults; the node information includes the occurrence time and level of the first node fault when the node acts as the source node, and the occurrence time and level of the second node fault when the node acts as the handle node; the node information also includes the number of first node faults that cause the source node fault when the node acts as the source node, and the number of second node faults that cause the handle node fault when the node acts as the handle node. Before calculating the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network, the method further includes: Based on the difference between the system time and the occurrence time of each first node failure, a first time decay factor is determined for each occurrence of the source node failure when the node is the source node; and based on the difference between the system time and the occurrence time of each second node failure, a second time decay factor is determined for each occurrence of the handle joint failure when the node is the handle joint. Based on the time decay coefficient and the first time decay factor, a first time decay weight is determined for each occurrence of a source node failure when the node acts as the source node; and a second time decay weight is determined for each occurrence of a handle failure when the node acts as the handle node, based on the time decay coefficient and the second time decay factor; wherein the base of the first time decay weight is the time decay coefficient, and the exponent of the first time decay weight is the first time decay factor; the base of the second time decay weight is the time decay coefficient, and the exponent of the second time decay weight is the second time decay factor. The sub-source risk scores of each node when it is the source node are summed to obtain the source risk score; wherein each sub-source risk score is the sum of the products of the first node failure level and the first time decay weight for each time the source node failure occurs when the node is the source node; The sub-gatekeeping risk scores of each node when it is the gatekeeping point are summed to obtain the gatekeeping risk score; wherein, each sub-gatekeeping risk score is the sum of the products of the second node failure level and the second time decay weight for each time the gatekeeping point failure occurs when the node is the gatekeeping point. The sum of the source risk score and the gatekeeping risk score is calculated to obtain the first accumulated value.

3. The quality problem analysis method based on node health pre-inspection according to claim 2, characterized in that, The calculation of the sum of the source risk score and the gatekeeping risk score to obtain the first accumulated value specifically includes: The corresponding source risk score coefficient and gate control risk score coefficient are determined based on the target project identifier; the sum of the source risk score coefficient and the gate control risk score coefficient is 1; Calculate the first product of the source risk score and the source risk score coefficient, and calculate the second product of the gate control risk score and the gate control risk score coefficient; Calculate the sum of the first product and the second product to obtain the first accumulated value.

4. The quality problem analysis method based on node health pre-inspection according to claim 3, characterized in that, If the network score is greater than or equal to the target network score threshold, then the project to be implemented is started, and the implementation process of the project to be implemented is monitored based on the project topology network. The method further includes: In the event of a problem in the implementation process of the project to be implemented, the faulty node of the project to be implemented and the node type corresponding to the faulty node when the fault occurs are determined; If the node type corresponding to the faulty node when the fault occurs is the source node, then the source risk score coefficient is increased by a preset step size, and the gate control risk score coefficient is decreased by the preset step size. If the node type corresponding to the faulty node at the time of the fault is the gatekeeper node, then the source risk score coefficient is decreased by the preset step size, and the gatekeeper risk score coefficient is increased by the preset step size.

5. The quality problem analysis method based on node health pre-inspection according to claim 2, characterized in that, The difference between the calculation baseline value and the first accumulated value yields the network score corresponding to the project topology network, specifically including: Calculate the sum of the sub-source risk score and the sub-gatekeeping risk score corresponding to the node, and determine the first score of the node; Calculate the difference between the benchmark value and the first score corresponding to the node to obtain the second score corresponding to the node; If the second score corresponding to each node is greater than or equal to the score threshold, then the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network.

6. The quality problem analysis method based on node health pre-inspection according to claim 2, characterized in that, The difference between the calculation baseline value and the first accumulated value yields the network score corresponding to the project topology network, specifically including: The number of first node failures that cause the source node failure when each of the nodes is the source node, and the number of second node failures that cause the handle node failure when each of the nodes is the handle node. If the number of failures of the first node and the number of failures of the second node corresponding to the node are both less than the node failure number threshold, then the difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network.

7. The quality problem analysis method based on node health pre-inspection according to claim 1, characterized in that, After obtaining the target project identifier upon detecting a project change event, the process further includes: Obtain the project level mapping table; wherein, the project level mapping table includes the mapping relationship between project identifiers and project levels; Based on the project level mapping table, determine the target project level corresponding to the target project identifier; Based on the correspondence between each project level and the network score threshold, the target network score threshold corresponding to the target project level is determined.

8. A quality problem analysis device based on node health pre-inspection, characterized in that, include: Display components and controllers; The controller is configured to: Upon detecting a project change event, the target project identifier is obtained; wherein, the target project identifier is used to characterize the project to be implemented; A corresponding project topology network is determined based on the target project identifier; wherein, the project topology network includes multiple nodes; the nodes are used to represent the key business corresponding to the project to be implemented; Obtain node information and time decay coefficients corresponding to each node; wherein, the node information includes the node failure occurrence time and node failure level for each node failure when the node is of different node types; the time decay coefficient and the node failure occurrence time are used to determine the time decay weight; the time decay coefficient serves as the base of the time decay weight, and the time decay factor serves as the exponent of the time decay weight, wherein the time decay factor is the difference between the system time and the node failure occurrence time; the time decay coefficient is obtained by integrating the impact of historical failures on current production; The difference between the baseline value and the first accumulated value is calculated to obtain the network score corresponding to the project topology network; the first accumulated value is the sum of the products of the node fault level of each node and the corresponding time decay weight; the baseline value is set according to the normal execution status of each node in the project topology network and the impact of minor faults on the network performance of the project topology network. If the network score is greater than or equal to the target network score threshold, the project to be implemented is started, and the implementation process of the project to be implemented is monitored based on the project topology network. If the network score is less than the target network score threshold, network adjustment information is generated, and the display component is controlled to display the network adjustment information; the network adjustment information is used to adjust the execution strategy of each node in the project topology network.

9. The quality problem analysis device based on node health pre-inspection according to claim 8, characterized in that, The node types include source nodes and handle nodes; the node faults include source node faults and handle node faults; the node information includes the occurrence time and level of the first node fault when the node acts as the source node, and the occurrence time and level of the second node fault when the node acts as the handle node; the node information also includes the number of first node faults that cause the source node fault when the node acts as the source node, and the number of second node faults that cause the handle node fault when the node acts as the handle node. Before the controller calculates the difference between the baseline value and the first accumulated value to obtain the network score corresponding to the project topology network, it is also configured as follows: Based on the difference between the system time and the time of each first node failure, a first time decay factor is determined for each failure of the source node when the node acts as the source node. Furthermore, based on the difference between the system time and the time of each second node failure, a second time decay factor is determined for each occurrence of the joint failure when the node is the joint point. Based on the time decay coefficient and the first time decay factor, determine the first time decay weight corresponding to each time the source node fault occurs when the node acts as the source node. And, based on the time decay coefficient and the second time decay factor, a second time decay weight is determined for each time the node, as the handle joint point, generates a handle joint point failure; wherein, the base of the first time decay weight is the time decay coefficient, and the exponent of the first time decay weight is the first time decay factor; the base of the second time decay weight is the time decay coefficient, and the exponent of the second time decay weight is the second time decay factor. The sub-source risk scores of each node when it is the source node are summed to obtain the source risk score; wherein each sub-source risk score is the sum of the products of the first node failure level and the first time decay weight for each time the source node failure occurs when the node is the source node; The sub-gatekeeping risk scores of each node when it is the gatekeeping point are summed to obtain the gatekeeping risk score; wherein, each sub-gatekeeping risk score is the sum of the products of the second node failure level and the second time decay weight for each time the gatekeeping point failure occurs when the node is the gatekeeping point. The sum of the source risk score and the gatekeeping risk score is calculated to obtain the first accumulated value.

10. The quality problem analysis device based on node health pre-inspection according to claim 9, characterized in that, The controller calculates the sum of the source risk score and the gatekeeping risk score to obtain the first accumulated value, which is specifically configured as follows: The corresponding source risk score coefficient and gate control risk score coefficient are determined based on the target project identifier; the sum of the source risk score coefficient and the gate control risk score coefficient is 1; Calculate the first product of the source risk score and the source risk score coefficient, and calculate the second product of the gate control risk score and the gate control risk score coefficient; Calculate the sum of the first product and the second product to obtain the first accumulated value.

Images