JP6610110B2 - Work management device and program - Google Patents

Description

  The present invention relates to a work management apparatus and a program.

  2. Description of the Related Art Conventionally, for example, a work shift creation support device in which managers such as managers of retail stores and restaurants create work shifts based on conditions desired by employees and past work shift results is known. (See Patent Document 1).

JP 2008-269256 A

  However, even after the work shift is created, the shift may not be changed due to absence or the like. In that case, the shift must be reorganized, which is a troublesome task for the manager. In addition, employees who cooperate with each other even when trying to reorganize the shift may not be found, and it is necessary to raise employee awareness of cooperation in order to proceed smoothly.

  An object of the present invention is to create a work shift based on the number of employees required for each working time, work date information desired by the employee, and employee time evaluation information.

In order to solve the above-described problems, the work management apparatus of the present invention includes an input means for inputting the number of employees required for each work time and work date information desired by the employees, and an attendance evaluation indicating an evaluation of the work status of the employees. a management unit configured to manage information as evaluation score, based on said attendance evaluation information managed by said management means the number of employees and the working time information input and by said input means, required for each of the working hours Shift creation means that creates work shifts by assigning employees, and when an employee is absent, subtract a predetermined subtraction value from the evaluation score of the employee, when other employees are absent When an employee cooperates with the vacancy replacement, an update means for updating the attendance evaluation information by adding a predetermined additional value to the evaluation score of the employee, and the other employee There provided upon absence, the attendance evaluation information selects an employee requesting vacancies replenished in order from the lower employees, and request means for requesting a vacancy replenished employees are selected, the.

In addition, the program of the present invention uses a computer to input the number of employees required for each working time and the working date and time information desired by the employees, and time evaluation information indicating evaluation of the working status of the employees as an evaluation score. managing means for managing, on the basis of the said employees entered by the input means and the work the attendance evaluation information managed by the date and time information and the management unit, by assigning the employees required for each of the working hours Shift creation means to create work shifts, when an employee is absent, subtract a predetermined subtraction value from the evaluation score of the employee, and when another employee is absent, the employee is replaced In the case of cooperation, an updating means for updating the attendance evaluation information by adding a predetermined additional value to the evaluation score of the employee, the other employee is absent In the Time evaluation information requesting vacancies replenished from lower employees in order to select an employee, a program to function as, request means for requesting a vacancy replenished employees chosen.

  According to the present invention, it is possible to create a work shift based on the number of employees required for each working time, work date information desired by the employee, and employee time evaluation information.

It is a block diagram which shows the work management system in this embodiment. (A) is a figure which shows the structure of desired shift totalization DB, (b) is a figure which shows the structure of desired shift submission management, (c) is a figure which shows the structure of work shift DB, (D) is a figure which shows the structure of shift adjustment DB. (A) is a figure which shows the structure of attendance evaluation DB, (b) is a figure which shows the structure of change management DB, (c) is a figure which shows the structure of calendar DB. It is a flowchart which shows the shift creation process in this embodiment. It is a flowchart which shows the replacement registration process in this embodiment. It is a flowchart which shows the attendance evaluation process in this embodiment. It is a flowchart which shows the desired shift creation process in this embodiment. It is an example of the input screen which an employee operates. It is a figure for demonstrating the specific example of a desired shift creation process. It is an example of the input screen which an employee operates.

  Embodiments according to the present invention will be described below in detail with reference to the accompanying drawings. The present invention is not limited to the illustrated example.

