JPWO2020250276A1 - Indicator management system, indicator management method, engineering equipment and engineering program - Google Patents

Abstract

The index management system (200) includes an engineering device (100) and an operation system (201). The engineering device accepts the designation of a management index, a management target data group indicating the configuration of the operation system, and the management from the setting information data group for each index indicating the information set in the operation parameter group for each index. The setting information data group for the index is selected, the operation parameter group for the management index is generated based on the setting information data group for the management index and the management target data group, and the operation parameter group for the management index is generated. Is set in the operation system. The operation system calculates a management index value based on the operation parameter group for the management index.

Description

The present invention relates to a method for calculating an index for production control.

Production sites are managed by key performance indicators (KPI).
Patent Document 1 discloses a technique for calculating a highly accurate KPI for a production control system. In this technique, the first computer involved in production control sends an equipment index script to the second computer of the production system, receives the equipment index from the second computer, and calculates the KPI using the equipment index.

Japanese Unexamined Patent Publication No. 2016-170460

In Patent Document 1, a script is used to calculate the device index. Therefore, when the device index is redefined, it becomes necessary to review the entire script and correct the entire script. In addition, when developing a new system or when a device index is redefined, it is difficult to perform engineering to extract the data necessary for calculating the new index and store it in the database.

An object of the present invention is to make it possible to easily calculate an index value even when a new system is developed or an index to be managed is changed.

The index management system of the present invention is
An operation system that calculates the management index value based on a group of operation parameters for the management index, which is one or more parameters used to calculate the management index value.
It is provided with an engineering device for setting an operation parameter group for the management index in the operation system.
The engineering equipment is
Setting information for the management index from the setting information data group for each index that accepts the designation of the management index and the management target data group indicating the configuration of the operation system and indicates the information set in the operation parameter group for each index. The reception desk for selecting data groups and
A generation unit that generates an operation parameter group for the management index based on the setting information data group for the management index and the management target data group.
It is provided with a setting unit for setting an operation parameter group for the management index in the operation system.

According to the present invention, the management index value can be calculated according to the management index and the configuration of the operation system. Therefore, it is possible to easily calculate the index value even when a new system is developed or the index to be managed is changed.

The block diagram of the index management system 200 in Embodiment 1. FIG. The block diagram of the engineering apparatus 100 in Embodiment 1. FIG. The hardware configuration diagram of the operation system 201 in Embodiment 1. FIG. The flowchart of the index management method in Embodiment 1. The figure which shows the management target data group 300 in Embodiment 1. FIG. The figure which shows the setting information data group 310 in Embodiment 1. FIG. The figure which shows the operation parameter group 320 in Embodiment 1. FIG. The flowchart of the reception process (S110) in Embodiment 1. The figure which shows the index list data 301 in Embodiment 1. FIG. The figure which shows the data information data 311 in Embodiment 1. FIG. The figure which shows the storage condition data 312 in Embodiment 1. FIG. The figure which shows the table template data 313 in Embodiment 1. FIG. The figure which shows the plug-in definition data 314 in Embodiment 1. FIG. The figure which shows the index supply data 315 in Embodiment 1. FIG. The figure which shows the access information data 302 in Embodiment 1. FIG. The figure which shows the process information data 303 in Embodiment 1. FIG. The flowchart of the production process (S120) in Embodiment 1. The figure which shows the data list data 321 in Embodiment 1. FIG. The figure which shows the data acquisition parameter 322 in Embodiment 1. FIG. The figure which shows the data management parameter 323 in Embodiment 1. FIG. The figure which shows the storage table parameter 324 in Embodiment 1. FIG. The figure which shows the index calculation parameter 325 in Embodiment 1. FIG. The figure which shows the index supply parameter 326 in Embodiment 1. FIG. The figure which shows the index acquisition parameter 327 in Embodiment 1. FIG. The flowchart of the setting process (S130) in Embodiment 1. The flowchart of the operation process (S140) in Embodiment 1. The figure which shows the operation image of the data list data 321 in Embodiment 1. FIG. The figure which shows the operation image of the data acquisition parameter 322 in Embodiment 1. FIG. The figure which shows the operation image of the data management parameter 323 in Embodiment 1. FIG. The figure which shows the operation image of the storage table parameter 324 in Embodiment 1. FIG. The figure which shows the operation image of the index calculation parameter 325 in Embodiment 1. FIG. The figure which shows the operation image of the index supply parameter 326 in Embodiment 1. FIG. The figure which shows the operation image of the index acquisition parameter 327 in Embodiment 1. FIG. The figure which shows the setting information data group 310B in Embodiment 2. FIG. The figure which shows the acquisition condition data 316 in Embodiment 2. FIG. The figure which shows the access information data 302B in Embodiment 2. FIG. The flowchart of the production process (S120B) in Embodiment 2. The figure which shows the data list data 321B in Embodiment 2. FIG. The figure which shows the data acquisition parameter 322B in Embodiment 2. FIG. The figure which shows the data management parameter 323B in Embodiment 2. FIG. The flowchart of the setting process (S130B) in Embodiment 2. The flowchart of the operation process (S140B) in Embodiment 2. The figure which shows the operation image of the data list data 321B in Embodiment 2. FIG. The figure which shows the operation image of the data acquisition parameter 322B in Embodiment 2. FIG. The figure which shows the operation image of the data management parameter 323B in Embodiment 2. FIG. The figure which shows the configuration example of the operation system 201B in Embodiment 2. FIG. The figure which shows the configuration example of the operation system 201C in embodiment. The figure which shows the configuration example of the operation system 201D in embodiment. The figure which shows the configuration example of the plurality of operation system 201C in embodiment. The figure which shows the configuration example of the plurality of operation system 201D in embodiment. The hardware block diagram of the engineering apparatus 100 in embodiment.

In embodiments and drawings, the same or corresponding elements are designated by the same reference numerals. Descriptions of elements with the same reference numerals as the described elements will be omitted or simplified as appropriate. The arrows in the figure mainly indicate the flow of data or the flow of processing.

Embodiment 1.
The index management system 200 will be described with reference to FIGS. 1 to 33.

*** Explanation of configuration ***
The configuration of the index management system 200 will be described with reference to FIG.
The index management system 200 includes an engineering device 100 and an operation system 201.
The operation system 201 includes an index management device 210, an intermediary device 220, and a manufacturing device 230.
The engineering device 100, the index management device 210, the mediation device 220, and the manufacturing device 230 communicate with each other via a network.

The engineering device 100 includes elements such as a reception unit 111, a generation unit 112, and a setting unit 113. These elements are realized by software.

The index management device 210 includes an index management unit 211. The index management unit 211 is realized by software.

The intermediary device 220 includes elements such as an index supply unit 221, an index calculation unit 222, and a data management unit 223. These elements are realized by software.
Further, the intermediary device 220 includes a database 229. The database 229 is realized by a storage device.

The manufacturing apparatus 230 includes a data supply unit 231. The data supply unit 231 is realized by software.

