JP6964160B2 - Work management system, work management method, and work management program - Google Patents

Description

The present invention relates to a work management system for managing work of the user.

In the technique described in Patent Document 1, the operation on the virtual desktop used by the user for business is detected, the time when the login operation is executed is the start time, and the time when the logout operation or the virtual desktop close operation is executed is the end. It is described that the working hours of the user are calculated as the time.

Japanese Unexamined Patent Publication No. 2019-40477

In the above-mentioned conventional technology, when a large number of terminals including virtual terminals are used due to the recent work style reform, for example, terminals such as smartphones and tablets that do not necessarily require logon / logoff in order to use the terminals for business. , Applications installed on the above terminals, terminals used remotely using IoT terminals such as system monitoring, terminals provided with transportation means can be used in parallel, and terminals can be changed depending on the location and time when the user uses the terminal. It is not assumed that it will be used properly, and whether it is used for business purposes or private purposes, and it is not possible to grasp the working hours of the user assuming these usage situations.

Further, in the above-mentioned conventional technique, logon and logoff on each system and operation log of the above-mentioned terminal are managed individually. Therefore, in the management based on the logon and logoff time in the above-mentioned conventional technique, the user's terminal operation is performed for a certain period of time. Even if you do not have it, you will be treated as working, but if you simply exclude the time when you do not operate the terminal, you will use the destination terminal when you move by means of transportation such as trains, cars, buses, etc. at business events. It is not possible to treat the travel time until the work is done, and there are restrictions on using the terminal at times and places other than the scheduled work time, the distinction between the use of the terminal for business use, private use, and public use, and whether it is the main business even for business use. In a situation where there is no distinction between side jobs, it is not possible to restrict the long working hours that the user's manager should suppress in consideration of the type, and it is not possible to appropriately grasp and manage the working hours of the user.

Therefore, in the present invention, even when a user uses various terminals or applications in the terminals in order to solve the above-mentioned problems, the working hours of the user are based on the integrated log information associated with the user ID. The purpose is to provide a work management system, a work management method, and a work management program that can appropriately grasp the above.

In the work management system and work management method according to claims 1 and 8 of the present invention, at least two of virtual terminals, FAT terminals, and arbitrary terminals managed by different systems that the user may use. One or more terminals and / or the use schedule information including the location of use of the applications installed in the terminal and the type and / or time of the data generated after use, the terminal as log information for managing the usage status of the user Based on the control unit that controls to integrate and acquire each terminal ID, the integrated log table that stores the data acquired by the control unit as integrated log information in association with the user ID, and the integrated log table. , A generation unit that generates work record information of a user corresponding to the user ID.

Further, in the integrated log information of the work management system and the work management method according to claims 2 and 9 of the present invention, the work schedule information of the user is recorded as the usage schedule information in association with each user ID. It is provided with a function of generating work record information of a user corresponding to the user ID based on the work schedule information and the integrated log information that manages the usage status of a terminal or the like.

Further, in the work management system and the work management method according to claims 3 and 10 of the present invention, a function of determining whether or not the user is in a working state based on the usage schedule information and / or the integrated log information is further added. Be prepared.

Further, in the work management system and the work management method according to claims 4 and 11 of the present invention, the work is operated as work although it is not the scheduled work time, based on the scheduled work time included in the scheduled use information and the integrated log information. It is further provided with a function to perform processing for optimizing work when it is determined that the person is working or is not operating as work even during the scheduled work time.

Further, in the work management system and the work management method according to claims 5 and 12 of the present invention, the scheduled work time included in the usage schedule information and the time determined to be working based on the integrated log information are predetermined. If there is a time difference between the two, it is further provided with a function to perform work confirmation processing based on the travel time from the location of the immediately preceding event to the location related to the immediately following event.

According to the invention described in claim 1 and 8, and a type and / or the time of occurrence of data to be generated after use and use plan information including a use place of the application installed on at least two terminal and / or the terminal Since it is stored as integrated log information in association with the user ID as the usage status of the user's terminal or the like, it is possible to grasp the working situation of the user from a bird's-eye view from the usage status of various terminals or the like.

Further, according to the invention described in claim 2 and 9 of the present invention, since the work schedule information of the user is recorded as the use schedule information, based on the work schedule information and the integrated log information, service users Can be grasped more accurately.

Further, according to the inventions according to claims 3 and 10 of the present invention, since it is determined whether or not the user is in a working state based on the usage schedule information and / or the integrated log information, the terminal used for public and private use. Even in the usage situation such as, it is possible to grasp the work of the user more accurately.

Further, according to the inventions of claims 4 and 11 of the present invention, since the work confirmation process for optimization is performed based on the integrated log information, the scheduled work time included in the planned use information and the integrated even if there is a predetermined time difference between the time it is determined that working on the basis of the log information, it is possible to grasp the work of the user more accurately.

Further, according to the inventions of claims 5 and 12 of the present invention, the travel time is calculated from the data of the place related to the event immediately after from the place of the event immediately before included in the planned use information, and the work confirmation process is performed. from, even when there is a predetermined time difference between the work to that determined the time and work schedule time, on the basis of the scheduler information of the user can grasp the work more accurately.

It is a system block diagram which shows the functional structure of the work management system in one aspect of this disclosure. It is a figure which shows the specific example of the log information. It is a figure which shows the processing sequence of the work management system. It is a figure which shows the specific example of the work management data. It is a figure which shows the specific example of the work record table. It is a figure which shows the work record table at the time of a predetermined time interval between a work start date and time and a logon transmission record. It is a figure which shows the work record table which does not have log information such as a logon transmission record at all. It is a figure which shows the specific example of the information which is notified to a superior when an inappropriate work record table is generated. It is a sequence diagram which shows the log information acquisition process. It is a sequence diagram which shows the process of logging on and managing each terminal 50 independently. It is a sequence diagram (No. 1) for management that allows logon to only a single terminal. It is a sequence diagram (No. 2) for management that allows logon to only a single terminal. It is a hardware block diagram of the work management server 100 in this disclosure.

An embodiment of the present invention will be described with reference to the accompanying drawings. When possible, the same parts are designated by the same reference numerals and duplicate description is omitted.

FIG. 1 is a system configuration diagram showing a functional configuration of a work management system according to one aspect of the present disclosure. As shown in FIG. 1, this work management system includes a work management server 100, a general log management server 200, and a schedule management server 300. The terminals 50 (user terminals 51 to 54) are communication terminals having different forms, and are a notebook personal computer, a desktop personal computer, a tablet terminal, and a smartphone, respectively.

