Production Abnormal Event Handling Methods, Systems, and Controllers

Abstract

This application proposes a method, system, and controller for handling production anomalies, applied in the field of anomaly handling technology. The method includes: acquiring production anomalies; determining the event type of the production anomaly according to preset classification rules; generating an alarm based on the production anomaly to obtain production anomaly alarm information; determining the alarm receiving organization based on the event type, obtaining the alarm receiving organization, and sending the production anomaly alarm information to the alarm receiving organization; after the alarm receiving organization completes the handling of the production anomaly based on the production anomaly alarm information, generating a data analysis chart of the production anomaly. This application uses preset classification rules and alarm push to realize production anomaly handling, improving the efficiency of anomaly handling while ensuring the standardization and timeliness of anomaly handling; at the same time, this application automatically generates data analysis charts based on the anomaly handling results, which can provide reliable data support for production optimization and reduce the recurrence rate of production anomalies.

Description

Technical Field

[0001] This application relates to the field of abnormal event handling technology, and in particular to a method, system, and controller for handling abnormal production events. Background Technology

[0002] In related technologies, with the increasing variety of products and continuous improvement in production capacity, sauce production lines face problems such as frequent changes in planned work orders, increased complexity of fault types due to the growing number of equipment, and difficulty in real-time monitoring of quality control under high-speed production modes. Currently, the notification and transmission of various production anomalies mainly rely on instant messaging tools used by employees. Information transmission is significantly delayed, and after multiple forwardings, it is prone to deviation and distortion, making it difficult for enterprises to carry out effective pre-event risk prevention and post-event review and summary work. Summary of the Invention

[0003] This application aims to address at least one of the technical problems existing in the prior art. To this end, this application proposes a method and system for handling production anomaly events, as well as a controller, designed to handle anomaly events occurring during the production process.

[0004] In a first aspect, embodiments of this application provide a method for handling production anomaly events, the method comprising: Acquire production anomaly events; The event type of the production anomaly event is determined according to a preset classification rule; Based on the aforementioned production anomaly events, alarms are generated to obtain production anomaly event alarm information; The alarm receiving organization is determined according to the event type, and the alarm information of the production anomaly event is sent to the alarm receiving organization. After the alarm receiving organization completes the processing of the production anomaly event based on the production anomaly event alarm information, it generates a data analysis chart of the production anomaly event.

[0005] According to some embodiments of this application, the alarm receiving organization includes a primary alarm receiving organization, a secondary alarm receiving organization, and a tertiary alarm receiving organization. The step of determining the alarm receiving organization based on the event type to obtain the alarm receiving organization includes: Based on the event type, the corresponding primary, secondary, and tertiary alarm receiving organizations are determined.

[0006] According to some embodiments of this application, the method further includes: The urgency of the production anomaly event is determined based on the event type to obtain the event urgency level. The time is determined based on the event type and the event urgency, resulting in the first-level upgrade time and the second-level upgrade time.

[0007] According to some embodiments of this application, sending the production anomaly alarm information to the alarm receiving organization includes: The alarm information regarding the production anomaly event is sent to the primary alarm receiving organization; Based on the first-level escalation time, the production anomaly alarm information is sent to the second-level alarm receiving organization; Based on the second-level upgrade time, the production anomaly alarm information is sent to the third-level alarm receiving organization.

[0008] According to some embodiments of this application, sending the production anomaly alarm information to the secondary alarm receiving organization based on the primary escalation time includes: When the primary alarm receiving organization completes the processing of the production anomaly event based on the production anomaly event alarm information within the primary escalation time, it does not need to send the production anomaly event alarm information to the secondary alarm receiving organization. If the primary alarm receiving organization fails to process the production anomaly event according to the production anomaly event alarm information within the primary escalation time, it shall send the production anomaly event alarm information to the secondary alarm receiving organization.

