CN111222778A

CN111222778A - Project inspection management method, system and computer readable medium

Info

Publication number: CN111222778A
Application number: CN201911413358.6A
Authority: CN
Inventors: 陆益超; 张洋; 段成辉; 毛怡燕
Original assignee: Mobilemd System Jiaxing Co ltd
Current assignee: SHANGHAI YIKAI INTELLIGENT TECHNOLOGY Co.,Ltd.
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2020-06-02

Abstract

The invention provides a project inspection management method, a project inspection management system and a computer readable medium. The method realizes the project inspection process in the project inspection management system, and can ensure that inspection related personnel can input inspection related information on line and accurately inform the inspection related personnel, thereby greatly shortening the time required by the inspection process and improving the project inspection management efficiency of an organization.

Description

Project inspection management method, system and computer readable medium

Technical Field

The present invention relates to the field of quality management, and more particularly, to a project audit management method, system and computer readable medium.

Background

At present, organizations (such as large enterprises and research centers) often perform multiple projects simultaneously, and each project has a plurality of roles such as different researchers, project managers and coordinators. After the inspection party puts forward the inspection requirements, the following problems often occur: it is difficult to notify each relevant person intuitively (especially when the person has different roles in different items); it is difficult to intuitively retrieve and manage audit scenarios and audit CAPA (corrective precautions); the inspection report and the inspection discovery items depend on paper transmission, the procedure is complicated, and the process is time-consuming; special persons are required to manage, coordinate and track inspection progress and CAPA completion progress.

Currently, the inspection is performed in an offline manner, and the inspection plan is usually communicated in a man-by-man manner, a mail manner, a telephone manner and the like. The information generated in the inspection and communication process is not managed in a centralized way, and the situation that the plan needs to be modified by repeated communication due to information loss and information error often occurs. And after the inspection is finished, reporting and project inspection management are carried out in a paper mode.

Organizations often conduct multiple projects simultaneously, undergoing multiple audits each year. Each audit often creates a number of problems, each of which requires a targeted analysis and corrective precautions to be taken. Therefore, for organizations, a large number of project inspection and problems need to be dealt with each year, and methods capable of improving project inspection management efficiency are needed.

Disclosure of Invention

The technical problem to be solved by the present invention is to provide a project inspection management method, system and computer readable medium, which can record inspection related information on line and accurately notify inspection related personnel.

In order to solve the technical problem, the invention provides a project inspection management method, which comprises the following steps: generating an inspection plan according to the input of an inspector, wherein the inspection plan comprises an inspection project name, a project manager and inspection contents, and informing the related personnel of the inspection plan, wherein the related personnel comprises the project manager; receiving the questions input by the auditor and generating an audit report to inform a project manager, wherein the audit report comprises one or more questions, and each question comprises a question description; presenting an inspection report on an interface of a project manager, and notifying a corresponding problem responsible person of the problems in the inspection report according to the distribution of the project manager; receiving reason analysis input, correction preventive measure input and executor distribution on an interface of a problem responsible person, and informing the executor of the correction preventive measure; receiving an execution record of the corrective action on the executor's interface and submitting the executed corrective action to an approval by the problem responsible person; and receiving confirmation of the performed corrective preventative action on the interface of the problem responsible person.

Optionally, the audit plan further includes audit dates.

Optionally, the method further comprises accepting an approval result of the audit plan on an interface of the project manager and returning the approval result to the auditor.

Optionally, when the approval result is failed, modifying the inspection plan according to the input of the inspector and informing the project manager.

Optionally, after receiving the cause analysis entry, the corrective precaution entry, and the assignment of the executives on the interface of the problem responsible person, an audit rectification plan is generated and sent to the interface of the project manager, and the audit rectification plan includes the corrective precautionary to be completed.

Optionally, the method further comprises presenting the status of the problem and corrective precautions associated with the problem responsible person on the interface of the problem responsible person.

Optionally, the method further includes generating an audit correction report at the project manager and/or auditor interface after all corrective precautions associated with the issue have been identified, the audit correction report including a description of the issue and the completed corrective precautions.

Optionally, the method further comprises closing the problems associated with the audit correction report after the audit correction report is validated by the project manager and/or the auditor.

Optionally, the method further includes presenting, on the institution interface, a status of the audit plan, audit report, and corrective precautions associated with the institution.

Optionally, the method further comprises counting problem categories, problem liability and cause distributions associated with the institution and presenting on the institution interface.

