8D quality improvement collaboration method and device based on process engine driving and medium

Abstract

The invention provides an 8D quality improvement collaboration method and device based on process engine driving and a medium, and can improve the problem solving speed, enhance the quality improvement effect, improve team collaboration and communication and enhance the continuous improvement ability, and the method comprises the steps: creating an 8D process corresponding to each production stage of the whole production process of a product; when it is determined that a quality problem is found in a first production stage, a target 8D process is automatically matched, the first production stage is any one of the production stages, and the target 8D process is an 8D process corresponding to the first production stage; the driving process engine executes the target 8D process according to a specified node sequence constraint mechanism, in the process, the driving process engine uses an experience library to automatically fill an 8D report field, and the 8D report field is a field needing to be filled in corresponding steps in the target 8D process; and the process engine is driven 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 present application relates to the field of quality management technology, and in particular to an 8D quality improvement collaborative method, device and medium driven by a process engine. Background Art

[0002] 8D is a problem-solving methodology, also known as the 8D method or 8D process. It consists of eight steps (1D to 8D), each with specific tasks and goals, designed to help organizations systematically identify, analyze, resolve, and prevent problems. In the quality improvement process, 8D is a key tool and methodology, enabling quality improvement to be achieved through these eight steps.

[0003] However, in the traditional 8D process, each step is simply information entry. For example, the cause analysis node (such as 4D) only enters the cause of the problem, and the improvement countermeasure node (such as 7D) only enters the improvement countermeasures for the cause of the problem. In addition, the steps are completed sequentially. Therefore, many problems may arise during the actual implementation process, such as: (1) Inefficient collaboration: Relying on manual coordination (through emails or meetings), the efficiency of cross-departmental task allocation and tracking is low, resulting in a long cycle (usually 20-30 days).

[0004] (2) Process skipping risk: Key steps (such as 4D root cause analysis and 7D preventive measures) are easily overlooked or formalized, resulting in a high recurrence rate of quality problems. For example, in order to complete the 8D improvement task as quickly as possible, some steps may be skipped, resulting in the analysis process not recording the root cause, the verification of the effect is not repeated, the lack of review and sign-off by team participants, and the lack of preventive measures, which leads to a high recurrence rate of quality problems.

[0005] (3) Data silos: The process data of traditional 8D processes are scattered across multiple systems (such as manufacturing execution system MES, quality management system QMS, and enterprise resource planning ERP), lacking real-time integration and closed-loop feedback. Summary of the Invention

[0006] The present application provides an 8D quality improvement collaborative method, device, and medium driven by a process engine to solve the problems existing in related technologies. The technical solution is as follows: In a first aspect, an embodiment of the present application provides an 8D quality improvement collaborative method driven by a process engine, comprising: Create 8D processes corresponding to each production stage of the entire product production process; When it is determined that quality problems are found in the first production stage, the target 8D process is automatically matched, where the first production stage is any production stage among the various production stages, and the target 8D process is the 8D process corresponding to the first production stage; Driving the process engine to execute the target 8D process according to the specified node sequence constraint mechanism, during which the process engine is driven to automatically fill in 8D report fields using the experience library, where the 8D report fields are the fields required to be filled in for the corresponding steps in the target 8D process; The process engine is driven to uniformly store the process data generated when the process engine executes the target 8D process in a designated storage device.

[0007] In one embodiment, creating an 8D process corresponding to each production stage of the entire product production process includes: Based on the preset process template, create 8D processes corresponding to each production stage of the entire product production process.

[0008] In one embodiment, when quality issues are identified in the first production stage, the automatic matching target 8D process includes: When it is determined that quality problems are found in the first production stage, driving the process engine to start a quality improvement business process; After the quality improvement business process is started, it is automatically matched to the target 8D process based on the first production stage.

[0009] In one embodiment, driving the process engine to execute the target 8D process according to a specified node sequence constraint mechanism includes: Each step of the target 8D process is defined as a process node, and node attribute constraints are added between adjacent process nodes, wherein the node attribute constraints include execution order constraints and data constraints; Driving the process engine to execute each process node in sequence according to the execution order constraint in the node attribute constraint; When the process node is being transferred, the process engine is driven to execute the next process node after determining that the data information entered by the currently executed process node meets the data constraint conditions in the node attribute constraint conditions.

