JP7850909B2 - Business management system, business management server, and business management program - Google Patents

Description

This invention relates to a work management system, a work management server, and a work management program for managing the work of employees, particularly security guards dispatched to construction sites and other locations to perform traffic control and other related tasks.

Security guards performing traffic control and other duties at construction sites, store parking lots, etc., would go to the site and perform their duties according to instructions from the security company. It was common practice to report the start and end of their shifts to the security company by telephone. Furthermore, security guards were required to prepare daily reports, which included the start and end times of their work and required the signature and seal of the site supervisor.

However, creating such daily reports in writing was inefficient, and there was a risk of errors in the reports or the reports being lost.

Therefore, a work status management system has been proposed that can generate daily reports based on the start and end times of work transmitted from security guards via user terminals (see, for example, Patent Document 1).

Japanese Patent Publication No. 2022-161307

By the way, security guards may be unable to arrive at the site by the scheduled start time due to illness or traffic issues, resulting in unavoidable delays. In such cases, the scheduled start time and the actual start time will not match.

In this regard, the aforementioned work status management system works as follows: When the reporter (security guard) touches the start button on the user terminal, the actual work start time is recorded on the server. The system then determines whether this actual work start time matches the scheduled work start time, and if they do not match, a predetermined warning is displayed.

However, with such a system, no warning will be displayed, regardless of how much time has passed since the scheduled start time, until the latecomer touches the start button and the actual start time is recorded on the server. Furthermore, the system does not account for situations where some security guards are late when multiple guards are on duty.

The present invention aims to provide a business management system, a business management server, and a business management program that enable easier management of employee tasks.

The business management system according to the present invention comprises a user terminal that receives input of attendance reporting operations by a user, and a management server capable of data communication with the user terminal. The user terminal has 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 device itself. When the user-side control unit receives input of the attendance reporting operation, it transmits an attendance signal and location information acquired by the location information acquisition unit to the management server via the user-side communication unit. The management server has a server-side control unit, a server-side communication unit that communicates with the user terminal, and a database that records the scheduled start time and selection information indicating whether or not a batch report is selected. The control unit, when the selection information indicates no selection, prohibits the user from inputting the attendance report operation after the scheduled start time has elapsed. When the selection information indicates a selection, it allows the user to input the attendance report operation even after the scheduled start time has elapsed. If the control unit receives the attendance signal from the user terminal before the scheduled start time has elapsed, it records the scheduled start time and location information in the database as the work start time and attendance location information, respectively. If the control unit receives the attendance signal from the user terminal after the scheduled start time has elapsed, it records the location information as the attendance location information in the database, and also records a time advanced by a predetermined amount from the current time as the work start time in the database.

The business management server according to the present invention comprises a database that records a scheduled start time and selection information indicating whether or not a batch report is selected, and a control unit. The control unit, when the selection information indicates no selection, displays a first operation button on the user terminal before the scheduled start time has elapsed, and displays a predetermined error message on the user terminal instead of the first operation button after the scheduled start time has elapsed. When the selection information indicates selection has been made, the control unit displays a second operation button on the user terminal regardless of whether or not the scheduled start time has elapsed. If the user operates either the first or second operation button before the scheduled start time has elapsed, the control unit acquires the user terminal's location information from the user terminal and records the scheduled start time and location information in the database as the business start time and clock-in location information, respectively. If the second operation button is operated after the scheduled start time has elapsed, the control unit acquires the user terminal's location information from the user terminal, records the location information as clock-in location information in the database, and records a time advanced by a predetermined amount from the current time as the business start time in the database.

The business management program according to the present invention causes a computer to perform the following steps: determine whether batch reporting is selected; if batch reporting is not selected, determine whether it is before the scheduled start time; if it is determined that it is before the scheduled start time, cause a first operation button to be displayed on the user terminal held by the user; if it is determined that it is not before the scheduled start time, cause a predetermined error display to be displayed on the user terminal instead of the operation button; if batch reporting is selected, cause a second operation button to be displayed on the user terminal; if the first or second operation button is operated before the scheduled start time, acquire the location information of the user terminal and record the scheduled start time and the location information in the database as the business start time and attendance location information, respectively; and if the second operation button is operated after the scheduled start time, acquire the location information of the user terminal, record the location information as attendance location information in the database, and record a time advanced by a predetermined amount from the current time as the business start time in the database.

According to this invention, since users are prohibited from reporting their attendance after the scheduled start time, this encourages users to report to administrators and facilitates administrators in understanding the situation. On the other hand, if batch reporting is selected, users are permitted to report their attendance even after the scheduled start time, allowing administrators to handle late arrivals. Furthermore, when an attendance report is submitted before the scheduled start time, the scheduled start time is recorded in the database as the work start time. When an attendance report is submitted after the scheduled start time, a time advanced by a predetermined amount from the current time is recorded in the database as the work start time, thus eliminating the need to manually enter the start time regardless of whether there is lateness or not.

