JP7333885B1 - STRESS DATA ANALYSIS SYSTEM, STRESS DATA ANALYSIS METHOD AND STRESS DATA ANALYSIS PROGRAM - Google Patents

Abstract

The stress data analysis system (1) includes a stress data acquisition unit (22) that acquires stress data regarding stress situations that occur to users who use engineering tools, and a stress data acquisition unit (22) that acquires stress data regarding stress situations that occur in users who use engineering tools. A cause analysis part identifies the parts by analyzing stress data, a countermeasure creation part creates possible countermeasures for the cause, and an engineering tool by reflecting the adopted countermeasures in the engineering tool. and an updating unit (36) for updating.

Description

The present disclosure relates to a stress data analysis system, a stress data analysis method, and a stress data analysis program for analyzing stress occurring in a user using an engineering tool.

2. Description of the Related Art In recent years, engineering software and other programming software are required to work more efficiently through intuitive operations as the software becomes more sophisticated. The engineering software is hereinafter referred to as an engineering tool. In order to enable intuitive operation of an engineering tool, it is desirable to be able to reduce the stress caused by the operation or to avoid the stress caused by the operation. In order to reduce stress or avoid stress, it is important to collect information when stress occurs and to utilize the collected information.

In Patent Document 1, a user's operation history regarding functions of a computer system is acquired, and if the operation history satisfies a dissatisfied condition indicating that the user is dissatisfied with the computer system, the operation history that satisfies the dissatisfied condition is disclosed. to a system developer's destination. In Patent Document 1, the computer system is a business 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 systems such as electronic medical record systems in which functions expected by user operations are determined in advance. A function expected by a user's operation is, for example, a function of acquiring an electronic medical chart. On the other hand, when the expected functions of the system are constructed by programming by the user, such as engineering tools, the route to realize the expected functions, for example, the programming method or the usage of the engineering tools, differs depending on the user. Therefore, in order to increase the satisfaction of engineering tools by reducing or avoiding stress, it is necessary to collect information not only on the operation of functions prepared in advance but also in the process of using the functions prepared in advance. necessary. In the technique described in Patent Document 1, there is a problem that it is difficult to improve satisfaction in using the engineering tool because information is not collected in the process of using the prepared functions. .

The present disclosure has been made in view of the above, and an object thereof is to obtain a stress data analysis system capable of improving satisfaction in using an engineering tool.

In order to solve the above-described problems and achieve the object, the stress data analysis system according to the present disclosure determines whether or not the user using the engineering tool is stressed. In such a case, a stress data acquisition unit that acquires stress data about the stress situation occurring in the user, and a cause that identifies the part of the engineering tool that is the cause of stress in the use of the engineering tool by analyzing the stress data. The analysis department, the countermeasure creation department that creates possible countermeasures for the identified cause , and the countermeasures created by the countermeasure creation department are divided into the essential countermeasures that need to be executed and the a countermeasure classifying unit that classifies countermeasures into temporary countermeasures that are countermeasures and stores information on the countermeasures, thereby classifying and managing the countermeasures into essential countermeasures and primary countermeasures; an updating unit that updates the engineering tool by reflecting the determined countermeasure on the engineering tool.

The stress data analysis system according to the present disclosure has the effect of improving satisfaction in using engineering tools.

1 is a diagram showing a configuration example of a stress data analysis system according to a first embodiment; FIG. FIG. 4 is a diagram showing a configuration example of an engineering device, a server device, and a terminal device of the stress data analysis system according to the first embodiment; FIG. 4 is a diagram showing a configuration example of a data analysis unit included in the server device of the stress data analysis system according to the first embodiment; 4 is a flow chart showing the procedure of the operation of the stress data analysis system according to the first embodiment; 4 is a flowchart showing the procedure of operations by the server device when executing a countermeasure registered as a temporary countermeasure in the first embodiment; 4 is a flow chart showing a first example of an operation procedure for acquiring data for analysis by the stress data analysis system according to the first embodiment; 4 is a flow chart showing a first example of an operation procedure for creating countermeasures and registering the created countermeasures by the server device of the stress data analysis system according to the first embodiment; 9 is a flowchart showing a second example of the procedure of operations for acquiring data for analysis by the stress data analysis system according to the first embodiment; 5 is a flow chart showing a second 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; 9 is a flow chart showing a third example of the procedure for acquiring data for analysis by the stress data analysis system according to the first embodiment; FIG. 10 is a flowchart showing a third example of an operation procedure for creating countermeasures and registering the created countermeasures by the server device of the stress data analysis system according to the first embodiment; FIG. 10 is a flowchart showing a fourth example of the procedure for acquiring data for analysis by the stress data analysis system according to the first embodiment; FIG. 10 is a flowchart showing a fourth example of an operation procedure for creating countermeasures and registering the created countermeasures by the server device of the stress data analysis system according to the first embodiment; FIG. FIG. 2 is a diagram showing a hardware configuration example of a server device that constitutes the stress data analysis system according to the first embodiment; FIG. 2 is a diagram showing a hardware configuration example of an engineering device that configures the stress data analysis system according to the first embodiment; FIG.

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

Embodiment 1.
FIG. 1 is a diagram showing a configuration example of a stress data analysis system 1 according to the first embodiment. The stress data analysis system 1 collects information about stress that occurs in users who use engineering tools, and provides countermeasures for stress reduction or stress avoidance.

A stress data analysis system 1 includes an engineering device 2 used by a user, a server device 3 that collects data and analyzes the collected 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 be a LAN (Local Area Network).

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

The engineering tool is a program creation support program that assists the creation of a program that is used by a control device that controls a control target device such as a robot to control the control target device. The controller is, for example, a programmable logic controller. In Embodiment 1, 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. The form of use of the engineering tool is not limited to SaaS, and may be a form in which the engineering tool is installed in the engineering device 2 and the engineering device 2 executes the engineering tool.

