JP2020004138A - Labor management system - Google Patents

Abstract

To provide a labor management system which can calculate substantial time when an employee worked for a business without his self-assessment and can grasp precise labor time.SOLUTION: In a labor management system, a labor management server has a use history acquiring unit for acquiring a use history including date and time when a worker utilizes a business system, and a labor time estimating unit for identifying, among the acquired use history, use relating to the business based on the set rule and for estimating labor time for the business based on the identified use history.SELECTED DRAWING: Figure 5

Description

  The present invention relates to a labor management system.

  The working hours of workers are automatically grasped. For example, Patent Literature 1 describes that work time is managed by logging in and logging off of a terminal.

JP 2003-323533 A

  However, there are some people who often go out and forget their overtime report. However, only obtaining the working hours from the login and logoff of the terminal as in Patent Document 1 requires the actual time involved in the work. As a result, they had to rely on self-assessment from their employees, making it difficult to grasp accurate working hours.

  The present invention has been made in view of such a background, and an object of the present invention is to provide a technique capable of accurately estimating the working hours of an employee.

  A main invention of the present invention for solving the above-mentioned problem is a labor management system for managing the working hours of an employee, and a use history acquisition for acquiring a use history including a date and time relating to the use of the business system by the employee. And a working time estimating unit that specifies, according to a set rule, one of the obtained usage histories that corresponds to the task, and estimates the working time of the task based on the specified usage history. Shall be provided.

  Other problems disclosed by the present application and methods of solving the problems will be clarified by the description of the embodiments of the invention and the drawings.

  According to the present invention, the working hours of an employee can be accurately estimated.

It is a figure explaining the whole composition of the labor management system of this embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a user terminal. FIG. 3 is a diagram illustrating an example of a software configuration of a user terminal 10. FIG. 3 is a diagram illustrating an example of a hardware configuration of a labor management server 20. FIG. 3 is a diagram illustrating an example of a software configuration of a labor management server 20. FIG. 6 is a diagram illustrating an example of rule information registered in a rule storage unit 251. 5 is a diagram illustrating a configuration example of business information registered in a business history storage unit 252. FIG. FIG. 9 is a diagram illustrating a configuration example of labor information registered in a working time storage unit 253. FIG. 7 is a diagram showing a flow of processing performed by the labor management server 20 for estimating working hours. It is a figure which shows the flow of the process which calculates overtime. It is a figure explaining an estimation process of working hours. It is a figure explaining the flow of correction processing of labor information. It is a figure showing the 1st modification of this embodiment. It is a figure showing the flow of the evaluation processing of the risk concerning the 1st modification. It is a figure showing the 2nd modification of this embodiment. It is a screen display example by this Embodiment. The work rules on the aggregation condition customization screen are shown. 13 is another screen display example according to the present embodiment. This is a display for each department in each year on the overtime hours upper limit risk display screen. 13 is another screen display example according to the present embodiment. Shows the status of individual units on the working hours estimation / report comparison screen. 13 is another screen display example according to the present embodiment corresponding to FIG. 11. 13 shows a working time correction screen. 13 is another screen display example according to the present embodiment. This is an exclusion setting on the aggregation condition customization screen. 13 is another screen display example according to the present embodiment. This section shows the status of each department on a monthly basis on the work hour estimation / report comparison screen.

  The contents of the embodiment of the present invention will be listed and described. The labor management system according to the embodiment of the present invention has the following configuration.