[0009] According to some embodiments of this application, the step of sending the production anomaly alarm information to the tertiary alarm receiving organization according to the secondary escalation time includes: When the secondary alarm receiving organization completes the processing of the production anomaly event based on the production anomaly event alarm information within the secondary escalation time, it does not need to send the production anomaly event alarm information to the tertiary alarm receiving organization. If the secondary alarm receiving organization fails to process the production anomaly event according to the production anomaly event alarm information within the secondary escalation time, it shall send the production anomaly event alarm information to the tertiary alarm receiving organization.

[0010] Secondly, embodiments of this application provide a production anomaly event handling system for executing the production anomaly event handling method as described in the first aspect, the production anomaly event handling system comprising: The event acquisition module is used to acquire production exception events; The event classification module is used to determine the event type of the production anomaly event according to preset classification rules; The alarm generation module is used to generate alarms based on the production anomaly events and obtain production anomaly event alarm information. The alarm dispatch module is used to determine the alarm receiving organization based on the event type, obtain the alarm receiving organization, and send the production abnormality event alarm information to the alarm receiving organization. The data analysis module is used to generate data analysis charts of the production anomaly after the alarm receiving organization has completed the processing of the production anomaly based on the alarm information.

[0011] Thirdly, embodiments of this application provide a controller, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the production anomaly event handling method described in the first aspect when running the computer program.

[0012] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the production anomaly handling method as described in the first aspect above.

[0013] Fifthly, embodiments of this application provide a computer program product, including a computer program or computer instructions, wherein the computer program or computer instructions are stored in a computer-readable storage medium, a processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, causing the computer device to perform the production anomaly handling method as described in the first aspect above.

[0014] The technical solution according to the embodiments of this application has at least the following beneficial effects: This application proposes a production anomaly event handling method, system, and controller, applied in the field of anomaly event handling technology. The method includes: acquiring production anomalies; determining the event type of the production anomaly event according to preset classification rules; generating an alarm based on the production anomaly event to obtain production anomaly event alarm information; determining the alarm receiving organization based on the event type to obtain the alarm receiving organization, and sending the production anomaly event alarm information to the alarm receiving organization; after the alarm receiving organization completes the handling of the production anomaly event based on the production anomaly event alarm information, generating a data analysis chart of the production anomaly event. This application uses preset classification rules and alarm push to realize production anomaly event handling, which improves the efficiency of anomaly event handling while ensuring the standardization and timeliness of anomaly handling; at the same time, this application automatically generates data analysis charts based on the anomaly handling results, which can provide reliable data support for production optimization and reduce the recurrence rate of production anomalies.

[0015] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0016] The accompanying drawings are used to provide a further understanding of the technical solutions of this application and constitute a part of the specification. They are used together with the embodiments of this application to explain the technical solutions of this application and do not constitute a limitation on the technical solutions of this application.

[0017] Figure 1 This is a flowchart of a production anomaly event handling method provided in one embodiment of this application; Figure 2 This is a flowchart of a production anomaly event handling method provided in another embodiment of this application; Figure 3 This is a flowchart of a production anomaly event handling method provided in another embodiment of this application; Figure 4 This is a flowchart of a production anomaly event handling method provided in an overall embodiment of this application; Figure 5 This is a schematic diagram of the structure of a production anomaly event handling system provided in one embodiment of this application; Figure 6 This is a schematic diagram of a controller for executing a production anomaly event handling method according to an embodiment of this application. Detailed Implementation

[0018] The embodiments of this application are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain this application, and should not be construed as limiting this application.

[0019] In the description of this application, it should be understood that the orientation descriptions, such as up, down, front, back, left, right, etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0020] In the description of this application, "several" means one or more, "more than" means two or more, "greater than," "less than," and "exceeding" are understood to exclude the stated number, while "above," "below," and "within" are understood to include the stated number. The use of "first" and "second" in the description is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the order of the indicated technical features.

[0021] In the description of this application, unless otherwise expressly defined, terms such as "setup," "installation," and "connection" should be interpreted broadly, and those skilled in the art can reasonably determine the specific meaning of the above terms in this application in conjunction with the specific content of the technical solution.

