JP7306550B1 - Production control system, production control method and program - Google Patents

Abstract

A production control system, a production control method, and a program capable of transmitting data from the outside to the inside of a closed network to control equipment inside the closed network are provided. A production management system comprising: an external data acquisition unit that periodically communicates from the inside of a closed network in a production base with an external system outside the closed network, and acquires from the external system external data to be linked from the outside to the inside of the closed network; and an internal linkage relay unit that links the external data acquired by the external data acquisition unit to equipment inside the closed network. [Selection drawing] Fig. 2

Description

Application of Article 30, Paragraph 2 of the Patent Act Website publication date November 11, 2021 Website address https://navinect. jp/app/dockator/

The present invention relates to a production control system, production control method, and program.

In recent years, the need for IoT (Internet of Things) is increasing in various industrial fields. For example, at the production site of products, by collecting data from sensors installed at the production site through IoT and analyzing the data on a server, the analysis results can be utilized for production management.

The following patent document 1 discloses a technique of converting measurement data measured in each process of a product production factory into a common format by an IoT relay device and then transmitting the data to a cloud computing system for analysis. disclosed.
In addition, in Patent Document 2 below, a gateway device collects, converts, and processes measurement data measured by a sensor, and then transmits the data to a data collection server, and the data collection server generates rules based on the measurement data. is disclosed.

Japanese Patent No. 6419234 Japanese Patent No. 5737696

Both Patent Literature 1 and Patent Literature 2 described above disclose that measurement data measured by a sensor is transmitted from the server side to the server side via an IoT relay device or a gateway device. On the other hand, none of the patent documents disclose the control of the production equipment by sending data to the production equipment provided in the production factory based on the measurement data sent to the server. If data can be sent from the server side to the production equipment in the production factory, the scope of what can be done in production management can be expanded. However, in production sites such as factories, a closed network is often constructed, and it has been difficult to transmit data from the outside of the closed network to equipment inside and control the equipment.

In view of the above problems, an object of the present invention is to provide a production control system, a production control method, and a program capable of transmitting data from the outside to the inside of a closed network to control equipment inside the closed network. to do.

In order to solve the above-described problems, a production management system according to one aspect of the present invention is a production management system including a relay device, an internal system, and an external system, wherein the relay device is installed in a production base. Using authentication information from the internal system inside the constructed closed network to periodically access the external system outside the closed network to obtain external data that cooperates with the inside of the closed network. External data acquisition for periodically transmitting a request to the external system , and acquiring the unlinked external data transmitted from the external system when the external data unlinked to the internal system exists in the external system and an internal linking relay unit that links the external data acquired by the external data acquiring unit with facilities inside the closed network.

A production control method according to one aspect of the present invention is a production control method in a production control system including a relay device, an internal system, and an external system, wherein an external data acquisition unit of the relay device is installed in a production base. Using authentication information from the internal system inside the constructed closed network to periodically access the external system outside the closed network to obtain external data that cooperates with the inside of the closed network. External data acquisition for periodically transmitting a request to the external system , and acquiring the unlinked external data transmitted from the external system when the external data unlinked to the internal system exists in the external system and an internal cooperation relay process in which the internal cooperation relay unit of the relay device cooperates with the equipment inside the closed network with the external data acquired by the external data acquisition unit.

A program according to an aspect of the present invention is a program for causing a computer to function as a production control system including a relay device, an internal system, and an external system,
The computer functioning as the relay device periodically accesses the external system outside the closed network using the authentication information from the internal system inside the closed network built in the production site, A request to acquire external data to be linked to the inside of the closed network is periodically sent to the external system , and when the external data not linked to the internal system exists in the external system, the request is sent from the external system. external data acquisition means for acquiring the uncoordinated external data , and internal linkage relay means for linking the external data acquired by the external data acquisition means to equipment inside the closed network. make it work.

According to the present invention, it is possible to transmit data from the outside to the inside of the closed network and control the equipment inside the closed network.

It is a block diagram showing an example of a schematic structure of a production control system concerning this embodiment. It is a block diagram which shows an example of the functional structure of the relay apparatus which concerns on this embodiment. 3 is a block diagram showing an example of the functional configuration of an on-premises server according to this embodiment; FIG. It is a block diagram showing an example of the functional configuration of the operation terminal according to the present embodiment. 3 is a block diagram showing an example of a functional configuration of a relay server according to this embodiment; FIG. It is a block diagram showing an example of functional composition of a cloud server concerning this embodiment. FIG. 4 is a sequence diagram showing an example of the flow of processing in collecting internal data of a factory according to the present embodiment; FIG. 5 is a sequence diagram showing an example of the flow of processing in external linkage of factory internal data according to the present embodiment; FIG. 5 is a sequence diagram showing an example of the flow of processing in acquiring external data according to the embodiment; FIG. 5 is a sequence diagram showing an example of the flow of processing in internal cooperation of external data according to the present embodiment; FIG. 5 is a sequence diagram showing an example of the flow of processing from job selection to pre-production confirmation according to the present embodiment; FIG. 11 is a sequence diagram showing an example of the flow of processing from confirmation of a confirmation result by a worker to inventory update according to the present embodiment; FIG. 5 is a sequence diagram showing an example of the flow of processing related to control of production equipment by the cloud server according to the present embodiment; FIG. 5 is a sequence diagram showing an example of the flow of processing related to monitoring by the cloud server according to the embodiment;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

<1. Schematic configuration of production control system>
A schematic configuration of the production management system according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of a schematic configuration of a production management system according to this embodiment.
A production management system 1 shown in FIG. 1 is a system for managing production at a production base. A production base is, for example, a factory FC that produces (manufactures) a predetermined product. The field of factory FC is not particularly limited, and examples include fields such as printing, papermaking, machinery, automobiles, chemistry, steel, construction, food, pharmaceuticals, and home appliances. In addition, the production process managed by the factory FC is not particularly limited. An inspection process for inspection, a shipping process for shipping products after inspection, and the like are managed respectively. Each process can be further divided into detailed processes according to the production target.

As shown in FIG. 1 , the production control system 1 includes an internal system 2 and an external system 3 . The internal system 2 is a system for managing production in the factory FC from inside the closed network NW1 (closed network) built in the factory FC. The closed network NW1 according to this embodiment is a wide area communication network that can be used only by limited users due to restrictions such as firewalls. The external system 3 is a system for managing production in the factory FC from outside the closed network NW1. In the production control system 1, the inside and outside of the closed network NW1 can be linked, so that production in the factory FC can be managed from outside the closed network NW1.

As shown in FIG. 1, the internal system 2 includes a sensor terminal 10, a production facility 20, a control terminal 21, a management control terminal 22, a management system 30, a conversion terminal 31, a relay device 100, and an on-premises server. 200 and an operation terminal 300 . The external system 3 has a relay server 400 and a cloud server 500 .
Relay device 100 is communicably connected to relay server 400 and cloud server 500 via network NW2.

(1) Sensor terminal 10
The sensor terminal 10 is provided in the factory FC and is a terminal that acquires (measures) information on production in the factory FC (hereinafter also referred to as “production information”). Examples of production information measured by the sensor terminal 10 include temperature and relative humidity detected by a temperature/humidity sensor, accumulated water detection information obtained by a water leakage sensor, current value obtained by a current sensor, and the like. The sensor terminal 10 transmits the measured production information to the relay device 100 .