A block diagram showing the configuration of a business management system according to an embodiment of the present invention. A diagram showing an example of a user-specific screen displayed on the user's terminal. This diagram shows an example of a daily report input screen displayed on a user terminal. This diagram shows an example of a daily report confirmation screen displayed on a user's terminal. This diagram shows an example of a user-specific screen (representative-only screen) displayed on the user's terminal. A diagram showing an example of a batch attendance screen displayed on a user's terminal. This diagram shows an example of a user-specific screen (member-only screen) displayed on the user's terminal. A schematic diagram illustrating an example of the data structure of the database on the management server. Figure 1 shows an example of a task registration screen displayed on the administrator terminal. This diagram shows an example of the task list screen displayed on the administrator's terminal. A flowchart illustrating the procedures for business management processes executed by the management server. A flowchart showing the procedure for the single-person management process executed in S3 of Figure 11. This diagram shows an example of the attendance status screen displayed on the administrator's terminal. This diagram shows an example of the daily report editing screen displayed on the administrator's terminal. This diagram shows an example of the attendance processing screen displayed on the administrator's terminal. A flowchart showing the procedure for the batch report management process executed in S5 of Figure 11. A flowchart illustrating the procedure for determining late arrivals, which is performed by the management server. This diagram shows an example of the daily report screen displayed on the administrator's terminal.

The following describes one embodiment of the present invention with reference to the attached drawings. Referring to Figure 1, the business management system 1 according to this embodiment is a system for managing the work of employees (hereinafter referred to as "users") who perform duties at various work locations. Here, the case where the user is a security guard will be used as an example.

The business management system 1 comprises a user terminal 2 carried and operated by the 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 a network (NW).

The user terminal 2 is comprised of a terminal device with communication capabilities, such as a smartphone or tablet, and is capable of accessing the website provided by the management server 3. It comprises a communication unit (user-side communication unit) 21, a storage unit 22, a display input unit 23, a location information acquisition unit 24, and a control unit (user-side control unit) 25.

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 within the control unit, as well as input data, and consists of RAM (Random Access Memory), ROM (Read Only Memory), etc.

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

The control unit 25 controls the overall operation of the user terminal 2 by executing programs stored in the memory unit 22, and is composed of a CPU (Central Processing Unit), etc. The control unit 25 also functions as a location information transmission unit 25a, an attendance signal transmission unit 25b, an attendance departure signal transmission unit 25c, a display control unit 25d, etc.

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 activated simultaneously with the attendance signal transmission unit 25b and the attendance signal transmission unit 25c when they transmit their attendance and attendance signals, respectively, and transmits the location information.

The attendance signal transmission unit 25b transmits a predetermined attendance signal to the management server 3 via the communication unit 21 when the user performs the attendance reporting operation described later. The attendance departure signal transmission unit 25c transmits a predetermined departure signal to the management server 3 via the communication unit 21 when the user performs the attendance departure reporting operation described later.

The display control unit 25d displays various information on the display unit 23a, and in this case, it displays various web pages provided by the management server 3 on the display unit 23a. These web pages include the user-specific screen (Figure 2) and the daily report input screen (Figure 3), which will be described later. In this embodiment, upon successful login on the web page login screen (not shown), the user-specific screen is displayed on the display unit 23a of the user terminal 2, allowing the user to check important information, report attendance, and report departure on this user-specific screen.

Figure 2(a) shows an example of a user-specific screen. The user-specific screen 201 shown in Figure 2(a) includes a basic information field 211 related to work, a common contact information field 212, an individual contact information field 213, a clock-in button 214, and a daily report input button 215. The basic information field 211 displays basic information related to work. The common contact information field 212 and the individual contact information field 213 will be described later.

Furthermore, the attendance button 214 is for the user to perform the attendance reporting operation. When the user operates (tap) the attendance button 214 (the first operation button), the location information of the user terminal 2 is transmitted to the management server 3 along with a predetermined attendance signal. As shown in Figure 2(b), the user terminal 2 then displays a user-specific screen 201, including an attendance reporting completion display 216, in place of the attendance button 214.

The daily report input button 215 is operated by the user when leaving work. When the daily report input button 215 is operated, the daily report input screen is displayed on the user terminal 2.

Figure 3 shows an example of a daily report input screen. The daily report input screen 202 shown in Figure 3 includes a start time display field 221, an end time input field 222, and a button 223 for the confirmation screen. The start time display field 221 displays the start time of the work. The end time input field 222 is entered by the user. When the user operates the button 223 for the confirmation screen, the daily report confirmation screen is displayed on the user terminal 2.

Figure 4 shows an example of the daily report confirmation screen 203. The user presents the daily report confirmation screen 203 to the site supervisor for confirmation of the work details, and the site supervisor operates the confirmation completion button 224. When the confirmation completion button 224 is operated in this way, the location information of the user terminal 2, etc., is transmitted to the management server 3 along with a predetermined clock-out signal. As shown in Figure 3(c), the user terminal 2 displays a user-specific screen 201, including a daily report input completion display 217, instead of the daily report input button 215. In other words, in this embodiment, operating the confirmation completion button 224 (Figure 4) corresponds to the clock-out report operation.