The configuration of the engineering device 100 will be described with reference to FIG.
The engineering device 100 is a computer including hardware such as a processor 101, a main storage device 102, an auxiliary storage device 103, an input / output device 104, a communication device 105, and a display device 106. These hardware are connected to each other via signal lines.

The processor 101 is an IC that performs arithmetic processing and controls other hardware. For example, the processor 101 is a CPU.
CPU is an abbreviation for Central Processing Unit.

The main storage device 102 is a main memory. For example, the main storage device 102 is a RAM. The data stored in the main storage device 102 is stored in the auxiliary storage device 103 as needed.
RAM is an abbreviation for Random Access Memory.

The auxiliary storage device 103 is a non-volatile storage device. For example, the auxiliary storage device 103 is a ROM, an HDD, or a flash memory. The data stored in the auxiliary storage device 103 is loaded into the main storage device 102 as needed.
ROM is an abbreviation for Read Only Memory.
HDD is an abbreviation for Hard Disk Drive.

The input / output device 104 is an input device and an output device. For example, the input device is a keyboard and mouse, and the output device is a speaker.

The communication device 105 is a receiver and a transmitter. For example, the communication device 105 is a communication chip or NIC.
NIC is an abbreviation for Network Interface Card.

The display device 106 is a display. For example, the display device 106 is a liquid crystal display.

The engineering device 100 includes elements such as a reception unit 111, a generation unit 112, and a setting unit 113. These elements are realized by software.

The auxiliary storage device 103 stores an engineering program for operating the computer as a reception unit 111, a generation unit 112, and a setting unit 113. The engineering program is loaded into the main storage 102 and executed by the processor 101.
The auxiliary storage device 103 further stores the OS. At least a portion of the OS is loaded into main storage 102 and executed by processor 101.
The processor 101 executes an engineering program while executing an OS.
OS is an abbreviation for Operating System.

The input / output data of the engineering program is stored in the storage unit 190.
The main storage device 102 functions as a storage unit 190. However, a storage device such as an auxiliary storage device 103, a register in the processor 101, and a cache memory in the processor 101 may function as a storage unit 190 in place of the main storage device 102 or together with the main storage device 102. ..

The engineering device 100 may include a plurality of processors that replace the processor 101. The plurality of processors share the role of the processor 101.

The engineering program can be computer-readablely recorded (stored) on a non-volatile recording medium such as an optical disc or flash memory.

The hardware configuration of each device in the operation system 201 will be described with reference to FIG.
Each of the index management device 210, the intermediary device 220, and the manufacturing device 230 is a computer, and is equipped with various hardware like the engineering device 100 (to be precise, the manufacturing device 230 has a computer (possibility of a plurality of units). Yes), sensors, actuators, machines, etc. are included. However, this index management system does not engineer equipment other than computers for index calculation, so it is excluded.)
Specifically, each device includes hardware such as a processor 291, a main storage device 292, an auxiliary storage device 293, an input / output device 294, a communication device 295, and a display device 296. However, the manufacturing device 230 may not include the input / output device 294 and the display device 296.

The auxiliary storage device 293 stores an application program for causing a computer to execute software elements of each device. The application program is loaded into main storage 292 and executed by processor 291.
The OS is further stored in the auxiliary storage device 293. At least a portion of the OS is loaded into main memory 292 and executed by processor 291.
The processor 291 executes the application program while executing the OS.
However, the manufacturing apparatus 230 may not be equipped with an OS.

The input / output data of the application program is stored in the storage unit.
The storage unit is realized by a storage device such as a main storage device 292, an auxiliary storage device 293, a register in the processor 291 and a cache memory in the processor 291.

The application program can be computer-readablely recorded (stored) in a non-volatile recording medium such as an optical disk or flash memory.

*** Explanation of operation ***
The operation of the index management system 200 corresponds to the index management method. The procedure of the index management method corresponds to the procedure of the index management program.
The operation of the engineering device 100 corresponds to the engineering method. In addition, the procedure of the engineering method corresponds to the procedure of the engineering program.

An index management method will be described with reference to FIG. The flow of the index management method is as follows.
In step S110, the engineering device 100 receives the management index and the management target data group 300, and selects the setting information data group 310 for the management index from the setting information data group 310 for each index. Here, the management index is an index to be managed.
In step S120, the generation unit 112 generates the operation parameter group 320 based on the setting information data group 310 for the management index and the management target data group 300.
In step S130, the setting unit 113 sets the operation parameter group 320 in the operation system 201 by communicating with the operation system 201.
In step S140, the operation system 201 calculates the management index value using the operation parameter group 320.
The outline of the management target data group 300, the setting information data group 310, and the operation parameter group 320 that appear in the present embodiment will be described below.

FIG. 5 shows the managed data group 300.
The management target data group 300 is a data group in which the user has engineered the index management system 200.
The management target data group 300 includes access information data 302 and process information data 303.
The access information data 302 and the process information data 303 will be described later.

FIG. 6 shows the setting information data group 310.
The setting information data group 310 is a parameter group for creating an operation parameter group 320 together with the management target data group 300.
The setting information data group 310 includes data information data 311, storage condition data 312, table template data 313, plug-in definition data 314, and index supply data 315.
Each parameter included in the setting information data group 310 will be described later.

FIG. 7 shows the operation parameter group 320.
The operation parameter group 320 is a parameter group for operating the index management system 200.
The operation parameter group 320 includes data list data 321, data acquisition parameter 322, data management parameter 323, storage table parameter 324, index calculation parameter 325, index supply parameter 326, and index acquisition parameter 327.
Each parameter included in the operation parameter group 320 will be described later.

Returning to FIG. 4, a description will be given from S110.
In step S110, the engineering device 100 receives the management index and the management target data group 300, and selects the setting information data group 310 for the management index from the setting information data group 310 for each index. Here, the management index is an index to be managed.

The procedure of the reception process (S110) will be described with reference to FIG.
In step S111, the reception unit 111 receives the management index.

For example, the reception unit 111 accepts the management index as follows.
First, the reception unit 111 displays the index list shown in the index list data 301 on the display.
Next, the user selects a management index from the index list and specifies the management index using the input device.
Then, the reception unit 111 receives the designated management index.

FIG. 9 shows a specific example of the index list data 301.
The index list data 301 is data indicating the index list, and is stored in advance in the storage unit 190.
The index list includes indicators such as "non-defective rate". For example, the reception unit 111 accepts the "non-defective product rate" as a management index.

Returning to FIG. 8, the description will be continued from step S112.
In step S112, the reception unit 111 selects the setting information data group 310 for the management index from the setting information data group 310 for each index.

FIG. 6 shows a specific example of the setting information data group 310.
The setting information data group 310 is prepared for each index, and the setting information data group 310 for each index is stored in advance in the storage unit 190. For example, the reception unit 111 selects the setting information data group 310 for the “non-defective product rate”.

