JP7779679B2 - Vacation management device, vacation management method, and vacation management program - Google Patents

Description

The present invention relates to a vacation management device, a vacation management method, and a vacation management program.

As background technology related to vacation management, Patent Document 1 (JP 2020-112979 A) discloses a time management system that constantly manages work status. In this time management system, the server device of the time management system, which records and manages the work time for each work item input from a terminal device, is equipped with a time management means, a work item management means, a recording means, and a report output means.

The time management means acquires the number of units of work time sent from the terminal device, which is a predetermined unit of time, for each worker, and records the work time for each work item from the acquired number of units for each worker. The work item management means records the work items sent from the terminal device for each worker. The shared recording means records the information acquired for each worker so that it can be shared with other workers. The report output means then outputs a report in a format specified by the terminal device based on the recorded information.

This type of time management system does not manage time precisely down to the minute, but rather divides time into blocks, allowing for human ingenuity and contributing to improved productivity through continuous time management.

Japanese Patent Application Laid-Open No. 2020-112979

Today, there are various employment types, including full-time employees, temporary workers, contract employees (fixed-term employment contracts), and part-time workers. Furthermore, there are various working styles, including regular work, day shifts, night shifts, rotating shifts, part-time work, and reduced hours. There are also various types of vacation, including annual paid leave, compensatory leave, nursing care leave, caregiver leave, special leave for special occasions, and sick leave. While it is common for vacation to be taken in daily or half-day increments today, it is expected that in the future, different types of vacation will be available for different workers. Therefore, it is desirable to enable vacation management that can accommodate the various types of vacation that may be available in the future.

The present invention has been made in light of the above, and aims to provide a vacation management device, a vacation management method, and a vacation management program that enable flexible vacation management in response to various types of vacation acquisition.

In order to solve the above-mentioned problems and achieve the object, the leave management device of the present invention refers to a storage unit that stores whether each type of leave can be taken in hourly units and the unit of leave taken, between full-day, half-day, and hourly, set for each type of leave, and determines whether the type of leave applied for in a leave application is one that allows leave to be taken in hourly units. If the type of leave applied for in a leave application is one that allows leave to be taken in hourly units, the device multiplies the number of leave days that the leave taker can take by the number of working hours in one day that is set in accordance with the leave taker's employment type to form total leave time by converting the number of leave days granted to the leave taker into hours. If the device determines that the type of leave applied for in an leave application does not allow leave to be taken in hourly units, the device multiplies the number of leave days by the number of working hours in one day, which is a fixed number of hours, to form total leave time. If the employment type of the leave taker changes , the device calculates the total leave time using the working hours in accordance with the changed employment type. a remaining vacation time calculation unit that calculates remaining vacation time by subtracting the vacation time taken from the total vacation time and calculates the remaining vacation time after the change in employment type by subtracting the vacation time taken after the change in employment type from the total vacation time after the change in employment type; a remaining vacation allocation processing unit that, when a vacation taker applies for another vacation before the planned date of the vacation they are planning to take, determines whether the vacation time taken for the applied for vacation and the vacation time taken for the vacation they are planning to take exceed the remaining vacation time and generates allocation error data if the remaining vacation time exceeds; an allocation error determination unit that determines whether there is allocation error data for the application for the interrupted vacation and, if allocation error data has been generated, outputs a specified error message together with the number of days and time exceeded; and a career revision processing unit that updates vacation entitlement data including the remaining vacation time before the change in employment type to vacation entitlement data including the remaining vacation time after the change in employment type .

In order to solve the above-mentioned problems and achieve the object, the vacation management method of the present invention has a vacation time conversion processing section that refers to a storage section that stores information on whether each type of vacation can be taken in hourly units and the unit of leave taken, among full-day, half-day, and hourly units, set for each type of vacation, and determines whether the type of vacation requested in the vacation application is a type of vacation that can be taken in hourly units, and if the type of vacation requested in the vacation application is a type of vacation that can be taken in hourly units, multiplies the number of vacation days that the vacation taker can take by the number of working hours in one day that is set according to the employment type of the vacation taker. a vacation time conversion processing step in which a vacation acquisition time conversion processing unit converts the vacation period applied for by the vacation taker into vacation acquisition time based on the daily working hours set according to the employment type of the vacation taker, and converts the number of vacation days granted to the vacation taker into hours to form total vacation time, and if it is determined that the type of vacation does not allow acquisition in hourly units, forms total vacation time, and if the employment type of the vacation taker is changed, calculates the total vacation time based on the working hours according to the changed employment type ; a vacation acquisition time conversion processing step in which a vacation acquisition time conversion processing unit converts the vacation period applied for by the vacation taker into vacation acquisition time based on the daily working hours set according to the employment type of the vacation taker, and if the employment type of the vacation taker is changed, converts the period based on the working hours according to the changed employment type; a remaining vacation time calculation step in which a remaining vacation time calculation unit calculates remaining vacation time by subtracting the vacation acquisition time from the total vacation time , and calculates remaining vacation time after the change in employment type by subtracting the vacation acquisition time after the change in employment type from the total vacation time after the change in employment type; and a remaining vacation time calculation step in which a vacation remaining allocation processing unit converts the vacation period applied for by the vacation taker before the planned date of the vacation that the vacation taker is scheduled to take, into vacation acquisition time based on the working hours after the change in employment type. The system has a remaining vacation allocation step that determines whether the vacation time taken for vacation and the vacation time taken for vacation that is planned to be taken exceeds the remaining vacation time, and generates allocation error data if the remaining vacation time is exceeded; an allocation error determination step in which an allocation error determination unit determines whether or not there is allocation error data for an application for vacation interruption, and if allocation error data has been generated, outputs a predetermined error message together with the number of days and time exceeded; and a career revision processing step in which a career revision processing unit updates vacation grant data including the remaining vacation time before the change in employment type to vacation grant data including the remaining vacation time after the change in employment type .

Furthermore, in order to solve the above-mentioned problems and achieve the object, a leave management program according to the present invention includes a computer that references a storage unit that stores information on whether each type of leave can be taken in hourly units and the units of leave taken, among full-day, half-day, and hourly units, set for each type of leave, to determine whether the type of leave applied for in a leave application allows for leave to be taken in hourly units; if the type of leave applied for in a leave application allows for leave to be taken in hourly units, the program multiplies the number of leave days available to the leave taker by the number of working hours in one day set in accordance with the leave taker's employment type to form total leave time by converting the number of leave days granted to the leave taker into hours; if the program determines that the type of leave applied for in an leave application does not allow for leave to be taken in hourly units, the program multiplies the number of leave days by the number of working hours in one day, which is a fixed number of hours, to form total leave time; and if the employment type of the leave taker changes, calculates the total leave time using the working hours in accordance with the changed employment type ; and a leave time conversion processing unit that converts the leave period applied for by the leave taker into the number of working hours in accordance with the changed employment type. The system includes a vacation time conversion processing unit that converts vacation time into vacation time based on working hours in minutes, and when the employment type of the vacation taker is changed, converts the converted vacation time based on the working hours according to the changed employment type ; a remaining vacation time calculation unit that calculates remaining vacation time by subtracting vacation time from total vacation time , and calculates remaining vacation time after the change in employment type by subtracting vacation time after the change in employment type from total vacation time after the change in employment type; a remaining vacation allocation processing unit that, when a vacation taker applies for another vacation before the planned date of the vacation they are planning to take, determines whether the vacation time of the applied for vacation and the vacation time of the vacation they are planning to take exceed the remaining vacation time, and generates allocation error data if the remaining vacation time exceeds; an allocation error determination unit that determines whether allocation error data exists for the application for the vacation interruption, and if allocation error data has been generated, outputs a predetermined error message together with the number of days and time exceeded; and a career revision processing unit that updates vacation grant data including remaining vacation time before the change in employment type to vacation grant data including remaining vacation time after the change in employment type .

The present invention has the advantage of enabling flexible vacation management in response to various vacation acquisition patterns.

