JPH09114708A - Operation history collection controlling method of operator in human interface terminal and device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically collect only necessary information from the operation history of an operator and to efficiently execute the control/analysis of an operation history by using the specified operator operation history collection controlling system in a human interface terminal. SOLUTION: An operation history collection level decision part 1 refers to an operation level file 11 by an operator name and decides the collection level of the operation history according to the level of the operator. An operation history collection decision part 2 refers to an operation history collection item setting file 12 and designates the presence/absence of the collection of the operation history and the collection item of the operation history. A request contents delivering part 4 receives the request issued for every screen and performs a delivering processing by performing a screen operation by the operator. An operation history calculation part 5 determines the operation history according to the collection setting from screen request contents. An operation history storage part 6 additionally writes/holds the operation history of the screen determined by the operation history calculation part 5 for every screen ID in a timewise order.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and a device for collecting and managing an operation history of an operator in a human interface (HMI) terminal, and more particularly to feedback of a usage pattern / situation of an operator in an operation system (OpS). , A method and apparatus for collecting and managing an operator's operation history in an HMI terminal for surely collecting and efficiently analyzing an operator's operation history necessary for grasping data rewriting responsibility, isolating problems during debugging, etc. Regarding

[0002] In OpS, an operation function is created based on the business flow of the service.
It is important to feed back the usage pattern / situation of the operator who operates the MI terminal and reflect it in the operation function of the system. In addition, since the OpS rewrites data in a common database (DB) from a plurality of HMI terminals by a plurality of operators, it is necessary to ensure that the changer can correspond to the changer in terms of security. is important. Furthermore, OpS
When debugging, it is desirable to be able to isolate and manage whether the problem is due to an operator error or a system bug.

[0003]

2. Description of the Related Art Conventionally, in order to verify the appropriateness of an operation function and the like, there is a method of investigating by a subjective evaluation experiment / questionnaire when grasping the usage form of an operator. Further, when it is necessary to check the rewriting of data, there is a method of estimating the person who changed the data at that time from the information such as the update date and time of the data and inquiring about the changed content.

Further, when a failure occurs in the system during the operation of the operator, the operation log is acquired, and the log information relating to the operation of the operator is acquired from the operation log, or the reproduction test is performed to solve the problem. Divide / cause analysis.

[0005]

However, the above conventional method has the following problems. The information is inaccurate because the operation history of the desired operator cannot be automatically collected. I can't easily set whether to get the operation history. Even if the operation log is taken, the information other than the operator's operation is collected, and the amount of information increases. It is necessary to consider how to store / save when the amount of information becomes large. It is difficult to extract necessary information such as log information of a specific operator from the collected operation history, and the analysis takes time. It is unclear how to understand the responsibility for data rewriting.

The present invention has been made in view of the above points, and can automatically collect the operation history of an operator in an HMI terminal and accurately collect only necessary information as a fixed format, and is useless in managing the operation history. There is no analysis /
An object of the present invention is to provide an operator operation history collection management method and device in an HMI terminal that enables efficient analysis and makes it clear that data changes are managed.

[0007]

FIG. 1 is a diagram for explaining the principle of the present invention. In the present invention, an operator is a human interface terminal (hereinafter referred to as an HMI terminal).
In the operator operation history collection management method in the HMI terminal for collecting the operation history using, the operation level of the operator is determined (step 1), and the operation history collection items to be collected among the operation history information are collected based on the operation level. When the operator decides (step 2) and issues a request for each screen (step 3), the operation history for each screen is generated by referring to the operation history collection item (step 4), and the generated operation history is stored in a file. Store (step 5).

Further, according to the present invention, when an operation request is issued from the screen of the HMI terminal, the operation request information is sorted for each screen identifier of each screen, operation history information is calculated for each screen identifier of the request, and each screen identifier of the request is calculated. The operation history information is held in the table, and when the screen request is completed, the held operation history information for each screen identifier is collectively written in the file corresponding to the screen identifier.

Further, according to the present invention, the HMI is set by the operator.
When an operation request is issued from the screen of the terminal, the operation history information is sorted for each screen identifier of each screen, operation history information is calculated for each screen identifier of the request, and a file to be written is determined for each screen identifier. Additional writing to.

Further, according to the present invention, the HMI is set by the operator.
When a request for the screen is issued from the screen of the terminal, operation history information is calculated for each request, the screen identifier is determined from the operation history information, and additional writing is performed in the file corresponding to the determined screen identifier.

Further, according to the present invention, the time when the operation history information is generated and the screen identifier are used as the file name of the file.
Further, according to the present invention, the elapsed time after the operation history information is written in the file is acquired by referring to the file name, and when the predetermined time has elapsed, the file is deleted.

Further, according to the present invention, when a plurality of screens can be activated, a unique screen identifier is given to the screens.
FIG. 2 is a block diagram showing the principle of the present invention. The present invention is based on HMI
In the operator operation history collection management device in the HMI terminal for generating and managing the operation history of the operator who operates the terminal, when the operator starts up the HMI terminal, the operation history collection level according to the operator's level is determined An operation history collection level determining unit 1, an operation history collection determining unit 2 that specifies whether to collect operation history and operation history collection items, and an operation history collection setting storage unit 3 that holds collection setting items. An operator receives a request for each screen input by operating the screen, and refers to the request content distribution unit 4 for distributing and processing the request and the operation history collection setting storage unit 3 to make a request for each screen. A plurality of operation history calculating means 5 for obtaining an operation history according to the collection setting item from the contents, and those obtained by the operation history calculating means 5. A plurality of operation history storage means 6 for adding and collecting operation histories, and an operation history storage means 7 for saving the operation history acquired from the operation history storage means 6 as a separate file when the request for each screen is completed. When,
And a control means 8 for controlling each means.

