JP6986428B2 - Working time calculator, working time calculation method and working time calculation program - Google Patents

Description

The present invention relates to a working time calculation device, a working time calculation method and a working time calculation program.

In Patent Document 1, the working hours are quantized in unit hours for each business item, the quantized time zones are made to correspond to the cells on the working management table, the cells are displayed on the working management table, and the pointing device is described. Use to select a range of cells by specifying the time axis direction for a specific business item and display the cells in the selected range to indicate that the working hours have been entered for a specific business item, pointing device. For a specific business item, select a range of cells by specifying the direction opposite to the time axis, undisplay the cells in the selected range in order, and the work input was canceled for the specific business item. A time input method is disclosed to indicate that (see paragraph "0020", etc.).

Japanese Unexamined Patent Publication No. 2008-065527

By the way, by adopting a system that allows paid leave to be taken on an hourly basis, multiple reasons for absence such as paid leave and breaks can be combined in a day, such as taking paid leave on an hourly basis with a lunch break in between. Can occur in. In the conventional technique, input control that causes an input error when trying to register different reasons for absence in the same time zone is common. Therefore, when multiple reasons for absence occur in combination in a day, it is necessary to devise the registration of the reasons for absence according to the input control, which makes the registration and management of the reasons for absence complicated. There was a point. This problem cannot be solved even in the above-mentioned Patent Document 1.

The present invention has been made in view of the above, and an object of the present invention is to facilitate registration and management of events when a plurality of events occur in combination.

In order to solve the above-mentioned problems and achieve the object, the working time calculation device according to the present invention is a working time calculation device including a control unit and a storage unit, and the control unit accepts input by a user. Each time zone according to the input means, the working time zone where the reason type is work, the break time zone where the reason type is a break, and the absent time zone where the reason type is absent, which are input by the input means. A storage means for storing a plurality of time information indicating a start time and an end time, and a reason type indicating the content of absence, and a plurality of times stored in the storage unit for a day's time. Create a means to create a section between adjacent divisions by setting a division separated by the time indicated by the information and a predetermined time, and create a working time zone, a break time zone, and an absent time zone. Of the division means that divides each section created by the means to generate the division time zone and the section created by the creation means, the section including one or more division time zones has the highest division time zone. The selection means for selecting the division time zone corresponding to the reason type for which the priority is set for each section and the division time zone selected by the selection means are aggregated for each division time zone with the same reason type. It is characterized by having a counting means.

Further, in the working time calculation device according to the present invention, the selection means is characterized in that the division time zone is selected for each section based on the priority master in which the reason type and the priority are associated with each other.

Further, in the working time calculation device according to the present invention, the input means inputs an input in which at least two time zones of the working time zone, the break time zone, and the absent time zone have overlapping portions. It is characterized by accepting.

Further, the working time calculation device according to the present invention is characterized in that the input means can accept input of a plurality of break time zones and absent time zones for one day, respectively.

Further, in the working hour calculation device according to the present invention, the input means accepts input of a reason type further indicating the content of absence for each of a plurality of absent time zones, and a plurality of different reason types indicating the input content of absence. It is characterized in that it is possible to accept an input having an overlapping portion in the absence time zone of.

Further, in the working hour calculation device according to the present invention, the input means inputs the reason type further indicating the content of absence based on the absence reason master in which the reason type and the absence reason indicating the content of absence are associated. It is characterized by.

Further, in the working time calculation device according to the present invention, the creating means sets the start time and the end time of each of the predetermined working time zone and the midnight time zone as predetermined times, and sets the delimiter as the aggregation means. Divides the working hours selected by the selection means based on the start time and the end time of each of the working hours and the midnight hours, and further divides the working hours into and out of the working hours, and It is characterized in that it is aggregated separately within the midnight time zone and outside the midnight time zone.

Further, in the working time calculation device according to the present invention, the input means can input a plurality of time information in the minimum time unit managed by the control unit.

Further, the working time calculation method according to the present invention is a working time calculation method executed by a working time calculation device including a control unit and a storage unit, and is an input executed by the control unit that accepts input by a user. Start of each time zone according to the step, the working time zone where the reason type is work, the break time zone where the reason type is break, and the absent time zone where the reason type is absent, which are input by the step and the input step. A storage step for storing a plurality of time information indicating the time and an end time and a reason type indicating the content of absence in the storage unit, and a plurality of time information stored in the storage unit for the time of the day. A step to create a section between adjacent delimiters by setting a delimiter separated by a time indicated by and a predetermined time, and a step to create a working time zone, a break time zone, and an absent time zone. Of the division steps that generate the division time zone by dividing each section created by, and the section that includes one or more division time zones among the sections created by the creation step, the highest priority among the division time zones. A selection step that selects the division time zone corresponding to the reason type for which the degree is set for each section, and a division time zone selected by the selection step are aggregated for each division time zone with the same reason type. It is characterized by including steps.

Further, the working time calculation program according to the present invention is a working time calculation program for causing an information processing apparatus including a control unit and a storage unit to execute, and accepts input by a user for causing the control unit to execute. Each time zone according to the input step, the working time zone where the reason type is work, the break time zone where the reason type is break, and the absent time zone where the reason type is absent, which are input by the input step. A storage step for storing a plurality of time information indicating a start time and an end time and a reason type indicating the content of absence in the storage unit, and a plurality of times stored in the storage unit for a day's time. Create a step to create a section between adjacent delimiters by setting a delimiter separated by the time indicated by the information and a predetermined time, and create a working time zone, a break time zone, and an absent time zone. The highest of the division time zones in the division step that divides each section created by the step to generate the division time zone and the section that includes one or more division time zones in each of the sections created by the creation step. The selection step that selects the division time zone corresponding to the reason type for which the priority is set for each section and the division time zone selected by the selection step are aggregated for each division time zone with the same reason type. It is characterized by including an aggregation step.

According to the present invention, there is an effect that registration and management of events when a plurality of events occur in combination are facilitated.

FIG. 1 is a diagram for schematically explaining an existing registration method when a plurality of absentee events occur in combination. FIG. 2 is a diagram for schematically explaining an existing registration method when a plurality of absentee events occur in combination. FIG. 3 is a diagram showing a configuration example of a working hour calculation system applicable to the embodiment. FIG. 4 is a block diagram showing an example of a hardware configuration applicable to the working time calculation device according to the embodiment. FIG. 5 is a functional block diagram for explaining the function of the working hour calculation device according to the embodiment. FIG. 6 is a diagram showing an example of an input screen for inputting and registering work information data, which is applicable to the embodiment. FIG. 7 is a diagram showing an example of an absentee reason master according to an embodiment. FIG. 8 is a diagram showing an example of a priority master according to an embodiment. FIG. 9 is a flowchart showing an example of processing in the working time calculation device according to the embodiment. FIG. 10 is a diagram schematically showing an example of reason detail data according to an embodiment. FIG. 11 is a schematic diagram schematically showing an example of creating event detail data according to an embodiment. FIG. 12 is a diagram schematically showing an example of reference time detailed data according to an embodiment. FIG. 13 is a schematic diagram schematically showing an example of creating reference time detailed data according to an embodiment. FIG. 14 is a diagram schematically showing an example of reason detail division data according to an embodiment. FIG. 15 is a schematic diagram schematically showing an example of creating reason detail division data according to an embodiment. FIG. 16 is a diagram showing the reason detail division data according to the embodiment by using a block that divides the time zone of the day. FIG. 17 is a diagram for explaining the grouping process according to the embodiment. FIG. 18 is a diagram for explaining the process of generating the reason detail division extraction data according to the embodiment. FIG. 19 is a diagram showing an example of predetermined aggregation conditions for extracting a section from the reason detail division extraction data according to the embodiment. FIG. 20 is a diagram for explaining an aggregation method according to an embodiment. FIG. 21 is a diagram showing an example of an input screen on which the aggregation result is displayed according to the embodiment.

Hereinafter, embodiments of the working hours calculation device, the working hours calculation method, and the working hours calculation program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment.

[1. Overview]
In recent years, with the keyword "work style reform", proper management of working hours has become more important, and along with this, expectations and needs for time and attendance management systems have also increased. In work style reform, for example, it is necessary for management departments and supervisors to accurately grasp the exact working conditions of workers, prevent overwork, and encourage regular leave to be taken. .. Therefore, it is necessary to appropriately register and manage the daily work status of workers on an hourly (minute) basis.

On the other hand, as a measure to encourage effective leave acquisition according to various work styles, there are an increasing number of cases where paid leave (hereinafter referred to as hourly paid leave) can be taken on an hourly basis. Examples of ways to use paid holidays include balancing work and life (such as going to the hospital during the day) and working in a well-balanced manner (adjusting work and returning one hour earlier than usual).

With the introduction of paid holidays, multiple reasons for absence, such as vacations and breaks, will occur in combination during the day, and the combination of acquisition times will also diversify. On the other hand, when a combination of a plurality of reasons for absence occurs, there is a problem that management becomes complicated with the existing registration method. In the existing registration method, it is common to control that different reasons cannot be registered in duplicate in the same time zone (input error), and the data is divided and registered according to the input control. This is because it is necessary to adjust the input method.

The existing registration method when a plurality of absentee reasons occur in combination will be schematically described with reference to FIGS. 1 and 2. FIG. 1 shows an example of a work schedule for a certain employee (assumed to be an employee with employee ID “A”) on a certain day (September 3, 2017). In the following, the time is described in 24-hour notation. Further, an employee with an employee ID "A" is referred to as an employee A.

