Information processing system, information processing method, and program

Abstract

To provide an information processing system, an information processing method, and a program capable of reducing processing loads in work management.SOLUTION: An information processing system for managing work information according to one embodiment of the present invention comprises a determination unit, a notification unit, and an execution unit. The determination unit determines whether or not there is notification required information defined as information to be notified to an employee, in response to input of identification information that identifies the employee. The notification unit notifies the employee of a determination result made by the determination unit and confirmation information for confirming whether or not the employee desires to remain logged in to the information processing system. The execution unit generates a main menu screen for using the information processing system if an input indicating the desire to remain logged in to the information processing system is received in response to the confirmation information.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing method, and a program applicable to the business management of employees.

Background Art

[0002] In the attendance and departure management system described in Patent Document 1, information is distributed and processed by an information collection and distribution device such as a dispatcher and a plurality of write / read control devices such as a page server. As a result, it becomes possible to perform authentication processing based on an ID from an input display means such as a touch panel in a short time. As a result, even when information from many employees concentrates at the time of attendance, processing can be performed quickly, and the attendance time can be registered accurately.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a system for performing various business management such as management of employee attendance and departure, a technique capable of reducing the processing load is required.

[0005] In view of the above circumstances, an object of the present invention is to provide an information processing system, an information processing method, and a program capable of reducing the processing load in business management.

Means for Solving the Problems

[0006] To achieve the above object, an information processing system according to an aspect of the present invention is an information processing system for managing business information, and includes a determination unit, a notification unit, and an execution unit. The determination unit determines the presence or absence of information to be notified, which is defined as information to be notified to the employee, in response to the input of identification information for identifying the employee. The notification unit notifies the employee of the determination result by the determination unit and confirmation information for confirming whether the employee wishes to be in a logged-in state to the information processing system. When there is an input indicating that the employee wishes to be in a logged-in state for the confirmation information, the execution unit generates a main menu screen for using the information processing system.

[0007] The main menu screen may include a display area where the information to be notified is displayed, and a display area where the business information not defined as the information to be notified is displayed.

[0008] The determination unit may determine the presence or absence of the information to be notified in response to the input of the identification information via a login screen for logging in to the information processing system.

[0009] The information processing system further includes a mode setting unit that switches and sets between a login confirmation mode in which each of the determination by the determination unit of the presence or absence of the information to be notified, the notification by the notification unit of the determination result and the confirmation information, and the generation of the main menu screen by the execution unit in response to the input indicating that the employee wishes to be in a logged-in state is executed, and a non-login confirmation mode in which each of the determination by the determination unit of the presence or absence of the information to be notified, the notification by the notification unit of the determination result and the confirmation information, and the generation of the main menu screen by the execution unit in response to the input indicating that the employee wishes to be in a logged-in state is not executed.

[0010] The mode setting unit may switch and set between the login confirmation mode and the non-login confirmation mode based on the status of the processing load of the information processing system.

[0011] When the processing load of the information processing system is relatively high, the mode setting unit may set the login confirmation mode, and when the processing load of the information processing system is relatively low, the mode setting unit may set the unconfirmed login mode.

[0012] The mode setting unit may set the login confirmation mode during a predetermined time zone and set the unconfirmed login mode during other time zones.

[0013] The notification unit may notify the employee of the time required to generate the main menu screen.

[0014] When it is determined based on the operation history information of the employee on the main menu screen that there is information indicating that the display on the main menu screen is unnecessary, or when an instruction to omit the display is input from the employee, the execution unit may generate a simplified version of the main menu image in which a part of the information displayed on the main menu screen is omitted.

[0015] When an instruction to display the information omitted on the simplified version of the main menu screen is input from the employee, the execution unit may display the information targeted by the instruction.

[0016] The main menu screen may include information on unprocessed tasks that the employee needs to complete. In this case, the notification unit may notify the employee of the time required to complete the unprocessed tasks.

[0017] An information processing method according to an aspect of the present invention is an information processing method executed by a computer system that manages business information, and includes determining the presence or absence of information to be notified, which is defined as information to be notified to an employee, in response to an input of identification information for identifying the employee. The determination result of the determination and confirmation information for confirming whether the employee desires to be logged in to the computer system are notified to the employee. When there is an input indicating a desire to log in to the computer system with respect to the confirmation information, a main menu screen for using the computer system is generated.

[0018] A program according to one aspect of the present invention is a program that causes a computer system for managing business information to execute the information processing method.

Advantages of the Invention

[0019] As described above, according to the present invention, it is possible to reduce the processing load in business management.

Brief Description of the Drawings

[0020]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

[0021] Hereinafter, embodiments according to the present invention will be described with reference to the drawings.

[0022] [Business Management System] FIG. 1 is a schematic diagram showing a configuration example of a business management system according to an embodiment of the present invention. The business management system 1 can manage business information related to business and perform business management for an organization (group) such as a company.

[0023] In the present disclosure, the business information includes any information related to the business of an organization such as a company. For example, information on any matter related to the business, such as personnel information, employment information, attendance information, budget information, etc., is included in the business information. Also, information related to the business of each employee 2 belonging to the organization is included in the business information.

[0024] By managing these business information, the present business management system 1 can perform various business management such as personnel management, employment management, attendance management, budget management, etc. Also, it is possible to execute various procedures related to the business of the employee 2.

[0025] Also, in the present disclosure, the management of business information does not necessarily mean managing all business information. Managing some of the information included in the business information is also an embodiment of the management of business information according to the present invention. For example, it is also possible to construct a system that manages only the attendance information as an embodiment of the business management system according to the present invention.

[0026] As shown in FIG. 1, the business management system 1 includes a server device 3, a database (DB) 4, and an employee terminal 5.

[0027] The server device 3 and the employee terminal 5 are communicably connected to each other via a network 6. The network 6 is constructed by, for example, the Internet or a wide area communication line network. In addition, any WAN (Wide Area Network), LAN (Local Area Network), etc. may be used, and the protocol for constructing the network 6 is not limited.

[0028] The server device 3 and the employee terminal 5 have the hardware necessary for a computer, such as a processor such as a CPU, GPU, or DSP, a memory such as a ROM or RAM, and a storage device such as an HDD (see FIG. 25). By loading the program according to the present invention stored in the storage unit or the memory into the RAM and executing it by the processor, the information processing method (business management method / login management method) according to the present invention is executed.

[0029] In the present embodiment, an application service (hereinafter referred to as a business management application) capable of performing various business management is provided by the server device 3 and the DB 4. That is, it can be said that the business management system 1 is a system equipped with business software capable of managing business information and performing various business processes.

[0030] The business management application is provided, for example, as a web application. The employee 2 can use this business management application on the web page displayed by the web browser using the employee terminal 5.

[0031] Of course, it is not limited to this, and the business management application may be provided as a native application. In this case, the program of the business management application is downloaded to the employee terminal 5 of the employee 2. In addition, various forms for using the business management application may be adopted.

[0032] In the business management application, various processes related to business management are executed by the server device 3. For example, various processes related to employment management, attendance management, personnel management, budget management, and management operations for any matters related to business content are executed.

[0033] DB4 stores any information related to business operations (business information). For example, it stores employee information such as the names, genders, addresses, and phone numbers of employees, as well as employment information and attendance information related to the salaries paid to each employee, arrivals and departures, vacations, overtime work, etc. In addition, any information related to personnel, budgets, business content, etc. is stored as business information.

[0034] In the example shown in FIG. 1, DB4 is composed of a storage device separate from the server device 3 and is connected to the server device 3. However, it is not limited to this configuration, and DB4 may be composed of the storage unit (see FIG. 25) of the server device 3. Also, a configuration may be adopted in which DB4 is constructed on the network 6 and can be accessed via the network 6.

[0035] In FIG. 1, the server device 3 is schematically illustrated by a computer consisting of one housing. Of course, it is not limited to such a configuration, and various processes related to business operations may be executed by the cooperation of a plurality of server devices having various functions.

[0036] In FIG. 1, three employees 2 are illustrated, but the number of employees 2 who can use this business management application is not limited. Also, in FIG. 1, one of the three employees 2 is illustrated as the administrator 7. The administrator 7 is an example of an employee who has greater authority than the employees 2, and the specific position, etc. is not particularly limited.

[0037] For example, the employee 2 uses the employee terminal 5 to display a login screen for logging in to the business management system 1. Then, a login operation is performed by inputting their employee ID, password, etc. When the personal authentication is successful for the login operation, the business management application becomes available, and it becomes possible to execute various processes related to business operations, such as clocking in and out, applying for paid leave, applying for overtime work, and submitting digitized documents.

[0038] The manager 7 also performs a login operation using the manager terminal 8. When the personal authentication for the login operation is successful, the main business management application becomes available, and it becomes possible to manage various business information such as the attendance status, overtime status, and acquisition status of paid leave of the employees 2 to be managed (for example, subordinates, etc.). Of course, it is also possible to clock in and out of one's own work and make various applications, etc.

