WO2024095410A1

WO2024095410A1 - Stress data analysis system, stress data analysis method, and stress data analysis program

Info

Publication number: WO2024095410A1
Application number: PCT/JP2022/041049
Authority: WO
Inventors: 英松林; 一樹新山; 剛人池田
Original assignee: 三菱電機株式会社
Priority date: 2022-11-02
Filing date: 2022-11-02
Publication date: 2024-05-10
Also published as: JP7333885B1

Abstract

A stress data analysis system (1) comprises a stress data acquisition unit (22) that acquires stress data regarding a situation of stress that occurs to a user who uses an engineering tool, a cause analysis unit that analyzes the stress data to identify a part of the engineering tool that causes the stress resulting from the use of the engineering tool, a countermeasure creation unit that creates a countermeasure that can be taken against the cause, and an update unit (36) that updates the engineering tool by reflecting, to the engineering tool, the countermeasure determined to be employed.

Description

STRESS DATA ANALYSIS SYSTEM, STRESS DATA ANALYSIS METHOD, AND STRESS DATA ANALYSIS PROGRAM

The present disclosure relates to a stress data analysis system, a stress data analysis method, and a stress data analysis program that analyze the stress experienced by users of engineering tools.

In recent years, as engineering software and other programming software have become more sophisticated, there is a demand for more efficient work through intuitive operation. Hereinafter, engineering software will be referred to as engineering tools. To enable intuitive operation of engineering tools, it is desirable to be able to reduce the stress caused by operation or to be able to avoid stress caused by operation. To be able to reduce or avoid stress, it is important to collect information when stress occurs and to utilize the collected information.

Patent Document 1 discloses an information transmission program that acquires a user's operation history for the functions of a computer system, and if the operation history satisfies a dissatisfaction condition indicating that the user is dissatisfied with the computer system, transmits the operation history that satisfies the dissatisfaction condition to the address of the system developer. In Patent Document 1, the computer system is a business-related computer system, such as an electronic medical record system.

JP 2019-144660 A

In the technology described in Patent Document 1, information is collected for a system in which functions expected from user operations are predetermined, such as an electronic medical record system. Functions expected from user operations include, for example, a function to obtain electronic medical records. On the other hand, when functions expected of a system are constructed by user programming, such as an engineering tool, the path to realize the expected functions, such as the programming method or the use of the engineering tool, differs from user to user. For this reason, in order to increase satisfaction with an engineering tool by reducing or avoiding stress, it is necessary to collect not only information about the operation of functions prepared in advance, but also information on the flow of using the prepared functions. In the technology described in Patent Document 1, information is not collected during the flow of using the prepared functions, so there is a problem in that it is difficult to increase satisfaction in using the engineering tool.

The present disclosure has been made in consideration of the above, and aims to provide a stress data analysis system that makes it possible to improve satisfaction in the use of engineering tools.

In order to solve the above-mentioned problems and achieve the objectives, the stress data analysis system disclosed herein comprises a stress data acquisition unit that acquires stress data regarding the stress conditions experienced by a user who uses an engineering tool, a cause analysis unit that identifies the part of the engineering tool that is the cause of stress when using the engineering tool by analyzing the stress data, a countermeasure creation unit that creates countermeasures that can be taken against the cause, and an update unit that updates the engineering tool by reflecting the countermeasure that has been decided upon in the engineering tool.

The stress data analysis system disclosed herein has the effect of improving satisfaction in using engineering tools.

FIG. 1 is a diagram showing a configuration example of a stress data analysis system according to a first embodiment; FIG. 1 is a diagram showing an example of the configuration of an engineering device, a server device, and a terminal device of a stress data analysis system according to a first embodiment. FIG. 1 is a diagram showing an example of the configuration of a data analysis unit included in a server device of a stress data analysis system according to a first embodiment; 1 is a flowchart showing a procedure of an operation performed by the stress data analysis system according to the first embodiment. 1 is a flowchart showing a procedure of an operation performed by a server device when a countermeasure registered as a temporary countermeasure is executed in the first embodiment. 1 is a flowchart showing a first example of an operation procedure for acquiring data for analysis by the stress data analysis system according to the first embodiment; 11 is a flowchart showing a first example of an operation procedure of creating a countermeasure and registering the created countermeasure by the server device of the stress data analysis system according to the first embodiment; 11 is a flowchart showing a second example of an operation procedure for acquiring data for analysis by the stress data analysis system according to the first embodiment. 11 is a flowchart showing a second example of a procedure of an operation of creating a countermeasure and registering the created countermeasure by the server device of the stress data analysis system according to the first embodiment. 11 is a flowchart showing a third example of an operation procedure for acquiring data for analysis by the stress data analysis system according to the first embodiment. 11 is a flowchart showing a third example of an operation procedure of creating a countermeasure and registering the created countermeasure by the server device of the stress data analysis system according to the first embodiment. 11 is a flowchart showing a fourth example of an operation procedure for acquiring data for analysis by the stress data analysis system according to the first embodiment. 11 is a flowchart showing a fourth example of an operation procedure for creating a countermeasure and registering the created countermeasure by the server device of the stress data analysis system according to the first embodiment. FIG. 1 is a diagram illustrating an example of a hardware configuration of a server device constituting the stress data analysis system according to the first embodiment. FIG. 1 is a diagram showing an example of a hardware configuration of an engineering device constituting the stress data analysis system according to the first embodiment;

Below, the stress data analysis system, stress data analysis method, and stress data analysis program according to the embodiments will be described in detail with reference to the drawings.

Embodiment 1.
1 is a diagram showing an example of the configuration of a stress data analysis system 1 according to the embodiment 1. The stress data analysis system 1 collects information about stress caused to a user who uses an engineering tool, and provides countermeasures for reducing or avoiding stress.

The stress data analysis system 1 comprises an engineering device 2 used by a user, a server device 3 that collects and analyzes data, and a terminal device 4 that presents countermeasures against stress. The engineering device 2 and the server device 3 communicate with each other via a network. The server device 3 and the terminal device 4 communicate with each other via a network. The network is, for example, a WAN (Wide Area Network) such as the Internet. The network may also be a LAN (Local Area Network).

The server device 3 is a server built in a cloud environment. The cloud environment includes computer resources provided in a cloud service platform. Because the server device 3 is built in a cloud environment, it is sometimes called a cloud server.

The engineering tool is a program creation support program that supports the creation of a program used by a control device that controls a controlled device such as a robot to control the controlled device. The control device is, for example, a programmable logic controller. In the first embodiment, the engineering tool is provided via a network by SaaS (Software as a Service). The engineering device 2 uses the engineering tool executed by the server device 3 via the network. Note that the use of the engineering tool is not limited to SaaS, and the engineering tool may be installed in the engineering device 2 and executed by the engineering device 2.

The user creates a program using an engineering tool by operating the engineering device 2. The program created using the engineering tool is, for example, a ladder program. The engineering device 2 transmits stress data about the stress situation of the user who uses the engineering tool to the server device 3. The engineering device 2 also transmits operation history data, which is a history of operations by the user, to the server device 3. The server device 3 searches for the cause of stress from the stress data and the operation history data, and creates possible countermeasures for the cause. The server device 3 transmits information indicating the countermeasures to the terminal device 4. The stress data analysis system 1 notifies the user of the countermeasures by transmitting information indicating the countermeasures from the server device 3 to the engineering device 2.

The terminal device 4 presents the countermeasures created by the server device 3. A judge who determines which countermeasure to adopt decides whether or not to adopt the countermeasure presented by the terminal device 4. The terminal device 4 transmits information indicating whether or not the countermeasure can be adopted to the server device 3. The server device 3 updates the engineering tool by reflecting the countermeasure that has been decided to be adopted in the engineering tool. The engineering device 2 uses the updated engineering tool.