[0010] In one embodiment, driving the process engine to automatically fill in 8D report fields using the experience library includes: Drive the process engine to identify target keywords in the problem description content entered in the 2D step, and determine the fault information matching the target keywords in the experience database; Driving the process engine to fill 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; Driving the process engine to determine the target cause and target improvement countermeasure matching the fault information in the experience database; The process engine is driven to fill the target cause into the 8D report field of the 4D step, and to fill the target improvement measure into the 8D report field of the 7D step.

[0011] In one embodiment, the method further comprises: The process engine is driven to update the 8D report field in response to a modification operation on the 8D report field.

[0012] In one embodiment, the method further comprises: When the process engine completes each step in the target 8D process, a completion message of each step is pushed to the person in charge of each step using a specified message push method.

[0013] In a second aspect, the present application also provides an 8D quality improvement collaboration device driven by a process engine, including: Creation unit, used to create 8D processes corresponding to each production stage of the entire product production process; A matching unit, configured to automatically match a target 8D process when a quality problem is found in the first production stage, wherein the first production stage is any production stage among the various production stages, and the target 8D process is the 8D process corresponding to the first production stage; an execution unit, configured to drive the process engine to execute the target 8D process according to a specified node sequence constraint mechanism, and during this process, drive the process engine to automatically fill in 8D report fields using an experience library, wherein the 8D report fields are fields required to be filled in for corresponding steps in the target 8D process; The storage unit is used to drive the process engine to uniformly store the process data generated when the process engine executes the target 8D process in a designated storage device.

[0014] In one embodiment, when the creation unit is used to create the 8D process corresponding to each production stage of the entire product production process, it is specifically used to: Based on the preset process template, create 8D processes corresponding to each production stage of the entire product production process.

[0015] In one embodiment, when the matching unit is used to automatically match the target 8D process when determining that a quality problem is found in the first production stage, it is specifically used to: When it is determined that quality problems are found in the first production stage, driving the process engine to start a quality improvement business process; After the quality improvement business process is started, it is automatically matched to the target 8D process based on the first production stage.

[0016] In one embodiment, when the execution unit 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 to: Each step of the target 8D process is defined as a process node, and node attribute constraints are added between adjacent process nodes, wherein the node attribute constraints include execution order constraints and data constraints; Driving the process engine to execute each process node in sequence according to the execution order constraint in the node attribute constraint; When the process node is being transferred, the process engine is driven to execute the next process node after determining that the data information entered by the currently executed process node meets the data constraint conditions in the node attribute constraint conditions.

[0017] In one embodiment, when the execution unit is used to drive the process engine to automatically fill in the 8D report fields using the experience library, it is specifically used to: Drive the process engine to identify target keywords in the problem description content entered in the 2D step, and determine the fault information matching the target keywords in the experience database; Driving the process engine to fill 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; Driving the process engine to determine the target cause and target improvement countermeasure matching the fault information in the experience database; The process engine is driven to fill the target cause into the 8D report field of the 4D step, and to fill the target improvement measure into the 8D report field of the 7D step.

[0018] In one embodiment, the execution unit is further configured to: The process engine is driven to update the 8D report field in response to a modification operation on the 8D report field.

[0019] In one embodiment, the execution unit is further configured to: When the process engine completes each step in the target 8D process, a completion message of each step is pushed to the person in charge of each step using a specified message push method.

[0020] In a third aspect, an embodiment of the present application further provides a computer device comprising: a memory and a processor, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement a method in any one of the above-mentioned embodiments, wherein the memory and the processor communicate with each other through an internal connection path.

[0021] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the method in any one of the above-mentioned embodiments is implemented.

[0022] The advantages or beneficial effects of the above technical solution include at least: (1) Improved problem solving speed: Using a process engine to drive the execution of the 8D process corresponding to the production stage of quality problems can speed up problem handling, reduce problem solving time, improve responsiveness, shorten the 8D improvement cycle by 30%-50%, and reduce quality improvement costs.