[0039] [Login Management] The main business management system 1 can execute the management of the login of each employee 2 to the business management system 1. The main business management system 1 that executes each process for managing the login described below functions as an embodiment of the information processing system according to the present invention.

[0040] Of course, it is also possible to construct, as an embodiment of the information processing system according to the present invention, a system that does not execute business management regarding other matters such as work management and only executes the login management described below.

[0041] In the present disclosure, the state of being logged in to the business management system 1 is regarded as the logged-in state with respect to the business management system 1. Also, the state of not being logged in to the business management system 1 is regarded as the logged-out state with respect to the business management system 1.

[0042] Managing the login of each employee 2 to the business management system 1 includes any management related to login and logout of the business management system 1, such as management of the presence or absence of login (whether it is in the logged-in state), management of whether to continue the logged-in state, and management of canceling the logged-in state (that is, logging out).

[0043] For example, managing the number of employees 2 in the logged-in state and managing the number of employees 2 in the logged-out state are included in the login management according to this technology.

[0044] Also, for example, the operations listed below are included in the login management according to this technology. Notify the employee 2 in the logged-out state to prompt login. Notify the employee 2 in the logged-in state to prompt logout. Notify the employee 2 in the logged-in state to prompt continued logged-in status. Notify the employee 2 in the logged-out state to confirm whether they wish to log in. Notify the employee 2 in the logged-in state to confirm whether they wish to log out. Notify the employee 2 in the logged-in state to confirm whether they wish to continue the logged-in status.

[0045] Also, notifying the employee 2 to confirm whether they wish to be in the logged-in state is included in the login management according to this technology. Note that confirming whether the employee 2 wishes to be in the logged-in state includes both confirming whether the employee 2 in the logged-out state wishes to log in and confirming whether the employee 2 in the logged-in state wishes to continue the logged-in state.

[0046] Of course, the login management is not limited to the case where all of the above-listed examples can be executed. A system capable of executing at least one of the management regarding login and logout for the business management system 1 is a system capable of executing login management.

[0047] Hereinafter, the login management executed by the business management system 1 (server device 3) according to this embodiment will be described.

[0048] [Basic Configuration and Basic Operation of Server Device] As schematically illustrated in FIG. 1, in this embodiment, when the processor of the server device 3 executes a predetermined program, as functional blocks, a determination unit 9, a notification unit 10, and an execution unit 11 are configured. Of course, dedicated hardware such as an IC (integrated circuit) may be used to realize each functional block.

[0049] The program is installed in the server device 3 via various recording media, for example. Alternatively, the installation of the program may be executed via the Internet or the like. The type of the recording media on which the program is recorded is not limited, and any recording media readable by a computer may be used. For example, any non-transitory storage medium readable by a computer may be used.

[0050] FIG. 2 is a flowchart showing the basic operation of login management executed by the server device 3. In response to the input of the employee ID which is identification information for identifying the employee 2, the determination unit 9 determines the presence or absence of the information to be notified which is defined as the information to be notified to the employee 2 (step 101).

[0051] As the information to be notified, for example, it is possible to set notifications of various alerts for the employee 2, notifications for prompting predetermined applications or submissions, notifications of unprocessed processes that the employee 2 needs to complete, and the like. For example, it is possible to set, as the information to be notified, information that the employee 2 is required to preferentially check or process.

[0052] For example, as the information to be notified, it is possible to set notifications of forgetting to punch in for work, notifications of forgetting to punch out for work, notifications for prompting predetermined applications such as overtime applications, notifications for prompting submissions of predetermined documents, and the like.

[0053] Also, as the information to be notified to the administrator 7, notifications indicating that approvals for various applications such as applications related to punching in and out, overtime applications, paid leave applications, etc. from the employee 2 to be managed are unprocessed, notifications indicating that the overtime hours of the employee 2 to be managed are more than a predetermined time, and other alert notifications related to the attendance status of the employee 2 to be managed can be set.

[0054] Of course, the information defined as the information to be notified is not limited, and any information can be set as the information to be notified.

[0055] The notification unit 10 notifies the employee 2 of the determination result by the determination unit 9 and confirmation information for confirming whether the employee 2 wishes to be logged in to the business management system 1 (step 102). In the present embodiment, the notification unit 10 generates a confirmation screen (confirmation image) including the determination result and the confirmation information, and transmits it to the employee terminal 5.

[0056] As the determination result of the determination unit 9, for example, notification information such as "There is notification information to be notified", "There are 5 pieces of notification information", "There is no notification information" is displayed. Of course, it is not limited to such notification information, and the determination result may be notified in any form. For example, the determination result may be output by voice output.

[0057] As confirmation information for confirming whether the employee 2 wishes to be logged in to the business management system 1, for example, notification information such as "Do you want to log in to the system?", "Do you want to continue the logged-in state to the system?" is displayed. Also, notification information for confirming whether the employee does not wish to be in the logged-in state, such as "Do you want to log out of the system?", can be used as the confirmation information according to the present technology.

[0058] The execution unit 11 determines whether there is an input indicating a desire to be logged in to the business management system 1 for the confirmation information (step 103). If there is no input indicating a desire to be logged in to the business management system 1 for the confirmation information (No in step 103), the process ends.

[0059] When there is an input indicating a desire to be logged in to the business management system 1 for the confirmation information (Yes in step 103), the execution unit 11 generates a main menu screen for using the business management system 1.

[0060] FIG. 3 is a schematic diagram showing an example of the main menu screen. The main menu screen shown in FIG. 3 is an example of the main menu screen generated for the administrator 7. Note that the main menu screen is often called the top menu screen.

[0061] As shown in FIG. 3, on the main menu screen 13, the system name "Business Management System" is displayed at the top. On the right side of the "Business Management System", the name of the logged-in employee 2 (hereinafter referred to as the logged-in user) is displayed as "Login Name (Taro Amano)". On the right side of "Login Name (Taro Amano)", a logout button 14 is provided. When the logged-in user wishes to log out, the user clicks the logout button 14. As a result, the business management system 1 enters the logged-out state.

[0062] Below the "Business Management System" on the main menu screen 13, menu buttons 15 are installed. In this embodiment, six menu buttons 15 of "Daily Processing", "Notification Processing", "Monthly Processing", "Ad Hoc Processing", and "Various Analyses" are provided. The logged-in user can execute various procedures (processes) corresponding to each menu by appropriately clicking each menu button 15.

[0063] For example, when each menu button 15 is clicked, an application corresponding to each menu is launched, and various processes related to attendance management such as registration and modification of attendance data, application and approval of overtime work, and confirmation of overtime work hours can be executed. Of course, various other processes can also be executed.

[0064] Below the menu button 15 for "Daily Processing" on the main menu screen 13, a calendar 16 is displayed.

[0065] Below the calendar 16, a manual confirmation area 17 is set. A link to the operation manual is embedded in the text (string) of "Operation Manual" in the manual confirmation area 17, and when "Operation Manual" is clicked, the operation manual is displayed. Also, a link to the screen where the FAQ is displayed is embedded in "FAQ" in the manual confirmation area 17, and when "FAQ" is clicked, the corresponding screen is displayed.

[0066] On the right side of the calendar 16 and the manual confirmation area 17 on the main menu screen 13, a notification information display area 18 is set. In the notification information display area 18, information that the logged-in user is preferentially requested to check and information that the user is requested to process are listed and displayed.

[0067] In this embodiment, three types of information classified as "Bulletin Board", "Notification to You", and "Notification to Administrator" are displayed in the notification information display area 18. The logged-in user can switch and display these three types of information in the notification information display area 18 by selecting each tab of "Bulletin Board", "Notification to You", and "Notification to Administrator".

[0068] In addition, when the logged-in user is not the administrator 7, the tab of "Notification to Administrator" is not provided.

[0069] In the "Bulletin Board", notifications for all employees logged in to the main business management system 1 are displayed. Of course, the "Bulletin Board" may be constructed for each department or section.

[0070] As "Notification to You", notification information for the logged-in employee 2 himself / herself is displayed. The said notification information is an embodiment of the information to be notified shown in FIG. 2, and for example, information defined as information to be notified such as notification information regarding work management is displayed.

[0071] In the "Notification to Administrator", notification information for the administrator 7 is displayed. The said notification information is also an embodiment of the information to be notified shown in FIG. 2. For example, notification information regarding work management of the employee 2 who is under the management of the logged-in user (administrator 7) and other information defined as information to be notified are displayed.

[0072] That is, in the example shown in FIG. 3, the notification information displayed as "Notification to You" and "Notification to Administrator" is an embodiment of the information to be notified to Employee 2 as defined in the present invention. Note that the notification information can also be referred to as notification data.

[0073] As shown in FIG. 3, in this embodiment, as the information to be notified displayed in "Notification to Administrator", "Creation Date", "Creation Time", "Classification", "Occurrence Count", and "Message" are displayed.