Furthermore, if a user is late or otherwise fails to press the clock-in button 214 by the scheduled start time of work, an error message 218 will be displayed on the user-specific screen 201 on the user terminal 2 instead of the clock-in button 214, as shown in Figure 2(d). This prevents the user from pressing the clock-in button 214 (i.e., reporting their attendance). In this case, the user reports the situation to the administrator by telephone or other means. When the administrator receives the report from the user and performs the attendance processing operation described later on the administrator terminal 4, the user -specific screen 201 shown in Figure 2(b) will be displayed on the user terminal 2.

Thus, users who have not reported their attendance despite being late for work (hereinafter referred to as "latecomers") are required to report to their supervisor. This requirement is in place so that supervisors can quickly understand the user's situation and take necessary measures.

Here, users may work individually or as part of a group. Furthermore, in group work, it may suffice for one user to act as a representative and submit a single report for all users' attendance and departure times.

Therefore, in this embodiment, when working in a group, if a single user (hereinafter referred to as the "representative") selects to submit a bulk report, instead of the user-specific screen 201 shown in Figure 2, the representative's user terminal 2 displays a user-specific screen for the representative (hereinafter also referred to as the "representative's screen"), and the user terminals 2 of users other than the representative display a user-specific screen for members (hereinafter also referred to as the "member's screen").

Figure 5(a) shows an example of a screen for the representative only. The representative-only screen 204 shown in Figure 5(a) is almost identical to the user-only screen 201 shown in Figure 2(a), but it includes a batch attendance button 244 instead of the attendance button 214. When the batch attendance button 244 is pressed, the batch attendance screen (selection screen) is displayed on the representative's user terminal 2.

Figure 6 shows an example of a group attendance screen. The group attendance screen 205 in Figure 6 displays a list of usernames of the users who make up the group, with a checkbox 251 next to each username. The checkbox 251 is checked by default, meaning all assigned users are selected. The representative confirms that all users are present and unchecks the boxes for any absent (late) users. Then, when the attendance button 252 (second operation button) is pressed on the group attendance screen 205, an attendance signal is sent to the management server 3 along with the location information of the representative's user terminal 2. This results in an attendance report being submitted for at least one assigned user selected on the group attendance screen (with a checked checkbox 251). In other words, in this embodiment, pressing the attendance button 214 or the attendance button 252 corresponds to the attendance report operation.

Subsequently, when the batch attendance button 244 shown in Figure 5(a) is operated again, the batch attendance screen is displayed again on the user terminal 2. This screen displays a list of usernames of assigned users who were not selected in the previous operation (i.e., whose checkboxes 251 were unchecked), along with their checkboxes 251. When the representative operates the attendance button 252, an attendance signal is sent to the management server 3 along with the location information of the representative's user terminal 2, and an attendance report is submitted for at least one assigned user selected on the batch attendance screen.

Furthermore, once all assigned users have completed their attendance reports in this manner, the representative's dedicated screen 204 on the representative's user terminal 2 will display an attendance report completion indicator 246 instead of the batch attendance button 244, as shown in Figure 5(b).

Furthermore, if the option for a representative to submit a bulk report is selected, the representative is not prohibited from submitting an attendance report even if an employee is late. The representative can submit the attendance report by pressing the attendance button 252. This is because, even if an employee is late, the representative can understand the situation and take appropriate action on behalf of the administrator.

Furthermore, the daily report input button 245 (Figure 5(b)) on the representative-only screen 204 is operated by the representative at the end of their workday. When the daily report input button 245 is operated, a daily report batch input screen (not shown) is displayed on the representative's user terminal 2. This daily report batch input screen is almost identical to the daily report input screen 202 shown in Figure 3, but differs in that it allows the completion time to be entered for each of the assigned users constituting the group. When the representative enters the completion time for each assigned user on this daily report batch input screen and operates the button (not shown) to the confirmation screen, a daily report confirmation screen (not shown) is displayed. When the confirmation complete button (not shown) is operated on this daily report confirmation screen (i.e., the clock-out report operation is performed), a predetermined clock-out signal is sent to the management server 3 along with the location information of the representative's user terminal 2, and the daily report input completion display 247 is displayed on the representative-only screen 204 on the representative's user terminal 2, as shown in Figure 5(c).

Figure 7 shows an example of a member-only screen displayed on user terminal 2 for users other than the representative. The member-only screen 206 shown in Figure 7 includes a basic information section 211 related to work, a common contact section 212, and an individual contact section 213. However, it does not include a clock-in button or a daily report input button, preventing members from reporting their attendance or departure times themselves.

Referring to Figure 1, the administrator terminal 4 is installed, for example, in a security company acting as the administrator, and comprises a communication unit 41, a control unit 42, a display unit (administrator-side display unit) 43, an input unit 44, and a storage unit 45.

The communication unit 41 is a communication interface for communicating with the management server 3. The display unit 43 displays various information, and various web pages are displayed here based on various signals provided by the management server 3. In this embodiment, when the administrator successfully logs in on the web page login screen, the display unit 43 of the administrator terminal 4 displays the business registration screen (Figure 9) and the business list screen (Figure 10), etc., as described later.

Furthermore, the management server 3 comprises 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 the functions of the control unit 33, and is composed of RAM (Random Access Memory), ROM (Read Only Memory), etc. The databases stored in the storage unit 32 include the user database 32a, client database 32b, and business database 32c, which will be described later.

