Information processing systems, information processing methods, and programs

Abstract

We provide an information processing system that allows for greater flexibility in inputting man-hours for man-hour management. [Solution] According to one aspect of the present invention, an information processing system is provided which includes one or more processors, wherein in a display step, the processor displays input fields for inputting man-hour information indicating the man-hours of one or more projects, the input fields include a ratio input field for inputting man-hours as a percentage of the working hours of a first period, and a time input field for inputting man-hours in the first period in units of hours, and in an output step, the processor is capable of outputting a total man-hour for a second period including multiple periods, which is the sum of the man-hours indicated by the man-hour information entered in the ratio input field and the man-hour information indicated by the man-hour information entered in the time input field, as the man-hours for the second period of the project.

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing method, and a program.

Background Art

[0002] Patent Document 1 discloses a technique for determining the man-hour of a worker's work using the worker's schedule information, obtaining the working hours of the worker, and changing the man-hour so that the man-hour and the working hours are consistent.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Conventionally, man-hour management of workers has been performed for cost management of projects and the like, and the time operated for man-hour management has been input as man-hour information, but the degree of freedom of input has been low.

[0005] In view of the above circumstances, the present invention aims to provide an information processing system and the like that can increase the degree of freedom of input of man-hours for man-hour management.

Means for Solving the Problems

[0006] According to one aspect of the present invention, an information processing system is provided comprising one or more processors, wherein in a display step, the processor displays input fields for inputting man-hour information indicating the man-hours of one or more projects, the input fields include a ratio input field for inputting man-hours as a percentage of the working hours of a first period, and a time input field for inputting man-hours in the first period in units of hours, and in an output step, the processor is capable of outputting a total man-hour for a second period comprising multiple periods, obtained by summing the man-hours indicated by the man-hour information entered in the ratio input field and the man-hour information indicated by the man-hour information entered in the time input field, as the man-hours for the second period of the project.

[0007] This configuration allows for greater flexibility in inputting man-hours for man-hour management. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the overall configuration of the man-hour management system 1. [Figure 2] This figure shows an example of the hardware configuration of the man-hour management server 10. [Figure 3] This figure shows an example of the hardware configuration of user terminal 30. [Figure 4] This is an activity diagram showing an example of the effort input process. [Figure 5] This figure shows an example of a work time input screen. [Figure 6] This figure shows an example of a work time input screen during data entry. [Figure 7] This figure shows an example of how to revise the man-hours. [Figure 8] This figure shows an example of images for batch editing. [Figure 9] This figure shows an example of a screen for entering man-hours in bulk. [Figure 10] This figure shows an example of the man-hour DB3. [Modes for carrying out the invention]

[0009] Embodiments of the present invention will be described below with reference to the drawings. The various features shown in the embodiments below can be combined with each other.

[0010] Incidentally, the program for implementing the software appearing in one embodiment may be provided as a non-transitory computer-readable medium, or it may be provided as a downloadable medium from an external server, or it may be provided so that the program is launched on an external computer and its functions are realized on a client terminal (so-called cloud computing).

[0011] Furthermore, in various information processing according to one embodiment, an input and an output corresponding to the input can be realized. Here, as long as an output is obtained as a result of the input, the form of the information referenced in such information processing (hereinafter referred to as "reference information") is not limited. The reference information may be, for example, rule-based information such as a database, a lookup table, or a predetermined function (including a decision formula such as a regression equation constructed by a statistical method), or a pre-trained model that has learned the correlation between input and output in advance, or a large-scale language model that can output a desired result by inputting a prompt.

[0012] Furthermore, in one embodiment, "part" may include, for example, hardware resources implemented by a circuit in a broad sense, and the information processing of software that can be specifically realized by these hardware resources. Also, in one embodiment, various types of information are handled, and this information can be represented, for example, by the physical values ​​of signal values ​​representing voltage and current, the high or low values ​​of signal values ​​as a set of binary bits composed of 0s or 1s, or by quantum superposition (so-called qubits), and communication and calculations can be performed on a circuit in a broad sense.

[0013] Furthermore, a circuit in a broad sense is a circuit realized by appropriately combining at least a circuit, circuitry, a processor, a memory, etc. The processor may be a general-purpose processor or a dedicated circuit. That is, it includes an application specific integrated circuit (ASIC), a programmable logic device (for example, a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)), etc.

[0014] <Embodiment> 1. System Configuration Hereinafter, the system configuration according to the embodiment will be described. FIG. 1 is a diagram showing an example of the overall configuration of the man-hour management system 1. In FIG. 1, each device included in the man-hour management system 1 and an outline of users who use those devices are shown. Each outline will be described as needed while referring to other figures.

[0015] The man-hour management system 1 includes a communication line 2, a man-hour management server 10, an attendance management server 20, and a user terminal 30. The communication line 2 is not particularly limited, but for example, it is constituted by the Internet network. Also, the communication line 2 may include a local area network, a mobile communication network, a virtual private network (VPN), etc. The communication line 2 mediates the exchange of data between devices connected to its own line. In the example of FIG. 1, the man-hour management server 10 and the attendance management server 20 are wired-connected to the communication line 2, and the user terminal 30 is wirelessly connected. Note that the connection of each device to the communication line 2 may be wired or wireless.

[0016] The man-hour management system 1 is a system that manages the amount of work performed by workers in a project or the like, that is, the man-hours. The man-hour management server 10 executes various information processes related to man-hour management. The attendance management server 20 executes various information processes related to the attendance management of workers. The user terminal 30 has display means and input means and functions as a UI (User Interface) for operations by users related to man-hour management. The user terminal 30 is, for example, a notebook computer or the like, and is mainly used by users who perform operations related to the man-hour management of contractors. This user is basically the worker himself, but in some cases, for example, an administrator or the like may input the man-hours on behalf of the worker.

[0017] The man-hour management server 10 executes an authentication process for authenticating users who use the man-hour management system 1 and a display process for causing the user terminal 30 to display an image. The man-hour management server 10 stores authentication information (such as user ID and password) for authenticating users, and authenticates the user who inputs the authentication information as a user of the man-hour management system 1. By authenticating the user, the man-hour management server 10 determines the data that the user can access, or assigns identification information to the data input by the user to make it identifiable.

[0018] The man-hour management server 10 performs, as display processing, processes such as generation and transmission of an HTML (Hyper Text Markup Language) file, generates a web page showing the system screen, and causes the generated system screen to be displayed on the user terminal 30 using the function of a browser. Note that an application program for the user terminal 30 to use the man-hour management system 1 may be introduced, and the man-hour management server 10 may generate and display a system screen that can be displayed by the application. By performing these display processes, the man-hour management server 10 controls the display of the user terminal 30.

[0019] The work time management server 10 stores the work time DB3 (database). The work time DB3 stores information about the worker's work time, such as the date the work was performed and the amount of work performed. The attendance management server 20 stores the attendance DB4. The attendance DB4 stores information about the worker's attendance, such as the date the worker worked and the amount of work performed each day.