The invention also provides a project inspection management system, which comprises: a memory for storing instructions executable by the processor; and a processor for executing the instructions to implement the method as described above.

The invention also provides a computer readable medium having stored thereon computer program code which, when executed by a processor, implements a method as described above.

Compared with the prior art, the invention has the following advantages:

by realizing the inspection process in the project inspection management system, inspection related personnel can enter inspection related information on line and accurately notify the inspection related personnel, so that the time required by the inspection process is greatly shortened and the project inspection management efficiency of an organization is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the principle of the invention. In the drawings:

FIG. 1 is a flowchart illustrating a project audit management method according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a project audit management process according to an embodiment of the present invention.

FIG. 3 is an interface illustrating a newly created audit plan for a project audit management system according to one embodiment of the invention.

FIG. 4 is an audit problem management interface for an auditor of the project audit management system, according to one embodiment of the invention.

FIG. 5 is a problem management interface for a problem responsible person of the project audit management system according to one embodiment of the present invention.

FIG. 6 illustrates a CAPA management interface for an actor of the project audit management system according to one embodiment of the invention.

FIG. 7 is a problem statistics interface of the project audit management system according to an embodiment of the present invention.

FIG. 8 is a system block diagram illustrating a project audit management system according to an embodiment of the invention.

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 project inspection management method. FIG. 1 is a flowchart illustrating a project audit management method according to an embodiment of the present invention. As shown in fig. 1, the project inspection management method of the embodiment of the present invention includes the following steps:

step 101, generating an inspection plan according to the input of an inspector, wherein the inspection plan comprises an inspection project name, project managers and inspection contents, and informing related personnel of the inspection plan, wherein the related personnel comprise project managers;

102, receiving the problems input by the inspector, and generating an inspection report to inform a project manager, wherein the inspection report comprises one or more problems, and each problem comprises a problem description;

step 103, presenting an inspection report on an interface of a project manager, and notifying a corresponding problem responsible person of the problems in the inspection report according to the distribution of the project manager;

104, receiving reason analysis input, correction preventive measure input and executor distribution on an interface of the problem responsible person, and informing the executor of the correction preventive measure;

step 105, receiving an execution record of the corrective precautionary measure on an interface of an executor, and submitting the executed corrective precautionary measure to a problem accountant for approval; and

at step 106, 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 project inspection management method in detail:

in step 101, an audit plan is generated according to the input of the auditor, the audit plan includes an audit project name, project managers and audit content, and associated persons of the audit plan are notified, the associated persons include the project managers.

FIG. 2 is a diagram illustrating a project audit management process according to an embodiment of the present invention. As shown in FIG. 2, the personnel involved in the project audit management process include: auditors, project managers, problem liability personnel, and Corrective Action Prevention (CAPA) performers. The project manager is a person responsible for managing the entire project. The auditor is responsible for initiating audit, writing corresponding audit plans and conducting audit on the project. The project inspection management system generates an inspection plan according to the input of an inspector, wherein the inspection plan comprises an inspection project name, project managers and inspection contents. Optionally, the audit plan may also include audit dates. FIG. 3 is an interface illustrating a newly created audit plan for a project audit management system according to one embodiment of the invention. In one example, the auditor may enter audit plan information within the interface shown in FIG. 3, including: audit type, project name, sponsor, auditor, research center, inspector, PM (i.e., project manager), audit content, project start date, and attachments. After the audit plan is generated, the system automatically notifies personnel associated with the audit plan. The personnel associated with the audit plan include the project manager for the project being audited.

And after receiving the inspection plan, the project manager examines and approves the inspection plan according to the actual situation. When the project manager considers that the inspection plan has problems, the inspection plan can be rejected, namely, the approval result of the inspection plan is failed, and the project manager can explain the reason of rejection in the approval result. The system receives the approval results of the inspection plan on the interface of the project manager and returns the approval results to the inspector.

When the auditor receives the failed approval results, the audit plan can be adjusted according to the reason of the refusal of the project manager. For example, when the reason for the refund of the project manager is due to a time conflict, the auditor can adjust the audit date of the audit plan and input the modified audit date into the system. The system modifies the audit plan according to the input of the auditor and informs the project manager to carry out the examination and approval again.

In step 102, the questions entered by the auditor are received and an audit report notification project manager is generated, the audit report including one or more questions, each of which includes a description of the question.

