JP6665455B2 - Work management device, display control method, and program - Google Patents

Description

The present invention relates to a work management device, a display control method, and a program.

Conventionally, a schedule management tool generally manages a schedule in which a start time and an end time are set, and a ToDo list (work item list) in which a final deadline and a priority are set. It is.
As a technology for automatically generating a ToDo list, an e-mail is acquired from a user's mail server based on information registered by the user, and information on a sender, a schedule included in the e-mail, and a ToDo (work item) (Patent Document 1) discloses a technique of extracting the information of the most important sentence, extracting the information of the most important sentence, and combining the information to generate an abstract including a ToDo list.
In addition, in the case of work that must be performed periodically, there is also known a technique of defining a work repetition interval and automatically generating ToDo without registering ToDo every time.

JP-A-2002-24144

However, in the technology for automatically generating a ToDo (work item), even when it is necessary to take several steps to complete one work, the entirety is generated and managed as one ToDo. The Rukoto. In this case, the progress management of the work cannot be performed in detail, which makes the work ambiguous, and there is a possibility that inconvenience such as running out of time in the latter half of the work may occur.
Further, in order to appropriately manage the progress of the work, it is possible to manually generate each procedure constituting one work as an individual ToDo, but as the number of procedures increases, the work of registering in the ToDo list becomes more complicated. Thus, efficient ToDo management could not be performed.

  An object of the present invention is to generate work items related to each procedure constituting one work so that efficient work management can be performed.

In order to solve the above-mentioned problem, a work management device according to the present invention includes a display control unit for displaying a Todo list, a template including a plurality of procedures constituting the work, an execution order of the procedure, and necessary number of days information for each procedure. A storage means for storing data, and a work item including a deadline of the procedure for each procedure constituting the work, based on a scheduled completion date of the work specified by a user and template data stored in the storage means. a generating means for setting said display control means according to the display start date of work items thus generated to the Todo list for each work item generated and generates as Todo the advance of the work items generated by the generating means For the work item corresponding to the defined procedure, the user can set the completion date / time information or When the ease information is input, the execution result information corresponds to the predetermined procedure in the template data so that the execution result information is reflected in the setting of the display start date for the next work item by the generation unit. And correction means for correcting the required number of days information .
Further, the display control method according to the present invention is a Todo executed by a work management apparatus including a storage unit for storing a plurality of procedures constituting a work, an execution order of the procedures, and template data including information on the number of days required for each of the procedures. A list display control method, comprising, for each procedure constituting the work, a time limit of the procedure based on a scheduled completion date of the work specified by a user and template data stored in the storage unit. a generation step of setting the display start date of work items thus generated of a work item to the Todo list for each work item generated so as to generate as Todo, a predetermined one of the work items generated in the generation step For the work item corresponding to the procedure, the completion date / time information or difficulty information of the work item is input by the user as the execution result information. In this case, the required number of days information corresponding to the predetermined procedure in the template data is corrected so that the execution result information is reflected in the setting of the display start date for the next work item by the generation step. And a correcting step .
In addition, the program according to the present invention includes a computer, a display control unit for displaying a Todo list, a scheduled completion date of work specified by a user, a plurality of procedures constituting the work, an execution order of the procedure, and the procedure. based on the stored template data storage means for storing template data containing the required number of days information for each, and the work items including the date of the procedure for each procedure constituting the working produces and generates as Todo Generating means for setting a display start date of the generated work item on the Todo list by the display control means for each work item; a work item corresponding to a predetermined procedure among the work items generated by the generating means In response to this, the user inputs completion date / time information or difficulty information of the work item as the performance result information. In this case, the required number of days information corresponding to the predetermined procedure in the template data is corrected so that the execution result information is reflected in the setting of the display start date for the next work item by the generation unit. It is characterized by functioning as a correction means .

  ADVANTAGE OF THE INVENTION According to this invention, the work item which concerns on each procedure which comprises one work can be produced | generated and efficient work management can be performed.

1 is a connection diagram illustrating a schematic configuration of a work management system according to an embodiment. FIG. 2 is a block diagram illustrating a main control configuration of a server device and a client terminal according to the embodiment. It is a figure showing an example of ToDo data. It is a figure showing an example of ToDo template data. It is a figure showing an example of delay cause data. It is a figure showing an example of time factor data. It is a figure showing an example of each procedure which constitutes a leaflet distribution work. It is a flowchart which shows the process which numbers a procedure number to each procedure which comprises an operation | work. It is a flowchart which shows the process which produces | generates ToDo based on ToDo template data. It is a figure showing an example of ToDo data to which newly generated ToDo was added. 11 is a flowchart illustrating a process of updating a correction value of a template relating to the ToDo when the generated ToDo is completed.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