In the example of FIG. 1 (a), the work start time is the time "09:00", the work end time is the time "18:00", the break start time is the time "12:00", and the end time is the time. It is said to be "13:00". Further, the employee A takes time holidays with the start time as the time "11:00" and the end time as the time "14:00" with the break time in between. That is, the time paid holiday in this case includes a break time from the time "12:00" to the time "13:00". As shown in FIG. 1 (b), each time has a vacation time of 2 hours (120 minutes) and a break time of 1 hour (60 minutes) due to paid holidays. In addition, the actual working hours are 6 hours (360 minutes) obtained by subtracting these vacation times and break times from the time from the start time to the end time (9 hours).

FIG. 2 schematically shows an example of registering the work schedule shown in FIG. 1 (a) using the existing technology. FIG. 2A schematically shows the actual attendance of employee A according to the work schedule of FIG. 1A. Employee A starts work at the time "09:00" of the work start time, and suspends work at the time "11:00" of the start time of the paid holidays. A break time (time "12:00" to time "13:00") is sandwiched between the time "11:00" and the time "14:00" acquired as time holidays. This break time is a break that is considered to be during the vacation time due to paid holidays, and is the original right of employee A. Employee A resumes work from the time "14:00" at the end time of the paid holidays, and continues to work until the time "18:00" at the end time of the work.

A first example of the registration method by the existing technique will be described with reference to FIG. 2 (b). This first example is an example in which the reason for each time zone is correctly registered. When the break time (time "12:00" to time "13:00") is predetermined, as shown in FIG. 2 (b), the time holiday is set to the time "11" which is the time before the break time. The work schedule is divided into a time zone from ": 00" to the time "12:00" and a time zone from the time "13:00" to the time "14:00", which is the time after the break time. Additional registration. In the first example, by registering the paid holidays in two steps in this way, the duplicate registration of the paid holidays and the break time is avoided.

A second example of the registration method using the existing technique will be described with reference to FIG. 2 (c). This second example is an example of collectively registering time-paid holidays that are divided into two with a break time in between. In this case, for example, by shifting the break time, which is originally the time "12:00" to the time "13:00", to the time "13:00" to the time "14:00", the time is long. A continuous time zone for two hours (time "11:00" to time "13:00") is secured, and time holidays are registered in this time zone. This makes it possible to avoid duplicate registration of paid holidays and breaks. On the other hand, in this second example, the registration itself for paid holidays can be done only once, but it is necessary to shift the acquisition time of the breaks.

The work schedule shown in FIG. 1 (a) is an example of a pattern, and is actually a combination of reasons such as "half-day break and break", "private outing and break", and "private outing and vacation". Various derivation patterns can occur depending on the number and the degree of overlap of time. In particular, in the example of FIG. 1 (a), the reason is divided by a good time (in this case, in 1-hour units) such as time "11:00", time "12:00", and time "13:00". Although it has expired, in reality, it is necessary to assume that it is managed accurately in minutes, such as time "11:15", time "12:30", and so on.

