Work management system, work management server, and work management program

Abstract

To provide a work management system that allows employees's work to be managed in greater detail.SOLUTION: A work management system 1 includes a user terminal 2 and a management server 3. When receiving a user's input of an attendance report operation, a user terminal 2 sends an attendance signal and its own position information to the management server 3. The management server 3 prohibits the user from inputting the attendance report operation after a scheduled start time has elapsed when a batch report is not selected, allows the user to input the attendance report operation even after the scheduled start time has elapsed when the batch report is selected, records the scheduled start time in a work database 32 as position information at the time of attendance when the attendance signal is received before the scheduled start time has elapsed, and records a time that is advanced by a predetermined amount of time from a current time in the work database 32 as a work start time when the attendance signal is received after the scheduled start time has elapsed.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a service management system, a service management server, and a service management program for managing the services of employees, particularly security guards who are dispatched to construction sites and perform tasks such as traffic control. [Background technology]

[0002] Security guards who perform tasks such as traffic control at construction sites and store parking lots follow instructions from the security company to go to the site and perform their duties, but it was common for them to report the start of their shift (upper duty report) and the end of their shift (lower duty report) to the security company by phone. In addition, security guards had to prepare daily reports that included the start and end times of their shifts and were required to be signed and stamped by the site manager.

[0003] However, preparing such daily reports in writing is not efficient, and there is a risk of mistakes being made in the daily reports or the reports being lost.

