A process engine driven 8D quality improvement collaboration method, device and medium

Abstract

The application provides an 8D quality improvement collaborative method and device based on a process engine, and a medium. The method can improve problem solving speed, enhance quality improvement effect, improve team cooperation and communication, and enhance continuous improvement capability. The method comprises the following steps: creating 8D processes corresponding to each production stage in the whole production process of a product; when a quality problem is found in a first production stage, automatically matching a target 8D process, the first production stage being any production stage in each production stage, and the target 8D process being the 8D process corresponding to the first production stage; driving the process engine to execute the target 8D process according to a specified node sequence constraint mechanism; in the process, the process engine automatically fills in 8D report fields by using an experience library, the 8D report fields being fields required to be filled in corresponding steps in the target 8D process; and driving the process engine to uniformly store process data generated when the process engine executes the target 8D process into a specified storage device.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of quality management, in particular to an 8D quality improvement collaboration method and device based on a process engine and a medium. BACKGROUND

[0002] 8D is a problem-solving method, also known as 8D method or 8D process, which includes 8 steps (1D to 8D), each step has specific tasks and goals, aiming to help organizations systematically identify, analyze, solve and prevent problems. In the process of quality improvement, 8D is an important quality improvement tool method, which can complete quality improvement through 8 steps.

[0003] However, in the traditional 8D process, each step is simply information input, for example, the cause analysis node (such as 4D) is only to input the cause of the problem, and the improvement countermeasure node (such as 7D) is only to input the improvement countermeasure for the cause of the problem, and the steps are completed sequentially, so there are many problems in the actual execution process, such as:

[0004] (1) Low efficiency of collaboration: relying on manual coordination (through email or meetings), cross-department task allocation and tracking efficiency is low, resulting in long cycle (usually 20-30 days).

[0005] (2) Risk of process skipping: key steps (such as 4D problem root analysis, 7D prevention countermeasure) are easily ignored or formalized, and the quality problem recurrence rate is high. For example, in order to complete the 8D improvement task as soon as possible, some steps may be skipped artificially, resulting in no record of root cause analysis process, no repeated verification of effect, lack of team participant's audit signature, and no prevention measures, etc., resulting in high quality problem recurrence rate.

[0006] (3) Data island: the process data of the traditional 8D process is scattered in multiple systems (such as manufacturing execution system MES, quality management system QMS, enterprise resource planning ERP), lacking real-time integration and closed-loop feedback. SUMMARY

[0007] The embodiments of the application provide an 8D quality improvement collaboration method and device based on a process engine to solve the problems in the related art, and the technical solutions are as follows:

[0008] In a first aspect, the embodiments of the application provide an 8D quality improvement collaboration method based on a process engine, comprising:

[0009] Creating 8D processes corresponding to each production stage of the entire production process of a product;

[0010] automatically matching a target 8D process when a quality problem is found in a first production stage, the first production stage being any one of the production stages, the target 8D process being the 8D process corresponding to the first production stage;

[0011] driving the process engine to execute the target 8D process according to the specified node sequence constraint mechanism, in the process, driving the process engine to automatically fill in 8D report fields using the experience base, the 8D report fields being fields required to be filled in for corresponding steps in the target 8D process;

[0012] driving the process engine to store process data generated when the process engine executes the target 8D process to a specified storage device.

[0013] In an embodiment, creating 8D processes corresponding to each production stage of the entire product production process includes:

[0014] According to a preset process template, creating 8D processes corresponding to each production stage of the entire product production process.

[0015] In an embodiment, automatically matching a target 8D process when a quality problem is found in a first production stage includes:

[0016] driving the process engine to start a quality improvement business process when a quality problem is found in the first production stage;

[0017] After the quality improvement business process is started, automatically matching the target 8D process based on the first production stage.

[0018] In an embodiment, driving the process engine to execute the target 8D process according to the specified node sequence constraint mechanism includes:

[0019] defining each step of the target 8D process as a process node, and adding node attribute constraint conditions between adjacent process nodes, the node attribute constraint conditions including execution sequence constraint conditions and data constraint conditions;

[0020] driving the process engine to execute each process node in sequence according to the execution sequence constraint conditions in the node attribute constraint conditions;

[0021] When the process node flows, driving the process engine to execute the next process node after determining that the data information entered in the currently executed process node meets the data constraint conditions in the node attribute constraint conditions.

[0022] In an embodiment, driving the process engine to automatically fill in 8D report fields using the experience base includes:

[0023] The process engine is driven to identify target keywords in the 2D step entry problem description content, and determine fault information in the experience library that matches the target keywords;

[0024] The process engine is driven to fill the relevant content in the fault information into the 8D report field of the 2D step, the 8D report field of the 4D step, and the 8D report field of the 7D step;

[0025] The process engine is driven to determine target causes and target improvement measures in the experience library that match the fault information;