The apparatus configuration of the present embodiment will be described with reference to FIGS.
First, with reference to FIG. 1, the work management system 1 of this Embodiment is demonstrated. FIG. 1 is a block diagram showing a work management system 1.

  The work management system 1 is a system that provides support when a manager such as a manager of a retail store or a restaurant creates a work shift for managing the working hours of employees.

  The work management system 1 includes a server 10 as a work management device and a terminal device 20. Each device of the work management system 1 is connected to a communication network N.

  The server 10 is a server device in the cloud of the communication network N, and stores and manages information regarding work, information regarding employee shift, information regarding employee evaluation, and the like. The server 10 is configured by one unit, but is not limited to this, and may be configured by a plurality of devices.

  The terminal device 20 is a device that the administrator and each employee possess and use as a user. The terminal device 20 is a mobile terminal such as a tablet PC, a notebook PC, or a smartphone, and can be connected to the communication network N by wireless communication. Therefore, the terminal device 20 can be used anytime and anywhere by the employee.

  The communication network N is assumed to be the Internet, and may include a WAN (Wide Area Network), a LAN (Local Area Network), a dedicated line, and the like.

  In FIG. 1, only one terminal device 20 provided in the work management system 1 is illustrated. However, the work management system 1 includes a plurality of terminal devices 20 respectively owned by an administrator and a plurality of employees. The server 10 is configured to manage information on the manager and all employees.

  Next, the functional configuration of the server 10 will be described in detail.

  The server 10 includes a CPU (Central Processing Unit) 11, an operation unit 12, a RAM (Random Access Memory) 13, a display unit 14, and a storage unit as shift creation means, update means, request means, and desired shift creation means. As a storage unit 15 and a communication unit 16. Each part of the server 10 is connected via a bus 17.

  The CPU 11 controls each unit of the server 10. The CPU 11 reads a designated program out of the system program and application program stored in the storage unit 15 and expands it in the RAM 13 and executes various processes in cooperation with the program.

  The operation unit 12 includes a key input unit such as a keyboard and a pointing device such as a mouse, receives key input and position input, and outputs the operation information to the CPU 11.

  The RAM 13 is a volatile memory, and forms a work area for temporarily storing various data and programs.

  The display unit 14 includes an LCD (Liquid Crystal Display), an EL (Electro Luminescent) display, and the like, and performs various displays according to display information instructed from the CPU 11.

  The storage unit 15 includes a hard disk drive (HDD), a solid state drive (SSD), and the like, and is a storage unit that can write and read data and programs. The storage unit 15 stores a desired shift tabulation DB (database) 30, a desired shift submission management DB 40, a work shift DB 50, a shift adjustment DB 60, an attendance evaluation DB 70, a shift management DB 80, and a calendar DB 90, which will be described later. In addition, the storage unit 15 stores a shift creation program 151, a shift registration program 152, an attendance evaluation program 153, and a desired shift creation program 154.

  The communication unit 16 includes a network card or the like, and is connected to the communication network N by wired communication. The CPU 11 can communicate with devices on the communication network N via the communication unit 16.

  Next, the functional configuration of the terminal device 20 will be described in detail.

  The terminal device 20 includes a CPU 21, an operation unit 22, a RAM 23, a display unit 24, a storage unit 25, and a communication unit 26. Each unit of the terminal device 20 is connected via a bus 27.

  Since the CPU 21, RAM 23, and display unit 24 are the same as the CPU 11, RAM 13, and display unit 14 of the server 10, overlapping descriptions are omitted. The CPU 21 controls each unit of the terminal device 20.

  The operation unit 22 is a capacitive touch panel or the like provided on the display screen of the display unit 24. The operation unit 22 accepts a touch input by a finger from the user and outputs the operation information to the CPU 21. The operation unit 22 may accept input from a touch pen (digitizer pen).

  The storage unit 25 includes a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), and the like, and is a memory capable of reading and writing information.

  The communication unit 26 includes a wireless communication unit including an antenna, a modulation / demodulation circuit, a signal processing unit, and the like, and performs wireless communication with a base station (not shown) or an access point (not shown) on the communication network N. The CPU 21 can communicate with devices on the communication network N via the communication unit 26.

  Next, information stored in the server 10 will be described with reference to FIGS. FIG. 2A is a diagram showing a configuration of the desired shift tabulation DB 30. FIG. 2B is a diagram showing the configuration of the desired shift submission management DB 40. FIG. 2C is a diagram illustrating a configuration of the work shift DB 50. FIG. 2D is a diagram illustrating a configuration of the shift adjustment DB 60. FIG. 3A is a diagram illustrating a configuration of the attendance evaluation DB 70. FIG. 3B is a diagram showing the configuration of the replacement management DB 80. FIG. 3C is a diagram showing the configuration of the calendar DB 90.

  With reference to FIG. 2A, the desired shift tabulation DB 30 stored in the storage unit 15 of the server 10 will be described. The desired shift tabulation DB 30 is a database that manages information related to the contents of desired shifts submitted by employees. The desired shift indicates a work shift time desired by the employee (in this case, a desired work date and a desired work time zone). The desired shift tabulation DB 30 has fields of “employee No.” 31, “date” 32, and “time zone category” 33.

  “Employee No.” 31 is an identification number for specifying each employee. “Date” 32 is a date of a desired work day. The “time zone category” 33 is a desired working time zone.

  The desired shift submission management DB 40 stored in the storage unit 15 of the server 10 will be described with reference to FIG. The desired shift submission management DB 40 is a database that manages information related to whether or not an employee scheduled to work has submitted a desired shift. The desired shift submission management DB 40 has fields of “employee No.” 41, “desired total time” 42, and “submitted flag” 43.

  “Employee No.” 41 is an identification number for specifying each employee. The “desired total time” 42 is a total time of working hours totaled from the submitted desired shift. The “submitted flag” 43 indicates that the desired shift has been submitted, and is updated from “0” to “1” when the desired shift is submitted.

  With reference to FIG.2 (c), the work shift DB50 memorize | stored in the memory | storage part 15 is demonstrated. The work shift DB 50 is a database that manages information related to work in order to determine a work shift. In addition, the work shift DB 50 is updated according to a change in the work shift of the employee or the like. The work shift DB 50 includes “date” 51, “time zone category” 52, “necessary number of people” 53, “confirmed number of people” 54, “employee number” 55, and “confirmed flag” 56. Has a field.

