Attendance management method, attendance management program, attendance management computer, database server computer, and attendance management system

Abstract

To provide an attendance management method, an attendance management program, and an attendance management system that can grasp and manage start / end time for each time of a work day for a worker who starts / ends work several times in one day.SOLUTION: An attendance management method according to the present application includes the steps of, each time a worker takes procedures for start of work several times in one day, generating a data record that records start times and end times and recording a start time into the generated data record, and, each time the worker takes procedures for end of work, recording an end time into the data record in which the most recent start time is entered. The method includes calculating and tallying work hours from the start time and end time for each time for calculating total man-hours of one day. The man-hours are tallied in units such as daily, weekly, monthly and yearly, which are displayed in a list or displayed in a graph format for allowing management of work status, normal work hours, and overwork hours.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a work management method, a work management program, a work management system, and a database server computer used in the work management system. [Background technology]

[0002] An attendance management system is generally configured to manage the working hours of a worker, including regular working hours, overtime hours, and the regular working hours and overtime hours for each case that the worker is in charge of. Various systems and methods have been known as technologies for configuring such attendance management systems.

[0003] For example, Patent Document 1 discloses a technology that calculates working hours based on the worker's self-reported arrival and departure times, the arrival and departure times punched in using a card reader or the time the worker logs on (punches in to start work) and off (punches in to finish work) into an information terminal used for work, thereby enabling a more objective understanding of working hours and improving the accuracy of working hour management.

[0004] Furthermore, Patent Document 2 discloses an attendance management sheet that lists employee identification information and each day of the week for each week of the month for that employee in a single document, and also provides a condition deficiency display column that can list multiple condition deficiencies that do not meet the conditions for the number of specified working days or working hours within that month, and a column that displays the values ​​of the number of working days or working hours that correspond to these deficiencies, thereby making it possible to view all the information necessary for labor management at a glance and streamlining management operations.

[0005] Furthermore, Patent Document 3 discloses a technique for implementing a method for authenticating the arrival of a dispatched worker at a site and managing his / her attendance in a dispatch service, which is suitable for use in home care, for example. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent No. 6430052 [Patent Document 2] JP 2013-240961 A [Patent Document 3] JP 2002-288402 A Summary of the Invention [Problem to be solved by the invention]

[0007] The above-mentioned conventional technologies disclose various aspects of attendance management systems, but all of them are based on the premise of a work style of one shift per day.

[0008] In other words, in Patent Document 1, the arrival and departure times for that day are calculated based on the worker's self-reported arrival and departure times, the arrival and departure times punched in using a card reader or the like, and the time the worker logs on (punches in to start work) and logs off (punches in to end work) into the information terminal used by the worker for work, and one working hour for that day is calculated, and there is one set of arrival and departure times for that working hour.

[0009] In Patent Document 2, the working hours per day are grasped and recorded in a list. Here too, there is one working hour per day, and the corresponding starting and ending times are also one set.

[0010] Patent Document 3 discloses a technology for grasping the arrival time at each visit destination or the start and end time of work at the visit destination in a visiting care service by a home helper or the like. For example, as seen in paragraph 0024, this document states that "attendance management of dispatched workers is performed" referring to managing the start and end times of work at the visit destination, but this term "attendance management" has a different meaning from the "attendance management" referred to in the present invention, that is, grasping and managing the arrival and departure times, and refers to managing the start and end times of work at each visit destination while visiting several visiting care destinations in a day's work.

[0011] That is, Patent Document 3 discloses in paragraph 0003 that visiting care services provided by home helpers and the like are a mobile service, and also states in paragraph 0031 as an effect of the invention that "particularly in the case of mobile dispatch, progress management can be performed in real time."

[0012] From these descriptions, it is clear that the home helper etc. is an employee of the home care service provider, and in this case too, the arrival and departure times for the day's work are one group.

[0013] In addition, looking at the implementation methods used by general business operators, for example, large corporations are adopting a system in which so-called flapper gate equipment is installed at the entrances to offices and entrances to business premises, and employees hold their employee ID cards or special security cards over the card sensor of the gate to record the entry and exit times.

[0014] Looking at the actual operations of such companies, for example, they record the time of the entrance stamp when arriving at work in the morning, the exit stamp when leaving during the lunch break, the entrance stamp when re-entering before the end of the lunch break, and the exit stamp when leaving work in the evening.They then record the earliest entrance stamp as the arrival time and the latest exit stamp as the departure time, and manage attendance by treating these as a pair of arrival and departure times.

[0015] In this case, the earliest entry time and the latest exit time are recorded as one set of entry and exit times and attendance management is performed because some employees do not enter or re-enter during their lunch break. For example, some employees use the company cafeteria, while others bring their own lunch and eat it at their own desk in the office.

[0016] In recent years, the establishment of laws related to work style reform has progressed in Japan, and in response to the "work style reform" promoted by the Japanese government, various work styles are being proposed, planned, and implemented in companies, etc., for example, by introducing discretionary work systems depending on the type of job, and by considering the introduction of systems that allow workers to choose from a variety of work styles depending on their individual circumstances. Furthermore, even newer work styles are expected to be implemented in the future.

[0017] For example, for workers of child-rearing age, in addition to the previously common so-called reduced-hours work (shortened hours work) that involves arriving late and leaving early, it is thought that in the future there will also be working styles that allow workers to leave early through reduced-hours work, take care of their children, and then work from home late at night for a few hours.

[0018] In this case, the time between leaving work early and starting telecommuting is neither working time nor a break, and must be considered non-work time. This is because telecommuting time may or may not occur depending on whether the person works from home (or is able to do so). If the person works from home, there will be two sets of arrival and departure times.

[0019] Also, for example, in a restaurant or other establishment, a worker might work early in the morning when supplies are being purchased and preparation is being made, for example from around 4:00 a.m. to around 7:00 a.m., then leave the office, come back to work during the daytime when the store is busy, work from around 11:00 a.m. to 2:00 p.m., leave the office again, and then come back to work a third time in the evening or later.

[0020] In this case too, it would be appropriate to consider the time between leaving work at 7am and 11am, and between 2pm and arriving at work in the evening, as non-working hours, and not as on-duty hours. If the time between these shifts were considered on-duty hours, the working hours per day would be longer than 12 hours, which would be unreasonable. In this case too, each shift is not limited to the time of arrival and departure planned in advance, and it is acceptable for employees to arrive and leave at any time depending on the situation. In this example, there are three sets of arrival and departure times.

[0021] Furthermore, currently, for example, there are cases where a discretionary work system is applied to creative workers, and a set wage is paid regardless of the actual hours worked, but there are still some who view this as a social problem, as it may encourage long hours of overtime work. One solution to this problem may eventually be to properly grasp the actual times people come and go to work, and somehow determine the relationship with remuneration.

[0022] For workers in such more creative occupations, working arrangements may involve changing locations or moving around over time while using mobile devices to carry out work.

[0023] For example, suppose you are walking around town and suddenly get a new idea. You immediately go to a nearby cafe, go through the "clock in" procedure, enter the idea into your mobile device, and once you have completed a series of related tasks, go through the "clock out" procedure to take a break or leave the cafe and move on.