[0074] As the "Message", for example, in the notification information where the "Classification" is "Notification", texts such as "There is a notification awaiting approval." are displayed. In the notification information where the "Classification" is "Item to be Confirmed", texts such as "There is an oversight in punching in for work." or "There is an oversight in punching out for work." are displayed. In the notification information where the "Classification" is "Labor Alert", texts such as "This month's overtime hours exceed 45h." are displayed.

[0075] Also, the URL of an application such as attendance management is embedded in the text displayed in the "Message". Therefore, when the logged-in user (Administrator 7) clicks on the text, the application can be launched to execute the process.

[0076] For example, when clicking on "There is a notification awaiting approval.", the notification approval application can be launched to perform the approval process. Also, when clicking on "There is an oversight in punching in for work.", it is possible to correct and input or apply for the work entry and exit times.

[0077] Below the notice information display area 18 of the main menu screen 13, an attendance status display area 19 is provided. In the attendance status display area 19, attendance status information regarding the attendance status of the employee 2 to be managed is displayed. In this embodiment, as the attendance status information, "personal code", "name", "department name", "calendar", "attendance / work type", "shift type", "arrival time", and "departure time" are displayed. By checking the attendance status information, the administrator 7 can check the attendance status of the employee 2 to be managed.

[0078] Below the attendance status display area 19 of the main menu screen 13, a work weekly / monthly report display area 20 is provided. In the work weekly / monthly report display area 20, work weekly / monthly report information regarding the work weekly / monthly report of the logged-in user himself / herself is displayed. In this embodiment, as information indicating the work status on a predetermined working day, "processing date", "day of the week", "calendar", "attendance / work type", "shift type", "arrival time", "departure time", "going-out time", and "return time" are displayed. Also, as information indicating the work status for a predetermined month, "overtime (overtime working hours)", "late-night overtime hours", "time off during work", "late-night time off during work", "predetermined number of days", and "number of working days" are displayed.

[0079] It is also possible to collectively call the attendance status display area 19 and the work weekly / monthly report display area 20 the work information display area. And it is also possible to collectively call the attendance status information displayed in the attendance status display area 19 and the work weekly / monthly report information displayed in the work weekly / monthly report display area 20 work information. Note that in this embodiment, these work information (attendance status information, work weekly / monthly report information) are information not defined as information to be notified.

[0080] As the work information displayed on the main menu screen 13, frequently referred-to attendance / work information such as the attendance status information and work weekly / monthly report information illustrated in FIG. 3 is displayed. Of course, there is no limitation on what work information is to be displayed, and it can be arbitrarily designed.

[0081] The employment information such as the attendance status information and the weekly / monthly work reports exemplified in FIG. 3 is generated by acquiring daily data from DB4 and performing aggregation processing and the like each time. That is, the employment information displayed in the employment information display area is generated by appropriately reading out the employment information and attendance information stored in DB4 and executing aggregation processing and the like.

[0082] FIG. 4 is a schematic diagram showing another example of the employment information displayed on the main menu screen 13. In the example shown in FIG. 4, three types of information are displayed together with a graph.

[0083] In the display area 22 of the "Overtime Information (Monthly Information)", the occurrence ratios of overtime hours (overtime working hours) in December 2023 for the four departments of "Network Department", "Core System Department", "General Affairs Department", and "Facilities Department" are displayed as bar graphs.

[0084] In the display area 23 of the "Attendance Rate", the attendance rates in December 2023 for the four departments of "Network Department", "Core System Department", "General Affairs Department", and "Facilities Department" are displayed as pie charts.

[0085] In the display area 24 of the "Overtime Hours (Annual Information)", the changes in overtime hours from January 2023 to December 2023 for the four departments of "Network Department", "Core System Department", "General Affairs Department", and "Facilities Department" are displayed as line graphs.

[0086] These graphs are also generated by appropriately reading out the employment information and attendance information stored in DB4 and executing aggregation processing and the like. Note that the logged-in user can change the displayed information by appropriately operating the department selection button, period selection button, and deletion button provided in each display area 22 - 24.

[0087] In this way, the main menu screen 13 includes a display area where information to be notified is displayed and a display area where business information not defined as information to be notified is displayed. In other words, it can also be said that the main menu screen 13 includes items where information to be notified is displayed and items where business information not defined as information to be notified is displayed.

[0088] On the main menu screen 13, notification information specific to the logged-in user, such as information prompting the processing of unprocessed data and information prompting business attention, is displayed. Also, various labor management information and the like are displayed on the main menu screen 13. Thereby, efficient business operation becomes possible. For example, when a graph or the like as shown in FIG. 4 is displayed, the administrator 7 can easily grasp various attendance information, enabling efficient management work.

[0089] On the other hand, if the logins from the employees 2 become concentrated, it will impose a large load on the access to the DB4 for displaying the main menu screen 13 and the generation of the main menu screen 13, increasing the processing load of the business management system 1 (server device 3). As a result, waiting times for the display of the main menu screen 13 and the like will occur, deteriorating the efficiency of business operation.

[0090] For example, the employee 2 often logs in to display the main menu screen 13 for the purpose of checking whether there is any notification information (information to be notified) displayed in "Notifications for You" and "Notifications for Administrator" shown in FIG. 3. For example, the generation process of the notification information can be executed in the background to suppress the processing load. However, in order to generate the employment information (attendance status information, weekly / monthly employment reports, three graphs) shown in FIGS. 3 and 4, it is necessary to execute access to the DB4 and aggregation processing etc. each time, imposing a high processing load.

[0091] In this embodiment, as shown in FIG. 2, the determination result of the presence or absence of notification information (information to be notified) and confirmation information for confirming whether or not to desire a logged-in state are notified. Thereby, it becomes possible to prompt an employee 2 who logs in to check the notification information and displays the main menu screen 13 not to log in when there is no notification information.

[0092] That is, it becomes possible to suppress an action such as logging in first to check whether there is notification information, and it becomes possible to suppress the concentration of logins. It becomes possible to reduce the processing load on the business management system 1 (server device 3). Thereby, it becomes possible to appropriately operate business management.

[0093] Hereinafter, a detailed embodiment of the business management system 1 capable of executing login management according to the present technology shown in FIG. 2 will be described.

[0094] (First Embodiment) FIG. 5 is a block diagram showing a functional configuration example of the server device 3 according to the first embodiment. As shown in FIG. 5, in this embodiment, when a processor of the server device 3 executes a predetermined program, as functional blocks, a personal authentication unit 26, a notification information generation unit 27, a notification information acquisition unit 28, a login state confirmation unit 29, and a main menu screen generation unit 30 are configured.

[0095] FIGS. 6 to 8 are schematic diagrams showing an example of business information stored in the DB 4. As shown in FIG. 6, in this embodiment, "personal master" is stored in the DB 4. The "personal master" is created for each employee 2 (including the administrator 7). The "personal master" is generated as basic data and becomes data included in employee information regarding each employee.

[0096] As shown in FIG. 6, the "personal master" includes the following information. "Personal code"... an ID (employee ID) that can identify the employee 2. For example, it is composed of 10 digits or the like. Of course, any other form of data may be used as the "personal code". "Name"... The name of Employee 2. "Password"... The password required for login. "Department Code"... An ID that can identify the department. "Supervisor Code"... The personal code of the supervisor. "Administrator Flag"... A flag indicating whether the user is an administrator.

[0097] Also, as shown in FIG. 7, the "Notification Information Generation Setting Information" is stored in the DB4. The "Notification Information Generation Setting Information" is information set to generate notification information, and the generation conditions of the notification information are retained.

[0098] As shown in FIG. 7, the "Notification Information Generation Setting Information" includes the following information. "Notification Name"... The name used when notifying as notification information. For example, "Forgotten Attendance Punch", "Forgotten Overtime Application", "Pending Approval Submission", etc. are retained. "Extraction Conditions"... Conditions for extracting as notification information. For example, there is a forgotten attendance punch. There is a forgotten departure punch. There is pending approval submission data. The monthly overtime hours are 45 hours or more. Such extraction conditions are retained. "Target Period"... The period of data for which extraction is performed as notification information. For example, "Previous Month", "Current Month", "Previous Day", "Current Day", "2023 / 1 - 2023 / 12", etc. are retained. "Notification Destination"... The destination of the notification information. For example, "Self", "Supervisor", "Personnel Administrator", etc. When there is information (data) that matches the "Extraction Conditions", the individual who is the target for generating the notification information is retained. "Launch AP (Application)"... The application to be launched when the URL (link) embedded in the text of the "Message" in the "Notification to Administrator" shown in FIG. 3 is clicked is retained.

[0099] Also, as shown in FIG. 8, the "Notification Information" generated based on the "Notification Information Generation Setting Information" is stored in the DB4. The "Notification Information" includes the following information.