For communication between the sensor terminal 10 and the relay device 100, for example, the LPWA (Low Power Wide Area) communication standard may be used, or the LTE (Long Term Evolution) or 4G (fourth generation mobile communication system) may be used. ) may be used. Specific LPWA standards include, for example, ZETA, LoRa (registered trademark), and EnOcean (registered trademark).
When using LPWA, an access point or an LPWA server (for example, a cloud server) may be provided between the sensor terminal 10 and the relay device 100 . In this case, the sensor terminal 10 transmits the measured production information to the LPWA server via the access point. Thereafter, the LPWA server transmits (cooperates with) the production information received from the access point to the cloud server 500 via the relay device 100 .
On the other hand, when LPWA is not used, the sensor terminal 10 may be a terminal connected via Ethernet, or may be a terminal connected to a PLC (Programmable Logic Controller) via a physical line.

The number of sensor terminals 10 provided in the factory FC is not particularly limited, and an arbitrary number N (N is a natural number) of sensor terminals 10-1 to 10-N may be provided in the factory FC. Further, the position where the sensor terminal 10 is provided in the factory FC is not particularly limited as long as it is a position where the above-described production information can be measured, and may be any position.

The number of access points provided in the factory FC is not particularly limited, and any number of access points may be provided in the factory FC. for example. One access point may be provided for one sensor terminal 10 , or one access point may be provided for a plurality of sensor terminals 10 . Further, the position where the access point is provided in the factory FC is not particularly limited as long as it can relay the communication of the sensor terminal 10 described above, and may be any position.

(2) Production facility 20
The production equipment 20 is equipment used to produce products. The production facility 20 is, for example, a production device that assembles and processes products, a labeler that affixes labels to products, a conveyer that conveys products, an inspection device, and the like. The production equipment 20 is installed corresponding to a predetermined process for producing each product in the factory FC.

The number of production facilities 20 provided in the factory FC is not particularly limited, and an arbitrary number L (L is a natural number) of production facilities 20-1 to 20-L may be provided in the factory FC. Further, the position where the production facility 20 is provided in the factory FC is not particularly limited, and may be any position.

(3) Control terminal 21
The control terminal 21 is a terminal that controls the operation of the production facilities 20 (20-1 to 20-L). The control terminal 21 is, for example, a computer device such as a PLC. The control terminal 21 is communicably connected to the corresponding production equipment 20 . Also, the control terminal 21 is communicably connected to the management control terminal 22 via a predetermined inter-PLC network.

The number of control terminals 21 provided in the factory FC is not particularly limited, and an arbitrary number K (K is a natural number) of control terminals 21-1 to 21-K may be provided in the factory FC. for example. One control terminal 21 may be provided for one production facility 20 , or one control terminal 21 may be provided for a plurality of production facilities 20 . Further, the position where the control terminal 21 is provided in the factory FC is not particularly limited, and may be any position.

(4) Management control terminal 22
The management control terminal 22 is a terminal that functions as a master control terminal for the control terminal 21 . The management control terminal 22 is also a PLC when the control terminal 21 is a PLC.
The management control terminal 22 is communicably connected to each of the control terminals 21 via a predetermined inter-PLC network. The management control terminal 22 communicates with the control terminal 21 to acquire production information including predetermined information regarding the operation of the production facility 20 and predetermined information regarding the production of products from the control terminal 21 . The predetermined information regarding operation is, for example, information indicating set values for operation of the production facility 20 (hereinafter also referred to as “setting information”). In addition, the predetermined information related to the production of the product includes, for example, information indicating the production plan of the product in the production facility (hereinafter also referred to as "production plan information") and information indicating the production results in the production facility (hereinafter referred to as "production It is also referred to as "performance information"). The management control terminal 22 also communicates with the control terminal 21 to give instructions and notifications regarding the operation of the production equipment 20 to the control terminal 21 .
The position where the management control terminal 22 is provided in the factory FC is not particularly limited, and may be any position.

(5) Management system 30
The management system 30 is a system that manages information on production management in the factory FC (hereinafter also referred to as "management information"). The management system 30 is, for example, an ERP (Enterprise Resources Planning) system, a WMS (Warehouse Management System) system, or the like. The management system 30 is communicably connected to the conversion terminal 31 . The management system 30 transmits and receives, for example, management information in communication with the conversion terminal 31 .
The number of management systems 30 used in the factory FC is not particularly limited, and an arbitrary number J (J is a natural number) of management systems 30-1 to 30-J may be used in the factory FC.

(6) Conversion terminal 31
The conversion terminal 31 is a conversion module that converts the data format of data. The conversion terminal 31 is communicably connected to the management system 30 and the on-premises server 200 . When transmitting data (for example, management information) from the management system 30 to the on-premises server 200, the conversion terminal 31 converts the data received from the management system 30 into a data format suitable for the on-premises server 200, and then transmits the data to the on-premises server 200. Send data. On the other hand, when transmitting data from the on-premises server 200 to the management system 30, the conversion terminal 31 converts the data received from the on-premises server 200 into a data format suitable for the management system 30, and then transmits the data to the management system 30. do.

Further, the conversion terminal 31 may accept input of data in an arbitrary data format and output the data in an arbitrary data format without converting the data. Arbitrary data formats include, for example, text files (CSV (Comma Separated Values), fixed length data, etc.), data formats for databases, data formats for HTTP (HyperText Transfer Protocol) communication, and the like.
As an example, when linking CSV data to a database, first, the management system 30 outputs linked data as a CSV file and transmits it to the conversion terminal 31 . The conversion terminal 31 decomposes the CSV data in the CSV file received from the management system 30 and develops the decomposed CSV data in response to the query set on the conversion terminal 31 . Conversion terminal 31 then executes a query to on-premises server 200 .
As another example, when data in a database is linked to a WEB server through HTTP communication, the conversion terminal 31 first acquires linked data by executing a query to the management system 30 . Next, the conversion terminal 31 develops the acquired linkage data into the HTTP body information set on the conversion terminal 31 (for example, the information in column A is reflected in the HTTP body information A). Next, the conversion terminal 31 transmits body information in which the URL and the linking data are developed to the set URL (Uniform Resource Locator). Then, the receiving WEB server decomposes the received body information and develops it in a database.

(7) Relay device 100
The relay device 100 is a device that relays communication between the inside and the outside of the closed network NW1. The relay device 100 is communicably connected to the management control terminal 22, the conversion terminal 31, and the on-premises server 200 within the closed network NW1. Also, the relay device 100 is communicably connected to the relay server 400 and the cloud server 500 of the external system 3 via the network NW2.

The relay device 100 receives, via the network NW2, data linked from the inside of the closed network NW1 to the outside (hereinafter also referred to as "internal data") and data linked from the outside to the inside of the closed network NW1 (hereinafter referred to as (also referred to as "external data").
When linking internal data from inside the closed network NW1 to the outside, the relay device 100 acquires internal data within the closed network NW1 and links the internal data acquired via the network NW2 to the external system 3 . The internal data includes, for example, production information received from the sensor terminal 10, production information received from the management control terminal 22, management information received from the conversion terminal 31, and the like.
When linking external data from the outside to the inside of the closed network NW1, the relay device 100 acquires the external data from the external system 3 via the network NW2, and links the acquired external data to the inside of the closed network NW1. The external data includes, for example, information for controlling the operation of the control terminal 21 (hereinafter also referred to as "control information"), information to be displayed on the operation terminal 300 (hereinafter also referred to as "display information"), Includes management information, etc.

Note that the relay device 100 actively acquires external data from inside the closed network NW1 to the outside. For example, the relay device 100 uses the authentication information to periodically (for example, every time a predetermined time elapses) transmit an external data acquisition request to the cloud server 500 of the external system 3 . When uncoordinated external data exists in the cloud server 500 , the relay device 100 acquires the uncoordinated external data from the cloud server 500 . When the external data can be acquired, the relay device 100 links the acquired external data to the inside of the closed network NW1.

(8) On-premise server 200
The on-premises server 200 is a server provided inside the closed network NW1, and manages external data linked from the outside. On-premises server 200 is communicably connected to relay device 100 , operation terminal 300 , and conversion terminal 31 . The on-premises server 200 receives external data from the relay device 100, analyzes the external data, converts the data into a data format suitable for the internal system 2, and stores the data. In addition, the on-premises server 200 links the external data after conversion to a terminal according to its contents. For example, if the external data is control information or display information, the on-premises server 200 links the external data to the operation terminal 300 . Also, when the external data is management information, the on-premises server 200 links the external data to the conversion terminal 31 .

(9) Operation terminal 300
The operation terminal 300 is a terminal operated by a user. The users are, for example, factory FC workers and administrators. The operation terminal 300 is, for example, a computer device such as an LCS (Line Control System). The operation terminal 300 is communicably connected to the on-premises server 200 and the management control terminal 22 . The operation terminal 300 , for example, receives external data from the on-premises server 200 , displays display information of the external data on its own terminal, and transmits control information to the management control terminal 22 . The operation terminal 300 also receives an operation for controlling the operation of the production equipment 20 from the user, and transmits control information corresponding to the operation to the management control terminal 22 .

(10) Relay server 400
The relay server 400 is a server provided outside the closed network NW1 and relays internal data linkage to the cloud server 500 . Relay server 400 is communicably connected to relay device 100 via network NW2 and receives internal data from relay device 100 . Relay server 400 analyzes the internal data received from relay device 100 , converts the data into a data format suitable for cloud server 500 , and cooperates with cloud server 500 .

(11) Cloud server 500
The cloud server 500 is a server provided outside the closed network NW1, and manages external data linked to the inside of the closed network NW1 and internal data linked from the inside. Cloud server 500 stores internal data linked from relay device 100 via relay server 400 . The cloud server 500 also stores various types of information (for example, production information and management information) input by users from terminals outside the closed network NW1 via web browsers and applications. Further, cloud server 500 is communicably connected to relay device 100 via network NW2. Data is transmitted to the relay device 100 .

The cloud server 500 may generate external data based on at least one of internal data linked from inside the closed network NW1 and various information input by the user.

<2. Functional Configuration of Relay Device>
The schematic configuration of the production management system 1 has been described above with reference to FIG. Next, with reference to FIG. 2, the functional configuration of the relay device 100 according to this embodiment will be described. FIG. 2 is a block diagram showing an example of the functional configuration of the relay device 100 according to this embodiment.
As shown in FIG. 2 , relay device 100 includes communication unit 110 , storage unit 120 , and control unit 130 .

(1) Communication unit 110
The communication unit 110 has a function of transmitting and receiving various information. The communication unit 110 receives production information from the sensor terminal 10 and the management control terminal 22 and receives management information from the conversion terminal 31 within the closed network NW1. Also, the communication unit 110 transmits external data to the on-premises server 200 within the closed network NW1. Further, the communication unit 110 transmits internal data to the relay server 400 and transmits an external data acquisition request to the cloud server 500 via the network NW2. The communication unit 110 also receives external data from the cloud server 500 via the network NW2.

(2) Storage unit 120
The storage unit 120 has a function of storing various information. The storage unit 120 is a storage medium provided as hardware in the relay apparatus 100, for example, a HDD (Hard Disk Drive), SSD (Solid State Drive), flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), RAM (Random Access Memory). read /write Memory), ROM (Read Only Memory), or any combination of these storage media.
The storage unit 120 temporarily stores, for example, various information received by the communication unit 110 and data processed by a data processing unit 132 described later.