[0024] In this case, the "clock in" and "clock out" procedures may be, for example, "log in" and "log out" operations to a mobile terminal, or "log in" and "log out" operations to access a server at the workplace. Of course, it goes without saying that a method involving a dedicated procedural operation other than a simple log in and log out operation may also be used.

[0025] After that, if your idea expands, or if you get a new idea for another task, you may want to start the next task. If you can work on the spot, you can go through the "Clock in" procedure and do the work, and once you have completed the related tasks, you can go through the "Clock out" procedure again and take a break or leave the store and move on. In this way, it is conceivable that in the near future, a work style in which employees clock in and clock out several times a day will be implemented.

[0026] In that case, the interval between one shift and the next could be around 10 to 15 minutes, or it could be several hours or even span several days. Therefore, the length of the time between each shift is effectively indefinite, and it would be unreasonable to consider it either as working time or as a break. Therefore, the time period between multiple shifts would have to be treated as outside of working hours.

[0027] Furthermore, as the diversity of employment patterns of workers continues to advance, it is expected that the number of businesses that allow employees to have side jobs or concurrent jobs will increase. When an employee has a side job, for example, they may come to work in the morning, work as their main job (employee of business A) in the morning, and finish work around noon. In the afternoon, they may come to work as their side job (employee of business B), and finish work for business B in the evening. After that, they may come to work again as their main job (employee of business A), work for a few hours, and then finish work.

[0028] In this case, the attendance management system of the employer A, where the employee works as his / her main job, will not treat the time that the employee works at the workplace of the employer B, where the employee works as a side job, as part of the employee's work management, nor will it treat the time as part of the employee's working hours. Therefore, the employer A, which is the employee's main job, will treat the employee's work on that day as having two clock-in and clock-out times. Therefore, in this case, the employee's clock-in and clock-out times will be managed as two sets.

[0029] This type of work style also applies to workers who work in a manner known as "teleworkers."

[0030] In recent years, the number of workers who work from home or so-called "satellite offices" without going to any place of business has been increasing. Such workers carry a business information processing terminal, etc., and by operating it and taking the prescribed authentication procedures, such as logging in to the server of business A, which is their main business, they can come to work and work as an employee of business A, and by taking the prescribed authentication procedures, such as logging out of business A's server, they can clock out from business A. Similarly, by taking the prescribed authentication procedures, such as logging in to business B's server, they can come to work and work as an employee of business B, and by taking the prescribed authentication procedures, such as logging out of business B's server, they can clock out from business B.

[0031] Then, on the same day, if the employee takes the prescribed authentication procedure, such as logging in to the server of business A, which is his / her main business, he / she can come to work again as an employee of business A, and after working, he / she can leave work again as an employee of business A by taking the prescribed authentication procedure, such as logging out of business A's server.

[0032] In this way, it is possible for teleworkers who do not come to the offices of business operators A or B to have a side job in addition to their main job and work as employees of the respective businesses. In this case, business operator A's attendance management system will recognize that the employee has clocked in and clocked out twice on the same day, and will keep track of and manage each of the employee's clocking in and clocking out times.

[0033] However, all of the above-mentioned conventional technologies are based on the assumption that an employee works one shift per day, and therefore cannot accommodate a work style in which an employee may clock in and clock out multiple times per day, making it impossible to properly grasp and manage an employee's working hours.

[0034] Therefore, the object of the present invention is to provide an attendance management method, attendance management program, and attendance management system that can accommodate the above-mentioned work style, i.e., a work style in which workers clock in and out multiple times at any time at their discretion, rather than being limited to one shift per day. [Means for solving the problem]

[0035] The attendance management method of the present invention includes a step of generating a data record in a database that records the arrival and departure times when a worker who clocks in and out multiple times a day operates a computer to record their arrival time, or when the computer detects that the worker has clocked in, and a step of recording the departure time in the data record that records the most recent arrival time when the computer is operated to record a departure time, or when the computer detects that the worker has clocked out.

[0036] The attendance management program of the present invention has a step of generating a data record in a database that records the arrival and departure times when a worker who clocks in and out multiple times a day operates a computer to record their arrival time, or when the computer detects that the worker has clocked in, and a step of recording the departure time in the data record that records the most recent arrival time when the computer is operated to record a departure time, or when the computer detects that the worker has clocked out.

[0037] The attendance management system of the present invention is configured with a computer that executes an attendance management method, which includes the steps of: when a worker who clocks in and out multiple times a day operates the computer to record his / her clock-in time, or when the computer detects that the worker has clocked in, generating a data record in a database that records the clock-in and clock-out times, and recording the clock-in time; and when the computer operates the computer to record a clock-out time, or when the computer detects that the worker has clocked out, recording the clock-out time in the data record that records the most recent clock-in time. Effect of the Invention

[0038] According to the present invention, it is possible to provide an attendance management method, an attendance management program, and an attendance management system that can handle a work style in which an employee clocks in and out at any time multiple times a day at their discretion. It is also possible to provide an attendance management method, an attendance management program, and an attendance management system that can manage the attendance times and working hours of an employee who may clock in and out multiple times a day, as well as the progress of various overtime hours. [Brief description of the drawings]

[0039] [Figure 1] FIG. 1 shows a timeline showing the arrival and departure times on a certain working day of a worker who may work multiple shifts in a day, as envisaged by the present invention, an example of the structure of a data record that records each arrival and departure time, and the correspondence between them. [Figure 2A] FIG. 2(a) shows an example of a terminal screen when the current time is registered as the working time by operating a mobile terminal or the like, and the corresponding relationship between the terminal screen and elements of a data record. [Figure 2B] FIG. 2(b) shows an example of a terminal screen when an employee manually inputs a time different from the current time mainly by operating a PC terminal or the like, and the correspondence between the terminal screen and elements of a data record. [Figure 2C] Figure 2(c) shows an example of a registration operation screen and the correspondence with elements of a data record when registering actual working hours separately from the clock-in / clock-out times after they have been punched, including other clock-in / clock-out methods. [Figure 3A] FIG. 3(a) shows an example of a setting screen for setting a case ID for each of the multiple times a day that a person clocks in and out. [Figure 3B] FIG. 3B shows an example of a case ID setting method for setting multiple case IDs for a single clock-in / clock-out session when work is performed to process multiple cases during that session. [Figure 4A] FIG. 4(a) shows an example of an input screen for inputting a breakdown of man-hours for each case based on the total man-hours for each day, and an example of the structure of the corresponding record. [Figure 4B]FIG. 4(b) shows an example of the operations and behavior when adding a case category on the input screen for inputting the breakdown of man-hours for each case. [Figure 5A] FIG. 5(a) shows an example of a management screen that displays a list of the total man-hours for each day, along with weekly and monthly aggregate values. [Figure 5B] FIG. 5(b) shows an example of a management screen that, when any day is selected from the list screen, displays a list of the arrival and departure status, case ID, and man-hours for the selected day. [Figure 5C] FIG. 5(c) shows an example of a management screen that displays monthly man-hours / monthly overtime man-hours in a graph format. [Figure 5D] FIG. 5(d) shows an example of a management screen that displays monthly man-hours / monthly overtime man-hours in a graph format. [Figure 6] FIG. 6 shows an example of a management screen that displays a list of monthly statutory overtime hours and statutory holiday working hours for each employee on an annual basis. [Figure 7A] FIG. 7(a) shows an example of a flowchart of a software program for realizing the attendance management method of the present invention. [Figure 7B] FIG. 7(b) shows an example of a flowchart of a software program for realizing the attendance management method of the present invention. [Figure 7C] FIG. 7(c) shows an example of a flowchart of a software program for realizing the attendance management method of the present invention. [Figure 7D] FIG. 7(d) shows an example of a flowchart of a software program for realizing the attendance management method of the present invention. [Figure 8] FIG. 8 shows an example of the configuration of an attendance management system that executes a software program to realize the attendance management method of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0040] Figure 1 shows a timeline showing an example of the arrival and departure times of a worker in one day, and an example of the structure of data records in a database (hereinafter referred to as "DB") that captures and records the arrival and departure times of the worker, and the relationship between them.