[0100] "Personal Code"... The "Personal Code" of Employee 2 corresponding to the "Notification Destination" in the "Notification Information Generation Setting Information". That is, the "Personal Code" of Employee 2 who is the notification destination of the notification information is retained. "Creation Date"... The date on which the "Notification Information" was generated. "Creation Time"... The time at which the "Notification Information" was generated. "Classification"... The type of the "Notification Information". For example, "Notification", "Confirmation Items", "Labor Alert", etc. are retained. "Message Content"... The text displayed as "Message" in the notification information display area 18 of the main menu screen 13. "URL"... The URL of the application embedded in the text of the "Message Content". "Sent Flag"... A flag indicating whether an email or message has been sent. The sending of emails and messages will be described later.

[0101] The personal authentication unit 26 shown in FIG. 5 executes an authentication process on the employee ID and password input by the login operation of Employee 2. Specifically, the personal authentication unit 26 reads out the "Personal Master" in which the "Personal Code" matching the input employee ID is retained from the DB4. If there is no "Personal Master" in which the "Personal Code" matching the input employee ID is retained, the authentication fails and an error is notified.

[0102] If there is a "Personal Master" in which the "Personal Code" matching the input employee ID is retained, it is determined whether the input password matches the "Password" retained in the "Personal Master". If the passwords match, the authentication is successful. If the passwords do not match, the authentication fails and an error is notified.

[0103] The notification information generation unit 27 generates "notification information" based on the "notification information generation setting information". The generation of the notification information is executed periodically or irregularly. For example, the notification information is generated at a predetermined timing (for example, every day) in a time zone when the processing load of the business management system 1 (server device 3) is low (for example, holidays or late at night).

[0104] In the present embodiment, the following attendance management-related data stored in the DB 4 is read by the notification information generation unit 27. Check-in / check-out data... Data on daily check-in / check-out times and going-out times. It is particularly read when extracting missed check-ins. Monthly ledger data... Data on monthly aggregates such as working hours and overtime hours. Notification application data... Data on the content of notifications such as overtime applications and leave applications.

[0105] When these attendance management-related data match the conditions for extracting notification information held in the "notification information generation setting information" shown in FIG. 7, the "notification information" shown in FIG. 8 is generated. Of course, the data read etc. is not limited, and other algorithms may be adopted as the method for generating the notification information. The generated "notification information" is stored in the DB 4.

[0106] The notification information acquisition unit 28 accesses the DB 4 and determines whether there is notification information for each employee 2. And when there is notification information, the notification information is acquired from the DB 4.

[0107] The login status confirmation unit 29 generates a confirmation screen including the determination result of the presence or absence of notification information and confirmation information for confirming whether the employee 2 wishes to be logged in to the business management system 1, and transmits it to the employee terminal 5.

[0108] The main menu screen generation unit 30 generates the main menu screen 13 as illustrated in FIGS. 3 and 4.

[0109] In this embodiment, the determination unit 9 shown in FIG. 5 is realized by the personal authentication unit 26 and the notification information acquisition unit 28. Further, the notification unit 10 shown in FIG. 1 is realized by the login state confirmation unit 29. Further, the execution unit 11 shown in FIG. 1 is realized by the login state confirmation unit 29 and the main menu screen generation unit 30.

[0110] FIG. 9 is a flowchart showing an operation example of login management according to this embodiment. A login screen is displayed on the employee terminal 5 (step 201). For example, a login screen is requested from the employee terminal 5 to the server device 3. In response to the request, a login screen is transmitted from the server device 3 to the employee terminal 5, and the login screen is displayed on the employee terminal 5.

[0111] FIG. 10 is a schematic diagram showing a configuration example of the login screen. The employee 2 inputs his / her employee ID ("personal code") and password into the login screen 32 and clicks the login button 33. The input employee ID and password are transmitted from the employee terminal 5 to the server device 3 (step 202).

[0112] The personal authentication unit 26 executes an authentication process. If the authentication fails, an error is notified to the employee terminal 5. If the authentication is successful, the notification information acquisition unit 28 acquires the number of pieces of notification information regarding the authenticated employee 2 (step 203). Note that if no notification information has been generated, 0 pieces are acquired as the number of notifications. The acquisition of the number of pieces of notification information in step 203 is one embodiment of the determination of the presence or absence of notification information.

[0113] The login state confirmation unit 29 generates a confirmation screen and transmits it to the employee terminal 5 (step 204).

[0114] FIG. 11 is a schematic diagram showing an example of the confirmation screen. FIG. 11A is a diagram showing an example of the confirmation screen 35a generated when there is notification information. FIG. 11B is a diagram showing an example of the confirmation screen 35b generated when there is no notification information.

[0115] In the example shown in FIG. 11A, as the determination result of the presence or absence of notification information, the text "There is a notification for you." is displayed. Also, the text prompting the employee to log in and check the content of the notification, "Log in and proceed to the main menu screen to check the notification content.", is displayed.

[0116] Also, in the example shown in FIG. 11A, as confirmation information for checking whether the employee desires to be logged in to the business management system 1, a login button 36 and an operation end button 37 are displayed. When the login button 36 is clicked by the employee 2, it is possible to confirm that the employee 2 desires to be logged in to the business management system 1. When the operation end button 37 is clicked by the employee 2, it is possible to confirm that the employee 2 does not desire to be logged in to the business management system 1.

[0117] In the example shown in FIG. 11B, as the determination result of the presence or absence of notification information, the text "There is no notification for you." is displayed. Also, the text indicating that button operation is required when logging in, "If you want to log in, click 'Log in'.", is displayed. Also, on the confirmation screen 35b shown in FIG. 11B, as confirmation information for checking whether the employee desires to be logged in to the business management system 1, a login button 36 and an operation end button 37 are displayed.

[0118] In the examples shown in FIGS. 11A and B, when authentication is successful by inputting the employee ID and password via the login screen 32 shown in FIG. 10, confirmation screens 35a and 35b are generated to confirm with the employee 2 whether to actually log in or not. That is, in the examples shown in FIGS. 11A and B, the confirmation screens 35a and 35b are generated to confirm whether to desire a login from the logged-out state as a confirmation of whether to desire a logged-in state.

[0119] FIG. 12 is a schematic diagram showing another example of the confirmation screen. FIG. 12A is a diagram showing an example of the confirmation screen 39a generated when there is notification information. FIG. 12B is a diagram showing an example of the confirmation screen 39b generated when there is no notification information.

[0120] In the example shown in FIG. 12A, as the determination result of the presence or absence of notification information, the text "There is a notification for you." is displayed. Also, the text prompting to proceed to the main menu screen 13 to check the content of the notification information, "Proceed to the main menu screen and check the notification content." is displayed.

[0121] Also, in the example shown in FIG. 12A, as confirmation information for checking whether the employee 2 wishes to be logged in to the business management system 1, a button 40 to proceed to the main menu screen and a logout button 41 are displayed. When the button 40 to proceed to the main menu screen is clicked by the employee 2, it is possible to confirm that the employee 2 wishes to be logged in to the business management system 1. When the logout button 41 is clicked by the employee 2, it is possible to confirm that the employee 2 does not wish to be logged in to the business management system 1.

[0122] In the example shown in FIG. 12B, as the determination result of the presence or absence of notification information, the text "There is no notification for you." is displayed. Also, the text indicating that a button operation is required when proceeding to the main menu screen 13, "If you proceed to the main menu screen, click 'Proceed to the main menu screen'." is displayed. Also, in the confirmation screen 39b shown in FIG. 12B, as confirmation information for checking whether the employee wishes to be logged in to the business management system 1, a button 40 to proceed to the main menu screen and a logout button 41 are displayed.

[0123] In the examples shown in FIGS. 12A and 12B, when authentication is successful by inputting an employee ID and password via the login screen 32 shown in FIG. 10, it is determined that the employee has logged in to the business management system 1. Then, while continuing the logged-in state, confirmation screens 39a and 39b are generated to confirm with Employee 2 whether to proceed to the main menu screen 13 or not. That is, in the examples shown in FIGS. 12A and 12B, as a confirmation of whether to desire a logged-in state, confirmation screens 39a and 39b are generated to confirm whether to desire to continue the logged-in state.

[0124] In the present embodiment, in response to the input of an employee ID via the login screen 32, it is determined whether there is notification information, which is information to be notified. As shown in FIGS. 11 and 12, when authentication is successful with the employee ID and password input via the login screen 32, it is possible to appropriately set whether to consider this as the final confirmation stage of login before login (i.e., the logged-out state) or as a logged-in state.

[0125] The confirmation screen is displayed on the employee terminal 5 (step 205). Then, it waits for an input from Employee 2 on whether to desire a logged-in state to the business management system 1 (step 206). If Employee 2 inputs that they do not desire a logged-in state (No in step 206), Employee 2 will be in the logged-out state and the business management system 1 will be in an inoperative state for Employee 2.

[0126] For example, when the operation end button 37 is clicked in the confirmation screens 35a and 35b shown in FIG. 11, or when the logout button 41 is clicked in the confirmation screens 39a and 39b shown in FIG. 12, step 206 will be No and Employee 2 will be in the logged-out state.

