JP5487720B2 - Work management apparatus, program, and work management method - Google Patents

Description

  The present invention relates to a work management apparatus configured to determine whether or not a reminder is required for a work performer who performs work.

  Work management that automatically reminds the work performer by means of e-mail or the like so that the work is surely performed within the preset deadline by the person who should do it (hereinafter referred to as the work performer) The device is known. Non-Patent Document 1 describes a work management apparatus that notifies a work performer when a completion deadline set in association with a work is approaching.

  Further, Patent Document 1 describes a work management device that detects that an operation related to a requested work has not occurred within a certain period on a terminal of a work performer and performs a reminder in response to the detection. Yes. For example, when the content of the requested work is “confirmation of the content of the document by the work performer”, a reminder is performed when the document browsing tool is not activated within a certain time on the work performer's terminal.

  Patent Document 2 discloses a material procurement support system. The system manages the ordering information of materials including the supplier and delivery date, and the standard procurement period required for procurement of the material, and determines when the supplier should be reminded based on the delivery date and standard procurement period of the material. When the determined time has elapsed, a reminder message is automatically transmitted.

  Patent Document 3 discloses a production management system. The system is configured to automatically create an item list that is late or close to the delivery date, and automatically send a reminder message to a supplier of the item selected by the purchaser in the item list.

  Patent Document 4 discloses a system that supports a project approver. The system is configured to automatically prompt the approver by e-mail or the like based on the importance of the item and the approval deadline. Further, Patent Document 4 discloses using an order amount and a customer name as key information for determining the importance of a case.

JP 2008-217491 A JP 2002-279248 A JP 2002-351529 A JP 2006-185011 A

"Help and how to use Microsoft Office 2003 Set and clear work alarm", [online], Microsoft Corporation, [Search February 16, 2009], Internet <URL: http://office.microsoft.com/ ja-jp / outlook / HP052430671041.aspx>

  One of the problems of the technologies disclosed in Non-Patent Literature 1 and Patent Literatures 1 to 4 is that inappropriate reminders such as reminders at unnecessary timing or unnecessary reminders may be performed. It is. The reason for this is that the work completion deadline is only used as an index for determining whether or not a dunning is required, and the dunning is performed unconditionally when the work completion deadline approaches. For example, regarding work A completed in 2 hours, it is assumed that a reminder is given to the work performer 4 hours before the completion deadline with a margin. In this case, if the work time 4 hours until the completion deadline of the work performer is filled with the work B that is more urgent than the work A, the work A is not in time for the completion deadline. An unnecessary reminder notice also arrives when a work performer schedules a work in time for the completion deadline, such as starting a requested work three hours before the completion deadline.

  These problems occur even when the execution of the dunning is determined based on whether or not an operation related to the request work as described in Patent Document 1 occurs. Here, “confirmation of sent document” is considered as an example of the request work. In general, in order to roughly grasp the requested work, the work performer once opens the sent document, but there are many cases where the detailed content itself is confirmed later. That is, even if a related operation occurs, the work performer does not always complete the work at that time. Therefore, if the dunning is determined based on the occurrence of the related operation, the necessary dunning may not be performed. Also, even if there is no related operation occurring 4 hours before the completion deadline, it is unnecessary for work performers who are scheduled to work in time for the completion deadline, such as starting work 3 hours before the same as above Reminders will be made.

  In addition, any of the systems disclosed in Patent Documents 2 to 4 only determines whether or not the dunning is necessary using the work completion deadline as an index. In other words, Patent Documents 2 to 4 do not disclose any consideration of the work schedule or work plan of the work performer when determining whether or not the work performer needs to be prompted.

  An object of the present invention is to provide a work management device that reduces dunning or unnecessary dunning at a timing not in time for a completion deadline and recommends dunning at an appropriate timing for a work performer and a work requester. .

  A first aspect of the present invention is a work management apparatus having a dunning necessity determination unit. The dunning necessity determination means includes work information including a work completion deadline set by a work requester, and work schedule information for ending the work set by the work performer by the completion deadline. Is obtained from the storage means. Furthermore, the dunning necessity determination means determines the necessity of dunning for the performer based on the completion deadline and the work schedule information.

The second aspect of the present invention is a program including a group of instructions for causing a computer to execute information processing related to work management. Here, the information processing provided by the computer executing the program includes the following steps (a) and (b).
Step of obtaining from the storage means work information including a work completion deadline set by a work requester and work schedule information for ending the work set by the work performer by the completion deadline (A); and a step (b) of determining the necessity of prompting the performer based on the completion deadline and the work schedule information.

A third aspect of the present invention is a work management method. The method includes the following steps (a) and (b).
The work information including the work completion deadline set by the work requester and the work schedule information for ending the work set by the work performer by the completion deadline are read from the storage means to the processor. Step (a); and in the processor, a step (b) for determining the necessity of prompting the performer based on the completion deadline and the work schedule information.

  According to each aspect of the present invention described above, it is possible to reduce reminders at unnecessary timing, unnecessary reminders, and the like, and to prompt the work requester at an appropriate timing for the work performer and the work requester. .