[0023] (2) Enhanced quality improvement effect: Driven by the process engine, process nodes can be automatically matched, quality improvement processes can be standardized, improvements can be carried out in an orderly manner, and the reliability and sustainability of the improvement effect can be improved.

[0024] (3) Improved team collaboration and communication: Driven by a process engine, it can promote collaboration and communication among team members and reduce errors and delays in information transmission.

[0025] (IV) Enhanced continuous improvement capabilities: Through systematic process-driven development, organizations can establish a culture and mechanism for continuous improvement, and continuously improve quality management levels and efficiency.

[0026] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present application will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar components or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments disclosed in this application and should not be construed as limiting the scope of this application.

[0028] Figure 1 An example flow chart of an 8D quality improvement collaborative method driven by a process engine provided in an embodiment of the present application; Figure 2 This is an example diagram of a drag-and-drop interface provided in an embodiment of the present application; Figure 3 This is an example diagram of a constraint entry interface provided in an embodiment of the present application; Figure 4 A 1D step process visualization interface provided in an embodiment of the present application; Figure 5 This is an example diagram of a reason query interface provided in an embodiment of the present application; Figure 6 A 4D step process visualization interface provided in an embodiment of the present application; Figure 7 Another 4D step process visualization interface provided in an embodiment of the present application; Figure 8 A structural block diagram of an 8D quality improvement collaboration device driven by a process engine provided in an embodiment of the present application; Figure 9 This is a structural block diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] Hereinafter, only certain exemplary embodiments are briefly described. As will be appreciated by those skilled in the art, the described embodiments may be modified in various ways without departing from the spirit or scope of the present application. Therefore, the drawings and description are to be regarded as illustrative in nature and not restrictive.

[0030] In order to facilitate understanding of the corresponding technical solutions provided in the embodiments of the present application, the eight steps 1D to 8D of the 8D process are introduced accordingly below.

[0031] 1D. Form a problem-solving team: Emphasize cross-functional teamwork. Team members must possess product and process knowledge and possess sufficient time, authority, and skills. When implementing the 8D problem-solving approach, the team's role composition is crucial. Typically, the team includes an 8D team leader, who leads and coordinates the team's work.

[0032] 2D, Problem Description: Describe the problem phenomenon in detail and specifically. When defining the problem, it is necessary to clearly define its boundaries to ensure the accuracy and controllability of the problem description. A detailed description is usually performed using the 5W2H analysis method.

[0033] 3D, Containment Temporary Measures: Develop, validate, and implement temporary measures to isolate the problem and prevent it from escalating until fundamental measures are implemented. The goal of this phase is to isolate the problem, buying time for the 8D team to conduct in-depth analysis and identify the root cause.

[0034] 4D, Root Cause Analysis: In finding the root cause of the problem and determining the real source of the problem, we mainly use the "Five Whys" tool to gradually reveal the deep-seated reasons behind the problem through continuous questioning and in-depth analysis.

[0035] 5D. Corrective Action: After identifying the root cause, develop long-term countermeasures to ensure the best improvement plan to prevent the problem from recurring.

[0036] 6D, Process and Effect Verification: Develop an implementation plan, monitor and verify its effects, and ensure that the problem-solving standards are met. Monitor its implementation to ensure its effectiveness.

[0037] 7D. Preventive measures: After the improvement measures are defined, establish a long-term monitoring mechanism to evaluate the effectiveness of the improvement measures and standardize operating procedures to prevent the problem from recurring.

[0038] 8D. Team summary: Summarize and review the improvements to ensure that the improvement experience is included in the experience library.

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

[0040] Figure 1 FIG. 8 is a flow chart of an 8D quality improvement collaborative method driven by a process engine according to an embodiment of the present application. Figure 1 As shown, the method may include the following steps: S110. Create 8D processes corresponding to each production stage of the entire product production process.

[0041] In one embodiment, an 8D process corresponding to each production stage of the entire product production process can be created based on a preset process template.