Data information The data 311 specifies a data set used for calculating the index value. Data information The data set specified by the data 311 is referred to as a "target data set".
The storage condition data 312 specifies a condition for storing the target data set (excluding the completion flag).
The table template data 313 indicates a template of the table in which the target data set (excluding the completion flag) is stored.
The plug-in definition data 314 specifies a plug-in for calculating an index value.
The index supply data 315 specifies a method for supplying the index.

FIG. 10 shows a specific example of data information data 311 for “non-defective product rate”.
Data information Data 311 specifies to read the data values of the two datasets in order to calculate the "non-defective rate".
The set (1) is a data set consisting of an "ID", an "input time", and a "input completion flag".
The set (2) is a data set consisting of "ID", "inspection time", "inspection result", and "inspection completion flag".
The data type of "ID" is unsigned 16 bits.
The data type of "input time" and "inspection time" is unsigned 32 bits.
The data type of the "inspection result" is unsigned 16 bits.
The data type of "input completion flag" and "inspection completion flag" is a bit.

FIG. 11 shows a specific example of the storage condition data 312 for the “non-defective product rate”.
The storage condition data 312 specifies a storage condition (1) and a storage condition (2).
The storage condition (1) is a condition for storing the set (1).
The storage condition (2) is a condition for storing the set (2).

FIG. 12 shows a specific example of the table template data 313 for the “non-defective product rate”.
The table template data 313 shows a template of the input table and a template of the inspection table.
The input table is a table in which the set (1) is stored. The input table template indicates the data format of each data included in the set (1).
The inspection table is a table in which the set (2) is stored. The template of the inspection table indicates the data format of each data included in the set (2).
Moreover, the column name of the table and the data name in the data set correspond to each other.

FIG. 13 shows a specific example of the plug-in definition data 314 for “non-defective product rate”.
The plug-in definition data 314 specifies a plug-in name. Functions executed by plug-ins are called plug-in functions.
The plug-in definition data 314 specifies an argument to be set in the plug-in function.

FIG. 14 shows a specific example of the index supply data 315 for “non-defective product rate”.
The index supply data 315 specifies a method name and a function (including an argument).

Returning to FIG. 8, the description will be continued from step S113.
In step S113, the reception unit 111 receives the access information data 302.
The access information data 302 is data indicating access information of each device in the operation system 201.
The access information is information used to access each device.

A specific example of the access information data 302 will be described with reference to FIG.
The user performs the following operations using the input / output device 104 and the display device 106.
The user illustrates the intermediary device 220 and the manufacturing device 230. Since each is one, it is shown as an intermediary device 1 and a manufacturing device 1.
The user illustrates the data management unit 223, the index supply unit 221 and the database 229 in the intermediary device 220. Since there is only one database, it is shown as DB1. The user designates the URI of the index supply unit 221. URI is an abbreviation for Uniform Resource Identifier and is an example of a resource identifier. The user specifies the IP address of the database 229 and the data source name of the database 229. As the IP address of the database 229, the upper system IP address and the lower system IP address are specified. The higher-level IP address is an IP address for connecting the index calculation unit 222 and the database 229. The lower-level IP address is an IP address for connecting the data management unit 223 and the database 229. IP is an abbreviation for Internet Protocol, and IP address is an example of an address.
The user illustrates one or more controllers (A, B) in the manufacturing apparatus 230. The user specifies the IP address of each controller.
Access information such as URIs, IP addresses and data source names can be set graphically by clicking on the components.

The reception unit 111 generates data indicating the illustrated information. The generated data is the access information data 302.

Returning to FIG. 8, step S114 will be described.
In step S114, the reception unit 111 receives the process information data 303.

A specific example of the process information data 303 will be described with reference to FIG.
The user illustrates the process flow to be managed. The process flow includes an assembly process and an inspection process.
The user illustrates the controller used in each process. Controller A is used in the assembly process and controller B is used in the inspection process.
The user specifies the data set information to be acquired in each process. Further, from FIG. 16, the data set of the controller A (excluding the completion flag) is a set of "ID" and "input time", and is registered in the "input table". At this time, it is also specified which database 229 to put this table in (DB1 in this example). The data set of the controller B (excluding the completion flag) is a set of "ID", "inspection time", and "inspection result", and is registered in the "inspection table". At this time as well, as in the case of the "input table", the database 229 to which the "inspection table" is stored is also specified (DB1 in this example). Further, the user specifies a communication protocol and an acquisition cycle for acquiring the data value of each data set. The management index "non-defective rate" is automatically set.
Each dataset can be selected from the datasets (1) and (2) listed in the data information data 311.

The reception unit 111 generates data indicating the illustrated information. The generated data is the process information data 303.

Returning to FIG. 4, the description will be continued from step S120.
In step S120, the generation unit 112 generates the operation parameter group 320 based on the setting information data group 310 for the management index and the management target data group 300.

The procedure of the generation process (S120) will be described with reference to FIG.
In step S121, the generation unit 112 generates the data list data 321 based on the data information data 311, the access information data 302, and the process information data 303.
The data list data 321 is a list of data sets (target data sets) used for calculating the management index value.

FIG. 18 shows a specific example of the data list data 321.
The data list data 321 indicates a data set (target data set) acquired from each controller. Further, the data list data 321 indicates a communication protocol and an acquisition cycle for acquiring data in real time from each controller.

The generation unit 112 acquires each controller name from the access information data 302, and sets each controller name in the data list data 321.
The generation unit 112 confirms the data set information (excluding the completion flag) of each controller with reference to the process information data 303, acquires the data set information (excluding the completion flag) of each controller from the data information data 311. The data set information of each controller is set in the data list data 321.
The generation unit 112 acquires the communication protocol and acquisition cycle of each data set from the process information data 303, and sets the communication protocol and acquisition cycle of each data set in the data list data 321.

Returning to FIG. 17, the description will be continued from step S122.
In step S122, the generation unit 112 generates the data acquisition parameter 322 based on the access information data 302 and the data list data 321.
The data acquisition parameter 322 indicates a rule for acquiring the data value of the target data set (excluding the completion flag) from each controller.

FIG. 19 shows a specific example of the data acquisition parameter 322.
The data acquisition parameter 322 indicates the acquisition data information. The acquired data information is information of data acquired from each controller.
Further, the data acquisition parameter 322 indicates the IP address of each controller.

The generation unit 112 acquires the acquired data information from the data list data 321 and sets the acquired data information in the data acquisition parameter 322.
The generation unit 112 acquires each controller name from the data list data 321 and sets each controller name in the data acquisition parameter 322.
The generation unit 112 acquires the IP address of each controller from the access information data 302, and sets the IP address of each controller in the data acquisition parameter 322.

Returning to FIG. 17, the description will be continued from step S123.
In step S123, the generation unit 112 generates the data management parameter 323 based on the access information data 302 and the process information data 303.
Data management parameter 323 indicates a rule for managing the target data set (excluding the completion flag).