[Item 1]
A labor management system that manages the working hours of employees,
A use history acquisition unit that acquires a use history including a date and time related to use of the business system by the employee,
According to a set rule, a working time estimating unit that specifies a job corresponding to the job among the acquired usage histories and estimates the working hours of performing the job based on the specified usage history.
A labor management system comprising:
[Item 2]
The labor management system according to item 1, wherein
The business system includes a calendar system, the usage history according to the calendar system includes the employee's schedule managed by the calendar system,
The working time estimating unit estimates whether or not the schedule corresponds to the job, depending on whether or not a predetermined keyword is included in the schedule.
Labor management system characterized by the following.
[Item 3]
The labor management system according to item 1 or 2,
The business system includes an e-mail system, and the usage history according to the e-mail system includes transmission and reception of an e-mail,
The working time estimation unit determines whether or not the transmission and reception of the email corresponds to the job, depending on whether or not a predetermined keyword is included in the content of the email that has been subjected to the transmission and reception. Estimating,
Labor management system characterized by the following.
[Item 4]
The labor management system according to any one of items 1 to 3,
The business system includes a file management system, and the use history according to the file management system includes an operation related to at least one of a file and a directory managed by the file management system.
The working time estimating unit includes a predetermined keyword in at least one of the name of the file and the directory subjected to the operation, and at least one of the contents of the file subject to the operation. Estimating whether or not the operation on the file or the directory corresponds to the task according to whether or not the operation has been performed.
[Item 5]
The labor management system according to any one of items 1 to 4,
The rule is a rule for determining whether the use of the business system corresponds to the business,
A rule storage unit that stores the rule,
A rule setting unit that receives input of the rule and registers the received rule in the rule storage unit;
A labor management system, further comprising:
[Item 6]
The labor management system according to item 1, wherein
A neural network having the use history as an input signal and an output signal indicating whether the use history corresponds to a business;
A learning processing unit that receives input of information indicating whether or not the use history corresponds to a task, and causes the neural network to learn the input information as a teacher signal;
Further comprising
The working time estimating unit is to give the obtained use history to the neural network, and to estimate whether the use history corresponds to work,
Labor management system characterized by the following.
[Item 7] (Risk judgment by matching with attendance management)
The labor management system according to item 1, wherein
Acquiring a declared time, which is the working time declared by the employee, further comprising a risk evaluation unit that outputs a difference between the working time estimated by the working time estimation unit and the declared time as a risk,
Labor management system characterized by the following.
[Item 8] (PC log, entry / exit log)
The labor management system according to item 1, wherein
The working time estimating unit acquires at least one of a work log related to work performed on a personal computer used by the employee and an entry / exit log related to entering / leaving a work space, and the acquired work log And at least one of the operation using the personal computer and the entry / exit to / from the work space is performed in accordance with whether or not a preset keyword is included in at least one of the entry / exit logs. Estimating whether or not
Labor management system characterized by the following.

== Overall configuration ==
Hereinafter, a labor management system according to an embodiment of the present invention will be described. In the present embodiment, it is assumed that the user is an employee employed by a user of a company or the like (hereinafter simply referred to as a company), and the labor management system of the present embodiment is used by the user. The working hours of the user are automatically estimated based on the usage history of various business systems.

  FIG. 1 is a diagram illustrating the overall configuration of the labor management system according to the present embodiment. The labor management system according to the present embodiment includes a labor management server 20, and the labor management server 20 is communicably connected to a mail server 32, a calendar server 33, and a file management server 34 via a communication network 31. . The mail server 32, the calendar server 33, and the file management server 34 are communicably connected to the user terminal 10 via the communication network 31. In the present embodiment, the communication network 31 is assumed to be the Internet. However, the communication network 31 may be a LAN (Local Area Network). The communication network 31 is constructed by, for example, a telephone line network, Ethernet (registered trademark), a wireless communication network, or the like.

  The user terminal 10 is a computer operated by a user. The user terminal 10 is, for example, a personal computer, a tablet computer, a smartphone, or the like. The user performs a task by operating a task system (software) related to the task to be engaged. In the present embodiment, it is assumed that the business system is executed in a so-called cloud. The user operates the user terminal 10 to connect to the cloud, and uses the business system.

  In the present embodiment, as a business system executed in the cloud, an e-mail service for sending and receiving e-mail, a calendar service for managing a user's schedule, and a file management service for managing various files related to the user's business are assumed. I do. Each of the mail server 32, the calendar server 33, and the file management server 34 is a virtual computer which is realized by one or more computers and operates as a so-called cloud, and provides these business systems.

  The mail server 32 is a virtual computer that operates as a so-called cloud realized by one or a plurality of computers that provide an electronic mail service. The email service provides various functions including sending and receiving, editing, and deleting email. The mail server 32 functions as an MTA (Mail Transfer Agent) that sends and receives e-mails, and as an MRA (Mail Retrieval Agent) that stores e-mails and provides them to the user terminal 10. The user terminal 10 transmits a request (hereinafter, referred to as a mail request) in accordance with SMTP (Simple Mail Transfer Protocol), IMAP (Internet Message Access Protocol), and POP (Post Office Protocol) to the mail server 32, thereby transmitting the electronic mail. It is possible to send, receive, edit, and delete mail.

  The calendar server 33 is a virtual computer that operates as a so-called cloud realized by one or more computers that provide a calendar service. The calendar service provides various functions including creation, acquisition, editing, and deletion of information (hereinafter, referred to as schedule information) including the date and time, title, and content related to the user's actions such as the user's schedule and conference room reservation. The calendar server 33 provides an HTML (HyperText Markup Language) calendar screen and an API (Application Programming Interface) for creating, acquiring, editing, and deleting schedule information. The user terminal 10 can create, obtain, edit, and delete schedule information by transmitting an API request (hereinafter, referred to as a calendar request) to the calendar server 33.

  The file management server 34 is a virtual computer that operates as a so-called cloud realized by one or more computers that provide a file management service. The file management service provides various functions including creation, acquisition, editing, and deletion of files. The file management server 34 provides an API for creating, acquiring, editing, and deleting a file. The user terminal 10 transmits an API request (hereinafter, referred to as a file request) to the file management server 34. , And can perform file operations.

  The labor management server 20 is a computer operated by a labor administrator of the company. The labor management server 20 is, for example, a personal computer or a workstation. The labor management server 20, like the mail server 32, the calendar server 33, and the file management server 34, may operate as a virtual computer in the cloud.

