JP2012150669A - Information analysis device, information analysis method, information analysis system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow a business amount of an employee to be easily grasped.SOLUTION: According to the present invention, working hours irrelevant to business assigned to a user (business loss time) are determined based on an operation history of the user in a terminal device, and a time from a predetermined time to a time (final operation time) when the terminal device is no longer operated is determined as office hours or overtime hours. Further, a business amount of the user is analyzed and output based on the business loss time and the office hours or the overtime hours, so that a manager can easily grasp a business amount of an employee.

Description

  The present invention relates to an information analysis device, an information analysis method, an information analysis system, and a program for analyzing the usage status of each terminal device.

  In recent years of severe economic conditions, many companies tend to reduce overtime. Therefore, managers need to grasp the necessity of overtime by grasping busy employees and idle employees from the workload of each employee.

  According to Patent Document 1, a system for monitoring the usage status of an application running on a terminal and monitoring the usage status of an employee's application is disclosed.

JP 2003-330760 A

  However, with the system of Patent Document 1, it is not possible to grasp the appropriate amount of work for employees. For example, it was not possible to grasp whether the work of a certain employee is small or large.

  Then, an object of this invention is to enable it to grasp | ascertain easily the work amount of an employee.

The information analysis apparatus of the present invention includes, for example, an input unit that inputs a user operation history in the terminal device,
A work loss time determination means for extracting a work time not related to the work imposed on the user from the operation history input by the input means, and determining the extracted work time as a work loss time;
The time when the terminal device is no longer operated is acquired from the operation history input by the input unit, the time is determined as the final operation time, and the time from the predetermined time to the final operation time is determined as the working time. Working time determination means;
Analyzing means for analyzing the amount of work of the user based on the work loss time and the working time;
Output means for outputting an analysis result by the analysis means.

  According to the present invention, based on the user's operation history in the terminal device, the work time not related to the work imposed on the user (work loss time) is determined, and the time at which the terminal device is no longer operated from a predetermined time The time until (last operation time) is determined as working hours. Furthermore, since the user's work volume is analyzed and output based on the work loss time and the working time, the administrator can easily grasp the work volume of the employee.

It is a figure which shows an example of an information analysis system. It is a figure which shows the hardware constitutions of a terminal device. It is a figure which shows the hardware constitutions of a log management server. It is a figure which shows the hardware constitutions of an information analyzer. It is a figure which shows an example of the operation | movement history of an application program. It is a figure which shows an example of the input log | history with respect to an input device. It is a figure which shows an example of the browsing history of a website. It is a flowchart which shows an example of a loss time calculation process. It is a flowchart which shows an example of a loss amount calculation process. It is a flowchart which shows an example of working time calculation. It is a flowchart which shows an example of a work amount determination process. It is a figure which shows an example of an analysis result.

(System configuration)
FIG. 1 is a diagram illustrating an example of an information analysis system. The information analysis system is a system that includes an operation history management server that holds a user's operation history in a terminal device, and an information analysis device that analyzes the operation history. Specifically, the information analysis system includes a plurality of terminal devices 11 a and 11 b, a log management server 12, and an information analysis device 13. The terminal devices 11a and 11b are examples of terminals arranged in a company. The log management server 12 manages an operation log (operation history) of an application program executed in a terminal device arranged in the company. The information analysis device 13 is an example of an information analysis device that analyzes an operation history of an application program in a terminal device arranged in a company. These devices are connected via various networks 50 such as an intranet including a LAN (Local Area Network) and the Internet. When the matters common to the terminal devices 11a and 11b are described, they are simply referred to as the terminal device 11.

  The log management server 12 may be arranged in a company where the terminal device 11 is installed, or may be arranged in another company. Similarly, the information analysis apparatus 13 may be arranged in a company where the terminal device 11 is installed, or may be arranged in another company. Further, the log management server 12 and the information analysis device 13 may be managed by the same company, or may be managed by another company.

  The terminal device 11 includes a monitoring unit 14. The monitoring unit 14 monitors operations in the terminal device (for example, Web usage status, application usage status, mail usage status, user operation man-hours for the input device) and records them as an operation history.

