Busyness prediction device, system, method, and program

Abstract

To provide a busyness prediction device and the like that can contribute to the assessment of a timing for communication in a workplace by conducting individual busyness prediction according to an employee.SOLUTION: A busyness prediction device includes: a vital database in which vital data of the past is organized for each confirmation object person; a schedule database in which schedule data is organized for each of the confirmation object person; a control unit that, when receiving a busyness information request related to busyness of a confirmation object person from a confirmation requester terminal used by a confirmation requester, requests new vital data from a wearable terminal attached to the confirmation object person and acquires the new vital data from the wearable terminal; and a prediction unit that predicts busyness of the confirmation object person on the basis of the new vital data, the vital database and the schedule database.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present invention relates to a busyness prediction device, a busyness prediction system, a method, and a program. [Background technology]

[0002] In recent years, many companies have introduced remote work, which has eliminated the stress of commuting for employees and allowed them to use their commuting time for private time, helping them achieve a work-life balance. On the other hand, remote work makes it difficult to communicate with other employees because they do not meet face-to-face, and it is difficult to understand the other person's situation and schedule, which is an obstacle to work efficiency. However, even if you come to the office, it is not easy to determine whether other employees have time to consult with you. Therefore, even if you want to consult about work, you may not be able to find the right timing, and work that could be completed quickly may drag on. Therefore, some companies have introduced a schedule sharing system that allows employees to share their schedules, making it easier to adjust the timing of communication with other employees.

[0003] However, the schedule sharing system cannot grasp the importance or urgency of each task registered in the schedule, and it is difficult for even the person himself to grasp the degree of busyness. In addition, although it is possible to grasp the degree of busyness to some extent by describing the schedule in detail, writing the schedule requires extra man-hours. Furthermore, even if the man-hours are spent creating a schedule, there is a possibility that a meeting will be extended, or that an unexpected situation will occur, such as being forced to deal with a sudden problem. Even if the schedule appears to be relaxed, it is quite possible that the person is actually busy, so it is difficult to determine the timing to communicate only by sharing the schedule. Therefore, there is a technology that acquires vital data such as heart rate and body temperature from a wearable sensor attached to the employee and estimates the degree of busyness of the employee based on the vital data (see, for example, Patent Documents 1-3). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2018-186435 [Patent Document 2] Patent Publication No. 2017-26568 [Patent Document 3] Patent Publication No. 2009-20672 Summary of the Invention [Problem to be solved by the invention]

[0005] The following analysis is provided by the present inventors.

[0006] However, since vital data varies from person to person, it is difficult for the techniques described in Patent Documents 1-3 to predict how busy an individual employee will be.

[0007] The main objective of the present invention is to provide a busyness prediction device, system, method, and program that can contribute to determining the timing to promote communication within the workplace by making individual busyness predictions for each employee. [Means for solving the problem]

[0008] A busyness prediction device according to a first aspect includes a vital database in which past vital data is organized for each person to be confirmed, a schedule database in which schedule data is organized for each person to be confirmed, a control unit configured to request new vital data from a wearable device worn by the person to be confirmed and acquire the new vital data from the wearable device when a busyness information request related to the busyness of the person to be confirmed is received from a confirmation requester terminal used by the confirmation requester, and a prediction unit configured to predict the busyness of the person to be confirmed based on the new vital data, the vital database, and the schedule database.

[0009] A busyness prediction system according to a second aspect includes a busyness prediction device according to the first aspect, a person to be confirmed terminal used by the person to be confirmed, a wearable terminal worn by the person to be confirmed, and a confirmation requester terminal used by the person to be confirmed, wherein the wearable terminal is configured to periodically transmit the vital data corresponding to the past vital data to the busyness prediction device and to transmit the vital data corresponding to the busyness information request to the busyness prediction device separately from the periodic transmission of the vital data, the person to be confirmed terminal is configured to transmit the schedule data input by operation of the person to be confirmed to the busyness prediction device, and the confirmation requester terminal is configured to transmit the busyness information request input by operation of the person to be confirmed to the busyness prediction device, and to receive and display busyness information related to the busyness predicted by the busyness prediction device.

[0010] A busyness prediction method according to a third aspect is a method executed by hardware resources, the hardware resources including a vital database in which past vital data is organized for each person to be confirmed, and a schedule database in which schedule data is organized for each person to be confirmed, and the method includes the steps of, upon receiving a busyness information request related to the busyness of the person to be confirmed from a confirmation requester terminal used by the confirmation requester, requesting new vital data from a wearable device worn by the person to be confirmed, acquiring the new vital data from the wearable device, and predicting the busyness of the person to be confirmed based on the new vital data, the vital database, and the schedule database.

[0011] A program relating to a fourth aspect is a program that causes hardware resources to execute a process of predicting how busy a person to be confirmed will be, the hardware resources including a vital database that organizes past vital data for each person to be confirmed, and a schedule database that organizes schedule data for each person to be confirmed, and when the program receives a busyness information request related to the busyness of the person to be confirmed from a confirmation requester terminal used by the confirmation requester, the program causes the hardware resources to execute a process of requesting new vital data from a wearable device worn by the person to be confirmed, a process of acquiring the new vital data from the wearable device, and a process of predicting how busy the person to be confirmed will be based on the new vital data, the vital database, and the schedule database.