[0127] When an input indicating a desire for a logged-in state is received from Employee 2 (Yes in Step 206), the main menu screen generation unit 16 generates the main menu screen 13 and transmits it to the employee terminal 5 (Step 207).

[0128] For example, when the login button 36 is clicked on the confirmation screens 35a and 35b shown in FIG. 11, or when the button 40 to proceed to the main menu screen is clicked on the confirmation screens 39a and 39b shown in FIG. 12, Step 206 becomes Yes, and the main menu screen 13 is generated and transmitted to the employee terminal 5.

[0129] The main menu screen is displayed on the employee terminal 5. Employee 2 is in a logged-in state, and the operation of the business management system 1 continues for Employee 2.

[0130] As described above, in the business management system 1 and the server device 3 according to the present embodiment, in response to the input of the employee ID, which is the identification information of Employee 2, the presence or absence of the notification information, which is the information to be notified to Employee 2 and defined as the information to be notified, is determined. Then, the determination result and the confirmation information for confirming whether Employee 2 desires to be in a logged-in state with respect to the business management system 1 are notified to Employee 2. When an input indicating a desire for a logged-in state is received with respect to the confirmation information, the main menu screen 13 is generated. As a result, it is possible to suppress the frequency of the generation process of the main menu screen 13 and reduce the processing load in business management.

[0131] (Second Embodiment) FIG. 13 is a block diagram showing a functional configuration example of the server device 3 according to the second embodiment. As shown in FIG. 13, in the present embodiment, further, as a functional block, a mode setting unit 43 is configured.

[0132] The mode setting unit 43 switches between and sets a login confirmation mode and a non-login confirmation mode. The login confirmation mode is a mode in which each of the determination by the determination unit 9 shown in FIG. 1 of the presence or absence of notification information (information to be notified), the notification by the notification unit 10 of the determination result and the confirmation information, and the generation of the main menu screen 13 according to the input indicating the desired login state by the execution unit 11 are executed.

[0133] The non-login confirmation mode is a mode in which each of the determination by the determination unit 9 shown in FIG. 1 of the presence or absence of notification information (information to be notified), the notification by the notification unit 10 of the determination result and the confirmation information, and the generation of the main menu screen 13 according to the input indicating the desired login state by the execution unit 11 are not executed.

[0134] That is, when the login confirmation mode is set, the login management shown in FIG. 2 is executed. When the non-login confirmation mode is set, the login management is not executed, and the normal login process is executed.

[0135] FIGS. 14 and 15 are flowcharts showing an example of mode setting by the mode setting unit 43. The mode setting illustrated in FIGS. 14 and 15 is repeatedly executed, for example, at a predetermined frame rate. Alternatively, the mode setting may be executed at a predetermined timing determined in advance.

[0136] In the example shown in FIG. 14, the current (current time) performance counter is acquired (step 301). It is determined whether the value of the acquired performance counter is less than the threshold value (step 302).

[0137] When the value of the performance counter is not less than the threshold value (No in step 302), the login confirmation mode is set (step 303). When the value of the performance counter is less than the threshold value (Yes in step 302), the non-login confirmation mode is set (step 304).

[0138] That is, in the mode setting shown in FIG. 14, the mode setting unit 43 switches and sets between a login confirmation mode and a non-login confirmation mode based on the status of the processing load of the business management system 1 (server device 3).

[0139] When the processing load of the business management system 1 (server device 3) is relatively high, the login confirmation mode is set, and when the processing load of the business management system 1 (server device 3) is relatively low, the non-login confirmation mode is set.

[0140] When the server device 3 executes the management of the login illustrated in FIG. 2, since there is a confirmation as to whether or not the login state is desired, the number of operations for the employee 2 until reaching the main menu screen 13 increases, and there is a possibility that the convenience decreases.

[0141] In this embodiment, when the processing load of the business management system 1 (server device 3) is relatively low, the confirmation as to whether or not the login state is desired is not performed, and normal login becomes possible. Thereby, efficient business operation becomes possible.

[0142] Note that the specific configuration of the performance counter is not limited. For example, the value of the performance counter may be calculated based on various parameters capable of evaluating the status of the processing load, such as the CPU usage rate, the free memory capacity, and the network communication speed.

[0143] Also, the method for evaluating the status of the processing load is not limited to the case where a performance counter is used. Any algorithm capable of evaluating the status of the processing load may be used.

[0144] Also, the reference value (threshold value) for determining that the processing load is relatively high and that the processing load is relatively low can be arbitrarily set.

[0145] In the example shown in FIG. 15, the date and time setting information in the login confirmation mode is acquired (step 401). The time setting information is information that defines the time zone in which the login confirmation mode is set.

[0146] It is determined whether the current date and time is included in the time zone of the login confirmation mode defined by the date and time setting information (step 402). If the current date and time is included in the time zone of the login confirmation mode (Yes in step 402), the login confirmation mode is set (step 403). If the current date and time is not included in the time zone of the login confirmation mode (No in step 402), the unconfirmed login mode is set (step 404).

[0147] That is, in the example shown in FIG. 15, the mode setting unit 43 sets the login confirmation mode in a predetermined time zone and sets the unconfirmed login mode in other time zones. In the present disclosure, the time zone includes information such as year, day, day of the week, and time.

[0148] By executing the mode setting shown in FIG. 15, normal login is possible in time zones where login restrictions are unnecessary, and efficient business operation is realized.

[0149] Note that which time zone is to be the time zone of the login confirmation mode may be arbitrarily set. For example, the day of the week and time when the processing load of the business management system 1 (server device 3) is relatively high, in other words, the day of the week and time for which the processing load is desired to be reduced, are set as the time zone of the login confirmation mode.

[0150] For example, the time zone immediately before the start time when attendance punches are concentrated, the time zone immediately after the end time when leaving punches are concentrated, the time zone immediately before the end time when overtime applications and their approval processes are concentrated, etc. are set as the time zone of the login confirmation mode. Alternatively, the time zone near the end of each month, the time zone at the end of the year or the end of the fiscal year, etc. may be set as the time zone of the login confirmation mode. In addition, any time zone can be set as the time zone of the login confirmation mode. Also, the time zone of the login confirmation mode may be automatically optimized or automatically determined.

[0151] Figure 16 is a flowchart showing an operation example of login management in the present embodiment. A login screen 32 is displayed on the employee terminal 5 (step 501). An employee 2 performs a login operation on the login screen 32, and an employee ID ("personal code") and a password are input (step 502).

[0152] If the authentication by the personal authentication unit 26 is successful, the notification information acquisition unit 28 determines whether or not the login confirmation mode is set (step 503). If the login confirmation mode is not set and the login unconfirmed mode is set (No in step 503), the main menu screen generation unit 30 generates the main menu screen 13 and transmits it to the employee terminal 5 (step 504).

[0153] In this way, when the login unconfirmed mode is set, the notification of the determination result of the presence or absence of notification information and the confirmation of whether or not to desire the login state are not performed, and a so-called normal login process is executed. The main menu screen 13 is displayed on the employee terminal 5 (step 505), and the operation of the business management system 1 continues.

[0154] If the login confirmation mode is set (Yes in step 503), login management including the notification of the determination result of the presence or absence of notification information and the confirmation of whether or not to desire the login state is performed (steps 506 to 511). These steps 506 to 511 are the same processes as steps 203 to 208 shown in FIG. 9.

[0155] Note that a functional block for determining whether or not it is the login confirmation mode in step 503 may be configured, and the determination result may be output to the notification information acquisition unit 28, the login state confirmation unit 29, and the main menu screen generation unit 30 shown in FIG. 13. Then, based on the determination result of whether or not each of these blocks is in the login confirmation mode, operations corresponding to each mode may be executed.

[0156] Alternatively, an area for storing a login confirmation mode flag may be set in DB4, and the flags for "login confirmation mode" and "unconfirmed login mode" may be stored respectively. The notification information acquisition unit 28, the login state confirmation unit 29, and the main menu screen generation unit 30 execute operations corresponding to each mode by referring to the login confirmation mode flag. Such a setting is also possible.

[0157] Alternatively, the mode settings for the login confirmation mode and the unconfirmed login mode may not be processed as matters. For example, the notification information acquisition unit 28 may determine the status of the processing load of the business management system 1 (server device 3). When the processing load of the business management system 1 (server device 3) is relatively high, the flow for managing logins is not executed, and the normal login process is executed. When the processing load of the business management system 1 (server device 3) is relatively low, the flow for managing logins is executed.

[0158] Also, for example, the notification information acquisition unit 28 may determine whether the current date and time is included in the time zone for executing login management. When the current date and time is not included in the time zone for executing login management, the flow for managing logins is not executed, and the normal login process is executed. When the current date and time is included in the time zone for executing login management, the flow for managing logins is executed. Such a setting is also possible.

[0159] When the notification information acquisition unit 28 determines the status of the processing load of the business management system 1 (server device 3) or determines whether the current time is included in the time zone for executing login management, it can be said that the notification information acquisition unit 28 functions as a block for determining whether to execute login management.

