History management system, history management method, and program

Abstract

This system provides a history management system and method that retrieves the history of web tools used by individual users and displays the status of the user's work. [Solution] In the history management system, the history management device includes a storage unit that stores the credentials of multiple web tools used by the user in association with user information, an acquisition unit that acquires event history information from the user's tools based on the credentials associated with the user information, and a display processing unit that displays the history based on the acquired event history information. The event history information is information relating to the history of events, including active events that occurred as a result of the user's work.

Description

Technical Field

[0001] The present invention relates to a history management system, a history management method, and a program.

Background Art

[0002] In recent years, workers often perform their work using software tools. In such cases, it has become difficult for users and the like who manage workers to grasp the working conditions and productivity of the workers. Therefore, technologies for grasping the working conditions of workers have been developed.

[0003] For example, Patent Document 1 discloses a labor management system that can collect log information from peripheral systems and the like to identify workers to be cared for and track them.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] [[ID=3⑧]] However, the invention described in Patent Document 1 does not disclose any specific method for acquiring event history information from a web tool and displaying the event history information.

[0006] Therefore, an object of the present invention is to provide a history management system that acquires the history of web tools used by individual users and shows the working conditions of the users.

Means for Solving the Problems

[0007] [1] A history management system, A storage unit that stores the credentials of multiple web tools used by the user, associated with user information, An acquisition unit that acquires event history information from the user's tools from multiple tools based on the credentials associated with the user information, Based on the acquired event history information, a display processing unit displays the history, Equipped with, The aforementioned event history information is information regarding the history of events, including active events that occurred as a result of the user's actions. History management system. [2] The event history information includes the event details and date and time information, The display processing unit displays two or more event display elements, which are screen display elements related to the event, in chronological order based on the event history information. The aforementioned event display element is a screen display element that shows the event details and the date and time the event occurred. [1] The history management system described above. [3] The display processing unit displays a first event display element indicating the occurrence of a first event and a second event display element indicating the occurrence of a second event in chronological order, and displays the time difference between the occurrence of the first event and the occurrence of the second event. [2] The history management system described above. [4] The history management system further includes a specific processing unit, When the specified processing unit receives a specified condition including the required time, it identifies the history of an event in which the time difference until the next event occurs matches the specified condition, based on the event history information including the date and time information. The display processing unit displays the event display elements based on the event history information that corresponds to the specific conditions. [2] The history management system described above. [5] The event history information includes access information to the event target display screen in the web tool, The event display element includes an access element to the event target display screen based on the access information, [2] The history management system described above. [6] The history management system includes a status identification unit, The aforementioned event history information includes event target identification information that identifies the target of the event and the event type, The status identification unit identifies the status of the event target based on the event target identification information and the event type, The aforementioned event display element displays the status, [2] The history management system described above. [7] The web tool includes a messaging tool, The status identification unit identifies the status of a conversation, including replied and unreplied, based on the event history information, which includes the event type, including received and sent, and the event target identification information. The history management system described in [6]. [8] The event history information includes information that includes a history of events that occurred as a result of the user working with the web tool, and includes date and time information and an event type for identifying at least passive and active events, The display processing unit displays the user's activity history based on the event history information relating to the active event identified based on the event type. A history management system as described in any of [1] to [7]. [9] The history management system further comprises an activity time identification unit and an identification processing unit, The activity time identification unit identifies the start time and end time of the activity for the day based on the event history information. The acquisition unit acquires the user's declared start time and declared end time of work. The specified processing unit receives work specification conditions including the allowable time, and identifies the work days of users where the difference between the activity start time and the declared start time of work and / or the difference between the declared end time of work and the end time of activity is equal to or greater than the allowable time. The display processing unit displays in a list the date on the working day of the user identified by the specific processing unit, the activity start time, and the activity end time. The history management system according to [8].

[10] The history management system further includes an index calculation unit. Based on the event history information regarding the active event, the index calculation unit calculates an activity index regarding the activity history of the user. The display processing unit displays the activity index. The history management system according to [8].

[11] The event history information includes date and time information. The activity index includes an activity amount indicating the total amount of the activity history of the user per unit time based on the event history information. The history management system according to

[10] .

[12] The event history information includes tool types. The display processing unit displays the activity amount for each tool type. The history management system according to

[11] .

[13] The event history information includes unique identification information for identifying related events. The activity index includes the time required from the occurrence of the first event until the occurrence of the second event related to the first event identified based on the identification information. The history management system according to

[10] .

[14] The user information includes department information. The index calculation unit calculates the activity index for each department. The display processing unit displays the activity index for each department. The history management system according to

[10] .

[15] The history management system further includes a specific processing unit. The specific processing unit receives specific conditions and identifies the event history information corresponding to the specific conditions based on the event history information. The index calculation unit calculates the activity index based on the event history information corresponding to the specific conditions specified by the specific processing unit. The history management system according to

[10] .