Further, according to the present invention, in an operator operation history collection management device in an HMI terminal for generating and managing an operation history of an operator who operates the HMI terminal, when the operator starts up the HMI terminal, the operator level Operation history collection level determining means for determining the collection level of the operation history according to the operation history, and operation history collection determining means for specifying whether or not the operation history is collected and operation history collection items,
Operation history collection setting storage means for holding collection setting items, request content distribution means for receiving a request for each screen input by an operator performing screen operation, and operation history collection A plurality of operation history calculation means for obtaining an operation history corresponding to the collection setting item from the request content for each screen with reference to the setting storage means,
An operation history distribution unit that allocates the operation history generated by the operation history calculation unit to each screen, and an operation history storage that sequentially stores the operation history distributed by the operation history distribution unit by additionally writing to a corresponding file for each screen It has a means and a control means which controls each means.

According to the present invention, in an operator operation history collection management device in an HMI terminal for generating and managing an operation history of an operator who operates an HMI terminal, when the operator starts up the HMI terminal, the operator operation history collection management apparatus can be operated according to the level of the operator. Operation history collection level determining means for determining the operation history collection level, operation history collection determining means for specifying whether or not operation history collection is performed, and operation history collection items, and operation history collection for holding collection setting items An operation history calculation unit that obtains an operation history corresponding to a collection setting item for each screen by referring to the setting storage unit and the operation history collection setting storage unit, and an operation history generated by the operation history calculation unit as a screen identifier The operation history distribution means for allocating each file by and the operation history distributed by the operation history distribution means It has an operation history storage means for storing the additional writing in response to the file, and control means for controlling each unit.

The above-mentioned operation history storage means makes the patterns of items stored in the file common. The operation history calculation means refers to the operation history collection setting storage means at regular intervals. The operation history storage means includes a setting item for setting the collected operation history information so that the collected operation history information can be erased after a predetermined time elapses.

The above operation history storage means allocates one file for each screen identifier. Further, the operation history distribution means allocates one file for each screen identifier. As described above, the present invention manages the operation level of each operator who operates the HMI terminal and determines the operation history collection item according to the operation level, so that only the necessary items can be acquired as the operation history information. Is.
Further, the amount of information to be collected can be adjusted by changing the definition of the operation history collection item in various ways.

Further, since the unit of collecting the operation history is one screen identifier (hereinafter, ID) unit, even when a plurality of same screens are used, by using the screen IDs given to the respective screens, Since it is possible to acquire the operation history of each operator and the history information of various screens is not mixed, it is easy to search the history information if it is possible to know which screen is used later. .

When the generated operation history information is managed as a file, the file name is set by using the generation date and screen ID of the file, so that the file is generated by simply referring to the file name. I can grasp. Therefore, when the operation history information becomes huge,
Files that have been created for a long time can be deleted by specifying the date and time. Also, at regular intervals,
It can also be built to automatically delete old files.

As a method of accumulating operation history information, as soon as a request for a screen is received from an operator, it is sorted by screen ID, an operation history is calculated for each screen ID, and when the request for the screen ID is completed. so,
Method of collectively outputting to file; Method of sorting by screen ID as soon as a screen request is received from the operator, calculating operation history for each screen ID, and sequentially performing additional writing to the file for each screen ID; Operator When the screen request is received from the screen, the operation history is generated in the order in which the request is made without sorting by the screen ID, the screen ID is determined, and the operation history is sorted into the screen ID based on the determination result. Since there is a method of storing in a corresponding file, various configurations are possible depending on the resource of the device.

Further, since it is possible to define the collection method in the operation history collection item for determining whether or not to collect the operation history, the permission / stop of the operation history collection is also referred to at a predetermined cycle or at an arbitrary timing. It becomes possible by doing. According to the above method, it becomes possible to automatically collect only the necessary items at that time in the fixed format of the operation history of the operator.

Further, since only the necessary operation history information is managed using the operation history collection item information, there is no extra information and the search time can be shortened. Moreover, since the management information of the operator is managed in a fixed format, analysis / analysis can be performed efficiently.

[0022]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below. The present invention is to acquire the operation history information of the operator in the HMI terminal that outputs the acquired information by performing the DB access by the input operation.

FIG. 3 is a diagram for explaining the function of the HMI terminal of the present invention. When the HMI terminal makes a data request to the screen control module by the input operation of the operator, the screen control module activates the screen corresponding process, shapes it, and outputs it. In addition, the request issuing module converts the data request input by the operator into a database access format and requests the DB access process. As a result, the DB access process allocates the request to the corresponding DB for access. Further, the DB access process receives data from each DB, sorts the data for each corresponding screen ID, and transfers the data to the request receiving module. The request receiving module activates the screen corresponding process, and the screen control module shapes and outputs the data.

According to the present invention, H which realizes the function as shown in FIG.
The MI terminal collects and manages the operation history of the operator. First, the first embodiment will be described. FIG.
FIG. 3 shows a configuration of an operator operation history collection / management device in the HMI terminal according to the first embodiment of the present invention. The operation history collection management device shown in FIG.
Operation history collection determination unit 2, operation history collection setting storage file 3, request content distribution unit 4, operation history calculation unit 5 set for each screen ID, operation history storage unit 6 set for each screen ID, operation history Storage unit 7 and control unit 8, operation level file 11, operation history collection item setting file 12, and screen I
It is composed of a plurality of operation history files 13 set for each D.