FIG. 1 is a block diagram of a vacation management device according to an embodiment. FIG. 2 is a diagram showing an example of taking annual paid leave, child care leave, and family care leave. FIG. 3 is a schematic diagram of the vacation remaining management classification master. FIG. 4 is a schematic diagram of the vacation type master. FIG. 5 is a schematic diagram of the employee classification setting master. FIG. 6 is a schematic diagram of the working hours master. FIG. 7 is a schematic diagram of the employee master. FIG. 8 is a schematic diagram of the employee history DB. FIG. 9 is a flowchart showing the flow of the process of granting annual paid leave. FIG. 10 is a flowchart showing the flow of the process for granting leave other than annual paid leave. FIG. 11 is a flowchart showing the flow of an employee's vacation acquisition process. FIG. 12 is a flowchart showing the flow of the operation for changing the predetermined time (working hours) due to a change in the employment type or status of an employee. FIG. 13 is a flowchart showing the flow of vacation application processing by an employee after the employee classification has been changed. FIG. 14 is a diagram for explaining the operation of granting annual paid leave. FIG. 15 is a diagram for explaining another vacation granting operation. FIG. 16 is a diagram showing the types of leave, remaining leave time, and leave acquisition status of employee A. FIG. 17 is a diagram illustrating an example of vacation remaining allocation data. FIG. 18 is a diagram showing how remaining vacation allocation data is generated in response to vacation acquisition. FIG. 19 is a diagram illustrating an example of vacation remaining allocation data. FIG. 20 is a diagram for explaining parameters acquired by the vacation balance allocation processing unit when allocating vacation balance. FIG. 21 is a diagram illustrating an example of vacation remaining allocation data. FIG. 22 is a diagram for explaining the operation of generating allocation candidate data. FIG. 23 is a diagram illustrating an example of vacation remaining allocation data. FIG. 24 is a diagram illustrating an example of the allocation candidate assignment data. FIG. 25 is a diagram for explaining the operation of generating allocation calculation target data. FIG. 26 is a diagram for explaining the initialization of allocation error data and the acquisition operation of allocation calculation target data. FIG. 27 is a diagram for explaining the operation of acquiring allocation candidate data. FIG. 28 is a diagram for explaining the process of adding remaining vacation allocation data. FIG. 29 is a diagram for explaining the update process of the allocation calculation target data and the allocation candidate assignment data. FIG. 30 is a diagram for explaining an error that occurs after a vacation interruption request. FIG. 31 is a diagram for explaining the operation of generating allocation error data. FIG. 32 is a diagram for explaining the division and allocation process. FIG. 33 is a diagram for explaining the update process of the allocation candidate assignment data and the allocation calculation target data. FIG. 34 is a diagram for explaining the processing of spontaneously extinguished records. FIG. 35 shows an example of an error message displayed when there is an insufficient vacation balance. FIG. 36 is a diagram showing an example of a vacation application. FIG. 37 is a diagram for explaining a check by the allocation error determination unit for a shortage of remaining vacation time. FIG. 38 is a diagram for explaining a specific example of how the allocation error determination unit checks for a shortage of remaining vacation time. FIG. 39 is a diagram for explaining the operation of generating vacation acquisition data. FIG. 40 is a diagram for explaining the operation of checking an allocation error. FIG. 41 is a diagram showing an example of vacation remaining allocation data. FIG. 42 is a diagram for explaining the operation of changing the employment type or status of an employee. FIG. 43 is a diagram for explaining the processing of nursing leave after the employee classification change processing is completed.

The following describes in detail a vacation management device, an embodiment of the present invention, with reference to the drawings. Note that the present invention is not limited to this embodiment.

[Hardware configuration]
First, Fig. 1 is a block diagram of a vacation management device according to an embodiment. As shown in Fig. 1, the vacation management device 1 according to the embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5. An input device 6 such as a keyboard and a mouse is connected to the input/output interface unit 5. An output device 7 such as a monitor is also connected to the input/output interface unit 5. The communication interface unit 4 is connected to a terminal device 9 of an employee or the like via a predetermined network 8. The network 8 may be, for example, a private network such as an in-house LAN (Local Area Network) or a wide area network such as the Internet.

The memory unit 2 contains a vacation balance management category master 11, a vacation type master 12, an employee category setting master 13, a work hours master 14, an employee master 15, and an employee history database (employee history DB) 16. The memory unit 2 also stores a vacation management program, vacation grant data, vacation acquisition data, vacation balance allocation data, allocation candidate grant data, allocation calculation target data, and allocation error data. Details of each master and data will be provided below.

By executing the vacation management program stored in the memory unit 2, the control unit 3 realizes the functions of the display control unit 21, input processing unit 22, update processing unit 23, vacation balance determination unit 24, vacation balance allocation processing unit 25, allocation error determination unit 26, employee classification change processing unit 27, and career revision processing unit 28. Each of these functions will be described later. The vacation balance allocation processing unit 25 is an example of a vacation time conversion processing unit, vacation acquisition time conversion processing unit, and remaining vacation time calculation unit.

[Image of taking vacation time]
As an example, Figure 2 shows how annual paid leave, child care leave, and family care leave can be acquired. The number of days of annual paid leave granted varies depending on the number of years or months of service, and is valid for two years, with a total of 40 days granted per year. In addition, any remaining days of annual paid leave from the previous year can be carried over to the following year.

Child care leave is granted for five days per year if there is one eligible child, and ten days per year if there are two or more eligible children. Nursing care leave is granted for five days per year if there is one eligible person requiring care, and ten days per year if there are two or more eligible people requiring care. Child care leave and nursing care leave expire on the last day of the fiscal year and are newly granted on the first day of the fiscal year.

Annual paid leave, child care leave, and family care leave can be taken in the form of full-day leave, half-day leave, or hourly leave, respectively.

[Vacation Remaining Management Category Master]
Next, Figure 3 shows a schematic diagram of the vacation balance management category master 11. The vacation balance management category master 11 is a master that controls the types of vacation that are subject to vacation balance management and whether or not they can be taken in hourly units. The vacation balance management category master 11 stores the remaining management category, the remaining management category name, and whether or not they can be taken in hourly units. Annual paid vacation is annual paid vacation granted in the paid vacation granting process, and the remaining management category is "1", meaning that it can be taken in hourly units (yes). Compensatory vacation is vacation granted in place of overtime pay for working on a holiday, and the remaining management category is "2", meaning that it cannot be taken in hourly units (no).

Caregiver leave is leave based on the carer leave system, and the remaining management category is "5", meaning that it can be taken in hourly units. Nursing care leave is leave based on the child nursing care leave system, and the remaining management category is "6", meaning that it can be taken in hourly units. Compensatory holidays (regular holidays) are compensatory holidays when an employee works a substitute shift on a regular holiday, and the remaining management category is "7", meaning that it cannot be taken in hourly units.

Compensatory holidays (statutory holidays) are compensatory holidays when employees work on statutory holidays, and their remaining management category is "8," meaning they cannot be taken in hourly units. Saved paid leave 1 is leave that companies adopt at their discretion (leave when expired leave is accumulated after exceeding the annual paid leave limit or deadline), and their remaining management category is "9," meaning they can be taken in hourly units. Saved paid leave 2 is leave that companies adopt at their discretion (leave when expired leave is accumulated after exceeding the limit or deadline for saved paid leave 1), and their remaining management category is "10," meaning they can be taken in hourly units.

[Vacation type master]
Next, Figure 4 shows a schematic diagram of the leave type master 12. The leave type master 12 is a master that manages combinations of leave type, acquisition unit (all day/first half/second half/hour), and remaining management category. That is, this leave type master 12 stores information indicating that annual paid leave with a remaining management category of "1" can be acquired as all-day paid leave, first half paid leave, second half paid leave, or hourly paid leave. The leave type master 12 also stores information indicating that family care leave with a remaining management category of "5" can be acquired as all-day, first half, second half, or hourly.

[Employee classification setting master]
Next, FIG. 5 shows a schematic diagram of the employee category setting master 13. The employee category setting master 13 is a master for controlling the treatment of employees based on differences in employment type and status, and the "equivalent daily prescribed hours" is set as the number of minutes when one day is converted into paid vacation time. As an example, for a full-time employee working a regular shift, the employee category setting master 13 stores an equivalent daily prescribed hours of "480 minutes" based on an eight-hour work day. For a reduced-hours employee working a reduced-hours shift, the employee category setting master 13 stores an equivalent daily prescribed hours of "300 minutes" based on a five-hour work day. For a part-time employee working a part-time shift, the employee category setting master 13 stores an equivalent daily prescribed hours of "240 minutes" based on a four-hour work day.

[Predetermined time master]
Next, FIG. 6 shows a schematic diagram of the work hour master 14. The work hour master 14 is a master that manages work hours and rest periods for each work style. The work hour master 14 stores predetermined work hours and other information used for calculating overtime hours, etc. For example, for a regular shift work style, the work hour master 14 stores the work start time and work end time (9:00 to 17:45), the 465-minute work hours (525 minutes, the corresponding working time, minus a 60-minute rest period), and the 60-minute rest period. For a part-time shift work style, the work hour master 14 stores the work start time and work end time (11:00 to 15:45), the 240-minute work hours (285 minutes, the corresponding working time, minus a 45-minute rest period), and the 45-minute rest period.

[Employee Master]
7 is a schematic diagram of the employee master 15. The employee master 15 is a master that manages the attributes of each employee. The employee master 15 stores the employee code, employee name, and employee classification, such as full-time employee, part-time employee, or casual employee, for each employee.

[Employee history DB]
Next, Figure 8 shows a schematic diagram of the employee history DB 16. The employee history DB 16 stores data for managing the attribute history for each employee. Specifically, the employee history DB 16 stores employee code, attribute classification such as employee category, career start date, career end date, and career attributes such as full-time employee or part-time employee. This data in the employee history DB 16 is rewritten when an attribute in the employee master 15 is changed.

[Annual paid leave grant processing]
Next, the process for granting annual paid leave will be explained using the flowchart in Figure 9. When granting annual paid leave, for example, a labor manager operates the leave management device 1 to display the leave grant data stored in the memory unit 2 on the output device 7 (step S1). The control unit 3 of the leave management device 1 operates based on the leave management program, and the input processing unit 22 and display control unit 21 read the leave grant data from the memory unit 2 in response to the input operation of the labor manager, and display it on the output device 7.