[0026] The process engine is driven to fill the target causes into the 8D report field of the 4D step, and fill the target improvement measures into the 8D report field of the 7D step.

[0027] In an embodiment, the method further comprises:

[0028] The process engine is driven to update the 8D report field in response to a modification operation on the 8D report field.

[0029] In an embodiment, the method further comprises:

[0030] When the process engine completes each step in the target 8D process, a specified message pushing manner is used to push a completion message of each step to the person in charge of each step.

[0031] In a second aspect, the embodiments of the present application also provide an 8D quality improvement collaboration device driven by a process engine, comprising:

[0032] A creation unit is configured to create 8D processes corresponding to each production stage in the entire production process of a product;

[0033] A matching unit is configured to automatically match a target 8D process when a quality problem is found in a first production stage, the first production stage being any production stage in the plurality of production stages, and the target 8D process being the 8D process corresponding to the first production stage;

[0034] An execution unit is configured to drive the process engine to execute the target 8D process according to a specified node sequence constraint mechanism, and in this process, drive the process engine to automatically fill an 8D report field by using an experience library, the 8D report field being a field required to be filled in by a corresponding step in the target 8D process;

[0035] A storage unit is configured to drive the process engine to uniformly store process data generated when the process engine executes the target 8D process to a specified storage device.

[0036] In an implementation, the creating unit is specifically configured to:

[0037] create the 8D process corresponding to each production stage of the product production whole process according to the preset process template.

[0038] In an implementation, the matching unit is specifically configured to:

[0039] determine the target 8D process when the first production stage discovers the quality problem.

[0040] drive the process engine to start the quality improvement business process when the first production stage discovers the quality problem;

[0041] automatically match the target 8D process based on the first production stage after the quality improvement business process is started.

[0042] define each step of the target 8D process as a process node, and add node attribute constraint conditions between adjacent process nodes, the node attribute constraint conditions including execution order constraint conditions and data constraint conditions;

[0043] drive the process engine to execute each process node in sequence according to the execution order constraint conditions in the node attribute constraint conditions;

[0044] drive the process engine to execute the next process node when it is determined that the data information entered in the currently executed process node meets the data constraint conditions in the node attribute constraint conditions.

[0045] In an implementation, the execution unit is specifically configured to:

[0046] drive the process engine to identify a target keyword in the problem description content entered in the 2D step, and determine fault information in the experience library that matches the target keyword;

[0047] drive the process engine to fill the related content in the fault information into the 8D report field of the 2D step, the 8D report field of the 4D step, and the 8D report field of the 7D step;

[0048] drive the process engine to determine a target cause and a target improvement countermeasure in the experience library that match the fault information;

[0049] The process engine is driven to fill the target cause into the 8D report field of the 4D step, and fill the target improvement countermeasure into the 8D report field of the 7D step.

[0050] In an implementation, the execution unit is further configured to:

[0051] The process engine is driven to update the 8D report field in response to a modification operation on the 8D report field.

[0052] In an implementation, the execution unit is further configured to:

[0053] When the process engine completes each step in the target 8D process, a specified message pushing manner is used to push a completion message of each step to a person in charge of each step.

[0054] In a third aspect, the embodiments of the present application further provide a computer device, which comprises a memory and a processor, the memory stores instructions, the instructions are loaded and executed by the processor to implement the method in any of the embodiments of the above aspects, and the memory and the processor communicate with each other through an internal connection path.

[0055] In a fourth aspect, the embodiments of the present application further provide a computer readable storage medium, which stores a computer program, and when the computer program runs on a computer, the method in any of the embodiments of the above aspects is implemented.

[0056] The advantages or beneficial effects of the above technical solutions at least include:

[0057] (I) Problem solving speed is improved: the 8D process corresponding to the production phase of the problem discovery quality is driven and executed by the process engine, which can accelerate the problem solving speed, reduce the problem solving time, improve the response ability, shorten the 8D improvement cycle by 30%-50%, and reduce the quality improvement cost.

[0058] (II) Quality improvement effect is enhanced: through the driving of the process engine, the process nodes can be automatically matched, the quality improvement process can be standardized, the improvement can be carried out in order, and the reliability and continuity of the improvement effect are improved.

[0059] (III) Team collaboration and communication are improved: through the driving of the process engine, the collaboration and communication among team members can be promoted, and the error and delay of information transmission can be reduced.

[0060] (IV) Continuous improvement ability is enhanced: through the systematic process driving, the organization can establish the culture and mechanism of continuous improvement, and continuously improve the quality management level and efficiency.

[0061] The above summary is intended to illustrate only and is not intended to be limiting in any way. Further aspects, embodiments and features of the present application will be readily apparent to those skilled in the art by reference to the drawings and the following detailed description. BRIEF DESCRIPTION OF DRAWINGS