[16] A history management method executed by a computer, The storage unit of the computer stores the credentials of a plurality of web tools used by the user in association with the user information. An acquisition step of acquiring event history information from a plurality of tools based on the credentials associated with the user information; A display processing step of displaying a history based on the acquired event history information; Comprising: The event history information is information regarding a history of events including active events generated by the work of the user. History management method.

[17] A computer program that causes the computer to execute the history management method according to

[16] .

Effect of the Invention

[0008] According to the invention according to [1], it is possible to collect event history information using credentials for web tools and display the history.

[0009] According to the invention according to [2], it is possible to display the history of events in chronological order.

[0010] According to the invention according to [3], it is possible to check the time difference between the occurrences of events.

[0011] According to the invention according to [4], it is possible to specify and display a history corresponding to a specific condition that the time difference is equal to or longer than a required time set as a condition.

[0012] According to the invention according to [5], it is possible to easily transition from a screen displaying a history to a screen displaying an event target and display it.

[0013] The invention described in [6] makes it possible to identify and display the status of the target of an event.

[0014] The invention described in [7] makes it possible to specify and display the status of a messaging tool such as an email application, such as whether it has been replied to or not.

[0015] The invention described in [8] makes it possible to display a history of a user's activities using event history information related to active events that occur as a result of the user's actions, etc.

[0016] The invention described in [9] makes it possible to identify workdays that are likely to be problematic, such as when the difference between the activity time obtained from the tool and the work time applied for by the user is greater than or equal to an acceptable amount of time.

[0017] The invention described in

[10] makes it possible to calculate and display an indicator of user activity using event history information related to active events that occur as a result of user activity.

[0018] The invention described in

[11] makes it possible to display the status of a user's tool-based activity per unit of time.

[0019] The invention described in

[12] makes it possible to display the activity status for each type of tool.

[0020] The invention described in

[13] makes it possible to specify and display the time required from the occurrence of one event to the occurrence of the next event for a given event.

[0021] The invention described in

[14] makes it possible to display indicators of user activity for each department.

[0022] The invention described in

[15] makes it possible to calculate and display activity indicators using event history information that meets the conditions. [Brief explanation of the drawing]

[0023] [Figure 1] Block diagram showing the overall system configuration [Figure 2] System hardware configuration diagram [Figure 3] Data configuration diagram in one embodiment [Figure 4] Screen display example in one embodiment [Figure 5] Screen display example in one embodiment [Figure 6] Screen display example in one embodiment [Figure 7] Screen display example in one embodiment [Modes for carrying out the invention]

[0024] Further details will be provided below with reference to the attached drawings. The drawings show preferred embodiments. However, many different forms are possible and the embodiments are not limited to those described herein.

[0025] For example, this embodiment describes the configuration and operation of the history management system, but similar effects can be achieved by the method, device, computer program, etc. The program may be provided as a non-transient recording medium readable by a computer, or it may be provided so that it can be downloaded from an external server.

[0026] One embodiment of the present invention, a history management system, collects and displays event history information from tools used by workers during their work, particularly web tools such as web applications, making it easier to understand the status of workers. In this embodiment, the event history information is used for various purposes such as performance management and attendance management, as will be described later. Furthermore, the tool from which the history management system of the present invention acquires event history information is a web tool such as a web application used by the user for work, etc. In this embodiment, it is a messaging tool such as an email application or chat tool, cloud storage, a calendar application, etc., but it can be any tool that is used on the web and used for work.

[0027] In this embodiment, the history management system uses event history information related to events that occur in the tool, such as receiving and sending emails and chats, creating and editing files in cloud storage, and creating and editing appointments in a calendar application, to perform the processing described later. The event history information collected includes information on active events that occur due to user actions such as sending emails and editing files, and passive events that occur without user action, such as receiving emails and notifications of file editing by other users. When it is necessary to understand the user's work status and activities, such as identifying the user's activity time, the system uses event history information related to active events to perform processing. In this embodiment, one event history piece of information is acquired for each event. In this embodiment, multiple acquired event history pieces of information are used to perform the processing described later.

[0028] <System Configuration> Figure 1 is a block diagram showing the configuration of a system according to one embodiment. As shown in Figure 1, the history management system 0 comprises a history management device 1, a user terminal 2, and a tool provision system 3, which are connected to each other via a network 4 so as to be able to communicate.

[0029] One or more server devices, such as general-purpose servers or personal computers, can be used as the history management device 1.

[0030] As user terminal 2, a terminal device such as a personal computer, smartphone, or tablet can be used. User terminal 2 connects to history management device 1 by executing a history management device utilization program such as a browser application, and executes the processing described later. In this embodiment, the history management device utilization program is a browser application that is pre-installed or downloaded in advance to user terminal 2, but it may also be a client application downloaded from a program provider device (not shown).