It is a block diagram which shows the structure of the 1st Embodiment of this invention. It is a figure which shows an example of the worker information in the 1st Embodiment of this invention. It is a figure which shows an example of the work information in the 1st Embodiment of this invention. It is a figure which shows an example of the request work registration screen in the 1st Embodiment of this invention. It is a figure which shows an example of the request work completion state browsing / reminding execution screen in the 1st Embodiment of this invention. It is a figure which shows an example of the request work list screen in the 1st Embodiment of this invention. It is a figure which shows an example of the worker authentication screen in the 1st Embodiment of this invention. It is a sequence diagram which shows the operation | movement of the request work registration of the 1st Embodiment of this invention. It is a sequence diagram which shows operation | movement of the request work browsing and work schedule input of the 1st Embodiment of this invention. It is a sequence diagram which shows operation | movement of the work completion condition browsing and reminding execution of the 1st Embodiment of this invention. It is a flowchart which shows the operation | movement of calculation of the dunning necessity of the 1st Embodiment of this invention. It is a figure which shows an example of another request work list screen of the 1st Embodiment of this invention. It is a block diagram which shows the structure of the 2nd Embodiment of this invention. It is a figure which shows an example of the work information in the 2nd Embodiment of this invention. It is a figure which shows an example of the request work registration screen in the 2nd Embodiment of this invention. It is a figure which shows an example of the request work completion state browsing and reminding execution screen in the 2nd Embodiment of this invention. It is a flowchart which shows the operation | movement of calculation of the dunning necessity of the 2nd Embodiment of this invention. It is a flowchart which shows the operation | movement of calculation of the dunning necessity of the 2nd Embodiment of this invention. It is a flowchart which shows the operation | movement of calculation of the dunning necessity of the 2nd Embodiment of this invention. It is a block diagram which shows the structure of the 3rd Embodiment of this invention.

  Hereinafter, specific embodiments to which the present invention is applied will be described in detail with reference to the drawings. In the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted as necessary for the sake of clarity.

<First Embodiment>
Referring to FIG. 1, the work management system according to the first exemplary embodiment of the present invention includes at least one terminal 1 and a work management apparatus 3a. The terminal 1 and the work management device 3a are connected by a communication network 2.

  The terminal 1 includes an input / output unit 11 and a reminder transmission / reception unit 12. Two or more terminals 1 may be arranged. In this case, at least one terminal may be used as a terminal used by the work requester, and another terminal may be used as a terminal used by the work performer. The work requester and the work performer may share one terminal 1. As a typical terminal 1, a desktop personal computer, a notebook personal computer, a mobile tool, an STB (Set-Top BOX), a mobile phone, a PHS, a PDA (Personal Digital Assistant), or the like is used. be able to.

  The input / output unit 11 includes an input function that receives an input from an operator (work requester or work performer) by an input device and an output function that supplies a display signal for displaying information on the display device. Here, the input device is, for example, a mouse, a keyboard, a touch panel, or the like. The output device is, for example, a liquid crystal display, a CRT (Cathode Ray Tube) display, or the like.

  The dunning transmission / reception unit 12 arranged in the terminal 1 used by the work requester, in response to receiving a dunning execution instruction from the work requester, sets a destination (e-mail address or the like) accessible to the work performer. Send a reminder notice to it. Further, the dunning transmission / reception unit 12 arranged in the terminal 1 used by the work performer receives the dunning notice generated in response to the work requester's instruction via the network 2. An arbitrary communication unit can be used for the reminder transmission / reception unit 12. As typical examples, a soft phone, a mobile phone, an e-mail, or the like that enables a voice call on a telephone or a personal computer can be used.

  As the communication network 2, an arbitrary public network, a dedicated network, or a combination thereof can be used.

  The work management device 3a includes a control unit 31a and a storage unit 32a. The control unit 31a performs control processing related to requested work, work schedule, and dunning. The storage unit 32a stores information on requested work / work schedule.

  In the example of FIG. 1, the storage unit 32a includes a worker information storage unit 321 and a work information storage unit 322a. Among these, the worker information storage unit 321 includes worker information that can identify the worker requester and the worker. In the following, the term “worker” is used to collectively refer to the worker requester and the work performer. For example, the worker information includes a worker ID and a worker's first and last name. The worker information may include a password, a telephone number, a mobile phone number, an e-mail address, and the like. An example of worker information is shown in FIG. The telephone number, the mobile phone number, and the e-mail address are used as the destination information of the reminder notification.

  The work information storage unit 322a stores information on the requested work and the work schedule (hereinafter, work information). The work information includes a work ID, a work name, a work requester ID, a work performer ID, a completion deadline, a work schedule, and a completion date. An example of assigned work information is shown in FIG.

  The control unit 31a includes a requested work management unit 311a, a work schedule management unit 312, a reminder necessity determination unit 313a, and a worker authentication unit 314.

  The requested work management unit 311a operates in cooperation with the terminal 1 to allow the work requester to register the requested work, view the completed state regarding the requested work, and execute a reminder. Regarding the registration of the requested work, for example, a requested work registration screen as shown in FIG. 4 may be displayed on the input / output unit 11 of the terminal 1 operated by the work requester. The terminal 1 accepts an input operation by the work requester who has browsed the requested work registration screen in FIG. 4, and transmits work information including the work name, the work performer who requests the work, and the completion deadline to the requested work management unit 311a. The requested work management unit 311a records the work information received from the terminal 1 in the work information storage unit 322a.