The terminal 50 is a terminal that can be used by logging on based on a user ID and used in at least one business (for example, a virtual terminal managed as a terminal used in OA business, a FAT terminal, and / or a mobile terminal or a smartphone. , Tablet), but not shown, any terminal whose logon is not necessarily a condition for using the terminal (mainly privately used but can be used for business, mobile terminals and smartphones, Control electronic devices including IoT (Internet of Thing) -related sensors that are not intended for use in OA operations, remote control devices such as drones, and electronic control devices installed in automobiles from remote terminals. (Including business terminals used in the above) and the applications themselves installed on those terminals may be used as different terminals. In addition, the remote terminal can be used not only when the user remotely operates the virtual terminal or client PC, but also when the user does not directly operate the remote terminal, the operation is performed based on the application and the result is monitored. (Factory Automation), RPA (Robotic Process Automation), AI (Artificial Intelligence), electronic control devices, robots, drones, flying cars, airplanes, and other electronically controlled terminals. Is also good.

A virtual terminal is a virtual machine such as a client PC logically built in a virtual server, and has a configuration in which applications required for virtualization can be started using an area allocated to each user. .. Then, the screen information displayed as a result of activating these applications is displayed on a terminal or the like connected remotely.

Therefore, even if one virtual terminal is used from multiple terminals that can access the virtual server, the same virtual terminal will be displayed, and logon / logoff and operation and monitoring of applications installed on the virtual terminal will be displayed. Logs such as etc. are basically temporarily accumulated in the virtual server.

On the other hand, logs of virtual terminal operations and monitoring generated by logging on to a virtual terminal, logon / logoff to a terminal connected remotely (hereinafter referred to as a remote terminal) itself, and installation on a remote terminal Since it is independent of the log of application operation and monitoring, it is managed separately. Especially, the log related to the remote terminal when using a smartphone or tablet as a remote terminal is basically different from the log of the virtual terminal. Logs are managed.

In addition, the FAT terminal is connected to a network provided in each company, a publicly installed work environment such as SOHO, an Internet cafe, etc., and an application is installed in the terminal in the same manner as a general client PC. , It is configured to be available at logon.

For any terminal for which logon is not necessarily a condition for using the terminal, an application according to the operating system of the terminal and an application according to the purpose of business use are installed, and access restrictions and logs are basically installed on different systems. Management is performed as needed, and it is configured so that log information of terminals and the like can be used via the Internet and the like.

Hereinafter, when the aspect of the present invention is described, it is expressed as a terminal 50, but it goes without saying that the terminal and the like described above are included.

In the work management system according to one aspect of the present disclosure, the user logs on from any terminal including these user terminals 51 to 54 using one user ID, thereby performing centralized management of the user in the work management system. It can be carried out. Hereinafter, each component will be described.

First, the functional configuration of the work management server 100 will be described. The work management server 100 includes an integrated control unit 101, a terminal log information aggregation unit 102, an attendance and departure optimization processing unit 103, a work record management table 104 (integrated log table), an operation record management unit 105 (generation unit), and an appropriate operation determination unit. It includes 106 (determination unit), an operation record table 107, and a screen lock control unit 108.

The integrated control unit 101 is a part that collects log information of the terminal 50 from the comprehensive log management server 200 by communicating with the comprehensive log management server 200 via a network.

The terminal log information aggregation unit 102 uses the logon / log-off information of the terminal 50 from the logon status management table 202 of the comprehensive log management server 200, and from the server side at regular time intervals (for example, every 5 minutes) after logging on to the terminal 50. Monitoring log information that monitors the usage status of terminals, etc. is acquired via the integrated control unit 101, sorted daily and in chronological order, and the log information that makes the terminal ID the same is listed as integrated log information as a group. This is the part that performs the processing to do so.

This integrated log information includes operation log information indicating the operation of the terminal 50 by the user, such as a sleep operation on the terminal 50, a terminal lock operation described later, for example, an operation of an application such as mail transmission, a position information of the terminal 50, and a user. Information indicating the usage schedule information of the terminal 50 and the access history to the terminal 50 may be included. In addition, the user's business trip or outing event information described in the work schedule information, and related information including the location information of the terminal 50 corresponding to the event information or the event date and time may be included.

The usage schedule information includes the work schedule information, which is the schedule data of the user, in which the terminal 50, which may be used in the business subject to the work management, is registered in the schedule management server 300 together with the schedule information of the user. The usage schedule information of the terminal 50 and the information on the work place, the date and time and place of the business trip or going out in each schedule information are acquired, and the ID of the registered terminal 50 is used within the scheduled work time from this information. It is information that it is planned.

Needless to say, the terminal 50 used by the user may be managed by a server different from the schedule management server.

There are various management levels for this usage schedule information, but in addition to the management level that allows the use of the most flexible terminal 50, which allows business use by logging in from all registered terminals 50, the use of the stricter terminal 50 At the management level limited to, if the work place is a company, it is limited to the client PC (FAT terminal) installed in the company, or if the work place is at home, it is installed at home and is mainly used by users for private use. A method of managing after selecting a terminal ID that can be used for notebook PCs, smartphones, tablets, etc. that can be carried out, etc., depending on the location and time of business trips, etc. You may take it.

These business virtual terminals, client PCs (FAT terminals), smartphones and tablets, virtual terminals, client PCs (FAT terminals) that are mainly used for private use and also used for business, terminal serial numbers of smartphones and tablets, etc. An ID that can identify the terminal 50 is registered in advance. In the present embodiment, it is referred to as event information including the log type included in the integrated log information and the user's schedule information such as business trips, including the scheduled working hours of the user determined by the approval of the monthly operation application and the overtime application described later. ..

The attendance / leaving optimization processing unit 103 associates the usage schedule information for each user ID with the log information integrated for each terminal ID from the integrated log information acquired by the terminal log information aggregation unit 102 with the user ID. and integrated log table, and generates a work record information indicating the service of the user corresponding to the user ID in accordance with the work management level.

Specifically, for example, for OA work centered on desk work, use from any of the registered terminals 50, which is the level for the most flexible terminal usage management, is permitted, and is integrated for each ID of the terminal 50. The usage record (including the use of intermittently divided time) is stored in the operation record table assuming that the user is using the business and has a work record, and the usage record for each ID of the terminal 50 is arranged in chronological order. Information that has been used by a plurality of terminals 50 at the same time is superimposed, and integrated work record management information ( work management data) is generated for each user ID and stored in the work record management table 104.

Here, depending on the level of terminal usage management, the terminal 50 used at the work place, the terminal in the home or public work space or cafeteria, the mobile terminal used while moving to a business trip destination, the smartphone, the tablet, etc. The terminals 50 may be distinguished, and based on the user's schedule information, management may be performed using only the appropriate terminal usage record as the work record, or the usage location and usage time of the terminals 51 to 54 may be determined in an integrated manner. It is also good as a work record.

Even when it is necessary to urgently use a terminal for which the ID of the terminal 50 that manages the terminal use is not registered in advance, the reason for the use and the terminal 50 are given to the user's superior as in the case of the overtime use application described later. Needless to say, the terminal use is permitted after the terminal use application with the ID of is approved and approved.

In addition, for users engaged in medical services and customer service services that provide services face-to-face with patients, customers, business partner personnel, etc., centering on tasks other than the illustrated desk work tasks, the client PC In addition to the usage record, for example, the use of a mobile terminal, a smartphone, or a tablet used for business communication, particularly the call record and the transmission record of e-mail, SMS, chat, etc. may be mainly managed.

In this case, even during the time when the user has not used the terminal 50 by himself / herself, the actual work situation is based on the integrated log information including the presence information acquired from the sensor information of the conference room or the examination room to which the entry / exit management sensor is attached. The work record management information may be generated as if it existed and superimposed on the usage record of the terminal 50.

Also, in system monitoring work, if a problem occurs in the system, the system is remotely operated and restarted, and the person in charge of system monitoring who takes measures against the problem remotely monitors the system status. The startup status and operation status of the monitoring application of the terminal 50 may be collected as a log from the monitoring application, or a log may be collected from the access management server on the system. From these integrated log information, the user's work It may have a track record.

By the way, after the integrated work record management information for each user ID is stored, it is determined whether or not the user is in the work state based on the work schedule information included in the usage schedule information and / or the integrated log information. Specifically, it is classified into work performance management based on three cases: (1) only the usage schedule information, (2) only the general log information, and (3) both the usage schedule information and the integrated log information. The details of each process are different.

First, in case (1), when the user originally registered the usage schedule of the terminal 50, but the integrated log information could not be collected for some reason, or the user was infected with the new coronavirus or influenza virus. This applies to cases such as when the terminal 50 is not actually used for business purposes because the user is forced to take a vacation in a hurry due to poor physical condition or the like.

Since there is no integrated log information for the target date in the work record table, it can be systematically determined that the work status is not met. However, even if the user actually works on the target day and uses the terminal 50, it is assumed that all the integrated log information including the logon information cannot be acquired due to a problem on the terminal 50 or the system side. Therefore, as will be described in detail later in the explanation of FIG. 3 , in order to perform the process for optimizing the work , the operation performance confirmation notification is sent to the user's superior, and the user and the user's superior communicate with each other. By confirming the work record and approval by the user's superior, it may be admitted that the work was performed according to the scheduled work time from the record of zero work record.

Further, in the case of (2), the integrated log information is collected for some reason on the target day when the user has not originally registered the usage schedule of the terminal 50 such as a holiday, or as in the conventional technology (although it is said). However, it goes without saying that the logs from various terminals 50 are not integrated), and when the management level that performs the minimum work management is selected using the logon / logoff information from the terminal 50, the above From the comprehensive log information, it corresponds to the case where it is treated as having a work record of the user based on the log of the start and end of use of at least one of the terminals 50 for business use and various log information. .. However, it is out of the question that a user engaged in OA work leaks a vacation application or a transfer holiday application (although it is necessary for the user to apply for vacation even after the fact and obtain approval from the user's superior), system monitoring In business and customer service, it may be necessary to work in a hurry on holidays due to system circumstances or customer convenience. Therefore, as in the case of (1), as a process for optimizing work, the user Notification of operation record confirmation is sent to the superior, and by confirmation of the work record exchanged between the user and the user's superior and approval by the user's superior, it is acknowledged that the employee has worked as a work day or a transfer work day. You may. In addition, since there is a possibility that log information that is not used for business purposes such as logs from private terminals may be collected, it is possible to perform processing that is not treated as work in the exchange between the user and the user's superior.

Further, the case (3) is the work performance management based on both the scheduled work time and the integrated log information included in the planned use information, and is applied to the most general case in the present invention to perform a wide variety of work management. It is possible. Originally, the work schedule information included in the usage schedule of the terminal 50 by the user is registered based on the approval of the monthly operation application and the overtime schedule application, which will be described later. Although there are differences in the work styles and work styles adopted by various companies, the log information of the terminal 50 is stored in the logon status management table 202 every moment, and batches are performed on a user ID and daily basis (0:00 to 24:00). This is a case where work performance information based on processed integrated log information is generated on a daily basis.

For example, its service record time (e.g. 28 minutes to 20 8:00 min 9:00), compared work schedule information (e.g. 9:00 30 minutes to 20) in attendance optimizing unit 103, a predetermined time difference (e.g. If there is no difference exceeding 15 minutes), it is treated as a person who worked according to the scheduled working hours, the generated working hours are registered as the correct working hours, and the actual working hours are actually paid. It shall be the time.

In addition, since users engaged in OA work generally use the terminal 50 registered during the scheduled working hours (or rather, they cannot work without the terminal), they are uniquely treated as scheduled use information. It is also possible. In addition, the scheduled working hours vary depending on the company, industry, and work. For example, in general OA work, day shifts are from 9:00 to 17:30, such as medical staff and system managers. Night shift from 23:30 to 9:00 the next morning, shift system from 16:00 to 24:00 and 23:30 to 9:00 the next morning, part-time work every Monday, Wednesday, and Friday at 12:00 The working hours are set for each company, such as from 17:00 to 17:00. In addition, companies that adopt a shift work system have a work style that allows the start and end times of day shifts to be shifted by one hour before and after, and in the case of a flextime system, they are preset within the work hours of one day. You may flexibly set working hours by using categories such as core hours, contract employees, full-time employees, part-time employees, and part-time employees.

On the other hand, when it is detected that the operation log of the terminal 50 cannot be collected for more than a predetermined time due to some user's action, the function of the terminal 50 sleeps or the monitoring log is displayed beyond the scheduled working time (including divided work). There may be a time when the screen is locked from the monitoring server side (hereinafter referred to as the lock time), which is collected in the integrated log information.

Since the time zone controlled for each purpose is the time when the user cannot continue the business in common, the judgment criteria are set according to the work management policy of each company. If there is a time difference from the scheduled usage time (scheduled working hours), the actual working hours after optimization after the work confirmation processing (overtime application and approval) is performed by the attendance optimization judgment department. It will be the actual operating hours that are subject to salary payment. The sleep process is described in the process on the terminal side for suppressing the power consumption of the terminal 50, and the screen lock process is described in the process on the monitoring server side for suppressing the long working hours of the user. It is not limited to this case, and any process may be processed by the application installed in the terminal 50, or may be processed based on the operation log or the monitoring log on the server side. After that, when the user continues to use the terminal 50, it may be set so that authentication such as a password and approval of the superior are required.

The important point here is that, based on the scheduled working hours included in the scheduled usage information and the integrated log information, the working hours are not scheduled working hours, but they are operating as working hours, or they are not operating as working hours even during the scheduled working hours. Efficient work from integrated log information to the extent possible systematically for work styles in which various companies, industries, and businesses exist when there is a predetermined time difference between the time judged to be Is it possible to carry out processing for optimization?

Regarding the above-mentioned work treatment of lock time, it was explained that judgment criteria will be set according to the work management policy of each company, but from the viewpoint of promoting work style reform, the terminal 50 that permits business use The harmful effects of diversity can also occur. For example, if the use of various terminals 50 is permitted, the integrated log information of the target that the user should judge to have worked increases, and the lock time (for example, a seat at a meeting or a business trip) where it cannot be denied that the user was actually doing business For those who had removed it, did not use the terminal, read business materials and books and considered business trips, etc.), in order for the company to avoid violating the Labor Standards Act, it is possible to work unpaid by treating all lock hours as work. There may be a decision based on a policy that excludes gender, that is, emphasizes compliance. On the other hand, in the case of a company that adopts a policy of strictly managing the actual work hours, the time when the user was away from the desk due to a meeting or a business trip, the time to go back and forth between multiple work places of the company to which the user belongs, and so on. Alternatively, the time to move to a business trip location such as a customer or a business partner is related to the event immediately after the location of the immediately preceding event by utilizing the location information in the schedule information of the integrated log information or the location information of the terminal 50, for example. The system may automatically calculate the travel time to the place, or it may be calculated as work by utilizing the presence information based on the information of the IoT device installed at the meeting place. In addition, it is limited to the use of virtual terminals only, and the time until unlocking outside working hours is not treated as work, and basically the time when the virtual terminal is unlocked (time from logon to lock processing) is treated as work. It is also possible to.