The stress data analysis system 1 may be equipped with a device that acquires the user's physical condition information. The physical condition information is information acquired by observing the user's physical condition. The camera 2a shown in FIG. 1 is an example of a device that acquires the user's physical condition information. The camera 2a photographs the user using the engineering device 2, and outputs the physical condition information, which is image data of the user. The physical condition information is input to the engineering device 2.

FIG. 2 is a diagram showing an example configuration of the engineering device 2, server device 3, and terminal device 4 of the stress data analysis system 1 according to the first embodiment.

The engineering device 2 includes a user interface unit 21, a stress data acquisition unit 22, and an operation history acquisition unit 23. The user interface unit 21 accepts operations by the user. The user interface unit 21 also displays information. The user interface unit 21 transmits information input to the user interface unit 21 by operation to the server device 3. The user uses the engineering tool by operating the user interface unit 21.

The stress data acquisition unit 22 acquires stress data of a user who uses the engineering tool. The stress data acquisition unit 22 judges whether or not the user is experiencing stress, and acquires stress data when it is judged that the user is experiencing stress. The stress data acquisition unit 22 transmits the acquired stress data to the server device 3. The operation history acquisition unit 23 acquires operation history data regarding operations of the user interface unit 21. The operation history acquisition unit 23 transmits the acquired operation history data to the server device 3. In the example shown in FIG. 2, the stress data acquisition unit 22 acquires data of an image captured by the camera 2a.

The server device 3 includes an engineering tool unit 31, a stress data collection unit 32, an operation history collection unit 33, a data analysis unit 34, and an update unit 36. The server device 3 holds a countermeasure DB (DataBase) 35. The engineering tool unit 31 executes an engineering tool according to information from the engineering device 2.

The stress data collection unit 32 receives stress data from the stress data acquisition unit 22 and collects the stress data. The stress data collected by the stress data collection unit 32 is input to the data analysis unit 34. The operation history collection unit 33 receives operation history data from the operation history acquisition unit 23 and collects the operation history data. The operation history data collected by the operation history collection unit 33 is input to the data analysis unit 34.

The data analysis unit 34 analyzes the stress data collected by the stress data collection unit 32 and the operation history data collected by the operation history collection unit 33 to identify the cause of stress. The data analysis unit 34 creates a countermeasure according to the cause of stress. The data analysis unit 34 transmits information about the countermeasure to the terminal device 4. The data analysis unit 34 outputs the information about the countermeasure to the countermeasure DB 35. The server device 3 stores the created countermeasure in the countermeasure DB 35.

The update unit 36 reads out information about the countermeasures from the countermeasure DB 35. The update unit 36 updates the engineering tool by reflecting the countermeasure that has been decided to be adopted in the engineering tool. The update unit 36 also transmits information indicating the countermeasures to the engineering device 2. The user interface unit 21 of the engineering device 2 receives the information indicating the countermeasures and displays the information indicating the countermeasures. This notifies the user of the countermeasures. By notifying the user of the countermeasures, the user can be made aware of the countermeasures for reducing or avoiding stress.

The terminal device 4 includes a user interface unit 41. The user interface unit 41 receives information about countermeasures and displays the information about the countermeasures. The user interface unit 41 also accepts operations by the decision maker. The user interface unit 41 presents countermeasures created by a countermeasure creation unit in the data analysis unit 34, and functions as a presentation unit that accepts information indicating whether or not the presented countermeasures can be adopted. The countermeasure creation unit will be described later. The user interface unit 41 transmits information indicating whether or not the countermeasures can be adopted to the server device 3.

The data analysis unit 34 receives information indicating whether or not a countermeasure is to be adopted, and outputs information about the countermeasure that has been decided to be adopted to the countermeasure DB 35. When the information about the countermeasure that has been decided to be adopted is stored in the countermeasure DB 35, the data analysis unit 34 notifies the update unit 36 that the countermeasure information has been stored. Upon receiving the notification, the update unit 36 reads out the information about the countermeasure that has been decided to be adopted from the countermeasure DB 35. As a result, the update unit 36 reflects the countermeasure that has been decided to be adopted in the user interface unit 41 in the engineering tool.

The update unit 36 also acquires stress data from the stress data collection unit 32. The update unit 36 checks whether or not there is a countermeasure that corresponds to the acquired stress data by referring to the countermeasure information stored in the countermeasure DB 35. If there is a countermeasure that corresponds to the acquired stress data, the update unit 36 reads the information on the countermeasure that corresponds to the acquired stress data from the countermeasure DB 35 and reflects the countermeasure in the engineering tool. The update unit 36 outputs the information on the countermeasure that has been reflected in the engineering tool to the data analysis unit 34.

Here, we will explain the stress data. The stress data acquisition unit 22 can acquire stress data by the first to fourth acquisition methods described below. The stress data acquisition unit 22 may acquire stress data by one of the first to fourth acquisition methods, or may acquire stress data by two or more of the first to fourth acquisition methods.

In the first acquisition method of stress data, the stress data acquisition unit 22 works in conjunction with an AI (Artificial Intelligence) chatbot, which is a communication tool that accepts inquiries about engineering tools. When a question is input by a user, the AI chatbot outputs an answer to the question. When a user inputs a question to the AI chatbot, the stress data acquisition unit 22 acquires the information input to the AI chatbot as stress data. That is, in the first acquisition method, the stress data includes information input by the user to the AI chatbot.

In the first acquisition method, the stress data acquisition unit 22 determines that an event that caused stress to the user has occurred when the user inputs a question to the AI chatbot. The stress data acquisition unit 22 also treats the information input to the AI chatbot as stress data related to stress. The stress data acquisition unit 22 acquires the input information when a question about how to use the engineering tool or a question about how to deal with errors in the engineering tool is input to the AI chatbot. The stress data acquisition unit 22 may also acquire the input information when a request for improvements to the engineering tool is input to the AI chatbot.

In the second method of acquiring stress data, the stress data acquisition unit 22 works in conjunction with a device that acquires information about the user's physical condition. For example, the camera 2a takes a video of the user operating the engineering device 2, and transmits the image data to the stress data acquisition unit 22. The stress data acquisition unit 22 observes the user's condition based on the image data from the camera 2a. The stress data acquisition unit 22 detects changes in the user's physical condition or changes in the user's behavior from the image data. A change in the physical condition is, for example, a change in facial color. A change in behavior is, for example, repeated tapping of the keyboard with the fingers.

The stress data acquisition unit 22 determines that the user is stressed when a change in physical condition or behavior is detected. When the stress data acquisition unit 22 determines that the user is stressed, it acquires image data as stress data. The image data is physical condition information acquired by observing the user's physical condition. In the second acquisition method, the stress data includes physical condition information. For example, the stress data acquisition unit 22 may learn physical condition information when stress is occurring by a method such as machine learning, and determine the presence or absence of stress based on the learning result.

The physical condition information may be any information capable of detecting a change in the user's physical condition or a change in the user's behavior, and is not limited to image data acquired by shooting a video. The device that acquires the physical condition information may include a microphone that captures audio. The stress data acquisition unit 22 may determine that the user is stressed when the user speaks or when the user's tone of voice changes.

The stress data acquisition unit 22 constantly monitors the user's physical condition based on the physical condition information while the user is using the engineering tool. If the stress data acquisition unit 22 determines that the user is stressed, it acquires physical condition information from a point in time that is a preset time prior to the point in time of the determination as stress data. The stress data acquisition unit 22 transmits the stress data to the server device 3. If the stress data acquisition unit 22 determines that the user's stress has been relieved, it stops transmitting the stress data to the server device 3.

In the above, it is stated that whether or not the user is in a stressed state is determined by the stress data acquisition unit 22 of the engineering device 2, but this is not limited to the above. The function of determining whether or not the user is in a stressed state may be provided in the server device 3.