[0020] The work time management system 1 is used, for example, when a user enters work time. Work time can be entered at any time; it can be entered daily or all at once for the month. The work time management server 10 displays a system screen G1 for entering work time on the user terminal 30. The system screen G1 displays a work time display field C16 that shows the worker's working hours. The work time management server 10 retrieves the worker's working hours from the attendance management server 20 and displays them in the work time display field C16.

[0021] The effort management server 10 displays an effort input field D1 for entering effort hours. The effort input field D1 includes a percentage input field for entering effort hours as a percentage and a time input field for entering effort hours as time. Workers can enter their daily effort hours as a percentage in the percentage input field or as time in the time input field. The effort management server 10 sums the daily effort hours entered in the effort input field D1 and displays it in the effort display field C17. The effort management server 10 also displays the sum of the effort hours displayed in the effort display field C17 as the total effort hours for the current month in the current month total display field C20. In this way, the effort management system 1 allows users to enter effort hours as a percentage or as time.

[0022] 2. Hardware Configuration The hardware configuration according to this embodiment will be described below. Figure 2 shows an example of the hardware configuration of the time management server 10. The time management server 10 comprises a control unit 101, a storage unit 102, a communication unit 103, and a bus 104. The bus 104 electrically connects each part of the time management server 10.

[0023] (Control Unit 101) The control unit 101 has at least one processor. The at least one processor may consist of, for example, a central processing unit (CPU), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), one or more integrated circuits, one or more discrete circuits, or a combination thereof.

[0024] The control unit 101 is a computer that realizes various functions related to the man-hour management system 1 by reading predetermined programs stored in the memory unit 102. In other words, information processing by software stored in the memory unit 102 is concretely realized by the control unit 101, which is an example of hardware, and can be executed as each functional unit included in the control unit 101. Note that the control unit 101 is not limited to being a single unit, and may be implemented with multiple control units 101 for each function, or a combination thereof.

[0025] (Storage unit 102) The storage unit 102 stores various types of information as defined above. This can be done, for example, as a storage device such as a solid-state drive (SSD) or hard disk drive (HDD) that stores various programs related to the man-hour management system 1 executed by the control unit 101, or as memory such as random access memory (RAM) that stores temporarily necessary information (arguments, arrays, etc.) related to program calculations. The storage unit 102 stores various programs and variables related to the man-hour management system 1 executed by the control unit 101.

[0026] (Communications Department 103) The communication unit 103 is composed of a communication module. The communication module may be a wireless communication module compliant with standards such as IEEE 802.11a / b / g / n / ac / ax, LTE, 5G, 6G, or a wired communication module compliant with standards such as IEEE 802.3. The communication unit 103 is configured to transmit various electrical signals from the time management server 10 to external components. The communication unit 103 is also configured to receive various electrical signals from external components to the time management server 10. More preferably, the communication unit 103 has a network communication function, thereby enabling the communication of various information between the time management server 10 and external devices via the communication line 2.

[0027] The attendance management server 20 has the same hardware configuration as the work time management server 10. For the attendance management server 20, only the control unit 201 will be described using a different reference numeral than the control unit 101 of the work time management server 10.

[0028] Figure 3 shows an example of the hardware configuration of a user terminal 30. The user terminal 30 comprises a control unit 301, a storage unit 302, a communication unit 303, an input unit 304, an output unit 305, and a bus 306. The bus 306 electrically connects each part of the user terminal 30. The control unit 301, storage unit 302, and communication unit 303 are similar hardware to the control unit 101, storage unit 102, and communication unit 103 shown in Figure 3, although their specifications and models may differ.

[0029] (Input section 304) The input unit 304 has input receiving means such as keys, buttons, touchscreens, and mice, and accepts input from the user. The input unit 304 may also have sound receiving means such as a microphone, and may have a function to collect the user's voice and accept the input of the collected voice.

[0030] (Output section 305) The output unit 305 has display means such as a display and sound emission means such as a speaker, and outputs visual information and auditory information. For example, the output unit 305 displays visual information such as screens, images, icons, and text on the display surface of the display unit in a manner that is visible to the user. The output unit 305 also outputs audible sound such as speech or synthesized sound from the speaker.

[0031] 3. Information Processing The following describes the information processing according to the embodiment. In the following description, the man-hour management server 10, the attendance management server 20, and the user terminal 30 are described as the main entities of each information processing, but these information processing are executed by at least one processor provided in the man-hour management system 1, that is, the processor in the control unit of each device. The man-hour management system 1 executes man-hour input processing to allow the user to input man-hours.

[0032] Figure 4 is an activity diagram showing an example of the work time input process. The work time input process is initiated, for example, when a user logs into the work time management system 1 and displays the work time input screen. First, the work time management server 10 requests attendance information of the logged-in user (worker) from the attendance management server 20 (Activity A11). Specifically, the work time management server 10 requests the worker's working hours, attendance category, and attendance-related application information (such as leave requests) as attendance information.

[0033] The attendance management server 20 reads the requested worker's attendance information from the attendance DB4 (Activity A12) and sends the read attendance information to the effort management server 10. The effort management server 10 acquires the received attendance information (Activity A13). Next, the effort management server 10 reads the worker's entered effort from the effort DB3 (Activity A14). The effort DB3 and other related systems will be explained in detail after effort is entered, so here we will explain assuming there is no effort to read. Subsequently, the effort management server 10 generates an effort input screen using the acquired attendance information (Activity A15) and displays the generated effort input screen on the user terminal 30 (Activity A16).

[0034] Figure 5 shows an example of a work time input screen. The system screen G1 shown in Figure 5 displays a period display field C11 and a synchronization display field C12. The period display field C11 displays the period during which the worker performed the work, and in the example in Figure 5, "XX month" is displayed. Work time input can be done in the middle of a month, but in the example in Figure 5, it is assumed that it was done at the end of "XX month" and into the next month. The synchronization display field C12 displays the date and time synchronized with the attendance system, and in the example in Figure 5, the date and time when attendance information was acquired in A13 is displayed as the synchronization date and time.

[0035] Furthermore, system screen G1 displays the following fields: date display field C13, category display field C14, application display field C15, working hours display field C16, man-hour display field C17, percentage display field C18, difference display field C19, current month total display field C20, and man-hour input field D1. The date display field C13 displays the date of the target month for which man-hours are to be entered. The category display field C14 displays the attendance category for each date. Attendance categories are classifications that represent work patterns or statuses, and include, for example, weekday work and holiday work.

[0036] The application display field C15 shows the status of attendance-related applications. Applications include, for example, full leave, half leave, and working on holidays. The work hour management server 10 displays the attendance-related application information indicated by the attendance information acquired in A13. The working hours display field C16 shows the worker's working hours for the current month, broken down by day. The work hour management server 10 displays the working hours indicated by the attendance information acquired in A13. In the example in Figure 5, since "XX month" has ended, working hours are displayed for all days the user was at work.

