JP3580347B2 - Data management method, data management device, and their recording media - Google Patents

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a data management method, a data management device, and a recording medium thereof, and more particularly, relates to a method for controlling a PLC (Programmable Logic Controller) and a database for storing data collected from the PLC or an application for controlling the PLC. The present invention relates to a data management method, a data management device, and a recording medium for automatically executing data flow control by setting an association between a trigger and an action.
[0002]
[Prior art]
In recent FA (factory automation) applications, when "something necessary timing" occurs, it is often constructed in such a way that "processing corresponding to it" is executed.
[0003]
For example,
1) Every time a predetermined time elapses, PLC data is collected in a form specified by the user and stored in a database.
2) When production by the PLC is started, necessary data such as recipe data, master data, work instructions, etc. are searched and downloaded to the PLC.
The application is built in the form.
[0004]
[Problems to be solved by the invention]
However, the programming of the above-mentioned application is performed such that when "a necessary timing" occurs, that is, when a trigger occurs, a "corresponding process" is executed, that is, an action is executed. Programming is performed separately for each trigger type and each action type, and in this type of programming, it is often required to cooperate with other user applications. There has been a problem that the development cost is high and that it takes time to deal with the processing change.
[0005]
Therefore, the present invention provides a data management method, a data management device, and a recording medium thereof that can easily cope with an increase in trigger types and action types, and that can reduce the development cost. With the goal.
[0006]
[Means for Solving the Problems]
In order to achieve the above object, the invention according to claim 1 is:A data management method for connecting to the programmable logic controller via an FA network and managing data of the programmable logic controller;Indicates the start timing of processingpluralTriggerTrigger type execution program for generating a trigger for each ofUnique trigger IDWhenToCorrespondingSet,Each of the above programmable logic controllersIndicates the actual content of the operationpluralactionAction type execution program to execute an action for each ofUnique action IDWhenToCorrespondingSet,A trigger to be generated is selected from the plurality of triggers, an action to be performed when the trigger is generated is selected, and a combination of the selected trigger and the action is selected.The above trigger IDAnd aboveAction IDBy storing in correspondence withSet up the job,By starting and executing the above-mentioned trigger type execution program, a corresponding trigger ID is added.TriggerAnd itsTrigger IDSearch and respond to the job set above based onIdentify the action ID, That particularAction IDAnd execute the action type execution program corresponding toActionAutomaticExecute.
[0007]
The invention according to claim 2 isIn the data management device connected to the programmable logic controller via the FA network and managing the data of the programmable logic controller, a trigger is generated for each of a plurality of triggers indicating a start timing of each process for the programmable logic controller. Trigger setting means for setting a trigger type execution program and a unique trigger ID in association with each other, and executing an action for each of a plurality of actions indicating the actual contents of each processing for the programmable logic controller. Setting means for setting an action type execution program and a unique action ID in association with each other, one of the plurality of triggers, and an action to be executed when the trigger occurs And sets the trigger ID and the action ID in association with each other, reads a trigger type execution program from the job setting means for storing the trigger ID and the action ID, and executes the trigger type execution program. The event notification is performed by adding the corresponding trigger ID, and the corresponding action ID is obtained by searching the job setting means based on the trigger ID by the event notification, and the specific action acquired from the action setting means is obtained. A control unit for acquiring an action type execution program corresponding to the action ID and performing an execution process of the action type execution program;Is provided.
[0011]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of a data management method, a data management device, and a recording medium according to the present invention will be described in detail with reference to the accompanying drawings.
[0012]
FIG. 1 is a system configuration diagram showing one embodiment of a data flow control system configured by applying a data management method, a data management device, and their recording media according to the present invention.
[0013]
In FIG. 1, the data flow control system connects a data flow control device 10 between a plurality of PLCs 20-1 and 20-2 connected to an FA network 30 and a data file 40 and a user application 50. The data flow control device 10 associates and sets various triggers and various actions corresponding to the triggers, and automatically executes a desired action corresponding to the triggers in response to the generation of the triggers. -1, 20-2 and the data file 40 and the user application 50.
[0014]
Here, the data flow control device 10 is constituted by an FA personal computer (FA personal computer), functions as middleware between the plurality of PLCs 20-1 and 20-2, the data file 40 and the user application 50, and generates various triggers. Is triggered by the occurrence of the error, stores data collected from the plurality of PLCs 20-1 and 20-2 in the data file 40, and notifies the user application 50. And the like for downloading to the PLCs 20-1 and 20-2 are automatically executed in accordance with the setting of the user.
[0015]
FIG. 2 is a block diagram showing a detailed configuration of the data flow control device shown in FIG.
[0016]
2, the data flow control device 10 includes a device setting tool 11 for performing various settings for the data flow control device 10, a setting table 12 for storing setting contents set by the device setting tool 11, and a data flow control device 10. A tag setting tool 13 for setting tags for data transfer by the tag 10, a tag database 14 for storing tags set by the tag setting tool 13, and a service processing unit 15 for executing a service of data flow control by the data flow control device 10. It comprises.
[0017]
The service processing unit 15 includes a control module 16 for executing data flow control by the data flow control device 10, a trigger module 17 for generating various triggers, and an action module 18 for executing various actions. .
[0018]
Further, a command such as data collection start and stop is notified from the user application 50 to the control module 16 of the service processing unit 15, and a command such as generation of a trigger is notified from the user application 50 to the trigger module 17. The action module 18 notifies the user application 50 of the application (application notification).
[0019]
The action module 18 sends and receives data to and from the user data file 40.
[0020]
The service processing unit 15 transmits and receives data to and from the plurality of PLCs 20-1 and 20-2 via the gateway 60.
[0021]
Here, the service by the service processing unit 15 realizes a data logging process, a download process, and the like. That is, when a certain trigger occurs, the service processing unit 15 executes an action corresponding to the trigger. This
1) Store the data of the PLCs 20-1 and 20-2 in the user data file 40
2) Search the database created by the user under specified conditions, and write the results to the PLCs 20-1 and 20-2.
3) Notify the user application 50 as an action when a trigger occurs
And so on.
[0022]
In addition, the device setting tool 11
1) Registration of setting data required for service of service processing unit 15
2) Starting and stopping the service of the service processing unit 15
3) Registration, start, and end of a job, which is a unit of a trigger and an action (work) to be logged at that time
And other functions.
[0023]
In addition, the tag setting tool 13
1) Setting tags for the variable area of the target device
2) Setting of event memory mapping with target device
And other functions.
[0024]
The tag database 14 is a database that stores tag information set by the tag setting tool 13.
[0025]
The setting table 12 is a database that stores a collection of data necessary for executing the service of the service processing unit 15.
[0026]
The user data file 40 is a database in which data for actually logging data is stored or a database in which data to be downloaded is stored. The table configuration (schema) of this database can be designed and created by the user.
[0027]
FIG. 3 is a functional block diagram showing a detailed operation of the data flow control device shown in FIG.
[0028]
In FIG. 3, the trigger setting unit 111 executes a trigger type setting program, that is, a trigger type 1 setting program 151-1, a trigger type 2 setting program 151-2, and a trigger type 3 setting program 151-3. Is set in the trigger setting database (trigger setting DB) 121.
[0029]
The job setting unit 112 sets a job in which a trigger and an action are associated with each other in a job setting database (job setting DB) 122.
[0030]
The action setting unit 113 executes an action type setting program, that is, an action type 1 setting program 152-1, an action type 2 setting program 152-2, and an action type 3 setting program 152-3, and stores the results in an action setting database. (Action setting DB) 123 is set.
[0031]
The trigger starting unit 151 reads the trigger set in the trigger setting database (trigger setting DB) 121 and the job set in the job setting database (job setting DB) 122, and executes the execution program of the trigger type, that is, the execution of the trigger type 1 The start / stop command is notified to the program 153-1, the trigger type 2 execution program 153-2, the trigger type 3 execution program 153-3, and the trigger type 4 execution program 153-4.
[0032]
When an event occurs due to execution of the trigger type 1 execution program 153-1, the trigger type 2 execution program 153-2, the trigger type 3 execution program 153-3, and the trigger type 3 execution program 153-4, the event is transmitted to the flow control unit. 152 is notified.
[0033]
The flow control unit 152 that executes the event reads the action set in the action setting database (action setting DB) 123 and the job set in the job setting database (job setting DB) 122, and executes the execution program of the action type, that is, The execution instruction is notified to the action type 1 execution program 154-1, the action type 2 execution program 154-2, the action type 3 execution program 154-3, and the action type 4 execution program 154-4.
[0034]
FIG. 4 is a diagram showing an example of the job setting database (job setting DB) shown in FIG.
[0035]
4, a job setting database (job setting DB) 122 includes a job table 122-1.
[0036]
The job table 122-1 shown in FIG. 4 is a table in which an action ID is stored in correspondence with a trigger ID.
[0037]
That is, in the job table 122-1 shown in FIG. 4, the action ID "200" is set for the trigger ID "100", the action ID "210" is set for the trigger ID "100", and the trigger ID This indicates that the action ID “230” is set for “110”.
[0038]
FIG. 5 is a diagram showing an example of the trigger setting database (trigger setting DB) shown in FIG.
[0039]
5, a trigger setting database (trigger setting DB) 121 includes a trigger table 121-1, a trigger program information table 121-2, and a table 121-3 for each trigger type.
[0040]
The trigger table 121-1 illustrated in FIG. 5 is a table in which a trigger name and a trigger type ID are stored in association with a trigger ID.
[0041]
That is, in the trigger table 121-1 shown in FIG. 5, the trigger name "every 30 seconds" and the trigger type ID "1" are set for the trigger ID "100", and the trigger name "1" is set for the trigger ID "110". This indicates that “production start” and the trigger type ID “3” are set.
[0042]
The trigger program information table 121-2 shown in FIG. 5 is a table in which a trigger type name, a setting program, and an execution program are stored in correspondence with a trigger type ID.
[0043]
That is, in the trigger program information table 121-2 shown in FIG. 5, the trigger type name "fixed period", the setting program "SetCyclic", and the execution program "CyclicExec" are set for the trigger type ID "1". The trigger type name “specified time”, the setting program “SetTime”, and the execution program “TimeExe” are set for the ID “2”, and the trigger type name “condition match” and the setting program “ SetTag ”and the execution program“ TagExe ”are set.
[0044]
Further, a table 121-3 for each trigger type shown in FIG. 5 is a table for a fixed period trigger, and is a table in which a fixed period is stored in correspondence with a trigger ID.
[0045]
That is, in the table 121-3 for each trigger type shown in FIG. 5, the fixed period “0: 0: 30” is set for the trigger ID “100”, and the fixed period “0” is set for the trigger ID “101”. : 1: 0 "is set.
[0046]
FIG. 6 is a diagram showing an example of the action setting database (action setting DB) shown in FIG.
[0047]
6, the action setting database (action setting DB) 123 includes an action table 123-1, an action program information table 123-2, and a table 123-3 for each action type.
[0048]
The action table 123-1 shown in FIG. 6 is a table in which an action name and an action type ID are stored in association with the action ID.
[0049]
That is, in the action table 123-1 shown in FIG. 6, the action name "Result data collection" and the action type ID "1" are set for the action ID "200", and the action name "210" is set for the action ID "210". "Facility abnormality", action type ID "1" are set, and action name "instruction download" and action type ID "3" are set for action ID "230".
[0050]
Also shown in FIG.actionThe program information table 123-2 is a table in which an action type name, a setting program, and an execution program are stored in correspondence with the action type ID.
[0051]
That is, in the action program information table 123-2 shown in FIG. 6, the action type name "data collection (file)", the setting program "SetCollectFile", and the execution program "CollectFileExec" are set for the action type ID "1". For the action type ID "2", the action type name "Data collection (DB)", the setting program "SetCollectDB", and the execution program "CollectDBExe" are set. "Download", a setting program "SetDownLoadFile", and an execution program "DownLoadFileExe" are set.
[0052]
The table 123-3 for each action type shown in FIG. 6 shows a table for data collection, and is a table in which a data collection file and collection contents are stored in correspondence with an action ID.
[0053]
That is, the table 123-3 for each action type shown in FIG. 6 indicates that the data collection file "Collect1.log" is set for the action ID "200".
[0054]
FIG. 7 is a flowchart showing the processing of the trigger setting unit shown in FIG.
[0055]
7, when the processing of the trigger setting unit 111 shown in FIG. 3 is started, first, the user selects one of the trigger type names registered in the trigger program information table 121-2 shown in FIG. (Step 201).
[0056]
Then, a setting program corresponding to the registered trigger type name is executed (Step 202). Then, the process of the job setting unit 111 ends.
[0057]
FIG. 8 is a flowchart showing an example of a process executed by the trigger setting program for each type selected in the process shown in FIG.
[0058]
The process shown in FIG. 8 indicates a process executed by the setting program when the trigger type is “fixed period”.
[0059]
In FIG. 8, when this process is started, first, a trigger name is input (step 211). Next, an interval to be generated at a fixed period is input (step 212).
[0060]
Then, the trigger table 121-1 shown in FIG. 5 is set (step 213). Here, the trigger name is set to the name of the trigger input in this program, that is, the trigger name input in step 211, the trigger ID is set by generating a unique ID, and the trigger type is set to a fixed period. It is set to the type ID that represents.
[0061]
Next, a table (periodic trigger table) 121-3 for each trigger type shown in FIG. 5 is set (step 214). Here, the trigger ID is set to the same ID as the trigger ID set in the trigger table 121-1, that is, the same ID as the ID set in step 213, and the fixed cycle is the value of the fixed cycle input in step 212. Is set. After that, this processing ends.
[0062]
FIG. 9 is a flowchart showing the processing of the action setting unit shown in FIG.
[0063]
In FIG. 9, when the processing of the action setting unit 113 shown in FIG. 3 is started, first, the user selects one of the action type names registered in the action program information table 123-2 shown in FIG. (Step 221).
[0064]
Then, a setting program corresponding to the registered action type name is executed (step 202). Then, the process of the action setting unit 113 ends.
[0065]
FIG. 10 is a flowchart illustrating an example of a process executed by the action setting program for each type selected in the process illustrated in FIG. 9.
[0066]
Note that the processing illustrated in FIG. 10 indicates processing executed by the setting program when the action type is “collect”.
[0067]
In FIG. 10, when this processing is started, first, an action name is input (step 231). Next, information necessary for data collection is input (step 232).
[0068]
Then, the action table 123-1 shown in FIG. 6 is set (step 233). Here, the action name is set to the name of the action input in this program, that is, the action name input in step 231, the action ID is set by generating a unique ID, and the action type represents collection. Set to the type ID.
[0069]
Next, a table (data collection table) 123-3 for each action type shown in FIG. 6 is set (step 234). Here, the action ID is set in the action table 123-1.actionThe same ID as the ID, that is, the same ID as the ID set in step 233 is set, the file name is set to the file name for data collection, and the data collection format sets which data is collected and how. . After that, this processing ends.
[0070]
FIG. 11 is a flowchart showing the processing of the job setting unit shown in FIG. In FIG. 11, when the processing of the job setting unit 112 shown in FIG. 3 is started, first, a list of triggers registered in the trigger table 121-1 shown in FIG. 5 is displayed and generated therein. A trigger is selected (step 241).
[0071]
Next, a list of actions registered in the action table 123-1 shown in FIG. 6 is displayed, and an action to be executed when the previously selected trigger occurs is selected from the list (step 242).
[0072]
Then, each ID of the selected combination of the trigger and the action is registered in the job table 122-1 shown in FIG. 4 (step 243), and the processing of the job setting unit 112 is ended.
[0073]
FIG. 12 is a flowchart illustrating a starting process by the trigger starting unit illustrated in FIG. 3.
[0074]
In the activation process shown in FIG. 12, first, the trigger ID of the job registered in the job table 122-1 shown in FIG. 4 is obtained (step 251).
[0075]
Next, the trigger ID is searched from the job table 122-1 shown in FIG. 4 to know the trigger type (step 252).
[0076]
Then, an execution program corresponding to the trigger type is searched from the trigger program information table 121-2 shown in FIG. 5, and the corresponding execution program is started. At this time, a trigger ID is passed as a start parameter of the execution program (step 253).
[0077]
Next, it is checked whether all jobs have been completed (step 226). If not completed (NO in step 254), the process returns to step 251. If it is determined that all jobs have been completed, (YES in step 254), and proceeds to step 255.
[0078]
In step 255, a job action ID registered in the job table 122-1 shown in FIG. 4 is obtained.
[0079]
Then, the action ID is searched from the action table 123-1 shown in FIG. 6 to know the action type (step 256).
[0080]
Next, an execution program corresponding to the action type is searched from the action program information table 123-2 shown in FIG. 6, and the corresponding execution program is started. At this time, an action ID is passed as a start parameter of the execution program (step 257).
[0081]
Then, it is checked whether all the jobs have been completed (step 258). If not all the jobs have been completed (NO in step 258), the process returns to step 255, but if it is determined that all the jobs have been completed, (YES in step 258), and ends this process.
[0082]
FIG. 13 is a flowchart showing processing by the execution program for each trigger activated by the processing shown in FIG.
[0083]
In FIG. 13, when this process is started, the table 121-3 for each trigger type shown in FIG. 5 based on the trigger ID passed at the time of activation, that is, for example, for each trigger type consisting of a fixed-cycle trigger table, A setting table is searched (step 261).
[0084]
Then, the setting contents for each type corresponding to the searched trigger ID are acquired (step 261). Here, the setting content for each type corresponding to the acquired trigger ID is, for example, an interval at which a trigger is generated at a fixed cycle in the fixed cycle trigger table.
[0085]
Next, preparations are made for generating a trigger based on the acquired information (step 263). Here, the preparation for generating a trigger based on the acquired information means that, for example, when the trigger type is a fixed period, a timer for generating a trigger is started for each period.
[0086]
Then, upon recognizing that the trigger has occurred, for example, when a timer interrupt occurs at a fixed period due to a fixed period trigger, an event notification is performed to the flow control unit 152 shown in FIG. In this event notification, a trigger ID is added and notified (step 264).
[0087]
Next, it is determined whether or not to end the processing (step 265). If not (NO in step 264), the process returns to step 263. If it is determined that the processing is ended (YES in step 265), the processing ends. .
[0088]
FIG. 14 is a flowchart showing the processing of the flow control unit shown in FIG.
[0089]
In FIG. 14, when the process of the flow control unit 152 shown in FIG. 3 is started, first, it waits for event reception (step 271).
[0090]
Then, it is checked whether an event has been received (step 272). If it is determined that the event has not been received (NO in step 272), the process returns to step 271. If it is determined that the event has been received (YES in step 272), the process returns to FIG. 4 based on the passed trigger ID. The corresponding job ID is obtained by searching the job table 122-1 (step 273), and searching the action table 123-1 shown in FIG.Type execution programIs acquired (step 274).
[0091]
Then, the occurrence of a trigger is notified to the action execution program for each action ID activated in the activation process shown in FIG. 12 (step 275).
[0092]
Next, it is determined whether or not to end the processing (step 276). If it is determined that the processing is not to be ended (NO in step 276), the process returns to step 271; The process ends.
[0093]
FIG. 15 is a flowchart showing the execution program initialization process for each action type started by the process of FIG.
[0094]
In FIG. 15, when this process is started, first, the action ID passed at the time of activation is used to set the table 123-3 for each action shown in FIG. 6, that is, for example, the setting for each action consisting of a data collection action table. The table is searched (step 281).
[0095]
Next, the setting contents for each type corresponding to the searched action ID, for example, the information of the collection file name and the collection format are acquired in the data collection action table (step 282).
[0096]
Then, processing for each type is performed (step 283). For example, in data collection, processing such as opening a specified data collection file is performed.
[0097]
In this state, when a trigger is notified from the flow control unit 152 shown in FIG. 3, execution processing specific to the action type such as data collection is performed in accordance with the settings (step 284).
[0098]
Next, it is determined whether or not to end the process (step 285). If it is determined that the process is not to be ended (NO in step 285), the process returns to step 284. The process ends.
[0099]
As described above, in the present embodiment, the data flow control device 10 is connected between the plurality of PLCs 20-1 and 20-2, the data file 40 and the user application 50, and the data flow control device 10 Since various triggers and various actions corresponding to the triggers are set in association with each other and a desired action corresponding to the triggers is automatically executed in response to the occurrence of the triggers, a plurality of PLCs 20-1 and 20-20 are configured. -2, the data flow between the data file 40 and the user application 50 can be easily controlled even if the number of trigger types and action types increases, and the development cost can be kept low.
[0100]
【The invention's effect】
As described above, according to the first aspect of the present invention, a trigger indicating the start timing of a process and an action indicating the actual content of the process are set in association with each other, and the trigger corresponding to the trigger is generated based on the occurrence of the trigger. To provide a data management method that can easily cope with an increase in the number of trigger types and action types, and that can keep the development cost low, because the configured actions are automatically executed. Can be.
[0101]
According to the second aspect of the present invention,Trigger setting means for setting a trigger indicating the start timing of the processing, action setting means for setting an action indicating the actual content of the processing, and setting in the action setting means corresponding to the trigger set in the trigger setting means Job setting means for setting a job by associating the set actions with each other, and control means for executing the action associated with the job setting means in response to occurrence of a trigger set by the trigger setting means. Therefore, it is possible to provide a data management apparatus that can easily cope with an increase in the number of triggers and the number of actions and that can reduce the development cost.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram showing an embodiment of a data flow control system configured by applying a data management method, a data management device, and a recording medium thereof according to the present invention.
FIG. 2 is a block diagram showing a detailed configuration of the data flow control device shown in FIG.
FIG. 3 is a functional block diagram showing a detailed operation of the data flow control device shown in FIG. 2;
FIG. 4 is a view showing an example of a job setting database (job setting DB) shown in FIG. 3;
FIG. 5 is a view showing an example of a trigger setting database (trigger setting DB) shown in FIG. 3;
FIG. 6 is a view showing an example of an action setting database (action setting DB) shown in FIG. 3;
FIG. 7 is a flowchart showing the processing of a trigger setting unit shown in FIG. 3;
FIG. 8 is a flowchart showing an example of a process executed by a trigger setting program for each type selected in the process shown in FIG. 7;
FIG. 9 is a flowchart showing the processing of the action setting unit shown in FIG. 3;
FIG. 10 is a flowchart showing an example of a process executed by an action setting program for each type selected in the process shown in FIG. 9;
FIG. 11 is a flowchart illustrating processing of a job setting unit illustrated in FIG. 3;
FIG. 12 is a flowchart showing activation processing by a trigger activation unit shown in FIG. 3;
FIG. 13 is a flowchart showing processing by an execution program for each trigger activated by the processing shown in FIG. 12;
FIG. 14 is a flowchart showing the processing of the flow control unit shown in FIG. 3;
FIG. 15 is a flowchart showing an execution program initialization process for each action type started by the process of FIG. 12;
[Explanation of symbols]
10 Data flow control device
11 Device setting tool
12 Setting table
13 Tag setting tool
14 Tag database
15 Service processing unit
16 Control module
17 Trigger module
18 Action Module
20-1, 20-2 PLC (Programmable Logic Controller)
30 FA Network
40 data files
50 User Application
60 Gateway
111 Trigger setting section
112 Job setting section
113 Action setting section
121 Trigger setting database (Trigger setting DB)
121-1 Trigger table
121-2 Trigger program information table
121-3 Table for Each Trigger Type
122 Job Setting Database (Job Setting DB)
122-1 Job table
123 Action Setting Database (Action Setting DB)
123-1 Action table
123-2 Action program information table
123-3 Table for each action type
151 Trigger activation unit
151-1 Trigger type 1 setting program
151-2 Trigger type 2 setting program
151-3 Trigger type 3 setting program
152 Flow control section
152-1 Action type 1 setting program
152-2 Action type 2 setting program
152-3 Action type 3 setting program
153-1 Trigger type 1 execution program
153-2 Trigger Type 2 Execution Program
153-3 Trigger Type 3 Execution Program
153-4 Trigger Type 4 Execution Program
154-1 Action type 1 execution program
154-2 Action type 2 execution program
154-3 Action type 3 execution program
154-4 Action type 4 execution program