[0062] In the drawings, like numerals refer to like elements throughout the various drawings. The drawings are not necessarily to scale, the emphasis instead being placed on the principles of the application. It should be understood that the drawings are merely intended to depict some of the embodiments of the application. The application should not be considered limited to the precise drawing illustrations.

[0063] Figure 1 A flowchart of an 8D quality improvement collaborative method based on a process engine driven, provided for an embodiment of the present application;

[0064] Figure 2 An example diagram of a drag-and-drop interface, provided for an embodiment of the present application;

[0065] Figure 3 An example diagram of a constraint entry interface, provided for an embodiment of the present application;

[0066] Figure 4 A flow visualization interface of a 1D step, provided for an embodiment of the present application;

[0067] Figure 5 An example diagram of a reason query interface, provided for an embodiment of the present application;

[0068] Figure 6 A flow visualization interface of a 4D step, provided for an embodiment of the present application;

[0069] Figure 7 Another flow visualization interface of a 4D step, provided for an embodiment of the present application;

[0070] Figure 8 A structural block diagram of an 8D quality improvement collaborative device based on a process engine driven, provided for an embodiment of the present application;

[0071] Figure 9 A structural block diagram of a computer device, provided for an embodiment of the present application. DETAILED DESCRIPTION

[0072] In the following, only some exemplary embodiments are simply described. As those skilled in the art can recognize, the described embodiments can be modified in various different ways without departing from the spirit or scope of the present application. Therefore, the drawings and the description are considered to be exemplary in nature and not limiting.

[0073] To facilitate the understanding of the corresponding technical solutions provided by the embodiments of the present application, the 1D to 8D steps of the 8D process are introduced as follows.

[0074] 1D, form a problem solving team: emphasize cross-functional team collaboration. Team members need to have product and process knowledge, have enough time allocation, authority and skills. In the implementation of the 8D problem solving method, the role of the team is very important. Usually, the team includes an 8D team leader who is responsible for leading and coordinating the work of the whole team.

[0075] 2D, problem description: describe the problem in detail and specifically. When defining the problem, the boundaries need to be clearly defined to ensure the accuracy and controllability of the problem description. Usually, the 5W2H analysis method is used for detailed description.

[0076] 3D, temporary measures: develop, verify and implement temporary measures to isolate the problem and ensure that the problem does not get worse before the root cause is found. The goal of this stage is to isolate the problem and give the 8D team time to analyze and find the root cause of the problem.

[0077] 4D, problem root analysis: find the root cause of the problem and determine the true root cause of the problem. The "five why" tool is mainly used to gradually reveal the deep reasons behind the problem through continuous questioning and in-depth analysis.

[0078] 5D, corrective measures: after finding the root cause, develop long-term countermeasures to ensure that the best improvement plan is proposed to prevent the problem from recurring.

[0079] 6D, process and effect confirmation: develop an implementation plan, monitor and verify its effectiveness, and ensure that the problem solving standards are met. The implementation is monitored to ensure its effectiveness.

[0080] 7D, preventive countermeasures: after the improvement measures are defined, establish a long-term monitoring mechanism to evaluate the effectiveness of the improvement measures and standardize the operation process to prevent the problem from recurring.

[0081] 8D, team summary: summarize and review the improvement to ensure that the improvement experience enters the experience library.

[0082] The corresponding technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0083] Figure 1 A flowchart of an 8D quality improvement collaboration method based on a process engine driven according to an embodiment of the present application is shown. As shown in Figure 1 The method can include the following steps:

[0084] S110, create the 8D process corresponding to each production stage of the product production whole process.

[0085] In an embodiment, the 8D process corresponding to each production stage of the product production whole process can be created according to a preset process template.

[0086] For example, the 8D process corresponding to each production stage of the product production whole process can be created according to the same preset process template. Alternatively, a corresponding process template can be preset for each production stage of the product production whole process, and then the 8D process corresponding to each production stage of the product production whole process can be created according to the process template corresponding to each production stage of the product production whole process.

[0087] For example, the production stages of the product production whole process can include, but are not limited to, supplier raw material receiving, inventory transfer, ingredient production, process collection, process inspection, semi-finished product processing, finished product warehousing, and finished product delivery.

[0088] In the embodiments of the present application, by performing step S110, the corresponding 8D process can be automatically matched when a quality problem is found in each production stage of the product production whole process in the future, and the quality improvement of each production stage can be effectively targeted.

[0089] S120, determine the target 8D process to be automatically matched when a quality problem is found in the first production stage.

[0090] In an embodiment, the first production stage is any production stage of the product production whole process. The target 8D process is the 8D process corresponding to the first production stage.

[0091] For example, when a quality problem is found in a certain production stage during production, at the factory, or after sale, a prompt message can be initiated by QMS, which can be used to indicate that a quality problem is found in the first production stage. Accordingly, when receiving the prompt message from QMS, it can be determined that a quality problem is found in the first production stage.

