Production management system, production management method and program

Abstract

To provide a production management system capable of controlling facilities in a closed network by transmitting data from external to internal of the closed network, a production management method and a program.SOLUTION: A production management system includes: an external data acquisition part for periodically communicating from internal of a closed network at a production base to an external system outside the closed network, to acquire, from the external system, external data linked from external to the internal of the closed network; and an internal linkage relay part for linking the external data acquired by the external data acquisition part with facilities inside the closed network.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a production management system, a production management method, and a program. [Background technology]

[0002] In recent years, the need for IoT (Internet of Things) has been increasing in various industrial fields. For example, at production sites, IoT can be used to collect data from sensors installed at the production site, analyze the data on a server, and use the analysis results for production management.

[0003] The following Patent Document 1 discloses a technology in which measurement data measured at each process in a product production factory is converted into a common format by an IoT relay device, and then transmitted to a cloud computing system for analysis. Furthermore, Patent Document 2 listed below discloses a technology in which a gateway device collects, converts, processes, etc., measurement data measured by a sensor and then transmits it to a data collection server, and the data collection server generates rules based on the measurement data. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6419234 [Patent Document 2] Patent No. 5737696 Summary of the Invention [Problem to be solved by the invention]

[0005] Both of the above Patent Documents 1 and 2 disclose transmitting measurement data measured by a sensor to the server side via an IoT relay device or a gateway device from the server side. On the other hand, neither of the patent documents discloses transmitting data to a production facility installed in a production factory based on the measurement data transmitted to the server side, and controlling the production facility. If data can be transmitted from the server side to the production facility in the production factory, the scope of what can be done in production management can be expanded. However, in production sites such as factories, closed networks are often constructed, and it has been difficult to transmit data from outside the closed network to the facility inside the closed network and control the facility.

[0006] In view of the above-mentioned problems, an object of the present invention is to provide a production management system, a production management method, and a program capable of transmitting data from outside a closed network to inside the closed network to control equipment inside the closed network. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems, a production management system according to one embodiment of the present invention includes an external data acquisition unit that periodically communicates from inside a closed network at a production base to an external system outside the closed network, and acquires external data from the external system that is linked from outside to inside 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.

[0008] A production management method according to one embodiment of the present invention includes an external data acquisition process in which an external data acquisition unit periodically communicates from inside a closed network at a production base to an external system outside the closed network, and acquires external data from the external system that is linked from outside to inside the closed network, and an internal linkage relay process in which an internal linkage relay unit links the external data acquired by the external data acquisition unit to equipment inside the closed network.

[0009] A program according to one embodiment of the present invention causes a computer to function as an external data acquisition means that periodically communicates from inside a closed network at a production base to an external system outside the closed network, and acquires external data from the external system that is linked from outside the closed network to inside the closed network, and as an internal linking relay means that links the external data acquired by the external data acquisition means to equipment inside the closed network. Effect of the Invention

[0010] According to the present invention, it is possible to control equipment inside a closed network by transmitting data from the outside of the closed network to the inside of the closed network. [Brief description of the drawings]

[0011] [Figure 1] 1 is a block diagram showing an example of a schematic configuration of a production management system according to an embodiment of the present invention; [Diagram 2] 2 is a block diagram showing an example of a functional configuration of a relay device according to the embodiment; FIG. [Diagram 3] FIG. 2 is a block diagram showing an example of a functional configuration of an on-premises server according to the present embodiment. [Figure 4] 2 is a block diagram showing an example of a functional configuration of an operation terminal according to the present embodiment. FIG. [Diagram 5] 2 is a block diagram showing an example of a functional configuration of a relay server according to the embodiment; FIG. [Figure 6] 2 is a block diagram showing an example of a functional configuration of a cloud server according to the present embodiment. FIG. [Figure 7] FIG. 11 is a sequence diagram showing an example of a process flow for collecting internal data of a factory according to the embodiment. [Figure 8] 11 is a sequence diagram showing an example of a process flow in external linkage of internal data of a factory according to the embodiment; FIG. [Figure 9] FIG. 11 is a sequence diagram showing an example of a process flow for acquiring external data according to the embodiment. [Figure 10] 11 is a sequence diagram showing an example of a process flow in internal linkage of external data according to the embodiment; FIG. [Figure 11] FIG. 11 is a sequence diagram showing an example of a processing flow from operation selection to pre-production confirmation according to the present embodiment. [Figure 12] 11 is a sequence diagram showing an example of a process flow from confirmation of a confirmation result by a worker to updating of inventory according to the present embodiment. FIG. [Figure 13] 11 is a sequence diagram showing an example of a process flow regarding control of production equipment by a cloud server according to the embodiment. FIG. [Figure 14] 11 is a sequence diagram showing an example of a processing flow regarding monitoring by a cloud server according to the embodiment. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[0013] <1.Outline of the production management system> The schematic configuration of the production management system according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the schematic configuration of the production management system according to this embodiment. The production management system 1 shown in FIG. 1 is a system for managing production at a production base. The production base is, for example, a factory FC that produces (manufactures) a specified product. The field of the factory FC is not particularly limited, and examples of the fields include printing, papermaking, machinery, automobiles, chemicals, steel, construction, food, pharmaceuticals, and home appliances. The production processes managed by the factory FC are also not particularly limited, and for example, a receiving process in which parts and raw materials are delivered, a processing process in which the parts and raw materials are processed, an assembly process in which the processed parts are assembled, an inspection process in which the assembled products are inspected, and a shipping process in which the inspected products are shipped are each managed. Each process can be further divided into detailed processes depending on the production target.