A user creates a program using an engineering tool by operating the engineering device 2 . A program created using an engineering tool is, for example, a ladder program. The engineering device 2 transmits to the server device 3 stress data about stress situations that occur in the user using the engineering tool. 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 the stress from the stress data and the operation history data, and prepares countermeasures that can be taken against the cause. The server device 3 transmits information indicating countermeasures to the terminal device 4 . The stress data analysis system 1 notifies the user of the countermeasure by transmitting information indicating the countermeasure from the server device 3 to the engineering device 2 .

The terminal device 4 presents the countermeasure created by the server device 3 . A person who decides which countermeasure to adopt decides whether or not to adopt the countermeasure presented by the terminal device 4 . The terminal device 4 transmits to the server device 3 information indicating whether or not to adopt the countermeasure. The server device 3 updates the engineering tool by reflecting the measures decided to be adopted in the engineering tool. The engineering device 2 utilizes 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 obtained by observing the user's physical condition. A camera 2a shown in FIG. 1 is an example of a device that acquires physical condition information of a user. The camera 2a photographs a user using the engineering device 2 and outputs physical condition information, which is image data of the user. Physical condition information is input to the engineering device 2 .

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

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

The stress data acquisition unit 22 acquires the stress data of the user who uses the engineering tool. The stress data acquiring unit 22 determines whether or not the user is stressed, and acquires stress data when it is determined that the user is stressed. 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 addition, 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 section 31 , a stress data collection section 32 , an operation history collection section 33 , a data analysis section 34 and an update section 36 . The server device 3 holds a countermeasure DB (DataBase) 35 . The engineering tool section 31 executes engineering tools 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 countermeasures according to the cause of stress. The data analysis unit 34 transmits countermeasure information to the terminal device 4 . The data analysis unit 34 outputs information on countermeasures to the countermeasure DB 35 . The server device 3 stores the created countermeasure in the countermeasure DB 35 .

The updating unit 36 reads information on countermeasures from the countermeasure DB 35 . The update unit 36 updates the engineering tool by reflecting the measures decided to be adopted in the engineering tool. Also, the update unit 36 transmits information indicating countermeasures to the engineering device 2 . The user interface unit 21 of the engineering device 2 receives the information indicating the countermeasure and displays the information indicating the countermeasure. As a result, the user is notified of countermeasures. By notifying the user of the countermeasure, it is possible to make the user aware of the countermeasure for stress reduction or stress avoidance.

The terminal device 4 has a user interface section 41 . The user interface unit 41 receives countermeasure information and displays the countermeasure information. Also, the user interface unit 41 receives an operation by the judge. The user interface unit 41 functions as a presentation unit that presents countermeasures created by the countermeasure creation unit in the data analysis unit 34 and receives 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 to the server device 3 information indicating whether or not the countermeasure can be adopted.

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

The updating unit 36 also acquires stress data from the stress data collecting unit 32 . The updating unit 36 checks whether there is a countermeasure corresponding to the acquired stress data by referring to the countermeasure information stored in the countermeasure DB 35 . If there is a countermeasure corresponding to the acquired stress data, the updating unit 36 reads information on the countermeasure corresponding to the acquired stress data from the countermeasure DB 35 and reflects the countermeasure in the engineering tool. The update unit 36 outputs information on the countermeasures reflected in the engineering tool to the data analysis unit 34 .

Here, the stress data will be explained. The stress data acquisition unit 22 can acquire stress data by 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 acquires stress data by two or more of the first to fourth acquisition methods. can be

In the first stress data acquisition method, the stress data acquisition unit 22 cooperates with an AI (Artificial Intelligence) chatbot, which is a communication tool for receiving inquiries about engineering tools. The AI chatbot outputs the answer to the question when the question is entered by the user. When the 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 entered by the user into the AI chatbot.

In the first acquisition method, the stress data acquisition unit 22 determines that an event causing stress to the user has occurred when the user inputs a question to the AI chatbot. In addition, the stress data acquiring unit 22 treats information input to the AI chatbot as stress data related to stress. The stress data acquisition unit 22 acquires input information when a question about how to use an engineering tool or a question about how to handle an error in an engineering tool is input to the AI chatbot. The stress data acquisition unit 22 may acquire input information when a request for improvement of an engineering tool is input to the AI chatbot.

In the second stress data acquisition method, the stress data acquisition unit 22 cooperates with a device that acquires the user's physical condition information. For example, the camera 2 a captures 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 a change in the user's physical condition or a change in the user's behavior from the image data. A change in the physical condition is, for example, a change in complexion. A change in behavior is, for example, a repeated action of poking the keyboard with a finger.

The stress data acquiring unit 22 determines that the user is stressed when a change in physical condition or behavior is detected. The stress data acquisition unit 22 acquires image data as stress data when it is determined that the user is stressed. The image data is physical condition information obtained by observing the user's physical condition. In a 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 may determine the presence or absence of stress based on the learning result.

Note that the physical condition information may be any information that can detect changes in the user's physical condition or behavior, and is not limited to image data obtained by shooting a moving image. A device that captures physical state information may include a microphone that captures audio. The stress data acquiring unit 22 may determine that the user is stressed when the user speaks or when the tone of the user's voice changes.

The stress data acquisition unit 22 constantly observes the user's physical condition based on the physical condition information while the user uses the engineering tool. When the stress data acquiring unit 22 determines that the user is under stress, it acquires physical condition information from a point in time prior to the point of time of determination as stress data. The stress data acquisition unit 22 transmits stress data to the server device 3 . When the stress data acquisition unit 22 determines that the user's stress has been eliminated, the stress data acquisition unit 22 stops transmitting the stress data to the server device 3 .

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

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

In the fourth stress data acquisition method, the stress data acquisition unit 22 determines that the user is stressed when no error has occurred but the user is having trouble creating the program. In the fourth acquisition method, the stress data includes information indicating details of the operation when a specific event occurs in the user's operation while using the engineering tool. A specific event is, for example, the time during which the user's operation is delayed in the case where the step in which the creation is being performed or the creation of the program in the step related to the step in which the creation is being performed is continued. exceeds a preset time. If you are unsure which one of the multiple functions of the engineering tool to use, or if you are unsure of which algorithm to use, the time required to restart the operation will be longer. The stress data acquiring unit 22 determines that the user has been stressed because the user has taken time to create the program when the time since the operation was stopped exceeds the set time.