[0092] In an embodiment, when a quality problem is found in the first production stage, the process engine can be driven to start a quality improvement business process, so that the quality improvement business can be started to improve the quality by driving the execution of the corresponding 8D process. After the quality improvement business process is started, the target 8D process can be automatically matched based on the first production stage.

[0093] Exemplarily, in the process of creating the 8D process corresponding to each production stage of the product production whole process in step S110, the identification information of each production stage can be set, and then the identification information of each production stage is associated with the corresponding 8D process, so as to obtain the association relationship between the identification information of each production stage and the corresponding 8D process. Based on the identification information of the first production stage and the association relationship, the target 8D process can be matched.

[0094] In the embodiment of the application, by performing step S120, the corresponding process node can be automatically matched when the quality problem is found.

[0095] S130, driving the process engine to execute the target 8D process according to the specified node order constraint mechanism, in the process, the process engine fills the 8D report field automatically by using the experience library.

[0096] In an implementation, the 8D report field is a field required to be filled in by the corresponding step in the target 8D process.

[0097] In an implementation, the implementation process of driving the process engine to execute the target 8D process according to the specified node order constraint mechanism can include the following steps:

[0098] S131, defining each step of the target 8D process as a process node, and adding a node attribute constraint condition between adjacent process nodes.

[0099] In a specific implementation, the node attribute constraint condition can include an execution order constraint condition and a data constraint condition.

[0100] As an example, each step of the target 8D process can be defined as a process node by the process designer, and a node attribute constraint condition can be added between adjacent process nodes. For example, as shown in Figure 2 , each step of the target 8D process can be customized as a visual process node in the drag-and-drop interface provided by the process designer, and a constraint adding control can be set on the connection line between the process nodes, so that the constraint entry interface can be displayed by clicking the constraint adding control, and after the node attribute constraint condition between adjacent process nodes is entered on the constraint entry interface, the node attribute constraint condition between adjacent process nodes can be added.

[0101] Exemplarily, the execution order constraint condition in the node attribute constraint condition can be entered on the attribute setting on the constraint entry interface as shown in Figure 3 , including node display order, whether to be selected. After the entry is completed, the execution order constraint condition can be added between adjacent process nodes by clicking the "save" control.

[0102] S132, the driving flow engine executes each flow node in sequence according to the execution sequence constraint in the node attribute constraint condition.

[0103] In specific implementation, by driving the flow engine to execute each flow node in sequence according to the execution sequence constraint in the node attribute constraint condition, the compliance of the target 8D flow can be forced, and the flow engine is prevented from skipping the execution of some steps of the target 8D flow.

[0104] For example, in the application of the traditional 8D flow, the 3D step, the 6D step and the 8D step are steps that are easily skipped by people. In the embodiment of the present application, by executing step S132, the three steps can be prevented from being skipped by people.

[0105] S133, when the flow node is in progress, the driving flow engine executes the next flow node after determining that the data information entered by the currently executed flow node meets the data constraint condition in the node attribute constraint condition.

[0106] In specific implementation, the data constraint condition can be used to force the flow node to enter necessary data, which can be set according to actual needs. It can be understood that, by the data constraint condition, the flow node with earlier execution sequence among two adjacent flow nodes must enter necessary data, so that the flow node with later execution sequence among the two adjacent flow nodes can be executed.

[0107] In the embodiment of the present application, by executing step S133, the omission of the entry of necessary data in the process of executing the flow node by the driving flow engine can be prevented.

[0108] In one embodiment, the implementation process of the driving flow engine for automatically filling the 8D report field by using the experience library can include the following steps:

[0109] S131a, the driving flow engine identifies the target keyword in the problem description content entered in the 2D step, and determines the fault information in the experience library that matches the target keyword.

[0110] In specific implementation, the flow engine has completed the entry of the problem description content when the 2D step of the target flow is executed. Then, the fault information in the experience library can be automatically matched according to the target keyword in the problem description content.

[0111] As an example, the keywords can be set according to the problems that can occur in each production stage of the whole product production process, and the set keywords and corresponding production stages are stored in the experience library. Then, the keyword range can be locked according to the production stage where the quality problem is found. The fault information corresponding to each production stage keyword can also be set and stored in the experience library. These keywords and fault information can be subsequently archived and updated using the summary of historical 8D process execution.

[0112] As shown in FIG. 8, the problem description content entered in the 2D step is: the product was found to have a batch shell extrusion deformation during the process transfer process on May 21, 2025, the occurrence location was the 001 assembly line, the time was 13:30, and the number was 50. Then, the corresponding production stage is the inventory transfer stage, and the corresponding keywords in the inventory transfer can be "shell", "deformation", and "001 assembly line". That is, the target keywords in the problem description content entered in the 1D step are "shell", "deformation", and "001 assembly line". Figure 4