[0041] In the figure, 11, 13, and 15 indicate the worker's arrival time on a timeline (horizontal axis) that shows the passage of time t on a certain working day, and 12, 14, and 16 indicate the worker's departure time, respectively.

[0042] Additionally, the times between 11 and 12, between 13 and 14, and between 15 and 16 indicate the working hours "Commuting 1," "Commuting 2," and "Commuting 3," respectively. In other words, these are examples of the worker working three shifts on this day.

[0043] In the present invention, the arrival and departure times of workers who work in a shift that involves coming to and leaving work multiple times a day are grasped and recorded. Here, since the number of times a worker comes to and leaves work in a day is indefinite, the number of records that record the arrival and departure times is also indefinite. For this reason, the data records in Fig. 1 do not have to exist in advance as three. For example, each time the system grasps the attendance of a worker, a new record is generated in the DB and the arrival and departure times are recorded.

[0044] Arrow 110 in FIG. 1 indicates that data record 1 in the work management data TBL (TBL is used as an abbreviation for "table." Here, a table refers to a data table included in a DB. The same applies below) was generated in response to arrival and departure times 1.

[0045] Similarly, arrow 120 indicates that data record 2 was generated in correspondence with clock-in / clock-out time 2, and arrow 130 indicates that data record 3 was generated in correspondence with clock-in / clock-out time 3, respectively.

[0046] In addition to the pair of "work arrival time" and "work departure time", the data record in FIG. 1 also has a pair of "work start" and "work end". However, both may be present depending on the attendance management rules of the company implementing the present invention. For example, in a company that regards the work arrival time as the work start time, there may only be a pair of "work start" and "work end", and the data record may not have a pair of "work arrival time" and "work end time".

[0047] These variations are indicated by solid arrow 17 and dotted arrow 18 in FIG.

[0048] The solid arrow 17 indicates that the arrival time and departure time of attendance record 1 are recorded in the "arrival time" and "departure time" elements of data record 1, respectively.

[0049] For example, in companies that have installed a flapper gate at the entrance to the office and have employees hold their employee ID cards or special security cards over the card sensor of this gate to record entry and exit times, the time when the employee passes through the gate is recorded as the "clock in time" and "clock out time," and separately, the time when an employee sits down at their desk and actually starts their assigned work, for example, the time when they log in and log out of their PC terminal at their desk, or the time when they take up and finish work procedures in some other way, is recorded as the "start of work" and "end of work" time.

[0050] The "work start" and "work end" times may be registered each time an employee clocks in and out of work, or, for example, the "work start" and "work end" times for the previous day may be registered the day after an employee clocks in and out of work.

[0051] In this case, the "man-hours" element of data record 1 can be configured so that when the "end of work" time is recorded, the time from the "start of work" time to the "end of work" time is calculated and recorded as man-hours.

[0052] On the other hand, the dotted arrow 18 indicates that the working time and clock out time of working time 1 are recorded in the "work start" and "work end" elements of data record 1, respectively.

[0053] This is an example of the case where the present invention is applied to a company or the like that treats the arrival and departure times as the "start of work" and "end of work" times. In this case, too, the "man-hours" element of data record 1 can be configured to calculate the time from the "start of work" time to the "end of work" time when the end of work time is recorded, and record this as man-hours.

[0054] Needless to say, in this case, it is not necessary for the elements "start time" and "end time" to be included in record 1.

[0055] Furthermore, for example, the "employee ID" does not have to be included in this data record, but can be linked to the ID information of the employee data registered in advance in a separately provided "employee data TBL", making it possible to determine whose attendance data record it is.

[0056] Thus, the configuration of elements of a data record may have many variations and is not limited to the configuration disclosed in FIG.

[0057] In this way, when multiple arrivals and departures are recorded in a day and multiple data records are generated, the total man-hours for that day can be calculated by adding up the values ​​of the "man-hours" element recorded in each data record.

[0058] Needless to say, it is possible to calculate the total man-hours for a work day even if each data record does not have a "man-hours" element. By using data extraction and calculation functions such as DB queries, it is possible to configure the system to calculate the total man-hours for that day by referencing the time information recorded in the work start and work end elements of each data record that belongs to that day.

[0059] FIG. 2 illustrates a specific method for recording time information in each of the elements "time at work," "time off work," "start of shift," and "end of shift" in one of the data records in FIG. 1 (generalized as "data record n" in FIG. 2).

[0060] FIG. 2(a) shows an example in which an employee clocks in and out of the office, mainly from outside the office, such as at home.

[0061] Employees can clock in and out from outside the company, such as at home, using information terminals they carry with them, such as smartphones, smart watches, tablet devices, and mobile PCs.

[0062] In other words, the system can be configured so that when an employee operates a mobile information terminal and goes through the prescribed authentication procedures, such as logging in to the company's DB server via a network, whether wireless or wired, a menu screen (not shown) is displayed, and when the "clock-in / clock-out" menu is selected from there, the operation screen 21 shown in the figure is displayed.

[0063] By tapping or clicking (hereinafter referred to as "clicking, etc.") either the "Clock in" button 22 or the "Clock out" button 23 displayed on the display screen 21, the time of the operation can be registered as the "Clock in time" or "Clock out time" in the data record of the company's DB server via the network.

[0064] This method is not limited to cases where the "clock-in time" and "clock-out time" are punched from outside the company, such as when the employee is out, but may also be done within the company or on the screen of a PC terminal at one's desk. Also, a computer may detect the clock-in and clock-out times of employees, etc., and register the clock-in and clock-out times in a data record. For example, when a computer detects the clock-in and clock-out times using a camera, a flap gate, a security card, etc., the time of detection is registered in the data record as the clock-in and clock-out times.

[0065] Figure 2(b) is intended for cases where the arrival time and departure time are registered primarily on the PC terminal screen of one's own desk at the office, but this is not a limitation. The key point is that the "arrival time" and "departure time" are manually registered as times that are different from the current time.