When the operator starts up the HMI terminal, the operation history collection level determination unit 1 refers to the operation level file 11 by the operator name and determines the operation history collection level according to the operator's level. The operation history collection determination unit 2 uses the operation history collection item setting file 12
Specify whether to collect the operation history and specify the operation history collection items by referring to. That is, the operation history is collected according to this operation history collection item.

The operation history collection setting storage file 3 holds the collection level of the operator judged by the operation history collection level judgment unit 1 and the presence / absence of collection / collection items which are the judgment results of the operation history collection judgment unit 2. . Request content distribution unit 4
The operator performs a screen operation to receive a request issued for each screen, determines to which operation history calculation unit 5 the request is transferred based on the screen ID, and distributes the request.

The operation history calculation unit 5 obtains an operation history according to the collection setting from the screen request contents distributed by the request content distribution unit 4 on a screen ID basis. In addition, at the time of first activation and when the request content regarding a new screen ID is transferred, a new operation history calculation unit 5 for the screen ID is generated. That is, when there are three requests with different screen IDs, three types of operation history calculation units 5 are generated. Further, when all the relevant screen requests have been processed, these operation history calculation units 5 are deleted.

The operation history storage unit 6 additionally writes and holds the operation history of the screen obtained by the operation history calculation unit 5 in order of time for each screen ID. When the operation history stored in the operation history storage unit 6 is transferred at the time when all screen requests are completed, the operation history storage unit 7 collectively writes the operation history to the operation history file 13 set for each screen ID. .

The control unit 8 communicates and controls each processing unit.
The operation level file 11 is, as shown in FIG. 5 and FIG.
The operation level for each operator and the contents that can be operated at the operation level are shown. As shown in FIGS. 7 to 10, the operation history collection item setting file 12 stores the presence / absence of operation history collection and operation history collection items. The operation history file 13 stores the operation history information generated for each screen ID in time series. 11 and 12 show examples of the operation history file 13 generated in the standard format of the present invention. The example shown in FIG. 11 is an operation history when the operator presses a button or the like to set conditions. The operation history information shown in the figure includes operator name, date and time, and screen I.
D, pressed button name, setting conditions at the time of pressing, and the like. FIG.
Is an operation history when the operator takes an action for the information on the screen. The operation history information shown in the figure includes an operator name, date and time, screen ID, action type, setting conditions at the time of action, and the like.

Next, the detailed operation of the management device will be described. FIG. 13 is a diagram for explaining the operation of the first mode of the present invention. Step 101) First, the operation history collection level determination unit 1
When the HMI terminal is started up, the level of the operator is determined by referring to the operation level file (for each operator) 11 which holds the level of the operator with the inputted operator name.

Step 102) Further, the operation history collection level judgment unit 1 judges the collection level according to the operation level of the operator by referring to the operation level file (by level) 11 according to the level judged in Step 101,
The collection level is transferred to the operation history collection setting storage file 3.

The operator levels determined in the above step 101 are classified as shown in FIG. 5, and the operation levels of the operator are classified as shown in FIG. Step 103) Next, the operation history collection determining unit 2 determines the operation collection file 12 that holds the collected contents of the operation history.
By referring to, the presence / absence of the operation history and the collection item of the operation history are designated, and the presence / absence / collection item of the collection is stored in the operation history collection setting storage file 3. The operation history collection setting storage file 3 stores the collection level and the presence / absence of collection / collection settings of collection items sent from the operation history collection level determination unit 1 and the operation history collection determination unit 2.

Step 104) Next, the request content distribution unit 4 receives the request for each screen of the HMI terminal input by the operator. Step 105) The request content distribution unit 4 distributes the request content for each screen ID using the screen ID as a key for the screen request.

Step 106) At this time, the control section 8 judges whether the screen has been activated or has been activated, and if it has been activated, the process proceeds to step 111. Step 107) If it is the time when the screen is activated in the determination of Step 106, the operation history calculation unit 5 corresponding to the screen ID is newly generated.

Step 108) The control unit 8 instructs the request content distribution unit 4 to transfer the distributed contents to the generated operation history calculation unit 5. The operation history calculation unit 5
In step 103, the operation history is calculated based on the content of the screen request with reference to the collection item information stored. The method for calculating the operation history is an existing method and is not particularly limited in the present invention.

Step 109) The control unit 8 newly adds
The operation history storage unit 6 corresponding to the screen ID is generated, and the operation history information generated by the operation history calculation unit 5 is transferred. Step 110) The operation history storage unit 6 writes the generated operation history information. The process shifts to the process of receiving the next screen request (shift to step 104).

Step 111) In Step 106, if the screen is already activated and the screen request is the last one, the process proceeds to Step 115. Step 112) The operation history calculation unit 5 calculates the operation history information corresponding to the acquired screen request and transfers it to the operation history storage unit 6 corresponding to the screen ID.

Step 113) The operation history storage 6
Operation history information is acquired from the operation history calculation unit 5. Step 114) The operation history storage unit 6 additionally writes the acquired operation history information in the storage area. Move to step 104.

Step 115) In the case of the last screen request, the operation history calculation unit 5 calculates the operation history information corresponding to the screen ID and transfers it to the operation history storage unit 6. Step 116) The operation history storage unit 6 acquires the operation history information from the operation history calculation unit 5.