Next, the labor manager operates the input device 6 to input annual paid leave entitlement information (step S2). The input processing unit 22 acquires the input leave entitlement information. The update processing unit 23 updates the leave entitlement data in the memory unit 2 based on the input leave entitlement information (step S3).

Next, the vacation balance allocation processing unit 25 associates (allocates) the vacation grant data with the vacation acquisition data, creates vacation balance allocation data, and stores it in the memory unit 2 (step S4). The detailed operation of this vacation balance allocation process will be described later.

[Other leave granting process]
Next, the process for granting leave other than annual paid leave will be described using the flowchart in Figure 10. When granting other leave, for example, a labor manager operates the leave management device 1 to display the leave grant data stored in the memory unit 2 on the output device 7 (step S11). The control unit 3 of the leave management device 1 operates based on the leave management program, and the input processing unit 22 and display control unit 21 read the leave grant data from the memory unit 2 in response to the input operation of the labor manager, and display it on the output device 7.

Next, the labor manager operates the input device 6 to input vacation grant information for the vacation to be granted (step S12). The input processing unit 22 acquires the input vacation grant information. The update processing unit 23 updates the vacation grant data in the memory unit 2 based on the input vacation grant information (step S13).

Next, the vacation balance allocation processing unit 25 associates (allocates) the vacation grant data with the vacation acquisition data, creates vacation balance allocation data, and stores it in the memory unit 2 (step S14). The detailed operation of this vacation balance allocation process will be described later.

[Employee leave taking behavior]
Next, the process of an employee taking vacation will be described using the flowchart in Figure 11. In this case, the employee operates, for example, their own terminal device 9 to input the application details corresponding to the vacation they wish to take (step S21) and execute the vacation application (step S22). As a result, information indicating the details of the vacation they wish to take (such as the type of vacation and the number of days to be taken) is sent from the employee's terminal device 9 to the vacation management device 1 via the network 8.

The control unit 3 of the vacation management device 1 operates based on the vacation management program, and the vacation balance determination unit 24 checks the vacation balance insufficiency based on the vacation acquisition data (step S23). This check of the vacation balance insufficiency is a check to see whether there is an insufficient amount of vacation available at the time the vacation is requested. This check of the vacation balance insufficiency can be performed in advance, before the vacation balance allocation process (step S25) is executed, and is therefore performed before the vacation acquisition data update process (step S24).

If the vacation balance determination unit 24 determines that there is an insufficient vacation balance (there is an insufficiency), the control unit 3 sends an error notification to the employee's terminal device 9 via the communication interface unit 4, indicating that the vacation application will be rejected due to an insufficient vacation balance (step S27).

If the vacation balance determination unit 24 does not determine whether there is a vacation balance deficiency (no deficiency), the update processing unit 23 performs update processing on the vacation acquisition data in the memory unit 2 corresponding to the requested vacation.

Next, the vacation balance allocation processing unit 25 associates (allocates) the vacation grant data with the vacation acquisition data, creates vacation balance allocation data, and stores it in the memory unit 2 (step S25). The detailed operation of this vacation balance allocation process will be described later.

Next, the allocation error determination unit 26 checks for allocation errors due to the vacation remaining allocation process in step S25 (step S26), and if there are no allocation errors, the processing of the flowchart in Figure 11 ends.

This allocation error check is performed to check whether there is sufficient vacation time available at the time the vacation is requested, but if an interruption is taken, a previously requested vacation of the same type for a future date will result in insufficient vacation time due to the vacation expiration date.

Such cases can be detected after the remaining vacation allocation process. For this reason, in the vacation management device 1 of this embodiment, the acquisition is initially approved and the vacation application is made possible. After the vacation acquisition data update process and the remaining vacation allocation process, the allocation error determination unit 26 performs an allocation error check, and if an allocation error is detected, the display control unit 21 displays an allocation error on the output device 7 (step S27). If an allocation error occurs, in the vacation management device 1 of this embodiment, the vacation applied for earlier or later can be changed to a different type of vacation. This will be described in more detail below.

[Processing of changes to specified hours due to changes in employee employment status or status]
Next, the process for changing the specified time (working hours) due to a change in an employee's employment status or status will be described using the flowchart in Figure 12. In this case, the employee classification change processing unit 27 first checks the number of remaining vacation days or vacation hours based on the vacation grant data and vacation acquisition data (step S31). Next, the employee classification change processing unit 27 changes the employee classification of the employee whose classification is being changed from the employee classifications stored in the employee master 15 shown in Figure 7 to a new employee classification (step S32). The employee classification change processing unit 27 also revises (changes) the career history of the employee whose employee classification has been changed, stored in the employee history DB 16 shown in Figure 8 (step S33).

Next, if there is a change in the specified hours (working hours) due to a change in the employee's employment status or status, the career revision processing unit 28 updates the equivalent daily specified hours in the vacation grant data, vacation take data, or vacation remaining allocation data held by the employee. The vacation remaining allocation processing unit 25 then associates (allocates) the vacation grant data with the vacation take data, creates vacation remaining allocation data, and stores it in the memory unit 2 (step S34). Detailed operations of this vacation remaining allocation process will be described later.

[Leave application behavior after employee classification change]
Next, the vacation application process by an employee after changing their employee classification will be explained using the flowchart in Figure 13. As an example, assume that an employee whose employee classification has been changed from a full-time employee to a part-time employee operates the terminal device 9 to apply for vacation (steps S41 and S42). In this case, the vacation balance allocation processing unit 25 associates (allocates) the vacation grant data with the vacation acquisition data, creates vacation balance allocation data, and stores it in the storage unit 2 (step S43). The detailed operation of this vacation balance allocation process will be described later.

[Details of leave granting behavior]
Next, the vacation granting operation explained with reference to FIGS. 9 and 10 will be described in detail.

(Annual paid leave granting operation)
First, the operation of granting annual paid leave explained using Fig. 9 will be described in detail. Fig. 14 is a diagram for explaining the operation of granting annual paid leave. In this case, the update processing unit 23 calculates the number of days of annual paid leave granted based on the number of years and months of service of the grantee, and creates leave grant data based on the number of years of paid leave storage period.

Specifically, Figure 14(a) shows an example of a vacation registration screen displayed on the output device 7 of the vacation management device 1 operated by the labor manager. Based on this vacation registration screen, the labor manager selects "annual paid vacation" as the remaining management category and selects the employee (in this example, Mr. A) to whom annual paid vacation will be granted. Employee A is stored in the employee master 15 as a full-time employee, as shown in Figure 14(b). Furthermore, as shown in Figure 14(c), the employee category setting master 13 stores "daily equivalent hours" indicating that full-time employees work regular shifts and that their daily working hours are 8 hours, or "480 minutes." Furthermore, as shown in Figure 14(d), the vacation remaining management category master 11 stores information indicating whether annual paid vacation can be taken in hourly units, with "yes" registered, indicating that it can be taken in hourly units.

The update processing unit 23 automatically inputs the equivalent daily specified hours into the leave registration screen shown in Figure 14(a) in accordance with the master settings of the employee to whom leave is to be granted. Note that if hourly leave acquisition is registered as "None," such as for "Compensatory Leave" as shown in Figure 14(d), the update processing unit 23 does not automatically input the equivalent daily specified hours into the leave registration screen. In this case, leave acquisition is permitted only in full-day or half-day units. Furthermore, if hourly leave acquisition is registered as "None," the update processing unit 23 fixes working hours to 8 hours for all employees, calculates the equivalent daily specified hours (480 minutes), and inputs this into the leave registration screen.

Next, the update processing unit 23 calculates the "granted hours," which is the amount of annual paid leave corresponding to the number of granted annual paid leave days, by multiplying the number of granted annual paid leave days by the equivalent daily time (480 minutes). The update processing unit 23 then stores the vacation grant data, including the calculated granted hours, in the memory unit 2, as shown in Figure 14(e). In the example of Figure 14(e), the number of newly granted annual paid leave days is 18, so the update processing unit 23 calculates the granted hours as 18 days x 480 minutes = 8,640 minutes, and stores this as part of the vacation grant data.

In the example of Figure 14(e), the remaining number of annual paid leave days granted for the previous year was 16, so 16 days x 480 minutes = 7,680 minutes of granted time is included and stored in the leave grant data. Furthermore, in the case of annual paid leave, the update processing unit 23 sets the start date of the validity period as the grant date, and the end date of the validity period to the number of years after the grant date that the paid leave storage period lasted.

Figure 14 (f) shows an example of annual paid leave granted in this way. The amount carried over from fiscal year 2020 will expire at the end of March 2022, and the 8,640 minutes of annual paid leave granted in April 2021 will be valid until the end of March 2023.

(Other leave granting actions)
Next, the granting of other types of leave besides the annual paid leave explained using Fig. 10 will be described in detail. Fig. 15 is a diagram for explaining the granting of other types of leave. For leave that does not automatically accrue according to specific conditions, such as annual paid leave, the labor manager grants leave via the leave registration screen as needed each time.