(3) Control unit 130
The control unit 130 has a function of controlling the overall operation of the relay device 100 . The control unit 130 is implemented, for example, by causing a CPU (Central Processing Unit) provided as hardware in the relay device 100 to execute a program.
As shown in FIG. 2 , control unit 130 includes internal data acquisition unit 131 , data processing unit 132 , external linkage relay unit 133 , external data acquisition unit 134 , and internal linkage relay unit 135 .

(3-1) Internal data acquisition unit 131
The internal data acquisition unit 131 has a function of acquiring, within the closed network NW1, internal data that links from the inside of the closed network NW1 to the outside. For example, the internal data acquisition unit 131 acquires production information received by the communication unit 110 from the sensor terminal 10 and the management control terminal 22 or management information received from the conversion terminal 31 as internal data. After the acquisition, internal data acquisition section 131 outputs the acquired internal data to data processing section 132 .

(3-2) Data processing unit 132
The data processing unit 132 has a function of processing the internal data acquired by the internal data acquisition unit 131 as necessary. For example, when the cloud server 500 requires a calculation result using internal data, the data processing unit 132 performs calculation using the internal data acquired by the internal data acquisition unit 131 (hereinafter referred to as “calculation processing ”) processes the internal data. The data processing unit 132 can perform, for example, four arithmetic operations, surplus calculations, exponentiation calculations, logarithmic calculations, and the like in arithmetic processing. As an example, the data processing unit 132 sums the weights of the objects measured by the sensor terminals 10-1 to 10-N to calculate the total weight.

It is also assumed that the data format of the internal data acquired by the internal data acquisition unit 131 or the data format of the processed internal data is different from the data format of the internal data required by the cloud server 500 . In this case, the data processing unit 132 converts the data format of the internal data into the data format of the internal data required by the cloud server 500 (hereinafter also referred to as “cleansing process”) to convert the internal data. process. The data processing unit 132 can perform, for example, fraction processing or range conversion in cleansing processing. In rounding, internal data is rounded, rounded down, or rounded up, and the number of digits after the decimal point is changed. In range conversion, the possible range (minimum value and maximum value) of the value indicated by the internal data is converted into a range based on a standard different from the current standard.

Further, the data processing unit 132 may perform conditional branching based on the value indicated by the internal data acquired by the internal data acquisition unit 131 or the processed internal data. Thereby, the data processing unit 132 can determine, for example, whether or not to process the internal data, and, if the internal data is to be processed, how to process it.

(3-3) External linkage relay unit 133
The external linkage relay unit 133 has a function of linking internal data from inside the closed network NW1 to the external system 3 . For example, the external linkage relay unit 133 links internal data acquired by the internal data acquisition unit 131 or internal data processed by the data processing unit 132 from inside the closed network NW1 to the external system 3 .

(3-4) External data acquisition unit 134
The external data acquisition unit 134 has a function of acquiring external data linked from inside the closed network NW1 to outside. For example, the inside of the closed network NW1 periodically communicates with the external system 3 outside the closed network NW1 to acquire external data from the external system 3 . Specifically, the external data acquisition unit 134 uses the authentication information to access the cloud server 500 and transmit an external data acquisition request. When cloud server 500 has uncoordinated external data, the external data is transmitted from cloud server 500 to relay device 100 . Thereby, the external data acquisition unit 134 can acquire the external data that the communication unit 110 has received from the cloud server 500 .

(3-5) Internal cooperation relay unit 135
The internal cooperation relay unit 135 has a function of relaying cooperation of external data to each facility inside the closed network NW1. For example, the internal linking relay unit 135 links the external data acquired by the external data acquiring unit 134 with equipment inside the closed network NW1. For example, the internal linkage relay unit 135 links external data to the on-premises server 200 . The external data linked by the internal linkage relay unit 135 is further linked to other equipment by the on-premises server 200 .

<3. Functional Configuration of On-Premises Server>
The functional configuration of the relay device 100 has been described above with reference to FIG. Next, the functional configuration of the on-premises server 200 according to this embodiment will be described with reference to FIG. FIG. 3 is a block diagram showing an example of the functional configuration of the on-premises server 200 according to this embodiment.
As shown in FIG. 3, the on-premises server 200 includes a communication unit 210, a storage unit 220, and a control unit 230.