[0022] In some cases, with the increasing variety of products and continuous improvement in production capacity, sauce production lines face problems such as frequent changes in planned work orders, increased complexity of fault types due to the growing number of equipment, and difficulty in real-time monitoring of quality control under high-speed production modes. Currently, the notification and transmission of various production anomalies mainly rely on instant messaging tools used by employees. Information transmission is significantly delayed, and after multiple forwardings, it is prone to deviation and distortion, making it difficult for enterprises to carry out effective pre-event risk prevention and post-event review and summary work.

[0023] Based on the above, this application proposes a method, system, and controller for handling abnormal events in production, aiming to process abnormal events that occur during the production process.

[0024] The various embodiments of the production anomaly handling method of this application will be further described below with reference to the accompanying drawings.

[0025] like Figure 1 As shown, Figure 1 This is a flowchart of a production anomaly event handling method provided in one embodiment of this application; the production anomaly event handling method may include, but is not limited to, steps S110, S120, S130, S140 and S150.

[0026] Step S110: Obtain production anomaly events; Step S120: Determine the event type of the production anomaly event according to the preset classification rules; Step S130: Generate alarms based on production anomaly events to obtain production anomaly event alarm information; Step S140: Determine the alarm receiving organization according to the event type, obtain the alarm receiving organization, and send the production abnormal event alarm information to the alarm receiving organization; Step S150: After the alarm receiving organization completes the processing of the production anomaly event based on the alarm information, it generates a data analysis chart of the production anomaly event.

[0027] In one embodiment, a production anomaly event is acquired; the event type of the production anomaly event is determined according to a preset classification rule; an alarm is generated based on the production anomaly event to obtain production anomaly event alarm information; an alarm receiving organization is determined according to the event type to obtain the alarm receiving organization, and the production anomaly event alarm information is sent to the alarm receiving organization; after the alarm receiving organization completes the processing of the production anomaly event based on the production anomaly event alarm information, a data analysis chart of the production anomaly event is generated. This application uses preset classification rules and alarm push to realize the processing of production anomaly events, which improves the efficiency of anomaly event handling while ensuring the standardization and timeliness of anomaly processing; at the same time, this application automatically generates data analysis charts based on the anomaly processing results, which can provide reliable data support for production optimization and reduce the recurrence rate of production anomalies.

[0028] Understandably, the preset classification rules can match and determine the occurrence, affected objects, and problem attributes of production anomalies, classifying them into quality anomalies, inventory anomalies, equipment anomalies, safety anomalies, production anomalies, and process anomalies, thereby determining the event type of the production anomaly. The event types include quality, inventory, equipment, safety, production, and process.

[0029] It is understandable that alarm receiving organizations include primary alarm receiving organizations, secondary alarm receiving organizations, and tertiary alarm receiving organizations. The alarm receiving organization is determined according to the type of event, including: analyzing the event type to determine the corresponding primary, secondary, and tertiary alarm receiving organizations.

[0030] Understandably, this application can match corresponding alarm receiving organizations for different event types such as quality, inventory, equipment, safety, production, and process, so as to achieve accurate alarm push, avoid cross-departmental buck-passing and response delays, improve the professionalism and timeliness of handling, and reduce the impact of anomalies on production.

[0031] Understandably, once the alarm receiving organizations at all levels have completed the entire process from handling and verification to closure based on the alarm information of production anomalies, the system will automatically summarize, statistically analyze, and visualize the data such as the handling process, response time, handling results, and causes of the anomaly, and generate corresponding production anomaly data analysis charts to provide intuitive data support for subsequent prediction of similar anomalies, process optimization, and accountability.

[0032] For example, if the production anomaly is an inspection timeout and the event type is quality, the corresponding first-level alarm receiving organization is the quality inspector, the second-level alarm receiving organization is the quality inspection manager, and the third-level alarm receiving organization is the factory manager.

[0033] For example, a production anomaly event is an incomplete inspection task, the event type is equipment, and the corresponding first-level alarm receiving organization is the inspection personnel, the second-level alarm receiving organization is the inspection personnel's direct supervisor, and the third-level alarm receiving organization is the plant manager.