[0066] For example, if you start working as soon as you arrive at work and forget to register your arrival time, or if you forget to register your departure time when you get home the previous day, you may need to register a time different from the current time. This is an example of how to enter your arrival and departure times for such cases.

[0067] In this case, too, when an employee operates an information terminal and goes through a prescribed authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and by selecting the "Enter work arrival and departure times" menu there, the screen shown in the figure can be reached. In the figure, an employee can register his or her own arrival and departure times by entering times in the arrival and departure time input field 25 and the departure time input field 26 displayed on the display screen 24, and clicking the registration button 242, for example.

[0068] Also, for example, if one wishes to register the arrival and departure times of any given day before the previous day, the screen 24 can be configured to allow one to move forward or backward in date by clicking the "Previous" or "Next" button 241 on the screen 24, for example.

[0069] Furthermore, when you perform a "Register" operation on this screen, including the arrival and departure times, a new attendance data record is generated in the database, and the arrival and departure times are recorded.

[0070] FIG. 2(c) is different from (a) and (b) in that it illustrates a method for manually registering the "start of work" and "end of work" times after the arrival and departure times have already been registered.

[0071] For example, in a company that has installed a flapper gate at the entrance to the office and has employees hold their employee ID cards or special security cards over the card sensor of this gate to obtain the entry and exit times and record these times in the "Arrival time" and "Leaving time" elements of the data record, this is assumed to be the case in a company that has adopted a system in which the start and end times of the previous day's work are registered after the fact by self-reporting.

[0072] In this case as well, when an employee or the like operates an information terminal and goes through a prescribed authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and when the "Enter work start / end time" menu is selected from there, the screen 27 in Fig. 2(c) can be reached. In the figure, the employee or the like can register his or her own work start time and end time of the previous day by entering times in work start time input field 28 and work end time input field 29 while referring to, for example, the previous day's arrival time and departure time displayed on display screen 27, and clicking "Register" button 272, etc.

[0073] Here, for example, if there were multiple clock-in / clock-outs on the previous day, it is necessary to select which clock-in / clock-out data to enter. For this reason, the "clock-in / clock-out number" is displayed on the screen 27, and "Previous" and "Next" buttons 271 are provided so that the number can be moved forward or backward. By clicking the "Previous" and "Next" buttons, the "clock-in / clock-out number" is increased or decreased, and the desired clock-in / clock-out number data can be accessed.

[0074] Also, for example, if you want to register the start / end time of any work day on any day before the previous day, you can select the "Date" display section on screen 27 by clicking on it, and then click on "Previous" or "Next" button 271 to move forward or backward in the date.

[0075] In this way, the data for each element, "time to work", "time to leave work", "start of shift", and "end of shift", can be grasped and registered in various ways. It goes without saying that the methods are not limited to the three examples above, and can be configured in even more diverse ways.

[0076] 3(a) and (b) show examples of a method for registering case IDs in the “case ID” elements 111 to 113 of data records 1 to 3 in FIG.

[0077] In this case, too, when an employee operates an information terminal and goes through a prescribed authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and when the "Case ID setting" menu is selected from the menu screen, the screen of Fig. 3(a) can be reached. In Fig. 3(a), the display screen 31 can be configured so that the employee can input the "Case ID" of the corresponding case (in this example, "B123-4567" for "Case 1") according to the work content that he or she performed, into each "Case ID" field corresponding to "Clock in / out 1," "Clock in / out 2," and "Clock in / out 3" displayed on the display screen 31.

[0078] After setting the case ID for each entry and exit, the employee, etc., finalizes the set case ID by, for example, clicking the "Register" button 311 on screen 31. This causes the set case ID to be recorded in the case ID element of each corresponding data record in the DB.

[0079] Here, there may be cases where a person is required to work on multiple cases during one shift. Figure 3(b) shows an example of how to handle such a case.

[0080] In FIG. 3(b), for example, if work corresponding to two cases is performed during clock-in / clock-out 2, to register two case IDs for clock-in / clock-out 2, add two lines for "clock-in / clock-out 2" and register a case ID in each line.

[0081] Specifically, first, select "Attendance 2" by clicking on it as indicated by the P1 arrow in the diagram. When selected, "Attendance 2" will change color or some other way to make it clear that it has been selected. Next, when the "Add Row" button as indicated by the P2 arrow in the diagram is clicked, a row is added as indicated by the P3 arrow in the diagram, and another row for "Attendance 2" is displayed. The case ID of the second case is registered in this row.

[0082] In this example, the "Arrival time" and "Leaving time" in the added row for "Attendance 2" are copied to be the same times as the original "Attendance 2." Employees, etc. refer to this and enter the ID of the case they worked on in the Case ID column for each row, and enter the man-hours spent on each case in the respective "Man-hours" columns. At this time, the value displayed in the "Man-hours" column for the original "Attendance 2" must be changed. This displayed value can be overwritten by the employee, etc., entering the man-hours spent on the work for that case ID.

[0083] Furthermore, if work related to more cases is performed during a single entry / exit, the above-mentioned method can be used to perform further "add row" operations and enter a case ID into each row.

[0084] In this case, too, after setting the case ID and man-hours for each attendance, the employee clicks the "Register" button 311 on the screen 31. It goes without saying that the system can be configured to generate new records in the DB according to the number of attendance rows set on the screen 31 when the "Register" operation is performed.

[0085] In addition, since the total man-hours for Attendance 2 can be calculated from the "Arrival time" and "Leaving time" for Attendance 2, when a row is added, the system checks whether the sum of the man-hours spent on each project in multiple rows matches the total man-hours for Attendance 2, and if they do not match, a display is displayed to alert employees, etc.

[0086] Figures 4(a) and (b) show examples of a case ID registration method that differs from that explained in Figure 3. In other words, Figure 3 shows a method in which case IDs and man-hour data are recorded for each "attendance" for multiple attendances in one day in a so-called "one shift, one case, one record" format, whereas Figure 4 shows a method in which case IDs and man-hour data are registered based on how many hours work was performed for each case on a daily basis, based on the total man-hours for the day (hereinafter referred to as "total man-hours"), and "man-hours by case" data is grasped and recorded in a so-called "one case, one record per day" format.

[0087] In this case, too, the configuration in Figure 1 is applied in that the total man-hours for one day that can be calculated from "attendance" data recorded in the "one shift, one case, one record" format is used as the basis. However, when grasping the man-hours for each case using the method in Figure 4, it is not necessary for the case ID and man-hours elements to exist in the data record in Figure 1, and it is possible to generate a data record separate from that in Figure 1 for each case, as shown in 412 to 414 in Figure 4(a), and configure it so that the man-hours are managed on a case-by-case basis.

[0088] Fig. 4(a) shows an example of a "Project-by-Project Man-Hour Breakdown Input Screen" for registering the project ID and the man-hours spent on the project based on the project classification. In this case, too, when an employee or the like operates an information terminal and goes through a prescribed authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and the screen of Fig. 4(a) can be reached by selecting the "Project-by-Project Man-Hour Breakdown Input" menu.