(1) Communication unit 210
The communication unit 210 has a function of transmitting and receiving various information. The communication unit 210 receives external data from the relay device 100 within the closed network NW1. Further, the communication unit 210 transmits control information or display information to the operation terminal 300 and transmits management information to the conversion terminal 31 within the closed network NW1.

(2) Storage unit 220
The storage unit 220 has a function of storing various information. The storage unit 220 is configured by a storage medium provided as hardware in the on-premises server 200, such as an HDD, SSD, flash memory, EEPROM, RAM, ROM, or any combination of these storage media.
The storage unit 220 stores, for example, converted external data.

(3) Control unit 230
The control unit 230 has a function of controlling the overall operation of the on-premises server 200 . The control unit 230 is implemented, for example, by causing a CPU provided as hardware in the on-premises server 200 to execute a program.
As shown in FIG. 3 , the control unit 230 includes a conversion unit 231 , an insertion unit 232 and an internal cooperation unit 233 .

(3-1) Conversion unit 231
The conversion unit 231 has a function of converting the data format of external data. For example, the conversion unit 231 analyzes external data received by the communication unit 210 from the relay device 100 and converts it into a data format compatible with the internal system 2 . For example, the conversion unit 231 converts the external data into JSON (Javascript Object Notation) format data. At this time, the conversion unit 231 determines whether or not the external data is invalid data by analyzing the external data. If the external data is invalid data, the conversion unit 231 does not convert the data format and excludes it from the data linked to each facility.

(3-2) Insertion portion 232
The insertion unit 232 has a function of inserting external data into the database in the storage unit 220 . For example, the inserting unit 232 analyzes the external data converted by the converting unit 231 and generates a query. After generation, the insertion unit 232 inserts the external data converted by the conversion unit 231 into the database in the storage unit 220 using the generated query.
Note that the processing of the conversion unit 231 described above is performed at the front of the on-premises server 200, and the processing of the insertion unit 232 is performed at the back of the on-premises server 200. FIG. By dividing the processing of the conversion unit 231 and the processing of the insertion unit 232 into front and back in this way, the load (writing amount) on the database due to external access can be controlled to be constant.

(3-3) Internal cooperation unit 233
The internal linking unit 233 has a function of linking external data to each facility inside the closed network NW1. For example, the internal linking unit 233 links external data linked by the internal linking relay unit 135 of the relay device 100 to equipment corresponding to the external data. For example, the internal cooperation unit 233 confirms whether the external data converted by the conversion unit 231 is control information, display information, or management information. When the external data is control information or display information, the internal linking unit 233 links the external data to the operation terminal 300 . On the other hand, when the external data is management information, the internal linking unit 233 links the external data to the conversion terminal 31 .

<4. Functional Configuration of Operation Terminal>
The functional configuration of the on-premises server 200 has been described above with reference to FIG. Next, with reference to FIG. 4, the functional configuration of the operation terminal 300 according to this embodiment will be described. FIG. 4 is a block diagram showing an example of the functional configuration of the operation terminal 300 according to this embodiment.
As shown in FIG. 4 , operation terminal 300 includes communication section 310 , input section 320 , storage section 330 , control section 340 and output section 350 .

(1) Communication unit 310
The communication unit 310 has a function of transmitting and receiving various information. The communication unit 310 receives external data (control information or display information) from the on-premises server 200 within the closed network NW1. The communication unit 310 also transmits external data (control information) to the management control terminal 22 within the closed network NW1.

(2) Input unit 320
The input unit 320 has a function of receiving input from the user. The input unit 320 is realized by, for example, a keyboard, a mouse, buttons, a touch panel, a microphone, etc. provided in the operation terminal 300 .

(3) Storage unit 330
The storage unit 330 has a function of storing various information. The storage unit 330 is configured by a storage medium provided as hardware in the operation terminal 300, such as an HDD, SSD, flash memory, EEPROM, RAM, ROM, or any combination of these storage media.

(4) Control unit 340
The control unit 340 has a function of controlling the overall operation of the operation terminal 300 . The control unit 340 is implemented, for example, by causing a CPU provided as hardware in the operation terminal 300 to execute a program.
As shown in FIG. 4 , the control section 340 includes an output control section 341 .

(4-1) Output control section 341
The output control section 341 has a function of controlling the output of the operation terminal 300 . For example, the output control unit 341 determines the type of external data received by the communication unit 310, and performs output according to the type. When the external data is control information, the output control section 341 transmits the control information from the communication section 310 to the management control terminal 22 . Also, when the external data is display information, the output control unit 341 causes the output unit 350 to display the display information.

(5) Output section 350
The output unit 350 has a function of outputting various information. For example, the output unit 350 displays display information.

<5. Functional Configuration of Relay Server>
The functional configuration of the operation terminal 300 has been described above with reference to FIG. Next, the functional configuration of the relay server 400 according to this embodiment will be described with reference to FIG. FIG. 5 is a block diagram showing an example of the functional configuration of the relay server 400 according to this embodiment.
As shown in FIG. 5 , relay server 400 includes communication unit 410 , storage unit 420 , and control unit 430 .

(1) Communication unit 410
The communication unit 410 has a function of transmitting and receiving various information. Communication unit 410 receives internal data from relay device 100 via network NW2. Also, the communication unit 410 transmits the converted internal data to the cloud server 500 .

(2) Storage unit 420
The storage unit 420 has a function of storing various information. The storage unit 420 is configured by a storage medium provided as hardware in the relay server 400, such as an HDD, SSD, flash memory, EEPROM, RAM, ROM, or any combination of these storage media.
The storage unit 420 may temporarily store internal data before conversion or internal data after conversion, for example.

(3) Control unit 430
The control unit 430 has a function of controlling the overall operation of the relay server 400 . The control unit 430 is implemented, for example, by causing a CPU provided as hardware in the relay server 400 to execute a program.
As shown in FIG. 5 , the control section 430 includes a conversion section 431 and an insertion section 432 .

(3-1) Conversion unit 431
The conversion unit 431 has a function of converting the data format of internal data. For example, the conversion unit 431 analyzes internal data received by the communication unit 410 from the relay device 100 and converts it into a data format compatible with the cloud server 500 . For example, the conversion unit 431 converts internal data into data in JSON format. At this time, the conversion unit 431 determines whether or not the internal data is invalid data by analyzing the internal data. If the internal data is invalid data, the conversion unit 431 does not convert the data format and excludes it from the data linked to the cloud server 500 .

(3-2) Insertion portion 432
The insertion unit 432 has a function of inserting internal data into the database in the cloud server 500 . For example, the insertion unit 432 analyzes internal data converted by the conversion unit 431 and generates a query. After generation, the insertion unit 432 inserts the internal data converted by the conversion unit 431 into the database in the cloud server 500 using the generated query. That is, the relay server 400 links the internal data to the cloud server 500 by the insertion unit 432 .

The processing of the conversion unit 431 described above is performed at the front of the relay server 400 , and the processing of the insertion unit 432 is performed at the back of the relay server 400 . By dividing the processing of the conversion unit 431 and the processing of the insertion unit 432 into front and back in this way, the load (writing amount) on the database due to external access can be controlled to be constant.

<6. Functional Configuration of Cloud Server>
The functional configuration of the relay server 400 has been described above with reference to FIG. Next, the functional configuration of the cloud server 500 according to this embodiment will be described with reference to FIG. FIG. 6 is a block diagram showing an example of the functional configuration of the cloud server 500 according to this embodiment.
As shown in FIG. 6 , cloud server 500 includes communication unit 510 , storage unit 520 , and control unit 530 .

