JP2008257286A - Project progress management system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a project progress management system and method for preventing a worker from failing to check all the required tasks, and reliably preventing the worker from omitting or failing in the work. <P>SOLUTION: A task required for an event is specified from an event management database 1 storing events of a project and a task database 4 storing tasks required before the event. The check results are registered in a check result database 5 based on the check items accumulated in the check item database 5. The check items which have not been checked in the check result database 5 and the check items which have not satisfied check determination are extracted from the check item database with a check item extraction part 10. A work procedure in which work contents of the tasks regarding the displayed check items are described is extracted from a work procedure database 7 and displayed. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a progress management system that manages a project schedule and an event progress state on a computer, and in particular, a project progress management system that can be suitably implemented to prevent check items from being checked during product development, and Regarding the method.

  In development and design work such as home appliances, it is necessary to perform various inspections and experiments necessary for commercialization in cooperation with related departments or external companies. Furthermore, in recent years, development design work has been required to be completed in a shorter period of time, such as a shorter development period and an increased number of development models. However, in the situation where multiple models are being developed in parallel, there are many developments such as different destinations and different sizes, and such products look the same, and laboratories and inspection tools are limited. Therefore, there is a risk that a model that has already been experimentally inspected will be inspected again, or that a model that needs to be experimentally inspected will be mistaken for being inspected.

  Therefore, the milestones that become milestones in development work and the progress of the work required up to that milestone are managed on the computer, the work checklist for the work end of the recently completed milestone, the worklist of the next milestone, and A system has been proposed in which periodic warnings about work of milestones exceeding the schedule are delivered to a specified email address. (For example, refer to Patent Document 1.)

JP 2002-236788 A

  In the above-mentioned conventional technology, checklists are delivered by email in units of milestones, but it is not confirmed whether or not they are checked, and in the situation where multiple models are developed in parallel, there is a mistake in the check work. There is a problem that leaks. Further, there is a problem that when the check is performed but the determination is NG, forgetting to perform the check again. In addition, if you want to view the work procedure manual to confirm the work procedure of the check, the work procedure manual corresponding to the check item is not grasped in advance by the system side, so it is necessary for people to search on the system separately There is a problem that the work procedure manual cannot be accurately retrieved or that it takes time to retrieve the corresponding work procedure manual.

  The object of the present invention is to prevent check omissions for all tasks that an operator needs to perform, and reliably prevent omissions and work errors.

The project progress management system of the present invention
A project progress management system for managing the progress of a project,
An event management database where project events are stored;
A task database that stores tasks that need to be done before the event,
A target task extraction unit that extracts and identifies a task necessary for the event from an event management database and a task database;
A check item database in which check items to be confirmed in each task are accumulated;
A check results database in which check results of each check item of the check item database are accumulated;
A check record registration unit for registering a check record in the check record database;
A work procedure manual database in which procedure manuals describing the detailed work contents of each task are stored;
A check item that is not checked in the check results database in the task specified by the target task extraction unit, and a check item that does not satisfy the check determination; a check item extraction unit that extracts from the check item database;
A check item display unit for displaying the check items extracted by the check item extraction unit;
A work procedure manual extracting unit that extracts a work procedure manual describing the work contents of a task related to the check item displayed by the check item display unit from the work procedure manual database;
A project progress management system comprising: a work procedure manual display unit that displays the work procedure manual extracted by the work procedure manual extraction unit.

The present invention also provides
It further includes a project management database in which the types of projects are stored, and the progress management of a plurality of projects is performed.