In the third method of acquiring stress data, the stress data acquisition unit 22 determines that the user is stressed when an error occurs while using the engineering tool. When the stress data acquisition unit 22 determines that the user is stressed, it acquires an error log, which is information about the error, as stress data. The error log includes information indicating the content of the operation when the error occurred. That is, in the third acquisition method, the stress data includes information indicating the content of the operation when an error occurs while using the engineering tool.

In a fourth method for acquiring stress data, the stress data acquisition unit 22 determines that the user has become stressed when no error has occurred but the user is having trouble creating a program. In the fourth acquisition method, the stress data includes information indicating the content of an operation when a specific event occurs in the user's operation when using the engineering tool. The specific event is, for example, when the user is continuing to create a program in the step being created or in a step related to the step being created, and the time during which the user's operation is stalled exceeds a preset time. When the user is unsure which of multiple functions of the engineering tool to use, or when the user is unsure which algorithm to use, the time until the operation is resumed becomes long. When the time from when the operation was stopped exceeds the preset time, the stress data acquisition unit 22 determines that the user is having trouble creating a program and has become stressed.

The specific event may be any event that can be determined to be an event that requires time and effort in creating a program by the user, and is not limited to an operation interval exceeding a preset time. The specific event may be, for example, an operation and cancellation of the operation being repeated consecutively.

Next, the operation history data will be explained. The operation history acquisition unit 23 constantly acquires operation history data such as the use of function buttons corresponding to various functions of the engineering tool, the movement of the pointer by operating the pointing device included in the user interface unit 21, or the use of function blocks.

When the stress data acquisition unit 22 determines that the user is stressed, the operation history acquisition unit 23 uses the determination that stress is occurring as a trigger to transmit operation history data to the server device 3. The operation history acquisition unit 23 transmits operation history data from a point in time that is a preset time prior to the point in time at which it was determined that stress was occurring to the server device 3. When the stress data acquisition unit 22 determines that the user's stress has been relieved, the operation history acquisition unit 23 stops transmitting the operation history data to the server device 3. The stress data analysis system 1 can search for causes that contributed to the occurrence of stress by analyzing the operation history data from a point in time prior to the point in time at which it was determined that stress was occurring.

Next, the configuration of the data analysis unit 34 will be described. FIG. 3 is a diagram showing an example of the configuration of the data analysis unit 34 of the server device 3 of the stress data analysis system 1 according to the first embodiment. FIG. 3 shows the data analysis unit 34, a countermeasure DB 35, and a user interface unit 41 of the terminal device 4.

The data analysis unit 34 includes a cause analysis unit 341, a countermeasure creation unit 342, and a countermeasure classification unit 343. Stress data and operation history data are input to the cause analysis unit 341. The cause analysis unit 341 identifies the part of the engineering tool that is the cause of stress when using the engineering tool by analyzing the stress data.

The countermeasure creation unit 342 creates countermeasures that can be taken for the causes identified by the cause analysis unit 341. The countermeasure creation unit 342 may, for example, learn countermeasures that enable stress reduction or stress avoidance using a method such as machine learning, and create countermeasures based on the learning results. If the stress data analysis system 1 uses an AI chatbot, the AI engine of the AI chatbot may be used as the countermeasure creation unit 342.

The countermeasure creation unit 342 may determine the difference between the program created by the user and the program based on the learning results, and create a countermeasure based on the difference. The countermeasure creation unit 342 may create, as a countermeasure, a tool or function that can guide the program created by the user to a program based on the learning results. A program based on the learning results is a program that does not cause stress when created, or can reduce stress when created. This allows the countermeasure creation unit 342 to create a countermeasure that makes it possible to reduce or avoid stress.

The countermeasures may be, for example, a bug fix program for the engineering tool, a function in the engineering tool that recommends recommended programs, or a function that recommends recommended programs based on the user's unique characteristics. The countermeasures may be, for example, changing the layout of function buttons, improving function blocks, or a function that automatically creates programs from the user's required specifications. The automatic program creation function is a function that creates a program from text.

The countermeasure classification unit 343 classifies and manages the countermeasures created by the countermeasure creation unit 342 into essential countermeasures that must be executed and temporary countermeasures that are countermeasures other than essential countermeasures. Essential countermeasures are countermeasures that should be executed regardless of the user's terms of use, or countermeasures that should be executed because they cause high levels of stress. Examples of essential countermeasures are a bug fix program for an engineering tool, a recommendation function for recommended programs in an engineering tool, or a change in the layout of function buttons.

Temporary countermeasures are countermeasures other than essential countermeasures among the countermeasures created by the countermeasure creation unit 342, and are countermeasures that can be taken as a temporary response to stress. Temporary countermeasures include common countermeasures and customized countermeasures. Common countermeasures are countermeasures that can be commonly applied regardless of individuals or conditions. Customized countermeasures are countermeasures that can be applied after being customized to suit individuals or conditions. Common countermeasures are also candidates for essential countermeasures. An example of a common countermeasure is an automatic program creation function based on the user's required specifications. This automatic program creation function is changed to an essential countermeasure as the accuracy of the automatic creation improves. An example of a customized countermeasure is a recommendation function for recommended programs based on the user's unique characteristics.

The countermeasure classification unit 343 transmits information on the countermeasure created by the countermeasure creation unit 342 together with category information on the countermeasure to the terminal device 4. The category information indicates whether the countermeasure has been classified into an essential countermeasure or a temporary countermeasure category. The user interface unit 41 of the terminal device 4 presents the countermeasures for each category. The judge inputs information indicating whether the presented countermeasure can be adopted to the user interface unit 41. The user interface unit 41 transmits information indicating whether the countermeasure can be adopted to the server device 3. The countermeasure classification unit 343 receives the information indicating whether the countermeasure can be adopted, and outputs information on the countermeasure that has been decided to be adopted and category information to the countermeasure DB 35. The countermeasure DB 35 stores information on the countermeasures for each category. As a result, the countermeasure classification unit 343 manages the countermeasures created by the countermeasure creation unit 342 by classifying them into essential countermeasures and temporary countermeasures.

If the decision maker wishes to adopt a countermeasure classified as an essential countermeasure as a temporary countermeasure, he or she can instruct the presented countermeasure to change the category by operating the user interface unit 41. In this case, the user interface unit 41 transmits an instruction to change the category to the server device 3 together with information indicating whether the presented countermeasure can be adopted. The countermeasure classification unit 343 changes the category of the countermeasure that has been decided to be adopted from an essential countermeasure to a temporary countermeasure.

When the countermeasure information is stored in the countermeasure DB 35, the countermeasure classification unit 343 notifies the update unit 36 shown in FIG. 2 via the countermeasure DB 35 that the countermeasure information has been stored. Upon receiving the notification, the update unit 36 reflects the countermeasures classified as essential countermeasures and stored in the countermeasure DB 35, i.e., the countermeasures registered as essential countermeasures, in the engineering tool. By applying essential countermeasures, the stress data analysis system 1 can fundamentally avoid stress.

In addition, when the update unit 36 acquires stress data from the stress data collection unit 32, it checks whether or not there is a countermeasure corresponding to the acquired stress data among the countermeasures classified as temporary countermeasures and stored in the countermeasure DB 35, i.e., the countermeasures registered as temporary countermeasures. If there is a countermeasure corresponding to the acquired stress data, the update unit 36 reads information about the countermeasure corresponding to the acquired stress data from the countermeasure DB 35 and reflects the countermeasure in the engineering tool. The stress data analysis system 1 can reduce stress by applying temporary countermeasures, thereby preventing the accumulation of stress.