[0042] For example, you can create 8D processes corresponding to each production stage of the entire product production process based on the same preset process template. You can also pre-set corresponding process templates for each production stage of the entire product production process, and then subsequently create 8D processes corresponding to each production stage of the entire product production process based on the process templates corresponding to each production stage of the entire product production process.

[0043] As an example, the various production stages of the entire product production process may include but are not limited to: supplier raw material receipt, inventory transfer, ingredient production, process collection, process inspection, semi-finished product processing, finished product warehousing and finished product shipment.

[0044] In the embodiment of the present application, by executing step S110, it is possible to automatically match the corresponding 8D process when quality problems are found in various production stages of the entire product production process, and to effectively carry out targeted quality improvements in each production stage.

[0045] S120: When quality problems are found in the first production stage, the target 8D process is automatically matched.

[0046] In one embodiment, the first production stage is any production stage in the entire production process of the product, and the target 8D process is the 8D process corresponding to the first production stage.

[0047] As an example, if a quality issue is discovered at a certain stage during the production process, on-site inspection, or after-sales service, a prompt message can be sent through the QMS. This prompt message can be used to indicate that a quality issue was discovered during the first production stage. Accordingly, when a prompt message is received from the QMS, it can be determined that a quality issue was discovered during the first production stage.

[0048] In one embodiment, when quality issues are identified during the first production phase, the process engine can be driven to initiate a quality improvement business process. This process can then be initiated to improve quality by driving the execution of the corresponding 8D process. Once initiated, the quality improvement business process can automatically match the target 8D process based on the first production phase.

[0049] For example, during the process of creating the 8D process corresponding to each production stage of the entire product production process in step S110, identification information for each production stage can be set. Then, the identification information for each production stage can be associated with its corresponding 8D process. This can yield an association between the identification information for each production stage and the corresponding 8D process. Subsequently, based on the identification information for the first production stage and this association, the target 8D process can be matched.

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

[0051] S130 , driving the process engine to execute the target 8D process according to the specified node sequence constraint mechanism. During this process, the driving process engine automatically fills in the 8D report fields using the experience library.

[0052] In one embodiment, the 8D report fields are fields that need to be filled in corresponding steps in the target 8D process.

[0053] In one embodiment, the implementation process of driving the process engine to execute the target 8D process according to the specified node sequence constraint mechanism may include the following steps: S131. Define each step of the target 8D process as a process node, and add node attribute constraints between adjacent process nodes.

[0054] During specific implementation, the node attribute constraint condition may include an execution order constraint condition and a data constraint condition.

[0055] As an example, each step of the target 8D process can be defined as a process node through the process designer, and node attribute constraints can be added between adjacent process nodes. For example, Figure 2As shown, in the drag-and-drop interface provided by the process designer, each step of the target 8D process can be customized as a visual process node, and constraint adding controls can be set on the connection lines between process nodes. In this way, the constraint adding control can be triggered by clicking to display the constraint entry interface. After entering the node attribute constraints between adjacent process nodes on the constraint entry interface, the node attribute constraints between adjacent process nodes can be added.

[0056] For example, in Figure 3 On the constraint entry screen, enter the execution order constraints for the node attribute constraints, including the node display order and whether they are required. Once completed, click "Save" to add the execution order constraints between adjacent process nodes.

[0057] S132 . Drive the process engine to execute each process node in sequence according to the execution order constraint in the node attribute constraint.

[0058] In specific implementation, by driving the process engine to execute each process node in sequence according to the execution order constraints in the node attribute constraints, the compliance of the target 8D process can be enforced, and the process engine can be prevented from skipping certain steps of the target 8D process.

[0059] For example, in the application of the traditional 8D process, the 3D step, the 6D step, and the 8D step are steps that are easily skipped. In the embodiment of the present application, by executing step S132, these three steps can be avoided from being skipped manually.

[0060] S133. When the process node is being transferred, the driving process engine executes the next process node after determining that the data information entered into the currently executed process node satisfies the data constraint conditions in the node attribute constraint conditions.

[0061] In practice, these data constraints can be used to force process nodes to enter required data, which can be set based on actual needs. This means that the data constraint requires the earlier of two adjacent process nodes to enter the required data before the later one (i.e., the later one) can be executed.