“Date” 51 is a work day date. The “time zone category” 52 is a working time zone. The “necessary number” 53 is the number of employees required for work. The “determined number of persons” 54 is the number of employees who are confirmed to attend work. “Employee No.” 55 is an employee No. of an employee who has been confirmed to work. It is. The “confirmation flag” 56 indicates that the shift has been confirmed, and when the “necessary number of people” 53 and the “confirmed number of people” 54 become the same number, “0” is updated to “1”.
The “date” 51, the “time zone category” 52, and the “necessary number of people” 53 are work conditions for creating a work shift, and are registered by the administrator.

  The shift adjustment DB 60 stored in the storage unit 15 of the server 10 will be described with reference to FIG. The shift adjustment DB 60 is a database that manages information related to whether or not a shift adjustment that changes the content of a desired shift submitted by an employee has been performed. The shift adjustment DB 60 has fields of “employee No.” 61 and “adjustment flag” 62.

  “Employee No.” 61 is an identification number for specifying each employee. The shift adjustment DB 60 has records for all employees. The “adjustment flag” 62 indicates that shift adjustment has been performed, and is updated to “0” when not adjusted, “1” when adjustment is being performed, and “2” when adjustment has been performed. .

  With reference to Fig.3 (a), time evaluation DB70 memorize | stored in the memory | storage part 15 of the server 10 is demonstrated. The attendance evaluation DB 70 is a database that manages information related to employee evaluation scores. The attendance evaluation DB 70 has fields of “employee No.” 71 and “evaluation score” 72.

  “Employee No.” 71 is an identification number for specifying each employee. The shift adjustment DB 60 has records for all employees. The “evaluation score” 72 is a total value of employee evaluation scores.

  The replacement management DB 80 stored in the storage unit 15 of the server 10 will be described with reference to FIG. The shift management DB 80 is a database that manages information related to shift shifts of employees. The shift management DB 80 includes “No.” 81, “Attendance target date” 82, “Time zone category” 83, “Non-working employee No.” 84, “Cooperation employee No.” 85, “Event” It has fields of “date of discovery” 86, “generation flag” 87, and “absence flag” 88.

  “No.” 81 is a number automatically assigned to each record. The “work attendance date” 82 is a work day when the shift is changed. The “time zone category” 83 is a work time zone in which shifts are changed. “Non-working employee No.” 84 is the employee number of the employee who was absent. It is. “Cooperating employee No.” 85 is an employee No. of the employee who worked instead of the absent employee. It is. “Event discovery date” 86 is the date on which the absence was notified. The “creation time generation flag” 87 indicates the cause of the shift change, and is “1” in the case of cooperation for the excess or shortage of personnel generated at the time of the shift creation, and “0” in the case of a request from the employee. The “absence flag” 88 is “1” in the case of a shift for absence and “0” in response to a time change that occurs at the time of shift creation.

The calendar DB 90 stored in the storage unit 15 of the server 10 will be described with reference to FIG. The calendar DB 90 is a database that manages schedules other than employee work. The calendar DB 90 is updated each time an employee registers a schedule.
The calendar DB 90 has “employee No.” 91 and “schedule” 92. “Employee No.” 91 is an identification number for specifying each employee. The “schedule” 92 is a schedule other than the work of the employee on a specific schedule.

  Next, the operation of the work management system 1 will be described with reference to FIGS. FIG. 4 is a flowchart showing the shift creation process. FIG. 5 is a flowchart showing the replacement registration process. FIG. 6 is a flowchart showing attendance evaluation processing. FIG. 7 is a flowchart showing a desired shift creation process. FIG. 8 is an example of an input screen operated by an employee. FIG. 9 is a diagram for explaining a specific example of the desired shift creation process. FIG. 10 is an example of an input screen operated by an employee.