Step 117) The control unit 8 erases the operation history calculation unit 5 corresponding to the screen ID. Step 118) The operation history storage unit 5 is set to Step 11
The operation history information acquired in 6 is additionally written.

Step 119) The operation history storage 5
The screen I that has been accumulated by additional writing until then
A series of operation history information corresponding to D is transferred to the operation history storage unit 7. Step 120) The control unit 8 erases the operation history storage unit 5.

Step 121) The operation history storage unit 7
The operation history information transferred from the operation history storage unit 5 is collectively written in the operation history file 13 corresponding to the screen ID. The operation history storage unit 7 can also store the operation history of the same screen ID in different operation history files 13 by distinguishing by operation time. When configuring the operation history file 13 by distinguishing by time,
As shown in FIG. 15, a file name is generated using the month, day, hour, minute, second, screen ID and the like. By generating the file names in this way, when the number of files increases, it is easy to automatically delete the files that have passed a certain period of time with reference to time information such as the date.

As described above, in the first embodiment, the operation history storage unit 6 receives the operation history and obtains one screen ID.
Until the end of the request, the operation history is added as a work area, and when the operation history calculation unit 5 corresponding to the screen request is lost, the operation history is sequentially additionally written, and the operation history calculation unit corresponding to the screen request is performed. When No. 5 is deleted, the operation history is collectively transferred to the operation history storage unit 7. The operation history storage unit 7 writes the operation history information in the operation history file 13 for each screen ID. That is, the operation history information additionally written in the operation history storage unit 6 is transferred from the operation history storage unit 6 to the operation history storage unit 7 at the timing when the input of the screen request for a certain screen ID is completed.
The operation history storage unit 7 collectively writes the operation history file 13 corresponding to the screen ID.

Next, a second embodiment will be described. FIG.
FIG. 3 is a configuration diagram (part 2) of the operator's operation history collection management device in the HMI terminal of the present invention. In the figure, the same components as those in FIG. 4 are designated by the same reference numerals. The operation history collection management device shown in FIG. 16 includes an operation history collection level determination unit 1, an operation history collection determination unit 2, an operation history collection setting storage file 3, a request content distribution unit 4, and an operation history generated for each screen ID. The calculation unit 5, the operation history distribution unit 16, the operation history storage unit 7, the control unit 8, the operation level file 11, the operation history collection item setting file 12, and the operation history file 13 generated for each screen ID. . That is, the present embodiment is different from the first embodiment in that one operation history distribution unit 16 distributes the operation history information generated for each screen ID and sequentially stores the result in the operation history file 7. .

Regarding the operation history collection level determination unit 1, the operation history collection determination unit 2, the operation history collection setting storage file 3, the request content distribution unit 4, and the operation history calculation unit 5, the above-mentioned first
The operation is the same as that described in the above embodiment. The operation history distribution unit 16 acquires the operation history for each screen ID obtained by the operation history calculation unit 5, sorts the operation history for each screen ID, and sequentially transfers the operation history to the operation history storage unit 7. The operation history storage unit 7 stores the operation history distributed by the operation history distribution unit 16 in each operation history file 13 corresponding to the screen ID.

17 and 18 are diagrams for explaining the operation of the second embodiment of the present invention. Step 201) First, the operation history collection level determination unit 1
When the HMI terminal is started up, the level of the operator is determined by referring to the operation level file (for each operator) 11 which holds the level of the operator with the inputted operator name.

Step 202) Further, the operation history collection level judgment unit 1 judges the collection level according to the operation level of the operator by referring to the operation level file (by level) 11 according to the level judged in Step 201,
The collection level is transferred to the operation history collection setting storage file 3.

Step 203) Next, the operation history collection determining unit 2 refers to the operation collection file 12 that holds the collected contents of the operation history to determine whether the operation history exists or not.
Collection items of the operation history are designated, and the presence / absence / collection items of the collection are stored in the operation history collection setting storage file 3.
The operation history collection setting storage file 3 stores the collection level and the presence / absence of collection / collection settings of collection items sent from the operation history collection level determination unit 1 and the operation history collection determination unit 2.

Step 204) Set the temporary storage area of the operation history distribution unit 16 for storing and distributing the operation history information. Step 205) The request content distribution unit 4 receives the request for each screen of the HMI terminal input by the operator.

Step 206) The request content distribution unit 4
The screen request is assigned to each screen ID by using the screen ID as a key. Step 207) At this time, the control unit 8 determines whether the screen has been activated or has already been activated, and if it has been activated, the process proceeds to step 216.

Step 208) When the screen is activated, a new operation history calculation unit 5 corresponding to the screen ID is generated. Step 209) The operation history calculation unit 5 executes Step 20.
The operation history for each screen ID is calculated with reference to the collection item information stored in 3. Depending on the items collected, Figure 1
9 and various operation histories as shown in FIG. 20 are generated.

Step 210) The operation history calculation unit 5 adds a screen ID to the generated operation history information and transfers it to the operation history distribution unit 16. Step 211) The operation history distribution unit 16 receives the operation history information generated from the operation history calculation unit 5.

Step 212) Operation history distribution unit 16
Determines the screen ID of the acquired operation history information. (Step 213) In step 212, the operation history file 13 corresponding to the determined screen ID is generated.

Step 214) Operation history distribution unit 16
When the operation history information is given a screen ID and transferred to the operation history storage unit 7, the operation history storage unit 7 writes the operation history information in the operation history file 13 corresponding to the information. The process moves to the process of receiving the next screen request (moves to step 205).

