JP2008065790A - Operation and method of project risk management system, and project risk management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To share information among members and among projects by electronized project management and to easily share grasping and measures at an early stage about rerunning and risks in a quality aspect in project management technology. <P>SOLUTION: This project risk management system comprises: a project risk retrieval processing part for retrieving corresponding risk information in risk information about a management object project to be an object of risk management by receiving an operation and outputting information with a user terminal as the other party through a communication network, wherein the project information includes the risk information about risks in a project; a project influence calculation processing part for calculating the influence of the risk on the project on the basis of the retrieved risk information; and a risk output processing part for outputting at least one between the risk information and the influence by receiving an operation and outputting information with the user terminal as the other party through the communication network. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to the improvement of project management technology. In addition to information sharing among members and projects by computerized project management, early grasp and countermeasures regarding risks such as rework and quality are easily shared. Operation and method of project risk management system and project risk management program.

  2. Description of the Related Art Conventionally, there is a project management system that mainly manages project schedules as a technique for providing computer support for progress and quality control in development and manufacturing projects of hardware and software products in manufacturing operations. This type of project management is particularly related to technology, design, manufacturing, and quality control of a small amount of indented products, control devices, and system products. A typical example of software that performs such project management is management by the PERT method. Is a tool. This is to manage the critical (path) such as the predecessor, successor relationship, and individual work start and end schedules of all the works constituting the project.

  However, with the project management software as described above, it is not possible to specify the scope and content of the work to be redone or reverted when a certain work included in the project becomes impossible to complete, There was no way for each party to share information such as non-conformance information and concerns. For this reason, there has been a problem that it is difficult for the project manager to grasp the risk of occurrence of redo and reversion.

  In addition, in order to efficiently advance the entire project consisting of multiple systems and projects, the risk of redoing and reversing is minimized in the progress management for each individual system and each project. There is a need to.

  However, in this respect as well, in the past, actual project management was based on vague data only. For this reason, it is difficult for each technology, design, production, manufacturing and testing, and shipping process to grasp in detail the progress status, remaining items, confirmation of issues, quality status such as nonconformity information, and product risk information. there were. In addition, due to factors such as force majeure that cannot predict in advance the risk that will occur in the course of project execution, the designated date for project completion cannot be observed, man-hour management and productivity efficiency of each scheduled process operation can be reduced. It was difficult to accurately grasp, and it was difficult to grasp the risk of redoing and reversion.

  In addition, when managing the progress of the project, even if the project is completely designed, even if the project is completely designed, there will be a force majeure factor other than the department in charge, such as specification changes and materials not coming in as planned. Etc. may also occur. Due to these factors, the cost of design man-hours, manufacturing man-hours, test man-hours, etc. at each progress step increased from the estimated time before the start of the project, and due to factors such as insufficient follow-up for non-conformance of quality status, Even if it becomes an abnormal value such as a delay, it cannot be immediately recognized, and it takes a lot of time to plan and execute a measure for the countermeasure and recovery.

  Eventually, there will be delays in redoing and revising corrections, countermeasures for nonconformities and points to be pointed out, leaving problems such as seriously hindering processes in later steps, and horizontal development of past nonconformities and risk issues. In some cases, it was difficult to reflect the situation, and it was shipped in advance with the risk and risk expected of the situation, or the quality level could not be maintained. In the future, if a similar new project is ordered, it will be difficult to horizontally deploy various data such as nonconformities in existing projects, pending items, process delay factors, etc. to the new project. It was difficult to use it effectively to reflect the planned man-hours.

  Further, in terms of operation, the progress management of each project plan has traditionally relied on a project plan created on paper media. At that time, the progress of each project was written and prepared by the person in charge on a paper plan, and only those involved in the project in the same department managed the plan. As a result, members who are involved in sales / technical department projects in other departments, headquarters / branches, etc. cannot quickly grasp the progress of other related projects, and the progress of the projects they want. Regarding information and problems, it was necessary to check the progress / management status and problems from the person in charge each time.

  For this reason, in order to deal with the above-mentioned problems, a great deal of time was lost and backtracking work occurred, and the quality status of products and system products could not be fully confirmed within the planned period. As a result, quality problems will occur after delivery to the customer, a large amount of man-hours will be generated that will not contribute to the improvement of productivity and the occurrence of backtracking work, the estimation plan will be exceeded as project management, and the trust from the customer There was a tendency to cause problems such as the loss of disappearance and the time and money and the number of people required to deal with the nonconformity.

  In addition, when proceeding with the progress and management of projects that are managed using conventional paper media, holding project review meetings at each step, displaying a list of follow-up items pointed out at the meeting, issuing minutes, and the number of remaining cases The management and the fill-in management of the progress of the remaining cases have all been managed by the person in charge in the department in charge by the human system. Therefore, when actually planning a project, the risk that occurs in the above situation is anticipated, the risk is managed, and it is anticipated that an unexpected situation will occur, or even if it occurs Where there is a need to minimize the impact on the project, there are individual differences in the amount of information in charge and the sensitivity to risk management, which has been the limit in minimizing damage.

  Specifically, when risk management is implemented in a conventional project, new technology, problems and concerns experienced in past projects, nonconformities, and surrounding technical managers are subject to risk management at the project planning stage. Based on the advice from the project, the risk items are roughly identified, the risk items are monitored at the project execution stage, and when each risk item becomes a problem, an improvement plan is made each time. I was trying to minimize it.

  There are a plurality of examples of technical support for such correspondence. For example, the technology of the first example (Patent Document 1: Project Risk Management Support Device) is a similar risk item implemented in the past stored in the project database. By using, we can grasp the risk items included in the risk management target project without missing, and for the project manager, we can quantitatively understand the impact of each risk item on the risk management target project. It was an attempt to suppress the occurrence of unforeseen circumstances as much as possible.

  The project risk management support apparatus in Patent Document 1 generally includes project information including project attributes, risk items included in the corresponding project, and impact information of the risk item on the corresponding project in each project executed in the past. A project information database for storing information, a project information search means for reading all risk items and impact information of projects similar to the risk management target project from the project information database, and the read risk item and impact information for the risk management target project Risk editing means for editing the risk item and impact information corresponding to the risk item, and the risk item to the risk management target project from the edited risk item and impact information. Was equipped with a risk impact calculation means output in graphical form to calculate the risk impact showing the effect of.

  In the project risk management support apparatus configured as described above, project information including project attributes, risk items, and impact information in each project executed in the past is stored in the project information database.

  When a new risk management target project that needs to be risk-managed is generated, all list items and influence information of similar projects are read from the project information database.

  When the operator edits the read risk item and impact information to correspond to the risk management target project, each risk item gives to the risk management target project based on the edited risk item and impact information. A quantitative influence is calculated and displayed graphically. As a result, the operator can grasp at a glance the risk items included in the risk management target project and the quantitative influence level.

  Prior Example 2 (Patent Document 2: Reversion Risk Evaluation System) has a storage means for storing breakdown structure information representing a series of small goals that are achieved step by step until completion for each project. The purpose is to calculate the amount of return to be spent on the review process when the target becomes impossible.

  In Prior Example 3 (Patent Document 3: Project Quality Management System Operation Method), it is possible to quickly grasp the progress status of a plurality of projects, to prevent the delay of project progress as much as possible, Detailed progress status and work productivity of each project and person in charge, immediate countermeasures in case of cost increase, new project estimates and plans for completed projects It can be used effectively.

  In the preceding example 3, the plan and approval status (unapproved, approval requested, approved) for each process of design, manufacturing, and testing are added to protect the approved data and on the screen. Since each progress status is displayed on the screen, paper-based approval is not required, management is simple, detailed management of plans and results for each process is possible, and the approval status is easy to understand on the screen. It is also intended to be able to display and protect the data of approval information.

  In addition, there is no need to approve paper-based media, no need to store paper-based project management tables, and no need to pass paper media when updating approval information. The purpose is to provide that it is possible to accurately determine whether or not project management has been completed or not completed for each process by digitizing the function of the approval act.

  Prior example 4 (patent document 4: project management device) manages the plan and results of a project, and adds information on the approval status (unapproved, approval requested, approved) for each work. In addition to protecting the approved data and displaying the status on the line table screen, the conventional paper-based approval is not required, the management is simple and the plan and actual status can be managed finely for each work, and the line table The purpose is to realize the display of the approval state on the screen in an easy-to-understand manner and the protection of the approval information.

  Prior Example 5 (Patent Document 5: Project management method) is a system for managing product development projects, and therefore it can improve the work efficiency in a project management system and a project when a high level of security management is required. It relates to a project management method that can

  Prior Example 6 (Patent Document 6: Project Progress Management Method) relates to a target / result comparison evaluation covering both process and quality, and it is possible to manage the process and quality of the project in association with each other. The purpose is to obtain a quantitative amount of unloading work for the work that has not yet achieved the target.