First, the shift creation process will be described with reference to FIG.
The shift creation process is a process for assembling the working day and working hours of the employee based on the desired shift submitted by the employee.
The CPU 11 of the server 10 reads out from the storage unit 15 using, for example, an instruction from the administrator's terminal device 20 or a preset date (such as the third Monday of every month) as a trigger (START). Then, the shift creation process is executed in cooperation with the shift creation program 151 that is appropriately expanded in the RAM 13.

  First, the CPU 11 notifies the employee's terminal device 20 to urge submission of a desired shift (step S11). Here, the CPU 11 notifies all the terminal devices 20 owned by the employees scheduled to work on the work management system 1. In addition, the deadline for submission will be notified at this time.

  Next, the CPU 11 receives the desired shift transmitted from the employee's terminal device 20, registers it in the desired shift tabulation DB 30, and updates the desired shift submission management DB 40 (step S12).

  Next, the CPU 11 determines whether or not the submission deadline for the desired shift has been reached (step S13). If the submission deadline has not been reached (step S13: NO), the CPU 11 returns to step S12 and repeats the subsequent processing.

  On the other hand, if the deadline for submission has been reached (step S13: YES), has the CPU 11 confirmed the “submitted flag” 43 in the desired shift submission management DB 40 to receive from all the terminal devices 20 that have notified the desired shift? It is determined whether or not (step S14).

  If not received from all the terminal devices 20 that have notified the desired shift (step S14: NO), the CPU 11 notifies the undelivered terminal device 20 to prompt the user and notifies the administrator ( Step S15).

  On the other hand, when it receives from all the terminal devices 20 which notified desired shift (step S14: YES), CPU11 sets an employee to work shift DB50 in order with high evaluation of attendance evaluation DB70 (step S16). For example, in the case of work of “afternoon on March 1, 2015”, the required number of people is one by referring to the work shift DB 50. Employees “0002” and “0003” who wish to work in this time zone are referred to the desired shift tabulation DB 30, but the employee “0002” who has a high evaluation in the attendance evaluation DB 70 is set to shift. Is done. In other words, by setting work shifts in consideration of the employee's desired shift in descending order of time evaluation, the work shifts are created with priority given to employees who have higher time evaluation.

  Next, the CPU 11 determines whether there is an excess or deficiency of personnel in the work shift DB 50 after setting the employees (step S17).

  If there is no excess or deficiency of personnel (step S17: NO), the CPU 11 distributes the shift to the terminal device 20 (step S18), and ends this process.

  On the other hand, when there is an excess or deficiency of the staff (step S17: YES), the CPU 11 notifies the shift adjustment request in order from the lowest evaluation of the attendance evaluation DB 70 (step S19). In other words, the work management system 1 has a mechanism for giving an opportunity for improving evaluation to an employee with a low evaluation score for work evaluation so that the evaluation score of the employee becomes high.

  Next, the CPU 11 determines whether or not a response to the shift adjustment request has been received (step S20). If the response has not been received (step S20: NO), the processing of step S20 is repeated.

  On the other hand, when a response to the shift adjustment request is received (step S20: YES), the CPU 11 updates the work shift DB 50, the shift adjustment DB 60, and the shift management DB 80 (step S21), and returns to step S17 to perform the subsequent processing. repeat.

Next, the replacement registration process will be described with reference to FIG.
The shift registration process is a process to search for employees who can be replaced and change the shift to reflect the shift when the shift of the shift created by the shift creation process described above is not given due to the absence of the employee. It is.
The CPU 11 of the server 10 uses the reception of the shift notification from the terminal device 20 (employee) as a trigger (START), and the replacement is performed in cooperation with the replacement registration program 152 that is read from the storage unit 15 and appropriately expanded in the RAM 13. Execute the registration process.

  First, the CPU 11 determines whether or not the contact received from the terminal device 20 is an absence contact (step S31).

  And when it is notification of absenteeism (Step S31: YES), CPU11 updates change management DB80 (Step S32).

  Next, the CPU 11 notifies the cooperation request in ascending order of evaluation in the attendance evaluation DB 70 (step S33), and proceeds to step S31. That is, step S33 is a mechanism that gives an employee with a low evaluation score for work evaluation a chance to improve the evaluation so that the evaluation score of the employee becomes high. As will be described later with reference to FIG. 6, when the employee who has received the notification works in response to the cooperation request, 3 points are added to the evaluation score of the cooperated employee.

  In step S31, if it is not absence notification (step S31: NO), the CPU 11 determines whether or not it is OK notification to the shift adjustment request (step S34), and OK notification to the shift adjustment request. If not (step S34: NO), the process proceeds to step S33.

  On the other hand, if it is an OK message for the shift adjustment request (step S34: YES), the CPU 11 updates the replacement management DB 80 and the shift DB (step S35), and ends this process.