[0089] In the figure, display 41 shows a list consisting of a case classification column, a case ID column, and a labor hour column, along with the "date" indicating which work day the display refers to, the "total labor hours" for that day, and the "employee ID" indicating the employee in charge.

[0090] Generally, an employee may process more than one case per day, so for ease of registration, the list may be configured to display four or five rows from the beginning.

[0091] On screen 41, if the number of tasks performed is greater than the number of rows displayed, for example, by clicking the "Add case category" button pointed to by the arrow P1 in Figure 4(b), the screen can be configured to additionally display a row for case category "4" pointed to by the arrow P2 in the figure.

[0092] Furthermore, if more case categories are added, for example, the number of rows that can be expanded in the table for display purposes may be limited to five rows, and beyond that, the number of rows in the table itself may be increased, and the screen display may be configured to allow scrolling up and down within the display range of those five rows, for example.

[0093] In either case of Figure 4(a) or (b), when an employee, etc., enters a case ID in the "Case ID" column of the list, enters man-hours in the man-hours column, and performs a registration operation such as clicking the "Register" button 411, the required number of case-specific data records will be generated in the DB depending on the number of case categories for which data has been entered at that time, and the data can be recorded in each of the elements: employee ID, date, case ID, and man-hours.

[0094] First Example As mentioned above, one of the required functions in employee attendance management based on the technology to grasp, record, and manage the daily attendance data of employees who may work multiple times a day is the progress management of man-hours based on the total man-hours for each employee.

[0095] That is, a monthly list of man-hour progress for each employee may be displayed, or the progress may be displayed in a graph format so that the situation can be more visually understood. In addition, the monthly progress of overtime hours may be displayed in a list format or in a graph format.

[0096] Fig. 5(a) shows an example of a configuration in which the total man-hours for each employee are displayed in a daily list, together with weekly and monthly aggregated values. In this case, too, when an employee operates an information terminal and goes through a prescribed authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and when the "Monthly Man-hour Management" menu is selected from the menu screen, the screen in Fig. 5(a) can be reached. Screen 51 is called the "Monthly Man-hour Management Screen" and displays a list of daily total man-hours. It goes without saying that, for example, it can also be configured to display aggregated values ​​for each day of the week.

[0097] Using this display screen, the manager can see the daily distribution of man-hours in concrete figures, as well as read the busyness of each week and the amount of man-hours required on each day of the week.

[0098] Here, for example, you may want to check the details of the workload for Tuesday of the second week, because it is significantly higher than the other days. In such a case, if you select the date column for Tuesday of the second week, shown as 511 in the figure by clicking on it, Figure 5(b) will be displayed.

[0099] In Fig. 5(b), the selected sunrise / sunrise / shutdown situation, work start / end times, and the case ID and man-hours of the completed work are displayed on screen 52, allowing you to confirm the specific details. This allows you to see what the sunrise / shutdown situation was like, as well as the working hours, work content, and man-hours for each sunrise / shutdown.

[0100] Here, Figures 5(a) and (b) may be provided for the administrator to view for management purposes, but may also be made available for each employee to view in order to check their own working conditions. For example, when viewing the list display screen 51 in Figure 5(a) to review their own working conditions for the current month, if the man-hours for Tuesday of the second week are unexpectedly large or small, the employee can select that day and check the details on screen 52 in Figure 5(b).

[0101] Furthermore, if any error or the like is found in the registered data, the data registered in the corresponding data record can be corrected and updated by, for example, selecting the cell in the table that needs to be corrected by clicking on it, updating the data appropriately, and clicking on the "Edit" button 521, for example.

[0102] Fig. 5(c) shows an example of a display screen configured to display the list display format of the monthly man-hour management screen in Fig. 5(a) in graph format. In this case, too, when an employee or the like operates an information terminal and goes through a predetermined authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and when the "Monthly man-hour management (graph display)" menu is selected there, the screen in Fig. 5(c) can be reached.

[0103] For the employee identified by "Employee ID" at the bottom left of screen 53, the total man-hours for each day are shown in a bar graph, starting from the first day of the month displayed in "Year and Month" at the top right of the screen, and the cumulative values ​​for each day are displayed in a line graph 531. In this example, data up to the 16th of the current month is currently displayed. In other words, this screen is displayed and viewed at a certain time on the 17th of the same month.

[0104] This example shows a month in which the 1st (the first day of the month) is a Monday. In other words, the 6th is a Saturday and the 7th is a Sunday, which are holidays for the example company and no work is done, so the total man-hours are zero. On the other hand, the total man-hours increase on the 13th (Saturday) and the 14th (Sunday) because people worked on those days, and in this example, the color of the bar graphs has been changed to make it clear that people worked on those days.

[0105] Line graph 532 shows the cumulative trend of the total man-hours for week 2. Line graph 532 stops at the end of Sunday the 14th so that only the trend for week 2 can be read. To make it possible to understand the relationship between the total work hours for one week and the statutory weekly work hour regulation value, a horizontal line indicating the "weekly upper limit" is displayed at a height of 40 hours on the vertical axis, and line graph 532 can be seen to exceed this limit.

[0106] Similarly, line graph 533 shows the cumulative progress of the total effort for the third week.

[0107] Here, only the line graph 531 for the first week is drawn from the second week onwards in order to display the cumulative progress for the first week together with the cumulative progress for the month. This is configured to make it easy to read how this progress is progressing against the line indicating the legal upper limit of monthly man-hours and the line indicating 100 hours of overtime.

[0108] In this example, a graph 534 is displayed, which predicts how much the man-hours are expected to increase by the end of the month, assuming that the cumulative total man-hours up to the 16th of the month is divided by the number of days that have passed. This shows that the man-hours are progressing at a pace that could reach the 100-hour overtime line by the end of the month if things continue as they are.

[0109] FIG. 5(d) is a "monthly overtime man-hours management screen," as shown in a different color at the top of screen 54. In this case, too, when an employee or the like operates an information terminal and goes through a prescribed authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and when the employee selects the "monthly overtime man-hours management (graph display)" menu there, the screen of FIG. 5(d) can be reached. FIG. 5(d) displays only the overtime hours of the total man-hours in FIG. 5(c) in a graph. Accordingly, the number of hours on the vertical axis is changed from FIG. 5(c), and the regulation value display lines for overtime hours are set to a "weekly upper limit" of 45 hours and a "special upper limit" of 100 hours.

[0110] Each graph shows only the overtime hours extracted from the employee's man-hours in Figure 5(c). In other words, the 6th and 7th of the month were Saturday and Sunday, so there was no work and no overtime, but the 13th and 14th were Saturday and Sunday, so the employee worked on the holidays, and so the total man-hours are all counted and displayed as overtime. As a result, line graphs 541 and 542 show a sharp increase on Saturday and Sunday, the 13th and 14th. Line graph 543 shows the cumulative change in overtime hours in the third week.