First, the configuration of the work management system 100 according to the present embodiment will be described.
As shown in FIG. 1, the work management system 100 includes a server device (work management device) 1 and a plurality of client terminals 2. In the work management system 100, the server device 1 and the client terminal 2 are communicably connected to each other by a communication network N. The communication network N is a communication network including a wired LAN (Local Area Network), a wireless LAN, a mobile communication network, the Internet, and the like. The number of client terminals 2 is not particularly limited.

The server device 1 is an information device such as a PC and a WS (Work Station). The server device 1 is a schedule management server that manages work schedules, ToDo (work items), and the like.
The server device 1 includes one or a plurality of servers deployed on the communication network N. In the present embodiment, one management server is used. However, for example, a plurality of server groups such as a web server, a DB server, and a storage server may be used.
As illustrated in FIG. 2, the server device 1 includes a control unit 11, an operation unit 12, a display unit 13, a storage unit 14, and a communication unit 15.

  The control unit 11 centrally controls the operation of the server device 1. Specifically, the control unit 11 is configured to include a CPU, a ROM, a RAM, and the like. The control unit 11 cooperates with the ROM developed in the work area of the RAM and the program data stored in the storage unit 14 and the CPU. The respective parts of the device 1 are generally controlled.

  The operation unit 12 includes a keyboard having character input keys, numeric input keys, and keys associated with other various functions, a pointing device such as a mouse, and the like. The operation unit 12 receives an operation input from a user and responds to the operation input. An operation signal is output to the control unit 11.

  The display unit 13 includes a display such as an LCD (Liquid Crystal Display), and displays an image based on a display control signal output from the control unit 11 on a display screen.

  The storage unit (storage unit) 14 is configured by a hard disk drive (HDD), a semiconductor memory, or the like, and stores data such as program data and various setting data so that the control unit 11 can read and write the data. The storage unit 14 also stores schedule data 141 for managing a work schedule, ToDo data (work item data) 142 (see FIG. 3) for managing ToDo, operating day data 143, and ToDo template data ( Work item template data) 144 (see FIG. 4), delay cause data 145 (see FIG. 5), and time factor data 146 (see FIG. 6) are stored.

  As shown in FIG. 3, the ToDo data (work item data) 142 includes, for each ToDo (work item), a display start date A1 indicating a start date of display of ToDo, a deadline A2 indicating a final completion deadline, and a work period A2. Title A3 indicating the name, detail A4 indicating the details of the work, priority A5 indicating the importance or urgency of the work, status A6 indicating the current state, completion date A7 indicating the date when the work was actually completed, template , A template number A8 indicating the number of the template referred to when the ToDo was generated, a procedure number A9 indicating the number of the work procedure in the template, and a progress difficulty A10 indicating the difficulty of completing within the deadline A2. , A delay cause number A11, which is a number indicating a cause when the work is delayed.

  The priority A5 is defined as 1 to 5, and the smaller the number, the higher the priority. In the status A6, "1" is set when not started, "2" is set for a work in progress, and "3" is set for completed. The progress difficulty level A10 is set to “−1” when the task is completed with a margin, “0” when the task is completed as scheduled, and “1” when the task is not completed to be completed as scheduled. The delay cause number A11 is a number indicating a cause when the completion date A7 has passed the deadline A2.

  As shown in FIG. 4, the ToDo template data (work item template data) 144 includes a template number B1 indicating the management number of the template, a template name B2 indicating the name of the template to be referred to when adding the ToDo, an operation in the template. Procedure number B3 indicating the number of the procedure, procedure name B4 indicating the name of the work procedure, procedure details B5 indicating the details of the work procedure, procedure priority B6 indicating the priority of the work procedure, number of days required to complete the work , The relative flag B8 indicating the base point for calculating the required number of days B7, the next procedure number B9 indicating the number of the work procedure to be executed after the current procedure is completed, and the correction to be added to the required number of days B7 next time It is composed of information of a correction value B10 indicating a value.