(1) Communication unit 510
The communication unit 510 has a function of transmitting and receiving various information. Communication unit 510 receives internal data from relay server 400 . Communication unit 510 also receives a request to acquire external data from relay device 100 via network NW2 and transmits the external data to relay device 100 .

(2) Storage unit 520
The storage unit 520 has a function of storing various information. The storage unit 520 is configured by a storage medium provided as hardware in the cloud server 500, such as an HDD, SSD, flash memory, EEPROM, RAM, ROM, or any combination of these storage media.
Storage unit 520 stores, for example, internal data received by communication unit 510 from relay server 400 . The storage unit 520 also stores production information, management information, and the like input by the user from a terminal outside the closed network NW1 via a web browser or application.

(3) Control unit 530
The control unit 530 has a function of controlling the overall operation of the cloud server 500 . The control unit 530 is implemented, for example, by causing a CPU provided as hardware in the cloud server 500 to execute a program.
As shown in FIG. 6, the control unit 530 includes an internal data management unit 531, an external data linkage unit 532, and a production management unit 533.

(3-1) Internal data management unit 531
The internal data management unit 531 has a function of managing internal data. For example, the internal data management unit 531 causes the storage unit 520 to store (insert into the database) the internal data received by the communication unit 510 from the relay server 400 .

(3-2) External data linkage unit 532
The external data linking unit 532 has a function of linking external data. For example, when the communication unit 510 receives an external data acquisition request from the relay device 100 , the external data linking unit 532 links the external data to the relay device 100 .
At this time, the external data linking unit 532 checks whether or not the external data stored in the storage unit 520 includes external data that has not been linked to the inside of the closed network NW1. The external data has a status indicating, for example, "linked" or "not linked" to the inside of the closed network NW1. Therefore, the external data linking unit 532 can check the presence or absence of unlinked external data by referring to the status. If there is unlinked external data, the external data linking unit 532 links only the unlinked external data to the relay device 100 . After linking, the external data linking unit 532 updates the status of the linked external data to "coordinated".

(3-3) Production control department 533
The production management section 533 has a function of generating information for managing production in the factory FC as external data. The production management unit 533 generates external data based on the internal data linked via the relay server 400 by the external link relay unit 133 of the relay device 100 . Moreover, the production control section 533 may generate external data based on the internal data and the control information stored in the storage section 520 . The management information stored in storage unit 520 is management information input by a user and accumulated over a long period of time. Therefore, the production management unit 533 can generate external data considering long-term progress by using the management information as well.
As shown in FIG. 6 , the production management section 533 includes an equipment status confirmation section 5331 , an equipment control section 5332 , an inventory management section 5333 and a monitoring section 5334 .

(3-3-1) Equipment state confirmation unit 5331
The equipment status confirmation unit 5331 has a function of confirming the status of the production equipment 20 within the closed network NW1. The equipment status confirmation unit 5331 confirms whether the status of the production equipment 20 is correct before, during or after production by the production equipment 20 in the closed network NW1, and generates information indicating the confirmation result as external data. The equipment status confirmation unit 5331 confirms the status of the production equipment 20 based on information acquired from the production equipment 20 in the closed network NW1 before, during or after production. The information acquired from the production equipment 20 is, for example, production information. Specifically, the production information acquired before production includes information indicating materials and jigs set in the production equipment 20, setting values (setting information) set for the production equipment 20, and the like. is. The production information acquired during or after production includes information indicating materials and jigs set in the production equipment 20 and current values of items for which setting values are set.
An example in which the facility status checking unit 5331 checks the status of the production facility 20 before production by the production facility 20 will be described below as an example. Hereinafter, the processing performed by the facility status confirmation unit 5331 is also referred to as "pre-production confirmation", and the information indicating the confirmation result is also referred to as "confirmation result information".

In this embodiment, the user selects the work to be started by operating the operation terminal 300 when starting production of a product. When the user selects a work, production information is acquired by the management control terminal 22 from the production facility 20 corresponding to the selected work. The production information acquired by the management control terminal 22 is linked from the relay device 100 to the cloud server 500 as internal data. The production information linked from the management control terminal 22 includes information indicating materials and jigs used in the work selected by the user, setting values of the production equipment 20, and materials and jigs actually set in the production equipment 20. , set values, etc. For this reason, the equipment status confirmation unit 5331 confirms, based on the linked production information, whether the correct materials and jigs are used for the work to be started from now on, and whether there are any problems with the setting values of the production equipment 20. can be done. Based on this confirmation, the equipment status confirmation unit 5331 can confirm that the production equipment 20 is in the correct condition if the correct materials and jigs are used and there is no problem with the set values.

(3-3-2) Equipment control unit 5332
The equipment control unit 5332 has a function of controlling the operation of the production equipment 20 within the closed network NW1. The equipment control unit 5332 generates control information for controlling the operation of the production equipment 20 in the closed network NW1 as external data. For example, the equipment control unit 5332 determines whether control of the production equipment 20 is necessary based on production information linked from the relay device 100 during production. When determining that control is necessary, the facility control section 5332 generates control information based on the production information. The production information linked from the relay device 100 during production includes, for example, information indicating the number of stays in the production line. Therefore, the facility control unit 5332 can generate, as control information, an instruction to stop transportation or an instruction to cancel the stoppage of transportation according to the number of stays from the linked production information.
The production information linked from the relay device 100 may be the production information acquired by the sensor terminal 10 and linked, or the production information acquired from the production facility 20 by the management control terminal 22 and linked from the management control terminal 22. It may be production information.

(3-3-3) Inventory management unit 5333
The inventory management unit 5333 has a function of managing inventory related to production in the production facilities 20 within the closed network NW1. The inventory management unit 5333 generates inventory information of products produced by the production equipment 20 in the closed network NW1 as external data. For example, the inventory management unit 5333 generates inventory information based on production information linked from the relay device 100 during production. The production information linked from the relay device 100 during production includes, for example, information indicating the number of products produced, the amount of materials used, and the like. Therefore, the inventory management unit 5333 can calculate the inventory quantity of manufactured products and the inventory quantity of materials from the linked production information.
Note that the inventory information generated by the inventory management unit 5333 may be used for pre-production confirmation by the facility status confirmation unit 5331 .

(3-3-4) Monitoring unit 5334
The monitoring unit 5334 has a function of monitoring production in the production facility 20 within the closed network NW1. The monitoring unit 5334 generates monitoring information indicating the monitoring status as external data.
For example, the monitoring unit 5334 monitors the production status of the production equipment 20 in the closed network NW1, and generates information indicating the production status (hereinafter also referred to as "production status information") as monitoring information. For example, the monitoring unit 5334 generates production status information based on production information linked from the relay device 100 during production. The production information linked from the relay device 100 during production includes, for example, information indicating the production status measured by the sensor terminal 10 . Therefore, the monitoring unit 5334 can monitor the production status of the production facility 20 by monitoring changes in the linked production information.

In addition, the monitoring unit 5334 monitors a sign that an abnormality will occur in production by the production facility 20, and when detecting a sign, generates information indicating the sign (hereinafter also referred to as “sign information”) as monitoring information. do. For example, the monitoring unit 5334 generates predictor information based on production information linked from the relay device 100 during production. The production information linked from the relay device 100 during production includes, for example, information indicating the operating status of the production facility 20 . Therefore, the monitoring unit 5334 can monitor whether there is a sign that an abnormality will occur in the operating state of the production equipment 20 by monitoring changes in the linked production information.