== User terminal 10 ==
FIG. 2 is a diagram illustrating an example of a hardware configuration of the user terminal 10. The user terminal 10 includes a CPU 101, a memory 102, a storage device 103, a communication interface 104, an input device 105, and an output device 106. The storage device 103 stores various data and programs, such as a hard disk drive, a solid state drive, and a flash memory. The communication interface 104 is an interface for connecting to the communication network 30. For example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone line network, and a wireless communication device for performing wireless communication , A USB (Universal Serial Bus) connector for serial communication and an RS232C connector. The input device 105 is a device for inputting data, for example, a keyboard, a mouse, a touch panel, a button, a microphone, and the like. The output device 106 outputs data, such as a display, a printer, and a speaker.

  FIG. 3 is a diagram illustrating an example of a software configuration of the user terminal 10. The user terminal 10 includes a work processing unit 111, a working time display unit 112, and a working time correction unit 113. The work processing unit 111, the working time display unit 112, and the working time correction unit 113 are realized by the CPU 101 of the user terminal 10 reading out a program stored in the storage device 103 into the memory 102 and executing the program.

  The business processing unit 111 accesses the mail server 32, the calendar server 33, and the file management server 34 to perform various business processes. The business processing unit 111 uses an e-mail service by sending a mail request to the mail server 32, uses a calendar service by sending a calendar request to the calendar server 33, and sends a file request to the file management server 34. By doing so, the file management service can be used.

  The working hour display unit 112 presents the estimated working hours to the user. The working time display unit 112 transmits a request (hereinafter, referred to as an acquisition request) to the labor management server 30, and information (hereinafter, referred to as labor information) relating to the working time managed by the labor management server 30, which will be described later. get. As will be described later, from the labor management server 30, the usage history of the business system together with the labor information (hereinafter, the usage history managed by the labor management server 30 is referred to as the business history, Is referred to as business information.). In the task information transmitted from the labor management server 30, information indicating whether the use corresponds to a task (an exclusion flag indicating whether the task does not correspond to a task in the present embodiment) is set. The working hour display unit 112 displays the working hours estimated by the labor management server 30.

  The working time correction unit 113 corrects labor information and usage history. The working time correction unit 113 receives corrections of working hours and overtime hours from the user. For example, the working time correction unit 113 can receive, for each piece of usage information included in the usage history, an input for private use, and set the exclusion flag of the received usage information to “true”. Further, the working time correction unit 113 may receive information indicating that the use information estimated to be private use is the use of the business system by business, and set the exclusion flag to “false” for the use information. it can. The working time correction unit 113 transmits a request including the corrected labor information and the usage information (hereinafter, referred to as a correction request) to the labor management server 30, and transmits the labor information and the usage information managed by the labor management server 30. Update.