[0111] In Figure 5(d), a graph 544 is displayed that predicts how much the overtime hours are expected to increase by the end of the month if the cumulative total of the overtime hours up to the 16th of the month is divided by the number of days that have passed. This shows that the overtime hours are increasing at a pace that could exceed the "special upper limit" of 100 hours of overtime by the end of the month if things continue as they are.

[0112] Incidentally, in Figure 5(d), the line graph showing the cumulative amount of overtime work is shown as an example that roughly rises to the right. However, in the future, when workers are able to clock in and out at any time they like at their own discretion, the cumulative amount of overtime work will not necessarily rise to the right, and may fluctuate depending on the working conditions.

[0113] For example, it is conceivable that the total number of hours that an employee works each month may fall short of the regular working hours. In that case, as is the case with companies that currently use flextime systems, it is conceivable that the shortfall in the regular working hours during the month may be offset by working a certain amount of overtime.

[0114] In this case, the offsetting of overtime hours with normal working hours can be done in various ways, such as daily, weekly, or monthly. If it is done daily or weekly, the line graph of overtime hours will increase or decrease for each unit.

[0115] In such cases, the present invention records the time data for each time an employee clocks in and out, including early morning and late night hours, so that regular working hours and overtime hours can be calculated in accordance with the employment rules of the company where the employee works, and it can be configured to properly handle, for example, offsetting calculations between them.

[0116] In addition, there are several categories of overtime hours to be managed, and typically, a period and a time limit within that period are set for each category.

[0117] As an example of classification, the Japanese Labor Standards Act first regulates statutory working hours. According to this, the working hours per day at the time of filing this application are set at 8 hours, and the working hours per week at 40 hours. Any working hours exceeding these limits must be considered as overtime work.

[0118] Overtime work hours are limited to 45 hours per week and 360 hours per year, and furthermore, when special clauses are applied, the upper limit is set as follows: the number of times that 45 hours per month can be exceeded is 6 times per year, the average monthly overtime hours and holiday work hours combined is 80 hours over a 2-6 month period, the total overtime hours and holiday work hours combined is 100 hours per month, and the total overtime hours per year is 720 hours. (The above values ​​are the work hour restrictions set out in the Japanese Labor Standards Act at the time of writing the specification of the present invention.)

[0119] The "weekly upper limit," "legal upper limit," and "100 hours of overtime" on the monthly labor hour management screen, and the "weekly upper limit" and "special upper limit" on the monthly overtime labor hour management screen shown in Figures 5(c) and (d) above are examples of these regulatory values.

[0120] Figure 6 shows an example of a "Legal overtime and statutory holiday work hour upper limit management screen" that displays and manages a list of annual overtime work hours that cannot be managed on a monthly basis. In this case, too, when an employee operates an information terminal and goes through a prescribed authentication procedure, such as logging in to the company's DB server, a menu screen (not shown) is displayed, and by selecting the "Legal overtime and statutory holiday work hour upper limit management" menu there, the screen in Figure 6 can be reached.

[0121] Screen 61 in Figure 6 allows you to manage the statutory overtime hours, statutory holiday overtime hours, and their total values ​​for the employee identified by the "Employee ID" displayed in the upper left, for the "Year" in the upper right corner of the screen, in a list.

[0122] It goes without saying that, in the same way as the example graphs shown in Figures 5(c) and (d) are used to compare the list display in Figure 5(a) with Figure 6, the annual trend in overtime work hours can also be displayed in a graph as appropriate.

[0123] Operation explanation Next, the operation of the attendance management system of the present invention, which can also accommodate a work style in which workers clock in and out multiple times a day at any time at their discretion, will be described with reference to FIG.

[0124] FIG. 7 shows an example of a flowchart for explaining the operation of the attendance management system of the present invention.

[0125] Referring to Figure 7(a), it can be seen that the control program for the attendance management system of the present invention is configured to start execution from step S100, and then execute step S200 of grasping and recording the worker's multiple arrival and departure times per day, step S300 of calculating the worker's total daily man-hours, and step S400 of tallying up and managing the total daily man-hours, and repeat these steps.

[0126] Here, in Fig. 7, for the purpose of explanation, a configuration in which a series of programs are repeatedly executed is disclosed, but this is described as an example of a configuration that can respond without delay when an employee or other person operates an information terminal, and is not limited to such a loop configuration. Currently, it is generally known that software programs can be configured to detect user operations, such as so-called "event-driven," and launch necessary processing depending on the content of the operations.

[0127] However, if one were to apply such a structure to an explanation as is, the flow chart would become fragmented for each event, and the explanation would inevitably become complicated and difficult to understand.

[0128] Therefore, for ease of explanation and understanding, this specification will show an example of a flowchart as a more general software that detects events by program.

[0129] The following description is one embodiment of the present invention, and a program having the same effect can be created with a configuration other than the flowchart of Fig. 7. Therefore, the program of the present invention is not limited to the configuration of the flowchart disclosed in Fig. 7, and it goes without saying that programs with various configurations are included in the scope of the present invention without departing from the gist of the present invention.

[0130] Step S200 in FIG. 7(a) “grasp and record the worker's arrival and departure times multiple times a day” can be realized, for example, by configuring the system as shown in the flowchart in FIG. 7(b).

[0131] That is, starting from step S201, first in step S202, it is checked whether or not a "time registration" operation has been performed. This is to check whether the registration button 242 in Fig. 2(b) or the registration button 272 in Fig. 2(c) has been clicked. If either of them has been clicked, step S202 proceeds to "Y".

[0132] Next, in step S203, it is checked whether the button that was clicked is the registration button 272 in Fig. 2(c). If so, proceed to "Y", and in step S204, the time entered in the work start time input field 28 in Fig. 2(c) and the time entered in the work end time input field 29 in Fig. 2(c) are recorded in the "work start time" and "work end time" elements of the data record in the DB corresponding to the date and attendance number displayed in the upper right corner of the screen 27 in Fig. 2(c), respectively.

[0133] If there is no operation of the time registration button in Figures 2(b) and (c), or if the registration button clicked, etc. is 242 in Figure 2(b), or if recording in step S204 is completed, proceed to step S205 and check whether the employee, etc. has registered the time of arrival.

[0134] This includes detection of an operation such as clicking on the "Clock in" button 22 on screen 21 in FIG. 2(a) and an operation such as clicking on the "Register" button 242 on screen 24 in FIG. 2(b).

[0135] If any of these operations is detected, step S205 proceeds to "Y", and in step S206 a new data record is generated in the DB and the working time is recorded in the "working time" element.

[0136] If the clock-in operation is not detected, or if the clock-in time registration is completed in step S206, the process proceeds to step S207, where a clock-out time registration operation by an employee or the like is checked.

[0137] This includes detection of an operation such as clicking the "Clock Out" button 23 on the screen 21 in FIG. 2(a) and an operation such as clicking the "Register" button 242 on the screen 24 in FIG. 2(b).

[0138] If any of these operations is detected, step S207 proceeds to "Y", and the work-clock time is recorded in the "work-clock time" element in step S208. If the "Register" button 242 in Fig. 2(b) is clicked, the work-clock time entered in the work-clock time input field 26 is recorded in the "work-clock time" element of the data record.