Regarding the viewing of the completion status of the requested work and the execution of the reminder, the requested work management unit 311a refers to the work information stored in the work information storage unit 322a and displays a list of requested work registered by the work requester. It transmits to the terminal 1 and outputs it. FIG. 5 is a diagram showing an example of a requested work completion state browsing / reminding execution screen displayed on the input / output unit 11 of the terminal 1 operated by the work requester. The work requester can confirm the work with a high necessity of dunning by browsing the requested work completion state browsing / reminding execution screen, and can send dunning to the work performer. Specifically, in the screen example of FIG. 5, the following (a) to (d) are displayed.
(a) Work name, completion deadline, work performer registered by work requester for each work;
(b) Completion status of the requested work registered by the person performing the work ("Completed" if completed, scheduled work if not completed);
(c) Dunning necessity determined by the dunning necessity judging unit 313a (501 in FIG. 5); and
(d) A dunning execution button for executing dunning (502 in FIG. 5).

  In the terminal 1, the dunning transmission / reception unit 314 is called in response to the input / output unit 11 receiving a dunning execution instruction input (pressing the dunning execution button 502) by the work requester. The dunning transmission / reception unit 314 transmits a dunning notice to the work performer of the corresponding work. In addition, as shown in the example of FIG. 5, the reminder execution button may be devised on display such that the higher the need for reminder is, the larger the button is displayed and the more noticeable it is.

  The work schedule management unit 312 generates display information for outputting the work list display screen requested to the work performer to the input / output unit 11 of the terminal 1, and transmits this to the terminal 1. In addition, the work schedule management unit 312 receives date information regarding “work schedule” and “work completion” received by the terminal 1.

  FIG. 6 shows an example of a requested work list screen displayed on the terminal 1 of the work performer. In the screen example of FIG. 6, the work requested by the work performer is divided for each scheduled work day (“Today's work”, “Tomorrow's work”, “Undecided work”, etc., 601 in FIG. 6). Is displayed. The work for which the work schedule has not been entered is displayed in the “undecided work” section. Therefore, the requested work registered by the work requester is first displayed in the “Undecided work” section. For example, as shown by an arrow 603 in FIG. 6, the work item included in the “undecided work” place is moved to the “today work” or “tomorrow work” place by a drag-and-drop operation. An input of the scheduled work date may be accepted. When the work is moved from “undecided work” to “today's schedule” or “tomorrow's schedule”, the work schedule management unit 312 updates the work schedule of the corresponding work information in the work information storage unit 322a. For example, if the current date is 2009/01/15, when moving to “Today's schedule”, 2009/01/15 will be set, and when moving to “Tomorrow's schedule”, 2009/01/16 will be set as the schedule. Record it. The work schedule may be moved not only from “undecided schedule” to “today's schedule” or “tomorrow's schedule”, but also freely movable between each. Further, an input of the completion date of the requested work may be received by an operation of checking a check box 602 displayed at the top of the work.

  The dunning necessity determination unit 313a determines whether or not it is necessary to dunn the work performer regarding the requested work or the degree of necessity based on the work completion deadline and the work schedule input by the work performer. More specifically, the dunning necessity determination unit 313a first calculates a numerical value indicating the necessity of dunning regarding the requested work (hereinafter referred to as a dunning necessity level), and needs dunning according to the size of the dunning degree. The sex is determined at a stage such as “high”, “medium”, “low”, “none”, etc. (hereinafter, this stage is referred to as a dunning necessity).

  The details of the method for calculating the demand level will be described in the operation of the present embodiment described below. Here, the basic rules in the calculation method will be described. First, there is no need for dunning for work for which a completion date has been entered, that is, work that has already been completed. Therefore, the dunning necessity determination unit 313a determines that the dunning necessity is “none” for the work for which the completion date is input. Next, with respect to the work whose work schedule is input on a date before the completion deadline, it is considered that the work performer has made a work schedule in time for the completion deadline. For this reason, the dunning necessity determination unit 313a determines that the dunning necessity is low for the work whose work schedule is input on a date before the completion deadline. Finally, work for which no work schedule has been input is considered not incorporated in the work performer's schedule. For this reason, the dunning necessity determination unit 313a gradually increases the dunning necessity for the work for which the work schedule is not input as the completion deadline approaches.

  The worker authentication unit 314 performs worker authentication in order to identify a worker who has issued a request from the terminal 1. Before making a request from the terminal 1 to the requested work management unit 311a and the work schedule management unit 312, the worker enters his / her worker ID and password on the worker authentication screen displayed on the terminal 1 by the worker authentication unit 314. input. FIG. 7 shows an example of a worker authentication screen displayed on the terminal 1. The worker authentication unit 314 searches the worker information storage unit 321 in the worker information storage unit 321 based on the worker information corresponding to the input worker ID and password, and identifies the corresponding worker information. If the corresponding worker information exists, this worker ID is stored, and thereafter, it is determined that the request from the corresponding terminal 1 is from the worker assigned the stored worker ID. May be. When the corresponding worker information does not exist in the worker information storage unit 321, the worker authentication screen may be displayed to prompt the worker ID and password to be input again.

  Next, the operation of the present embodiment will be described in detail with reference to FIGS. The work management device 3a typically (1) accepts a registration operation of a requested work performed by a work requester, (2) accepts an input operation of a work schedule related to a requested work performed by a work performer, and (3) It is used in the order of determining work with high necessity of dunning and executing dunning for work with high necessity of dunning based on the instruction of the work requester. These three operations will be described in detail according to this order. Before the operation described below, worker authentication by the worker authentication unit 314 has already been completed, and a worker who makes a request to the requested work management unit 311a and the work schedule management unit 312 from the terminal 1 ( It is assumed that the worker ID) is specified.

  First, a specific example of the registration operation of the requested work will be described with reference to the sequence diagram of FIG. First, in step A1, the input / output unit 11 of the terminal 1 displays a requested work registration screen (example of FIG. 4) and requested work information (for example, a work name of the requested work, a work performer requesting the work, Accepts the input by the requesting worker. The inputted requested work information is transmitted from the terminal 1 to the work management apparatus 3a (step A2). In steps A3 and A4, the requested work management unit 311a receives the requested work information and records it in the work information storage unit 322a.

  Next, with reference to the sequence diagram of FIG. 9, a specific example of an operation for receiving an input of a work schedule and a work completion for the requested work will be described. First, the terminal 1 issues a request to display a requested work list screen (for example, FIG. 5) to the work schedule management unit 312 according to the operation of the input / output unit 11 by the work performer (step B1). In step B2, the work schedule management unit 312 extracts work information in which the worker ID specified in the display request is set as the work performer ID from the work information storage unit 322a. In step B <b> 3, the work schedule management unit 312 transmits a requested work list including the extracted work information to the terminal 1. In step B4, the terminal 1 displays a requested work list screen. The requested work list screen may be displayed as shown in FIG. 6, for example.

  In step B5, the terminal 1 accepts an input of a work schedule according to the operation of the input / output unit 11 by the work performer. For example, as described with reference to FIG. 6, the work schedule input may be received by a drag and drop operation on the requested work list screen. The input work schedule information is transmitted from the terminal 1 to the work management apparatus 3a (step B6). In step B7, the work schedule management unit 312 updates the work schedule record of the corresponding work information in the work information storage unit 322a with the received work schedule information.

  In step B <b> 8, the terminal 1 accepts an input of work completion according to the operation of the input / output unit 11 by the work performer. For example, as described with reference to FIG. 6, the operation completion input may be received by a check operation on the check box 602. The input work completion information is transmitted from the terminal 1 to the work management apparatus 3a (step B9). In step B10, the work schedule management unit 312 updates the work completion record of the corresponding work information in the work information storage unit 322a with the received work completion information.

  Next, with reference to the sequence diagram of FIG. 10, a specific example of the operation from the determination of the necessity of the dunning regarding the execution of the requested work to the dunning will be described. First, in response to an operation of the input / output unit 11 by a work requester, the terminal 1 issues a request to display a requested work completion state browsing / reminding execution screen (example in FIG. 5) to the requested work management unit 311a (step C1). . Upon receiving the display request, the requested work management unit 311a extracts from the work information storage unit 322a the work information in which the worker ID of the requesting work requester is set as the work requester ID. Then, the requested work management unit 311a passes a list of work IDs regarding the extracted work information to the reminder necessity determination unit 313a.

  In step C2, the dunning necessity determination unit 313a calculates the dunning necessity for each work requested by the requesting work requester. Details of the operation for calculating the necessity for dunning will be described later.

  In Step C3, the dunning necessity determination unit 313a receives the dunning necessity calculated by the dunning necessity determination unit 313a and receives information including the dunning necessity necessary for displaying the requested work completion state browsing / reminding execution screen. Transmit to terminal 1.

  In step C4, the terminal 1 displays a requested work completion state browsing / reminding execution screen. For example, this screen may be displayed as shown in FIG. In step C5, the terminal 1 accepts an input for dunning execution in response to an operation of the input / output unit 11 by the work requester. For example, as shown in FIG. 5, the input of the dunning execution may be such that a pressing operation of the dunning execution button 502 by the work requester who has viewed the dunning necessity 501 is accepted. In response to the input reception of the dunning execution, the terminal 1 transmits a dunning execution command to the requested work management unit 311a.

  In step C <b> 7, the requested work management unit 311 a refers to the worker information in the worker information storage unit 321, and acquires information on a reminder notification destination regarding the work performer of the corresponding work. Then, the requested work management unit 311a passes the dunning notification destination information to the dunning transmission / reception unit 12 of the work requester's terminal 1, and activates the dunning transmission / reception unit 12 (steps C8 and C9). What is given as the information of the dunning notification destination and the operation when the dunning transmission / reception unit 12 is activated differ depending on the type of the dunning transmission / reception unit 12. Here, a case where the reminder transmission / reception unit 12 is a soft phone will be described as an example. In the case of a softphone, the telephone number of the work performer is passed to the execution process of the softphone activated on the work requester's terminal 1 as information of the reminder notification destination, and the softphone on the work performer's terminal 1 is passed to the execution process You can make a call.

  Next, a specific example of the operation (step C2 in FIG. 10) in which the dunning necessity determination unit 313a calculates the dunning necessity will be described with reference to the flowchart in FIG. The value of the dunning necessity used in the description is an example, and other values can be used as appropriate. First, the dunning necessity determination unit 313a refers to the work information storage unit 322a and acquires the completion deadline, the work schedule, and the completion date of the work A, which is a dunning necessity calculation target (step D1). Next, the determination unit 313a determines whether or not a completion date has been input. If the completion date has been input, the determination necessity degree is set to 0 (steps D2 and D3). When the completion date of work A has not been input, the determination unit 313a determines whether a work schedule has been input for work A (step D4). When the work schedule is input on a date that is in time for the completion deadline, it can be determined that the work performer has made a work schedule in time for the completion deadline. For this reason, the determination part 313a sets the degree of necessity for dunning to 10 (steps D5 and D6). Note that, here, the larger the numerical value of the dunning necessity level, the higher the necessity for dunning.

  When the work schedule is not set, or when the work schedule is input with a date ahead of the completion deadline (future), the determination unit 313a calculates the dunning necessity degree according to the proximity of the completion deadline of the work A To do. Specifically, the degree of necessity for dunning may be calculated higher as the completion deadline is approached (step D7). As shown in FIG. 11, for example, when the completion deadline is the same as the current date (today), the reminder necessity level is 100, and when the completion deadline is the day after the current date (tomorrow), the reminder necessity level is 50. When the completion deadline is ahead of tomorrow, 20 is set as the degree of necessity for reminder.

  Finally, the dunning necessity determination unit 313a determines the dunning necessity based on the dunning necessity value. The dunning necessity may be an index having a coarser granularity (lower resolution) than the dunning necessity. Here, the necessity for dunning is an index of four levels (none, low, medium, high) for the degree of dunning necessary represented by an integer value of 0 to 100. For example, if the necessity level for dunning = 0, “None” is required for dunning requirement, “low” is required for dunning requirement if 0 <requiring necessity ≦ 30, and dunning is required if 30 <requiring necessity ≦ 80 In the case of “middle” in the sex, and 80 <requirement for necessity, it is determined that “high” in the necessity for reminder (step D8). By applying clear indicators in this way, it becomes possible for the work requester to easily determine whether or not to perform a dunning, and it is possible to prevent a determination error from occurring when the work requester decides the final dunning execution. Can be suppressed.

  In the flowchart of FIG. 11, the necessity level of fineness (high resolution) is calculated as compared with the necessity level identified in four stages, and then the necessity level is determined based on the value of the necessity level. A two-step procedure is shown. However, the necessity for dunning may be determined directly based on the comparison result of the current date, completion deadline, completion date, and work schedule. For example, in steps D3 and D6 in FIG. 11, it may be determined that the necessity for urgency = “low”. Further, in step D7, the urgency necessity may be set to “high”, “medium” or “low” according to the comparison result between the current date and the completion deadline.

  In the present embodiment, it is assumed that the work requester uses another means such as oral, telephone, and e-mail in order to transmit the detailed contents of the requested work to the work performer. However, on the requested work registration screen displayed by the requested work management unit 311a, the work requester can enter the details of the requested work and the files related to the requested work, such as allowing the work requester to enter details of the requested work. You may manage by the management apparatus 3a.

  In this embodiment, the work schedule is input in rough units such as “today” and “tomorrow” for the purpose of saving labor for the work performer to input the work schedule. However, using a calendar-like input screen as shown in FIG. 12, the work performer may be allowed to input the start time and end time of the work schedule in detail like a schedule.

  Next, the effect of this embodiment will be described. In the present embodiment, the dunning necessity determination unit 313a determines the necessity of dunning based on the work schedule of the requested work input by the work performer in the work schedule management unit 312, so that the work is performed when the dunning is received. The number of cases where the schedule is filled and the deadline for completion is not met, and the case where an unnecessary reminder arrives even if the work is scheduled to meet the deadline for completion is reduced. A dunning is possible.

  By the way, the processing performed by each of the units 311a, 312, 313a, and 314 included in the control unit 31a can be realized by causing a computer system to execute a program including instruction codes related to these processings. Specifically, a program including an instruction code related to the processing procedure described with reference to FIGS. 8, 9, 10 and 11 is prepared, and the program is an instruction such as an MPU (Micro Processing Unit) or a CPU (Central Processing Unit). The computer system including the execution unit may be executed. This program can be stored in various types of storage media, and can be transmitted via a communication medium. Here, the storage medium includes, for example, a flexible disk, a hard disk, a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD, a ROM cartridge, a RAM memory cartridge with battery backup, a nonvolatile RAM, a flash memory, and the like. In addition, the communication medium includes a wired communication medium such as a telephone line, a wireless communication medium such as a microwave line, and the Internet.

<Second Embodiment>
Next, a second embodiment of the present invention will be described in detail with reference to the drawings. FIG. 13 is a block diagram showing a configuration of the work management apparatus 3b according to the present embodiment. Referring to FIG. 13, the difference between the present embodiment and the first embodiment is that the control unit 31b of the work management device 3b has a work load calculation unit 315, and information stored in the work information storage unit 322b. Are added, and the operations of the requested work management unit 311b and the reminder necessity determination unit 313b are partially changed so as to cooperate with the added unit 315 and the added information.

  The work information of this embodiment recorded in the work information storage unit 322b includes a desired deadline in addition to the completion deadline, work schedule, and completion date. In general, the work requester sets the completion deadline at a date and time that has some allowance in consideration of the circumstances of the person performing the work, or sets the completion date and time as the limit date and time that would interfere with the next work if exceeded. Or often. However, if the work is completed before the completion deadline, it is often convenient for the work requester such that the subsequent work can be started earlier. Therefore, in the present embodiment, an input of a desired deadline desired by a work requester who does not consider the convenience of the work performer is accepted. That is, a time (month, day, time, etc.) that is the same as or earlier than the completion deadline is designated as the desired deadline for each work. FIG. 14 shows a specific example of work information recorded in the work information storage unit 322b. Referring to FIG. 14, a desired due date 1401 is added to the work information of the first embodiment shown in FIG.

  The requested work management unit 311b operates in cooperation with the terminal 1 to display on the terminal 1 a requested work registration screen that prompts the work requester to input a desired deadline. For example, a request work registration screen including an input form 1501 for a desired deadline as shown in FIG. The requested work management unit 311b receives the desired deadline input by the work requester together with other work information such as the work name from the terminal 1, and records this in the work information storage unit 322b. In addition, the requested work management unit 311b causes the terminal 1 to display a requested work completion state browsing / reminding execution screen including the desired deadline referred to from the work information storage unit 322b by operating in cooperation with the terminal 1. For example, as shown in FIG. 16, a request work completion state browsing / reminding execution screen including a display of the desired deadline 1601 may be displayed on the terminal 1.

  The dunning necessity determination unit 313b, in calculating the dunning necessity, in addition to the work completion deadline and work schedule used in the work information of the first embodiment, the desired deadline and work load calculation unit input by the work requester The work load of the work performer calculated by 315 is used. The details of the method for calculating the demand level in this embodiment will be described in the operation of this embodiment described below. Here, the basic rules of the calculation method will be described. First, when the work load of the work performer is very high, the dunning necessity is calculated low. This is because, when the work load is very high, the work time of the work performer is filled with other high-priority work, and there is a high possibility that the work cannot be started even if a reminder is performed. If a reminder is given in such a case, the work being performed by the work performer may be interrupted, and the completion of the work may be delayed. Further, when the work load of the work performer is low, even if the completion deadline is not approaching, the necessity for urging the work whose desired deadline is approaching or exceeding is calculated. Thereby, when the work performer is not busy, it is possible to recommend a reminder of work that the work requester wants to complete ahead of schedule.

The work load calculation unit 315 calculates the work load of the work performer, that is, the busyness of the work performer. The calculation of the work load of the work performer can be realized by various methods. Here, a method of calculating from the rate at which the work requested by the work performer is completed within the completion deadline will be described as an example. In this method, the higher the completion rate of the requested work, the lower the work load on the work performer. The work load calculation unit 315 refers to the work information storage unit 322b, and regarding the work information of the work performer for which the work load is to be calculated, the number of work whose completion date is the current date (today) (hereinafter, the number of completed work) The number of tasks whose completion deadline is today or earlier and whose completion date has not been entered (hereinafter, the number of unfinished tasks) is acquired. The work completion rate is calculated by the following equation (1).
Work completion rate = number of completed work / (number of completed work + number of incomplete work) (1)

If the work load is simply calculated from the work completion rate, the work load at the start time is calculated to be high when the work start time (morning) and the work end time (night) of the work performer are compared. This is because the number of completed tasks is zero at the start of work, and generally the number of completed tasks increases with the passage of time. Therefore, in order to eliminate the influence due to the passage of time, first, the working hour elapsed rate is calculated by the following equation (2) using the working hours of the worker performing the day and the elapsed time from the working start time.
Elapsed working rate = Elapsed time from working start time / working hours per day (2)

  Here, in order to calculate the working time of the work performer and the elapsed time from the work start time, the work start time and the work end time of the work performer are required. When these times are the same for all work performers, the work load calculation unit 315 may hold a given value. Further, when different for each worker, the worker start time and the work end time for each worker may be included in the worker information recorded in the worker information storage unit 321.

Then, by subtracting the work completion rate from the work time elapsed rate as in the following equation (3), the work load excluding the influence of the time elapsed is calculated.
Work load = working hour elapsed rate-work completion rate (3)
The workload calculated by Equation (3) is a standard workload when 0, 1 is the highest (busy), and -1 is the lowest (with a margin). Become. Here, as an example, the work load of the work performer is calculated from the completion rate of the requested work. However, as another method, the method of manually inputting the work load by the work performer and the schedule of the work performer are available. For example, a method of calculating the work load higher as the time is shorter, a method of calculating the work load higher as the number of times the other work requesters are urged to the corresponding work performer, and the like may be used.

  Next, the operation of the present embodiment will be described in detail with reference to a series of flowcharts shown in FIGS. In the operation of the present embodiment, the operation for receiving an input of a work schedule by a work performer is the same as the operation of the first embodiment. The operation of accepting the registration of the requested work by the work requester is the same as the operation of the first embodiment except that the desired deadline is added to the information input by the work requester on the requested work registration screen. is there. Therefore, detailed description of these two operations is omitted.

  Hereinafter, a series of operations for determining the necessity for dunning, providing the determination result to the work requester, and executing dunning based on a dunning execution instruction by the work requester will be described. This series of operations is also different from the operation of the first embodiment shown in FIG. 10 only in the operation (step C2) in which the dunning necessity determination unit 313b calculates the dunning necessity. For this reason, with reference to FIG. 17, the calculation operation | movement of the dunning necessity in this Embodiment is demonstrated in detail. First, the dunning necessity determination unit 313b refers to the work information storage unit 322b and acquires the work performer ID, completion deadline, desired deadline, work schedule, and completion date of the work A for calculating the dunning necessity (Step E1). ).

  Next, the reminder necessity determination unit 313 b passes the work performer ID for which the business load is to be calculated to the business load calculation unit 315. The work load calculation unit 315 refers to the work information storage unit 322b, obtains the number of completed tasks and the number of uncompleted tasks for the corresponding task performer, and calculates the task completion rate using the above-described equation (1) (step E2). ). Subsequently, the working time elapsed rate is calculated from the elapsed time from the working start time to the current time and the working time of one day by the above-described formula (2) (step E3). Then, the business load is calculated by the above-described equation (3), and passed to the reminder necessity determination unit 313b (step E4).

  From step E5, which calculates the necessity level of dunning from the input state of the completion date, to step E9, which calculates the necessity level of the work for which the work schedule is set, from the first implementation shown in FIG. Since it is the same as step D2 to step D6 of the operation of the embodiment, description thereof is omitted.

  The description will be continued from the operation of calculating the dunning necessity of the work for which the work schedule is not set. First, it is determined whether the work completion deadline is the day before the current date (tomorrow), and if the condition is satisfied, if the completion deadline is before today, 100 is required for the reminder, and if the completion deadline is tomorrow, the reminder 50 is set as the necessity (steps E10 and E11).

  Next, when the work completion deadline is a date earlier than tomorrow, it is determined whether the work load value of the work performer is a certain value (for example, −0.5) or more (step E12), and the condition is determined. If it satisfies, the demand level for dunning is set to 10 (step E13). If the workload value is smaller than a certain value, that is, if there is room for the worker, determine whether the desired deadline for the work is a date before tomorrow, if the condition is met, if the completion deadline is before today Sets 70 as the necessity level for dunning and 40 as the necessity level for dunning if the completion deadline is tomorrow (steps E14 and E15).