The cases described so far are just examples, and if there is a predetermined time difference between the scheduled working hours included in the planned usage information and the time determined to be working based on the integrated log information, the company / Needless to say, work confirmation processing may be performed based on the work management policies of various companies such as business type, work, and work style.

Regarding the schedule information such as business trips in the work management system and the work management method of the present invention, the information indicating the business trip and the time zone is acquired from the schedule management server 300 as the work schedule information, and the user actually obtains the information. Is inserted in chronological order of log information including the position information acquired from the terminal 50 in order to confirm the date and time and the place recorded in the event information.

The work record management table 104 is a table that stores the work record management information generated by the attendance / departure optimization processing unit 103.

The operation record management unit 105 is a part that generates a work record table based on the work record management table 104.

The appropriate operation determination unit 106 is a part of the schedule management server 300 that determines whether or not the work record management information is appropriate based on the user's schedule (scheduled work time) and the work record management table 104. When the proper operation determination unit 106 determines that the suitability is not appropriate, the proper operation determination unit 106 performs a predetermined confirmation process on the superior on the job of the user.

The operation record table 107 is a part that stores the work record table generated by the operation record management unit 105.

The screen lock control unit 108 is a part that locks and controls the terminal screen in use when the user receives log information using each terminal 50 outside the scheduled working hours. This is to curb long working hours so that employees do not work overtime that is not approved by their superiors.