[0113] The fault information matched in the experience library by the process engine based on the target keywords "shell", "deformation", and "001 assembly line" can include single number, problem source, material code, material name, process definition, defect code, and defect code description, and the like.

[0114] S132a, drive the process engine to fill the related content in the fault information into the 8D report field of the 2D step, the 8D report field of the 4D step, and the 8D report field of the 7D step.

[0115] As shown in FIG. 8, the problem description content entered in the 2D step is: the product was found to have a batch shell extrusion deformation during the process transfer process on May 21, 2025, the occurrence location was the 001 assembly line, the time was 13:30, and the number was 50. Then, the corresponding production stage is the inventory transfer stage, and the corresponding keywords in the inventory transfer can be "shell", "deformation", and "001 assembly line". That is, the target keywords in the problem description content entered in the 1D step are "shell", "deformation", and "001 assembly line". Figure 4 As shown in FIG. 8, the single number, problem source, material code, material name, process definition, defect code, and defect code description in the fault information can be filled into the 8D report field of the 2D step.

[0116] As shown in FIG. 8, the single number, problem source, material code, material name, process definition, defect code, and defect code description in the fault information can be filled into the 8D report field of the 2D step.

[0117] S133a, drive the process engine to determine the target cause and target improvement countermeasure in the experience library that match the fault information.

[0118] In specific implementation, the process engine can be driven to determine the target cause and target improvement countermeasure in the experience library that match the defect code of the fault information.

[0119] ​As an example, the causes and improvement countermeasures corresponding to the respective defect codes can be stored in the experience library. Subsequently, the causes and improvement countermeasures corresponding to the defect codes can be found from the experience library based on the defect codes, and the corresponding causes and improvement countermeasures can be selected therefrom.

[0120] As an example, the causes are taken as an example, as shown in Figure 5 In the cause query interface provided by the experience library, the corresponding causes (such as the occurrence causes) can be queried based on the defect codes in the fault information, and two root causes are obtained. When the corresponding responsible person selects one of the root causes, the selected root cause is the target cause.

[0121] In step S134a, the flow engine is driven to fill the target cause into the 8D report field of the 4D step, and the target improvement countermeasure is filled into the 8D report field of the 7D step.

[0122] As an example, as shown in Figure 6 The flow engine can be driven to fill the target cause "in the material outbound transportation process, the carrier protection is improper, causing the material appearance to be scratched" into the occurrence cause position in the 8D report field of the 4D step.

[0123] It should be understood that steps S131a-S134a and steps S131-S133 are interleaved.

[0124] In the embodiments of the present application, by performing step S130, the execution efficiency of the target 8D process can be affected by human intervention, which helps to improve the improvement efficiency of the discovered quality problem and realizes the improvement in place. In addition, the target 8D process can be strictly executed according to the corresponding order, realizing systematic process management and control, which can avoid human skipping of the corresponding steps, thereby avoiding problems such as process confusion and step omission, and ensuring the improvement effect of the discovered quality problem.

[0125] Considering that in actual application, when the occurrence cause of an unpredictable quality problem is encountered, if only the occurrence causes provided in the experience library are used, there will be an unreliable problem. Based on this, in the process of performing step S130, the flow engine can be driven to update the 8D report field in response to a modification operation on the 8D report field.

[0126] As an example, by double-clicking Figure 6 the display position of the occurrence cause "in the material outbound transportation process, the carrier protection is improper, causing the material appearance to be scratched" in the 8D report field, the modification of the occurrence cause can be triggered. After the modification is completed, clicking other display positions in the interface can complete the modification and update of the occurrence cause.

[0127] In the implementation, in the process of modifying the 8D report field, the root cause of the occurrence reason can be added. For example, when the root cause in the selected Figure 7 is selected, the root cause of the updated occurrence reason can be added by using the 5why method.

[0128] That is, in the embodiment of the application, the 8D report field can be modified and updated to adapt to different production environments and different quality problems caused by different occurrence reasons.

[0129] S140, driving the process engine to uniformly store process data generated when the process engine executes the target 8D process to the designated storage device.

[0130] In the implementation, the storage device can be set according to actual needs, for example, it can be a local storage device, a cloud storage device, a QMS, etc., and the embodiment of the application does not limit this.

[0131] In the embodiment of the application, by performing step S140, the process data of the target 8D process can be automatically stored uniformly, realizing data collection and analysis without relying on manual work, and solving the data island problem existing in the traditional 8D process application, avoiding the influence of inaccurate or incomplete data on the scientificity of decision-making, so as to realize real-time integration and closed-loop feedback of data.

[0132] In an applicable scenario provided by the embodiment of the application, the 8D quality improvement collaboration method based on the process engine driving provided by the embodiment of the application can further include the following:

[0133] S150, when the process engine completes each step in the target 8D process, a designated message pushing method is used to push a completion message of each step to the person in charge of each step.

