Production line yield control method and related device

Abstract

The application provides a yield control method and related equipment for a production line. The yield control method comprises: obtaining yield information of the production line; generating alarm information corresponding to the production line if the yield information does not meet a preset yield condition; matching the alarm information with a preset user account permission; sending the alarm information to one or more target user accounts having corresponding processing permissions according to a matching result; receiving processing information of the target user accounts, the processing information being a processing scheme of the target user accounts for the alarm information; updating the yield information after receiving the processing information, and evaluating a processing effect of the processing scheme and an operation status of the production line based on the updated yield information. The application can supervise and control the yield of the production line, and improve the production and management efficiency of the production line.

Description

Technical Field

[0001] This invention relates to the field of production monitoring technology, and more specifically, to a method and related equipment for production line yield control. Background Technology

[0002] In modern manufacturing, production line yield is a key indicator for measuring production efficiency and product quality. Traditional yield monitoring methods often rely on manual statistics and reporting, which suffers from problems such as information lag, inaccurate data, difficulty in problem localization, unclear handling processes, and ambiguous responsibility allocation. When abnormalities occur in the production line yield, it is impossible to quickly and accurately notify the personnel with the appropriate handling authority, resulting in untimely problem handling and impacting production efficiency and cost control. Furthermore, the lack of an effective evaluation mechanism for the effectiveness of handling solutions makes it difficult to form closed-loop management and continuous improvement. Summary of the Invention

[0003] In view of this, this application provides a production line yield control method and related equipment, which can monitor and control the yield of the production line and improve the production and management efficiency of the production line.

[0004] The first aspect of this application provides a production line yield control method, comprising: acquiring yield information of the production line; generating alarm information corresponding to the production line when the yield information does not meet preset yield conditions; matching the alarm information with preset user account permissions; sending the alarm information to one or more target user accounts with corresponding processing permissions according to the matching result; receiving processing information from the target user accounts, the processing information being a processing plan for the alarm information by the target user accounts; updating the yield information after receiving the processing information; and evaluating the processing effect of the processing plan and the operating status of the production line based on the updated yield information.

[0005] Compared with related technologies, the embodiments of this application have at least the following advantages: By acquiring real-time yield information from the production line, the system can quickly generate alarm messages when the yield does not meet preset conditions, ensuring that problems are detected promptly and preventing defective products from flowing into subsequent processes or affecting overall production efficiency. Simultaneously, alarm messages are matched with preset user account permissions, ensuring that alarm messages are sent to target user accounts with the appropriate processing permissions, thereby avoiding mis-sending or missed messages and improving the efficiency and targeting of problem handling. After receiving the alarm message, the target user account can promptly provide a solution and provide feedback through the system, thus shortening the problem handling time and reducing production line downtime or production losses caused by anomalies. After receiving the processing information, the system updates the yield information and evaluates the effectiveness of the processing solution and the production line's operating status based on the updated data. This update and evaluation mechanism reflects the effectiveness of problem handling in real time, providing data support for subsequent decision-making.

[0006] Optionally, the production line is used to produce the target product. Obtaining the yield information of the production line includes: dividing the production line into multiple steps according to the manufacturing process of the target product, with each step corresponding to one or more sections, and each section corresponding to at least one operating device; calculating the yield data of each operating device in producing the target product within a preset time period; and summarizing the yield data of each operating device according to the hierarchical relationship of operating device, step, and section to obtain the yield information of the production line.

[0007] Optionally, the alarm information includes: a first alarm information, a second alarm information, a third alarm information, and a fourth alarm information. The alarm information generated corresponds to the production line and includes: identifying the abnormal operating device from multiple operating devices based on yield information; generating a first alarm information indicating the location of the abnormal operating device; generating a second alarm information indicating the department information associated with the abnormal operating device; generating a third alarm information indicating the person responsible for the abnormal operating device; and generating a fourth alarm information indicating an abnormal operation event occurring at the abnormal operating device.

[0008] Optionally, the processing information also includes the cause of production line abnormalities; based on the updated yield information, the processing effect of the processing solution and the operating status of the production line are evaluated, including: based on the processing information, according to the work section, step and operating device, the frequency of abnormality occurrence and the efficiency of abnormality resolution of the production line are statistically analyzed; based on the frequency of abnormality occurrence and the efficiency of abnormality resolution, the operating status of the production line is evaluated and a production line operating status report is generated.

[0009] Optionally, the user account permissions include first user account permissions, which include at least one or both of setting preset yield conditions and monitoring the yield information of the production line; before sending the alarm information to one or more target user accounts with corresponding processing permissions, the method further includes: sending the alarm information to the user corresponding to the first user account permissions.