As an example, the monitoring unit 5334 detects a sign that an abnormality will occur based on upper and lower limit value management, change amount management, continuous change, and the like. In the upper and lower limit value management, a sign is detected when the value indicated by the production information is out of the set range. In change amount management, the production information acquired last time is compared with the production information acquired this time, and if the amount of change is equal to or greater than a set value, a sign is detected. In continuous change, a sign is detected when the change is continuous (n-point continuous rise or fall).

<7. Process Flow>
The functional configuration of the cloud server 500 has been described above with reference to FIG. Next, the flow of processing according to the present embodiment will be described with reference to FIGS. 7 to 14. FIG.

(1) Flow of Overall Processing The flow of overall processing in the production control system 1 will be described with reference to FIGS. 7 to 10. FIG.

(1-1) Collection of Internal Data Referring to FIG. 7, the flow of processing for collecting internal data of the factory FC will be described. FIG. 7 is a sequence diagram showing an example of the flow of processing in collecting internal data of the factory FC according to this embodiment.

As shown in FIG. 7, first, the sensor terminal 10 measures production information (step S101). The sensor terminal 10 transmits the measured production information to the relay device 100 (step S102).

The management control terminal 22 acquires production information from the production equipment 20 before production or during production via the control terminal 21 (step S103). The management control terminal 22 transmits the acquired production information to the relay device 100 (step S104).

The management system 30 updates the management information managed by its own system (step S105). After the update, the management system 30 transmits management information indicating at least the updated part to the conversion terminal 31 (step S106).
The conversion terminal 31 converts the data format of the management information received from the management system 30 (step S107). After the conversion, conversion terminal 31 transmits the converted management information to relay device 100 (step S108).

(1-2) External Linkage of Internal Data Next, the flow of processing in external linkage of internal data of the factory FC will be described with reference to FIG. FIG. 8 is a sequence diagram showing an example of the flow of processing in external linkage of internal data of the factory FC according to this embodiment. The processing shown in FIG. 8 is performed, for example, at the timing when the internal data is acquired by the processing shown in FIG.

As shown in FIG. 8, first, the internal data acquisition unit 131 of the relay device 100 acquires internal data (step S201). The internal data is production information and management information transmitted in steps S102, S104, S108, etc. shown in FIG.
Next, the data processing unit 132 of the relay device 100 checks whether the acquired internal data needs processing (step S202). If processing is required (step S202/YES), the process proceeds to step S203. On the other hand, if processing is not required (step S202/NO), the process proceeds to step S204.
When the process proceeds to step S203, the data processing unit 132 processes the internal data (step S203). After processing, the process proceeds to step S204.
When the process proceeds to step S204, the external cooperation relay unit 133 of the relay device 100 transmits the internal data to the relay server 400 via the network NW2 (step S204).

Conversion unit 431 of relay server 400 analyzes the internal data received from relay device 100 (step S205). At this time, the conversion unit 431 checks whether or not there is illegal data in the internal data (step S206). If there is invalid data (step S206/YES), the process proceeds to step S207. On the other hand, if there is no illegal data (step S206/NO), the process proceeds to step S208.
When the process proceeds to step S207, the conversion unit 431 excludes unauthorized data from the linked internal data (step S207). After exclusion, the process proceeds to step S208.
When the process proceeds to step S208, the conversion unit 431 converts the data format of the internal data (step S208). After the conversion, the insertion unit 432 of the relay server 400 generates a query based on the converted internal data, and inserts (transmits) the converted internal data to the cloud server 500 using the query (step S209).

The internal data management unit 531 of the cloud server 500 inserts the internal data received from the relay server 400 into the database of the storage unit 520 and stores it (step S210).

(1-3) Acquisition of External Data Next, the flow of processing for acquiring external data will be described with reference to FIG. FIG. 9 is a sequence diagram showing an example of the flow of processing in acquiring external data according to this embodiment. The processing shown in FIG. 9 may be performed at any timing regardless of whether or not the processing shown in FIGS. 7 and 8 is executed.

As shown in FIG. 9, first, the external data acquisition unit 134 of the relay device 100 confirms whether or not it is time to acquire external data (step S301). If it is the acquisition timing (step S301/YES), the process proceeds to step S302. On the other hand, if it is not the acquisition timing (step S301/NO), step S301 is repeated.
When the process proceeds to step S302, the external data acquisition unit 134 transmits an external data acquisition request to the cloud server 500 via the network NW2 (step S302).

In the cloud server 500 that has received the external data acquisition request, the external data linking unit 532 determines whether there is external data that has not been linked to the inside of the closed network NW1 in the external data stored in the storage unit 520. is confirmed (step S303). If there is unlinked external data (step S303/YES), the process proceeds to step S304. On the other hand, if there is no unlinked data (step S303/NO), the process ends.
When the process proceeds to step S304, the external data linking unit 532 acquires unlinked external data from the storage unit 520 (step S304).
Next, the external data linking unit 532 updates the status of the acquired unlinked external data to "linked" (step S305).
Next, the external data linking unit 532 transmits the acquired unlinked external data to the relay device 100 via the network NW2 (step S306).

In the relay device 100 that has received the uncoordinated external data, the external data acquisition unit 134 acquires the external data from the communication unit 110 (step S307).
Next, the internal cooperation relay unit 135 of the relay device 100 transmits the external data acquired by the external data acquisition unit 134 to the on-premises server 200 (step S308).

(1-4) Internal Linkage of External Data Next, the flow of processing in internal linkage of external data will be described with reference to FIG. FIG. 10 is a sequence diagram showing an example of the flow of processing in internal linkage of external data according to this embodiment. The process shown in FIG. 10 is performed, for example, after step S308 of the process shown in FIG.

As shown in FIG. 10, first, the conversion unit 231 of the on-premises server 200 analyzes the external data linked from the relay device 100 and checks whether or not there is unauthorized data (step S401). If there is invalid data (step S401/YES), the process proceeds to step S402. On the other hand, if there is no illegal data (step S401/NO), the process proceeds to step S403.
When the process proceeds to step S402, the conversion unit 231 excludes unauthorized data from the linked external data (step S402). After exclusion, the process proceeds to step S403.
When the process proceeds to step S403, the conversion unit 231 converts the data format of the external data (step S403). After the conversion, the insertion unit 232 of the on-premises server 200 generates a query based on the converted external data, inserts the converted external data into the database of the storage unit 220 of the on-premises server 200 using the query, and stores it. (Step S404).
Next, the internal linking unit 233 of the on-premises server 200 checks whether the linked external data is information for the conversion terminal 31 or information for the operation terminal 300 (step S405). Here, the information for the conversion terminal 31 is management information, and the information for the operation terminal 300 is control information or display information. If the information is for conversion terminal 31 (step S405/for conversion terminal), the process proceeds to step S406. On the other hand, if the information is for the operation terminal 300 (step S405/for operation terminal), the process proceeds to step S410.

When the process proceeds to step S406, the internal cooperation unit 233 transmits the external data to the conversion terminal 31 (step S406).
Next, the conversion terminal 31 converts the data format of the external data (that is, management information) received from the on-premises server 200 (step S407). After conversion, the conversion terminal 31 transmits the converted management information to the management system 30 (step S408).
Next, the management system 30 updates existing management information based on the received management information (step S409).

When the process proceeds to step S410, the internal cooperation unit 233 transmits the external data to the operation terminal 300 (step S410).
Next, the output control unit 341 of the operation terminal 300 checks whether the external data received by the communication unit 310 is control information or display information (step S411). If it is control information (step S411/control information), the process proceeds to step S412. On the other hand, if it is display information (step S411/display information), the process proceeds to step S414.