[0134] In one embodiment, in step S131, when each step of the target 8D process is defined as a process node, the corresponding message pushing method of each process node can be configured to realize process task notification. Subsequently, when the process engine completes each process node, the process engine can automatically push a completion message to the person in charge of the process node. The completion message can include related information and completion time entered in the process node, etc.

[0135] As an example, the designated message pushing method can be one of email pushing, WeChat pushing, enterprise WeChat pushing, etc.

[0136] In the embodiments of the present application, by performing step S150, the execution state of the target 8D process can be automatically informed according to the progress of the process executed by the driving engine, so as to realize real-time updating of the execution state of the target 8D process, thereby being able to track and monitor the execution of each step, prevent the phenomenon of easy information loss or error, and transparentize the improvement process of the discovered quality problem.

[0137] As can be known from the above description, the 8D quality improvement collaboration method based on the process engine driving provided by the embodiments of the present application can achieve the following beneficial effects:

[0138] (1) Problem solving speed is improved: the 8D process corresponding to the production stage of the discovered problem quality is executed by using the process engine driving, which can accelerate the problem processing speed, reduce the problem solving time, improve the response ability, shorten the 8D improvement period by 30%-50%, and reduce the quality improvement cost.

[0139] (2) Quality improvement effect is enhanced: through the process engine driving, the process nodes can be automatically matched, and the quality improvement process can be standardized, so that the improvement is orderly, and the reliability and continuity of the improvement effect are improved.

[0140] (3) Team collaboration and communication are improved: through the process engine driving, the collaboration and communication among team members can be promoted, and the error and delay of information transmission are reduced.

[0141] In actual application, task-to-person automatic notification and real-time monitoring can also be realized, which can improve the work efficiency by 30%.

[0142] (4) Continuous improvement ability is enhanced: through systematic process driving, the organization can establish a culture and mechanism for continuous improvement, and continuously improve the quality management level and efficiency.

[0143] For example, in the process of executing the 8D process by the process engine driving, the experience library can be loaded, and the causes and improvement measures of defects can be recommended, which can improve the efficiency by more than 50%, and the experience library can be fully reused.

[0144] For example, defect codes can be set, such as defect codes corresponding to problems of size being too large, scratches, deformation, and dirt. When a problem defect occurs, the corresponding defect code is selected. Since the defect code can be used as a unique identifier for archiving and referencing in the experience library, each time a problem is improved, the defect code will be automatically identified, and then the defect code is used to query historical improvement data in the experience library. When the improvement data is queried, it will be automatically displayed after filtering. At this time, only the problem causes and countermeasures that need to be loaded need to be selected manually. In this way, the data in the experience library can be reused, and after the improvement is completed, the data in the experience library can be supplemented and improved according to the defect code, so as to enrich the related content of the experience library.

[0145] Figure 8 This diagram illustrates a structural block diagram of an 8D quality improvement collaborative device based on a process engine driven according to an embodiment of this application. Figure 8 As shown, the device may include:

[0146] Create unit 210, which is used to create the 8D process corresponding to each production stage of the entire product manufacturing process;

[0147] Matching unit 220 is used to automatically match the target 8D process when a quality problem is found in the first production stage. The first production stage is any production stage among all production stages, and the target 8D process is the 8D process corresponding to the first production stage.

[0148] The execution unit 230 is used to drive the process engine to execute the target 8D process according to the specified node sequence constraint mechanism. During this process, the process engine automatically fills the 8D report fields using the experience base. The 8D report fields are the fields that need to be filled in for the corresponding steps in the target 8D process.

[0149] Storage unit 240 is used to drive the process engine to uniformly store the process data generated when the process engine executes the target 8D process into the designated storage device.

[0150] In one implementation, when creating the 8D process corresponding to each production stage of the entire product manufacturing process, the creation unit 210 is specifically used for:

[0151] Based on the preset process template, create 8D processes corresponding to each production stage of the entire product manufacturing process.

[0152] In one implementation, when the matching unit 220 automatically matches the target 8D process to determine that a quality problem was found in the first production stage, it is specifically used for:

[0153] When a quality problem is identified in the first production stage, the process engine initiates a quality improvement business process.

[0154] Once the quality improvement business process is initiated, it will automatically match the target 8D process based on the first production stage.

[0155] In one implementation, when the execution unit 230 is used to drive the process engine to execute the target 8D process according to the specified node sequence constraint mechanism, it is specifically used for:

[0156] Each step of the target 8D process is defined as a process node, and node attribute constraints are added between adjacent process nodes. The node attribute constraints include execution order constraints and data constraints.

[0157] The driving flow engine executes each flow node in sequence according to the execution sequence constraint in the node attribute constraint condition.

[0158] When the flow node stream is being performed, the driving flow engine executes the next flow node after determining that the data information entered by the currently executed flow node meets the data constraint in the node attribute constraint condition.