[0010] Optionally, the user account permissions include second user account permissions, which are the permissions to execute the processing scheme, the second user account carries processing scope permissions, and the second user account is associated with department information; the step of matching the alarm information with preset user account permissions includes: obtaining department information related to production line abnormalities from the alarm information; comparing the department information related to production line abnormalities with the department information associated with the second user account or the processing scope permissions of the second user account; and based on the comparison result, determining one or more second user accounts as the target user accounts.

[0011] Optionally, after evaluating the effectiveness of the treatment plan, the production line yield control method also includes: if the treatment effect does not meet the preset effectiveness standard, determining the parent user account of the target user account; generating notification information based on alarm information and treatment effect, and sending the notification information to the parent user account.

[0012] A second aspect of this application provides a production line yield control device, comprising: a monitoring unit for acquiring production line yield information; an alarm unit for generating alarm information corresponding to the production line when the yield information does not meet preset yield conditions; a matching unit for matching the alarm information with preset user account permissions; a sending unit for sending the alarm information to one or more target user accounts with corresponding processing permissions according to the matching result; a receiving unit for receiving processing information from the target user accounts, wherein the processing information is a processing plan for the alarm information by the target user accounts; and an evaluation unit for updating the yield information after receiving the processing information, and evaluating the processing effect of the processing plan and the operating status of the production line based on the updated yield information.

[0013] Thirdly, embodiments of this application also provide an electronic device, which includes a processor and a memory. The memory is used to store instructions, and the processor is used to call the instructions in the memory, so that the electronic device executes the production line yield control method as described in the first aspect.

[0014] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the production line yield control method as described in the first aspect. The technical effects obtained by the second, third, and fourth aspects are similar to those obtained by the corresponding technical means in the first aspect, and will not be repeated here. Attached Figure Description

[0015] Figure 1This is a schematic diagram illustrating the application environment of the production line yield control method provided in an embodiment of this application.

[0016] Figure 2 A flowchart illustrating the steps of a production line yield control method provided in an embodiment of this application.

[0017] Figure 3 for Figure 2 The flowchart shown is a sub-flowchart of the steps in the production line yield control method.

[0018] Figure 4 A flowchart illustrating the steps of a production line yield control method provided in another embodiment of this application.

[0019] Figure 5 for Figure 2 The flowchart shown is a sub-flowchart of the steps in the production line yield control method.

[0020] Figure 6 A flowchart illustrating the steps of a production line yield control method provided in another embodiment of this application.

[0021] Figure 7 This is a schematic diagram of a set of user interfaces provided in one embodiment of this application.

[0022] Figure 8 A functional block diagram of a production line yield control device provided in an embodiment of this application.

[0023] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0024] To better understand the above-mentioned objectives, features, and advantages of this application, the application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.

[0025] The following description sets forth many specific details to provide a full understanding of this application. The described embodiments are only some, not all, of the embodiments of this application.

[0026] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the specification of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application.

[0027] It should be further noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0028] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects, not to describe a specific order or sequence.

[0029] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0030] For ease of understanding, some concepts related to the embodiments of this application are illustrated and explained by way of example for reference.

[0031] Those skilled in the art will understand that Figure 1 The schematic diagram of the implementation environment for the production line yield control method shown is merely an example. The implementation environment described in this application embodiment is for the purpose of more clearly illustrating the technical solution of this application embodiment and does not constitute a limitation on the technical solution provided by this application embodiment. As those skilled in the art will know, with the emergence of new business scenarios, the technical solution provided by this application embodiment is also applicable to similar technical problems.

[0032] exist Figure 1In this application embodiment, the production line yield control method can be deployed on server 120. Server 120 can integrate the production line yield control device provided in this application embodiment. The terminal device 110 includes, but is not limited to, user equipment capable of establishing a communication connection with server 120. Terminal device 110 and server 120 can be connected via a network. Server 120 can also receive information sent by various operating devices 130 deployed on the production line. Operating devices 130 include, but are not limited to, pick-and-place machines, reflow soldering equipment, automated optical inspection (AOI) equipment, in-circuit testing (ICT) equipment, machine tools, and industrial robots. The operating data of operating devices 130 and the quantity of products produced / processed by the operating devices (total quantity, qualified quantity, abnormal quantity, etc.) can be collected and reported to server 120. Data collection methods include, but are not limited to, completion by the operating device 130 itself, completion by sensors deployed on or around the operating device 130, and manual input. Server 120 can receive reported data and perform data cleaning, storage, and analysis to perform calculations, alarm judgments, permission matching, information push, and effect evaluation. Server 120 can also store production line structure information, which may include: production steps, sections, operating devices and their hierarchical relationships for the target product, yield data, preset yield conditions, user information (e.g., user information may include: account, department, permissions, hierarchical relationships, etc.), alarm records, processing information, and evaluation results.