Step 216) If the screen request is the last one when the screen is already activated in step 207, the process proceeds to step 222. Step 217) The operation history calculation unit 5 calculates the operation history information corresponding to the screen ID of the acquired screen request and transfers it to the operation history distribution unit 16.

Step 218) Operation history distribution unit 16
Acquires operation history information. Step 219) The operation history distribution unit 16 refers to the screen ID of the acquired operation history information and distributes the operation history file 13 to be written. Step 220) The operation history distribution unit 16 gives the allocated screen IDs to the operation history information, and the operation history storage unit 7
Transfer to

Step 221) The operation history storage unit 7
The distributed operation history information is additionally written in the operation history file 13 corresponding to the screen ID. The process proceeds to the process of accepting the next screen request (moves to step 205). Step 222) When the request is the last screen request, the operation history calculation unit 5 calculates the operation history information corresponding to the screen ID, The operation history information is given a screen ID and transferred to the operation history distribution unit 16.

Step 223) Operation history distribution unit 16
Acquires operation history information. Step 224) The control unit 8 erases the operation history calculation unit 5 corresponding to the screen ID. Step 225) The operation history distribution unit 16 executes the step 2
The file ID is assigned to the operation history file 13 to be written by referring to the screen ID of the operation history information acquired in 23.

Step 226) Operation history distribution unit 16
Transfers the operation history information distributed for each operation history file 13 to the operation history storage unit 7. Step 227) The operation history storage unit 7 refers to the file ID given to the operation history information transferred from the operation history distribution unit 16, and additionally writes to the operation history file 13 corresponding to the ID.

Step 228) The control unit 8 erases the operation history information storage area of the operation history distribution unit 16. As described above, in the second embodiment, when one operation history distribution unit 16 receives all the operation histories obtained for each screen ID and transfers them to the operation history storage unit 7, the operation history storage unit 7 selects the corresponding screen IDs. The operation history file 13 to be written is allocated based on the above. The operation history information is transferred to the operation history storage unit 7 every time it is sorted, and additionally written in the operation history file 13. The operation history file 13 is created when each screen is activated and additional writing is performed to the operation history file 13 each time there is a request from each screen.

Next, a third embodiment will be described. FIG.
FIG. 1 is a configuration diagram (No. 3) of the operator operation history collection management device in the HMI terminal of the present invention. The operator operation history collection management device shown in the figure includes an operation history collection level determination unit 1, an operation history collection determination unit 2, an operation history collection setting storage unit 3, an operation history calculation unit 15, an operation history distribution unit 26, and an operation history. Storage unit 7, control unit 8, operation level file 11,
The operation history collection item setting file 12 and the operation history file 13 are included.

The operation history calculation unit 15 shown in FIG. 21 directly acquires the request for each screen, obtains the operation history according to the collection setting, and transfers the operation history to the operation history distribution unit 26. The operation history calculation unit 15 can calculate the operation history corresponding to the changed collection setting by accessing the operation history collection setting storage unit 3 at regular intervals and receiving the collection setting. The operation history corresponding to the collection setting is as shown in FIGS.

The operation history distribution unit 26 is the operation history calculation unit 1
When 5 receives the request without distinguishing the screen and receives the operation history according to the collection setting, the corresponding screen ID is determined and transferred to the operation history storage unit 7. Operation history distribution unit 26
Even if a plurality of the same screens can be activated, the screens are transferred to the operation history storage unit 7 so that the screen IDs can be distinguished and written in different corresponding operation history files 13.

The operation history storage unit 7 includes an operation history distribution unit 26.
The operation history transferred from is received, and the operation history is added and stored in the corresponding operation history file 13. Even operation histories of the same screen ID can be saved as separate operation history files by distinguishing them by time. FIG. 22 is a diagram for explaining the operation of the third mode of the present invention.

Step 301) First, the operation history collection level determination unit 1 refers to the operation level file (for each operator) 11 that holds the operator level with the input operator name when the HMI terminal is started up. By doing so, the level of the operator is determined.

Step 302) Further, the operation history collection level judgment unit 1 judges the collection level according to the operation level of the operator by referring to the operation level file (by level) 11 according to the level judged in Step 201,
The collection level is transferred to the operation history collection setting storage file 3.

Step 303) Next, the operation history collection determining unit 2 refers to the operation collection file 12 that holds the collected contents of the operation history to determine whether or not there is an operation history,
Collection items of the operation history are designated, and the presence / absence / collection items of the collection are stored in the operation history collection setting storage file 3.
The operation history collection setting storage file 3 stores the collection level and the presence / absence of collection / collection settings of collection items sent from the operation history collection level determination unit 1 and the operation history collection determination unit 2.

Step 304) A temporary storage area of the operation history distribution unit 26 for storing and distributing the operation history information is set. Step 305) If the screen request is completed, the process is completed. Step 306) If the screen request has been issued, the operation history calculation unit 5 directly receives the request for each screen of the HMI terminal input by the operator, refers to the collection items determined in Step 303, and makes the request. The operation history is calculated based on the operation history and transferred to the operation history distribution unit 26.

Step 307) Operation history distribution unit 26
Divides the operation history for each screen ID and sequentially transfers the operation history to the operation history holding unit 7. Step 308) The operation history holding unit 7 sequentially writes the transferred operation history information into the operation history file 13.

As a result, the operation history distribution unit 26 can acquire the same operation history as the first and second operations even in the operation according to the third mode.

[0071]

Embodiments of the present invention will be described below. [First Embodiment] A first embodiment of the present invention will be described below based on the configuration of FIG.