The control unit 33 controls the overall operation of the management server 3 by executing programs stored in the storage unit 32, and is composed of a CPU (Central Processing Unit) and the like. The control unit 33 also includes a site provision unit 33a and a record control unit 33b, which are activated and executed by programs stored in the storage unit 32.

The site provision 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 and 43 of the user terminal 2 and the administrator terminal 4, and accepting input operations performed on those web pages.

For example, when the site provider unit 33a receives an access request from the user terminal 2, it sends the website login screen to the user terminal 2, and the user terminal 2 displays the login screen on the display unit 23a. Furthermore, upon successful authentication, the site provider unit 33a sends the user-specific screen or other relevant information from the website to the user terminal 2, and the user terminal 2 displays the aforementioned user-specific screen or other relevant information on the display unit 23a.

Similarly, when access is received from the administrator terminal 4, the site provision unit 33a provides the website login screen to the administrator terminal 4, and the administrator terminal 4 displays the provided login screen on the display unit 43. Furthermore, upon successful authentication, the site provision unit 33a, in response to a request from the administrator via the administrator terminal 4, transmits the website's business registration screen (Figure 9), etc., to the administrator terminal 4, and the administrator terminal 4 displays the business registration screen, etc., on the display unit 43.

The recording control unit 33b, for example, when it receives attendance signals and departure signals from the user terminal 2, records the start and end times of work, the location information of the user terminal 2, attendance flags, etc., in the storage unit 32. Further details will be described later.

The user database 32a records user information such as user ID, login ID, password, name, and address, with each entry associated with the other.

The client database 32b records client information such as client ID, name, address, and the names of the first to Nth work sites, with each site being associated with the other. A "work site" refers to the location where the user is dispatched to perform their duties.

Figure 8 schematically shows an example of the data structure of the business database 32c. The business database 32c stores information related to each business requested by the client, including the "business code," "client ID," "site name," "start time," "scheduled start time," "common contact information," "bulk report selection," and "assigned user." The information for the "assigned user" includes the "user ID," "individual contact information," "start time," "end time," "location information at arrival," "location information at departure," and "attendance" information. Furthermore, multiple users may be assigned to a single business; in such cases, information for multiple "assigned users" is associated and recorded for that single business.

In this embodiment, the "Batch Report Selection" data area records a flag (selection flag) for determining whether batch reporting is selected, as selection information indicating whether batch reporting is selected.

Furthermore, the "Attendance" data area records attendance information indicating whether a user is at work. This includes a flag (attendance flag) used to determine whether a user is present. The attendance flag is stored when a user reports attendance during the business management process described later, or when an administrator performs the attendance processing operation described later.

Figure 9 shows an example of the task registration screen 401 displayed on the administrator terminal 4. When a client requests a task, the administrator (a representative of the security company) enters and selects the necessary information on the task registration screen 401 displayed on the administrator terminal 4 to register the task. The data entered and selected in this way is recorded in the respective data areas of the task database 32c shown in Figure 8.

More specifically, the task registration screen 401 shown in Figure 9 includes a client selection field 411 for selecting the client, a site name input field 412 for selecting the site name, a date input field 413 for entering the date, a start time input field 414 for entering the start time of the assigned user's work, a scheduled start time input field 415 for entering the scheduled start time of the task, a contact information input field 416 for entering common contact information, a selection box 417 for selecting bulk reporting, and an assigned user registration field 418 for registering the assigned user.

The client ID and site name of the client selected in the client selection field 411 and the site name input field 412 are recorded in the business database 32c as "Client ID" and "Site Name," respectively. Similarly, the date, start time, and scheduled start time entered in the date input field 413, the start time input field 415, and the scheduled start time input field 415 are recorded in the business database 32c as "Date," "Scheduled Start Time," and "Start Time," respectively.

The contact information input field 416 is used to enter all contact information for all assigned users. The contact information entered in the contact information input field 416 is recorded in the business database 32c as "common contact information." This common contact information is then displayed in the contact information field 212 on the user-specific screen 201 (204, 206).

The selection box 417 allows you to choose whether or not the representative will submit attendance and departure reports for all assigned users in a batch. Selecting (checking) selection box 417 selects batch reporting, and a selection flag is recorded in the batch reporting selection data area of the business database 32c. Note that batch reporting is only available when there are multiple assigned users; it cannot be selected when there is only one assigned user.

The user registration field 418 includes a user selection field 419 for selecting the assigned user and a contact information input field 420. The contact information input field 420 allows for individual contact information to be entered for the assigned user. In the example shown in Figure 9, three users are selected as the first, second, and third assigned users (User 1, User 2, and User 3). Even when multiple users are selected as assigned users, or even when only one user is selected, the first assigned user is automatically set as the representative.

The user ID of the user selected in the user selection field 419 is recorded in the business database 32c as "User ID," and the individual contact information entered in the contact information input field 420 is recorded in the business database 32c as "Individual Contact Information." This individual contact information is then displayed in the individual contact information field 213 on the user-specific screen 201 (204, 206).