The operation history may include, for example, the following information.
-Terminal device identification information: Computer name, IP address, MAC address, etc.-User name-ID of the user logged in to the terminal device-Operation start date and time-Operation start date and time (operation history At the start of acquisition)
・ Application name of active window: Process name, etc. ・ Title name of active window: Caption name (name of file being edited, etc.)
-Operation time: Application operation time and browsing time for each URL-URL: Web page address-Keyboard keystrokes-Input character code-Full-width / half-width, 2-byte characters / single-byte characters , Unicode / EUC / ISO / JIS, etc. ・ Input confirmed characters: Characters confirmed through the front-end processor (FEP) ・ Moving distance of the pointer of the pointing device ・ Number of clicks of the pointing device The monitoring unit 14 of the terminal device 11 An operation history is created for each preset monitoring period (eg, 1 minute) and transmitted to the log management server 12. Note that the monitoring unit 14 of the terminal device 11 may create an operation history each time the active window is switched.

  Furthermore, since the operation start date and time described later is when the acquisition of the operation history is started, the operation time for each active window can be calculated from the operation start date and time. For example, the operation time of the first active window when the first active window is switched to the second active window can be calculated as the time from the operation start date / time of the first active window to the operation start date / time of the second active window.

  Various conditions are conceivable for the terminal device 11 to transmit the operation history to the log management server 12 from the operation history acquired in this way. For example, when a predetermined time has elapsed (for example, every 2 hours), when an operation history of a predetermined amount or more is accumulated, when the terminal device 11 is started, when the terminal device 11 is instructed to shut down, the log management server For example, when transmission of an operation history from 12 is requested.

  The log management server 12 is an information processing device (computer) that accumulates operation histories collected from each of the plurality of terminal devices 11 and transmits the accumulated operation histories to the information analysis device 13. As shown in FIG. 1, the log management server 12 includes a log management DB 15. DB is an abbreviation for database. The log management server 12 records the operation history for each terminal device (or for each user) in the log management DB 15 based on the operation history received from the terminal device 11.

  The information analysis device 13 is an information processing device including an analysis unit 18 and an analysis result DB 19. Based on the operation history received from the log management server 12 via the network 50, the information analysis device 13 analyzes and outputs the operation content (for example, the user's workload) for the application program and OS. The network interface of the information analysis device 13 is an example of an input unit (accepting unit) for inputting an operation history in the terminal.

  For example, the analysis unit 18 creates an analysis result for each user, each terminal device, or each department, and records the created analysis result in the analysis result DB 19. The analysis result recorded in the analysis result DB 19 is output to the display device as a graph or table, output to a recording medium by a printing device, output as the body of an e-mail, or output as a web page of a website. May be.

  The operation history is transferred from the log management server 12 to the information analysis apparatus 13 via the network 50 or an external storage medium (FD, MO, USB memory, CD-R, DVD-RAM, etc.). Good. The information analysis device 13 includes such a drive device for an external storage medium, and functions as an input means for inputting an operation history in the terminal. The log management server 12 also includes such a drive device for an external storage medium, and functions as means for outputting or writing an operation history in the terminal.

(Hardware configuration)
FIG. 2A is a diagram illustrating a hardware configuration of the terminal device 11. The terminal device 11 is an information processing device such as a personal computer disposed in an office or the like. In the terminal device 11, the CPU 21 functions as various means according to software stored in the hard disk drive (HDD 25). In particular, the CPU 21 functions as the monitoring unit 14 described above, monitors the web usage status, application usage status, mail usage status, user operation man-hours for the input device, etc., creates an operation history, and sends it to the log management server 12 To do. The display device 22 is a user interface for displaying information. The memory 23 includes RAM, ROM, and the like. The network interface 24 is a communication circuit for communicating with other computers via the network 50. The HDD 25 stores an application program 27, a monitoring program 28 that monitors operation man-hours and the like and creates an operation history. The input unit 26 is a pointing device (mouse or touch panel) or a keyboard. The keyboard may be a software keyboard. The input unit 26 may be a voice recognition input unit that recognizes the input voice of the operator using a voice recognition function and inputs an instruction to the CPU 21.

  FIG. 2B is a diagram illustrating a hardware configuration of the log management server 12. The log management server 12 is also a kind of computer. In the log management server 12, the CPU 31 functions as various means according to software stored in the hard disk drive (HDD 35). The memory 33 includes RAM, ROM, and the like. The network interface 34 is a communication circuit for communicating with other computers through the network 50. The HDD 35 stores a log management program 36 and a log management DB 15.

  FIG. 2C is a diagram illustrating a hardware configuration of the information analysis device 13. The information analysis device 13 is also a kind of computer. In the information analysis device 13, the CPU 41 functions as various means according to software stored in the hard disk drive (HDD 45). The memory 43 includes RAM, ROM, and the like. The network interface 44 is a communication circuit for communicating with other computers via the network 50. The HDD 45 stores an information analysis program 47 and an analysis result DB 19. The output unit 46 is a display device or a printing device that outputs analysis results.

(Log management database)
Information on the operation history transmitted from the terminal device 11 to the log management server 12 is recorded in the log management DB 15 of the log management server 12. The contents recorded in the log management DB 15 will be described with reference to FIG. 3, FIG. 4, and FIG.

  3, 4, and 5 are diagrams illustrating examples of recorded contents of the log management DB 15. FIG. 3 shows an example of the operation history of the application that is a part of the operation history received from the terminal device 11. In FIG. 3, terminal information identification information is recorded in a PC name column 301. In the user name column 302, identification information of an employee who has logged in to the terminal device is recorded. In the operation start date and time column 303, data of the date and time when the monitoring unit 14 starts recording the operation history (operation history) is recorded. In the window title column 304, identification information for identifying an application (eg, editing work name, name of editing target file, etc.) is recorded. For example, if the electronic mail program (mailer) is an application, the editing work name is, for example, “Create” and “Re: Thank you” as the mail title. In the process name column 305, the process name (application name) of the process executed in the active window is recorded. In the operation time column 306, the length of time during which the active window is executed is recorded. For example, the time from the operation start date / time of the first active window to the operation start date / time of the second active window is calculated and recorded as the operation time of the first active window. The operation history is recorded in time series according to the order in which one record is created for each active window and the active windows are displayed. The monitoring unit 14 may create one record each time the active window is switched, or may create one record for each window. In the latter case, the operation time measured every time the window becomes an active window is accumulated for each window.

  FIG. 4 shows an example of an input history to the input device that is a part of the operation history received from the terminal device 11. In the PC name column 401, identification information of the terminal device is recorded. In the user name column 402, identification information of an employee who has logged in to the terminal device is recorded. In the operation start date / time column 403, data of the date / time when the recording of the operation history (input history) is started is recorded. The number of keystrokes 404 of the keyboard records the number of times the keyboard has been pressed during a predetermined monitoring period (eg, 1 minute) from the operation start date and time. In the pointer movement distance column 405, data on the distance that the pointer of the pointing device has moved during a predetermined monitoring period (eg, 1 minute) from the operation start date and time is recorded.

  FIG. 5 shows an example of a browsing history related to browsing a Web site that is a part of the operation history received from the terminal device 11. In the PC name column 501, the terminal identification information of the terminal device 11 is recorded. In the user name column 502, identification information of the user (login user) of the terminal device 11 is recorded. The browsing date / time column 503 records the date and time when the Web site was browsed. In the URL column 504, identification information (URL) of a Web site browsed by the user through the terminal device 11 is recorded. The monitoring unit 14 of the terminal device 11 basically monitors the URL of the website to be browsed, and whenever a different URL is specified or changed by the user, the URL that has been browsed so far The browsing history for one record is transmitted. Therefore, each record is recorded in the log management DB 15 in order along the browsing date of the website.

(Loss time calculation process)
FIG. 6 is a flowchart showing the flow of the loss time calculation process. The CPU 41 of the information analysis device 13 executes this loss time calculation process according to the information analysis program 47. As a result, the CPU 41 functions as the analysis unit 18. Before this process is executed, the CPU 31 of the log management server 12 performs an operation history (Web usage status, application usage status, mail usage status, user's status for the input device) from the terminal device 11 according to the log management program 36. Operation man-hours etc.) is received and registered in the log management DB 15.

  In step S <b> 601, the CPU 41 (analysis unit 18) inputs a user operation history in the terminal device to the memory 43. For example, the CPU 41 may receive or read the operation history from the log management DB 15 of the log management server 12, or may read the operation history from a portable data recording medium such as a USB memory or a CD-ROM. Therefore, the network interface 44 and the CD-ROM drive device used for receiving the user operation history in the terminal device held by the operation history management server (log management server 12) as a communication medium or a portable recording medium. It functions as an input means to input via. The operation history reading unit can be freely set by the administrator, such as a user name, a PC name, and an operation start date and time. The CPU 41 reads the operation history for each set reading unit.

In step S <b> 602, the CPU 41 (analysis unit 18) determines whether the read operation history is business or non-business based on information stored in the HDD 45 in advance. The HDD 45 stores a keyword table for discriminating private Web site browsing, private mail exchange, game use, and private multimedia use. In the keyword table, keywords related to business and keywords not related to business are registered. The keywords related to the business are, for example, the URL of the Web site related to the business, the mail address related to the business, and the like. The keywords not related to business are, for example, keywords irrelevant to business, process names of application programs not related to business. Thereby, the analysis unit 18 detects private browsing of the Web site, private transmission / reception of mail, private use of games and multimedia, and classifies these as “out-of-business” operations. The analysis unit 18 also classifies the task as “out of business” even when there is no input operation for a predetermined period (for example, the number of keystrokes is 0 and the pointer movement distance is 0 pixels). If work outside the business is detected (YES in S602), the process proceeds to S603.
If no keyword is registered in the keyword table, it is possible to determine whether the job is out of business or not by a management terminal (not shown) and detect the work outside the business by receiving the result. .

  In S <b> 603, the CPU 41 (analysis unit 18) calculates a non-business time (business loss time) from the operation history and records it in the analysis result DB 19. For example, regarding the operation history of the application shown in FIG. 3, the CPU 41 determines that the window title: Sample5 is “out of business”, and calculates 181 seconds recorded in the operation time column 306 as the non-business time. For the input history to the input device shown in FIG. 4, the CPU 41 determines that the number of keystrokes is 0, the pointer movement distance is 0 pixels, and “pixels out of service”, the number of keyboard strokes is 0, and the pointer movement distance is 0. The operation time that was pixels is accumulated, and the accumulated time is determined as the non-business hours. Regarding the browsing history related to browsing of the website shown in FIG. co. The URL of jp is detected as a “non-business” website, and the browsing time of the URL is calculated as the non-business time. ffff. co. jp is registered in the keyword table in advance. When the CPU 41 detects a mail containing a prohibited word (for example, a drinking party) registered in the keyword table in the title or main part of the mail history related to the mail, the CPU 41 determines that the mail is created as “out of business”. Furthermore, the CPU 41 calculates the non-business hours by setting the work time per one outgoing mail to 3 minutes and the work time per one incoming mail to 0.5 minutes. For example, when non-business mail is transmitted five times and non-business mail is received six times, the non-business time is 18 minutes. The coefficient of 3 minutes or 0.5 minutes is merely an example.

  As for the mail history related to mail, it is also possible to calculate the operation time for each active window from the window title and calculate the non-business hours of the mail.

  In this way, the CPU 41 functions as business loss time determination means for extracting work time not related to the work imposed on the user from the operation history input by the input means and determining the extracted work time as work loss time. .

(Loss amount calculation processing)
In S604 of FIG. 6, the CPU 41 (analysis unit 18) calculates a loss amount from the non-business hours (loss time) calculated in S603, and stores the loss amount in the analysis result DB 19. For example, the CPU 41 calculates a numerical value obtained by multiplying the non-business hours by the labor cost per unit time as a loss amount, and registers it in the analysis result DB 19.

  FIG. 9 is a diagram illustrating an example of the analysis result DB 19. In the user name column 901, identification information of the employee who is the analysis target is recorded. In the loss amount column 902, the loss amount for each user calculated in S604 is recorded. In the final operation time column 903, data of time when the user stops operating the keyboard and the pointing device is recorded. In the classification column 904, the classification of the workload is recorded. The final operation time substantially means the work end time. If the work end time is in the overtime hours, the work end time corresponds to the overtime end time.

  The CPU 41 may calculate an annual loss amount. For example, the CPU 41 divides the non-business hours by the operating days of the period in which the operation history is extracted, and multiplies the annual operating days (242 days) by the labor cost per day (4000 yen) to obtain the annual loss amount. And may be registered in the analysis result DB 19. For example, it is assumed that the operation history from February 1 to February 28 is read from the log management DB 15 and the non-business hours during that period are calculated. Further, it is assumed that the working days (actual working days excluding holidays) from February 1 to February 28 were 19 days. The annual loss amount in this case can be calculated from the following formula.

Annual loss amount = non-business hours ÷ 19 × 242 × 4000
Note that the method of calculating the loss amount is an example, and is not limited to this.

  As described above, the CPU 41 functions as a business loss amount calculation unit that calculates the business loss amount by multiplying the business loss time by the coefficient related to the labor cost.

(Working time calculation process)
In general, working hours are the time from working time to working time. The attendance time is generally handled as the work start time determined by the work rules, but it may be the actual attendance time. In an office environment in which a terminal such as a computer is generally used, the attendance time is expected to be close to the time when a user who is an employee starts operating the terminal, for example. Therefore, the time when the operation history is first acquired in the terminal on the day may be calculated as the attendance time. The overtime hours are the time from the end time (overtime start time) determined by the work rules to the leave time.

  By the way, there are cases where employees are not concentrated on work during all working hours and overtime hours. Therefore, in the present embodiment, a method for calculating the substantial working hours and overtime hours using the operation history is proposed.

  FIG. 7 is a flowchart showing the flow of the working time calculation process. The CPU 41 of the information analysis device 13 executes this working time calculation process according to the information analysis program 47.

  In S <b> 701, the CPU 41 reads the operation history for the input device illustrated in FIG. 4 from the log management DB 15. The operation history reading unit can be freely set such as a user name, a PC name, and an operation start date and time.

  In S702, the CPU 41 determines whether there is a key input. For example, the CPU 41 determines whether or not the number of keystrokes in the operation history is zero. If there is a key input, it indicates that the employee was working at the time when the operation history was acquired. Therefore, in this case, the process returns to S701 to read the next operation history. On the other hand, if there is no key input, there is a high possibility that the employee has finished the work at the time when the operation history is acquired, so the process proceeds to S703.

  In step S <b> 703, the CPU 41 determines whether there is an operation on the pointing device. For example, the CPU 41 determines whether or not the pointer movement distance is 0 pixel in the operation history. If the pointer movement distance is not 0 pixel, it indicates that the employee was working at the time when the operation history was acquired. Therefore, in this case, the process returns to S701 to read the next operation history. On the other hand, if the pointer movement distance is 0 pixel, since it is highly likely that the employee has finished the work at the time when the operation history is acquired, the process proceeds to S704.

  In S <b> 704, the CPU 41 determines the operation start date / time of the operation history in which no operation has been performed on both the keyboard and the pointing device as the final operation time, and records it in the analysis result DB 19. That is, the operation start date and time of the operation history in which the operation has been lost for both the keyboard and the pointing device is recorded in the last operation time column 903 shown in FIG. Note that the final operation time may be treated as an employee's return time.

  In S <b> 705, the CPU 41 calculates and calculates the time from the predetermined time (working start time, work time or the time when the operation history is first acquired in the day) stored in the HDD 45 to the final operation time in advance. The time is recorded in the analysis result DB 19 as working hours. The CPU 401 may calculate the time from the overtime start time stored in the HDD 45 in advance to the final operation time, and record the calculated time in the analysis result DB 19 as the overtime.

  Thus, by setting the time when the pointing device and the keyboard are no longer operated as the final operation time, for example, even when the user returns home without shutting down the PC, the accurate final operation time can be grasped. As a result, substantial working hours and overtime hours can be calculated from the final operation time.

  As described above, the CPU 41 obtains the time when the terminal device is no longer operated from the operation history input by the input unit, determines the time as the final operation time, and sets the time from the predetermined time to the final operation time as a working hour. It functions as a working time determination means that determines time. Similarly, the CPU 41 functions as overtime determination means for determining the time from a predetermined overtime start time to the final operation time as overtime.

(Work load classification processing)
FIG. 8 is a flowchart showing the flow of the work amount determination process. The CPU 41 of the information analysis device 13 executes this workload determination process according to the information analysis program 47. Here, the CPU 41 functions as an analysis unit that analyzes the amount of work of the user based on the work loss time and the working hours or overtime hours.

  In S <b> 801, the CPU 41 reads the loss time and working hours or overtime hours for each user from the analysis result DB 19. In S802, the CPU 41 determines whether or not the loss time is less than a predetermined time Th1 (eg, 1 hour). If the loss time is less than the predetermined time Th1, the process proceeds to S803. In S803, the CPU 41 determines whether the working time is less than a predetermined time Th2 (eg, 10 hours). The CPU 41 may determine whether or not the overtime is less than a predetermined time Th2 (eg, 2 hours). If the working time or overtime is less than the predetermined time Th2, the process proceeds to S804. In step S <b> 804, the CPU 41 classifies the user's workload as “appropriate workload” and records the classification in the analysis result DB 19.

  On the other hand, if the working time or overtime is equal to or longer than the predetermined time Th2 in S803, the process proceeds to S805. In step S <b> 805, the CPU 41 classifies the user's workload as “large”, and records the classification in the analysis result DB 19.

  On the other hand, if it is determined in S802 that the loss time is equal to or longer than the predetermined time Th1, the process proceeds to S806. In S806, the CPU 41 determines whether the working time is less than a predetermined time Th2 (eg, 10 hours). Similarly, in S806, the CPU 41 may determine whether or not the overtime is less than a predetermined time Th2 (eg, 2 hours). If the working time or overtime is less than the predetermined time Th2, the process proceeds to S807. In step S <b> 807, the CPU 41 classifies the user's workload as “low” and records the classification in the analysis result DB 19. On the other hand, if it is determined in S806 that the working time or overtime is equal to or longer than the predetermined time Th2, the process proceeds to S808. In step S <b> 808, the CPU 41 classifies the user as “inefficient (working overtime after lazy work)”, and records the classification in the analysis result DB 19.

  In FIG. 8, the working hours and overtime hours are compared with threshold values, but the final operation time may be compared with a predetermined threshold time.

  According to FIG. 9, Usr1 is classified as an inefficient employee, Usr14 is classified as an employee with a small amount of work, Usr21 is classified as an employee with an appropriate amount of work, and Usr22 is an employee with a large amount of work. It is classified. In addition, this invention is not limited to this, You may classify | categorize work volume by making loss time into a loss amount and overtime working time as the last operation time.

  As described above, the CPU 41 determines whether the user is an employee with an appropriate amount of work, an employee with a large amount of work, an employee with a small amount of work, and an inefficient employee according to the work loss time and working hours or overtime hours. It functions as a classification means for classifying into a plurality of classifications including at least one of them as a classification.

(Analysis result output)
FIG. 10 is a diagram illustrating an output example of the analysis result. The CPU 41 of the information analysis device 13 converts the analysis result shown in FIG. 9 into a table or graph and outputs it to the output unit 46. Therefore, the CPU 41 functions as an output unit that outputs an analysis result by the analysis unit. In particular, the CPU 41 graphically outputs the analysis results using the business loss time and overtime hours as coordinate axes.

  Here, the overtime hours will be described, but the working hours may be represented graphically. Further, according to FIG. 10, the loss amount is employed instead of the business loss time, but any may be employed. This is because the business loss time and the business loss amount are measures indicating the work outside the work of the employees. Similarly, according to FIG. 10, the return home time (final operation time) is adopted instead of the overtime hours, but either may be adopted. This is because the overtime, the return time, and the last operation time all indicate the time that the employee is bound by the company.

  That is, FIG. 10 shows a graph in which the loss amount and the return home time (final operation time) are plotted for each user. In this example, a user whose loss amount is ¥ 90,000 or less and whose return time is up to 19:30 can visually grasp that it is “appropriate work amount”. As described above, the CPU 41 may create data that is schematized based on the analysis result.

  As described above, it is possible to grasp the work amount of an employee (user) from information indicating an operation history. By knowing the work of employees, for example, an administrator can allocate additional work to employees who are classified as having a low work volume, or can be assigned to employees classified as working overtime. It is possible to call attention to the fact that overtime is unnecessary by concentrating on daytime work. In addition, by analyzing in units of departments, it is possible to identify departments that have insufficient personnel and departments that have excessive personnel, which can be used as reference when personnel changes.

  Thus, according to the present invention, based on the user's operation history in the terminal device, work time (business loss time) not related to the business imposed on the user is determined, and the terminal device is operated from a predetermined time. The time until the time when it is no longer used (the last operation time) is determined as working hours and overtime hours. Furthermore, since the amount of work of the user is analyzed and output based on the work loss time and the working hours or overtime hours, the administrator can easily grasp the work amount of the employee.

  Further, by classifying employees as users according to business loss time and working hours or overtime hours, the manager can more easily grasp the work volume of the employees. The classification may include, for example, at least one of employees with an appropriate amount of work, employees with a large amount of work, employees with a small amount of work, and inefficient employees. The above four classifications are merely examples, and other classifications may be adopted as long as the classifications can grasp the work amount of employees.

  Also, by calculating the amount of business loss, it becomes possible to grasp the operational efficiency of each employee in monetary terms. This will enable managers and managers to increase management efficiency.

  Further, if the analysis result is graphically output using the business loss time (business loss amount) and the working time or overtime time (return time or the last operation time) as coordinate axes, the manager visually recognizes each employee's You will be able to understand the workload. In addition, the diagram will make it easier for managers to grasp the amount of work among employees.

<Other embodiments>
The log management server 12 and the information analysis device 13 described above may be realized on the same server, or may be executed on different servers. In the former case, there is an advantage that the log management server 12 and the information analysis device 13 do not need to perform data communication through the network 50. In this case, the information analysis apparatus 13 includes a log management DB 15, an analysis unit 18, and an analysis result DB 19. As described above, by realizing the log management server 12 and the information analysis device 13 on the same server, it is possible to manage the operation history and analysis results in the same company. Therefore, analysis considering security can be performed.

  In the above embodiment, the company and employees are exemplified, but the present invention can also be applied to government offices and public servants, schools and teachers, groups and group members, and the like.

Claims (8)

An input means for inputting a user's operation history in the terminal device;
A work loss time determination means for extracting a work time not related to the work imposed on the user from the operation history input by the input means, and determining the extracted work time as a work loss time;
The time when the terminal device is no longer operated is acquired from the operation history input by the input unit, the time is determined as the final operation time, and the time from the predetermined time to the final operation time is determined as the working time. Working time determination means;
Analyzing means for analyzing the amount of work of the user based on the work loss time and the working time;
An information analysis apparatus comprising: output means for outputting an analysis result by the analysis means. The working time determining means includes
Overtime determination means for determining the time from a predetermined overtime start time to the final operation time as overtime hours,
The information analysis apparatus according to claim 1, wherein the analysis unit analyzes the work amount of the user based on the work loss time and the overtime of the work hours. The analysis means includes
The user is classified according to the business loss time and the working time as at least one of an employee with an appropriate amount of work, an employee with a large amount of work, an employee with a small amount of work, and an inefficient employee. The information analysis apparatus according to claim 1, further comprising: a classifying unit that classifies the plurality of classifications into a plurality of classifications. 4. The information analysis according to claim 1, further comprising: a business loss amount calculation unit that calculates a business loss amount by multiplying the business loss time by a coefficient related to personnel expenses. apparatus.   5. The information analysis apparatus according to claim 1, wherein the output unit graphically outputs the analysis result using the work loss time and the working time as coordinate axes. 6. An input step in which the input means inputs a user's operation history in the terminal device;
A business loss time determination unit that extracts a work time not related to the business imposed on the user from the operation history input in the input step, and determines the extracted work time as a business loss time; ,
The overtime determination unit obtains a time when the terminal device is no longer operated from the operation history input by the input unit, determines the time as a final operation time, and a time from a predetermined time to the final operation time Working time determination process for determining as working hours,
An analysis step in which the analysis means analyzes the amount of work of the user based on the work loss time and the work time;
An information analysis method, characterized in that the output means includes an output step of outputting the analysis result by the analysis means. A program, on a computer,
An input step for inputting a user's operation history in the terminal device;
A work loss time determination step of extracting a work time not related to the work imposed on the user from the operation history input by the input step, and determining the extracted work time as a work loss time;
The time when the terminal device is no longer operated is acquired from the operation history input in the input step, the time is determined as the final operation time, and the time from the predetermined time to the final operation time is determined as the working time. Working hours determination process;
An analysis step of analyzing the amount of work of the user based on the work loss time and the work hours;
A program for executing an output process for outputting an analysis result obtained in the analysis process. An information analysis system comprising an operation history management server that holds a user operation history in a terminal device, and an information analysis device that analyzes the operation history,
The information analyzer is
Input means for inputting a user's operation history in the terminal device held by the operation history management server via a communication medium or a portable recording medium;
A work loss time determination means for extracting a work time not related to the work imposed on the user from the operation history input by the input means, and determining the extracted work time as a work loss time;
The time when the terminal device is no longer operated is acquired from the operation history input by the input unit, the time is determined as the final operation time, and the time from the predetermined time to the final operation time is determined as the working time. Working time determination means;
Analyzing means for analyzing the amount of work of the user based on the work loss time and the working time;
An information analysis system comprising: output means for outputting an analysis result by the analysis means.