JP7579653B2 - Employment management system, employment management method, employment management device and program - Google Patents

Description

The present invention relates to an employment management system, an employment management method, an employment management device, and a program for managing the attendance status of employees.

Although time recorders are widely used to manage working hours, if an employee forgets to clock in and out, the data must be corrected at a later date. In many cases, employees submit requests to correct their time-stamped data, but if the time is submitted based solely on the employee's own memory and there is a discrepancy between the actual time and the requested time, the working hours cannot be accurately recorded. It is also possible to submit arrival and departure times that result in fraudulently long working hours.

For example, Patent Document 1 discloses a technology for a time recorder that allows an employee to use a specified terminal device to send information such as their arrival and departure times to a specified management device, even if they are unable to or have not directly punched into the time recorder, and the information is then automatically sent to the time recorder, allowing the unpunched information to be punched in at the next time the employee punches in.

JP 2002-245502 A

However, in Patent Document 1, employees must send their clock-in/clock-out information using their terminal devices. If this sending operation is not performed, the clock-in/clock-out information will not be stored in the management device, and the problem of not clocking in cannot be resolved.

In view of the above circumstances, the object of the present invention is to provide an employment management system, an employment management method, an employment management device, and a program that can perform proper labor management by reducing the amount of correction work such as applications and the administrative work required by employees, even when employees forget to punch in and out times into the time recorder.

An employment management system according to one embodiment of the present invention includes a business device used by a worker for work, an employment management device operated by the worker, and a management device capable of communicating with the business device and the employment management device.
The business device includes a boot history information transmission unit that transmits boot history information relating to a boot state and a non-boot state to the management device.
The employment management device has a clock unit, a first memory unit that stores employee identification information that identifies an employee, a time-stamp information generation unit that generates, when an employee inputs the employee identification information and stamps in, the time obtained from the clock unit and information indicating the employee as attendance/time-stamp information, and a time-stamp information transmission unit that transmits the attendance/time-stamp information to the management device.
The management device has a second memory unit, a startup history information recording unit which records the startup history information transmitted from the business device in the second memory unit, a time attendance information recording unit which records the time attendance information transmitted from the work management device in the second memory unit, and a time attendance complementary information generating unit which detects whether or not there is unpunched time attendance information with missing punches from the time attendance information recorded in the second memory unit, and when the unpunched time attendance information is detected, generates data to complement the unpunched time attendance information based on the startup history information recorded in the second memory unit.

The management device may further include an attendance complementary information confirmation unit that executes a process to have the employee or a manager confirm the unstamped attendance information using the data generated by the attendance complementary information generation unit.

The attendance completion information generating unit may be configured to change the type of startup history and acquisition priority used to complete the unstamped attendance information depending on conditions such as the working status of the employee.

The attendance completion information generating unit may be configured to execute an estimation process of attendance times when there is no startup history to be used to complete the unstamped attendance information.

The attendance supplementary information generating unit may be configured to use various time data related to the work as startup history information used to supplement the unstamped attendance information.

A method for managing work according to one aspect of the present invention includes transmitting activation history information relating to an activated state and an inactivated state from a business device used by an employee for work to a management device;
A working management device operated by the worker transmits time stamp information including a time stamp and information indicating the worker to the management device;
The management device records the start-up history information transmitted from the business device in a memory unit, records the clock-in/clock-out information transmitted from the work management device in the memory unit, detects whether there is any unpunched clock-in/clock-out information with missing clock-in/clock-out information from the clock-in/clock-out information, and when the unpunched clock-in/clock-out information is detected, generates data to complement the unpunched clock-in/clock-out information based on the start-up history information.

An employment management device according to an embodiment of the present invention includes a clock unit, a storage unit, a time-stamp information generating unit, and an attendance time-stamp information transmitting unit.
The storage unit stores worker identification information for identifying a worker.
When an employee inputs the employee identification information and stamps his/her time, the stamp information generating unit generates the time acquired from the clock unit and information indicating the employee as attendance/leave stamp information.
The attendance time-stamp information sending unit detects whether there is any unpunched attendance information with missing punches from the attendance time-stamp information, and when the unpunched attendance time-stamp information is detected, it sends the attendance time-stamp information to a management device that is capable of generating data to complement the unpunched information based on startup history information regarding the startup and non-startup states sent from the business device used by the employee for work.

According to one aspect of the present invention, there is provided a program for managing a management device,
A step of recording attendance information including a time stamp and information indicating the worker, the time stamp being transmitted from a work management device operated by the worker;
A step of recording activation history information regarding an activated state and an inactivated state transmitted from a business device used by an employee for business;
A step of detecting whether there is any unstamped clock-in/clock-out information with missing clock-in/clock-out information from the clock-in/clock-out information;
When the unpunched clock-in/out information is detected, data for complementing the unpunched clock-in/out information is generated based on the start-up history information.

According to the present invention, when a time stamp is forgotten on an employment management device (time recorder), the amount of correction work such as applications and the amount of management work required by the employment staff can be reduced, and proper labor management can be performed.