[0037] The current month total display field C20 displays the sum of the values ​​for each item for the current month. The items for which the total is displayed are working hours, man-hours, percentage, difference, and entered man-hours. The man-hour management server 10, for example, displays the total working hours for the current month (162:30 in the example in Figure 5) in the current month total display field C20 for working hours. Note that in the example in Figure 5, it is assumed that no man-hours have been entered in the man-hour input field D1 yet. Therefore, for example, the current month total display field C20 for "man-hours" is "0:00".

[0038] The work time display field C17 shows the worker's work time for the current month, broken down by day. The work time displayed in the work time display field C17 is the sum of the work time entered in the work time input field D1. The percentage display field C18 shows the ratio of work time to working hours. The difference display field C19 shows the difference between working hours and work time. In the example in Figure 5, since no work time has been entered yet, the work time is "0:00", the percentage is "0.0%", and the difference is the same as the working hours for all days.

[0039] In the effort input field D1, an effort input field is displayed for each project the user is participating in. In the example in Figure 5, the user is participating in three projects: "PRJ1", "PRJ2", and "PRJ3", and for each of these, percentage input fields D11, D12, and D13 (hereinafter referred to as "percentage input field D10" when they are not distinguished) and time input fields D21, D22, and D23 (hereinafter referred to as "time input field D20" when they are not distinguished) are displayed.

[0040] The work hour management server 10 displays the percentage input field D10 and the time input field D20 only for days when working hours are displayed, i.e., days when the user was at work. Similarly, the work hour management server 10 also displays the working hours display field C16, the work hour display field C17, the percentage display field C18, and the difference display field C19 only for days when the user was at work.

[0041] On days when a user is not at work, the "Add Work Time" button B11 is displayed. When the "Add Work Time" button B11 is pressed, the work time management server 10 displays the work time display field C16, the percentage input field D10, and the time input field D20, corresponding to the day. If a user is at work but their work time is not displayed, they can press the "Add Work Time" button B11 to enable work time input.

[0042] The user enters the work hours for the day they are at work in either the percentage input field D10 or the time input field D20. When the user terminal 30 receives work hour input in either the percentage input field D10 or the time input field D20 for any project on any day of any month displayed (Activity A21), it sends the entered work hours, date, and work hour information indicating the project to the work hour management server 10. The entered work hours are shown as a percentage value if entered in the percentage input field D10, and as hours and minutes if entered in the time input field D20 (for example, if "5:51" is entered, it means a value of 5 hours + 51 minutes = 351 minutes). Hereafter, work hours expressed as a percentage will be referred to as "percentage work hours," and work hours expressed as hours will be referred to as "hourly work hours."

[0043] When the effort management server 10 receives effort information, it calculates the effort to be displayed in the other input field for the same project on the same day, based on the effort indicated by the received effort information, that is, the effort entered in one input field (Activity A22). If the effort information indicates a percentage effort, the effort management server 10 calculates the time effort to be displayed in the other input field by multiplying the day's working hours by the percentage effort. Also, if the effort information indicates a time effort, the effort management server 10 calculates the percentage effort to be displayed in the other input field by dividing that time effort by the day's working hours.

[0044] For example, if a percentage effort of "60.0%" is entered in the percentage input field D10 for "PRJ1" on "2 (Month)" as shown in Figure 5, the effort management server 10 calculates "5:51" (351 minutes) as the time effort to be displayed in the time input field D20, by multiplying 60% of the working time of "9:45" (585 minutes). Conversely, if a time effort of "5:51" is entered in the time input field D20 for "PRJ1", the effort management server 10 calculates "60.0%" as the percentage effort to be displayed in the percentage input field D10, by dividing the time effort of "5:51" (351 minutes) by the working time of "9:45" (585 minutes), expressed as a percentage. The calculation of fractional amounts will be explained in detail later.

[0045] Next, the effort management server 10 calculates the total effort for the day in terms of percentage effort and hourly effort (Activity A23). If all projects for the day are entered using percentage effort, the effort management server 10 sums those percentage effort values. If all projects are entered using hourly effort, it sums those hourly effort values. If each project for the day has a mix of percentage effort and hourly effort, the effort management server 10 sums the entered percentage effort values ​​and the percentage effort values ​​calculated in A22, and then sums the entered hourly effort values ​​and the hourly effort values ​​calculated in A22.

[0046] Next, the effort management server 10 calculates the difference between the day's working hours and the total effort (activity A24). The effort management server 10 calculates the difference for the day by subtracting the day's working hours, which are displayed in the working hours display field C16, from the total day's time and effort calculated in A23. For example, if the day's working hours are "8:00" and the day's total time and effort are "0:00", the effort management server 10 calculates the difference for the day as "-8:00".

[0047] Next, the effort management server 10 calculates the total effort for the month and the ratio of the total effort to the working hours for the month (Activity A25). First, for each project, the effort management server 10 calculates the total effort for the month by summing the entered time effort and the calculated time effort. Then, for each project, the effort management server 10 calculates the ratio of the total effort to the working hours for the month by dividing the total effort for the month by the total working hours for the month.

[0048] Furthermore, the effort management server 10 calculates the total effort for all projects for the month by summing the total effort for each project for the current month (the time effort displayed in the total monthly display column C20 for each project). In addition, the effort management server 10 calculates the ratio of the total effort to the working hours for all projects for the current month by summing the percentage of effort for each project for the current month (the percentage of effort displayed in the total monthly display column C20 for each project).

[0049] Next, the effort management server 10 calculates the difference between the working hours and effort for the current month (Activity A26). The effort management server 10 calculates the difference for the current month by subtracting the total effort for all projects for the current month, calculated in A25, from the total working hours for the current month, which are displayed in the working hours display field C16. Then, the effort management server 10 reflects each of the calculated values ​​on the effort input screen (Activity A27), and displays the reflected effort input screen on the user terminal 30 (Activity A28). As steps A21 to A28 are repeatedly executed, effort is entered into each input field of the effort input field D1.

[0050] Figure 6 shows an example of the work hour input screen during data entry. In the example in Figure 6, work hours for the current month from the 2nd (Monday) to the 5th (Thursday) have been entered. From the 2nd (Monday) to the 4th (Wednesday), work hours have been entered in the percentage input field D10 for all projects. Specifically, for example, on the 2nd (Monday), the percentage work hours entered are "60.0%" for PRJ1, "25.0%" for PRJ2, and "15.0%" for PRJ3. The work hour management server 10 displays the input fields in which work hours have been entered by making the border lines thicker.

[0051] The time input field D20, which corresponds to the percentage input field D10, displays the time man-hours calculated by the man-hour management server 10. For example, for PRJ1, 2, and 3 on Monday the 2nd, the time man-hours displayed are "5:52", "2:26", and "1:28", corresponding to the percentage man-hours of "60.0%", "25.0%", and "15.0%", respectively. The man-hour management server 10 calculates the time man-hours for each of these projects from the working hours and percentage man-hours for the day.