It should be noted that the specific event may be any event that can be judged to require time and effort for the user to create the program, and is not limited to exceeding the preset time interval between operations. The specific event may be, for example, a continuous repetition of an operation and an undo of the operation.

Next, operation history data will be described. The operation history acquisition unit 23 acquires the history of 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 as operation history data. Always get.

When the stress data acquisition unit 22 determines that the user is stressed, the operation history acquisition unit 23 acquires the operation history data using the fact that the user is stressed as a trigger. to the server device 3. The operation history acquisition unit 23 transmits to the server device 3 the operation history data from the point in time prior to the point in time when it was determined that stress was occurring. The operation history acquisition unit 23 stops transmission of the operation history data to the server device 3 when the stress data acquisition unit 22 determines that the user's stress is relieved. The stress data analysis system 1 can search for causes that have contributed to the occurrence of stress by analyzing the operation history data from the time before 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 a configuration example of the data analysis section 34 included in the server device 3 of the stress data analysis system 1 according to the first embodiment. FIG. 3 shows the data analysis section 34, the countermeasure DB 35, and the user interface section 41 of the terminal device 4. As shown in FIG.

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 portion of the engineering tool that causes stress in the use of the engineering tool by analyzing the stress data.

The countermeasure creation unit 342 creates possible countermeasures for the cause identified by the cause analysis unit 341 . The countermeasure creation unit 342 may, for example, learn countermeasures that enable stress reduction or stress avoidance by 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 creating unit 342 may obtain the difference between the program created by the user and the program based on the learning result, and create the countermeasure based on the difference. As a countermeasure, the countermeasure creation unit 342 may create a tool or function that can guide a program created by the user to a program based on the learning result. A program based on learning results is a program that does not cause stress in creation or that can reduce stress in creation. Thereby, the countermeasure creation unit 342 can create a countermeasure that enables stress reduction or stress avoidance.

Countermeasures include, for example, a bug fix program for engineering tools, a recommended program recommendation function for engineering tools, or a recommended program recommendation function based on user-specific characteristics. Countermeasures may be, for example, changing the layout of function buttons, preparing function blocks, or automatically creating a program based on the specifications requested by the user. The automatic program creation function is a function for creating a program from characters.

The countermeasure classification unit 343 classifies and manages the countermeasures created by the countermeasure creation unit 342 into essential countermeasures that need to be executed and temporary countermeasures that are countermeasures other than essential countermeasures. . The essential countermeasures are countermeasures that should be executed without being affected by the user's usage conditions, or countermeasures that should be executed with a high frequency of stress. Examples of essential countermeasures are a bug fix program for an engineering tool, a recommended program recommendation function for an engineering tool, or a layout change of function buttons.

A temporary countermeasure is a countermeasure other than the essential countermeasure among the countermeasures created by the countermeasure creation unit 342, and is a countermeasure that can be taken as a temporary countermeasure against stress. Temporary workarounds include common workarounds and customized workarounds. Common countermeasures are countermeasures that are commonly applicable regardless of individuals or conditions. Customized countermeasures are countermeasures that can be applied after being customized according to individuals or conditions. Common countermeasures are also candidates for essential countermeasures. An example of a common countermeasure is the automatic program creation function based on user requirements. The program automatic creation function will be changed to an essential countermeasure by improving the accuracy of automatic creation. An example of a customization countermeasure is the ability to recommend programs that are recommended based on user-specific characteristics.

The countermeasure classifying unit 343 transmits the information on the countermeasure created by the countermeasure creating unit 342 and the category information of the countermeasure to the terminal device 4 . The category information is information indicating whether the countermeasure is classified into the essential countermeasure category or the temporary countermeasure category. The user interface unit 41 of the terminal device 4 presents countermeasures for each category. The decision maker inputs information indicating whether or not the presented countermeasure can be adopted to the user interface unit 41 . The user interface unit 41 transmits to the server device 3 information indicating whether or not the applicant can be employed. The countermeasure classifying unit 343 receives information indicating whether or not to adopt the countermeasure, and outputs information on the countermeasure decided to be adopted and category information to the countermeasure DB 35 . The countermeasure DB 35 stores countermeasure information for each category. Thereby, the countermeasure classifying unit 343 classifies the countermeasures created by the countermeasure creating unit 342 into essential countermeasures and temporary countermeasures and manages them.

If the judge wants to adopt a countermeasure classified as an essential countermeasure as a temporary countermeasure, he/she can instruct to change the category of the presented countermeasure 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 or not the proposed countermeasure can be adopted. The countermeasure classifying unit 343 changes the category of the countermeasure decided to be adopted from essential countermeasure to 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 countermeasure classified as the essential countermeasure and stored in the countermeasure DB 35, that is, the countermeasure registered as the essential countermeasure to the engineering tool. The stress data analysis system 1 can fundamentally avoid stress by applying essential countermeasures.

Further, when the stress data is acquired from the stress data collection unit 32, the updating unit 36 updates the countermeasures classified as temporary countermeasures and stored in the countermeasure DB 35, that is, the countermeasures registered as temporary countermeasures. From among them, confirm whether there are countermeasures corresponding to the acquired stress data. If there is a countermeasure corresponding to the acquired stress data, the updating unit 36 reads information on 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. This can prevent stress from accumulating.

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

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 acquiring unit 22 acquires stress data by determining that the user is stressed. The stress data acquisition unit 22 transmits the acquired stress data to the server device 3 . The stress data collector 32 receives stress data and collects the stress data. The engineering device 2 also 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 operation history data and collects the operation history data.

In step S2, the data analysis unit 34 of the server device 3 uses the cause analysis unit 341 to identify the cause of stress based on the stress data and the operation history data. 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 to identify the cause of stress.