[0159] In an embodiment, the execution unit 230 is specifically configured to:

[0160] The driving flow engine identifies a target keyword in the problem description content entered by the 2D step, and determines fault information in the experience library that matches the target keyword;

[0161] The driving flow engine fills the related content in the fault information into the 8D report field of the 2D step, the 8D report field of the 4D step, and the 8D report field of the 7D step;

[0162] The driving flow engine determines a target cause and a target improvement countermeasure in the experience library that match the fault information;

[0163] The driving flow engine fills the target cause into the 8D report field of the 4D step, and fills the target improvement countermeasure into the 8D report field of the 7D step.

[0164] In an embodiment, the execution unit 230 is further configured to:

[0165] The driving flow engine updates the 8D report field in response to a modification operation on the 8D report field.

[0166] In an embodiment, the execution unit 230 is further configured to:

[0167] When the flow engine completes each step in the target 8D flow, a specified message pushing manner is used to push a completion message of each step to a person in charge of each step.

[0168] The functions of each unit in the 8D quality improvement collaboration device driven by the flow engine according to the embodiments of the present application can be referred to the corresponding description in the above method, which will not be repeated here.

[0169] Figure 9 A structural block diagram of a computer device according to an embodiment of the present application is shown. As shown in the figure, the computer device includes a memory 310 and a processor 320, the memory 310 stores instructions which are loaded and executed by the processor 320 to implement the 8D quality improvement collaboration method driven by the flow engine in the above embodiments. The number of memories 310 and processors 320 can be one or more. Figure 9 The number of memories 310 and processors 320 can be one or more.

[0170] The computer device also includes:

[0171] The communication interface 330 is configured to communicate with external devices and transmit data.

[0172] If the memory 310, the processor 320 and the communication interface 330 are implemented independently, the memory 310, the processor 320 and the communication interface 330 can be connected to each other through a bus and complete communication between each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 9 Only one thick line is used in the figure, but it does not mean that there is only one bus or only one type of bus.

[0173] Optionally, in a specific implementation, if the memory 310, the processor 320 and the communication interface 330 are integrated on a chip, the memory 310, the processor 320 and the communication interface 330 can complete communication between each other through an internal interface.

[0174] The embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores a computer program. When the computer program runs on a computer, the method provided in the embodiment of the present application is implemented.

[0175] The embodiment of the present application also provides a chip. The chip includes a processor, which is configured to invoke and run instructions stored in a memory, so that a communication device installed with the chip executes the method provided in the embodiment of the present application.

[0176] The embodiment of the present application also provides a chip. The chip includes an input interface, an output interface, a processor and a memory. The input interface, the output interface, the processor and the memory are connected through an internal connection path. The processor is configured to execute code in the memory. When the code is executed, the processor is configured to execute the method provided in the embodiment of the present application.

[0177] It is to be understood that the above-described processor can be a Central Processing Unit (CPU), a general-purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like. The general-purpose processor can be a microprocessor or any conventional processor, or the like. It is to be appreciated that the processor can be an Advanced RISC Machines (ARM) architecture processor.

[0178] Further, the memory can include a read-only memory and a random access memory, and can further include a non-volatile random access memory. The memory can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memory. The non-volatile memory can include a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), or a flash memory. The volatile memory can include a random access memory (RAM) used as an external cache. By way of example, but not limitation, a number of forms of RAM can be used. For example, a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synchlink DRAM (SLDRAM), and a direct rambus RAM (DR RAM) can be used.

[0179] In the above-described embodiments, all or part can be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed by a computer, all or part generates the processes or functions according to the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium.

[0180] In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. Also, the specific features, structures, materials or characteristics described can be combined in any appropriate manner in any one or more embodiments or examples. In addition, the person skilled in the art can combine and combine the different embodiments or examples described in the present specification and the features of the different embodiments or examples, without contradiction.

[0181] In addition, the terms "first", "second", etc. are used only for the purpose of description and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined with "first", "second" can explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "a plurality of" is two or more, unless otherwise explicitly specified.

[0182] Any process or method descriptions or descriptions in flow charts or otherwise described herein can be understood as representing code modules, segments, or portions of code that include one or more executable instructions for implementing specific logic functions or steps in the process. And the scope of the preferred embodiments of the present application includes additional implementation in which the functions can be performed in different orders, including substantially simultaneously or in reverse order, according to the functions involved.

[0183] The logic and / or steps represented in the flow chart or otherwise described herein, for example, can be considered as a list of executable instructions for implementing the logic function, which can be specifically implemented in any computer-readable medium for instruction execution system, device or equipment (such as computer-based system, system including processor or other system that can take instructions from instruction execution system, device or equipment and execute instructions) or in conjunction with these instructions execution system, device or equipment.