[0014] As shown in FIG. 1, the production management 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 a closed network NW1 (closed network) constructed 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 a firewall. The external system 3 is a system for managing production in the factory FC from outside the closed network NW1. The production management system 1 makes it possible to manage production in the factory FC from outside the closed network NW1 by enabling the inside and outside of the closed network NW1 to cooperate with each other.

[0015] 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, an on-premise server 200, and an operation terminal 300. The external system 3 includes a relay server 400 and a cloud server 500. The relay device 100 is communicably connected to a relay server 400 and a cloud server 500 via a network NW2.

[0016] (1) Sensor terminal 10 The sensor terminal 10 is a terminal provided in the factory FC, and acquires (measures) information related to production in the factory FC (hereinafter also referred to as "production information"). Examples of the production information measured by the sensor terminal 10 include temperature and relative humidity measured by a temperature and humidity sensor, information on accumulated water detected by a water leakage sensor, and a current value measured by a current sensor. The sensor terminal 10 transmits the measured production information to the relay device 100.

[0017] For example, a communication standard such as LPWA (Low Power Wide Area) or LTE (Long Term Evolution) or 4G (fourth generation mobile communication system) may be used for communication between the sensor terminal 10 and the relay device 100. Specific LPWA standards include ZETA, LoRa (registered trademark), EnOcean (registered trademark), etc. When LPWA is used, an access point or an LPWA server (e.g., a cloud server) may be provided between the sensor terminal 10 and the relay device 100. In this case, the sensor terminal 10 transmits measured production information to the LPWA server via the access point. After that, the LPWA server transmits (links) 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.

[0018] The number of sensor terminals 10 installed in the factory FC is not particularly limited, and any number N (N is a natural number) of sensor terminals 10-1 to 10-N may be installed in the factory FC. Furthermore, the positions at which the sensor terminals 10 are installed in the factory FC are not particularly limited as long as they are positions at which the above-mentioned production information can be measured, and may be any positions.

[0019] 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 multiple sensor terminals 10. The location at which the access point is provided in the factory FC is not particularly limited as long as it is a location that can relay the communication of the sensor terminals 10 described above, and may be any location.

[0020] (2) Production facilities 20 The production equipment 20 is equipment used in the production of products. The production equipment 20 is, for example, a production device that assembles and processes products, a labeler that attaches labels to products, a transport conveyor that transports products, an inspection device, etc. The production equipment 20 is installed in the factory FC in correspondence with a predetermined process for producing products.

[0021] The number of production equipment 20 installed in the factory FC is not particularly limited, and any number L (L is a natural number) of production equipment 20-1 to 20-L may be installed in the factory FC. Furthermore, the location at which the production equipment 20 is installed in the factory FC is not particularly limited, and may be any location.

[0022] (3) Control terminal 21 The control terminal 21 is a terminal that controls the operation of the production equipment 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 communicatively connected to the corresponding production equipment 20. In addition, the control terminal 21 is communicatively connected to the management control terminal 22 via a predetermined PLC network.

[0023] The number of control terminals 21 provided in the factory FC is not particularly limited, and any 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 multiple production facilities 20. Furthermore, the location at which the control terminal 21 is provided in the factory FC is not particularly limited, and may be any location.

[0024] (4) Management and control terminal 22 The management control terminal 22 is a terminal that functions as a master control terminal for the control terminal 21. When the control terminal 21 is a PLC, the management control terminal 22 is also a PLC. The management control terminal 22 is communicatively connected to each of the control terminals 21 via a predetermined PLC network. The management control terminal 22 acquires production information including predetermined information related to the operation of the production facility 20 and predetermined information related to the production of products from the control terminal 21 through communication with the control terminal 21. The predetermined information related to the operation is, for example, information indicating setting values ​​for the operation of the production facility 20 (hereinafter also referred to as "setting information"). In addition, the predetermined information related to the production of products is, for example, information indicating a production plan for 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 also referred to as "production results information"). In addition, the management control terminal 22 issues instructions and notifications related to the operation of the production facility 20 to the control terminal 21 through communication with the control terminal 21. The location where the management control terminal 22 is provided in the factory FC is not particularly limited, and may be any location.

[0025] (5) Management System 30 The management system 30 is a system that manages information related to 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 or a WMS (Warehouse Management System). The management system 30 is communicatively connected to a conversion terminal 31. In communication with the conversion terminal 31, the management system 30 transmits and receives, for example, the management information. The number of management systems 30 used in the factory FC is not particularly limited, and any number J (J is a natural number) of management systems 30-1 to 30-J may be used in the factory FC.