In step S<b>3 , the data analysis unit 34 creates possible countermeasures for the identified cause by the countermeasure creation unit 342 . In step S<b>4 , the data analysis unit 34 classifies the countermeasures created in step S<b>3 by the countermeasure classification unit 343 . The countermeasure classifying unit 343 transmits information on the created countermeasure and category information on the countermeasure 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 the countermeasure information for each category based on the received countermeasure information and the received category information. The judge decides whether or not to adopt the presented countermeasure by inputting information indicating whether or not to adopt the countermeasure to the user interface unit 41 . The user interface unit 41 transmits to the server device 3 information indicating whether or not the countermeasure can be adopted.

The countermeasure classifying unit 343 receives information indicating whether or not to adopt the countermeasure, and outputs information on the countermeasure decided to be adopted and category information to the countermeasure DB 35 . In step S<b>6 , the server device 3 stores the information on the countermeasures in the countermeasure DB 35 , thereby registering the countermeasures decided to be adopted. Countermeasures are registered for each category based on the category information. When the countermeasure information is stored in the countermeasure DB 35, the countermeasure classification unit 343 notifies the updating unit 36 that the countermeasure information has been stored.

In step S7, the update unit 36 of the server device 3 updates the engineering tool by reflecting the registered countermeasures in the engineering tool. Upon receiving notification from the countermeasure classifying unit 343 that the countermeasure information has been stored, the updating unit 36 reads the countermeasure information registered as the essential countermeasure from the countermeasure DB 35 . As a result, the updating unit 36 reflects the countermeasures classified as essential countermeasures in the engineering tool. The engineering device 2 utilizes the updated engineering tool. With the above, the stress data analysis system 1 ends the operation according to the procedure shown in FIG.

Next, the operation of the server device 3 when executing a countermeasure registered as a temporary countermeasure will be described. FIG. 5 is a flow chart showing the procedure of operations by the server device 3 when executing a countermeasure registered as a temporary countermeasure in the first embodiment.

In step S<b>11 , the server device 3 collects stress data by the stress data collection unit 32 . The stress data collection unit 32 collects the stress data acquired by the stress data acquisition unit 22 upon determining that the user is stressed. The stress data collection unit 32 outputs the collected stress data to the data analysis unit 34 and the update unit 36, respectively.

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

In step S<b>13 , the server device 3 collects the stress data after executing the countermeasure in step S<b>12 by the stress data collection unit 32 . 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, the countermeasure information reflected in the engineering tool, and the stress data collected in step S13 are input to the data analysis unit . That is, the data analysis unit 34 stores stress data before the countermeasures registered as temporary countermeasures are executed, information on the countermeasures that have been executed, and stress data after the countermeasures are executed. is entered.

In step S<b>14 , the server device 3 determines whether or not the executed countermeasure is sufficient by the cause analysis unit 341 of the data analysis unit 34 . The cause analysis unit 341 determines whether the executed countermeasure is sufficient based on the stress data before the countermeasure registered as the temporary countermeasure is executed and the stress data after the countermeasure is executed. Decide whether it was a policy or not.

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

If it is determined that the executed countermeasure is sufficient (step S14, Yes), in step S15, the server apparatus 3 causes the countermeasure classification unit 343 of the data analysis unit 34 to perform the countermeasure executed in step S12. Change the category of countermeasures that have been identified from temporary countermeasures to essential countermeasures. Information on the executed countermeasures is classified into essential countermeasures and stored in the countermeasure DB 35 . In other words, the registration of the countermeasure is corrected to the registration as the essential countermeasure. In this way, the countermeasure classifying unit 343 changes the classification of the countermeasure from temporary countermeasure to essential countermeasure based on the result of executing the countermeasure classified as temporary countermeasure.

On the other hand, if it is determined that the executed countermeasure is not a sufficient countermeasure (step S14, No), in step S16, the server apparatus 3 corrects the countermeasure by the countermeasure creation unit 342 of the data analysis unit 34. . The countermeasure creation unit 342 acquires information on the countermeasure that has been executed, and divides the stress data before executing the countermeasure registered as a temporary countermeasure into the stress data after executing the countermeasure. Based on this, the countermeasures will be revised. The countermeasure creation unit 342 modifies the countermeasure to improve stress based on the change in the stress data before and after the countermeasure is executed. The corrected countermeasure information is stored in the countermeasure DB 35 .

By ending step S15 or step S16, the server device 3 ends the operation according to the procedure shown in FIG. The stress data analysis system 1 can reduce or avoid the stress of the 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. By reducing or avoiding user stress, satisfaction in using the engineering tool can be improved.

Next, the details of the operation of acquiring data for analysis in the data analysis unit 34 and the details of the operation of creating countermeasures by the data analysis unit 34 and registering the created countermeasures will be described. Here, when the stress data acquired for analysis is the stress data acquired by the above-described first acquisition method, when it is the stress data acquired by the above-described second acquisition method, The case of the stress data acquired by the third acquisition method and the case of the stress data acquired by the fourth acquisition method will be described.

FIG. 6 is a flow chart showing a first example of an operation procedure for acquiring data for analysis by the stress data analysis system 1 according to the first embodiment. FIG. 7 is a flow chart showing a first example of an operation 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. A first example shown in each of FIGS. 6 and 7 is an example of obtaining stress data by the first obtaining method.

In step S21 shown in FIG. 6, the stress data analysis system 1 uses the stress data acquisition unit 22 to determine whether an AI chatbot has been used. The use of the AI chatbot shall refer to inputting a question to the AI chatbot. For example, when a problem arises in creating a program using an engineering tool, the user inputs a question to the AI chatbot in order to solve the problem. If the AI chatbot is not used (step S21, No), the stress data analysis system 1 returns the procedure to step S21.