1 is a configuration diagram of an employment management system according to an embodiment of the present invention; 2 is a configuration diagram of a business device, an employment management device, and a management device in the employment management system. 11 is a diagram showing a format of start-up history information transmitted from a business apparatus to a management apparatus. FIG. FIG. 2 is a front view showing an example of a configuration of the work management device. FIG. 4 is a diagram illustrating an example of an employee information table stored in the work management device. 11 is a diagram showing a format of time-stamp information transmitted from the work management device to the management device. FIG. FIG. 4 is a diagram illustrating an example of an employee information table stored in the management device. FIG. 4 illustrates an example of a boot history information table stored in the management device. FIG. 4 is a diagram illustrating an example of a work attendance information table stored in the management device. 11 is a first half of a flowchart illustrating an example of a processing procedure executed in a management device. 11 is a second half of a flowchart illustrating an example of a processing procedure executed in the management device. FIG. 4 is a diagram illustrating an example of a work schedule information table stored in the management device. FIG. 4 is a diagram illustrating an example of a work shift table stored in the management device. 11 is a diagram illustrating an example of a boot history search target information table stored in the management device. FIG. FIG. 11 is a diagram illustrating an example of a work attendance supplementary information table stored in the management device. FIG. 13 is a diagram showing an example of an email displayed on a business device. FIG. 13 is a diagram showing an example of a work management screen displayed on the business device. FIG. 13 is a diagram illustrating an example of a pop-up screen displayed on a business device. FIG. 13 is a diagram showing an example of a work attendance information table to which complementary data has been added; FIG. 13 is a diagram illustrating an example of a pop-up screen displayed on a business device. FIG. 13 is a configuration diagram of an employment management system according to another embodiment of the present invention. 11 is a diagram showing a format of start-up history information transmitted from a business apparatus to a management apparatus. FIG.

The following describes embodiments of the present invention with reference to the drawings. The following embodiments disclose preferred specific examples of the present invention, but the technical scope of the present invention is not limited to these aspects.

[Work Management System]
FIG. 1 is a configuration diagram of an employment management system according to an embodiment of the present invention.
The work management system 10 of this embodiment includes a business device 1, a work management device 2, and a management device 3.
The business device 1, the work management device 2, and the management device 3 are connected to each other via a network N so as to be able to communicate with each other and to send and receive data. In the illustrated example, there is one business device 1, but typically, two or more business devices 1 are included. In the illustrated example, there is one work management device 2, but typically, there are two or more work management devices 2. In addition, the work management system 10 in FIG. 1 is a Web version, and the business device 1 performs various notification application processes on a Web screen generated by the management device 3.

The business device 1 is a device that is managed and used within the company by employees who are employed in the course of their daily work. Typically, the business device 1 is a desktop or notebook type information processing device (personal computer), a tablet, a smartphone or other PDA (personal digital assistant). The business device 1 may also include a business device used by a manager who manages employees.

The work management device 2 is a work management device (time recorder) that registers the arrival and departure times of employees. The work management device 2 is placed, for example, at each business office, department, or store of a company, and is typically installed near the entrance and exit of the workplace.

The management device 3 is an employment management server that centrally manages the attendance data entered by each employee on the employment management device 2, accepts various procedures carried out by employees and management personnel on the business device 1, and performs various processes such as updating the database.

Figure 2 is a configuration diagram of the business device 1, the work management device 2, and the management device 3 in the work management system 10.

(Business equipment)
As shown in FIG. 2, the business device 1 includes a control unit 11, a storage unit 12, a display unit 13, an input unit 14, an interface unit 15, an external communication unit 19, and the like.
The storage unit 12, the display unit 13, the input unit 14 and the external communication unit 19 are connected to one another via an interface unit 15. The interface unit 15 is connected to the control unit 11 via a bus 16.

The storage unit 12 stores software (programs) for executing various functions of the business device 1. The storage unit 12 is composed of a hard disk drive (HDD), a solid state drive (SSD), a read only memory (ROM), a random access memory (RAM), etc. The above software may be installed, for example, via a recording medium or via the network N.

The display unit 13 is a display such as an LCD panel, and may be a device separate from the main body of the business device 1. The input unit 14 includes a keyboard, a mouse, a touch panel, etc. The external communication unit 19 is a communication module capable of communicating with the work management device 2 through the network N. The communication method is not particularly limited, and may be wired communication or wireless communication.

The control unit 11 is an information processing device including a CPU (Central Processing Unit) and memory, and performs various information processing by executing software stored in the storage unit 12. The control unit 11 includes a startup history information transmission unit 111 as a functional block.

The start-up history information transmission unit 111 generates start-up history information related to the start-up state and non-start-up state of the business device 1. The start-up state typically means a state in which the business device 1 is powered on and an OS (Operating System) is running. If multiple OSs are installed in the business device 1, it is determined whether each OS is running.
Furthermore, the non-activated state typically refers to a shutdown state of the business device 1, but is not limited thereto and may include a sleep state and a logout (or logoff) state. Furthermore, the activated state may include a power recovery from sleep and a login (or logon) state to the business device 1.

The startup history information transmission unit 111 transmits the generated startup history information to the management device 3 via the external communication unit 19 each time a change in the started/non-started state occurs. The startup history information transmission unit 111 generates startup history information indicating startup information when the business device 1 is started, when the power is restored from sleep, or when a login operation is performed, and transmits this to the management device 3. The startup history information transmission unit 111 also generates startup history information indicating a non-started state when a shutdown operation, a sleep operation, or a logout operation is performed, and transmits this to the management device 3.