[0062] In the embodiment of the present application, by executing step S133, it is possible to prevent the omission of entry of necessary data in the process of driving the process engine to execute the process node.

[0063] In one embodiment, the process of driving the process engine to automatically fill in the 8D report fields using the experience library may include the following steps: S131a. The driving process engine identifies target keywords in the problem description content entered in the 2D step, and determines fault information matching the target keywords in the experience database.

[0064] In practice, the process engine completes the input of the problem description content when executing the 2D step of the target process. After that, it can automatically match the fault information in the experience library based on the target keywords in the problem description content.

[0065] As an example, you can set keywords based on potential issues that may occur at each stage of the product production process. These keywords and their corresponding production stages can be stored in an experience database. Later, you can narrow down the keyword range based on the production stage where the quality issue was discovered. You can also set fault information corresponding to the keywords at each production stage and store it in the experience database. These keywords and fault information can then be archived and updated using historical summaries of the 8D process.

[0066] For example, Figure 4 As shown, the problem description entered in step 2D is: "During the process transfer on May 21, 2025, a batch of housings were found to be deformed due to extrusion. The location of the deformation was Assembly Line 001, the time was 1:30 PM, and the quantity was 50." Therefore, the corresponding production stage is the inventory transfer stage, and the keywords in this inventory transfer could be "housing," "deformation," and "Assembly Line 001." This means that the process engine identifies the target keywords in the problem description entered in step 1D as "housing," "deformation," and "Assembly Line 001."

[0067] The process engine matches the target keywords "shell", "deformation", and "001 assembly line" in the experience database. The fault information obtained may include order number, problem source, material code, material name, process definition, defect code, defect code description and other related information.

[0068] S132a. The driving process engine fills 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.

[0069] For example, Figure 4 As shown, the order 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.

[0070] Exemplarily, the defect code in the fault information can be filled into the 8D report field of the 4D step and the 8D report field of the 7D step respectively.

[0071] S133a. Drive the process engine to determine the target cause and target improvement measures that match the fault information in the experience database.

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

[0073] As an example, the causes and improvement measures corresponding to the corresponding defect codes can be stored in the experience library. Subsequently, the causes and improvement measures corresponding to the defect codes can be found from the experience library based on the defect codes, and then the corresponding causes and improvement measures can be selected from them.

[0074] For example, take the reasons as an example, Figure 5 As shown, in the cause query interface provided by the experience library, the corresponding cause (such as the cause of occurrence) can be queried based on the defect code in the fault information to obtain two root causes. When the corresponding responsible person selects one of the root causes, the selected root cause becomes the target cause.

[0075] S134a, driving the process engine to fill the target cause into the 8D report field of the 4D step, and to fill the target improvement measure into the 8D report field of the 7D step.

[0076] For example, Figure 6 As shown, the process engine can be driven to fill the target cause "improper carrier protection during material outbound transportation causes material appearance to be bumped and scratched" into the cause position in the 8D report field of the 4D step.

[0077] It should be understood that steps S131a to S134a are performed alternately with steps S131 to S133.

[0078] In an embodiment of the present application, by executing step S130, human intervention that affects the execution efficiency of the target 8D process can be avoided, which helps to improve the efficiency of improving the quality problems found and achieve effective improvements. The target 8D process can also be executed strictly in the corresponding order, realizing systematic process management and control, and avoiding human skipping of corresponding steps, thereby avoiding problems such as process confusion and missing steps, and ensuring the improvement effect of the quality problems found.

[0079] Considering that unpredictable causes of quality problems may be encountered in actual applications, if only the causes provided in the experience library are used, there will be unreliability problems. Based on this, during the execution of step S130, the embodiment of the present application can drive the process engine to respond to the modification operation on the 8D report field and update the 8D report field.

[0080] For example, you can double-click Figure 6The display position of the cause of occurrence in the 8D report field "During the transportation of materials out of the warehouse, the carrier is improperly protected, resulting in bumps and scratches on the surface of the materials" can trigger the modification of the cause of occurrence. After the modification, click other display positions in the interface to complete the modification and update of the cause of occurrence.