Here, individual contact information entered in the contact information input field 420 is reported only to the user in charge. For example, the unlock code required to access the site can be entered as an individual contact item for the first user in charge (representative), ensuring that this information is reported only to the representative. On the other hand, information that should be shared with all users in charge can be entered as a common contact item in the contact information input field 416, ensuring that all users are notified. For example, in the example shown in Figure 9, "unlock code 12345" is entered as an individual contact item for the first user in charge, who is the representative.

Figure 10 shows an example of a task list screen displayed on the administrator terminal 4. The task list screen 403 shown in Figure 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 and client ID).
On this task list screen 403, administrators can check the site name, the assigned user's start time, the scheduled start time of the task, the representative's name, and the assigned user's attendance status for each task.

More specifically, the task list screen 403 displays the "Site Name," "Date," "Start Time," "Scheduled Start Time," and "Representative Name," which are read from the task database 32c. The "Attendance Status" indicates the attendance status of the assigned users. In this embodiment, the status display 431 shows the number of assigned users and the number of assigned users who have already reported attendance, linked together. For example, "2/3" indicates that out of three assigned users, two have reported attendance (attendance reported), and one has not reported attendance (attendance not reported).

In this embodiment, whether or not a user has already reported to work is determined by whether or not a work attendance flag is recorded in the business database 32c corresponding to that user.

Next, an example of the business management process executed by the management system 1 will be explained. Figure 11 is a flowchart showing the flow of the business management process executed on the management server 3. This business management process starts when any user responsible for the work on that day successfully logs in to their individual screen, and is executed by the control unit 33 of the management server 3 based on a predetermined program.

In the business management process, first, a user-specific screen including a basic information field 211, a contact information field 213, and an individual contact information field 213 is displayed on the user terminal 2 held by the user (S1). Basic information 211, contact information field 213, and individual contact information field 213 are respectively read from the business database 32c and displayed.

Next, it is determined whether bulk reporting is selected for the tasks assigned to the user (S2). If bulk reporting is not selected (S2: NO), the individual management process is executed (S3). On the other hand, if bulk reporting is selected (S2: YES), it is determined whether the user is the representative (S4). If the user is the representative (S4: YES), the bulk reporting management process is executed (S5). On the other hand, if the user is not the representative (S4: NO), the process is terminated.

Next, the individual management process executed in S3 of Figure 11 will be explained with reference to the flowchart in Figure 12.

In the individual user management process, first, it is determined whether the start time for work has passed (S11). If the start time for work has passed (S11: YES), it is determined whether the user has already left work (S12). This determination can be made, for example, by checking whether the end time is recorded in the business database 32c. If the user has not left work (S12: NO), it is determined whether the user has already clocked in (S13). As described above, in this embodiment, the determination of whether the user has already clocked in is made by checking whether the clocked-in flag is recorded in the business database 32c.

If the user has not yet reported for work (S13: NO), it is determined whether the scheduled start time has elapsed (S14). If the scheduled start time has not elapsed (S14: NO), as shown in Figure 3(a), the user terminal 2 displays the attendance button 214 (first operation button) and the daily report input button 215 (S15), and it is determined whether the attendance button 214 was operated, i.e., whether an attendance signal was received from the user terminal 2 (S16).

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 user terminal 2 is obtained from user terminal 2. Furthermore, the scheduled start time and the location information recorded in the business database 32c are recorded in the business database 32c as the start time (work start time) and clock-in location information, respectively, in association with the user, and a clock-in flag is recorded (S17). Next, as shown in Figure 2(b), the clock-in report completion display 216 and the daily report input button 215 are displayed on user terminal 2 (S18). After that, it is determined whether or not 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.

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

Subsequently, when the user operates button 223 to access the confirmation screen, the user terminal 2 displays a daily report confirmation screen 203 as shown in Figure 4 (S21). It then determines whether the confirmation completion button 224 was operated on the daily report confirmation screen 203 (i.e., whether a clock-out signal was received from the user terminal 2) (S22).

If the confirmation complete button 224 is not pressed (S22: NO), the system waits until the confirmation complete button 224 is pressed. When the confirmation complete button 224 is pressed (S22: YES), the system obtains the location information of the user terminal 2 from the user terminal 2. The system also records the location information and the end time entered on the daily report input screen 202 in the business database 32c as clock-out location information and end time (work end time), associated with the user (S23). Subsequently, as shown in Figure 3(c), the system displays the daily report input completion indicator 217 on the user-specific screen 201 on the user terminal 2 (S24), and the process ends.

On the other hand, if the start time for work has not yet passed in S11 (S11: NO), the system waits until the start time for work arrives. This prevents users from reporting their attendance before the start time.

Furthermore, if the user has already clocked out in S12 (S13: YES), the user terminal 2 will display a clock-in completion indicator 216 and a daily report entry completion indicator 217, as shown in Figure 3(c).

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

If error message 218 is displayed as shown here, the user should report the situation to the administrator by telephone or other means. Upon receiving the situation report, the administrator will perform the following attendance processing operation on the administrator terminal 4.

Specifically, in the task list screen 403 shown in Figure 10, when the administrator operates (clicks) any of the status indicators 431, the management server 3 displays the attendance status screen on the administrator terminal 4. Figure 13 shows an example of the attendance status screen displayed on the administrator terminal 4 when the status indicator 431 ("2/3") for the third task from the top in Figure 10 is operated.