[0034] In addition, such as Figure 2 As shown, Figure 2 This is a flowchart of a production anomaly event handling method provided in another embodiment of this application; the production anomaly event handling method may also include, but is not limited to, steps S210 and S220.

[0035] Step S210: Determine the urgency of production anomalies based on event type to obtain event urgency; Step S220: Determine the time based on the event type and urgency to obtain the first-level upgrade time and the second-level upgrade time.

[0036] Understandably, based on the type of event and in conjunction with the degree of production impact, urgency of handling, and safety risk level corresponding to the production anomaly, the urgency of the production anomaly is determined, thereby obtaining the corresponding event urgency level.

[0037] Understandably, different event types and urgency levels correspond to different first-level and second-level escalation times. This allows for refined configuration of anomaly response strategies, ensuring that high-urgency and high-risk anomalies can be escalated and handled more quickly, avoiding delays that could exacerbate production losses, and improving the scientific nature and effectiveness of the overall emergency response.

[0038] Understandably, the urgency of an event can be categorized as routine but not urgent, routine but urgent, important but not urgent, and important but urgent.

[0039] For example, if the production anomaly is an inspection timeout and the event type is quality, the urgency of the production anomaly is determined based on the event type, the degree of production impact, the urgency of handling, and the safety risk level. The corresponding event urgency is then determined to be "normal and not urgent". Based on the event type and the event urgency, the corresponding first-level escalation time is 0.5 hours and the second-level escalation time is 2 hours.

[0040] For example, a production anomaly is an inspection timeout, and the event type is quality. Based on the event type, the corresponding first-level alarm receiving organization is the quality inspector, the second-level alarm receiving organization is the quality inspection manager, and the third-level alarm receiving organization is the factory manager. Simultaneously, based on the event type, and considering the production impact, urgency, and safety risk level of the production anomaly, the urgency level is determined, resulting in a "normal, not urgent" urgency level. Therefore, based on the event type and urgency level, the corresponding first-level escalation time is 0.5 hours, and the second-level escalation time is 2 hours. The production anomaly is first sent to the quality inspector. If the quality inspector handles the production anomaly within 0.5 hours, the alarm is lifted. If the quality inspector does not handle the production anomaly within 0.5 hours, the production anomaly is sent to the quality inspection manager. If the quality inspector handles the production anomaly within 2 hours, the alarm is lifted. If the quality inspector does not handle the production anomaly within 2 hours, the production anomaly is sent to the factory manager.

[0041] In addition, such as Figure 3 As shown, Figure 3 This is a flowchart of a production anomaly event handling method provided in another embodiment of this application; regarding the "sending production anomaly event alarm information to the alarm receiving organization" in the above step S140, it may include, but is not limited to, steps S310, S320 and S330.

[0042] Step S310: Send the production anomaly alarm information to the primary alarm receiving organization; Step S320: Based on the first-level upgrade time, send the production anomaly alarm information to the second-level alarm receiving organization; Step S330: Based on the secondary upgrade time, send the production anomaly alarm information to the tertiary alarm receiving organization.

[0043] Understandably, the alarm information for production anomalies is first pushed to the corresponding primary alarm receiving organization for initial response; then, based on the determined primary escalation time, the alarm information is automatically escalated and pushed to the secondary alarm receiving organization, thus raising the level of response; subsequently, based on the secondary escalation time, the alarm information is further escalated and pushed to the tertiary alarm receiving organization, completing a multi-level progressive alarm notification.

[0044] Understandably, when a primary alarm receiving organization completes the processing of production anomaly feedback based on the production anomaly alarm information within the primary escalation time, it is determined that the production anomaly has been resolved in a closed loop and does not need to be further escalated or transferred to a secondary alarm receiving organization. This avoids duplicate pushes of production anomaly alarm information, reduces redundant notifications across levels, saves management resources, improves handling efficiency, and prevents response chaos and resource waste caused by multi-level linkage.

[0045] It is understandable that if the primary alarm receiving organization fails to process the production anomaly opinion based on the production anomaly alarm information within the primary escalation time, sending the production anomaly alarm information to the secondary alarm receiving organization can effectively prevent the anomaly from escalating due to delays in handling at a single level, ensure that production anomalies are continuously followed up and handled, form a closed-loop supervision mechanism, and improve the success rate of anomaly handling and production support capabilities.