[0033] Server 120 is also used to determine whether the current yield rate is abnormal according to preset rules and to generate structured alarm information. Server 120 can also be used to maintain user accounts and their permission information, including monitoring permissions, processing permissions, department affiliation, processing scope, and hierarchical relationships.

[0034] Optionally, in this embodiment, the terminal device 110 may be a terminal device configured with a target client, which may include, but is not limited to, at least one of the following: mobile phone, laptop computer, tablet computer, PDA, mobile internet device (MID), desktop computer, smartwatch, etc. The aforementioned network may include, but is not limited to, wired network and wireless network, wherein the wired network includes: local area network, metropolitan area network and wide area network, and the wireless network includes: Bluetooth, Wi-Fi and other networks that enable wireless communication. Figure 1 The following is an illustration using a mobile phone as an example of a terminal device 110.

[0035] Terminal device 110 provides a visual interface that displays multiple visual components, allowing users to view relevant information about production line yield. This visual interface is accessible to users with different permissions for logging in, viewing information, receiving alarms, and submitting processing information.

[0036] Server 120 can be used to execute the production line yield control method provided in the embodiments of this application, so as to monitor and control the yield of the production line and improve the production and management efficiency of the production line.

[0037] It is understood that server 120 can be a standalone server, a server network, or a server cluster. For example, server 120 described in this embodiment includes, but is not limited to, computers, network hosts, single network servers, multiple network server sets, or cloud servers composed of multiple servers. Cloud servers consist of a large number of computers or network servers based on cloud computing. It should be noted that the above-mentioned production line yield control method is not limited to execution only on servers; the production line yield control method can also be deployed and executed on terminal device 110.

[0038] like Figure 2 As shown, one embodiment of this application also provides a production line yield control method, which can be applied to the server 120 described above. The production line yield control method may specifically include the following steps.

[0039] S210: Obtain the yield information of the production line.

[0040] In some embodiments, the server continuously, in real-time or near real-time collects production line yield information, or calculates production line yield information in real time based on reported data. The production line in this embodiment may be one or more pre-designated production lines. Yield information may include, but is not limited to, the yield of a specific manufacturing area (MA Yield) or the overall production line yield. Optionally, yield information is typically defined as the ratio of the number of qualified products to the total output of a specific production line or process within a certain time period, which can be obtained by dividing the number of qualified products by the total output.

[0041] In some embodiments, the production line for producing the target product can be divided into multiple logical or physical steps according to the manufacturing process of the target product. Each step can be further subdivided into one or more sections, where each section can correspond to at least one operating device that performs a specific operation. The operating device can be the basic execution unit of the section, such as a printer, pick-and-place machine, reflow oven, or AOI equipment on an SMT production line, or a component insertion machine or wave soldering equipment on a DIP line, or ICT equipment or functional testing (FCT) equipment on a test station. The server can interface with each operating device or the control system or detection system of the operating device, or through manual input, barcode scanning, etc., to count the total number of target products and the number of qualified products produced by each operating device within a preset time period (e.g., per hour, per shift, per batch), thereby calculating their respective yield data.

[0042] In some embodiments, yield information may be directly reported to the server by the operating device or the control system, detection system of the operating device, or manual input.

[0043] S220: If the yield information does not meet the preset yield conditions, generate alarm information corresponding to the production line.

[0044] In some embodiments, the preset yield condition can be a decrease in overall yield, an overall yield below a preset value, or a yield of a specific critical item below a preset value. For example, if a yield problem occurs with a critical material (such as an excessive defect rate of a certain type of capacitor) or a critical equipment parameter (such as BGA soldering temperature fluctuations exceeding ±5°C), the server generates an alarm message. Another example is if the SMT placement process yield drops sharply from 98% to 92%, the server generates an alarm message, or if the real-time monitoring system detects that the yield is below a preset threshold (such as <95% for 3 consecutive hours), the server generates an alarm message.

[0045] Optionally, when an alarm message pushes an abnormal yield information, it will also push a time requirement for the user to handle the yield abnormality. For example, the alarm message may take the form of an automatically pushed email or SMS alert, requiring the team to respond to the alarm message within 30 minutes.

[0046] In some embodiments, alarm information may be presented as a Top Item Alarm, which only alerts the parameters of critical materials or equipment.

[0047] It is understandable that if the yield information meets the preset yield conditions, alarm information may not be generated.

[0048] S230: Match alarm information with preset user account permissions.

[0049] User account permissions refer to the permissions to process alarm information. The server can maintain a management system with multiple user accounts and their permissions. Each user account is associated with specific permission configurations. The server can match alarm information with preset user account permissions.