[0052] The effort management server 10, in detail, converts the day's working hours into minutes, multiplies the converted working hours by the percentage effort, and rounds the result to the nearest whole number to calculate the effort time for each project. For example, in the case of Monday the 2nd, the effort management server 10 converts the working hours of "9:45" to 585 minutes, and calculates the effort time for PRJ1 as 585 minutes × 60.0% = 351.0 minutes = 351 minutes = "5:51". Similarly, for PRJ2, it calculates the effort time as 585 minutes × 25.0% = 146.25 minutes = 146 minutes = "2:26", and for PRJ3, it calculates the effort time as 585 minutes × 15.0% = 87.75 minutes = 88 minutes = "1:28".

[0053] In the case of Monday the 2nd, the total percentage effort entered for each project for the day is "60.0%" + "25.0%" + "15.0%" = "100.0%", and the total calculated hourly effort for the day is "351 minutes" + "146 minutes" + "88 minutes" = "585 minutes", which matches the working hours. On the other hand, because the calculation of hourly effort rounds to the nearest whole number, even if the total percentage effort is 100.0%, the calculated total hourly effort may not match the working hours.

[0054] For example, on Tuesday the 3rd, the effort management server 10 calculates the working time of "8:00" as 480 minutes, and calculates PRJ1 as 480 minutes × 58.0% = 278.4 minutes = 278 minutes = "4:38". Similarly, for PRJ2 it calculates 480 minutes × 29.0% = 139.2 minutes = 139 minutes = "2:19", and for PRJ3 it calculates 480 minutes × 13.0% = 62.4 minutes = 62 minutes = "1:02". In this case, the total of the calculated time and effort (278 minutes + 139 minutes + 62 minutes = 479 minutes) is 1 minute less than the working time of 480 minutes.

[0055] In the example above, the total effort was shorter, but sometimes the total effort becomes longer after rounding up the fractional parts. In such cases, where the sum of percentage effort is 100.0% but the sum of hourly effort does not match the working hours, the effort management server 10 adjusts for the fractional parts that occurred when calculating the hourly effort. Specifically, the effort management server 10 selects one of the projects according to a predetermined rule and adds or subtracts the difference between the total effort and working hours to the hourly effort of the selected project. For example, the effort management server 10 adds or subtracts the difference in one-minute increments, starting with the projects with the largest hourly effort.

[0056] In the example for Tuesday the 3rd, the time effort for PRJ1 is the largest at "4:38," so the effort management server 10 adjusts the time effort for PRJ1 by adding the difference of "1" minute to "4:38" to make it "4:39." As a result of this fractional adjustment, the effort displayed in the effort display field C17 becomes "8:00," the same as the working time, the percentage display field C18 displays "100.0%" and the difference display field C19 displays "0:00." If the effort is entered so that the sum of the percentage effort for all projects equals "100.0%", the time effort is calculated so that the fractional adjustment is made in this way and the difference is "0:00."

[0057] On the other hand, for Thursday the 5th, time and effort are entered in the time input field D20 for all projects. Specifically, PRJ1 has "5:30", PRJ2 has "2:00", and PRJ3 has "1:00". In this case, the total time and effort for each project is "8:30", and the working time is "9:00", so the percentage display field C18 shows "94.4%" and the difference display field C19 shows "-0:30" as the difference.

[0058] If the correct man-hours are not entered in this way, a discrepancy will arise between them and the actual working hours. In this case, the user will correct the man-hours so that the discrepancy becomes "0:00". In this case, the user will correct the total man-hours to match the actual working hours by, for example, consolidating the discrepancy of "-0:30" into one project or distributing it across multiple projects and adding it to each project. In the example for Thursday the 5th, adding "0:30" to the man-hours for PRJ1, which is "5:30", will correct it to "6:00", making the total man-hours match the actual working hours.

[0059] The effort management server 10 displays the total hourly effort for each project for the current month, and the percentage of that total relative to the total working hours for the current month, in the current month total display field C20. For example, for PRJ1, "21:51" is displayed as the total hourly effort for the current month, and "13.4%" is displayed as the percentage relative to the total working hours for the current month, "162:30". The effort management server 10 also displays the total effort, "36:00", which is the sum of the total hourly effort for all projects for the current month, and the total effort, "22.2%", which is the sum of the percentage effort for all projects for the current month. As shown in Figure 6, only "22.2%" of the effort for the current month has been entered so far.

[0060] Note that in the percentage input field D10 and the time input field D20, you can enter values ​​that exceed 100.0% of the total man-hours, resulting in the total man-hours being greater than the working hours. In that case, since man-hours exceeding 100.0% will be entered initially, a difference will occur, so you will need to correct each man-hour to make the difference "0:00". Also, man-hour corrections may be made even on days when the total man-hours percentage is already 100.0%, in order to correct the man-hours for each project.

[0061] Figure 7 shows an example of how man-hours can be revised. In the example in Figure 7, the total man-hours for Tuesday the 3rd are 100.0%, but the man-hours for each project have been revised. For example, the user has revised the percentage man-hours for PRJ2 from "29.0%" to "25.0%", the hourly man-hours for PRJ1 from "4:39" to "5:00", and the hourly man-hours for PRJ3 from "1:02" to "1:00".

[0062] Thus, man-hours entered as percentage man-hours may be corrected to hourly man-hours. Conversely, man-hours entered as hourly man-hours may be corrected to percentage man-hours. When the man-hour management server 10 receives hourly man-hours followed by percentage man-hours, or vice versa, for the same project and the same day, it adopts the man-hours entered later and discards the man-hours entered earlier.

[0063] In the example shown in Figure 7, the effort management server 10 discards the percentage effort of "58.0%" entered in the percentage input field D10 for PRJ1 on Tuesday the 3rd, and adopts the time effort of "5:00" that was entered. Specifically, the effort management server 10 displays the adopted "5:00" in the time input field D20, and at the same time displays the percentage effort of "62.5%" calculated from the adopted time effort in the percentage input field D10. At this time, the effort management server 10 restores the border of the percentage input field D10, where the effort was entered first, and displays the border of the time input field D20, where the effort was entered later, as a thick border. This makes it clear which effort was entered by the user.

[0064] Thus, it is acceptable for percentage-based and hourly effort to be mixed for each project on the same day (for example, PRJ1 and PRJ3 may use hourly effort, while PRJ2 may use percentage-based effort). Even in such cases, if the sum of the entered percentage-based effort and the percentage-based effort calculated from the entered hourly effort is 100.0%, and the sum of the hourly effort calculated from the entered percentage-based effort and the entered hourly effort does not match the working hours, the effort management server 10 will perform the same rounding adjustment as described above.