When the process proceeds to step S412, the output control unit 341 transmits control information to the control terminal 21 via the management control terminal 22 (step S412). At this time, the management control terminal 22 that has received the control information from the operation terminal 300 refers to the contents indicated by the control information, for example, and transmits the control information to the control terminal 21 corresponding to the production facility 20 to be controlled.
The control terminal 21 that has received the control information controls the operation of the production facility 20 managed by the own terminal based on the control information (step S413).

When the process proceeds to step S414, the output control unit 341 causes the output unit 350 to display the display information (step S414).

(2) Specific Example of Processing The flow of the overall processing in the production management system 1 has been described above. Next, a specific example of processing will be described with reference to FIGS. 11 to 14. FIG. In the following, as an example, the flow of processing from the start of production to its completion will be described in detail when the start of production is set as the starting point of the processing.

(2-1) Flow of Processing from Work Selection to Pre-production Confirmation First, the flow of processing from work selection to pre-production confirmation will be described with reference to FIG. FIG. 11 is a sequence diagram showing an example of the flow of processing from work selection to pre-production confirmation according to this embodiment.

As shown in FIG. 11, first, the worker operates the operation terminal 300 to select a work to be started (step S501).
The operation terminal 300 that has received the operation from the worker transmits an instruction to stop the transportation to the production facility 20 via the management control terminal 22 and the control terminal 21 (step S502).
The production equipment 20 that has received the instruction stops the transportation (step S503).

Next, the management control terminal 22 acquires production information from the production facility 20 whose transportation has been stopped via the control terminal 21 (step S504).
Next, the management control terminal 22 transmits the acquired production information to the cloud server 500 via the relay device 100 and the relay server 400 (step S505).

The facility status confirmation unit 5331 of the cloud server 500 performs pre-production confirmation based on the received production information (step S506). After the pre-production confirmation, the facility status confirmation unit 5331 generates confirmation result information (step S507).
The external data acquisition unit 134 of the relay device 100 periodically transmits an external data acquisition request to the cloud server 500 (step S508).
Assume that when the communication unit 510 of the cloud server 500 receives the external data acquisition request from the relay device 100, there is uncoordinated confirmation result information (for example, confirmation result information generated in step S507). In this case, the external data linking unit 532 of the cloud server 500 acquires the unlinked confirmation result information and transmits it to the operation terminal 300 via the relay device 100 and the on-premises server 200 (step S509).
In the operation terminal 300 that has received the confirmation result information, the output control unit 341 causes the output unit 350 to display the confirmation result information (step S510).

(2-2) Flow of Processing from Confirmation of Confirmation Result by Worker to Update of Inventory Next, the flow of processing from confirmation of the confirmation result by the worker to update of inventory will be described with reference to FIG. FIG. 12 is a sequence diagram showing an example of the flow of processing from confirmation of the confirmation result by the worker to inventory update according to the present embodiment. The process shown in FIG. 12 is performed, for example, after step S510 of the process shown in FIG.

As shown in FIG. 12, first, the operator confirms the confirmation result displayed on the operation terminal 300 (step S601). The operator confirms whether or not all confirmations have been completed normally (step S602). If not completed (step S602/NO), the process proceeds to step S603. On the other hand, if completed (step S602/YES), the process proceeds to step S604.
When the process proceeds to step S603, the operator makes corrections so that all confirmations are completed normally (step S603). In the correction correspondence, for example, materials and jigs set in the production equipment 20 are changed, setting values set in the production equipment 20 are corrected, and additional information necessary for production is input. Note that it is also possible to change the setting values collectively. After the change, the process returns to step S602.

When the process proceeds to step S604, the worker operates the operation terminal 300 to start production (step S604).
The operation terminal 300, which has received the operation from the worker, transmits an instruction to cancel the transportation stop to the production facility 20 via the management control terminal 22 and the control terminal 21 (step S605).
The production facility 20 that has received the instruction resumes transportation (step S606). Accordingly, production by the production facility 20 is started.

After starting production, the management control terminal 22 acquires production information from the production facility 20 via the control terminal 21 (step S607).
Next, the management control terminal 22 transmits the acquired production information to the cloud server 500 via the relay device 100 and the relay server 400 (step S608).
Next, the inventory management unit 5333 of the cloud server 500 generates inventory information based on the production information received by the communication unit 510, and updates the inventory information managed by the cloud server 500 (step S609).

(2-3) Flow of Processing Related to Control of Production Equipment by Cloud Server Next, a flow of processing related to control of the production equipment 20 by the cloud server 500 will be described with reference to FIG. FIG. 13 is a sequence diagram showing an example of the flow of processing regarding control of the production equipment 20 by the cloud server 500 according to this embodiment. The process shown in FIG. 13 may be performed, for example, before or after step S609 of the process shown in FIG. 12, or may be performed in parallel with step S609.

As shown in FIG. 13, first, the internal data management unit 531 of the cloud server 500 causes the storage unit 520 to store the production information received by the communication unit 510 from the relay server 400 (step S701).
Next, the equipment control unit 5332 of the cloud server 500 confirms whether or not control of the production equipment 20 is necessary based on the production information (step S702). If control is required (step S702/YES), the process proceeds to step S703. On the other hand, if control is not required (step S702/NO), the process proceeds to step S704.
When the process proceeds to step S703, the equipment control unit 5332 generates control information as external data (step S703). After generation, the process proceeds to step S704.
The external data acquisition unit 134 of the relay device 100 periodically transmits an external data acquisition request to the cloud server 500 (step S704).
Assume that when the communication unit 510 of the cloud server 500 receives the external data acquisition request from the relay device 100, there is uncoordinated control information (for example, the control information generated in step S703). In this case, the external data linkage unit 532 of the cloud server 500 acquires the unlinked control information and transmits it to the operation terminal 300 via the relay device 100 and the on-premises server 200 (step S705).

In the operation terminal 300 that has received the control information, the output control unit 341 transmits the control information to the control terminal 21 via the management control terminal 22 (step S706). At this time, the management control terminal 22 that has received the control information from the operation terminal 300 refers to the contents indicated by the control information, for example, and transmits the control information to the control terminal 21 corresponding to the production facility 20 to be controlled.
The control terminal 21 that has received the control information controls the operation of the production equipment 20 managed by the own terminal based on the control information (step S707).

(2-4) Flow of Processing Related to Monitoring by Cloud Server Next, a flow of processing related to monitoring by the cloud server 500 will be described with reference to FIG. FIG. 14 is a sequence diagram showing an example of the flow of processing related to monitoring by the cloud server 500 according to this embodiment. The processing shown in FIG. 14 is performed, for example, before or after step S609 of the processing shown in FIG. 12 or in parallel with step S609. Further, the processing shown in FIG. 14 may be performed either before or after the processing shown in FIG. 13, or may be performed in parallel with the processing shown in FIG.

As shown in FIG. 14, first, the internal data management unit 531 of the cloud server 500 causes the storage unit 520 to store the production information received by the communication unit 510 from the relay server 400 (step S801).
Next, the monitoring unit 5334 of the cloud server 500 monitors the production status of the production equipment 20 and the sign of occurrence of an abnormality based on the production information (step S802).
Next, the monitoring unit 5334 generates monitoring information (step S803). At this time, if no sign of abnormality occurrence is detected, the monitoring unit 5334 may generate monitoring information including only production status information.