[0050] Optionally, user account permissions may include: first user account permissions and second user account permissions. First user account permissions are typically granted to administrators or monitoring roles (such as production managers, quality managers, etc.), and their permissions may include at least one or both of setting preset yield conditions and monitoring production line yield information. In some process designs, before sending alarms to the alarm processing layer (target user account), the server will first send the alarm information to the user with first user account permissions, enabling them to gain a global view and understand the occurring production line anomalies.

[0051] Secondary user account permissions are typically granted to personnel who need to take direct action and execute solutions, such as engineers, technicians, and operators. User accounts with secondary user account permissions are usually associated with departmental information (e.g., "Quality Department - SMT Inspection Group") and may carry scope permissions (e.g., explicitly stating that they are responsible for handling "SMT line AOI equipment malfunctions" or "malfunctions of specific product models").

[0052] S240: Based on the matching results, send the alarm information to one or more target user accounts with the corresponding processing permissions.

[0053] In some embodiments, the server may execute matching logic to compare the generated alarm information with a user rights database to determine one or more target user accounts that should receive the alarm information. For example, the server may extract key hierarchical information from the alarm information, particularly departmental information related to the production line anomaly contained in the alarm information, or determine the responsible department or maintenance team based on the equipment / process information in the alarm information. The extracted departmental information or inferred scope of responsibility is compared with the departmental information or processing scope permissions associated with user accounts with second-user account permissions stored in the system. Based on the comparison results, one or more users' permissions can be determined to match the current alarm event. These users are then identified as target user accounts. The server can then send the alarm information to these identified target user accounts.

[0054] Specific alarm information is shown in the example below, and will not be repeated here.

[0055] S250: Receives processing information from the target user account, which is the target user account's processing plan for alarm information.

[0056] In some embodiments, after receiving an alarm message, the target user account can perform corresponding investigation and processing actions, generate processing information from the processing plan, and upload the processing information to the system. For example, after receiving an abnormal alarm from device 1, engineer A goes to the site to inspect device 1, analyzes the data of device 1, adjusts parameters, and repairs device 1. After processing is completed, the user submits the processing information through the interface provided by the terminal device (e.g., PC client, web page, or mobile APP interface).

[0057] Optionally, the processing information may include: the cause of the production line abnormality, the handling plan, and other relevant information, such as the person handling the issue, the handling time, whether spare parts were replaced, and whether the measures were temporary or permanent. Specifically, the cause of the production line abnormality is the reason for the decrease in yield determined by the user after analysis and diagnosis. For example, the cause for equipment 1 is inaccurate lens calibration parameters. The handling plan may be the specific solutions taken by the user, such as re-executing the lens calibration procedure for equipment 1.

[0058] After a user submits processing information through the interface provided by the terminal device, the processing information can be uploaded to the server, and then the server can receive the processing information of the target user account.

[0059] S260: After receiving the processing information, update the yield information, and based on the updated yield information, evaluate the processing effect of the processing scheme and the operating status of the production line.

[0060] In some embodiments, after receiving processing information submitted by the target user, the server may initiate a verification and evaluation process for the target user's processing. For example, this can be achieved by obtaining the yield information of the device that previously experienced an anomaly after the target user's processing; that is, the currently obtained yield information refers to the newly generated yield information of the device after the processing measures are implemented, i.e., the updated yield information.

[0061] For example, the treatment effect can be assessed by calculating the average repair time: the repair took 35 minutes, which is 32.7% better than the historical average MTTR (52 minutes) of the device. Alternatively, the treatment effect can be assessed by calculating the recurrence index, which calculates the recurrence risk level (low / medium / high) based on the frequency of similar abnormalities occurring on the same device over the past 30 days.

[0062] If the updated yield information shows that the problem has been resolved (e.g., the yield of device B1 stabilizes at 99.9% within an hour after processing), the system evaluates the user-submitted solution as effective and marks the status of the abnormal event as "resolved" or "closed," while updating the production line's operating status (e.g., the device that previously experienced the abnormality has returned to normal).

[0063] If the updated yield information shows that the problem has not been resolved or the expected improvement has not been achieved, it is evaluated as invalid or ineffective.

[0064] Optionally, this embodiment can also perform more in-depth analysis and reporting functions on the production line's operating status. For example, based on long-term accumulated processing information (including the causes of anomalies and handling solutions) and the efficiency of resolving each anomaly (the time from alarm generation to yield recovery), the system can perform statistical analysis, and the statistical analysis results can be visualized in the form of dashboards and reports.

[0065] In some embodiments, the frequency of anomalies and the efficiency of anomaly resolution in the production line can be statistically analyzed according to multiple dimensions such as work section, step, operating device, and type of anomaly cause. For example, the monthly number of anomalies in work section 1 or equipment 1 can be calculated, or the average resolution time for a specific type of problem can be calculated.