[0046] Understandably, when the secondary alarm receiving organization completes the processing of production anomaly opinions based on the production anomaly alarm information within the secondary escalation time, it is determined that the production anomaly has been resolved in a closed loop and does not need to be further escalated or transferred to the tertiary alarm receiving organization for processing. This avoids the repeated push of production anomaly alarm information, reduces redundant notifications across levels, saves management resources, improves handling efficiency, and at the same time prevents response chaos and resource waste caused by multi-level linkage.

[0047] Understandably, if the secondary alarm receiving organization fails to process the production anomaly feedback based on the production anomaly alarm information within the secondary escalation time, sending the production anomaly alarm information to the tertiary alarm receiving organization can further strengthen the supervision of anomalies, prevent the interruption of the handling chain, ensure that difficult and complex anomalies are handled by higher-level intervention, minimize the continuous impact of anomalies on production, quality and safety, and ensure a closed-loop handling process.

[0048] For example, all production anomaly alarm information is recorded, including event type, time of occurrence, production line, equipment, alarm content, status, and handler; quality-related alarms have simultaneous audible and visual alarms, allowing on-site personnel to quickly be notified and deactivated. For instance, if a filling weight exceeds the lower limit in the filling room of a production line, triggering a quality safety light, a Level 1 alarm is immediately activated. If it is not deactivated within 10 minutes, the information automatically escalates to Level 2 and is pushed to the line supervisor after 10 minutes, continuing until the alarm is deactivated and the record of the excess is retained.

[0049] Based on the production anomaly event handling methods of the above embodiments, the following are embodiments of the production anomaly event handling methods of this application.

[0050] like Figure 4 As shown, Figure 4 This is a flowchart of a production anomaly event handling method provided in an overall embodiment of this application.

[0051] The process involves: acquiring production anomalies; determining the event type based on preset classification rules; generating alarms based on the anomalies; determining the urgency level of the anomalies based on their event type; and determining the time frame for escalation based on the event type and urgency level. The process also includes analyzing the event type to identify the corresponding primary, secondary, and tertiary alarm receiving organizations and sending the alarm information to them. Once the receiving organizations have processed the anomalies based on the alarm information, a data analysis chart is generated. This application utilizes preset classification rules and alarm push notifications to handle production anomalies, improving efficiency while ensuring standardized and timely processing. Furthermore, the automatic generation of data analysis charts based on the anomaly processing results provides reliable data support for production optimization and reduces the recurrence rate of production anomalies.

[0052] Understandably, when a primary alarm receiving organization completes the processing of production anomaly feedback based on the production anomaly alarm information within the primary escalation time, it is determined that the production anomaly has been resolved in a closed loop and does not need to be further escalated or transferred to a secondary alarm receiving organization. This avoids duplicate pushes of production anomaly alarm information, reduces redundant notifications across levels, saves management resources, improves handling efficiency, and prevents response chaos and resource waste caused by multi-level linkage.

[0053] It is understandable that if the primary alarm receiving organization fails to process the production anomaly opinion based on the production anomaly alarm information within the primary escalation time, sending the production anomaly alarm information to the secondary alarm receiving organization can effectively prevent the anomaly from escalating due to delays in handling at a single level, ensure that production anomalies are continuously followed up and handled, form a closed-loop supervision mechanism, and improve the success rate of anomaly handling and production support capabilities.

[0054] Understandably, when the secondary alarm receiving organization completes the processing of production anomaly opinions based on the production anomaly alarm information within the secondary escalation time, it is determined that the production anomaly has been resolved in a closed loop and does not need to be further escalated or transferred to the tertiary alarm receiving organization for processing. This avoids the repeated push of production anomaly alarm information, reduces redundant notifications across levels, saves management resources, improves handling efficiency, and at the same time prevents response chaos and resource waste caused by multi-level linkage.