[0160] In addition, a functional block for determining the status of the processing load of the business management system 1 (server device 3) and a functional block for determining whether the current date and time is included in the time zone for executing login management may be configured separately.

[0161] (Third Embodiment) FIG. 17 is a schematic diagram showing an example of a confirmation screen according to the third embodiment of the present invention. In this embodiment, the estimated time required until the main menu screen 13 is displayed is displayed as an estimated display time on the confirmation screens 45a and 45b displayed on the employee terminal 5.

[0162] In this embodiment, the time required to generate the main menu screen 13 is calculated as the estimated display time by the main menu screen generation unit 30. For example, in the DB4, the time required to generate the main menu screen 13, the data volume, etc. are stored as main menu screen generation history data. The main menu screen generation unit 30 can calculate the estimated display time by checking the main menu screen generation history data.

[0163] In addition, the algorithm for calculating the estimated display time is not limited, and any algorithm may be adopted. Also, considering the communication speed of the network, etc., the time required to generate the main menu screen 13 and display it on the employee terminal 5 may be calculated as the estimated display time. Of course, a functional block capable of calculating the time required to generate the main menu screen may be configured separately.

[0164] The notification of the confirmation screens 45a and 45b including the estimated display time corresponds to an embodiment of notifying the employee of the time required to generate the main menu screen according to the present invention.

[0165] The employee 2 can grasp the approximate time until the main menu screen 13 is displayed by checking the confirmation screens 45a and 45b. For example, when the logins of the employee 2 are concentrated, the estimated display time becomes longer. When the estimated display time displayed on the confirmation screens 45a and 45b is relatively long, for example, an employee who does not require urgency can make a judgment to log in later. As a result, it is possible to suppress the concentration of logins and reduce the processing load.

[0166] That is, for Employee 2, the estimated display time serves as a basis for determining whether to log in now, and it becomes possible to suppress an increase in the processing load due to concentrated logins. As a result, efficient business operation is achieved.

[0167] (Fourth Embodiment) FIG. 18 is a flowchart showing an operation example of login management according to the fourth embodiment of the present invention. FIG. 19 is a schematic diagram showing an example of a confirmation screen according to this embodiment. FIG. 20 is a schematic diagram showing an example of a simplified main menu screen according to this embodiment.

[0168] Steps 601 to 605 shown in FIG. 18 are the same processes as steps 201 to 205 shown in FIG. 9.

[0169] As shown in FIG. 19, in this embodiment, on the confirmation screens 47a and 47b, selection images (selection GUIs) 48 for selecting information to be displayed on the main menu screen 13 are displayed.

[0170] In this embodiment, for the three types of information, namely, the notification information displayed in the notification information display area 18 shown in FIG. 2, the attendance status information displayed in the attendance status display area 19, and the weekly / monthly work report information displayed in the weekly / monthly work report display area 20, it is possible to select whether to display them on the main menu screen 13.

[0171] On the confirmation screen 47a when there is notification information shown in FIG. 19A, only the notification information is selected. This is an input of an instruction to display only the notification information on the main menu screen 13 and not to display the attendance status information and the weekly / monthly work report information.

[0172] On the confirmation screen 47b when there is no notification information shown in Fig. 19B, attendance status information and work weekly / monthly report information are selected. This is an instruction input to display attendance status information and work weekly / monthly report information on the main menu screen 13 and not to display notification information.

[0173] The selection of information to be displayed on the main menu screen 13 via the selection screens 47a and 47b illustrated in Fig. 19 is an embodiment when an instruction to omit display from an employee is input according to the present invention. Of course, the method, GUI, etc. for selecting information to be displayed on the main menu screen 13 (conversely, information to be omitted from display on the main menu screen 13) is not limited and may be arbitrarily designed.

[0174] Also, on the selection screens 47a and 47b illustrated in Fig. 19, for each of the notification information, attendance status information, and work weekly / monthly report information, the estimated display time until it is displayed on the main menu screen 13 is shown. Employee 2 can sufficiently consider and decide which information to display (of course, including not displaying any information) by checking the estimated display time for each information.

[0175] In step 606, if there is an input from Employee 2 indicating a desire to be in a logged-in state (Yes), it is determined whether there is an instruction to create a simplified version of the main menu screen 13 by the main menu screen generation unit 30 (step 607).

[0176] The simplified version of the main menu screen 13 is a main menu screen 13 with some of the information displayed on the normal main menu screen 13 omitted. In this embodiment, on the confirmation screens 47a and 47b shown in Fig. 19, when all information is selected, it is determined that there is no instruction to create a simplified version of the main menu screen 13 (No in step 607), and the normal main menu screen 13 is generated and transmitted to the employee terminal 5 (step 608).

[0177] The normal main menu screen 13 is the main menu screen 13 where information is not omitted. The normal main menu screen 13 is displayed on the employee terminal 5 (step 609).

[0178] In the confirmation screens 47a and 47b shown in FIG. 19, if any information is selected, it is determined that there is an instruction to create a simplified version of the main menu screen 13 (Yes in step 607), and a simplified version of the main menu screen 13 in which the selected information is displayed (in other words, the unselected information is omitted) is generated and transmitted to the employee terminal 5 (step 610). The simplified version of the main menu screen 13 is displayed on the employee terminal 5 (step 609).

[0179] FIG. 20 shows a simplified version of the main menu screen 13 when none of the notification information, attendance status information, and work weekly / monthly report information is selected in the confirmation screens 47a and 47b shown in FIG. 19. That is, the main menu screen 13 in which all the displays of the notification information, attendance status information, and work weekly / monthly report information are omitted is shown.

[0180] Compared with the case of generating the normal main menu screen 13, the processing load for generating the simplified version of the main menu screen 13 is reduced. The more information is omitted, the greater the reduction in the processing load can be achieved.

[0181] Therefore, by displaying only the information required by the employee 2 on the main menu screen 13, the processing load can be reduced, and the response can be accelerated. As a result, efficient business operation is realized.

[0182] As shown in FIG. 20, the text "※Please click if you want to display the notification information" is displayed in the notification information display area 18 of the simplified version of the main menu screen 13. When the employee 2 clicks the text via the employee terminal 5, the notification information whose display has been omitted is displayed.

[0183] In addition, in the attendance status display area 19, text reading "※Please click if you want to display the attendance status" is shown. When the said text is clicked, the attendance status information whose display has been omitted is displayed.

[0184] In addition, in the work weekly / monthly report display area 20, text reading "※Please click if you want to display the work weekly / monthly report" is shown. When the said text is clicked, the work weekly / monthly report information whose display has been omitted is displayed.

[0185] In this way, Employee 2 can instruct the simplified main menu screen 13 to display the information whose display has been omitted. Thereby, it becomes possible to efficiently display the information that needs to be confirmed.

[0186] Note that the clicking of each text shown in FIG. 20 corresponds to one embodiment of the input of an instruction from an employee according to the present invention to display the information omitted on the simplified main menu screen. Also, the display of information in response to the clicking of each text corresponds to one embodiment of the display of the information targeted by the instruction according to the present invention.

[0187] Of course, the method and GUI for inputting an instruction to display the information omitted on the simplified main menu screen 13 are not limited and may be arbitrarily designed. For example, input by voice is also possible.

[0188] Regarding the determination of whether to generate the normal main menu screen 13 or the simplified main menu screen 13, other embodiments can also be realized. For example, as the confirmation screen transmitted to the employee terminal 5, confirmation screens 39a and 39b shown in FIG. 11, which do not have the selection image 48, are displayed.

[0189] When an input indicating a desire to be in a logged-in state is made by Employee 2, the main menu screen generation unit 30 may automatically determine whether to generate the normal main menu screen 13 or the simplified version of the main menu screen 13.

[0190] For example, in the DB4, operation history information (log information) of Employee 2 on the main menu screen 13 during the logged-in state is stored. The main menu screen generation unit 30 can determine based on the history information whether there is information that does not require display on the main menu screen 13. Of course, a functional block capable of determining whether there is information that does not require display on the main menu screen 13 may be configured separately.

[0191] For example, assume that as the history information of a certain Employee 2, information indicating that the main menu screen 13 was displayed in the evening on Tuesday and the overtime application was immediately made by clicking the menu button 15 is stored. Assume that the said Employee 2 clicked the login buttons 36 on the confirmation screens 39a and 39b in the evening on Tuesday.

[0192] Regarding the said click, it is possible to estimate that the overtime application will be made by clicking the menu button 15. For example, it is determined that all of the information such as the notification information, attendance status information, and work weekly / monthly report information does not require display on the main menu screen 13, and a simplified version of the main menu screen 13 in which these information are omitted as shown in FIG. 20 is generated. It is possible to execute such an automatic determination.