[0012] The program can be recorded in a computer-readable storage medium. The storage medium can be a non-transient medium such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. In the present disclosure, the program can also be embodied as a computer program product. The program is input to the computer device from an input device or an external device via a communication interface, stored in a storage device, drives the processor according to a predetermined step or process, and can display the processing result, including an intermediate state as necessary, at each stage via a display device, or can communicate with the outside via the communication interface. For example, a computer device for this purpose typically includes a processor, a storage device, an input device, a communication interface, and a display device as necessary, which are connectable to each other via a bus. Effect of the Invention

[0013] According to the above-mentioned viewpoints 1-4, it is possible to predict how busy each employee is individually, thereby contributing to determining the best timing for communication within the workplace. [Brief description of the drawings]

[0014] [Figure 1] 1 is a block diagram showing a schematic configuration of a busyness prediction system according to a first embodiment. [Diagram 2] 2 is a schematic diagram showing the configuration of vital data and schedule data used in the busyness prediction system according to the first embodiment. FIG. [Diagram 3] FIG. 2 is a flow chart diagram illustrating the operation of the busyness prediction system according to the first embodiment. [Figure 4] 4 is a flowchart illustrating an example of an operation of a busyness prediction device in the busyness prediction system according to the first embodiment. [Diagram 5] FIG. 11 is a block diagram showing a schematic configuration of a busyness prediction device according to a third embodiment. [Figure 6] FIG. 2 is a block diagram illustrating a schematic configuration of hardware resources. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, the embodiments will be described with reference to the drawings. In addition, when drawing reference symbols are used in this application, they are intended to aid understanding only and are not intended to limit the present invention to the illustrated aspects. In addition, the following embodiments are merely examples and do not limit the present invention. In addition, the connection lines between blocks in the drawings and the like referred to in the following description include both bidirectional and unidirectional. A unidirectional arrow is a schematic representation of the flow of a main signal (data) and does not exclude bidirectionality. Furthermore, although not explicitly shown in the circuit diagrams, block diagrams, internal configuration diagrams, connection diagrams, and the like shown in this disclosure, an input port and an output port exist at the input end and output end of each connection line. The same is true for input / output interfaces. A program is executed via a computer device, which includes, for example, a processor, a storage device, an input device, a communication interface, and a display device as necessary, and the computer device is configured to be able to communicate with an internal or external device (including a computer) via the communication interface, regardless of whether it is wired or wireless.

[0016] [Embodiment 1] The busyness prediction system according to the embodiment 1 will be described with reference to the drawings. Fig. 1 is a block diagram showing a schematic configuration of the busyness prediction system according to the embodiment 1. Fig. 2 is a schematic diagram showing a configuration of vital data and schedule data used in the busyness prediction system according to the embodiment 1.

[0017] The busyness prediction system 1 is a system for predicting how busy a person to be confirmed is (see FIG. 1). The busyness prediction system 1 includes a busyness prediction device 10, a wearable terminal 20, a person to be confirmed terminal 30, a confirmation requester terminal 40, and a network 50.

[0018] The busyness prediction device 10 is a device that predicts the busyness of a person to be confirmed upon request of a confirmation requester (see FIG. 1). For example, a server device equipped with a computer including a processor, a memory, a network interface, etc. can be used as the busyness prediction device 10. The busyness prediction device 10 is communicably connected to a wearable terminal 20, a person to be confirmed terminal 30, and a confirmation requester terminal 40 via a network 50. By executing a predetermined program, the busyness prediction device 10 can be virtually configured to include a vital database 11, a schedule database 12, a receiving unit 13, a control unit 14, a prediction unit 15, and a transmitting unit 16.

[0019] The vital database 11 is a database that organizes past vital data for each person to be confirmed (see FIG. 1). Here, the vital data includes identification information, biometric information, and date and time information (see FIG. 2). The identification information is information for identifying the person to be confirmed who wears the wearable terminal 20, and may be, for example, the identification number, email address, or IP (Internet Protocol) address of the person to be confirmed. The biometric information is information related to the state of the body obtained from the person to be confirmed using the wearable terminal 20, and may be, for example, numerical values ​​such as body temperature, pulse rate, and blood pressure. The date and time information is information related to the date and time when the biometric information was obtained. The vital data may also include meteorological data such as temperature, air pressure, and humidity that may affect the biometric information. The vital database 11 may accumulate vital data collected periodically (vital data for creating a busy / slow standard), hold the vital data for a predetermined period going back from the present to the past, and delete old vital data that exceeds the predetermined period. In addition, the vital data database 11 may store, for each person to be confirmed, vital data (vital data that serves as the basis for calculating the degree of busyness) acquired from the wearable terminal 20 in response to a request for busyness information from the confirmation requester terminal 40, in addition to the vital data collected periodically.