As shown in Figure 13, this attendance status screen displays a list of the names (organizations) of the users assigned to that task, along with the status and location information of each assigned user.

In this embodiment, if the assigned user has already reported to work (i.e., the attendance flag is recorded in the work database 32c), the status field 441 displays the word "Reported," and the location information field 442 displays the location information recorded in the work database 32c at the time of arrival. On the other hand, for assigned users who have not yet reported to work, both the status field 441 and the location information field 442 are blank if it is before the scheduled start time. However, after the scheduled start time, the status field 441 displays an indication that attendance reporting is prohibited (in the example in Figure 13, the word "Locked"). This allows the administrator to check which employees have reported to work and which are late.

Furthermore, in the task list screen 403 shown in Figure 10, when the administrator operates any of the daily report editing buttons 432, the management server 3 displays the daily report editing screen on the administrator terminal 4. Figure 14 shows an example of the daily report editing screen displayed on the administrator terminal 4 when the daily report editing button 432 for the third task from the top in Figure 10 is operated. As shown in Figure 14, the daily report editing screen displays a start time input field 451 corresponding to the name of each assigned user. When the administrator enters the start time in the start time input field 451 for a latecomer and operates the registration button 452, the management server 3 records the start time as the start time in the task database 32c, associated with that user.

Furthermore, when an administrator selects a task on the task list screen 403 shown in Figure 10 (in this case, by checking the checkbox 432 corresponding to the task) and operates the attendance processing button 433, the management server 3 displays the attendance processing screen on the administrator terminal 4. Figure 15 shows an example of the attendance processing screen. This attendance processing screen displays a list of names (employees) of users who have not yet reported for the selected task, and the administrator can select a user by checking the checkbox 461. When the administrator selects a user (i.e., checks the checkbox 461 for the relevant user) and operates the attendance processing button 462, the management server 3 records an attendance flag in the task database 32c associated with the selected user, and the user is processed as having reported for work.

As described above, when the attendance flag is recorded in the business database 32c through the administrator's attendance processing operation, in S26, it is determined that the user has already attended attendance (S26: YES), and the process proceeds to S18.

Next, the batch reporting management process executed in S5 of Figure 11 will be explained with reference to the flowchart in Figure 16. This batch reporting management process first determines whether the start time for work has elapsed (S31). If the start time for work has not elapsed (S31: NO), the system waits until the start time for work arrives. On the other hand, if the start time for work has elapsed (S31: YES), the system determines whether the employee has already left work (S32).

If the user has not yet clocked out (S32: NO), the system determines whether all assigned users have clocked in (S33). If none have clocked in (S33: NO), the system displays the batch clock-in button 244 and the daily report input button 245 on the user terminal 2, as shown in Figure 5(a) (S34), and determines whether the batch clock-in button 244 has been operated (S35). If the batch clock-in button 244 is not operated (S35: NO), the system waits until the batch clock-in button 244 is operated.

On the other hand, when the batch attendance button 244 is operated (S35: YES), the batch attendance screen 205, as shown in Figure 6, is displayed on the user terminal 2 (S36). As described above, the batch attendance screen 205 displays a list of assigned users who have not yet reported to work, along with the attendance button 252 (the second operation button). Next, it is determined whether or not the attendance button 252 has been operated, that is, whether or not an attendance signal has been received from the user terminal 2 (S37).

If the clock-in button 252 is not pressed (S37: NO), the system waits until the clock-in button 252 is pressed. If the clock-in button 252 is pressed (S37: YES), the system acquires the location information of the user terminal 2 and records this location information in the business database 32c, corresponding to at least one (one or more) assigned users (hereinafter referred to as "selected users") selected on the batch clock-in screen (S38). Next, the system determines whether the scheduled start time has elapsed (S39). If the scheduled start time has not elapsed (S39: NO), the system records the scheduled start time recorded in the business database 32c as the start time, corresponding to the selected user, and records the clock-in flag (S40), then returns to S33.

On the other hand, if the scheduled start time has elapsed (S39: NO), the system adjusts to the selected user, rounds the current time up to a predetermined time unit (e.g., 30-minute increments), records the start time in the business database 32c, records the attendance flag (S41), and returns to S33.

On the other hand, if all assigned users have reported to work in S33 (S33: YES), the user terminal 2 displays a "Report Report Complete" indicator 246 and a daily report input button 125, as shown in Figure 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 user terminal 2 displays a daily report registration screen (not shown) (S44). The user performs the same operations on this daily report registration screen as on the daily report input screen 202 displayed in S20 above.

Specifically, the user enters the end time (work completion time) for each assigned user. Then, when the user operates the button (not shown) to proceed to the confirmation screen on the daily report registration screen, the daily report confirmation screen (confirmation complete button (second operation button)) is displayed on the user terminal 2 (S45), and it is determined whether the confirmation complete button was operated (i.e., whether a clock-out signal was received from the user terminal 2) (S46). If the confirmation complete button is not operated (S46: NO), the system waits until it is operated. If the confirmation complete button is operated (S46: YES), the location information of the user terminal 2 is acquired, associated with each assigned user, and recorded in the work database 32c as clock-out location information. The end time entered on the daily report registration screen in S41 is also recorded as the end time (S47).