FIG. 23 is a diagram for explaining the first embodiment of the present invention. (1) First, the operation history collection level determination unit 1 acquires the operator level from the operation level file 11 by the operator names “Jiro Yamamoto”, “Shiro Kato”, and “Hachiro Kobayashi”. In the example of FIG. 5, "Jiro Yamamoto" is "Level A",
The information that "Sato Kato" is "level B" and "Hachiro Kobayashi" is "level C" is acquired. Here, regarding each level, "level A" is a level at which only data can be viewed, "level B" is a level at which only specific data can be written / changed, and "level C". Indicates that all data can be written / changed.

(2) Next, the operation history collection / determination unit 2
The operation history collection item setting file 12 is referenced to acquire the items for which the operation history should be collected. In this example, it is assumed that the operation history information items shown in FIG. 10 have been acquired. (3) The operator level obtained in (1),
The operation history collection items acquired in (2) are stored in the operation history collection setting storage unit 3.

(4) The operation history calculation unit 5 accesses the operation history collection setting storage unit 3 at a predetermined cycle and acquires the collection setting item and the operator level information. As the collection setting items, all the requested contents on the screen (screen ID, request /
It is assumed that an ID capable of recognizing a response and the like, and setting conditions such as request / application are acquired.

(5) Here, when the operator makes a request on the screen of the HMI terminal, the request content distribution unit 4 receives the request for each screen, and uses the screen ID as a key to display the request content for each screen ID. The screen ID is sorted, as shown in FIG.
Is transferred to the operation history calculation unit 5 corresponding to. When the screen is activated, the operation history calculation unit 5 corresponding to the screen ID is created and the request content is sent. Further, when the process in the operation history calculation unit 5 is completed, the operation history calculation unit 5 is deleted.

(6) The operation history calculation section 5 sends the requested content
Receives the request content obtained from the division 4 and obtains it in (4)
The operation history according to the collected setting is obtained. Operation history calculation
Part 5 ₁Corresponds to screen ID = A, and the operation history calculation unit 5_Two
Corresponds to the screen ID = B, and the operation history calculation unit 5_ThreeIs an image
It is assumed that the surface ID = C is supported, and each is based on the setting information.
Then, the operation history information A, B, C is generated. Where the picture
It is assumed that a request of surface ID = C is newly issued.
Therefore, the operation history calculation unit 5_ThreeIs newly generated
become.

(7) The operation history information A, B, C generated in (6) is transferred to the operation history storage unit 6. When the operation history storage unit 6 acquires the operation history information C from the newly generated operation history calculation unit C, the operation history storage unit 6 ₃ corresponding to the operation history calculation unit C is newly provided, and the operation history storage unit 6 is provided. ₃
The operation history information C is stored in. In addition, the operation history information A,
Since the area corresponding to B is set in the operation history storage units 6 ₁ and 6 ₂ , additional writing is performed.

(8) When all screen requests are completed, the operation history storage units 6 _1, 6 ₂ , and 6 ₃ respectively display screen IDs.
The operation history information items (A, B, C) are collectively transferred to the operation history storage unit 7. The operation history storage unit 7 is shown in FIG. 11 and FIG.
As shown in FIG. 2, the operation history information is collectively written in the operation history files 13 ₁ , 13 ₂ , 13 ₃ for each screen ID using a fixed format. Based on the setting information, as shown in FIGS. 11 and 12, the operation history file 1
3 ₁ , 13 ₂ and 13 ₃ include an operator name, date and time, screen ID, push button name, setting condition when pressed, operator name, date and time at action, screen ID, action type, setting condition at action, etc. The operation history information of is written.

At this time, the same operator or
Even if the screen ID is the same, if the operation time is different,
You may make it hold _| maintain as each different operation log file 13n. Further, since the operation date and time is set in the operation history file 13, the operation history file 13 can be deleted by deleting the record of the operation history file 13 at every predetermined cycle, for example, by deleting the record that has passed one week. 13 resources are saved.

[Second Embodiment] The second embodiment of the present invention is the operation history information for each screen ID distributed by the request content distribution unit 4 in (6) of the first embodiment. Is generated, it is transferred to the operation history distribution unit 16. For example,
24, when the operation history information A is transferred, the operation history distribution unit 16 determines the screen ID of the history information and transfers it to the operation history storage unit 7. At this time, since screen ID information is set in the operation history information, the operation history storage unit 7 stores each operation history information in the operation history file 13 corresponding to the screen ID information. For example, the operation history information of screen ID = A is stored in the operation history file A, the operation history information of screen ID = B is stored in the operation history file B, and the operation history information of screen ID = C is stored in the operation history file C. It is additionally written in time order. When the operation history calculation unit 5 generates operation history information for a new screen ID, the operation history file 13 _n corresponding to the screen ID is generated.

In this embodiment as well, as in the first embodiment, the operation date and time is set in the operation history file 13, so that the record of the file 13 is erased at every predetermined cycle. You may. [Third Embodiment] The third embodiment of the present invention has a configuration that does not include a request content distribution unit for distributing requests for each screen, and as shown in FIG. The operation history corresponding to the collection setting information is generated without distinguishing the screen ID and transferred to the operation history distribution unit 26. The operation history distribution unit 26 determines the screen ID of the transferred information,
The determination result is added to the operation history information and transferred to the operation history storage unit 7. As a result, the operation history storage unit 7 writes to the operation history file corresponding to each screen ID held in each operation history information.

For example, when the screen request of screen ID = A is first issued and then the screen request of screen ID = C is issued, the operation history calculation unit 15 causes the operation history collection setting holding unit 3 to operate. With reference to the screen request with the screen ID = A, the operation history information is generated and transferred to the operation history distribution unit 26. The operation history distribution unit 26 specifies the operation history file 13 _{1 in} which the operation history information should be stored, and transfers the operation history information to the operation history storage unit 7. The operation history storage unit 7 writes the operation history file 13 ₁ designated by the operation history distribution unit 26. Next, the process related to screen ID = C is also screen ID =
The operation history information generated in the operation history file 13 ₃ by the same process as A is stored.

When the same screen is activated in the operation history distribution unit 26, a plurality of screen IDs are given to the screen and the operation history file 13 is generated based on the screen ID. The operation history storage unit 7 may be instructed to store the generated operation history.

The third embodiment described above has the simplest apparatus configuration and does not have an operation history calculation unit and an operation history storage unit for each screen ID, so resources and the like can be saved. In each of the above embodiments, the operation history file 13 uniquely determines the file name based on the set of the file creation time and the screen ID, as shown in FIG.
Even operation histories of the same screen ID of the same screen can be distinguished by time, and thus the operation history information can be stored as separate files.

Further, by referring to the file creation time of the file name, it is defined in advance in the operation history collection item setting file 12 that a file which has passed a certain period of time is deleted when the file capacity becomes large. By setting it, it becomes possible to automatically erase.

Further, since the operation history collection item setting file 12 and the operation level file 11 are files that can be arbitrarily updated by the operator in advance, when the level of the operator is improved, the file is searched by the operator name. Then, the corresponding contents can be changed. Also, if you want to change the contents of collection items,
By changing the operation history collection item setting file 12 by the operator, it is possible to acquire the operation history information of an item as needed.

The format of the operation history file 13 can be read as it is in spreadsheet software or the like by using a fixed format as shown in FIGS. 11 and 12. As described above, according to each of the above-described embodiments, the operation history of the operator in the HMI terminal can be automatically and accurately collected only for necessary information.

Further, since only the necessary operation history is managed, there is no waste in the storage amount and it is possible to easily extract information for analysis. Further, since it is possible to easily recognize which operator performed the process, the responsibility of updating the data becomes clear.

The present invention is not limited to the above embodiments, but various modifications and applications are possible within the scope of the claims.

[0090]

As described above, according to the method and apparatus for collecting and managing the operation history of the operator in the human interface terminal according to the present invention, the operation history of the operator in the HMI terminal is automatically and accurately set as the standard format only the necessary information. Can be collected. In addition, there is no waste in management of the operation history, and analysis / analysis can be efficiently performed.

Furthermore, by clarifying the management of data change, the operator who made the change becomes clear when a failure occurs. Therefore, by inquiring the operator concerned, the time for investigating the cause can be shortened. It

[Brief description of the drawings]

FIG. 1 is a diagram for explaining the principle of the present invention.

FIG. 2 is a principle configuration diagram of the present invention.

FIG. 3 is a diagram for explaining the function of the HMI terminal of the present invention.

FIG. 4 is a configuration diagram (No. 1) of an operator operation history collection management device in the HMI terminal of the present invention.

FIG. 5 is a diagram showing an example of operator level classification according to the present invention.

FIG. 6 is a diagram showing an example of level classification according to the present invention.

FIG. 7 is a diagram showing an example (part 1) of an operation history collection item setting file of the present invention.

FIG. 8 is a diagram showing an example (part 2) of an operation history collection item setting file of the present invention.

FIG. 9 is a diagram showing an example (part 3) of an operation history collection item setting file of the present invention.

FIG. 10 is a diagram showing an example (No. 4) of an operation history collection item setting file of the present invention.

FIG. 11 is a diagram showing an example (part 1) of an operation history file generated in the standard format of the present invention.

FIG. 12 is a diagram showing an example (part 2) of an operation history file generated in the standard format of the present invention.

FIG. 13 is a diagram (No. 1) for explaining the operation of the first mode of the present invention.

FIG. 14 is a diagram (No. 2) for explaining the operation of the first mode of the present invention.

FIG. 15 is a diagram showing an example of giving an operation history file name according to the present invention.

FIG. 16 is a configuration diagram (part 2) of the operator's operation history collection management device in the HMI terminal of the present invention.

FIG. 17 is a diagram (No. 1) for explaining the operation of the second embodiment of the present invention.

FIG. 18 is a diagram (No. 2) for explaining the operation of the second embodiment of the present invention.

FIG. 19 is a diagram showing an example (part 1) of an operation history corresponding to the collection setting of the present invention.

FIG. 20 is a diagram showing an example (No. 2) of the operation history corresponding to the collection setting of the present invention.

FIG. 21 is a configuration diagram (No. 3) of the operator operation history collection management device in the HMI terminal of the present invention.

FIG. 22 is a diagram for explaining the operation of the third mode of the present invention.

FIG. 23 is a diagram for explaining the first embodiment of the present invention.

FIG. 24 is a diagram for explaining the second embodiment of the present invention.

FIG. 25 is a diagram for explaining the third embodiment of the present invention.

[Explanation of symbols]

1 operation history collection level determination unit, operation history collection level determination unit 2 operation history collection determination unit, operation history collection determination unit 3 operation history collection setting file 4 request content distribution unit, request content distribution unit 5 operation history calculation unit, Operation history calculation unit 6 Operation history storage unit, operation history storage unit 7 Operation history storage unit, operation history storage unit 8 Control unit, control unit 11 Operation level file 12 Operation history collection item setting file 13 Operation history file 15 Operation history calculation unit 16 Operation history distribution unit 26 Operation history distribution unit

Claims (15)

[Claims] 1. An operator operation history collection and management method in an HMI terminal for an operator to collect an operation history using a human interface terminal (hereinafter referred to as an HMI terminal), wherein an operation level of the operator is determined, and the operation is performed. The operation history collection items to be collected from the operation history information are determined based on the level, and when a request for each screen is issued by the operation of the operator, the operation history for each screen is generated by referring to the operation history collection items. Then, a method for collecting and managing an operator operation history in an HMI terminal, characterized in that the generated operation history is stored in a file. 2. When a request is issued for each screen of the HMI terminal, the request is distributed for each screen identifier, operation history information is calculated for each screen identifier of the request, and each screen identifier of the request is calculated. The operator operation history in the HMI terminal according to claim 1, wherein the operation history information is held in a storage device, and when the request for the screen is completed, the held operation history information for each screen identifier is collectively written in a file corresponding to the screen identifier. Collection management method. 3. When a request is issued for each screen of the HMI terminal, the request is distributed for each screen identifier, operation history information is calculated for each screen identifier of the request, and writing is performed for each screen identifier. Decide which file to do,
The HM according to claim 1, wherein additional writing is sequentially performed to the file.
A method for collecting and managing an operator operation history in an I terminal. 4. When a request is issued for each screen of the HMI terminal, operation history information is calculated for each request, a screen identifier is determined from the operation history information, and a file corresponding to the determined screen identifier The method for collecting and managing an operator operation history in an HMI terminal according to claim 1, wherein the additional writing is sequentially performed. 5. The file name of the file is the time and screen identifier at which the operation history information is generated.
A method for collecting and managing operator operation history in the described HMI terminal. 6. The file according to claim 5, wherein the elapsed time after the operation history information is written in the file is acquired by referring to the file name, and the file is deleted when a predetermined time has elapsed. And method for collecting and managing operator operation history in the HMI terminal. 7. When a plurality of screens can be activated,
The method for collecting and managing an operator operation history in an HMI terminal according to claim 1, wherein a screen identifier is uniquely assigned to each screen. 8. An operator operation history collection management device in an HMI terminal for generating and managing an operation history of an operator who operates the HMI terminal, wherein when the operator starts up the HMI terminal, the operator's level is adjusted according to the operator's level. Operation history collection level determination means for determining the collection level of operation history, operation history collection determination means for designating the presence or absence of operation history collection, and operation history collection items, and operation history collection for holding the collection setting items With reference to the setting storage means, the request content distribution means for receiving the request for each screen input by the operator operating the screen, and distributing the request, and the operation history collection setting storage means, respectively. A plurality of operation history calculating means for obtaining an operation history according to the collection setting item from the request content, and the operation history A plurality of operation history storage means for adding up and summarizing the operation history obtained by the calculation means, and an operation for saving the operation history acquired from the operation history storage means as a separate file when the request for each screen is completed An operator operation history collection / management apparatus in an HMI terminal, comprising: history storage means and control means for controlling each of the means. 9. An operator operation history collection management device in an HMI terminal for generating and managing an operation history of an operator who operates the HMI terminal, wherein when the operator starts the HMI terminal, the operator operation history Operation history collection level determination means for determining the collection level of operation history, operation history collection determination means for designating the presence or absence of operation history collection, and operation history collection items, and operation history collection for holding the collection setting items With reference to the setting storage means, the request content distribution means for receiving a request for each screen input by the operator operating the screen and distributing the request, and the operation history collection setting storage means, A plurality of operation history calculation means for obtaining an operation history according to the collection setting item from the request content on the screen; An operation history distribution unit that distributes the operation history generated in each stage for each screen, and an operation history storage unit that additionally stores the operation history distributed by the operation history distribution unit in a file corresponding to each screen. And an operator operation history collection management device in an HMI terminal, which comprises: 10. An operator operation history collection management device in an HMI terminal for generating and managing an operation history of an operator who has operated the HMI terminal, wherein when the operator starts the HMI terminal, the operator operation history collection management apparatus responds to the level of the operator. Operation history collection level determination means for determining the collection level of operation history, operation history collection determination means for designating the presence or absence of operation history collection, and operation history collection items, and operation history collection for holding the collection setting items With reference to the setting storage means and the operation history collection setting storage means, an operation history calculation means for obtaining an operation history according to the collection setting item for each screen, and an operation history generated by the operation history calculation means are displayed. The operation history distribution means for distributing each file according to the identifier of the screen and the operation history distribution means for distributing by the operation history distribution means. An operator operation history collection and management device in an HMI terminal, comprising: an operation history storage unit for additionally writing the stored operation history in a corresponding file; and a control unit for controlling each unit. 11. The operator operation history collection management device in an HMI terminal according to claim 8, wherein the operation history storage unit shares a pattern of items stored in the file. 12. The operator operation history collection management device in an HMI terminal according to claim 8, 9 or 10, wherein the operation history calculation means refers to the operation history collection setting storage means at a constant cycle. 13. The operation history storage means includes a setting item for setting so that the collected operation history information can be erased after a predetermined time has elapsed.
An operator operation history collection management device in the HMI terminal described in 0. 14. The HM according to claim 8, wherein the operation history storage unit allocates one file for each screen identifier.
An operator operation history collection management device in the I terminal. 15. The operation history distribution means allocates one file for each screen identifier.
An operator operation history collection management device in the described HMI terminal.