When the inspector finds the problems in the inspection, the problems are input into the project inspection management system. FIG. 4 is an audit problem management interface for an auditor of the project audit management system, according to one embodiment of the invention. As shown in FIG. 4, the inspector may enter new questions by clicking on the "Add questions" button, each question including a question number, a question category, a question rating, and a question description. The system receives the problems input by the inspector and generates an inspection report according to the problems to inform a project manager. One or more questions may be included in the audit report, each question including a question description for the question.

In step 103, the audit report is presented on the project manager interface and the corresponding problem responsible person is notified of the problems in the audit report based on the distribution of the project manager.

The audit report is presented on the project manager's interface for the project manager to view. The project manager distributes one or more problems in the report to one or more corresponding problem accountants in the system according to the audit report. The system notifies the corresponding problem responsible person of the problems in the audit report according to the distribution of the project manager. In one example, the assigned problem responsible person may be notified by way of a system message, email, or text message.

In step 104, the cause analysis entry, corrective action entry, and assignment of the actor are received on the interface of the problem responsible person and the executive is notified of the corrective action.

After the problem responsible person receives the distributed problems, the reason of the problems is analyzed and corresponding Corrective Action and Preventive Action (CAPA) is made. 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 executor is distributed, the reason analysis input, the CAPA input and the executor distribution are carried out on the interface of the problem responsible person. FIG. 5 is a problem management interface for a problem responsible person of the project audit management system according to one embodiment of the present invention. The problem responsible person can view all the problems for which the person is responsible on the interface as shown in figure 5. The problem responsible person may enter the cause analysis, correct the precautions and perform the assignment of the person by clicking on the "write CAPA" button. 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.

Optionally, after receiving the cause analysis entry, the corrective action entry, and the assignment of the executives on the interface of the problem responsible person, an audit rectification plan may be generated and sent to the interface of the project manager, where the audit rectification plan includes the corrective actions to be completed.

After the reason analysis input, the CAPA input and the executor distribution, the system correspondingly generates a problem rectification plan of each problem according to the input content, and then generates an inspection rectification plan according to all the problem rectification plans under inspection and sends the inspection rectification plan to an interface of a project manager for the project manager to confirm. The audit rectification plan includes CAPA to be completed.

In step 105, 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 accountant for approval.

The executor completes the task according to the allocated CAPA task. After the implementer has performed CAPA, a record of the implementation of CAPA is logged into the system, where the record of the implementation may include proof of tampering. The system receives the CAPA execution record on the executor's interface and submits the executed CAPA to the problem accountant for approval. FIG. 6 illustrates a CAPA management interface for an actor of the project audit management system according to one embodiment of the invention. As shown in FIG. 6, the implementer may view all CAPA performed by himself 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.

In step 106, a confirmation of the performed corrective precaution is received on the interface of the person responsible for the problem.

The problem responsible person acknowledges the executed CAPA submitted by the executive, and the system receives an acknowledgement of the executed CAPA on the interface of the problem responsible person. Alternatively, when the problem responsible person deems that the executed CAPA cannot pass, the problem responsible person may not confirm the CAPA but make the executive record of the CAPA supplementary.

In summary, the project inspection management method in the embodiment of the invention can enable the inspection related personnel to enter the inspection related information on line and accurately notify the inspection related personnel by realizing the inspection process in the project inspection management system, thereby greatly shortening the time required by the inspection process and improving the inspection management efficiency of the institution.

Optionally, the method may further include generating an audit correction report at the project manager and/or auditor interface after all corrective precautions associated with the issue have been identified, the audit correction report including a description of the issue and the completed corrective precautions.

After all CAPA associated with all issues under inspection are confirmed, the system generates an inspection correction report. The audit correction report includes a description of all the problems under audit and the completed CAPA. And presenting the audit correction report on an interface of the project manager and/or the auditor for the project manager and/or the auditor to view. And when the project manager and/or the inspector thinks that the inspection correction report passes, the inspection correction report can be confirmed. In one example, the project manager can first confirm the audit correction report, and after the project manager confirms the audit correction report, the project manager can submit the audit correction report to the auditor for confirmation.

Optionally, the method may further include closing the issues associated with the audit correction report after the audit correction report is validated by the project manager and/or the auditor.

After receiving the inspection correction report, the project manager and/or the inspector can confirm the inspection correction report when considering that the inspection correction report passes. The audit correction report is confirmed by the project manager and/or the auditor, that is, the audit correction work is completed, and the problems associated with the audit correction report can be closed.