[0055] Understandably, if the secondary alarm receiving organization fails to process the production anomaly feedback based on the production anomaly alarm information within the secondary escalation time, sending the production anomaly alarm information to the tertiary alarm receiving organization can further strengthen the supervision of anomalies, prevent the interruption of the handling chain, ensure that difficult and complex anomalies are handled by higher-level intervention, minimize the continuous impact of anomalies on production, quality and safety, and ensure a closed-loop handling process.

[0056] Based on the production anomaly event handling methods of the above embodiments, the following are embodiments of the production anomaly event handling system of this application.

[0057] like Figure 5 As shown, Figure 5 This is a schematic diagram of the structure of a production anomaly event handling system provided in one embodiment of this application; In one embodiment, the production anomaly event handling system includes: The event acquisition module is used to acquire production exception events; The event classification module is used to determine the event type of production anomalies according to preset classification rules; The alarm generation module is used to generate alarms based on production anomaly events and obtain production anomaly event alarm information; The alarm dispatch module is used to determine the alarm receiving organization based on the event type, obtain the alarm receiving organization, and send the alarm information of the production abnormal event to the alarm receiving organization. The data analysis module is used to generate data analysis charts of production anomalies after the receiving organization has completed the processing of the production anomaly based on the alarm information.

[0058] The content of the above-described production anomaly handling method embodiments is applicable to the production anomaly handling system embodiments. The specific functions implemented in this production anomaly handling system embodiment are the same as those in the above-described production anomaly handling method embodiments, and the beneficial effects achieved are also the same as those achieved in the above-described production anomaly handling method embodiments.

[0059] Based on the production anomaly handling methods of the above embodiments, the following presents various embodiments of the controller, computer-readable storage medium, and computer program product of this application.

[0060] like Figure 6 As shown, Figure 6 This is a schematic diagram of a controller for executing a production anomaly handling method according to an embodiment of this application. The controller 700 implemented in this application includes: a processor 710, a memory 720, and a computer program stored in the memory 720 and executable on the processor 710, wherein... Figure 6The example uses a processor 710 and a memory 720.

[0061] The processor 710 and memory 720 can be connected via a bus or other means. Figure 6 Taking the example of a connection between China and Israel via a bus.

[0062] Memory 720, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory 720 may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 720 may optionally include remotely located memories 720 relative to processor 710, which can be connected to controller 700 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0063] Those skilled in the art will understand that Figure 6 The device structure shown does not constitute a limitation on the controller 700 and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0064] exist Figure 6 In the controller 700 shown, the processor 710 can be used to call the control program stored in the memory 720, thereby implementing the production anomaly event handling method described above. Specifically, the non-transitory software program and instructions required to implement the production anomaly event handling method of the above embodiment are stored in the memory 720, and when executed by the processor 710, the production anomaly event handling method of the above embodiment is executed.

[0065] It is worth noting that, since the controller 700 of this application embodiment can execute the production abnormal event handling method of any of the above embodiments, the specific implementation method and technical effect of the controller 700 of this application embodiment can refer to the specific implementation method and technical effect of the production abnormal event handling method of any of the above embodiments.

[0066] Furthermore, one embodiment of this application provides a computer-readable storage medium storing computer-executable instructions for performing the aforementioned production anomaly handling method. Exemplarily, the above-described method is executed... Figures 1 to 4 The methods and steps in the text.

[0067] It is worth noting that, since the computer-readable storage medium of this application embodiment can execute the production abnormal event handling method of any of the above embodiments, the specific implementation and technical effects of the computer-readable storage medium of this application embodiment can be referred to the specific implementation and technical effects of the production abnormal event handling method of any of the above embodiments.

[0068] Furthermore, one embodiment of this application also provides a computer program product, including a computer program or computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform the aforementioned production anomaly handling method. Exemplarily, the above-described method is performed... Figures 1 to 4 The methods and steps in the text.

[0069] It is worth noting that, since the computer program product of this application embodiment can execute the production abnormal event handling method of any of the above embodiments, the specific implementation method and technical effect of the computer program product of this application embodiment can refer to the specific implementation method and technical effect of the production abnormal event handling method of any of the above embodiments.