[0031] The tool provisioning system 3 includes a tool provisioning device 31. One or more server devices, such as general-purpose servers or personal computers, can be used as the tool provisioning device 31. In this embodiment, the tool provisioning device 31 provides event history information related to events generated by the tool to the history management device 1. Although not shown in Figure 1, there are multiple tool provisioning systems 3. In this embodiment, the tool provisioning system 3 is a system that provides functions for web applications such as email applications, chat tools, cloud storage, and calendar applications. In this embodiment, the history management device 1 acquires event history information from the tool provisioning system 3 via the network 4.

[0032] Network 4 is an IP (Internet Protocol) network, but there are no restrictions on the type of communication protocol, network type, etc.

[0033] <Hardware Configuration> Figure 2 is a hardware configuration diagram of the history management device 1 and the user terminal 2.

[0034] Figure 2(a) is a hardware configuration diagram of the history management device 1. As shown in Figure 2(a), the history management device 1 comprises a processing unit 101, a storage unit 102, and a communication unit 103, which are used to ensure the operation of each unit and each process.

[0035] The processing unit 101 has a processor such as a CPU capable of executing instruction sets, and executes the OS, history management programs, etc. The memory unit 102 has volatile memory such as RAM that can store instruction sets, and non-volatile recording media such as HDDs or SSDs that can store the OS, history management programs, etc. The communication unit 103 has an interface for connecting to the network 4 and performs communication control with the network 4 to input and output information.

[0036] Figure 2(b) is a hardware configuration diagram of user terminal 2. As shown in Figure 2(b), user terminal 2 has a processing unit 201, a storage unit 202, a communication unit 203, an input unit 204, and an output unit 205, which are used to perform the functions of each unit and each process.

[0037] The processing unit 201 has a processor such as a CPU capable of executing instruction sets and executes programs such as the OS and history management device utilization programs. The memory unit 202 has a volatile memory such as RAM that can store instruction sets, and a non-volatile recording medium such as an HDD or SSD that can record application programs (such as history management device utilization programs) that can utilize multiple services including the OS and history management services. The communication unit 203 has an interface for connecting to network 4 and performs communication control with network 4 to input and output information. The input unit 204 has input devices such as touch panels and keyboards, which are operation input devices capable of input processing. The output unit 205 has an output device such as a display device capable of display processing, such as a display.

[0038] <Data Structure> In the following, Figure 3 will be used to illustrate an example of the data structure of various data stored in the memory unit 102 and used in the processing described later in the history management system 0. The memory unit 102 stores user information about the user, web tool credentials, and event history information obtained from multiple tool provision systems 3.

[0039] The user information shown in Figure 3(a) is information about a user in the history management system 0, and includes identification information (such as a user ID), a username, and departmental information regarding the department to which the user belongs. In addition, one or more credentials are associated with the user information using the identification information such as the user ID.

[0040] The credentials shown in Figure 3(b) are information for authenticating a user in the tool provision system 3, and include the tool type (tool name), user identification information such as a user ID, and a password. In this embodiment, the credentials include a password, but they do not include a password, or they may be in any format, such as an email address, as long as they are information that can authenticate the user. In this embodiment, if a user is using multiple web tools, multiple credentials of different tool types are linked to the user information. If a user has multiple accounts for a particular tool, multiple credentials for the same tool (of the same tool type) may be linked to a single user information. The history management system 0 acquires event history information of users of other tool provision systems 3 identified by the credentials, as information regarding the tool history of the user of the history management system whose user information is linked to the credentials used for acquisition.

[0041] The event history information shown in Figure 3(c) is information relating to the history of events in the tool, and includes date and time information, tool type, event type, event content, event target identification information, and access information. In this embodiment, the event history information is stored in association with the user information of the user associated with the credential information used at the time of acquisition.

[0042] The date and time information refers to information regarding the date and time an event occurred. In this embodiment, the date and time information also includes information regarding the year, month, day, time, and day of the week.

[0043] The tool type refers to the type of tool used to acquire event information, and in this embodiment, this includes email applications, chat tools, cloud storage, online meeting tools, etc. Note that email application A and email application B may be identified as different tool types.

[0044] The event type is the type of event, and in this embodiment, if the tool type is an email application, the event type is set to be appropriate for each tool type, such as receiving or sending emails, or if it is cloud storage, it is set to be file creation or file editing. In this embodiment, event history information where the event type is receiving emails is classified as event history information for passive events, and event history information where the event type is sending emails is classified as event history information for active events. In this embodiment, event history information is classified into event history information for active events and event history information for passive events based on the event type. In this embodiment, event types are classified into either active events or passive events, but there may be event types that fall into other classifications.

[0045] Event content information is information relating to the content of the event. In this embodiment, if the tool type is email, it indicates the subject of the email; if the tool type is cloud storage, it indicates the file name, etc., indicating the name of the target of the event. However, it may also be the body of the email, etc., as long as it is information relating to the content of the event.

