JPH11250125A - Project management device and recording medium - Google Patents

Abstract

(57) [Summary] The present invention relates to a project management device and a recording medium for managing a project plan and results.
Approval status of plan and actual for each operation (not approved, approval requested,
(Approved) information is added to protect the approved data, and the status is displayed on the line table screen, eliminating the need for conventional paper-based approval, simplifying management, and displaying the status of plans and results for each operation. It is an object of the present invention to enable fine-grained management and to easily display an approval state on a line table screen and protect the approval information. SOLUTION: A table for registering and managing the state of the plan and the result for each work of the project, a means for setting the state of the plan or the result for each work of the project in the table and requesting approval, and receiving the approval request Means for setting approval for a plan or a result for each operation in the table.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a project management apparatus and a recording medium for managing a project plan and results.

[0002]

2. Description of the Related Art Generally, work has three states, "planning->working->completed", as shown in FIG. In the development, approval is received before the work is completed after the planning is completed for each work, and is approved and completed when the work is completed.

[0003] Conventionally, the project management tool has determined that only the actual result is a completed work when the progress ratio% = (actual amount / planned amount) × 100% is 100%.

[0004]

Therefore, in practice,
There was a problem that the approval of the plan and the result were not performed, and it was not possible to grasp the status.

In the project management tool, the progress rate of each work is managed, but the status of approval is not managed. Therefore, it is difficult to judge the completion of the work correctly, and it is determined whether the change of the line table is permitted. Has been left to the user, and there has been a problem of being ambiguous.

[0006] In addition, since the approval is managed by a paper-based line table, in which the approved line table is printed and the seal is pressed to perform the approval, the line table is updated and printed each time the line table is updated. In addition to the time and effort required to manage by pressing the mark, the time and effort required to maintain the original version of the line table at the time of planning as a separate file because it was paper-based in terms of data protection after approval. There was also a problem that would.

[0007] The present invention solves these problems,
Approval status of plan and actual for each operation (not approved, approval requested,
(Approved) information is added to protect the approved data, and the status is displayed on the line table screen, eliminating the need for conventional paper-based approval, simplifying management, and displaying the status of plans and results for each operation. It is an object of the present invention to enable fine-grained management and to display an approval state on a line table screen in an easily understandable manner and to protect the approval information.

[0008]

Means for solving the problem will be described with reference to FIG. In FIG. 1, a plan creator terminal 1 creates a plan for each work and creates a table 5 and the like.

[0009] The manager terminal 2 is for giving approval to the plan and the result. The clerk terminal 3 is for setting, for example, the work in progress or the work completion in the table 5 for each work.

The project management data file 7 registers and manages various tables 5 necessary for a project. Next, the operation will be described.

The plan creator operates the plan creation terminal 1 to create a plan for each work of the project, sets it in the table 5 and makes an approval request, and the manager operates the manager terminal 2 to store the table 5 Approval is set in the plan for the work concerned, the person in charge operates the person in charge terminal 3 to set the state (work in progress, work completed, etc.) for each work, and makes an approval request when the work is completed. By operating the administrator terminal 2, approval is set for the actual work in the table 5.

At this time, the plan and results for each work set in the table 5 and the approval status thereof are displayed on the line table screen separately for each work. Further, the update of the data of the plan or the result of which the approval is set in the table 5 is prohibited and protected.

Therefore, it is necessary to add the information on the approval status (unapproved, approval requested, approved) of the plan and the result for each work to protect the approved data and to display the status on the line table screen. This eliminates the need for conventional paper-based approvals, makes management simple and allows for detailed management of the status of plans and results for each work, and realizes the display of approval status on a line table screen and protects approval information. Becomes possible.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, an embodiment and operation of the present invention will be described in detail with reference to FIGS.

FIG. 1 shows a system configuration diagram of the present invention.
In FIG. 1, as shown, a table 5 is set by providing the following items shown for each work.

Work name: For example, "Work A" Status: Plan completed Requester: Plan creator Approver: Approver (administrator) Other: Here, the status is Plan completed, Work in progress, Work completed The requester is a person who has requested approval (plan creator, worker, etc.), and the approver is a person (manager) who has approved a request for approval such as a plan or an actual result.

The project management data file 7 registers and manages various tables 5 and the like necessary for the project. In this example, the table 5 and the like are registered and managed. In the table 5, when the status "planned" and "work completed" are set, the update is prohibited and the plan data is individually protected for each work.

Next, the operation of the configuration of FIG. 1 will be described in detail according to the order shown in the flowchart of FIG. FIG. 2 is a flowchart illustrating the operation of the present invention.

In FIG. 2, S1 sets a table. In step S2, a plan is created. In these steps S1 and S2, the plan creator creates a project plan, and creates the table 5 for each work constituting the plan, as shown in the table 5 in FIG. 1 described above.

In S3, an approval request is made. This is S1, S
In step 2, the plan creator creates the above-described table 5 for each project planning operation, and notifies the administrator of the table 5 of an approval request.

By the above S1 to S3, the plan creator operates the plan creation terminal 1 of FIG. 1, and the work 5 of the drafted plan is stored in the table 5 for each work of the planned work. Plan creator-Approver: It is possible to set and notify the administrator terminal 2 of the approval request.

In step S5, an approval procedure is executed. In this case, the processing of FIG. 8 to S11 described later is performed (described later), and approval for each planned work is set in the table 5. S5 is
log in.

In step S6, the work progress is input. These S
In steps S5 and S6, the worker operates the person in charge terminal 3 to log in (inputs a person's ID and password and receives approval to log in) and inputs the work progress, for example, as shown in Table 5 in FIG. Enter the following items.

Work name: work A Status: work completed Requester: person in charge (worker) Approver: S7 requests approval. That is, in S6, the worker sets a work name (work A), a state (work completed), a requester (worker) in the table 5 of the work of the project planning, and notifies the manager of an approval request. .

Through steps S4 to S7, the operator can operate the operator terminal 3 shown in FIG. 1, set the work status in the table 5, and notify the administrator terminal 2 of the approval request. .

In step S8, the user logs in. In S9, it is determined whether there is an approval request. In the case of YES, the process proceeds to S10. N
In the case of O, the processing ends.

In step S10, a line chart is displayed and approval is made. As shown in a line table screen of FIG. 6 described later, the state (plan) and state (actual) of each project of the project for which approval has been requested are displayed in an easy-to-read manner on the screen. Approval is set to the state (actual) for which approval has been requested (state (plan) approval is already set in the approval procedure of S4 described above).

In step S11, the line table display table 5 is updated, and updating is prohibited and highlighted (approved). This is shown in FIG.
After the approval is set on the line table screen, the approval is set for the corresponding state (actual) in Table 5, and thereafter, the update is prohibited and the data in the approved state (actual) is protected, and the approval is set. It is highlighted for clarity.

In steps S8 to S11, the manager operates the manager terminal 2 in FIG. 1 to display the line table screen in FIG. 6 and display the status of the results (plan in S5) for each work. Then, approval is set for the work for which approval has been requested, the status of the corresponding table 5 is updated to approved, the updating of table 5 is prohibited, and the result data (approved) is protected. It is possible to highlight the approval (actual result) so that it can be easily understood.

FIG. 3 is an explanatory diagram of table creation of a line display display according to the present invention. This is for explaining the creation of the line table display table 5 described above. FIG. 3A shows a creation flowchart.

In FIG. 3A, a step S21 creates a table 5 in a line table display. Here, the following items shown in the figure are set and created for each operation. -Work name field:-Approval definition: Person in charge, date, update date, etc.-Other: Here, the work name field is a work name for each work, as shown in Table 5 of FIG. , Plan and actual fields, and a field for setting line table display data (data for setting a line table screen, data indicating approved highlighting, etc.) is provided on the right side of each field. As a result, as shown in FIG. 6, which will be described later, the work name, plan, and actual fields are displayed on the left side, and the line table display and highlighted display are executed on the right side in accordance with the data set for each field. Become.

In step S22, registration is performed. This registers the data set in S21 as shown in FIG. As described above, the fields for setting the plan, actual, and line table display data for each operation are created and registered in the line table display table 5. When the plan, actual, and line table display data are set for each operation of the table 5, the line table screen is automatically displayed based on the set data as shown in FIG.

FIG. 3B shows an example of a table 5 in a line table display. Here, as shown in the figure, the work name,
The plan, actual, and line table display data fields are provided, and according to the flowchart of FIG.
According to the approval procedure, the result setting in S12, and the approval setting in S13, it is possible to set data for each operation in the table 5, and to display the line table screen of FIG. 6 based on the set table 5.

FIG. 4 shows an update flowchart of the present invention. This is a flowchart when the plan creator, the person in charge, the manager, and the like in FIG. In FIG. 4, in step S21, the user enters a user name and password to log in. That is, based on the input user name and password, only a user who is qualified to log in with reference to a table (not shown) is permitted to log in.
Proceed to. Do not allow users who do not qualify to log in.

In step S22, it is determined whether the person who has logged in is an approver. This is because the person who has logged in at step S21 will be described later with reference to FIG.
It is determined whether the approver is qualified by referring to the user entry table. In the case of YES, the process proceeds to S23. NO
In this case, it is determined that the person is not the approver, and the process proceeds to S25.

In S23, since it is determined in S22 that the person is qualified for approval, it is determined whether or not there is an approved work. In the case of YES, it is determined that there is an approved work, so the approval is canceled at the location where the data is to be updated in S24, and the data can be updated. On the other hand, in the case of NO in S23, it is determined that there is no work that has been approved.
Proceed to.

In step S25, the line table is updated. A step S26 requests the approval of the line table again. In response to this approval request, the updated data is approved in S25, including the data canceled in S24, and the updated data after the approval is prohibited and protected.

As described above, the users such as the plan creator, the person in charge, and the manager in FIG. 1 operate the terminals and log in, and approve the approved update-protected data such as the table 5 that has been prohibited. It is possible to update or set data that has not been approved or updated after canceling, and it is also possible to request approval after updating and approve and protect it as update prohibited.

FIG. 5 shows an example of a user entry table according to the present invention. This is a table for checking the authorization authority of a user (user such as a person in charge, a leader, a department manager, etc.) logged in at the time of login in S5 and S8 in FIG. 2 and S22 in FIG. Here, for example, the approval qualification is set as shown below.

Person who has logged in Qualification Approval A Leader Confirmation only (Confirmation of approval or non-approval only) B Person in charge None (No approval qualification) C Manager Yes (Approval qualification) For example, user A is a leader who The user B is a worker in charge and has no qualification for approving plans and results, and the user C is a manager and has a qualification for approving plans and results. .

It is possible to set a qualification for each user in the above-mentioned user entry table, specify a user who can be approved, and clarify the responsibility for the approval.

FIG. 6 shows an example of a line table screen according to the present invention. This is an example of a screen displayed based on the line table display table 5 created and set in accordance with the flowchart of FIG. 2 described above. The left half shows data (FIG. 7), and the right half shows a line table. (FIG. 8).

FIG. 7 shows a data input area (left side of the entire screen) of the present invention. This is an enlarged display of the data input area on the left side of the entire screen of FIG. 6 described above. Here, the following items shown in the figure can be set.

-Sequential number:-Work name: Chapter 1-State (plan): Approved (Honda)-State (actual): Approved (Honda)-Person in charge: Honda-Scheduled work start date and time: 1997.5.1 ・ Scheduled work end date and time: 1997.6.15 ・ Scheduled production amount: 25 ・ Actual work start date and time: 1997.5.510 ・ Actual work end date and time: 1997.6.10 ・ Actual production amount: 25 Progress rate: 100% FIG. 8 shows a display portion (right side of the entire screen) of the present invention.
This shows a state in which the display portion on the right side of the entire screen of FIG. 6 described above is enlarged and displayed (it does not completely match the enlarged part of FIG. 6 and shows the concept). Here, the following items, which are surrounded by rectangles and indicated by arrows, are displayed as lines.

Scheduled start date: Scheduled end date: Actual work start date: Actual work end date: Approval status display: See FIG. 3 (b) Progress rate: The length of the bar graph next to the rectangle Show progress rate

[0046]

As described above, according to the present invention,
Approval status of plan and actual for each operation (not approved, approval requested,
(Approved) information is added to protect the approved data, and the status is displayed on the line table screen. This eliminates the need for conventional paper-based approval, making management simple and easy for each task. In addition, the state of the plan and the result can be managed finely, and the approval state can be easily displayed on the line table screen and the approval information can be protected. As a result, there is no need to approve the conventional paper-based line table, and there is no need to keep paper.In addition, since the approval information is updated without passing through the paper, processing can be performed only by changing the information inside the data. It is possible to do. Further, by providing the approval function, it is possible to accurately determine whether the work is completed or not.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of the present invention.

FIG. 2 is a flowchart illustrating the operation of the present invention.

FIG. 3 is an explanatory diagram of table creation of a line table display according to the present invention.

FIG. 4 is an update flowchart of the present invention.

FIG. 5 is an example of a user entry table according to the present invention.

FIG. 6 is an example of a line table screen according to the present invention.

FIG. 7 is an example of a data input area (left side of the entire screen) according to the present invention.

FIG. 8 is an example of a display portion (right side of the entire screen) according to the present invention.

FIG. 9 is an explanatory diagram of a conventional technique.

[Explanation of symbols]

 1: Plan creator terminal 2: Manager terminal 3: Person in charge terminal 4: Project management data file 5: Table (table for displaying line chart)

Claims (4)

[Claims] A table for registering and managing the state of the plan and result for each work of the project, and a table for storing the state of the plan or result for each work of the project. And a means for setting approval for a plan or a result for each work in the table for which the approval request has been received. 2. The project management apparatus according to claim 1, further comprising means for displaying a plan and a result for each work set in the table and an approval state thereof separately for each work. 3. The project management apparatus according to claim 1, further comprising means for prohibiting and protecting update of plan or actual data in which approval is set in the table. 4. A means for registering and managing the status of the plan and result for each work of the project in a table, a means for setting the status of plan or result for each work of the project in the table and requesting approval, A computer-readable recording medium that records a program that functions as a means for setting an approval for a plan or an actual result of each work in the table that has received the approval request.