FIG. 3 shows a format of the start-up history information transmitted from the business device 1 to the management device 3. As shown in FIG.
The startup history information format shown in the figure has fields for "ID type," which indicates the type of ID for personal identification, and the "identification ID" of the operator, and is further composed of "date,""time,""eventcontent,""location of occurrence," and "type of location of occurrence."
The example of Figure 3 shows the startup history information when an employee (personal code 001) with an identification ID of "001N" in the NW (network) login ID started up (logged in) a personal computer (PC1) at 8:50 a.m. on June 1, 2020.

(Work management device)
As shown in FIG. 2, the employment management device 2 has a control unit 21, a memory unit 22 (first memory unit), a display unit 23, an audio output unit 24, an interface unit 25, a clock unit 26, an operation input unit 27, an operator information input unit 28, an external communication unit 29, etc.
The display unit 23, the audio output unit 24, the clock unit 26, the operation input unit 27, the operator information input unit 28 and the external communication unit 29 are connected to one another via an interface unit 25. The storage unit 22 and the interface unit 15 are connected to the control unit 21 via a bus 30.

The memory unit 22 stores software (programs) for executing various functions of the work management device 2. The memory unit 22 is composed of a HDD, SSD, ROM, RAM, etc. The above software may be installed, for example, via a recording medium or via the network N. The memory unit 22 stores identification information for each employee.

Figure 4 is a front view showing an example of the configuration of the work management device 2.

The display unit 23 is a display such as a liquid crystal panel, and is typically installed on the front of the housing 20 of the work management device 2, as shown in FIG. 4. The audio output unit 24 typically outputs an electronic sound indicating whether the operation is normal or abnormal, and may be configured to present the operation method by audio depending on the settings.

The clock unit 26 keeps track of the current time and displays the time together with the date on the display unit 23. The operation input unit 27 inputs a time stamp type including at least clocking in and clocking out based on an operation by an operator, that is, an employee.
In this embodiment, the operation input unit 27 is an input operation surface such as a touch sensor that constitutes part of the display unit 23, and as shown in Fig. 4, each selection button (selection key) for "Clock in", "Clock out", "Go out", and "Return" is arranged in the display area of the display unit 23. However, without being limited to this, the operation input unit 27 may be composed of an operation button or the like arranged in an area other than the display unit 23.

The operator information input unit 28 acquires identification information from the operator and inputs the information. The operator information input unit 28 is configured with a card reader capable of reading out the operator's identification information (also referred to as operator information or employee information) from an ID card capable of contactless communication, such as an employee ID card issued to each employee.
The operator inputs the operator's identification information into the work management device 2 by holding an ID card over the card reader surface 28a installed near the display unit 23. Examples of the operator information include an employee code (personal code), an individual name, and a company code.

The external communication unit 29 is a communication module capable of communicating with each business device 1 through the network N. The communication method is not particularly limited, and may be wired communication or wireless communication.

The control unit 21 is an information processing device including a CPU and memory, and performs various information processing by executing software stored in the storage unit 22. As shown in FIG. 2, the control unit 21 includes, as functional blocks, an employee recognition unit 211, a display control unit 212, a time-stamp information generation unit 213, and a time-stamp information transmission unit 214.

The employee recognition unit 211 recognizes the operator from the identification information input to the operator information input unit 28. The employee recognition unit 211 recognizes the operator based on the employee information table stored in the memory unit 22.

FIG. 5 shows an example of an employee information table stored in the work management device 2.
The worker information table shown in the figure holds the card ID and personal name of each employee, which is a personal identification ID in the work management device 2. The contents of the worker information table are transmitted from the management device 3 in advance.
The employee with the card ID "001C" shown in Fig. 5 is the same as the employee with the network ID "001N" shown in Fig. 3. In other words, the identification ID with "C" added to the end of the employee's personal code corresponds to the card ID, and the identification ID with "N" added to the end of the personal code corresponds to the NW login ID (see Fig. 7).

The display control unit 212 generates an image to be displayed on the display unit 23. The display control unit 212 normally controls the display unit 23 so that a screen showing the current time, date, and type of stamping (Figure 4) is displayed.

The time-stamp information generation unit 213 generates the attendance time-stamp information using the operator's identification ID, the type of time-stamp input by the operator, and the time information obtained from the clock unit.

The attendance time-stamp information sending unit 214 sends the attendance time-stamp information generated by the time-stamp information generating unit 213 to the management device 3.

FIG. 6 shows a format of the clock-in/clock-out information transmitted from the work management device 2 to the management device 3.
The attendance time stamp information format shown in the figure has fields for "ID type," which indicates the type of ID used for personal identification, and the operator's "identification ID," and is further composed of "date,""time,""attendancecategory,""location of occurrence," and "location type of occurrence."