Next, the operation of the stress data analysis system 1 will be described. FIG. 4 is a flowchart showing the procedure of the operation of the stress data analysis system 1 according to the first embodiment. FIG. 4 shows an example of the procedure of the operation when a countermeasure registered as an essential countermeasure is executed.

In step S1, the engineering device 2 acquires stress data and operation history data. The engineering device 2 acquires stress data by the stress data acquisition unit 22. The stress data acquisition unit 22 acquires stress data by determining that the user is experiencing stress. The stress data acquisition unit 22 transmits the acquired stress data to the server device 3. The stress data collection unit 32 receives the stress data and collects it. In addition, the engineering device 2 acquires operation history data by the operation history acquisition unit 23. The operation history acquisition unit 23 transmits the acquired operation history data to the server device 3. The operation history collection unit 33 receives the operation history data and collects it.

In step S2, the data analysis unit 34 of the server device 3 identifies the cause of stress based on the stress data and the operation history data by the cause analysis unit 341. The cause analysis unit 341 analyzes the stress data collected by the stress data collection unit 32 and the operation history data collected by the operation history collection unit 33, and identifies the cause of stress.

In step S3, the data analysis unit 34 creates possible countermeasures for the identified cause using the countermeasure creation unit 342. In step S4, the data analysis unit 34 classifies the countermeasures created in step S3 using the countermeasure classification unit 343. The countermeasure classification unit 343 transmits information about the created countermeasures and category information about the countermeasures to the terminal device 4.

In step S5, the user interface unit 41 of the terminal device 4 presents countermeasures. The user interface unit 41 displays information about countermeasures for each category based on the received countermeasure information and the received category information. The judge inputs information indicating whether or not the countermeasure can be adopted to the user interface unit 41, thereby deciding whether or not to adopt the presented countermeasure. The user interface unit 41 transmits information indicating whether or not the countermeasure can be adopted to the server device 3.

The countermeasure classification unit 343 receives information indicating whether or not to adopt the countermeasure, and outputs information about the countermeasure that has been decided to be adopted and category information to the countermeasure DB 35. In step S6, the server device 3 registers the countermeasure that has been decided to be adopted by storing the information about the countermeasure in the countermeasure DB 35. The countermeasures are registered for each category based on the category information. When the information about the countermeasure is stored in the countermeasure DB 35, the countermeasure classification unit 343 notifies the update unit 36 that the information about the countermeasure has been stored.

In step S7, the server device 3 updates the engineering tool by having the update unit 36 reflect the registered countermeasures in the engineering tool. When the update unit 36 receives a notification from the countermeasure classification unit 343 that countermeasure information has been stored, it reads out information on the countermeasures registered as essential countermeasures from the countermeasure DB 35. As a result, the update unit 36 reflects the countermeasures classified as essential countermeasures in the engineering tool. The engineering device 2 uses the updated engineering tool. With the above, the stress data analysis system 1 ends the operation according to the procedure shown in FIG. 4.

Next, the operation of the server device 3 when executing a countermeasure registered as a temporary countermeasure will be described. Figure 5 is a flowchart showing the procedure of the operation of the server device 3 when executing a countermeasure registered as a temporary countermeasure in embodiment 1.

In step S11, the server device 3 collects stress data using the stress data collection unit 32. The stress data collection unit 32 collects stress data acquired by the stress data acquisition unit 22 upon determining that the user is experiencing stress. The stress data collection unit 32 outputs the collected stress data to each of the data analysis unit 34 and the update unit 36.

The update unit 36 checks whether or not there is a countermeasure that corresponds to the stress data among the countermeasures classified as temporary countermeasures and stored in the countermeasure DB 35. Here, it is assumed that the countermeasures that correspond to the stress data are stored in the countermeasure DB 35. The update unit 36 reads information on the countermeasures that correspond to the acquired stress data from the countermeasure DB 35. The update unit 36 reflects the countermeasures that correspond to the acquired stress data in the engineering tool. In this way, in step S12, the server device 3 executes the countermeasures registered as temporary countermeasures. The update unit 36 outputs the information on the countermeasures reflected in the engineering tool to the data analysis unit 34.

In step S13, the server device 3 uses the stress data collection unit 32 to collect stress data after the countermeasure in step S12 has been implemented. The stress data acquisition unit 22 outputs the collected stress data to the data analysis unit 34. Through the above procedure, the stress data collected in step S11, information on the countermeasure reflected in the engineering tool, and the stress data collected in step S13 are input to the data analysis unit 34. In other words, the data analysis unit 34 receives stress data before the countermeasure registered as a temporary countermeasure is implemented, information on the implemented countermeasure, and stress data after the implementation of the countermeasure.

In step S14, the server device 3 uses the cause analysis unit 341 of the data analysis unit 34 to determine whether the implemented countermeasure was sufficient. The cause analysis unit 341 determines whether the implemented countermeasure was sufficient based on the stress data before the countermeasure registered as a temporary countermeasure was implemented and the stress data after the countermeasure was implemented.

The cause analysis unit 341 judges whether the implemented countermeasure was sufficient based on the change in stress data before and after the implementation of the countermeasure. For example, if it is determined that the change in stress data is due to an improvement in stress, the cause analysis unit 341 judges that the implemented countermeasure was sufficient. On the other hand, if there is no change in the stress data or if it is determined that the change in stress data is due to a worsening of stress, the cause analysis unit 341 judges that the implemented countermeasure was not sufficient.

If it is determined that the implemented countermeasure is sufficient (step S14, Yes), in step S15, the countermeasure classification unit 343 of the data analysis unit 34 of the server device 3 changes the category of the countermeasure implemented in step S12 from a temporary countermeasure to an essential countermeasure. Information on the implemented countermeasure is classified as an essential countermeasure and stored in the countermeasure DB 35. In other words, the registration of the countermeasure is corrected to a registration as an essential countermeasure. In this way, the countermeasure classification unit 343 changes the classification of the countermeasure from a temporary countermeasure to an essential countermeasure based on the results when the countermeasure classified as a temporary countermeasure was implemented.

On the other hand, if it is determined that the implemented countermeasure is not sufficient (step S14, No), in step S16, the server device 3 modifies the countermeasure by the countermeasure creation unit 342 of the data analysis unit 34. The countermeasure creation unit 342 acquires information on the implemented countermeasure, and modifies the countermeasure based on the stress data before the implementation of the countermeasure registered as a temporary countermeasure and the stress data after the implementation of the countermeasure. The countermeasure creation unit 342 modifies the countermeasure to improve stress based on the change in the stress data before and after the implementation of the countermeasure. Information on the modified countermeasure is stored in the countermeasure DB 35.

By completing step S15 or step S16, the server device 3 ends the operation according to the procedure shown in FIG. 5. The stress data analysis system 1 can reduce or avoid stress for a user who continues to use the engineering tool by operating according to the procedure shown in FIG. 4 or by operating according to the procedure shown in FIG. 5. By reducing or avoiding user stress, it is possible to improve satisfaction in using the engineering tool.

Next, we will explain the details of the operation of acquiring data for analysis in the data analysis unit 34, and the operation of creating countermeasures by the data analysis unit 34 and registering the created countermeasures. Here, we will explain the cases where the stress data acquired for analysis is stress data acquired by the above-mentioned first acquisition method, stress data acquired by the above-mentioned second acquisition method, stress data acquired by the above-mentioned third acquisition method, and stress data acquired by the above-mentioned fourth acquisition method.

FIG. 6 is a flowchart showing a first example of an operational procedure for acquiring data for analysis by the stress data analysis system 1 according to the first embodiment. FIG. 7 is a flowchart showing a first example of an operational procedure for creating countermeasures and registering the created countermeasures by the server device 3 of the stress data analysis system 1 according to the first embodiment. The first examples shown in each of FIG. 6 and FIG. 7 are examples of the case where stress data is acquired by the first acquisition method.