The procedure number B3 is numbered in reverse order to the work procedure, with the last work being “1”. When added to ToDo, the procedure name B4, the procedure details B5, and the procedure priority B6 become the title A3, the details A4, and the priority A5 (see FIG. 3).
The required number of days B7 is used in combination with the relative flag B8. Specifically, when the relative flag B8 is "0", it indicates how many days before the completion of the final work procedure the work procedure needs to be completed. For example, when the relative flag B8 is "0" and the required number of days B7 is "3", it indicates that the work procedure needs to be completed at least three days before the completion of the final work procedure. When the relative flag B8 is "1", it indicates the number of days required to complete the work procedure. For example, when the relative flag B8 is “1” and the required number of days B7 is “1”, it indicates that the number of days required to complete the work procedure is one.
The correction value B10 indicates a correction value to be added to the necessary number of days B7 next time when the work is not completed within the set time limit A2 after the execution of ToDo.

  As shown in FIG. 5, the delay cause data 145 includes a delay cause number C1 indicating the management number of the delay cause, a delay cause C2 indicating the cause of the delay when executing ToDo, and whether or not the delay is reflected in the correction. And a timing factor flag C4, which is a flag indicating whether or not the cause of the delay is due to the timing.

  As shown in FIG. 6, the timing factor data 146 includes a template number D1 indicating a template number to be corrected by time, a procedure number D2 indicating a procedure number to perform correction by time, a month D3 indicating a month to be corrected, It is composed of information of a correction value D4 indicating a correction value due to a time factor.

  The communication unit 15 is a communication interface having a communication IC (Integrated Circuit), a communication connector, and the like, and performs data communication via the communication network N using a predetermined communication protocol under the control of the control unit 11.

The client terminal 2 is an information device such as a PC, a tablet terminal, a smartphone, and a mobile phone.
As shown in FIG. 2, the client terminal 2 includes a control unit 21, an operation unit 22, a display unit 23, a storage unit 24, and a communication unit 25.

  The control unit 21 centrally controls the operation of the client terminal 2. Specifically, the control unit 21 is configured to include a CPU, a ROM, a RAM, and the like. The respective parts of the terminal 2 are totally controlled.

  The operation unit 22 includes a keyboard having character input keys, numeric input keys, keys associated with various functions, and the like, a pointing device such as a mouse, and receives an operation input from a user and responds to the operation input. An operation signal is output to the control unit 21.

  The display unit 23 includes a display such as an LCD, and displays an image based on a display control signal output from the control unit 21 on a display screen. For example, the display unit 23 displays a screen for listing the generated ToDo as a ToDo list. The display unit 23 displays a screen on which the user can select the progress difficulty level A10 and the delay cause number A11 of the completed ToDo.

  The storage unit 24 is configured by an HDD, a semiconductor memory, or the like, and stores data such as program data and various setting data so that the control unit 21 can read and write the data.

  The communication unit 25 is a communication interface having a communication IC, a communication connector, and the like, and performs data communication via the communication network N using a predetermined communication protocol under the control of the control unit 21.

Next, the operation of the server device 1 of the work management system 100 according to the present embodiment will be described with reference to FIGS.
First, a process of creating the ToDo template data 144 will be described with reference to FIGS. In the present embodiment, as an example of a task for creating the ToDo template data 144, a task of creating and distributing a flyer for an advertisement (hereinafter, a leaflet distribution task) will be described.