[0193] In addition, any technology (such as an algorithm) may be used to determine whether there is information that does not require display. For example, any machine learning algorithm using DNN (Deep Neural Network), RNN (Recurrent Neural Network), CNN (Convolutional Neural Network), etc. may be used. For example, by using an AI (Artificial Intelligence) that performs deep learning, it becomes possible to execute the determination process with high accuracy.

[0194] For example, a trained learning model for performing machine learning to output information that does not require display is constructed using the operation history information for the main menu screen 13 as teacher data. By inputting information of employee 2 who performs a login operation, information on the time zone when the login operation is performed, etc. into the learning model, it is possible to obtain information that does not require display from the learning model. Of course, it is not limited to the case of constructing such a learning model.

[0195] The learning block (learning unit) for training the learning model may be configured in the server device 3. Alternatively, the learning block (learning unit) may be configured in a computer different from the server device 3, and the trained learning model after learning is installed in the server device 3. In addition, the specific configurations of the learning model and the learning block (learning unit) for learning the learning model are not limited.

[0196] Note that the application of the machine learning algorithm may be executed for any process within the present disclosure. That is, for any process described within the present disclosure, a process using machine learning may be executed.

[0197] (Fifth Embodiment) FIG. 21 is a schematic diagram showing an example of a confirmation screen according to the fifth embodiment of the present invention. In this embodiment, an estimated processing time required to complete an unprocessed process that needs to be completed by the administrator 7 and is displayed as notification information on the confirmation screen 50 displayed on the administrator terminal 8 used by the administrator 7 is displayed. That is, in this embodiment, the administrator 7 is notified of the estimated processing time required to complete the unprocessed process.

[0198] In the example shown in FIG. 21, a confirmation screen 50 is illustrated when "data awaiting approval (10 items)", "forgetting to punch in (2 items)", and "forgetting to punch out (1 item)" are displayed as unprocessed process data (unprocessed data) on the main menu screen 13.

[0199] As shown in FIG. 21, 200 seconds is displayed as the estimated processing time until the processing of 10 "data awaiting approval" is completed. Also, 50 seconds is displayed as the estimated processing time until the processing of 2 "forgetting to punch in" is completed. Further, 25 seconds is displayed as the estimated processing time until the processing of 1 "forgetting to punch out" is completed.

[0200] By checking the confirmation screen 50, the administrator 7 can grasp the time required to process the unprocessed data and eliminate the alert. For example, when the estimated processing time is very short, it is possible to make a judgment to log in first and quickly complete the processing. Conversely, for example, since the estimated processing time is very short, it is possible to make a judgment to complete the processing at a more convenient timing a little later, or to make a judgment to complete the processing at once after a little more unprocessed data has accumulated.

[0201] This makes it possible to suppress the situation of simply displaying the main menu screen 13 first to check the status of unprocessed data, and to log in at the necessary timing to display the main menu screen 13. As a result, it is possible to suppress the concentration of logins and reduce the processing load.

[0202] That is, for the administrator 7, the estimated processing time serves as a factor for determining whether to log in now, and it becomes possible to suppress an increase in the processing load due to concentrated logins. As a result, efficient business operation is realized.

[0203] The estimated processing time can be calculated, for example, based on the accumulated operation history. Also, it is possible to calculate according to the number of data items by presetting the standard time required for processing for each item of unprocessed data (for example, standard time × number of data items). It is also possible to calculate based on the proficiency of the administrator 7. In addition, any algorithm such as a machine learning algorithm may be used. Also, the functional block capable of calculating the estimated processing time may be configured separately.

[0204] Note that the notification of the estimated processing time is not limited to being performed for the administrator 7. When the unprocessed processing is notified as notification information to an employee 2 who is not the administrator 7, the notification of the estimated processing time may also be executed together.

[0205] [Notification of Notification Information] In the business management system 1 according to each of the above-described embodiments, it is also possible to mount a function of notifying notification information to each employee 2.

[0206] For example, by the notification information generation unit 27 shown in FIG. 5 and the like, the generation process of the notification information for each employee 2 is executed at a predetermined timing when the processing load of the business management system 1 (server device 3) becomes low.

[0207] For example, by the notification unit 10 shown in FIG. 1, at a predetermined regular or irregular timing, a notification indicating that there is notification information is executed to the employee terminal 5 of the employee 2 for whom the notification information has been generated. Of course, a notification information notification unit for notifying the notification information may be configured as a functional block different from the notification unit 10 shown in FIG. 1.

[0208] For example, as shown in FIG. 22A, it is also possible to notify the employee 2 for whom the notification information has been generated by email. In the example shown in FIG. 22A, a notification email with the subject line "(Confirmation Request) Regarding Forgotten Signing Out" is sent from the "Business Management System" which is the sender to the employee 2 (Taro Amano) for whom the notification information has been generated and who is the recipient.

[0209] In the body of the notification email, the text "There is a forgotten signing out. Please confirm." is displayed. Also, a link (URL) to the main menu screen 13 is displayed. If the notification information is unprocessed data, a link (URL) to the application for processing the unprocessed data may be displayed.

[0210] Also, as shown in FIG. 22B, a notification indicating that there is notification information may be executed via a message function such as SMS.

[0211] FIG. 23 is a flowchart showing an example of the process for notifying notification information. Notification information that has not been sent is acquired (step 701). For all the unsent data, it is determined whether the notification has been completed (step 702). If the notification for all the data has not been completed (No in step 702), the next notification information that has not been sent is acquired (step 703).

[0212] A notification indicating that there is notification information is executed via email or a message as shown in FIGS. 22A and B (step 704). The sent flag of the notification information shown in FIG. 8 is updated to sent (step 705). The process returns to step 702 and is repeated until the notification for all the unsent data is completed.

[0213] By using such mails or messages to send a notice that there is notification information, it is possible to suppress, for example, displaying the main menu screen 13 first to check for the presence of notification information, and to display the main menu screen 13 by logging in at the necessary timing. As a result, it is possible to suppress the concentration of logins and reduce the processing load.

[0214] Figure 24 is a flowchart showing another processing example of the notification of notification information. Steps 801, 802, 804 to 806 shown in Figure 23 are the same processing as steps 701 to 705 shown in Figure 22.

[0215] In the flow shown in Figure 23, at step 802, when not all notifications have been completed (No), it is determined whether the upper limit value of the number of sent mails has been reached (step 803). If the number of sent mails has not reached the upper limit value, the process proceeds to step 804, and notifications are executed for the notification information that has not been sent. If the number of sent mails has reached the upper limit value, the notifications for the unsent notification information are not executed, and the notification of the notification information ends.

[0216] For example, when a large number of notices indicating the existence of notification information are sent, logins may concentrate from the links in the mails or messages, and the processing load may increase. As shown in Figure 24, by setting the upper limit value of the number of sent mails and controlling the number of sent mails, it is possible to suppress the concentration of logins.

[0217] The specific method for setting the upper limit value of the number of sent letters is not limited and can be set arbitrarily. For example, when the processing load of the business management system 1 (server device 3) is relatively high, the upper limit value is set small, and when the processing load of the business management system 1 (server device 3) is relatively low, the upper limit value is set large. Alternatively, the upper limit value is set small during the time zone when the processing load of the business management system 1 (server device 3) is relatively high, and the upper limit value is set large during the time zone when the processing load of the business management system 1 (server device 3) is relatively low. In this way, the upper limit value may vary depending on the situation.

[0218] <Other Embodiments> The present invention is not limited to the embodiments described above, and various other embodiments can be realized.

[0219] Each of the above embodiments has been described as a variation example in executing the login management illustrated in FIG. 2. On the other hand, it is also possible to individually install the functions (technologies) described in each embodiment without executing the login management illustrated in FIG. 2 to construct a new business management system (information processing system).

[0220] For example, in the third embodiment, as shown in FIG. 17, the estimated display time required until the main menu screen 13 is displayed is notified to the employee 2. For example, it is also possible to construct a business management system (information processing system) that only executes the notification of the estimated display time without executing the login management. By notifying the estimated display time, it becomes possible to determine whether to log in now, and the effect of suppressing the concentration of logins is exhibited.

[0221] In the fourth embodiment, as shown in FIG. 19, the employee 2 can select the information (items) displayed on the main menu screen 13. For example, it may be possible to only select the information displayed on the main menu screen 13 without performing login management. That is, it may be possible to only execute the selection of whether to display the normal main menu screen 13 or the simplified version of the main menu screen 13. As a result, it becomes possible to display only the information required by the employee 2 on the main menu screen 13, and it becomes possible to reduce the processing load.

[0222] In the fifth embodiment, as shown in FIG. 21, the employee 2 is notified of the estimated processing time required to complete the unprocessed processing that needs to be completed. For example, it is also possible to construct a business management system (information processing system) that only executes the notification of the estimated processing time without performing login management. By notifying the estimated processing time, it becomes possible to determine whether to log in now, and the effect of suppressing the concentration of logins is exerted.

[0223] In the above embodiment, the login management illustrated in FIG. 2 is executed based on the employee ID via the login screen 32 shown in FIG. 10. However, the present invention is not limited to this, and the employee ID may be input through a screen (GUI) different from the login screen 32, and the login management may be executed.