[0066] In some embodiments, the server can automatically generate periodic (e.g., daily, weekly, monthly) production line operation status reports based on the frequency of anomalies and the efficiency of resolution. These reports can be sent to users with the permissions of the first user account. The production line operation status reports can highlight areas, equipment, or problem types where anomalies frequently occur, assessing overall stability, response efficiency, and resolution capabilities, providing decision support for management. The reports can also include handling recommendations for frequent anomalies. For example, a production line operation status report might state: "SMT line P1 has been operating stably recently, but the calibration stability of AOI equipment B1 needs attention; we recommend communicating with the equipment supplier or increasing the frequency of preventative maintenance."

[0067] Through the implementation of the above steps, the production line yield control method provided in this application can achieve refined and automated monitoring of production line yield. When an anomaly occurs, it can quickly and accurately notify the target user with the appropriate processing authority, receive and record the handling plan, and verify the effectiveness of the handling plan through subsequent yield data, forming a closed-loop management system of problem discovery, handling, verification, and analysis. Simultaneously, the hierarchical permission mechanism ensures that abnormal events can be responded to and handled in a timely and effective manner, ultimately achieving the goal of improving production line efficiency and product quality.

[0068] Please also refer to Figure 3 Taking the production line used to produce the target product as an example, obtaining the yield information of the production line may include the following steps.

[0069] S2101: The production line is divided into multiple steps according to the manufacturing process of the target product. Each step corresponds to one or more sections, and each section corresponds to at least one operating device.

[0070] S2102: Calculate the yield data of the target product produced by each operating device within a preset time period.

[0071] S2103: Summarize the yield data of each operating device according to the hierarchical relationship of operating device, step and section to obtain the yield information of the production line.

[0072] For example, as shown in Table 1, the production line can be divided into three main steps: Assembly Process (AP), Radio Frequency (RF), and Testing Process (TEST). Each step is further divided into multiple sections. For instance, the AP step includes sections VMI1, VMI2, UF_VI, and AP_TEST_INPUT1; the RF step includes sections VMI2, UF_VI, and MTS2_VI; and the TEST step includes sections TEST_INPUT1 and VMI4. Each section corresponds to at least one operating device, and the yield data of the target product produced by each operating device within a preset time period is statistically analyzed. For example, for section VMI1, the yield data of the target product produced by its operating device within one hour is statistically analyzed; for section UF_VI, the yield data of its operating device within one hour is statistically analyzed.

[0073] By summarizing the yield data of each operating device according to the hierarchical relationship of operating device, step, and section, the yield information of the production line can be obtained. For example, summarizing the yield data of sections VMI1, VMI2, UF_VI, and AP_TEST_INPUT1 under the AP step yields the overall yield information of the AP step; summarizing the yield data of sections VMI2, UF_VI, and MTS2_VI under the RF step yields the overall yield information of the RF step; and summarizing the yield data of sections TEST_INPUT1 and VMI4 under the TEST step yields the overall yield information of the TEST step.

[0074] An alarm message is generated if the yield information does not meet the preset yield conditions. For example, when the overall yield of the AP step is lower than the preset 99.5%, an alarm message is generated. The alarm message may include abnormal steps (step AP), abnormal sections (such as section VMI1), and abnormal operating devices (such as equipment A1).

[0075] In some embodiments, alarm information may include first alarm information, second alarm information, third alarm information, and fourth alarm information. Generating alarm information may specifically include: identifying an abnormal operating device from multiple operating devices based on yield information; generating first alarm information representing the location of the abnormal operating device; generating second alarm information representing the department information associated with the abnormal operating device; generating third alarm information representing the person responsible for the abnormal operating device; and generating fourth alarm information representing an abnormal operation event occurring at the abnormal operating device.

[0076] In this embodiment, the first alarm information is used to characterize the location information of the malfunctioning device. The first alarm information can be used to indicate the specific physical or logical location of the malfunctioning device. For example, the first alarm information includes: "SMT line 1, step P1-SMT, section S1.4-AOI inspection, equipment B1". The second alarm information is used to characterize the department information associated with the malfunctioning device, which helps route the alarm to the correct responsible team. For example, the second alarm information includes: "Quality Department - SMT Inspection Group" or "Equipment Engineering Department - SMT Maintenance Group". The third alarm information is used to characterize the information of the person responsible for the malfunctioning device. For example, the responsible person may include the name or employee number of the equipment manager, area team leader, or engineer. For example, the third alarm information includes: Equipment Manager B or Team Leader C. The fourth alarm information is used to characterize the specific abnormal event that occurred in the abnormal operation device. It is used to provide information about the nature, time, observed phenomena or preliminary analysis results of the abnormality. For example, the fourth alarm information includes: "The detection yield of equipment A1 dropped to 99.2% at 14:30 on October 27, 2023, which is lower than the threshold of 99.5%."