[0020] The schedule database 12 is a database in which schedule data is organized for each person to be confirmed (see FIG. 1). Here, the schedule data includes identification information, time schedule information, and detailed schedule information (see FIG. 2). The identification information is information for identifying the person to be confirmed who wears the wearable terminal 20, and may be, for example, the identification number, email address, or IP address of the person to be confirmed. The time schedule information is schedule information related to time, and includes, for example, the start time and end time of the person to be confirmed's work, as well as time information such as the start time of the outbound movement, the arrival time at the local site, the start time of the return movement, and the arrival time at the next destination (including returning to the company) in the case of work involving movement. The detailed schedule information is detailed schedule information, and includes, for example, detailed information such as the work content, work location, and expected busyness level of the work (level arbitrarily input by the person to be confirmed). The schedule data is registered in the schedule database 12 by the person to be confirmed using the person to be confirmed terminal 30 himself / herself. When the person to be confirmed changes the schedule data using the person to be confirmed terminal 30, the schedule database 12 is immediately updated with the data.

[0021] The receiver 13 is a functional unit configured to receive information from the wearable terminal 20, the person to be confirmed terminal 30, and the confirmation requester terminal 40 (see FIG. 1). Information received by the receiver 13 includes vital data from the wearable terminal 20 (see FIG. 2), schedule data from the person to be confirmed terminal 30 (see FIG. 2), and a busyness information request from the confirmation requester terminal 40.

[0022] The control unit 14 is a functional unit configured to control the vital sign database 11, the schedule database 12, the receiving unit 13, the control unit 14, the prediction unit 15, and the transmitting unit 16 (see FIG. 1). The control unit 14 organizes the vital sign data and schedule data received by the receiving unit 13 for each person to be confirmed, and stores them in the vital sign database 11 and the schedule database 12. The control unit 14 causes the transmitting unit 16 to transmit a vital sign data request to the wearable device 20 of the person to be confirmed corresponding to the busyness information request.

[0023] The prediction unit 15 is a functional unit configured to predict the current busyness of the confirmation subject based on the vital data acquired in response to the vital data request, the vital database 11, and the schedule database 12 (see FIG. 1). When the vital data acquired in response to the vital data request is registered in the vital database 11, the prediction unit 15 reads out the vital data collected periodically from the vital database 11, and creates a busy / slow standard based on the read out vital data. The prediction unit 15 calculates the busy / slow level based on the vital data acquired in response to the vital data request and the busy / slow standard. For example, when calculating the busy / slow level based on the pulse rate among the biological information in the vital data, the busy / slow level can be calculated by dividing the pulse rate (the corrected pulse rate in the case of correcting with weather data) in the vital data acquired in response to the vital data request by the busy / slow standard related to the pulse rate. The prediction unit 15 predicts busyness based on the detailed schedule information in the read out schedule data and the calculated busy / slow level. In predicting busyness, for example, if the detailed schedule information includes a busyness level, busyness can be predicted (calculated) by multiplying the busyness level by the busy / unbusy degree. If the detailed schedule information does not include a busyness level, busyness may be calculated by the busy / unbusy degree.

[0024] Here, in creating the busy / slow standard, for example, a busy / slow standard (standard consisting of average values ​​of various types of biometric information) can be created by calculating an average value of biometric information (pulse, body temperature, blood pressure, etc.) in the vital data based on the read-out vital data. In addition, in creating the busy / slow standard, for example, if the read-out vital data includes meteorological data (temperature, air pressure, humidity, etc.), the busy / slow standard may be created by correcting the calculated various types of biometric information to biometric information at normal temperature and normal pressure and then calculating an average value. In this case, the periodically collected vital data is a value obtained by correcting the biometric information in the periodically collected vital data to biometric information at normal temperature and normal pressure. In addition, in creating the busy / slow standard, for example, when calculating an average value of biometric information, the busy / slow standard may be created by using date and time information in the read-out vital data to select biometric information at a time corresponding to the time of date and time information in the vital data acquired in response to a vital data request and calculating an average value.

[0025] The transmitting unit 16 is a functional unit configured to transmit information to the wearable device 20 and the confirmation requester terminal 40 (see FIG. 1). When the receiving unit 13 receives a busyness information request from the confirmation requester terminal 40, the transmitting unit 16 transmits a vital data request to the wearable device 20 of the person to be confirmed corresponding to the busyness information request. The transmitting unit 16 transmits information related to busyness predicted by the predicting unit 15 (busyness information) to the confirmation requester terminal 40 of the confirmation requester corresponding to the busyness information request. The busyness information may include schedule data of the person to be confirmed (for example, schedule data for the date and time corresponding to the busyness information) as necessary.

[0026] The wearable terminal 20 is a terminal that is attached to a predetermined part of the body of the person to be confirmed (see FIG. 1). For example, a wearable computer, a smart watch, a wristband terminal, or the like, including a processor, a memory, a network interface, a display, and a sensor, can be used as the wearable terminal 20. The wearable terminal 20 may communicate with the busyness prediction device 10 via a network 50, or may communicate with the busyness prediction device 10 via the person to be confirmed terminal 30 and the network 50. The wearable terminal 20 includes a sensor that measures the biological condition of the person to be confirmed (for example, body temperature, pulse, blood pressure, etc.). The wearable terminal 20 may also include a sensor that measures (detects) weather data (for example, temperature, air pressure, humidity, etc.) in which the person to be confirmed is located. The wearable terminal 20 periodically transmits the measured vital data to the busyness prediction device 10. Furthermore, the wearable device 20 transmits the measured vital data to the busyness prediction device 10 in response to a vital data request, in addition to the periodic transmission of the vital data.