Specifically, Figure 15(a) shows an example of a leave registration screen for nursing care leave displayed on the output device 7 of the leave management device 1 operated by the labor manager. Figure 15(b) shows an example of a leave registration screen for family care leave displayed on the output device 7 of the leave management device 1 operated by the labor manager. Based on this leave registration screen, the labor manager selects, for example, nursing care leave (Figure 15(a)) or family care leave (Figure 15(b)) as the remaining management category, and selects the employee (in this example, Mr. A) to whom nursing care leave or family care leave will be granted.

Employee A is stored in the employee master 15 as a full-time employee, as shown in Figure 15(c). Furthermore, as shown in Figure 15(d), the employee classification setting master 13 stores the "equivalent daily hours" indicating that the full-time employee's work style is a regular shift, with a daily working time of 8 hours, or "480 minutes." Furthermore, as shown in Figure 15(e), the remaining vacation management master 11 stores the information "Yes," indicating that nursing leave and family care leave can be taken in hourly units.

The update processing unit 23 automatically enters the equivalent daily specified hours into the leave registration screen shown in Figure 15(a) according to the master settings of the employee to whom leave is granted. Note that if hourly acquisition is set to "None," the update processing unit 23 fixes the working hours to 8 hours for all employees, calculates the equivalent daily specified hours (480 minutes), and enters this into the leave registration screen for nursing care leave (Figure 15(a)) or the leave registration screen for family care leave (Figure 15(b)).

Next, the update processing unit 23 calculates the "granted time" corresponding to the number of days of nursing care leave and family care leave granted by multiplying the number of days of nursing care leave granted by the equivalent daily predetermined time (480 minutes). The update processing unit 23 then stores the leave grant data including the calculated granted time in the storage unit 2, as shown in FIG. 15(f). In the example of FIG. 15(f), the number of days of nursing care leave granted is 10, so the update processing unit 23 calculates 10 days x 480 minutes = 4,800 minutes of granted time and stores this in the leave grant data. In the example of FIG. 15(f), the number of days of family care leave granted is 5 days, so the update processing unit 23 calculates 5 days x 480 minutes = 2,400 minutes of granted time and stores this in the leave grant data.

The update processing unit 23 sets the effective period end date to the date one year after the start date of the current fiscal year, when nursing leave and family care leave are granted. The example in Figure 15 (f) is an example where the grant date and effective period start date are different. For nursing leave granted on May 1, 2021, and family care leave granted on June 1, 2021, the effective period start date is set to April 1, 2021, the start date of the current fiscal year, and the effective period end date is set to March 31, 2022, one year after the effective period start date.

Figure 15(g) is an example of nursing leave and caregiver leave granted in this manner. The example in Figure 15(g) is an example of nursing leave granted on May 1, 2021 for 10 days, totaling 4,800 minutes, with the effective period starting on April 1, 2021 and ending on the end of March 2022. Also, the example in Figure 15(g) is an example of nursing leave granted on June 1, 2021 for 5 days, totaling 2,400 minutes, with the effective period starting on April 1, 2021 and ending on the end of March 2022.

[Leftover Allocation Processing]
Next, we will explain the remaining vacation allocation process, which is the process of step S4 in Figure 9, step S14 in Figure 10, step S25 in Figure 11, and step S34 in Figure 12. First, Figure 16 shows the vacation type, remaining vacation time, and vacation acquisition status of employee A. The example in Figure 16(a) shows an example in which 7,680 minutes of annual paid vacation, equivalent to 16 days, was granted on April 1, 2020. As shown in Figure 16(b), the first half of the paid vacation was taken on March 10, 2021, resulting in 6,900 minutes of the paid vacation for the current fiscal year being taken, and the remaining 780 minutes (1.5 days + 1 hour) being carried over to the next fiscal year. The example in Figure 16(a) also shows an example in which 8,640 minutes of annual paid vacation, equivalent to 18 days, was newly granted on April 1, 2021, and 4,800 minutes of nursing leave, equivalent to 10 days, was granted on May 1, 2021.

With such remaining vacation time and vacation usage status, if there is a vacation scheduled to be taken after the start date of the validity period of annual paid vacation or other vacation, the order in which vacation is taken may change. For this reason, the remaining vacation allocation processing unit 25 executes the remaining vacation allocation process described below based on the "validity period end date" and "validity period start date" of the vacation. This allows vacation with an earlier expiration date to be taken first when revising the career history, as described below.

The vacation balance allocation processing unit 25 associates (allocates) the vacation grant data and vacation acquisition data stored in the memory unit 2 to create "vacation balance allocation data." The vacation balance allocation data subtracts the remaining vacation time taken from the vacation grant data, making it possible to check the remaining time taking into account the expiration date. Figure 17 is a diagram showing an example of vacation balance allocation data. Figures 17(a) and 17(b) show a series of vacation balance allocation data that are continuous row-wise. Figure 17(c) shows an example of vacation balance allocation data that are continuous column-wise with the vacation balance allocation data in Figure 17(a). Figure 17(d) shows an example of vacation balance allocation data that are continuous column-wise with the vacation balance allocation data in Figure 17(b).

As shown in Figures 17(a) and 17(c), the remaining vacation allocation data includes allocation key information including an allocation identification number (allocation ID), employee code, and remaining management category, and vacation grant data including an grant ID, grant date, validity period start date, validity period end date, granted time, and daily equivalent hours. Furthermore, as shown in Figures 17(b) and 17(d), the remaining vacation allocation data includes vacation acquisition data including an acquisition ID, vacation acquisition date, vacation acquisition time, and daily equivalent hours, and allocation information including an allocation sequence number, allocation category, allocated time, and remaining time after allocation.

The allocation sequence number is information that indicates the allocation order of vacation acquisition data assigned to the same vacation grant data. The sequence numbers are assigned in order of the earliest acquisition date. If multiple vacation days are taken on the same day, such as paid vacation days in the first half and paid vacation days in the second half, the vacation day taken earlier will be given priority in the allocation sequence number. If the time unit is included, the vacation day taken earlier will be given priority in the allocation sequence number.

Allocated time is the time in minutes allocated to leave taken data from the granted time of leave grant data. Remaining time after allocation is the remaining time in minutes obtained by subtracting the total allocated time of leave taken data with allocation serial numbers equal to or lower than the user's number from the granted time, among leave taken data assigned to the same leave grant data. Remaining time after allocation decreases according to the amount of leave taken, and when it reaches "0", the leave grant data cannot be allocated any further. For example, the example in Figure 17(b) shows that by taking a half-day leave (240 minutes) on March 10, 2021, the remaining allocated time of granted time decreased to 1020 minutes - 240 minutes = 780 minutes.

Any remaining time that has not been taken will expire naturally on the last day of the validity period. Rows with a null acquisition ID and number of days taken are special allocation data that means that untaken vacation time will expire on the last day of the validity period. For example, the example in Figure 17(b) shows that if no vacation time is taken after March 10, 2021, 780 minutes of vacation time will expire on the last day of the validity period, with the remaining allocated time after expiration being 0 minutes.

Figure 18 shows how remaining vacation allocation data is formed in response to vacation time taken. In the vacation allocation status shown in Figure 16(a), assume that a full-day paid vacation (480 minutes) is taken on May 12, 2021, a first-half paid vacation (240 minutes) is taken on June 19, 2021, and 105 minutes of paid vacation time is taken on July 30, 2021, as shown in Figure 18. Since the carryover time of annual paid vacation from fiscal year 2020 is 780 minutes, taking 105 minutes of paid vacation time on July 30, 2021 results in a shortfall of 780 minutes - 480 minutes - 240 minutes - 105 minutes, or "-45 minutes." Therefore, when all of the annual paid vacation time granted for fiscal year 2020 has been used, the remaining vacation allocation data is formed, transitioning to the use of annual paid vacation time granted for fiscal year 2021.

That is, the vacation balance allocation data for this example is as shown in Figure 19. Figures 19(a) and 19(b) are a series of vacation balance allocation data that are continuous in the row direction. Figures 19(c) and 19(d) are a series of vacation balance allocation data that are continuous in the row direction. Figures 19(e) and 19(f) are a series of vacation balance allocation data that are continuous in the row direction. Figures 19(a), 19(c), and 19(e) are a series of vacation balance allocation data that are continuous in the column direction. Figures 19(b), 19(d), and 19(f) are a series of vacation balance allocation data that are continuous in the column direction.

As shown in Figure 19(b), when 105 minutes of paid vacation time is taken on July 30, 2021, 60 minutes of these 105 minutes are allocated to consume annual paid vacation time for fiscal year 2020, and the remaining 45 minutes are allocated to consume annual paid vacation time for fiscal year 2021, as shown in Figure 19(d) (split allocation). This allows vacation time with the earliest expiration date to be consumed first.

[Flow of vacation balance allocation process]
Next, the flow of such vacation balance allocation processing will be explained. The vacation balance allocation processing unit 25 executes the vacation management program stored in the storage unit 2 to perform the following processes.

(Getting input parameters)
FIG. 20 is a diagram explaining the parameters acquired by the vacation balance allocation processing unit 25 when allocating vacation balance. The vacation balance allocation processing is performed during a period when reallocation is required, such as when vacation grant data is added, modified, or deleted, or when vacation acquisition data is added or deleted. When vacation grant data is registered, changed, or deleted, the vacation balance allocation processing unit 25 acquires the "validity period start date" and "validity period end date" of the relevant data as the base dates, as shown in FIG. 20(a). In the example of FIG. 20(a), the vacation balance allocation processing unit 25 acquires the validity period start date of April 1, 2021, and the validity period end date of March 31, 2023, as the base dates.