[0065] If time-based work hours are entered for one or more projects on the same day, the total time-based work hours for the day will match the working hours. However, the total percentage of work hours for the day may not equal 100.0% because the fractional parts of the calculated percentage work hours are rounded down or up. In that case, the work hour management server 10 will display the time hours displayed in the percentage input field D10 and the time input field D20—that is, the time hours entered and calculated for each project—as they are, but will only display the total percentage of work hours for the day as 100.0%. This is because the percentage work hours should equal 100.0% if calculated from the working hours and the total time-based work hours for the day.

[0066] The user terminal 30 accepts the user's operation to modify the man-hours as described above (Activity A31) and sends the modified man-hours information, including the modified man-hours, project, and date, to the man-hours management server 10. Upon receiving the modified man-hours information, the man-hours management server 10 performs the operations from A22 to A28, recalculates the total man-hours and differences after the modifications, and reflects them on the man-hours input screen.

[0067] As described above, manually entering each work hour one by one is quite time-consuming. Therefore, in the work hour management system 1, work hours can be entered in bulk by operating the bulk edit button B12 shown in Figure 5. First, the user checks the check box B13 corresponding to the date for which they want to enter work hours in bulk. At that time, by checking the bulk check box B14, all days for which working hours are displayed can be checked. Then, when the user operates the bulk edit button B12, the work hour management server 10 displays an image for bulk editing.

[0068] Figure 8 shows an example of an image for batch editing. In the example in Figure 8, the batch editing image G3 is displayed superimposed on the system screen G1. The batch editing image G3 displays the effort editing check box B31, the remarks editing check box B32, and the execute button B33. In the example in Figure 8, when the effort editing check box B31 is checked, the image for effort editing displays the percentage input field D31, the time input field D32, the delete button B34, and the add button B35.

[0069] The percentage input field D31 and the time input field D32 are displayed for each project the user is participating in. For each project, the user enters either the percentage effort or the time effort they wish to input in bulk. If there are projects that the user does not wish to input in bulk, they can delete the project by using the delete button B34, and they can add projects that they wish to input in bulk by using the add button B35.

[0070] When the remarks editing check box B32 is checked, the effort management server 10 displays a remarks input field for entering remarks in bulk. Remarks are, for example, input fields for comments about the entered effort. Although not shown in Figure 5, etc., it is assumed that it will be displayed to the right of the effort input field D1 by scrolling to the right.

[0071] Once the user has finished entering the man-hours and remarks to be entered in bulk, they operate the execute button B33. When the execute button B33 is operated, the man-hour management server 10 enters the entered man-hours and remarks into each input field on the man-hour input screen in bulk. Next, the man-hour management server 10 calculates the man-hours and differences for each date from A22 to A24, and then calculates the man-hours and differences for the current month in bulk from A25 to A26. Finally, the man-hour management server 10 reflects the calculated values ​​on the man-hour input screen in A27 and displays them on the user terminal 30 in A28.

[0072] Figure 9 shows an example of a screen for entering man-hours in bulk. In the system screen G1 shown in Figure 9, the percentage man-hours for PRJ1 are entered as "60%", for PRJ2 as "25%", and for PRJ3 as "15%". In this case, fractional adjustments are made for each date, so the sum of the differences for all dates becomes "0:00", and the sum of the differences for the current month also becomes "0:00". Users can modify the bulk-entered man-hours as needed. Also, by operating the bulk delete button B15, all man-hours for the date selected in check box B13 are deleted, and the man-hours can be re-entered.

[0073] Once the user has finished entering the man-hours, they operate the "Complete" button B16 displayed on the system screen G1. When the user terminal 30 receives the operation of the "Complete" button B16 as the completion operation for man-hour entry (Activity A32), it notifies the man-hour management server 10 that the man-hour entry has been completed. Upon receiving this completion notification, the man-hour management server 10 stores each man-hour entered on the man-hour entry screen in the man-hour DB3 (Activity A33).

[0074] Figure 10 shows an example of the Man-Hour DB3. The Man-Hour DB3 stores the "Worker ID," "Work Month," and "Work Day" in correspondence with the man-hour information for each project. The man-hour information stores the input type, percentage man-hours, and hourly man-hours. The input type indicates whether the input was percentage man-hours or hourly man-hours; if it was entered as percentage man-hours, the string "Percentage" is stored, and if it was entered as hourly man-hours, the string "Hours" is stored.

[0075] If the input type is "percentage," the percentage effort is stored in the effort input field, and the time effort is stored in the effort management server 10. If the input type is "time," the percentage effort is stored in the effort management server 10, and the time effort is stored in the time effort field. Of the time effort stored in the effort DB3 in this way, the time effort (both the input time effort and the calculated time effort) is used for cost accounting.

[0076] Users may enter attendance information while simultaneously entering work hours. For example, they might display the work hour input screen and begin entering work hours, but because they haven't entered the latest attendance information, several days' worth of work hours may not be displayed. As a result, even if they enter percentage work hours for those days, they may not be able to calculate the hourly work hours. In addition, there may be cases where the work hours entered as attendance information are incorrect and need to be corrected.

[0077] In those cases, first, the user terminal 30 accesses the attendance management server 20 via user operation to display the attendance information input screen (Activity A41) and accepts attendance information input from the user (Activity A42). This input may be new information or an input to modify existing attendance information. The user terminal 30 sends the entered attendance information to the attendance management server 20, and the attendance management server 20 stores the received attendance information in the attendance DB4 (Activity A43).

[0078] Next, the user operates the sync button B17 displayed on the system screen G1 shown in Figure 9. The user terminal 30 accepts this operation as a sync operation (Activity A44) and requests the time management server 10 to synchronize with the attendance system. Upon receiving the sync request, the time management server 10 requests the worker's attendance information from the attendance management server 20 (Activity A45). The attendance management server 20 reads the requested worker's attendance information from the attendance DB4 (Activity A46) and sends the read attendance information to the time management server 10.

[0079] The time management server 10 reflects the transmitted attendance information on the time input screen (Activity A47). Specifically, the time management server 10 displays the working hours and other information included in the transmitted attendance information on the time input screen (Activity A48). By synchronizing the attendance information in this way, users can input time based on newly entered working hours.

[0080] As described above, the effort management server 10 functions as an example of a display unit that displays input fields for inputting effort information indicating the effort of workers in one or more projects. The input fields include a percentage input field for inputting effort as a percentage of the working hours in the first period, and a time input field for inputting effort in the first period in units of hours. In the example in Figure 4, the period of "1 day" is an example of the "first period". Also, the percentage input field D10 shown in Figure 5 is an example of a percentage input field, and the time input field D20 is an example of a time input field.

[0081] Furthermore, the effort management server 10 functions as an example of an output unit capable of outputting the total effort for the second period of the project. The second period is a period that includes multiple individual periods. In the example shown in Figure 4, the period "January" is an example of the "second period". Specifically, the effort management server 10 (an example of an output unit) can output the total effort for the second period of the project, which is the sum of the effort indicated by the effort information entered in the percentage input field and the effort indicated by the effort information entered in the time input field.