[0046] Event target identification information is unique identification information for identifying the target of an event. In this embodiment, event target identification information is a unique URL (Uniform Resource Locator) for identifying a group of event history information related to events that occurred on the same target, such as events like the creation or editing of channels and threads in a chat tool, or the sending and receiving of emails displayed on a single screen as a thread in an email application. However, it can be in any format, such as the name of the event target, as long as it can identify the target of the event that occurred. The target of the event is the target on which the event occurred in the tool, and in this embodiment, this includes emails, threads, files, etc. Furthermore, in this embodiment, since event target identification information is a URL that allows transition to a screen for displaying the event target, it also functions as access information, as described later.

[0047] Access information is information that allows transitioning to an event target display screen that displays the target of an event in a web tool, and in this embodiment, it is a URL. The event target display screen is a screen for displaying the event target, and is, for example, an email display screen in an email application, a channel or thread display screen in a chat tool, or a file display screen in cloud storage.

[0048] In this embodiment, the history management system 0 uses processed event history information that has undergone preprocessing to be converted into a format easily handled within the system to perform the processing described later. However, it may also use raw data obtained from the tool provisioning system 3 to perform the processing described later.

[0049] <Functional Configuration of History Management System 0> Figure 1 further shows the functional configuration of the history management system 0. As shown in Figure 1, the history management device 1 comprises an acquisition unit 11, a specific processing unit 12, a status specification unit 13, an activity time specification unit 14, an indicator calculation unit 15, and a display processing unit 16. This is a system in which processing by software (a history management program temporarily or permanently stored in the storage unit 102) is concretely realized by hardware (processing unit 101, etc.). In addition, the user terminal 2 may have some of the functional configuration described later and execute some of the processing. In this case, the user terminal 2 stores some of the history management program in the storage unit 202 and executes some of the processing by the processing unit 201, thereby executing some of the processing of the history management device 1.

[0050] <Acquisition part 11> The acquisition unit 11 acquires event history information from one or more tool provision systems 3 based on user information and credentials associated with it, and stores it in the storage unit 102. In this embodiment, the acquisition unit 11 uses user information and credentials associated with it to acquire event history information about events that occurred in a specific user's web tool. The acquired event history information is stored in the storage unit 102 in association with the user information linked to the credentials used for acquisition, and is used as a history of events in a specific user's tool for processing described later. The acquisition unit 11 may also be configured to periodically acquire data from the tool provision system 3, or it may be configured to acquire data when an event occurs in the tool provision system 3.

[0051] Furthermore, the acquisition unit 11 may perform a process to convert the raw event history information acquired from the tool provisioning system 3 into a format that is easy to use in the history management system 0. In this case, the acquisition unit 11 converts the data into a format suitable for use in the history management system 0 based on the conversion rules for each tool type stored in the storage unit 102.

[0052] Furthermore, the acquisition unit 11 accepts various inputs from the user terminal 2, such as specific conditions, work-specific conditions, work start time, work end time, specific conditions, and work-specific conditions. The acquisition unit 11 may also accept user information from the user terminal 2.

[0053] <Specific Processing Unit 12> The identification processing unit 12 identifies event history information that matches the specified conditions received from the user terminal 2. The specified conditions are conditions set by the user to identify the event history information to be extracted, and in this embodiment, they include the start date, end date, start time, end time, tool type, keyword, event type, duration, user, and user's department. When the start date is specified, the identification processing unit 12 identifies event history information related to events that occurred on or after the start date as event history information that matches the conditions, and when the end date is specified, it identifies event history information related to events that occurred before the end date as event history information that matches the conditions. Furthermore, the identification processing unit 12 identifies event history information of the specified user or users belonging to the specified department in the specified conditions.

[0054] Furthermore, the identification processing unit 12 identifies the working days of users who meet the conditions based on the work identification conditions received from the user terminal 2. The work identification conditions are conditions for identifying the work to be identified, and in this embodiment, they include the allowable hours, the department, the start date, and the end date. When a start date is set in the work identification conditions, working days from the set date onward are identified, and when an end date is set, working days prior to the set date are identified as days that meet the work identification conditions. In this embodiment, the identification processing unit 12 identifies the working days of users where either or both of the following are greater than or equal to the allowable hours: the difference between the activity start time and the work start time (activity start time - work start time), and the difference between the work end time and the activity end time (work end time - activity end time). This is done based on the work identification conditions including the allowable hours, the work start time and work end time acquired by the acquisition unit 11, and the activity start time and activity end time identified by the activity time identification unit 14. Furthermore, the specific processing unit 12 may identify working days in which the difference between the activity time and the user's daily working hours (for example, the time from the declared start time to the declared end time of work) is greater than or equal to the allowable time.

[0055] Workdays where there is a discrepancy between reported hours and actual working hours are likely to be problematic. By performing this processing in the specific processing unit 12, it is possible to identify workdays that may have problems, such as those where there is a discrepancy between reported hours and actual working hours.

[0056] <Status Identification Unit 13> The status identification unit 13 identifies the status of a specific event target based on event history information, including event target identification information and event type.