Claims (2)

A data management method in a data management device that connects to a programmable logic controller via an FA network and manages data of the programmable logic controller,
For each of a plurality of trigger indicating the start timing of each process for the programmable logic controller, in association with the unique trigger ID and the trigger type execution program for generating the trigger set,
For each of a plurality of action that indicates the actual content of each process for the programmable logic controller, and a unique action ID and the action type execution program for executing the action to set corresponding,
Said plurality of triggers to be generated from the trigger is selected, the trigger is selected action to be performed when an error occurs, the combination of the selected triggers and actions made to correspond to the aforementioned trigger ID and the action ID By setting and storing the job,
By executing by activating the trigger type execution program, generating a trigger added with corresponding trigger ID, to identify the action ID corresponding to search the job the set based on the trigger ID, the specific A data management method characterized by executing an action type execution program corresponding to the action ID of (1) and automatically executing a desired action according to the job setting . A data management device that connects to the programmable logic controller via an FA network and manages data of the programmable logic controller,
Trigger setting means for setting a trigger type execution program for generating a trigger and a unique trigger ID in association with each of the plurality of triggers indicating the start timing of each process for the programmable logic controller,
Action setting means for setting an action type execution program for executing an action and a unique action ID in association with each of a plurality of actions indicating the actual contents of each process for the programmable logic controller,
Job setting means for setting a job of a combination of any one of the plurality of triggers and an action to be executed when the trigger occurs by associating the trigger ID with the action ID and storing the job When,
The trigger type execution program is read from the trigger setting means, the corresponding trigger ID is added by executing the trigger type execution program, an event notification is performed, and the job setting means is searched based on the trigger ID by the event notification. Control means for acquiring an action ID corresponding to the specified action ID, acquiring an action type execution program corresponding to the specific action ID acquired from the action setting means, and executing the action type execution program.
A data management device comprising:

Images