Furthermore, when vacation acquisition data is registered or deleted, the vacation remaining allocation processing unit 25, in the example shown in Figure 20(b), acquires May 12, 2021, which is the date of the current vacation acquisition, as the base date. In the example of Figure 20(b), the vacation remaining allocation processing unit 25 acquires Mr. A's employee code, remaining annual paid vacation management category, and the base date of May 12, 2021 as input parameters, as shown in Figure 20(c).

(Delete old vacation balance allocation data)
Next, the vacation balance allocation processing unit 25 deletes from the vacation balance allocation data any old vacation balance allocation data whose employee code and balance management category are the same as the input parameters and whose vacation acquisition date is greater than or equal to the reference date. Figures 21(a) and 21(b) show an example of a series of consecutive vacation balance allocation data in the row direction. As shown in Figures 21(a) and 21(b), the vacation balance allocation processing unit 25 temporarily deletes vacation balance allocation data for a period for which reallocation calculation is required due to changes in vacation grant data or vacation acquisition data.

(Generation of allocation candidate assignment data)
Next, the vacation balance allocation processing unit 25 acquires vacation grant data whose employee code and remaining management category are the same as the input parameters and whose effective period start date is equal to or less than the base date and whose effective period end date is equal to or less than the base date.Then, it creates a list of allocation candidate grant data corresponding to the period for which reallocation calculation is required.

Specifically, in the example of Figure 22(a), the leave entitlement data for which the remaining management category is annual paid leave is such that the validity period start date ≤ reference date ≤ validity period end date. Therefore, the remaining leave allocation processing unit 25 acquires the leave entitlement data for which the remaining management category is annual paid leave, and, as shown in Figure 22(b), sorts the acquired leave entitlement data in order of earliest fixed-term end date to generate allocation candidate entitlement data.

(Setting remaining time after allocation)
Next, the vacation remaining allocation processing unit 25 sets the remaining time after allocation for the vacation remaining allocation data that has the same allocation ID as the allocation candidate allocation data and the largest allocation sequence number. Since the allocation data after the reference date has been deleted, the "remaining time after allocation for the data with the largest allocation sequence number" means the remaining time that can be allocated after the reference date.

Figure 23 shows an example of remaining vacation allocation data. Figures 23(a) and 23(b) show an example of remaining vacation allocation data arranged consecutively in the row direction. In the example of Figure 23, the remaining vacation allocation data with the same assigned ID as the candidate assigned data and the largest assigned serial number is the remaining vacation allocation data with assigned serial number N+1, as shown in Figure 23(b). Therefore, the remaining vacation allocation processing unit 25 sets the remaining vacation time from the previous year, 780 minutes, as the remaining time after allocation for the remaining vacation allocation data with assigned serial number N+1. By retaining this remaining time after allocation, the remaining vacation allocation data can be recalculated efficiently. This is also effective for inquiry screens for checking the remaining vacation time, as described below.

Next, the vacation balance allocation processing unit 25 obtains the allocation sequence number and remaining post-allocation time set in the vacation balance allocation data and adds them to the allocation candidate assigned data as shown in Figure 24. The example in Figure 24 is an example in which an allocation sequence number of N+1 and a remaining post-allocation time of 780 minutes are added to the allocation candidate assigned data with an assigned ID of XXX1. Furthermore, the vacation balance allocation data shown in Figure 23 does not contain vacation balance allocation data with an assigned ID of XXX2. In this case, the vacation balance allocation processing unit 25 adds an allocation sequence number of "0" and the 8,640 minutes of assigned time assigned for the next year as the remaining post-allocation time to the allocation candidate assigned data with an assigned ID of XXX2 shown in Figure 24.

(Generation of allocation calculation target data)
Next, the vacation balance allocation processing unit 25 acquires vacation acquisition data in which the employee code and remaining management category are the same as the input parameters and the vacation acquisition date is equal to or greater than the base date. Figure 25 is a diagram for explaining the operation of generating allocation calculation target data. Of these, Figure 25(a) shows an example of vacation acquisition data. As shown in Figure 25(a), the vacation balance allocation processing unit 25 acquires vacation acquisition data in which the employee code is "A", the remaining management category is "annual paid leave", and the vacation acquisition date is equal to or greater than the base date.

Then, the vacation balance allocation processing unit 25 generates allocation calculation target data by sorting the acquired vacation acquisition data in order of earliest vacation acquisition date, as shown in Figure 25 (b). Note that if there is multiple vacation acquisition data for the same day, the vacation balance allocation processing unit 25 sorts the multiple vacation acquisition data for the same day in the following priority order: all day < first half < second half < time, and generates allocation calculation target data.

(Allocation error data initialization)
Next, if the acquisition ID to be processed exists in the allocation error data (excess data at the time of allocation, described later), the vacation remaining allocation processing unit 25 deletes it as shown as "STEP 0" in FIG.

(Acquisition of allocation calculation target data)
Next, the vacation remaining allocation processing unit 25 acquires allocation calculation target data of the acquired ID to be processed, as shown as "STEP 1" in FIG.

(Acquisition of allocation candidate assignment data)
Next, the vacation remaining allocation processing unit 25 acquires allocation candidate allocation data of the allocation ID to be processed, as shown in FIG.

(Additional processing of remaining vacation allocation data)
Next, the vacation remaining allocation processing unit 25 performs additional processing of the vacation remaining allocation data as shown in FIG. 28(c) based on the acquired allocation calculation target data and allocation candidate assigned data shown in FIG. 28(a) and FIG. 28(b). The allocated time is the acquired time less than the remaining post-allocation time. If the acquired time is greater than the remaining post-allocation time, it is not possible to allocate all of the time, so the vacation remaining allocation processing unit 25 allocates the remainder from the subsequent assigned data. As shown in FIG. 28(d), the vacation remaining allocation processing unit 25 adds the allocation serial number by incrementing the current allocation serial number of the allocation candidate assigned data by one (N+2). The remaining post-allocation time is the time obtained by subtracting the currently added allocation time from the current remaining post-allocation time of the allocation candidate assigned data. In the example of FIG. 28(d), the vacation remaining allocation processing unit 25 subtracts the 480 minutes of the currently added allocation time from the current remaining post-allocation time of 780 minutes, resulting in 300 minutes as the remaining post-allocation time.

(Update processing of allocation calculation target data and allocation candidate assignment data)
Next, when the vacation remaining allocation data is additionally processed in this way, the vacation remaining allocation processing unit 25 updates the allocation calculation target data by subtracting the allocated time from the acquisition time of the allocation calculation target data (480 minutes - 480 minutes = 0 minutes), as shown in Figure 29(a). Also, the vacation remaining allocation processing unit 25 increments the allocation serial number by one (N + 1 + 1 = N + 2), and subtracts the allocated time from the post-allocation time (780 minutes - 480 minutes = 300 minutes), as shown in Figure 29(b).

If the acquisition time of the current allocation calculation target data is greater than 0, the remaining vacation allocation processing unit 25 repeatedly performs the above-described process of adding remaining vacation allocation data for the allocation candidate allocation data from the second row onwards. If there is insufficient remaining time with one piece of vacation allocation data, the allocation is split and switched to allocation to another piece of vacation allocation data.

(Generation of allocation error data)
Next, even after processing all the allocation candidate grant data, if the acquisition time of the current allocation calculation target data is greater than 0, as shown in FIG. 31(a), the remaining vacation allocation processing unit 25 generates allocation error data as shown in FIG. 31(b). Normally, if there is insufficient remaining time at the time of taking the vacation, an error occurs in the check before taking the vacation, but in the following cases, an error occurs after the fact and detection is necessary. For example, as shown in FIG. 30(a), if a user applies for another vacation before the originally scheduled vacation date, there are no grants available to allocate to the original vacation, as shown in FIG. 30(b). In this case, an error is detected as a result of the allocation recalculation.

If such operations were checked and prohibited in advance, it would be difficult to take leave and could hinder prompt taking of leave, which is undesirable. For this reason, rather than treating it as an input error in advance, error data is generated during the calculation process, and the person in charge, their superior, and attendance manager can be made aware of it using the alert detection described below. If there is remaining leave other than paid leave (such as compensatory leave or substitute leave), subsequent measures can be taken, such as transferring it to another leave.

(Division allocation process)
The vacation balance allocation processing unit 25 also performs this process on the allocation calculation target data from the second row onwards shown in Figure 26. From this, vacation balance allocation data is sequentially added and processed, as shown in Figure 32. Figures 32(a) and 32(b) show a series of vacation balance allocation data that continues row-wise. Since the remaining time for grant ID = XXX1 is 0, the above-mentioned divided allocation process is performed, and the remainder is allocated to grant ID = XXX2.

In addition, the vacation balance allocation processing unit 25, in addition to adding the vacation balance allocation data, updates the allocation candidate assignment data and allocation calculation target data as described above, as shown in Figures 33(a) and 33(b).