A specific example of the data management parameter 323 is shown with reference to FIG.
The data management parameter 323 indicates a “storage condition”, a “storage data”, a “storage table”, and a “storage DB” for each data set (excluding the completion flag) stored in the database 229.
The “storage condition” indicates the condition of the data set stored in the database 229.
“Stored data” indicates information on the data set stored in the database 229.
The "storage table" indicates the name of the table in which the data values of the data set are stored.
The “storage DB” indicates an identifier of the database 229 in which the data value of the data set is stored.

The generation unit 112 acquires the storage condition of the data value of each data set (excluding the completion flag) from the storage condition data 312, and sets the storage condition of the data value of each data set (excluding the completion flag) to the data management parameter 323. Set.
The generation unit 112 acquires each data set information from the process information data 303, and sets each data set information in the data management parameter 323.
The generation unit 112 acquires the storage table name of the data value of each data set from the process information data 303, and sets the storage table name of the data value of each data set in the data management parameter 323.
The generation unit 112 acquires the identifier of the database 229 from the access information data 302 and the process information data 303, and sets the identifier of the database 229 specified by the process information data 303 for each data set.

Returning to FIG. 17, the description will be continued from step S124.
In step S124, the generation unit 112 generates the storage table parameter 324 based on the process information data 303 and the table template data 313.
The storage table parameter 324 identifies the table template data 313 in which the data value of the target data set (excluding the completion flag) is stored, and matches the data set (excluding the completion flag) of the process information data 303 based on the table template data 313. Create a table (storage table).
A storage table for each database is created using the storage table parameter 324.

FIG. 21 shows a specific example of the storage table parameter 324.
The storage table parameter 324 indicates the data structure (data type, etc.) of the storage table for each data set (excluding the completion flag).
The generation unit 112 acquires each data set information from the process information data 303, and sets each data set information in the storage table parameter 324.
The generation unit 112 acquires the storage table name of each data set from the process information data 303, and sets the storage table name of the data value of each data set in the storage table parameter 324.
The generation unit 112 acquires the data structure information of each storage table from the table template data 313, and sets the data structure information of each storage table in the storage table parameter 324.

Returning to FIG. 17, the description will be continued from step S125.
In step S125, the generation unit 112 generates the index calculation parameter 325 based on the access information data 302, the process information data 303, and the plug-in definition data 314.
The index calculation parameter 325 indicates a rule for calculating the management index value.

FIG. 22 shows a specific example of the index calculation parameter 325.
The index calculation parameter 325 indicates a "plug-in", a "plug-in function", a "table name", a "process name", and a "DB designated data".
"Plug-in" indicates a plug-in name.
"Plug-in function" indicates the name of the plug-in function. Conditions for calculating the index are set in the argument of the plug-in function.
"Table name" indicates the name of each storage table. The "process name" indicates which process the data in each table is. The process name is necessary for the index calculation unit to grasp the process range for calculating the index.
The "DB designated data" indicates the access information of the database 229 including each storage table.

The generation unit 112 acquires the plug-in name and the plug-in function information from the plug-in definition data 314, and sets the plug-in name and the plug-in function information in the index calculation parameter 325.
The generation unit 112 acquires each storage table name from the process information data 303, and sets each storage table name in the index calculation parameter 325.
The generation unit 112 acquires the process name to which each storage table belongs from the process information data 303, and sets the process name in the index calculation parameter 325.
The generation unit 112 acquires the access information of the database 229 specified by the process information data 303 from the access information data 302, and sets the access information of the database 229 in the index calculation parameter 325.

Returning to FIG. 17, the description will be continued from step S126.
In step S126, the generation unit 112 generates the index supply parameter 326 based on the index supply data 315.

FIG. 23 shows a specific example of the index supply parameter 326.
The indicator supply parameter 326 shows the method and function used to supply the indicator value. Methods and functions have arguments that enter conditions for calculating indicators.

Returning to FIG. 17, the description will be continued from step S127.
In step S127, the generation unit 112 generates the index acquisition parameter 327 based on the access information data 302 and the index supply data 315.

FIG. 24 shows a specific example of the index acquisition parameter 327.
The index acquisition parameter 327 indicates the URI of the index supply unit 221. The URI of the index supply unit 221 is information (access information) used to access the index supply unit 221.
The index acquisition parameter 327 indicates a method used for acquiring the index value. Conditions for calculating the index are set in the argument of the method.

Returning to FIG. 4, the description will be continued from step S130.
In step S130, the setting unit 113 sets the operation parameter group 320 in the operation system 201 by communicating with the operation system 201.

The procedure of the setting process (S130) will be described with reference to FIG. 25.
In step S131, the setting unit 113 sets the index acquisition parameter 327 in the index management unit 211 by communicating with the index management device 210.

In step S132, the setting unit 113 sets the index supply parameter 326 to the index supply unit 221 by communicating with the intermediary device 220.
The setting unit 113 sets the index calculation parameter 325 in the index calculation unit 222 by communicating with the intermediary device 220.
The setting unit 113 sets the storage table parameter 324, the data management parameter 323, the data acquisition parameter 322, and the data list data 321 in the data management unit 223 by communicating with the intermediary device 220. At this time, the setting unit 113 creates a table in the database using the storage table parameter 324 (in the case of index change, the table and the column of the table are added / deleted).

In step S133, the setting unit 113 sets the data list data 321 in the data supply unit 231 by communicating with the manufacturing apparatus 230.
Then, the user changes the control program so that the data is put in the variable of the list data name.

Returning to FIG. 4, step S140 will be described.
In step S140, the operation system 201 calculates the management index value using the operation parameter group 320.

The procedure of the operation process (S140) will be described with reference to FIG. 26.
In step S141, the data supply unit 231 stores the data in the variable of the data list data 321. As a result, each controller obtains the data value of the target data set (excluding the completion flag).
Each controller saves the data value of each target data set (excluding the completion flag), and sets "ON" to the completion flag corresponding to each target data set.

In step S142, the data management unit 223 accesses each controller by using the access information (IP address) of each controller specified in the data acquisition parameter 322.
Next, the data management unit 223 acquires the data value of the target data set from each controller in the acquisition cycle specified in the data list data 321. The target data set is specified in the data list data 321. When acquiring the data value of the target data set (excluding the completion flag), the data management unit 223 communicates with each controller by the communication protocol specified in the data list data 321.
Next, the data management unit 223 selects a target data set (excluding the completion flag) that matches the storage conditions specified in the data management parameter 323, and the data value of the selected target data set (excluding the completion flag). Is stored in the database table specified in the data management parameter 323. When storing the data value of the target data set (excluding the completion flag), the data management unit 223 refers to the storage table parameter 324. The data structure information of the storage table is set in the storage table parameter 324. In addition, the data of the data set (excluding the completion flag) is stored in the column having the same column name as the data name. The same column name as the data name is described in the storage table parameter 324.
Then, the data management unit 223 sets "OFF" in the completion flag of the stored target data set.