(Management Device)
As shown in FIG. 2, the management device 3 includes a control unit 31, a storage unit 32 (second storage unit), a display unit 33, an input unit 34, an interface unit 35, an external communication unit 39, and the like.
The storage unit 32, the display unit 33, the input unit 34 and the external communication unit 39 are connected to one another via an interface unit 35. The interface unit 35 is connected to the control unit 31 via a bus 36.

The memory unit 32 is composed of a HDD, SSD, ROM, RAM, etc. The memory unit 32 stores an attendance information table 321, a startup history information table 322, an attendance supplementary information table 323, a startup history search target information table 324, an employee information table 325, a work schedule information table 326, a work shift table 327, etc.

The control unit 31 is composed of an information processing device having a CPU and a memory. As shown in FIG. 2, the control unit 31 has, as functional blocks, an attendance information recording unit 311, a startup history information recording unit 312, an attendance complementary information generating unit 313, and an attendance complementary information determining unit 314.

The startup history information recording unit 312 receives the startup history information in the format shown in FIG. 3 sent from the business device 1, references the employee information table 325 in the memory unit 32 from the identification ID in the startup history information, obtains the corresponding personal code, and stores it in the startup history information table 322 in the memory unit 32.

FIG. 7 shows an example of the worker information table 325 stored in the storage unit 32. As shown in FIG.
The employee information table 325 shown in the figure stores, in addition to personal codes and personal names, various identification IDs linked to personal information, such as card IDs and network login IDs, and email addresses.

Figure 8 shows an example of the startup history information table 322 stored in the memory unit 32. The startup history information table 322 stores personal codes, dates, times, event contents, occurrence locations, and occurrence location types.

In this startup history information table 322, the event content indicates the state of the corresponding startup history information, as well as the login and logoff information of the business device 1. The occurrence location holds the specific name of the occurrence location of the startup history information of the corresponding business device 1. The occurrence location type holds the classification of the corresponding business device 1.

Each time the startup history information is transmitted by the startup history information transmission unit 111 of the business device 1, the startup history information is added to the startup history information table 322 by the startup history information recording unit 312 of the management device 3. The startup history information is not limited to being constantly communicated and recorded in real time, and the management device 3 may update the startup history information table by periodically acquiring the startup history information from the business device 1 as a batch process.

The attendance information recording unit 311 receives attendance time-stamping information in the format shown in FIG. 6 sent from the work management device 2, refers to the employee information table 325, obtains the corresponding personal code from the card ID, and stores it in the attendance information table 321 in the memory unit 32.

Figure 9 shows an example of the attendance information table 321 stored in the memory unit 32. This attendance information table 321 stores personal codes, dates, times, attendance categories, event details, occurrence locations, occurrence location types, occurrence cause types, and status types.

The clock-in/out category indicates the type of clock-in, such as "clock-out". The event content holds the event from the startup history when clock-in/out information is recorded from the startup history. The occurrence location holds the specific name of the location where the clock-in/out information occurred. The occurrence location type holds the classification of the location where the clock-in/out information occurred.
The occurrence cause type holds a classification of the occurrence cause of the attendance information, whether it is reception from the work management device 2 (time recorder) or automatic completion from the start history as described later. The status type holds a state such as "identity confirmed" or "administrator approved" as the current status of the attendance information.

In addition, each time the attendance time-stamping information is sent by the attendance time-stamping information sending unit 214 of the work management device 2, the attendance time-stamping information is added to the attendance time-stamping information table 321 by the attendance time-stamping information recording unit 311 of the management device 3. The system is not limited to performing real-time recording processing by performing constant communication processing, and the management device 3 may update the attendance time-stamping information table by periodically obtaining attendance time-stamping information from the work management device 2 as a batch process.

The attendance supplementary information generating unit 313 refers to the attendance information table 321 to detect whether there is any unpunched attendance information with missing time stamps, and when it detects unpunched attendance information, it extracts data that can be supplemented with information from the start-up history information table 322, and adds the data to the attendance supplementary information table 323 (see FIG. 15). This data is used to supplement unpunched attendance information with missing time stamps.

The attendance information generation unit 313 may be called at any time required for business purposes, such as at a specific time during the day, such as when the date change time is reached or when overtime starts, or periodically, such as every 10 minutes or every 30 minutes, or whenever a record is added to the startup history information table.

The attendance information confirmation unit 314 executes a process to have the worker or the manager confirm the unstamped attendance information using the data generated by the attendance information generation unit 313. In this embodiment, the attendance information confirmation unit 314 performs post-processing such as sending an application request to the worker for the attendance information added by the attendance information generation unit 313, accepting the processing, and storing the results in a database, as described below. The database may be installed inside the management device 3 (e.g., as part of the storage unit 32) or outside the management device 3.

[Work management system operation]
(Process of generating attendance information using start history information)
Next, the operation of the work management system 10 configured as above will be described.

Figures 10 and 11 are flowcharts showing an example of the operation procedure of the control unit 31 (mainly the attendance completion information generation unit 313) executed in the management device 3.

The following is an example of a case in which an employee with "Personal Code = 004" logs off from business device 1 on business device "PC4" at "2020/6/1 21:15", leaves the office without clocking out on work management device 2, and attendance supplementary information is generated on management device 3 the next day.