Next, the attendance evaluation process will be described with reference to FIG.
The attendance evaluation process is a process for calculating an evaluation value for performing attendance evaluation reflecting the absence of employees and the actual working situation other than the desired shift.
The CPU 11 of the server 10 uses, for example, a preset date (the last day of every month, etc.) as a trigger (START), in cooperation with the attendance evaluation program 153 that is read from the storage unit 15 and appropriately expanded in the RAM 13. Execute time evaluation process.

  First, the CPU 11 determines whether or not there is a replacement date in the replacement management DB 80 (step S51). If there is no replacement date (step S51: NO), the process of step S51 is repeated.

  On the other hand, if there is one for which the replacement date has passed (step S51: YES), the CPU 11 determines whether or not the “absence flag” is “1” (step S52).

  If the “absence flag” is not “1” (step S52: NO), the CPU 11 adds one point to the attendance evaluation DB 70 of the cooperated employee (step S53), and then deletes the target record from the shift management DB 80. (Step S54), and this process is terminated.

  If the absence flag is “1” in step S52 (step S52: YES), the CPU 11 determines whether the “generation flag” is “1” (step S55).

If the “occurrence flag at the time of creation” is not “1” (step S55: NO), the CPU 11 deducts the attendance evaluation DB 70 of the absentee employee by a predetermined score calculated by calculation described later (step S56). Three points are added to the attendance evaluation DB 70 of the cooperated employee (step S57), and then the process proceeds to step S54.
On the other hand, when the “generation occurrence flag” is “1” (step S55: YES), the CPU 11 proceeds to step S57.

Here, the method of calculating the score in step S56 will be described.
First, the number of days from the date of attendance to the date of absence notification is calculated. Next, a value obtained by subtracting the calculated number of days from “10” which is a preset value is calculated, and this is set as “corresponding score”. If this value is “10” or more, it is limited to one point.
For example, if the date of work attendance is “7/10” and the date of absence notification is “7/5”, 10-5 is calculated and the score is “5”.
In addition, when the date of work attendance is “7/10” and the date of absence notification is “7/2”, the calculation of 10-8 is performed and the score is “2”.
In addition, when the date of work attendance is “7/10” and the date of absence notification is “6/30” or earlier, the score is “1”.

  By such calculation, the value of the attendance evaluation DB 70 reflects the working attitude of each employee in more detail.

Thus, according to the present system, the administrator only needs to set the work conditions of the work shift DB 50.
Also, employees who need to be absent or changed after confirming the shift in the work shift DB 50 access this system and register it in the shift management DB 80. Then, the employee's attendance evaluation DB 70 and the desired shift submission management DB 40 are used. In addition, a change request or vacancy replacement request is sent to the target employee. When the target employee returns OK or NG to the system, the shift adjustment DB 60 is updated. Specifically, if the reply is NG, contact the next target employee and repeat until an OK reply is received. When an OK reply is received, it is registered in the replacement management DB 80. In addition, when all the employees reply NG, the manager is notified.
In addition, if a shortage occurs in the shift creation stage, the system automatically sends an alternative request to the elephant employee as in the case of a sudden vacancy.
Employees who cooperated with change requests and substitution requests will receive additional points in the evaluation, and points will be deducted for those who are absent from work.