Next, the monitoring unit 5334 confirms whether or not a sign of abnormality has been detected (step S804). If a sign of abnormality is detected (step S804/YES), the process proceeds to step S805. On the other hand, if no sign of abnormality is detected (step S804/NO), the process proceeds to step S806.
When the process proceeds to step S805, the equipment control unit 5332 also generates control information as external data (step S805). The control information generated here is, for example, information for controlling the operation of the production facility 20 so as not to cause an abnormality whose sign has been detected. After generation, the process proceeds to step S806.
The external data acquisition unit 134 of the relay device 100 periodically transmits an external data acquisition request to the cloud server 500 (step S806).
When the communication unit 510 of the cloud server 500 receives the external data acquisition request from the relay device 100, uncoordinated monitoring information (for example, the monitoring information generated in step S803) or control information (for example, the control information generated in step S805) ). In this case, the external data linking unit 532 of the cloud server 500 acquires the unlinked monitoring information or control information and transmits it to the operation terminal 300 via the relay device 100 and the on-premises server 200 (step S807).

In the operation terminal 300 that received the monitoring information, the output control unit 341 displays the monitoring information on the output unit 350 (step S808). The operator confirms the monitoring status by confirming the monitoring information displayed on the output unit 350 (step S809).
The operation terminal 300 confirms whether or not the control information has been received together with the monitoring information (step S810). If control information has also been received (step S810/YES), the process proceeds to step S811. On the other hand, if the control information has not been received (step S810/NO), the process ends.
When the process proceeds to step S811, the output control unit 341 transmits control information to the control terminal 21 via the management control terminal 22 (step S811). At this time, the management control terminal 22 that has received the control information from the operation terminal 300 refers to the contents indicated by the control information, for example, and transmits the control information to the control terminal 21 corresponding to the production facility 20 to be controlled.
The control terminal 21 that has received the control information controls the operation of the production facility 20 managed by the own terminal based on the control information (step S812).

As described above, the production management system 1 according to the present embodiment periodically communicates with the external system 3 outside the closed network NW1 from inside the closed network NW1 in the factory FC (production base). an external data acquisition unit 134 that acquires external data from the external system 3 for linking from the outside to the inside of the closed network NW1; and an internal cooperation relay unit 135 that cooperates with.

With such a configuration, the production management system 1 according to the present embodiment can transmit data from the outside of the closed network NW1 to the equipment inside the closed network NW1 for the production site such as the factory FC where the closed network NW1 is constructed. do.
Therefore, the production management system 1 according to the present embodiment makes it possible to transmit data from the outside to the inside of the closed network and control the equipment inside the closed network.
As a result, workers and administrators at the production site can remotely control equipment inside the closed network NW1 and perform inspection work remotely from outside the closed network NW1.

The embodiments of the present invention have been described above. A part or all of the functions of the production management system 1 in the above-described embodiment may be realized by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in this recording medium may be read into a computer system and executed. It should be noted that the "computer system" referred to here includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems. Furthermore, "computer-readable recording medium" refers to a program that dynamically retains programs for a short period of time, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. It may also include something that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client in that case. Further, the program may be for realizing a part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system. It may be implemented using a programmable logic device such as an FPGA (Field Programmable Gate Array).

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configurations are not limited to those described above, and various design changes can be made without departing from the gist of the present invention. It is possible to

1... Production control system, 2... Internal system, 3... External system, 10 (10-1 to 10-N)... Sensor terminal, 20 (20-1 to 20-L)... Production equipment, 21 (21-1 to 21-K)... Control terminal 22... Management control terminal 30 (30-1 to 30-J)... Management system 31... Conversion terminal 100... Relay device 110... Communication unit 120... Storage unit 130... Control unit 131 Internal data acquisition unit 132 Data processing unit 133 External link relay unit 134 External data acquisition unit 135 Internal link relay unit 200 On-premise server 210 Communication unit 220 Storage Unit 230 Control unit 231 Conversion unit 232 Insertion unit 233 Internal cooperation unit 300 Operation terminal 310 Communication unit 320 Input unit 330 Storage unit 340 Control unit 341 Output control unit 350 Output unit 400 Relay server 410 Communication unit 420 Storage unit 430 Control unit 431 Conversion unit 432 Insertion unit 500 Cloud server 510 Communication unit 520 Storage unit 530 Control unit 531 Internal data management unit 532 External data cooperation unit 533 Production control unit 5331 Equipment state confirmation unit 5332 Equipment control unit 5333 Inventory control unit 5334 Monitoring unit, NW1... Closed network, NW2... Network

Claims (14)

A production control system comprising a relay device, an internal system, and an external system,
The relay device
From the internal system inside the closed network built in the production base, using the authentication information, the external system outside the closed network is periodically accessed , and the outside of the closed network is linked to the inside. Periodically sending an acquisition request for external data to the external system , and acquiring the external data not linked to the internal system when the external data not linked to the internal system exists in the external system an external data acquisition unit for
an internal link relay unit that links the external data acquired by the external data acquisition unit with equipment inside the closed network;
production control system. The external system is
External data for transmitting the unlinked external data to the relay device when the acquisition request is received from the relay device and the external data not linked to the relay device that has transmitted the acquisition request exists. Liaison Department,
The production control system according to claim 1, comprising: The external system is
a production control unit that generates information for managing production at the production base as the external data;
The production control system according to claim 1, comprising: The production control department
A facility status confirmation unit that checks whether the status of the production facility is correct before, during, or after production by the production facility in the closed network, and generates information indicating the confirmation result as the external data;
4. The production control system of claim 3 , further comprising: The facility status confirmation unit checks whether the status of the production facility is correct based on information acquired from the production facility in the closed network.
The production management system according to claim 4 . The production control department
an equipment control unit that generates control information for controlling the operation of production equipment in the closed network as the external data;
4. The production control system of claim 3 , further comprising: The production control department
an inventory management unit that generates, as the external data, inventory information of products produced by production equipment in the closed network;
4. The production control system of claim 3 , further comprising: The production control department
a monitoring unit that monitors the production status of production equipment in the closed network and generates information indicating the monitoring status as the external data;
4. The production control system of claim 3 , further comprising: The monitoring unit monitors a sign of an abnormality occurring in production by the production equipment, and when detecting the sign, generates information indicating the sign as the external data.
The production management system according to claim 8 . an internal data acquisition unit that acquires, within the closed network, internal data that links from the inside of the closed network to the outside;
an external linkage relay unit that links the internal data acquired by the internal data acquisition unit from inside the closed network to the external system;
further comprising
The production control unit generates the external data based on the internal data linked by the external link relay unit.
The production management system according to any one of claims 3 to 9 . The external system is
a storage unit that stores management information related to production management at the production base, which is input from outside the closed network;
further comprising
The production management unit generates the external data based on the internal data and the management information.
The production management system according to claim 10 . The production control system is
an internal system for managing production at the production base from inside the closed network;
further comprising
The internal system is
an internal linking unit that links the external data linked by the internal linking relay unit to a facility corresponding to the external data;
The production control system according to claim 1, comprising: A production control method in a production control system comprising a relay device, an internal system, and an external system,
The external data acquisition unit of the relay device periodically accesses the external system outside the closed network using authentication information from the internal system inside the closed network constructed in the production site, A request for obtaining external data to be linked to the inside of the closed network is periodically sent to the external system , and when the external data not linked to the internal system exists in the external system, the external system sends the request . an external data acquisition process for acquiring the unlinked external data to be processed ;
an internal cooperation relay process in which the internal cooperation relay unit of the relay device cooperates with the equipment inside the closed network with the external data acquired by the external data acquisition unit;
production control methods including; A program for causing a computer to function as a production control system comprising a relay device, an internal system, and an external system,
a computer functioning as the relay device ,
From the internal system inside the closed network built in the production base, using the authentication information, the external system outside the closed network is periodically accessed , and the outside of the closed network is linked to the inside. Periodically sending an acquisition request for external data to the external system , and acquiring the external data not linked to the internal system when the external data not linked to the internal system exists in the external system external data acquisition means for
an internal linkage relay means for linking the external data acquired by the external data acquisition means with facilities inside the closed network;
A program to function as

Images