[0070] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically include computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0071] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0072] In the several embodiments provided in this application, it should be understood that the disclosed systems, instruments, and methods can be implemented in other ways. For example, the instrument embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between instruments or units may be electrical, mechanical, or other forms. Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0073] It should also be understood that the various implementation methods provided in this application can be combined arbitrarily to achieve different technical effects.

[0074] The above provides a detailed description of the preferred embodiments of this application. However, this application is not limited to the above-described embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for handling production anomaly events, characterized in that, The method includes: Acquire production anomaly events; The event type of the production anomaly event is determined according to a preset classification rule; Based on the aforementioned production anomaly events, alarms are generated to obtain production anomaly event alarm information; The alarm receiving organization is determined according to the event type, and the alarm information of the production anomaly event is sent to the alarm receiving organization. After the alarm receiving organization completes the processing of the production anomaly event based on the production anomaly event alarm information, it generates a data analysis chart of the production anomaly event.

2. The method according to claim 1, characterized in that, The alarm receiving organization includes a primary alarm receiving organization, a secondary alarm receiving organization, and a tertiary alarm receiving organization. The process of determining the alarm receiving organization based on the event type, resulting in the alarm receiving organization, includes: Based on the event type, the corresponding primary, secondary, and tertiary alarm receiving organizations are determined.

3. The method according to claim 2, characterized in that, The method further includes: The urgency of the production anomaly event is determined based on the event type to obtain the event urgency level. The time is determined based on the event type and the event urgency, resulting in the first-level upgrade time and the second-level upgrade time.

4. The method according to claim 3, characterized in that, Sending the production anomaly alarm information to the alarm receiving organization includes: The alarm information regarding the production anomaly event is sent to the primary alarm receiving organization; Based on the first-level escalation time, the production anomaly alarm information is sent to the second-level alarm receiving organization; Based on the second-level upgrade time, the production anomaly alarm information is sent to the third-level alarm receiving organization.

5. The method according to claim 4, characterized in that, The step of sending the production anomaly alarm information to the secondary alarm receiving organization according to the primary escalation time includes: When the primary alarm receiving organization completes the processing of the production anomaly event based on the production anomaly event alarm information within the primary escalation time, it does not need to send the production anomaly event alarm information to the secondary alarm receiving organization. If the primary alarm receiving organization fails to process the production anomaly event according to the production anomaly event alarm information within the primary escalation time, it shall send the production anomaly event alarm information to the secondary alarm receiving organization.

6. The method according to claim 5, characterized in that, The step of sending the production anomaly alarm information to the tertiary alarm receiving organization according to the secondary upgrade time includes: When the secondary alarm receiving organization completes the processing of the production anomaly event based on the production anomaly event alarm information within the secondary escalation time, it does not need to send the production anomaly event alarm information to the tertiary alarm receiving organization. If the secondary alarm receiving organization fails to process the production anomaly event according to the production anomaly event alarm information within the secondary escalation time, it shall send the production anomaly event alarm information to the tertiary alarm receiving organization.

7. A production anomaly event handling system, characterized in that, The production anomaly handling system is configured to perform the production anomaly handling method as described in any one of claims 1-6, and comprises: The event acquisition module is used to acquire production exception events; The event classification module is used to determine the event type of the production anomaly event according to preset classification rules; The alarm generation module is used to generate alarms based on the production anomaly events and obtain production anomaly event alarm information. The alarm dispatch module is used to determine the alarm receiving organization based on the event type, obtain the alarm receiving organization, and send the production abnormality event alarm information to the alarm receiving organization. The data analysis module is used to generate data analysis charts of the production anomaly after the alarm receiving organization has completed the processing of the production anomaly based on the alarm information.

8. A controller, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, performs the production anomaly handling method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The device stores computer-executable instructions for performing the production anomaly handling method as described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program or computer instructions, characterized in that, The computer program or the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer program or the computer instructions from the computer-readable storage medium and executes the computer program or the computer instructions, causing the computer device to perform the production anomaly handling method as described in any one of claims 1 to 6.

Images