In step S21 shown in FIG. 6, the stress data analysis system 1 determines whether or not the AI chatbot has been used by the stress data acquisition unit 22. Using the AI chatbot refers to inputting a question to the AI chatbot. For example, if a problem occurs when creating a program using an engineering tool, the user inputs a question to the AI chatbot to solve the problem. If the AI chatbot has not been used (step S21, No), the stress data analysis system 1 returns the procedure to step S21.

On the other hand, if an AI chatbot is used (step S21, Yes), in step S22, the stress data analysis system 1 acquires the information input to the AI chatbot by the stress data acquisition unit 22. The stress data acquisition unit 22 transmits the stress data, which is the information input to the AI chatbot, to the stress data collection unit 32. The stress data acquisition unit 22 also acquires information on the response output by the AI chatbot in response to the input as stress data, and transmits it to the stress data collection unit 32. The stress data collection unit 32 outputs the collected stress data to the cause analysis unit 341.

The operation history acquisition unit 23 is triggered by the determination that stress is occurring, and transmits operation history data to the operation history collection unit 33. That is, the operation history acquisition unit 23 is triggered by the use of an AI chatbot, and transmits operation history data to the operation history collection unit 33. In step S23, the stress data analysis system 1 acquires the operation history data transmitted by the operation history acquisition unit 23 using the operation history collection unit 33. The operation history collection unit 33 collects the operation history data, and outputs the collected operation history data to the cause analysis unit 341.

In step S24, the stress data analysis system 1 obtains program creation status data by extracting the functions used in creating the program and the created program using the cause analysis unit 341. The cause analysis unit 341 extracts the part of the created program that is the theme of the question based on the information input to the AI chatbot. The cause analysis unit 341 identifies the cause by identifying the function or function block in the program created using an engineering tool. The cause analysis unit 341 also extracts the function used in creating that part of the program, such as copy, paste, function block, or icon placement, from the operation history data. The program creation status data includes the extracted program and data indicating the extracted function. The cause analysis unit 341 stores the stress data, which is the information input to the AI chatbot and the information output from the AI chatbot, and the program creation status data in association with each other.

The user takes appropriate measures indicated in the response to the question. For example, if the problem is not resolved even after taking the measures indicated in the response, the user makes an additional inquiry to the AI chatbot. In step S25, the stress data analysis system 1 determines whether or not additional information has been input to the AI chatbot using the stress data acquisition unit 22. If additional information has been input to the AI chatbot (step S25, Yes), the stress data analysis system 1 returns the procedure to step S22 and acquires the additional information using the stress data acquisition unit 22.

On the other hand, if no additional information is input to the AI chatbot (step S25, No), in step S26, the stress data analysis system 1 determines, via the stress data acquisition unit 22, whether a certain period of time has passed since the information was input to the AI chatbot. The certain period of time is a period set in advance. If the certain period of time has not passed (step S26, No), the stress data analysis system 1 returns the procedure to step S25.

On the other hand, if a certain period of time has passed (step S26, Yes), the stress data acquisition unit 22 determines that the problem has been resolved by implementing the measures indicated in the response. As a result, the stress data analysis system 1 ends the operation according to the procedure shown in FIG. 6.

The server device 3 starts analyzing the stress data and the program creation status data in the cause analysis unit 341. In step S31 shown in FIG. 7, the cause analysis unit 341 searches for the cause of stress based on the information input to the AI chatbot and the responses to the input.

In step S32, the cause analysis unit 341 extracts parts of the program creation status data that are related to the keywords included in the input information, and searches for the cause of stress based on the extracted parts. The cause analysis unit 341 extracts the parts related to the keywords, assuming that the part of the program that was being created was the part that caused the user's question. The cause analysis unit 341 extracts the program up to a certain number of steps from the point when the information was input into the AI chatbot. The cause analysis unit 341 searches for the cause of stress from the extracted program.

The cause analysis unit 341 determines whether or not the program created by the user has any wasteful parts when compared with an ideal program. Furthermore, if the program created by the user has any wasteful parts, the cause analysis unit 341 searches for the cause of the creation of the wasteful parts. An ideal program is a basic algorithm. If a program to be adopted for the program being created is suggested in the response of the AI chatbot, the ideal program may be the program suggested in the response.

In step S33, the countermeasure creation unit 342 creates countermeasures for the causes of stress discovered in steps S31 and S32. As countermeasures, for example, the creation of function blocks, which are program components that can simplify program creation, a function to present function blocks to the user, or a function to guide the user to a function that presents function blocks can be adopted.

In step S34, the countermeasure classification unit 343 judges whether the countermeasure created in step S33 is an essential countermeasure. If the created countermeasure is an essential countermeasure (step S34, Yes), the countermeasure classification unit 343 transmits category information indicating that the countermeasure is an essential countermeasure to the terminal device 4 along with information about the created countermeasure. When the decision is made by the judge to adopt the countermeasure, in step S35, the countermeasure classification unit 343 registers the countermeasure created in step S33 as an essential countermeasure.

On the other hand, if the created countermeasure is not an essential countermeasure (step S34, No), the countermeasure classification unit 343 determines that the created countermeasure is a temporary countermeasure. The countermeasure classification unit 343 transmits information about the created countermeasure and category information indicating that it is a temporary countermeasure to the terminal device 4. When the decision is made by the judge to adopt the countermeasure, in step S36, the countermeasure classification unit 343 registers the countermeasure created in step S33 as a temporary countermeasure. With the above, the server device 3 ends the operation according to the procedure shown in FIG. 7.

If the judge decides to adopt a countermeasure classified as a temporary countermeasure by the countermeasure classification unit 343 as an essential countermeasure, the countermeasure classification unit 343 registers the countermeasure created in step S33 as an essential countermeasure. As shown in FIG. 5, the server device 3 may also search for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and revise the registration of the countermeasure to a registration as an essential countermeasure.

FIG. 8 is a flowchart showing a second example of the procedure of the operation of the stress data analysis system 1 according to the first embodiment to acquire data for analysis. FIG. 9 is a flowchart showing a second example of the procedure of the operation of the server device 3 of the stress data analysis system 1 according to the first embodiment to create countermeasures and register the created countermeasures. The second examples shown in each of FIG. 8 and FIG. 9 are examples of the case where stress data is acquired by the second acquisition method.

In step S41 shown in FIG. 8, the stress data analysis system 1 determines whether or not the user is in a stressed state using the stress data acquisition unit 22. The stress data acquisition unit 22 observes how the user operates the engineering device 2. If the stress data acquisition unit 22 detects a change in the user's physical condition or behavior, it determines that the user is in a stressed state. If it determines that the user is not in a stressed state (step S41, No), the stress data analysis system 1 returns the procedure to step S41.

On the other hand, if it is determined that the user is in a stressed state (Yes in step S41), in step S42, the stress data analysis system 1 acquires physical condition information by the stress data acquisition unit 22. The stress data acquisition unit 22 transmits the stress data, which is physical condition information, to the stress data collection unit 32. The stress data collection unit 32 outputs the collected stress data to the cause analysis unit 341.

When it is determined that the user is in a stressed state, the operation history acquisition unit 23 sends operation history data to the operation history collection unit 33. In step S43, the stress data analysis system 1 acquires the operation history data sent by the operation history acquisition unit 23 using the operation history collection unit 33. The operation history collection unit 33 collects the operation history data and outputs the collected operation history data to the cause analysis unit 341.

In step S44, the stress data analysis system 1 obtains program creation status data by extracting the functions used in creating the program and the created program using the cause analysis unit 341. The cause analysis unit 341 extracts the part of the program that was being created when it was determined that stress was occurring. The cause analysis unit 341 also extracts the functions used in creating that part of the program from the operation history data. The cause analysis unit 341 stores the stress data, which is physical condition information, and the program creation status data in association with each other.

