Vacation management device, vacation management method, and vacation management program

Abstract

To enable flexible vacation management corresponding to various acquisition forms.SOLUTION: A vacation time conversion processing part forms total vacation time obtained by converting the number of vacation days imparted to a vacation acquiring person into time by multiplying the number of vacation days which can be acquired by the vacation acquiring person by working time for one day set according to the employment form of the vacation acquiring person. A vacation acquisition time conversion processing part converts a vacation period applied for vacation acquisition by the vacation acquirer into a vacation acquisition time on the basis of working hours for one day set according to an employment form of the vacation acquirer. Then, the remaining vacation time calculation section calculates the remaining vacation time by subtracting the vacation acquisition time from the total vacation time. Thus, it is possible to perform vacation management flexibly corresponding to various acquisition forms according to the employment form of the vacation acquirer.SELECTED DRAWING: Figure 37

Description

[Technical Field]

[0001] The present invention relates to a vacation management device, a vacation management method, and a vacation management program. [Background technology]

[0002] As background art 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, a server device of the time management system that records and manages the work time for each work item input from a terminal device includes a time management means, a work item management means, a recording means, and a report output means.

[0003] 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 outputs a report in a format specified by the terminal device based on the recorded information.

[0004] This type of time management system does not manage time precisely down to the minute, but manages time in blocks, allowing for human discretion and contributing to improved productivity through continuous time management. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2020-112979 Summary of the Invention [Problem to be solved by the invention]

[0006] Nowadays, there are various employment forms, such as full-time employees, temporary workers, contract employees (fixed-term labor contracts), and part-time workers. There are also various working styles, such as regular work, day shifts, night shifts, shift work, part-time work, and reduced-hours work. There are also various types of vacation, such as annual paid leave, compensatory leave, nursing care leave, caregiver leave, congratulatory and condolence leave, and sick leave. While taking vacation in daily or half-day increments is common today, it is predicted that in the future, various vacation acquisition forms will be available for each worker. Therefore, it is desirable to manage vacation in a way that accommodates the various vacation acquisition forms that may be available in the future.

[0007] The present invention has been made in view 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. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the objectives, the vacation management device of the present invention has a vacation time conversion processing unit that converts the number of vacation days granted to a vacation taker into hours by multiplying the number of vacation days available to the vacation taker by the working hours of one day set according to the vacation taker's employment type to form total vacation time; a vacation taken time conversion processing unit that converts the vacation period applied for by the vacation taker into vacation taken time based on the working hours of one day set according to the vacation taker's employment type; and a remaining vacation time calculation unit that calculates remaining vacation time by subtracting the vacation taken time from the total vacation time.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the vacation management method of the present invention includes a vacation time conversion processing step in which a vacation time conversion processing unit multiplies the number of vacation days available to the vacation taker by the working hours of one day set in accordance with the employment type of the vacation taker to form total vacation time by converting the number of vacation days granted to the vacation taker into hours; a vacation taken time conversion processing step in which a vacation taken time conversion processing unit converts the vacation period applied for by the vacation taker into vacation taken hours based on the working hours of one day set in accordance with the employment type of the vacation taker; and a remaining vacation time calculation step in which a remaining vacation time calculation unit calculates the remaining vacation time by subtracting the vacation taken hours from the total vacation time.

[0010] In addition, in order to solve the above-mentioned problems and achieve the objectives, the vacation management program of the present invention causes a computer to function as a vacation time conversion processing unit that converts the number of vacation days granted to a vacation taker into hours by multiplying the number of vacation days available to the vacation taker by the working hours per day set according to the vacation taker's employment type to form total vacation time, a vacation taken time conversion processing unit that converts the vacation period applied for by the vacation taker into vacation taken time based on the working hours per day set according to the vacation taker's employment type, and a remaining vacation time calculation unit that calculates remaining vacation time by subtracting the vacation taken time from the total vacation time. [Effects of the Invention]

[0011] The present invention provides the advantage of enabling flexible vacation management in response to various acquisition forms. [Brief explanation of the drawings]

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

[0013] A vacation management device according to an embodiment of the present invention will be described in detail below with reference to the drawings, although the present invention is not limited to this embodiment.