Next, the desired shift creation process will be described with reference to FIGS.
In the present embodiment, when a notification prompting the submission of the desired shift is made in step S11 of the shift creation process, the desired shift can be automatically created and submitted by obtaining the desired shift parameter from the employee. .
In other words, the desired shift creation process is a process for obtaining a desired shift parameter from an employee, and creating and submitting a desired shift based on the desired working day and desired working time of the employee based on the parameter.
For example, the CPU 11 of the server 10 is triggered by the fact that a predetermined shift desired parameter has been transmitted from the employee (START), and in cooperation with the desired shift creation program 154 that is read from the storage unit 15 and appropriately expanded in the RAM 13. The desired shift creation process is executed.

  First, the CPU 11 acquires a desired shift parameter transmitted from the terminal device 20 (employee) (step S71).

  Here, FIG. 8A is an example of the input screen 100 displayed on the display unit 24 of the terminal device 20 when the employee inputs the desired shift parameter.

  The input screen 100 includes a “shift desired date / time list display” 101, an “add button” 102, a “delete button” 103, an “edit button” 104, a “cancel button” 105, an “OK button” 106, It has.

  “Shift desired date / time list display” 101 indicates a desired work day (day of the week) and time. The “add button” 102 is used when adding a desired shift date and time. The “delete button” 103 is used when deleting the contents of the “shift desired date / time list display” 101. The “edit button” 104 is used when editing the content of the “display desired shift date / time list” 101. A “cancel button” 105 is used to cancel the screen display of the input screen 100. The “OK button” 106 is used when the contents of the screen display of the input screen 100 are OK.

  FIG. 8B is an example of the transition destination input screen 200 displayed when the “add button” 102 or the “edit button” 104 is operated.

  The input screen 200 includes a “date designating part” 201, a “time designating part” 202, a “cancel button” 203, and an “OK button” 204.

  The “date designation part” 201 can designate the date individually or repeatedly. The “time designation unit” 202 can designate the time all day or individually. A “cancel button” 203 is used to cancel the screen display of the input screen 200. The “OK button” 204 is used when the content of the screen display of the input screen 200 is OK.

The CPU 11 acquires the desired working day (day of the week) and the desired working time input on the input screen 100 and the input screen 200 as the shift desired parameters.
For example, as shown in FIG. 9A, for example, a desired shift parameter such as “desired every Wednesday from 17:00 to 22:00” is acquired.

Next, the CPU 11 acquires a schedule for a period for creating a shift from the calendar DB (step S72).
The schedule of the period for creating the shift is a schedule other than the work of the employee registered in advance in the calendar DB. For example, as shown in FIG. 9B, “Schedule 1: February 11 (Wednesday) ) 13: 00 to 18:00 is scheduled "" Schedule 2: February 12 (Thursday) 14: 00 to 15:00 is scheduled ".

Next, the CPU 11 creates a temporary shift table from the desired shift parameter acquired in step S71 (step S73).
The temporary shift table is a shift table created only from the acquired desired shift parameter. For example, from the desired shift parameter shown in FIG. 9A, as shown in FIG. 1: February 4 17: 00 to 22:00 "" Hope 2: February 11 17: 00 to 22:00 "" Hope 3: February 18 17: 00 to 22:00 "" Hope 4: A temporary shift table such as “February 25, 17: 00 to 22:00” is created.

Next, the CPU 11 excludes shifts in the temporary shift table that are covered by the schedule acquired in step S72 (step S74).
For example, if the schedule shown in FIG. 9B is excluded from the temporary shift table shown in FIG. 9C, “hope 1: February 4 17: 00 to 22:00” “hope 3: February 18th 17: 00 to 22:00 "and" Hope 4: 2/25 17: 00 to 22:00 "will remain.

