Detailed Description
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only examples or embodiments of the invention, from which it is possible for a person skilled in the art, without inventive effort, to apply the invention also in other similar contexts. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.
As used in this disclosure and in the claims, the terms "a," "an," "the," and/or "the" are not intended to be inclusive in the singular, but rather are inclusive in the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements. The term "and/or" as used in this document includes any and all combinations of one or more of the associated listed items.
Flow charts are used in the present invention to illustrate the operations performed by a system according to embodiments of the present invention. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, various steps may be processed in reverse order or simultaneously. Meanwhile, other operations are added to or removed from these processes.
The invention provides a problem management method. Fig. 1 is a flowchart illustrating a problem management method according to an embodiment of the present invention. As shown in fig. 1, the problem management method according to the embodiment of the present invention includes the following steps:
step 101, receiving a problem input by a system administrator, wherein the problem comprises a problem description and a problem responsible person, and notifying the problem responsible person of the problem;
102, receiving reason analysis input, correction preventive measure input and allocation of an executor on an interface of a problem responsible person, and informing the executor of the correction preventive measure;
103, receiving an execution record of the corrective precautionary measure on an interface of the executor, and submitting the executed corrective precautionary measure to a problem liability person for approval; and
at step 104, confirmation of the corrective preventative action being performed is received at the interface of the person responsible for the problem.
The following describes each step in the problem management method in detail:
in step 101, a problem entered by a system administrator is received, the problem including a problem description and a problem principal, and the problem principal is notified of the problem.
FIG. 9 is a schematic diagram illustrating a problem management flow according to an embodiment of the present invention. As shown in fig. 9, the persons involved in the problem management flow include: problem discoverer/recipients, system administrators, problem liability people, and corrective precautions (CAPA) performers. Sources of problems may include customer complaints, market regulatory, customer inspection, third party inspection, daily inspection, internal inspection, changes, deviations, failures, and the like. When the problem source is in the organization, the problem finder in the organization submits the problem description to a system administrator; when the problem source is outside the organization (e.g., a customer), the problem description is communicated to the problem receiver inside the organization by personnel outside the organization, and then submitted to the system administrator by the problem receiver. The problem finder/receiver does not need to use the system in the embodiment of the invention, and one person of the system administrator can be responsible for the system operation, namely, the management of the problems of all sources. Thus, when a problem occurs, the system administrator is responsible for receiving the problem and logging the problem into the system. In one example, the system administrator may be Quality Assurance (QA) personnel. After receiving the problem description, the system administrator needs to judge and assign the person responsible for the problem. Thus, the questions entered by the system administrator within the issue management system include the issue description and the issue principal. After the system administrator enters the problem, the system notifies the problem responsible person of the problem. In one example, the system may notify the problem responsible person of the problem by mail and/or text message.
Optionally, the issue may also include the issue source and resolution time limit. When a system administrator records the problems in the problem management system, the problem source and the solution time limit of the problems can be recorded.
FIG. 2 is an illustration of a problem entry interface of the problem management system, according to an embodiment of the present invention. As shown in FIG. 2, the system administrator may enter the source of the problem, the type of audit, the classification of the problem, the description of the problem, whether corrective precautions (CAPA) are required, the principal, and the date of the target solution (i.e., the term of resolution of the problem) at the problem entry interface.
In step 102, a cause analysis entry, a corrective preventative action entry, and an assignment of a human actor are received on the interface of the problem responsible person and the human actor is notified of the corrective preventative action.
And after the problem responsible person receives the problems input by the system administrator, the reason of the problems is analyzed. The person responsible for the problem makes corresponding Corrective Action and Productive Action (CAPA) based on the reason analysis. CAPA can be divided into corrective measures, which are measures taken to eliminate the cause of a failure or other undesirable condition that has been discovered, and preventative measures, which are measures taken to eliminate the cause of a potential failure or trend. One question may correspond to one or more CAPAs. The problem responsible person, after formulating the CAPA, distributes one or more CAPA tasks to the corresponding one or more actors.
After the problem responsible person completes the reason analysis, the CAPA is established and the executive is allocated, the reason analysis and the CAPA are recorded and the executive is allocated on an interface of the problem responsible person in the system. Optionally, the problem responsible person may also determine a correction time limit for the CAPA and enter the system, which may receive the correction time limit for the CAPA on the interface of the problem responsible person. After the problem responsible person makes an assignment of the actor to CAPA within the system, the system notifies the assigned actor of the CAPA online. In one example, the assigned performer may be notified by way of a system message, email, or text message.
FIG. 3 is an illustration of an entry interface for a problem responsible person of the problem management system, according to an embodiment of the present invention. As shown in FIG. 3, the problem responsible person may perform root cause analysis, entry of measures (i.e., CAPA), CAPA responsible person, and CAPA predicted completion dates at the entry interface.
In step 103, a record of the execution of the corrective action is received on the implementor's interface and the executed corrective action is submitted to the problem responsible person for approval.
After the system notifies the actor of CAPA, the actor receives CAPA on the actor's interface and begins executing CAPA. After the executive completes the execution of the CAPA, the executive records the execution of the CAPA on the interface of the executive, and submits the executed CAPA to the problem accountant for examination and approval. The execution record may include a record indicating that the implementer has performed CAPA and may include evidence of the necessary rectification. The issue management system receives these execution records and submits them to the issue accountant for review along with the CAPA.
FIG. 4 is a CAPA management interface for an actor of the issue management system, shown in accordance with an embodiment of the present invention. As shown in FIG. 4, the implementer may view all CAPA performed by the practitioner at the CAPA management interface. The implementer may supplement CAPA by clicking on a "compose" button in the interface. The executive may submit the executed CAPA to the issue liability person for approval by clicking on a "submit" button in the interface.
Optionally, receiving the cause analysis entry, the corrective action entry, and the assignment of the performer on the interface of the problem responsible person may further include generating a problem reformulation plan on the interface of the system administrator and/or the problem responsible person, the problem reformulation plan including the corrective action of the assigned performer.
After receiving the cause analysis entry, the CAPA entry, and the assignment of the executor on the interface of the problem responsible person, the system may automatically generate a problem rectification plan based on all CAPAs associated with the problem and the assigned executives and present the problem rectification plan to the system administrator and/or the problem responsible person on the interface of the system administrator and/or the problem responsible person.
FIG. 5 is an interface of the issue management system illustrating viewing an issue rectification plan, according to an embodiment of the present invention. The system administrator can acquire the problem rectification plan through the interface, so that the problem rectification situation can be comprehensively known. A system administrator may derive a problem reformulation plan to send to a problem finder or problem recipient.
In step 104, a confirmation of the corrective action performed is received on the interface of the person responsible for the problem.
After the executive submits the executed CAPA to the problem accountant for approval, the problem accountant audits the content submitted by the executive. When the problem responsible person passes the executed CAPA audit, the problem responsible person confirms the executed CAPA on the problem responsible person's interface within the system, and the system receives confirmation of the executed CAPA.
Optionally, when the problem-responsible person fails the performed CAPA audit, the performed CAPA may be rejected on the problem-responsible person's interface within the system, and then the performing person may replenish the CAPA for a further audit.
In summary, in the problem management method in the embodiment of the present invention, the problem is managed by the system administrator in the problem management system, so that unified management of problems from multiple sources is realized, manpower and material resources are saved, and the problem management efficiency of the mechanism is greatly improved.
Optionally, the problem management method in the embodiment of the present invention may further include: after all of the corrective precautions associated with the issue have been confirmed, an issue correction report is generated on the system administrator's interface, which may include a description of the issue and the corrective precautions that have been completed.
When all CAPAs associated with the issue are confirmed, an issue correction report may be generated on a system administrator's interface for presentation to the system administrator, where the issue correction report may include a description of the issue and the CAPAs completed. FIG. 6 is an interface of the issue management system illustrating viewing of issue rectification reports, according to an embodiment of the present invention. As shown in fig. 6, a system administrator may obtain a problem rectification report on the interface. The problem rectification report includes two parts, a problem and CAPA. The system administrator can fully understand the problems and the condition of CAPA associated with the problems through the problem rectification report.
As shown in fig. 9, a system administrator may export a problem correction report from the system and send it to a problem finder or problem recipient for their confirmation of the problem correction content.
Optionally, the problem management method in the embodiment of the present invention may further include: after the problem rectification report is confirmed, the problem associated with the problem rectification report is closed.
A system administrator may validate problem rectification reports within the system. In one example, a system administrator may perform a confirmation operation on a problem rectification report within the system after the problem finder or problem recipient confirms the problem rectification report. After the problem rectification report is confirmed, the problem associated with the problem rectification report is closed. Alternatively, after the problem closes, all records relating to the problem may be archived for storage, for example, as electronic data for long term storage within the problem management system.
Optionally, the problem management method in the embodiment of the present invention may further include: the status of the problem and corrective precautions associated with the problem responsible person is presented on the problem responsible person's interface.
By presenting the problems and the status of the CAPA associated with the problem responsible person on the interface of the problem responsible person, the problem responsible person can view all the problems and the status of the CAPA associated with the problem responsible person, thereby improving the efficiency of the problem responsible person in processing the problems.
The issue management system may also provide an organizational interface for an organization to view for organizational management.
Optionally, the problem management method in the embodiment of the present invention may further include: presenting a status of issues and corrective precautions associated with the organization on the organization interface.
By presenting the problems and CAPA status associated with the organization on the organization interface, the organization can view all the problems and CAPA status associated with the organization, thereby improving the efficiency of the organization in managing the problems.
Optionally, the problem management method in the embodiment of the present invention may further include: the problem classification, problem liability and cause distribution associated with the organization are counted and presented on the organization interface.
The problem management system can count problem classifications, problem accountants and reason distributions associated with the organization and present the statistics on an organization interface for the organization to view, so that the organization can uniformly view the distribution of the final root causes of the problems from various sources.
FIG. 7 is a problem statistics interface of the problem management system shown in accordance with an embodiment of the present invention. As shown in fig. 7, the problem statistics interface includes information such as a problem quantity overview, problem solutions of individual responsible persons, problem classifications, and problem levels. By carrying out statistics on problem classification, problem accountants and reason distribution and presenting the statistical results by adopting a visual interface, the organization can intuitively and comprehensively know the problems, so that the problems can be systematically solved and the problem management efficiency can be further improved.
The invention also provides a problem management system, comprising: a memory for storing instructions executable by the processor; and a processor for executing the instructions to implement the issue management method as described above.
FIG. 8 is a system block diagram illustrating an issue management system in accordance with an embodiment of the present invention. The issue management system 800 may include an internal communication bus 801, a Processor (Processor)802, a Read Only Memory (ROM)803, a Random Access Memory (RAM)804, a communication port 805, and a hard disk 807. The internal communication bus 801 may enable data communication among the components of the issue management system 800. The processor 802 may make the determination and issue the prompt. In some embodiments, the processor 802 may be comprised of one or more processors. The communication port 805 may enable data communication of the issue management system 800 with the outside. In some embodiments, the issue management system 800 may send and receive information and data from a network through the communication port 805. The issue management system 800 may also include various forms of program storage units and data storage units, such as a hard disk 807, Read Only Memory (ROM)803 and Random Access Memory (RAM)804, capable of storing various data files for use in computer processing and/or communications, as well as possible program instructions for execution by the processor 802. The processor executes these instructions to implement the main parts of the method. The processor executes these instructions to implement the main parts of the method. The results processed by the processor are communicated to the user device through the communication port and displayed on the user interface.
For example, the problem management process can be implemented as a computer program stored in the hard disk 807 and loaded into the processor 802 for execution to implement the method of the present invention.
The invention also provides a computer readable medium having stored thereon computer program code which, when executed by a processor, implements a problem management method as described above.
When implemented as a computer program, the problem management process may also be stored as an article of manufacture in a computer readable storage medium. For example, computer-readable storage media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD)), smart cards, and flash memory devices (e.g., electrically Erasable Programmable Read Only Memory (EPROM), card, stick, key drive). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media (and/or storage media) capable of storing, containing, and/or carrying code and/or instructions and/or data.
It should be understood that the above-described embodiments are illustrative only. The embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, and/or other electronic units designed to perform the functions described herein, or a combination thereof.
Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing disclosure is only illustrative and not limiting of the invention. Various modifications, improvements and adaptations of the present invention may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed within the present invention and are therefore within the spirit and scope of the exemplary embodiments of this invention.
Also, the present invention has been described using specific terms to describe embodiments of the invention. Such as "one embodiment," "an embodiment," and/or "some embodiments" means a feature, structure, or characteristic described in connection with at least one embodiment of the invention. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some of the features, structures, or characteristics of one or more embodiments of the present invention may be combined as suitable.
Aspects of the present invention may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. The processor may be one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), digital signal processing devices (DAPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. Furthermore, aspects of the present invention may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips … …), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD) … …), smart cards, and flash memory devices (e.g., card, stick, key drive … …).
Similarly, it should be noted that in the preceding description of embodiments of the invention, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to suggest that the claimed subject matter requires more features than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.
Although the present invention has been described with reference to the present specific embodiments, it will be appreciated by those skilled in the art that the above embodiments are merely illustrative of the present invention and various equivalent changes and substitutions may be made without departing from the spirit of the invention, and therefore, it is intended that all changes and modifications to the above embodiments, which fall within the true spirit of the invention, fall within the scope of the claims of the present invention.