[0082] In the example shown in Figure 9, the effort management server 10 outputs "60.0%" as the percentage effort and "97:30" as the total effort for the current month for "PRJ1". The effort management server 10 also outputs "25.0%" as the percentage effort and "40:37" as the total effort for the current month for "PRJ2", and "15.0%" as the percentage effort and "24:22" as the total effort for the current month for "PRJ3".

[0083] With this configuration, since both percentage-based and hourly-based man-hours can be entered, the degree of flexibility in entering man-hours for man-hour management is increased compared to cases where only percentage-based or hourly-based man-hours can be entered. For example, if the work time can be remembered or confirmed by a schedule, accurate man-hours can be entered by entering hourly-based man-hours, and even if the work time is unclear, a rough estimate can be easily entered by entering percentage-based man-hours.

[0084] Furthermore, the effort management server 10 (an example of the display unit) displays a percentage input field and a time input field for each project if the user is participating in two or more projects. In the example in Figure 5, the percentage input field D10 and the time input field D20 are displayed for each of the three projects, PRJ1, PRJ2, and PRJ3. The effort management server 10 (an example of the output unit) then outputs the total effort for each project. In the example in Figure 9, the total effort for the current month for PRJ1, PRJ2, and PRJ3, "97:30", "40:37", and "24:22", are displayed in the current month total display field C20, respectively. With this configuration, effort can be managed for each project.

[0085] Furthermore, the effort management server 10 (an example of an output unit) sums the effort entered in one of the input fields, the percentage input field and the time input field, for the same project in the first period, but does not sum the effort entered in the other input field. For example, as described above, if effort is entered in one of the effort fields, either the percentage effort or the time effort, before the other effort is entered, the effort management server 10 uses the effort entered later (i.e., "the other effort") to calculate the total effort, and discards the effort entered earlier (i.e., "the one effort") and does not use it to calculate the total effort.

[0086] This configuration prevents inconsistencies from occurring when different percentage-based and hourly man-hours are entered for the same project and period. The man-hour management server 10 may also prevent the input of the other man-hour if either the percentage-based or hourly man-hour has been entered. In this case, inconsistencies can also be prevented. However, this would be inconvenient as only the man-hour that has been entered once can be entered, so the man-hour management server 10 may, for example, allow the input of the other man-hour if the entered man-hour is deleted after the other man-hour has been entered.

[0087] Furthermore, when an amount of work is entered into one of the input fields, either the percentage input field or the time input field, the work time management server 10 displays the entered amount of work and displays a value representing that entered amount of work in the other input field. For example, when an amount of work is entered into the percentage input field D10, the work time management server 10 displays the entered percentage amount of work and displays the same amount of time in the corresponding time input field D20. Also, for example, when an amount of time is entered into the time input field D20, the work time management server 10 displays the entered time amount and displays the same amount of time in the corresponding percentage input field D10.

[0088] For example, in the case of Monday 2 as shown in Figure 6, if a percentage effort of "25.0%" is entered, the same effort is displayed as an hourly effort of "2:26". Similarly, in the case of Thursday 5, if an hourly effort of "2:00" is entered, the same effort is displayed as a percentage effort of "22.2%". With this configuration, whether effort is entered as a percentage or as an hourly effort, both effort values ​​can be displayed.

[0089] Furthermore, the effort management server 10 (an example of a display unit) displays a history image indicating whether the effort was entered by the user in the percentage input field or the time input field. In the example shown in Figure 6, for example, the effort management server 10 displays the border of the input field, shown by the thick line, as the history image. Note that the history image is not limited to the border image. For example, an input field with a different border color, line type, or background color may be used as the history image. Also, text with a different color, size, font, etc. (for example, gray text) may be used as the history image. As shown in Figure 10, the effort management server 10 can display a history image even for effort entered in the past by storing the input type in the effort DB3. With this configuration, it is possible to later determine whether the effort was entered as a percentage or as time.

[0090] Furthermore, if the effort management server 10 (an example of an output unit) receives effort information for two or more projects in the first period, such that the sum of the percentages equals 100%, it adjusts the fractional part of the effort time calculated from those percentages to match the working hours for the first period. For example, in the case of example 3 (Tuesday) shown in Figure 6, there is a difference of 1 minute between the sum of the time effort calculated from each percentage effort and the working hours, so the effort management server 10 adds this difference to the time effort calculated from the percentage effort of PRJ1 to adjust the fraction. With this configuration, the total effort for two or more projects in the first period can be made accurate.

[0091] Furthermore, the effort management server 10 (an example of a display unit) displays a batch input field for entering percentages for the second period of the same project all at once. For example, the effort management server 10 displays a percentage input field D31, which is an example of a batch input field, in the batch editing image G3 shown in Figure 8. The effort management server 10 (an example of a display unit) then displays the percentages entered in the batch input field in the selected percentage input field for the second period.

[0092] The man-hour management server 10, for example, inputs the percentage man-hours entered into the batch editing image G3 in a batch, as shown in Figure 9. This configuration reduces the effort required to input man-hours as a percentage compared to manually entering them into each percentage input field. Furthermore, after batch input, the percentage man-hours can be corrected or re-entered as time man-hours as needed to obtain more accurate man-hours.

[0093] The effort management server 10 displays a batch input field for entering all the time to be entered in the time input fields for the second period of the same project at once. For example, the effort management server 10 displays a time input field D32, which is an example of a batch input field, in the batch editing image G3 shown in Figure 8. The effort management server 10 (an example of a display unit) then displays the time entered in the batch input field in the selected time input field among the time input fields for the second period. This configuration reduces the effort required to enter effort by time compared to manually entering time into each time input field.

[0094] Furthermore, the time management server 10 functions as an example of an acquisition unit that acquires attendance information, including the user's working hours for the first period, from the attendance system that manages the user's attendance. For example, in A11 to A13 shown in Figure 4, the time management server 10 acquires attendance information, including the user's working hours, from the attendance management server 20. The attendance management server 20 is an example of a device that constitutes the user's attendance system. With this configuration, the effort of manually entering the working hours for the first period can be eliminated.

[0095] Furthermore, the time management server 10 functions as an example of a synchronization unit that synchronizes attendance information with the attendance system when a user performs a synchronization operation. For example, in A44 to A48 shown in Figure 4, the time management server 10 synchronizes the user's attendance information with the attendance management server 20 through a user's synchronization operation. The operation of the synchronization button B17 shown in Figure 9 is an example of a synchronization operation. With this configuration, the user can immediately reflect the entered attendance information on the time input screen and input time based on the reflected attendance information (especially working hours).