Next, the comprehensive log management server 200 will be described. The comprehensive log management server 200 includes a communication control unit 201 and a logon status management table 202.

The communication control unit 201 is a part that communicates with the terminal 50, the work management server 100, and other log information servers of the terminal 50 managed by different systems (not shown) via a network.

The logon status management table 202 is a part that stores log information such as access status, operation log, and monitoring log of the terminal 50 acquired via the communication control unit 201.

Specifically, the logon status management table 202 sets the processing types such as logon / logoff processing, sleep processing, operation processing of the terminal 50 by the user, response processing to the periodic monitoring signal from the server, and the time when the processing occurs. The log type and occurrence time of the target terminal 50, which is acquired from a server (not shown) that manages the access status of each terminal 50 and is managed by itself, is the log before being integrated for each ID of the terminal 50 each time the log is acquired. It is stored moment by moment as information (hereinafter referred to as general log).

The operation log information is information indicating that the terminal 50 is being operated, and it may be possible to collect necessary log information for each application installed on the terminal 50. In that case, the terminal 50 may be used in advance. Install a monitoring application that can collect various logs.

When acquiring a log of the access status of the terminal 50, which is not under the control of the log management server, from a server or the like (not shown), it is necessary to consider the privacy of the user so as not to conflict with the confidentiality of communication.

In particular, when a user acquires a log of sending an e-mail using the terminal 50, the e-mail destination is a customer or a transaction in order to determine whether or not the user is using the terminal 50 when permitting the use of the terminal 50 in advance. It is desirable to obtain consent to be collected together with the log of user's operation etc. for the purpose of confirming whether it is the destination address used by the destination or other destinations.

In addition, the screen is locked in order to prevent the terminal 50 from being operated for a predetermined time and going to sleep, which does not originally correspond to the operation log, and to suppress the use of the terminal 50 during non-working hours based on the monitoring log. The processing is also acquired and stored as integrated log information. Specifically, the log information shown in FIG. 2 is stored. As shown in FIG. 2, at least the log information includes time, user ID, terminal ID, and log type (content).

Next, the schedule management server 300 will be described. The schedule management server 300 includes a monthly operation processing unit 301 and a schedule data storage unit 302.

The monthly operation processing unit 301 is a part that sets the scheduled work date and time according to the work style (flex work, fixed time system, etc.) of the user and stores it in the schedule data storage unit 302. This setting operation is performed by an administrator such as a user, a superior thereof, or an operator.

The processing of the work management system configured in this way will be described. FIG. 3 is a diagram showing a processing sequence of a work management method in a work management system.

At the terminal 50, the user makes a monthly operation application and an overtime application (S101, S102). In this method, when the user operates the terminal 50, the schedule data is registered in the schedule management server 300 (S103).

The superior of the user refers to the schedule data of the user of the schedule management server 300 by operating the superior terminal 500 (personal computer or the like), and approves the schedule data (S104). This approval operation is performed by the superior clicking the approval button or the like displayed on the personal computer.

At a predetermined timing (for example, once a day) in the work management server 100, the attendance / departure optimization processing unit 103 is based on the work start date / time and work end date / time described in the schedule data of the schedule management server 300. Therefore, a template of work record management information (work record management table 104) describing the work start date and time and work end date and time is generated for each user (S105). FIG. 4A shows a template of work performance management information. As shown in the figure, the work start date and time and the work end date and time are stored for each user ID and working day (working day). The column in which the start date and time of work is not described indicates a holiday, a day without work, or a scheduled vacation date.

On the other hand, in the comprehensive log management server 200, the communication control unit 201 collects log information (logon / logoff, monitoring log information) from the terminal 50 and stores it in the logon status management table 202 (S106). Further, the communication control unit 201 collects the user's schedule (business trip event, etc.) from the schedule management server 300 and stores it in the logon status management table 202.

Then, in the work management server 100, the terminal log information aggregation unit 102 collects and integrates the log information from the comprehensive log management server 200 at a predetermined timing (for example, once a day at a predetermined time). The attendance / leaving optimization processing unit 103 optimizes and stores the collected log information for the template of the work record management information (S107).

Here, the optimization process (retable) will be described in detail. The work record management information is generated from the raw data stored in the comprehensive log management table accumulated in chronological order according to the data acquisition time. Then, as log information for managing the usage status of each terminal 50, the IDs of one or more terminals 50 and the like are integrated and stored in the table. FIG. 4B is an example of work performance management information that has been integrated and optimized. As shown in FIG. 4 (b), this work record management information is the log information for each of the same working days (here, 2019/12/1) of user A (user ID: A), and the terminal ID accessed by the log information. It is information aggregated for each. For example, in FIG. 4B, the record R1 stores the logon time and the logoff time transmitted from the terminal 50 (terminal ID: A) as the logon transmission record and the logoff transmission record. In the monitoring log record, log monitoring information based on the presence or absence of user operation is stored every predetermined time (here, 5 minutes) after logging on. Record R1 indicates that the monitoring log was recorded every 5 minutes from 9:33.