On the other hand, when the AI chatbot is used (step S21, Yes), the stress data analysis system 1 acquires the information input to the AI chatbot by the stress data acquisition unit 22 in step S22. The stress data acquisition unit 22 transmits stress data, which is information input to the AI chatbot, to the stress data collection unit 32 . The stress data acquiring unit 22 also acquires the information of the answers output by the AI chatbot in response to the input as stress data, and transmits the stress data to the stress data collecting 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, triggered by the determination that stress is occurring. That is, the operation history acquisition unit 23 transmits operation history data to the operation history collection unit 33 with the use of the AI chatbot as a trigger. In step S<b>23 , 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 . Operation history collection unit 33 collects operation history data and outputs the collected operation history data to cause analysis unit 341 .

In step S24, the stress data analysis system 1 acquires program creation status data by extracting the functions used in creating the program and the created program by the cause analysis unit 341. FIG. Based on the information input to the AI chatbot, the cause analysis unit 341 extracts the question theme part from the created program. The cause analysis unit 341 identifies the cause by identifying functions or function blocks in the program created using the engineering tool. Further, the cause analysis unit 341 extracts from the operation history data the functions used to create the relevant part of the program, such as functions such as copy, paste, function block, or icon installation. The program creation status data includes data indicating the extracted program and the extracted function. The cause analysis unit 341 associates stress data, which is information input to the AI chatbot and information output from the AI chatbot, and program creation status data, and stores them.

The user appropriately implements the measures indicated in the answers to the questions. For example, if the problem is not solved even after taking the measures indicated in the answer, the user makes an additional inquiry to the AI chatbot. In step S25, the stress data analysis system 1 uses the stress data acquisition unit 22 to determine whether additional information has been input to the AI chatbot. If additional information is input to the AI chatbot (step S25, Yes), the stress data analysis system 1 returns the procedure to step S22, and the stress data acquisition unit 22 acquires additional information.

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 whether a certain period of time has elapsed since the information was input to the AI chatbot. is determined by the stress data acquisition unit 22 . The fixed period is 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 the certain period of time has passed (step S26, Yes), the stress data acquisition unit 22 determines that the problem has been solved by taking the measures indicated in the reply. With the above, the stress data analysis system 1 ends the operation according to the procedure shown in FIG.

The server device 3 starts analysis of 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 the part related to the keyword included in the input information from the programming situation data, and searches for the cause of stress based on the extracted part. The cause analysis unit 341 regards the part of the program that was being created as the part that caused the user's question, and extracts the part related to the keyword. The cause analysis unit 341 extracts a program up to a certain number of steps from when information is input to 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 a useless part in comparison with the ideal program. Further, when the program created by the user has a useless portion, the cause analysis unit 341 searches for the cause of the useless portion. The ideal program is the algorithm on which it is based. If a program to be adopted in the program being created is suggested in the AI chatbot's response, the ideal program may be the program suggested in the response.

In step S33, the countermeasure creation unit 342 creates countermeasures for the stress causes found in steps S31 and S32. As countermeasures, for example, the creation of function blocks, which are program parts that can simplify program creation, the function of presenting function blocks to the user, or the function of guiding the user to the function that presents function blocks. can.

In step S34, the countermeasure classification unit 343 determines whether or not the countermeasure created in step S33 is an essential countermeasure. If the prepared countermeasure is an essential countermeasure (step S34, Yes), the countermeasure classifying unit 343 stores the information on the prepared countermeasure and the category information indicating that it is an essential countermeasure to the terminal device 4. Send to When the judgment person decides to adopt a 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 prepared countermeasure is not the essential countermeasure (step S34, No), the countermeasure classification unit 343 determines that the prepared countermeasure is a temporary countermeasure. The countermeasure classifying unit 343 transmits to the terminal device 4 category information indicating a temporary countermeasure together with information on the created countermeasure. When the judgment person decides 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.

It should be noted that if the measure classified as a temporary measure by the measure classification unit 343 is determined to be adopted as an essential measure by the judge, the measure classification unit 343 Register the workaround as an essential workaround. In addition, as shown in FIG. 5, the server device 3 searches for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and changes the registration of the countermeasure to the registration of the essential countermeasure. You can fix it.

FIG. 8 is a flow chart showing a second example of an operation procedure for acquiring data for analysis by the stress data analysis system 1 according to the first embodiment. FIG. 9 is a flow chart showing a second example of an operation 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. A second example shown in each of FIGS. 8 and 9 is an example of obtaining stress data by the second obtaining method.

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

On the other hand, when it is determined that the user is in a state of stress (step S41, Yes), the stress data analysis system 1 acquires physical condition information by the stress data acquiring section 22 in step S42. The stress data acquisition unit 22 transmits 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 .

The operation history acquisition unit 23 transmits operation history data to the operation history collection unit 33 when it is determined that the user is in a stressful state. In step S<b>43 , 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 . Operation history collection unit 33 collects operation history data and outputs the collected operation history data to 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 by the cause analysis unit 341. FIG. The cause analysis unit 341 extracts a portion of the program that was being created when it was determined that stress was occurring. Further, the cause analysis unit 341 extracts from the operation history data the functions used to create the part of the program. Cause analysis unit 341 stores stress data, which is physical condition information, and program creation situation data in association with each other.

In step S<b>45 , the stress data analysis system 1 selects a temporary countermeasure using the updating unit 36 and presents the selected temporary countermeasure using the user interface unit 41 . The updating unit 36 acquires stress data from the stress data collecting 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 updating unit 36 selects a countermeasure corresponding to the stress data from the countermeasures registered as temporary countermeasures. The countermeasure classification unit 343 transmits the information on the countermeasure selected by the update unit 36 and the category information indicating the temporary countermeasure to the user interface unit 41 of the terminal device 4 . When the judgment person decides to adopt the countermeasure, in step S46, the updating unit 36 reflects the decided temporary countermeasure on the engineering tool.