After calculation of the dunning requirement is completed, it is determined whether the work load value of the work performer is a certain value (for example, 1.5) or more. Decrease the value (steps E16, E17). For example, it calculates like following Formula (4).
Necessity of dunning = original necessity of dunning / (work load−0.5) (4)

  Finally, the calculated dunning necessity is converted into dunning necessity by the same operation as Step D8 of the operation of the first embodiment shown in FIG. 10 (Step E18).

  Next, the effect of the second embodiment will be described. In the present embodiment, the dunning necessity determination unit 313b calculates the dunning necessity low when the work performer's work load is high based on the work load of the work performer calculated by the work load calculation unit 315. When the work load of the work performer is low, even if the completion deadline is not approaching, the necessity for urging the work whose work requester's desired deadline is approaching is calculated high. By calculating the necessity of dunning in consideration of the work load of such work performers, it is possible to reduce cases where work is interrupted due to reminders to work performers with high work loads, and conversely delays completion. You can urge low-level performers to work ahead of time.

  By the way, the processing performed by each of the units 311b, 312, 313b, 314, and 315 included in the control unit 31b can be realized by causing a computer system to execute a program including instruction codes related to these processings. Specifically, a program including instruction codes related to the processing procedure described with reference to FIGS. 8, 9, 10 and 17 to 19 is prepared, and the program is stored in an MPU (Micro Processing Unit), a CPU (Central Processing Unit), or the like. The computer system including the instruction execution unit may be executed.