When the monitoring log of the terminal is detected for a certain period of time (for example, 15 minutes) outside the scheduled work hours, the screen lock control is performed collectively for the terminal currently in use and other terminals that are not logged off. This is a function to prevent working during unordered hours and to optimize working hours such as suppressing long working hours.

The targets of work optimization are as follows.

(1) If there is a difference of, for example, one hour or more between the hours determined not to work within the scheduled working hours, the data is transmitted to the superior and displayed as the non-working hours. The superior confirms with the user, confirms the actual working conditions at that time, and if it is not working, fills in the time off, and if it is working, writes that fact and approves it. The processing optimizes working hours.

(2) For example, monitoring logs every 5 minutes are accumulated three times in total at the time when it is determined that the user is working outside the scheduled working hours, and the actual usage of the terminal 50 for 15 minutes is the scheduled working hours on holidays and weekdays. If it is detected based on the integrated log information, the terminal 50 currently used as a business unordered is screen-locked and the time when it occurs is notified to the superior. Upon receiving the contact, the superior confirms the actual work situation with the user, instructs the user to correct the scheduled work time if it is work, confirms the cause of the alarm notified by the monitoring log etc. if it is not work, and works. Register the process to the effect that it is not. As a result, the working hours of the user are optimized. The attendance / leaving optimization processing unit 103 aggregates the monitoring log information transmitted from the same terminal during the logon transmission record and the logoff transmission record as one record.

Similarly, when the attendance / leaving optimization processing unit 103 acquires only the logon time and cannot acquire the logoff time, the sleep state is confirmed in the monitoring log among the monitoring logs after the logon time on the same terminal. Aggregate monitoring logs up to the time into one record. Record R2 indicates that the monitoring log was recorded every 5 minutes between the logon time transmitted from the terminal 50 of the terminal ID: E and 10:25 to 13:30, and temporarily went to sleep at 10:50. Indicates that it has become. Record R21 then indicates that he logged on again at 10:55 and went to sleep again at 13:30. Therefore, it can be determined that the working hours of the user, including the record R2 and the record R21, are from 10:25 to 13:30.

Record R3 does not store either the logoff time or the sleep time. This is because the user logged on from the smartphone D while using the terminal B (terminal ID: B). The attendance / departure optimization processing unit 103 aggregates the logon time and the monitoring log having the same terminal ID in one record R3 between the logon time and the next logon time. In record R3, the logon time is 14:58, and the monitoring log is recorded every 5 minutes thereafter. Then, since the smartphone D is used without logging off the terminal B (terminal ID: B), the records R4 for the smartphone D are aggregated. Here, since the sleep time is 16:45, it can be determined that the working hours are 16: 15-16: 45.

In record R5, the user is logged on from terminal C (terminal ID: C) at 17:02. After that, the monitoring log is recorded every 5 minutes. At this time, since the scheduled work time has passed and the user is logged on, the screen is temporarily locked (or the terminal is locked) at 18:05. The monitoring log is recorded from 17:02 to 20:02. Therefore, it can be determined that the working hours are from 17:02 to 20:02.

The operation record management unit 105 refers to each record in the work record management table 104 and generates a work record table (S108). FIG. 5 is a specific example of the work record table. The record R11 is information represented as an operation record by aggregating each record from the record R1 to the record R5 of the work record management table 104 shown in FIG. 4 (b).

Specifically, the operation record management unit 105 aggregates a plurality of records on the same operation day in the work record management table 104 into one, and sets the earliest monitoring log time and the latest monitoring log time in the work record management table 104. Derived from the logon transmission record and other monitoring logs, and described in the work record table. Further, the operation record management unit 105 describes the terminal lock start (time), terminal lock end (time), sleep earliest time, and sleep latest time in the work record table with reference to the work record management table 104. Generate.

Next, in FIG. 3, the proper operation determination unit 106 determines whether or not the generated work record table is valid (S109). Specifically, the appropriate operation determination unit 106 determines the work start date and time, the work end date and time, the earliest monitoring log time, and the latest monitoring log in the work record table described based on the approved schedule data of the schedule management server 300. By comparing with the time, it is judged whether or not the work record table is appropriate. If the schedule data is not reflected in the work record table, compare it with the schedule data.

For example, the appropriate operation determination unit 106 compares the logon transmission record (or the earliest monitoring log time) in the work record table with the work start date and time, and is appropriate based on whether or not the time difference is equal to or greater than a predetermined time. Judge whether or not. Similarly, the logoff transmission record (or the latest monitoring log time) is compared with the work end date and time.

When the operation record management unit 105 determines that the work record management information is appropriate by the appropriate operation determination unit 106, the operation record management unit 105 stores the generated work record as an operation record as a salary payment target in the operation record table 107 (S111). ). The time unit for registering the operation record may be set in units of 15 minutes from the correlation with the unit of working hours specified in the work management policy, the monitoring time until screen lock processing, and the reference time for determining optimization. Although it may be set in minutes, it is desirable that the operating hours subject to salary payment be set so that wages are not unpaid by rounding up the hours in the above unit.