[0027] The confirmation target person terminal 30 is a terminal used by the confirmation target person (see FIG. 1). There may be at least one confirmation target person terminal 30 in the busyness prediction system 1, and there may be multiple confirmation target person terminals 30. When the confirmation target person becomes a confirmation requester, the confirmation target person terminal 30 may become a confirmation requester terminal 40. The confirmation target person terminal 30 can communicate with the busyness prediction device 10 via the network 50. For example, a personal computer including a processor, memory, network interface, display, input device, etc., a tablet terminal, a smartphone, etc. can be used as the confirmation target person terminal 30. The confirmation target person terminal 30 can input, output, transmit, receive, and display information (for example, schedule, etc.). The confirmation target person terminal 30 transmits schedule data input by the operation of the confirmation target person to the busyness prediction device 10. The confirmation target person terminal 30 may relay communication between the wearable terminal 20 and the network 50.

[0028] The confirmation requester terminal 40 is a terminal used by the confirmation requester (see FIG. 1). There may be at least one confirmation requester terminal 40 in the busyness prediction system 1, and there may be multiple confirmation requester terminals 40. When the confirmation requester becomes the person to be confirmed, the confirmation requester terminal 40 may become the person to be confirmed terminal 30. The confirmation requester terminal 40 can communicate with the busyness prediction device 10 via the network 50. For example, a personal computer, tablet terminal, smartphone, etc. including a processor, memory, network interface, display, input device, etc. can be used as the confirmation requester terminal 40. The confirmation requester terminal 40 can input, output, transmit, receive, and display information (for example, busyness information request, busyness information, etc.). When the confirmation requester checks the busyness of the person to be confirmed, the confirmation requester terminal 40 transmits a busyness information request input by the operation of the confirmation requester to the busyness prediction device 10. The busyness information request includes identification information of the person to be confirmed and identification information of the confirmation requester. The confirmation requester terminal 40 receives the busyness information from the busyness prediction device 10 and displays it.

[0029] The network 50 is a wired or wireless communication network for communication between the busyness prediction device 10, the wearable terminal 20, the confirmation target terminal 30, and the confirmation requester terminal 40 (see FIG. 1). For the network 50, for example, a communication network such as a personal area network (PAN), a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), or a global area network (GAN) can be used.

[0030] Next, the operation of the busyness prediction system according to the first embodiment will be described with reference to the drawings. Fig. 3 is a flow chart diagram illustrating the operation of the busyness prediction system according to the first embodiment.

[0031] First, when new schedule data is registered or updated (regardless of the number of updates), the confirmation subject terminal 30 inputs schedule data (changes, additions, deletions in case of updates) at any time through the operation of the confirmation subject, and transmits the input data to the busyness prediction device 10 (step A1).

[0032] Next, the busyness prediction device 10 receives the schedule data from the confirmation target person terminal 30, and registers (updates) the received schedule data in the schedule database 12 (step A2).

[0033] In addition, when the vital data is collected periodically, the wearable device 20 detects the biological condition of the person to be confirmed at preset regular points in time, and transmits the vital data including the detected biological information to the busyness prediction device 10 (step B1).

[0034] Next, the busyness prediction device 10 receives the vital data from the wearable device 20, and accumulates the received vital data in the vital database 11 (step B2). Note that steps B1 and B2 are periodically repeated.

[0035] Furthermore, when the confirmation requester is about to meet with the person to be confirmed, the confirmation requester terminal 40 selects the person to be confirmed through the operation of the person to be confirmed, and transmits a busyness information request including the identification information of the person to be confirmed to the busyness prediction device 10 (step C1).

[0036] Next, the busyness prediction device 10 transmits a vital data request to the wearable device 20 of the person to be confirmed who corresponds to the received busyness information request (Step C2).

[0037] Next, the wearable device 20 receives a vital data request from the busyness prediction device 10, measures the biological information of the person to be confirmed in real time, and transmits vital data including the measured biological information to the busyness prediction device 10 (step C3).

[0038] Next, the busyness prediction device 10 receives the vital data from the wearable device 20, and registers the received vital data in the vital database 11 separately from the vital data collected periodically (step C4).

[0039] Next, the busyness prediction device 10 reads out the vital data collected periodically from the vital data database 11 for the person to be confirmed who corresponds to the received busyness information request, and creates busy / slow standards based on the read out vital data (step C5).

[0040] Next, the busyness prediction device 10 calculates the busy / unbusy degree based on the vital data acquired in response to the vital data request and the busy / unbusy criteria (step C6).

[0041] Next, the busyness prediction device 10 predicts busyness based on the detailed schedule information in the read schedule data and the calculated busy / unbusy degree (step C7). Note that if the detailed schedule information does not include a busyness level, the busy / unbusy degree may be used as busyness.

[0042] Next, the busyness prediction device 10 transmits information relating to the predicted busyness (busyness information) to the confirmation requester terminal 40 of the confirmation requester corresponding to the busyness information request (step C8).