[0004] In response to this, a work status management system has been proposed that is capable of creating a daily report based on the work start time and work end time transmitted from a security guard via a user terminal (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent Publication No. 2022-161307 Summary of the Invention [Problem to be solved by the invention]

[0006] However, there are cases where a security guard is unable to arrive at the site by the scheduled start time due to illness or traffic conditions, and is unavoidably late. In such cases, the scheduled start time and the actual start time of work will not match.

[0007] In this regard, in the above-mentioned work status management system, when the reporter (security guard) touches the start button on the user terminal, the actual work start time is recorded on the server, and a determination is made as to whether the actual work start time matches the scheduled work start time, and if they do not match, a specified warning is displayed.

[0008] However, in such a system, no warning will be displayed until the latecomer touches the start button and the actual work start time is recorded in the server, no matter how long the scheduled work start time has passed. Also, when multiple security guards are on guard duty, the case where some of the guards are late is not taken into consideration.

[0009] The present invention aims to provide a task management system, a task management server, and a task management program that can more easily manage employee tasks. [Means for solving the problem]

[0010] The business management system according to the present invention comprises a user terminal that accepts an input of an attendance report operation by a user, and a management server capable of data communication with the user terminal, the user terminal having a user side control unit, a user side communication unit that communicates with the management server, and a location information acquisition unit that acquires location information of the user terminal, the user side control unit, when accepting the input of the attendance report operation, transmits an attendance signal and the location information acquired by the location information acquisition unit to the management server via the user side communication unit, the management server having a server side control unit, a server side communication unit that communicates with the user terminal, and a database that records a scheduled start time and selection information indicating whether or not a batch report is selected in association with each other, and the server If the selection information indicates that no selection is made, the server-side control unit prohibits the user from inputting the attendance report operation after the scheduled start time has passed, and if the selection information indicates that a selection is made, the server-side control unit allows the user to input the attendance report operation even after the scheduled start time has passed.If the server-side control unit receives the attendance signal from the user terminal before the scheduled start time has passed, the server-side control unit records the scheduled start time and the location information in the database as the work start time and the attendance location information, respectively.If the server-side control unit receives the attendance signal from the user terminal after the scheduled start time has passed, the server-side control unit records the location information in the database as the attendance location information, and records a time that is advanced a predetermined time from the current time in the database as the work start time.

[0011] The business management server of the present invention comprises a database that records a scheduled start time and selection information indicating whether or not a batch report has been selected, in association with each other, and a control unit. When the selection information indicates no selection, the control unit displays a first operation button on the user terminal before the scheduled start time has elapsed, and displays a predetermined error display on the user terminal instead of the first operation button after the scheduled start time has elapsed. When the selection information indicates a selection, the control unit displays a second operation button on the user terminal regardless of whether the scheduled start time has elapsed. When the first operation button or the second operation button is operated by the user before the scheduled start time has elapsed, location information of the user terminal is obtained from the user terminal, and the scheduled start time and the location information are recorded in the database as the business start time and the arrival location information, respectively. When the second operation button is operated after the scheduled start time has elapsed, the control unit obtains location information of the user terminal from the user terminal, and records the location information in the database as the arrival location information, and records a time that is advanced a predetermined time from the current time in the database as the business start time.

[0012] The business management program of the present invention causes a computer to execute the following steps: determining whether or not batch reporting has been selected; if it is determined that batch reporting has not been selected, determining whether or not it is before the scheduled start time; if it is determined that it is before the scheduled start time, displaying a first operation button on a user terminal carried by a user; if it is determined that it is before the scheduled start time, displaying a predetermined error display on the user terminal instead of the operation button; if it is determined that it is not before the scheduled start time, displaying a second operation button on the user terminal; if it is determined that batch reporting has been selected, acquiring location information of the user terminal when the first operation button or the second operation button is operated before the scheduled start time has elapsed, and recording the scheduled start time and the location information in the database as the business start time and the arrival location information, respectively; and if the second operation button is operated after the scheduled start time has elapsed, acquiring location information of the user terminal, recording the location information in the database as the arrival location information, and recording a time that is advanced a predetermined time from the current time in the database as the business start time. Effect of the Invention

[0013] According to the present invention, since the user is prohibited from reporting to work after the scheduled start time has passed, the user is encouraged to report to the manager, and the manager can easily grasp the situation. On the other hand, when the batch report is selected, the user is permitted to report to work even after the scheduled start time has passed, and even if a latecomer occurs, the user can be left to deal with the lateness. In addition, when the user reports to work before the scheduled start time has passed, the scheduled start time is recorded in the database as the business start time, and when the user reports to work after the scheduled start time has passed, the time that is advanced by a predetermined time from the current time is recorded in the database as the business start time, so that the effort of inputting the start time can be eliminated regardless of whether the user is late or not. [Brief description of the drawings]

[0014] [Figure 1]1 is a block diagram showing a configuration of a business management system according to an embodiment of the present invention. [Diagram 2] FIG. 13 is a diagram showing an example of a user-dedicated screen displayed on a user terminal. [Diagram 3] FIG. 13 is a diagram showing an example of a daily report input screen displayed on a user terminal. [Figure 4] FIG. 13 is a diagram showing an example of a daily report confirmation screen displayed on a user terminal. [Diagram 5] FIG. 13 is a diagram showing an example of a user-only screen (representative-only screen) displayed on a user terminal. [Figure 6] FIG. 13 is a diagram showing an example of a batch attendance screen displayed on a user terminal. [Figure 7] FIG. 13 is a diagram showing an example of a user-only screen (member-only screen) displayed on a user terminal. [Figure 8] FIG. 2 is a diagram illustrating an example of a data structure of a database included in the management server. [Figure 9] 2 is a diagram showing an example of a business registration screen displayed on the administrator terminal shown in FIG. 1; [Figure 10] FIG. 13 is a diagram showing an example of a task list screen displayed on the administrator terminal. [Figure 11] 11 is a flowchart showing the procedure of a service management process executed by a management server. [Figure 12] 12 is a flowchart showing the procedure of one-person management processing executed in S3 of FIG. 11; [Figure 13] FIG. 13 is a diagram showing an example of an attendance status screen displayed on a manager terminal. [Figure 14] FIG. 13 is a diagram showing an example of a daily report editing screen displayed on the manager terminal. [Figure 15] FIG. 13 is a diagram showing an example of a clock-in processing screen displayed on a manager terminal. [Figure 16] 12 is a flowchart showing the procedure of a batch report management process executed in S5 of FIG. 11; [Figure 17] 11 is a flowchart showing the procedure of a latecomer determination process executed by the management server. [Figure 18] FIG. 13 is a diagram showing an example of a daily report screen displayed on the manager terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. With reference to Fig. 1, a business management system 1 according to this embodiment is a system for managing the business of employees (hereinafter, referred to as "users") who go to various work locations to perform their work, and in this embodiment, a case where the user is a security guard will be described as an example.

[0016] The business management system 1 comprises a user terminal 2 carried and operated by a user, a management server (business management server) 3 capable of communicating with the user terminal 2 via a network NW, and an administrator terminal 4 capable of communicating with the management server 3 via the network NW.

[0017] The user terminal 2 is composed of a terminal device with communication function such as a smartphone or a tablet, and is a device that can access the website provided by the management server 3, and is equipped with a communication unit (user side communication unit) 21, a memory unit 22, a display input unit 23, a location information acquisition unit 24, and a control unit (user side control unit) 25.

[0018] The communication unit 21 is a communication interface for communicating with the management server 3. The storage unit 22 stores programs for executing various control processes and functions in the control unit, input data, etc., and is composed of a RAM (Random Access Memory), a ROM (Read Only Memory), etc.

[0019] The display input unit 23 is, for example, a touch panel display, and includes a display unit (user side display unit) 23a and an input unit 23b. The position information acquisition unit 24 acquires position information of the user terminal 2 using, for example, a GPS (Global Positioning System).

[0020] The control unit 25 controls the overall operation of the user terminal 2 by executing the programs stored in the storage unit 22, and is composed of a CPU (Central Processing Unit) etc. The control unit 25 also functions as a position information transmission unit 25a, a clock-in signal transmission unit 25b, a clock-out signal transmission unit 25c, a display control unit 25d, etc.

[0021] The location information transmission unit 25a transmits the location information acquired by the location information acquisition unit 24 to the management server 3 via the communication unit 21. This location information transmission unit 25a is started up at the same time as the clock-in signal transmission unit 25b and the clock-out signal transmission unit 25c transmit the clock-in signal and the clock-out signal, respectively, to transmit the location information.

[0022] The clock-in signal transmission unit 25b transmits a predetermined clock-in signal to the management server 3 via the communication unit 21 when the user performs a clock-out report operation described later. The clock-out signal transmission unit 25c transmits a predetermined clock-out signal to the management server 3 via the communication unit 21 when the user performs a clock-out report operation described later.

[0023] The display control unit 25d displays various information on the display unit 23a, and in this example, displays various web pages provided by the management server 3 on the display unit 23a. The web pages include a user-dedicated screen (FIG. 2) and a daily report input screen (FIG. 3), which will be described later. In this embodiment, when login is successful on a login screen (not shown) of the web page, a user-dedicated screen is displayed on the display unit 23a of the user terminal 2, and the user can check contact information and perform attendance and clock-out reporting operations on the user-dedicated screen.

[0024] An example of a user-only screen is shown in Fig. 2(a). The user-only screen 201 shown in Fig. 2(a) includes a basic information field 211 related to work, a common message field 212, an individual message field 213, an attendance button 214, and a daily report input button 215. Basic information related to work is displayed in the basic information field 211. The common message field 212 and the individual message field 213 will be described later.

[0025] In addition, the clock-in button 214 is provided for the user to perform the clock-in report operation. When the clock-in button 214 (first operation button) is operated (tapped) by the user, the location information of the user terminal 2 is sent to the management server 3 along with a predetermined clock-in signal, and the user terminal 2 displays a user-specific screen 201 including an attendance report completion display 216 in place of the clock-in button 214, as shown in FIG. 2(b).

[0026] The daily report input button 215 is operated by the user when clocking out. When the daily report input button 215 is operated, a daily report input screen is displayed on the user terminal 2.

[0027] Fig. 3 is an example of a daily report input screen. A daily report input screen 202 shown in Fig. 3 is provided with a start time display field 221, an end time input field 222, a button 223 for confirmation screen, and the like. The start time display field 221 displays the start time of business. The user inputs the end time of business into the end time input field 222. When the user operates the button 223 for confirmation screen, a daily report confirmation screen is displayed on the user terminal 2.

[0028] 4 is an example of the daily report confirmation screen 203. The user presents the daily report confirmation screen 203 to the site manager, has the site manager confirm the work content, and has the site manager operate the confirmation completion button 224. When the confirmation completion button 224 is operated in this manner, the location information of the user terminal 2 and the like are transmitted to the management server 3 together with a predetermined clock-out signal, and the user terminal 2 displays the user-dedicated screen 201 including a daily report input completion display 217 instead of the daily report input button 215, as shown in FIG. 3(c). That is, in this embodiment, the operation of the confirmation completion button 224 (FIG. 4) corresponds to the clock-out report operation.

[0029] Furthermore, if the user is late or the like and does not operate the clock-in button 214 by the scheduled start time of the work day, an error message 218 is displayed on the user-only screen 201 on the user terminal 2 instead of the clock-in button 214, as shown in FIG. 2(d). This prohibits the user from operating the clock-in button 214 (i.e., clock-in report operation). In this case, the user reports the situation to the manager by telephone or the like. When the manager who has received the report from the user performs the clock-in processing operation described below on the manager terminal 4, the user terminal 2 displays the user terminal screen 201 as shown in FIG. 2(b).

[0030] In this way, users who have not reported to work even though the scheduled start time of work has passed (hereinafter referred to as "latecomers") are required to report to the administrator. The reason for requiring users to report to the administrator is so that the administrator can quickly grasp the user's situation and take the necessary measures.

[0031] Here, a user may work alone or in a group of multiple users. In the case of a group of users, it may be sufficient for one user to report the attendance and departure times of all users at once.

[0032] Therefore, in this embodiment, when working in a group, if a single user (hereinafter referred to as the "representative") selects to make a collective report, instead of the user-only screen 201 as shown in FIG. 2, a user-only screen for the representative (hereinafter also referred to as the "representative-only screen") is displayed on the user terminal 2 of the representative, and a user-only screen for members (hereinafter also referred to as the "member-only screen") is displayed on the user terminals 2 of users other than the representative.

[0033] An example of the representative-only screen is shown in Fig. 5(a). The representative-only screen 204 shown in Fig. 5(a) is almost the same as the user-only screen 201 shown in Fig. 2(a), but includes a batch attendance button 244 instead of the attendance button 214. When the batch attendance button 244 is operated, a batch attendance screen (selection screen) is displayed on the user terminal 2 of the representative.

[0034] FIG. 6 is an example of a batch attendance screen. In the batch attendance screen 205 shown in FIG. 6, the user names of the responsible users who make up the group are displayed in a list, and a check box 251 is displayed next to each user name. The check box 251 is checked in the initial setting, that is, all the responsible users are selected. The representative checks whether all users are present, and if there is an absent user (latecomer), unchecks the absent user. After that, when the attendance button 252 (second operation button) is operated on the batch attendance screen 205, an attendance signal is transmitted to the management server 3 together with the position information of the representative's user terminal 2, and thus, an attendance report is made for at least one responsible user selected (check box 251 is checked) on the batch attendance screen. That is, in this embodiment, the operation of the attendance button 214 or the attendance button 252 corresponds to the attendance report operation.

[0035] If the batch attendance button 244 shown in FIG. 5(a) is operated again after that, the batch attendance screen is displayed again on the user terminal 2, and the user names of the responsible users who were not selected in the previous operation (check boxes 251 are unchecked) are displayed in a list along with the check boxes 251 on the batch display screen. When the representative operates the attendance button 252, an attendance signal is sent to the management server 3 together with the location information of the representative's user terminal 2, and an attendance report is made for at least one responsible user selected on the batch attendance screen.

[0036] Furthermore, when the attendance reports of all responsible users have been completed in this manner, the representative-only screen 204 on the representative's user terminal 2 displays an attendance report completion display 246 instead of the batch attendance button 244, as shown in FIG. 5(b).

[0037] In addition, when the representative's batch report is selected, the representative's attendance report operation is not prohibited even if a latecomer occurs, and the representative can report attendance by operating the attendance button 252. This is because, even if a latecomer occurs, the representative can grasp the current situation and respond instead of the manager.

[0038] In addition, the daily report input button 245 (FIG. 5(b)) on the representative-only screen 204 is operated by the representative when the representative finishes work, and when the daily report input button 245 is operated, a daily report batch input screen (not shown) is displayed on the user terminal 2 of the representative. This daily report batch input screen is almost the same as the daily report input screen 202 shown in FIG. 3, but differs from the daily report input screen 202 shown in FIG. 3 in that the representative can input the end time for each of the responsible users constituting the group. When the representative inputs the end time for each responsible user on the daily report batch input screen and operates a button (not shown) to the confirmation screen, a daily report confirmation screen (not shown) is displayed, and when the confirmation completion button (not shown) is operated on this daily report confirmation screen (i.e., a clock-out report operation is performed), a predetermined clock-out signal is transmitted to the management server 3 together with the position information of the representative's user terminal 2, and a daily report input completion display 247 is displayed on the representative-only screen 204 on the user terminal 2 of the representative, as shown in FIG. 5(c).

[0039] Fig. 7 is an example of a member-only screen displayed on the user terminal 2 of a user other than the representative. The member-only screen 206 shown in Fig. 7 includes a basic information field 211 related to work, a common message field 212, and an individual message field 213, but does not include a work attendance button or a daily report input button, and the members themselves cannot report their attendance or departure.

[0040] Referring to Figure 1, the administrator terminal 4 is installed, for example, at a security company acting as an administrator, and includes a communication unit 41, a control unit 42, a display unit (administrator side display unit) 43, an input unit 44, and a memory unit 45.

[0041] The communication unit 41 is a communication interface for communicating with the management server 3. The display unit 42 displays various information, and in this case, various web pages are displayed based on various signals provided from the management server 3. In this embodiment, when the administrator successfully logs in on the login screen of the web page, a task registration screen (FIG. 9), a task list screen (FIG. 10), etc., which will be described later, are displayed on the display unit 43 of the administrator terminal 4.

[0042] The management server 3 also includes a communication unit (server-side communication unit) 31, a storage unit 32, and a control unit (server-side control unit) 33. The communication unit 31 is a communication interface for communicating with the user terminal 2 and the administrator terminal 4. The storage unit 32 stores programs, input data, databases, etc. for executing various control processes and each function of the control unit 33, and is composed of a RAM (Random Access Memory), a ROM (Read Only Memory), etc. The databases stored in the storage unit 32 include a user database 32a, a client database 32b, and a business database 32c, which will be described later.

[0043] The control unit 33 controls the overall operation of the management server 3 by executing the programs stored in the storage unit 32, and is composed of a CPU (Central Processing Unit) etc. The control unit 33 also includes, as its functions, a site providing unit 33a and a storage control unit 33b, which are started up and executed by the programs stored in the storage unit 32.

[0044] The site providing unit 33a has the functionality of a web server, and provides websites to the user terminal 2 and the administrator terminal 4, thereby displaying various web pages on the display units 23a, 43 of the user terminal 2 and the administrator terminal 4, and also accepting input operations performed on the web pages.

[0045] For example, when the site providing unit 33a is accessed by the user terminal 2, it transmits a login screen of the website to the user terminal 2, and the user terminal 2 displays the login screen on the display unit 23a. Furthermore, when the authentication is successful, the site providing unit 33a transmits a user-dedicated screen of the website to the user terminal 2, and the user terminal 2 displays the above-mentioned user-dedicated screen on the display unit 23a.

[0046] Similarly, when there is access from the administrator terminal 4, the site providing unit 33a provides a login screen of the website to the administrator terminal 4, and the administrator terminal 4 displays the provided login screen on the display unit 43. Furthermore, when authentication is successful, the site providing unit 33a transmits a business registration screen ( FIG. 9 ) of the website to the administrator terminal 4 in response to a request from the administrator via the administrator terminal 4, and the administrator terminal 4 displays the business registration screen, etc. on the display unit 43.

[0047] For example, when the recording control unit 33b receives a clock-in signal or a clock-out signal from the user terminal 2, it records the start and end times of work, the location information of the user terminal 2, the clock-in flag, and the like in the storage unit 32. Details will be described later.

[0048] In the user database 32a, information related to a user, such as a user ID, a login ID, a password, a name, an address, etc., is recorded in association with each other.

[0049] In the client database 32b, information on the client, such as the client ID, name, address, and the first to Nth site names, is recorded in association with each other. Note that the site refers to the place where the user is dispatched to actually perform the work.

[0050] 8 shows an example of the data structure of the task database 32c. In the task database 32c, information on a "task code", a "client ID", a "site name", a "start time of work", a "scheduled start time", a "general message", a "selection of collective report", and a "responsible user" is stored in association with each task requested by a client, and the information on the "responsible user" includes a "user ID", an "individual message", a "start time", an "end time", "location information at the time of work arrival", "location information at the time of leaving work", and information on "work arrival". In addition, multiple users may be in charge of one task, and in such a case, information on multiple "responsible users" is recorded in association with one task.

[0051] In this embodiment, in the data field of "lump report selection", a flag (selection flag) for determining whether or not a lump report has been selected is recorded as selection information indicating whether or not a lump report has been selected.

[0052] In addition, in the "Attendance" data area, a flag (Attendance flag) is recorded as attendance information indicating whether the user has attended work or not, and the attendance flag is stored when the user performs an attendance report operation in the business management processing described below, or when the administrator performs the attendance processing operation described below.

[0053] 9 shows an example of a task registration screen 401 displayed on the administrator terminal 4. When a task request is received from a client, the administrator (person in charge at the security company) inputs, selects, and registers the necessary items on the task registration screen 401 displayed on the administrator terminal 4. The data thus input and selected is recorded in the respective data areas of the task database 32c shown in FIG.

[0054] More specifically, the business registration screen 401 shown in FIG. 9 includes a client selection field 411 for selecting the client who is requesting the work, a site name input field 412 for selecting the site name, a date input field 413 for inputting the date, a work start time input field 414 for inputting the work start time of the responsible user, a scheduled start time input field 415 for inputting the scheduled start time of the business, a message input field 416 for inputting common message items, a selection box 417 for selecting a bulk report, and a responsible user registration field 418 for registering a responsible user.

[0055] The client ID and site name of the client selected in the client selection field 411 and site name input field 412 are recorded in the business database 32c as "client ID" and "site name." Similarly, the date, work start time, and scheduled start time input in the date input field 413, work start time input field 415, and scheduled start time input field 416 are recorded in the business database 32c as "date," "scheduled start time," and "work start time," respectively.

[0056] Messages to all responsible users are input in the message input field 416, and the messages input in the message input field 416 are recorded in the business database 32c as "common messages." The common messages are displayed in the message field 212 of the user-dedicated screen 201 (204, 206).

[0057] The selection box 417 is used to select whether or not the representative will make a batch report of the attendance and departure reports of the users in charge, and when the selection box 417 is selected (checked), batch reporting is selected and a selection flag is recorded in the batch report selection data area of ​​the business database 32c. Note that batch reporting can only be selected when there are multiple users in charge, and cannot be selected when there is only one user in charge.

[0058] The responsible user registration field 418 includes a responsible user selection field 419 for selecting a responsible user, and a message input field 420, and the message input field 420 allows input of individual messages to the corresponding responsible users. In the example shown in FIG. 9, three users are selected as the first to third responsible users (user 1, user 2, and user 3). Even if multiple users are selected as responsible users in this way, or even if only one user is selected as the responsible user, the first responsible user is automatically set as the representative.

[0059] The user ID of the user selected in the user selection field 419 is recorded as a "user ID" in the business database 32c, and the individual message entered in the message input field 420 is recorded as an "individual message" in the business database 32c. The individual message is displayed in the individual message field 213 of the user-only screen 201 (204, 206).

[0060] Here, since the individual message entered in the message input field 420 is reported only to the responsible user, for example, an unlock number required to access the site can be entered as an individual message for the first responsible user (representative), and the information can be reported only to the representative. On the other hand, information that should be shared by all responsible users can be input as a common message in the message input field 416, and this can be notified to all responsible users. For example, in the example shown in FIG. 9, "unlock number 12345" is entered as an individual message for the first responsible user, who is the representative.

[0061] Fig. 10 shows an example of a task list screen displayed on the administrator terminal 4. The task list screen 403 shown in Fig. 10 is displayed on the display unit 43 of the administrator terminal 4 by the control unit 33 of the management server 3, and the task list screen 403 displays a list of tasks extracted based on specified conditions (date or client ID). On this task list screen 403, the administrator can confirm the site name for each task, the start time of the user in charge, the scheduled start time of the task, the representative name, and the attendance status of the user in charge.

[0062] More specifically, the "site name", "date", "start time of work", "scheduled start time", and "representative name" are read from the work database 32c and displayed on the work list screen 403. "Attendance status" indicates the attendance status of the responsible user, and in this embodiment, the number of responsible users and the number of responsible users who have already attended work are displayed in association with each other as a status display 431 that displays the attendance status, for example, "2 / 3" indicates that of three responsible users, two have already attended work (reported attendance) and one has not attended work, i.e., has not yet attended work (not reported attendance).

[0063] In this embodiment, whether or not the user in charge has already clocked in is determined based on whether or not an attendance flag is recorded in the business database 32c in association with the user in charge.

[0064] Next, an example of the business management process executed by the management system 1 will be described. Fig. 11 is a flowchart showing the flow of the business management process executed by the management server 3. This business management process is started when any user in charge of business on the day successfully logs in to an individual screen, and is executed by the control unit 33 of the management server 3 based on a predetermined program.

[0065] In the business management process, first, a user-dedicated screen including a basic information field 211, a message field 213, and an individual message field 214 is displayed on the user terminal 2 possessed by the user (S1). Basic information, general messages, and individual messages related to business are read out from the business database 32c and displayed in the basic information field 211, the message field 213, and the individual message field 213, respectively.

[0066] Next, it is determined whether or not batch reporting has been selected for the tasks for which the user is responsible (S2). If batch reporting has not been selected (S2: NO), one-person management processing is executed (S3). On the other hand, if batch reporting has been selected (S2: YES), it is determined whether or not the user is a representative (S4). If the user is a representative (S4: YES), batch report management processing is executed (S5). On the other hand, if the user is not a representative (S4: NO), the processing is terminated.

[0067] Next, the one-person management process executed in S3 of FIG. 11 will be described with reference to the flowchart of FIG.

[0068] In the one-person management process, first, it is determined whether the working start time has passed (S11). If the working start time has passed (S11: YES), it is determined whether the user has already clocked out (S12). This determination can be made, for example, based on whether the end time has been recorded in the business database 32c. If the user has not already clocked out (S12: NO), it is determined whether the user has already clocked in (S13). As described above, in this embodiment, whether the user has already clocked in is determined based on whether the working flag has been recorded in the business database 32c.

[0069] If the user has not yet clocked in (S13: NO), it is determined whether the scheduled start time has passed (S14). If the scheduled start time has not passed (S14: NO), as shown in Fig. 3(a), the clock-in button 214 (first operation button) and the daily report input button 215 are displayed on the user terminal 2 (S15), and it is determined whether the clock-in button 214 has been operated, i.e., whether a clock-in signal has been received from the user terminal 2 (S16).

[0070] If the clock-in button 214 is not operated (S16: NO), the process returns to S14. On the other hand, if the clock-in button 214 is operated (S16: YES), the process proceeds to S17. In S17, the location information of the user terminal 2 is acquired from the user terminal 2. In addition, the scheduled start time and the location information recorded in the business database 32c are recorded in the business database 32c in association with the user as the start time (business start time) and clock-in location information, respectively, and the clock-in flag is recorded (S17). Next, as shown in FIG. 2(b), the clock-in report completion display 216 and the daily report input button 215 are displayed on the user terminal 2 (S18). Then, it is determined whether the daily report input button 215 has been operated (S19). If the daily report input button 215 has not been operated (S19: NO), the process waits until the daily report input button 215 is operated.

[0071] On the other hand, when the daily report input button 215 is operated (S19: YES), the daily report input screen 202 (FIG. 3) as shown in FIG. 3 is displayed on the user terminal 2 (S20). At this time, the start time already recorded in the business database 32c is displayed in the start time display field 221. The user inputs the end time (business end time) in the end time input field 222.

[0072] Thereafter, when the user operates the button 223 to the confirmation screen, the daily report confirmation screen 203 as shown in FIG. 4 is displayed on the user terminal 2 (S21), and it is determined whether the confirmation completion button 224 on the daily report confirmation screen 203 has been operated (i.e., whether a clock-out signal has been received from the user terminal 2) or not (S22).

[0073] If the confirmation completion button 224 is not operated (S22: NO), the process waits until the confirmation completion button 224 is operated, and when the confirmation completion button 224 is operated (S22: YES), the process acquires the location information of the user terminal 2 from the user terminal 2. In addition, the location information and the end time entered on the daily report registration screen 202 are associated with the user and recorded as clock-out location information and end time (work end time) in the business database 32c (S23). Thereafter, as shown in FIG. 3(c), a daily report input completion display 217 is displayed on the user-specific screen 201 on the user terminal 2 (S24), and the process ends.

[0074] On the other hand, if the work start time has not passed in S11 (S11: NO), the process waits until the work start time arrives. This prevents the user from clocking in before the work start time.

[0075] If it is determined in S12 that the user has already clocked out (S13: YES), a work clock-in report completion display 216 and a daily report input completion display 217 are displayed on the user terminal 2, as shown in FIG.

[0076] In S14, if it is determined that the scheduled start time has passed (S14: YES), it is determined whether the user has already clocked in (i.e., whether the clock-in flag is recorded in the business database 32c) (S26). If the user has not already clocked in (S26: NO), a predetermined error message 218 is displayed on the user terminal 2 (S27), as shown in Fig. 3(d), and the process returns to S26.

[0077] Here, when the error message 218 is displayed, the user reports the situation to the manager by telephone, etc. The manager who receives the situation report performs the clock-in process operation on the manager terminal 4 as follows.

[0078] That is, when the manager operates (clicks) any of the status displays 431 on the task list screen 403 shown in Fig. 10, the management server 3 displays the attendance status screen on the manager terminal 4. Fig. 13 shows an example of the attendance status screen displayed on the manager terminal 4 when the status display 431 ("2 / 3") of the third task from the top in Fig. 10 is operated.

[0079] As shown in FIG. 13, the attendance status screen displays a list of the names (appellations) of the users assigned to the task, as well as the status and location information of each user.

[0080] In this embodiment, if a responsible user has already clocked in (i.e., an attendance flag is recorded in the business database 32c), the status column 441 displays the word "At Work," and the location information column 442 displays the location information at the time of attendance recorded in the business database 32c. On the other hand, for a responsible user who has not yet clocked in, both the status column 441 and the location information column 442 are blank if it is before the scheduled start time, but after the scheduled start time, a display indicating that attendance reporting is prohibited (the words "Locked" in the example of FIG. 13) is displayed in the status column 441. This allows the manager to confirm which responsible users have already clocked in and which are late.

[0081] 10, when the manager operates any one of the daily report edit buttons 432, the management server 3 causes the manager terminal 4 to display a daily report edit screen. Fig. 14 shows an example of the daily report edit screen displayed on the manager terminal 4 when the daily report edit button 432 for the third task from the top in Fig. 10 is operated. As shown in Fig. 14, the daily report edit screen displays a start time input field 451 corresponding to the name of each responsible user, so when the manager enters a start time in the start time input field 451 of a latecomer and operates the register button 452, the management server 32 records the start time in the task database 32c as a start time in association with the user.

[0082] Furthermore, when the administrator selects any one of the tasks on the task list screen 403 shown in FIG. 10 (here, by checking the check box 432 corresponding to the target task) and operates the attendance processing button 433, the management server 3 displays the attendance processing screen on the administrator terminal 4. FIG. 15 shows an example of the attendance processing screen. This attendance processing screen displays a list of the names (names) of users who have not yet clocked in for the selected task, and the administrator can select a user by checking a check box 461. When the administrator selects any one of the users (i.e., by checking the check box 461 of the relevant user) and operates the attendance button 462, the management server 3 records an attendance flag in the task database 32c in association with the selected user, and the user is thereby processed as having clocked in.

[0083] When the clock-in flag is recorded in the business database 32c by the clock-in processing operation by the administrator as described above, it is determined in S26 that the user has already clocked in (S26: YES), and the process proceeds to S18.

[0084] Next, the batch report management process executed in S5 of Fig. 11 will be described with reference to the flowchart of Fig. 16. In this batch report management process, first, it is determined whether the work start time has passed (S31). If the work start time has not passed (S31: NO), it waits until the work start time arrives. On the other hand, if the work start time has passed (S31: YES), it is determined whether the person has already clocked out (S32).

[0085] If they have not clocked out (S32: NO), it is determined whether all the responsible users have clocked in (S33). If they have not clocked in (S33: NO), as shown in Fig. 5(a), the batch clock-in button 244 and the daily report input button 245 are displayed on the user terminal 2 (S34), and it is determined whether the batch clock-in button 244 has been operated (S35). If the batch clock-in button 244 has not been operated (S35: NO), it waits until the batch clock-in button 244 is operated.

[0086] On the other hand, when the batch attendance button 244 is operated (S35: YES), the batch attendance screen 205 as shown in Fig. 6 is displayed on the user terminal 2 (S36). As described above, the batch attendance screen 205 displays a list of the names of users in charge who have not yet arrived at work, and also displays the attendance button 252 (second operation button). Next, it is determined whether the attendance button 252 has been operated, that is, whether an attendance signal has been received from the user terminal 2 (S37).

[0087] If the clock-in button 252 is not operated (S37: NO), the process waits until the clock-in button 252 is operated. On the other hand, if the clock-in button 252 is operated (S37: YES), the process acquires the location information of the user terminal 2, and records the location information in the business database 32c in association with at least one (one or more) responsible user selected on the collective clock-in screen (hereinafter, referred to as the "selected user") (S38). Next, the process judges whether the scheduled start time has passed (S39). If the scheduled start time has not passed (S39: NO), the process records the scheduled start time recorded in the business database 32c as the start time in association with the selected user in the business database 32c, records the clock-in flag (S40), and returns to S33.

[0088] On the other hand, if the scheduled start time has passed (S39: NO), the current time is rounded up to a predetermined time unit (for example, 30 minutes) and recorded as the start time in the business database 32c for the selected user, and the attendance flag is recorded (S41), and the process returns to S33.

[0089] On the other hand, if all the responsible users have already clocked in at S33 (S33: YES), the user terminal 2 displays the attendance report completion display 246 and the daily report input button 125 as shown in FIG. 5(b) (S42), and determines whether the daily report input button 245 has been operated (S43). If the daily report input button 245 has not been operated (S43: NO), the system waits until the daily report input button 245 is operated. On the other hand, if the daily report input button 245 has been operated (S43: YES), the system displays a daily report registration screen (not shown) on the user terminal 2 (S44). The user performs the same operations on the daily report registration screen as on the daily report input screen 202 displayed in S20 described above.

[0090] That is, the user inputs the end time (work end time) for each of all the users in charge. Then, when the user operates a button (not shown) to confirm screen on the daily report registration screen, the daily report confirmation screen (confirmation completion button (second operation button)) is displayed on the user terminal 2 (S45), and it is determined whether the confirmation completion button has been operated (i.e., whether a clock-out signal has been received from the user terminal 2) (S46). If the confirmation completion button has not been operated (S46: NO), the system waits until it is operated, and when the confirmation completion button is operated (S46: YES), the system obtains the location information of the user terminal 2, associates it with each user in charge, and records the location information in the business database 32c as clock-out location information, and records the end time input on the daily report registration screen in S41 as the end time (S47).

[0091] Thereafter, as shown in FIG. 5(c), a daily report input completion display 247 is displayed on the user terminal 2 (S48), and the process ends.

[0092] On the other hand, if it is determined in S32 that the user has already clocked out (S31), as shown in FIG. 5(c), a work clock-in report completion display 246 and a daily report input completion display 247 are displayed on the user terminal 2, and the process ends.

[0093] Next, the lateness determination process executed in the management server 3 will be described with reference to the flowchart shown in Fig. 17. This lateness determination process determines whether or not there is a latecomer for each task, and if there is a latecomer, displays a warning on the task list screen 403. Methods for displaying the warning include, but are not limited to, displaying the relevant task in red or in reverse video.

[0094] This lateness determination process is executed by the control unit 33 for each task registered in the task database 32c based on a predetermined program, and first, it is determined whether the scheduled start time of the task has passed (S51). If it has not passed (S51: NO), the process is terminated.

[0095] On the other hand, if the scheduled start time has passed (S51: YES), the variable i is set to 1 (S52), and it is determined whether the i-th responsible user has already clocked in (whether an attendance flag is recorded in the business database 32c) (S53). If it is determined that the i-th responsible user has already clocked in (S53: YES), it is determined whether processing has been completed for all responsible users (S54). If processing has been completed (S54: YES), the display mode on the business list screen 403 is set to the normal display mode (maintaining the normal display mode), and the processing ends.

[0096] On the other hand, if the process has not been completed for all users (S54: NO), the value of the variable i is incremented by 1 (S56), and the process returns to S53.

[0097] Also, in S53, if it is determined that the user has not yet clocked in (S53: NO), the display mode on the task list screen 403 is set to the warning display mode (the warning display mode is maintained) (S57), and the process ends.

[0098] As a result, if even one person is late for each task, the display mode on the task list screen 403 is set to a warning display mode, and a warning message is displayed on the task list screen 403 indicating the task.

[0099] Furthermore, in this embodiment, when any of the daily report output buttons 435 is operated on the task list screen 403 in Fig. 10, the management server 2 refers to the memory unit 32 (here, the user database 32a, the client database 32b, and the task database 32c) and displays a daily report screen on the display unit 43 of the management terminal 4. Fig. 18 is an example of a daily report screen. In addition to the "client name", "site name", and "date", the daily report screen displays a "start time" (time when the task begins) and an "end time" (time when the task ends) associated with at least one responsible user, and the administrator can print out the daily report screen or send it to a client.

[0100] In this way, in the business management system of this embodiment, if a user reports their attendance before the scheduled start time, the predetermined scheduled start time of the work is recorded in the memory unit 32 as the user's work start time, making it easy to create a daily report.

[0101] Also, by prohibiting latecomers from reporting their attendance, they are encouraged to report to the manager by telephone or the like, which allows the manager to quickly grasp the status of the lateness.

[0102] On the other hand, when batch reporting is selected and someone is late, the situation can be understood by the representative, which reduces the burden on the manager, and the user only needs to perform the attendance report operation to record the time that is advanced a certain number of hours from the current time as the start time of the work, eliminating the need to input the start time of the work. Furthermore, the manager can input and edit the start time on the daily report editing screen (Fig. 14), which allows for flexible response according to the situation and circumstances.

[0103] Although the embodiment of the present invention has been described above with reference to the accompanying drawings, the present invention is not limited to such an embodiment, and various modifications and alterations are possible without departing from the scope of the present invention.

[0104] For example, in the above embodiment, the determination of whether a user has already clocked in to work is made based on whether an attendance flag is recorded in association with the user in the memory unit 32 (business database 32c), but instead, the determination may be made based on, for example, whether a start time is recorded in association with the user in the memory unit 32 (business database 32c).

[0105] In addition, in the above embodiment, when a work arrival report or a work departure report is made, the location information of the user terminal 2 is recorded in the business database 32c. However, in addition to the location information, the time when the work arrival report or the work departure report is made (work arrival report time or work departure report time) may also be recorded in the business database 32c.

[0106] In the above embodiment, the end time input on the daily report registration screen is recorded in the business database 32c, but the end time that can be input on the daily report registration screen may be limited. For example, the control unit 33 of the management server 3 determines whether the end time input on the daily report registration screen is within a predetermined time before or after the current time (for example, 30 minutes before or after), and if it is within the predetermined time before or after the current time, accepts the input of the end time, associates it with the user, and records it in the business database 32c, whereas if it is outside the predetermined time before or after the current time, it may not accept the input of the end time and display an error message on the user terminal 2.

[0107] Furthermore, in the above embodiment, the representative inputs the end time for each of all the users in charge on the daily report registration screen (not shown) displayed in S44 of FIG. 16. Alternatively, it is possible to set whether or not to select the batch clock-out report on the daily report registration screen, and when the batch clock-out report is selected, the end time input for the representative is reflected as the end time for all the users in charge (i.e., the end time input as the end time for the representative is recorded in the database 32c as the end time for all the users in charge). In this case, the representative only needs to input his / her own end time, and can omit inputting the end times for the other users in charge. As a method for setting whether or not to select the batch clock-out report, it is preferable to provide a batch clock-out report selection box on the daily report registration screen, and allow the representative to select the batch clock-out report by checking the box. [Explanation of symbols]

[0108] 1 Business Management System 2. User terminal 3 Management Server 4. Administrator terminal 21 Communication unit (user side communication unit) 23a Display unit (user side display unit) 24 Location information acquisition section 25 Control section (user side control section) 31 Communication unit (server-side communication unit) 32 Storage section 33 Control unit (server side control unit) 41 Communication Department (Administrator's Communication Department) 43 Display section (Administrator side display section) 205 Bulk attendance screen (selection screen) 214 Attendance button (first operation button) 252 Attend button (second operation button)

Claims

1. A user terminal that accepts an input of a user's attendance report operation; a management server capable of data communication with the user terminal; The user terminal, A user side control unit; A user-side communication unit that communicates with the management server; A location information acquisition unit that acquires location information of the device itself; having When the user-side control unit receives the input of the attendance report operation, the user-side control unit transmits an attendance signal and the location information acquired by the location information acquisition unit to the management server via the user-side communication unit; The management server includes: A server-side control unit; A server-side communication unit that communicates with the user terminal; a database for recording the scheduled start time and selection information indicating whether or not a batch report is selected, in association with each other; having The server-side control unit If the selection information indicates no selection, prohibiting the user from inputting the attendance report operation after the scheduled start time has passed; When the selection information indicates that a selection has been made, the input of the attendance report operation by the user is permitted even after the scheduled start time has passed; When the clock-in signal is received from the user terminal before the scheduled start time has passed, the scheduled start time and the location information are recorded in the database as a work start time and clock-in location information, respectively; When the clock-in signal is received from the user terminal after the scheduled start time has passed, the business management system records the location information in the database as the clock-in location information, and records a time that is advanced a predetermined amount from the current time in the database as the business start time.

2. The business management system described in claim 1, wherein when the selection information indicates that a selection has been made, the server-side control unit records the work start time and the arrival location information in the database in association with each of at least one user selected by the user.

3. The user terminal further includes a user side display unit, The business management system described in claim 2, wherein when the selection information indicates that a selection has been made, the server-side control unit displays a selection screen on the user-side display unit, and records the work start time and the arrival location information in the database in association with each of at least one user selected on the selection screen.

4. The system further includes an administrator terminal operated by an administrator, The administrator terminal includes an administrator-side communication unit that communicates with the administration server, and an administrator-side display unit; 2. The business management system according to claim 1, wherein the server-side control unit determines whether or not any person is late, and when it determines that any person is late, causes the manager-side display unit to display a warning message.

5. The user terminal further receives an input of an end time and an input of a clock-out report operation; the user-side control unit, when receiving the input of the clock-out report operation, transmits a clock-out signal together with the end time to the management server; 2. The business management system according to claim 1, wherein the server-side control unit, upon receiving the clock-out signal from the user terminal, records the finish time in the database in association with the user.

6. 6. The business management system according to claim 5, wherein, when the end time input by the user is within a predetermined time before or after the current time, the server-side control unit records the end time in the database.

7. a database for recording the scheduled start time and selection information indicating whether or not a batch report is selected, in association with each other; A control unit, The control unit is when the selection information indicates no selection, before the scheduled start time has elapsed, a first operation button is displayed on the user terminal, and after the scheduled start time has elapsed, a predetermined error display is displayed on the user terminal instead of the first operation button; When the selection information indicates that a selection has been made, a second operation button is displayed on the user terminal regardless of whether the scheduled start time has passed or not; When the first operation button or the second operation button is operated by the user before the scheduled start time has passed, location information of the user terminal is acquired from the user terminal, and the scheduled start time and the location information are recorded in the database as a work start time and arrival location information, respectively; When the second operation button is operated after the scheduled start time has passed, a business management server obtains location information of the user terminal from the user terminal, records the location information in the database as location information at the time of arrival at work, and records a time that is advanced by a predetermined amount from the current time in the database as the business start time.

8. On the computer, determining whether batch reporting is selected; a step of determining whether or not it is before a scheduled start time when it is determined that a batch report has not been selected; when it is determined that the scheduled start time has passed, displaying a first operation button on a user terminal carried by a user; when it is determined that the scheduled start time has not yet arrived, displaying a predetermined error message on the user terminal instead of the operation button; When it is determined that a batch report is selected, displaying a second operation button on the user terminal; When the first operation button or the second operation button is operated before the scheduled start time has passed, acquiring location information of the user terminal, and recording the scheduled start time and the location information in a database as a work start time and arrival location information, respectively; When the second operation button is operated after the scheduled start time has passed, location information of the user terminal is acquired, the location information is recorded in the database as location information at the time of arrival at work, and a time that is advanced by a predetermined amount from the current time is recorded in the database as the work start time.

Images