Cooperative exception handling method and system for production-type information system
By introducing exception handling components and automated notification mechanisms in production-type information systems, we quickly identify and handle collaborative exceptions, and solve the problem of difficult identification and notification of collaborative exceptions in a timely manner, improving the efficiency of problem solving, and ensuring the stability of enterprise production and operation .
Patent Information
- Application Number
- CN202411480079.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-23
- Publication Date
- 2024-11-22
AI Technical Summary
In production-type information systems, collaboration abnormalities are difficult to be identified and notified in a timely manner, resulting in delays in problem resolution and affecting the company's production activities and business management.
By introducing exception handling components into the system, determining the pending node in response to user triggering instructions, displaying exception scene templates, and automatically creating and sending exception handling tasks to the target person in charge, achieving rapid identification and notification.
It improves the abnormal response speed, ensures that problems can be quickly identified and communicated to the correct responsible persons, reduces the risk of production interruptions, and effectively guarantees the production activities and business management of the enterprise.
Smart Images

Figure CN119005665A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a collaborative exception handling method and system for a production-type information system. Background Art
[0002] In production-oriented information systems, enterprises often face problems with abnormal upstream and downstream collaboration. These abnormal collaboration problems may occur in multiple business processes, such as procurement processes, production processes, and sales processes. These processes usually include multiple nodes, such as purchase requisitions, purchase orders, purchase quality inspection, purchase receipt, purchase warehousing, purchase returns, etc.
[0003] In related technologies, enterprises use information systems to manage their business processes. These systems usually include data entry, process monitoring and reporting functions. However, when collaboration anomalies occur, such as the supplier delivers goods to the door but the buyer fails to enter the purchase order in time, resulting in the warehouse keeper being unable to receive the goods, or the operator reporting work and finding that the previous process has not been reported, resulting in the inability to report work in time.
[0004] It can be seen that when collaboration anomalies occur, the system often cannot identify the problem in a timely manner and notify the relevant responsible persons, resulting in delayed problem solving, which in turn affects the company's production activities and business management. Summary of the invention
[0005] The embodiments of the present application provide a collaborative exception handling method and system for a production information system. In order to have a basic understanding of some aspects of the disclosed embodiments, a simple summary is given below. This summary is not a general review, nor is it intended to identify key / important components or describe the scope of protection of these embodiments. Its only purpose is to present some concepts in a simple form as a preface to the detailed description that follows.
[0006] In a first aspect, an embodiment of the present application provides a collaborative exception handling method for a production information system, the method comprising: In response to a trigger instruction for an exception handling component displayed on a system operation interface, determine an abnormal node to be processed; wherein the node to be processed is a node of a business link with an abnormality in a node set corresponding to a business process with a collaboration abnormality in a business process set, the business process set is obtained by standardizing all business processes pre-defined in a production information system, and the node set is obtained by dividing the business process according to different preset business links; Displaying an abnormal scenario template set of a node to be processed, each abnormal scenario template in the abnormal scenario template set is module information pre-set based on multiple abnormal scenarios existing in the node to be processed and used to characterize business process abnormalities; In response to a selection instruction for the displayed abnormal scene template set, obtaining a target abnormal scene template indicated by the selection instruction in the abnormal scene template set; Based on the target exception scenario template, an exception handling task is created and sent to the client of the target person in charge. The target person in charge is pre-set for the node to be processed.
[0007] Optionally, determining an abnormal node to be processed includes: Determine a link icon for representing a business link indicated by the trigger instruction, where the link icon carries a target business process tag and a target business link tag; Obtaining a business process set obtained by standardizing all business processes pre-defined in the production information system; Compare the target business process tag with the business process tag carried by each business process in the business process set to find out the business process corresponding to the business process tag that is the same as the target business process tag as the business process with collaboration anomaly; The business link mark carried by each node in the node set corresponding to the business process with collaborative anomalies is compared with the target business link mark to find out the node corresponding to the business link mark that is the same as the target business link mark as the node to be processed with the anomaly.
[0008] Optionally, determining a link icon for representing a business link indicated by the trigger instruction includes: Get the target pixel coordinates of the user's click on the screen corresponding to the trigger instruction; According to the preset pixel parameters, a two-dimensional coordinate system is created for displaying the interface; Projecting a set of link icons used to represent all business links in the production information system into a two-dimensional coordinate system to obtain a set of pixel coordinates of each link icon; Calculate the similarity distance between the target pixel coordinates and each pixel coordinate in the pixel coordinate set of each link icon; The link icon corresponding to the pixel coordinate set to which the pixel coordinates with the smallest similarity distance belong is used as the link icon for representing the business link indicated by the trigger instruction; wherein, The similarity distance calculation formula is:
[0009] in, is the pixel coordinates of the target pixel and the pixel coordinates of each link icon. The similarity distance between pixel coordinates, and are the horizontal and vertical coordinates of the target pixel coordinates, respectively. and They are the pixel coordinates of each link icon. The horizontal and vertical coordinates of the pixel coordinates.
[0010] Optionally, generate a node set by following the steps below, including: Traverse all pre-defined business processes in the production information system; Standardize all business processes to obtain a business process set; Get the preset different business links corresponding to each business process in the business process set; According to the preset different business links corresponding to each business process, each business process is divided to obtain a node set corresponding to each business process.
[0011] Optionally, all business processes are standardized to obtain a business process set, including: Obtain the business execution order of each business process in all business processes; According to the business execution sequence, all business processes are checked for integrity to determine whether each business process has a logical start point and a logical end point; When each business process has a logical start point and a logical end point, each business process is classified and aggregated to obtain a business process set; wherein, The business process set includes procurement process, production process and sales process.
[0012] Optionally, each business process is divided according to different preset business links corresponding to each business process to obtain a node set corresponding to each business process, including: In the case where the business process is a procurement process, different preset business links corresponding to the procurement process are determined. The different preset business links corresponding to the procurement process include a demand identification link, a supplier selection link, an order generation link, a goods reception link, and a payment processing link; From the process information of the procurement process, obtain the process information corresponding to the demand identification stage, supplier selection stage, order generation stage, goods receiving stage and payment processing stage respectively; Based on the acquired process information corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link, nodes corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link are created respectively; All created nodes are used as the node set corresponding to the procurement process.
[0013] Optionally, the target exception scenario template is module information for characterizing a business process exception, and the module information is a visual interactive interface, and the interactive interface carries a parameter ID; Create an exception handling task based on the target exception scenario template, including: Based on the parameter ID, obtain the abnormal type information, impact range information, processing steps and urgency information of the target abnormal scenario template as task parameters; Fill the task parameters into the interactive interface one by one to obtain an interactive interface with the parameters; Treat the interactive interface with parameters as an exception handling task.
[0014] Optionally, the parameter ID includes the exception type ID, the impact scope ID, the processing steps, and the urgency ID; Based on the parameter ID, obtain the exception type information, impact range information, processing steps and urgency information of the target exception scenario template, including: Build an executable SQL query statement based on the exception type ID, impact range ID, processing steps, and urgency ID; Execute executable SQL query statements to obtain the exception type information, impact range information, processing steps and urgency information of the target exception scenario template from the database.
[0015] Optionally, the interactive interface consists of an exception type input box, an impact range drop-down menu, a processing step text area, and an urgency slider; Fill the task parameters into the interactive interface one by one to obtain an interactive interface with parameters, including: Fill the exception type information into the exception type input box to obtain the exception type input box with parameters; Mapping and associating the impact range information with the impact range drop-down menu to obtain the impact range drop-down menu with parameters; Fill the processing steps into the processing step text area to obtain a processing step text area with parameters; Mapping and associating the urgency information with the urgency slider to obtain an urgency slider with parameters; An exception type input box with parameters, an impact range drop-down menu with parameters, a processing step text area with parameters, and an urgency slider with parameters are used as the interactive interface with parameters.
[0016] In a second aspect, an embodiment of the present application provides a collaborative exception handling system for a production information system, the system comprising: A to-be-processed node determination module is used to respond to a trigger instruction for an exception handling component displayed on a system operation interface, and determine an abnormal to-be-processed node; wherein the to-be-processed node is a node of an abnormal business link in a node set corresponding to a business process with a collaboration abnormality in a business process set, the business process set is obtained by standardizing all business processes pre-defined in a production information system, and the node set is obtained by dividing the business process according to different preset business links; An abnormal scenario template set display module is used to display an abnormal scenario template set of a node to be processed, each abnormal scenario template in the abnormal scenario template set is module information pre-set based on multiple abnormal scenarios existing in the node to be processed and used to characterize business process abnormalities; A target abnormal scene template acquisition module, configured to acquire a target abnormal scene template indicated by the selection instruction in the abnormal scene template set in response to a selection instruction for the displayed abnormal scene template set; The exception handling task sending module is used to create an exception handling task based on the target exception scenario template and send the exception handling task to the client of the target person in charge. The target person in charge is pre-set for the processing node.
[0017] The technical solution provided by the embodiments of the present application may have the following beneficial effects: In an embodiment of the present application, in a production-type information system, business processes are standardized, and each process is subdivided into multiple nodes, each node representing a business link. When an exception occurs, the system can quickly locate the node to be processed where the exception occurs through the standardized process node. At the same time, the system can display a set of exception scenario templates associated with the node to be processed. Each template is pre-set for possible exceptions. By selecting the corresponding exception scenario template, the system will automatically create a detailed exception handling task and send it to the client of the pre-specified target person in charge. This automated exception identification and notification process greatly improves the exception response speed, ensures that the problem can be quickly identified and communicated to the correct person in charge, and the rapid problem-solving mechanism not only reduces the risk of production interruption, but also causes the problem to be resolved in the shortest time, thereby effectively guaranteeing the company's production activities and business management.
[0018] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0020] Figure 1It is a flowchart of a collaborative exception handling method for a production information system provided in an embodiment of the present application; Figure 2 It is a data representation intent of all business processes predefined in a production information system provided by this application; Figure 3 This is a partial information diagram of a business process set obtained after all business processes are standardized, as provided by the present application; Figure 4 This is a UI interface diagram provided by this application; Figure 5 This is a schematic diagram of an exception handling task parameter configuration interface provided by this application; Figure 6 It is a structural diagram of a collaborative exception handling system for a production information system provided in an embodiment of the present application; Figure 7 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0021] The following description and the accompanying drawings sufficiently illustrate specific embodiments of the present application to enable those skilled in the art to practice them.
[0022] It should be clear that the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.
[0023] When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are only examples of systems and methods consistent with some aspects of the present application as detailed in the attached claims.
[0024] In the description of the present application, it should be understood that the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to the specific circumstances. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0025] The present application provides a collaborative exception handling method and system for a production information system to solve the problems existing in the above-mentioned related technical problems. In an embodiment of the present application, in a production information system, the business process is standardized, each process is subdivided into multiple nodes, and each node represents a business link. When an exception occurs, the system can quickly locate the node to be processed with the exception through the standardized process node. At the same time, the system can display a set of exception scenario templates associated with the node to be processed. Each template is pre-set for possible exceptions. By selecting the corresponding exception scenario template, the system will automatically create a detailed exception handling task and send it to the client of the pre-specified target person in charge. This automated exception identification and notification process greatly improves the exception response speed, ensures that the problem can be quickly identified and communicated to the correct person in charge, and the rapid problem solving mechanism not only reduces the risk of production interruption, but also causes the problem to be solved in the shortest time, so that the production activities and business management of the enterprise are effectively guaranteed. The following exemplary embodiments are used for detailed description.
[0026] The following will be combined with the attached Figure 1 -Attached Figure 5 , a detailed introduction is given to the collaborative exception handling method for a production-type information system provided in an embodiment of the present application. The method can be implemented by a computer program and can be run on a collaborative exception handling system for a production-type information system based on the von Neumann architecture. The computer program can be integrated into an application or run as an independent tool application.
[0027] See also Figure 1 , which is a flowchart of a collaborative exception handling method for a production information system according to an embodiment of the present application. Figure 1 As shown, the method of the embodiment of the present application may include the following steps: S101, in response to a trigger instruction for an exception handling component displayed on a system operation interface, determining an abnormal node to be processed; wherein the node to be processed is a node of an abnormal business link in a node set corresponding to a business process with a collaboration abnormality in a business process set, the business process set is obtained by standardizing all business processes pre-defined in a production information system, and the node set is obtained by dividing the business process according to different preset business links; Among them, the system operation interface is a graphical interface for users to interact with the computer system, which provides various controls and indicators for users to operate. The exception handling component is a part of the system operation interface that is specifically used to handle abnormal situations, such as buttons. Trigger instructions are instructions issued by users through the operation interface to activate or start a function or component in the system. Collaboration exceptions are exceptions that occur in the collaborative links of business processes, such as information transmission errors, resource allocation conflicts, etc. Business links are specific links or steps in a business process, such as procurement, production, sales, etc.
[0028] In some embodiments, the user clicks on the "Exception Handling Component" on the system operation interface, triggering a trigger instruction. The system responds to the trigger instruction and begins to check various business processes. The system finds that there is a delay in the "supplier delivery" link in the procurement process, which is a collaborative exception. At this time, the system recognizes that the specific node corresponding to this exception is "Receipt Confirmation". The system maintains a set of business processes, which includes procurement processes, production processes, and sales processes, all of which have been standardized. The procurement process is divided into multiple nodes, such as "demand approval", "order generation", "supplier delivery" and "receipt confirmation". In this example, the "receipt confirmation" node becomes a pending node due to supplier delivery delays.
[0029] In some embodiments of the present application, the specific process of determining an abnormal node to be processed includes: determining a link icon indicated by a trigger instruction for representing a business link, the link icon carrying a target business process tag and a target business link tag; obtaining a business process set obtained by performing process standardization processing on all business processes pre-defined in a production information system; comparing the target business process tag with the business process tag carried by each business process in the business process set to find out the business process corresponding to the business process tag that is the same as the target business process tag, as the business process with a collaboration abnormality; comparing the business link tag carried by each node in the node set corresponding to the business process with a collaboration abnormality with the target business link tag, to find out the node corresponding to the business link tag that is the same as the target business link tag, as the node to be processed with an abnormality.
[0030] Among them, the link icon is a graphic or symbol used to represent a specific business link in the system operation interface. The target business process tag and the target business link tag are unique identifiers associated with the link icon, which are used to identify the business process and business link respectively. The business process set is a collection of all pre-defined and process-standardized business processes in the enterprise. The business process tag is a unique identifier for each business process, which is used to distinguish different business processes. A business process with collaboration anomalies is a business process with collaboration problems in the business process set. The business link tag is a unique identifier for each business link, which is used to distinguish different business links.
[0031] In an embodiment of the present application, by accurately identifying the target business process and business link tags carried by the link icon, the system can effectively locate the specific abnormal node. This process first involves obtaining and comparing the business process tags to determine the specific business process where the abnormality is located. Subsequently, the system further analyzes the set of nodes in the process to find the abnormal nodes that match the target business link tags. This method improves the accuracy and response speed of anomaly detection, ensuring that problems can be quickly identified and handled in a timely manner, thereby reducing production delays and improving enterprise operational efficiency.
[0032] In some embodiments of the present application, the specific process of determining the link icon for representing the business link indicated by the trigger instruction includes: obtaining the target pixel coordinates of the user clicked on the screen corresponding to the trigger instruction; creating a two-dimensional coordinate system for displaying the interface according to the preset pixel parameters; projecting the link icon set used to represent all business links in the production information system into the two-dimensional coordinate system to obtain the pixel coordinate set of each link icon; calculating the similarity distance between the target pixel coordinates and each pixel coordinate in the pixel coordinate set of each link icon; using the link icon corresponding to the pixel coordinate set to which the pixel coordinate with the smallest similarity distance belongs as the link icon for representing the business link indicated by the trigger instruction; wherein the similarity distance calculation formula is:
[0033] in, is the pixel coordinates of the target pixel and the pixel coordinates of each link icon. The similarity distance between pixel coordinates, and are the horizontal and vertical coordinates of the target pixel coordinates, respectively. and They are the pixel coordinates of each link icon. The horizontal and vertical coordinates of the pixel coordinates.
[0034] The target pixel coordinates are the coordinates of where the user clicks on the screen ( , ). Two-dimensional coordinate system: A coordinate system defined by preset pixel parameters, usually with the upper left corner of the screen as the origin (0,0). The link icon set is the icons of all business links in the production information system. The pixel coordinate set of the link icon is the coordinate of each link icon in the two-dimensional coordinate system ( , ).
[0035] For example, suppose the coordinates clicked by the user are (150,300)(150,300), the coordinate set of a link icon is: [(100,200),(150,300),(200,400)][(100,200),(150,300),(200,400)], the threshold is set to 50 pixels. At this time, d1=(150−100) 2 +(300−200) 2 = square root of 5000 = 70.71; d2 = (150 − 150)2 + (300 − 300)2 = 0; d3 = (150 − 200)2 + (300 − 400)2 = square root of 10000 = 100; Only when the distance d2 = 0 of the second coordinate is less than the threshold 50, the icon corresponding to the coordinate set to which the second coordinate belongs is recognized as the target icon clicked by the user.
[0036] S102, displaying an abnormal scenario template set of the node to be processed, where each abnormal scenario template in the abnormal scenario template set is module information pre-set based on multiple abnormal scenarios existing in the node to be processed and used to characterize business process abnormalities; Among them, the abnormal scenario template set is a set of predefined templates, each template represents an abnormal scenario that occurs, describes a specific type of abnormal situation, including the characteristics of the abnormality, possible causes and recommended processing steps. Module information refers to the information that constitutes the system function module, specifically a set of data and instructions used to characterize business process abnormalities.
[0037] In some embodiments, during the production process, the system detects a delay in the supply of raw materials, which causes the node "waiting for raw materials" to become a pending node. After the system identifies the pending node, it displays a set of abnormal scenario templates, which includes all abnormal scenario templates that may be related to the "waiting for raw materials" node. For example, the upstream has not reported the work, the buyer has not placed an order, the warehouse keeper has not shipped out, and the technician has not set the BOM.
[0038] In some embodiments of the present application, a node set is generated according to the following steps, including: traversing all business processes pre-defined in the production information system; standardizing all business processes to obtain a business process set; obtaining different preset business links corresponding to each business process in the business process set; dividing each business process according to the different preset business links corresponding to each business process to obtain a node set corresponding to each business process.
[0039] Among them, production information systems refer to information systems used to support the operation of production enterprises, such as ERP (Enterprise Resource Planning) systems, which help manage the production, supply chain, finance and other business processes of enterprises. Process standardization is to format and unify business processes according to certain standards to ensure the consistency and manageability of the processes.
[0040] In an embodiment of the present application, by traversing all pre-defined business processes in a production information system and standardizing these processes, an enterprise can build a unified set of business processes. This set allows each business process to be clearly decomposed into different preset business links, and then further divided into node sets. This method not only improves the transparency and manageability of business processes, but also enables enterprises to more effectively monitor and manage the execution of each business link, thereby improving the efficiency and response speed of the entire production and supply chain. In addition, this also provides a clear framework for anomaly detection and problem solving, allowing enterprises to quickly locate problems and take action.
[0041] Among them, all business processes predefined in the production information system, such as Figure 2 As shown, Process Name is the name of the business process, such as "Purchase Process", "Production Process", etc. Description is a brief description of the business process. Owner is the manager or team leader responsible for the business process. Start Date / End Date is the planned start and end time of the business process. Status is the current status of the business process, such as "Active", "Paused", or "Complete".
[0042] In some embodiments of the present application, the specific process of obtaining a business process set after standardizing all business processes includes: obtaining the business execution order of each business process in all business processes; performing integrity checks on each business process in all business processes according to the business execution order to determine whether each business process has a logical start point and a logical end point; if each business process has a logical start point and a logical end point, classifying and aggregating each business process to obtain a business process set; wherein the business process set includes a procurement process, a production process, and a sales process. Among them, some information of the business process set obtained after standardizing all business processes, such as Figure 3shown.
[0043] Specifically, each business process is divided according to the preset different business links corresponding to each business process, and the specific process of obtaining the node set corresponding to each business process includes: when the business process is a procurement process, determining the preset different business links corresponding to the procurement process, the preset different business links corresponding to the procurement process include demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link; from the process information of the procurement process, respectively obtaining the process information corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link; based on the obtained process information corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link, respectively create nodes corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link; all created nodes are used as the node set corresponding to the procurement process.
[0044] S103, in response to a selection instruction for the displayed abnormal scene template set, obtaining a target abnormal scene template indicated by the selection instruction in the abnormal scene template set; The selection instruction is an instruction issued by the user, which is used to select a specific item from the options. The target abnormal scenario template is a specific abnormal scenario template selected by the user, which will be used to handle the current abnormality.
[0045] In some embodiments, assume that a production information system is running and the system detects a supply chain disruption problem. The system displays a series of abnormal scenario templates on the user interface, such as "supply chain disruption", "equipment failure", "order cancellation", etc. Figure 4 In the UI shown, the user reviews the available templates and selects the "supply chain interruption" template to respond to the current abnormal situation. The system recognizes and responds to the user's selection instruction by obtaining the "supply chain interruption" template selected by the user. Based on the user's selection, the system retrieves the "supply chain interruption" template from the abnormal scenario template collection and prepares to use the processing steps and strategies defined in the template to resolve the abnormality.
[0046] S104, based on the target exception scenario template, create an exception handling task, and send the exception handling task to the client of the target person in charge, where the target person in charge is pre-set for the node to be processed.
[0047] The target exception scenario template is a module information for characterizing a business process exception. The module information is a visual interactive interface that carries a parameter ID.
[0048] In an embodiment of the present application, the specific process of creating an exception handling task based on the target exception scenario template includes: based on the parameter ID, obtaining the exception type information, impact range information, processing steps and urgency information of the target exception scenario template as task parameters; filling the task parameters into the interactive interface one by one to obtain an interactive interface with parameters; and using the interactive interface with parameters as an exception handling task.
[0049] Among them, the parameter ID is a unique identifier used to specify or identify a specific exception scenario template. Exception type information is data that describes the nature and characteristics of the exception, such as "system failure", "data leakage", etc. Impact scope information is data that describes the system part or business process affected by the exception. Processing steps are a series of ordered actions or measures used to respond to and resolve exceptions. Urgency information is priority information that indicates how quickly the exception needs to be responded to and resolved. The interactive interface is a graphical user interface (GUI) for users to interact with the system.
[0050] In an embodiment of the present application, by using parameter IDs to automatically obtain detailed information in the target exception scenario template (including exception type, scope of impact, processing steps, and urgency), the system is able to dynamically generate a set of task parameters for a specific exception. These parameters are then filled into the interactive interface to create an interface with all the necessary information, allowing users to interact directly with the system to quickly respond to abnormal situations. This approach not only improves the efficiency and accuracy of exception handling, but also enhances the user experience because users can immediately see all relevant information and take action accordingly. Ultimately, this approach to automation and information integration helps ensure that exceptions are handled in a timely and effective manner.
[0051] The parameter ID includes the exception type ID, impact range ID, processing steps and urgency ID.
[0052] In some embodiments of the present application, based on the parameter ID, the specific process of obtaining the exception type information, impact range information, processing steps and urgency information of the target exception scenario template is: constructing an executable SQL query statement according to the exception type ID, impact range ID, processing steps and urgency ID; executing the executable SQL query statement to obtain the exception type information, impact range information, processing steps and urgency information of the target exception scenario template from the database.
[0053] The interactive interface consists of an exception type input box, an impact range drop-down menu, a processing step text area, and an urgency slider.
[0054] In some embodiments of the present application, task parameters are filled into the interactive interface one by one to obtain an interactive interface with parameters, which specifically includes: filling exception type information into the exception type input box to obtain an exception type input box with parameters; mapping and associating the impact range information with the impact range drop-down menu to obtain an impact range drop-down menu with parameters; filling the processing steps into the processing steps text area to obtain a processing steps text area with parameters; mapping and associating the urgency information with the urgency slider to obtain an urgency slider with parameters; using the exception type input box with parameters, the impact range drop-down menu with parameters, the processing steps text area with parameters, and the urgency slider with parameters as an interactive interface with parameters.
[0055] Among them, the exception handling task parameter configuration interface is as follows: Figure 5 shown.
[0056] In an embodiment of the present application, in a production-type information system, business processes are standardized, and each process is subdivided into multiple nodes, each node representing a business link. When an exception occurs, the system can quickly locate the node to be processed where the exception occurs through the standardized process node. At the same time, the system can display a set of exception scenario templates associated with the node to be processed. Each template is pre-set for possible exceptions. By selecting the corresponding exception scenario template, the system will automatically create a detailed exception handling task and send it to the client of the pre-specified target person in charge. This automated exception identification and notification process greatly improves the exception response speed, ensures that the problem can be quickly identified and communicated to the correct person in charge, and the rapid problem-solving mechanism not only reduces the risk of production interruption, but also causes the problem to be resolved in the shortest time, thereby effectively guaranteeing the company's production activities and business management.
[0057] The following is a system embodiment of the present application, which can be used to execute the method embodiment of the present application. For details not disclosed in the system embodiment of the present application, please refer to the method embodiment of the present application.
[0058] See also Figure 6 , which shows a schematic diagram of the structure of a collaborative exception handling system for a production information system provided by an exemplary embodiment of the present application. The collaborative exception handling system for a production information system can be implemented as all or part of an electronic device through software, hardware, or a combination of both. The system 1 includes a to-be-processed node determination module 10, an abnormal scenario template set display module 20, a target abnormal scenario template acquisition module 30, and an abnormal processing task sending module 40.
[0059] The to-be-processed node determination module 10 is used to determine the to-be-processed node with an exception in response to a trigger instruction for the exception handling component displayed on the system operation interface; wherein the to-be-processed node is a node of a business link with an exception in a node set corresponding to a business process with a collaboration exception in a business process set, the business process set is obtained by standardizing all business processes pre-defined in a production information system, and the node set is obtained by dividing the business process according to different preset business links; The abnormal scenario template set display module 20 is used to display the abnormal scenario template set of the node to be processed, and each abnormal scenario template in the abnormal scenario template set is module information pre-set based on multiple abnormal scenarios existing in the node to be processed and used to characterize business process abnormalities; A target abnormal scene template acquisition module 30, configured to acquire a target abnormal scene template indicated by the selection instruction in the abnormal scene template set in response to a selection instruction for the displayed abnormal scene template set; The exception handling task sending module 40 is used to create an exception handling task based on the target exception scenario template and send the exception handling task to the client of the target person in charge, and the target person in charge is pre-set for the node to be processed.
[0060] It should be noted that the collaborative exception handling system for a production information system provided in the above embodiment only uses the division of the above-mentioned functional modules as an example when executing the collaborative exception handling method for a production information system. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the collaborative exception handling system for a production information system provided in the above embodiment and the collaborative exception handling method embodiment for a production information system belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.
[0061] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0062] In an embodiment of the present application, in a production-type information system, business processes are standardized, and each process is subdivided into multiple nodes, each node representing a business link. When an exception occurs, the system can quickly locate the node to be processed where the exception occurs through the standardized process node. At the same time, the system can display a set of exception scenario templates associated with the node to be processed. Each template is pre-set for possible exceptions. By selecting the corresponding exception scenario template, the system will automatically create a detailed exception handling task and send it to the client of the pre-specified target person in charge. This automated exception identification and notification process greatly improves the exception response speed, ensures that the problem can be quickly identified and communicated to the correct person in charge, and the rapid problem-solving mechanism not only reduces the risk of production interruption, but also causes the problem to be resolved in the shortest time, thereby effectively guaranteeing the company's production activities and business management.
[0063] The present application also provides a computer-readable medium having program instructions stored thereon, which, when executed by a processor, implement the collaborative exception handling method for a production information system provided by the above-mentioned various method embodiments.
[0064] The present application also provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the collaborative exception handling method for a production information system of each of the above method embodiments.
[0065] See also Figure 7 , is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 7 As shown, the electronic device 1000 may include: at least one processor 1001 , at least one network interface 1004 , a user interface 1003 , a memory 1005 , and at least one communication bus 1002 .
[0066] The communication bus 1002 is used to realize the connection and communication between these components.
[0067] The user interface 1003 may include a display screen (Display) and a camera (Camera). Optionally, the user interface 1003 may also include a standard wired interface and a wireless interface.
[0068] The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).
[0069] Among them, the processor 1001 may include one or more processing cores. The processor 1001 uses various interfaces and lines to connect various parts of the entire electronic device 1000, and executes various functions and processes data of the electronic device 1000 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1005, and calling data stored in the memory 1005. Optionally, the processor 1001 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 1001 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1001, and it can be implemented separately through a chip.
[0070] Among them, the memory 1005 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 1005 includes a non-transitory computer-readable storage medium. The memory 1005 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1005 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 1005 may also be optionally at least one storage system located away from the aforementioned processor 1001. As Figure 7 As shown, the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a collaborative exception handling application for a production information system.
[0071] exist Figure 7In the electronic device 1000 shown, the user interface 1003 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 1001 can be used to call the collaborative exception handling application for the production information system stored in the memory 1005, and specifically perform the following operations: In response to a trigger instruction for an exception handling component displayed on a system operation interface, determine an abnormal node to be processed; wherein the node to be processed is a node of a business link with an abnormality in a node set corresponding to a business process with a collaboration abnormality in a business process set, the business process set is obtained by standardizing all business processes pre-defined in a production information system, and the node set is obtained by dividing the business process according to different preset business links; Displaying an abnormal scenario template set of a node to be processed, each abnormal scenario template in the abnormal scenario template set is module information pre-set based on multiple abnormal scenarios existing in the node to be processed and used to characterize business process abnormalities; In response to a selection instruction for the displayed abnormal scene template set, obtaining a target abnormal scene template indicated by the selection instruction in the abnormal scene template set; Based on the target exception scenario template, an exception handling task is created and sent to the client of the target person in charge. The target person in charge is pre-set for the node to be processed.
[0072] In one embodiment, when the processor 1001 determines that there is an abnormal node to be processed, the processor 1001 specifically performs the following operations: Determine a link icon for representing a business link indicated by the trigger instruction, where the link icon carries a target business process tag and a target business link tag; Obtain a business process set obtained by standardizing all business processes pre-defined in the production information system; Compare the target business process tag with the business process tag carried by each business process in the business process set to find out the business process corresponding to the business process tag that is the same as the target business process tag as the business process with collaboration anomaly; The business link mark carried by each node in the node set corresponding to the business process with collaborative anomalies is compared with the target business link mark to find out the node corresponding to the business link mark that is the same as the target business link mark as the node to be processed with the anomaly.
[0073] In one embodiment, when the processor 1001 determines the link icon for representing the service link indicated by the trigger instruction, it specifically performs the following operations: Get the target pixel coordinates of the user's click on the screen corresponding to the trigger instruction; According to the preset pixel parameters, a two-dimensional coordinate system is created for displaying the interface; Projecting a set of link icons used to represent all business links in the production information system into a two-dimensional coordinate system to obtain a set of pixel coordinates of each link icon; Calculate the similarity distance between the target pixel coordinates and each pixel coordinate in the pixel coordinate set of each link icon; The link icon corresponding to the pixel coordinate set to which the pixel coordinates with the smallest similarity distance belong is used as the link icon for representing the business link indicated by the trigger instruction; wherein, The similarity distance calculation formula is:
[0074] in, is the pixel coordinates of the target pixel and the pixel coordinates of each link icon. The similarity distance between pixel coordinates, and are the horizontal and vertical coordinates of the target pixel coordinates, respectively. and They are the pixel coordinates of each link icon. The horizontal and vertical coordinates of the pixel coordinates.
[0075] In one embodiment, when executing the generation of the node set, the processor 1001 specifically performs the following operations: Traverse all pre-defined business processes in the production information system; Standardize all business processes to obtain a business process set; Get the preset different business links corresponding to each business process in the business process set; According to the preset different business links corresponding to each business process, each business process is divided to obtain a node set corresponding to each business process.
[0076] In one embodiment, when the processor 1001 performs process standardization processing on all business processes to obtain a business process set, the processor 1001 specifically performs the following operations: Obtain the business execution order of each business process in all business processes; According to the business execution sequence, all business processes are checked for integrity to determine whether each business process has a logical start point and a logical end point; When each business process has a logical start point and a logical end point, each business process is classified and aggregated to obtain a business process set; wherein, The business process set includes procurement process, production process and sales process.
[0077] In one embodiment, when the processor 1001 divides each business process according to the preset different business links corresponding to each business process to obtain the node set corresponding to each business process, the processor 1001 specifically performs the following operations: In the case where the business process is a procurement process, different preset business links corresponding to the procurement process are determined. The different preset business links corresponding to the procurement process include a demand identification link, a supplier selection link, an order generation link, a goods reception link, and a payment processing link; From the process information of the procurement process, obtain the process information corresponding to the demand identification stage, supplier selection stage, order generation stage, goods receiving stage and payment processing stage respectively; Based on the acquired process information corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link, nodes corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link are created respectively; All created nodes are used as the node set corresponding to the procurement process.
[0078] In one embodiment, when the processor 1001 creates an exception handling task based on a target exception scenario template, the processor 1001 specifically performs the following operations: Based on the parameter ID, obtain the abnormal type information, impact range information, processing steps and urgency information of the target abnormal scenario template as task parameters; Fill the task parameters into the interactive interface one by one to obtain an interactive interface with the parameters; Treat the interactive interface with parameters as an exception handling task.
[0079] In one embodiment, when the processor 1001 acquires the abnormality type information, the impact range information, the processing steps and the urgency information of the target abnormal scenario template based on the parameter ID, the processor 1001 specifically performs the following operations: Build an executable SQL query statement based on the exception type ID, impact range ID, processing steps, and urgency ID; Execute executable SQL query statements to obtain the exception type information, impact range information, processing steps and urgency information of the target exception scenario template from the database.
[0080] In one embodiment, when the processor 1001 fills the task parameters into the interactive interface one by one to obtain the interactive interface with the parameters, the processor 1001 specifically performs the following operations: Fill the exception type information into the exception type input box to obtain the exception type input box with parameters; Mapping and associating the impact range information with the impact range drop-down menu to obtain the impact range drop-down menu with parameters; Fill the processing steps into the processing step text area to obtain a processing step text area with parameters; Mapping and associating the urgency information with the urgency slider to obtain an urgency slider with parameters; An exception type input box with parameters, an impact range drop-down menu with parameters, a processing step text area with parameters, and an urgency slider with parameters are used as the interactive interface with parameters.
[0081] In an embodiment of the present application, in a production-type information system, business processes are standardized, and each process is subdivided into multiple nodes, each node representing a business link. When an exception occurs, the system can quickly locate the node to be processed where the exception occurs through the standardized process node. At the same time, the system can display a set of exception scenario templates associated with the node to be processed. Each template is pre-set for possible exceptions. By selecting the corresponding exception scenario template, the system will automatically create a detailed exception handling task and send it to the client of the pre-specified target person in charge. This automated exception identification and notification process greatly improves the exception response speed, ensures that the problem can be quickly identified and communicated to the correct person in charge, and the rapid problem-solving mechanism not only reduces the risk of production interruption, but also causes the problem to be resolved in the shortest time, thereby effectively guaranteeing the company's production activities and business management.
[0082] A person skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the program for collaborative exception handling of a production information system can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the storage medium of the program for collaborative exception handling of a production information system can be a disk, an optical disk, a read-only storage memory, or a random access storage memory, etc.
[0083] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.
Claims
1. A collaborative exception handling method for a production information system, characterized in that: The method comprises: In response to a trigger instruction for an exception handling component displayed on a system operation interface, determine an abnormal node to be processed; wherein the node to be processed is a node of a business link with an abnormality in a node set corresponding to a business process with a collaboration abnormality in a business process set, the business process set is obtained by performing process standardization processing on all business processes pre-defined in a production information system, and the node set is obtained by dividing the business process according to different preset business links; Displaying the abnormal scenario template set of the node to be processed, each abnormal scenario template in the abnormal scenario template set is module information pre-set based on multiple abnormal scenarios existing in the node to be processed and used to characterize business process abnormalities; In response to a selection instruction for the displayed abnormal scene template set, acquiring a target abnormal scene template indicated by the selection instruction in the abnormal scene template set; Based on the target exception scenario template, an exception handling task is created, and the exception handling task is sent to the client of the target person in charge, and the target person in charge is pre-set for the node to be processed.
2. The method according to claim 1, characterized in that: The determining of the abnormal node to be processed includes: Determine a link icon for representing a business link indicated by the trigger instruction, wherein the link icon carries a target business process mark and a target business link mark; Obtain a business process set obtained by standardizing all business processes pre-defined in the production information system; Compare the target business process tag with the business process tag carried by each business process in the business process set to find out the business process corresponding to the business process tag that is the same as the target business process tag as the business process with collaboration anomaly; The business link mark carried by each node in the node set corresponding to the business process with collaborative abnormality is compared with the target business link mark to find out the node corresponding to the business link mark that is the same as the target business link mark as the node to be processed with the abnormality.
3. The method according to claim 2, characterized in that The step of determining the link icon for representing the business link indicated by the trigger instruction includes: Obtain the target pixel coordinates of the user's click on the screen corresponding to the trigger instruction; According to the preset pixel parameters, a two-dimensional coordinate system is created for the display interface; Projecting a set of link icons used to represent all business links in the production information system into the two-dimensional coordinate system to obtain a set of pixel coordinates of each link icon; Calculating the similarity distance between the target pixel coordinates and each pixel coordinate in the pixel coordinate set of each link icon; The link icon corresponding to the pixel coordinate set to which the pixel coordinates with the smallest similarity distance belong is used as the link icon for representing the business link indicated by the trigger instruction; wherein, The similarity distance calculation formula is: in, is the pixel coordinates of the target pixel and the pixel coordinates of each link icon in the set The similarity distance between pixel coordinates, and are the horizontal and vertical coordinates of the target pixel coordinates, respectively. and are the pixel coordinates of the icons of each link. The horizontal and vertical coordinates of the pixel coordinates.
4. The method according to claim 1, characterized in that: Follow these steps to generate a node collection, including: Traversing all business processes predefined in the production information system; Standardize all business processes to obtain a business process set; Obtaining different preset business links corresponding to each business process in the business process set; According to different preset business links corresponding to each business process, each business process is divided to obtain a node set corresponding to each business process.
5. The method according to claim 4, characterized in that The process standardization is performed on all business processes to obtain a business process set, including: Obtaining the business execution order of each business process in all the business processes; According to the business execution sequence, performing integrity check on each of the business processes in all the business processes to determine whether each of the business processes has a logical start point and a logical end point; In the case where each business process has a logical starting point and a logical ending point, each business process is classified and aggregated to obtain a business process set; wherein, The business process set includes a procurement process, a production process and a sales process.
6. The method according to claim 4, characterized in that According to the preset different business links corresponding to each business process, each business process is divided to obtain a node set corresponding to each business process, including: In the case where the business process is a procurement process, determining different preset business links corresponding to the procurement process, wherein the different preset business links corresponding to the procurement process include a demand identification link, a supplier selection link, an order generation link, a goods reception link, and a payment processing link; From the process information of the procurement process, respectively obtain process information corresponding to the demand identification link, supplier selection link, order generation link, goods receiving link and payment processing link; Based on the acquired process information corresponding to the demand identification link, supplier selection link, order generation link, goods reception link and payment processing link, nodes corresponding to the demand identification link, supplier selection link, order generation link, goods reception link and payment processing link are created respectively; All created nodes are used as the node set corresponding to the procurement process.
7. The method according to claim 1, characterized in that The target abnormal scenario template is a module information for characterizing a business process abnormality, and the module information is a visual interactive interface, and the interactive interface carries a parameter ID; The creating an exception handling task based on the target exception scenario template includes: Based on the parameter ID, obtain the abnormality type information, impact range information, processing steps and urgency information of the target abnormal scenario template as task parameters; Filling the task parameters into the interactive interface one by one to obtain an interactive interface with the parameters; Treat the interactive interface with parameters as an exception handling task.
8. The method according to claim 7, characterized in that The parameter ID includes the exception type ID, the impact range ID, the processing steps and the urgency ID; The acquiring of the abnormality type information, the impact range information, the processing steps and the urgency information of the target abnormality scenario template based on the parameter ID includes: Construct an executable SQL query statement according to the exception type ID, impact range ID, processing steps and urgency ID; Execute an executable SQL query statement to obtain the abnormal type information, impact range information, processing steps and urgency information of the target abnormal scenario template from the database.
9. The method according to claim 7, characterized in that: The interactive interface is composed of an exception type input box, an impact range drop-down menu, a processing step text area, and an urgency slider; The step of filling the task parameters into the interactive interface one by one to obtain an interactive interface with the parameters includes: Fill the exception type information into the exception type input box to obtain an exception type input box with parameters; Mapping and associating the impact range information with the impact range drop-down menu to obtain an impact range drop-down menu with parameters; Filling the processing steps into the processing step text area to obtain a processing step text area with parameters; Mapping and associating the urgency information with the urgency slider to obtain an urgency slider with parameters; An exception type input box with parameters, an impact range drop-down menu with parameters, a processing step text area with parameters, and an urgency slider with parameters are used as the interactive interface with parameters.
10. A collaborative exception handling system for a production information system, characterized in that: The system comprises: A to-be-processed node determination module is used to determine an abnormal to-be-processed node in response to a trigger instruction for an abnormal processing component displayed on a system operation interface; wherein the to-be-processed node is a node of an abnormal business link in a node set corresponding to a business process with a collaboration abnormality in a business process set, wherein the business process set is obtained by subjecting all pre-defined business processes in a production-type information system to process standardization, and the node set is obtained by dividing the business process according to different preset business links; An abnormal scenario template set display module, used to display the abnormal scenario template set of the node to be processed, each abnormal scenario template in the abnormal scenario template set is module information pre-set based on multiple abnormal scenarios existing in the node to be processed and used to characterize business process abnormalities; A target abnormal scene template acquisition module, configured to, in response to a selection instruction for the displayed abnormal scene template set, acquire a target abnormal scene template indicated by the selection instruction in the abnormal scene template set; The exception handling task sending module is used to create an exception handling task based on the target exception scenario template and send the exception handling task to the client of the target person in charge, and the target person in charge is pre-set for the node to be processed.
Citation Information
Patent Citations
Fault finding method and device of application system, equipment and medium
CN109739680A
Material production whole process information perception visualization system based on supply chain control tower
CN113052650A
Abnormal logistics order processing method and device, equipment and storage medium
CN114663031A
Touch screen touch method and device based on intelligent full-process data and electronic equipment
CN114895836A
Business process monitoring methods, devices, computer equipment, and storage media
CN114936136A
Cited By
Instruction approval data processing method and system based on multiple neural networks
CN120013457A