In step S45, the stress data analysis system 1 selects a temporary countermeasure using the update unit 36, and presents the selected temporary countermeasure using the user interface unit 41. The update unit 36 acquires stress data from the stress data collection unit 32. The update unit 36 acquires program creation status data from the cause analysis unit 341. Based on the stress data and the program creation status data, the update unit 36 selects a countermeasure corresponding to the stress data from among the countermeasures registered as temporary countermeasures. The countermeasure classification unit 343 transmits category information indicating that the countermeasure is a temporary countermeasure to the user interface unit 41 of the terminal device 4, together with information on the countermeasure selected by the update unit 36. When the decision to adopt the countermeasure is made by the judge, in step S46, the update unit 36 reflects the determined temporary countermeasure in the engineering tool.

In a situation where an engineering tool reflecting temporary countermeasures is being used, in step S47, the stress data analysis system 1 determines whether the stressful state has been resolved using the stress data acquisition unit 22. If it is determined that the stressful state has not been resolved (step S47, No), the stress data analysis system 1 returns to step S42, and acquires stress data and program creation status data in the cause analysis unit 341. The cause analysis unit 341 stores the stress data and the program creation status data in association with each other. On the other hand, if it is determined that the stressful state has been resolved (step S47, Yes), the stress data analysis system 1 ends the operation according to the procedure shown in FIG. 8.

The server device 3 starts analyzing the stress data and the program creation status data in the cause analysis unit 341. In step S51 shown in FIG. 9, the cause analysis unit 341 searches for the cause of stress based on the physical condition information.

In step S52, the cause analysis unit 341 extracts a portion of the program creation status data that corresponds to the time when a change in physical condition occurred, and searches for the cause of stress based on the extracted portion. The cause analysis unit 341 extracts the portion that corresponds to the time when the change in physical condition occurred, assuming that stress occurred from the time when the change in physical condition occurred.

The cause analysis unit 341 determines whether the program created by the user contains any wasteful parts when compared with an ideal program. If the program created by the user contains any wasteful parts, the cause analysis unit 341 searches for the cause of the wasteful parts being created.

In step S53, the countermeasure creation unit 342 creates countermeasures for the causes of stress discovered in steps S51 and S52.

In step S54, the countermeasure classification unit 343 determines whether the countermeasure created in step S53 is an essential countermeasure. If the created countermeasure is an essential countermeasure (step S54, Yes), the countermeasure classification unit 343 transmits category information indicating that the countermeasure is an essential countermeasure to the terminal device 4 along with information about the created countermeasure. When the decision is made by the judge to adopt the countermeasure, in step S55, the countermeasure classification unit 343 registers the countermeasure created in step S53 as an essential countermeasure.

On the other hand, if the created countermeasure is not an essential countermeasure (step S54, No), the countermeasure classification unit 343 determines that the created countermeasure is a temporary countermeasure. The countermeasure classification unit 343 transmits category information indicating that the countermeasure is a temporary countermeasure to the terminal device 4 along with information about the created countermeasure. When the decision is made by the judge to adopt the countermeasure, in step S56, the countermeasure classification unit 343 registers the countermeasure created in step S53 as a temporary countermeasure. With the above, the server device 3 ends the operation according to the procedure shown in FIG. 9.

If the judge decides to adopt a countermeasure classified as a temporary countermeasure by the countermeasure classification unit 343 as an essential countermeasure, the countermeasure classification unit 343 registers the countermeasure created in step S53 as an essential countermeasure. As shown in FIG. 5, the server device 3 may also search for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and revise the registration of the countermeasure to a registration as an essential countermeasure.

FIG. 10 is a flowchart showing a third example of the procedure of the operation of the stress data analysis system 1 according to the first embodiment to acquire data for analysis. FIG. 11 is a flowchart showing a third example of the procedure of the operation of the server device 3 of the stress data analysis system 1 according to the first embodiment to create countermeasures and register the created countermeasures. The third examples shown in each of FIG. 10 and FIG. 11 are examples of the case where stress data is acquired by the third acquisition method.

In step S61 shown in FIG. 10, the stress data analysis system 1 determines whether or not an error has occurred in the use of the engineering tool using the stress data acquisition unit 22. When an error has occurred in the use of the engineering tool, the stress data acquisition unit 22 regards the occurrence of an error as a case in which the user has experienced stress. If no error has occurred (step S61, No), the stress data analysis system 1 returns the procedure to step S61.

On the other hand, if an error occurs (step S61, Yes), in step S62, the stress data analysis system 1 acquires an error log by the stress data acquisition unit 22. The stress data acquisition unit 22 transmits the stress data, which is the error log, to the stress data collection unit 32. The stress data collection unit 32 outputs the collected stress data to the cause analysis unit 341.

When an error occurs during use of the engineering tool, the operation history acquisition unit 23 sends operation history data to the operation history collection unit 33. In step S63, the stress data analysis system 1 acquires the operation history data sent by the operation history acquisition unit 23 using the operation history collection unit 33. The operation history collection unit 33 collects the operation history data and outputs the collected operation history data to the cause analysis unit 341.

In step S64, the stress data analysis system 1 obtains program creation status data by extracting the functions used in creating the program and the created program using the cause analysis unit 341. The cause analysis unit 341 extracts the part of the program that was being created when the error occurred. The cause analysis unit 341 also extracts the functions used in creating that part of the program from the operation history data. The cause analysis unit 341 stores the stress data, which is the error log, and the program creation status data in association with each other.

In step S65, the stress data analysis system 1 selects a temporary countermeasure using the update unit 36, and presents the selected temporary countermeasure using the user interface unit 41. When the decision to adopt the countermeasure is made by the judge, in step S66, the update unit 36 reflects the determined temporary countermeasure in the engineering tool. Details of steps S65 and S66 are the same as those of steps S45 and S46 shown in FIG. 8.

In a situation where an engineering tool reflecting temporary countermeasures is being used, in step S67, the stress data analysis system 1 determines whether the error has been resolved using the stress data acquisition unit 22. If it is determined that the error has not been resolved (step S67, No), the stress data analysis system 1 returns to step S62, and acquires stress data and program creation status data in the cause analysis unit 341. The cause analysis unit 341 stores the stress data and the program creation status data in association with each other. On the other hand, if it is determined that the error has been resolved (step S67, Yes), the stress data analysis system 1 ends the operation according to the procedure shown in FIG. 10.

The server device 3 starts analyzing the stress data and the program creation status data in the cause analysis unit 341. In step S71 shown in FIG. 11, the cause analysis unit 341 searches for the cause of stress based on the error log.

In step S72, the cause analysis unit 341 extracts the part of the program creation status data that is related to the error, and searches for the cause of stress based on the extracted part. The cause analysis unit 341 extracts the part related to the error, assuming that stress occurred from the time the error occurred.

In step S73, the countermeasure creation unit 342 creates countermeasures for the causes of stress discovered in steps S71 and S72.

In step S74, the countermeasure classification unit 343 judges whether the countermeasure created in step S73 is an essential countermeasure. If the created countermeasure is an essential countermeasure (step S74, Yes), the countermeasure classification unit 343 transmits category information indicating that the countermeasure is an essential countermeasure to the terminal device 4 along with information about the created countermeasure. When the decision is made by the judge to adopt the countermeasure, in step S75, the countermeasure classification unit 343 registers the countermeasure created in step S73 as an essential countermeasure.