== Labor Management Server 20 ==
FIG. 4 is a diagram illustrating an example of a hardware configuration of the labor management server 20. The labor management server 20 has the same configuration as the user terminal 10, and includes a CPU 101, a memory 102, a storage device 103, a communication interface 104, an input device 105, and an output device 106. The storage device 103 stores various data and programs, such as a hard disk drive, a solid state drive, and a flash memory. The communication interface 104 is an interface for connecting to the communication network 30. For example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone line network, and a wireless communication device for performing wireless communication , A USB (Universal Serial Bus) connector for serial communication and an RS232C connector. The input device 105 is a device for inputting data, for example, a keyboard, a mouse, a touch panel, a button, a microphone, and the like. The output device 106 outputs data, such as a display, a printer, and a speaker.

  FIG. 5 is a diagram illustrating an example of a software configuration of the labor management server 20. The labor management server 30 includes a rule setting unit 211, a usage history acquisition unit 212, a working time estimation unit 213, a working time correction unit 214, a rule storage unit 251, a work history storage unit 252, and a working time storage unit 253. Note that the rule setting unit 211, the usage history acquisition unit 212, the working time estimation unit 213, and the working time correction unit 214 allow the CPU 101 included in the labor management server 30 to read the program stored in the storage device 103 into the memory 102 and execute the program. The rule storage unit 251, the work history storage unit 252, and the working time storage unit 253 are realized as a part of a storage area provided by the memory 102 and the storage device 103 included in the labor management server 20.

  The rule storage unit 251 stores information (hereinafter, referred to as rule information) in which a rule for determining whether or not the use of the business system by the user is due to the business is set. In the present embodiment, the rule information registered in the rule storage unit 251 sets a rule for estimating that the use of the business system is not based on business (private use). Further, in the present embodiment, it is assumed that a rule is set for information (hereinafter referred to as usage information) relating to each use included in the usage history of the business system by the user. FIG. 6 is a diagram illustrating an example of rule information registered in the rule storage unit 251.

  As described above, in the present embodiment, the business system includes an e-mail service, a calendar service, and a file management service. The usage information relating to the e-mail service is represented by an e-mail transmitted from the user to the outside. It is assumed that the usage information related to the calendar service is represented by schedule information stored in the calendar server 33. It is assumed that the usage information related to the file management service is represented by meta information (including a path and an update date and time) of a file created, obtained, edited, or deleted by the user.

  The rule information stored in the rule storage unit 251 includes a company ID for identifying a company, a service type, a target item, and a pattern. In the rule storage unit 251, rule information is stored for each company. In the present embodiment, the service type is one of “mail” indicating an electronic mail service, “calendar” indicating a calendar service, and “file” indicating a file management service. In the case of an e-mail service, the target item is information indicating each part constituting the e-mail, and for example, a "title" is set. In the case of the calendar service, the target item is information indicating each item included in the schedule information, such as “title”, “place”, “content”, and “participant”. In the case of the file management service, the target items are various types of information about the file, such as “file name”, “directory name”, “path”, and “extension”. The pattern is information for pattern matching. In the present embodiment, for simplicity of description, the pattern is a character string for partially matching the target item.

  In the example of FIG. 6, when the title of the e-mail includes the character string "# private use", rule information for estimating that the e-mail is a private use mail (not due to business) is registered. Have been. If the title of the schedule information includes the character string "(Private use)", the rule information for estimating that the schedule related to the schedule information is private use (not due to business) is not included. It is registered. Furthermore, if the file path includes a character string “private”, rule information for presuming that various operations on the file are for private use (not for business) is registered. I have.

  The rule setting unit 211 receives input of rule information from the operator, and registers the received rule in the rule storage unit 251. The setting of the rule information can be set, for example, by a user of the management department of the company. Thereby, different rules can be set for each company. For example, a user in the management department of a company can set a keyword representing private use (for example, “pr” instead of “private use”) according to the rules of the company.

  In this way, the rule setting unit 211 can determine a company's own pattern with reference to a pattern set by another company, even if the user is not used to setting rules. For example, for each keyword registered by another company, the rule setting unit 211 counts the number of times included in the title of the schedule information of the other company, and can propose a keyword whose frequency is equal to or more than a predetermined number. . For example, when other companies register “drinking party”, “reception party”, and “study session” as keywords, the rule setting unit 211 sets the title of the schedule information of the company to “drinking party”, “reception party”, “reception party”, If the number of “study sessions” is equal to or more than a predetermined number, these can be proposed as keywords.

  The use history acquisition unit 212 acquires the use history of the business system by the user. In the present embodiment, the usage history acquisition unit 212 acquires, from the mail server 32, the e-mail transmitted and received during the tallying period (for example, one month), and from the calendar server 33, the schedule including the date and time during the tallying period. The information is acquired, and the meta information of the file created, browsed, edited, or deleted during the counting period is acquired from the file management server 34. These pieces of information can be obtained by using an API.

  The working time estimation unit 213 estimates working hours based on the usage history acquired by the usage history acquisition unit 212. The details of the working time estimation process will be described later. First, the working time estimation unit 213 determines whether each piece of usage information included in the usage history is based on work according to the rules registered in the rule storage unit 251. It is determined whether or not it is not, and the business information including the determination result and ID information for specifying the usage information is created and registered in the business history storage unit 252.

  FIG. 7 is a diagram illustrating a configuration example of the task information registered in the task history storage unit 252. As shown in the figure, the business information includes a user ID, a start date and time, an end date and time, a service type, ID information, and an exclusion flag. The user ID is information for identifying a user. The start date and time is the date and time relating to the usage information. The end date and time is the end date and time of the period when the usage information includes the period, and is the same as the start date and time when the usage information does not include the period. For example, when the usage information is the transmitted e-mail, the period is not included, and the transmitted date and time are set as the start date and time and the end date and time. On the other hand, when the usage information is schedule information and the start date and time and the end date and time of the schedule are set, these are set as the start date and time and the end date and time of the business information. The service type is information for specifying a business system. In the present embodiment, the service type is any one of “mail” indicating an e-mail service, “calendar” indicating a calendar service, and “file” indicating a file management service. And The ID information is information for specifying the entity related to the use information in the business system, and specifies the e-mail in the e-mail service, specifies the schedule information in the calendar service, and specifies the file in the file management service. The exclusion flag is a value indicating that the use of the business system according to the usage information is not considered to be a business.

  The working time estimation unit 213 estimates working hours based on the work information, and registers the estimated working hours in the work history storage unit 252.

  The working time storage unit 253 stores labor information. FIG. 8 is a diagram showing a configuration example of labor information registered in the working time storage unit 253. The labor information includes a user ID, a date, an estimated working time, an estimated overtime, a declared working time, and a declared overtime. The user ID is information for specifying the user, similarly to the business information, and the date is the date on which the working hours are counted. The labor information is associated with the user ID and the date, and estimates the working hours and overtime hours of the user on the date, the working hours on the date reported by the user (reported working hours), and Overtime hours (reported overtime hours) are set.

  The working time correction unit 214 corrects labor information. In response to the acquisition request from the user terminal 10, the working time correction unit 214 reads the business information and the labor information corresponding to the user ID indicating the user terminal 10 from the business history storage unit 252 and the working time storage unit 253, and Send to 10. Further, the working time correction unit 214 receives the correction request transmitted from the user terminal 10, and stores the corrected business information and labor information included in the received correction request in the business history storage unit 252 and the working time storage unit 253. Register with.