[0057] The following describes an example of how the status of a message tool such as an email application is determined when the storage unit 102 stores event history information for when a user receives an email MA, when they send an email MB (a reply to the email MA), and when they store event history information for email MCs (which are unrelated to email MAs and email MBs). In an email application, a series of emails that are related and displayed on a single screen in a thread view (for example, an email MA and an email MB) are associated and managed by unique identification information in the tool provisioning system 3, and the event history information for these series of emails is stored in the storage unit 102 associated by unique event target identification information. In this case, the event type for email MAs and email MCs is email reception, and the event type for email MBs is email sending.

[0058] The status identification unit 13 identifies the status of a series of email MAs and MBs as "replied" because the events of receiving and sending emails have occurred. Furthermore, for email MCs, although an event of the type "received email" has occurred, the status is identified as "not replied to" because the event history information associated with the same event target identification information does not include an event of "sent email." Thus, in this embodiment, when the tool type is email, the status identification unit 13 identifies the status of the event target email, including whether it is unreplied or replied to, based on the event type and event target identification information. Also, in this embodiment, the status of "replied" or "not replied" is identified as the status of a series of conversations that are sent / replied to and displayed as a thread within a messaging tool, including an email application.

[0059] Here, we have explained the status of emails and the like, but the status identification unit 13 may identify any status as long as it can identify the status of the event target based on event history information about events that occur continuously for the event target. For example, the status identification unit 13 may identify the status of whether a file has been updated or not in cloud storage, or whether a user has responded to an invitation to an event in a calendar application or not.

[0060] Furthermore, the status identification unit 13 may also identify the status as "replied" based on date and time information, taking into account the sequence of events, such as identifying the status as "replied" when an event sending an email occurs after an event receiving an email in the event history information associated with the same event target identification information.

[0061] <Activity time specific part 14> The activity time identification unit 14 identifies the start time and end time of the activity each day based on the event history information. In order to identify the time when the target user is active, the activity time identification unit 14 excludes event history information related to passive events such as receiving emails, and uses event history information related to active events caused by the user's activities to identify the start time, end time, and duration of the activity. The activity time identification unit 14 identifies event history information related to active events based on the event type included in the event history information, and uses the identified event history information related to active events to perform processing related to the identification of the start time, end time, and duration of the activity for each workday. In this embodiment, the activity time identification unit 14 identifies the time when the first active event occurs in a day as the activity start time and the time when the last active event occurs in a day as the activity end time, based on event history information associated with the user information of a specific user. However, the activity start time and activity end time may also be identified as times that satisfy certain conditions based on event history information, such as the time when a predetermined number of events occur for the first / last time in a day, or the time when the number of events per unit time exceeds a predetermined number, or falls below a predetermined number, for the first / last time in a day.

[0062] Furthermore, the activity time identification unit 14 further identifies the activity time, which is the time during which the user is performing work or other activities using the tool. In this embodiment, the activity time identification unit 14 identifies the time from the start time to the end time of the activity as the activity time. However, any method can be used to identify the activity time as long as the time during which the user is active can be identified based on event history information, such as identifying the activity time by aggregating the time during which there is event history information related to a certain number of active events for each unit of time. The activity start time, activity end time, and activity time for each workday identified by the activity time identification unit 14 are stored in the storage unit 102 in association with user information for each workday and may be used for display processing on the attendance management screen and for processing related to identifying workdays that meet the conditions in the identification processing unit 12. In addition, the activity time identification unit 14 may identify the time during which the user is active using the tool for each type of tool.

[0063] <Indicator calculation section 15> The indicator calculation unit 15 calculates activity indicators based on event history information. Activity indicators are indicators of user activity based on event history information, and in this embodiment, include activity volume, number of emails sent, number of unreplied messages, message reply time, and time taken. The indicator calculation unit 15 may also calculate activity indicators for a user based on event history information linked to user information, or it may calculate activity indicators for a group of multiple users based on the event history information of multiple users, such as users belonging to a specific department. Furthermore, the indicator calculation unit 15 may calculate indicators using event history information that corresponds to specific conditions identified in the specific processing unit 12, for example, by using the event history of multiple users belonging to a specific department, based on specific conditions received from the user terminal 2.

[0064] The following describes specific examples of activity indicators. Activity level is the amount of active events occurring per unit time, and in this embodiment, it is the number of historical information entries related to active events. In this embodiment, the indicator calculation unit 15 calculates the total activity level as the number of event history information entries for active events when the unit time is one week, and the average activity level as the average of the total activity level per unit time (in this embodiment, the unit time is one day: total activity level ÷ 7 days). The indicator calculation unit 15 may also calculate the number of historical information entries for each tool type and each event type as an activity indicator. In this embodiment, the number of emails sent, where the tool type is email and the event type is email sending, is calculated as the activity indicator. The indicator calculation unit 15 may also calculate the activity level as the number of events with a specific status, such as the number of unreplied emails or the number of replied emails, based on the status identified by the status identification unit 13.