On the other hand, if the created countermeasure is not an essential countermeasure (step S74, No), the countermeasure classification unit 343 determines that the created countermeasure is a temporary countermeasure. The countermeasure classification unit 343 transmits category information indicating that the countermeasure is a temporary countermeasure to the terminal device 4 along with information about the created countermeasure. When the decision is made by the judge to adopt the countermeasure, in step S76, the countermeasure classification unit 343 registers the countermeasure created in step S73 as a temporary countermeasure. With the above, the server device 3 ends the operation according to the procedure shown in FIG. 11.

If the judge decides to adopt a countermeasure classified as a temporary countermeasure by the countermeasure classification unit 343 as an essential countermeasure, the countermeasure classification unit 343 registers the countermeasure created in step S73 as an essential countermeasure. As shown in FIG. 5, the server device 3 may also search for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and revise the registration of the countermeasure to a registration as an essential countermeasure.

FIG. 12 is a flowchart showing a fourth example of the procedure of the operation of the stress data analysis system 1 according to the first embodiment to acquire data for analysis. FIG. 13 is a flowchart showing a fourth example of the procedure of the operation of the server device 3 of the stress data analysis system 1 according to the first embodiment to create countermeasures and register the created countermeasures. The fourth examples shown in each of FIG. 12 and FIG. 13 are examples of the case where stress data is acquired by a fourth acquisition method.

In step S81 shown in FIG. 12, the stress data analysis system 1 determines whether an alarm has occurred during use of the engineering tool using the stress data acquisition unit 22. The engineering tool generates an alarm when a specific event occurs during operation by the user during use of the engineering tool. For example, the engineering tool generates an alarm when the time since the user's operation stopped exceeds a preset time. The stress data acquisition unit 22 considers the occurrence of an alarm during use of the engineering tool to be a case in which the user has become stressed. If an alarm has not occurred (step S81, No), the stress data analysis system 1 returns the procedure to step S81. On the other hand, if an alarm has occurred (step S81, Yes), in step S82, the stress data analysis system 1 acquires alarm information using the stress data acquisition unit 22.

The alarm information includes information about the event that caused the alarm, such as the time the operation started, the time the alarm occurred, the time the operation ended if it ended, the step where the operation was stalled, or the program number where the operation was stalled. The stress data acquisition unit 22 transmits the stress data, which is the alarm information, to the stress data collection unit 32. The stress data collection unit 32 outputs the collected stress data to the cause analysis unit 341.

The operation history acquisition unit 23 transmits operation history data to the operation history collection unit 33 when an alarm occurs during use of the engineering tool. In step S83, the stress data analysis system 1 acquires the operation history data transmitted by the operation history acquisition unit 23 using the operation history collection unit 33. The operation history collection unit 33 collects the operation history data and outputs the collected operation history data to the cause analysis unit 341.

In step S84, the stress data analysis system 1 obtains program creation status data by extracting the functions used in creating the program and the created program using the cause analysis unit 341. The cause analysis unit 341 extracts the part of the program that was being created when the alarm occurred. The cause analysis unit 341 also extracts the functions used in creating that part of the program from the operation history data. The cause analysis unit 341 stores the stress data, which is alarm information, and the program creation status data in association with each other.

In step S85, the stress data analysis system 1 selects a temporary countermeasure using the update unit 36, and presents the selected temporary countermeasure using the user interface unit 41. When the decision to adopt the countermeasure is made by the judge, in step S86, the update unit 36 reflects the determined temporary countermeasure in the engineering tool. Details of steps S85 and S86 are the same as those of steps S45 and S46 shown in FIG. 8.

In a situation where an engineering tool reflecting temporary countermeasures is being used, in step S87, the stress data analysis system 1 determines whether the alarm has been released using the stress data acquisition unit 22. If it is determined that the alarm has not been released (step S87, No), the stress data analysis system 1 returns to step S82, and acquires stress data and program creation status data in the cause analysis unit 341. The cause analysis unit 341 stores the stress data and the program creation status data in association with each other. On the other hand, if it is determined that the alarm has been released (step S87, Yes), the stress data analysis system 1 ends the operation according to the procedure shown in FIG. 12.

The server device 3 starts analyzing the stress data and the program creation status data in the cause analysis unit 341. In step S91 shown in FIG. 13, the cause analysis unit 341 searches for the cause of stress based on the alarm information.

In step S92, the cause analysis unit 341 extracts the portion of the program creation status data that is related to the alarm, and searches for the cause of stress based on the extracted portion. The cause analysis unit 341 extracts the portion related to the alarm, assuming that stress arose from the point in time when the event that caused the alarm occurred. The point in time when the event that caused the alarm occurred is, for example, the point in time when the operation was stopped.

In step S93, the countermeasure creation unit 342 creates countermeasures for the causes of stress discovered in steps S91 and S92.

In step S94, the countermeasure classification unit 343 determines whether the countermeasure created in step S93 is an essential countermeasure. If the created countermeasure is an essential countermeasure (step S94, Yes), the countermeasure classification unit 343 transmits category information indicating that the countermeasure is an essential countermeasure to the terminal device 4 along with information about the created countermeasure. When the decision is made by the judge to adopt the countermeasure, in step S95, the countermeasure classification unit 343 registers the countermeasure created in step S93 as an essential countermeasure.

On the other hand, if the created countermeasure is not an essential countermeasure (step S94, No), the countermeasure classification unit 343 determines that the created countermeasure is a temporary countermeasure. The countermeasure classification unit 343 transmits category information indicating that the countermeasure is a temporary countermeasure to the terminal device 4 along with information about the created countermeasure. When the decision is made by the judge to adopt the countermeasure, in step S96, the countermeasure classification unit 343 registers the countermeasure created in step S93 as a temporary countermeasure. With the above, the server device 3 ends the operation according to the procedure shown in FIG. 13.

If the judge decides to adopt a countermeasure classified as a temporary countermeasure by the countermeasure classification unit 343 as an essential countermeasure, the countermeasure classification unit 343 registers the countermeasure created in step S93 as an essential countermeasure. As shown in FIG. 5, the server device 3 may also search for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and revise the registration of the countermeasure to a registration as an essential countermeasure.

The stress data analysis system 1 identifies the cause of stress in the use of an engineering tool based on stress data and program creation status data. The stress data analysis system 1 can identify the part of the engineering tool that is the cause of stress. The part of the engineering tool that is the cause of stress is, for example, one of the functions of the engineering tool that is causing stress to the user.

The stress data analysis system 1 creates possible countermeasures for the identified causes, and reflects the countermeasures that have been decided upon for adoption in the engineering tool. The stress data analysis system 1 also classifies and manages the created countermeasures into essential countermeasures and temporary countermeasures. By applying countermeasures classified as essential countermeasures, the stress data analysis system 1 can fundamentally avoid stress. By applying temporary countermeasures, the stress data analysis system 1 can reduce stress and prevent stress from accumulating.

The stress data analysis system 1 can improve satisfaction in using the engineering tool by continually improving the engineering tool through the application of countermeasures. The stress data analysis system 1 can create countermeasures that correspond to the unique characteristics of the user by providing a category of temporary countermeasures. For countermeasures that are sufficient for the user, the stress data analysis system 1 can change the category from temporary countermeasures to essential countermeasures, thereby enabling the fundamental avoidance of stress in accordance with the user's characteristics.

In the first embodiment, when stress data is acquired, the stress data analysis system 1 may award points to the user, etc., according to the stress data, based on a preset rule. The rule may be, for example, awarding a number of points according to the number of times stress data is acquired, or awarding a number of points according to the importance of a problem caused by stress.

In the first embodiment, the stress data analysis system 1 analyzes stress and creates countermeasures using engineering tools, but the target may be programming software other than engineering tools. Programs created using programming software are not limited to ladder programs written using ladder language, and may be programs written in programming languages other than ladder language.