(Handling of naturally extinguished records)
Next, the vacation remaining allocation processing unit 25 extracts the naturally extinguished records from the allocation candidate grant data shown in Fig. 34(a) and adds the naturally extinguished allocation to the vacation remaining allocation data as shown in Fig. 34(b). The acquisition ID and acquisition time of the naturally extinguished data are set to NULL, and the allocation time is the remaining time after allocation of the allocation candidate data, and the remaining time after allocation is set to 0. Due to the naturally extinguished data, the remaining time is always 0 at the end date of the validity period.

In this way, by explicitly recording a natural extinction record in the remaining vacation allocation data at the end of the validity period, you can check the remaining vacation allocation data to determine the remaining available time for all vacation days.

[Behavior when taking leave]
Next, the operation of the vacation management device 1 when taking vacation will be described using the flowchart in Figure 11. When applying for vacation, an employee creates a vacation application via terminal device 9, including the employee code, vacation date, vacation type, and reason for application, as shown in Figures 36(a) to 36(c), and sends it to the vacation management device 1. The example in Figure 36(a) is an example of a vacation application in which employee A applies for a full day of paid vacation on August 22, 2021, to visit a hospital. The example in Figure 36(b) is an example of a vacation application in which employee A applies for a full day of paid vacation on September 10, 2021, to visit a hospital.

The allocation error determination unit 26 of the vacation management device 1 checks for a shortage of remaining vacation time as of the acquisition date of the vacation application before updating. Figures 37(a) and 37(b) show a series of row-wise consecutive vacation remaining allocation data. This vacation remaining allocation data is the vacation remaining allocation data for employee A shown in Figures 37(c) and 37(d). The vacation remaining allocation processing unit 25 retrieves from this vacation remaining allocation data for employee A the row with the smallest allocation sequence number, where "validity period start date ≦ vacation acquisition date ≦ validity period end date" and "vacation acquisition date ≧ application date," for each granted ID. If the retrieved data exists and the sum of (allocated time + remaining time after allocation) ≧ acquisition time, the vacation is permitted; otherwise, an error indicating insufficient vacation time is generated. In the case of an insufficient vacation time error, the vacation remaining allocation processing unit 25 sends an error screen indicating insufficient vacation time, as shown in Figure 35, to employee A's terminal device 9 and rejects the vacation application.

To explain more specifically, as shown in Figure 36(a), employee A applied for a full day of paid leave on August 22, 2021, to go to the hospital. As shown in Figure 38, at the time of the application on August 22, 2021, the remaining available time was 8,595 minutes, and the equivalent days and hours were 17.5 days, 3 hours, and 15 minutes (03:15). Therefore, the remaining vacation allocation processing unit 25 determines to allow the vacation to be taken.

The remaining available time is the remaining time before allocation, calculated by adding the allocated time to the remaining time after allocation. The conversion days and hours are calculated using the "granted conversion daily specified hours / 2" formula for each remaining vacation allocation data (converted in half-day units).

Similarly, as shown in Figure 36(b), employee A applied for a full day of paid leave on September 10, 2021, for a medical visit. As shown in Figure 38, at the time of the application on September 10, 2021, the remaining available time was 8,115 minutes, and the equivalent days and hours were 16.5 days, 3 hours, and 15 minutes (03:15). Therefore, the remaining vacation allocation processing unit 25 determines to allow the vacation to be taken.

If there is remaining vacation time due to untaken vacation time, there will always be allocation data that will automatically expire on the expiration date of the validity period. Therefore, it is always possible to back-calculate the remaining time as of the date of acquisition from the most recent remaining vacation allocation data after the current vacation was taken.

Next, when a decision is made to allow the leave to be taken, the remaining leave allocation processing unit 25 creates leave data based on the leave type, leave acquisition date, leave acquisition unit, and requested time. Figure 39(a) is a schematic diagram of the leave type master, Figure 39(b) is an example of a leave application by Mr. A for full-day paid leave, Figure 39(c) is an example of a leave application by Mr. A for first-half paid leave, Figure 39(d) is an example of a leave application by Mr. A for hourly paid leave (16:00-17:45), Figure 39(e) is an example of a leave application by Mr. A for nursing leave (all-day), Figure 39(f) is an example of a leave application by Mr. A for nursing leave (second half), and Figure 39(g) is an example of a leave application by Mr. A for nursing leave (hours, 15:00-17:45).

Based on such vacation application, the remaining vacation allocation processing unit 25 generates vacation data including the following fields: acquisition ID, employee code, vacation acquisition date, vacation type, remaining management category, number of days taken, duration of vacation, equivalent daily hours, and reason for application, as shown in Figure 39 (h). The number of days taken is 1.0 day if the acquisition unit category is all day, 0.5 day if the acquisition unit category is the first half or second half, and not set if the acquisition unit category is hours. Furthermore, if the acquisition unit category is all day, first half, or second half, the duration of vacation is calculated by multiplying the number of days taken by the equivalent daily hours. Furthermore, if the acquisition unit category is hours, the duration (minutes) is calculated based on the requested time.

(Allocation error processing)
Next, we will explain the allocation error process, which is a process by the allocation error determination unit 26 to check whether or not future vacation leave will be insufficient due to an interruption in vacation leave acquisition. For example, as shown in Figure 40(a), assume that employee A applies for vacation leave on March 15, 2022, to take the second half of the paid vacation registered in the vacation type master 12 shown in Figure 40(b) in order to visit a hospital.

The allocation error determination unit 26 determines whether allocation error data for the leave type of employee A who applied for leave, as shown in Figure 40(c), is stored in the memory unit 2. In the example of Figure 40(c), an application for second-half paid leave was made on March 25, 2022, but allocation error data indicating that 60 minutes of overtime had occurred was stored in the memory unit 2. In this case, it becomes necessary to transfer the leave to another leave, etc. Therefore, as shown in Figure 40(d), for example, because the leave exceeds the available leave balance, the allocation error determination unit 26 sends an error message to employee A's terminal device 9 prompting the employee to transfer the leave to another leave.

The allocation error determination unit 26 converts the number of overtime days and time into "hours + minutes" and displays them. Furthermore, if the overtime exceeds one day for a consecutive holiday spanning multiple days (overtime > predetermined hours per day), the allocation error determination unit 26 may display the quotient of overtime ÷ (predetermined hours per day / 2) as the number of days (e.g., 560 minutes = 480 + 60 + 20 = 1.0 day and 1 hour 20 minutes).

[Change in daily hours of granted conversion due to change in employment status or status of employee]
Next, we will explain in detail the operation of changing the granted equivalent daily hours due to changes in an employee's employment type or status, as explained using the flowchart in Figure 12. When the granted equivalent daily hours change due to a change in an employee's employment type or status, the daily hours converted in the leave grant data, leave acquisition data, and remaining leave allocation data must also be changed, and the remaining leave hours held must be recalculated. Below, we will explain an example using nursing care leave data, in which Mr. A, a full-time employee (working hours: 8 hours), changes his employee classification to a part-time employee (working hours: 5 hours) as of January 16, 2022.

First, Figures 41(a) and 41(b) show a series of remaining vacation allocation data that run consecutively in the row direction. The employee classification change processing unit 27 references Mr. A's remaining vacation allocation data shown in Figures 41(a) and 41(b) during vacation inquiries, etc., and calculates the remaining time at the end of the period by working backwards from the allocated time + remaining time after allocation (3915 minutes + 0 minutes = 3915 minutes), thereby calculating the remaining time at the end of the period immediately prior to the employee classification change. Note that the examples shown in Figures 41(a) and 41(b) are examples where the remaining time after allocation is 0 due to natural expiration just before the end of the inquiry period, and the allocated time and remaining time at the end of the period match.

Next, the employee classification change processing unit 27 converts the end-of-year balance calculated in this way into the current daily accrual conversion time (480 minutes), and calculates an end-of-year balance of 8 days, 1 hour, and 15 minutes, as shown in Figure 42 (a).

Next, in response to the labor manager's operation, the employee classification change processing unit 27 changes Mr. A's employee classification in the employee master 15 from full-time employee to part-time employee, as shown in FIG. 42(b). Furthermore, the employee classification change processing unit 27 updates the end date of Mr. A's career as a full-time employee and adds the start date of Mr. A's career as a part-time employee in the employee history data in the employee history DB 16, as shown in FIG. 42(c).

Next, the career revision processing unit 28 adds the remaining number of vacation days, remaining hours, and equivalent daily hours as of the career start date to the vacation registration screen shown in Figure 42(d) and the vacation grant data shown in Figure 42(h). That is, when the employee classification becomes a part-time employee as shown in Figure 42(e), the equivalent daily hours change from 480 minutes to 300 minutes, as registered in the employee classification master in Figure 42(f). Also, as registered in the vacation remaining management classification master in Figure 42(g), vacation can be taken in hourly units for caregiving leave (yes).