On the other hand, if the proper operation determination unit 106 determines that the time interval is equal to or longer than a predetermined time, it determines that this work record is not appropriate (S110: No). In this case, the proper operation determination unit 106 performs the work record confirmation process, and transmits, for example, the operation record confirmation notification to the predetermined superior terminal 500 (the terminal of the user's boss). Upon receiving this notification, the superior judges the validity of the user's work performance.

By the way, when the work record table is generated, the interval from the logoff time (or sleep time) to the next logon time may be less than a predetermined time in each record of the work record management table 104. In the above description, the operation record management unit 105 ignores this and generates a work record table including the logon transmission record and other various log information. However, as described above, there is a predetermined time interval between each record. May be. Even in that case, the proper operation determination unit 106 operates so as to confirm the superior when it is determined that the work record table is not appropriate after comparing with the scheduled work time of the schedule management server 300.

For example, it is assumed that the proper operation determination unit 106 has a predetermined time difference between the records. It is assumed that there is a predetermined time or more between the logoff time or sleep time (or the last time of the monitoring log time) of the immediately preceding record and the logon time of the record immediately after that.

The appropriate operation determination unit 106 refers to the schedule management server 300 and determines whether or not there is a schedule for going out, a business trip, or a time off at the relevant date and time and the time zone, so that the work record table is appropriate. Judge whether or not.

At that time, the travel time may be considered based on the location information of the business trip destination or the outing destination. For example, based on the distance between the information for specifying the position or location described in the schedule data and the location information described in the log information, it is determined that the vacancy is the travel time. The location of the log information is based on GPS and other access point information.

If it is inappropriate, the operation record confirmation notification, which will be described later, includes information to the effect that there is no actual work during that time period.

Upon receiving the operation record confirmation notification in the superior terminal 500 (S112), the superior determines whether or not correction is necessary based on the content (S113). When the superior determines that the correction is necessary, the superior terminal 500 sends a notification to the terminal 50 requesting the correction of the working hours according to the operation of the superior. Upon receiving this, the terminal 50 reapplies for the approved application content (S114).

In the schedule management server 300, the monthly operation processing unit 301 corrects the schedule information (S115) and notifies the superior terminal 500 to that effect. Upon receiving the notification of the correction of the schedule information in the superior terminal 500, the information performs the approval operation (S116).

The work management server 100 generates and stores a work record table based on the approval operation (S110). For example, a work record table in which the work start date and time and / and the work end date and time are changed is generated according to the user's reapplication. When the user takes a time off during the working hours, a time zone for the time off is provided in a separate column in the work record table, and the time is recorded in the time off column.

Next, the process in step S109 will be described in detail with reference to a specific example. FIG. 6 is a specific example of the operation record table 107 when there is a predetermined time interval between the work start date and time and the logon transmission record. In record R21, there is a 55-minute time interval as a predetermined time between the work start date and time and the logon transmission record. In addition, one hour is between the work end date and time and the sleep latest time.

In this case, the proper operation determination unit 106 notifies the superior terminal 500 to that effect. The superior confirms with the user by operating the superior terminal 500 as described above. Here, the user corrects the work start date and time to 10:00 and the work end date and time to 16:30, or makes a retroactive application for time leave and corrects the schedule data. The operation record management unit 105 performs a process of modifying the operation table in accordance with the modification of the schedule data. Here, the work start date and time and the work end date and time will be updated.

FIG. 7 is a diagram showing a work record table in which there is no log information such as logon transmission record. As shown in the figure, the log-on transmission record and the like are not stored in the record R31. This happens when the user takes a sudden vacation. If the information is missing, the proper operation determination unit 106 determines that the information is not suitable and performs the confirmation process on the superior terminal 500. The superior confirms with the user and responds to apply for vacation retroactively.

FIG. 8 is a diagram showing a specific example of information notified to the superior when an inappropriate work record table is generated.

FIG. 8A shows a work record table. The appropriate operation determination unit 106 compares the work start date and time with the earliest monitoring log time, and also compares the work end date and time with the sleep latest time, and when the time difference is equal to or longer than a predetermined time, FIG. 7B is shown in FIG. The information shown in is transmitted to the superior terminal 500. This information indicates that the category is unemployed. The information indicating the classification is information that is automatically added by the work management server 100 as undecidable when there is a time difference as described above. The superior sees this information and approves it or asks the user if necessary.

Next, various log information acquisition processes in the comprehensive log management server 200 will be described with reference to FIGS. 9 to 12. FIG. 9 is a sequence diagram showing a general log information acquisition process.

When the user performs a logon operation on a virtual terminal or the like, a logon request is transmitted to the authentication server (S201). The authentication server 400 is a server that authenticates the logon of each terminal 50. The authentication server 400 performs an authentication process based on the password entered by the user at the time of the logon request (S202, S203). Here, in addition to the predetermined password, authentication using a one-time password (OTP) is performed. The one-time password is a password issued by the superior at the request of the user when the user uses the terminal outside the scheduled working hours. If the authentication is denied here, the process returns to S201 again.

When the authentication is permitted, the terminal 50 is logged on and can be operated (S204). Further, in the comprehensive log management server 200, the logon time is stored in the logon status management table 202 in association with the user ID and the terminal ID (S205).

When the input detection is stopped for a predetermined time (S206: NO), the terminal 50 goes into a sleep state (S207). On the other hand, when the terminal 50 detects the input within the predetermined time (S206: YES), the terminal 50 saves the operation log together with the time, or saves the sleep state together with the time (S208). Then, the terminal 50 periodically transmits the operation log and the sleep state as a monitoring log (S209).

The general log management server 200 receives the monitoring log and stores the monitoring log in the logon status management table 202 (S210). Steps S205 to S215 are performed as post-logon processing.

The comprehensive log management server 200 checks the monitoring log, and if the company adopts a management level that limits the number of terminals 50 used for work to one, or if it is used other than when scheduled to work, the terminal 51 can be used. In a certain case (S211), a terminal lock operation is performed on other terminals 52 to 54 (S212). The scheduled working hours may be acquired from the schedule management server 300 in advance. Further, the terminal ID used by the user may be registered in advance, and the use of another terminal may be determined based on the registration.

When the terminal is locked, the terminal 50 either returns (S213) or logs off or shuts down (S214) according to the user's operation, and enters the logoff state (S215). The return process is performed by verification using a one-time password.

In this way, the logon information or the monitoring log of the terminal 50 is stored in the comprehensive log management server 200 with the time.

FIG. 10 is a sequence diagram showing a process of independently logging on and managing each terminal 50. Here, the time when the user terminals 51 to 53 are logged on independently is shown.

When the user terminal 51 makes a logon request (S301), the authentication server 400 is subjected to the authentication process (S302), and when the authentication is permitted, the user terminal 51 is in the logon state (S303). Further, the authentication server 400 notifies the general log management server 200 that the user terminal 51 is logged on.

After that, when the above-mentioned post-logon processing (S304) is performed and a logoff or the like is detected (S305), that fact is transmitted to the authentication server 400 (S306). The authentication server 400 cancels the authentication based on the logoff notification. The user terminal 51 also logs off (S307).

Similarly, the user terminal 52 and the user terminal 53 also independently perform logon / logoff processing (S301a to S307a, S301b to S307b).

FIG. 11 is a sequence diagram for management that allows logon to only a single terminal. When the logon request is made in the user terminal 51 (S401), the user inputs the password, and the authentication server 400 verifies and authenticates the password (S402). When the authentication server 400 permits authentication from the user terminal 51, the user terminal 51 is logged on (S403). After that, the user terminal 51 performs the above-mentioned post-logon processing (S404).

At this time, a logon request is made at the user terminal 52 by a user operation (S405). In the authentication server 400, the password is collated and authenticated in response to the logon request (S406). If permitted here, the user terminal 51 locks the terminal (S407). In addition, the user terminal 52 is logged on (S408). Further, in the comprehensive log management server 200, the user terminal 51 is in the locked state, the user terminal 52 is in the logged-on state, and their times are stored (S409). After that, the user terminal 52 performs post-logon processing (S410).

Further, here, a logon request is made at the user terminal 53 (S411). The authentication server 400 performs verification and authentication for the password entered in the logon request from the user terminal 53 (S412). If authentication is permitted here, the user terminal 52 is locked. Further, the user terminal 53 enters the logon state (S414), and then the post-logon process is performed (S416). Further, in the comprehensive log management server 200, the information that the user terminal 52 is locked and the user terminal 53 is logged on is stored, and the time is stored (S415).

Here, when the unlock request is made by the user operation in the user terminal 51 (S417), the re-authentication process is performed in the authentication server 400 (S418). This is the same as the verification and authentication process for logon requests. If permitted here, the user terminal 51 is in the unlocked state and is in the logon state (S419). The user terminal 53 is locked (S420). In the general log management server 200, it is memorized that the user terminal 51 is in the unlocked state and the user terminal 53 is in the locked state, and the time is memorized (S421).

When the user terminal 51 is logged off by the logoff operation (S422), the user terminal 51 is in the logoff state. Then, the authentication is canceled in the authentication server 400 (S424), and the user terminal 51 is in the logoff state and the time is stored in the comprehensive log management server 200 (S425).

The following will be described with reference to FIG. FIG. 12 shows a processing sequence inherited from the processing sequence of FIG.

When the unlock request is made in the user terminal 52 (S501), the re-authentication process is performed in the authentication server 400 (S502). If the re-authentication process is permitted here, the user terminal 52 is in the unlocked state (S503). Further, in the comprehensive log management server 200, the unlocking of the user terminal 52 and the time thereof are stored (S504).

When the user terminal 52 is unlocked and then logged off by a user operation (S505), the user terminal 52 is in the logoff state (S506). In the authentication server 400, the authentication is canceled according to the logoff of the user terminal 52 (S507). Then, in the comprehensive log management server 200, the user terminal 52 is in the logoff state and the time is stored (S508).

When the unlock request is made by the user operation in the user terminal 53 (S509), the authentication server 400 re-authenticates (S510), and the user terminal 53 is in the unlock state (S512). Further, in the comprehensive log management server 200, the unlocked state of the user terminal 53 and the time thereof are stored (S511).

When the user terminal 53 is logged off after unlocking (S513), the user terminal 53 is in the logoff state (S514). Further, the authentication server 400 cancels the authentication (S515), and the comprehensive log management server 200 stores the logoff of the user terminal 53 and the time thereof (S516).

FIG. 13 is a hardware configuration diagram of the work management server 100 in the present disclosure. Physically, as shown in FIG. 13, the work management server 100 shown in FIG. 13 has one or more CPUs 11, RAMs 12 and ROM 13 as main storage devices, and input devices 14 such as a keyboard and a mouse as input devices. It is configured as a computer system including an output device 15 such as a display, a communication module 16 which is a data transmission / reception device such as a network card, and an auxiliary storage device 17 such as a hard disk or a semiconductor memory. Each function in FIG. 1 operates the input device 14, the output device 15, and the communication module 16 under the control of the CPU 11 by loading predetermined computer software on the hardware such as the CPU 11 and the RAM 12 shown in FIG. It is realized by reading and writing data in the RAM 12 and the auxiliary storage device 17.

Next, the operation and effect of the work management system in the present disclosure will be described. In the work management system, it is a system that manages the work of the user based on the usage status of at least two or more of a virtual terminal, a FAT terminal, and an application installed on the terminal that the user may use.

This work management system includes usage schedule information including at least two or more virtual terminals, FAT terminals, and arbitrary terminals managed by different systems and / or the terminals and / or the usage locations of applications installed on the terminals. The work record management table 104 (integrated log table) that stores the work record management information, which is the integrated log information that integrates the type and / or time of the data generated after use, and the work record management table 104. Based on the above, the operation record management unit 105 that generates operation record information indicating the work of the user corresponding to the user ID is provided.

With this configuration, even when the user intermittently uses a plurality of terminals 50 (virtual terminal, FAT terminal, other terminals) by using the user ID, the work management server 100 can be centrally used. It is possible to manage the usage status of users. Therefore, the working status of the user can be grasped based on the usage status.

By the way, in the present disclosure, data managed by the terminal 50 or the like by another system (for example , operation log of a smartphone application provided by another company, log information such as call history and location information managed by a server of another company's mobile company, and log information, etc. Various data managed by a system different from the log of the FAT terminal in the company, such as the log information of the work management system of another company and the log information of the virtual terminal of another company) are based on the communication secrets and laws imposed on the telecommunications carrier. , It is difficult to collect logs.

Therefore, in the present disclosure, for example, the work management system or its application is designed to acquire a log when the application is installed by the user (at this time, the user ID and the terminal ID can be uniquely distinguished and centrally managed). It is assumed that a shrink wrap contract is made, which is considered to be agreed by installing.

In addition, since the time when calling for business purposes (there is almost no terminal operation during this period) is also treated as work, for example, after masking the call record (for example, the date and time of the call and the destination phone number) as log information of the mobile terminal or smartphone. It shall be possible to obtain various personal information (such as only the data of the above) and various personal information within the range that does not violate the law.

As a result, log data can be collected from terminals and the like registered as management targets without invading the confidentiality of communications by the Company, which is not a company that manages users or users' terminals and the like.

Under these assumptions, in the present disclosure, since the collected data is first accumulated in chronological order for each log acquisition time, the comprehensive log management server 200 is logged on sequentially as raw data regardless of the terminal ID or user ID. It is accumulated in the status management table 202.

The integrated control unit 101 collects log data from the logon status management table 202 of the comprehensive log management server 200, but when storing the log data in the logon status management table 202 (later work record management table 104), each terminal ID is used. Before integrating (that is, if the terminal 50 is shared, the usage status of multiple user IDs is included) and later tabulated in the work record management table 104 (which requires work for each user ID). , Preprocessing is performed to make it easier to refer to and obtain from the user ID and terminal ID, which are common keys.

After storing once, for example, in batch processing such as daily, the data required as the work record management table 104, which is one step before the final form (operation record table after the optimization process is performed), is stored. , Log data type and occurrence time, terminal ID, location information, user's work place / industry, work style, user's terminal usage schedule information and schedule information, etc. are stored in the logon status management table 202 for each user ID. It is stored in the work record management table 104 by aggregating, analyzing, and extracting based on predetermined conditions determined based on various information (the information stored after the judgment becomes the work performance information judged systematically). NS.

After that, by comparing the work schedule information included in the usage schedule information with the work record information, which is one of the above-mentioned predetermined conditions, it is being moved to the business trip destination even if there is a time difference, whether it is working hours or not. Whether it is (so-called work treatment, etc.), processing is performed to make an appropriate judgment according to various company types and work styles. Processing such as salary payment is performed based on the operation record data, which is the final form stored after the optimization processing is performed.

Further, this work management system further includes a schedule data storage unit 302 (work schedule information table) that stores schedule data, which is the work schedule information of the user, in association with each user ID.

The operation record management unit 105 generates operation record information indicating the work of the user corresponding to the user ID based on the schedule data and the work record management information.

With this configuration, it is possible to generate operation record information including schedule data, and it is possible to facilitate the work management of the user.

Further, the appropriate operation determination unit 106 (determination unit) determines the work state in the work record table based on the schedule data and / or the work record management information. That is, if the difference between the work record table and the schedule data is large, it is judged that the work record table is not suitable.

As a result, the work management of the user can be performed accurately.

The work record information is at least one or more terminals and / or at least information such as a user's business trip or outing event described in the schedule data and user's work schedule information as a place of use of the application installed on the terminal. Based on one or more usage schedule information, logon / logoff operation performed by at least one user operation that is data after use, monitoring performed at predetermined time intervals from the logon time, and the work schedule information. It includes at least two or more data including terminal lock for controlling use, a certain period of time, a sleep state when the user does not operate the terminal for a predetermined time or more, or position information of the terminal.

The appropriate operation determination unit 106 is between the working hours indicated by the schedule data (work schedule information in the work schedule information table) of the schedule data storage unit 302 and the time determined to be working based on the work record management information. If there is a predetermined time difference in, work performance confirmation processing ( work confirmation processing) for work confirmation for optimization is performed. For example, the proper operation determination unit 106 gives a confirmation notification to the superior terminal 500.

This makes it possible to check if there is a work record that differs from the schedule.

Further, when there is a predetermined time difference between the working hours indicated by the schedule data and the hours determined to be working based on the work record management information, the appropriate operation determination unit 106 immediately after the location of the immediately preceding event. Work confirmation processing is performed based on the travel time to the place related to the event. With this configuration, the actual working conditions can be determined in consideration of the user's schedule.

101 ... Integrated control unit, 102 ... Terminal log information aggregation unit, 103 ... Attendance and departure optimization processing unit, 104 ... Work record management table, 105 ... Operation record management unit, 106 ... Appropriate operation determination unit, 107 ... Operation record table, 108 ... Screen lock control unit, 200 ... Comprehensive log management server, 201 ... Communication control unit, 202 ... Logon status management table, 300 ... Schedule management server, 301 ... Monthly operation processing unit, 302 ... Schedule data storage unit, 500 ... Superior Terminal.

Claims (18)

In a work management system that manages a user's work based on the usage status of at least two terminals or applications identified based on the user ID.
Includes at least two or more terminals of virtual terminals, FAT terminals, and arbitrary terminals managed by different systems that the user may use and / or where applications installed on the terminals are used. A control unit that controls to integrate and acquire the usage schedule information and the type and / or time of data generated after use as log information for managing the usage status of the user for each terminal ID of the terminal.
An integrated log table that stores data acquired by the control unit as integrated log information in association with the user ID.
Based on the integrated log table, a generation unit that generates work record information of the user corresponding to the user ID, and a generation unit.
Work management system equipped with. A work schedule information table that stores the work schedule information of the user in association with each user ID as the usage schedule information is further provided.
The work management system according to claim 1, wherein the generation unit generates work record information of a user corresponding to the user ID based on the work schedule information and the integrated log information. The work management system according to claim 1 or 2, further comprising a determination unit for determining whether or not the user is in a work state based on the usage schedule information and / or the integrated log information. The control unit
Based on the scheduled work time included in the scheduled use information and the integrated log information, if it is determined that the work is not working as a work even though it is not the scheduled work time, or it is not working as a work even during the scheduled work time, the work is performed. The work management system according to any one of claims 1 to 3, wherein processing for optimization is performed. The control unit
When there is a predetermined time difference between the working hours included in the usage schedule information and the time determined to be working based on the integrated log information, the travel time from the location of the immediately preceding event to the location related to the immediately following event. The work management system according to any one of claims 1 to 4, which performs work confirmation processing based on the above. The control unit acquires various personal information from the terminal based on the consent of the user.
The work management system according to any one of claims 1 to 5, wherein the work management system is characterized in that. The control unit generates work record information of the user corresponding to the user ID based on the management level of the usage schedule information.
The work management system according to any one of claims 1 to 6, wherein the work management system is characterized in that. In a work management method in which a computer manages a user's work based on the usage status of at least two terminals or applications identified based on the user ID.
The computer is a virtual terminal, a FAT terminal, and at least two or more terminals of any terminal managed by a different system and / or an application installed on the terminal that the user may use. The usage schedule information including the usage location and the type and / or time of data generated after use are integrated and acquired for each terminal ID of the terminal as log information for managing the usage status.
The computer stores the log information integrated for each terminal ID in the integrated log table as integrated log information in association with the user ID.
The computer generates the work record information of the user corresponding to the user ID based on the integrated log table.
A work management method characterized by that. As the usage schedule information, the work schedule information of the user is associated with each user ID and stored in the work schedule information table.
The eighth aspect of claim 8, wherein the computer generates work record information of a user corresponding to the user ID based on the work schedule information and the integrated log information that manages the usage status of the terminal. Work management method. The work according to claim 8 or 9, wherein the computer determines whether or not it is in a work state based on the work schedule information included in the use schedule information and / or the integrated log information. Management method. When it is determined that the computer is operating as a work, although it is not a scheduled work time, based on the scheduled work time included in the scheduled use information and the integrated log information, or when it is determined that the computer is not operating as a work even during the scheduled work time. The work management method according to any one of claims 8 to 10, wherein a process for optimizing work is performed. When there is a predetermined time difference between the scheduled working time included in the scheduled usage information and the time determined to be working based on the integrated log information, the computer relates to the event immediately after the location of the immediately preceding event. The work management method according to any one of claims 8 to 11, wherein the work confirmation process is performed based on the travel time to the place. The acquisition indicates that various personal information is acquired from the terminal based on the consent of the user.
The work management method according to any one of claims 8 to 12, characterized in that. The computer generates work record information of a user corresponding to the user ID based on the management level of the usage schedule information.
The work management method according to any one of claims 8 to 13, characterized in that. In a work management program for managing a user's work performance based on the usage status of at least two terminals or applications identified based on the user ID.
Use including a virtual terminal, a FAT terminal, at least two or more terminals of arbitrary terminals managed by different systems, and / or a place of use of an application installed on the terminal, which the user may use. The schedule information and the type and / or time of data generated after use are integrated for each terminal ID and stored in the integrated log table as log information for managing the usage status of the terminal.
After integrating the log information for each terminal ID , the data type and / or time of the integrated log table is reintegrated for each user ID, and the user's work record information and the operation to be paid are paid. A work management program characterized by retable to enable database linkage with the performance table. Based on the consent of the user, various personal information is acquired from the terminal.
The work management program according to claim 15. As the log information, the usage schedule information of the terminal, the logon / logoff operation performed by the user operation from at least one terminal, the mail transmission log performed by the user operation, the mail transmission log performed by the user operation, and the predetermined time interval from the logon time. It is described in the monitoring log performed in, the terminal lock that controls the use based on the work schedule information, the sleep state when the user does not operate the terminal for a certain period of time, or the sleep state when the user does not operate the terminal for a predetermined time or more, or the work schedule information. At least one of the event information of the user on a business trip or going out, the location information of the terminal corresponding to the event information, the related information including the event date and time, the access data to the terminal, and the probe data constituting the movement history of the terminal. Remember,
The work management program according to claim 15 or 16. On a daily basis, the work start date and time and work end date and time based on the user's schedule, and the earliest and latest logon times based on the logon time are set.
The work management program according to any one of claims 15 to 17.

Images