[0139] If a clock-out operation is not detected, or if the recording process of the clock-out time is completed in step S208, the process proceeds to step S209, where the process of step S200 in FIG. 7(a) ends.

[0140] The next step S300 in FIG. 7(a) “calculate the total man-hours of workers in one day” can be realized, for example, by configuring as shown in the flowchart in FIG. 7(c).

[0141] That is, starting from step S301, first, in step S302, it is checked whether it is time to execute "daily processing". For example, the attendance management system may be equipped with a timer to execute the daily processing at a certain time before dawn each day, or an employee may execute the daily processing when necessary. When the timing to execute the daily processing is detected, step S302 proceeds to "Y".

[0142] In step S303, it is checked whether there is an attendance data record included in the target day of the daily processing, such as the day or the previous day. This is because there are days when there are no attendance data records of employees, such as company holidays.

[0143] When a data record to be processed is found, step S303 proceeds to "Y". Then, for each employee, the man-hours recorded in the "man-hours" element of the multiple data records are totaled to calculate the total man-hours for the day. This totaling process is repeated in step S305 until the next record is not found.

[0144] For example, in the case of an employee who clocks in and out three times in one day, as shown in FIG. 1, the existence of data record 1 is detected first, so step S303 proceeds to "Y", and in step S304, the data recorded in the "man-hours" element of data records 1 to 3 is totaled.

[0145] In this way, when the counting for one day is completed, step S305 proceeds to "N", and the process ends in step S306.

[0146] The next step S400 in FIG. 7(a) "total man-hours per day are collected and managed" can be realized, for example, by configuring as shown in the flowchart in FIG. 7(d).

[0147] That is, starting from step S401, first, in step S402, it is checked whether or not an "Administration" screen display operation has been performed. If any administration screen display operation is detected, step S402 proceeds to "Y", and the respective administration screen is displayed according to the display flow of the selected administration screen.

[0148] The "Monthly man-hours management screen (list display)" displayed in step S403 is screen 51 in Fig. 5(a). If date 511 of Tuesday of the second week is clicked or the like in Fig. 5(a), the operation is detected in step S404 in Fig. 7(d) and the process proceeds to "Y", and in step S405, the "Work status management screen" 52 in Fig. 5(b) is displayed. In step S405, as described above with respect to Fig. 5(b), corrections are made to the registered case ID, man-hours, etc., and when the data update of the data record is completed, the process proceeds to step S412 in Fig. 7(d) and ends the process.

[0149] The "Monthly Man-hour Management Screen (Graph Display)" displayed in step S406 is screen 53 in Fig. 5(c). To display this screen, data on the total man-hours per day for the employee identified by the "Employee ID" displayed on screen 53 is used. The data collected in step S300 in Fig. 7(a) may be used as the total man-hours data, but it may also be configured to collect and use, as necessary, the recorded data of the "man-hours" element in data records 1 to 3 shown in Fig. 1, for example.

[0150] The "Monthly overtime man-hours management screen (graph display)" displayed in step S407 is screen 54 in Fig. 5(d). To display this screen, it is necessary to calculate and use the overtime hours based on the data of the total man-hours per day of the employee identified by the "employee ID" displayed on screen 54.

[0151] The "Legal Overtime / Legal Holiday Work Hours Upper Limit Management Screen" displayed in step S408 is screen 61 in Fig. 6. To display this screen, it is necessary to calculate and use the statutory overtime work hours and statutory holiday overtime work hours based on the data on the total daily man-hours of the employee identified by the "Employee ID" displayed on screen 61.

[0152] "Input case ID and man-hours on man-hours breakdown input screen for each case" in step S409 refers to the operation of displaying the "input man-hours breakdown screen for each case" 41 described in Figs. 4(a) and (b) and setting the case ID and man-hours. When an employee or the like operates screen 41 in Fig. 4 to input data and clicks the "Register" button 411, "register case" is detected in step S410 in Fig. 7(d) and the process proceeds to "Y". As a result, in step S411, data records 412 to 414 shown in Fig. 4(a) are generated in the DB for each registered case, and the input case ID and man-hours are recorded in the "case ID" and "man-hours" elements of each record. When step S411 is completed, the process proceeds to step S412 and ends.

[0153] Returning to FIG. 7(a), when step S400 is completed, control returns to step S200, and the above processing is repeated.

[0154] System configuration example FIG. 8 shows an example of an embodiment of the attendance management system of the present invention.

[0155] 8, 81 and 82 are information input / output terminals including smartphones, smart watches, tablet terminals, mobile PCs, etc. owned by general employees, including in-house workers and external workers such as temporary workers. Employees 811 and 821 are users of the information input / output terminals 81 and 82, respectively. The number of these is not limited to the two shown in the figure, and may be as many as the number of employees.

[0156] These information input / output terminals are used by connecting to a DB 84 via a network 83. The network 83 may be a general-purpose network such as the Internet, or may be a dedicated line such as a so-called VPN, or in the case of a small-scale system, may be configured as an in-house LAN network.

[0157] DB84 can be configured as a computer-based information processing system such as a so-called DB server. This is configured to include at least a "Work Management Data TBL" 841 that records the attendance data, case ID data, various man-hour data, etc. of each employee, an "Employee Data TBL" 842 that records information about employees such as the employee ID and employee name of each employee, and a "Work Rules Data TBL" 843 that records information about the company's work rules, etc.

[0158] The attendance management terminal 85 is connected to the DB 84 and is operated mainly by employees of the management staff department, etc., and is used for attendance management such as progress management of the number of hours worked and the number of overtime hours worked by each worker. Employees, etc. 851 are employees of the staff department, etc.

[0159] In Fig. 8, employees, including those in the staff department, register their arrival and departure times or work start and end times in the DB using information input / output terminals 81, 82, and 85, respectively, in the manner shown in Fig. 2(a), (b), and (c). This operation generates data records 1 to 3, as shown in Fig. 1, records the arrival and departure times and work start and end times, and calculates man-hours.

[0160] In addition, general employees 811, 821, etc. shown in Figure 8 can register the case ID and man-hours for the cases they performed for each time they clock in and out by operating screen 31 shown in Figures 3(a) and (b).

[0161] Furthermore, general employees 811, 821, etc. shown in FIG. 8 can also register the case ID and man-hours for each case they have completed by operating screen 41 shown in FIGS.

[0162] An employee 851 in a staff department or the like shown in Figure 8 can operate the attendance management terminal 85 and refer to each management screen, for example, as shown in Figures 5(a), (b), (c), (d), and 6, to perform attendance management tasks for each employee.

[0163] In addition, if the management screens shown in Fig. 5(a), (b), (c), (d) and Fig. 6 are configured so that general employees 811, 821 can refer to their own data, they can manage their own man-hour progress, overtime man-hour progress, etc. In particular, if they notice something abnormal in the data for a certain day by referring to Fig. 5(a), they can check it individually and make appropriate corrections as shown in Fig. 5(b). In addition, if the general employees 811, 812 have subordinates, they can manage their subordinates' man-hour progress, overtime man-hour progress, etc. by configuring the screens so that they can refer to their subordinates' data when referring to their own data.