For this reason, the employee classification change processing unit 27 displays 8 days on the vacation registration screen as the number of vacation days granted after the employee classification has been changed to a part-time employee. Furthermore, the employee classification change processing unit 27 adjusts the remaining 1 hour and 15 minutes (75 minutes) of vacation time that the employee had when they were a full-time employee based on the ratio of the 8 hours (480 minutes) equivalent daily prescribed hours for the full-time employee classification before the employee classification change to the 5 hours (300 minutes) equivalent daily prescribed hours for the part-time employee classification after the employee classification change.

In other words, in this case, the employee category change processing unit 27 calculates the remaining time after the employee category change by multiplying the remaining time of 75 minutes by the ratio of the equivalent daily hours of a part-time employee (5 hours) to the equivalent daily hours of a full-time employee (8 hours) (75 minutes x (5 hours ÷ 8 hours) ≈ 47 minutes). Note that it is preferable to perform fractional adjustment (rounding up) according to the time unit that is allowed to be taken (rounding down is also acceptable).

Next, when the employee classification change processing unit 27 detects operation of the registration button on the leave registration screen shown in Figure 42 (d), it adds the registered number of granted nursing leave days, registered grant time and minutes, granted hours, and equivalent daily specified hours to Mr. A's leave grant data, as shown in Figure 42 (h). In the example of Figure 42 (h), the grant date and validity period start date of nursing leave are January 16, 2022, and the validity period end date is March 31, 2022. Furthermore, the registered number of granted nursing leave days and registered grant time are 8 days and 47 minutes (00:47), and the total granted hours are 2,447 minutes. This data is stored in Mr. A's leave grant data.

(Processing of requested nursing leave)
Next, once this employee classification change process is complete, the remaining vacation allocation processing unit 25 submits a vacation application for the date on which Mr. A wishes to take nursing leave after the equivalent daily prescribed hours have been changed. That is, Figure 43(a) shows the nursing leave application submitted by Mr. A. Mr. A's employee classification in the employee master 15 shown in Figure 43(b) has been changed from full-time employee to part-time employee. Furthermore, the employee classification setting master 13 shown in Figure 43(c) reveals that the equivalent daily prescribed hours for part-time employees is 300 minutes.

If, after the equivalent daily prescribed hours have been changed, Mr. A submits a leave application requesting to take nursing leave (second half) on January 24, 2022, the remaining leave allocation processing unit 25 will add the leave acquisition data for nursing leave (second half) corresponding to the part-time employee for the date of this leave application, January 24, 2022, as shown in Figure 43 (d). In this case, since this is a half-day leave for a part-time employee who works five hours a day, the acquired time will be 2.5 hours, or 150 minutes. The equivalent daily prescribed hours for part-time employees is 300 minutes.

Next, the remaining vacation allocation processing unit 25 adds remaining vacation allocation data indicating that 150 minutes of nursing care leave, which is half a day's leave for a part-time employee, has been taken, as shown in Figures 43(e) and 43(f). Figures 43(e) and 43(f) are a series of remaining vacation allocation data arranged row-wise. As shown in Figure 43(f), by taking nursing care leave (second half) after changing the employee classification, 150 minutes of vacation time has been consumed, and the 2,447 minutes of vacation time (remaining time after allocation) has become 2,297 minutes (2,447 minutes - 150 minutes).

In this way, even if an employee's classification changes midway, the vacation entitlement data is split and the equivalent daily hours before and after the employee classification change are retained separately. This allows the remaining vacation days and hours to be properly converted before and after the employee classification change, ensuring the correct amount of vacation remaining can be determined even after the employee classification is changed.

[Effects of the embodiment]
With the current trend toward work style reforms and other factors promoting planned vacation time, there is a need for mechanisms in both labor and systems to encourage appropriate vacation time based on the type of vacation (annual paid vacation, compensatory vacation, etc.). Furthermore, couples who both work and raise small children, or who face nursing care issues due to an aging society, are often forced to take unexpected vacation time due to injuries or illnesses of family members.

The hourly annual paid leave system was introduced with the revision of the Labor Standards Act in April 2010, but with the recent spread of the idea of "work-life balance," which seeks to harmonize work and personal life, the number of companies introducing this system has been rapidly increasing in recent years.

In addition, the amendment to the Childcare and Family Care Leave Act, which came into effect in January 2021, has made it mandatory by law to take child care leave and family care leave in hourly units, and has increased the types of leave that can be taken in hourly units (e.g., annual paid leave, compensatory leave, child care leave, family care leave).

In addition, as the need to constantly adjust work arrival and departure times has increased, more and more workers are switching to shorter working hours, taking advantage of systems for reduced working hours for childcare or for elderly care.

In addition, there is a demand for an environment in which employees can continue working while flexibly adapting their work style to suit life events, such as when an employee initially works regular scheduled working hours, but then temporarily shifts to reduced hours for childcare or elderly care, and then returns to regular work after a few years. Such changes to an employee's scheduled working hours require changes to the remaining leave management status for day-based and hourly leave, making leave management tasks more complicated.

In addition, the annual paid leave system was changed from one that only allowed leave in days to one that allowed employees to take five days' worth of leave in hourly increments. In this case, if an employee had 40 days of leave remaining at the beginning of the year, the leave was managed separately in terms of hours and days, with five days (40 hours) managed in hours and the remaining 35 days managed in days. As a result, if an employee used up all of their remaining leave in days (e.g., taking 35 days of leave), they were deemed to have used up all of their leave, even if they still had leave in hours. Furthermore, if the "scheduled working hours per day" changed, the "remaining leave in hours" had to be recalculated and reset based on the "new working hours per day," which was extremely cumbersome.

While the Labor Standards Act and the Childcare and Family Care Leave Act stipulate hourly leave, the scope of support available in systems is often limited due to gradual legal reforms and increasingly complex systems. For example, child care leave was initially only permitted in one-day increments, but a legal amendment in 2017 allowed it to be taken in half-day increments, and a legal amendment in December 2019 (effective January 2021) made it possible to take leave in hourly increments. It is difficult to incorporate functionality that anticipates this from the start. For example, if part of a day's leave is taken in hourly increments, the remaining time of the day is reserved exclusively for hourly leave, making it difficult to carry it over to the following year. Furthermore, systems cannot accommodate changes in working hours due to changes in employee status, or require manual maintenance, making the process cumbersome.

Furthermore, system accommodations are merely minimum requirements, and in many cases, accommodations cannot be made if the work rules stipulate treatment that is more favorable to workers than stipulated by law (for example, allowing leave to be taken in 15-minute or 30-minute increments).

For this reason, the vacation management device 1 of this embodiment can flexibly respond to changes in the system by mastering all differences in control depending on the reason for vacation. Furthermore, vacation management units are internally managed in the smallest unit of "minutes," and conversion or display methods can be switched depending on how the vacation is taken (by day or hour), achieving both accurate vacation balance management and convenience.

In addition, the vacation management device 1 of this embodiment can handle different calculation rules for calculating overtime hours and vacation hours by separately managing the specified time for calculating overtime work (e.g., 7 hours and 45 minutes) and the specified time for converting vacation hours (e.g., 8 hours). Furthermore, by storing the specified time for conversion in a non-normalized form in the vacation data, even if the working hours (equivalent specified hours per day) change due to a change in an employee's employee classification, it is possible to uniformly convert data for the specified hours that differ before and after the change.

As a result, the vacation management device 1 of this embodiment can achieve the following effects:

1. The vacation management device 1 of this embodiment can centrally manage multiple types of vacation, including daily, half-day, and hourly vacations, through master control, enabling general-purpose calculations of vacation granting, acquisition, and remaining management.

2. By managing vacation time in minutes in vacation grant data, vacation acquisition data, and remaining vacation allocation data, and by storing the employee's "equivalent daily hours" at that time in the data, it is possible to respond to changes in employment status, etc., which change the scheduled working hours.

3. Furthermore, because leave can be taken in "minute increments," which exceeds the "hourly units" required by the system, all data can be calculated based on the "minute" of time. While it is unlikely that leave would be taken in one-minute increments, the leave management device 1 of this embodiment can accommodate situations where leave is taken in rounded increments such as 15 minutes, such as when a company's working hours are 9:00-17:45 (total of 7 hours and 45 minutes) and an employee takes one hour and 45 minutes of leave to go home at 16:00.

4. By setting "daily equivalent hours" in the employee classification setting master 13, you can manage the daily equivalent hours (e.g., 8 hours) for hourly leave conversion, separately from the specified working hours (e.g., 7.5 hours) used to calculate actual work performance according to employment type. Furthermore, the current vacation grant data, vacation consumption data, and remaining vacation allocation data can be automatically reflected in the daily equivalent hours. Furthermore, when a day's vacation is allocated to hourly leave, conversion can be performed in one-hour increments to avoid fractional amounts.

5. In addition, by managing changes to employee classifications in the employee master data 15, historical revisions to vacation grant data can be made automatically. Existing vacation time can be eliminated and re-granted in hours and minutes in response to changes in scheduled working hours, allowing accurate remaining vacation time to be carried over even after changes to scheduled working hours.

6. By providing "remaining management category" and "acquisition unit category" (all day, first half, second half, hour) in the leave type master 12, it is possible to unify control over multiple types of leave. This allows for flexible settings in accordance with the company's work rules or system revisions, such as leave that can only be taken in days or leave that can be taken in hourly units.