== Processing ==
Hereinafter, processing executed in the labor management system of the present embodiment will be described. FIG. 9 is a diagram illustrating a flow of processing performed by the labor management server 20 for estimating working hours. The processing shown in FIG. 9 may be executed, for example, at the start of use of the system, when the setting of a deletion flag, a keyword, or the like is changed, or may be executed at predetermined time intervals (for example, every day). Good.

  The use history acquisition unit 212 receives designation of a period for estimating working hours from the operator (S401), and acquires a use history corresponding to the designated period from the business system (S402). Note that the period may be automatically set. For example, when labor management starts first, the past year is automatically set; when the setting of exclusion flags and keywords are changed, the entire period related to the usage history acquired in the past is automatically set to 1 day. can do.

  The usage history acquisition unit 212 downloads, for example, an e-mail transmitted within a specified period from the outbox of the mail server 32, and sends, from the calendar server 33, schedule information in which a date within the specified period is set. It is possible to download, from the file management server 34, the meta information relating to the file that has been downloaded and created, changed or deleted within the designated period.

  The working time estimation unit 213 performs the following processing for each piece of usage information included in the usage history acquired by the usage history acquisition unit 212.

  The working time estimating unit 213 applies the rule registered in the rule storage unit 251 to the use information, and the use of the business system related to the use information has been performed other than in business (for private use). It is estimated whether or not this is the case, and the estimation result is set as an exclusion flag of the business information (S403). In the present embodiment, the working time estimation unit 213 reads out the rule information corresponding to the service for which the usage history has been acquired from the rule storage unit 251, and for each of the read out rule information, the pattern included in the rule information indicates that the target item is It is estimated whether or not the usage information is for private use, based on whether or not the usage information is included in the item of usage information shown.

  The working time estimating unit 213 sets the date and time relating to the usage information as the start date and time of the business information (S404), and if the end date and time is set in the usage information (S405: YES), in this embodiment, the schedule information indicates the end date and time. Is set as the end date and time of the business information (S406), and if the end date and time are not set in the use information (S405: NO), the present embodiment If the usage information is an e-mail transmission history, if the usage information is file meta information, or if the usage information is schedule information and the schedule information does not have an end date and time, The date and time is set as the end date and time of the business information (S407). The working time estimating unit 213 includes a user ID indicating a user, a start date and time of the business information, an end date and time of the business information, a service type indicating a business system related to usage information, and an ID for specifying usage information on the business system. The information and the business information in which the exclusion flag of the business information is set are registered in the business history storage unit 252 (S408).

  The working time estimation unit 213 performs the following processing for each date included in the target period after performing the above processing for each of the use information.

  The working time estimating unit 213 determines the time from the earliest time in the start date and time to the latest time in the end date and time for the business information corresponding to the date and for which the exclusion flag is false. It is calculated as working hours (S409). The working time estimation unit 213 performs a process of calculating overtime hours (S410).

  FIG. 10 is a diagram illustrating a flow of a process of calculating overtime hours. The working time estimation unit 213 initializes the overtime hours to 0 (S421), and if the earliest time among the start times of the business information corresponding to the date is earlier than the start time (S422: YES), the relevant time Is added to the overtime hours (S423). If the latest time of the end date and time of the business information corresponding to the date is later than the closing time (S424: YES), the working time estimating unit 213 determines the time from the closing time to the latest time as overtime. (S425).

  Returning to FIG. 10, the working time estimation unit 213 subtracts a predetermined rest time from the working time (S 411), and registers labor information including the date and the calculated working time and overtime hours in the working time storage unit 253. (S412).

  FIG. 11 is a diagram illustrating a process of estimating working hours. The upper part of FIG. 11 shows the actual status of the work and the breaks that the user was involved in. In the example of FIG. 11, the user started work at 09:45, sent and received e-mails, participated in a meeting at 10:45, took a break at 12:10, and created materials at 13:15. It is shown.

  Here, an e-mail is transmitted at 09:47, 10:03, and 10:25 as usage information (321), and a meeting (331) of “business regular” is scheduled from 10:45 to 12:00 as schedule information. It is registered. At 12:05, the file is operated (333) in the file management server 34, an e-mail is transmitted again at 13:16 (321), and the file management is performed at 13:17, 13:20, and 14:35. The file operation (333) is performed in the server 34. In this way, by arranging the usage histories of the business system in chronological order, it is possible to easily grasp at what timing the user was engaged in the business.

  Here, in the conventional labor management, when the user declares that "the business started from 10:00", the user relies on the declaration and sets the work start time to 10:00. In the form of the labor management system, it is possible to detect that there is an e-mail that was transmitted as a business at 09:47 before 10:00, and estimate 09:47 as the work start time.

  As described above, the labor management server 20 can estimate the working hours, which are the hours involved in the business, based on the usage history of the business system. In the labor management system of the present embodiment, since the use information of the business system corresponding to the private use can be specified based on the rules and the private use information can be excluded, the business system is efficiently used as the work. , And it is possible to automatically estimate the working hours based on the usage history irrespective of the report from the user.

  FIG. 12 is a diagram illustrating the flow of the labor information correction process. In the user terminal 10, the working time correction unit 113 transmits to the labor management server 20 an acquisition request specifying a user ID indicating a user using the user terminal 10 and a target period for which the working time is to be corrected. (S441). Note that the target period may be input from the user or a period such as the previous day or the previous month may be automatically specified.

  In the labor management server 20, the working time correction unit 214 receives the acquisition request transmitted from the user terminal 10 (S442), and the business information and labor information corresponding to the user ID and the target period set in the received acquisition request. Is read from the work history storage unit 252 and the working time storage unit 253 (S443), and the read work information and labor information are transmitted to the user terminal 10 (S444).

  The working time correction unit 113 of the user terminal 10 displays the business information and the labor information responded from the labor management server 20 to make the user confirm (S445), and excludes the business information exclusion flag and the working hours and the overtime hours of the labor information. Is received (S446), and a correction request in which business information and labor information reflecting the received correction are set is transmitted to the labor management server 20 (S447).

  In the labor management server 20, when the working time correction unit 214 receives the correction request (S448), the business information set in the correction request is registered in the business history storage unit 252 and the business information is updated (S449). Further, the working time correction unit 214 sets true in the edited field of the labor information set in the correction request, and then registers it in the working time storage unit 253 to update the labor information (S450).

  As described above, the working hours estimated by the labor management server 20 can be corrected on the user side.