Furthermore, the project progress management method of the present invention includes:
A project progress management method for managing the progress of a project,
A target task extraction step for identifying a task necessary for the event from an event management database in which the project event is stored and a task database in which a task necessary to be performed by the event is stored;
Based on a check item database in which check items to be confirmed in a task are accumulated, a check result registration step for registering check results of check items in a check result database;
A check item extraction step for extracting from the check item database check items that are not checked in the check result database in the task identified by the target task step, and check items that do not satisfy the check determination;
A check item display step for displaying the check items extracted by the check item extraction unit;
A work procedure manual extraction step for extracting a work procedure manual in which work contents of a task related to the check item displayed by the check item display unit are described from the work procedure manual database storing the work procedure manual;
And a work procedure manual display step for displaying the work procedure manual extracted by the work procedure manual extraction unit.

  Furthermore, the program of the present invention causes a computer to execute the project progress management method.

  Furthermore, the recording medium of the present invention causes a computer to execute the project progress management method.

  According to the present invention, an event management database in which project events are stored and a task database in which tasks that need to be performed before the event are specified are identified for the event and accumulated in the check item database. Based on the check item, the check record is registered in the check record database. Check items that are not checked in the check results database and check items that do not satisfy the check judgment are extracted from the check item database by the check item extractor and displayed, and the task contents related to the displayed check items Is extracted from the work procedure manual database and displayed.

  In this way, three cases are managed, when the check judgment of the check item is satisfied, when it is not satisfied, and when it is not checked, among which the check judgment is NG and the check is not automatically checked Since the operator can obtain the check items that he / she needs to perform, and the work procedure manual necessary for the work of the check items can be reversely viewed from the check items, Work can be done efficiently.

  According to the present invention, for a task that an operator needs to perform in a progress plan, a check item that is not checked among check items necessary for work is not satisfied, and a check that needs to be checked again. Since items are automatically extracted and displayed, check omissions can be prevented, and work procedure manuals corresponding to each check item are displayed for the procedure, preventing work omissions and work mistakes. it can.

  FIG. 1 is a diagram showing a configuration of a project progress management system according to an embodiment of the present invention, and FIG. 2A is a flowchart for explaining a system flow of the project progress management system according to the embodiment of the present invention. is there. The project progress management system according to the present embodiment is realized by a computer, and presents a product development by presenting the checks regarding the implementation of tasks to be performed before the meeting to be held based on a predetermined schedule without fail. Used to support. This project progress management system is realized by executing a program readable by a computer according to the project progress management method of the present invention, and this program is recorded on a recording medium such as a CD-ROM.

  The project progress management system according to the present embodiment includes seven event management databases 1, a project management database 2, a progress management database 3, a task database 4, a check item database 5, a check results database 6, and a work procedure manual database 7. The database is composed of six main parts: a target task extraction unit 8, a check result registration unit 9, a check item extraction unit 10, a check item display unit 11, a work procedure manual extraction unit 12, and a work procedure manual display unit 13. ing.

  Each information to be registered in various databases is registered (step a11), a project is created based on the registered information (step a12), a schedule of the project is registered (step a13), and an actual task is performed. Work while browsing the procedure manual (step a14) and register the check results of the check items (step a15). In the work procedure manual, as shown in FIG. 15, work contents to be worked on in each task are described, and check items are assigned as items to be checked in particular. There may be a plurality of work procedure manuals 152, and there may be a plurality of check items 153 corresponding to the work procedure manuals 152.

  FIG. 2B is a flowchart showing the work procedure of the administrator of the project progress management system according to the embodiment of the present invention. The administrator registers information to be registered in the database (step b1), creates a new project (step b2), creates and registers a progress schedule (step b3), and then starts event progress (step b1). b4). Then, confirm and register the progress of the task by the worker (step b5), check whether all events have been completed (step b6), and if not, hold the next event. The result is registered (step b4) (step b5), and the process ends when the event allocated to the project is completed.

  FIG. 2C is a flowchart showing a procedure when used by an operator of the project progress management system. Details of the operator's work procedure will be described below. In the project management database 2, a project name 32 is stored in association with the project management number 31, as shown in FIG.

  In the event management database 1, as shown in FIG. 4, event names 42 performed in each project are stored in association with the event management number 41.

  In the progress management database 3, as shown in FIG. 5, the event management number 54, the scheduled execution date 52 of the event, and the event actual date 53 are stored using the progress plan number 51 as a search key. ing. This is stored together with the model management number 55 so that it can be managed for each model.

  In the work procedure manual database 7, as shown in FIG. 6, a work procedure manual 62 is stored in various formats such as PDF format and MS-Office (Word / Excel / PowerPoint) format. The work procedure manual number 61 is assigned as a search key. Note that tasks corresponding to work in the work procedure manual are associated using the task number 63 as a search key.

  In the task database 4, as shown in FIG. 7, an event management number 72 for knowing an event name necessary for each task by referring to the progress management database 3 using the task number 71 as a search key, and each task A standard number of days 73 required for the above work and a task name 74 of each task are stored and stored. The event name in the event management database 1 is searched using the event management number 72 as a search key, and the event name can be obtained. Similarly, from the progress management database 3 using the event management number 72 as the search key. It is possible to obtain the scheduled date of the event.

  As shown in FIG. 8, the check item database 5 includes a check item number 81 as a search key, a check item name 82, and a work procedure for reversing a work procedure manual necessary for checking each check item. The book number 83 is stored.

  The work procedure manual number 61 in the work procedure manual database 7 is searched by using the work procedure manual number 83 as a search key, and the work procedure manual can be obtained. The task number 63 in the work procedure manual database 7 can be obtained. The task name is available from

  In the check record database 6, as shown in FIG. 9, the check item number 91 is used as a search key and the check item determination result is “OK”, and the determination is not satisfied. A search result 92 for registering the result of “NG” indicating “no” or “none” indicating that the item is not checked, and a search key for searching for the project name in which the check result 92 is registered Project management number 93 is stored.

  It is assumed that “None” that is not checked is registered as the specified value before the check record registration. The check item database 5 is searched using the check item number 91 as a search key, and the check item name 82, the work procedure manual 62, and the task name 74 can be obtained.

  These check item names 82, work procedure manuals 62, and task names 74 do not have model-specific information, but by distinguishing the work procedure manuals 62, it is possible to distinguish the task differences for each destination. It becomes. For example, by registering two types of work procedure manuals 62 for Country A and Country B, and corresponding to different tasks and projects, it is possible to display only the corresponding ones.

  As shown in FIG. 10, the extraction procedure of the target task extraction unit 8 describes a process of specifying a task necessary for a certain meeting using the progress management database 3 and the task database 4. For example, when developing a model of home appliance, a schedule is first determined according to the scheduled date and time of an event registered in the progress management database 3.

  Next, a task necessary for a certain event can be extracted and specified by searching the event management number 72 of the task database 4 from the event management number 54 of the progress management database 3. In FIG. 10, the meeting D is held on June 30, 2006, and shows the result of specifying that six tasks, Task A to Task F, are required by the due date.

  In addition, since the standard number of days necessary for the task is also stored in the task database 4, it is possible to notify the due date of the start time of the task by subtracting the standard number of days of 73 minutes from the meeting date. Is possible. By doing this, it is possible to avoid delaying the time to start a task, and by providing a margin for the number of days required for each task, the ideal processing order of tasks can be presented from the system side. Is possible.

  In the check record registration unit 9, when the determination result of the check item work result is OK, “completed”, “NG”, and “NG” when re-check is necessary, an input instruction given by the operator In accordance with the check result database 6. A specific operation procedure will be described with reference to FIG.

  The worker can know the schedule of the meeting by browsing the confirmation page 111 as shown in FIG. 13 using an HTML browser such as Internet Explorer (step c1 in FIG. 2C). Then, a list 116 of tasks that need to be performed up to a certain conference 115 can be known (step 2 in FIG. 2C). For example, when the task selection button 116 of the task A is pressed, a work procedure manual browsing button 124 necessary for the work of the task A, the contents of the check items and the check result registration column 125 are displayed in the right adjacent frame. Therefore, when the operator wants to confirm the details of the work contents of task A, the user can proceed with the work while viewing the detailed work procedure manual by pressing the procedure manual display button 124.

  The result of the check item is registered after the work is completed, but before the operator registers, “None” is input as a reference value in the check presence / absence column as indicated by reference numeral 127, and the worker registers the result. By doing so, the value is changed. For example, when the determination of the check result item of the work is “OK” and “completed” is to be registered as the check item result, the check portion under “OK” in the check result registration column 125 of the confirmation page 111 is checked. By clicking with the mouse, the check presence / absence column results are reflected in the database as indicated by reference numeral 128.

  If the result of the work check item is “NG” and the work needs to be performed again and “NG” is to be registered as the check item result, “NG” in the check result registration column 126 of the confirmation page 111 is displayed. By clicking with a mouse on the lower check portion, the result is reflected in the database as indicated by reference numeral 129.

  The procedure for the check item extraction unit 10 to extract check items, as shown in FIG. 11, shows data to be extracted from the check item database 5 and the check results database 6 and displayed by the check item display unit 11. . Here, using the check item number as a search key, the check item 82 from the check item database 5 and the work procedure manual No83, “none” of the check records 92 from the check record database 6, and “NG”, Project management number 93 is extracted and regrouped under the same check item number.

  Then, the check item display unit 11 displays the check item A2, the check result A3, the project name / task name, and when the operator gives an instruction to browse the work procedure manual, the work procedure is displayed. The book number A5 is searched as a search key and displayed. In addition, by extracting the task number 63 in the work order database 7, it is possible to divide into groups for the same task number and to set a delimiter between different task numbers.

  The work procedure manual extraction unit 12 specifies a designated work procedure manual in the work procedure manual database 7 using the work procedure manual number as a search key when an instruction is given by the worker to view the procedure manual. Then, the worker can view the specified work procedure manual with an application associated with each file format. For example, if the file format is the PDF format, “Acrobat Reader” is activated, and if the file format is the MS-Office Excel format, “MS-Office Excel” is activated.

  FIG. 12 shows a data update procedure when the schedule is changed. For example, when the meeting D is changed from the originally scheduled date of June 30, 2006 to July 8, 2006, The change information is updated in conjunction with the end date and time of each task in the task database via the event management numbers 54 and 72. It is also possible to update the start date and time from the required number of days at the same time.

  FIG. 13 is a diagram showing an embodiment according to the present invention. The worker can know the schedule of the conference by browsing the task list confirmation page 111 using an HTML browser (step c1 in FIG. 2C). Then, it is possible to know a list of tasks that need to be performed by a certain conference 115 (step c1 in FIG. 2C). For example, when the selection button 116 of the task C is pressed, a work procedure manual browsing button 117 necessary for the work of the task C, the contents of the check items, and the check result registration column 118 are displayed in the right adjacent frame. Then, the operator can perform the check work while browsing the work procedure manual (step c3 in FIG. 2C), and can register the results as in the procedure in FIG. 12 (step c4 in FIG. 2C).

  Here, by pressing the selection button 116 of another task, the information in the frame on the right is switched (step c5 in FIG. 2C), the work procedure manual browsing button 117 of the newly selected task, and the check item The contents and the check result registration column 118 are displayed, and the operator can perform the check work while browsing the work procedure manual (step c3 in FIG. 2C), and can register the result as in the procedure in FIG. (Step c4 in FIG. 2C).

  Then, when it is desired to extract check items that have not been checked yet and check items that are registered as “NG” among check items that are necessary until a certain meeting, the operator presses the confirmation button 119 to It is possible to extract check items that are necessary for the conference and are not checked, and check items whose check determination is NG (step c6 in FIG. 2C).

  For example, when the confirmation button 119 in FIG. 13 is pressed, the tasks with the check record “None” and “NG” among the tasks required up to the meeting D are extracted as indicated by reference numeral 114. The confirmation button 119 can display a task necessary for the current conference by moving to the next conference or the previous conference on the schedule starting from the current conference.

  When the confirmation button 119 is pressed, a series of check items such as A1 to A6 in FIG. 11 is finally extracted through the above-described process, and the check list 112 is displayed by the check item display unit 11 ( Step c7) in FIG. 2C. The check list 112 displays a model name 120 and a task name 121 as well as a check item that is necessary and not checked before the meeting and a check item 122 whose determination is “NG”.

  In the check item 122, a check item with a determination of “NG” is displayed in red, for example, so that the operator can easily distinguish the check item with no check from the determination “NG”. Here, for each check item, a procedure manual display button 123 for displaying a work procedure manual indicating the work is prepared (step c8 in FIG. 2C), and the operator presses the button 123. Thus, the work procedure manual is extracted and displayed (steps c9 and c10 in FIG. 2C).

  Then, the work is proceeded according to the work procedure manual, and when it is confirmed that the check determination is “OK”, the check item result registration field 122 is clicked with the mouse as in FIG. The result can be registered (step c11 in FIG. 2C). Furthermore, by pressing the update button 112B, the contents of the check record database 6 including the newly registered check record are updated until there are no check items that have not yet been checked and check items that are judged “NG”. The extraction is repeated (step c12 in FIG. 2C). When these items disappear, the close operation button 112A is pressed to end the extraction operation.

  According to the above procedure, three cases are managed: the case where the check determination result of the check item is OK, the case where it is NG, and the case where it is not checked, and the check determination is checked as “NG”. Since it is possible to automatically extract and display items that do not exist, the operator can obtain the check items that he / she needs to perform and reverse the work procedure manual necessary for the work of the check items from the check items. Since it can be browsed, it is possible to work efficiently.

  Also, for the tasks that the worker needs to perform in the progress plan, among the check items necessary for the work, the check items that are not checked and the determination items are NG and the check items that need to be checked again are automatically extracted. Since it is displayed, the check omission can be prevented, and the work procedure manual corresponding to each check item is displayed for the procedure, so it is possible to prevent work omissions and work mistakes, and the operator needs to do It is possible to reliably check all tasks with no omissions.

  In the project progress management system and method of the present invention, a progress plan is managed on a computer, and a single or a plurality of tasks are assigned by the date and time when a meeting as a milestone of the progress plan is held. It is possible to check without omission when there is a single or a plurality of check items, and it is possible to quickly browse the work procedure manual for the procedure.