JP 2001-195383 A JP 2000-200303 A JP 2005-128796 A JP-A-11-250125 JP 2002-288405 A Japanese Patent Laid-Open No. 06-332911 JP 2004-246742 A

  However, in the above-mentioned conventional technologies related to risk management in a project, risk items included in a project subject to risk management are roughly identified based on problems experienced in past projects and advice from technical managers. However, it was not possible to grasp risks, take countermeasures and share them effectively, and more specifically, there were the following problems.

(1) It is difficult to grasp the risk items of similar projects stored in the project information database, and it is difficult to quantitatively grasp the degree of impact of each risk item on the risk management target project. There was a limit to the effect of suppressing the occurrence of unforeseen circumstances.

(2) There is a problem that information cannot be visualized and the project cannot be operated efficiently because the management of the risk of occurrence of backtracking work by the project manager is not shared.

(3) The project progress and risk cannot be managed quantitatively, and the difficulty of the project cannot be grasped in a homogeneous manner, resulting in variations in production, quality, etc., which can be reflected in process management. Therefore, there was a problem that the project could not be managed efficiently.

(4) It was difficult for a limited number of project managers to quickly grasp the risks and progress of multiple projects, and it was difficult to effectively prevent delays in project completion.

(5) The person in charge cannot manage the progress of the process in detail, and it is impossible to grasp the risk of work productivity of each project and person in charge.

(6) Even if you want to make effective use of completed project data for estimating and planning new projects, the data and risk information are personally managed and file storage for each person in charge. Especially in the case of department changes, it was very difficult to share information and data that was owned by individuals.

(7) In the operation based on the paper-based project management plan table, the plan and risk information for each process of design, manufacturing, and testing are managed by the person in charge and the department to be stored. It was difficult to share and manage each process with a common recognition.

(8) By managing the storage of paper-based project management by each department, project risk management can only be performed by persons in charge and specific management departments, and it is difficult to accumulate risk management.

(9) Risk management information at the project review meeting, information on pending items, nonconformity information items, process delays, etc. are not shared, so overlooked inquiries from related departments, considerations, and significant horizontal development items In the end, the risk indications are shipped to the customer without being reflected in the product, and due to the customer's indication or the occurrence of a serious nonconformity, a return work occurs, and there is a lot of man-hours and money not included in the estimate. In some cases, this could have affected production.

(10) Even if the person in charge checks the timely information and processes of the members involved in the project while checking the processes, the progress of the members involved in the project is grasped due to the congestion of the project. Tended to be difficult.

