Information processing system, information processing method, and program
The information processing system effectively utilizes employee life log information for business management by selecting and managing usage permissions based on business information and consent, ensuring privacy and confidentiality.
Patent Information
- Application Number
- JP2023085212
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-24
- Publication Date
- 2024-12-05
AI Technical Summary
There is a need for technology that allows employees' life log information to be appropriately utilized for business management, considering privacy and confidentiality.
An information processing system that includes a first acquisition unit for detecting life log information, a second acquisition unit for acquiring business information, an information selection unit for selecting usage permission information based on business information, and an information utilization unit for utilizing the selected information, with condition setting and consent management to ensure appropriate use.
Enables the appropriate utilization of employee life log information for business management while protecting privacy and preventing unauthorized access to sensitive data.
Smart Images

Figure 2024168489000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing system, an information processing method, and a program that can be applied to the management of employee operations. [Background technology]
[0002] Patent document 1 discloses a technology that enables users to set the conditions for disclosure / non-disclosure of life log information they wish to make public based on a combination of multiple classification elements, thereby enabling fine-grained control over disclosure / non-disclosure. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2010-266960 A Summary of the Invention [Problem to be solved by the invention]
[0004] There is a demand for technology that enables employees' life log information to be appropriately used for business management.
[0005] In view of the above circumstances, an object of the present invention is to provide an information processing system, an information processing method, and a program that enable the appropriate use of employee life log information for business management. [Means for solving the problem]
[0006] In order to achieve the above object, an information processing system according to an embodiment of the present invention includes a first acquisition unit, a second acquisition unit, an information selection unit, and an information utilization unit. The first acquisition unit acquires life log information detected from an employee. The second acquisition unit acquires business information relating to a business of the employee. The information selection unit selects, based on the acquired business information, from the acquired life log information, usage permission information that is permitted to be used for business-related processing. The information utilization unit utilizes the selected usage permission information.
[0007] The information selection unit may select, as the allowable use information, the life log information detected within an allowable use time period that is set based on working hours of the employee.
[0008] The information selection unit may select, as the permitted use information, the life log information detected within a permitted use area that is set based on the employee's place of work.
[0009] The information processing system may further include a condition setting unit that sets a usage allowance condition for selecting the life log information as the usage allowance information. In this case, the information selection unit may select the usage allowance information from the life log information based on the set usage allowance condition.
[0010] The first acquisition unit may acquire the life log information by type, in which case the condition setting unit may set the usage permission condition for each of the types.
[0011] The information processing system may further include a condition input UI providing unit that provides a condition input UI (User Interface) for inputting the use permission conditions via a predetermined terminal.
[0012] The usage acceptance conditions may include at least one of a condition related to the time the life log information was detected, a condition related to the location where the life log information was detected, a condition related to the type of the life log information, a condition related to whether or not the employee who detected the life log information has given his or her consent, and a condition related to whether or not the employee has authority to use the usage acceptance information.
[0013] The information processing system may further include an information search unit that searches for the life log information based on search conditions inputted through a predetermined terminal. In this case, the information selection unit may select the usage permission information from a search result by the information search unit.
[0014] The information use unit may display the usage permission information on a display device.
[0015] The information use unit may analyze the usage permission information and use a result of the analysis.
[0016] The information processing system may further include an information output restriction unit that restricts output of non-permitted use information that is not selected as the permitted use information from a sensor that detects the life log information from the employee.
[0017] The information processing system may further include a consent input UI providing unit that provides the employee about whom the life log information has been detected with a consent UI for inputting whether or not the employee consents to selecting the life log information as the acceptable usage information.
[0018] When the employee is in a predetermined state, the information selection unit may select the usage allowance information for the detected life log information based on a usage allowance condition corresponding to the predetermined state.
[0019] The information selection unit may select the detected life log information as the permitted use information when the employee is in a state where there is a risk of leaking confidential information.
[0020] The life log information may include at least one of location information of the employee and biometric information of the employee.
[0021] The work information may include at least one of attendance information and information regarding work content.
[0022] The information processing system may further include a history management section that manages history information regarding the use of the usage permission information by the information use section.
[0023] An information processing method according to an embodiment of the present invention is an information processing method executed by a computer, and includes acquiring life log information detected from an employee. Job information relating to the employee's job is obtained. Based on the acquired business information, usage permission information that allows use of the life log information for business-related processing is selected from the acquired life log information. The selected usage permission information is utilized.
[0024] A program according to one embodiment of the present invention causes a computer to execute the following steps. Obtaining life log information detected from the employee. Obtaining job information relating to the employee's job. A step of selecting, based on the acquired business information, from the acquired life log information, usage permission information that is permitted to be used for business-related processing. A step of utilizing the selected usage permission information. Effect of the Invention
[0025] As described above, according to the present invention, it is possible to appropriately use employee life log information for business management. [Brief description of the drawings]
[0026] [Figure 1] 1 is a schematic diagram illustrating an example of the configuration of a business management system according to a first embodiment. [Diagram 2] FIG. 2 is a block diagram illustrating an example of a functional configuration of a server device. [Diagram 3] FIG. 13 is a schematic diagram showing an example of business information stored in a DB (personal master). [Figure 4]FIG. 13 is a schematic diagram showing an example of business information stored in a DB (wearable data). [Diagram 5] FIG. 13 is a schematic diagram showing an example of business information stored in a DB (working hours data). [Figure 6] 4 is a schematic diagram showing an example of life log information acquired by a first acquisition unit; FIG. [Figure 7] 7 is a schematic diagram showing a specific example of the "life log information" shown in FIG. 6. [Figure 8] 13 is a schematic diagram showing another example of life log information acquired by the first acquisition unit. FIG. [Figure 9] 9 is a schematic diagram showing a specific example of the "life log information" shown in FIG. 8. [Figure 10] 13 is a flowchart illustrating an example of a basic operation of the server device. [Figure 11] 11 is a schematic diagram for explaining an example of how usage permission information is displayed on a display device. FIG. [Figure 12] 11 is a schematic diagram for explaining an example of how usage permission information is displayed on a display device. FIG. [Figure 13] 11 is a schematic diagram for explaining an example of how usage permission information is displayed on a display device. FIG. [Figure 14] FIG. 11 is a block diagram showing an example of a functional configuration of a server device according to a second embodiment. [Figure 15] FIG. 13 is a schematic diagram showing an example of "condition data" stored in a DB. [Figure 16] 16 is a schematic diagram showing a specific example of the "condition data" shown in FIG. 15. [Figure 17] FIG. 13 is a schematic diagram showing an example of a condition input GUI for inputting use allowable conditions and non-use allowable conditions. [Figure 18] 13 is another example of a GUI configuration of a personal consent required / not required selection unit for inputting whether personal consent is required or not. [Figure 19] FIG. 13 is a schematic diagram showing an example of a GUI for inputting consent provided to an employee. [Figure 20] 13 is a schematic diagram showing an example of "personal consent data" stored in a DB. FIG. [Figure 21] 10 is a flowchart showing an example of an operation of the server device in selecting use permission information; [Figure 22] 13 is a flowchart showing a specific example of selection of usage permission information. [Diagram 23] 13 is a flowchart showing a specific example of selection of usage permission information according to the third embodiment. [Figure 24] 11 is a schematic diagram showing an example of "confidential information take-out application data" stored in a DB. [Diagram 25] 1 is a schematic diagram showing an example of a functional configuration of a sensor device that detects life log information from an employee. [Figure 26] 11 is a flowchart showing an example of transmission of life log information by a sensor device. [Figure 27] 11 is a schematic diagram for explaining a reference value regarding the use of the usage permission information. FIG. [Figure 28] FIG. 2 is a block diagram showing an example of the hardware configuration of a computer that can be used as a sensor device, a management terminal, and a server device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0027] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[0028] <First embodiment> [Business management system] 1 is a schematic diagram showing an example of the configuration of a business management system according to a first embodiment of the present invention. The business management system 1 is capable of managing business in an organization such as a company. For example, it is possible to execute various procedures related to the business of employees 2 belonging to the organization such as a company, and to manage business information related to the business of each employee 2.
[0029] In the present disclosure, business management includes any management work for any matters related to business. For example, employment management, attendance management, personnel management, budget management, etc. are included in business management related to the present technology. In addition, management work for any matters related to business content is also included in business management. For example, business planning, review of business content, personnel allocation, etc. are also included in business management.
[0030] In this business management system 1, it becomes possible to appropriately use the life log information detected from each employee 2 for business management. This will be explained in detail below.
[0031] As shown in FIG. 1, the business management system 1 includes a sensor device 3, a management terminal 4, a server device 5, and a database (DB) 6.
[0032] The sensor device 3, the management terminal 4, and the server device 5 are connected to each other so as to be able to communicate with each other via a network 7. The network 7 is constructed, for example, by the Internet or a wide area communication line network. Alternatively, any WAN (Wide Area Network) or LAN (Local Area Network) may be used, and the protocol for constructing the network 7 is not limited.
[0033] The sensor device 3, the management terminal 4, and the server device 5 each have hardware necessary for a computer, such as a processor such as a CPU, a GPU, or a DSP, a memory such as a ROM or a RAM, and a storage device such as a HDD (see FIG. 28). The processor loads a program related to the present technology stored in the storage unit or memory into the RAM and executes the program, thereby executing an information processing method related to the present technology (a method for selecting usage allowance information / a method for using usage allowance information).
[0034] The sensor device 3 detects the life log information of the employee 2 and transmits it to the server device 5 via the network 7.
[0035] In the present disclosure, the life log information includes any log information that records various actions and various states of the employee 2 in his / her daily life. For example, the life log information includes log information of the employee 2's location information (behavioral history information) and biometric information.
[0036] For example, the life log information includes information on the current location of employee 2, and more specifically, information on whether the employee is indoors, outdoors, in a meeting, etc. In addition, the life log information includes, for example, the travel distance, travel time, travel speed, number of steps, distance walked, distance run, means of transportation used, time spent using the means of transportation, distance traveled by means of transportation, etc.
[0037] Furthermore, for example, the life log information includes body temperature, blood pressure, pulse rate, heart rate, sweat rate, blood sugar level, water content, body fat percentage, weight, height, muscle mass balance, bone density, respiratory rate, lung capacity, blood test results, MRS test results, urine test, blood alcohol concentration, etc. Furthermore, the life log information also includes information on whether the person is asleep or awake, and what type of sleep state the person is in (REM sleep, non-REM sleep, deep sleep, light sleep, etc.).
[0038] The life log information also includes exercise information regarding the exercise performed by employee 2. For example, information regarding walking, running, traveling by train, driving, etc. can be acquired as life log information. Information regarding posture, such as whether the employee is sitting, standing, leaning forward, looking to the side, or looking up, can also be acquired as life log information.
[0039] In addition, images of employees 2 captured by a camera and audio information such as conversations between employees captured by a microphone are also included in the life log information. In this disclosure, images include both still images and moving images (video).
[0040] Life log information can be detected using various sensors, such as an IMU (Inertial Measurement Unit) sensor, a GPS, various types of biosensors, an image sensor (camera), etc. The detection results (values, etc.) detected by these sensors can themselves be used as life log information. Without being limited to this, it is also possible to generate various types of life log information based on the detection results detected by the sensors.
[0041] For example, the coordinate values of latitude and longitude are detected as location information by a GPS and are used as life log information. Based on the life log information, behavior history information including information on landmarks visited by the employee 2 may be further generated as life log information.
[0042] In addition, detection values of a temperature sensor capable of measuring body temperature, a heart rate sensor capable of measuring heart rate, a sweat sensor capable of measuring the amount of sweat, etc. are detected as life log information. Based on these detection values, the health condition, sleeping condition, etc. of employee 2 may be generated as life log information.
[0043] When the detection result (value, etc.) detected by the sensor is used as the life log information, the time when the life log information was detected is the detection time of the life log information. On the other hand, when various life log information is further generated based on the detection result detected by the sensor, the time when the detection result of the sensor used to generate the life log information was detected is the detection time of the life log information.
[0044] For example, assume that "acceleration" is detected by the IMU sensor at a specific time (date, time A). In this case, if the "acceleration" is used as life log information, the time (date, time A) when the "acceleration" was detected becomes the detection time of the life log information.
[0045] Meanwhile, suppose that life log information "walking" is generated based on "acceleration" detected by the IMU sensor at date, time A. In this case, the detection time of the life log information "walking" is the time when the "acceleration" was detected (date, time A), not the time when the life log information "walking" was generated. In other words, the date, time when employee 2 is "walking" is the detection time of the life log information "walking".
[0046] The sensor device 3 is configured by a computer equipped with a sensor capable of detecting life log information, or is configured by a sensor capable of detecting life log information and capable of communicating via the network 7.
[0047] 1, a smartphone, an HMD (which can also be considered a glasses-type wearable device), a watch-type (wristband-type) wearable device, and a camera are exemplified as the sensor device 3. Of course, the sensor device 3 is not limited to these devices, and various configurations may be adopted to realize the sensor device 3.
[0048] 1, sensor devices 3a to 3c are provided for employees 2a to 2c, respectively. However, the present invention is not limited to this, and images of multiple employees 2 may be captured by a camera installed in a specific space, and life log information of each employee 2 may be obtained based on the captured images.
[0049] In the present disclosure, acquisition of information, etc. includes both receiving the information from another device and generating the information by performing analysis, extraction, estimation, etc. That is, in the present disclosure, acquisition of life log information includes both receiving life log information detected by the sensor device 3, for example, and generating life log information on the basis of the detection result of the sensor device 3.
[0050] The life log information may be generated by the sensor device 3 based on the detection result detected by the sensor device 3. Furthermore, the server device 5 may further generate life log information based on the detection result received from the sensor device 3, the life log information generated by the sensor device 3, etc.
[0051] Any technology (algorithm, etc.) may be used to acquire life log information, etc. For example, any machine learning algorithm using a DNN (Deep Neural Network), an RNN (Recurrent Neural Network), a CNN (Convolutional Neural Network), etc. may be used. For example, by using an AI (artificial intelligence) that performs deep learning, it becomes possible to execute each process with high accuracy.
[0052] For example, by inputting sensor detection results, etc. into a trained learning model that has undergone machine learning to output life log information, it is possible to obtain life log information from the learning model.
[0053] As a learning method for a learning model, for example, the backpropagation method is used. The backpropagation method is a learning method that is commonly used for training neural networks. A neural network is a model that originally imitates the neural circuits of the human brain, and is a model with a layer structure consisting of three types of layers: an input layer, an intermediate layer (hidden layer), and an output layer.
[0054] Neural networks with many hidden layers are called deep neural networks, and the deep learning technology used to train them is known as a model that can learn complex patterns hidden in large amounts of data. Backpropagation is one such learning method, and is often used, for example, in training CNNs, which are used to recognize images and videos.
[0055] In addition, as a hardware structure for realizing such machine learning, a neurochip / neuromorphic chip incorporating the concept of neural networks can be used.
[0056] The algorithm for learning the learning model is not limited, and any machine learning algorithm may be used. For example, machine learning algorithms include supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, inverse reinforcement learning, active learning, transfer learning, etc. In addition, machine learning models such as HMM (Hidden Markov Model) and SVM (Support Vector Machine) may be used.
[0057] A learning block (learning unit) for learning the learning model may be configured in the sensor device 3 or the server device 5. Alternatively, the learning block (learning unit) may be configured in a computer different from the sensor device 3 or the server device 5, and the learned learning model after learning is executed may be loaded into the sensor device 3 or the server device 5. Besides, the specific configuration of the learning model and the learning block (learning unit) for learning the learning model is not limited.
[0058] The application of the machine learning algorithm may be performed for any process in the present disclosure. In other words, a process using machine learning may be performed for any process described in the present disclosure.
[0059] Furthermore, the method for extracting life log information from the captured image of employee 2 is not limited, and any technology (algorithm) may be used. For example, any image recognition technology such as matching processing using a model image of an object, edge detection, projective transformation, etc. may be used. Skeleton estimation (bone estimation) may also be used. Furthermore, an externally constructed library having existing functions such as image processing and machine learning may be used.
[0060] Any machine learning algorithm may be used to extract lifelog information from the captured images. For example, semantic segmentation may be performed on the image information to determine the type of object for each pixel in the image.
[0061] The management terminal 4 is a terminal used by an administrator 8. The administrator 8 is an example of an employee having greater authority than the employees 2, and is not particularly limited to a specific position or the like.
[0062] The server device 5 is a device for providing a business management service. Various processes related to business management are executed by the server device 5. For example, various processes related to management of arbitrary matters related to employment management, attendance management, personnel management, budget management, and business content are executed.
[0063] DB6 stores any information related to work (business information). For example, employee information such as the name, sex, address, and phone number of employees, as well as work information and attendance information related to the salary paid to each employee, clock-in / clock-out times, holidays, overtime, etc. Any other information related to personnel, budgets, work content, etc. is stored as business information.
[0064] 1, DB 6 is configured by a storage device or the like separate from server device 5, and is connected to server device 5. The present invention is not limited to this configuration, and DB 6 may be configured by a storage unit (see FIG. 28) of server device 5. Also, DB 6 may be constructed on network 7, and a configuration may be adopted in which DB 6 is accessible via network 7.
[0065] 1, the server device 5 is illustrated as a computer having one housing. Of course, the configuration is not limited to this, and various business-related processes may be performed by multiple server devices having various functions working together.
[0066] 1 also shows three employees 2a to 2c and one manager 8. Of course, there is no limit to the number of employees 2 and managers 8 to which this work management system 1 can be applied. This work management system 1 can be applied to a larger number of employees 2 and managers 8.
[0067] [Server device functional configuration example] Fig. 2 is a block diagram showing an example of a functional configuration of the server device 5. In this embodiment, as shown in Fig. 2, a processor of the server device 5 executes a predetermined program to configure functional blocks including a first acquisition unit 10, a second acquisition unit 11, an information selection unit 12, an information search unit 13, and an information utilization unit 14. Of course, dedicated hardware such as an IC (integrated circuit) may be used to realize the functional blocks.
[0068] The program is installed in the server device 5 via, for example, various recording media. Alternatively, the program may be installed via the Internet or the like. There is no limitation on the type of recording medium on which the program is recorded, and any computer-readable recording medium may be used. For example, any computer-readable non-transitory storage medium may be used.
[0069] The first acquisition unit 10 acquires life log information of the employee 2. The first acquisition unit 10 receives the life log information detected by the sensor device 3, receives the life log information generated by the sensor device 3, generates the life log information based on the detection result detected by the sensor device 3, and the like.
[0070] The life log information acquired by the first acquisition unit 10 is stored in the DB 6. For example, the life log information is stored by type based on an employee ID ("personal code") assigned to each employee 2. The type of life log information can also be said to be an item of the life log information.
[0071] The second acquisition unit 11 acquires business information related to the business of the employee 2. In this embodiment, the business information for each employee 2 stored in the DB 6 is read out and acquired as appropriate.
[0072] The information selection unit 12 selects, based on the business information acquired by the second acquisition unit 11, from the life log information acquired by the first acquisition unit 10, usage allowable information that is permitted to be used for business-related processing.
[0073] In other words, the information selection unit 12 determines whether various types of life log information acquired for each employee 2 is information that may be used for business-related processing (permitted use information) or information that must not be used for business-related processing (non-permitted use information), and selects the information that may be used for business-related processing (permitted use information).
[0074] The information search unit 13 searches for life log information based on search conditions input via a specific terminal. In this embodiment, the "specific terminal" is described by taking the management terminal 4 used by the manager 8 as an example.
[0075] For example, the search conditions include the specification of the employee 2 that the manager 8 wishes to view, the type of life log information that the manager wishes to view, the period during which the life log information was detected, etc. The information search unit 13 searches for and collects life log information that satisfies the search conditions by referring to the "personal code" of the employee 2 (see FIG. 3, etc.), the "type" and "date" of the life log information (see FIG. 6, etc.), etc.
[0076] The information utilization unit 14 utilizes the usage allowance information selected by the information selection unit 12. For example, the information utilization unit 14 displays the usage allowance information on the display device of the management terminal 4, analyzes the usage allowance information, and utilizes the analysis results in creating a business plan, etc. In addition, the usage allowance information is utilized for various other business-related processes.
[0077] 3 to 5 are schematic diagrams showing an example of business information stored in DB 6. As shown in Fig. 3, in this embodiment, "personal master" is stored in DB 6. The "personal master" is created for each employee 2 (including the manager 8). The "personal master" is data included in the employee information relating to each employee.
[0078] As shown in FIG. 3, the “Personal Master” includes the following information: "Personal code": an ID that can identify employee 2. For example, it is composed of a 10-digit number. Of course, any other form of data may be used as the "personal code". “Name”…Employee 2’s name. “Gender”…Employee 2’s gender. "Email address": An email address used during work. Often distributed to employees 2 by companies or other organizations. "Workplace name": The name of the place of work of employee 2. For example, XX branch office, XX factory, etc. "Workplace coordinates": Location information of the workplace. In this embodiment, the same latitude / longitude as the GPS coordinates are used. Note that information indicating a predetermined range that includes the entire premises of the workplace may also be used. For example, the coordinate values of four points may be used as "workplace coordinates." The workplace may also be referred to as the place of work.
[0079] As shown in Fig. 4, "wearable data" is stored as business information. In this embodiment, a wearable device is attached to each employee 2 as the sensor device 3 shown in Fig. 1. The "wearable data" is data of the wearable device attached to each employee 2.
[0080] As shown in FIG. 4, “Wearable Data” includes the following information: “Personal Code”: The personal code of employee 2 who will be wearing the wearable device. “Name”: Name of the wearable device. "Serial No.": The serial number of the wearable device.
[0081] 4, it is possible to determine which employee 2 the life log information (including the detection result data) transmitted from the wearable device pertains to. Note that information that can determine the type of life log information transmitted from the wearable device may be stored in the "wearable data."
[0082] The "personal master" and "wearable data" shown in Figures 3 and 4 can be considered basic data for implementing this technology.
[0083] 5, "working hours data" is stored as business information. The "working hours data" is created for each employee 2 (including the manager 8) and is included in the employee information for each employee.
[0084] As shown in FIG. 5, the "Working Hours Data" includes the following information: "Personal Code" "Date": If the data is past, the date of work. If the data is for planned future work, the planned date. "Scheduled start time of work": The time you plan to start work. "Scheduled end time of work": The time you plan to end your work. "Break 1 start time": The time when the first break starts. "Break 1 end time": The time the first break ends. "Break 2 start time": The time when the second break starts. "End time of break 2": The time the second break ends. "Attendance time (actual)": The actual time the employee arrived at work. If the data is for a future work schedule, leave it blank. "Time of leaving work (actual)": The actual time of leaving work. If the data is for a future work schedule, leave it blank.
[0085] In addition, any other information may be stored as business information relating to the employee's business.
[0086] 6 is a schematic diagram showing an example of the life log information acquired by the first acquisition unit 10. The data of the life log information acquired by the first acquisition unit 10 is also stored in the DB6.
[0087] 6 is an example of "life log information" related to biometric information and location information of an employee. The "life log information" includes the following information: "Personal Code" “Date”…The date the life log information was detected. "Time": The time when the life log information was detected. “Type”: Type of life log information. "Value": Data representing the content of the life log information. In some cases, the detection result detected by the sensor device 3 is stored, and in other cases, data generated based on the detection result of the sensor device 3 is stored.
[0088] FIG. 7 is a schematic diagram showing a specific example of the "life log information" related to the biometric information and location information of the employee shown in FIG.
[0089] In Figure 7, the "life log information" for an employee named "Taro Yamada" is shown as an example. Various pieces of life log information were detected at the following times on "Date" = "2022 / 6 / 20".
[0090] "Time" = "6:07:11" "Type" = "Sleep" "Value" = "Wake up (Awake)" "Time" = "6:08:11" "Type" = "Acceleration" "Value" = "-30,5,110" "Time" = "6:09:28" "Type" = "GPS" "Value" = "35.6566376,139,7459452" "Time" = "6:10:41" "Type" = "Weight" "Value" = "76.3" "Time" = "6:20:41" "Type" = "Acceleration" "Value" = "87,8,30" "Time" = "6:31:52" "Type" = "GPS" "Value" = "35.681111,139,766667" "Time" = "7:01:22" "Type" = "Heart Rate" "Value" = "75"
[0091] "Sleep" can be detected by a sleep sensor. "Acceleration" can be detected by an IMU sensor. "GPS" can be detected by a GPS. "Weight" can be detected by a weight scale, although devices other than wearable devices are often used. "Heart rate" can be detected by a heart rate sensor.
[0092] Fig. 8 is a schematic diagram showing another example of the life log information acquired by the first acquisition unit 10. The example shown in Fig. 8 is an example of "life log information" related to the sleep state information of the employee 2. The "life log information" includes the following information.
[0093] "Personal Code" "Sleep state": For example, it is possible to classify the sleep state into wakefulness (awake), REM sleep, non-REM sleep, deep sleep, and light sleep. The method of classifying the sleep state is not limited, and any setting can be adopted. "State start date and time": The date and time when each sleep state started. "State end date and time": The date and time each sleep state ended.
[0094] FIG. 9 is a schematic diagram showing a specific example of the "life log information" related to the sleep state information of the employee shown in FIG.
[0095] 9 shows an example of "life log information" related to an employee with the name "Yamada Taro." Also, in FIG. 9, a case where "name" is stored instead of "personal code" is shown so that it can be intuitively understood that this is "life log information" for "Yamada Taro." In this way, "name" may be stored instead of "personal code."
[0096] The following changes in "sleep state" are acquired as "life log information." "Sleep state" = "Light" "State start date and time" = "December 24, 2022, 22:05" "State end date and time" = "December 24, 2022, 22:50" "Sleep state" = "Awake (awake)" "State start date and time" = "December 24, 2022, 10:50 p.m." "State end date and time" = "December 24, 2022, 11:05 p.m." "Sleep state" = "REM" "State start date and time" = "December 24, 2022, 11:05 p.m." "State end date and time" = "December 24, 2022, 11:46 p.m." "Sleep state" = "Deep" "State start date and time" = "December 24, 2022 23:46" "State end date and time" = "December 24, 2022 3:25" "Sleep state" = "Light" "State start date and time" = "December 24, 2022, 3:25" "State end date and time" = "December 24, 2022, 5:15"
[0097] [Basic operation of the server device] 10 is a flowchart showing an example of a basic operation of the server device 5. The first acquisition unit 10 acquires life log information of the employee 2. Furthermore, the second acquisition unit 11 acquires business information of the employee 2 (step 101).
[0098] For example, the sensor device 3 periodically detects life log information of the employee 2 at a predetermined frame rate. Then, the detected life log information is transmitted to the server device 5 via the network 7. The first acquisition unit 10 receives the life log information transmitted from the sensor device 3.
[0099] Alternatively, a trigger for the sensor device 3 to transmit the life log information may be set as appropriate. For example, at a predetermined time, the sensor device 3 transmits untransmitted life log information detected up to that time. Alternatively, when there is a request from the server device 5, the sensor device 3 transmits the life log information detected up to that time. Any other setting may be adopted.
[0100] The second acquisition unit 11 typically acquires, from the DB 6, business information corresponding to the life log information acquired by the first acquisition unit 10. For example, by referring to a "personal code" associated with the life log information, the second acquisition unit 11 acquires "personal master," "wearable data," "working hours data," and the like for the same "personal code."
[0101] For example, search conditions are input via the management terminal 4 with respect to the employee 2, the type of life log information, etc. The information searching unit 13 searches for life log information that matches the search conditions from the life log information acquired by the first acquiring unit 10. The second acquiring unit 11 acquires business information corresponding to the searched life log information.
[0102] Of course, the present invention is not limited to this, and an automatic analysis application may be started, and life log information to be used for analysis may be selected from the life log information acquired by the first acquisition unit 10. The second acquisition unit 11 acquires business information corresponding to the searched life log information.
[0103] The information selection unit 12 selects, based on the business information, from the life log information, permitted use information that is permitted to be used for business-related processing (step 102).
[0104] For example, the information selection unit 12 selects, as the permitted use information, the life log information detected within the permitted use time set based on the working hours (working hours) of the employee 2. In this case, the life log information detected outside the permitted use time is not selected as the permitted use information, but becomes the non-permitted use information.
[0105] As the allowable use time set based on working hours, for example, working hours are used as they are. In this case, the life log information detected during working hours is selected as the allowable use information. Moreover, the life log information detected outside working hours is selected as the non-allowable use information.
[0106] Without being limited thereto, a time range different from the working hours may be set as the permitted use time. For example, a time a certain time before the start time of the working hours may be set as the start time of the permitted use time. Also, a time a certain time after the end time of the working hours may be set as the end time of the permitted use time.
[0107] For example, if the employee 2 is a bus driver or an airplane pilot, it may be important to know the sleep state, alcohol level, etc., before working hours. In such a case, life log information detected from several hours or one day before working hours may be selected as the permitted use information.
[0108] In addition, if the employee 2 is a diver or the like, it may be important to know the health condition, etc., until a predetermined time after the end of working hours. In such a case, the life log information detected until the predetermined time after the end of working hours may be selected as the permitted use information.
[0109] In addition, if it is important to know the sleep state during breaks, the allowable use time may be set to include breaks. In this way, it is possible to flexibly set the allowable use time based on working hours, based on the work information such as the example shown in Figure 5.
[0110] In addition, in the "Working Hours Data" shown in Figure 5, if the "Actual Arrival Time" and "Actual Leave Time" are blank, it is possible to determine the working hours of Employee 2 by referring to the "Scheduled Start Time of Work" and "Scheduled End Time of Work."
[0111] For example, when performing a selection process of allowable use information for life log information detected in real time on the day, if the timing is before the "time to arrive at work (actual)" is stored, it is possible to set the allowable use time by treating the time from the "scheduled start time of work" to the "scheduled end time of work" as the working time of employee 2. If the timing is after the "time to arrive at work (actual)" is stored but before the "time to leave work (actual)" is stored, it is possible to set the allowable use time by treating the time from the "time to arrive at work (actual)" to the "scheduled end time of work" as the working time of employee 2.
[0112] When performing the selection process of acceptable usage information for life log information of a past date, it is possible to set the acceptable usage time based on the time from the "actual start time" to the "actual finish time", i.e., the confirmed working hours.
[0113] In addition, when Employee 2 clocks in and out by punching a time card, there may be a time lag of, for example, 15 minutes before the information on the clock-in time and the clock-out time are stored in "Clock-in time (actual)" and "Clock-out time (actual)". Even in such a case, it is possible to define Employee 2's working hours by appropriately referring to the "Scheduled work start time" and "Scheduled work end time".
[0114] Also, for example, the life log information detected within a permitted use area set based on the employee's place of work is selected as the permitted use information by the information selection unit 12. Therefore, the life log information detected outside the permitted use area is not selected as the permitted use information, but becomes non-permitted use information.
[0115] As the permitted use area set based on the workplace, for example, the range of the workplace (such as the premises of the workplace) is adopted as it is. In this case, the life log information detected within the workplace is selected as the permitted use information. Furthermore, the life log information detected outside the workplace is selected as the non-permitted use information.
[0116] The permitted use area is not limited to this, and may be set to a range different from the workplace. For example, a larger area including the workplace may be set as the permitted use area. A predetermined smaller area within the workplace may be set as the permitted use area.
[0117] For example, if employee 2 is a salesman, a wide area including his / her place of work (workplace) and his / her sales destinations may be set as the permitted usage area. Also, if employee 2 is a researcher and works in a research building on the premises, only the area of that research building may be set as the permitted usage area.
[0118] In this way, it becomes possible to flexibly set permitted use areas based on the workplace, based on the business information such as the example shown in FIG.
[0119] In addition, any setting can be made as the selection of the usage permission information based on the work information.
[0120] The information usage unit 14 uses the selected usage allowance information (step 103). For example, the usage allowance information may be displayed on a display device. In this embodiment, the usage allowance information of the life log information that the administrator 8 wishes to view is displayed on the display (display device) of the management terminal 4.
[0121] Furthermore, the information utilization unit 14 analyzes the allowable use information and utilizes the analysis results. For example, an automatic analysis application may be started and the analysis results of the allowable use information may be utilized. For example, the outside action history information (allowable use information) of "Yamada Taro" in the sales department, who has an extremely good record, may be analyzed and shared as reference information for improving sales performance. In addition, the analysis results of the allowable use information may be utilized for various business-related processes such as business planning, health management, personnel management, and salary management.
[0122] Fig. 11 to Fig. 13 are schematic diagrams for explaining an example of displaying usage permission information on a display device. Here, an example will be explained in which the manager 8 shown in Fig. 1 displays life log information of an employee 3 on the display of the management terminal 4. Note that in Fig. 11 to Fig. 13, this business management system 1 is given the name of an integrated business management system.
[0123] For example, the administrator 8 uses the management terminal 4 to display a login screen for logging in to the business management system 1. The administrator 8 then enters his / her personal code and password, etc. to log in. This login operation enables the server device 5 to grasp information about the administrator 8 who uses the management terminal 4, the viewing authority of the life log information, etc.
[0124] In this embodiment, as shown in Fig. 11, on the screen after login, selection buttons for each of the menus "TOP", "Common", "Work", "Entry", "Salary" and "Personnel" are displayed, and the manager 8 selects the "Work" button 16. Then, by selecting the "Life log" button from the "Work" menu (not shown), the life log information display screen 17 shown in Fig. 11 is displayed.
[0125] 11 includes a "Search" button 18, an "Action History" button 19, a "Health" button 20, and a "Sleep" button 21. The "Search" button 18 is used when entering search conditions for life log information. When the "Search" button 18 is selected, a UI (User Interface) for entering search conditions is provided.
[0126] Specifically, a predetermined GUI (Graphical User Interface) for inputting search conditions is displayed. However, without being limited to this, a UI (audio UI) may be output by voice. In other words, it may be possible to search for life log information in a conversational format.
[0127] In the present disclosure, providing a predetermined UI includes displaying a GUI and outputting a voice UI. Of course, these may be performed simultaneously.
[0128] In the example shown in Figure 11, the life log information regarding the "behavioral history" of "Personal Code" = "xxxxxxxxxx" and "Name" = "Yamada Taro" on "2022 / 6 / 20" is specified as the object to be viewed.
[0129] Therefore, the "Behavioral History" button 19 is displayed in an active state, and the other buttons, "Health" 20 and "Sleep" 21, are displayed in an inactive state. By selecting the "Health" button 20, it is possible to specify life log information relating to Yamada Taro's health as the display subject. By selecting the "Sleep" button 21, it is possible to specify life log information relating to Yamada Taro's sleep as the display subject.
[0130] In this example, the time between the start and end of Taro Yamada's working hours, excluding break times, is set as the permitted use time. In other words, the location information (GPS coordinate values) detected during working hours excluding break times is selected as the permitted use information.
[0131] The manager 8 moves the slider 22 from the left end to the right to move it to a point between the start time of the working hours and "10:45". A map of the area where Yamada Taro was located is displayed in the life log display area 23. Then, on the map, GPS points detected from the start time of the working hours to "10:45", a movement route, and a point connection line connecting the GPS points are displayed. The GPS points, the movement route, and the point connection line are displayed so as to change in response to the movement of the slider 22. That is, each piece of information up to the position of the time (the acquisition time in the figure) corresponding to the position of the slider 22 is displayed on the map. The manager 8 can fully grasp the behavior history of Yamada Taro from the start time of the working hours to "10:45".
[0132] 12, the slider 22 moves to the point of "12:00", which is the start time of the break time. Since the break time is not included in the allowable use time, the location information (GPS coordinate value) detected at "12:00" is not selected as the allowable use information. Therefore, the map, GPS points, travel route, and point connecting lines are deleted from the life log display area 23. Also, a message is displayed in the life log display area 23 indicating that life log information cannot be displayed because it is outside working hours.
[0133] When the slider 22 passes the end time of the break, the detected location information (GPS coordinate value) is selected as the permitted use information. Then, the map, GPS points, the movement route, and the point connection line are displayed in the life log display area 23. At that time, the information corresponding to the break is not displayed, so a route that seems to be interrupted in the middle is displayed.
[0134] The display of "Data Available" shown in Fig. 11 corresponds to the fact that Yamada Taro's location information (GPS coordinate values) has been selected as the permitted information for use. The display of "No Data" shown in Fig. 12 corresponds to the fact that Yamada Taro's location information (GPS coordinate values) has not been selected as the permitted information for use. This display enables the administrator 8 to understand the reasons why a map or the like is or is not displayed. Of course, information such as "Information for this time period cannot be viewed" may also be displayed.
[0135] In the example shown in FIG. 13, the "health" button 20 is selected, and Yamada Taro's health-related log life information is specified as the display target. As shown in FIG. 13, it is possible to refer to four pieces of life log information: "pulse rate," "respiratory rate," "blood pressure," and "body temperature." In FIG. 13, the life log information of the pulse rate on "2022 / 6 / 20" is displayed. Specifically, a graph with the horizontal axis representing time and the vertical axis representing pulse rate is displayed in the life log display area 23.
[0136] In this example, the allowable use time is the working hours from 8:00 to 18:00, excluding the break time from 12:00 to 13:00. The pulse rate detected within the allowable use time is selected as allowable use information. The pulse rate detected during the break time from 12:00 to 13:00 is not selected as allowable use information, but becomes non-allowable use information.
[0137] 13, in the pulse rate graph displayed in the life log display area 23, no pulse rate data is displayed during break times from "12:00" to "13:00" and the graph is blank. This allows the manager 8 to fully grasp Yamada Taro's pulse rate during working hours excluding break times.
[0138] As described above, in the business management system 1 according to this embodiment, allowable use information that is permitted to be used for business-related processing is selected from the life log information of the employee 2 based on the business information of the employee 2. The selected allowable use information is then used. This makes it possible to appropriately use the life log information of the employee 2 for business management.
[0139] In order to improve work efficiency and manage attendance, it is considered to be an effective method to keep track of employees' whereabouts and health status using company-issued smartphones and wearable devices. On the other hand, if employees' whereabouts and health status are kept track of at all times without time or geographical restrictions, the stress of being monitored around the clock can lower employees' motivation and pose problems from the perspective of privacy.
[0140] In the business management system 1 according to this embodiment, the usage permission information is appropriately selected from the life log information detected from the employee based on the business information of the employee 2. This makes it possible to realize a system that allows a company or the like to appropriately acquire and use the life log information of the employee 2 while appropriately protecting the privacy of the employee 2, for example.
[0141] For example, by applying the present invention, it is possible to execute the following operations 1 to 3 in cooperation with each other. (Operation 1) The employee 2 life log information is transmitted to the server device 5 and stored in the DB 6 . (Operation 2) The attendance information of employee 2 is collected and stored using a time recorder or the like. (Operation 3) The administrator 8 starts the application that provides this business management service using the management terminal 4, and searches the server device 5 for the life log information that the administrator wishes to view. By selecting the usage permission information from the search results, the range is appropriately limited and displayed on the display of the management terminal 4.
[0142] In this embodiment, the business management system 1 corresponds to an embodiment of an information processing system according to the present invention.
[0143] <Second embodiment> A task management system according to a second embodiment of the present invention will be described. In the following description, the description of the same configurations and operations as those of the task management system 1 described in the above embodiment will be omitted or simplified.
[0144] 14 is a block diagram showing an example of a functional configuration of the server device 25 according to this embodiment. In this embodiment, the processor of the server device 25 executes a predetermined program to configure a condition setting unit 26, a UI providing unit 27, and a history management unit 28 as functional blocks.
[0145] The condition setting unit 26 sets the usage allowance conditions for selecting the life log information as the usage allowance information. The usage allowance conditions can also be called usage allowance rules. In addition, the disclosure of the usage allowance information, such as the display of the usage allowance information, can be called the usage allowance conditions as disclosure conditions or disclosure rules, as a representative example of the usage allowance information.
[0146] The condition setting unit 26 also sets non-use allowable conditions for selecting the life log information as non-use allowable information. The non-use allowable conditions can also be called non-use allowable rules, non-disclosure conditions, non-disclosure rules, or the like.
[0147] The UI providing unit 27 provides a condition input UI for inputting the use permission conditions via a predetermined terminal, and also provides a consent UI for inputting whether or not the employee 2 whose life log information has been detected consents to selecting the life log information as use permission information.
[0148] The UI providing unit 27 functions as an embodiment of a condition input UI providing unit according to the present invention, and also functions as an consent input UI providing unit according to the present invention.
[0149] The history management unit 28 manages history information regarding the use of the permitted use information by the information use unit 14. For example, information such as when, what kind of life log information (permissible use information) was used, and for what processing is stored as history information in the DB 6. In addition, various information regarding the used life log information (permissible use information), such as the target employee 2, the time of detection, the viewing range, etc., is stored as history information in the DB 6.
[0150] By referring to the history information, each employee 2 can check information such as what processing his / her life log information was used for. Also, it is possible to check his / her own life log information.
[0151] FIG. 15 is a schematic diagram showing an example of the “condition data” stored in the DB 6. As shown in FIG.
[0152] As shown in FIG. 15, the "condition data" includes the following information: "Condition name": the name of the condition. This can be input by the person who creates the usage permission conditions, such as the administrator 8.
[0153] "Allowed / Not Allowed": Information indicating whether the "Condition Data" is data of an acceptable use condition or a non-acceptable use condition. In other words, if this information is "Allowed", the above-mentioned "Condition Name" is the name of an acceptable use condition. On the other hand, if this information is "Not Allowed", the above-mentioned "Condition Name" is the name of a non-acceptable use condition.
[0154] "Condition subject time": the time that is subject to this condition. If the "condition data" is data on the acceptable use conditions, this information becomes the acceptable use time during which the detected life log information is selected as the acceptable use information. On the other hand, if the "condition data" is data on the non-acceptable use conditions, this information becomes the non-acceptable non-use time during which the detected life log information is selected as the non-acceptable non-use information.
[0155] "Condition subject area": Area that is subject to this condition. If the "condition data" is data of permissible use conditions, this information becomes a permissible use area in which the detected life log information is selected as permissible use information. On the other hand, if the "condition data" is data of non-permissible use conditions, this information becomes a non-permissible use area in which the detected life log information is selected as non-permissible use information.
[0156] "Life log information type": the type of life log information to which this condition applies. If the "condition data" is data on acceptable use conditions, this is the type of life log information that is subject to the acceptable use conditions. On the other hand, if the "condition data" is data on non-acceptable use conditions, this is the type of life log information that is subject to the non-acceptable use conditions.
[0157] By appropriately selecting the type of life log information, the condition setting unit 26 can set the allowable use conditions and the allowable non-use conditions for each type.
[0158] "Personal consent required / not required": Information on whether or not the consent of the employee whose life log information was detected is required when selecting the life log information as permitted use information or non-permitted use information. Note that if the "Condition data" is data on non-permitted use conditions, the information in the "Personal consent required / not required" field does not need to be used. In that case, the information in that field will be left blank.
[0159] "Viewing authority": Authority required to view life log information selected as permitted use information or non-permitted use information. Note that if the "condition data" is data of non-permitted use conditions, the information in the "viewing authority" item does not need to be used. In that case, the information in that item will be left blank.
[0160] When "Allowed / Not Allowed" in FIG. 15 is "Allowed", each piece of information related to FIG. 15 becomes a condition included in the usage allowance conditions. "Condition target time" is one embodiment of a condition related to the time when life log information according to the present invention was detected. "Condition target area" is one embodiment of a condition related to the location where life log information according to the present invention was detected. "Life log information type" is one embodiment of a condition related to the type of life log information according to the present invention. "Personal consent required / not required" is one embodiment of a condition related to the presence or absence of consent from the employee whose life log information according to the present invention was detected. "Viewing authority" is one embodiment of a condition related to the presence or absence of use authority for usage allowance information.
[0161] When "Allowed / Not Allowed" shown in FIG. 15 is "Not Allowed," each piece of information related to FIG. 15 becomes a condition included in the non-use allowance conditions. "Condition target time" is one embodiment of a condition related to the time at which life log information according to the present invention was detected. "Condition target area" is one embodiment of a condition related to the location at which life log information according to the present invention was detected. "Life log information type" is one embodiment of a condition related to the type of life log information according to the present invention.
[0162] FIG. 16 is a schematic diagram showing a specific example of the "condition data" shown in FIG.
[0163] In the example shown in Fig. 16, data on acceptable conditions of use named "health condition check during work" is shown. The information on each item is as follows: "Acceptable / Not Acceptable" = "Acceptable" "Condition target time" = "Working hours" "Condition target area" = "Head office" "Individual's consent" = "Unnecessary" "Life log information type" = "body temperature, heart rate" "Viewing authority" = "Self / HR"
[0164] 16, data on the usage permission conditions named "operation availability status check" is shown. The information for each item is as follows: "Acceptable / Not Acceptable" = "Acceptable" "Condition target time" = "0:00~24:00" "Condition target area" = "All areas" "Individual's consent" = "Required" "Life log information type" = "Sleep time, alcohol value" "Viewing authority" = "Self / Administrator"
[0165] 16 shows an example of non-use allowable condition data named "health condition check outside of work hours." The information for each item is as follows: "Acceptable / Not Acceptable" = "Not Acceptable" "Condition target time" = "Outside working hours" "Condition target area" = "All areas" "Individual's consent" = "Required" "Life log information type" = "Sleep time, alcohol value" "Viewing authority" = "Self / Health manager"
[0166] Fig. 17 is a schematic diagram showing an example of a condition input GUI for inputting a use allowable condition and a non-use allowable condition. The condition input GUI shown in Fig. 17 includes a condition name input section 30, an allowable / non-allowable selection section 31, a condition target time input section 32, a condition target area input section 33, a life log information type input section 34, a user consent required / not required selection section 35, and a viewing authority input section 36.
[0167] In the condition name input section 30, the administrator 8 can freely input text to input a condition name.
[0168] The allow / non-allow selection unit 31 is provided with an allow button and a non-allow button, and by selecting either button, it is possible to select whether to input the allowable use conditions or the non-allowable use conditions. Of course, this is not limited to such a configuration, and any configuration that allows the selection between "allow" and "non-allow" may be adopted.
[0169] The condition target time input section 32 has three options prepared: "During working hours", "Outside working hours", and "Specified time". The manager can input the condition target time by selecting a radio button and inputting the time as appropriate. Of course, the configuration is not limited to this, and any configuration that allows input of the condition target time may be adopted.
[0170] In the condition target area input section 33, various area designations including "all areas" can be selected using a pull-down menu. Of course, this is not limited to such a configuration, and any configuration that allows input of the condition target area may be adopted.
[0171] In the life log information type input unit 34, selectable types of life log information are displayed in a list with check boxes. The administrator 8 can input the types of life log information to which this condition applies by appropriately checking the check boxes. Of course, this is not limited to such a configuration, and any configuration that allows input of the types of life log information may be adopted.
[0172] The consent required / not required selection unit 35 provides options of "required" and "not required." The administrator can select whether the consent of the individual is required or not by appropriately selecting a radio button. Of course, the present invention is not limited to this configuration, and any configuration that allows the administrator to select whether the consent of the individual is required or not may be adopted.
[0173] The viewing authority input unit 36 has five options available: "Self", "Administrator", "Human Resources", "Health Manager", and "Designated". The administrator can input viewing authority by appropriately selecting a radio button and inputting the target person (target authority). Of course, this is not limited to such a configuration, and any configuration capable of inputting viewing authority may be adopted.
[0174] FIG. 18 is another example of the GUI configuration of the consent required / not required selection unit 35 for inputting whether the consent of the individual is required or not required. In the example shown in FIG. 18, the options of "required" and "not required" for the individual's consent are provided for each "condition name." The administrator 8 can easily select whether the consent of the individual is required or not required for each condition name, achieving high operability. In addition, it becomes possible to check in a list whether the consent of the individual is "required" or "not required" for each acceptable use condition, making it easy to understand the current condition settings.
[0175] 19 is a schematic diagram showing an example of a consent input GUI provided to the employee 2. The consent input GUI shown in FIG. 19 includes a condition name display section 39, a consent / non-consent selection section 40, and a details button 41.
[0176] The condition display section 39 displays a list of condition aspects of the usage permission conditions in which the condition that the user's consent is required is set.
[0177] The consent / non-conformance selection unit 40 is provided with a consent button and a non-conformance button, and it is possible to select consent or non-conformance by selecting either button. When the consent button is selected, consent is input as the person's intention information. When the non-conformance button is selected, non-conformance is input as the person's intention information. Of course, this is not limited to a configuration, and any configuration that allows the selection between "consent" and "non-conformance" may be adopted.
[0178] When the Details button 41 is selected, detailed content of each of the usage conditions is displayed. The employee 2 can input consent or non-consent while checking the detailed information of the usage conditions.
[0179] Fig. 20 is a schematic diagram showing an example of the "personal consent data" stored in the DB 6. As shown in Fig. 20, the "personal consent data" includes the following information. "Personal Code": The personal code of the employee who has agreed to the terms and conditions of use. "Name of acceptable use conditions": The name of the acceptable use conditions that have been accepted. "Date and time of acceptance": The date and time when the acceptance was entered.
[0180] When the person inputs consent via a consent GUI as shown in Fig. 19, "personal consent data" as shown in Fig. 20 is generated and stored in DB 6. Of course, a voice UI may be provided, and consent and non-consent regarding the acceptable conditions of use may be input in a conversational format or the like.
[0181] There is no limitation on the timing for providing the consent UI to confirm the intention of the employee 2, and the consent UI may be provided at any timing. For example, the consent UI may be provided to each employee 2 at the timing when the license conditions requiring the employee's consent are set. Alternatively, the consent UI may be provided to an employee whose life log information is detected at the timing when the life log information is selected as license information according to the license conditions requiring the employee's consent.
[0182] FIG. 21 is a flowchart showing an example of the operation of server device 25 in selecting use permission information.
[0183] First, the allowable use conditions are selected. Specifically, allowable use condition data is selected from the "condition data" stored in DB6 (step 201). Next, life log information to be the subject of the allowable use judgment is selected (step 202). Next, of the life log information selected in step 202, the life log information that matches the allowable use conditions selected in step 201 is selected as the allowable use information (step 203).
[0184] In this manner, in this embodiment, the allowable use information is selected from the life log information based on the allowable use conditions set by the condition setting unit 26 for selecting the life log information as the allowable use information.
[0185] Fig. 22 is a flow chart showing a specific example of the selection of the use permission information. It is monitored whether or not a function for using the life log information has been selected via a terminal logged in to the present business management system 1, such as the management terminal 4 shown in Fig. 1 (step 301).
[0186] For example, in the GUIs as exemplified in Fig. 11 to Fig. 13, the "Life Log" button is selected from the "Work" menu. Then, any one of the "Action History" button 19, the "Health" button 20, and the "Sleep" button 21 is selected. In such a case, step 301 becomes Yes, and the process proceeds to step 302.
[0187] In step 302, an acceptable use condition related to a function that utilizes the selected life log information is selected. For example, when the "Behavior History" button 19 is selected, an acceptable use condition related to "Behavior History" is selected. When the "Health" button 20 is selected, an acceptable use condition related to "Health" is selected. When the "Sleep" button 21 is selected, an acceptable use condition related to "Sleep" is selected.
[0188] Without being limited thereto, a list of "condition names" of each acceptable use condition may be displayed on the display device of the terminal, and the "condition name" may be selected by the operator. The information selection unit 12 selects the acceptable use condition of the "condition name" selected by the administrator 8 or the like. Alternatively, a UI such as "What kind of life log information do you want to use?" may be presented, and the acceptable use conditions may be narrowed down.
[0189] Next, it is determined whether or not the operator of the terminal, such as the administrator 8, has the viewing authority (step 303). This determination is made, for example, by comparing the viewing authority information included in the acceptable use conditions selected in step 302 with the authority information of the operator obtained from the login information of the terminal or the like. Of course, this is not limited to this, and a UI for confirming the authority of the operator may be provided.
[0190] If the terminal operator does not have the right to view the information (No in step 303), the selection of the permitted usage information ends.
[0191] If the operator of the terminal has viewing authority (Yes in step 303), the information search unit 13 searches for life log information based on the search conditions input via the terminal (step 304). For example, the search conditions input include the employee the operator wishes to view, the type of life log information the operator wishes to view, the period during which the life log information was detected, and the like.
[0192] It is determined whether or not the consent of the individual is required (step 305). This determination is made based on information on whether or not the consent of the individual is required, which is included in the usage allowance conditions selected in step 302. If the consent of the individual is required (Yes in step 304), it is determined whether or not the consent of the individual has been confirmed, i.e., whether or not the consent has been entered by employee 2 himself (step 306).
[0193] For example, the "personal consent data" shown in Fig. 20 is referenced to determine whether or not the employee 2 entered as a search condition in step 304 has given personal consent to the use allowance conditions selected in step 302. If the employee's consent is not confirmed (No in step 306), the selection of use allowance information ends.
[0194] If the employee's consent is not confirmed in step 306, a consent UI may be provided to the employee 2 in question to confirm the employee's intention. If the employee's consent is rejected (if non-consent is entered) or if no response is received within a predetermined time, the selection of the usage permission information may end.
[0195] If it is determined in step 305 that the consent of the person in question is not required, or if the consent of the person in question is confirmed in step 306, the process proceeds to step 307. In step 307, the life log information that matches the usage allowance conditions among the search results found in step 304 is selected as usage allowance information. That is, the information selection unit 12 selects the usage allowance information from the search results by the information search unit 13.
[0196] In the flowchart shown in Fig. 22, steps 301 and 302 correspond to step 201 shown in Fig. 21. Step 304 corresponds to step 202. Steps 303 and 305 to 307 correspond to step 203.
[0197] Of course, the selection of use permission information using the use permission conditions is not limited to the flows shown in FIG. 20 and FIG. 21, and any other flow may be adopted.
[0198] In this embodiment, it is also possible to select non-use allowable information using non-use allowable conditions. For example, it is possible to make the flow shown in Fig. 20 correspond to the selection of non-use allowable information. That is, it is possible to execute a step of selecting non-use allowable conditions, a step of selecting life log information to be the subject of non-use allowable judgment, and a step of selecting life log information that matches the non-use allowable conditions as non-use allowable information.
[0199] 21, it is possible to handle the selection of non-usage permitted information by deleting the viewing authority determination step in step 303 and the personal consent determination steps in steps 305 and 306. That is, it is possible to execute the steps of monitoring whether a function for making life log information non-usable has been selected, selecting non-usage permitted conditions related to the selected function, searching for life log information based on the search results, and selecting life log information from the search results that matches the non-usage permitted conditions as non-usage permitted information.
[0200] As described above, in this embodiment, it is possible to set the use allowable conditions and non-use allowable conditions as appropriate, and it is possible to select the use allowable information and non-use allowable information based on the set use allowable conditions and non-use allowable conditions. This allows more detailed settings regarding the use of the life log information, and it becomes possible to appropriately use the life log information of employee 2 in business management.
[0201] <Third embodiment> A business management system according to a third embodiment of the present invention will now be described. In this embodiment, a determination is made as to the state of the employee 2 with regard to the selection of permitted use information. When the employee 2 is in a predetermined state, the information selection unit 12 selects permitted use information for the life log information detected from the employee 2 based on permitted use conditions corresponding to the predetermined state.
[0202] The above-mentioned "predetermined state" is, for example, a state in which there is a risk that employee 2 may leak confidential information. For example, a state in which employee 2 takes out a computer such as a PC that stores confidential information in an internal storage device can be set as a state in which there is a risk that employee 2 may leak confidential information. Of course, the state is not limited to this, and for example, a state in which a database containing confidential information can be accessed and communication with the outside can be set as a state in which there is a risk that confidential information may be leaked.
[0203] An example of an acceptable use condition corresponding to a state where employee 2 is at risk of leaking confidential information is a condition in which all life log information detected from an employee in that state is selected as acceptable use information. For an employee 2 who is at risk of leaking confidential information, information such as where the employee 2 is and what the situation is is given priority as acceptable use information. This makes it possible to prevent the leaking of confidential information.
[0204] Of course, the acceptable conditions of use are not limited to these. As acceptable conditions of use corresponding to a state where there is a risk that employee 2 may leak confidential information, it is possible to set various conditions with a broader range of acceptable conditions of use than acceptable conditions of use corresponding to a normal state of employee 2 (a state where there is no risk of leaking confidential information).
[0205] Fig. 23 is a flow chart showing a specific example of the selection of the usage permission information Fig. 24 is a schematic diagram showing an example of the "confidential information take-out application data" stored in the DB6.
[0206] Steps 401 to 404 shown in FIG. 22 are similar to steps 301 to 304 shown in FIG.
[0207] In this embodiment, in step 405, it is determined whether or not the employee 2 whose life log information is the subject of the use permission determination (the employee 2 input as the detection condition in step 404) is in a state of taking out confidential information. That is, in step 405, it is determined whether or not the employee 2 is in a state where there is a risk of leaking confidential information.
[0208] This determination can be made by referring to the "confidential information take-out application data" shown in Fig. 24. As shown in Fig. 24, the "confidential information take-out application data" includes the following information.
[0209] "Personal Code" "Name of target device": Name of the device being taken out (name of the device that contains confidential information). "Status": Information indicating whether the device is being taken out or not. "Authorized individual code": The individual code of the person who approved the removal of the equipment. "Planned start date and time of removal": The planned date and time of removal of the equipment. "Planned end date and time of removal": The planned end date and time of removal of the equipment.
[0210] With reference to the "confidential information take-out application data", for example, if the "status" is that the device is being taken out, employee 2 is determined to be in a state where there is a risk of leaking confidential information. Without being limited to this, even if the "status" is not that the device is being taken out, if the current time is included in the "date and time of planned take-out start" to "date and time of planned take-out end", employee 2 may be determined to be in a state where there is a risk of leaking confidential information.
[0211] If employee 2 is in a state where there is a risk of leaking confidential information (Yes in step 405), the allowable use information is selected based on the allowable use conditions corresponding to that state. In the example shown in Fig. 24, the life log information searched for employee 2 is selected as the allowable use information (step 406).
[0212] If employee 2 is not in a state where there is a risk of leaking confidential information (No in step 405), steps 407 to 409 are executed. Steps 407 to 409 are the same as steps 305 to 307 shown in FIG.
[0213] It is also possible for the administrator 8 or the like to input a request to view the life log information of an employee 2 who is taking confidential information out. For example, a list of "confidential information take-out application data" is displayed on the management terminal 4. When the administrator 8 or the like selects "confidential information take-out application data," the life log information detected for the employee 2 corresponding to the "personal code" of the data is generated as usage permission information and becomes available for viewing. Such processing is also possible.
[0214] As described above, in this embodiment, it is determined whether employee 2 is in a predetermined state, and if so, the selection of allowable use information is executed based on the allowable use conditions corresponding to the predetermined state. This allows more detailed settings regarding the use of life log information, and makes it possible to appropriately use the life log information of employee 2 in business management.
[0215] It is also possible to set a state other than the state in which the employee 2 is at risk of leaking confidential information as the "predetermined state." For example, the present invention can be applied to various states of the employee 2, such as a state of a certain health condition or being in a certain area, as the "predetermined state."
[0216] <Other embodiments> The present invention is not limited to the above-described embodiment, and various other embodiments can be realized.
[0217] Fig. 25 is a schematic diagram showing an example of the functional configuration of a sensor device 3 that detects life log information from an employee 2. As shown in Fig. 25, a processor of the sensor device 3 executes a predetermined program to realize a condition reference unit 43, a life log information output control unit 44, and a UI provision unit 45 as functional blocks.
[0218] The condition reference unit 43 refers to the "condition data" stored in the DB 6. That is, the condition reference unit 43 accesses the DB 6 and refers to the use allowable conditions and the non-use allowable conditions. Alternatively, the "condition data" may be transmitted from the server device 5 to the sensor device 3. Then, the use allowable conditions may be referred to.
[0219] The life log information output control unit 44 controls the external output of the life log information detected by the sensor device 3. That is, the life log information output control unit 44 controls the transmission of the life log information to the server device 5.
[0220] The life log information output control unit 44 restricts the output of non-use allowable information that is not selected as use allowable information from among the detected life log information, based on the use allowable conditions and non-use allowable conditions acquired by the condition acquisition unit 43. In other words, the life log information output control unit 44 does not transmit to the server device 5 the non-use allowable information that is not selected as use allowable information.
[0221] In other words, the life log information output control unit 44 transmits life log information that may be selected as acceptable usage information, and detection results necessary to generate life log information that may be selected as acceptable usage information, to the server device 6 via the network 7.
[0222] On the other hand, the life log information output control unit 44 restricts the transmission to the server device 5 of life log information that may not be selected as acceptable usage information and detection results necessary to generate life log information that may not be selected as acceptable usage information.
[0223] For example, if the employee 2's consent is required to select the information as permitted use information, but the employee's consent cannot be confirmed, the transmission of the corresponding life log information to the server device 5 is restricted.
[0224] If the employee's consent cannot be confirmed, the UI providing unit 45 may provide a UI for consent to confirm the employee's intention. If the employee's consent is entered, output to the server device 5 is executed. If the employee's consent is not entered, output to the server device 5 is not executed.
[0225] 26 is a flowchart showing an example of transmission of life log information by the sensor device 3. Here, a case is taken as an example in which a determination is made as to whether or not to transmit life log information of “sleep state” to the server device 5, triggered by the employee 2 getting up (awakening).
[0226] The employee 2's waking up (awakening) is monitored (step 501). The condition reference unit 43 refers to the usage allowance conditions stored in the DB 6 (step 502).
[0227] The condition reference unit 43 determines whether or not there is an allowable use condition in which the "sleeping state" is a target use type (step 503). If there is no allowable use condition in which the "sleeping state" is a target use type (No in step 503), information to that effect is output to the life log information output control unit 44. The life log information output control unit 44 determines that the life log information of the "sleeping state" is non-allowable use information that is not selected as allowable use information, does not transmit the information to the server device 5, and ends the process.
[0228] If there is a use allowance condition in which the “sleep state” is the use target type (Yes in step 503 ), information to that effect is output to the life log information output control unit 44 .
[0229] The life log information output control unit 44 determines whether or not the person's consent is required (step 504), and determines whether the person's consent is confirmed (step 505). If it is determined in step 504 that the person's consent is required, and if the person's consent is not confirmed in step 505, it determines that the life log information of the "sleeping state" is non-usable information that is not selected as usable information, and transmission to the server device 5 is not executed, and the process ends.
[0230] If it is determined in step 504 that the individual's consent is not required, and if the individual's consent is confirmed in step 505, the life log information of "sleeping state" is determined to be the life log information to be selected as acceptable usage information, and the information of "sleeping state" is transmitted to server device 5 (step 506).
[0231] In this way, the transmission of life log information from the sensor device 3 to the server device 5 may be controlled based on the usage allowance conditions. This makes it possible to save the storage capacity of the DB 6 and reduce the amount of communication data.
[0232] Fig. 27 is a schematic diagram for explaining the reference value regarding the use of the use permission information. In the example shown in Fig. 27, a "reference value" is set for each type of life log information as shown below.
[0233] "Body temperature" ... "35.0~37.5" "Heart rate" ... "60~100" “Sleep information”… “Less than 6 hours” "Alcohol content" ... "0.5% or more"
[0234] The "reference value" is information that is referenced when life log information is selected as the permitted use information and is used for business-related processing. For example, when the value of the detected life log information (permitted use information) matches the range set as the "reference value," it is used for business-related processing. Such settings are possible.
[0235] Without being limited to this, the detected life log information (permitted use information) is used as information with different attributes depending on whether the value matches a range set as a "reference value" or not. For example, based on the "reference value", it is determined whether the life log information (permitted use information) is reference value match information or non-reference value match information, and the information is used appropriately as different information. Alternatively, for example, the life log information (permitted use information) is displayed or made public so that it can be identified as reference value match information or non-reference value match information. Such settings are also possible.
[0236] For example, assume that the use of the allowable usage information is to display it on a display device or to notify a specific person. In this case, for example, display or notification is performed only when the detected life log information (allowable usage information) is reference value match information. Alternatively, display or notification is performed so that it is possible to identify whether the detected life log information (allowable usage information) is reference value match information or non-reference value match information. For example, when it is reference value match information (or non-reference value match information), display or notification is performed together with a warning (alert). Such settings are also possible.
[0237] 28 is a block diagram showing an example of the hardware configuration of a computer 60 that can be used as the sensor device 3, the management terminal 4, and the server device 5. The sensor device 3 further includes a sensor.
[0238] The computer 60 includes a CPU 61, a ROM 62, a RAM 63, an input / output interface 65, and a bus 64 connecting these to one another. The input / output interface 65 is connected to a display unit 66, an input unit 67, a storage unit 68, a communication unit 69, a drive unit 70, and the like. The display unit 66 is, for example, a display device using a liquid crystal, an EL, etc. The input unit 67 is, for example, a keyboard, a pointing device, a touch panel, or other operating device. When the input unit 67 includes a touch panel, the touch panel can be integrated with the display unit 66. The storage unit 68 is a non-volatile storage device, such as a HDD, a flash memory, or other solid-state memory. The drive unit 70 is a device capable of driving a removable recording medium 71, such as an optical recording medium, a magnetic recording tape, or the like. The communication unit 69 is a modem, a router, or other communication device that can be connected to a LAN, a WAN, or the like and is used to communicate with other devices. The communication unit 69 may communicate either wired or wirelessly. The communication unit 69 is often used separately from the computer 60. Information processing by computer 60 having the above hardware configuration is realized by cooperation between software stored in storage unit 68 or ROM 62, etc., and hardware resources of computer 60. Specifically, the information processing method according to the present invention is realized by loading a program constituting the software stored in ROM 62, etc., into RAM 63 and executing the program. The program is installed in the computer 60 via, for example, the recording medium 71. Alternatively, the program may be installed in the computer 60 via a global network or the like. Any other computer-readable non-transitory storage medium may be used.
[0239] The information processing method (method for selecting usage allowance information / method for using usage allowance information) and program of the present invention may be executed by collaboration between multiple computers connected to each other so as to communicate with each other via a network or the like, thereby constructing an information processing system or information processing device of the present invention. That is, the information processing method and program according to the present invention can be executed not only in a computer system constituted by a single computer, but also in a computer system in which a plurality of computers operate in conjunction with each other. In this disclosure, a system refers to a collection of multiple components (devices, modules (parts), etc.), regardless of whether all the components are in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device in which multiple modules are housed in a single housing, are both systems.
[0240] The execution of the information processing method and program according to the present invention by a computer system includes both cases where, for example, acquisition of life log information, acquisition of business information, selection of usage allowance information, use of usage allowance information, etc., are executed by a single computer, and cases where each process is executed by a different computer. Furthermore, execution of each process by a specific computer includes causing another computer to execute part or all of the process and acquiring the results. In other words, the information processing method and program according to the present invention can also be applied to a cloud computing configuration in which a single function is shared and processed jointly by multiple devices via a network.
[0241] The configurations of the business management system, sensor device, server device, management terminal, DB, condition input GUI, consent input GUI, and each process flow such as selection of usage permission information and use of usage permission information, which have been described with reference to the drawings, are merely one embodiment and may be modified as desired without departing from the spirit of the present invention. In other words, any other configurations, algorithms, etc. for implementing the present invention may be adopted.
[0242] In this disclosure, in order to facilitate understanding of the explanation, the words "approximately", "almost", "approximately", etc. may be used as appropriate. However, there is no clear difference between using the words "approximately", "almost", "approximately", etc. and not using them. In other words, in the present disclosure, concepts that define shape, size, positional relationship, state, and the like, such as "center," "central," "uniform," "equal," "same," "orthogonal," "parallel," "symmetric," "extending," "axial direction," "cylindrical," "cylindrical," "ring-shaped," and "annular," are concepts that include "substantially central," "substantially central," "substantially uniform," "substantially equal," "substantially the same," "substantially orthogonal," "substantially parallel," "substantially symmetric," "substantially extending," "substantially axial direction," "substantially cylindrical," "substantially cylindrical," "substantially ring-shaped," "substantially annular," and the like. For example, this includes states that are included within a specified range (e.g., a range of ±10%) based on standards such as "perfectly centered," "perfectly central," "perfectly uniform," "perfectly equal," "perfectly the same," "perfectly orthogonal," "perfectly parallel," "perfectly symmetrical," "perfectly extended," "perfectly axial," "perfectly cylindrical," "perfectly cylindrical," "perfectly ring-shaped," "perfectly toric," etc. Therefore, even if the words "approximately", "almost", "roughly", etc. are not added, the concept expressed by adding "approximately", "almost", "approximately", etc. may be included. Conversely, a state expressed by adding "approximately", "almost", "approximately", etc. does not necessarily exclude a perfect state.
[0243] In this disclosure, expressions using "more than", such as "greater than A" and "smaller than A", are expressions that comprehensively include both concepts that include equivalent to A and concepts that do not include equivalent to A. For example, "greater than A" is not limited to cases that do not include equivalent to A, but also includes "A or greater." Furthermore, "smaller than A" is not limited to "less than A" but also includes "A or less." When implementing the present technology, specific settings and the like may be appropriately adopted from the concepts included in "greater than A" and "smaller than A" so as to achieve the effects described above.
[0244] Of the characteristic features of the present invention described above, at least two of the characteristic features may be combined. In other words, the various characteristic features described in each embodiment may be arbitrarily combined without distinction between the embodiments. In addition, the various effects described above are merely examples and are not limiting, and other effects may be exhibited. [Explanation of symbols]
[0245] 1. Business management system 2. Employees 3. Sensor device 4. Management terminal 5, 25…Server equipment 6. Database (DB) 8…Administrator 17…Life log information display screen 60…Computer
Claims
1. A first acquisition unit that acquires life log information detected from an employee; A second acquisition unit that acquires business information related to the business of the employee; an information selection unit that selects, based on the acquired business information, from the acquired life log information, usage permission information that is permitted to be used for business-related processing; an information utilization unit that utilizes the selected utilization permission information; An information processing system comprising:
2. 2. The information processing system according to claim 1, The information selection unit selects, as the allowable use information, the life log information detected within an allowable use time that is set based on the working hours of the employee. Information processing system.
3. 2. The information processing system according to claim 1, The information selection unit selects, as the permitted use information, the life log information detected within a permitted use area set based on the employee's place of work. Information processing system.
4. The information processing system according to claim 1, further comprising: a condition setting unit that sets a usage permission condition for the life log information to be selected as the usage permission information; The information selection unit selects the usage permission information from the life log information based on the set usage permission condition. Information processing system.
5. 5. The information processing system according to claim 4, The first acquisition unit acquires the life log information by type, The condition setting unit sets the usage permission conditions for each of the types. Information processing system.
6. The information processing system according to claim 4, further comprising: A condition input UI providing unit provides a condition input UI (User Interface) for inputting the use permission conditions via a predetermined terminal. Information processing system.
7. 5. The information processing system according to claim 4, The usage permission condition includes at least one of a condition regarding a time when the life log information was detected, a condition regarding a location where the life log information was detected, a condition regarding a type of the life log information, a condition regarding the presence or absence of consent of the employee where the life log information was detected, and a condition regarding the presence or absence of authority to use the usage permission information. Information processing system.
8. The information processing system according to claim 1, further comprising: An information search unit that searches for the life log information based on search conditions inputted via a predetermined terminal, The information selection unit selects the usage permission information from the search results by the information search unit. Information processing system.
9. 2. The information processing system according to claim 1, The information usage unit displays the usage permission information on a display device. Information processing system.
10. 2. The information processing system according to claim 1, The information usage unit analyzes the usage permission information and uses the analysis result. Information processing system.
11. The information processing system according to claim 1, further comprising: and an information output restriction unit that restricts output of non-permitted information that is not selected as the permitted use information from a sensor that detects the life log information from the employee. Information processing system.
12. The information processing system according to claim 1, further comprising: and a consent input UI providing unit that provides the employee whose life log information has been detected with a consent UI for inputting whether or not the employee consents to selecting the life log information as the permitted use information. Information processing system.
13. 2. The information processing system according to claim 1, When the employee is in a predetermined state, the information selection unit selects the use allowance information for the detected life log information based on a use allowance condition corresponding to the predetermined state. Information processing system.
14. The information processing system according to claim 13, The information selection unit selects the detected life log information as the permitted use information when the employee is in a state where there is a risk of leaking confidential information. Information processing system.
15. 2. The information processing system according to claim 1, The life log information includes at least one of location information of the employee and biometric information of the employee. Information processing system.
16. 2. The information processing system according to claim 1, The work information includes at least one of attendance information and information on work content. Information processing system.
17. The information processing system according to claim 1, further comprising: A history management unit that manages history information regarding the use of the usage permission information by the information use unit. Information processing system.
18. Acquire life log information detected from employees, Obtaining business information relating to the employee's business; selecting, based on the acquired business information, from the acquired life log information, usage permission information that is permitted to be used for business-related processing; Utilizing the selected usage permission information An information processing method implemented by a computer.
19. obtaining life log information detected from an employee; acquiring job information relating to the employee's job; selecting, based on the acquired business information, from the acquired life log information, usage permission information that is permitted to be used for business-related processing; utilizing the selected usage permission information; A program that causes a computer to execute the following.
Citation Information
Patent Citations
Information disclosure support apparatus, information disclosure support method, and information disclosure support program
JP2010266960A