The result of capturing the attendance information by the attendance information recording unit 311 before the attendance complementary information generation process is shown in the attendance information table 321 in FIG. 9. The result of capturing the startup history information by the startup history information recording unit 312 before the attendance complementary information generation process is shown in the startup history information table 322 in FIG. 8.

First, the control unit 31 acquires data of an individual from the employee information table 325 (see FIG. 7) (step S101).
Next, the control unit 31 obtains the arrival and departure information of the individual on the day to be checked from the attendance information table 321 (Figure 9), obtains the work schedule information for the relevant day from the work schedule information table 326 (Figure 12), and obtains the settings from the work shift table 327 (Figure 13).
If there is out-of-hours notification data, the out-of-hours notification data (not shown) is also acquired (step S102).

Figure 12 shows an example of a work schedule information table 326 stored in the management device 3. This work schedule information table 326 holds personal codes, dates, and work shifts.

Figure 13 shows an example of a work shift table 327 stored in the management device 3. This work shift table 327 stores the shift name, and the start time, end time, start time of work, start time of overtime, start/end time changeover time, date changeover time, and whether or not telework is enabled for each shift name.

As an example, data for "individual = 004" is obtained from the employee information table 325 (see FIG. 7), data for "individual = 004, date = 2020/6/1" is obtained from the attendance information table 321 (see FIG. 9), data for "individual = 004, work shift = late shift" is obtained from the work schedule information table 326 (see FIG. 12), and various data for "shift name = late shift" is obtained from the work shift table 327 (see FIG. 13).

Next, the control unit 31 acquires search targets for the start history for complementing missing time-stamps (unstamped clock-in/clock-out information) from the start history search target information table 324 (see FIG. 14). At this time, the control unit 31 checks the records in the order of sequence numbers, and if there is data that matches all of the clock-in/clock-out categories and application conditions, it expands the search targets in the storage unit 32.
This process is carried out for both clock-in and clock-out times, and if multiple search targets are set, all of them are acquired (step S103).

14 shows an example of the startup history search target information table 324 stored in the management device 3. As an example, for attendance, the work shift "late shift" acquired in step S102 does not have a telework attribute, so the search target data for "sequence No.=1" and "attendance category=attendance, not telework" is acquired. If there are multiple search targets, all of them are acquired.
A similar process is performed for clocking out, and the search target data for "Sequence No.=3" and the condition "Attendance category=clocking out, not teleworking" is obtained.

Next, the control unit 31 starts processing for clocking in and out.
If the attendance information indicates that the employee has already clocked in, or if the work schedule information table 326 indicates that the employee is not scheduled to come to work (step S104, No), the process for attendance is not performed, and the process for clocking out is started (step S109). If the employee is scheduled to come to work but has not clocked in (step S104, Yes), the process proceeds to the next step S105.

As an example, since attendance information for "Personal = 004, Date = 2020/6/1" exists in the attendance information table 321 (Figure 9), attendance supplementary information is not generated and the process proceeds to the attendance processing in step S109.

Next, if there are any launch history search targets remaining to be checked (step S105, Yes), launch history information that matches the search target is obtained from the launch history information for that individual on the relevant day (step S106).

Next, if the individual is scheduled to come to work at the regular time, the control unit 31 extracts the work shift from the schedule information for that day, obtains the work shift information, and determines whether there is any startup history information within the range of the work time period (from the start time of work to the start time of work).
If the user is scheduled to leave early, the overtime notification data is retrieved and it is determined whether or not there is activation history information within the early start time period (step S107). If there is no activation history (step S107, No), the system checks whether or not there is a search target of the next priority, and continues searching until there are no more search targets (step S105, No).

If there is startup history information within the working hours or early start hours (step S107, Yes), data indicating that the individual arrived at work at the time indicated in the startup history information is added to the attendance/leave complementary information table 323 (step S108, FIG. 15).
The control unit 31 records the same contents as the start history information in the occurrence location and occurrence location type of the attendance completion information table 323, and records that the occurrence cause type is a completion from the start history (see FIG. 15). Also, the status type is recorded to the effect that the user is waiting for personal identification.
This completes the processing for attendance.

Next, the control unit 31 starts processing for clocking out.
If the attendance information indicates that the employee has already clocked out, or if the work schedule information indicates that the employee is not scheduled to come to work (step S109, No), the process for clocking out is not performed. If the employee is scheduled to come to work but has not clocked out (step S109, Yes), the process proceeds to the next step S110.

In this example, the attendance information table 321 (Figure 9) does not contain clock-out data for "Person = 004, Date = 2020/6/1", so the control unit 31 extracts startup history data to be used to complement the unstamped attendance information for the missing clock-out punch (step 110).

In this embodiment, if there are still launch history search targets to be checked (step S110, Yes), launch history information that matches the search target is obtained from the launch history information for that individual on the relevant day (step S111).

For example, for clocking out, in step S103, startup history search target data with the condition "Attendance category = clocking out, not telework" for "Sequence No. = 3" is obtained, so a search is performed using search target 1's "Type: PC, Event: Logoff." As a result, the following data is obtained from the startup history information table 322 (see FIG. 8): "Individual = 004, Date = 2020/6/1, Time = 21:15, Event = Logoff, Location = PC4, Location type = PC."