[0077] Once an alarm is generated, the server can immediately send the alarm information through various channels (such as client push notifications, email, SMS, etc.) and set response time requirements, such as requiring the Directly Responsible Individual (DRI) team to respond and confirm within 30 minutes.

[0078] In some embodiments, the processing information also includes the cause of production line abnormalities; based on the updated yield information, the processing effect of the processing solution and the operating status of the production line are evaluated, which may specifically include: based on the processing information, according to the work section, step and operating device, the frequency of abnormality occurrence and the efficiency of abnormality resolution of the production line are statistically analyzed; based on the frequency of abnormality occurrence and the efficiency of abnormality resolution, the operating status of the production line is evaluated and a production line operating status report is generated.

[0079] Please also refer to Figure 4 User account permissions include primary user account permissions, which must include at least one or both of the following: setting preset yield conditions and monitoring production line yield information. Compared to... Figure 2 Before or after sending alarm information to one or more target user accounts with corresponding processing permissions, alarm information can also be sent to the user corresponding to the first user account's permissions, so that the user corresponding to the first user account's permissions can have a global view of the production line yield and understand the production line anomalies that have occurred. Figure 4The following example illustrates how alarm information is sent to the user corresponding to the first user account's permissions before being sent to one or more target user accounts with the appropriate processing permissions. The production line yield control method may specifically include the following steps.

[0080] S210: Obtain the yield information of the production line.

[0081] S220: If the yield information does not meet the preset yield conditions, generate alarm information corresponding to the production line.

[0082] S230: Match alarm information with preset user account permissions.

[0083] S270: Send the alarm information to the user corresponding to the first user account's permissions.

[0084] For example, if the server finds that Production Manager B has first-user privileges to monitor the overall yield of the production line, it will send the complete alarm information or a brief alarm information to Production Manager B's account.

[0085] In some embodiments, step S270 may also be performed before step S230.

[0086] S240: Based on the matching results, send the alarm information to one or more target user accounts with the corresponding processing permissions.

[0087] S250: Receives processing information from the target user account, which is the target user account's processing plan for alarm information.

[0088] S260: After receiving the processing information, update the yield information, and based on the updated yield information, evaluate the processing effect of the processing scheme and the operating status of the production line.

[0089] Please also refer to Figure 5 User account permissions include second user account permissions, which are the permissions to execute processing plans. The second user account carries processing scope permissions and is associated with department information. Matching alarm information with preset user account permissions can specifically include the following steps.

[0090] S2301: Obtain departmental information related to production line anomalies from alarm information.

[0091] S2302: Compare the department information related to the production line abnormality with the department information associated with the second user account or the processing scope permissions of the second user account.

[0092] S2303: Based on the comparison results, identify one or more second user accounts as the target user account.

[0093] For example, the server queries the user permission database and determines that the department information in the alarm message matches the department information of user C. This identifies user C as the target user account, and the alarm message can then be sent to user C's account through a specified channel (such as client message + SMS).

[0094] Optionally, in practical applications, different types of anomalies may require collaboration among different departments, and the target user accounts for different types of anomalies may differ. For example, abnormal adjustments to equipment parameters may primarily be handled by on-site personnel. Defect analysis involving product layout may require the involvement of a second department. For instance, issues with jigs or mechanical structures may require the handling of a third department. Incoming material quality issues would necessitate the handling of a fourth department.

[0095] Please see Figure 6 ,and Figure 2 In contrast, for situations where the handling solution is ineffective or not handled in a timely manner, production line yield control methods can also include an escalation mechanism. Alarm information is notified to the supervisor, higher-level technical experts, or those responsible for relevant processes to ensure timely handling of production line anomalies. Production line yield control methods can specifically include the following steps.

[0096] S210: Obtain the yield information of the production line.

[0097] S220: If the yield information does not meet the preset yield conditions, generate alarm information corresponding to the production line.

[0098] S230: Match alarm information with preset user account permissions.

[0099] S240: Based on the matching results, send the alarm information to one or more target user accounts with the corresponding processing permissions.

[0100] S250: Receives processing information from the target user account, which is the target user account's processing plan for alarm information.

[0101] S260: After receiving the processing information, update the yield information, and based on the updated yield information, evaluate the processing effect of the processing scheme and the operating status of the production line.

[0102] S280: If the processing effect does not meet the preset validity criteria, determine the parent user account of the target user account; S290: Generate notification information based on alarm information and processing results, and send the notification information to the next higher level user account.

[0103] In this embodiment, after evaluating the processing effect of the processing solution, if the processing effect does not meet the preset effectiveness standard, for example, the yield rate does not return to normal within a specified time, or it becomes abnormal again shortly after returning to normal, then steps S280 and S290 are further executed. The higher-level user account can be preset in the user permission database, and can typically be the direct supervisor of the target user, or a higher-level technical expert or person in charge of the relevant process.