== Modification 1 ==
FIG. 13 and FIG. 14 are views showing a first modification of the present embodiment. In the first modified example, it is assumed that the user has registered the working hours by self-declaration with respect to the other labor management devices 21, and the labor management server 20 has registered the working hours managed by the other labor management devices 21. A risk evaluation unit 215 for evaluating the risk is provided. In this modification, the risk evaluation unit 215 evaluates, as a risk, the risk of unpaid overtime due to a state in which the user does not declare working hours despite performing business.

  FIG. 14 is a diagram illustrating a flow of a risk evaluation process according to the first modification. First, the operator extracts data including the working hours (or overtime hours) of the user from another labor management device 21 in a format such as CSV (Comma-Separated Value), and extracts the data including the extracted working hours (or overtime hours). The risk is transmitted to the labor management server 20 by uploading or the like, and in the labor management server 20, the risk evaluation unit 215 receives data including working hours (or overtime hours) for each user (S501).

  The risk evaluation unit 215 reads, for each user, the working hours (or overtime hours) corresponding to the user from the working hours storage unit 253 (S502), and includes the read working hours (or overtime hours) in the received data. By subtracting the working hours (or overtime hours) related to the user, the risk (risk of unpaid overtime) of the user is calculated (S503).

  The risk evaluation unit 215 sums the risks calculated for each user (S504), and outputs the risk for each user and the total risk (S505).

  As described above, according to the first modified example, the risk of unpaid overtime due to intentional or unconscious omission of the report on the working hours managed by self-reporting by the other labor management device 21 is evaluated as a risk. can do.