Subsequently, as shown in Figure 5(c), the user terminal 2 displays a daily report input completion indicator 247 (S48), and the process is terminated.

On the other hand, if it is determined in S32 that the employee has already left work (S31), the attendance report completion indicator 246 and the daily report input completion indicator 247 are displayed on the user terminal 2, as shown in Figure 5(c), and the process is terminated.

Next, the tardiness detection process executed on the management server 3 will be explained with reference to the flowchart shown in Figure 17. This tardiness detection process determines whether or not there are latecomers for each task, and if there are, 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 inverting the colors to black and white.

This lateness determination process is executed by the control unit 33 based on a predetermined program for each task registered in the task database 32c. First, it determines whether the scheduled start time for the task has elapsed (S51). If it has not elapsed (S51: NO), the process is terminated.

On the other hand, if the scheduled start time has elapsed (S51: YES), the variable i is set to 1 (S52), and it is determined whether the i-th assigned user has already reported to work (whether the attendance flag is recorded in the work database 32c) (S53). If it is determined that the user has already reported to work (S53: YES), it is determined whether the processing has been completed for all assigned users (S54). If it has been completed (S54: YES), the display mode on the work list screen 403 is set to normal display mode (normal display mode is maintained), and the process is terminated.

On the other hand, if processing is not complete for all assigned users (S54: NO), add 1 to the value of variable i (S56), and return to S53.

Furthermore, if it is determined in S53 that the employee has not yet reported for work (S53: NO), the display mode on the work list screen 403 is set to warning display mode (and the warning display mode is maintained) (S57), and the process is terminated.

As a result, if even one person is late for any task, the display mode on the task list screen 403 is set to warning display mode, and a warning is displayed on the task list screen 403 indicating the relevant task.

Furthermore, in this embodiment, when any of the daily report output buttons 435 are operated on the task list screen 403 in Figure 10, the management server 3 refers to the storage unit 32 (here, the user database 32a, the client database 32b, and the task database 32c) and displays the daily report screen on the display unit 43 of the administrator terminal 4. Figure 18 is an example of a daily report screen. In addition to the "client name,""sitename," and "date," the daily report screen displays the "start time" (task start time) and "end time" (task end time) associated with each of the assigned users, and the administrator can print the daily report screen or send it to the client.

Thus, in the business management system according to this embodiment, if a user reports their attendance before the scheduled start time, the pre-set scheduled start time of the task is recorded in the storage unit 32 as the user's work start time, making it easy to create daily reports.

Furthermore, by prohibiting latecomers from submitting attendance reports, we encourage them to report to their supervisors via telephone or other means, allowing supervisors to quickly grasp the situation regarding lateness.

On the other hand, if a latecomer occurs when bulk reporting is selected, the responsibility for assessing the situation can be entrusted to a representative, thereby reducing the burden on administrators. Furthermore, since users simply perform the attendance report operation, the start time of work is recorded as the current time advanced by a predetermined amount, eliminating the need to manually enter the start time. In addition, administrators can input and edit the start time on the daily report editing screen (Figure 14), allowing for flexible responses according to the situation and circumstances.

Although embodiments of the present invention have been described above with reference to the accompanying drawings, the present invention is not limited to these embodiments, and various modifications and alterations are possible without departing from the scope of the present invention.

For example, in the above embodiment, the determination of whether a user has already reported to work was made by checking whether a work attendance flag is recorded in the storage unit 32 (business database 32c) in association with that user. Alternatively, this could be done by checking whether a start time is recorded in the storage unit 32 (business database 32c) in association with that user.

Furthermore, in the above embodiment, the location information of the user terminal 2 is recorded in the business database 32c when attendance reports or departure reports are submitted. However, in addition to the location information, the time when attendance reports or departure reports were submitted (attendance report time and departure report time) may also be recorded in the business database 32c.

In the above embodiment, the end time entered on the daily report registration screen is recorded in the business database 32c. However, restrictions may be placed on the end time that can be entered on the daily report registration screen. For example, the control unit 33 of the management server 3 may determine whether the end time entered on the daily report registration screen falls within a predetermined time frame before or after the current time (e.g., 30 minutes before or after). If it falls within the predetermined time frame before or after the current time, the system may accept the input of the end time, associate it with the user, and record it in the business database 32c. On the other hand, if it falls outside the predetermined time frame before or after the current time, the system may not accept the input of the end time and may display an error message on the user terminal 2.

Furthermore, in the above embodiment, the representative entered the end time for each assigned user on the daily report registration screen (not shown) displayed at S44 in Figure 16. Alternatively, it is possible to enable the selection of a bulk clock-out report on the same daily report registration screen. If the bulk clock-out report is selected, the end time entered for the representative will be reflected as the end time for all assigned users (i.e., the end time entered for the representative will be recorded in the database 32c as the end time for all assigned users). In this case, the representative only needs to enter their own end time, omitting the input of end times for other assigned users. It is preferable to provide a bulk clock-out report selection box on the daily report registration screen, allowing the representative to select the bulk clock-out report by checking the box.

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 unit 25 Control unit (user-side control unit)
31. Communications Unit (Server-side communications unit)
32 Storage Unit 33 Control Unit (Server-side control unit)
41. Communications Department (Administrative Communications Department)
43 Display section (Administrator side display section)
205. Batch attendance screen (selection screen)
214 Clock-in button (first operation button)
252 Clock-in button (second operation button)