[0043] Next, the confirmation requester terminal 40 receives and displays the busyness information from the busyness prediction device 10 (step C9), and then ends the process.

[0044] According to the first embodiment, by using the schedule data of the person to be confirmed (employee), the past vital data of the person to be confirmed, and new vital data corresponding to the busyness information request, it is possible to predict the busyness of each employee individually and contribute to determining the timing for communication within the workplace. As a result, no wasted work time is generated and the lack of communication within the workplace can be resolved.

[0045] Furthermore, according to the first embodiment, vital data of the person to be confirmed (employee) is automatically collected from the wearable device, so the current busyness of each employee can be calculated without increasing the burden on the employee. As a result, it becomes easy to know how busy other employees are, which contributes to improving work efficiency and the atmosphere in the workplace by reducing waiting time for case consultations and increasing opportunities for employees to talk to each other.

[0046] Furthermore, according to embodiment 1, a standard busy / unbusy standard suited to each employee is created based on the vital data and weather data of the person being checked (employee) to predict how busy they will be, so that individual differences in vital data such as pulse rate and body temperature can be absorbed.

[0047] [Embodiment 2] The busyness prediction system according to the second embodiment will be described with reference to the drawings. Fig. 4 is a flow chart that illustrates the operation of the busyness prediction device in the busyness prediction system according to the first embodiment. Note that the basic configuration of the busyness prediction system according to the second embodiment is similar to that of the busyness prediction system according to the first embodiment, so please refer to Fig. 1.

[0048] The second embodiment is a variation of the first embodiment, in which the busyness prediction device 10 counts the number of times a request for busyness information is received from the confirmation requester terminal 40 within a specified period going back from the present to the past, and when the counted number of times it is received reaches a threshold value, it determines that the person to be confirmed has a large number of personalized tasks, and sends a specified message to the confirmation requester terminal together with busyness information, encouraging the person to consult with employees other than the person to be confirmed in order to promote decentralization of tasks.

[0049] The vital information database 11 also stores, for each person to be confirmed, the number of times that a busyness information request has been received from the confirmation requester terminal 40 within a predetermined period going back from the present to the past.

[0050] When the control unit 14 receives a busyness information request from the confirmation requester terminal 40 at the receiving unit 13, it counts the number of times the busyness information request has been received for the confirmation subject corresponding to the busyness information request by one and registers this in the vital database 11.

[0051] After predicting busyness, the prediction unit 15 refers to the vital database 11 and judges whether the number of times busyness information requests related to the person to be confirmed have been received reaches a threshold value. The threshold value can be a preset constant, and can be calculated from the number of times busyness information requests have been received for each person to be confirmed and changed as appropriate. When calculating the threshold value, for example, the 30% number of times that busyness information requests have been received most frequently (for example, the third number of times that they have been received most frequently out of the 10 most frequently received requests) may be set as the threshold value.

[0052] When the number of times that busyness information requests are received does not reach a threshold value, the transmission unit 16 transmits information relating to busyness predicted by the prediction unit 15 (busyness information) to the confirmation requester terminal 40 of the confirmation requester corresponding to the busyness information request. When the number of times that busyness information requests are received reaches a threshold value, the transmission unit 16 transmits a predetermined message urging the person to consult with an employee other than the person to be confirmed, together with the busyness information predicted by the prediction unit 15, to the confirmation requester terminal 40 of the confirmation requester corresponding to the busyness information request.

[0053] Other configurations are the same as those of embodiment 1. The busyness prediction system according to embodiment 2 is similar to steps A1 to A2 and steps B1 to B2 in Fig. 3 in the operation of the busyness prediction system according to embodiment 1, but instead of the operation of the busyness prediction device 10 in steps C1 to C9 (step C2, steps C4 to C8), the following operations (steps D1 to D11) are performed.

[0054] When the confirmation requester is about to meet with the confirmation target, the busyness prediction device 10 receives a busyness information request from the confirmation requester terminal 40 (step D1).

[0055] Next, the busyness prediction device 10 counts (increments by one) the number of times that the busyness information request has been received for the confirmation subject corresponding to the received busyness information request (step D2).

[0056] Next, the busyness prediction device 10 transmits a vital data request to the wearable device 20 of the person to be confirmed corresponding to the received busyness information request (step D3). As a result, by receiving the vital data request from the busyness prediction device 10, the wearable device 20 measures the biological information of the person to be confirmed in real time and transmits vital data including the measured biological information to the busyness prediction device 10.

[0057] Next, the busyness prediction device 10 receives the vital data from the wearable device 20 (step D4).

[0058] Next, the busyness prediction device 10 registers the received vital data in the vital data database 11 separately from the periodically collected vital data (step D5).

[0059] Next, the busyness prediction device 10 reads out the vital data collected periodically from the vitals database 11 for the person to be confirmed who corresponds to the received busyness information request, and creates busy / slow standards based on the read out vitals data (step D6).

[0060] Next, the busyness prediction device 10 calculates the busy / unbusy degree based on the vital data acquired in response to the vital data request and the busy / unbusy criteria (step D7).