It is a figure which shows the structure of the project progress management system which concerns on one Embodiment of this invention. It is a flowchart which shows the system flow of a project progress management system. It is a flowchart which shows the administrator flow of a project progress management system. It is a flowchart which shows a project progress management system worker flow. It is a figure which shows the structure of the project management database. 2 is a diagram illustrating a configuration of an event management database 1. FIG. It is a figure which shows the structure of the progress management database. It is a figure which shows the structure of the work procedure manual database. It is a figure which shows the structure of the task database. It is a figure which shows the structure of the check item database. It is a figure which shows the structure of the check performance database. It is a figure which shows the data processing by the target task extraction part. It is a figure which shows the data processing by the check item extraction part. It is a figure which shows the data update at the time of progress plan change. It is a figure for demonstrating the work procedure by a project progress management system. It is a figure for demonstrating the other work procedure by a project progress management system. It is a figure which shows the relationship between a task, a work procedure manual, and a check item.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Event management database 2 Project management database 3 Progress management database 4 Task database 5 Check item database 6 Check result database 7 Work procedure document database 8 Target task extraction part 9 Check result registration part 10 Check item extraction part 11 Check item display part 12 Work Procedure Manual Extraction Unit 13 Work Procedure Manual Display Unit 31 Project Management Number (Project Management Database Search Key)
32 Project name 41 Event management number (event management database search key)
42 Event name 51 Progress plan number 52 Scheduled date 53 Progress result date 54 Event management number (event management database search key)
55 Project management number (Project management database search key)
61 Work procedure manual number (work procedure manual database search key)
62 Work procedure manual name (work procedure manual file name)
63 Task number (task database search key)
71 Task number 72 Event management number (event management database search key)
73 Standard days 74 Task name 81 Check item number 82 Check item name 83 Work procedure manual number (work procedure manual database search key)
91 Check Item Number 92 Check Item Performance 93 Project Management Number (Project Management Database Search Key)
111 List of Tasks Necessary until Meeting D 112 List of Check Items with “NG” and No Check 112A Button for Closing Check Item List 112B Check Item List Update Button 113, 152 Work Procedure Manual 114 Check Item Extraction Check items after extraction by department 115 Event name (Conference D)
116 Task Display Buttons Necessary to Event (Conference D) 117 Task Procedure Display Button for Task (Task C) 118 Check Item for Task C and Check Result Registration Field 119 Check Item List Extraction Execution Unit 120 Check Item Target Model Name 121 Target task name of check item 122 Check item name and check result 123 Check item work procedure manual display button 124 Task (task A) work procedure manual display button 125 Task A check item and check result registration field (before registration) )
126 Task A check items and check results registration field (after registration)
127 Before check result registration 128 After check result registration (in case of judgment OK)
129 After registering check results (in the case of judgment NG)
151 Task 153 Check item A1 Check item number A2 Check item name A3 Result of check item A4 Project management number (project management database search key)
A5 Work procedure manual number (work procedure manual database search key)
A6 Task number (task database search key)