As shown in FIG. 7, the flyer distribution work includes a procedure for arranging a printing shop (hereinafter referred to as a printing factory arrangement T1), a procedure for creating a manuscript for a flyer (hereinafter, manuscript creation T2), and arranging a part-time job for distributing a flyer. (Hereinafter referred to as part-time job distribution T3), submitting a manuscript to a print shop (hereinafter referred to as T4), receiving a sample from the print shop (hereinafter referred to as a sample rise T5), and confirming a sample (hereinafter referred to as a sample) , Sample check T6), a procedure for instructing final printing (hereinafter, final printing instruction T7), and a procedure for distributing a flyer sent from a printing shop (hereinafter, advertising flyer distribution T8).
The user operates the operation unit 22 of the client terminal 2 to register the above procedures and the connections between the procedures. The registered information is transmitted to the server device 1.
The server device 1 performs a process of assigning a procedure number to each procedure constituting the work based on the registration information. Hereinafter, the process of assigning the procedure number will be described with reference to the flowchart of FIG.

  First, the control unit 11 of the server device 1 assigns “1” as the procedure number to the final procedure, and sets “0” indicating that the next procedure does not exist as the next procedure number of the final procedure (step S101). ). For example, in the example shown in FIG. 7, “1” is assigned to “advertising flyer distribution T8” which is the final procedure.

  Next, the control unit 11 sets an initial value “1” for the procedure number N, an initial value “0” for the next procedure number Np, and “final procedure” for the numbering target procedure X (step S102).

  Next, the control unit 11 enumerates and rearranges the immediately preceding procedure connected to the numbering target procedure X, and sets them as Y (M) (step S103). That is, Y (M) is an array of Y having M elements. For example, in the example shown in FIG. 7, when “final procedure (advertisement leaflet distribution T8)” is set in the numbering target procedure X, the immediately preceding procedure connected to the numbering target procedure X is the final printing Instruction T7 and part-time job arrangement T3 for flyer distribution, and the arrangement of these two procedures is Y (M). In addition, as a method of rearranging the respective procedures, for example, an arbitrary method such as a sequence name of the procedure names or an order in which the user comes up with the work can be adopted. Here, it is assumed that the print job is arranged in the order of the final print instruction T7 and the part-time job arrangement T3 for flyer distribution.

  Next, the control unit 11 sets L indicating the arrangement order of M to 1 and sets the procedure number N to the next procedure number Np (step S104). For example, if the procedure number N is set to 1, “1” is set to the next procedure number Np.

  Next, the control unit 11 sets Y (L) in the numbering target procedure X (step S105). For example, when 1 is set in the arrangement order L, Y (1) is set in the numbering target procedure X. In the example of step S103, since Y (1) is "final print instruction T7", final print instruction T7 is set as numbering target procedure X.

  Next, the control unit 11 adds 1 to the procedure number N (Step S106). For example, when 1 is set to the procedure number N, 1 is added to the procedure number N and “2” is set.

  Next, the control unit 11 numbers the procedure number N to the numbering target procedure X (step S107). For example, when the final printing instruction T7 is set in the numbering target procedure X and 2 is set in the procedure number N, 2 is assigned as the procedure number to the final printing instruction T7.

Next, the control unit 11 determines whether or not there is an immediately preceding procedure connected to the numbering target procedure X (step S108). For example, in the example illustrated in FIG. 4, when “final print instruction T7” is set in the numbering target procedure X, “sample check T6” is connected as the immediately preceding procedure, so the immediately preceding procedure is performed. Is determined to exist.
When the control unit 11 determines that the immediately preceding procedure exists (step S108: YES), the process proceeds to the next step S109.
On the other hand, when the control unit 11 determines that the previous procedure does not exist (step S108: NO), the process proceeds to step S110.

  Next, the control unit 11 stores Y (M), M, L, and Np in a stack provided in a RAM or the like (Step S109). After storing the Y (M), M, L, and Np in the stack, the control unit 11 proceeds to step S103, and lists and arranges the immediately preceding procedure connected to the numbering target procedure X again. Instead, they are Y (M). Then, the processing after step S104 is repeated. As a result, in the example shown in FIG. 7, the numbering is performed in the order of sample check T6, sample rise T5, publication T4,.

If it is determined in step S108 that the immediately preceding procedure does not exist, the control unit 11 determines whether the arrangement order L is equal to or greater than M (step S110). That is, it is determined whether all the elements (procedures) arranged in step S103 have been numbered.
When determining that the arrangement order L is equal to or greater than M (step S110: YES), the control unit 11 determines that all the procedures arranged in step S103 have been numbered, and proceeds to the next step S111.
On the other hand, when determining that the arrangement order L is less than M (step S110: NO), the control unit 11 adds 1 to the arrangement order L (step S113), shifts to step S105, and again performs the numbering target procedure. X is set to Y (L). As a result, the procedure having the next position in the array order L is set as the numbering procedure X.

Next, the control unit 11 determines whether or not the stack is empty (Step S111).
When determining that the stack is empty (step S111: YES), the control unit 11 ends the processing.
On the other hand, if the control unit 11 determines that the stack is not empty (step S111: YES), it pulls out Y (M), M, L, and Np from the stack (step S112), shifts to step S108, and attaches again. It is determined whether or not there is an immediately preceding procedure connected to the number-target procedure X. Here, in the present embodiment, a first-in, first-out method is adopted in taking data in and out. That is, in step S112, the data (Y (M), M, L, Np) stored last in step S109 are sequentially extracted.