[0224] FIG. 25 is a block diagram showing a hardware configuration example of the server device 3 and the computer 60 that can be used as the employee terminal 5.

[0225] The computer 60 includes a CPU 61, a ROM 62, a RAM 63, an input / output interface 65, and a bus 64 that connects these to each other. Connected to the input / output interface 65 are a display unit 66, an input unit 67, a storage unit 68, a communication unit 69, a drive unit 70, and the like. The display unit 66 is, for example, a display device using a liquid crystal, an EL, etc. The input unit 67 is, for example, a keyboard, a pointing device, a touch panel, or other operating device. When the input unit 67 includes a touch panel, the touch panel can be integrated with the display unit 66. The storage unit 68 is a non-volatile storage device, such as a HDD, a flash memory, or other solid-state memory. The drive unit 70 is a device capable of driving a removable recording medium 71, such as an optical recording medium, a magnetic recording tape, or the like. The communication unit 69 is a modem, a router, or other communication device that can be connected to a LAN, a WAN, or the like and is used to communicate with other devices. The communication unit 69 may communicate either wired or wirelessly. The communication unit 69 is often used separately from the computer 60. Information processing by computer 60 having the above hardware configuration is realized by cooperation between software stored in storage unit 68 or ROM 62, etc., and hardware resources of computer 60. Specifically, the information processing method according to the present invention is realized by loading a program constituting the software stored in ROM 62, etc., into RAM 63 and executing the program. The program is installed in the computer 60 via, for example, the recording medium 71. Alternatively, the program may be installed in the computer 60 via a global network or the like. Any other computer-readable non-transitory storage medium may be used.

[0226] The information processing method (business management method / login management method) and program of the present invention may be executed by collaboration between multiple computers connected to each other so as to communicate with each other via a network or the like, thereby constructing an information processing system or information processing device of the present invention. That is, the information processing method and program according to the present invention can be executed not only in a computer system constituted by a single computer, but also in a computer system in which a plurality of computers operate in conjunction with each other. In the present disclosure, a system means a collection of a plurality of components (devices, modules (parts), etc.), and it does not matter whether all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network, and a single device in which a plurality of modules are housed in one housing are both systems.

[0227] The execution of the information processing method and program according to the present invention by a computer system includes, for example, the acquisition of identification information, the generation of information to be notified, the determination of the presence or absence of information to be notified, the notification of the determination result, the notification of confirmation information, the generation of a main menu screen, etc., both when executed by a single computer and when each process is executed by different computers. Also, the execution of each process by a predetermined computer includes causing part or all of the process to be executed by another computer and obtaining the result. That is, the information processing method and program according to the present invention can also be applied to a cloud computing configuration in which a single function is shared and jointly processed by a plurality of devices via a network.

[0228] The business management system, employee terminal, server device, various screens such as a confirmation screen, each configuration of various GUIs, the generation of information to be notified, the determination of the presence or absence of information to be notified, the notification of the determination result, the notification of confirmation information, the generation of a main menu screen, etc., described with reference to each drawing are merely one embodiment, and can be arbitrarily modified without departing from the gist of the present invention. That is, any other arbitrary configuration, algorithm, etc. for implementing the present invention may be adopted.

[0229] In the present disclosure, for the sake of easy understanding of the description, words such as "substantially", "almost", "approximately", etc. may be appropriately used. On the other hand, there is no clear difference defined between the cases where these words such as "substantially", "almost", "approximately", etc. are used and the cases where they are not used. That is, in the present disclosure, concepts that define shape, size, positional relationship, state, etc., such as "center", "central", "uniform", "equal", etc., shall be concepts including "substantially center", "substantially central", "substantially uniform", "substantially equal", etc. For example, states included within a predetermined range (e.g., a range of ±10%) based on "completely center", "completely central", "completely uniform", "completely equal", etc. are also included. Therefore, even when words such as "substantially", "almost", "approximately", etc. are not added, concepts expressed by adding so-called "substantially", "almost", "approximately", etc. may be included. Conversely, it does not necessarily mean that a complete state is always excluded for a state expressed by adding "substantially", "almost", "approximately", etc.

[0230] In the present disclosure, expressions using "more" such as "greater than A" and "less than A" are expressions comprehensively including both concepts that include the case of being equivalent to A and concepts that do not include the case of being equivalent to A. For example, "greater than A" is not limited to the case of not including equivalence to A, and also includes "greater than or equal to A". Further, "less than A" is not limited to "less than A", and also includes "less than or equal to A". When implementing the present technology, specific settings, etc. may be appropriately adopted from the concepts included in "greater than A" and "less than A" so that the effects described above are exhibited.

[0231] Among the characteristic parts of the present invention described above, it is also possible to combine at least two characteristic parts. That is, the various characteristic parts described in each embodiment may be arbitrarily combined without distinction between the embodiments. Also, the various effects described above are merely illustrative and not limiting, and other effects may also be exhibited.

Industrial Applicability

[0232] The present invention can be suitably used in an information processing system equipped with business software for performing business processes of an enterprise.

Explanation of Signs

[0233] 1…Business management system 2…Employee 3…Server device 5…Employee terminal 7…Administrator 8…Administrator terminal 13…Main menu screen 18…Notification information display area 19…Attendance status display area 20…Work weekly / monthly report display area 32…Login screen 35a, 35b, 39a, 39b, 45a, 45b, 47a, 47b, 50…Confirmation screen 60…Computer

Claims

1. An information processing system for managing business information, A determination unit that determines whether or not there is information that should be notified to the employee, as defined by the input of identification information that identifies the employee, A notification unit notifies the employee of the determination result from the determination unit and confirmation information to determine whether the employee wishes to log in to the information processing system. When the user has entered a request to log in to the information processing system in response to the aforementioned confirmation information, an execution unit generates a main menu screen for using the information processing system. An information processing system equipped with the following features.

2. The information processing system according to claim 1, The main menu screen includes a display area where the notification information is displayed, and a display area where the business information not specified as notification information is displayed. Information processing system.

3. An information processing system according to claim 1 or 2, The determination unit determines whether or not there is any notification required information in response to the input of the identification information via the login screen for logging into the information processing system. Information processing system.

4. The information processing system according to claim 1, further, A login confirmation mode in which the determination unit determines whether or not there is information requiring notification, the notification unit notifies the determination result and the confirmation information, and the execution unit generates the main menu screen in response to an input indicating a desire to be logged in, Login Unconfirmed Mode: In which the determination by the determination unit for the presence or absence of the notification information, the notification unit for the determination result and the confirmation information, and the execution unit for generating the main menu screen in response to the input indicating a desire to be logged in are not performed. It is equipped with a mode setting section that allows switching between different modes. Information processing system.

5. The information processing system according to claim 4, The mode setting unit switches between the login confirmation mode and the login unconfirmed mode based on the processing load status of the information processing system. Information processing system.

6. The information processing system according to claim 5, The mode setting unit sets the login confirmation mode when the processing load of the information processing system is relatively high, and sets the login unconfirmed mode when the processing load of the information processing system is relatively low. Information processing system.

7. The information processing system according to claim 4, The mode setting unit sets the login confirmation mode during a predetermined time period and sets the login unconfirmed mode during other time periods. Information processing system.

8. The information processing system according to claim 1, The notification unit notifies the employee of the time required to generate the main menu screen. Information processing system.

9. The information processing system according to claim 1, The execution unit generates a simplified main menu image in which some of the information displayed on the main menu screen is omitted, when it determines, based on the employee's operation history information on the main menu screen, that there is information that does not need to be displayed on the main menu screen, or when the employee has given instructions to omit the display of certain information. Information processing system.

10. The information processing system according to claim 9, When the execution unit receives an instruction from the employee to display information omitted from the simplified main menu screen, it will display the information to which the instruction applies. Information processing system.

11. The information processing system according to claim 1, The aforementioned main menu screen includes information on unprocessed tasks that the employee needs to complete. The notification unit notifies the employee of the time required to complete the pending processing. Information processing system.

12. An information processing method performed by a computer system that manages business information, In response to the input of identification information that identifies an employee, it is determined whether or not there is any information that must be notified to the employee as specified. The employee is notified of the determination result obtained by the above determination and confirmation information to determine whether or not the employee wishes to log in to the computer system. If the user indicates in the aforementioned confirmation information that they wish to log in to the computer system, the main menu screen for using the computer system will be generated. Information processing methods.

13. A program that causes a computer system that manages business information to execute an information processing method, The aforementioned information processing method is In response to the input of identification information that identifies an employee, it is determined whether or not there is any information that must be notified to the employee as specified. The employee is notified of the determination result obtained by the above determination and confirmation information to determine whether or not the employee wishes to log in to the computer system. If the user indicates in the aforementioned confirmation information that they wish to log in to the computer system, the main menu screen for using the computer system will be generated. program.

Images