[0065] The required time is the time from the occurrence of one event (the first event) to the occurrence of the next event (the second event). In this embodiment, the indicator calculation unit 15 calculates the required time based on event history information that corresponds to specific conditions obtained from the user terminal 2, such as the time from the occurrence of a passive event such as receiving an email to the occurrence of an active event such as replying to an email, or the time until the next event occurs in a specific tool. The average required time is the average of the required time for a specific user in a unit period, and in this embodiment, it is the average of the required time for a specific user over one week.

[0066] Furthermore, the metric calculation unit 15 may calculate the average required time for each tool type. In this embodiment, the metric calculation unit 15 calculates the average response time, which is the average required time for a messaging tool, based on event history information where the tool type is a messaging tool. At this time, the metric calculation unit 15 uses the event history information associated by the event target identification information to calculate the average required time for a specific event target, using the time required from the event of receiving an email or message (event type: receiving) to the event of sending an email or message (event type: sending) as the response time, and the average of the response time per unit of time as the average required time. In this embodiment, the average response time is the average required time for an email application, but it may be the average of the required times for multiple tools that send and receive messages, such as chat tools and email applications.

[0067] Furthermore, the response speed is the speed at which events are responded to. In this embodiment, it is an index calculated by dividing the unit time by the number of active events (the number of event history information related to active events). However, any index calculated based on event history information is acceptable, such as the reciprocal of the time from the occurrence of a passive event, such as an email notification, to the occurrence of an active event, such as sending an email.

[0068] <Display Processing Unit 16> The display processing unit 16 performs processing related to the display of various screens, such as the history display screen, attendance management screen, and dashboard screen, based on the event history information.

[0069] <Explanation of screen display example> The following explanation will use Figures 4-7 to describe examples of screen displays generated by the display processing unit 16.

[0070] <History display screen> Figure 4 shows an example of the display of the history display screen shown by the display processing unit 16. The history display screen W1 is a screen that displays the history of events based on event history information, and includes a specific condition input element W11 and event display elements W12A to W12E. In the example shown in Figure 4, five event display elements are displayed, but there is no limit to the number of event display elements; it may be five or more, or five or less.

[0071] The specific condition input element W11 is a screen display element for inputting conditions (specific conditions) for identifying event history information. In this embodiment, it is a screen display element that allows input of conditions regarding the start date, end date, tool type, keyword, start time, end time, action type (event type), and duration.

[0072] Event display elements W12A~12E are screen display elements for displaying the history of events (events EA~EE) based on event history information. In this embodiment, they are rectangular areas that display the date and time of event occurrence, event type, event content, and the status of the event target related to that event, based on date and time information. The event content also functions as an access element (link) that, when pressed, transitions to the event target display screen based on access information. In this embodiment, when an access element is pressed, the user terminal 2 displays the event target display screen in a separate tab in the browser application.

[0073] In the example shown in Figure 4, corresponding event display elements W12A to W12E are displayed for events EA to EE. Furthermore, event display elements W12A to W12E are connected and displayed in chronological order of event occurrence date and time. Between event display elements, for example, the difference in time (elapsed time) between the occurrence date and time of each event in each event display element is displayed, such as the difference in time (4 minutes and 56 seconds) between receiving an email with the subject "SANUS dev Test Everything" (event EC) and receiving an email with the subject "Salary Transfer Settings" (event ED).

[0074] Furthermore, when specific conditions are entered in the specific condition input element W11 and the search button is pressed, the specific processing unit 12 identifies event history information that matches the specific conditions. The display processing unit 16 displays event display elements based on the event history information that matches the specific conditions identified by the specific processing unit 12, and prevents the display of event history information that does not match the specific conditions. At this time, the time difference displayed between event display elements is the time difference between events displayed on the screen, but it may also be displayed as the difference between the event occurrence date and time in event history information that does not match the specific conditions and is not displayed on the screen.

[0075] <Attendance Management Screen> The attendance management screen W2 shown in Figure 5 is a screen displayed by the display processing unit 16 for displaying a list of the user's work status, and includes a work specification condition input element W21 and a work list W22. In this embodiment, when the attendance management screen W2 is displayed, the activity time specification unit 14 performs processing related to the specification of the start time of activity, the end time of activity, and the total activity time for each workday in advance.

[0076] The work-specific condition input element W21 is a screen element for inputting work-specific conditions to identify a work shift. In this embodiment, it includes an input field for inputting work-specific conditions including department, username / email address, start date, and end date, and a search button. The start date and end date can be entered by clicking on the date on the calendar displayed by clicking the calendar icon. In this embodiment, when a string is entered in the input field for inputting conditions related to the username and email address, the identification processing unit 12 identifies users whose username or email address includes that string as part or all of it, and information about that user's work days is displayed in the work list W22.