== Modification 2 ==
FIG. 14 is a diagram showing a second modification of the present embodiment. In the second modification shown in FIG. 14, the labor management server 20 includes a learning processing unit 216 and a neural network 217, and automatically generates rule information. The learning processing unit 216 causes the neural network 217 to perform learning using the use information in the business system indicated by the ID information of the business information corresponding to the labor information as an input signal and using the exclusion flag of the business information as a teacher signal. Then, in addition to the estimation based on the rule, the working time estimating unit 213 can estimate whether the usage information is for private use by inputting the usage information acquired from the business system to the neural network 217. . In this case, the rule storage unit 251 may be omitted without performing the estimation based on the rule. Note that, also in the second modified example, the labor management server 20 may include the risk evaluation unit 215 illustrated in FIG. 13 as in the first modified example.

  Although the present embodiment has been described above, the above-described embodiment is intended to facilitate understanding of the present invention, and is not intended to limit and interpret the present invention. The present invention can be modified and improved without departing from the gist of the present invention, and the present invention also includes equivalents thereof.

  For example, in the present embodiment, the business system is of three types: the mail server 32, the calendar server 33, and the file management server 34. However, the present invention is not limited to this. The working hours may be obtained and estimated. For example, it receives or manages input of log information related to PC start / stop by each employee, log information related to entering / leaving a work space, etc., collected by a person in charge of a company information system. It can be obtained from the server and used as a usage history for estimating working hours.

  Further, in the present embodiment, the usage history acquired from the mail server 32 is the transmission history of the e-mail. However, the present invention is not limited to this, and the history of browsing the received e-mail may be obtained. Further, in the present embodiment, the pattern of the rule information is applied only to the title of the e-mail. However, the present invention is not limited to this, and the pattern may be applied to other items of the e-mail. . For example, a transmission source, a transmission destination, a transmission time, a transmission count, a transmission frequency, a broadcast transmitter, a specific keyword in the text, and the like are exemplified, but the present invention is not limited thereto.

  In the present embodiment, the use history acquired from the calendar server 33 is the schedule information registered in the calendar server 33. However, the present invention is not limited to this. The operation may be acquired as a usage history.

  Further, in the present embodiment, the use history acquired from the file management server 34 is the meta information of the created file. However, the present invention is not limited to this, and the content of the file may be acquired.

  In the present embodiment, the rule for one piece of information included in the usage history of one business system is registered in the rule storage unit 251 provided in the labor management server 20, but one or a plurality of rules are registered. A plurality of continuous use patterns when the use histories of the business system are arranged in chronological order may be set.

  In the present embodiment, a partial match is assumed for the rule of estimation. However, a regular expression may be set for the rule pattern stored in the rule storage unit 251.

  Further, in the present embodiment, a rule for detecting non-business (for private use) is set in the rule information. However, the present invention is not limited to this, and a rule for detecting business can be set. May be set. For example, when “work”, “in” (in-house work), “ex” (out-of-office work), and the like are set in the pattern of the rule information, the working time estimation unit 213 determines that these patterns are included in the title of the e-mail. When it is included, it can be estimated that the transmission of the e-mail is related to the job and that the job is being performed. Further, the rule information may include not only a pattern but also a work start time, a work end time, a length of a break, and the like.

  In the present embodiment, the rule information is registered for each company. However, the present invention is not limited to this, and the rule information may be registered for each department, each individual, or the like.

  In the present embodiment, the start time and the end time are set in advance. However, the present invention is not limited to this. For example, the start time and the end time may be managed for each user. In this case, the labor management server 20 includes a working time storage unit that stores the starting time and the ending time for each user ID indicating a user. The working time storage unit may store a different starting time and ending time for each day.

  Further, the start time may not be set, and a portion where the total working hours of a day exceeds a predetermined constraint time (for example, 7 hours or 8 hours) may be calculated as overtime hours.