In step S143, the index management unit 211 accesses the index supply unit 221 using the address information (URI) specified in the index acquisition parameter 327.
Then, the index management unit 211 executes the method specified in the index acquisition parameter 327. When executing the method, the index management unit 211 sets computable calculation conditions in the argument of the method. As a result, the index management unit 211 requests the index supply unit 221 for the management index value.
Step S143 is executed at an arbitrary timing.

In step S144, the index supply unit 221 requests the index calculation unit 222 to calculate the management index value based on the index supply parameter.
Specifically, the index supply unit 221 notifies the index calculation unit 222 of the conditions for calculating the index set in the argument of the method executed in step S143.

In step S145, the index calculation unit 222 executes the plug-in specified in the index calculation parameter 325. As a result, the management index value that matches the calculation condition is calculated using the data value of the data set (excluding the completion flag).
Then, the index calculation unit 222 notifies the index supply unit 221 of the management index value.

For example, the management index "non-defective product rate" is calculated as follows.
First, the index calculation unit 222 calculates the number of records for which the inspection result "good product" is set by searching the inspection table containing the data of the inspection process. One record corresponds to one row in the database. The calculated number is referred to as "the number of non-defective products". Next, the index calculation unit 222 calculates the number of records stored in the input table containing the data of the assembly process. The calculated number is referred to as "input number".
Then, the index calculation unit 222 calculates the ratio of the number of non-defective products to the number of inputs (= number of non-defective products / number of inputs). The calculated ratio is the "non-defective product rate".

In step S146, the index supply unit 221 supplies the management index value to the index management unit 211 by executing the method specified in the index supply parameter 326.

27 to 33 show the relationship between the output image of the engineering device 100 and the operation image of the operation system 201. In each figure, the upper row is the output image and the lower row is the operation image.
The output image is each parameter of the operation parameter group 320.
The operational image is, for example, a memory image or a table image.
The program of the operation system 201 is usually created by using a compiled language. However, the part of the operation image of FIGS. 28, 29, 31, 32 and 33 may be created in a script language. This makes it possible to easily change the operational images of FIGS. 28, 29, 31, 32 and 33.

In FIG. 27, the operation image of the data list data 321 is the same as that of the data list data 321.

In FIG. 28, the operation image corresponding to the data list data 321 and the data acquisition parameter 322 represents the following contents.
The "data list data" is acquired from the controller A at the address A and the controller B at the address B in the "acquisition cycle" using the "communication protocol".

In FIG. 29, the operation image of the data management parameter 323 represents the following contents.
When the "input completion flag is ON", the "ID and input time" are inserted into the "input table" of the storage DB (1).
When the "inspection completion flag is ON", the "ID, inspection time, inspection result" is inserted into the "inspection table" of the storage DB (2).

In FIG. 30, the operation image of the storage table parameter 324 is the same as that of the storage table parameter 324.

In FIG. 31, the operation image of the index calculation parameter 325 represents the following contents.
For "calculation conditions" (in this example, the calculation process is from the assembly process to the inspection process), the number of records (1) whose inspection result is 1 (good product) is calculated from the "inspection table" of the DB corresponding to the inspection process. calculate. The total number of records (2) in the "input table" of the DB corresponding to the assembly process is calculated. The value obtained by calculating (1) / (2) is used as an index value.

In FIG. 32, the operational image of the index supply parameter 326 represents the following contents.
The index "non-defective rate" can be provided for various conditions (computable calculation process, period, etc.). Notify the index calculation unit of the arguments that specify them. In this example, the computable calculation process is from the assembly process to the inspection process.

In FIG. 33, the operational image of the index acquisition parameter 327 represents the following contents.
The index "non-defective rate" is acquired from the index supply unit for the calculation process and period that can be calculated at any timing. The URI of the intermediary device is "opc.tcp: // ...".

*** Supplement to Embodiment 1 ***
In step S111, the reception unit 111 may accept the calculation method together with the management index. The calculation method is a method for calculating a management index. In this case, the setting information data group 310 is prepared for each index calculation method. Then, in step S112, the generation unit 112 extracts the setting information data group 310 for the calculation method specified by the management index.
If the data type of the management index is not determined when accepting the management index in step S111, the reception unit 111 may accept the data type of the management index together with the management index. In this case, the generation unit 112 creates the same setting information data group as in FIGS. 10 to 14, and then the same processing is performed.
Further, the reception unit 111 may receive the data used for the management index calculation and the data type thereof when receiving the calculation method. In this case, the generation unit 112 creates the same setting information data group as in FIGS. 10 to 14, and then the same processing is performed.

A supplement is provided for step S114, step S124, and step S142.
In S114, each data set (excluding the completion flag) is input at the same time. That is, each data set (excluding the completion flag) is input collectively in one operation. This makes it possible to prevent input omission.
Also, whether the data name is the same or the database table name is the same in this paragraph is determined by the name with the suffix (described later).
When the same data is acquired in a plurality of steps by the same calculation method, the data name of the data set and the database table name may be duplicated. In that case, add a suffix to all data names and database names, and enter all data sets (excluding the completion flag) of the calculation method. The suffix is specified by the user. Examples of how to add a suffix are "ID_assembly process, input time_assembly process", "ID_inspection process, inspection time_inspection process, inspection result_inspection process" and the like. Suffixes to the completion flag and table name as well (the suffixes to the dataset (including the completion flag) and the table name do not necessarily have to be the same).
On the other hand, when setting other indicators, if the same process has the same data set (excluding the completion flag) and the database table name is the same, the data set (excluding the completion flag) is added to the process information data 303. Set only the index name without registering. If the same data set has a different database table name, register the database table name and data set data name with a suffix.
When setting other indicators, if the data with the same data name is part of the dataset (excluding the completion flag) in the same process and the table name is the same, do as follows. Only the data that does not overlap in the process information data 303 is registered with the same suffix as the other data names in the same table (when the other data names or table names in the same table do not have the suffix but the data names are duplicated). Adds a suffix to the data name and table name). At this time, when adding the column name to the storage table parameter 324 at the time of the generation process of step S124, the name without the suffix is added. Further, when the data of the data set (excluding the completion flag) is stored in the database 229 during the operation process of step S142, it is stored in the column having the same column name as the data name having no suffix.

When removing a certain index, the data that does not need to be acquired once the index is removed in the setting of each process of the process information data 303 is removed, and the description of the index is also removed.

*** Effect of Embodiment 1 ***
According to the first embodiment, the management index value can be calculated according to the management index and the configuration of the operation system. Therefore, it is possible to easily calculate the index value even when a new system is developed or the index to be managed is changed. Then, the method of connecting the production site and the application can be easily realized without waste. Furthermore, by automating the method, mistakes can be reduced.

Embodiment 2.
The mode in which the acquisition condition data 316 is used instead of the storage condition data 312 will be described mainly different from the first embodiment with reference to FIGS. 34 to 46.