[0061] Next, the busyness prediction device 10 predicts busyness based on the detailed schedule information in the read schedule data and the calculated busy / unbusy degree (step D8). Note that if the detailed schedule information does not include a busyness level, the busy / unbusy degree may be used as busyness.

[0062] Next, the busyness prediction device 10 refers to the vital database 11 to determine whether the number of times that the busyness information request related to the confirmation target person has been received has reached a threshold value (step D9).

[0063] If the number of times the busyness information request has been received does not reach the threshold value (NO in step D9), the busyness prediction device 10 transmits information related to the predicted busyness (busyness information) to the confirmation requester terminal 40 of the confirmation requester corresponding to the busyness information request (step D10), and then ends. As a result, the confirmation requester terminal 40 receives and displays the busyness information from the busyness prediction device 10.

[0064] If the number of times that busyness information requests have been received reaches the threshold value (YES in step D9), the busyness prediction device 10 transmits a predetermined message encouraging the person to consult with an employee other than the person to be confirmed together with the predicted busyness information to the confirmation requester terminal 40 of the confirmation requester corresponding to the busyness information request (step D11), and then ends. As a result, the confirmation requester terminal 40 receives and displays the predetermined message and busyness information from the busyness prediction device 10.

[0065] According to the second embodiment, as in the first embodiment, it is possible to predict the busyness of each employee individually, thereby contributing to determining the timing for communication within the workplace. In addition, when the number of times that requests for busyness information have been received for the person to be confirmed reaches a threshold value, a specified message is sent to the confirmation requester terminal 40 encouraging the person to consult with an employee other than the person to be confirmed, thereby encouraging the person to be confirmed who has too much work to distribute the work.

[0066] [Embodiment 3] A busyness prediction device according to the third embodiment will be described with reference to the drawings. Fig. 5 is a block diagram showing a schematic configuration of the busyness prediction device according to the third embodiment.

[0067] The busyness prediction device 10 is a device configured to predict the busyness of a confirmation subject (see FIG. 5). The busyness prediction device 10 includes a vital sign database 11, a schedule database 12, a control unit 14, and a prediction unit 15.

[0068] The vital database 11 is a database in which past vital data is organized for each person to be confirmed. The schedule database 12 is a database in which schedule data is organized for each person to be confirmed. The control unit 14 is configured to request new vital data from the wearable terminal 20 worn by the person to be confirmed and acquire the new vital data from the wearable terminal 20 when a busyness information request relating to the busyness of the person to be confirmed is received from the confirmation requester terminal 40 used by the confirmation requester. The prediction unit 15 is configured to predict the busyness of the person to be confirmed based on the new vital data, the vital database, and the schedule database.

[0069] According to embodiment 3, by using the schedule data of the person (employee) to be confirmed, the past vital data of the person to be confirmed, and new vital data corresponding to a request for busyness information, it is possible to predict individual busyness for each employee, thereby contributing to determining the timing for communication within the workplace.

[0070] The busyness prediction device according to the first and second embodiments can be configured by so-called hardware resources (information processing device, computer), and can use one having the configuration shown in Fig. 6. For example, the hardware resource 100 includes a processor 101, a memory 102, a network interface 103, etc., which are connected to each other by an internal bus 104.

[0071] Note that the configuration shown in Fig. 6 is not intended to limit the hardware configuration of the hardware resource 100. The hardware resource 100 may include hardware (e.g., an input / output interface) that is not shown. Furthermore, the number of units such as the processor 101 included in the device is not intended to be limited to the example shown in Fig. 6, and for example, multiple processors 101 may be included in the hardware resource 100. For example, a CPU (Central Processing Unit), an MPU (Micro Processor Unit), a GPU (Graphics Processing Unit), etc. can be used as the processor 101.

[0072] The memory 102 may be, for example, a random access memory (RAM), a read only memory (ROM), a hard disk drive (HDD), a solid state drive (SSD), or the like.

[0073] The network interface 103 may be, for example, a LAN (Local Area Network) card, a network adapter, a network interface card, or the like.

[0074] The functions of the hardware resource 100 are realized by the above-mentioned processing module. The processing module is realized, for example, by the processor 101 executing a program stored in the memory 102. The program can be updated by downloading it via a network or by using a storage medium storing the program. Furthermore, the processing module may be realized by a semiconductor chip. That is, it is sufficient that the functions performed by the processing module are realized by executing software on some kind of hardware.

[0075] A part or all of the above-described embodiments may be described as, but is not limited to, the following supplementary notes.