Next, if the person plans to leave work on time, the work shift is extracted from the schedule information for that day, the work shift information is acquired, and it is determined whether there is an activation history within the range of the leaving time (end of work time to start of overtime work).If the person plans to work overtime, the overtime notification data is extracted, and it is determined whether there is an activation history within the range of the overtime work time (step S112).
If there is no such object (step S112, No), the presence or absence of a search object of the next priority is confirmed, and a series of loops are continued until there is no search object (step S110, No).

For example, you can see that the data for "Personal = 004, Date = 2020/6/1, Time = 21:15, Event = Logoff, Occurrence location = PC4, Occurrence location type = Computer" is within the range of the off-work time (21:00-21:30).

If there is a start (stop) history during this time period (step S112, Yes), data indicating that the person left work at the time in the start history is added to the attendance record supplementary information table 323 (step S113, FIG. 15). The same contents as the start history information are recorded for the occurrence location and occurrence location type, and the occurrence cause type is recorded as being supplemented from the start history. In addition, the status type is recorded as being awaiting identity verification.

As an example, data indicating that "Individual=004" clocked out on "Date=2020/6/1, Time=21:15" is added to the attendance supplementary information table 323. Figure 15 shows an example of the attendance supplementary information table with the data added. This data is stored in the memory unit 32 of the management device 3.

This completes the processing for one individual.
If there are no more individuals who need to be processed (Yes at step S114), the process flow is completed.

As described above, by generating complementary information using the startup history from the business device 1, it is possible to reduce the management work required when a missed entry occurs. In addition, the search target (type of startup history) and acquisition priority of the startup history information data acquired for data complementation are set and used according to conditions such as the working status of the employee, so that conditions that match the actual working conditions can be appropriately set and operation can be carried out.

(Reflection in attendance information)
Next, a process performed by the management device 3 after the time attendance complementary information generating unit 313 updates the time attendance complementary information table 323 will be described.

The process of generating attendance supplementary information is assumed to be mainly performed automatically by the management device 3. If the information is confirmed as it is, it may be an unintended result for the worker, and inconvenience may occur. Therefore, the operation of the work management system 10 is to carry out confirmation work and, if necessary, correction work, before carrying out the process of confirming the attendance information.

The attendance complementary information determination unit 314 of the management device 3 searches the attendance complementary information table 323 for the previous day or earlier for which processing by the attendance complementary information generation unit 313 has been completed, and obtains data that matches the condition of "status type = waiting for identity verification".
In the example of the attendance supplementary information table 323 shown in Figure 15, the data that matches is "Individual = 004, Date = 2020/6/1, Attendance category = Clock-out", so the control unit 31 refers to the employee information table 325 (Figure 7) and sends a confirmation request email to the email address of "Individual = 004".

Figure 16 is an example of a confirmation request email sent to the employee.

Individual = 004 receives the email on business device 1, clicks on the URL for accessing the work management system 10 included in the body of the email, and enters the login ID and password for the work management system 10 on the screen that is displayed, which makes a request to the management device 3 to update the attendance information.
The management device 3 obtains the attendance information for the target period for individual=004, generates a Web page, and sends it back to the business device 1. Specifically, the attendance information for the display target period is obtained from the attendance information table, and a Web page is generated in which the missing portions are filled with the attendance supplementary information.

Figure 17 shows an example of a confirmation request screen sent to business device 1.

When you click on the "Date = 2020/6/1" and "Leave work time = 21:15" section, which has an "*" added to it to indicate that identity verification is required, a request is made to the management device 3 to proceed with the data completion process, and the following web page is displayed in a pop-up.

FIG. 18 is an example of the pop-up screen displayed on the business device 1.
Based on the contents of the corresponding attendance supplementary information data, information regarding the circumstances surrounding the time of departure (supplemented from the startup history of PC4 on the same day) is provided, and the person in question is then asked to confirm that there are no problems.
When individual=004 presses "Confirm OK", a processing request is made to the management device 3, and data indicating that the person clocked out at the time in the startup history is added to the attendance information table 321. The location and type of occurrence are recorded as the same as the startup history information, and the type of cause of occurrence is recorded as being a supplement from the startup history.
In addition, the status type is recorded as "personal identity verification has been completed." At the same time, the status type of the time attendance supplementary information table 323 is recorded as "personal identity verification has been completed." Fig. 19 shows an example of the time attendance information table 321 to which the above data has been added.

On the other hand, when "Submit Notification" is pressed on the pop-up screen shown in FIG. 18, a notification application screen as shown in FIG. 20 is displayed on the business device 1 as a pop-up.
In the above example, since the time of leaving work and the reason for leaving are inputtable and required fields, Individual=004 inputs the time to be changed and the reason for leaving. Here, the time may be input directly, or a list of the start-up history information for the corresponding day may be extracted and displayed so that it can be selected as an input candidate.
After inputting the information, the user clicks "Apply" to request the management device 3 to proceed with the process of changing the clock-out time. The requested time-stamp is confirmed after approval by the work manager or supervisor, the data is added to the attendance information table, and the status type item is updated to "Approved by administrator."