*** Explanation of configuration ***
The configuration of the index management system 200 is the same as the configuration in the first embodiment except that the configuration of the operation system 201 of FIG. 1 is the configuration of the operation system 201B of FIG. 46 (FIGS. 1 to 3, FIG. 46).

The configuration of the setting information data group 310B will be described with reference to FIG. 34.
The setting information data group 310B includes acquisition condition data 316 instead of the storage condition data 312 described in the first embodiment.
The acquisition condition data 316 indicates a condition for acquiring the data value of the target data set (excluding the completion flag).

FIG. 35 shows a specific example of the acquisition condition data 316 for the “non-defective product rate”.
The acquisition condition data 316 specifies the acquisition condition (1) and the acquisition condition (2).
The acquisition condition (1) is a condition for acquiring the set (1).
The acquisition condition (2) is a condition for acquiring the set (2).

*** Explanation of operation ***
The procedure of the index management method is the same as the procedure in the first embodiment (see FIG. 4).
However, the access information data 302B created in step S113 of the reception process (S110), a part of the generation process (S120), a part of the setting process (S130), and a part of the operation process (S140) are in the first embodiment. Different from processing.

A specific example of the access information data 302B will be described with reference to FIG. 36.
The user performs the following operations using the input / output device 104 and the display device 106.
The user illustrates the intermediary device 220B and the manufacturing device 230B. Since each is one, it is shown as an intermediary device 1 and a manufacturing device 1.
The user illustrates the index supply unit 221 and the database 229 in the intermediary device 220B. Since there is only one database, it is shown as DB1. The user designates the URI of the index supply unit 221. The user specifies the IP address of the database 229 and the data source name of the database 229. As the IP address of the database 229, the upper system IP address and the lower system IP address are specified. The higher-level IP address is an IP address for connecting the index calculation unit 222 and the database 229. The lower-level IP address is an IP address for connecting the data management unit 223B and the database 229.
The user illustrates the data management unit 223B and one or more controllers (A, B) in the manufacturing apparatus 230B. The user specifies the IP address of each controller.
Access information such as URIs, IP addresses and data source names can be set graphically by clicking on the components.

The reception unit 111 generates data indicating the illustrated information. The generated data is the access information data 302B.

The procedure of the generation process (S120B) will be described with reference to FIG. 37.
Steps S121B to S123B are different from the processing in the first embodiment (see FIG. 17). Steps S124 to S127 are as described in the first embodiment.

In step S121B, the generation unit 112 generates data list data 321B based on the data information data 311, the access information data 302B, and the process information data 303.

FIG. 38 shows a specific example of the data list data 321B.
The data list data 321B separately shows the data set of each controller and the completion flag corresponding to the data set. That is, here the completion flag is not included in the dataset.

The generation unit 112 acquires each controller name from the access information data 302B, and sets each controller name in the data list data 321B.
The generation unit 112 confirms the data set information of each controller with reference to the process information data 303, acquires the data set information of each controller from the data information data 311 and collects the data list (completion flag) from the data set information of each controller. ) Is acquired, and the data list of each controller is set to the data list data 321B for each data set. The generation unit 112 acquires a completion flag list from the data set information of each controller, sets the completion flag list of each controller in the data list data 321B, and sets the correspondence with the data set.
The generation unit 112 acquires the communication protocol and acquisition cycle of each data set from the process information data 303, and sets the communication protocol of each data set and the acquisition cycle of the completion flag in the data list data 321B.

Returning to FIG. 37, the description will be continued from step S122B.
In step S122B, the generation unit 112 generates the data acquisition parameter 322B based on the access information data 302B, the data list data 321B, and the acquisition condition data 316.

FIG. 39 shows a specific example of the data acquisition parameter 322B.
The data acquisition parameter 322B indicates the acquisition data information. Further, the data acquisition parameter 322B indicates the IP address of each controller.

Further, the data acquisition parameter 322B indicates a set of acquisition conditions and acquisition data set information. The data set information that forms a pair with the acquisition condition is the information of the data set that is acquired when the acquisition condition is satisfied.
The generation unit 112 acquires the acquisition condition from the acquisition condition data 316, and acquires the data set information corresponding to the completion flag included in the acquisition condition from the data list data 321B. Then, the generation unit 112 sets the set of the acquisition condition and the data set information in the data acquisition parameter 322B.
The other data generation method of the data acquisition parameter 322B is the same as the generation method in the first embodiment.

Returning to FIG. 37, step S123B will be described.
In step S123B, the generation unit 112 generates the data management parameter 323B based on the access information data 302B, the process information data 303, and the acquisition condition data 316.

FIG. 40 shows a specific example of the data management parameter 323B.
The data management parameter 323B indicates a “storage condition”, a “storage data”, a “storage table”, and a “storage DB” for each data set stored in the database 229.

Since the acquisition condition and the storage condition are the same in the second embodiment, the generation unit 112 acquires the storage condition of the data value of each data set from the acquisition condition data 316, and sets the storage condition of the data value of each data set as a data management parameter. Set to 323B.
The generation unit 112 acquires each data set information from the process information data 303, and sets each data set information in the data management parameter 323B.
The generation unit 112 acquires the storage table name of the data value of each data set from the process information data 303, and sets the storage table name of the data value of each data set in the data management parameter 323B.
The generation unit 112 acquires the identifier of the database 229 specified by the process information data 303 from the access information data 302B, and sets the identifier of the database 229 for each data set.

The procedure of the setting process (S130B) will be described with reference to FIG. 41.
Step S132B and step S133B are different from the processing in the first embodiment (see FIG. 25).
Step S131 is as described in the first embodiment.

In step S132B, the setting unit 113 sets the index supply parameter 326 to the index supply unit 221 by communicating with the intermediary device 220B.
The setting unit 113 sets the index calculation parameter 325 in the index calculation unit 222 by communicating with the intermediary device 220B.
The setting unit 113 sets the storage table parameter 324 in the intermediary device 220B by communicating with the intermediary device 220B. At this time, the setting unit 113 creates a table in the database using the storage table parameter 324 (in the case of index change, the table and the column of the table are added / deleted).

In step S133B, the setting unit 113 sets the storage table parameter 324, the data management parameter 323B, the data acquisition parameter 322B, and the data list data 321B in the data management unit 223B by communicating with the manufacturing apparatus 230B, and sets the data list data 321B. Is set in the data supply unit 231.
Then, the user changes the control program of the controller so that the data is put in the variable of the list data name.

The procedure of the operation process (S140B) will be described with reference to FIG. 42.
Step S142B is different from the process in the first embodiment (see FIG. 26).
Step S141 is as described in the first embodiment. Steps S143 to S145 are as described in the first embodiment.