[0026] (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-premise server 200. When transmitting data (e.g., management information) from the management system 30 to the on-premise server 200, the conversion terminal 31 converts the data received from the management system 30 into a data format that matches the on-premise server 200, and then transmits the data to the on-premise server 200. On the other hand, when transmitting data from the on-premise server 200 to the management system 30, the conversion terminal 31 converts the data received from the on-premise server 200 into a data format that matches the management system 30, and then transmits the data to the management system 30.

[0027] The conversion terminal 31 may also be capable of accepting input of data in an arbitrary data format and outputting the data in the arbitrary data format without converting the data. The arbitrary data format may be, for example, a text file (CSV (Comma Separated Values) or fixed-length data, etc.), a data format for a database, a data format for HTTP (HyperText Transfer Protocol) communication, etc. As an example, when linking CSV data to a database, first, the management system 30 outputs the 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 for a query set on the conversion terminal 31. Then, the conversion terminal 31 executes the query on the on-premise server 200. As another example, when linking database data to a WEB server through HTTP communication, first, the conversion terminal 31 executes a query to the management system 30 to obtain the linked data. Next, the conversion terminal 31 expands the acquired linked data into HTTP body information set on the conversion terminal 31 (for example, reflecting information in column A in HTTP body information A). Next, the conversion terminal 31 transmits body information in which a URL and the linked data have been expanded to a set URL (Uniform Resource Locator). The destination WEB server then breaks down the received body information and expands it into a database.

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

[0029] The relay device 100 relays, via the network NW2, the communication of data (hereinafter also referred to as "internal data") that is communicated from inside the closed network NW1 to the outside, and data (hereinafter also referred to as "external data") that is communicated from outside the closed network NW1 to the inside. When linking internal data from inside the closed network NW1 to the outside, the relay device 100 acquires the internal data within the closed network NW1, and links the acquired internal data 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 outside to inside the closed network NW1, the relay device 100 acquires 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"), management information, and the like.

[0030] The relay device 100 actively acquires external data from inside the closed network NW1 to the outside. For example, the relay device 100 uses authentication information to periodically (for example, every time a predetermined time elapses) transmit an acquisition request for external data to the cloud server 500 of the external system 3. If unlinked external data exists in the cloud server 500, the relay device 100 acquires the unlinked external data from the cloud server 500. If the external data is acquired, the relay device 100 links the acquired external data to the inside of the closed network NW1.

[0031] (8) On-premise server 200 The on-premise server 200 is a server provided inside the closed network NW1, and manages external data linked from the outside. The on-premise server 200 is communicably connected to the relay device 100, the operation terminal 300, and the conversion terminal 31. The on-premise server 200 receives external data linked from the relay device 100, analyzes the external data, converts the data into a data format that matches the internal system 2, and stores the data. The on-premise server 200 also links the converted external data to a terminal according to its contents. For example, when the external data is control information or display information, the on-premise server 200 links the external data to the operation terminal 300. When the external data is management information, the on-premise server 200 links the external data to the conversion terminal 31.

[0032] (9) Operation terminal 300 The operation terminal 300 is a terminal operated by a user. The user is, for example, a worker or a manager of the factory FC. 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-premise server 200 and the management control terminal 22. For example, the operation terminal 300 receives external data from the on-premise server 200, displays display information of the external data on the own terminal, and transmits control information to the management control terminal 22. In addition, the operation terminal 300 accepts 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.

[0033] (10) Relay server 400 The relay server 400 is a server provided outside the closed network NW1, and relays the linking of internal data to the cloud server 500. The relay server 400 is communicatively connected to the relay device 100 via the network NW2, and receives internal data from the relay device 100. The relay server 400 analyzes the internal data received from the relay device 100, converts it into a data format suited to the cloud server 500, and links it to the cloud server 500.

[0034] (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. The cloud server 500 stores internal data linked from the relay device 100 via the relay server 400. The cloud server 500 also stores various information (e.g., production information and management information) input by a user from a terminal outside the closed network NW1 via a web browser or an application. The cloud server 500 is communicably connected to the relay device 100 via the network NW2, and when an acquisition request for external data is received from the relay device 100 and there is unlinked external data, the cloud server 500 transmits the external data to the relay device 100.

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

[0036] <2. Functional configuration of relay device> The schematic configuration of the production management system 1 has been described above with reference to Fig. 1. Next, the functional configuration of the relay device 100 according to this embodiment will be described with reference to Fig. 2. 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, the relay device 100 includes a communication unit 110, a storage unit 120, and a control unit .

[0037] (1) Communications Department 110 The communication unit 110 has a function of transmitting and receiving various information. In the closed network NW1, 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. In addition, the communication unit 110 transmits external data to the on-premise server 200 in the closed network NW1. In addition, the communication unit 110 transmits internal data to the relay server 400 via the network NW2, and transmits an acquisition request for external data to the cloud server 500. In addition, the communication unit 110 receives external data from the cloud server 500 via the network NW2.

[0038] (2) Storage section 120 The storage unit 120 has a function of storing various information. The storage unit 120 is configured by a storage medium provided as hardware in the relay device 100, such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory, an electrically erasable programmable read only memory (EEPROM), a random access read / write memory (RAM), a read only memory (ROM), or any combination of these storage media. The storage unit 120 temporarily stores, for example, various types of information received by the communication unit 110 and data processed by a data processing unit 132 (described later).

[0039] (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 realized, 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, the control unit 130 includes an internal data acquisition unit 131, a data processing unit 132, an external link relay unit 133, an external data acquisition unit 134, and an internal link relay unit 135.

[0040] (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 communicates from the inside of the closed network NW1 to the outside. For example, the internal data acquisition unit 131 acquires, as internal data, production information that the communication unit 110 receives from the sensor terminal 10 and the management control terminal 22, or management information that the communication unit 110 receives from the conversion terminal 31. After acquisition, the internal data acquisition unit 131 outputs the acquired internal data to the data processing unit 132.

[0041] (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 needs a calculation result using the internal data, the data processing unit 132 processes the internal data by a process of performing a calculation using the internal data acquired by the internal data acquisition unit 131 (hereinafter, also referred to as "arithmetic processing"). The data processing unit 132 can perform, for example, four arithmetic operations, residual calculations, power calculations, logarithmic calculations, and the like in the arithmetic processing. As an example, the data processing unit 132 adds up the weights of the objects measured by each of the sensor terminals 10-1 to 10-N to calculate the total amount.

[0042] Also, assume that the data format of the internal data acquired by the internal data acquisition unit 131 or the data format of the internal data after processing is different from the data format of the internal data required by the cloud server 500. In this case, the data processing unit 132 processes the internal data by a process of converting 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 a "cleansing process"). The data processing unit 132 can perform, for example, fraction processing or range conversion by the cleansing process. In fraction processing, the internal data is rounded up, down, or up, and the number of decimal places is changed. In range conversion, the range (minimum and maximum values) that the value indicated by the internal data can take is converted to a range based on a standard different from the current standard.

[0043] Furthermore, 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. This enables the data processing unit 132 to determine, for example, whether or not to process the internal data, and if so, how to process the internal data.

[0044] (3-3) External Link Relay Unit 133 The external link 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 link relay unit 133 links the internal data acquired by the internal data acquisition unit 131 or the internal data processed by the data processing unit 132 from inside the closed network NW1 to the external system 3.

[0045] (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 the outside. For example, from inside the closed network NW1, communication is periodically performed with an 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 authentication information to access the cloud server 500 and transmits a request to acquire external data. If unlinked external data exists in the cloud server 500, the external data is transmitted from the cloud server 500 to the relay device 100. This allows the external data acquisition unit 134 to acquire the external data received by the communication unit 110 from the cloud server 500.

[0046] (3-5) Internal Linkage Relay Unit 135 The internal link relay unit 135 has a function of relaying linkage of external data to each facility inside the closed network NW1. For example, the internal link relay unit 135 links the external data acquired by the external data acquisition unit 134 to the facility inside the closed network NW1. For example, the internal link relay unit 135 links the external data to the on-premise server 200. The external data linked by the internal link relay unit 135 is further linked to other facilities by the on-premise server 200.

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

[0048] (1) Communications 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 in the closed network NW1. The communication unit 210 also transmits control information or display information to the operation terminal 300 and transmits management information to the conversion terminal 31 in the closed network NW1.

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

[0050] (3) Control unit 230 The control unit 230 has a function of controlling the overall operation of the on-premise server 200. The control unit 230 is realized, for example, by causing a CPU provided as hardware in the on-premise 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.

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

[0052] (3-2) Insertion section 232 The insertion unit 232 has a function of inserting external data into a database in the storage unit 220. For example, the insertion unit 232 analyzes the external data converted by the conversion 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. The above-mentioned processing of the conversion unit 231 is performed at the front end of the on-premise server 200, and the processing of the insertion unit 232 is performed at the back end of the on-premise server 200. In this way, by dividing the processing of the conversion unit 231 and the processing of the insertion unit 232 into the front end and the back end, the load (amount of writing) on ​​the database due to external access can be controlled to a constant level.

[0053] (3-3) Internal Cooperation Department 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 the external data linked by the internal linking relay unit 135 of the relay device 100 to a facility corresponding to the external data. For example, the internal linking unit 233 checks whether the external data converted by the conversion unit 231 is control information, display information, or management information. If 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, if the external data is management information, the internal linking unit 233 links the external data to the conversion terminal 31.

[0054] <4. Functional configuration of the operation terminal> The functional configuration of the on-premise server 200 has been described above with reference to Fig. 3. Next, the functional configuration of the operation terminal 300 according to this embodiment will be described with reference to Fig. 4. 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, the operation terminal 300 includes a communication unit 310, an input unit 320, a storage unit 330, a control unit 340, and an output unit 350.

[0055] (1) Communications 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-premise server 200 in the closed network NW1. The communication unit 310 also transmits the external data (control information) to the management control terminal 22 in the closed network NW1.

[0056] (2) Input unit 320 The input unit 320 has a function of receiving input from a user, and is realized by, for example, a keyboard, a mouse, a button, a touch panel, a microphone, etc. that the operation terminal 300 includes.

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

[0058] (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 realized, 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 unit 340 includes an output control unit 341.

[0059] (4-1) Output control unit 341 The output control unit 341 has a function of controlling the output in 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 unit 341 transmits the control information from the communication unit 310 to the management control terminal 22. When the external data is display information, the output control unit 341 causes the output unit 350 to display the display information.

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

[0061] <5. Functional configuration of the relay server> The functional configuration of the operation terminal 300 has been described above with reference to Fig. 4. Next, the functional configuration of the relay server 400 according to this embodiment will be described with reference to Fig. 5. 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, the relay server 400 includes a communication unit 410, a storage unit 420, and a control unit 430.

[0062] (1) Communications Department 410 The communication unit 410 has a function of transmitting and receiving various information. The communication unit 410 receives internal data from the relay device 100 via the network NW2. The communication unit 410 also transmits the converted internal data to the cloud server 500.

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

[0064] (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 realized, 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 unit 430 includes a conversion unit 431 and an insertion unit 432.

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

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

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

[0068] <6. Cloud server functional configuration> The functional configuration of the relay server 400 has been described above with reference to Fig. 5. Next, the functional configuration of the cloud server 500 according to this embodiment will be described with reference to Fig. 6. 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 a communication unit 510, a storage unit 520, and a control unit 530.

[0069] (1) Communications Unit 510 The communication unit 510 has a function of transmitting and receiving various information. The communication unit 510 receives internal data from the relay server 400. The communication unit 510 also receives an acquisition request for external data from the relay device 100 via the network NW2 and transmits the external data to the relay device 100.

[0070] (2) Storage section 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, an SSD, a flash memory, an EEPROM, a RAM, a ROM, or any combination of these storage media. The storage unit 520 stores, for example, internal data received by the communication unit 510 from the relay server 400. The storage unit 520 also stores production information and management information input by a user from a terminal outside the closed network NW1 via a web browser or an application.

[0071] (3) Control unit 530 Control unit 530 has a function of controlling the overall operation of cloud server 500. Control unit 530 is realized, for example, by causing a CPU provided as hardware in 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 linking unit 532, and a production management unit 533.

[0072] (3-1) Internal Data Management Department 531 The internal data management unit 531 has a function of managing the internal data. For example, the internal data management unit 531 causes the internal data received by the communication unit 510 from the relay server 400 to be stored in the storage unit 520 (inserted into a database).

[0073] (3-2) External data linking 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 there is any external data that has not been linked to the closed network NW1 among the external data stored in the storage unit 520. The external data has a status indicating, for example, "linked" or "not linked" to the closed network NW1. Therefore, the external data linking unit 532 can check whether or not there is any unlinked external data by referring to the status. If there is any 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 "linked".

[0074] (3-3) Production Management Department 533 The production management unit 533 has a function of generating information for managing production in the factory FC as external data. The production management unit 533 generates the external data based on the internal data linked by the external link relay unit 133 of the relay device 100 via the relay server 400. The production management unit 533 may also generate the external data based on the internal data and management information stored in the storage unit 520. The management information stored in the 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 that takes into account a long-term progress by also using the management information. As shown in FIG. 6, the production management unit 533 includes an equipment state confirmation unit 5331, an equipment control unit 5332, an inventory management unit 5333, and a monitoring unit 5334.

[0075] (3-3-1) Equipment Status Verification Section 5331 The equipment status checking unit 5331 has a function of checking the status of the production equipment 20 in the closed network NW1. The equipment status checking unit 5331 checks 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 check result as external data. The equipment status checking unit 5331 checks 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 is information indicating materials, jigs, etc. set in the production equipment 20, setting values ​​(setting information) set for the production equipment 20, and the like. In addition, the production information acquired during or after production is information indicating materials, jigs, etc. set in the production equipment 20, and information including current values ​​of items for which setting values ​​are set. In the following, an example will be described in which the equipment status confirmation unit 5331 confirms the status of the production equipment 20 before production by the production equipment 20. Hereinafter, the process performed by the equipment status confirmation unit 5331 is also referred to as "pre-production confirmation", and information indicating the confirmation result is also referred to as "confirmation result information".

[0076] In this embodiment, when starting production of a product, the user operates the operation terminal 300 to select a task to be started. When the user selects a task, the management control terminal 22 acquires production information from the production equipment 20 corresponding to the selected task. The production information acquired by the management control terminal 22 is linked to the cloud server 500 from the relay device 100 as internal data. The production information linked from the management control terminal 22 includes information indicating the materials and jigs used in the task selected by the user, the setting values ​​of the production equipment 20, and the like, and information indicating the materials and jigs actually set in the production equipment 20, the set values, and the like. Therefore, the equipment status confirmation unit 5331 can confirm, based on the linked production information, whether the correct materials and jigs are being used for the task to be started, whether there is a problem with the setting values ​​of the production equipment 20, and the like. Through this confirmation, the equipment status confirmation unit 5331 can confirm that the state of the production equipment 20 is correct if the correct materials and jigs are being used and there is no problem with the setting values.

[0077] (3-3-2) Equipment Control Unit 5332 The equipment control unit 5332 has a function of controlling the operation of the production equipment 20 in 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 or not control of the production equipment 20 is necessary based on the production information linked from the relay device 100 during production. If it is determined that control is necessary, the equipment control unit 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 items held up in the production line. Therefore, the equipment control unit 5332 can generate, as control information, an instruction to stop conveyance or an instruction to release the stop of conveyance according to the number of items held up from the linked production information. In addition, the production information linked from the relay device 100 may be production information acquired by the sensor terminal 10 and linked, or production information acquired from the production equipment 20 by the management control terminal 22 and linked from the management control terminal 22.

[0078] (3-3-3) Inventory Management Department 5333 The inventory management unit 5333 has a function of managing inventory related to production in the production facility 20 in the closed network NW1. The inventory management unit 5333 generates inventory information of products produced by the production facility 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 information indicating, for example, the number of products produced and the amount of materials used. Therefore, the inventory management unit 5333 can calculate the inventory number of produced products and the inventory number of materials from the linked production information. In addition, the inventory information generated by the inventory management unit 5333 may be used for pre-production confirmation by the equipment state confirmation unit 5331.

[0079] (3-3-4) Monitoring Department 5334 The monitoring unit 5334 has a function of monitoring production in the production facility 20 in 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 facility 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 the production status information based on the production information shared from the relay device 100 during production. The production information shared 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 shared production information.

[0080] Furthermore, the monitoring unit 5334 monitors for signs of abnormality occurring in production by the production facility 20, and when a sign is detected, generates information indicating the sign (hereinafter also referred to as "sign information") as monitoring information. For example, the monitoring unit 5334 generates the sign 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 operation state of the production facility 20. For this reason, the monitoring unit 5334 can monitor whether there is a sign of abnormality occurring in the operation state of the production facility 20 by monitoring changes in the linked production information.

[0081] As an example, the monitoring unit 5334 detects signs of an abnormality based on upper and lower limit value management, change amount management, continuous change, etc. In upper and lower limit value management, a sign is detected when a value indicated by production information is outside a set range. In change amount management, previously acquired production information is compared with currently acquired production information, and a sign is detected when the amount of change is equal to or greater than a set value. In continuous change, a sign is detected when changes are continuous (n-point continuous increase or decrease).

[0082] <7. Processing flow> The functional configuration of the cloud server 500 has been described above with reference to Fig. 6. Next, the flow of processing according to this embodiment will be described with reference to Figs.

[0083] (1) Overall process flow The overall flow of processing in the production management system 1 will be described with reference to FIGS.

[0084] (1-1) Collection of internal data The flow of processing in collecting internal data of the factory FC will be described with reference to Fig. 7. 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.

[0085] 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).

[0086] The management control terminal 22 acquires production information from the production facility 20 before 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).

[0087] The management system 30 updates the management information managed by the management system 30 itself (step S105). After updating, 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, the conversion terminal 31 transmits the converted management information to the relay device 100 (step S108).

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

[0089] 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, and the like shown in FIG. Next, the data processing unit 132 of the relay device 100 checks whether the acquired internal data needs to be processed (step S202). If processing is necessary (step S202 / YES), the process proceeds to step S203. On the other hand, if processing is not necessary (step S202 / NO), the process proceeds to step S204. When the process proceeds to step S203, the data processing unit 132 performs data processing on the internal data (step S203). After processing, the process proceeds to step S204. When the process proceeds to step S204, the external link relay unit 133 of the relay device 100 transmits the internal data to the relay server 400 via the network NW2 (step S204).

[0090] The conversion unit 431 of the relay server 400 analyzes the internal data received from the relay device 100 (step S205). At this time, the conversion unit 431 checks whether or not the internal data contains unauthorized data (step S206). If unauthorized data is present (step S206 / YES), the process proceeds to step S207. On the other hand, if unauthorized data is not present (step S206 / NO), the process proceeds to step S208. When the process proceeds to step S207, the conversion unit 431 removes the unauthorized data from the linked internal data (step S207). After the removal, 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).

[0091] 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).

[0092] (1-3) Acquisition of external data Next, a process flow for acquiring external data will be described with reference to Fig. 9. Fig. 9 is a sequence diagram showing an example of a process flow for acquiring external data according to this embodiment. Note that the process shown in Fig. 9 may be performed at any timing, regardless of whether the processes shown in Figs. 7 and 8 have been executed.

[0093] 9, first, the external data acquisition unit 134 of the relay device 100 checks whether it is time to acquire external data (step S301). If it is time to acquire the data (step S301 / YES), the process proceeds to step S302. On the other hand, if it is not time to acquire the data (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).

[0094] In the cloud server 500 that has received the external data acquisition request, the external data linking unit 532 checks whether or not there is any external data that has not been linked to the closed network NW1 among the external data stored in the storage unit 520 (step S303). If there is any 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, external data linking unit 532 acquires unlinked external data from 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).

[0095] In relay device 100 that has received the unlinked external data, external data acquisition unit 134 acquires the external data from communication unit 110 (step S307). Next, the internal link relay unit 135 of the relay device 100 transmits the external data acquired by the external data acquisition unit 134 to the on-premise server 200 (Step S308).

[0096] (1-4) Internal linkage of external data Next, a process flow in the internal linkage of external data will be described with reference to Fig. 10. Fig. 10 is a sequence diagram showing an example of a process flow in the internal linkage of external data according to this embodiment. The process shown in Fig. 10 is performed, for example, following step S308 of the process shown in Fig. 9.

[0097] 10, first, the conversion unit 231 of the on-premise server 200 analyzes the external data linked from the relay device 100 and checks whether or not there is any unauthorized data (step S401). If there is unauthorized data (step S401 / YES), the process proceeds to step S402. On the other hand, if there is no unauthorized data (step S401 / NO), the process proceeds to step S403. When the process proceeds to step S402, the conversion unit 231 removes the unauthorized data from the linked external data (step S402). After the removal, 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-premise server 200 generates a query based on the converted external data, and inserts the converted external data into the database of the storage unit 220 of the on-premise server 200 using the query, and stores the converted external data (step S404). Next, the internal linking unit 233 of the on-premise 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 the 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.

[0098] When the process proceeds to step S406, the internal cooperation part 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 (i.e., the management information) received from the on-premise server 200 (step S407). After the conversion, the conversion terminal 31 transmits the converted management information to the management system 30 (step S408). Next, the management system 30 updates the existing management information based on the received management information (step S409).

[0099] 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.

[0100] When the process proceeds to step S412, the output control unit 341 transmits the 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 transmits the control information to the control terminal 21 that corresponds to the production equipment 20 that is the target of control, for example, by referring to the contents indicated by the control information. The control terminal 21 that has received the control information controls the operation of the production equipment 20 that it manages based on the control information (step S413).

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

[0102] (2) Specific examples of processing Above, we have explained the overall process flow in the production management system 1. Next, we will explain a specific example of the process with reference to Figures 11 to 14. In the following, as an example, we will specifically explain the process flow from the start of production to its completion when the start of production is the starting point of the process.

[0103] (2-1) Processing flow from work selection to pre-production confirmation First, a process flow from work selection to pre-production confirmation will be described with reference to Fig. 11. Fig. 11 is a sequence diagram showing an example of a process flow from work selection to pre-production confirmation according to this embodiment.

[0104] As shown in FIG. 11, first, the worker operates the operation terminal 300 to select a task to be started (step S501). The operation terminal 300 that has accepted the operation from the worker transmits an instruction to stop the transfer to the production equipment 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 transfer (step S503).

[0105] Next, the management control terminal 22 acquires production information from the production equipment 20 that has stopped the transfer 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).

[0106] The equipment status checking unit 5331 of the cloud server 500 performs pre-production checking based on the received production information (step S506). After the pre-production checking, the equipment status checking unit 5331 generates checking 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 there is unlinked confirmation result information (e.g., the confirmation result information generated in step S507) when communication unit 510 of cloud server 500 receives the external data acquisition request from relay device 100. In this case, external data linking unit 532 of cloud server 500 acquires the unlinked confirmation result information and transmits it to operation terminal 300 via relay device 100 and on-premise 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).