[0164] The information processing system shown in FIG. 8 can be implemented in various forms.

[0165] For example, in a small or medium-sized enterprise, if one wishes to realize a system with a minimal configuration, it is possible to implement all of the functions of the information input / output terminals 81, 82, DB 84, and attendance management terminal 85 in a single notebook PC without using the network 83.

[0166] Alternatively, in medium-sized enterprises etc., a server device for the attendance management system can be installed within the company, DB 84 and various calculation processing programs can be installed on it, and general employees can be provided with information input / output terminals 81 etc. which can be connected to the server device via network 83 and access DB 84. Attendance management terminals 85 can also be installed in staff departments etc. to create the system shown in Figure 8.

[0167] Furthermore, in large companies, DB84 and various calculation processing programs, etc. can be implemented on a server on a cloud system provided by so-called cloud services, and information terminals 81, 82, etc. used by each general employee and attendance management terminals 85, etc. used by employees in the staff department, etc. can be connected to the server via network 83, allowing the construction and use of a so-called SaaS (Software as a Service) system.

[0168] Second Example As mentioned above, when managing the attendance of employees who may work multiple shifts in a day, one of the required functions is to manage the man-hour progress for each project, based on the technology to grasp, record, and manage the daily attendance data of such employees.

[0169] That is, for each project, a monthly list of man-hour progress may be displayed, or the progress may be displayed in a graph format so that the situation can be more visually understood. In addition, the monthly change in overtime hours may be displayed in a list format or in a graph format.

[0170] In this case, the daily man-hours for each case, which are the basis for constructing the display, can be obtained by the method described in Fig. 4. That is, the man-hours are recorded for each case ID in data records 412-414 shown in Fig. 4(a). Alternatively, it is also possible to use each data record shown in Fig. 1 as the basis and separate records for each case by the method shown in Fig. 3(b), and to extract equivalent information from the "case ID" and "man-hours" elements of each record by using a data processing function such as a DB query.

[0171] The monthly list display of man-hours for each project will be similar to that shown in Fig. 5(a), so a specific illustration will be omitted. If the "Employee ID" in the lower left corner of screen 51 in Fig. 5(a) is changed to "Project ID," it can be configured as a monthly man-hours management screen for the project.

[0172] In this case, for example, in Fig. 5(b) that is displayed by clicking on the date column 511 for Tuesday of the second week, the "Employee ID" in the bottom left of the screen 52 is treated as the "Project ID," and the "Employee ID" of the employee in charge of the project is displayed in the "Attendance 1," "Attendance 2," and "Attendance 3" columns of the table. The number of man-hours spent by each employee on that day can then be displayed in a corresponding table. This makes it possible to know who worked on the project for how many hours on that day.

[0173] In Figure 5 (c), the "Employee ID" in the bottom left of the screen 53 is used as the "Project ID," and the daily total amount of man-hours spent on the project by each employee in charge of the project is displayed as a bar graph, and the cumulative total can be plotted as a line graph 531.

[0174] In this case, the man-hour value on the vertical axis may be the upper limit of the estimated man-hours planned for the project. This allows a visual understanding of the current progress against the planned estimated man-hours. In addition, by plotting the forecast line 534 as a planned line of estimated man-hours to be used from the start of work to the delivery date, it is possible to read the excess or shortage of the actual usage of man-hours against the plan.

[0175] In FIG. 5(d), the “Employee ID” in the bottom left of the screen 54 is used as the “Project ID,” and the daily total amount of overtime hours worked by each employee in charge of the project is displayed as a bar graph, and the cumulative total can be plotted as a line graph 541.

[0176] In this case, the value of the man-hours on the vertical axis may be the upper limit of the planned overtime man-hours planned for the project. This allows a visual understanding of the current progress against the planned overtime man-hours. In addition, if the forecast line 544 is plotted as a planned line using the planned overtime man-hours from the start of work to the delivery date, the actual overtime man-hours against the plan can be read. [Explanation of symbols]

[0177] 11,13,15 Work time 12,14,16 Leave work time 21 Time clock screen 24. Work entry time input screen 25. Enter your working time 26. Input field for clock-out time 27 Work start / end time entry screen 28 Work start time input field 29 Entry field for end of work time 31 Item ID setting screen 41 Input screen for labor hours breakdown by project 412,413,414 DB records of man-hours for each project 51 Monthly man-hour management screen 52 Work status management screen 53 Monthly man-hours management screen (graph display) 54 Monthly overtime work management screen (graph display) 61 Overtime and Holiday Working Hours Upper Limit Management Screen 81,82 Information input / output terminal 83 Network lines 84 DB system 85 Attendance management terminal

Claims

1. A work management method executed by one or more computers, which records the work start time and work end time of a worker who may work two or more times a day with time not managed by the workplace in between, The computer includes: Each time, when information including the ID, date, and start time of work of the worker is acquired, a work management data record including at least the date and start time of work corresponding to the ID is generated and recorded in the work management data TBL of the database; Each time, when information including the ID, date, and work end time is obtained, which notifies the worker of the end of work, searching for a work management data record corresponding to the ID in the work management data TBL and extracting a work management data record in which the most recent work start time is recorded; recording the obtained end time of work in the extracted time management data record; A work management method that implements the above.

2. The work management method further comprises: When information is acquired that indicates that the work start time and / or the work end time have been modified, and that includes the modified work start time and / or the work end time, and identification information of the work management data record to be modified, searching the work management data TBL and extracting the work management data record to be modified; recording the obtained corrected work start time and / or the work end time in the extracted work management data record; The work management method according to claim 1 , further comprising the steps of:

3. A work management program for causing one or more computers to execute the work management method according to claim 1 or 2.

4. A work management computer comprising one or more computers that execute the work management program according to claim 3.

5. A work management system comprising the work management computer according to claim 4.

6. A database server computer used in a work management system that records the work start time and work end time of a worker who may work two or more times a day with time not managed by the workplace in between, The database server computer includes: Each time information including the worker's ID, date, and start time of work is received via the network, a process of generating and recording a work management data record corresponding to the ID and including at least the date and start time of work in the work management data TBL of the database; Each time information including the ID, date, and end time of work notifying the worker of the end of work is received via the network, a process of searching for a work management data record corresponding to the ID in the work management data TBL and extracting a work management data record in which the most recent work start time is recorded; recording the received end time in the extracted time management data record; The database server computer that runs

7. The database server computer further comprises: Upon receiving information via a network notifying that the work start time and / or the work end time have been modified, the information includes the modified work start time and / or the work end time, and identification information of the work management data record to be modified, searching the work management data TBL and extracting the work management data record to be modified; recording the received corrected work start time and / or the corrected work finish time in the extracted work management data record; 7. The database server computer of claim 6, which executes:

8. A work management system comprising the database server computer according to claim 6 or 7.

Images