[0076] [Appendix 1] A vital database that organizes the past vital data of each person to be confirmed, a schedule database in which schedule data is organized for each person to be confirmed; a control unit configured to, when receiving a busyness information request related to the busyness of the person to be confirmed from a confirmation requester terminal used by a confirmation requester, request new vital data from a wearable terminal worn by the person to be confirmed and acquire the new vital data from the wearable terminal; A prediction unit configured to predict the busyness of the confirmation subject based on the new vital data, the vital database, and the schedule database; Equipped with Busyness predictor. [Appendix 2] The prediction unit is a busy / unbusy standard is created based on the past vital data of the person to be confirmed corresponding to the busyness information request in the vital database, a busy / unbusy level is calculated based on the new vital data and the busy / unbusy standard, and a busyness is predicted based on the schedule data and the busy / unbusy level. 2. The busyness prediction device according to claim 1. [Appendix 3] The vital data includes biological information of the person to be confirmed, The busy / unbusy criterion is an average value of the biological information in the past vital data. 3. The busyness prediction device according to claim 2. [Appendix 4] The vital data includes biometric information of the person to be confirmed and date and time information when the biometric information was acquired, The busy / unbusy criterion is an average value of the biological information in the past vital data at a time corresponding to the time of the date and time information in the new vital data. 3. The busyness prediction device according to claim 2. [Appendix 5] The vital data includes biometric information of the person to be confirmed and meteorological data at the time when the biometric information was acquired, the new vital data is a value obtained by correcting the biological information in the new vital data using the meteorological data, The busy / unbusy criterion is an average value obtained by correcting the biological information in the past vital data using the meteorological data. 3. The busyness prediction device according to claim 2. [Appendix 6] The busy / unbusy degree is a value obtained by dividing the biological information in the new vital data by the busy / unbusy standard. 6. A busyness prediction device according to any one of claims 3 to 5. [Appendix 7] The schedule data includes an expected busyness level for the job, The busyness is a value obtained by multiplying the busyness level by the busy / unbusy degree. 3. The busyness prediction device according to claim 2. [Appendix 8] a transmitting unit configured to transmit busyness information related to the busyness to the confirmation requester terminal; 2. The busyness prediction device according to claim 1. [Appendix 9] a transmitter configured to transmit information; the control unit is configured, when receiving the busyness information request from the confirmation requester terminal, to count the number of times the busyness information request has been received for the confirmation target person corresponding to the busyness information request by one and register the number of times the busyness information request has been received in the vital database; The prediction unit is configured to refer to the vital database and determine whether or not a number of times a request for busyness information regarding the confirmation target person has been received has reached a threshold value; the transmission unit is configured to transmit, when the number of times of reception reaches the threshold value, a predetermined message urging the person to consult with an employee other than the person to be confirmed, together with busyness information relating to the busyness, to the confirmation requester terminal. 2. The busyness prediction device according to claim 1. [Appendix 10] A busyness prediction device according to claim 1; A verification subject terminal used by the verification subject; The wearable terminal is attached to the person to be confirmed; and the confirmation requester terminal used by the confirmation requester; Equipped with the wearable device is configured to periodically transmit the vital data corresponding to the past vital data to the busyness prediction device, and to transmit the vital data corresponding to the busyness information request to the busyness prediction device separately from the periodic transmission of the vital data; the confirmation target person terminal is configured to transmit the schedule data input by an operation of the confirmation target person to the busyness prediction device; the confirmation requester terminal is configured to transmit the busyness information request input by an operation of the confirmation requester to the busyness prediction device, and to receive and display busyness information relating to the busyness predicted by the busyness prediction device. Busyness prediction system. [Appendix 11] A method performed by a hardware resource, comprising: The hardware resources include: A vital database that organizes the past vital data of each person to be confirmed, a schedule database in which schedule data is organized for each person to be confirmed; Equipped with The method comprises: a step of requesting new vital data from a wearable device worn by the person to be confirmed when a busyness information request relating to the busyness of the person to be confirmed is received from a confirmation requester terminal used by the confirmation requester; acquiring the new vital data from the wearable device; A step of predicting the busyness of the confirmation subject based on the new vital data, the vital database, and the schedule database; Including, How to predict busyness. [Appendix 12] A program for causing a hardware resource to execute a process for predicting the busyness of a person to be confirmed, The hardware resources include: A vital database in which past vital data for each person to be confirmed is organized; and a schedule database in which schedule data is organized for each person to be confirmed; Equipped with The program is a process of requesting new vital data from a wearable device worn by the person to be confirmed when a busyness information request relating to the busyness of the person to be confirmed is received from a confirmation requester terminal used by the confirmation requester; A process of acquiring the new vital data from the wearable device; A process of predicting how busy the confirmation subject will be based on the new vital data, the vital database, and the schedule database; causing the hardware resource to execute program.

[0077] The disclosures of the above patent documents are incorporated herein by reference and may be used as the basis or part of the present invention as necessary. Within the framework of the entire disclosure of the present invention (including the claims and drawings), and further based on the basic technical idea, modifications and adjustments of the embodiments and examples are possible. Furthermore, within the framework of the entire disclosure of the present invention, various combinations or selections (or non-selection as necessary) of various disclosed elements (including each element of each claim, each element of each embodiment or example, each element of each drawing, etc.) are possible. In other words, the present invention naturally includes various modifications and corrections that a person skilled in the art would be able to make according to the entire disclosure, including the claims and drawings, and the technical idea. Furthermore, with regard to the numerical values ​​and numerical ranges described in this application, any intermediate value, lower numerical value, and small range are deemed to be described even if not specified. Furthermore, the disclosures of the above cited documents may be used in part or in whole in combination with the descriptions in this document as part of the disclosure of the present invention as necessary, in accordance with the spirit of the present invention, and are deemed to be included (belong) in the disclosures of this application. [Explanation of symbols]