Claims (8)

A user terminal that accepts input from users regarding attendance reporting operations,
An administrator terminal that accepts the administrator's input of the scheduled start time and the option to submit a bulk report,
The system comprises a management server capable of data communication with the user terminal and the administrator terminal,
The aforementioned user terminal is
User-side control unit,
A user-side communication unit that communicates with the aforementioned management server,
A location information acquisition unit that acquires the location information of the device,
It has,
When the user-side control unit receives input for the attendance reporting operation, it transmits the attendance signal and the location information acquired by the location information acquisition unit to the management server via the user-side communication unit.
The aforementioned management server
Server-side control unit,
A server-side communication unit that communicates between the user terminal and the administrator terminal,
A database that records the aforementioned scheduled start time entered by the administrator and selection information indicating whether or not the administrator has selected the aforementioned bulk report, in association with each other.
It has,
The server-side control unit,
If the aforementioned selection information indicates no selection, after the scheduled start time has elapsed, the user will be prohibited from entering the attendance report operation.
If the aforementioned selection information indicates that a selection has been made, the user is permitted to input the attendance report operation even after the scheduled start time has elapsed.
If the attendance signal is received from the user terminal before the scheduled start time has elapsed, the scheduled start time and location information are recorded in the database as the work start time and attendance location information, respectively.
A business management system that, upon receiving the attendance signal from the user terminal after the scheduled start time has elapsed, records the location information as attendance location information in the database and records a time advanced by a predetermined amount from the current time as the start time of work in the database. If the selection information indicates that a selection has been made, the server-side control unit records the work start time and the location information at the time of arrival in the database, associated with each of the at least one users selected by the user, according to claim 1 of the business management system. The user terminal further comprises a user-side display unit,
The business management system according to claim 2, wherein the server-side control unit, when the selection information indicates a selection, causes the user-side display unit to display a selection screen, and records the business start time and the location information at the time of arrival in the database in association with each of the at least one user selected on the selection screen. The administrator terminal comprises an administrator-side communication unit that communicates with the management server, and an administrator-side display unit.
The business management system according to claim 1, wherein the server-side control unit determines whether or not there are any latecomers, and if it determines that there are latecomers, it displays a warning on the administrator-side display unit. The user terminal further accepts input of the end time and the operation to report clocking out.
When the user-side control unit receives input for the clock-out report operation, it sends a clock-out signal to the management server along with the end time.
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 end time in the database in association with the user. The business management system according to claim 5, wherein, if the end time entered by the user falls within a predetermined time frame before or after the current time, the server-side control unit records the end time in the database. A control unit that displays a task registration screen on the administrator's screen for administrators to input their start time and scheduled start time and select batch reporting,
A database that records the aforementioned start time and scheduled start time entered by the administrator, and selection information indicating whether or not the administrator has selected the bulk reporting option, in association with each other.
Equipped with,
The control unit,
If the selection information indicates no selection, the first operation button is displayed on the user terminal after the start time but before the scheduled start time has elapsed, and a predetermined error message is displayed on the user terminal in place of the first operation button after the scheduled start time has elapsed.
If the selection information indicates that a selection has been made, after the start time has elapsed, regardless of whether the scheduled start time has elapsed or not, the second operation button will be displayed on the user terminal.
If the user operates the first or second operation button before the scheduled start time has elapsed, the system obtains the user terminal's location information from the user terminal and records the scheduled start time and location information in the database as the work start time and location information at the time of arrival, respectively.
When the second operation button is operated after the scheduled start time has elapsed, the business management server obtains the location information of the user terminal from the user terminal, records the location information as the location information at the time of arrival in the database, and records a time advanced by a predetermined amount from the current time as the start time of work in the database. On the computer,
The steps include displaying a task registration screen on the administrator's terminal for the administrator to select bulk reporting, and recording selection information in the database indicating whether the administrator has selected bulk reporting,
The steps include determining whether a batch report is selected based on the aforementioned selection information,
If it is determined that bulk reporting is not selected, the next step is to determine whether or not the start time for work has passed.
If the aforementioned start time for work has elapsed, the step is to determine whether or not it is before the scheduled start time.
If it is determined that the scheduled start time has not yet been determined, the first operation button is displayed on the user terminal held by the user.
If it is determined that the start time has not yet arrived, the user terminal is to display a predetermined error message instead of the operation button.
If it is determined that batch reporting is selected, the system determines whether or not the start time for work has elapsed, and if it is determined that the start time for work has elapsed , it displays a second operation button on the user terminal.
If the first or second operation button is operated before the scheduled start time has elapsed, the location information of the user terminal is acquired, and the scheduled start time and the location information are recorded in the database as the work start time and the location information at the time of arrival, respectively.
A business management program that, when the second operation button is operated after the scheduled start time has elapsed, performs the steps of acquiring the location information of the user terminal, recording the location information in the database as the location information at the time of arrival at work, and recording a time advanced by a predetermined amount from the current time as the start time of work in the database.