By performing the processing shown in FIG. 8 as described above, the procedure numbers are assigned to the respective steps constituting the work as shown in FIG.
Further, the user sets the required number of days B7 for each procedure numbered with the procedure number. As a method for setting the required number of days B7, a method for specifying how many days before the completion of the final work procedure it is necessary to complete the work procedure, and a method for specifying the number of days required for completing the work procedure And two methods.
For example, in the example shown in FIG. 7, the print factory arrangement T1, the part-time job arrangement T3 of the flyer distribution, the submission T4, the sample up T5, and the final print instruction T7 complete the work procedure by a certain number of days before the completion of the final work procedure. The required number of days B7 is set by a method of designating whether it is necessary to keep it. On the other hand, the required number of days B7 is set by a method of designating the number of days required for completing the work procedure in the document creation T2 and the sample check T6.
Accordingly, “0” is set in the relative flag B8 of the printing factory arrangement T1, the part-time job arrangement T3 of the flyer distribution, the publication T4, the sample up T5, and the final print instruction T7. On the other hand, “1” is set in the relative flag B8 of the document creation T2 and the sample check T6.

In addition, the user sets the procedure details B5 and the procedure priority B6 for each procedure numbered with the procedure number. The procedure details B5 and the procedure priority B6 are items arbitrarily set by the user who creates the ToDo template data 144. In the present embodiment, when the procedure priority B6 is not set, "3" is set as a default value.
Through the above processing, the ToDo template data 144 (see FIG. 4) is created and stored in the storage unit 14.

  Next, a process of generating ToDo based on the ToDo template data 144 will be described with reference to a flowchart of FIG. This process is started when the user selects a template to be used from the list of the ToDo template data 144 stored in the storage unit 14 and inputs a scheduled completion date of the work related to the selected template. In the present embodiment, a description will be given assuming that April 7 is input as the scheduled completion date of the advertisement flyer distribution T8, which is the final procedure of the flyer distribution work.

  First, the control unit 11 of the server device 1 extracts the procedure record of the template (template number B1) selected by the user, and extracts the first record (step S201). For example, in the example shown in FIG. 4, a record of the procedure name B4 of the procedure number B3 "1" and "flyer distribution" is extracted.

  Next, the control unit 11 sets the scheduled completion date input by the user as the deadline A2 of the first record extracted in step S201 (step S202). In the present embodiment, April 7 is set as the time limit A2 of the first record. The completion date is set as the deadline A2 of the first record here because the first record of the template is the final procedure.

  Next, the control unit 11 sets the display start date A1 of the first record extracted in step S201 (step S203). In the present embodiment, the display start date A1 is set as a default three days before the deadline A2. This is because it is more convenient to notify the user of ToDo several days before the deadline A2. Note that the default value of the display start date offset may be arbitrarily changeable by the user.

Next, the control unit 11 extracts the next record (Step S204).
Next, the control unit 11 sets a time limit A2 of the record extracted in step S204 (step S205). Specifically, when the relative flag B8 is “0”, the control unit 11 uses an expression of “expiration date A2 = input scheduled completion date− (necessary days B7 + correction value B10 + time factor correction value)”, The term A2 is set. The time factor correction value is a correction value obtained by searching the time factor data 146 using the template number B1, the procedure number B3, and the month of the time limit A2 as keys. On the other hand, when the relative flag B8 is “1”, the control unit 11 sets the time limit A2 using the expression “time limit A2 = time limit A2-1 of next procedure number”.

  Next, the control unit 11 sets the display start date A1 of the record extracted in step S204 (step S206). Specifically, when the relative flag B8 is “0”, the control unit 11 uses the expression “display start date A1 = time limit A2−display start date offset (“ 3 ”in the present embodiment)” to display. The start date A1 is set. on the other hand. When the relative flag B8 is “1”, the control unit 11 starts display using the expression “display start date A1 = expiration date A2- (necessary days B7 + correction value B10 + time factor correction value) −display start date offset”. Set the date A1.

Next, the control unit 11 determines whether or not there is a record for which the time limit A2 and the display start date A1 have not been set (step S207).
When determining that there is an unset record (step S207: YES), the control unit 11 proceeds to step S204, extracts the next record, and repeats the processing up to step S206.
On the other hand, when the control unit 11 determines that there is no record that has not been set (step S207: NO), the process proceeds to the next step S208.