By carrying out the above-mentioned confirmation process, employees can confirm and correct the recorded clock-in/clock-out data in the correct procedure without having to perform complicated operations. This allows the employment manager to properly carry out monthly payroll management and downstream business management tasks based on the correctly confirmed data.

As described above, according to this embodiment, even if a time stamp is forgotten on the work management device (time recorder), the startup history information of the business device 1, which indicates the work status of the worker, can be used as attendance information, thereby reducing the amount of correction work such as applications and the administrative work required by the work staff, and enabling proper labor management.

The management device 3 is also configured to use the data generated by the attendance supplementary information generation unit 313 to execute a process to have the worker or manager check the unstamped attendance information with missing punches. In this way, the attendance supplementary data generated by the management device 3 can be reflected in the attendance information upon confirmation by the worker or manager, allowing appropriate business processing and reducing management workload.

The management device 3 is also configured to set the type of startup history and acquisition priority to be used to complement unstamped attendance information with missing punches, depending on conditions such as the employee's working conditions. This allows the method of extracting startup history to be set depending on the employee's working conditions, etc., so that the time stamp complement process can be carried out appropriately.

[Other embodiments]
FIG. 21 is a configuration diagram of an employment management system 100 according to another embodiment of the present invention.
Hereinafter, configurations different from the first embodiment will be mainly described, and configurations similar to those in the first embodiment will be denoted by the same reference numerals, and descriptions thereof will be omitted or simplified.

In recent years, teleworking has become widespread, and the number of cases where work is done outside the company is increasing. In Fig. 21, the area above the dashed line represents the company's internal network, and the area below the dashed line represents the external network.
When working remotely, a VPN (Virtual Private Network) is used to connect to the company's internal network from an external location such as home via the Internet. In detail, the configuration includes a firewall and a VPN server, but these are omitted for the sake of simplicity.

When a business device 4 installed outside the company is used as a VPN client, a VPN connection application is started and an authentication ID and password are entered, authentication is received from the VPN server, and the business device 4 is connected to the intranet.
Using a remote desktop, the user remotely operates the in-house business device 1 from the external business device 4 to perform tasks. In this way, a method is adopted that prevents confidential data from being taken outside the company, maintains security, and allows users to access in-house resources and perform tasks efficiently.

However, in the configuration of FIG. 21, the work management device 2 is not installed on an external network, and clock-in and clock-out cannot be recorded during telework work.
In practice, people often switch between telework and office work depending on the day, so properly obtaining and collecting arrival and departure times can be a challenge.

In the above case, when obtaining the arrival and departure times, the business device 4 transmits startup history information of login and logoff to the VPN network in a format as shown in Figure 22 as time information regarding the start and end of work, and the management device 3 imports it.
In this way, the attendance/leave complementary information generating unit 313 can record attendance times and leave times according to the actual work situation.

In addition, for attendance complementary information data that is in a waiting for identity verification status and has occurred without the employee's own operation, the attendance complementary information confirmation unit 314 of the management device 3 prompts the employee to verify his/her identity and, if necessary, submits an application for correction, thereby confirming the attendance information in an appropriate process.

As mentioned above, even if the work management device 2 cannot be used due to telework or other work styles, the clock-in/clock-out time-stamp collection can be performed properly without the need to install and operate new software for network time recorders, improving convenience.

As described above, according to the working management system of the present invention, the start-up end time of the business device can be used to supplement the time when the clock-in/clock-out is forgotten. Since the time can be used considering the work shift and overtime schedule, the clock-in/clock-out time that is close to the actual work situation can be automatically generated, and the management workload of the working manager can be reduced.
In addition, the status of the confirmation of attendance information can be managed and confirmation work can be performed, allowing for more appropriate work management.

[Modification]
In the above embodiment, the startup history information used to complete unstamped attendance information with missing time stamps has been described by taking as an example the startup history information of the business device 1 and the startup history information of network login/logoff, but is not limited to this. For example, by using various time data related to work associated with an individual, such as the time of entering and leaving a facility, the on/off time of lighting equipment (such as a personal desk lamp), the on/off time of security equipment, the time of passing through a ticket gate for public transportation, and the time of getting on and off a company bus, it is possible to perform a time stamp completion process that is suited to the actual work situation.

On the other hand, the management device 3 may be configured to execute an estimation process of the arrival and departure times when there is no startup history to be used to complement the unpunched attendance information with missing punches. For example, complementary data for the unpunched attendance information may be generated from the day's work schedule (or work shift), past attendance information, or attendance information of another employee who belongs to the same department and worked the same shift on the day.

A typical example is a case where a worker alternates between office work and telework on a daily basis. Even if the PC logoff time used during office work is used to complete clock-in time when clock-out time is forgotten, if the next day is telework and requires an external VPN network connection, the worker may leave the office the day before teleworking without logging off the company's PC. In such cases, the log-off time is not recorded, and clock-in time cannot be completed when clock-in time is forgotten. As a solution, the system detects missed clock-in time-outs on office work days, and even if there is no PC log-off time to complete clock-in time, if the next day is a telework day, it is assumed that the worker left the office at regular time the previous day, and generates supplementary data for unclocked-in/out information using the regular end time.

In addition, data on past cases of forgetting to clock in and out can be accumulated and used as learning data to perform machine learning to estimate arrival and departure times.