In a situation where an engineering tool reflecting a temporary countermeasure is used, in step S47, the stress data analysis system 1 determines whether or not the stress-causing state has been resolved by the stress data acquisition unit 22. . If it is determined that the stressed state has not been resolved (step S47, No), the stress data analysis system 1 returns the procedure to step S42, and causes the cause analysis unit 341 to analyze the stress data and the program creation status data. get. The cause analysis unit 341 stores the stress data and the program creation status data in association with each other. On the other hand, when it is determined that the stressed state has been resolved (step S47, Yes), the stress data analysis system 1 terminates the operation according to the procedure shown in FIG.

The server device 3 starts analysis of 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 the portion corresponding to the time when the physical condition changed from the program creation situation data, and searches for the cause of stress based on the extracted portion. The cause analysis unit 341 extracts the part corresponding to the point in time when the physical state changed, assuming that the stress occurred from the point in time when the physical state changed.

The cause analysis unit 341 determines whether or not the program created by the user has a useless part in comparison with the ideal program. Further, when the program created by the user has a useless portion, the cause analysis unit 341 searches for the cause of the useless portion.

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

In step S54, the countermeasure classification unit 343 determines whether or not the countermeasure created in step S53 is an essential countermeasure. If the prepared countermeasure is an essential countermeasure (step S54, Yes), the countermeasure classification unit 343 stores category information indicating that it is an essential countermeasure together with information on the prepared countermeasure to the terminal device 4. Send to When the judgment person decides 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 prepared countermeasure is not the essential countermeasure (step S54, No), the countermeasure classification unit 343 determines that the prepared countermeasure is a temporary countermeasure. The countermeasure classifying unit 343 transmits to the terminal device 4 category information indicating a temporary countermeasure together with information on the created countermeasure. When the judgment person decides to adopt the countermeasure, in step S56, the countermeasure classification unit 343 registers the countermeasure created in step S53 as a temporary countermeasure. As described above, the server device 3 completes the operation according to the procedure shown in FIG.

It should be noted that, if the measure classified as a temporary measure by the measure classification unit 343 is determined to be adopted as an essential measure by the judge, the measure classification unit 343 Register the workaround as an essential workaround. In addition, as shown in FIG. 5, the server device 3 searches for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and changes the registration of the countermeasure to the registration of the essential countermeasure. You can fix it.

FIG. 10 is a flow chart showing a third example of an operation procedure for acquiring data for analysis by the stress data analysis system 1 according to the first embodiment. FIG. 11 is a flow chart showing a third example of an operation 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 third example shown in each of FIGS. 10 and 11 is an example of obtaining stress data by the third obtaining method.

In step S61 shown in FIG. 10, the stress data analysis system 1 uses the stress data acquiring section 22 to determine whether an error has occurred in the use of the engineering tool. The stress data acquiring unit 22 regards the case where an error occurs in the use of the engineering tool as the case where the user is stressed. 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 has occurred (step S61, Yes), the stress data analysis system 1 acquires an error log using the stress data acquiring section 22 in step S62. The stress data acquisition unit 22 transmits stress data, which is an 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 .

The operation history acquisition unit 23 transmits operation history data to the operation history collection unit 33, triggered by the occurrence of an error in the use of the engineering tool. In step S<b>63 , 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 . Operation history collection unit 33 collects operation history data and outputs the collected operation history data to 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 by the cause analysis unit 341. FIG. The cause analysis unit 341 extracts the portion of the program that was being created when the error occurred. Further, the cause analysis unit 341 extracts from the operation history data the functions used to create the part of the program. Cause analysis unit 341 stores stress data, which is an error log, and program creation status data in association with each other.

In step S<b>65 , the stress data analysis system 1 selects a temporary countermeasure using the updating unit 36 and presents the selected temporary countermeasure using the user interface unit 41 . When the judgment person decides to adopt the countermeasure, in step S66, the update unit 36 reflects the decided temporary countermeasure on the engineering tool. Details of steps S65 and S66 are the same as those of steps S45 and S46 shown in FIG.

In a situation where an engineering tool reflecting a temporary countermeasure is used, in step S67, the stress data analysis system 1 determines whether or not the error has been resolved by the stress data acquiring section 22. If it is determined that the error has not been resolved (step S67, No), the stress data analysis system 1 returns the procedure to step S62, and causes the cause analysis section 341 to acquire stress data and program creation status data. 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.

The server device 3 starts analysis of 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 related to the error from the program creation situation data, and searches for the cause of the stress based on the extracted part. The cause analysis unit 341 extracts the portion related to the error, assuming that the stress has occurred from the time the error occurred.

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

In step S74, the countermeasure classification unit 343 determines whether or not the countermeasure created in step S73 is an essential countermeasure. If the prepared countermeasure is an essential countermeasure (step S74, Yes), the countermeasure classifying unit 343 stores the information on the prepared countermeasure and the category information indicating that it is an essential countermeasure to the terminal device 4. Send to When the judgment person decides to adopt a 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 prepared countermeasure is not the essential countermeasure (step S74, No), the countermeasure classification unit 343 determines that the prepared countermeasure is a temporary countermeasure. The countermeasure classifying unit 343 transmits to the terminal device 4 category information indicating a temporary countermeasure together with information on the created countermeasure. When the judgment person decides to adopt the countermeasure, in step S76, the countermeasure classification unit 343 registers the countermeasure created in step S73 as a temporary countermeasure. As described above, the server device 3 ends the operation according to the procedure shown in FIG. 11 .

It should be noted that if the measure classified as a temporary measure by the measure classification unit 343 is determined to be adopted as an essential measure by the judge, the measure classification unit 343 Register the workaround as an essential workaround. In addition, as shown in FIG. 5, the server device 3 searches for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and changes the registration of the countermeasure to the registration of the essential countermeasure. You can fix it.

FIG. 12 is a flowchart showing a fourth example of the procedure of operations for acquiring data for analysis by the stress data analysis system 1 according to the first embodiment. FIG. 13 is a flowchart showing a fourth example of an operation 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. A fourth example shown in each of FIGS. 12 and 13 is an example of obtaining stress data by the fourth obtaining method.