Next, the control unit 11 refers to the ToDo template data 144 and transcribes the data of the procedure priority B6, the template number B1, and the procedure number B3 (Step S208).
Next, the control unit 11 sets “1” indicating that the user has not started to the status A6 (step S209).

  Through the above processing, data related to ToDo is generated, and the ToDo data 142 stored in the storage unit 14 is updated (see FIG. 10). That is, the control unit 11 functions as a generation unit of the present invention by generating a ToDo including a time limit of the procedure for each procedure configuring the work. Then, the ToDo data 142 is transmitted to the client terminal 2 and is displayed on the display unit 23 of the client terminal 2 as a ToDo list.

  Next, a process of updating the correction value B10 for correcting the required number of days B7 of the template related to the ToDo when the generated ToDo is completed will be described with reference to a flowchart of FIG. This process is started when a user operation indicating that the generated ToDo is completed is detected.

  First, the control unit 11 of the server device 1 sets “3” indicating completion to the status A6 of the record related to the completed ToDo (step S301). By the processing in step S301, the completed ToDo is deleted from the ToDo list displayed on the display unit 23 or the like of the client terminal 2.

  Next, the control unit 11 causes the display unit 23 of the client terminal 2 to display a screen on which the user can select (input) the completed difficulty level A10 of the completed ToDo and the delay cause number A11 (step S302).

  Next, the control unit 11 acquires the progress difficulty and the delay cause number selected by the user (step S303). The progress difficulty and the delay cause number acquired in step S303 are set to the progress difficulty A10 and the delay cause number A11 of the ToDo data 142, respectively. If the completion date A7 of the ToDo is within the time limit A2, the delay cause number is not selected, and only the progress difficulty level is obtained.

Next, the control unit 11 updates the correction value B10 based on the progress difficulty acquired in step S303 (step S304).
For example, if the progress difficulty selected by the user is “completed with a margin”, the control unit 11 determines that “correction value B10 = correction value B10 (0 if not set) −0.1 × The correction value B10 is updated using the equation of “necessary days B7”. Further, when the progress difficulty selected by the user is “completed as scheduled”, the control unit 11 retains the previous correction value B10 as it is. When the difficulty level of the progress selected by the user is “I tried to complete as scheduled”, the control section 11 calculates the expression “correction value B10 = correction value B10 + 0.1 × number of required days B7”. Is used to update the correction value B10.
That is, the control unit 11 functions as the updating unit of the present invention.

Next, the control unit 11 determines whether the completion date A7 of the completed ToDo is within the time limit A2 (step S305).
When determining that the completion date A7 of the completed ToDo is within the time limit A2 (step S305: YES), the control unit 11 determines that the delay cause number has not been selected by the user, and ends the process.
On the other hand, when the control unit 11 determines that the completion date A7 of the completed ToDo has passed the deadline A2 (step S305: NO), the control unit 11 proceeds to the next step S306.

Next, the control unit 11 updates the correction value B10 based on the delay cause number acquired in Step S303 (Step S306).
For example, when the correction reflection flag C3 of the record indicated by the delay cause number A11 selected by the user is “0”, the control unit 11 determines that the correction based on the delay cause is not performed.
On the other hand, when the correction reflection flag C3 of the record indicated by the delay cause number A11 selected by the user is “1”, the control unit 11 determines that the correction due to the delay cause is performed, and refers to the timing factor flag C4. Then, the correction value B10 is updated.

Specifically, when the time factor flag C4 of the record indicated by the delay cause number A11 selected by the user is “0”, the control unit 11 calculates the expression “correction value B10 = correction value B10 + number of days delayed”. To update the correction value B10.
When the time factor flag C4 of the record indicated by the delay cause number A11 selected by the user is “1”, the control unit 11 performs the execution of the template number D1, the procedure number D2, and the ToDo in the time factor data 146. A record is generated with the month D3 indicating the month as a key, and the number of delay days is set in the correction value D4. If a record using the template number D1, the procedure number D2, and the month D3 as keys already exists, the correction value D4 is updated by using the expression "correction value D4 = correction value D4 + number of days to be delayed". If the correction value B10 relating to the progress difficulty level is set in step S304, the correction value B10 relating to the progress difficulty level and the correction value D4 relating to the timing factor are used to correct the required number of days B7 for ToDo after the next time. Is corrected based on the value obtained by adding.

  By the above processing, when the generated ToDo (work item) is completed, the correction value B10 of the template registered in advance can be updated. Therefore, the correction value B10 is added to the required number of days B7 of the ToDo from the next time. It can be added, and the accuracy of the deadline A2 of the ToDo can be improved.