[0107] (2-2) Process flow from confirmation of confirmation results by the worker to updating inventory Next, the flow of processing from confirmation of the confirmation result by the worker to updating the inventory will be described with reference to Fig. 12. Fig. 12 is a sequence diagram showing an example of the flow of processing from confirmation of the confirmation result by the worker to updating the inventory according to this embodiment. The processing shown in Fig. 12 is performed, for example, following step S510 of the processing shown in Fig. 11.

[0108] As shown in Fig. 12, first, the worker checks the confirmation results displayed on the operation terminal 300 (step S601). The worker checks whether all confirmations have been completed normally (step S602). If they have not been completed (step S602 / NO), the process proceeds to step S603. On the other hand, if they have been completed (step S602 / YES), the process proceeds to step S604. If the process proceeds to step S603, the worker takes corrective action so that all checks are completed normally (step S603). Corrective action may involve, for example, changing the materials and jigs set in the production equipment 20, correcting the setting values ​​set in the production equipment 20, and inputting additional information required for production. Note that the setting values ​​can also be changed all at once. After the change, the process returns to step S602.

[0109] When the process proceeds to step S604, the worker performs an operation to start production on the operation terminal 300 (step S604). The operation terminal 300 that has accepted the operation from the worker transmits an instruction to release the stop of the transport 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 the transfer (step S606), thereby starting production by the production facility 20.