DESCRIPTION OF SYMBOLS 10 User terminal 20 Labor management server 31 Communication network 32 Mail server 33 Calendar server 34 File management server 111 Business processing section 112 Working time display section 113 Working time correction section 211 Rule setting section 212 Usage history acquisition section 213 Working time estimation section 214 Labor Time correction unit 215 Risk evaluation unit 216 Learning processing unit 217 Neural network 251 Rule storage unit 252 Work history storage unit 253 Working time storage unit

Claims (8)

A labor management system that manages the working hours of employees,
A use history acquisition unit that acquires a use history including a date and time related to use of the business system by the employee,
According to a set rule, a working time estimating unit that specifies a job corresponding to the job among the acquired usage histories and estimates the working hours of performing the job based on the specified usage history.
A labor management system comprising: The labor management system according to claim 1, wherein
The business system includes a calendar system, the usage history according to the calendar system includes the employee's schedule managed by the calendar system,
The working time estimating unit estimates whether or not the schedule corresponds to the job, depending on whether or not a predetermined keyword is included in the schedule.
Labor management system characterized by the following. The labor management system according to claim 1 or 2,
The business system includes an e-mail system, and the usage history according to the e-mail system includes transmission and reception of an e-mail,
The working time estimation unit determines whether or not the transmission and reception of the email corresponds to the job, depending on whether or not a predetermined keyword is included in the content of the email that has been subjected to the transmission and reception. Estimating,
Labor management system characterized by the following. The labor management system according to any one of claims 1 to 3,
The business system includes a file management system, and the use history according to the file management system includes an operation related to at least one of a file and a directory managed by the file management system.
The working time estimating unit includes a predetermined keyword in at least one of the name of the file and the directory subjected to the operation, and at least one of the contents of the file subject to the operation. Estimating whether or not the operation on the file or the directory corresponds to the task according to whether or not the operation has been performed. The labor management system according to any one of claims 1 to 4,
The rule is a rule for determining whether the use of the business system corresponds to the business,
A rule storage unit that stores the rule,
A rule setting unit that receives input of the rule and registers the received rule in the rule storage unit;
A labor management system, further comprising: The labor management system according to claim 1, wherein
A neural network having the use history as an input signal and an output signal indicating whether the use history corresponds to a business;
A learning processing unit that receives input of information indicating whether or not the use history corresponds to a task, and causes the neural network to learn the input information as a teacher signal;
Further comprising
The working time estimating unit, giving the obtained use history to the neural network, to determine whether the use history corresponds to work,
Labor management system characterized by the following. The labor management system according to claim 1, wherein
Acquiring a declared time, which is the working time declared by the employee, further comprising a risk evaluation unit that outputs a difference between the working time estimated by the working time estimation unit and the declared time as a risk,
Labor management system characterized by the following. The labor management system according to claim 1, wherein
The working time estimating unit acquires at least one of a work log related to a work performed on a personal computer used by the employee and an entry / exit log related to entering / leaving a work space, and the acquired work log And at least one of the operation using the personal computer and the entry / exit to / from the work space is performed in accordance with whether or not a preset keyword is included in at least one of the entry / exit logs. Estimating whether or not
Labor management system characterized by the following.