In one example, when the project manager first confirms the audit correction report, and after the project manager confirms the audit correction report, the project manager does not close the associated problem when confirming the audit correction report, and the auditor closes the problem associated with the audit correction report when confirming the audit correction report.

Optionally, the method may further include presenting the status of the problem and corrective precautions associated with the problem responsible person on an interface of the problem responsible person.

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 project inspection management system can also provide an organization interface for an organization to view so as to conduct organization management.

Optionally, the method can further include presenting the status of the audit plan, audit report, and corrective precautions associated with the organization on an organization interface.

By presenting the states of the audit plan, the audit report and the CAPA associated with the organization on the organization interface, the organization can check the states of all the audit plan, the audit report and the CAPA associated with the organization, thereby improving the project audit management efficiency of the organization.

Optionally, the method may further include counting and presenting on the institution interface the issue classifications, issue liability and cause distributions associated with the institution.

The 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 project audit management system according to 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 counting the problem classification, the problem responsibility and the reason distribution and presenting the statistical result by adopting a visual interface, the organization can intuitively and comprehensively know the problems, thereby systematically solving the problems and further improving the project inspection management efficiency.

The invention also provides a project inspection management system, which comprises: a memory for storing instructions executable by the processor; and the processor is used for executing the instructions to realize the project inspection management method.

FIG. 8 is a system block diagram illustrating a project audit management system according to an embodiment of the invention. The project audit 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 project audit 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 the project audit management system 800 to communicate data externally. In some embodiments, the project audit management system 800 may send and receive information and data from the network through the communication port 805. The project audit administration system 800 may also include various forms of program storage 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 used in computer processing and/or communications, as well as possibly program instructions executed 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 project audit management process can be implemented as a computer program stored in the hard disk 807 and recorded to be executed by the processor 802 to implement the method of the present invention.

The present invention also provides a computer readable medium having stored thereon computer program code which, when executed by a processor, implements a project audit management method as described above.

When implemented as a computer program, the project audit 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.

Claims

1. A project inspection management method comprises the following steps:

generating an inspection plan according to the input of an inspector, wherein the inspection plan comprises an inspection project name, a project manager and inspection contents, and informing the related personnel of the inspection plan, wherein the related personnel comprise the project manager;

receiving the problems input by the inspector and generating an inspection report to inform a project manager, wherein the inspection report comprises one or more problems, and each problem comprises a problem description;

presenting the inspection report on an interface of the project manager, and notifying a corresponding problem responsible person of the problems in the inspection report according to the distribution of the project manager;

receiving reason analysis input, correction preventive measure input and executor distribution on the interface of the problem responsible person, and informing the executor of the correction preventive measure;

receiving execution of the corrective preventative action on the actor's interface and submitting the executed corrective preventative action to the issue responsible person for approval; and

a confirmation of the performed corrective preventative action is received on the interface of the problem responsible person.

2. The method of claim 1, wherein the audit plan further comprises an audit date.

3. The method of claim 1, further comprising accepting an approval result of the audit plan on an interface of the project manager and returning the approval result to the auditor.

4. The method of claim 3, further comprising modifying the audit plan based on the inspector's input and notifying the project manager when the approval is failed.

5. The method of claim 1, wherein receiving cause analysis entry, corrective action entry, and assignment of executives on the interface of the problem responsible person further comprises generating and sending an audit rework plan to the interface of the project manager, the audit rework plan including corrective actions to be completed.

6. The method of claim 1, further comprising presenting a status of a problem and corrective precautions associated with the problem responsible person on an interface of the problem responsible person.

7. The method of claim 1, further comprising generating an audit correction report on an interface of the project manager and/or the auditor after corrective precautions associated with a problem are all confirmed, the audit correction report including a description of the problem and the corrective precautions that have been completed.

8. The method of claim 7, further comprising closing issues associated with the audit correction report after the audit correction report is validated by the project manager and/or the auditor.

9. The method of claim 1, further comprising presenting the status of audit plans, audit reports, and corrective precautions associated with the institution on an institution interface.

10. The method of claim 9, further comprising counting and presenting on the institution interface a problem classification, a problem liability and a cause distribution associated with the institution.

11. A project audit management system comprising:

a memory for storing instructions executable by the processor; and

a processor for executing the instructions to implement the method of any one of claims 1-10.

12. A computer-readable medium having stored thereon computer program code which, when executed by a processor, implements the method of any of claims 1-10.