<Third Embodiment>
In the first and second embodiments described above, (a) authentication of workers (work requesters and work performers); (b) reception of work information and work schedule information from the terminal 1; (c) storage It has been described that the work management devices 3a and 3b perform storage of work information and work schedule information in the unit 32; (d) transmission of a determination result of necessity of reminder to the terminal 1, and the like. However, the work management apparatuses 3a and 3b may be configured to determine the necessity of reminding and calculate the work load, and to cause the external computer to perform the above processes (a) to (d). Further, the storage unit 32b need not be directly connected to the work management devices 3a and 3b. Specifically, the storage unit 32b does not have to be a storage device (such as a built-in HDD) built in a computer that functions as the work management apparatuses 3a and 3b, and can be accessed from the work management apparatuses 3a and 3b. You may arrange | position via a network.

  A configuration example of the work management apparatus 3c according to the present embodiment is shown in FIG. The control unit 31c included in the work management device 3c reads out work information and a work schedule from the work information storage unit 32b arranged outside via the network 4, and determines the necessity for urgency. The determination result of the necessity for reminding is stored in the determination result storage unit 5. Note that the determination process of the necessity for reminding by the control unit 31c may be the same as that described in the first embodiment. In addition, the control unit 31c may perform the business load calculation process described in the second embodiment.

  Also with the work management apparatus 3c according to the present embodiment, the necessity for urgency can be determined based on the work schedule of the requested work input by the work performer, similarly to the above-described work management apparatuses 3a and 3b. This reduces the number of cases where work schedules are filled at the time of receiving a reminder and the deadline for completion is not met, and cases where unnecessary reminders arrive even if the work schedule is scheduled to meet the deadline for completion. It is possible to request the work requester at an appropriate timing.