In step S142B, the data management unit 223B accesses each controller using the access information (IP address) of each controller specified in the data acquisition parameter 322B.
Next, the data management unit 223B acquires the completion flag from each controller in the acquisition cycle specified in the data list data 321B. The acquired completion flag is the completion flag specified in the data acquisition parameter 322B.
Next, the data management unit 223B acquires the data value of the target data set corresponding to the completion flag satisfying the acquisition condition. The target data set corresponding to the completion flag is specified in the data acquisition parameter 322B.
Next, the data management unit 223B stores the acquired data value of the target data set (excluding the completion flag) in the database table specified in the data management parameter 323B. In addition, the data of the data set (excluding the completion flag) is stored in the column having the same column name as the data name. The same column name as the data name is described in the storage table parameter 324.
Then, the data management unit 223B sets "OFF" in the completion flag corresponding to the stored target data set (excluding the completion flag).

FIG. 43 shows an operation image of the data list data 321B.
The operation image of the data list data 321B is the same as that of the data list data 321B.

FIG. 44 shows an operation image corresponding to the data list data 321B and the data acquisition parameter 322B.
The operation image corresponding to the data list data 321B and the data acquisition parameter 322B represents the following contents.
The "completion flag of controllers A and B" is acquired from the controller A of the IP address A and the controller B of the IP address B in the "acquisition cycle" using the "communication protocol". When the "completion flag is ON", the data values of the corresponding controller A and B data sets are acquired.
The program of the operation system 201B is usually created by using a compiled language. However, the part of the operation image of FIG. 44 may be created in a script language. This makes it possible to easily change the operational image of FIG. 44.

FIG. 45 shows an operation image of the data management parameter 323B.
The operation image of the data management parameter 323B represents the following contents.
The "ID, input time" is inserted into the "input table" of the storage DB (1). The "ID, inspection time, inspection result" is inserted into the "inspection table" of the storage DB (2).
The program of the operation system 201B is usually created by using a compiled language. However, the part of the operation image of FIG. 45 may be created in a script language. This makes it possible to easily change the operational image of FIG. 45.

*** Supplement to Embodiment 2 ***
The supplement of the first embodiment also applies to the second embodiment. However, step S142 in the supplement of the first embodiment is replaced with step S142B in the second embodiment.

*** Effect of Embodiment 2 ***
According to the second embodiment, the controller acquires only the data set satisfying the storage condition. be able to. Therefore, the amount of communication for acquiring the required data set is reduced.

*** Summary of embodiments ***
The index management system 200 is configured as follows.
The index management system 200 includes a manufacturing device 230, an index management device 210, an intermediary device 220, and an engineering device 100. The engineering device 100 sets the manufacturing device 230, the index management device 210, and the intermediary device 220.
The manufacturing apparatus 230 includes a data supply unit 231 that supplies real-time information (data set) related to manufacturing to another apparatus (intermediary device 220) connected by a network.
The intermediary device 220 includes a data management unit 223, an index calculation unit 222, and an index supply unit 221. The data management unit 223 acquires real-time data (data set) from the data supply unit 231 of the manufacturing apparatus 230 via the network, and manages the acquired real-time data. The index calculation unit 222 calculates the index value according to a predetermined rule using the real-time data managed by the data management unit 223. The index supply unit 221 gives an instruction to the index calculation unit 222 and provides the calculated index value to another device (index management device 210).
Further, the data management unit 223 may be in the manufacturing apparatus 230.
The index management device 210 acquires an index value from the index supply unit 221 of the intermediary device 220 via the network, and utilizes the acquired index value.
The engineering device 100 includes a reception unit 111, a generation unit 112, and a setting unit 113. The reception unit 111 receives index list information (index list data 301), device-to-device connection information (access information data 302), and process parameter information (process information data 303) as inputs.
The generation unit 112 includes an index management unit 211, an index supply unit 221, an index calculation unit 222, and a data management unit 223 based on the input information to the reception unit 111 and the information included in the reception unit 111 (setting information data group 310). Each setting information (operation parameter group 320) with the data supply unit 231 is generated.
The setting unit 113 arranges the index acquisition parameter 327 in the index management unit 211. The setting unit 113 arranges the index supply parameter 326 in the index supply unit 221. The setting unit 113 arranges the index calculation parameter 325 in the index calculation unit 222. The setting unit 113 arranges the storage table parameter 324, the data management parameter 323, the data acquisition parameter 322, and the data list data 321 in the data management unit 223. The setting unit 113 arranges the data list data 321 in the data supply unit 231.

*** Supplement to the embodiment ***
A configuration example of the operation system 201 in the index management system 200 will be described with reference to FIGS. 47, 48, 49, and 50.
As shown in FIG. 47, the operation system 201C may include a plurality of manufacturing devices 230.
As shown in FIG. 48, the operating system 201D may include a plurality of manufacturing devices 230B.
As shown in FIG. 49, a plurality of operation systems 201C may exist.
As shown in FIG. 50, a plurality of operation systems 201D may exist.

The hardware configuration of the engineering apparatus 100 will be described with reference to FIG. 50.
The engineering device 100 includes a processing circuit 109.
The processing circuit 109 is hardware that realizes the reception unit 111, the generation unit 112, and the setting unit 113.
The processing circuit 109 may be dedicated hardware or may be a processor 101 that executes a program stored in the main storage device 102.

When the processing circuit 109 is dedicated hardware, the processing circuit 109 is, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof.
ASIC is an abbreviation for Application Specific Integrated Circuit.
FPGA is an abbreviation for Field Programmable Gate Array.

The engineering device 100 may include a plurality of processing circuits that replace the processing circuit 109. The plurality of processing circuits share the role of the processing circuit 109.

In the processing circuit 109, some functions may be realized by dedicated hardware, and the remaining functions may be realized by software or firmware.
In this way, the processing circuit 109 can be realized by hardware, software, firmware, or a combination thereof.

The index management device 210, the mediation device 220, and the manufacturing device 230 include a processing circuit like the engineering device 100.

The embodiments are examples of preferred embodiments and are not intended to limit the technical scope of the invention. The embodiment may be partially implemented or may be implemented in combination with other embodiments. The procedure described using the flowchart or the like may be appropriately changed.
The "part" which is an element of each device described in the embodiment may be read as "processing" or "process".

100 engineering device, 101 processor, 102 main storage device, 103 auxiliary storage device, 104 input / output device, 105 communication device, 106 display device, 109 processing circuit, 111 reception unit, 112 generation unit, 113 setting unit, 190 storage unit, 200 Index management system, 201,201B, 201C, 201D Operation system, 210 Index management device, 211 Index management unit, 220, 220B Mediation device, 221 Index supply unit, 222 Index calculation unit, 223,223B Data management unit, 229 database , 230, 230B Manufacturing equipment, 231 data supply unit, 291 processor, 292 main storage unit, 293 auxiliary storage unit, 294 input / output device, 295 communication device, 296 display device, 300 managed data group, 301 index list data, 302 , 302B access information data, 303 process information data, 310, 310B setting information data group, 311 data information data, 312 storage condition data, 313 table template data, 314 plug-in definition data, 315 index supply data, 316 acquisition condition data , 320 Operation parameter group, 321,321B data list data, 322,322B data acquisition parameter, 323,323B data management parameter, 324 storage table parameter, 325 index calculation parameter, 326 index supply parameter, 327 index acquisition parameter.