[0104] In some embodiments, if the evaluation of the solution's effectiveness is negative, for example, if the solution submitted by user A is marked as invalid, or if the yield of device A1 corresponding to the alarm information still does not meet the preset yield conditions, a notification can be generated based on the alarm information and sent to the upper-level user account to remind the upper-level user to pay attention to this unresolved issue and to coordinate, allocate resources, or personally intervene to ensure that the production line problem is ultimately effectively resolved.

[0105] In one specific embodiment, such as Figure 7 As shown, this application also provides a user interface to facilitate users in viewing pushed alarm information and submitting processing solutions. This user interface can be the interface of a client installed on the terminal device, and the server corresponding to the client can be the one described above. Figure 1 The server 120 shown can also be another server that is connected to and communicates with server 120. For example... Figure 7 As shown in (a), the main interface may include a search bar where users can search for specific tasks or messages. The main interface may also include two tabs: "Tasks" and "Messages". A circular progress bar may also be displayed in the center of the main interface, indicating the total number of tasks (16), of which the number of unprocessed tasks (4) and the number of processed tasks (12), of which the number of tasks processed by the individual (6). The main interface may also display two sections: "My Tasks" and "Progress Details", each of which may display icons and numbers representing the number of different types of tasks.

[0106] like Figure 7 As shown in (a), the main interface also displays two pending alarm messages: "SMA-Yield Anomaly" and "SMA-Carrier No. Anomaly". The alarm message for "SMA-Yield Anomaly" includes the following: the yield rate of workstation D053FS01-AP-VMI1 is 98.3%, which is lower than the target value of 99.9%, and the anomaly time is 08:02 on 2023 / 5 / 8. Users can handle this by clicking the "Reply Now" control.

[0107] The alarm message for "SMA-Carrier No. Anomaly" includes: Carrier No. RANPABCE000761 of workstation D053FS01-VMI1 failed 3pcs, with the anomaly occurring at 08:03 on 2023 / 5 / 8. Users can handle this by clicking the "Reply Now" control.

[0108] The main interface also has a navigation bar at the bottom with four controls: "Assign," which returns to the main interface; "Workbench," which takes you to the workbench interface to view and manage work tasks; "Smart Assistant," which takes you to the smart assistant interface to get help and suggestions; and "My Profile," which takes you to your personal center to view personal information and settings.

[0109] like Figure 7 As shown in (b), after the user clicks the "Reply Now" control corresponding to "SMA-Yield Exception", the main interface will redirect to the exception handling form interface. The exception handling form interface may include two text input boxes: "Please enter the reason for the exception", where the user enters the reason for the exception; and "Please enter the solution", where the user enters a solution to resolve the exception. The exception handling form interface also includes a "Submit" control. After the user clicks the "Submit" control, the reason for the exception and the solution entered by the user will be submitted to the server.

[0110] like Figure 8 As shown, this application provides a production line yield control device 40, comprising: The monitoring unit 410 is used to obtain the yield information of the production line.

[0111] The alarm unit 420 is used to generate alarm information corresponding to the production line when the yield information does not meet the preset yield conditions.

[0112] The matching unit 430 is used to match alarm information with preset user account permissions.

[0113] The sending unit 440 is used to send alarm information to one or more target user accounts with corresponding processing permissions based on the matching results.

[0114] The receiving unit 450 is used to receive processing information from the target user account, which is the processing plan for the target user account in response to alarm information.

[0115] The evaluation unit 460 is used to update the yield information after receiving the processing information, and to evaluate the processing effect of the processing scheme and the operation status of the production line based on the updated yield information.

[0116] In some embodiments, the aforementioned unit may be a programmable software instruction stored in memory and executable by a processor. It is understood that in other embodiments, the aforementioned unit may also be program instructions or firmware embedded in the processor.

[0117] Please refer to Figure 9 , Figure 9 This is a schematic diagram of an embodiment of the electronic device of this application.

[0118] The electronic device 100 includes a memory 20, a processor 30, and a computer program 50 stored in the memory 20 and executable on the processor 30. When the processor 30 executes the computer program 50, it implements the steps described in the above-described production line yield control method embodiment.

[0119] For example, computer program 50 can also be divided into one or more modules / units, one or more of which are stored in memory 20 and executed by processor 30. One or more modules / units can be a series of computer program instruction segments capable of performing a specific function, the instruction segments describing the execution process of computer program 50 in electronic device 100. For example, computer program 50 can be divided into... Figure 8 The monitoring unit 410, alarm unit 420, matching unit 430, sending unit 440, receiving unit 450, and evaluation unit 460 are shown.

[0120] Those skilled in the art will understand that the schematic diagram is merely an example of the electronic device 100 and does not constitute a limitation on the electronic device 100. It may include more or fewer components than shown, or combine certain components, or different components. For example, the electronic device 100 may also include input / output devices, network access devices, buses, etc.