[0110] After the start of production, the management control terminal 22 acquires production information from the production equipment 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).

[0111] (2-3) Processing flow for controlling production equipment using a cloud server Next, a process flow related to the control of the production facility 20 by the cloud server 500 will be described with reference to Fig. 13. Fig. 13 is a sequence diagram showing an example of a process flow related to the control of the production facility 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.

[0112] As shown in FIG. 13, first, the internal data management unit 531 of the cloud server 500 stores the production information received by the communication unit 510 from the relay server 400 in the storage unit 520 (step S701). Next, the equipment control unit 5332 of the cloud server 500 checks whether or not control of the production equipment 20 is necessary based on the production information (step S702). If control is necessary (step S702 / YES), the process proceeds to step S703. On the other hand, if control is not necessary (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 the 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 there is unlinked control information (e.g., the control information generated in step S703) when the communication unit 510 of the cloud server 500 receives the request to acquire external data from the relay device 100. In this case, the external data linking 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-premise server 200 (step S705).

[0113] 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 transmits the control information to the control terminal 21 that corresponds to the production equipment 20 that is the target of control, for example, by referring to the contents indicated by the control information. The control terminal 21 that has received the control information controls the operation of the production equipment 20 that it manages based on the control information (step S707).

[0114] (2-4) Processing flow for monitoring by cloud server Next, a process flow related to monitoring by the cloud server 500 will be described with reference to Fig. 14. Fig. 14 is a sequence diagram showing an example of a process flow related to monitoring by the cloud server 500 according to this embodiment. The process shown in Fig. 14 is performed, for example, before or after step S609 of the process shown in Fig. 12, or in parallel with step S609. In addition, the process shown in Fig. 14 may be performed, for example, before or after the process shown in Fig. 13, or in parallel with the process shown in Fig. 13.

[0115] As shown in FIG. 14, first, the internal data management unit 531 of the cloud server 500 stores the production information received by the communication unit 510 from the relay server 400 in the storage unit 520 (step S801). Next, the monitoring unit 5334 of the cloud server 500 monitors the production status in the production facility 20 and monitors for signs of 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 an abnormality is detected, the monitoring unit 5334 may generate monitoring information including only production status information.

[0116] Next, the monitoring unit 5334 checks whether a sign of an abnormality has been detected (step S804). If a sign of an abnormality has been detected (step S804 / YES), the process proceeds to step S805. On the other hand, if a sign of an abnormality has not been 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 equipment 20 so that the abnormality whose sign has been detected does not occur. 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). Assume that there is unlinked monitoring information (e.g., the monitoring information generated in step S803) or control information (e.g., the control information generated in step S805) when the communication unit 510 of the cloud server 500 receives the request to acquire external data from the relay device 100. 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-premise server 200 (step S807).