In addition, the Labor Standards Law requires payment of a late-night premium wage for work during the midnight hours (time "22:00" to the next day's time "05:00"). Therefore, it is also necessary to distinguish whether or not the entered work, break and vacation time zone is the midnight time zone. In addition, the work rules may stipulate extra wages for work outside the standard working hours (prescribed working hours) per day, so the entered working hours, breaks, and vacation hours are not prescribed. It is also necessary to distinguish whether it is the time zone or not.

In the embodiment, the above-mentioned problems are solved by the following policy.
-For each type of absentee reason, set a priority when multiple reasons overlap.
-On the input screen for registering attendance information, it is permitted to input different types of reasons for absence, including overlapping time zones.
-In the aggregation process after registering attendance information, the breaks, duplications, and priorities of reasons are automatically determined, and the correct breakdown time is calculated.
-In addition to the breaks for reasons, the start time and end time of scheduled work, and the breaks between the start time and end time of the midnight time zone are also determined, and overtime work hours and midnight work hours can be aggregated.

More specifically, in the present embodiment, registration of a plurality of time zones having different reasons for having overlapping portions is permitted, each time zone is divided according to the start time and end time of these multiple time zones, and each reason is divided into each time zone. According to the priority set, one is selected from the overlapping reasons in the divided time zone. As a result, even when a plurality of reasons occur in combination, it is possible to realize registration in which each reason is separated by a simple registration method.

[2. composition]
The configuration of the working hours calculation device according to the embodiment will be described. FIG. 3 shows a configuration example of a working hour calculation system applicable to the embodiment. The working hours calculation system according to the embodiment is suitable for use in an organization such as a company or a store where the wage calculation changes depending on the working hours and the reason for absence. In the following, the working hours calculation system according to the embodiment will be described as being applied to a company.

FIG. 3A is an example in which the working time calculation system includes the working time calculation device 10 according to the embodiment and the server 20 connected to the network 30. The working time calculation device 10 displays an input screen for inputting time information such as attendance / leaving time, break time, and absence time on the display, and a user (employee, etc.) inputs these time information according to this input screen. Input directly to the working time calculation device 10.

The server 20 includes, for example, an employee master for managing employee information, and can provide employee information to the working time calculation device 10. It is also possible to include the function of the server 20 in the working time calculation device 10.

FIG. 3B is an example in which an input terminal 40 connected to the network 30 is added to the configuration described in FIG. 3A. The working time calculation device 10 transmits display information for displaying an input screen for the user to input time information to the input terminal 40 via the network 30. The input terminal 40 causes the display to display the input screen according to the display information sent from the working time calculation device 10. The user inputs the time information according to the input screen displayed on the input terminal 40. The input terminal 40 transmits the input time information to the working time calculation device 10 via the network 30.

FIG. 4 shows an example of a hardware configuration applicable to the working time calculation device 10 according to the embodiment. In FIG. 4, the working hours calculation device 10 includes a CPU (Central Processing Unit) 1000, a ROM (Read Only Memory) 1001, a RAM (Random Access Memory) 1002, a graphic I / F (interface) 1003, and a storage 1004. The input / output I / F 1005 and the communication I / F 1006 are included, and each of these parts is communicably connected to each other by the bus 1010. As described above, the working time calculation device 10 according to the embodiment can be configured by using a general computer as an information processing device.

The storage 1004 is a non-volatile storage medium such as a hard disk drive or a flash memory, and stores a program for operating the CPU 1000 and various data. The CPU 1000 uses the RAM 1002 as a work memory according to a program stored in the storage 1004 and the ROM 1001 to control the overall operation of the working time calculation processing device 10.

The graphic I / F 1003 converts a display control signal generated by the CPU 1000 according to a program into an image signal compatible with the display 1020 and outputs the signal. As a result, the screen according to the program can be displayed on the display 1020.

The input / output I / F 1005 is an interface for inputting / outputting data to / from an external device. As the input / output I / F 1005, for example, USB (Universal Serial Bus) can be applied. In the example of FIG. 4, an input device 1021 that outputs a control signal corresponding to a user operation is connected to the input / output I / F 1005. The control signal output from the input device 1021 in response to the user operation is sent to the CPU 1000 via the input / output I / F 1005.

A keyboard or a pointing device can be applied to the input device 1021. Not limited to this, as the input device 1021, a touch panel configured integrally with the display device may be applied, or a microphone for performing voice input may be applied. When applying a microphone as the input device 1021, the input / output I / F 1005 includes an A / D converter that converts an analog audio signal into a digital audio signal. Further, a printer or a speaker can be connected to the input / output I / F 1005 as an output device. When applying a speaker as an output device, the input / output I / F 1005 includes a D / A converter that converts a digital audio signal into an analog audio signal.

The communication I / F 1006 communicates with a network such as a LAN (Local Area Network) or the Internet according to the instruction of the CPU 1000.

Since the server 20 and the input terminal 40 shown in FIG. 3B can be realized with the same configuration as the working time calculation device 10 of FIG. 4, the description thereof is omitted here.

FIG. 5 is a functional block diagram for explaining the function of the working hour calculation device 10 according to the embodiment. Note that FIG. 5 is a functional block diagram assuming the configuration described with reference to FIG. 3A.

In FIG. 5, the working time calculation device 10 includes a control unit 110, a storage unit 120, an input / output I / F (interface) unit 130, and a communication I / F 140 unit. Of the control unit 110, the storage unit 120, the input / output I / F unit 130, and the communication I / F unit 140, the control unit 110, the input / output I / F unit 130, and the communication I / F unit 140 operate on the CPU 1000. It consists of the execution of the working hours calculation program. As the storage unit 120, for example, predetermined storage areas of the storage 1004 and the RAM 1002 are used.

It is also possible to configure a part or all of the control unit 110, the storage unit 120, the input / output I / F unit 130, and the communication I / F unit 140 by a hardware circuit that operates in cooperation with each other.

The storage unit 120 includes an input information storage unit 121 and a data storage unit 125, and stores each master of the absence reason master 122 and the priority master 123. Of these, for the input information storage unit 121 and the data storage unit 125, for example, a predetermined area of the RAM 1002 or the storage 1004 is applied. Further, the absence reason master 122 and the priority master 123 are stored non-volatilely in the storage 1004.

Although the storage unit 120 is shown to include the employee master 124 in FIG. 5, the employee master 124 is actually stored in the server 20. As in the example of FIG. 5, the working time calculation device 10 may store the employee master 124.

In the storage unit 120, the input information storage unit 121 stores work information data including the reason type and the time information corresponding to the reason type, which is input by the user (for example, an employee) according to the input screen.

FIG. 6 shows an example of an input screen for inputting and registering work information data, which is applicable to the embodiment. In FIG. 6A, the input screen 200 is generated by the UI unit 111 described later and is displayed on the display 1020, for example, and includes the input units 2000 and 2100 and the aggregation result information display unit 2200. The input unit 2000 includes each input area for inputting the identification information (referred to as an employee ID) of the user (employee) who inputs to the input screen 200 and the date. The date may be automatically input by, for example, the calendar function provided in the working time calculation device 10.

In the following, the explanation will be given assuming that employee A inputs the work schedule on September 3, 2017.

The input unit 2100 provides information on working hours such as attendance time and leaving time for the reason type "work", start time and end time for the reason type "break", and start time and end time for the reason type "absence reason". , 2101, 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 ₂ , ....

Each input area included in the input screen 200 will be described in more detail. The input area 2101 is an area for inputting a start time and an end time of a predetermined time defined as working hours, for example. The predetermined time is a time zone predetermined by the system as a working time zone, and values set by the system can be input in advance for the start time and the end time of the predetermined time. The system referred to here is, for example, an employment management system including a working time calculation device 10, and is operated by an organization such as a company. In the example of FIG. 6A, the time "09: 00" and the time "17:30" are input in advance to the input area 2101 as the start time and end time of the predetermined time.

The input area 2102 is an area for inputting the attendance time and the leaving time indicating the start time and the end time of the working time zone whose reason type belongs to "working". In the example of FIG. 6A, the attendance time and the leaving time are shown as the attendance record.

The input areas 2103 ₁ , 2103 ₂ , ... Are areas for inputting the start time and end time of the break time zone in which the reason type belongs to "break", respectively. In the example of FIG. 6A, a plurality of break time zones (break 1, break 2, ...) can be set in one day as shown as _{input areas 2103 1} , 2103 _{2, ....} .. Further, in the example of FIG. 6A, in the break time zone indicated by "break 1", the time "12:00" and the time "13:00" are input in advance by the system as the start time and the end time. There is.

The input areas 2104 ₁ , 2104 ₂ , ... Are areas for inputting the absentee reason, start time and end time of the absentee reason time zone whose reason type belongs to "absent reason", respectively. In the example of FIG. 6A, a plurality of absentee reasons (absent reason 1, absent reason 2, ...) can be set in one day as shown as _{input areas 2104 1} , 2104 _{2, ....} There is.

In each input area 2104 ₁ , 2104 ₂ , ..., The area indicated by "reason" is an area for inputting the content of the reason for absence. In the area, the content of the absentee reason selected from a plurality of reason types based on the absentee reason master 122 whose details will be described later is input.

The input information storage unit 121 uses each information input to each input area 2101, 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 ₂ , ... Included in the input unit 2100 as work information data, and is an input unit. It is stored in association with the employee ID and date entered in 2000.

On the input screen 200, the aggregation result information display unit 2200 is based on the values input to the input areas 2101, 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 _{2, ...} The actual total information, which is the total result of the total, is displayed. In the example of FIG. 6A, the aggregation result information display unit 2200 aggregates the scheduled actual working hours, the non-scheduled actual working hours, the actual working hours, the late-night working hours, the break time, the paid vacation hours, and the non-working hours, respectively. Includes display areas 2201-2207 for displaying. The method of totaling each time displayed in each of these display areas 2201 to 2207 will be described later.

In the example of FIG. 6, each item is arranged in the horizontal direction in the input screen 200, but this is not limited to this example, and the layout of the input screen 200 is arbitrary. For example, each item may be arranged vertically to form a detailed screen. Further, the input information storage unit 121 stores the work information data input to the input screen 200 in the input information storage unit 121, for example, by using a table having a configuration similar to that of the input screen 200.

Next, the absence reason master 122 according to the embodiment will be described more specifically. FIG. 7 shows an example of the absence reason master 122 according to the embodiment. The absentee reason master 122 is stored in advance in the storage unit 120 in association with the absentee reason type related to the absence and the absentee reason indicating the content of the absence. In FIG. 7, the absence reason master 122 includes each item of “absence reason”, “absence unit classification”, and “reason type” in the record, and defines the absence reason of the user. The name of the reason for absence is defined in the item "reason for absence". In the example of FIG. 7, for the item "reason for absence", "all day paid leave", "first half paid leave", "second half paid leave", "hourly paid leave", "nursing leave", "late arrival" and "all day absenteeism" The name of the reason for absence is defined.

In the input screen 200 described above, _{the content of the absentee reason input to the area indicated by "reason" in each input area 2104 1} , 2104 ₂ , ... Is from each absentee reason name defined in this item "absent reason". Be selected.

In the item "absence unit classification", the unit of the time zone to be absent is defined. In the example of FIG. 7, "all day", "first half", "second half" and "time" are defined. Of these, "all day," "first half," and "second half" have a predetermined time zone as a unit of absence in the predetermined time specified as working hours. For example, "all day" is the time zone from the start time to the end time of the predetermined time, and "first half" and "second half" are the first half (for example, in the morning) and the second half (for example, in the morning) specified for the predetermined time, respectively. For example, the time zone (afternoon) is the unit of absence. Input control such as fixing the time zone is possible for these "all day", "first half" and "second half". In addition, "time" can be set to any time, and the time zone of the unit of absence is not fixed. In the example of FIG. 7, the absentee unit section of the absentee reason "all day paid leave", "nursing leave" and "all day absenteeism" is "all day", and the absentee unit section of the absentee reason "first half paid leave" and "second half paid leave" is "first half" respectively. "And" second half ", and the absentee unit section of the reasons for absence" time paid "and" late "is defined as" time ".

The item "reason type" is a reason type related to absence, and defines an absentee reason, for example, an institutional type in the company among all the reason types. In the example of FIG. 7, three types of reasons, "paid leave," "unpaid leave," and "non-working," are defined. Of these, the types of reasons "paid leave" and "unpaid leave" are treated as vacations, "paid leave" is the type of reason for which the default wage is paid, and "unpaid leave" is the type of reason for which wages are not paid. Is. On the other hand, the reason type "non-working" is a reason for absence that is not treated as a vacation, and is a type of reason for which wages are not paid and penalties are imposed in some cases.

Next, the priority master 123 according to the embodiment will be described more specifically. FIG. 8 shows an example of the priority master 123 according to the embodiment. In FIG. 8, the priority master 123 includes each item of “reason type” and “priority” in the record, and associates the priority with the reason type. In the example of FIG. 8, in the item “priority”, the priority is defined in four stages from the highest priority “1” to the lowest priority “4”. For each of these priorities "1" to "4", "break", "paid leave", "unpaid leave / unemployed", and "work" defined by the item "reason type" are associated with each other. ..

More specifically, the reason type "break" is a right that is always granted for working hours above a certain level, and the highest priority is set. The reason type "paid leave" is a leave that has the right to be taken for a fee under specific conditions according to laws and regulations and work regulations, and the highest priority is set after the break. Reason types "Unpaid leave" and "Unemployed" (collectively shown as "Unpaid leave / Unemployed" in Fig. 8) are treated as unpaid, such as nursing care leave, private outing, absenteeism, and late arrival due to personal reasons. The lowest priority is set for breaks and absenteeism, which is the time of absence that is considered subject to penalties. In addition, the reason type "work" is the time considered to be actual working hours as a result of deducting all the above-mentioned breaks and absences, and the lowest priority is set compared to other breaks and reasons for absence. ..

The association of the priority for each reason type defined in the item "reason type" in the priority master 123 is not limited to the example of FIG. Further, the reason type defined in the item “reason type” is not limited to the example of FIG. Furthermore, the priority for freedom of absence can be switched by the priority master etc. in consideration of laws and regulations and work rules, but it is rational to give higher priority to the reason for absence with strong rights of the user (employee). It is a target.

The data storage unit 125 is, for example, a storage area used as a work area of the control unit 110, and is a reason detail data 300, a reference, which is generated based on processing according to the work information data stored in the input information storage unit 121. Each data including the time detail data 310, the reason detail division data 320, and the reason detail division extraction data 330 is stored volatilely or non-volatilely. Specific examples of the reason detail data 300, the reference time detail data 310, the reason detail division data 320, and the reason detail division extraction data 330 will be described later.

In FIG. 5, the control unit 110 includes a UI (User Interface) unit 111, a storage management unit 112, a creation unit 113, a division unit 114, a selection unit 115, and an aggregation unit 116.

The UI unit 111 generates the above-mentioned input screen 200, and displays the generated input screen 200 on the display 1020. Further, the UI unit 111 receives each data input according to the input screen 200. For example, on the input screen 200, the UI unit 111 transfers the employee ID and date information input to the input unit 2000 and the work information data input to each input area of the input unit 2100 via the input / output I / F 1005. To receive. The UI unit 111 passes the received employee ID, date information, and work information data to the storage management unit 112.

The storage management unit 112 controls the management of the data stored in the storage unit 120, the storage of the data in the storage unit 120, and the reading of the data from the storage unit 120. For example, the storage management unit 112 stores the employee ID, date information, and work information data passed from the UI unit 111 in the input information storage unit 121 included in the storage unit 120. Further, when the data stored in the storage unit 120 (for example, the employee master 124) is the data on the server 20, the storage management unit 112 requests the server 20 to store and update the data, and the data. Send an acquisition request.

The creation unit 113 enumerates the reason types set on a certain work day (September 3, 2017) by a certain employee (assumed to be employee A) based on a plurality of time information input according to the input screen 200. Then, for each reason type, the reason detail data 300, which is the data in which the priority is associated with the start time and the end time, is created. The creation unit 113 further divides the time of the day according to a plurality of start times and end times included in the generated reason detail data 300 and a predetermined time, and a section sandwiched between adjacent divisions. (Reference time detailed data 310). That is, the creation unit 113 sets a delimiter for the time of the day, which is divided by a time indicated by a plurality of time information stored in the input information storage unit 121 of the storage unit 120 and a predetermined time. Then, a section sandwiched between the adjacent sections is created.

The division unit 114 combines the reason detail data 300 and the reference time detail data 310 according to predetermined conditions, and divides the time of the day into sections sandwiched between adjacent divisions based on the reference time detail data 310. The divided data 320 is generated. That is, the division unit 114 divides the working time zone, the break time zone, and the absent time zone into each section created by the creation unit 113 to generate the division time zone.

Based on the reason detail division data 320, the selection unit 115 selects the reason type associated with the highest priority for each section in which different reason types overlap in each section divided by the reason detail division data 320. Reason detail division Extraction data 330 is generated. That is, the selection unit 115 has a division time corresponding to the reason type in which the highest priority among the division time zones is set in the section including one or more division time zones in each of the sections created by the creation unit 113. Select the band for each section.

The aggregation unit 116 aggregates each division time zone selected by the selection unit 115 for each division time zone having the same reason type. The aggregation result is displayed on the aggregation result information display unit 2200 included in the input screen 200 by the UI unit 111. Not limited to this, the UI unit 111 may generate a display screen for displaying the aggregation result separately from the input screen 200. Further, the aggregation unit 116 may store the aggregation result in the storage unit 120, or may transmit the aggregation result to the outside (for example, the server 20) via the network 30.

In the working hour calculation device 10, the input / output I / F 130 unit is connected to the input device 150 and the output device 151. As an example, in the working hour calculation system shown in FIG. 3A, the input device 150 corresponds to, for example, the input device 1021 in FIG. 4, and the input / output I / F unit 130 controls the input / output I / F 1005. Then, input data corresponding to the control signal output from the input device 1021 is generated and passed to the control unit 110. The output device 151 is, for example, the display 1020 in FIG. 4, and the input / output I / F unit 130 controls the graphic I / F 1003 to convert the display control signal generated by the CPU 1000 into an image signal and display the display 1020. Supply to.

As another example, in the working hour calculation system shown in FIG. 3B, the input device and the display connected to the input terminal 40 can be made to correspond to the input device 150 and the output device 151, respectively.

The communication I / F unit 140 controls the communication I / F 1006 in FIG. 4 to perform communication with the network 30.

The working time calculation device 10 can communicate with the server 20 via the network 30 under the control of the communication I / F unit 140. Each master stored in the storage unit 120 may be stored in the server 20.

The working time calculation program for realizing each function according to the embodiment in the working time calculation device 10 is provided by recording a file in an installable format or an executable format on a computer-readable recording medium. .. Recording media that can be read by this computer include memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), and EEPROMs (registered). Any portable use such as (Electrically Erasable and Programmable Read Only Memory), CD (Compact Disk), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Blu-ray (registered trademark) Disc. It shall include physical media. Therefore, a recording medium containing a program for executing a process or a process method as described below in the present specification also constitutes the present invention.