[0081] In the specific implementation, when modifying the 8D report field, you can add the root cause of the cause. For example, you can select Figure 7 When the root cause is found, use the 5 why method to add the modified and updated root cause.

[0082] That is, in the embodiment of the present application, the 8D report fields can be allowed to be modified and updated to adapt to different production environments and situations of quality problems caused by different reasons.

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

[0084] During specific implementation, the storage device can be configured according to actual needs. For example, it can be a local storage device, cloud storage, QMS, etc. This embodiment of the present application does not limit this.

[0085] In an embodiment of the present application, by executing step S140, the process data of the target 8D process can be automatically stored in a unified manner, realizing data collection and analysis without relying on manual labor, and solving the data island problem existing in traditional 8D process applications, avoiding inaccurate or incomplete data that affects the scientific nature of decision-making, thereby realizing real-time integration of data and closed-loop feedback.

[0086] In an applicable scenario provided in an embodiment of the present application, the process engine-driven 8D quality improvement collaborative method provided in an embodiment of the present application may further include the following: S150. When the process engine completes each step in the target 8D process, a completion message of each step is pushed to the person in charge of each step using a specified message push method.

[0087] In one embodiment, in step S131, when defining each step of the target 8D process as a process node, a corresponding message push method can be configured for each process node to implement process task notifications. Subsequently, upon completion of each process node, the process engine can automatically push a completion message to the person responsible for that process node. This completion message can include, for example, the relevant information entered for the process node and the completion time.

[0088] As an example, the designated message push method may be one of email push, WeChat push, enterprise WeChat push, etc.

[0089] In an embodiment of the present application, by executing step S150, automatic notification can be made based on the process progress executed by the driving engine to achieve real-time updates of the execution status of the target 8D process, thereby being able to track and monitor the execution status of each step, preventing information loss or errors, and making the improvement process of discovered quality problems transparent.

[0090] From the above description, it can be seen that the 8D quality improvement collaborative method based on process engine drive provided in the embodiment of the present application can achieve the following beneficial effects: (1) Improved problem solving speed: Using a process engine to drive the execution of the 8D process corresponding to the production stage of quality problems can speed up problem handling, reduce problem solving time, improve responsiveness, shorten the 8D improvement cycle by 30%-50%, and reduce quality improvement costs.

[0091] (2) Enhanced quality improvement effect: Driven by the process engine, process nodes can be automatically matched, quality improvement processes can be standardized, improvements can be carried out in an orderly manner, and the reliability and sustainability of the improvement effect can be improved.

[0092] (3) Improved team collaboration and communication: Driven by a process engine, it can promote collaboration and communication among team members and reduce errors and delays in information transmission.

[0093] In actual application, it can also realize automatic notification of tasks to people and real-time monitoring, which can improve work efficiency by 30%.

[0094] (IV) Enhanced continuous improvement capabilities: Through systematic process-driven development, organizations can establish a culture and mechanism for continuous improvement, and continuously improve quality management levels and efficiency.

[0095] For example, when the process engine drives the execution of the 8D process, the experience library can be loaded to recommend the causes of defects and improvement measures, which can improve efficiency by more than 50% and enable the experience library to be fully reused.

[0096] For example, you can set defect codes, such as defect codes corresponding to problem defects such as oversize, scratches, deformation, and dirt. When a problem defect occurs, select the corresponding defect code. Since the defect code can be used as a unique identifier for archiving and reference in the experience library, each time the problem is improved, the defect code will be automatically identified. Then, the defect code can be used to query the historical improvement data in the experience library. When the improvement data is queried, it will be automatically displayed and filtered. At this time, you only need to manually select the cause and countermeasures of the problem that need to be loaded. In this way, the data in the experience library can be reused. At the same time, after the improvement is completed, the data in the experience library can be supplemented and improved according to the defect code to enrich the relevant content of the experience library.