[0096] Furthermore, the effort management server 10 (an example of a display unit) displays the difference between the working hours for the first period indicated by the acquired attendance information and the total effort hours indicated by the effort information entered in the percentage input field and time input field for each project during the first period. For example, in the effort input for Thursday 5 shown in Figure 6, the effort management server 10 displays "9:00" in the working hours display field C16 as the working hours indicated by the acquired attendance information, and displays "8:30", which is the total effort hours entered for each project, and "-0:30", which is the difference between that and the working hours, in the difference display field C19. In this case, it is shown that there is a difference of minus 30 minutes for Thursday 5.

[0097] Furthermore, the effort management server 10 (an example of a display unit) displays the difference between the total working hours for the second period indicated by the acquired attendance information and the total effort hours indicated by the effort information entered in the percentage input field and the time input field during the second period. For example, in the effort input shown in Figure 9, the effort management server 10 displays "162:30" in the current month total display field C20 as the total working hours indicated by the acquired attendance information, and displays "0:00" in the current month total display field C20 as the difference between that total working hours and the total effort hours for the second period entered for each project, which is "162:30". In this case, it is shown that the effort hours have been entered so that there is no difference for month XX.

[0098] In this configuration, compared to when the above difference is not displayed, it is easier to grasp the difference between the working hours managed by the attendance system and the entered man-hours. To resolve the difference thus identified (to "0:00"), the user modifies the man-hours for each project on the day in question. If it is percentage man-hours, the user simply needs to adjust the total percentage man-hours for the day so that it equals 100.0%. If it is hourly man-hours, the user simply needs to allocate the time required to eliminate the difference to the hourly man-hours of each project and add or subtract accordingly.

[0099] <Example: Adjustment of working hours> In the example above, when a discrepancy occurred, the man-hours entered by the user were corrected. However, there are cases where the man-hours entered by the user are correct, and the working hours shown in the attendance information are incorrect. In such cases, as shown in the example in Figure 4, the attendance management server 20 was accessed to update the attendance information before the synchronization process was performed. However, for such cases, the man-hour management server 10 may display the working hours in an editable format in the working hours display field C16.

[0100] When the working hours displayed in the working hours display field C16 are corrected, the man-hour management server 10 recalculates the percentage displayed in the percentage display field C18, the difference displayed in the difference display field C19, the hourly man-hours for projects where percentage man-hours are entered, the percentage man-hours for projects where hourly man-hours are entered, and the total displayed in the current month total display field C20, using the corrected working hours. In addition, when the synchronization button B17 shown in Figure 9 is operated, the man-hour management server 10 synchronizes the corrected working hours with the attendance information of the attendance system. With this configuration, even if the acquired working hours are incorrect, the working hours in the attendance system can be corrected simply by operating on the man-hour input screen.

[0101] <Variation example: Timing of acquiring attendance information> In the example above, the time management server 10 acquired attendance information at the time the time input screen was displayed, but the timing of acquiring attendance information is not limited to this. The time management server 10 (an example of the acquisition unit) may also acquire attendance information each time the user's attendance information is updated, at a timing corresponding to that update.

[0102] The attendance management server 20 updates attendance information through batch processing, for example, at night or early in the morning each day. In this case, the work time management server 10 requests attendance information from the attendance management server 20, for example, after the batch processing is completed. The attendance management server 20 sends the requested attendance information to the work time management server 10. The work time management server 10 retrieves the received attendance information. By the work time management server 10 immediately retrieving the updated attendance information in this way, for example, if there is a user who enters work time every day, the latest working hours will always be displayed on the work time entry screen, and the effort of entering working hours for the first period can be routinely eliminated.

[0103] <Variation example: Input restriction> The effort management server 10 may restrict the input of effort into the effort input fields. For example, if the effort management server 10 attempts to input effort that would cause the total effort for each project in the first period to exceed the working hours, it may control the input to prevent completion. For example, if a user enters a percentage effort exceeding 100% into the percentage input field D10, the effort management server 10 displays the message "Effort exceeds 100%" and controls the input state of that percentage input field D10 not to be cleared. Then, when a percentage effort is entered that brings the total percentage effort for the first period to 100% or less, the effort management server 10 clears the input state of that percentage input field D10, making it possible to input into other effort input fields. This configuration makes it possible to notice errors in the entered effort.

[0104] The effort management server 10 restricts input if time-based effort is entered and the total effort for the day exceeds the working hours. However, even in such cases, the time-based effort entered by the user may be more accurate (for example, when entering while checking the schedule), so the effort management server 10 may not restrict input for time-based effort even if the total effort for the day exceeds the working hours.

[0105] <Variation example: Man-hour input screen> The labor time input screen shown in Figure 5, etc., is just an example and is not limited to this. For example, the category display field C14, application display field C15, working hours display field C16, labor time display field C17, percentage display field C18, difference display field C19, and current month total display field C20 do not always need to be fully displayed; the items displayed may vary as needed, or they may be made available to toggle between being displayed and hidden.

[0106] <Example of variation: Variations in configuration> The configuration shown in Figure 1, etc. (overall configuration, hardware configuration, and functional configuration, etc.) is just an example, and other configurations can be used as long as they do not cause inconvenience in implementation. For example, the man-hour management server 10 and the attendance management server 20 may each be distributed across two or more devices, and may also be provided in the form of SaaS (Software as a Service) or a cloud computing system.

[0107] Furthermore, the time management server 10 and the attendance management server 20 may be integrated into a single server. Also, the user terminal 30 may execute the processes that the time management server 10 and the attendance management server 20 would normally perform, or the time management server 10 and the attendance management server 20 may execute the processes that the user terminal 30 would normally perform. In short, as long as the necessary information processing is performed throughout the time management system 1, the devices that perform that information processing are not limited.

[0108] The output destination for information or data (hereinafter referred to as "information, etc.") may be other devices, displays, storage units (including built-in and external storage units), email addresses, or accounts in other systems. Acquisition of information, etc. includes not only acquiring information, etc. transmitted from other devices, but also acquiring information, etc. generated by the device itself or information, etc. stored by the device itself. The database may be stored by an information processing device such as the man-hour management server 10, or it may be stored on an external device. Furthermore, the information stored in the database may be used in a manner that temporarily stores it in memory.

[0109] The embodiments described above included information processing devices such as a man-hour management server 10, an attendance management server 20, and a user terminal 30, or an information processing system such as a man-hour management system 1 equipped with these information processing devices. However, it may also be an information processing method. The information processing method comprises steps executed by one or more processors in the information processing system. Furthermore, the embodiments described above may also be a program. The program causes a computer to execute the same steps as those executed by the information processing system.

[0110] <Note> Furthermore, they may be provided in the following embodiments.

[0111] (1) An information processing system comprising one or more processors, wherein in a display step, the processor displays an input field for inputting man-hour information indicating the man-hours of one or more projects, the input field includes a ratio input field for inputting the man-hours as a percentage of the working hours of a first period, and a time input field for inputting the man-hours in the first period in units of hours, and in an output step, the processor is capable of outputting a total man-hour for a second period comprising multiple first periods, which is the sum of the man-hours indicated by the man-hour information entered in the ratio input field and the man-hours indicated by the man-hour information entered in the time input field, as the man-hours for the second period of the project.