[0117] In the operation terminal 300 that has received the monitoring information, the output control unit 341 displays the monitoring information on the output unit 350 (step S808). The worker checks the monitoring status by checking the monitoring information displayed on the output unit 350 (step S809). The operation terminal 300 checks whether or not 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 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 the 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 transmits the control information to the control terminal 21 that corresponds to the production equipment 20 that is the target of control, for example, by referring to the contents indicated by the control information. The control terminal 21 that has received the control information controls the operation of the production equipment 20 that it manages based on the control information (step S812).

[0118] As described above, the production management system 1 of this embodiment periodically communicates from inside the closed network NW1 in the factory FC (production base) to an external system 3 outside the closed network NW1, and is equipped with an external data acquisition unit 134 that acquires external data from the external system 3 to link from the outside to the inside of the closed network NW1, and an internal linkage relay unit 135 that links the external data acquired by the external data acquisition unit 134 to equipment inside the closed network NW1.

[0119] With this configuration, the production management system 1 of this embodiment makes it possible to transmit data from outside the closed network NW1 to equipment inside the closed network NW1 for a production site such as a factory FC in which the closed network NW1 is constructed. Therefore, the production management system 1 according to this embodiment makes it possible to control equipment inside the closed network by transmitting data from the outside to the inside of the closed network. This enables workers and managers at the production site to remotely control the equipment inside the closed network NW1 from outside the closed network NW1 and to remotely perform inspection work.