(11) Even if the risk items are the same due to the experience of new project managers or technical managers who have no experience in project management in the past, the impact and scale of the project are not consistent, and risk items cannot be extracted. And there was a problem that the scale of risk items was wrong.

  In carrying out project progress and quality management, it is necessary to manage the progress of the project and to ensure that the quality of the product intended for the result of executing the project is above a certain level. It must be noted. On the other hand, although the above-mentioned problems exist, it is important whether the quality of the software and hardware achieves the initial plan, and it can be said that the management of both projects is preferable because both managements are established.

  The present invention solves the problems of the prior art as described above, and its object is to provide rework and quality in project management technology, in addition to information sharing among members and projects by computerized project management. The object is to provide a project risk management system operation and method and a project risk management program that can easily share early understanding and countermeasures regarding the above risks.

  More specifically, the object of the present invention is to share information by unifying various risk information that may occur in the execution process in order to prevent unforeseen circumstances in project management, and to perform project risk search processing The project risk impact calculation process and the risk impact assessment function share project risk information among project members to reduce risk early.

  Another object of the present invention is to provide managers of each operational department with information for early detection and early countermeasures for high-risk projects in the departmental projects, and manage the progress of multiple projects. Project risk management information, project risk management, risk sharing such as project issues, nonconformities, and process delays are quickly and reliably captured and processed to a level where information can be shared. This is to improve the accuracy.

  Another object of the present invention is to share information on project risk management and improve the accuracy of risk management in the project, so that early detection of risks and early countermeasures can be achieved even for high-risk projects. It is to maintain and improve product quality.

  In other words, the object of the present invention is to promptly grasp the matters of concern, progress and risk when proceeding with one or more projects, and to prevent delays in project progress and completion as much as possible. In addition, it is possible to grasp the process progress status of each process and the person in charge in detail, and to understand the work productivity of each project and person in charge, and immediately take measures when the cost increases. It is possible to provide a project risk management system technology that can be used and the data of completed projects can be effectively used for estimation and planning of new projects.

  In addition, another object of the present invention is to eliminate the need for planning and paper-based management for each process of design, manufacturing, and testing, simplifying management, and finely managing the plan and results for each process, It is to display the risk status on the screen in an easy-to-understand manner, monitor a plurality of management systems, and quickly and surely capture the signs of the risk to enable information sharing. Another object of the present invention is to eliminate the need for paper-based media approval, eliminate the need for paper-based project management tables, and eliminate paper media. In other words, it is only necessary to change the information in the data, and it is possible to accurately determine whether the project management for each process is completed or not.

  In order to achieve the above object, according to one aspect of the present invention, a product development project is managed using a computer for project information including risk information, and a GUI interface of a user terminal connected via a communication network is provided. Project risk management system that supports project quality management through a project information database that stores project information related to project quality management for each project for a plurality of projects, and a registration screen displayed on the user terminal. Information registration management means for accepting registration of the project information from the user, and a search condition or output condition that is received from the user by displaying an input screen on the user terminal. Data output management means to be transmitted to the terminal, and the project information includes risk information related to risk in the project, and is subject to risk management by accepting operation and outputting information to the user terminal via the communication network. Project risk search processing unit that searches for the relevant risk information among the risk information, and the project impact calculation that calculates the degree of impact of the risk on the project based on the searched risk information And a risk output processing unit that outputs at least one of the risk information and the degree of influence by receiving an operation and outputting information from the user terminal via the communication network.

  According to the present invention as described above, with respect to a plurality of projects, detailed project information such as basic information, DR information, and shipping quality information is registered and received from the user terminal of each person in charge for centralized management and browsing. To enable information sharing and effective management among members and between projects, as well as search and calculate impact on project risks. Grasping and countermeasures can be easily shared via the GUI.

  Hereinafter, a project risk management system of the present invention (hereinafter referred to as “the present system”) and a project risk management method using the present system (hereinafter referred to as “the present method”) are best implemented (hereinafter referred to as “the present”). The embodiment will be described in detail with reference to the drawings. Note that, from the viewpoint of simplifying the explanation, the same components are denoted by the same reference numerals throughout the drawings, and the assumptions common to the explanation in the background art and problems are omitted as appropriate.