[0077] The work list W22 is a list for displaying the status of work, and for each workday it displays the date, user information including the user's department, job title and username, activity time, difference in start time (difference between activity start time and work start declaration time), difference in end time (difference between activity end time and work end declaration time), activity start time and activity end time identified by the activity time identification unit 14, and work start time and work end time acquired by the acquisition unit 11.

[0078] Furthermore, when work specification conditions are entered in the work specification condition input element W21 and the search button is pressed, the specification processing unit 12 identifies the work days that match the work specification conditions. The display processing unit 16 displays the work days that match the work specification conditions identified by the specification processing unit 12 in the work list W22.

[0079] <Dashboard screen> Using Figures 6 and 7, we will explain examples of the dashboard screen display shown by the display processing unit 16 based on the activity indicators calculated by the indicator calculation unit 15. The dashboard screen is a screen for displaying graphs and tables based on the activity indicators calculated by the indicator calculation unit 15. In Figure 6, dashboard screen W3 is displayed on a user terminal 2 such as an employee's terminal and displays the activity indicators of a specific user, while dashboard screen W3' shown in Figure 7 is displayed on a user terminal 2 such as an administrator's terminal and allows for the confirmation of detailed activity indicators for multiple users. Note that the screen displays in Figures 6 and 7 are merely examples, and graphs, lists, etc., using different activity indicators than those shown in the examples may be displayed.

[0080] The dashboard screen W3 in Figure 6 includes a condition input element W31, a radar chart display area W32, a departmental trend display area W33, and a time series chart display area W34.

[0081] The condition input element W31 is a screen element for inputting conditions (specific conditions) to identify event history information used for displaying the dashboard. In this embodiment, it includes input elements for inputting various conditions including start date, end date, keyword, and start time, and a search button. After conditions are entered in the condition input element W31, when the search button is pressed, the identification processing unit 12 identifies event history information that matches the specific conditions entered in the condition input element W31, and the indicator calculation unit 15 calculates an activity indicator using the event history information that matches the specific conditions entered in the condition input element W31, as identified by the identification processing unit 12. In this embodiment, if a start date is specified, the indicator calculation unit 15 calculates the activity indicator using event history information related to events that occurred after that start date, and so on, using event history information that matches the conditions entered in the condition input element W31. When the search button is pressed, the display processing unit 16 displays the dashboard screen W3 based on the activity indicator calculated by the indicator calculation unit 15 using the event history information that matches the conditions entered in the condition input element W31.

[0082] The radar chart display area W32 is an area for displaying a radar chart showing multiple activity indicators. In the example shown in Figure 6, the radar chart displayed in the radar chart display area W32 is a graph of activity indicators including response speed (1 ÷ response time), message sending speed (1 ÷ message response time), email sending speed (1 ÷ email response time), and contribution to GitHub (the number of beneficial activities (event history information of a specific event type) among event history information where the tool type is GitHub). In this embodiment, the contribution to GitHub is the number of event history information of an event type that can be judged as a beneficial activity for the developer, such as merging a pull request, among the event history where the tool type is GitHub. In this way, the indicator calculation unit 15 calculates the number of specific events related to a specific tool as an activity indicator based on the tool type and event type. Alternatively, the indicator calculation unit 15 may calculate the activity indicator based on the status of the event identified by the status identification unit.

[0083] The departmental trend display area W33 is a display area for displaying the activity level for each department. In the example shown in Figure 6, a bar graph of activity level is displayed for each department. The bar graph displays the activity level for each tool type (the number of event history information entries related to active events). In this embodiment, the departmental trend display area W33 shows a bar graph of the number of event history information entries where the tool type is Github, chat tool, or email. In the example shown in Figure 6, the number of event history information entries for a specific event type (for example, the number of event history information entries where the event type is sending a chat message) is displayed as an activity indicator for each tool type. In the example shown in Figure 6, the number of email replies is shown as the activity level in the activity level graph, but a graph showing the number of emails sent (the number of event history information entries where the tool type is an email application and the event type is sending an email) may also be displayed.

[0084] The time-series chart display area W34 is an area for displaying graphs that show activity levels for each time series. In the example shown in Figure 6, the graph displayed in the time-series chart display area W34 is a line graph showing daily activity levels.

[0085] The dashboard screen W3 shown in Figure 6 is a screen for displaying activity metrics for a specific user, but it may also be a screen for displaying activity metrics based on event history information of multiple users that meet the conditions entered in the condition input element W31, such as users belonging to a specific department.

[0086] Furthermore, the dashboard screen W3' in Figure 7 includes a condition input element W31, a departmental trend display area W33, a performance chart display area W35, and an activity list W36.

[0087] The performance chart display area W35 is a graph for displaying activity indicator values ​​for each user. In the example shown in Figure 6, the performance chart displayed in the performance chart display area W35 is a graph with the average message response speed (1 ÷ average message response time) and the average time taken set as the horizontal and vertical axes, respectively. In addition, the icon of each user is displayed at the position where points are plotted based on each user's activity indicator, and the user's name may also be displayed.