[0112] This configuration allows for greater flexibility in inputting man-hours for man-hour management.

[0113] (2) An information processing system as described in (1) above, wherein in the display step, the processor displays the percentage input field and the time input field for each project if the project is two or more projects, and in the output step, the processor outputs the total man-hours for each project.

[0114] In this configuration, man-hours can be managed for each project.

[0115] (3) An information processing system according to (1) or (2) above, wherein in the output step, the processor sums the man-hours entered in one of the input fields, the percentage input field and the time input field, for the same project in the first period, but does not sum the man-hours entered in the other input field.

[0116] This configuration prevents inconsistencies from occurring when different time and proportion values ​​for man-hours are entered for the same period.

[0117] (4) An information processing system according to any one of (1) to (3) above, wherein in the display step, the processor displays the man-hours entered in one of the input fields, the ratio input field and the time input field, and displays a value indicating the entered man-hours in the other input field.

[0118] In this configuration, both values ​​can be displayed regardless of whether the input is a percentage or time.

[0119] (5) An information processing system as described in (4) above, wherein in the display step, the processor displays a history image indicating which of the percentage input field and the time input field the man-hours were entered into.

[0120] This configuration makes it possible to later determine whether the input was in terms of percentage or time.

[0121] (6) An information processing system according to any one of (1) to (5) above, wherein in the output step, the processor, when inputting man-hour information for two or more projects in the first period such that the sum of the ratios equals 100%, adjusts the fraction of the man-hour time calculated from the ratios to match the working hours of the first period.

[0122] This configuration allows for the accurate calculation of the total man-hours for two or more projects in the first period.

[0123] (7) An information processing system according to any one of (1) to (6) above, wherein in the display step, the processor displays a batch input field for inputting the percentages to be entered in the percentage input field for the second period of the same project all at once, and displays the percentages entered in the batch input field in the percentage input field selected from the second period.

[0124] This configuration reduces the effort required when inputting man-hours as a percentage.

[0125] (8) An information processing system described in any one of (1) to (7) above, wherein in the acquisition step, the processor acquires attendance information, including the working hours of the user for the first period, from a system that manages the attendance of the user.

[0126] This configuration eliminates the need to manually input working hours for the first period.

[0127] (9) An information processing system as described in (8) above, wherein in the acquisition step, the processor acquires the attendance information each time the user's attendance information is updated, at a timing corresponding to the update.

[0128] This configuration eliminates the need to manually input working hours for the first period on a regular basis.

[0129] (10) Information processing system as described in (8) above, wherein in the synchronization step, the processor synchronizes the system with the attendance information when the user performs a synchronization operation.

[0130] In this configuration, the entered attendance information can be reflected immediately.

[0131] (11) An information processing system as described in (8) above, wherein in the display step, the processor displays the difference between the working hours for the first period indicated by the acquired attendance information and the total man-hours indicated by the man-hour information entered in the percentage input field and the time input field during the first period.

[0132] In this configuration, the difference between working hours and the entered man-hours can be easily determined.

[0133] (12) An information processing method comprising each of the steps described in any one of (1) to (11) above, which is performed by a processor.

[0134] This configuration allows for greater flexibility in inputting man-hours for man-hour management.

[0135] (13) A program that causes a computer to perform any one of the steps described in (1) to (11) above.

[0136] This configuration allows for greater flexibility in inputting man-hours for man-hour management. Of course, this is not always the case. Furthermore, the embodiments and modifications described above may be implemented in any combination.

[0137] Finally, various embodiments of the present invention have been described, but these are presented as examples only and are not intended to limit the scope of the invention. Novel embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. Embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents. [Explanation of Symbols]

[0138] 1: Effort Management System 2: Communication lines 10: Effort Management Server 20: Attendance Management Server 30: User terminal 101: Control Unit 201: Control Unit 301: Control Unit C16: Working Hours Display Section C17: Man-hour display field C18: Percentage display field C19: Difference display field C20: Current month total display column D1: Man-hour input field D10: Percentage input field D20: Time input field

Claims

1. An information processing system comprising one or more processors, In the display step, the processor displays an input field for inputting effort information indicating the effort required for one or more projects. The input fields include a ratio input field for inputting the man-hours as a percentage of the working hours in the first period, and a time input field for inputting the man-hours in the first period in units of hours. In the output step, the processor outputs, for a second period including multiple periods, the total effort obtained by summing the effort indicated by the effort information entered in the ratio input field and the effort indicated by the effort information entered in the time input field, as the effort for the second period of the project. Information processing system.

2. In the information processing system described in claim 1, In the display step, if the project consists of two or more projects, the processor displays the percentage input field and the time input field for each project. In the output step, the processor outputs the total man-hours for each project. Information processing system.

3. In the information processing system described in claim 1, In the output step, the processor sums the man-hours entered in one of the input fields, the percentage input field and the time input field, for the same project during the first period, but does not sum the man-hours entered in the other input field. Information processing system.

4. In the information processing system described in claim 1, In the display step, if the processor receives an input for man-hours in either the percentage input field or the time input field, it displays the man-hours entered in that input field and displays a value indicating the entered man-hours in the other input field. Information processing system.

5. In the information processing system described in claim 4, In the display step, the processor displays a history image indicating which of the percentage input field and the time input field the man-hours were entered into. Information processing system.

6. In the information processing system described in claim 1, In the output step, if the processor receives input as man-hour information for two or more projects in the first period such that the sum of the percentages equals 100%, it adjusts the fractional part of the man-hour time calculated from the percentages to match the working hours of the first period. Information processing system.

7. In the information processing system described in claim 1, In the display step, the processor displays a batch input field for entering the percentages to be entered in the percentage input field for the second period of the same project all at once, and displays the percentages entered in the batch input field in the percentage input field selected from the second period. Information processing system.

8. In the information processing system described in claim 1, In the acquisition step, the processor acquires attendance information, including the user's working hours for the first period, from a system that manages the user's attendance. Information processing system.

9. In the information processing system described in claim 8, In the acquisition step, the processor acquires the attendance information each time the user's attendance information is updated, at a timing corresponding to the update. Information processing system.

10. In the information processing system described in claim 8, In the synchronization step, the processor synchronizes the attendance information with the system when the user performs a synchronization operation. Information processing system.

11. In the information processing system described in claim 8, In the display step, the processor displays the difference between the working hours for the first period indicated by the acquired attendance information and the total man-hours indicated by the man-hour information entered in the percentage input field and the time input field during the first period. Information processing system.

12. Information processing method, The processor comprises each step according to any one of claims 1 to 11, Information processing methods.

13. It is a program, Cause the computer to perform each of the steps described in any one of claims 1 to 11. program.

Images