Not limited to this, the working hours calculation program may be provided by storing it on a computer connected to a network such as the Internet and downloading it via the network. In addition, the working hours calculation program may be configured to be provided or distributed via a network such as the Internet.

The working hours calculation program includes a control unit 110 (UI unit 111, a storage management unit 112, a creation unit 113, a division unit 114, a selection unit 115 and an aggregation unit 116), an input / output I / F unit 130, and a communication I / F unit. It has a module configuration including 140. As actual hardware, when the CPU 1000 reads the working hour calculation program from a storage medium such as ROM 1001 and executes it, each of the above-mentioned parts is loaded on a main storage device such as RAM 1002, and the control unit 110 (UI unit 111) is loaded. , Storage management unit 112, creation unit 113, division unit 114, selection unit 115 and tabulation unit 116), input / output I / F unit 130 and communication I / F unit 140 are now generated on the main storage device. There is.

Further, the "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by an OS (Operating System). Including those that achieve the function.

[3. Processing according to the embodiment]
Next, the process according to the embodiment will be described. FIG. 9 is a flowchart showing an example of processing in the working time calculation device 10 according to the embodiment. Prior to the execution of the flowchart of FIG. 9, each input area 2101, 2102, 2103 ₁ , 2103 included in the input unit 2100 by the user (employee) according to the input screen 200 described with reference to FIG. 6A. _{For 2} , ..., 2104 ₁ , 2104 ₂ , ..., The work information data including the predetermined time, the time of attendance and departure, the start and end times of the break, and the start and end times of the reasons for absence are input. Inputs to the input areas 2103 ₁ , 2103 ₂ , ..., And the input areas 2104 ₁ , 2104 ₂ , ... Are performed as necessary.

In the input screen 200 of FIG. 6A described above, each time information and the reason for absence are input to each input area 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 _{2, ...} An example is shown in FIG. 6 (b). Here, it is assumed that each time information and the reason for absence are input according to the work schedule explained with reference to FIG. 1 (a).

In the examples of FIGS. 6A and 6B, each input area of the input unit 2000 and the input areas 2101 and 2103 ₁ of the input unit 2100 have their respective values input in advance by the system. And. More specifically, the employee ID "A" and the working day "2017/09/03" are input by the system for each input area of the input unit 2000. Further, the time "09: 00" is input to the input area 2101 of the input unit 2100 as the start time of the predetermined time, and the time "17:30" is input as the end time by the system. Further, the time "12:00" is input to the input area 2103 ₁ as the start time of the break time zone of the break 1, and the time "13:00" is input as the end time by the system.

On the other hand, among the input areas 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 _{2 , ..., Each input area excluding the input area 2103 1 in} which input is made in advance by the system is a user (for example, an employee) according to the input screen 200. Each value is input by A). In the example of FIG. 6B, the time "09: 00" is input to the input area 2102 as the attendance time, and the time "18:00" is input as the leaving time by the employee A. Further, the time "11:00" is input to the input area 2104 ₁ as the start time of the absence time zone of the absence reason 1, and the time "14:00" is input as the end time. Further, in the input area 2104 ₁ , the absentee reason "time paid holiday" is input for the item "reason".

Here, in the work schedule shown in FIG. 1A, the time zone (time “11:00” to time “14:00”) acquired as a time holiday is set as a time zone (time “time”). 12:00 "to time" 13:00 ") is included. As illustrated in FIG. 6B, in the input screen 200, in the input area 2104 ₁ , the time “11:00” is set as the start time and the end time of the absent time zone in which the reason is “time paid”, which is the reason for absence. "And" 14:00 "are input. In addition, the input area 2103 _1, as a time zone that is included in the absence time zone that is input to the input area 2104 _1, the time "12:00" as the start time and end time of the break time zone reason is "break" and "13:00" is input.

As described above, the input screen 200 according to the embodiment has _{the overlapping time for such different reasons as shown in the input area 2103 1} and the input area 2104 ₁ (shown with a thick frame, respectively). Allows band input.

Further, the input screen 200 according to the embodiment _{also duplicates the input areas 2104 1} , 2104 ₂ , ... For inputting the reasons for absence if the contents of the reasons for absence input in the area indicated by "reason" are different. You are allowed to enter the time zone. For example, on the input screen 200, the absence due to the above-mentioned "private outing" and the absence due to "vacation (paid time)" can be input to _{the input areas 2104 1} and 2104 _{2 in overlapping time zones.}

In FIG. 6 (b), the display regions 2201 to 2207 included in the total result information display unit 2200, the input area 2101, 2102, and 2103 ₁ included in the input unit 2100 described above, 2103 _2, ..., 2104 _1, The actual total information, which is the total result of totaling based on the values entered in _{2104 2, ..., Is displayed.}

Returning to the explanation of FIG. 9, in step S100, the creation unit 113 has the work information data input to the input screen 200 for a certain work day (assumed to be September 3, 2017) of a certain employee (assumed to be employee A). Is obtained from the UI unit 111. In the next step S101, the creation unit 113 generates the reason detail data 300 from the work information data acquired in the step S100. In the next step S102, the creation unit 113 generates the reference time detail data 310 based on the reason detail data 300 generated in step S101 and the predetermined predetermined working hours and the midnight working hours.

In the next step S103, the division unit 114 combines the reason detail data 300 generated in step S101 and the reference time detail data 310 generated in step S102 according to a predetermined condition, and sets the time zone of the day into each section. The reason detail division data 320 is generated. In the next step S104, the selection unit 115 groups the reason detail division data 320 generated in step S103 according to the order of the start time of each section in which the time zone of the day is divided. In the next step S105, the selection unit 115 extracts the reason with the highest priority in each group grouped in step S104, and generates the reason detail division extraction data 330 according to the section corresponding to the extracted reason.

In the next step S106, the aggregation unit 116 extracts a section from the reason detail division extraction data 330 generated in step S105 according to a predetermined aggregation condition, and aggregates the section as an actual result. The aggregation result is, for example, passed to the UI unit 111 and displayed in each display area 2201 to 2207 of the aggregation result information display unit 2200 of the input screen 200. Further, the aggregated result is passed to the storage management unit 112, associated with the employee ID and date information, and stored in the storage unit 120. The storage management unit 112 can store the aggregated result in, for example, the employee master 124 in association with the employee ID and date information.