In step S81 shown in FIG. 12, the stress data analysis system 1 uses the stress data acquiring section 22 to determine whether or not an alarm has occurred during use of the engineering tool. The engineering tool generates an alarm when a specific event occurs in the user's operation during use of the engineering tool. For example, the engineering tool generates an alarm when the time from when the operation by the user is stopped exceeds a preset time. The stress data acquiring unit 22 considers that the user is stressed when an alarm occurs during the use of the engineering tool. If no alarm has 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), the stress data analysis system 1 acquires alarm information by the stress data acquiring section 22 in step S82.

The alarm information includes, for example, the time when the operation was started, the time when the alarm was generated, the time when the operation was finished if the operation was finished, the step at which the operation was delayed, or the program number at which the operation was delayed. Contains information about the causative event. The stress data acquisition unit 22 transmits stress data, which is 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, triggered by the occurrence of an alarm during use of the engineering tool. In step S<b>83 , 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 . Operation history collection unit 33 collects operation history data and outputs the collected operation history data to cause analysis unit 341 .

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

In step S<b>85 , the stress data analysis system 1 selects a temporary countermeasure using the updating unit 36 and presents the selected temporary countermeasure using the user interface unit 41 . When the judgment person decides to adopt the countermeasure, in step S86, the update unit 36 reflects the decided temporary countermeasure on the engineering tool. Details of steps S85 and S86 are the same as those of steps S45 and S46 shown in FIG.

In a situation where an engineering tool reflecting a temporary countermeasure is used, in step S87, the stress data analysis system 1 determines by the stress data acquiring section 22 whether or not the alarm has been cancelled. 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 causes the cause analysis section 341 to acquire stress data and program creation status data. 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 canceled (step S87, Yes), the stress data analysis system 1 ends the operation according to the procedure shown in FIG.

The server device 3 starts analysis of 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 part related to the alarm from the program creation status data, and searches for the cause of stress based on the extracted part. The cause analysis unit 341 extracts a part related to the alarm, assuming that the stress is generated from the time when the event that caused the alarm occurs. The point in time when the event causing the alarm occurs is, for example, the point in time when the operation is stopped.

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

In step S94, the countermeasure classification unit 343 determines whether or not the countermeasure created in step S93 is an essential countermeasure. If the prepared countermeasure is an essential countermeasure (step S94, Yes), the countermeasure classifying unit 343 stores information on the prepared countermeasure and category information indicating that it is an essential countermeasure to the terminal device 4. Send to When the judgment person decides to adopt a 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 prepared countermeasure is not the essential countermeasure (step S94, No), the countermeasure classification unit 343 determines that the prepared countermeasure is a temporary countermeasure. The countermeasure classifying unit 343 transmits to the terminal device 4 category information indicating a temporary countermeasure together with information on the created countermeasure. When the judgment person decides to adopt the countermeasure, in step S96, the countermeasure classification unit 343 registers the countermeasure created in step S93 as a temporary countermeasure. Thus, the server device 3 ends the operation according to the procedure shown in FIG. 13 .

It should be noted that, if the measure classified as a temporary measure by the measure classification unit 343 is determined to be adopted as an essential measure by the judge, the measure classification unit 343 Register the workaround as an essential workaround. In addition, as shown in FIG. 5, the server device 3 searches for the cause of stress when executing a countermeasure registered as a temporary countermeasure, and changes the registration of the countermeasure to the registration of the essential countermeasure. You can fix it.

The stress data analysis system 1 identifies the cause of stress in the use of engineering tools based on the stress data and program creation status data. The stress data analysis system 1 can identify the portion of the engineering tool that causes stress. The stress-causing portion of the engineering tool is, for example, the function of the engineering tool that causes stress to the user.

The stress data analysis system 1 creates countermeasures that can be taken for the identified cause, and reflects the countermeasures that have been decided to be adopted in the engineering tool. In addition, the stress data analysis system 1 classifies the prepared countermeasures into essential countermeasures and temporary countermeasures and manages them. The stress data analysis system 1 can fundamentally avoid stress by applying countermeasures classified as essential countermeasures. The stress data analysis system 1 can reduce stress and prevent accumulation of stress by applying temporary countermeasures.

The stress data analysis system 1 improves the engineering tool as needed by applying countermeasures, thereby increasing satisfaction in using the engineering tool. The stress data analysis system 1 can create a countermeasure according to the unique characteristics of the user by having the categories of temporary countermeasures. The stress data analysis system 1 changes the category of countermeasures sufficient for the user from temporary countermeasures to essential countermeasures, thereby making it possible to fundamentally avoid stress according to the characteristics of the user. .

In the first embodiment, when stress data is acquired, the stress data analysis system 1 may give points according to the stress data to the user or the like based on preset rules. The rules are, for example, giving a number of points according to the number of acquisitions of stress data, or giving a number of points according to the importance of stress-based defects.

In the first embodiment, the stress data analysis system 1 targets the engineering tool for stress analysis and countermeasure creation, but the target may be programming software other than the engineering tool. A program created using programming software is not limited to a ladder program written using a ladder language, and may be a program written in a programming language other than the ladder language.

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

Each of the engineering tool unit 31, the stress data collection unit 32, the operation history collection unit 33, the data analysis unit 34, and the update unit 36 of the server device 3 is configured by software, firmware, or a combination of software and firmware. Realized. Software or firmware is written as a program and stored in memory 54 . In the processing circuit 51 , the processor 53 reads out and executes the programs stored in the memory 54 , thereby realizing the functions of the respective units of the server device 3 . That is, the processing circuit 51 includes a memory 54 for storing a program that results 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 stress data analysis system 1 .

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

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

The program stored in the memory 54 may be written in a storage medium such as a CD (Compact Disc)-ROM, a DVD (Digital Versatile Disc)-ROM, or the like, and may be provided via a communication line. It may be in the form of being provided by