[0097] Figure 8 FIG. 8 is a block diagram of an 8D quality improvement collaborative device driven by a process engine according to an embodiment of the present application. Figure 8 As shown, the device may include: A creation unit 210 is used to create an 8D process corresponding to each production stage of the entire product production process; The matching unit 220 is configured to automatically match a target 8D process when a quality problem is found in the first production stage, where the first production stage is any production stage among the various production stages, and the target 8D process is the 8D process corresponding to the first production stage; An 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 is driven to automatically fill in the 8D report fields using the experience library. The 8D report fields are the fields required to be filled in the corresponding steps in the target 8D process. The 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 a designated storage device.

[0098] In one embodiment, when creating the 8D process corresponding to each production stage of the entire product production process, the creation unit 210 is specifically configured to: Based on the preset process template, create 8D processes corresponding to each production stage of the entire product production process.

[0099] In one embodiment, when the matching unit 220 is used to automatically match the target 8D process when determining that a quality problem is found in the first production stage, it is specifically used to: When quality problems are found in the first production stage, the process engine is driven to start the quality improvement business process; After the quality improvement business process is started, it is automatically matched to the target 8D process based on the first production stage.

[0100] In one embodiment, 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 to: Define each step of the target 8D process as a process node, and add node attribute constraints between adjacent process nodes. Node attribute constraints include execution order constraints and data constraints. Drive the process engine to execute each process node in sequence according to the execution order constraints in the node attribute constraints; When the process node is flowing, the driving process engine executes the next process node after determining that the data information entered by the currently executed process node meets the data constraint conditions in the node attribute constraint conditions.

[0101] In one embodiment, when the execution unit 230 is used to drive the process engine to automatically fill in the 8D report fields using the experience library, it is specifically used to: The driving process engine identifies the target keywords in the problem description entered in the 2D step and determines the fault information matching the target keywords in the experience database; The driving process engine fills 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; Drive the process engine to determine the target cause and target improvement measures that match the fault information in the experience database; The driving process engine fills the target cause into the 8D report field of the 4D step, and fills the target improvement measure into the 8D report field of the 7D step.

[0102] In one embodiment, the execution unit 230 is further configured to: The driving process engine updates the 8D report field in response to the modification operation on the 8D report field.

[0103] In one embodiment, the execution unit 230 is further configured to: When the process engine executes each step in the target 8D process, it pushes the completion message of each step to the person in charge of each step using the specified message push method.

[0104] The functions of each unit in the process engine-driven 8D quality improvement collaborative device in the embodiment of the present application can be found in the corresponding description in the above method and will not be repeated here.

[0105] Figure 9 FIG. 1 shows a block diagram of a computer device according to an embodiment of the present application. Figure 9 As shown, 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 process engine-driven 8D quality improvement collaborative method in the above embodiment. The number of memory 310 and processor 320 can be one or more.

[0106] The computer device also includes: The communication interface 330 is used to communicate with external devices and perform data exchange transmission.

[0107] If the memory 310, processor 320, and communication interface 330 are implemented independently, the memory 310, processor 320, and communication interface 330 can be connected to each other via a bus and communicate with 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. 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 diagram, but this does not mean that there is only one bus or one type of bus.

[0108] 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 communicate with each other through an internal interface.

[0109] An embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program runs on a computer, the method provided in the embodiment of the present application is implemented.

[0110] An embodiment of the present application also provides a chip, which includes a processor for calling and executing instructions stored in a memory, so that a communication device equipped with the chip executes the method provided in the embodiment of the present application.

[0111] An embodiment of the present application also provides a chip, including: 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 used to execute the code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the application.

[0112] It should be understood that the processor described above may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor. It is worth noting that the processor may be a processor that supports the Advanced RISC Machines (ARM) architecture.

[0113] Furthermore, optionally, the above-mentioned memory may include read-only memory and random access memory, and may also include non-volatile random access memory. The memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory may include random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available. For example, static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).

[0114] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0115] In the description of this specification, the reference terms "one embodiment," "some embodiments," "example," "specific example," or "some examples" mean that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials, or characteristics described may be combined in any appropriate manner in any one or more embodiments or examples. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification, as well as features of different embodiments or examples, unless they are mutually inconsistent.