[4. Details of processing according to the embodiment]
Next, the processing of steps S100 to S106 in the flowchart of FIG. 9 will be described in more detail.

[4-1. Step S100]
The work information data acquired by the creation unit 113 in step S100 includes at least the start time and end time of the predetermined time input to the input area 2101 and the start time and end time of the work time zone input to the input area 2102. The attendance time and the leaving time, which are, and the start time and the end time of the break time zone input to _{the input area 2103 1 are included.} In the example of FIG. 6B, the work information data further includes the reason for absence and the start time and end time of the absence time zone, which are input to _{the input area 2104 1.}

[4-2. Step S101]
In step S101, the creation unit 113 creates the reason detail data 300 from the work information data acquired in step S100.

FIG. 10 schematically shows an example of the reason detail data 300 according to the embodiment. In the example of FIG. 10, the reason detail data 300 is a table with records including each item of "employee", "working day", "reason type" and "priority", and "start time" and "end time". It is shown as. Among these, in the items "employee" and "working day", the employee ID and the working day value input to the input area 2000 of the input screen 200 are stored as common values in each record.

In the example of FIG. 10, each record of the reason detail data 300 is the input area 2101 at a predetermined time among the input areas 2101, 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 _{2, ... On the input screen 200.} Created for each input area except.

The items "start time" and "end time" are the start time and end time (input) input to each input area 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 _{2, ... In the input screen 200, respectively.} In the area 2102, the attendance time and the leaving time) are stored. The item "reason type" stores the reason type corresponding to the values stored in the items "start time" and "end time" of the record. Further, in the item "priority", the priority associated with the priority master 123 is stored in the reason type stored in the item "reason type" of the record.

In FIG. 11, the values input to the input areas 2101, 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 ₂ , ... In the input screen 200 of FIG. 6B by the creating unit 113 according to the embodiment. An example of creating the reason detail data 300 based on the above is schematically shown. The upper part of FIG. 11 shows excerpts of the input units 2000 and 2100 of the input screen 200 of FIG. 6B, and the lower part shows an example of the created reason detail data 300.

The first record of the reason detail data 300 is a record based on the input area 2102, as shown by a thick frame and an arrow in the figure. The creation unit 113 stores the start time and end time of the working hours zone input to the input area 2102 in the items "start time" and "end time" for the first record, respectively, and sets the item "reason type". The reason type "work" corresponding to the input area 2102 is stored in. Further, the creation unit 113 stores the priority "4" corresponding to the reason type "work" for the item "priority" based on the priority master 123.

As shown by a thick frame and an arrow in the figure, the creation unit 113 creates a second record of the reason detail data 300 based on the input contents of the _{input area 2103 1. That is, the creation unit 113 stores the start time and end time of the working hours zone input to the input area 2103 1} in the items "start time" and "end time", respectively, and stores the input area in the item "reason type". The _{reason type "break" corresponding to 2103 1} is stored, and the priority "1" corresponding to the reason type "break" is stored in the item "priority" based on the priority master 123, and the second record is concerned. To create.