[0014] [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 memory 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.

[0015] The storage unit 2 is provided with a vacation balance management category master 11, a vacation type master 12, an employee category setting master 13, a working hours master 14, an employee master 15, and an employee history database (employee history DB) 16. The storage 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 each data will be described later.

[0016] The control unit 3 executes the vacation management program stored in the memory unit 2 to realize the functions of a display control unit 21, an input processing unit 22, an update processing unit 23, a vacation balance determination unit 24, a vacation balance allocation processing unit 25, an allocation error determination unit 26, an employee classification change processing unit 27, and a 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, a vacation acquisition time conversion processing unit, and a remaining vacation time calculation unit.

[0017] [Image of taking vacation time] As an example, Figure 2 shows how annual paid leave, child care leave, and family care leave are taken. 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.

[0018] Child care leave is granted for 5 days per year if there is one eligible child, and 10 days per year if there are two or more eligible children. Family care leave is granted for 5 days per year if there is one eligible person requiring care, and 10 days per year if there are two or more eligible people requiring care. Child care leave and family care leave expire on the last day of the fiscal year and are newly granted on the first day of the fiscal year.

[0019] 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.

[0020] [Vacation Remaining Management Classification 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 that is granted in the paid vacation grant process, and the remaining management category is "1", meaning that it can be taken in hourly units (yes). Compensatory vacation is vacation that is 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).

[0021] Caregiver leave is leave based on the caregiver 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 employees work in lieu of work on regular holidays, and the remaining management category is "7", meaning that it cannot be taken in hourly units.

[0022] Compensatory holidays (statutory holidays) are compensatory holidays when employees work on statutory holidays, and the remaining management category is "8," meaning that they cannot be taken in hourly units. Saved paid leave 1 is leave that companies adopt at their discretion (leave when expired leave that has exceeded the upper limit or deadline of annual paid leave is accumulated), and the remaining management category is "9," meaning that they can be taken in hourly units. Saved paid leave 2 is leave that companies adopt at their discretion (leave when expired leave that has exceeded the upper limit or deadline of Saved Paid Leave 1 is accumulated), and the remaining management category is "10," meaning that they can be taken in hourly units.

[0023] [Leave 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. Furthermore, the leave type master 12 stores information indicating that care leave with a remaining management category of "5" can be acquired as all-day, first half, second half, or hourly.

[0024] [Employee Classification 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 hourly leave. As an example, for a full-time employee working a regular shift, the equivalent daily prescribed hours is stored in the employee category setting master 13 as "480 minutes" based on an eight-hour work day. For a part-time employee working a reduced-hours shift, the equivalent daily prescribed hours is stored as "300 minutes" based on a five-hour work day. For a part-time employee working a part-time shift, the equivalent daily prescribed hours is stored as "240 minutes" based on a four-hour work day.

[0025] [Specified time master] Next, FIG. 6 shows a schematic diagram of the working hours master 14. The working hours master 14 is a master that manages working hours and rest periods for each working style. The working hours master 14 sets predetermined working hours and the like that are used for calculating overtime hours, etc. For example, in the case of a regular shift working style, the working hours master 14 stores the work start time and work end time from 9:00 to 17:45, the working hours of 465 minutes obtained by subtracting a 60-minute rest period from the 525-minute commitment time corresponding to this working style, and the 60-minute rest period. In addition, in the case of a part-time shift working style, the working hours master 14 stores the work start time and work end time from 11:00 to 15:45, the working hours of 240 minutes obtained by subtracting a 45-minute rest period from the 285-minute commitment time corresponding to this working style, and the 45-minute rest period.

[0026] [Employee Master] Next, Fig. 7 shows 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.

[0027] [Employee History DB] Next, Fig. 8 shows a schematic diagram of the employee history DB 16. The employee history DB 16 stores data for managing the attribute history of 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 the attributes in the employee master 15 are changed.

[0028] [Annual paid leave grant processing] Next, the process of 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.

[0029] Next, the labor manager operates the input device 6 to input annual paid vacation grant information (step S2). 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 S3).

[0030] 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 storage unit 2 (step S4). The detailed operation of this vacation balance allocation process will be described later.

[0031] [Other leave grant processing] Next, the process of granting leave other than annual paid leave will be explained 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.

[0032] 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 storage unit 2 based on the input vacation grant information (step S13).

[0033] 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 storage unit 2 (step S14). The detailed operation of this vacation balance allocation process will be described later.

[0034] [Employee leave taking behavior] Next, the operation 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 to be taken (step S21), and then performs the operation to execute the vacation application (step S22). As a result, information indicating the details of the vacation to be taken (vacation type, number of days to be taken, etc.) is sent from the employee's terminal device 9 to the vacation management device 1 via the network 8.

[0035] The control unit 3 of the vacation management device 1 operates based on the vacation management program, causing the vacation balance determination unit 24 to check 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 a shortage of vacation balance available at the time the vacation was applied for. This check of the vacation balance insufficiency can be done in advance before the vacation balance allocation process (step S25) is executed, so it is performed before the vacation acquisition data update process (step S24).

[0036] If the vacation balance determination unit 24 determines that there is insufficient vacation balance (there is a shortage), 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 insufficient vacation balance (step S27).

[0037] If the vacation balance determination unit 24 does not determine whether the vacation balance is insufficient (no shortage), the update processing unit 23 performs an update process on the vacation acquisition data in the storage unit 2 corresponding to the requested vacation.

[0038] 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 storage unit 2 (step S25). The detailed operation of this vacation balance allocation process will be described later.

[0039] Next, the allocation error determination unit 26 checks for an allocation error due to the vacation remaining allocation process in step S25 (step S26), and if there is no allocation error, the process of the flowchart in FIG. 11 ends immediately.

[0040] This allocation error check is performed to check whether there is enough vacation remaining at the time the vacation is requested, but if an interruption is made, a previous request for the same type of vacation for a future date will not result in an insufficient vacation remaining due to the vacation expiration date.

[0041] Such cases can be detected after the remaining vacation allocation process. For this reason, in the vacation management device 1 of this embodiment, acquisition is initially permitted and vacation application is possible, and 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 later.

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

[0043] Next, if there is a change in the specified time (working hours) due to a change in the employee's employment type or status, the career revision processing unit 28 updates the equivalent daily specified time for the vacation grant data, vacation take data, or vacation remaining allocation data held by the employee. After this, the vacation remaining allocation processing unit 25 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). The detailed operation of this vacation remaining allocation process will be described later.

[0044] [Leave application behavior after employee classification change] Next, the operation of an employee applying for leave 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 terminal device 9 to apply for leave (steps S41 and S42). In this case, 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 memory unit 2 (step S43). The detailed operation of this vacation balance allocation process will be described later.

[0045] [Leave Granting Action Details] Next, the vacation granting operation explained with reference to FIGS. 9 and 10 will be explained in detail.

[0046] (Annual paid leave granting operation) First, the operation of granting annual paid leave explained using Fig. 9 will be explained 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.

[0047] Specifically, FIG. 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 an employee (in this example, Mr. A) to whom annual paid vacation will be granted. As shown in FIG. 14(b), employee A's employee category is stored in the employee master 15 as a full-time employee. As shown in FIG. 14(c), the employee category setting master 13 stores "equivalent daily 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 FIG. 14(d), the vacation remaining management category master 11 stores information indicating whether annual paid vacation can be taken in hourly units, with "yes" indicating that it can be taken in hourly units.

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

[0049] Next, the update processing unit 23 calculates the "granted hours," which is the amount of annual paid leave corresponding to the number of days of annual paid leave granted, by multiplying the number of days of annual paid leave granted by a predetermined equivalent time per day (480 minutes).The update processing unit 23 then stores leave grant data including the calculated granted hours in the storage unit 2, as shown in Figure 14(e).In the example of Figure 14(e), the number of days of annual paid leave newly granted 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 leave grant data.

[0050] 14(e), the remaining number of granted annual paid holidays for the previous year is 16, so the granted time of 16 days x 480 minutes = 7,680 minutes is included in the vacation grant data and stored. In the case of annual paid holidays, 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 holiday storage period lasted.

[0051] 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.

[0052] (Other leave granting actions) Next, we will explain in detail the operation of granting other types of leave other than the annual paid leave explained using Figure 10. Figure 15 is a diagram for explaining the operation of granting 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 each time as needed.

[0053] Specifically, Fig. 15(a) shows an example of a leave registration screen for nursing care leave that is displayed on the output device 7 of the leave management device 1 operated by the labor manager. Fig. 15(b) shows an example of a leave registration screen for family care leave that is 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 (Fig. 15(a)) or family care leave (Fig. 15(b)) as the remaining management category, and selects the employee (Mr. A in this example) to whom nursing care leave or family care leave will be granted.

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

[0055] The update processing unit 23 automatically inputs the equivalent daily prescribed hours into the leave registration screen shown in Fig. 15(a) in accordance with the master settings of the employee to whom leave is to be granted. Note that if the acquisition of hourly units is "none," the update processing unit 23 fixes the working hours to 8 hours for all employees, calculates the equivalent daily prescribed hours (480 minutes), and inputs this into the leave registration screen for nursing care leave (Fig. 15(a)) or the leave registration screen for family care leave (Fig. 15(b)).

[0056] Next, the update processing unit 23 calculates the "granted hours" corresponding to the granted days of nursing care leave and family care leave by multiplying the granted days of nursing care leave and family care leave by the equivalent predetermined time per day (480 minutes). The update processing unit 23 then stores the calculated granted hours in the storage unit 2, as shown in FIG. 15(f). In the example of FIG. 15(f), the granted days of nursing care leave are 10 days, so the update processing unit 23 calculates the granted hours as follows: 10 days × 480 minutes = 4,800 minutes, and stores this information in the leave grant data. In the example of FIG. 15(f), the granted days of family care leave are 5 days, so the update processing unit 23 calculates the granted hours as follows: 5 days × 480 minutes = 2,400 minutes, and stores this information in the leave grant data.

[0057] The update processing unit 23 sets the date one year after the start date of the current fiscal year, which is the grant date for nursing care leave and family care leave, as the end date of the validity period. The example in Figure 15(f) is an example in which the grant date and the start date of the validity period are different, and for nursing care leave granted on May 1, 2021, and family care leave granted on June 1, 2021, the start date of the current fiscal year is set as the start date of the validity period, and March 31, 2022, one year after the start date of the validity period, is set as the end date of the validity period.

[0058] 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 where nursing leave, totaling 4,800 minutes (10 days), was granted on May 1, 2021, 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 where nursing leave, totaling 2,400 minutes (5 days), was granted on June 1, 2021, with the effective period starting on April 1, 2021 and ending on the end of March 2022.

[0059] [Leave balance 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 care leave, equivalent to 10 days, was granted on May 1, 2021.

[0060] 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 the earliest expiration date to be taken first when revising the career history, as described below.

[0061] 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 in the row direction. Figure 17(c) shows an example of vacation balance allocation data that are continuous in the column direction relative to the vacation balance allocation data in Figure 17(a). Figure 17(d) shows an example of vacation balance allocation data that are continuous in the column direction relative to the vacation balance allocation data in Figure 17(b).

[0062] 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, vacation grant data including an grant ID, grant date, validity period start date, validity period end date, granted time, and granted equivalent hours per day. Also, 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, acquisition time, and granted equivalent hours per day, and allocation information including an allocation sequence number, allocation category, allocated time, and remaining time after allocation.

[0063] 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 vacations are acquired on the same day, such as paid vacation in the first half and paid vacation in the second half, the vacation acquired earlier in time will be given priority in the allocation sequence number. Also, if the time unit is included, the vacation acquired earlier in time will be given priority in the allocation sequence number.

[0064] Allocated time is the time in minutes allocated to the vacation take data from the granted time of the vacation entitlement data. The remaining time after allocation is the remaining time in minutes obtained by subtracting the total allocated time of the vacation take data with allocation serial numbers below the user's number, allocated to the same vacation entitlement data, from the granted time. The remaining time after allocation decreases according to the amount of vacation taken, and when it reaches "0", the vacation entitlement data cannot be allocated any further. For example, the example in Figure 17(b) shows that by taking a half-day vacation (240 minutes) on March 10, 2021, the remaining time after allocation of the granted time decreased to 1020 minutes - 240 minutes = 780 minutes.

[0065] Any remaining time that has not been taken will expire naturally on the end date of the validity period. Natural expiration data, where the acquisition ID and number of days taken are NULL, is special allocation data that means that untaken vacation will expire on the end date of the validity period. For example, the example in Figure 17(b) shows that if no vacation is taken after March 10, 2021, 780 minutes of vacation will expire on the end date of the validity period, and the remaining allocated time after expiration will be 0 minutes.

[0066] Figure 18 is a diagram showing how remaining vacation allocation data is generated 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) was taken on May 12, 2021, a first-half paid vacation (240 minutes) was taken on June 19, 2021, and 105 minutes of paid vacation time were taken on July 30, 2021, as shown in Figure 18. Because 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 45 minutes (780 minutes - 480 minutes - 240 minutes - 105 minutes). Therefore, when all of the annual paid vacation time granted for fiscal year 2020 is used, the remaining vacation allocation data is generated, transitioning to the use of annual paid vacation time granted for fiscal year 2021.

[0067] That is, the vacation balance allocation data in 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.

[0068] As shown in Figure 19(b), when 105 minutes of paid leave is taken on July 30, 2021, 60 minutes of these 105 minutes are allocated to consume annual paid leave for fiscal year 2020, and the remaining 45 minutes are allocated to consume annual paid leave for fiscal year 2021, as shown in Figure 19(d) (split allocation). This allows priority to be given to the use of leave that expires earliest.

[0069] [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.

[0070] (Getting input parameters) Figure 20 is a diagram explaining the parameters acquired by the vacation balance allocation processing unit 25 when allocating vacation balance. 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 Figure 20(a). In the example of Figure 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.

[0071] Furthermore, when vacation acquisition data is registered or deleted, in the example shown in Figure 20(b), the vacation remaining allocation processing unit 25 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, annual paid vacation remaining management category, and the base date of May 12, 2021 as input parameters, as shown in Figure 20(c).

[0072] (Delete old vacation balance allocation data) Next, the vacation balance allocation processing unit 25 deletes from the vacation balance allocation data 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 equal to or greater than the reference date. Figures 21(a) and 21(b) are examples 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 that requires reallocation calculation due to changes in vacation grant data or vacation acquisition data.

[0073] (Generation of allocation candidate 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 validity period start date is equal to or less than the base date and whose validity 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.

[0074] Specifically, in the example of Figure 22(a), the vacation entitlement data for which the remaining management category is annual paid vacation is the vacation entitlement data where the validity period start date ≦ base date ≦ validity period end date. Therefore, the vacation remaining allocation processing unit 25 acquires the vacation entitlement data for which the remaining management category is annual paid vacation, and generates allocation candidate grant data by sorting the acquired vacation entitlement data in order of earliest fixed term end date, as shown in Figure 22(b).

[0075] (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 among the vacation remaining allocation data. Since the allocation data after the reference date has been deleted, the "remaining time after allocation of the data with the largest allocation sequence number" means the remaining time that can be allocated after the reference date.

[0076] Figure 23 shows an example of vacation balance allocation data. Figures 23(a) and 23(b) show an example of vacation balance allocation data that is continuous in the row direction. In the example of Figure 23, the vacation balance allocation data that has the same assigned ID as the allocation candidate assigned data and the largest assigned sequence number is the vacation balance allocation data with assignment sequence number N+1, as shown in Figure 23(b). Therefore, the vacation balance allocation processing unit 25 sets 780 minutes, which is the remaining vacation time from the previous year, as the post-allocation remaining time for the vacation balance allocation data with assignment sequence number N+1. By retaining such post-allocation remaining time, the recalculation of vacation balance allocation data can be efficiently performed. This is also effective for inquiry screens for checking vacation balances, as described below.

[0077] Next, the vacation remainder allocation processing unit 25 acquires the allocation sequence number and remaining post-allocation time set in the vacation remainder 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 remainder allocation data shown in Figure 23 does not contain vacation remainder allocation data with an assigned ID of XXX2. In this case, the vacation remainder allocation processing unit 25 adds an allocation sequence number of "0" and 8640 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.

[0078] (Generating allocation calculation target data) Next, the vacation remaining allocation processing unit 25 acquires vacation taking data from the vacation taking data where the employee code and remaining management category are the same as the input parameters and the vacation taking 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 taking data. As shown in Figure 25(a), the vacation remaining allocation processing unit 25 acquires vacation taking data where the employee code is "A", the remaining management category is "annual paid leave", and the vacation taking date is equal to or greater than the base date.

[0079] The vacation balance allocation processing unit 25 then generates allocation calculation target data by rearranging 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 rearranges the multiple vacation acquisition data for the same day in the following priority order: all day < first half < second half < hour, and generates allocation calculation target data.

[0080] (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, which will be described later), the vacation remaining allocation processing unit 25 deletes it as shown as "STEP 0" in FIG.

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

[0082] (Acquisition of allocation candidate 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.

[0083] (Additional processing of remaining vacation allocation data) Next, the vacation remaining allocation processing unit 25 performs additional processing on the vacation remaining allocation data as shown in Figure 28(c) based on the acquired allocation calculation target data and allocation candidate assigned data shown in Figures 28(a) and 28(b). The allocated time is the acquired time that is 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 it, so the vacation remaining allocation processing unit 25 allocates the remainder from the subsequent assigned data. As shown in Figure 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 allocated time added this time from the current remaining post-allocation time of the allocation candidate assigned data. In the example of Figure 28(d), the vacation remaining allocation processing unit 25 subtracts the allocated time added this time (480 minutes) from the current remaining post-allocation time of 780 minutes, resulting in 300 minutes as the remaining post-allocation time.

[0084] (Update processing of allocation calculation target data and allocation candidate data) Next, when the vacation remaining allocation data is additionally processed in this way, the vacation remaining allocation processing unit 25 subtracts the allocated time from the acquisition time of the allocation calculation target data (480 minutes - 480 minutes = 0 minutes) as shown in Fig. 29(a) to update the allocation calculation target data. 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 Fig. 29(b) to update the allocation candidate grant data.

[0085] 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 grant data from the second row onwards. If the remaining time is insufficient with one vacation grant data, the allocation is divided here and switched to allocation to another vacation grant data.

[0086] (Generating 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 > 0, as shown in Figure 31(a), the remaining vacation allocation processing unit 25 generates allocation error data as shown in Figure 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 Figure 30(a), if an interrupt request for taking another vacation is made before the originally scheduled vacation date, as a result, there are no grants available to allocate to the original vacation, as shown in Figure 30(b). In this case, an error is detected as a result of the allocation recalculation.

[0087] If such operations were checked in advance and prohibited, it would be difficult to take leave and would 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, and if there is remaining leave other than paid leave (compensatory leave, substitute leave, etc.), a subsequent measure can be taken, such as transferring it to another leave.

[0088] (Split allocation processing) The vacation balance allocation processing unit 25 also performs this processing 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 in the row direction. Since the remaining time for granted ID = XXX1 becomes 0, the above-mentioned divided allocation processing is performed, and the remainder is allocated to granted ID = XXX2.

[0089] Furthermore, the vacation remaining allocation processing unit 25 performs the process of adding the vacation remaining allocation data, and also performs the process of updating the allocation candidate grant data and the allocation calculation target data as described above, as shown in FIGS. 33(a) and 33(b).

[0090] (Handling of naturally extinguished records) Next, the vacation remaining allocation processing unit 25 extracts the naturally extinguished record from the allocation candidate grant data shown in Fig. 34(a), and performs additional processing to allocate the naturally extinguished portion 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.

[0091] In this way, by explicitly recording a natural extinction record in the remaining vacation allocation data at the end of the validity period, the remaining available time for all vacation can be determined by checking the remaining vacation allocation data.

[0092] [Behavior when taking leave] Next, the operation of the vacation management device 1 when taking vacation will be described using the flowchart in FIG. 11. When applying for vacation, an employee creates a vacation application including the employee code, vacation date, vacation type, and reason for application via terminal device 9, as shown in FIGS. 36(a) to 36(c), and sends it to the vacation management device 1. The example in FIG. 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 go to the hospital. The example in FIG. 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 go to the hospital.

[0093] The allocation error determination unit 26 of the vacation management device 1 checks for a deficiency in remaining vacation time as of the date of vacation acquisition requested before updating. Figures 37(a) and 37(b) show a series of row-wise 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 the row with the smallest allocation sequence number from this vacation remaining allocation data for employee A, 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. If an error is detected, 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 request.

[0094] 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, and as of the time of application on August 22, 2021, the available remaining time is 8595 minutes, and the conversion days and hours are 17.5 days, 3 hours, and 15 minutes (03:15), as shown in Figure 38. Therefore, the remaining vacation allocation processing unit 25 determines to allow the vacation to be taken.

[0095] 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 the number of days and hours converted using the "granted conversion daily predetermined hours / 2" of each remaining vacation allocation data (converted in half-day units).

[0096] Similarly, as shown in Figure 36(b), employee A applied for a full day of paid leave on September 10, 2021, to go to the hospital, and as of the time of the application on September 10, 2021, the available remaining time is 8115 minutes, and the conversion days and hours are 16.5 days, 3 hours, and 15 minutes (03:15), as shown in Figure 38. Therefore, the remaining vacation allocation processing unit 25 determines to allow the vacation to be taken.

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

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

[0099] Based on such vacation application, the vacation balance allocation processing unit 25 generates vacation acquisition data including the following fields: acquisition ID, employee code, vacation acquisition date, vacation type, remaining management category, number of acquired days, acquired time, equivalent daily hours, and reason for application, as shown in Figure 39(h). Note that the number of acquired days 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 acquired time is calculated by multiplying the number of acquired days by the equivalent daily hours. Furthermore, if the acquisition unit category is hours, the time (minutes) is calculated based on the requested time.

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

[0101] 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 FIG. 40(c), is stored in the memory unit 2. In the example of FIG. 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. Therefore, as shown in FIG. 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.

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

[0103] [Changes in the amount of time granted per day due to changes in the employee's employment status or status] 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.

[0104] 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) when making a vacation inquiry, 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 change in employee classification. 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.

[0105] Next, the employee classification change processing unit 27 converts the end balance calculated in this manner into the current daily given time (480 minutes), and calculates an end balance of 8 days, 1 hour and 15 minutes, as shown in Figure 42(a).

[0106] 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 a full-time employee to a part-time employee, as shown in Fig. 42(b). In addition, 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 career data in the employee history DB 16, as shown in Fig. 42(c).

[0107] Next, the career revision processing unit 28 adds the remaining number of vacation days, remaining hours, and equivalent daily prescribed 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 prescribed 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).

[0108] Therefore, 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. Also, the employee classification change processing unit 27 adjusts the remaining 1 hour 15 minutes (75 minutes) of vacation that the employee acquired when he / she was a full-time employee based on the ratio between the 8 hours (480 minutes) equivalent daily prescribed hours for the employee classification of a full-time employee before the employee classification change and the 5 hours (300 minutes) equivalent daily prescribed hours for the employee classification of a part-time employee after the employee classification change.

[0109] That is, 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 prescribed hours for part-time employees (5 hours) to the equivalent daily prescribed hours for full-time employees (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).

[0110] Next, when the employee classification change processing unit 27 detects operation of the registration button on the leave registration screen shown in FIG. 42(d), it adds the registered number of granted nursing leave days, registered grant time, granted hours, and equivalent daily specified hours to Mr. A's leave grant data, as shown in FIG. 42(h). In the example of FIG. 42(h), the grant date and validity period start date of the 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.

[0111] (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 vacation application for nursing leave 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.

[0112] If, after the equivalent daily prescribed hours have been changed, Mr. A submits a leave application requesting to take nursing care leave (second half) on January 24, 2022, the remaining leave allocation processing unit 25 will add the leave acquisition data for nursing care leave (second half) corresponding to the reduced-hours 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 reduced-hours employee who works five hours a day, the acquired time will be 2.5 hours, or 150 minutes. The equivalent daily prescribed hours for reduced-hours employees is 300 minutes.

[0113] Next, the vacation remaining allocation processing unit 25 adds vacation remaining 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 vacation remaining allocation data arranged row by row. As shown in Figure 43(f), by taking the nursing care leave (second half) after the employee classification change, 150 minutes of vacation time has been consumed, and the vacation time that was 2,447 minutes (remaining time after allocation) has become 2,297 minutes (2,447 minutes - 150 minutes).

[0114] In this way, even if an employee's classification is changed midway, the vacation entitlement data is divided and the equivalent daily hours before and after the employee classification change are stored separately. This allows the appropriate conversion of the remaining vacation days and hours before and after the employee classification change, and allows the correct amount of remaining vacation to be determined even after the employee classification is changed.

[0115] [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.

[0116] 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 concept of "work-life balance," which aims to harmonize work and personal life, the number of companies introducing this system has rapidly increased in recent years.

[0117] 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).

[0118] In addition, as it has become increasingly necessary to constantly adjust work arrival and departure times, more and more workers are switching to shorter working hours, taking advantage of systems for shorter working hours for childcare or for elderly care.

[0119] In addition, there is a demand for an environment in which employees can continue working while flexibly changing their working 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 working hours after a few years. Such changes to an employee's scheduled working hours require changes to the remaining status of leave in units of days and hours, making leave management tasks more complicated.

[0120] Additionally, the annual paid leave system was changed from one that only allowed leave in days to one that allowed leave to be taken in hourly increments of up to five days. In this case, if an employee had 40 days of leave remaining at the beginning of the year, the system managed the leave by hours and days separately, such as "5 days (40 hours) managed in hourly increments" and "35 days managed in day increments." As a result, if an employee used up all of their day-based leave (e.g., if they took 35 days off), they were deemed to have used up all of their leave, even if they still had leave in hourly increments. Furthermore, if the "daily scheduled working hours" changed, the "hourly leave remaining" had to be recalculated and reset based on the "new daily working hours," which was extremely cumbersome.

[0121] Additionally, while the Labor Standards Act and the Childcare and Family Care Leave Act stipulate hourly leave, the scope of system support is often limited due to gradual legal reforms and increasingly complex systems. For example, child care leave was initially only permitted in full-day increments, but a legal amendment in 2017 allowed for half-day increments, and a legal amendment in December 2019 (effective January 2021) allowed for hourly leave. It is difficult to incorporate this functionality from the outset. 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 over to the next year. Furthermore, systems cannot accommodate changes in working hours due to changes in employee status, or require manual maintenance, making the process cumbersome.

[0122] Furthermore, compliance with the system is merely a minimum requirement, and it is often not possible to accommodate cases where the company's rules of employment stipulate treatment that goes beyond what is provided for by law and is advantageous to workers (for example, allowing leave to be taken in 15-minute or 30-minute increments).

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

[0124] Furthermore, the vacation management device 1 of the embodiment can handle different calculation rules for calculating overtime hours and vacation hours by separately managing the predetermined time for calculating overtime work (e.g., 7 hours and 45 minutes) and the predetermined time for converting vacation hours (e.g., 8 hours). By storing the predetermined time for conversion in a non-normalized form in the vacation data, even if the working hours (equivalent daily predetermined hours) change due to a change in the employee classification, the data for the predetermined time that differs before and after the change can be converted uniformly.

[0125] As a result, the vacation management device 1 according to the embodiment can achieve the following effects.

[0126] 1. The vacation management device 1 of the embodiment can centrally manage multiple types of vacations in daily, half-day, and hourly units through master control, and can enable general-purpose calculations of vacation granting, acquisition, and remaining management.

[0127] 2. In the leave grant data, leave acquisition data, and remaining leave allocation data, leave is managed in minutes, and by storing the employee's "equivalent daily prescribed hours" at that time in the data, it is possible to respond to changes in employment status, etc., which change the prescribed working hours.

[0128] 3. Furthermore, since vacation time can be taken in "minute increments," which exceeds the "hourly units" required by the system, all data can be calculated based on the "minute." While it is unlikely that vacation time would be taken in one-minute increments, the vacation management device 1 of the embodiment can accommodate cases where vacation time can be taken in rounded increments such as 15 minutes, such as taking one hour and 45 minutes of vacation time in a company where working hours are 9:00 to 17:45 (total of 7 hours and 45 minutes) to go home at 16:00.

[0129] 4. By setting "Converted daily hours" in the employee classification setting master 13, you can manage the daily hours (e.g., 8 hours) for hourly leave conversion, separately from the scheduled working hours (e.g., 7.5 hours) for work performance calculations according to the employment type. Also, the currently available leave data, leave consumption data, and remaining leave allocation data can be automatically reflected in the converted daily hours. Furthermore, when a day's leave is allocated to hourly leave, conversion can be performed in one-hour increments to avoid fractional amounts.

[0130] 5. In addition, by managing the history of changes to employee classifications in the Employee Master 15, the history of vacation grant data can be automatically revised, and accurate vacation balances can be carried over even after changes to scheduled working hours by extinguishing existing vacation and re-granting it in hours and minutes due to changes in scheduled working hours.

[0131] 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 the control of multiple types of leave. This allows for flexible settings according to the work regulations or system revisions adopted by the company, such as leave that can only be taken in days, leave that can be taken in hourly units, etc.

[0132] 7. Based on the relationship between the expiry date of vacation grant data and the date of vacation acquisition, priority allocation that does not disadvantage workers can be accurately calculated and managed even when vacation acquisition in units of days or hours is mixed.

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

[0134] Because the vacation management device 1 of the embodiment can achieve these effects, companies can introduce the vacation management device 1 of the embodiment while reducing the burden and costs of labor management. Also, 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.

[0135] 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 in daily increments but also in hourly increments. Furthermore, even within 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 in hourly or daily increments, and can smoothly change remaining leave even when 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.

[0136] [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.

[0137] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0138] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0139] [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.

[0140] For example, among 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.

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

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

[0143] For example, all or any part of the processing functions of the vacation management device 1, particularly the control unit 3 and the processing functions performed by the control unit 3, may be realized by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized 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 for working with the OS to issue instructions to the CPU and perform various processes. The computer program is executed by being loaded into RAM and works with the CPU to constitute the control unit 3.

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

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

[0146] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration 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 configurations and procedures.

[0147] 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 providing websites.

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

[0149] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional additions. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0150] The present invention is useful for managing employee vacation time. [Explanation of symbols]

[0151] 1. Vacation management device 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / output interface section 6 Input Devices 7 Output Devices 8 Network 9 Terminal Equipment 11 Vacation Remaining Management Category Master 12 Leave type master 13 Employee classification setting master 14 Working Hours Master 15 Employee Master 16 Employee History Database 21 Display control unit 22 Input processing section 23 Update processing section 24 Vacation Remaining Determination Department 25. Vacation Remaining Allocation Processing Unit 26 Allocation error determination unit 27 Employee classification change processing unit 28 Career Revision Processing Department

Claims

[Claim 1] a vacation time conversion processing unit that converts the number of vacation days granted to a vacation recipient into hours and forms total vacation time by multiplying the number of vacation days that the vacation recipient can take by the number of working hours in one day that is set according to the employment status of the vacation recipient; and a vacation time conversion processing unit that converts the vacation period applied for by the vacation taker into vacation hours based on the daily working hours set according to the employment status of the vacation taker; a remaining vacation time calculation unit that calculates remaining vacation time by subtracting the vacation time taken from the total vacation time; A vacation management device having:

Images