Next, in step S74, the CPU 11 sets the remaining shifts excluding the schedule from the provisional shift table as the provisional version desired shift (step S75).
In the example of FIGS. 9A to 9C, the temporary version desired shift is shown in FIG. 9D.

  Next, the CPU 11 starts transmitting the provisional version desired shift to the terminal device 20 (step S76).

  Here, FIG. 10A is an example of the provisional version desired shift 300 displayed on the display unit 24 of the terminal device 20.

  The provisional version desired shift 300 includes a “shift desired date / time list display” 301, an “add button” 302, a “delete button” 303, an “edit button” 304, a “notify later button” 305, and a “submit button”. 306.

  “Shift desired date / time list display” 301 indicates a desired work day (day of the week) and time. An “add button” 302 is used when adding a desired shift date and time. The “delete button” 303 is used when deleting the contents of the “shift desired date / time list display” 301. The “edit button” 304 is used when editing the contents of the “display desired shift date / time list” 301. The “notify later button” 305 is used when canceling the screen display of the provisional version desired shift 300 in order to submit the provisional version desired shift submission instruction later. A “submit button” 306 is used to instruct the submission with the contents of the provisional version desired shift 300.

  FIG. 10B is an example of the desired shift change screen 400 at the transition destination that is displayed when the “add button” 302 or the “edit button” 304 is operated.

  The desired shift change screen 400 includes a “date designating part” 401, a “time designating part” 402, a “cancel button” 403, and an “OK button” 404.

  A “date designation unit” 401 can designate a date. The “time specifying unit” 402 can specify the time all day or individually. A “cancel button” 403 is used to cancel the screen display of the desired shift change screen 400. The “OK button” 404 is used when the contents of the screen display of the desired shift change screen 400 are OK.

  Next, the CPU 11 determines whether or not a preset submission deadline has passed in a state where the “submit button” 306 of the provisional version desired shift 300 is not operated (step S77).

  If the submission deadline has passed (step S77: YES), the CPU 11 submits the provisional version desired shift (step S78), and ends this process.

  On the other hand, if the submission deadline has not passed (step S77: NO), the CPU 11 determines whether or not an instruction to submit later (operation of the “notify later button” 305) is given by the terminal device 20 ( If an instruction to submit later is given (step S79) (step S79: YES), the process returns to step S76 and the subsequent processing is repeated.

  In addition, when an instruction to submit later is not given, that is, an instruction to submit immediately is given (step S79: NO), the CPU 11 uses the terminal device 20 to correct the provisional version desired shift. It is determined whether or not an instruction has been given (step S80).

When an instruction to correct the provisional version desired shift is given (step S80: YES), the CPU 11 corrects and submits the provisional version desired shift (step S81), and ends this process.
On the other hand, when an instruction to correct the provisional version desired shift is not made (step S80: NO), the CPU 11 submits the provisional version desired shift as it is (step S82), and the process is terminated.

  As described above, according to the present system, the temporary version desired shift is automatically created from the shift desired parameter inputted in advance and the calendar inputted with the personal schedule. For this reason, the employee can confirm the automatically created provisional version desired shift, amend it if necessary, and submit it easily. Even if an employee has forgotten to submit the desired shift by the deadline, a provisional version of the desired shift is submitted, so the administrator can grasp the employee's desired shift at that point in time. It will be possible.

As described above, in the present embodiment, the server 10 stores in the storage unit 15 the number of employees necessary for each working time, the working date and time information desired by the employee, and the time evaluation information indicating the evaluation of the working status of the employee. The CPU 11 creates a work shift by assigning necessary employees for each working time based on the number of employees, working date / time information, and attendance evaluation information. In particular, the CPU 11 creates a work shift by prioritizing work date information of employees with high attendance evaluation information.
For this reason, by creating a work shift by prioritizing the wishes of employees with high attendance evaluations, it is possible to maintain the fairness of the shift assignment and increase the employee's awareness of cooperation.

Moreover, according to this embodiment, CPU11 updates attendance evaluation information according to the attendance record of the employee relevant to a work shift.
For this reason, since attendance evaluation increases according to attendance results, it is possible to increase employees' awareness of cooperation.

Further, according to the present embodiment, the attendance evaluation information is an evaluation score, and when an employee is absent, the CPU 11 subtracts a predetermined subtraction value from the evaluation score of the employee, If an employee cooperates with the vacancy replenishment when absenteeism, a predetermined additional value is added to the evaluation score of the employee.
For this reason, since the evaluation score is updated in accordance with the employee's absence or cooperation for vacancy replacement, a clear attendance evaluation can be performed.

Further, according to the present embodiment, when another employee is absent, the CPU 11 selects an employee who requests vacancy replenishment in order from the employee with the lowest time evaluation information, and replenishes the selected employee with vacancy replenishment. Request.
For this reason, the opportunity to raise time evaluation is given in an order from the employee with low time evaluation, and the cooperation consciousness of the employee can be raised.

In addition, according to the present embodiment, the CPU 11 creates work date information based on a shift request parameter indicating repetition of work desired by the employee and a non-work schedule of the employee stored in advance.
For this reason, it is possible to save labor for the employee to create the desired shift.

Further, according to the present embodiment, the desired shift parameter includes at least one of a specific day of the week, a specific week, and a specific date.
Therefore, the employee can create a desired shift only by setting a specific day of the week, a specific week, a specific date, and the like.

The attendance evaluation may be updated every predetermined period (for example, every month). By doing in this way, evaluation for every period becomes possible.
Moreover, it is good also as reducing the number of points deducted for the reason of absenteeism. For example, in the case of repelling, the score to be deducted may be set to “0”.

As mentioned above, although several embodiment of this invention was described, the scope of the present invention is not limited to the above-mentioned embodiment, The range of the invention described in the claim is equal to the equivalent range. Including.
The invention described in the scope of claims attached to the application of this application will be added below. The item numbers of the claims described in the appendix are as set forth in the claims attached to the application of this application.

[Appendix]
<Claim 1>
An input means for inputting the number of employees required for each working hour and the working date and time information desired by the employee;
A management means for managing time evaluation information indicating an evaluation of the employee's work status;
Shift creation that creates a work shift by assigning the required employees for each working time based on the number of employees and the work date information input by the input means, and the attendance evaluation information managed by the management means Means,
A work management device comprising:
<Claim 2>
The work management apparatus according to claim 1, wherein the shift creation unit creates the work shift by prioritizing the work date and time information of an employee with high attendance evaluation information.
<Claim 3>
The work management apparatus according to claim 1, further comprising an updating unit configured to update the time evaluation information in accordance with an employee's attendance record related to the work shift.
<Claim 4>
The attendance evaluation information is an evaluation score,
When the employee is absent from work, the updating means subtracts a predetermined subtraction value from the evaluation score of the employee, and when an employee cooperates with the vacancy replacement when other employees are absent The work management apparatus according to claim 3, wherein a predetermined addition value is added to the evaluation score of the employee.
<Claim 5>
5. When the other employees are absent from work, there is provided request means for selecting employees who request vacancy replenishment in order from the employees with the lowest time evaluation information, and requesting the selected employees to replenish vacancy. The work management device described in 1.
<Claim 6>
Any one of Claims 1-5 provided with the desired shift creation means which creates the said work date information based on the shift desired parameter which shows the repetition of the duty which an employee desires, and the non-work schedule of the employee memorize | stored beforehand. The work management device according to one item.
<Claim 7>
The work management apparatus according to claim 6, wherein the shift desired parameter includes at least one of a specific day of the week, a specific week, and a specific date.
<Claim 8>
Computer
Input means for entering the number of employees required for each working hour and the working date and time information desired by the employee,
A management means for managing time evaluation information indicating evaluation of the work status of employees,
Shift creation that creates a work shift by assigning the required employees for each working time based on the number of employees and the work date information input by the input means, and the attendance evaluation information managed by the management means means,
Program to function as.

1 work management system 10 server (work management device)
11 CPU (shift creation means, update means, request means, desired shift creation means)
12 operation unit 14 display unit 15 storage unit (input means, management means)
151 Shift creation program 152 Replacement registration program 153 Time evaluation program 154 Desired shift creation program 30 Desired shift tabulation DB
40 Desired shift submission management DB
50 Work shift DB
60 Shift adjustment DB
70 Time evaluation DB
80 shift management DB
90 Calendar DB
16 Communication unit 17 Bus 20 Terminal device 21 CPU
22 Operation unit 23 RAM
24 display unit 100, 200 input screen 300 provisional version desired shift 400 desired shift change screen 25 storage unit 26 communication unit 27 bus

Claims (5)

An input means for inputting the number of employees required for each working hour and the working date and time information desired by the employee;
A management means for managing attendance evaluation information indicating an evaluation of an employee's work status as an evaluation score ;
Based on the number of employees and the working time information input and said attendance evaluation information managed by said management means by said input means, to create a work shift by assigning employees required for each of the working hours Shift creation means;
If an employee is absent from work, a predetermined subtraction value is subtracted from the employee's evaluation score. When another employee is absent from work, if the employee cooperates in the replacement of the employee, the employee's Updating means for updating the attendance evaluation information by adding a predetermined addition value to the evaluation score;
When other employees are absent, selecting means for requesting vacancy replenishment in order from the employee with the lowest time evaluation information, and request means for requesting the selected employee to replenish vacancy,
A work management device comprising:   The work management apparatus according to claim 1, wherein the shift creation unit creates the work shift by prioritizing the work date and time information of an employee with high attendance evaluation information. The desired shift creation means for creating the work date and time information based on a shift request parameter indicating a repetition of work desired by the employee and a non-work schedule of the employee stored in advance. Work management device. The work management apparatus according to claim 3, wherein the shift desired parameter includes at least one of a specific day of the week, a specific week, and a specific date. Computer
Input means for entering the number of employees required for each working hour and the working date and time information desired by the employee,
Management means for managing attendance evaluation information indicating evaluations of employee work status as evaluation scores,
Based on the number of employees and the work date information input by the input means and the attendance evaluation information managed by the management means, a work shift is created by assigning necessary employees for each work time. Shift creation means ,
If an employee is absent from work, a predetermined subtraction value is subtracted from the employee's evaluation score. When another employee is absent from work, if the employee cooperates in the replacement of the employee, the employee's Updating means for updating the attendance evaluation information by adding a predetermined addition value to the evaluation score;
Request means for requesting vacancy replenishment to selected employees, selecting an employee who requests vacancy replenishment in order from the employee with the lowest time evaluation information when the other employee is absent.
Program to function as.

Images