As shown by a thick frame and an arrow in the figure, the creation unit 113 creates a third record of the reason detail data 300 based on the input contents of the _{input area 2104 1.} That is, the creation unit 113 stores the start time and the end time of the working hours zone input to the _{input area 2104 1} in the items “start time” and “end time”, respectively. Further, the creating unit 113 refers to the absentee reason master 122 based on the absentee reason "time paid holiday" input in the item "reason" in _{the input area 2104 1, and the reason type "corresponding to the absentee reason" time paid holiday ".} Acquire "paid leave" and store the acquired reason type "paid leave" in the item "reason type". The creation unit 113 refers to the priority master 123, stores the priority "2" corresponding to this reason type "paid leave" in the item "priority", and creates the third record.

The value to be stored in the item "reason type" of the reason detail data 300 is predetermined in the creating unit 113 for each input area 2101, 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 _{2, ...} Can be left. For example, the creation unit 113 predetermines the reason type "work" for the input area 2102, and the reason type "break" for _{the input areas 2103 1} , 2103 _{2, ....} Further, regarding the input areas 2104 ₁ , 2104 ₂ , ..., It is determined in advance that the reason type is acquired by referring to the absentee reason master 122 based on the input contents for the item "reason".

[4-3. Step S102]
In step S102, the creation unit 113 generates the reference time detail data 310 based on the reason detail data 300 generated in step S101 and the predetermined predetermined working hours and midnight working hours.

FIG. 12 schematically shows an example of the reference time detail data 310 according to the embodiment. In FIG. 12, the reference time detail data 310 is shown as a table of records including each item of "employee", "working day", "reference time", and "rank". Among these, in the items "employee" and "working day", the employee ID and the working day value input to the input area 2000 of the input screen 200 are stored as common values in each record.

The item "reference time" defines a reference time when the division unit 114 divides the time zone of the day in order to generate the reason detail division data 320. More specifically, the creation unit 113 lists each start time and end time included in the reason detail data 300 and a time predetermined by the system as the value of the item “reference time” in chronological order. The predetermined time includes, for example, a start time and an end time of a predetermined time defined as working hours, and a start time and an end time of a midnight time zone. For the item "rank", a value that gradually increases from the youngest time stored in the item "reference time" is set for each record.

In FIG. 13, the values input to the input areas 2101, 2102, 2103 _{1 , 2103 2} , ..., 2104 ₁ , 2104 ₂ , ... In the input screen 200 of FIG. 6B by the creating unit 113 according to the embodiment. An example of creating the reference time detail data 310 based on the reason detail data 300 shown in FIG. 11 is schematically shown. The upper part of FIG. 13 shows the input unit 2100 in the input screen 200 of FIG. 6B, the middle part shows the reason detail data 300, and the lower part shows the reference time detail data 310.

As shown by a thick frame in the figure, the creation unit 113 has a start time and an end time of a predetermined time input by the system to the input area 2101 of the input unit 2100 on the input screen 200, and each of the reason detail data 300. Get each start and end time contained in the record. The creation unit 113 creates each record including each acquired start time and end time as the value of the item "reference time", and is stored in the item "reference time" with respect to the item "rank" of each created record. Stores values that increase in chronological order.

The reference time detail data 310 is stored in the disclosure time "09: 00", the end time "17:30", and the items "start time" and "end time" of the reason detail data 300, which are input to the input area 2101. Each time "09: 00", "18:00", "12:00", "13:00", "11:00" and "14:00", the start of the midnight time zone set by the system. The time "22:00" and the end time "05:00" are stored in the item "reference time" of each record in chronological order. As for the item "rank", the values of "1" to "9" are stored in each record in order from the youngest time of the item "reference time" of each record.

In the example of FIG. 13, the record whose item “rank” is the value “1” stores the end time “05:00” of the midnight time zone, which is a system-fixed value, in the item “reference time”. In the record whose item "rank" is the value "2", the time "09: 00" which is the start time and the attendance time of the predetermined time is stored. In this way, the same time for different reason types is collectively stored in one record. In the record whose item "rank" is the value "3", the time "11:00" which is the start time of the break is stored. After that, for the items "rank" of the values "4" to "9", the start time of the paid vacation is "11:00", the start time of the break is "12:00", and the end time of the break is "13:". 00 ”, the end time of paid vacation“ 14:00 ”, the end time of a predetermined time“ 17:30 ”, the end time of work (leaving time)“ 18:00 ”, and the midnight time zone which is a fixed value of the system. The start time "22:00" and "reference time" are stored in the item "reference time", respectively.

The time zone of one day is divided by the reference time detailed data 310 into a section according to the time zone sandwiched between time adjacent times stored in the item "reference time". In the example of FIG. 13, the time zone of one day depends on the time zone from the time "05:00" to the time "09: 00" and the time zone from the time "09: 00" to the time "11:00". The section, the section according to the time zone from the time "11:00" to the time "12:00", the section according to the time zone from the time "12:00" to the time "13:00", and the time zone "13:00" to It depends on the time zone of time "14:00", the section of time "14:00" to time "17:30", and the time zone of time "17:30" to time "18:00". It is divided into a section and a section according to the time zone from the time "18:00" to the time "22:00".

Further, although omitted in FIG. 13, when the start and end times of the day are set to the time "00:00", the time "22:00" to the next day "00:00" and the time " Divisions are also made in each section according to each time zone from "00:00" to "05:00".

The minimum unit of the value stored in the item "reference time" is not particularly limited. For example, the minimum unit of the value stored in the item "reference time" may be 5 minutes or 10 minutes, or the value may be stored in a finer unit such as 1 minute unit or second unit.

[4-4. Step S103]
In step S103, the division unit 114 combines the reason detail data 300 generated in step S101 and the reference time detail data 310 generated in step S102 according to predetermined conditions, and has a working time zone, a break time zone, and absenteeism. The reason detail division data 320 is generated by dividing the time zone into each section.

More specifically, the division unit 114 sets an item for each value (start time and end time) stored in the items "start time" and "end time" for each record of the reason detail data 300. The records of the reference time detailed data 310 in which the value (reference time) of the "reference time" satisfies the condition of the following formula (1) are combined.
Start time ≤ reference time <end time ... (1)

FIG. 14 schematically shows an example of the reason detail division data 320 according to the embodiment, which is generated by combining the reason detail data 300 and the reference time detail data 310 according to the equation (1). In FIG. 14, the reason detail division data 320 includes “employee”, “working day”, “reason type”, “priority”, “start time”, “end time”, “division start time”, and “division start order”. , "Split end time", and "Split end order" are shown as a table with records containing each item. Among these, the items "employee" and "working day" are key items of the reason detail division data 320, and the employee ID and the working day value input to the input area 2000 of the input screen 200 are each. Stored as a common value in records.

In the reason detail division data 320, the items "reason type", "priority", "start time" and "end time" are record items in the combined reason detail data 300. The items "division start time" and "division start order" indicate the time zone of the reason type shown in the item "reason type" in the combined reason detail data 300, respectively, in each record of the reference time detail data 310. The start time of the section divided based on each time stored in the "reference time" and the order of the start times are stored. The items "division end time" and "division end order" store the end time of the section and the order of the end time.

FIG. 15 shows an example in which the division unit 114 according to the embodiment combines the reason detail data 300 shown in FIG. 11 and the reference time detail data 310 shown in FIG. 13 to create the reason detail division data 320. Shown schematically. The upper left side of FIG. 15 shows the reason detail data 300, the upper right side shows the reference time detail data 310, and the lower row shows the reason detail division data 320.

In FIG. 15, the reason detail data 300 includes three records of the reason types “work”, “break”, and “paid leave”. Among these, a method of generating the reason detail division data 320 will be described by taking a record of the reason type “work” as an example. In the record of the reason type "work", the times "09: 00" and "18:00" indicating the start time and the end time are stored for the items "start time" and "end time", respectively. When the above-mentioned equation (1) is applied to these times “09: 00” and “18:00”, each record of rank “2” to “7” satisfies the equation (1) in the reference time detailed data 310. You can see that.

That is, in the reference time detailed data 310, the time "5:00" stored in the item "reference time" of the record of the rank "1" is a time before the time "09: 00" indicating the start time. Equation (1) is not satisfied. The time "09: 00" stored in the item "reference time" of the record of the rank "2" in the reference time detailed data 310 is the same as the time "09: 00" indicating the start time, and the equation (1) is used. Fulfill. In the reference time detailed data 310, the item "reference time" of each record of rank "3" to "7" stores the time from the time "11:00" to the time "17:30", and each of these times is stored. , Since it is a time after the time "09: 00" indicating the start time and a time before the time "18:00" indicating the end time, both satisfy the equation (1). On the other hand, in the reference time detailed data 310, the time "18:00" stored in the item "reference time" of the record of the rank "8" is the same as the time "18:00" indicating the end time, and the formula ( Does not satisfy 1).

According to the determination result by the above-mentioned equation (1), the division unit 114 sets each record of the item "rank" of "2" to "7" in the reference time detail data 310 as the reason type in the reason detail data 300. Combine for "work" records (see arrow A in FIG. 15). At this time, each value stored in the items "reference time" and "rank" in the reference time detail data 310 is stored in the items "division start time" and "division start order" in the reason detail division data 320, respectively (FIG. See arrow B in 15.).

Further, the division unit 114 sets each record in the reference time detail data 310 as a value obtained by shifting the value of the item "rank" of each record combined with the reason detail data 300 to a value larger by 1 as the value of the item "rank". To get. The division unit 114 sets each value stored in the items "reference time" and "rank" included in each record acquired in this way into the items "division end time" and "division end order" in the reason detail division data 320, respectively. Store (see arrow C in FIG. 15).

The same applies to each record of the reason type "break" and "paid leave" in the reason detail data 300. The dividing unit 114 is set in the equation (1) according to the time stored in the items “start time” and “end time” and the time stored in the item “reference time” of each record of the reference time detailed data 310. Based on the condition determination, the record of the reference time detail data 310 that satisfies the condition is combined with the target record in the reason detail data 300. Further, the division unit 114 has the items "division start time" and "division start order" of the reason detail division data 320, based on the respective values stored in the items "reference time" and "rank" in the reference time detail data 310. In addition, the values are stored for the "division end time" and the "division end order".

In the example of FIG. 15, the time “09: 00” and “18:00” of the items “start time” and “end time” in the record of the reason type “work” in the reason detail data 300, and the reference time detail data 310. Based on each time of the item "reference time", the value of the item "division start time" is the time "09: 00", "11:00", "12:00", "13:00" in the reason detail division data 320. , "14:00" and "17:30", and 6 records in which the corresponding values of the items "division start order" are the order "2" to "7" are generated.

Further, in these 6 records, the value of each item "division end time" is 1 for the order "2" to "7" of the item "division start order" of the item "reference time" in the reference time detail data 310. Each time "11:00", "12:00", "13:00", "14:00", "17:30" and "17:30" corresponding to the ranks "3" to "8" shifted to a larger value. 18:00 ". Further, the value of the item "division end order" of each of the 6 records is set to the order "3" to "8". That is, for example, in the first record of the reason detail division data 320 shown in FIG. 15, the values of the items "division start time", "division start order", "division end time", and "division end order" are the times ", respectively. It becomes "09: 00", "2", "11:00" and "3".

Similarly, the items "start time" and "end time" in the record of the reason type "break" in the reason detail data 300 are "12:00" and "13:00", and the item "reference" of the reference time detail data 310. Based on each time of "time", in the reason detail division data 320, the value of the item "division start time" is the time "12:00", and the corresponding value of the item "division start order" is the order "4". 1 record is generated. In this one record, the value of the item "division end time" shifts the order "4" of the item "division start order" of the item "reference time" in the reference time detail data 310 to a value larger by one. The time corresponding to "5" is set to "13:00". Further, the value of the item "division end order" of the record 1 is set to the order "5".

Similarly, the time "11:00" and "14:00" of the items "start time" and "end time" in the record of the reason type "paid leave" in the reason detail data 300, and the item of the reference time detail data 310. Based on each time of the "reference time", the value of the item "division start time" is the time "11:00", "12:00" and "13:00" in the reason detail division data 320, and the item "division". Records of 3 in which the corresponding values of the "starting order" are the ordering "3" to "5" are generated. In these three records, the value of each item "division end time" is one larger than the order "3" to "5" of the item "division start order" of the item "reference time" in the reference time detail data 310. The times "12:00", "13:00" and "14:00" corresponding to the ranks "4" to "6" shifted to the values are set. Further, the value of the item "division end order" of each of the three records is set to the order "4" to "6".

In each record of the reason detail division data 320, the section between the time stored in the item "division start time" and the time stored in the item "division end time" is defined as an interval a to j. It is shown at the right end of the reason detail division data 320 in FIG.

Specifically, in each record in which the value of the item "reason type" is "work", the section a between the time "09: 00" and the time "11:00", the time "11:00" and the time The section b between "12:00", the section c between the time "12:00" and the time "13:00", and the section d between the time "13:00" and the time "14:00" , A section e sandwiched between the time "14:00" and the time "17:30", and a section f sandwiched between the time "17:30" and the time "18:00" are formed. Further, in the record in which the value of the item "reason type" is "rest", a section g sandwiched between the time "12:00" and the time "13:00" is formed. Further, in each record in which the value of the item "reason type" is "paid leave", the section h between the time "11:00" and the time "12:00", the time "12:00" and the time "13" A section i sandwiched between ": 00" and a section j sandwiched between the time "13:00" and the time "14:00" are formed.

In the process of generating the reason detail division data 320 by the division unit 114 described with reference to FIG. 15, the reason detail division data 300 is divided into strip-shaped blocks at the start time and the end time, which are the breaks in the daily attendance calculation. It is a process of dividing.

FIG. 16 is a diagram showing the reason detail division data 320 according to the embodiment shown in FIG. 15 using a block that divides the time zone of the day. In FIG. 16, each line shows a time zone according to the items “start time” and “end time” of the reason detail data 300 for each reason type. Further, in FIG. 16, the time zone of one day is stored in the item “reference time” of the reference time detailed data 310, respectively, at “05:00”, “09:00”, “11:00”, and “12”. Blocks based on sections sandwiched between adjacent times according to ": 00", "13:00", "14:00", "17:30", "18:00" and "22:00" It is shown that it is divided into.

As described above, the division unit 114 according to the embodiment divides the time zone of one day with the reference time stored in the reference time detailed data 310 as a delimiter. As a result, each block formed by the divided sections is always in either a state of having a reason or having no reason. Therefore, it is determined that the sections in the same time zone are in either the state of "no applicable reason" or "there is one or more applicable reasons".

In the example of FIG. 16, the time zone from the time "00:00" to the time "09:00" and the time zone from the time "18:00" to the time "00:00" on the next day are "no applicable reason". It is a section of. On the other hand, in the time zone from the time "09: 00" to the time "11:00" and the time zone from the time "14:00" to the time "18:00", "there is one corresponding reason", respectively. It is a section. In addition, the time zone from the time "11:00" to the time "12:00" and the time zone from the time "13:00" to the time "14:00" are each "there are two applicable reasons" sections. ing. Further, the time zone from the time "12:00" to the time "13:00" is a section where "there are three applicable reasons".

In the example of FIG. 16, each reason type is arranged so as to have a higher priority from the upper row to the lower row.

[4-5. Step S104]
In step S104, the selection unit 115 groups the reason detail division data 320 generated in step S103 according to the order of the start time of each section in which the time zone of the day is divided. In other words, the selection unit 115 groups the reason detail division data 320 generated in step S103 in units of the items “employee”, “working day”, and “division start time”.

At this time, for example, the reason detail division data 320 shown in FIG. 15 is data relating to an employee with a specific employee ID “A” and a specific working day “September 3, 2017”. Therefore, it can be considered that the reason detail division data 320 has already been grouped with respect to the items “employee” and “working day”.

For example, in the reason detail division data 320 shown in FIG. 15, the selection unit 115 forms a group from records having the same value stored in the item “division start time”, and sets each group into the item “division start order”. Sort by the values stored in.

The grouping process according to step S104 according to the embodiment will be described with reference to FIG. FIG. 17A shows an example of the reason detail division data 320 ′ in which the reason detail division data 320 is rearranged in this way. In the example of FIG. 17A, the group G # 1 including the record of 1 in which the value of the item “division start time” is the time “09: 00” and the group G # 1 in which the value is the time “11:00” are 2. Group G # 2 containing records, group G # 3 containing 3 records having the value at time "12:00", and group G # containing 2 records having the value at time "13:00". 4 is grouped into group G # 5 containing 1 record whose value is time "14:00" and group G # 6 including 1 record whose value is time "17:30". ing.

FIG. 17B is a diagram corresponding to FIG. 16 described above, and schematically shows the grouping process using blocks. As shown in FIG. 17B, the section from the time "09: 00" to the time "11:00" is in the group G # 1, and the section from the time "11:00" to the time "12:00" is in the group. In G # 2, the section from time "12:00" to time "13:00" is in group G # 3, and the section from time "13:00" to time "14:00" is in group G # 4. The section from "14:00" to time "17:30" is grouped in group G # 5, and the section from time "17:30" to time "18:00" is grouped in group G # 6. I understand. As described above, the grouping process in step S104 is a process of grouping the sections "having one or more applicable reasons" for each same time zone.

[4-6. Step S105]
In step S105, the selection unit 115 extracts the reason with the highest priority in each group grouped in step S104, and generates the reason detail division extraction data 330 according to the section corresponding to the extracted reason. FIG. 18 and FIG. 17 (a) described above will be used to describe the process of generating the reason detail division extraction data 330 according to the embodiment in step S105.

In step S105, the selection unit 115 extracts the record in which the highest priority is stored in the item "priority" in each group G # 1 to G # 6 of the reason detail division data 320'in FIG. 17 (a). do. In the example of FIG. 17A, since the groups G # 1, G # 5, and G # 6 each include only one record, each record (corresponding to the intervals a, e, and f) is extracted. In group G # 2, which includes 2 records having a priority of "2" and "4", respectively, a record having a higher priority of "2" (corresponding to the section h) is extracted. In group G # 3, which includes 3 records having priorities "1", "2", and "4", the record having the highest priority "1" (corresponding to the section g) is extracted. Further, in the group G # 4 including 2 records having a priority of "2" and "4", records having a higher priority of "2" (corresponding to the section j) are extracted.

FIG. 18A shows the reason detail division extraction data 330 generated by collecting the highest priority records extracted in each group G # 1 to G # 6 by the selection unit 115 as described above. .. As described above, the reason detail division extraction data 330 includes 6 records corresponding to the intervals a, h, g, j, e and f, respectively, extracted one by one from each group G # 1 to G # 6. ..

FIG. 18B shows an example in which the process according to step S105 is applied to FIG. 17B described above. In FIG. 18B, the rows are arranged so that the priority of the reason type is higher from the upper row to the lower row. Therefore, in each group G # 1 to G # 6, "corresponding". The lowest block among the blocks corresponding to the section "with one or more reasons" will be extracted. In the example of FIG. 18B, each block corresponding to the intervals a, h, g, j, e and f is extracted. The reason and time zone corresponding to each of the extracted blocks are adopted as the reason and time zone used for aggregation by the aggregation unit 116 in the next step S106.

In the example of FIG. 18B, the reason why each block corresponding to the sections a, e and f is adopted is extracted as “work”. The reason why the blocks corresponding to the sections h and j are adopted is extracted as "paid leave". Further, the reason why the block corresponding to the section g is adopted is extracted as a "break". In addition, each block indicated by "x (x)" in FIG. 18B is the reason and time used for aggregation by the aggregation unit 116 among the blocks belonging to each group G # 1 to G # 6. It shows the reason and time zone that is not adopted as a zone.

As a result, even when the working hour calculation device 10 according to the embodiment permits registration including overlapping time zones for different reason types, the reasons for each time zone described with reference to FIG. 2 (b). It is possible to generate the same data as the first example of the registration method by the existing technique, which correctly registers the data, by automatic processing.

[4-7. Step S106]
In step S106, the aggregation unit 116 extracts a section from the reason detail division extraction data 330 generated in step S105 according to a predetermined aggregation condition, and aggregates the section as an actual result. The section referred to here refers to each block shown in FIG. 18B, for example.

FIG. 19 shows an example of predetermined aggregation conditions for the aggregation unit 116 to extract a section from the reason detail division extraction data 330 in step S106 according to the embodiment. In the example of FIG. 19, the tabulation destination items are "scheduled actual working hours", "non-scheduled actual working hours", "actual working hours", "midnight working hours", "break time", "paid leave hours" and "paid leave hours". Each item of "non-working hours" is defined. Each of these aggregation destination items is defined based on, for example, a wage calculation method. The aggregation unit 116 extracts a section (block) satisfying a predetermined aggregation condition from the reason detail division extraction data 330, and aggregates the time of the extracted section.

The aggregation conditions for each of these aggregation destination items are as follows. In the following equations (2), (3) and (4), the symbol "∧" represents a logical product and the symbol "∨" represents a logical sum.

For the tabulation destination item "prescribed actual working hours", the section satisfying the following formula (2) is extracted, and the time of the extracted section is totaled.
(Reason type = work) ∧ (start time of predetermined time ≤ start time of division) ∧ (end time of division ≤ end time of predetermined time)… (2)

For the tabulation destination item "overtime actual working hours", the section satisfying the following formula (3) is extracted, and the time of the extracted section is totaled.
(Reason type = work) ∧ {(start time of predetermined time> division start time) ∨ (end time of predetermined time <division end time)}… (3)

As can be seen from the above equations (2) and (3), in the embodiment, when the section whose reason type is "work" is included within the predetermined time and when it is included outside the predetermined time. Aggregate by distinguishing with.

For the aggregation destination item "actual working hours", the section whose reason type is "working" is extracted, and the time of the extracted section is aggregated.

For the tabulation destination item "midnight working hours", the section satisfying the following formula (4) is extracted, and the time of the extracted section is totaled. In the formula (4), the time "05:00" and the time "22:00" are the end time and the start time of the time zone in which the payment of the late-night premium wage is obliged by the Labor Standards Act.
(Reason type = work) ∧ {(05:00> division start time) ∨ (22:00 <division end time)}… (4)

As can be seen from the above equation (4), in the embodiment, the section whose reason type is "working" is counted separately depending on whether the section is included in the midnight working hours zone or not.

For the aggregation destination item "break time", the section whose reason type is "break" is extracted, and the time of the extracted section is aggregated. For the aggregation destination item "paid leave time", the section whose reason type is "paid leave" is extracted, and the time of the extracted section is totaled. In addition, for the aggregation destination item "non-working hours", the section whose reason type is "non-working" is extracted, and the time of the extracted section is aggregated.

With reference to FIG. 20, a method of totaling each section by the totaling unit 116 according to the embodiment will be described. FIG. 20 (a) corresponds to FIG. 18 (b) described above, and the aggregation unit 116 aggregates each block extracted as being adopted according to the above-mentioned aggregation conditions. FIG. 20B shows an example in which each block is extracted for each aggregation destination item in FIG. The start time and end time of the predetermined time shall be the time "09: 00" and "17:30", respectively. Further, in FIG. 20 (b), "time" as a unit is represented by "h".

In the block of the section a in FIG. 20A, the reason type is "work", the division start time and the division end time are the time "09: 00" and the time "11:00", respectively, and the above-mentioned formula is used. (2) is satisfied. Similarly, in the block of the section e, the reason type is "work", the division start time and the division end time are the time "14:00" and the time "17:30", respectively, and the above equation (2) Meet. Therefore, as shown in the line of "prescribed actual working hours" in FIG. 20 (b), the block time "2 hours" in the section a and the block time "3.5 hours" in the section e are predetermined respectively. Calculated as actual working hours.

In the block of the section f in FIG. 20A, the reason type is "work", and the division start time and the division end time are the time "17:30" and the time "18:00", respectively. Of these, the time "18:00" of the division end time is a time after the end time "17:30" of the predetermined time, and satisfies the above-mentioned formula (3). Therefore, as shown in the row of "Overtime actual working hours" in FIG. 20B, the time "0.5 hours" of the block in the section f is calculated as the overtime actual working hours.

Each block of the section h and the section j in FIG. 20A has a reason type of "paid leave" and satisfies the condition of the above-mentioned aggregation destination item "paid leave time". Further, in the example of FIG. 19, the condition regarding the time (time) is not defined for the aggregation destination item “paid leave time”. Therefore, as shown in FIG. 20B, the block time "1 hour" in the section h and the block time "1 hour" in the section j are calculated as paid vacation times, respectively.

In the block of the section g in FIG. 20A, the reason type is "break", and the condition of the above-mentioned aggregation destination item "break time" is satisfied. Further, in the example of FIG. 19, the condition regarding the time (time) is not defined for the aggregation destination item “break time”. Therefore, as shown in the row of "break time" in FIG. 20 (b), the block time "1 hour" of the section g is calculated as the break time.

The aggregation unit 116 aggregates each time calculated in this way for each aggregation destination item. The tabulation result is shown at the right end of FIG. 20 (b). Specifically, the aggregation destination item "prescribed actual working hours" is set to "2 hours + 3.5 hours" and the aggregation result is 5.5 hours. The tabulation destination item "Overtime actual working hours" is 0.5 hours as the tabulation result. The aggregation destination item "break time" is one hour as the aggregation result. In addition, the aggregation destination item "paid leave" is set to "1 hour + 1 hour" and the aggregation result is 2 hours.

On the other hand, in the example of FIG. 20A, there is no section (block) in which the reason type is "non-working", such as "late" or "all day absenteeism". Further, in the example of FIG. 20A, the working time zone is from the time "09: 00" to the time "18:00", and the division start time of the block in the first section a of the working time zone and the working hours. The division end time of the block in the section f at the rear end of the time zone does not satisfy the condition of the above equation (4), and there is no section (block) corresponding to the aggregation destination item “midnight working hours”. Therefore, 0 hours are calculated for each of the aggregation destination items "non-working hours" and "midnight working hours" shown in FIG.

The aggregation destination item and aggregation condition shown in FIG. 19 are examples, and are not limited to this example. In other words, in reality, the tabulation destination items and tabulation conditions are set according to the employment form of employees, the difference between managers and supervisors and general employees, work rules, hiring system (variable working hours system, flextime system, etc.). Set.

The aggregation unit 116 passes the aggregation result aggregated for each aggregation destination item as described above to, for example, the UI unit 111. The UI unit 111 causes the aggregation result information display unit 2200 of the input screen 200 described with reference to FIG. 6 to display the aggregation result passed from the aggregation unit 116, for example.

FIG. 21 shows an example of an input screen 200 in which the aggregation result is displayed on the aggregation result information display unit 2200 according to the embodiment. In the example of FIG. 21, as shown by a thick frame in the figure, the predetermined actual working hours shown at the right end of FIG. 20B are set in each display area 2201 to 2207 of the aggregation result information display unit 2200. Total results of actual working hours, actual working hours, late-night working hours, break hours, paid vacation hours and non-working hours "5 hours 30 minutes", "0 hours 30 minutes", "6 hours 00 minutes", "0" "Time 00 minutes", "1 hour 00 minutes", "2 hours 00 minutes" and "0 hours 00 minutes" are displayed respectively. This tabulation result is consistent with the work schedule described with reference to FIGS. 1 (a) and 1 (b).

Not limited to this, the UI unit 111 may display the aggregation result by the aggregation unit 116 on a screen different from the input screen 200. Further, the aggregation unit 116 may store the aggregation result in the storage unit 120 without passing it to the UI unit 111. Further, the aggregation unit 116 may output the aggregation result from the input / output I / F unit 130 to the outside, or may transmit the aggregation result from the communication I / F unit 140 to the server 20 via the network 30.

As described above, the working time calculation device 10 according to the embodiment divides the time zone of the day according to the start time and the end time of each reason, and the time zone according to each reason is sandwiched between temporally adjacent divisions. It is divided into sections. In addition, each reason is associated with a priority. Therefore, even if the types of reasons for absence of attendance and the number of reasons with overlapping parts in time increase, it is possible to deal with them by a common procedure by clarifying the judgment of the priority to be associated with the reasons. ..

Further, the working hour calculation device 10 according to the embodiment aggregates each reason based on a section in which the time zone of the day is divided by the start time and the end time of each reason. Therefore, strict aggregation is possible regardless of the minimum management unit of attendance. For example, the minimum attendance management unit can be arbitrarily set to 1 hour, 30 minutes, 15 minutes, 5 minutes, 1 minute, etc., in principle, up to the second unit. In addition, the influence of the fineness of the minimum management unit on the computational complexity of aggregation is suppressed.

[5. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical ideas described in the claims.

For example, among the processes described in the embodiment, all or part of the processes described as being automatically performed may be performed manually, or all the processes described as being performed manually may be performed. Alternatively, a part thereof can be automatically performed by a known method.

In addition, the processing procedure, control procedure, specific name, information including parameters such as registration data and search conditions of each processing, screen example, master configuration, and data configuration shown in the present specification and drawings are specially described. It can be changed arbitrarily except in some cases.

Further, in the above description, the working hour calculation device 10 according to the embodiment is described to be composed of one computer, but this is not limited to this example. That is, the working time calculation device 10 according to the embodiment can also be configured as a system that operates a plurality of computers in an integrated manner.

Furthermore, the specific form of distribution / integration of the device is not limited to the one shown in the figure, and all or part of the device may be functionally or physically in any unit according to various additions or functional loads. Can be distributed and integrated into the configuration. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

The present invention is particularly useful in the field of attendance management such as companies and stores.

10 Working hours calculation device 20 Server 30 Network 110 Control unit 111 UI unit 112 Storage management unit 113 Creation unit 114 Division unit 115 Selection unit 116 Aggregation unit 120 Storage unit 121 Input information storage unit 122 Absence reason master 123 Priority master 200 Input screen 300 Reason detail data 310 Reference time detail data 320 Reason detail division data 330 Reason detail division extraction data 2000, 2100 Input unit 2200 Aggregation result information display unit

Claims (10)

It is a working time calculation device equipped with a control unit and a storage unit.
The control unit
Input means that accepts input by the user,
Start of each time zone according to the working time zone where the reason type is work, the break time zone where the reason type is a break, and the absent time zone where the reason type is absent, which are input by the input means. A storage means for storing a plurality of time information indicating the time and the end time, and the reason type indicating the content of the absence in the storage unit.
For the time of the day, a delimiter is set by the time indicated by the plurality of time information stored in the storage unit and the predetermined time, and the section sandwiched between the adjacent delimiters is set. How to create and how to create
A dividing means for generating a divided time zone by dividing the working time zone, the break time zone, and the absent time zone into each of the sections created by the creating means.
In each of the sections created by the creation means, in the section including one or more of the division time zones, the division time zone corresponding to the reason type for which the highest priority among the division time zones is set. With a selection means for selecting each section,
An aggregation means that aggregates the division time zones selected by the selection means for each division time zone having the same reason type.
A working time calculator characterized by being equipped with. The selection means is
The working hour calculation device according to claim 1, wherein the divided time zone is selected for each section based on the priority master in which the reason type and the priority are associated with each other. The input means is
Claim 1 or claim 2 is characterized in that at least two of the working hours, the resting hours, and the absentee hours have overlapping portions. The working hours calculator described in. The input means is
The working hour calculation device according to any one of claims 1 to 3, wherein the input of the rest time zone and the absence time zone can be accepted for each of the day. .. The input means is
The input of the reason type further indicating the content of the absence is accepted for each of the plurality of absent time zones.
The working hour calculation device according to claim 4, wherein a plurality of the absent time zones having different types of reasons indicating the input contents of the absence can accept the input having an overlapping portion. The input means is
Claims 1 to 5, wherein the reason type further indicating the content of the absence is input based on the absence reason master in which the reason type and the absence reason indicating the content of the absence are associated with each other. The working hour calculation device according to any one of the following items. The creation means is
The delimiter is set with the start time and end time of each of the predetermined working hours and midnight hours as the predetermined times.
The tabulation means is
Based on the start time and end time of the working time zone and the midnight time zone, the divided time zone obtained by dividing the working time zone selected by the selection means is further divided into the working time zone and the non-working time zone. The working hour calculation device according to any one of claims 1 to 6, wherein the aggregation is performed separately within the midnight time zone and outside the midnight time zone. The input means is
The working hour calculation device according to any one of claims 1 to 7, wherein the plurality of time information can be input in the minimum time unit managed by the control unit. It is a working time calculation method executed by a working time calculation device having a control unit and a storage unit.
Executed by the control unit,
Input steps that accept user input and
Start of each time zone according to the working time zone where the reason type is work, the break time zone where the reason type is a break, and the absent time zone where the reason type is absent, which are input by the input step. A storage step for storing a plurality of time information indicating the time and the end time, and the reason type indicating the content of the absence in the storage unit.
For the time of the day, a delimiter is set by the time indicated by the plurality of time information stored in the storage unit and the predetermined time, and the section sandwiched between the adjacent delimiters is set. The creation step to create and
A division step of dividing the working time zone, the break time zone, and the absence time zone into each of the sections created by the creation step to generate a divided time zone.
In each of the sections created by the creation step, in the section including one or more of the division time zones, the division time zone corresponding to the reason type for which the highest priority among the division time zones is set. With a selection step to select for each section,
An aggregation step in which the division time zones selected by the selection step are aggregated for each division time zone having the same reason type.
A method of calculating working hours, characterized by including. It is a working time calculation program to be executed by an information processing device equipped with a control unit and a storage unit.
To make the control unit execute
Input steps that accept user input and
Start of each time zone according to the working time zone where the reason type is work, the break time zone where the reason type is a break, and the absent time zone where the reason type is absent, which are input by the input step. A storage step for storing a plurality of time information indicating the time and the end time, and the reason type indicating the content of the absence in the storage unit.
For the time of the day, a delimiter is set by the time indicated by the plurality of time information stored in the storage unit and the predetermined time, and the section sandwiched between the adjacent delimiters is set. The creation step to create and
A division step of dividing the working time zone, the break time zone, and the absence time zone into each of the sections created by the creation step to generate a divided time zone.
In each of the sections created by the creation step, in the section including one or more of the division time zones, the division time zone corresponding to the reason type for which the highest priority among the division time zones is set. With a selection step to select for each section,
An aggregation step in which the division time zones selected by the selection step are aggregated for each division time zone having the same reason type.
A working hours calculation program characterized by including.

Images