[1. Constitution〕
This system is a project risk management system that uses a computer to manage project information including risk-related information for product development projects, and also supports business operations for project quality management. This system can be realized by using an appropriate type of computer such as a personal computer, and implements the configuration shown in the functional block diagram of FIG. 1 with the schematic hardware configuration shown in FIG.

  That is, as shown in FIG. 2, the present system is connected to a system bus 1 with a CPU 2 serving as an arithmetic unit, a known input unit 3 such as a pointing device such as a mouse or a tablet, a keyboard, and a known device such as a display or a speaker. The output unit 4 is connected to a ROM 5 and a RAM 6 as main storage devices, a hard disk device (HDD) 7 as an external storage device, a flexible disk device (FDD) 8, an optical disk device (ODD) 9, and the like.

  As shown in FIG. 1, the system implemented on the hardware as described above has a project information database 10, a project risk search processing unit 20, and a project impact calculation processing unit 30 as seen in the outline of functions. And a risk output processing unit 40 and a user interface 50 using, for example, a GUI. The user interface 50 displays the registration screen and displays the registration information of the project information from the user and the search condition or the output condition that displays the input screen and receives from the user. Data output management means 52 for transmitting to the user is provided.

[1-1. Project information database)
Among these, in the project information database 10, as shown in FIG. 3, project information 11 and an influence definition table 12 are stored for each project executed in the past and each project currently being executed. . In the figure, 42 is a customer product risk countermeasure list. Although the storage location of the impact definition table 12 is shown separately from the project information database 10 in FIG. 1, this is for convenience of explanation, and any implementation example inside or outside the project information database 10 can be considered.

  Each project information 11 is information relating to project quality management, and at least relates to design review (DR) shipment quality of a developed product. Specifically, customer product information 13, DR project information 14, medium schedule information 15, and nonconformity. Information 16, punch list information 17, preventive maintenance information 18, and arrangement information 19 are included. More specifically, the customer product information 13 is information about the customer and its product. As shown in FIG. 4A, the customer product ID, customer product name, project name, and order number of the corresponding project. Including shipping date, status code, etc.

  The DR project information 14 is information related to the implementation of DR (design review). As shown in FIG. 4B, the customer product ID, the section management number, the scheduled completion date, the DR implementation date, the impact of the project concerned. The degree classification code, the number of days delayed, etc. are included, but the next DR step scheduled date or the current DR step scheduled date may also be included. Further, as shown in FIG. 4 (c), the medium schedule information 15 includes the customer product ID, the product number, the scheduled date, the completion date, the impact category code, the delay days, the response date limit, the occurrence date of the project. Etc., including appropriate items.

  Further, the nonconformity information 16 is information regarding product nonconformity in relation to customer demand or other systems, and as shown in FIG. 4D, the customer product ID, nonconformity management number of the corresponding project, Includes impact category code, response date limit, date of occurrence, and scheduled date. The punch list information 17 is information on correction items, and includes a customer product ID, an impact category code, a delay date, a corresponding date limit, a drafting date, and the like of the corresponding project as shown in FIG.

  Further, the preventive maintenance information 18 is information relating to product functions, safety maintenance, and risk prevention, and includes a customer product ID, arrangement parts, and the like of the corresponding project as shown in FIG. Further, the arrangement product information 19 is information relating to the arrangement of parts, and includes a customer product ID, arrangement parts, revision / decommissioning information, alternative arrangement parts, etc. of the corresponding project as shown in FIG.

[1-2. (Risk value calculation impact definition table)
Next, as shown in FIG. 5, the influence degree definition table 12 stores an influence degree classification code and an influence degree in association with each other, and these are numerical values for calculating a risk value. In addition, the influence degree definition table 12 has a risk value calculation formula 33 for calculating a risk value using the table 12, and the influence degree for calculating the risk value in this calculation formula is a corresponding influence degree classification code. Ask from. For example, the influence degree classification code = 4 indicates the influence degree = 1.

  The risk value calculation formula 33 using the table 12 as described above includes DR project risk value information representing a calculation formula for calculating a risk value from a predetermined item of the DR project information, as shown in FIG. Nonconformity risk value information representing a calculation formula for calculating a risk value from a predetermined item of information, medium schedule risk value information representing a calculation formula for calculating a risk value from the predetermined item of the medium schedule information, and a predetermined value of the punch list information This is a calculation formula for calculating a risk value, including punch list risk value information representing a calculation formula for calculating a risk value from an item.

For example, the calculation formula for DR project risk value information is:

Risk value = (Delayed days / (Scheduled completion date-DR implementation date)) * Impact

The calculation formula for medium schedule risk value information is:

Risk value = days late

The formula for calculating nonconformity risk value information is

Risk value = (days of delay / (response date-occurrence date)) * impact

The formula for calculating punch list risk value information is:

Risk value = (days late / (response date-drafting date)) * impact

It is.

  Next, the risk influence degree determination condition 41 used in the risk output processing unit 40 is a condition for distributing the risk value calculated by the risk value calculation formula as described above to the risk degree as shown in FIG. This risk level indicates the content for prompting the user (operator) to take measures against the risk of the project, and is output as light, medium, serious, and most serious.

  Using this condition, as will be described later, the project impact calculation processing unit 30 uses a predetermined threshold value to calculate the risk value calculated by the risk value calculation formula 33 in the impact calculation. And output the decision by allocating to one of the most serious risks. Specifically, for example, when the risk value ≦ 10, the risk level is mild, when 11 ≦ risk value ≦ 50, the risk level is moderate, when 51 ≦ risk value ≦ 99, the risk level is significant, risk value When ≧ 100, the risk level is output as the most serious.

[2. Action)
The present embodiment configured as described above operates as follows.
[2-1. (Search for customer product information)
First, the project risk search processing unit 20 performs a project risk search process according to the processing procedure shown in FIG. Designation of a risk management target project as a risk search target may be performed from any information item, but as a typical example, product information of a customer destination is searched from customer information.

  In this case, the project risk search processing unit 20 first receives input of project customer information from the user (operator) of this system via the user interface (GUI) 50 (step S1), and from the project information database 10. Then, the project information corresponding to the input customer information, that is, customer product information is retrieved and extracted (step S2), and the corresponding project information 11 is output (step S3).

  Specifically, as illustrated in FIG. 9, the customer product division-specific risk search screen (upper part of FIG. 9) is displayed, and the customer (operator) inputs or selects the customer product name, order number, and the like. The search result corresponding to the selection is displayed on the risk list screen for each customer product section at the bottom of FIG. Depending on the operation or setting, information is also searched for projects similar to the risk management target project.

  That is, the project risk search processing unit 20 uses the input customer product name and order number, etc., from the project information database 10 to the corresponding customer product information 13 (FIG. 4 (a)) and the corresponding risk management target. Search and extract the project 11. Then, in the customer information search result output (step S3), based on the read customer product information 13 (FIG. 4A), the customer product-specific risk list shown in the lower part of FIG. 9 is displayed. At the same time, the customer product information 13 is stored in the customer product ID search result storage unit 21.

  In the customer product ID search result storage unit 21, the customer product ID, customer product name, project name, order number, shipping date, and status code of the project that outputs the risk are stored.

[2-2. (Risk impact calculation)
Next, the project risk impact calculation processing unit 30 calculates the risk value of each project from the customer product information (FIG. 4A) in order to calculate the risk impact managed by the project. Calculated by the risk value calculation formula and stored in the customer product ID risk information storage unit 31. The customer product ID risk information storage unit 31 is set with information shown in FIGS. 4B to 4C and a risk value.

  Specifically, the project risk impact calculation processing unit 30 performs the project risk impact calculation processing according to the flowchart shown in FIG. That is, first, the risk value is obtained and output from the DR project information of the customer product ID according to the risk value calculation formula (step T1). In this process, the customer product ID set in the customer product ID search result storage unit 21 is matched with the customer product ID from the DR project information 14 (FIG. 4B) in the project information database 10. The risk value of the DR project information is obtained by the risk value calculation formula 33 and stored in the customer product ID risk information storage unit 31.

For example, the calculation of DR project risk value information is

Risk value = (Delayed days / (Scheduled completion date-DR implementation date)) * Impact

To do.

  Next, the project risk impact calculation processing unit 30 obtains and outputs a risk value according to the risk value calculation formula from the medium schedule information of the customer product ID (step T2). In this process, the customer product ID set in the customer product ID search result storage unit 21 matches the customer product ID from the medium schedule information 15 (FIG. 4C) of the project information database 10. The risk value of the medium schedule information is obtained by the risk value calculation formula 33 and stored in the customer product ID risk information storage unit 31.

For example, calculation of medium schedule risk value information:

Risk value = days late

To do.

  Next, the project risk impact calculation processing unit 30 obtains and outputs a risk value according to the risk value calculation formula from the nonconformity information of the customer product ID (step T3). In this process, using the customer product ID set in the customer product ID search result storage unit 21, the nonconformity that matches the customer product ID from the nonconformity information 16 (FIG. 4D) in the project information database 10. The risk value of the information is obtained by the risk value calculation formula 33 and stored in the customer product ID risk information storage unit 31.

For example, calculation of nonconformity risk value information

Risk value = (days of delay / (response date-occurrence date)) * impact

To do.

  The nonconformity information 16 cooperates with other management systems related to nonconformity, such as a nonconformity analysis support device as exemplified in Patent Document 7, and provides information on the project list influence degree.

  The nonconformity analysis support device shares and unifies nonconformance information as electronic information, accumulates and manages it, and actively supports nonconformity analysis in consideration of horizontal development etc. using the accumulated nonconformity information on the network. Is. Specifically, the nonconformity information management application server is connected to the important nonconformity analysis support device, the reference terminal, and the reference-side simple mobile terminal via a communication network. The server 1 supports input of nonconformity information to various terminals connected through the communication network, and updates or searches information in the database based on the acquired data. In addition, the important nonconformity analysis support device provides the user with input support for conducting a case study including detailed important nonconformity analysis in order to pursue the root cause of the important nonconformity or examine the countermeasure. Analytical data of important nonconformity information is created based on the obtained data.

  Next, the project risk impact calculation processing unit 30 calculates and outputs a risk value from the punch list information of the customer product ID according to the risk value calculation formula (step T4). In this process, the customer product ID set in the customer product ID search result storage unit 21 is matched with the customer product ID from the punch list information 17 (FIG. 4E) in the project information database 10. The risk value of the punch list information is obtained by the risk value calculation formula 33 and stored in the customer product ID risk information storage unit 31.

For example, the calculation of punch list risk value information is

Risk value = (days late / (response date-drafting date)) * impact

To do.

  Next, the project risk impact calculation processing unit 30 outputs a product discontinued product and a use prohibition arranged component from the revision / decommission information in the preventive maintenance arranged component information storage unit of the customer product ID (step T5). Using other management systems and customer product IDs such as the preventive maintenance information system exemplified in 281296, customer product ID arrangement parts that match customer product IDs from the information of FIG. The information is stored in the information storage unit 32.

  The preventive maintenance information system realizes sharing and unification of preventive maintenance information, and appropriate classification, so that related parties can easily update and search data. Specifically, the preventive maintenance information management system is configured by a Web system, and the preventive maintenance information management Web application server includes a function unit that stores data through a user terminal and an input support display via a communication network. By exchanging data, the information obtained from the terminal is used to search each information file in the database or update each information file in the database in cooperation with the preventive maintenance information management data server.

  In the Web application server, the common information management unit and the already-delivered product information management unit manage customer information and product information about products shipped to customers, and basic information about preventive maintenance work for products, and a periodic maintenance result information management unit The horizontal development result information management unit manages result information related to the result of the preventive maintenance work of the product.

[2-3. (Risk output)
Next, the risk output processing unit 40 performs the risk output process according to the operation procedure as shown in FIG. In this process, each risk information (risk value and preventive maintenance information) obtained by the project risk impact calculation processing unit 30 is converted into customer products according to output requests (steps U1 to U7) for each project or item. The information is read from the ID risk information storage unit 31 and the customer product arrangement part information storage unit 32 and is output as a list on the user interface (GUI) 50.

  In this process, when a risk output request is made for each project (step U1), what risk information items exist for the project is displayed on the risk display screen of FIG. In this display example, the number of risks that can be output is displayed for each item of the project (for example, “punch list”, “DR examination item”, etc.), and the user (operator) displays this screen (FIG. 12). When the number of risks displayed in the desired project item is selected, the risk corresponding to each project item name is output as the risk countermeasure list 42.

  That is, if a user (operator) makes a risk output request for a DR project (step U3), the user is prompted to output a risk countermeasure list of DR project information. Similarly, the output of the risk countermeasure list of the medium schedule information is output for the risk output request of the middle schedule (step U4), and the risk countermeasure list of the nonconformance information is output for the risk output request of the nonconformity (step U5). In response to the punch list risk output request (step U6), the output of the risk countermeasure list of the punch list information is prompted.

  Further, in response to an output request for a production discontinued product and use prohibited arrangement part (step U7), the product discontinuation product and use prohibited arrangement part information is prevented by the preventive maintenance information management support method described in JP-A-2003-281296. It cooperates with maintenance information and outputs it to the customer product arrangement parts check sheet 43. The processing of steps U1 to U8 is repeated until the user (operator) risk output request is completed (step U2).

[2-4. (Output of risk countermeasure list)
The risk output of each item selected as described above can be of any format, but here, a risk countermeasure list is created and output (step U8). This risk countermeasure list may have several parts, and examples of output of individual parts in this case are shown in FIGS. Among these, FIG. 13 shows an example of a part (DR project output unit) related to the DR project in the output information. In the following, FIG. 14 shows an example of a medium schedule output unit, FIG. 15 shows an example of a nonconforming output unit, and FIG. 16 shows an example of a punch list output unit.

  In order to output the risk countermeasure list according to the request of the user (operator) in this way, the request of the user (operator) is the DR project information based on the risk value set in the customer product ID risk information 31. In the case of a request (step U3), the risk value for risk countermeasures and the risk level obtained from the risk impact determination condition 41 are output to the DR project output unit of FIG.

  Similarly, in the case of a middle schedule information request (step U4), in the middle schedule output part of FIG. 14, in the case of non-conformity information request (step U5), in the non-conformity output part of FIG. U6) Each risk value and the risk degree calculated from the risk influence degree determination condition 41 are output to the punch list output unit of FIG.

  The format for outputting the respective units (FIGS. 13 to 16) as described above is arbitrary. For example, it is output as the risk countermeasure list 42 according to a configuration of one screen or a plurality of screens, a tab switching screen configuration, or the like. In addition, the specific contents of the risk influence degree determination conditions as described above are also free. In this embodiment, when the risk value ≦ 10, the risk degree is mild, and when 11 ≦ risk value ≦ 50, the risk degree is medium. , 51 ≦ risk value ≦ 99, the risk level is critical, and when the risk value ≧ 100, the risk level is the most serious output, but it can be changed according to the target field of the project. is there.

[3. effect〕
As described above, according to the present embodiment, with respect to a plurality of projects, detailed project information such as basic information, DR information, and shipping quality information is registered from a user terminal such as each person in charge, and is centrally managed and viewed. By responding to usage, it is possible to share information and manage effectively between members and projects, as well as search and calculate the degree of impact on the project risk. Early grasp and countermeasures can be easily shared on the GUI.

More specifically, an excellent effect of improving the problem can be realized as described below.
(1) According to the present embodiment, it is possible to quickly grasp the progress status of a plurality of projects, to prevent the delay of completion of the project as much as possible, and to detail the progress status of each process and the person in charge. In addition, it was possible to grasp the work productivity of each project and the person in charge, and it was possible to immediately implement countermeasures in case the cost increased due to completion delays or addition of specifications. It is possible to provide a project quality management system and method capable of effectively utilizing project data for estimating and planning a new project.

(2) Further, according to the present embodiment, the plan and the approval status (not approved, approval requested, approved) for each process of design, manufacturing, and testing are added to protect the approved data. Because it is configured to display each progress status on the line table screen, it eliminates the need for conventional paper-based approval, simplifies management and allows detailed management of plans and results for each process, and on the screen. The approval status can be easily understood, and the data of the display and approval information can be protected.

(3) Further, according to the present embodiment, it is not necessary to perform a conventional paper-based approval, it is not necessary to store a project management table in paper, and a paper medium is used even when the approval information is updated. Since there is no need to pass, only the information inside the data needs to be changed. In addition, by digitizing the function of the approval action, it is possible to accurately determine whether the project management for each process is completed or not.

(4) In addition, according to the present embodiment, the plan and approval status (unapproved, approval requested, approved) for each process of design, manufacturing, and testing are shared in the project management plan table. Therefore, anyone can share and manage plans and results for each process with a common recognition.

(5) Also, according to this embodiment, the project plan / management table can be collectively managed and shared by these, data can be easily changed when the approval information is updated, and the approval etc. By being able to circulate the plan quickly, it is possible to share information on the completion and incompleteness of project management, and anyone can make an accurate decision.

(6) In addition, according to the present embodiment, for the issuance of the project review meeting holding guidance, etc., when the holding date is changed due to circumstances, etc., by issuing the holding guidance in the process based on the project plan. It is possible to respond promptly and to promptly contact the attending members who have been scheduled, and the burden on the person in charge can be greatly reduced.

(7) Also, according to this embodiment, in issuing the minutes of the project review meeting, it is quickly distributed to the members who attended the meeting, and the minutes are shared, and inquiries and minutes from the related departments The quality can be improved by sharing the considerations and important horizontal development items described in the records.

(8) Further, according to the present embodiment, it is not necessary for the person in charge to check the process and to make preparations such as holding a project review meeting each time, and the burden on the person in charge is extremely lightened and related to the project. By sharing information and processes with members, it is possible to grasp the progress of members involved in the project.

(9) In addition, using the risk items of the similar project stored in the project information database in the present embodiment, quantifying and outputting each risk item, and grasping 100% of the risk items included in the project risk management It is possible to quantitatively grasp the degree of influence of each risk item on the risk management target project, and to suppress the occurrence of unforeseen circumstances at the time of project execution as much as possible.

(10) Moreover, according to this embodiment, since the management of the risk of occurrence of backtracking work by the project manager is visualized, the project can be promoted efficiently.

(11) Further, in the present embodiment, the progress of the project can be managed quantitatively, the degree of difficulty of the project can be grasped relatively homogeneously, and variations in production and quality can be suppressed as much as possible.

  Further, from the following viewpoint, in this embodiment, in this embodiment, multiple types of information (customer product information, DR project information, medium schedule information, nonconformity information, punch list information, preventive maintenance information, By including (arranged product information) in the project information and using it as the basis for determining the impact of the risk, it becomes possible to grasp the risk more effectively.

  In this embodiment, by including a plurality of types of information such as product names and project names as customer product information, desired project information can be easily specified from a part of these information, or customer product information It is easy to comprehensively understand the risks related to the customer, and the customer satisfaction of the customer can be improved.

  Further, in the present embodiment, by including a plurality of types of information such as the number of days delayed and the scheduled completion date as DR (design review) project information, desired project information can be easily specified from a part of the DR project information. This makes it easy to comprehensively understand the risks related to DR project information, and enables effective use of design reviews.

  Further, in the present embodiment, by including a plurality of types of information such as delay days and scheduled dates as medium schedule information, desired project information can be easily specified from a part of the medium schedule information, or Risks can be easily grasped comprehensively, and effective risk management based on highly objective elements such as schedules becomes possible.

  In addition, in this embodiment, by including information such as a nonconformity management number as nonconformity information, it is possible to easily identify desired project information even from a part of the nonconformity information, and to easily grasp risks related to nonconformity information comprehensively. Thus, nonconformity can be effectively suppressed.

  In the present embodiment, the punch list information includes a plurality of types of information such as the number of days delayed and the scheduled date, so that desired project information can be easily specified even from a part of the middle schedule information, or the middle schedule information It becomes easy to grasp the risk comprehensively, and the risk of defect correction can be effectively managed.

  In addition, in this embodiment, by including information such as parts to be arranged as preventive maintenance information, desired project information can be easily identified from preventive maintenance information by using parts as a clue, and risks related to preventive maintenance information are comprehensively included. It becomes easy to grasp and safety quality can be effectively improved.

  Also, in this embodiment, by including information such as revision / decommissioning information and replacement parts information as the arrangement product information, desired project information can be easily identified from the arrangement information including the case of parts renovation or replacement. Therefore, it becomes easy to comprehensively understand the risks related to the arranged product information, and it is possible to effectively suppress the delay propagation caused by the arrangement of parts as a bottleneck.

  Further, in the present embodiment, by using the table 12 in which the impact degree classification code and the impact degree classification on the project are associated in advance, a consistent standard can be reliably applied with a simple determination process.

  Further, in the present embodiment, by preparing in advance a calculation formula 33 formulated to calculate a risk value from each item of information included in the project information, it can be quickly and stably reduced from the project management information with a small calculation burden. It becomes possible to grasp the risk.

  Further, in this embodiment, by assigning the calculated risk value to a plurality of risk degrees according to the risk impact determination condition 41, it becomes easy for anyone to determine which process is prioritized. , Improve the accuracy and efficiency of project management work.

  In this embodiment, the project risk search processing unit 20 receives a part of the customer product information and searches for and outputs matching customer product information and corresponding project information. This makes it easier to understand the risks used as clues and can effectively improve customer satisfaction.

[4. Other embodiments]
In addition, the said embodiment is only an illustration and this invention includes what is illustrated below and other embodiment other than that. For example, the apparatus described in the above embodiment can be realized by causing a computer to read and execute a program stored in a storage medium.

  Here, as a storage medium in the present invention, a magnetic disk, a flexible disk, a hard disk, an optical disk (CD-ROM, CD-R, DVD, etc.), a magneto-optical disk (MO, etc.), a program, etc. can be stored and read by a computer. As long as it is a possible storage medium, the storage format may be any form.

  In addition, an OS (operating system) running on a computer based on an instruction of a program installed in the computer from a storage medium, MW (middleware) such as database management software, network software, or the like implements the present embodiment. A part of each process may be executed.

  Furthermore, the storage medium in the present invention is not limited to a medium independent of a computer, but also includes a storage medium that stores or temporarily stores a program transmitted via a LAN, the Internet, or the like. The case where the processing in this embodiment is executed from this medium is also included in the storage medium in the present invention, and the medium configuration may be any configuration.

  The project risk management according to any one of claims 1 to 13, in particular, by connecting a server system having an ASP (Application Service Provider) configuration and a pre-registered service target user terminal via a communication network. If the system is realized, project risk management can be introduced and used easily, quickly and inexpensively for various departments and user groups without individual system development and server preparation.

  In addition, if the function of the project information database is realized as an ASP-configured server and can be accessed from the user terminal or other information processing system via a communication network, the database and the arithmetic processing accessing it can be separated. System renovation and load balancing are facilitated, improving system availability and throughput.

  Furthermore, a predetermined remote management means monitors and detects a fault such as an output abnormality, and when such a fault is detected, notifies the operator or a predetermined manager via the communication network by an alarm or a screen display. By doing so, it becomes possible to respond quickly to troubles by remote notification of defects, and project risk management work can be smoothly continued and resumed early.

  The computer according to the present invention executes each process according to the present embodiment based on a program stored in a storage medium, and includes a single device such as a personal computer or a system in which a plurality of devices are connected to a network. Any of these configurations may be used.

  The computer in the present invention is not limited to a personal computer, but includes a computing device, a microcomputer, and the like included in an information processing apparatus, and is a generic term for devices and apparatuses that can realize the functions of the present invention by a program.

Functional block diagram showing a schematic configuration of an embodiment of the present invention The figure which illustrates the hardware constitutions of the project risk management system in embodiment of this invention The conceptual diagram which shows the project information and impact degree definition table of each project which were implemented in the past and are currently running memorize | stored in the project information database in embodiment of this invention The figure which shows each project information in embodiment of this invention The figure which shows the structure of the influence degree definition table in embodiment of this invention. The figure which shows the risk value calculation formula in embodiment of this invention. The figure which shows the risk influence degree determination condition in embodiment of this invention The figure which shows the procedure of the project risk search process in embodiment of this invention. The figure which shows the example of a screen display of the project risk search process in embodiment of this invention The figure which shows the procedure of the project risk influence degree calculation process in embodiment of this invention. The figure which shows the procedure of the risk countermeasure output process in embodiment of this invention The figure which shows the example of a screen of the risk display in embodiment of this invention The figure which illustrates the part (DR project output part) regarding DR project among the risk outputs in the embodiment of the present invention The figure which illustrates the part (medium schedule output part) regarding a middle schedule among the risk outputs in embodiment of this invention. The figure which illustrates the part (nonconformity output part) regarding nonconformity among the risk outputs in embodiment of this invention The figure which illustrates the part (punch list output part) regarding a punch list among the risk outputs in embodiment of this invention

Explanation of symbols

1 ... System bus 2 ... CPU
3 ... Input unit 4 ... Output unit 5 ... ROM
6 ... RAM
7 ... HDD
8 ... FDD
9 ... ODD
10 ... Project information database 11 ... Project information 12 ... Impact level definition table 13 ... Customer product information 14 ... DR project information 15 ... Medium schedule information 16 ... Nonconformity information 17 ... Punch list information 18 ... Preventive maintenance information 19 ... Arranged product information 20 ... Project risk search processing unit 21 ... Customer product ID search result storage unit 30 ... Project risk impact calculation processing unit 31 ... Customer product ID risk information storage unit 32 ... Customer product ID arrangement part information storage unit 33 ... Risk Value calculation formula 40 ... Risk output processing unit 41 ... Risk impact determination condition 42 ... Customer product risk countermeasure list 43 ... Customer product arrangement product check sheet 44 ... DR project output unit 45 ... Medium schedule output unit 46 ... Non-conforming output unit 47 ... Punch list output unit 48 ... Preventive maintenance output unit 49 ... Arranged product output unit 50 ... User interface Over scan (GUI)

Claims (15)

In a project risk management system that manages project information including information about risks for product development projects using a computer and supports project quality management through a GUI interface of a user terminal connected via a communication network ,
Project information database that stores project information related to project quality control for each project for multiple projects,
Information registration management means for displaying a registration screen on the user terminal and accepting registration of the project information from the user;
Data output management means for transmitting the relevant project information to the user terminal based on a search condition or an output condition received from the user by displaying an input screen on the user terminal;
Have
The project information includes risk information regarding risks in the project,
A project risk search processing unit that searches for relevant risk information among the risk information for a management target project that is subject to risk management by receiving operation and outputting information to the user terminal via the communication network;
A project impact calculation processing unit that calculates the impact of the risk on the project based on the searched risk information;
A risk output processing unit that outputs at least one of the risk information and the degree of influence by accepting operation and outputting information to the user terminal via the communication network;
A project risk management system characterized by comprising: The project information database stores the project information for each project executed in the past and each project currently being executed, and an impact definition table.
The project information for each project is
Customer product information,
DR project information and
Medium schedule information,
Nonconformity information,
Punch list information and
Preventive maintenance information,
Arrangement information and
The project risk management system according to claim 1, comprising: The customer product information included in the project information is:
Customer product ID of the project,
Customer product name,
Project name and
Note number and
Shipping date,
Status code,
The project risk management system according to claim 2, comprising: The DR project information included in the project information is:
Customer product ID of the project,
With days late,
Scheduled completion date,
DR implementation date,
Impact classification code,
The project risk management system according to claim 2 or 3, characterized by comprising: The medium schedule information included in the project information is:
Customer product ID of the project,
With days late
Scheduled date and
Completion date,
5. The project risk management system according to claim 2, wherein the project risk management system includes: The nonconformity information included in the project information is:
Customer product ID of the project,
Nonconformity control number,
Impact category code,
Answer date and
Date of occurrence,
Scheduled date and
The project risk management system according to any one of claims 2 to 5, characterized by comprising: The punch list information included in the project information is:
Customer product ID of the project,
Impact classification code,
With days late,
Response time,
The drafting date,
The project risk management system according to any one of claims 2 to 6, characterized by comprising: The preventive maintenance information included in the project information is:
Customer product ID of the project,
Arrangement parts,
The project risk management system according to any one of claims 2 to 7, characterized by comprising: The arrangement information included in the project information is:
Customer product ID of the project,
Arrangement parts,
Reform information and
Replacement parts and
The project risk management system according to any one of claims 2 to 8, characterized by comprising: The influence definition table is
An impact level code that is a numerical value for calculating the risk value is associated with a category that represents the impact level.
The project risk management system according to any one of claims 2 to 9, further comprising a risk value calculation formula for calculating a risk value using the influence degree definition table. The risk value calculation formula is:
DR project risk value information representing a calculation formula for calculating a risk value from predetermined items of the DR project information;
Nonconformity risk value information representing a calculation formula for calculating a risk value from a predetermined item of the nonconformity information,
Medium schedule risk value information representing a calculation formula for calculating a risk value from the predetermined items of the medium schedule information;
Punch list risk value information representing a calculation formula for calculating a risk value from a predetermined item of the punch list information;
The project risk management system according to claim 10, comprising:   The project impact level calculation processing unit uses the risk value calculated by the risk value calculation formula as a risk impact level determination condition in the calculation of the impact level, with a predetermined threshold value, mild, moderate, serious, and maximum. 12. The project risk management system according to claim 10 or 11, wherein the project risk management system distributes the determination to any one of the serious risk levels and outputs the determination. The project risk search processing unit
Accept input via customer interface for customer product information of risk management target project, and read out relevant customer product information or at least part of relevant risk management target project from the project information database based on this input content. The project risk management system according to any one of claims 2 to 12, wherein In a project risk management method for managing product information including risk-related information for product development projects using a computer and supporting project quality management operations via a GUI interface of a user terminal connected via a communication network ,
For each project, project information related to project quality control is stored in a predetermined project information database for each project,
An information registration management process for displaying a registration screen on the user terminal and accepting registration of the project information from the user;
A data output management process for transmitting the corresponding project information to the user terminal based on a search condition or an output condition received from the user by displaying an input screen on the user terminal;
Including
The project information includes risk information regarding risks in the project,
Project risk search processing for searching for relevant risk information among the risk information for a management target project to be risk managed by operation reception and information output against the user terminal via the communication network;
Project impact calculation processing for calculating the impact of the risk on the project based on the searched risk information;
Risk output processing for outputting at least one of the risk information and the degree of influence by accepting operation and outputting information to the user terminal via the communication network;
A project risk management method characterized by including: By controlling the computer processing unit, project information including risk-related information is managed for product development projects, and project quality management work support is provided via the GUI interface of the user terminal connected via the communication network. In the project risk management program
For each project, use a predetermined project information database that stores project information related to project quality control for each project.
The project information includes risk information regarding risks in the project,
The program controls the arithmetic control unit,
Display a registration screen on the user terminal and accept registration of the project information from the user;
Based on search conditions or output conditions received from the user by displaying an input screen on the user terminal, the corresponding project information is transmitted to the user terminal,
By accepting operation and outputting information to the user terminal through the communication network, for the management target project to be risk management, let the relevant risk information search among the risk information,
Based on the retrieved risk information, the impact of the risk on the project is calculated,
A project risk management program characterized in that at least one of the risk information and the degree of influence is output by receiving an operation and outputting information from the user terminal via the communication network.

Images