[0120] The embodiment of the present invention has been described above. Note that some or all of the functions of the production management system 1 in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing the functions may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to realize the functions. Note that the term "computer system" here includes hardware such as an OS and peripheral devices. Furthermore, the term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into a computer system. Furthermore, the term "computer-readable recording medium" may include a medium that dynamically holds a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in that case. Furthermore, the above-mentioned program may be a program for realizing some of the functions described above, or may be a program that can realize the functions described above in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

[0121] Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes, etc. are possible within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0122] 1...production management 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 linkage relay unit, 134...external data acquisition unit, 135...internal linkage relay unit, 200...on-premise server, 210...communication unit, 220...storage unit, 230...control unit, 231...conversion unit, 2 32...insertion unit, 233...internal linking 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 linking unit, 533...production management unit, 5331...equipment status confirmation unit, 5332...equipment control unit, 5333...inventory management unit, 5334...monitoring unit, NW1...closed network, NW2...network

Claims

1. an external data acquisition unit that periodically communicates with an external system outside the closed network from inside the closed network at the production base and acquires external data from the external system that links from outside to inside the closed network; an internal linking relay unit that links the external data acquired by the external data acquisition unit to a server that manages the external data within the closed network; a conversion unit that analyzes the external data linked from the internal link relay unit to determine whether the data is fraudulent, and if the external data is not fraudulent, converts the data into a data format compatible with the internal system within the closed network, and if the external data is fraudulent, excludes the data from being linked to equipment included in the internal system without converting the data format; an insertion unit that inserts the external data converted by the conversion unit into a database of the server; Equipped with the conversion unit executes processing at the front end of the server, The insertion unit executes processing in the background of the server. Production management system.