<Other embodiments>
In the first to third embodiments described above, an example is described in which the necessity of urging for each work is determined in stages, and urging is performed based on the instructions of the work requester who has browsed the determination results. did. However, the work management apparatuses 3a, 3b, and 3c described in the first to third embodiments may be configured to automatically transmit a dunning based on a dunning necessity determination result. Specifically, a threshold is set for the magnitude of the dunning necessity determined according to the input status of the work schedule by the work performer, and the performer of the work given the necessity to exceed the threshold is specified, A dunning message may be transmitted to a transmission destination accessible by the performer.

  Further, in the second embodiment described above, the example in which the necessity for dunning is determined in consideration of the work load of the worker and the desired deadline has been described. However, the necessity for reminding may be determined in consideration of the work load of the work performer without using the desired deadline. Specifically, when the remaining period until the completion deadline is the same, it may be determined that the necessity of the reminder becomes relatively lower as the load on the performer becomes higher. As a result, it is possible to identify a work performer who has a low load and is likely to be able to start work early regardless of the completion deadline, and can efficiently prompt the work performer.

  Further, in the first to third embodiments described above, the configuration in which the terminal 1 on which the operator operates is provided separately from the work management devices 3a, 3b, and 3c. However, the work management devices 3a, 3b, and 3c and the terminal 1 may be realized by a single personal computer or the like.

  Furthermore, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the gist of the present invention described above.