[0184] It should be understood that each part of the present application can be realized by hardware, software, firmware or a combination thereof. In the above embodiments, a plurality of steps or methods can be realized by software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above-mentioned embodiment methods can be completed by a program instructing the relevant hardware, which can be stored in a computer readable storage medium and includes one or a combination of the steps of the embodiment methods when executed.

[0185] In addition, each functional unit in each embodiment of the present application can be integrated in one processing module, or each unit can be physically present separately, or two or more units can be integrated in one module. The above-mentioned integrated module can be realized in the form of hardware or in the form of a software functional module. The above-mentioned integrated module, if realized in the form of a software functional module and sold or used as an independent product, can also be stored in a computer readable storage medium. The storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

[0186] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A process engine driven 8D quality improvement collaboration method, characterized in that, The method comprises the following steps: An 8D process corresponding to each production stage of the whole product production process is created, the 8D process is a problem solving method, the 8D process comprises eight steps from 1D to 8D, each step has specific tasks and targets, and aims to help an organization to systematically identify, analyze, solve and prevent problems; When a quality problem is found in a first production stage, a driving process engine starts a quality improvement business process; After the quality improvement business process is started, a target 8D process is automatically matched based on the first production stage, the first production stage is any production stage of the production stages, and the target 8D process is the 8D process corresponding to the first production stage; Each step of the target 8D process is defined as a process node, and a node attribute constraint condition is added between adjacent process nodes, the node attribute constraint condition comprises an execution sequence constraint condition and a data constraint condition; The driving process engine executes each process node in sequence according to the execution sequence constraint condition in the node attribute constraint condition; In the process of executing the process node, the driving process engine executes the next process node after determining that the data information entered in the currently executed process node meets the data constraint condition in the node attribute constraint condition; in this process, the driving process engine executes the following process: identifying a target keyword in the problem description content entered in the 2D step, and determining fault information matched with the target keyword in an experience database; filling related content in the fault information into 8D report fields of the 2D step, 4D step and 7D step; determining a target cause and a target improvement countermeasure matched with the fault information in the experience database; The target cause is filled into the 8D report field of the 4D step, and the target improvement countermeasure is filled into the 8D report field of the 7D step, the 8D report field is a field required to be filled in the corresponding step in the target 8D process; The driving process engine uniformly stores process data generated when the driving process engine executes the target 8D process into a specified storage device.

2. The method of claim 1, wherein, Creating an 8D process corresponding to each production stage of the whole product production process comprises the following steps: According to a preset process template, an 8D process corresponding to each production stage of the whole product production process is created.

3. The method of claim 1, wherein, The method further comprises the following steps: The driving process engine updates the 8D report field in response to a modification operation on the 8D report field.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises the following steps: When the driving process engine completes execution of each step in the target 8D process, a specified message pushing mode is used to push a completion message of each step to a person in charge of each step.

5. A process engine driven 8D quality improvement collaboration device, characterized by, The method comprises the following steps: A creating unit is configured to create an 8D process corresponding to each production stage of the whole product production process, the 8D process is a problem solving method, the 8D process comprises eight steps from 1D to 8D, each step has specific tasks and targets, and aims to help an organization to systematically identify, analyze, solve and prevent problems; The matching unit is configured to determine, when a quality problem is found in the first production stage, to drive the process engine to start a quality improvement business process. After the quality improvement business process is started, the target 8D process is automatically matched based on the first production stage, the first production stage is any one of the production stages, and the target 8D process is the 8D process corresponding to the first production stage. The execution unit is configured to define each step of the target 8D process as a process node, and add a node attribute constraint condition between adjacent process nodes, the node attribute constraint condition including an execution order constraint condition and a data constraint condition. The process engine is driven to execute each process node in sequence according to the execution order constraint condition in the node attribute constraint condition. During the process node streaming, the process engine is driven to execute the next process node after determining that the data information entered in the currently executed process node meets the data constraint condition in the node attribute constraint condition. In this process, the process engine is driven to perform the following processes: identifying a target keyword in the problem description content entered in the 2D step, and determining fault information in the experience library that matches the target keyword; filling the related content in the fault information into the 8D report field of the 2D step, the 8D report field of the 4D step, and the 8D report field of the 7D step; determining a target cause and a target improvement countermeasure in the experience library that match the fault information. The target cause is filled into the 8D report field of the 4D step, and the target improvement countermeasure is filled into the 8D report field of the 7D step. The storage unit is configured to drive the process engine to uniformly store process data generated when the process engine executes the target 8D process into a designated storage device.

6. A computer apparatus, comprising: The memory and the processor, the memory stores instructions, the instructions are loaded and executed by the processor to realize the method of any one of claims 1-4. The computer readable storage medium stores a computer program, when the computer program runs on the computer, realizes the method of any one of claims 1-4.

7. A computer readable storage medium characterized in that, The computer readable storage medium stores a computer program, when the computer program runs on the computer, realizes the method of any one of claims 1-4.

Images