The technology of the present invention can be suitably used in work management systems in environments where work is carried out using information terminals such as personal computers.

1... Business device 2... Work management device 3... Management device 4... Business device 10... Work management system 11... Control unit 12... Memory unit 13... Display unit 21... Control unit 22... Memory unit (first memory unit)
23: Display unit 26: Clock unit 27: Operation input unit 28: Operator information input unit 31: Control unit 32: Storage unit (second storage unit)
33: Display unit 111: Start history information transmission unit 211: Worker recognition unit 212: Display control unit 213: Punch information generation unit 214: Time attendance punch information transmission unit 311: Time attendance information recording unit 312: Start history information recording unit 313: Time attendance complementary information generation unit 314: Time attendance complementary information determination unit

Claims (10)

Business equipment used by the employee for business purposes;
An employment management device operated by an employee;
A management device capable of communicating with the business device and the work management device,
the business device has a startup history information transmission unit that transmits startup history information relating to an activated state and a non-activated state to the management device;
The work management device includes:
The clock section and
A first storage unit that stores worker identification information that identifies a worker;
a time-stamp information generating unit that generates, when an employee inputs the employee identification information and stamps the employee, the time acquired from the clock unit and information indicating the employee as time-stamp information;
and a time-stamp information transmitting unit that transmits the time-stamp information to the management device,
The management device includes:
A second storage unit;
a boot history information recording unit that records the boot history information transmitted from the business device in the second storage unit;
a time-stamping information recording unit that records the time-stamping information transmitted from the work management device in the second storage unit;
a time-stamped information generating unit for detecting the presence or absence of unstamped time-stamped information from the time-stamped information recorded in the second storage unit, and generating data for supplementing the unstamped time-stamped information based on the start-up history information recorded in the second storage unit when the unstamped time-stamped information is detected ,
The clock-in/clock-out complementary information generating unit is configured to change the type of start-up history and the acquisition priority order used to complement the unstamped clock-in/clock-out information according to the working conditions of the workers.
Employment management system. The work management system according to claim 1,
The management device further includes an attendance supplementary information determination unit that executes a process to have the worker or a manager confirm the unstamped attendance information using the data generated by the attendance supplementary information generation unit. The work management system according to claim 1 ,
The attendance complementary information generating unit is configured to execute an estimation process of attendance times when there is no start-up history to be used for complementing the unclocked attendance information. The work management system according to claim 1 ,
The attendance supplementary information generating unit is configured to use various types of time data related to work as start-up history information used to supplement the unstamped attendance information. transmitting activation history information regarding activation and deactivation states from the business devices used by the employees for business purposes to the management device;
A working management device operated by the worker transmits time stamp information including a time stamp and information indicating the worker to the management device;
The management device records the start-up history information transmitted from the business device in a storage unit, records the clock-in/clock-out information transmitted from the work management device in the storage unit, detects whether or not there is unpunched clock-in/clock-out information with missing clock-in/clock-out information from the clock-in/clock-out information, and when the unpunched clock-in/clock-out information is detected, generates data for complementing the unpunched clock-in/clock-out information based on the start-up history information , and changes the type of start-up history and acquisition priority order used to complement the unpunched clock-in/clock-out information according to the conditions of the worker's working situation.
Employment management methods. The work management method according to claim 5 ,
The management device further executes a process of having the worker or a manager confirm the unpunched attendance information using the generated data that complements the unpunched attendance information . The work management method according to claim 5 ,
The management device executes an estimation process of arrival and departure times when there is no startup history to be used for complementing the unpunched arrival and departure information. The work management method according to claim 5 ,
The management device uses various time data related to work as start-up history information used to complement the unstamped attendance information. A management device capable of communicating with a business device used by an employee for work and an employment management device having a clock unit and operated by the employee,
The management device includes:
A storage unit;
a startup history information recording unit that records startup history information regarding an activated state and a non-activated state transmitted from the business device in the storage unit;
a time attendance information recording unit that records the time acquired from the clock unit and information indicating the worker as time attendance punch information in the memory unit when the worker inputs the worker identification information that identifies the worker and punches in the worker identification information transmitted from the work management device;
a time-stamped information generating unit that detects whether there is any unstamped time-stamped information from the time-stamped information recorded in the storage unit, and when the unstamped time-stamped information is detected, generates data for supplementing the unstamped time-stamped information based on the start-up history information recorded in the storage unit;
having
The clock-in/clock-out complementary information generating unit is configured to change the type of start-up history and the acquisition priority order used to complement the unstamped clock-in/clock-out information according to the working conditions of the workers.
Management device. The management device:
A step of recording attendance information including a time stamp and information indicating the worker, the time stamp being transmitted from a work management device operated by the worker;
A step of recording activation history information regarding an activated state and an inactivated state transmitted from a business device used by an employee for business;
A step of detecting whether there is any unstamped clock-in/clock-out information with missing clock-in/clock-out information from the clock-in/clock-out information;
generating data for complementing the unpunched attendance information based on the start history information when the unpunched attendance information is detected ;
changing the type of start history used to complement the unstamped attendance information and the acquisition priority order according to the working conditions of the worker;
A program that executes the following.

Images