[0078] 1. Busyness Prediction System 10 Busyness Prediction Device 11 Vital Database 12 Schedule Database 13 Receiving section 14 Control section 15 Prediction Department 16 Transmitter 20 Wearable devices 30 Confirmation target terminal 40 Confirmation requester terminal 50 Network 100 Hardware Resources 101 Processor 102 Memory 103 Network Interface 104 Internal Bus

Claims

1. A vital database that organizes the past vital data of each person to be confirmed, a schedule database in which schedule data is organized for each person to be confirmed; a control unit configured to, when receiving a busyness information request related to the busyness of the person to be confirmed from a confirmation requester terminal used by a confirmation requester, request new vital data from a wearable terminal worn by the person to be confirmed and acquire the new vital data from the wearable terminal; A prediction unit configured to predict the busyness of the confirmation subject based on the new vital data, the vital database, and the schedule database; Equipped with the prediction unit creates a busy / slow standard based on the past vital data of the confirmation subject corresponding to the busyness information request in the vital database, calculates a busy / slow degree based on the new vital data and the busy / slow standard, and predicts busyness based on the schedule data and the busy / slow degree. Busyness predictor.

2. The vital data includes biological information of the person to be confirmed, The busy / unbusy criterion is an average value of the biological information in the past vital data.

2. The busyness prediction device according to claim 1.

3. The vital data includes biometric information of the person to be confirmed and date and time information when the biometric information was acquired, The busy / unbusy criterion is an average value of the biological information in the past vital data at a time corresponding to the time of the date and time information in the new vital data.

2. The busyness prediction device according to claim 1.

4. The vital data includes biometric information of the person to be confirmed and meteorological data at the time when the biometric information was acquired, the new vital data is a value obtained by correcting the biological information in the new vital data using the meteorological data, The busy / unbusy criterion is an average value obtained by correcting the biological information in the past vital data using the meteorological data.

2. The busyness prediction device according to claim 1.

5. The busy / unbusy degree is a value obtained by dividing the biological information in the new vital data by the busy / unbusy standard.

5. The busyness prediction device according to claim 2.

6. a transmitter configured to transmit information; the control unit is configured, when receiving the busyness information request from the confirmation requester terminal, to count the number of times the busyness information request has been received for the confirmation target person corresponding to the busyness information request by one and register the number of times the busyness information request has been received in the vital database; The prediction unit is configured to refer to the vital database and determine whether or not a number of times a request for busyness information regarding the confirmation target person has been received has reached a threshold value; the transmission unit is configured to transmit, when the number of times of reception reaches the threshold value, a predetermined message urging the person to consult with an employee other than the person to be confirmed, together with busyness information relating to the busyness, to the confirmation requester terminal.

2. The busyness prediction device according to claim 1.

7. The busyness prediction device according to claim 1 ; A verification subject terminal used by the verification subject; The wearable terminal is attached to the person to be confirmed; and the confirmation requester terminal used by the confirmation requester; Equipped with the wearable device is configured to periodically transmit the vital data corresponding to the past vital data to the busyness prediction device, and to transmit the vital data corresponding to the busyness information request to the busyness prediction device separately from the periodic transmission of the vital data; the confirmation target person terminal is configured to transmit the schedule data input by an operation of the confirmation target person to the busyness prediction device; the confirmation requester terminal is configured to transmit the busyness information request input by an operation of the confirmation requester to the busyness prediction device, and to receive and display busyness information relating to the busyness predicted by the busyness prediction device; Busyness prediction system.

8. A method performed by a hardware resource, comprising: The hardware resources include: A vital database that organizes the past vital data of each person to be confirmed, a schedule database in which schedule data is organized for each person to be confirmed; Equipped with The method comprises: a step of requesting new vital data from a wearable device worn by the person to be confirmed when a busyness information request relating to the busyness of the person to be confirmed is received from a confirmation requester terminal used by the confirmation requester; acquiring the new vital data from the wearable device; A step of predicting the busyness of the confirmation subject based on the new vital data, the vital database, and the schedule database; Including, In the step of predicting, a busy / unbusy standard is created based on the past vital data of the person to be confirmed corresponding to the busyness information request in the vital database, a busy / unbusy level is calculated based on the new vital data and the busy / unbusy standard, and a busyness is predicted based on the schedule data and the busy / unbusy level. How to predict busyness.

9. A program for causing a hardware resource to execute a process for predicting the busyness of a person to be confirmed, The hardware resources include: A vital database in which past vital data for each person to be confirmed is organized; and a schedule database in which schedule data is organized for each person to be confirmed; Equipped with The program is a process of requesting new vital data from a wearable device worn by the person to be confirmed when a busyness information request relating to the busyness of the person to be confirmed is received from a confirmation requester terminal used by the confirmation requester; A process of acquiring the new vital data from the wearable device; A process of predicting how busy the confirmation subject will be based on the new vital data, the vital database, and the schedule database; on the hardware resource; In the prediction process, a busy / unbusy standard is created based on the past vital data of the confirmation subject corresponding to the busyness information request in the vital database, a busy / unbusy level is calculated based on the new vital data and the busy / unbusy standard, and a busyness is predicted based on the schedule data and the busy / unbusy level. program.

Images