[0116] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features being referred to. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. Throughout the description of this application, "plurality" means two or more, unless otherwise specifically defined.

[0117] Any process or method description in a flow chart or otherwise described herein can be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process. The scope of the preferred embodiments of the present application includes additional implementations in which the functions may be performed in a different order than shown or discussed, including in a substantially simultaneous manner or in a reverse order depending on the functions involved.

[0118] The logic and / or steps represented in the flowchart or otherwise described herein may be considered, for example, as a sequenced list of executable instructions for implementing the logical functions, and may be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device).

[0119] It should be understood that various parts of the present application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0120] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the aforementioned integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium. The storage medium may be a read-only memory, a magnetic disk, or an optical disk, etc.

[0121] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily conceive of various modifications or substitutions within the technical scope disclosed in this application, and such modifications or substitutions should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. An 8D quality improvement collaborative method driven by a process engine, characterized by: include: Create 8D processes corresponding to each production stage of the entire product production process; When it is determined that quality problems are found in the first production stage, the target 8D process is automatically matched, where the first production stage is any production stage among the various production stages, and the target 8D process is the 8D process corresponding to the first production stage; Driving the process engine to execute the target 8D process according to the specified node sequence constraint mechanism, during which the process engine is driven to automatically fill in 8D report fields using the experience library, where the 8D report fields are the fields required to be filled in for the corresponding steps in the target 8D process; The process engine is driven to uniformly store the process data generated when the process engine executes the target 8D process in a designated storage device.

2. The method according to claim 1, characterized in that The 8D processes corresponding to each production stage of the entire product production process include: Based on the preset process template, create 8D processes corresponding to each production stage of the entire product production process.

3. The method according to claim 1, characterized in that When quality issues are identified in the first production stage, the 8D process for automatically matching targets includes: When it is determined that quality problems are found in the first production stage, driving the process engine to start a quality improvement business process; After the quality improvement business process is started, it is automatically matched to the target 8D process based on the first production stage.

4. The method according to claim 1, wherein Driving the process engine to execute the target 8D process according to the specified node sequence constraint mechanism includes: Each step of the target 8D process is defined as a process node, and node attribute constraints are added between adjacent process nodes, wherein the node attribute constraints include execution order constraints and data constraints; Driving the process engine to execute each process node in sequence according to the execution order constraint in the node attribute constraint; When the process node is being transferred, the process engine is driven to execute the next process node after determining that the data information entered by the currently executed process node meets the data constraint conditions in the node attribute constraint conditions.

5. The method according to claim 1, wherein Driving the process engine to automatically fill in 8D report fields using the experience library includes: Drive the process engine to identify target keywords in the problem description content entered in the 2D step, and determine the fault information matching the target keywords in the experience database; Driving the process engine to fill 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; Driving the process engine to determine the target cause and target improvement countermeasure matching the fault information in the experience database; The process engine is driven to fill the target cause into the 8D report field of the 4D step, and to fill the target improvement measure into the 8D report field of the 7D step.

6. The method according to claim 1, wherein The method further comprises: The process engine is driven to update the 8D report field in response to a modification operation on the 8D report field.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: When the process engine completes each step in the target 8D process, a completion message of each step is pushed to the person in charge of each step using a specified message push method.

8. An 8D quality improvement collaborative device driven by a process engine, characterized in that: include: Creation unit, used to create 8D processes corresponding to each production stage of the entire product production process; A matching unit, configured to automatically match a target 8D process when a quality problem is found in the first production stage, wherein the first production stage is any production stage among the various production stages, and the target 8D process is the 8D process corresponding to the first production stage; an execution unit, configured to drive the process engine to execute the target 8D process according to a specified node sequence constraint mechanism, and during this process, drive the process engine to automatically fill in 8D report fields using an experience library, wherein the 8D report fields are fields required to be filled in for corresponding steps in the target 8D process; The storage unit is used to drive the process engine to uniformly store the process data generated when the process engine executes the target 8D process in a designated storage device.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory stores instructions, and the instructions are loaded and executed by the processor to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is run on a computer, the method according to any one of claims 1 to 7 is implemented.

Images