Claims (5)

A project progress management system for managing the progress of a project,
An event management database where project events are stored;
A task database that stores tasks that need to be done before the event,
A target task extraction unit that extracts and identifies a task necessary for the event from an event management database and a task database;
A check item database in which check items to be confirmed in each task are accumulated;
A check results database in which check results of each check item of the check item database are accumulated;
A check record registration unit for registering a check record in the check record database;
A work procedure manual database in which procedure manuals describing the detailed work contents of each task are stored;
A check item that is not checked in the check results database in the task specified by the target task extraction unit, and a check item that does not satisfy the check determination; a check item extraction unit that extracts from the check item database;
A check item display unit for displaying the check items extracted by the check item extraction unit;
A work procedure manual extraction unit that extracts a work procedure manual that describes work contents of a task related to the check item displayed by the check item display unit from the work procedure manual database;
A project progress management system comprising: a work procedure display unit that displays the work procedure manual extracted by the work procedure manual extraction unit.   The project management system according to claim 1, further comprising a project management database in which project types are stored, and performing progress management of a plurality of projects. A project progress management method for managing the progress of a project,
A target task extraction step for identifying a task necessary for the event from an event management database in which the project event is stored and a task database in which a task necessary to be performed by the event is stored;
Based on a check item database in which check items to be confirmed in a task are accumulated, a check result registration step for registering check results of check items in a check result database;
A check item extraction step for extracting from the check item database check items that are not checked in the check results database in the task identified by the target task extraction step, and check items that do not satisfy the check determination;
A check item display step for displaying the check items extracted by the check item extraction unit;
A work procedure manual extraction step for extracting a work procedure manual in which work contents of a task related to the check item displayed by the check item display unit are described from the work procedure manual database storing the work procedure manual;
A project progress management method, comprising: a work procedure display step for displaying the work procedure manual extracted by the work procedure manual extraction unit.   A program for causing a computer to execute the project progress management method according to claim 3.   A recording medium storing a program for causing a computer to execute the project progress management method according to claim 3.

Images