2. an internal linking unit that links the external data converted by the conversion unit to the equipment corresponding to the external data; The production management system according to claim 1 , further comprising:

3. The internal linking unit checks whether the external data converted by the conversion unit is control information, display information, or management information, and if the external data is the control information or the display information, links the external data to an operation terminal, and if the external data is the management information, links the external data to a management system via the conversion terminal. The production management system according to claim 2 .

4. The production management system includes: an external system for managing production at the production base from outside the closed network; Furthermore, The external system a production management unit that generates information for managing production at the production base as the external data; The production management system according to claim 1 , comprising:

5. The production management department an equipment status confirmation unit that confirms whether the status of the production equipment within the closed network is correct before, during, or after production by the production equipment, and generates information indicating the confirmation result as the external data; The production management system according to claim 4, further comprising:

6. the equipment status confirmation unit confirms whether the status of the production equipment is correct based on information acquired from the production equipment within the closed network; The production management system according to claim 5 .

7. The production management department an equipment control unit that generates control information for controlling the operation of production equipment within the closed network as the external data; The production management system according to claim 4, further comprising:

8. The production management department an inventory management unit that generates inventory information of products produced by production facilities within the closed network as the external data; The production management system according to claim 4, further comprising:

9. The production management department a monitoring unit that monitors the production status of production equipment within the closed network and generates information indicating the monitored status as the external data; The production management system according to claim 4, further comprising:

10. the monitoring unit monitors for signs of abnormality occurring in production by the production equipment, and when the sign is detected, generates information indicating the sign as the external data. The production management system according to claim 9.

11. an internal data acquisition unit that acquires, within the closed network, internal data that links from inside the closed network to outside; an external link relay unit that links the internal data acquired by the internal data acquisition unit from inside the closed network to the external system; Furthermore, the production management 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 4 to 10.

12. an external data acquisition process in which an external data acquisition unit periodically communicates with an external system outside the closed network from inside the closed network at the production base, and acquires external data linked from the outside to the inside of the closed network from the external system; an internal link relay step in which an internal link relay unit links the external data acquired by the external data acquisition unit to a server that manages the external data within the closed network; a conversion process in which a conversion unit analyzes the external data linked from the internal link relay unit to determine whether the data is invalid, and if the external data is not invalid, converts the data into a data format compatible with the internal system within the closed network, and if the external data is invalid, excludes the data from being linked to equipment included in the internal system without converting the data format; an inserting step in which an inserting unit inserts the external data converted by the converting unit into a database of the server; Including, In the conversion process, the conversion unit executes a process on the front end of the server, In the insertion process, the insertion unit executes a process in the background of the server. Production management methods.

13. Computer, an external data acquisition means for periodically communicating with an external system outside the closed network from within the closed network at the production base, and acquiring external data from the external system that links from the outside to the inside of the closed network; an internal linking relay means for linking the external data acquired by the external data acquisition means to a server that manages the external data within the closed network; a conversion means for analyzing the external data linked from the internal link relay means to determine whether the data is unauthorized, and if the external data is not unauthorized, converting the external data into a data format compatible with the internal system within the closed network, and if the external data is unauthorized, excluding the external data from the data linked to the equipment included in the internal system without converting the data format; an inserting means for inserting the external data converted by the converting means into a database of the server; It functions as The conversion means executes processing at the front end of the server, The insertion means executes processing in the background of the server. program.

Images