[0121] Electronic device 100 can be Figure 1 The server shown is 120.

[0122] Processor 30 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors, single-chip microcomputers, or any conventional processor.

[0123] The memory 20 can be used to store computer programs 50 and / or modules / units. The processor 30 implements various functions of the electronic device 100 by running or executing the computer programs and / or modules / units stored in the memory 20 and by calling data stored in the memory 20. The memory 20 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc.; the data storage area may store data created according to the use of the electronic device 100, etc. In addition, the memory 20 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0124] If the modules / units integrated in the electronic device 100 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunication signals.

[0125] This embodiment also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the production line yield control method in the above embodiment.

[0126] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for controlling production line yield, characterized in that, The method includes: Obtain production line yield information; If the yield information does not meet the preset yield conditions, an alarm message corresponding to the production line is generated; The alarm information is matched with the preset user account permissions; Based on the matching results, the alarm information is sent to one or more target user accounts with corresponding processing permissions; Receive processing information from the target user account, wherein the processing information is the processing plan of the target user account for the alarm information; After receiving the processing information, the yield information is updated, and based on the updated yield information, the processing effect of the processing scheme and the operating status of the production line are evaluated.

2. The method according to claim 1, characterized in that, The production line is used to produce the target product, and obtaining the yield information of the production line includes: According to the manufacturing process of the target product, the production line is divided into multiple steps, each step corresponds to one or more sections, and each section corresponds to at least one operating device. The yield data of the target product produced by each of the operating devices within a preset time period are statistically analyzed. The yield data of each of the operating devices are summarized according to the hierarchical relationship of the operating device, the step, and the section to obtain the yield information of the production line.

3. The method according to claim 2, characterized in that, The alarm information includes: a first alarm information, a second alarm information, a third alarm information, and a fourth alarm information. Generating alarm information corresponding to the production line includes: Based on the yield information, abnormal operating devices are identified from among the multiple operating devices; Generate first alarm information representing the location of the abnormal operation device; Generate second alarm information that represents the department information associated with the abnormal operation device; Generate the third alarm information representing the person in charge of the abnormal operation device; Generate the fourth alarm information characterizing the abnormal operation event of the abnormal operation device.

4. The method according to claim 2, characterized in that, The processing information also includes the cause of the production line abnormality; the evaluation of the processing effect of the processing solution and the operating status of the production line based on the updated yield information includes: Based on the processing information, according to the work section, the steps, and the operating device, the frequency of abnormality occurrence and the efficiency of abnormality resolution of the production line are statistically analyzed. Based on the frequency of the anomalies and the efficiency of the anomaly resolution, the operating status of the production line is evaluated, and an operating status report of the production line is generated.

5. The method according to claim 1, characterized in that, The user account permissions include first user account permissions, which include at least one or both of setting the preset yield conditions and monitoring the yield information of the production line. Before sending the alarm information to one or more target user accounts with corresponding processing permissions, the method further includes: The alarm information is sent to the user corresponding to the permissions of the first user account.

6. The method according to claim 1, characterized in that, The user account permissions include second user account permissions, which are the permissions to execute the processing scheme. The second user account carries processing scope permissions and is associated with department information. The step of matching the alarm information with preset user account permissions includes: Obtain departmental information related to production line anomalies from the alarm information; Compare the department information related to the production line anomaly with the department information associated with the second user account or the processing scope permissions of the second user account; Based on the comparison results, one or more of the second user accounts are identified as the target user accounts.

7. The method according to claim 6, characterized in that, After evaluating the treatment effect of the treatment scheme, the method further includes: If the processing effect does not meet the preset validity standard, determine the parent user account of the target user account; Based on the alarm information and the processing effect, a notification message is generated and sent to the parent user account.

8. A production line yield control device, characterized in that, include: The monitoring unit is used to obtain yield information from the production line; An alarm unit is used to generate alarm information corresponding to the production line when the yield information does not meet the preset yield conditions. A matching unit is used to match the alarm information with preset user account permissions; The sending unit is used to send the alarm information to one or more target user accounts with corresponding processing permissions based on the matching result; A receiving unit is configured to receive processing information from the target user account, wherein the processing information is a processing plan for the alarm information by the target user account; An evaluation unit is used to update the yield information after receiving the processing information, and to evaluate the processing effect of the processing scheme and the operating status of the production line based on the updated yield information.

9. An electronic device, the electronic device comprising a processor and a memory, characterized in that, The memory is used to store instructions, and the processor is used to call the instructions in the memory to cause the electronic device to execute the production line yield control method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on an electronic device, cause the electronic device to perform the production line yield control method as described in any one of claims 1 to 7.

Images