DESCRIPTION OF SYMBOLS 1 Terminal 11 Input / output part 12 Dunning transmission / reception part 2 Communication network 3a, 3b, 3c Work management apparatus 4 Communication network 5 Dunning necessity determination result storage part 31a, 31b Control part 311a, 311b Request work management part 312 Work schedule management part 313a 313b Dunning necessity determination unit 314 Worker authentication unit 315 Work load calculation unit 32a, 32b storage unit 321 Worker information storage unit 322a, 322b Work information storage unit

Claims (23)

Obtaining from the storage means work information including a work completion deadline set by the work requester and work schedule information for ending the work set by the work performer by the completion deadline. Urgency necessity determination means for determining the necessity of urgency for the performer based on the completion deadline and the work schedule information ;
Load calculating means for calculating the load of the executor based on a completion rate by which the executor has completed the requested work so far;
With
The dunning necessity determination means determines the necessity for dunning based on the completion deadline, the work schedule information, and the load.
Work management device. The said dunning necessity determination means makes the necessity of the dunning relatively low when the said work schedule information is set compared with the case where the said work schedule information is not set. Work management device. The dunning necessity determination means has a higher necessity for dunning as the completion deadline approaches, and the work schedule information is set when the work schedule information is set as compared to the case where the work schedule information is not set. The work management apparatus according to claim 1, wherein the necessity for the dunning is determined so that the necessity for the dunning is reduced.   The dunning necessity determination means determines that the dunning need is low if the work schedule information is set even if the completion deadline approaches, and the work schedule information even if the completion deadline is not approaching. The work management apparatus according to claim 1, wherein if it is not set, the necessity of the reminder is determined to be high. The said dunning necessity determination means determines that the necessity for dunning becomes relatively low as the load on the performer increases when the remaining period until the completion deadline is the same . 5. The work management apparatus according to any one of 4 above. Obtaining from the storage means work information including a work completion deadline set by the work requester and work schedule information for ending the work set by the work performer by the completion deadline. Urgency necessity determination means for determining the necessity of urgency for the performer based on the completion deadline and the work schedule information;
Load calculating means for calculating the load of the performer;
With
The work information further includes a desired deadline set equal to or before the completion deadline,
The dunning necessity determination means determines the necessity for dunning based on the completion deadline, the work schedule information, the load, and the desired deadline.
Work management device . The dunning necessity determination means determines that the necessity of dunning is low when the load on the performer is high, and when the load on the performer is low, the desired deadline is set even if the completion deadline is not approaching. The work management apparatus according to claim 6 , wherein the necessity of the reminder is determined to be high when approaching. The work management apparatus according to claim 6 , wherein the load calculating unit calculates the load of the executor based on a completion rate at which the executor has completed the requested work so far. The load calculating means determines the load of the executor according to a value obtained by subtracting the completion rate from the execution time lapse rate of the executor . The work management device according to any one of the above. The work management according to any one of claims 1 to 9 , wherein the load calculation unit calculates the load higher as the setting state of the work schedule of the performer is overcrowded based on the work schedule information. apparatus. The work management device according to any one of claims 1 to 9 , wherein the load calculating unit refers to an execution state of the reminder for the performer, and calculates the load higher as the number of reminders to the performer increases. . Work schedule management means for receiving input of the work schedule information by the performer for a plurality of the work,
The work schedule management means includes
A first area for displaying an image relating to a first work for which the scheduled work date is not set among the plurality of works, and an image relating to the second work for which the scheduled work date is set are classified for each scheduled work date. Outputting a display screen including a second region to be displayed to the display device;
Accepting an input of a scheduled work date for the first work by dragging and dropping an image from the first area to the second area;
The work management apparatus according to any one of claims 1 to 11 . A program including a group of instructions for causing a computer to execute information processing related to work management,
The information processing
Step of obtaining from the storage means work information including a work completion deadline set by a work requester and work schedule information for ending the work set by the work performer by the completion deadline (A),
A step (b) of calculating the load of the performer based on a completion rate at which the performer has completed the requested work so far, and the performer based on the completion deadline , the work schedule information , and the load Determining the need for a reminder to ( c ),
Including the program. In the step (c), when the work schedule information is set, relatively reducing the need for the dunning compared with the case where the work schedule information has not been set, according to claim 13 program. In the step ( c ), the necessity of the reminder becomes higher as the completion deadline approaches, and when the work schedule information is set, the work schedule information is not set compared to the case where the work schedule information is not set. The program according to claim 13 or 14 , wherein the necessity for the dunning is determined so that the necessity for the dunning is reduced. In the step ( c ), if the work schedule information is set even if the completion deadline is approaching, the necessity of the reminder is determined to be low, and even if the completion deadline is not approaching, the work schedule information is The program according to claim 13 or 14 , wherein if it is not set, the necessity for the dunning is judged high. In the step (c), determining the if is the residue period until completion deadline is the same, so that the need for the dunning as the executor of the load increases is relatively low, claim 13 to 16 The program according to any one of the above. A program including a group of instructions for causing a computer to execute information processing related to work management,
The information processing
Step of obtaining from the storage means work information including a work completion deadline set by a work requester and work schedule information for ending the work set by the work performer by the completion deadline (A),
Calculating the load on the performer (b), and
Determining the necessity of urging the performer based on the completion deadline, the work schedule information, and the load (c);
Including
The work information further includes a desired deadline set equal to or before the completion deadline,
In the step ( c ), the necessity of the dunning is determined based on the completion deadline, the work schedule information, the load, and the desired deadline.
Program . In the step ( c ), when the load on the performer is high, the necessity for the reminder is determined to be low, and when the load on the performer is low, the desired deadline approaches even if the completion deadline is not approaching. The program according to claim 18 , wherein the necessity of the dunning is determined to be high in the case where the request is made. The program according to claim 18 or 19 , wherein in the step ( b ), the load on the performer is calculated based on a completion rate at which the performer has completed the requested work so far. In the step ( b ), the magnitude of the load on the executor is determined according to a value obtained by subtracting the completion rate from the execution time lapse rate of the executor. The program according to any one of the above. The processor in the computer includes work information including a completion date of the work set by the work requester, and work schedule information for ending the work set by the performer of the work by the completion deadline. step of reading from the storage means to the processor (a),
A step (b) in which the processor calculates the load of the executor based on a completion rate at which the executor has completed the requested work so far; and the processor is based on the completion deadline and the work schedule information. Determining the need for a reminder to the performer ( c ),
Including work management methods. The said step ( c ) WHEREIN: When the said work schedule information is set, the necessity of the said dunning is made relatively low compared with the case where the said work schedule information is not set, The said claim ( c )) Method.

Images