[0088] Activity list W36 is a list for displaying the activity history of each user over a specific period, and displays the period, user information including the user's department, job title, and username, and activity indicators calculated by the indicator calculation unit 15, including average response time, average time taken, total activity, average activity, number of emails sent, and number of unreplied emails. [Explanation of Symbols]

[0089] 0 History Management System 1. History Management Device 11 Acquisition Department 12 Specific Processing Unit 13 Status Identification Section 14 Activity time specific section 15 Indicator calculation part 16 Display Processing Unit 101 Processing Unit 102 Storage section 103 Communications Department 2 User terminals 3. Tool Provision System 31 Tool-providing device 4 Network

Claims

1. It is a history management system, A storage unit that stores the credentials of multiple web tools used by the user, associated with user information, An acquisition unit that acquires event history information from the user's tools from multiple tools based on the credentials associated with the user information, Based on the acquired event history information, a display processing unit displays the history, Equipped with, The aforementioned event history information is information regarding the history of events, including active events that occurred as a result of the user's actions. History management system.

2. The aforementioned event history information includes event details and date / time information. The display processing unit displays two or more event display elements, which are display elements of the screen related to the event, in chronological order based on the event history information. The aforementioned event display element is a screen display element that shows the event details and the date and time the event occurred. The history management system according to claim 1.

3. The display processing unit displays a first event display element indicating the occurrence of a first event and a second event display element indicating the occurrence of a second event in chronological order, and displays the time difference between the occurrence of the first event and the occurrence of the second event. The history management system according to claim 2.

4. The history management system further includes a specific processing unit, When the specified processing unit receives a specified condition including the required time, it identifies the history of an event in which the time difference until the next event occurs matches the specified condition, based on the event history information including the date and time information. The display processing unit displays the event display elements based on the event history information that corresponds to the specific conditions. The history management system according to claim 2.

5. The aforementioned event history information includes access information to the event target display screen in the web tool, The event display element includes an access element to the event target display screen based on the access information, The history management system according to claim 2.

6. The history management system includes a status identification unit, The aforementioned event history information includes event target identification information that identifies the target of the event and the event type, The status identification unit identifies the status of the event target based on the event target identification information and the event type, The aforementioned event display element displays the status, The history management system according to claim 2.

7. The aforementioned web tool includes a messaging tool, The status identification unit identifies the status of a conversation, including replied and unreplied, based on the event history information, which includes the event type, including received and sent, and the event target identification information. The history management system according to claim 6.

8. The event history information includes a history of events that occurred as a result of the user working with the web tool, and includes date and time information, and an event type for identifying at least passive and active events. The display processing unit displays the user's activity history based on the event history information relating to the active event identified based on the event type. The history management system according to claim 1.

9. The history management system further comprises an activity time identification unit and an identification processing unit, The activity time identification unit identifies the start time and end time of the activity for the day based on the event history information. The acquisition unit acquires the user's declared start time and declared end time of work. The specified processing unit receives work specification conditions including the allowable time, and identifies the work days of users where the difference between the activity start time and the declared start time of work and / or the difference between the declared end time of work and the end time of activity is equal to or greater than the allowable time. The display processing unit displays a list of the date on the working day of the user identified by the identification processing unit, the start time of the activity, and the end time of the activity. The history management system according to claim 8.

10. The history management system further includes an indicator calculation unit, The aforementioned indicator calculation unit calculates activity indicators related to the user's activity history based on the event history information related to active events. The display processing unit displays the activity indicator. The history management system according to claim 8.

11. The aforementioned event history information includes date and time information, The activity indicator includes an activity volume that shows the total amount of user activity history per unit time based on the event history information, The history management system according to claim 10.

12. The aforementioned event history information includes the tool type, The display processing unit displays the activity level for each tool type. The history management system according to claim 11.

13. The aforementioned event history information includes unique identification information for identifying the relevant event, The activity indicator includes the time elapsed from the occurrence of the first event to the occurrence of a second event related to the first event, which is identified based on the identification information. The history management system according to claim 10.

14. The user information includes department information, The aforementioned indicator calculation unit calculates the aforementioned activity indicator for each department, The display processing unit displays the activity indicators for each department. The history management system according to claim 10.

15. The history management system further includes a specific processing unit, The specified processing unit receives a specified condition and, based on the event history information, identifies the event history information that corresponds to the specified condition. The indicator calculation unit calculates the activity indicator based on the event history information corresponding to the specific conditions identified by the specific processing unit. The history management system according to claim 10.

16. A method of managing history performed by a computer, The memory unit of the aforementioned computer stores the credentials of multiple web tools used by the user, associating them with user information. Based on the user information and the associated credentials, the acquisition step involves acquiring event history information from multiple tools using the user's tools, Based on the acquired event history information, a display processing step is performed to display the history, Equipped with, The aforementioned event history information is information regarding the history of events, including active events that occurred as a result of the user's actions. History management method.

17. A computer program that causes the computer to execute the history management method described in claim 16.

Images