Next, the hardware configuration of the server device 3 will be described. FIG. 14 is a diagram showing an example of the hardware configuration of the server device 3 constituting the stress data analysis system 1 according to the first embodiment. The server device 3 is realized by a computer system including a processing circuit 51 and a communication device 52. The processing circuit 51 includes a processor 53 and a memory 54. The processing circuit 51 is a circuit on which the processor 53 executes software.

Each of the engineering tool unit 31, stress data collection unit 32, operation history collection unit 33, data analysis unit 34, and update unit 36 of the server device 3 is realized by software, firmware, or a combination of software and firmware. The software or firmware is written as a program and stored in memory 54. In the processing circuit 51, the processor 53 reads and executes the program stored in memory 54, thereby realizing the functions of each of the parts of the server device 3. In other words, the processing circuit 51 has a memory 54 for storing a program that will result in the processing of the server device 3 being executed. The program stored in memory 54 is a stress data analysis program that causes a computer to execute the procedures and methods of the stress data analysis system 1.

The processor 53 is a CPU (Central Processing Unit), a processing unit, an arithmetic unit, a microprocessor, a microcomputer, a processor, or a DSP (Digital Signal Processor). The memory 54 is, for example, a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable Read Only Memory), or an EEPROM (registered trademark) (Electrically Erasable Programmable Read Only Memory). The countermeasure DB 35 is stored in the memory 54.

The communication device 52 communicates with devices external to the server device 3. The communication between the server device 3 and the engineering device 2, and the communication between the server device 3 and the terminal device 4 are realized by using the communication device 52.

The programs stored in memory 54 may be provided in a form written on a storage medium such as a CD (Compact Disc)-ROM or a DVD (Digital Versatile Disc)-ROM, or may be provided via a communication line.

The components provided in the server device 3 in the first embodiment may be realized by two or more devices arranged in different locations. Each of the two or more devices is realized, for example, by the hardware configuration shown in FIG. 14. The two or more devices are connected so as to be able to communicate with each other. Each of the two or more devices may be a server device. The two or more server devices may include a processing server and a data server.

Next, the hardware configuration of the engineering device 2 will be described. FIG. 15 is a diagram showing an example of the hardware configuration of the engineering device 2 constituting the stress data analysis system 1 according to the first embodiment. The engineering device 2 is realized by a computer system including a processing circuit 61, a communication device 62, an input device 65, and a display device 66.

The processing circuit 61 includes a processor 63 and a memory 64. The processing circuit 61 is a circuit in which the processor 63 executes software. The processor 63 and the memory 64 are assumed to be similar to the processor 53 and the memory 54 shown in FIG. 14. The functions of the stress data acquisition unit 22 and the operation history acquisition unit 23 of the engineering device 2 are realized by the processor 63 reading and executing a program stored in the memory 64.

The input device 65 is a device for inputting information to the engineering apparatus 2. A user operates the input device 65. The input device 65 is composed of a character input means and a pointing device. The input device 65 includes a keyboard, a mouse, a keypad, or a touch panel. The display device 66 displays various information. The display device 66 is, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display. The user interface unit 21 is realized by the input device 65 and the display device 66. The communication device 62 communicates with devices external to the engineering apparatus 2. Communication between the engineering apparatus 2 and the server apparatus 3 is realized by using the communication device 62.

Next, the hardware configuration of the terminal device 4 will be described. The terminal device 4 is realized by a hardware configuration similar to that shown in FIG. 15. Here, the hardware configuration of the terminal device 4 will be described with reference to FIG. 15. The user interface unit 41 is realized by an input device 65 and a display device 66. The terminal device 4 communicates with devices external to the terminal device 4 by means of a communication device 62. Communication between the terminal device 4 and the server device 3 is realized by using the communication device 62.

According to the first embodiment, the stress data analysis system 1 acquires stress data and analyzes the stress data to identify the cause of stress. The stress data analysis system 1 creates possible countermeasures for the cause, and updates the engineering tool by reflecting the countermeasures that have been decided upon for adoption. The stress data analysis system 1 is capable of collecting not only information about the operation of functions prepared in advance in the engineering tool, but also information in the flow of using the prepared functions, thereby making it possible to reduce or avoid stress in a user who continues to use the engineering tool. Reducing or avoiding user stress makes it possible to improve satisfaction in using the engineering tool. As a result, the stress data analysis system 1 has the effect of improving satisfaction in using the engineering tool.

The configurations shown in the above embodiments are examples of the contents of this disclosure. The configurations of the embodiments can be combined with other known technologies. Parts of the configurations of the embodiments can be omitted or modified without departing from the gist of this disclosure.

1 Stress data analysis system, 2 Engineering device, 2a Camera, 3 Server device, 4 Terminal device, 21, 41 User interface section, 22 Stress data acquisition section, 23 Operation history acquisition section, 31 Engineering tool section, 32 Stress data collection section, 33 Operation history collection section, 34 Data analysis section, 35 Countermeasure DB, 36 Update section, 51, 61 Processing circuit, 52, 62 Communication device, 53, 63 Processor, 54, 64 Memory, 65 Input device, 66 Display device, 341 Cause analysis section, 342 Countermeasure creation section, 343 Countermeasure classification section.

Claims

a stress data acquisition unit that acquires stress data regarding a stress state caused to a user who uses the engineering tool;
a cause analysis unit that identifies a part of the engineering tool that is a cause of stress in use of the engineering tool by analyzing the stress data;
A countermeasure creation unit that creates possible countermeasures for the cause;
an update unit that updates the engineering tool by reflecting the countermeasure that has been decided to be adopted in the engineering tool;
A stress data analysis system comprising:
The stress data analysis system according to claim 1, characterized in that the cause analysis unit identifies the cause by identifying a function or a function block in a program created using the engineering tool.
a presentation unit that presents the countermeasure created by the countermeasure creation unit and receives information indicating whether or not the presented countermeasure can be adopted;
2. The stress data analysis system according to claim 1, wherein the update unit reflects the countermeasure decided to be adopted by the presentation unit in the engineering tool.
a countermeasure classification unit that classifies and manages the countermeasures created by the countermeasure creation unit into essential countermeasures that need to be executed and temporary countermeasures that are the countermeasures other than the essential countermeasures;
4. The stress data analysis system according to claim 3, wherein the presentation unit presents a classification of the countermeasures created by the countermeasure creation unit.
The stress data analysis system according to claim 4, characterized in that the countermeasure classification unit changes the classification of the countermeasure from the temporary countermeasure to the essential countermeasure based on the outcome of implementing the countermeasure classified as the temporary countermeasure.
The stress data analysis system according to any one of claims 1 to 5, characterized in that the stress data includes information input by the user to a communication tool that accepts inquiries about the engineering tool.
The stress data analysis system according to any one of claims 1 to 5, characterized in that the stress data includes information obtained by observing the physical condition of the user.
The stress data analysis system according to any one of claims 1 to 5, characterized in that the stress data includes information indicating the operation content when an error occurs during use of the engineering tool.
The stress data analysis system according to any one of claims 1 to 5, characterized in that the stress data includes information indicating the content of an operation performed by the user when a specific event occurs in the operation performed by the user while using the engineering tool.
acquiring stress data regarding a stress situation caused to a user who uses the engineering tool;
identifying portions of the engineering tool that are causing stress in use of the engineering tool by analyzing the stress data;
generating possible countermeasures for the analyzed causes;
updating the engineering tool by reflecting the countermeasure that has been decided to be adopted in the engineering tool;
A stress data analysis method comprising:
acquiring stress data regarding a stress situation caused to a user who uses the engineering tool;
identifying portions of the engineering tool that are causing stress in use of the engineering tool by analyzing the stress data;
generating possible countermeasures for the identified causes;
updating the engineering tool by reflecting the countermeasure that has been decided to be adopted in the engineering tool;
A stress data analysis program that causes a computer to execute the above steps.