7. Based on the relationship between the expiry date of leave entitlement data and the date leave is taken, priority assignments that do not disadvantage workers can be accurately calculated and managed, even when leave taken in days or hours is mixed.

8. When there is a shortage of remaining vacation time due to an interruption request, etc., a warning including the number of days and hours can be displayed.

The vacation management device 1 of the embodiment can achieve these effects, allowing companies to introduce the vacation management device 1 of the embodiment while reducing the burden and costs of labor management. Furthermore, workers can flexibly apply for vacation with simple operations, even if their work style changes. Therefore, the vacation management device 1 of the embodiment can contribute to work style reform and work-life balance.

Furthermore, due to amendments to the Childcare and Family Care Leave Act that came into effect in January 2021, more and more leave can be taken not only by the day but also by the hour. Furthermore, even for the same employee, flexible working styles such as "working reduced hours while raising children" and "returning to regular work once childcare has settled down" are becoming more common. This has made managing "how much remaining leave can be taken" (remaining leave management) more complicated, posing an obstacle to introducing hourly leave. The leave management device 1 of the embodiment enables multiple types of remaining leave management on an hourly or daily basis, and can smoothly change remaining leave even if the "scheduled daily working hours" change, such as from reduced hours to regular work. As a result, the introduction of hourly leave can be encouraged.

[Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

Other Embodiments
The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, of the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the vacation management device 1, the components shown are functional concepts and do not necessarily have to be physically configured as shown.

For example, all or any part of the processing functions of the vacation management device 1, particularly the control unit 3 and the various processing functions performed by the control unit 3, may be implemented by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support device 1 as needed. That is, a storage unit such as a ROM or HDD stores a computer program that works in conjunction with the OS to issue commands to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works in conjunction with the CPU to form the control unit 3.

In addition, this computer program, the vacation management program, may be stored on another server device connected to the vacation management device 1 via any network, and all or part of it may be downloaded as needed.

The vacation management program for executing the processes described in this embodiment may be stored on a non-transitory computer-readable recording medium or configured as a program product. Here, "recording medium" includes any "portable physical medium" such as a memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical Disk), DVD (Digital Versatile Disk), and Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known structures and procedures.

The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and website provision.

The vacation management device 1 may also be configured as an information processing device such as a known personal computer or workstation, or may be configured as such an information processing device to which any peripheral devices are connected. The information processing device may also be implemented by installing software (including programs, data, etc.) that realizes the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional additions. In other words, the above-mentioned embodiments may be implemented in any combination, or embodiments may be implemented selectively.

This invention is useful for employee vacation management.

REFERENCE SIGNS LIST 1 Vacation management device 2 Storage unit 3 Control unit 4 Communication interface unit 5 Input/output interface unit 6 Input device 7 Output device 8 Network 9 Terminal device 11 Vacation balance management category master 12 Vacation type master 13 Employee category setting master 14 Working hours master 15 Employee master 16 Employee history database 21 Display control unit 22 Input processing unit 23 Update processing unit 24 Vacation balance determination unit 25 Vacation balance allocation processing unit 26 Allocation error determination unit 27 Employee category change processing unit 28 History revision processing unit

Claims (5)

a leave time conversion processing unit that refers to a storage unit that stores information on whether each type of leave can be taken in hourly units and the units of leave taken, either full day, half day, or hour, set for each type of leave, and determines whether the type of leave applied for in the leave application allows for leave to be taken in hourly units; if the type of leave applied for in the leave application allows for leave to be taken in hourly units, multiplies the number of leave days available to the leave taker by the working hours of one day set according to the leave taker's employment type to form total leave time, converting the number of leave days granted to the leave taker into hours; if it determines that the type of leave cannot be taken in hourly units, multiplies the number of leave days by the working hours of one day, which is a fixed number of hours, to form total leave time; and if the employment type of the leave taker is changed, calculates the total leave time using the working hours according to the changed employment type ;
a vacation time conversion processing unit that converts the vacation period applied for by the vacation taker into vacation hours based on the working hours for one day that are set according to the employment status of the vacation taker , and when the employment status of the vacation taker changes, performs the conversion processing based on the working hours according to the changed employment status;
a remaining vacation time calculation unit that calculates the remaining vacation time by subtracting the vacation time taken from the total vacation time, and calculates the remaining vacation time after the employment type change by subtracting the vacation time taken after the employment type change from the total vacation time after the employment type change ;
a remaining vacation allocation processing unit that, when the vacation taker applies for another vacation before the planned vacation date, determines whether the vacation time of the applied for vacation and the vacation time of the vacation to be taken exceed the remaining vacation time, and generates allocation error data if the remaining vacation time is exceeded;
an allocation error determination unit that determines whether or not there is allocation error data for the application at the time of the vacation interruption, and if there is allocation error data, outputs a predetermined error message together with the number of overtime days and time;
a career revision processing unit that updates vacation entitlement data including the remaining vacation time before the employment status change to vacation entitlement data including the remaining vacation time after the employment status change;
A vacation management device having: The vacation management device of claim 1, characterized in that when the vacation taken time is longer than the total vacation time and subtraction processing cannot be performed, the remaining vacation time calculation unit subtracts the vacation taken time from the total vacation time, and subtracts the remaining vacation taken time from the total vacation time of other vacations . The vacation management device according to claim 2 , wherein the remaining vacation time calculation unit displays a predetermined error message when the subtraction process cannot be performed because the vacation taken time is longer than the total vacation time. a leave hour conversion processing step in which a leave hour conversion processing unit references a storage unit that stores information on whether each type of leave can be taken in hourly units and the unit of leave taken for each type of leave, from full-day, half-day, and hourly, and determines whether the type of leave applied for in the leave application allows for leave to be taken in hourly units; and if the type of leave applied for in the leave application allows for leave to be taken in hourly units, multiplies the number of leave days available to the leave taker by the working hours of one day set according to the leave taker's employment type to form total leave hours by converting the number of leave days granted to the leave taker into hours; and if it is determined that the type of leave cannot be taken in hourly units, multiplies the number of leave days by the working hours of one day, which is a fixed number of hours, to form total leave hours, and if the employment type of the leave taker changes, calculates the total leave hours using the working hours according to the changed employment type ;
a vacation time conversion processing step in which a vacation time conversion processing unit converts the vacation period applied for by the vacation taker into vacation time based on the working hours for one day set according to the employment type of the vacation taker, and if the employment type of the vacation taker changes, converts the conversion based on the working hours according to the changed employment type ;
a remaining vacation time calculation step in which a remaining vacation time calculation unit calculates the remaining vacation time by subtracting the vacation taken time from the total vacation time, and calculates the remaining vacation time after the employment type change by subtracting the vacation taken time after the employment type change from the total vacation time after the employment type change ;
a vacation remaining allocation step in which, when the vacation taker applies for another vacation before the planned vacation date, the processing unit determines whether the vacation time of the requested vacation and the vacation time of the vacation to be taken exceed the remaining vacation time, and generates allocation error data if the remaining vacation time is exceeded;
an allocation error determination step in which an allocation error determination unit determines whether or not there is allocation error data for the application at the time of the vacation interruption, and if there is allocation error data, outputs a predetermined error message together with the number of overtime days and time;
a career revision processing step in which a career revision processing unit updates vacation entitlement data including the remaining vacation time before the employment status change to vacation entitlement data including the remaining vacation time after the employment status change;
A leave management method having: Computer,
a leave time conversion processing unit that refers to a storage unit that stores information on whether each type of leave can be taken in hourly units and the units of leave taken, either full day, half day, or hour, set for each type of leave, and determines whether the type of leave applied for in the leave application allows for leave to be taken in hourly units; if the type of leave applied for in the leave application allows for leave to be taken in hourly units, multiplies the number of leave days available to the leave taker by the working hours of one day set according to the leave taker's employment type to form total leave time, converting the number of leave days granted to the leave taker into hours; if it determines that the type of leave cannot be taken in hourly units, multiplies the number of leave days by the working hours of one day, which is a fixed number of hours, to form total leave time; and if the employment type of the leave taker is changed, calculates the total leave time using the working hours according to the changed employment type ;
a vacation time conversion processing unit that converts the vacation period applied for by the vacation taker into vacation hours based on the working hours for one day that are set according to the employment status of the vacation taker , and when the employment status of the vacation taker changes, performs the conversion processing based on the working hours according to the changed employment status;
a remaining vacation time calculation unit that calculates the remaining vacation time by subtracting the vacation time taken from the total vacation time, and calculates the remaining vacation time after the employment type change by subtracting the vacation time taken after the employment type change from the total vacation time after the employment type change ;
a remaining vacation allocation processing unit that, when the vacation taker applies for another vacation before the planned vacation date, determines whether the vacation time of the applied for vacation and the vacation time of the vacation to be taken exceed the remaining vacation time, and generates allocation error data if the remaining vacation time is exceeded;
an allocation error determination unit that determines whether or not there is allocation error data for the application at the time of the vacation interruption, and if there is allocation error data, outputs a predetermined error message together with the number of overtime days and time;
a leave management program that functions as a career revision processing unit that updates leave entitlement data including the remaining leave hours before the change in employment status to leave entitlement data including the remaining leave hours after the change in employment status .