A supplement is provided for step S114, step S124, and step S142.
In S114, each data set (excluding the completion flag) is input at the same time. That is, each data set (excluding the completion flag) is input collectively in one operation. This makes it possible to prevent input omission.
Also, whether the data name is the same or the database table name is the same in this paragraph is determined by the name with the suffix (described later).
When the same data is acquired in a plurality of steps by the same calculation method, the data name of the data set and the database table name may be duplicated. In that case, add a suffix to all data names and database names, and enter all data sets (excluding the completion flag) of the calculation method. The suffix is specified by the user. Examples of how to add a suffix are "ID_assembly process, input time_assembly process", "ID_inspection process, inspection time_inspection process, inspection result_inspection process" and the like. Suffixes to the completion flag and table name as well (the suffixes to the dataset (including the completion flag) and the table name do not necessarily have to be the same).
On the other hand, when setting other indicators, if the same process has the same data set (excluding the completion flag) and the database table name is the same, the data set (excluding the completion flag) is added to the process information data 303. Set only the index name without registering. If the same data set has a different database table name, register the database table name and data set data name with a suffix.
When setting other indicators, if the data with the same data name is part of the dataset (excluding the completion flag) in the same process and the table name is the same, do as follows. Only the data that does not overlap in the process information data 303 is registered with the same suffix as the other data names in the same table (when the other data names or table names in the same table do not have the suffix but the data names are duplicated). Adds a suffix to the data name and table name). At this time, when adding the column name to the storage table parameter 324 at the time of the generation process of step S124, the name without the suffix is added. Further, during the operation process of step S142, when storing the data in the dataset (excluding completion flag) in the database 229 stored in the column with the same column name as the data name of the names without a suffix.

Claims (11)

An operation system that calculates the management index value based on a group of operation parameters for the management index, which is one or more parameters used to calculate the management index value.
It is equipped with an engineering device that sets the operation parameter group for the management index in the operation system.
The engineering equipment is
Settings for the management index from the setting information data group for each index that accepts the designation of the management index and the management target data group indicating the configuration of the operation system and indicates the information set in the operation parameter group for each index. The reception department for selecting information data groups and
A generation unit that generates an operation parameter group for the management index based on the setting information data group for the management index and the management target data group.
An index management system including a setting unit for setting an operation parameter group for the management index in the operation system. The operation system is
A manufacturing device that supplies the data values of the target data set used for calculating the control index values, and
The index management system according to claim 1, further comprising an intermediary device for calculating the management index value using the data value of the target data set and an index management device for managing the management index value. The manufacturing equipment is
A data supply unit for supplying the data value of the target data set to the intermediary device is provided.
The intermediary device is
A data management unit that manages the data values of the target data set supplied from the manufacturing apparatus, and
An index calculation unit that calculates the management index value using the data value of the target data set, and
It is provided with an index supply unit that supplies the control index value to the index management device.
The index management device is
The index management system according to claim 2, further comprising an index management unit that manages a management index value supplied from the intermediary device. The generation unit is used as an operation parameter group for the management index.
Data list data indicating the target data set and
A data acquisition parameter indicating a rule for acquiring the data value of the target data set, and
Data management parameters indicating rules for managing the data values of the target data set, and
A storage table parameter that identifies the table in which the data values of the target dataset are stored, and
An index calculation parameter indicating a rule for calculating the management index value, and an index calculation parameter.
An index supply parameter indicating a rule for supplying the control index value, and an index supply parameter.
Generate an index acquisition parameter and an index acquisition parameter indicating a rule for acquiring the control index value.
The setting unit is
The data list data is set in the data supply unit, and the data is set in the data supply unit.
The data list data and the data acquisition parameter are set in the data management unit, and the data is set in the data management unit.
The storage table parameter, the data management parameter, and the data acquisition parameter are set in the data management unit.
The index calculation parameter is set in the index calculation unit, and the index calculation parameter is set in the index calculation unit.
The index supply parameter is set in the index supply unit, and the index supply parameter is set in the index supply unit.
The index management system according to claim 3, wherein the index acquisition parameter is set in the index management unit. The operation system is
A manufacturing device that manages the data values of the target data set used for calculating the control index values, and
The index management system according to claim 1, further comprising an intermediary device for calculating the management index value using the data value of the target data set and an index management device for managing the management index value. The manufacturing equipment is
A data supply unit that supplies the data values of the target data set, and
It is equipped with a data management unit that manages the data values of the supplied target data set.
The intermediary device is
An index calculation unit that calculates the management index value using the data value of the target data set, and
It is provided with an index supply unit that supplies the control index value to the index management device.
The index management device is
The index management system according to claim 5, further comprising an index management unit that manages a management index value supplied from the intermediary device. The program of the operation system is configured according to any one of claims 1 to 6 so that a part of processing using the operation parameter group for the management index can be created in a script language. Described indicator management system. The engineering device executes the process of accepting the process information data that sets the data required for data collection and storage in each process and the access information data that sets the information required for access between each device. , The data list data of the data collected by the manufacturing apparatus based on the data received by the engineering apparatus is output, and the engineering apparatus creates the program for the manufacturing apparatus to set the data value of the data list data, and the manufacturing apparatus. An index management system that enables the calculation of the selected index by updating. It is an index management method using engineering equipment and an operation system.
The engineering device receives the designation of the management index, the management target data group indicating the configuration of the operation system, and the management from the setting information data group for each index indicating the information set in the operation parameter group for each index. The setting information data group for the index is selected, the operation parameter group for the management index is generated based on the setting information data group for the management index and the management target data group, and the operation parameter group for the management index is generated. Is set in the above operation system,
An index management method in which the operation system calculates a management index value based on the operation parameter group for the management index. An engineering device that sets an operation parameter group for a control index, which is one or more parameters used for calculating a control index value, in an operation system.
Setting information for the management index from the setting information data group for each index that accepts the designation of the management index and the management target data group indicating the configuration of the operation system and indicates the information set in the operation parameter group for each index. The reception desk for selecting data groups and
A generation unit that generates an operation parameter group for the management index based on the setting information data group for the management index and the management target data group.
A setting unit that sets the operation parameter group for the management index in the operation system, and
Engineering equipment equipped with. It is an engineering program for setting an operation parameter group for a control index, which is one or more parameters used for calculating a control index value, in an operation system.
Setting information for the management index from the setting information data group for each index that accepts the designation of the management index and the management target data group indicating the configuration of the operation system and indicates the information set in the operation parameter group for each index. Reception process to select data group and
A generation process for generating an operation parameter group for the management index based on the setting information data group for the management index and the management target data group, and
The setting process for setting the operation parameter group for the management index in the operation system, and
An engineering program to get a computer to run.

Images