Each unit provided in the server device 3 in the first embodiment may be realized by two or more devices arranged at mutually different positions. Each of the two or more devices is implemented by, for example, the hardware configuration shown in FIG. Two or more devices are communicatively connected to 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 explained. FIG. 15 is a diagram showing a hardware configuration example of the engineering device 2 that configures the stress data analysis system 1 according to the first embodiment. The engineering device 2 is realized by a computer system comprising a processing circuit 61, a communication device 62, an input device 65, and a display device 66.

The processing circuitry 61 comprises a processor 63 and memory 64 . Processing circuit 61 is a circuit in which processor 63 executes software. Processor 63 and memory 64 are assumed to be similar to processor 53 and memory 54 shown in FIG. 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 out and executing programs stored in the memory 64 .

The input device 65 is a device for inputting information to the engineering device 2 . A user operates the input device 65 . The input device 65 is composed of character input means and a pointing device. The input device 65 includes a keyboard, mouse, keypad, touch panel, or the like. 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 section 21 is implemented by the input device 65 and the display device 66 . The communication device 62 communicates with devices external to the engineering device 2 . Communication with the server device 3 by the engineering device 2 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 implemented by a hardware configuration similar to the hardware configuration shown in FIG. Here, the hardware configuration of the terminal device 4 will be described with reference to FIG. The user interface unit 41 is implemented by the input device 65 and the display device 66 . The terminal device 4 communicates with devices external to the terminal device 4 through the communication device 62 . Communication with the server device 3 by the terminal device 4 is realized by using the communication device 62 .

According to Embodiment 1, the stress data analysis system 1 acquires stress data and identifies the cause of stress by analyzing the stress data. The stress data analysis system 1 creates countermeasures that can be taken against the cause, and updates the engineering tools by reflecting the countermeasures decided to be adopted in the engineering tools. The stress data analysis system 1 can collect not only information about the operation of the function prepared in advance in the engineering tool, but also information in the flow of using the prepared function, thereby improving the use of the engineering tool. It is possible to reduce or avoid the stress of the user who continues to By reducing or avoiding user stress, satisfaction in using the engineering tool can be improved. As described above, the stress data analysis system 1 has the effect of improving satisfaction in the use of engineering tools.

The configuration shown in the above embodiment shows an example of the content of the present disclosure. The configuration of the embodiment can be combined with another known technique. A part of the configuration of the embodiment can be omitted or changed without departing from the gist of the present disclosure.

1 stress data analysis system 2 engineering device 2a camera 3 server device 4 terminal device 21, 41 user interface unit 22 stress data acquisition unit 23 operation history acquisition unit 31 engineering tool unit 32 stress data collection unit , 33 operation history collection unit, 34 data analysis unit, 35 countermeasure DB, 36 update unit, 51, 61 processing circuit, 52, 62 communication device, 53, 63 processor, 54, 64 memory, 65 input device, 66 display device , 341 cause analysis unit, 342 countermeasure creation unit, and 343 countermeasure classification unit.

Claims (11)

a stress data acquisition unit that determines whether or not a user using the engineering tool is stressed, and acquires stress data about the stress situation of the user when it is determined that the user is stressed;
A cause analysis unit that identifies a portion of the engineering tool that causes stress in the use of the engineering tool by analyzing the stress data;
a countermeasure creation unit that creates countermeasures that can be taken against the identified cause;
classifying 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, and obtaining information on the countermeasures; a countermeasure classification unit that classifies and manages the countermeasures into the essential countermeasures and the temporary countermeasures by storing them;
an updating unit that updates the engineering tool by reflecting the countermeasure decided to be adopted in the engineering tool;
A stress data analysis system comprising: 2. The stress data analysis system according to claim 1, wherein said cause analysis unit identifies said cause by identifying a function or function block in a program created by using said 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 updating unit reflects the countermeasures decided to be adopted by the presenting unit in the engineering tool. 4. The stress data analysis system according to claim 3, wherein the presenting unit presents the classification of the countermeasures created by the countermeasure creating unit. The countermeasure classifying unit changes the classification of the countermeasure from the temporary countermeasure to the essential countermeasure based on a result of executing the countermeasure classified as the temporary countermeasure. The stress data analysis system according to claim 1 , characterized by: 6. The stress data analysis system according to any one of claims 1 to 5, wherein the stress data includes information input by the user to a communication tool that receives inquiries about the engineering tool. 6. The stress data analysis system according to any one of claims 1 to 5, wherein the stress data includes information obtained by observing the user's physical condition. 6. The stress data analysis system according to any one of claims 1 to 5, wherein said stress data includes information indicating details of operation when an error occurs in use of said engineering tool. 6. The stress data according to any one of claims 1 to 5, wherein the stress data includes information indicating details of the operation when a specific event occurs in the operation by the user in using the engineering tool. Stress data analysis system. a step of determining whether or not a user using the engineering tool is stressed, and when it is determined that the user is stressed, obtaining stress data about the stress situation of the user;
identifying portions of the engineering tool that are responsible for stress in the use of the engineering tool by analyzing the stress data;
creating possible remedies for the identified causes;
classifying the created countermeasures into essential countermeasures that need to be executed and temporary countermeasures that are the countermeasures other than the essential countermeasures;
registering the countermeasures decided to be adopted for each category of the essential countermeasures and the temporary countermeasures by storing information of the countermeasures decided to be adopted;
a step of updating the engineering tool by reflecting the countermeasure decided to be adopted in the engineering tool;
A stress data analysis method comprising: a step of determining whether or not a user using the engineering tool is stressed, and when it is determined that the user is stressed, obtaining stress data about the stress situation of the user;
identifying portions of the engineering tool that are responsible for stress in the use of the engineering tool by analyzing the stress data;
creating possible remedies for the identified causes;
classifying the created countermeasures into essential countermeasures that need to be executed and temporary countermeasures that are the countermeasures other than the essential countermeasures;
registering the countermeasures decided to be adopted for each category of the essential countermeasures and the temporary countermeasures by storing information of the countermeasures decided to be adopted;
a step of updating the engineering tool by reflecting the countermeasure decided to be adopted in the engineering tool;
A stress data analysis program characterized by causing a computer to execute

Images