As described above, according to the server device 1 of the work management system 100 according to the present embodiment, the template data including the plurality of procedures constituting the work, the execution order of the procedures, and the required number of days for each procedure is stored. In addition, based on the scheduled completion date of the work specified by the user and the template data stored in the storage means (storage unit 14), a work item (ToDo) including a deadline of the procedure for each procedure constituting the work is stored. Generate.
Therefore, it is possible to automatically generate a work item (ToDo) related to a procedure for configuring a work by a simple operation of inputting a scheduled completion date of the work. Therefore, efficient work item management can be performed even for a work that requires relatively long-term preparation in a repeated work.

In the present embodiment, the correction value is updated based on information on the correction value input by the user after the completion of the generated ToDo. For example, the correction value is updated based on the difficulty level of the progress of ToDo or the cause of the delay. Then, the required number of days is corrected based on the updated correction value.
Therefore, it is possible to improve the accuracy of the time limit setting when generating ToDo after the next time. Therefore, the ToDo management can be performed more efficiently.

Further, in the present embodiment, it is determined whether or not the delay cause is a timing factor, and when it is determined that the delay factor is a timing factor, the correction value related to the timing factor is updated. Then, when the scheduled completion date of the work is related to the timing factor, the required number of days is corrected based on the updated correction value related to the updated timing factor.
Therefore, even in a case where a delay occurs more than usual due to a season or time, a time limit can be appropriately set. Therefore, the accuracy of ToDo management can be ensured.

  As described above, the present invention has been specifically described based on the embodiment. However, the present invention is not limited to the above embodiment, and can be changed without departing from the gist of the invention.

  For example, in the above-described embodiment, the correction value is updated based on the information (the degree of difficulty of progress, the cause of delay, etc.) regarding the correction value input by the user after the completion of the generated ToDo, but is not limited thereto. It is not something to be done. For example, a configuration in which the correction value is not updated may be adopted. In addition, only the correction value based on the progress difficulty may be updated, or only the correction value based on the delay cause may be updated.

  In the above embodiment, the required number of days is corrected based on the updated correction value. However, the present invention is not limited to this. For example, a configuration is possible in which the user can directly input a correction value, and a configuration in which a method of correcting with the updated correction value and a method of directly inputting the correction value by the user may be arbitrarily selectable.

In the above embodiment, when the progress difficulty A10 input by the user is “completed with a margin”, the equation of “correction value B10 = correction value B10−0.1 × necessary days B7” is used. The correction value B10 is used to update the correction value, but the present invention is not limited to this. For example, when the operation is completed ahead of time, the correction value B10 may be updated using the expression “correction value B10 = correction value B10−number of days moved forward”.
In addition, advance factor data in which “forward factor number”, “forward factor”, “correction reflection flag”, and “time factor flag” are associated with each other is stored in the storage unit 14 in advance, and the user inputs the “forward factor number”. It is good also as a structure to make it. In this case, the correction value is updated based on the input forward factor.
Further, it may be determined whether or not the forward moving factor is a timing factor, and when it is determined that the timing factor is a timing factor, the correction value relating to the timing factor may be updated. In this case, when the scheduled completion date specified by the user is related to the timing factor, the required number of days is corrected based on the set correction value for the timing factor.

  Also, when calculating the deadline, if the deadline falls on a holiday or Sunday, adjust the deadline so that it is always the previous day, and make all adjustments before the procedure according to the adjusted date. May be.

In the above embodiment, the required number of days B7 is set after the procedure number is assigned to each procedure. However, the present invention is not limited to this. That is, the required number of days B7 may be set before assigning the procedure number to each procedure.
Also, the procedure number B5 and the procedure priority B6 may be set before assigning a procedure number to each procedure, similarly to the required number of days B7.

  In addition, the detailed configuration of each device and the detailed operation of each device constituting the server device and the client terminal can be appropriately changed without departing from the spirit of the present invention.

Although some embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and equivalents thereof.
In the following, the inventions described in the claims first attached to the application form of this application are appended. The item numbers of the appended claims are as set forth in the claims originally attached to the application for this application.
[Appendix]
<Claim 1>
Storage means for storing template data including a plurality of procedures constituting the work, an execution order of the procedures and a required number of days for each of the procedures,
Generating means for generating, based on the scheduled completion date of the work specified by the user and the template data stored in the storage means, a work item including a deadline of the procedure for each procedure configuring the work;
Work management device comprising:
<Claim 2>
The template data includes a correction value for correcting the required number of days,
Update means for updating the correction value in the template data based on information on the correction value input by a user after completion of the work item generated by the generation means,
The work management device according to claim 1, wherein the generation unit corrects the required number of days based on the correction value updated by the update unit when the work item is generated next time.
<Claim 3>
The information related to the correction value includes a progress difficulty indicating a difficulty of completing the work item within a deadline,
The work management device according to claim 2, wherein the update unit updates the correction value based on a progress difficulty level of the work item.
<Claim 4>
The information related to the correction value includes a delay cause or an advance factor of the work item,
4. The work management device according to claim 2, wherein the update unit updates the correction value based on a cause of delay or a cause of advance of the work item. 5.
<Claim 5>
The updating means determines whether the delay cause or the advance factor is a time factor, and when it is determined that the time factor is a time factor, updates the correction value related to the time factor,
5. The method according to claim 4, wherein the generation unit corrects the required number of days based on a correction value related to the timing factor updated by the updating unit when the scheduled completion date of the work is related to the timing factor. 6. Work management device.
<Claim 6>
A work management method for a work management apparatus, comprising a storage unit that stores template data including a plurality of procedures constituting a work, an execution order of the procedures, and a required number of days for each of the procedures,
Generating, based on the scheduled completion date of the work specified by the user and the template data stored in the storage unit, a work item including a deadline of the procedure for each procedure configuring the work;
Work management methods including.
<Claim 7>
Computer
Scheduled completion date of the work specified by the user, template data stored in storage means for storing a plurality of procedures constituting the work, the execution order of the procedures and template data including the required number of days for each procedure, Generating means for generating a work item including a time limit of the procedure for each procedure configuring the work, based on
Program to function as

100 work management system 1 server device (work management device)
11 control unit (generation means, update means)
12 operation unit 13 display unit 14 storage unit (storage means)
15 communication unit 2 client terminal 21 control unit 22 operation unit 23 display unit 24 storage unit 25 communication unit

Claims (4)

Display control means for displaying a Todo list;
Storage means for storing template data including a plurality of procedures constituting the work, an execution order of the procedures, and necessary number of days information for each procedure;
Based on the stored template data into the scheduled completion date of the designated the work the storage means by the user, and the work items including the date of the procedure for each procedure constituting the working produces and generates as Todo Generating means for setting a display start date of the generated work item on the Todo list by the display control means for each work item ;
For a work item corresponding to a predetermined procedure among the work items generated by the generation means, when a user inputs completion date / time information or difficulty information of the work item as execution result information, Correction means for correcting the required number of days information corresponding to the predetermined procedure in the template data, so that the execution result information is reflected in the setting by the generation means of the display start date for the next work item;
Work management apparatus characterized by comprising a. The generation unit sets the display start date for each of the work items based on a deadline of the procedure corresponding to the work item,
The work management device according to claim 1, wherein: A method for controlling a display of a Todo list executed by a work management apparatus including a storage unit for storing template data including a plurality of procedures constituting a work, an execution order of the procedures, and necessary days information for each of the procedures,
Generated with a scheduled completion date of the designated the work by the user, based on the stored template data in the storage means, it generates a work item containing the date of the procedure for each procedure constituting the working as Todo A generation step of setting a display start date of the generated work item in the Todo list for each work item performed ;
When the user inputs completion date / time information or difficulty information of the work item as execution result information for a work item corresponding to a predetermined procedure among the work items generated in the generation process, A correction step of correcting the required number of days information corresponding to the predetermined procedure in the template data, so that the execution result information is reflected in the setting of the display start date for the next work item in the generation step.
Display control method, which comprises a. Computer
Display control means for displaying a Todo list,
Scheduled completion date of work specified by the user, template data stored in storage means for storing a plurality of procedures constituting the work, execution order of the procedures, and template data including information on the required number of days for each procedure. , based on the display of work items thus generated to the Todo list by the display control means for each work item generated to generate a work item containing the date of the procedure for each procedure constituting the working as Todo Generation means for setting a start date ,
For a work item corresponding to a predetermined procedure among the work items generated by the generation means, when a user inputs completion date / time information or difficulty information of the work item as execution result information, Correction means for correcting the necessary number of days information corresponding to the predetermined procedure in the template data, so that the execution result information is reflected in the setting by the generation means of the display start date for the next work item;
A program characterized by functioning as a program.

Images